Re: File API: File's name property

On Sep 3, 2013, at 12:28 PM, Anne van Kesteren wrote:

> On Tue, Sep 3, 2013 at 5:14 PM, Glenn Maynard <glenn@zewt.org> wrote:
>> On Tue, Sep 3, 2013 at 10:17 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
>>> I don't think you want those conversion semantics for name. I do think
>>> we want the value space for names across different systems to be
>>> equivalent, which if we support zip basically means bytes.
>> 
>> I don't really understand the suggestion of using a ByteString for
>> File.name.  Can you explain how that wouldn't break
>> https://zewt.org/~glenn/picker.html, if the user picks a file named
>> "漢字.txt"?
> 
> ByteString doesn't work. A byte sequence might. If the platform does
> file names in Unicode it would be converted to bytes using utf-8.


Which in fact is how I think we should do File.name.  We'll stick to DOMString, but think it should specify a conversion to a byte sequence using utf-8.  And, restrict separators such as "/" and "\".

-- A*

Received on Tuesday, 3 September 2013 16:32:32 UTC