W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: [FileAPI] BlobBuilder.append("native")

From: Jarred Nicholls <jarred@sencha.com>
Date: Fri, 23 Sep 2011 10:04:41 -0400
Message-ID: <CANufG2P-7SRtpLSNaYw=wui2i01wr08jKqu2e7p_Rq_sWwpgeg@mail.gmail.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: public-webapps@w3.org
On Thu, Sep 22, 2011 at 7:47 PM, Glenn Maynard <glenn@zewt.org> wrote:

> > "native" Newlines must be transformed to the default line-ending
> representation of the underlying host filesystem. For example, if the
> underlying filesystem is FAT32, newlines would be transformed into \r\n
> pairs as the text was appended to the state of the BlobBuilder.
>
> This is a bit odd: most programs write newlines according to the convention
> of the host system, not based on peeking at the underlying filesystem.  You
> won't even know the filesystem if you're writing to a network drive.  I'd
> suggest "must be transformed according to the conventions of the local
> system", and let implementations decide what that is.  It should probably be
> explicit that the only valid options are \r\n and \n, or reading files back
> in which were transformed in this way will be difficult.
>

Agreed.


>
> Also, in the Issue above that, it seems to mean "native" where it says
> "transparent".
>
> --
> Glenn Maynard
>
>
>


-- 
................................................................

*Sencha*
Jarred Nicholls, Senior Software Architect
@jarrednicholls
<http://twitter.com/jarrednicholls>
Received on Friday, 23 September 2011 14:05:30 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT