FYI - the W3C versions of the File API's was done back in April of 2011. Inquiring minds can see the history in my repo: https://github.com/becka11y/phonegap-iphone/blob/master/PhoneGapLib/Classes/File.m
On Thu, Jan 10, 2013 at 12:12 PM, Becky Gibson <[email protected]>wrote: > I put this in when we implemented the File APIs as it was the only way > that I could get international /multi-byte characters to be supported. > The implementation was way before iOS 5 so maybe the embedded browser or > iOS internals have changed. > > -becky > > > > On Thu, Jan 10, 2013 at 11:26 AM, Braden Shepherdson > <[email protected]>wrote: > >> Yes, that's one of the tests in mobile-spec, and it works fine without the >> escaping. >> >> >> On Thu, Jan 10, 2013 at 11:24 AM, Marcel Kinard <[email protected]> >> wrote: >> >> > Can it pass non-ascii / multi-byte characters correctly without the >> > escaping? >> > >> > >> > On 1/10/2013 10:55 AM, Braden Shepherdson wrote: >> > >> >> Becky, do you know why this escaping was originally put in place? From >> our >> >> investigations it is unnecessary on iOS 5.0, 5.1 and 6, so we can drop >> it, >> >> and the iOS-specific readAsText implementation. >> >> >> >> If no one can remember why it was there (its existence predates the >> >> porting >> >> to Apache repos, so I can't see the commit that added it) and it seems >> to >> >> pass all the tests, then I vote to remove this extra complexity. >> >> >> >> Braden >> >> >> >> >> > >> > >
