- From: Simon Pieters <simonp@opera.com>
- Date: Fri, 23 Sep 2011 10:36:27 +0200
- To: public-webapps@w3.org, "Glenn Maynard" <glenn@zewt.org>
On Fri, 23 Sep 2011 01:47:15 +0200, 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. > > Also, in the Issue above that, it seems to mean "native" where it says > "transparent". Can we get away with always using \n? -- Simon Pieters Opera Software
Received on Friday, 23 September 2011 08:36:47 UTC