- From: Eric Uhrhane via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 28 Sep 2011 21:16:47 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/file-system
In directory hutz:/tmp/cvs-serv22783/file-system
Modified Files:
file-writer.html
Log Message:
Fix issue and normative text on line-ending conversion [filesystem->operating
system].
Index: file-writer.html
===================================================================
RCS file: /sources/public/2009/dap/file-system/file-writer.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -d -r1.32 -r1.33
--- file-writer.html 22 Sep 2011 00:04:46 -0000 1.32
+++ file-writer.html 28 Sep 2011 21:16:45 -0000 1.33
@@ -209,8 +209,8 @@
<dt>in optional DOMString endings</dt>
<dd>
<div class='issue'>Can we do without endings? Any choice other
- than "transparent" can be implemented by the app author, and
- most file formats don't care about line endings. "Transparent"
+ than "native" can be implemented by the app author, and
+ most file formats don't care about line endings. "Native"
would be handy for sharing certain types of text files with apps
outside the browser [e.g. Makefiles on a system where make is
expecting \n will have issues if they're written with \r\n]. Is
@@ -237,10 +237,10 @@
<td>"native"</td>
<td>
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 <code>\r\n</code> pairs as the
- text was appended to the state of the BlobBuilder.
+ representation of the underlying host operating system. For
+ example, if the underlying OS is Windows, newlines will be
+ transformed into <code>\r\n</code> pairs as the text is
+ appended to the state of the BlobBuilder.
</td>
</tr>
</table>
Received on Wednesday, 28 September 2011 21:16:49 UTC