[giow] (2) Add requirements for how to express file names in formdata

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=11452

git-svn-id: http://svn.whatwg.org/webapps@6206 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -52265,6 +52265,16 @@ <h5 id=multipart-form-data><span class=secno>4.10.22.6 </span>Multipart form dat
     not get converted to a 7-bit safe encoding as suggested in RFC
     2388).</p>
 
+    <p>File names included in the generated <code title="">multipart/form-data</code> resource (as part of file
+    fields) must use the character encoding selected above, though the
+    precise name may be approximated if necessary (e.g. newlines could
+    be removed from file names, quotes could be changed to "%22", and
+    characters not expressible in the selected character encoding
+    could be replaced by other characters). User agents must not use
+    the RFC 2231 encoding suggested by RFC 2388.</p> <!-- this isn't a
+    willful violation since 2388 doesn't make it a requirement, it
+    just vaguely suggests it -->
+
     <p>The boundary used by the user agent in generating the return
     value of this algorithm is the <dfn id=multipart/form-data-boundary-string><code title="">multipart/form-data</code> boundary string</dfn>. (This
     value is used to generate the MIME type of the form submission

index

@@ -52258,6 +52258,16 @@ fur
     not get converted to a 7-bit safe encoding as suggested in RFC
     2388).</p>
 
+    <p>File names included in the generated <code title="">multipart/form-data</code> resource (as part of file
+    fields) must use the character encoding selected above, though the
+    precise name may be approximated if necessary (e.g. newlines could
+    be removed from file names, quotes could be changed to "%22", and
+    characters not expressible in the selected character encoding
+    could be replaced by other characters). User agents must not use
+    the RFC 2231 encoding suggested by RFC 2388.</p> <!-- this isn't a
+    willful violation since 2388 doesn't make it a requirement, it
+    just vaguely suggests it -->
+
     <p>The boundary used by the user agent in generating the return
     value of this algorithm is the <dfn id=multipart/form-data-boundary-string><code title="">multipart/form-data</code> boundary string</dfn>. (This
     value is used to generate the MIME type of the form submission

source

@@ -59037,6 +59037,17 @@ fur
     not get converted to a 7-bit safe encoding as suggested in RFC
     2388).</p>
 
+    <p>File names included in the generated <code
+    title="">multipart/form-data</code> resource (as part of file
+    fields) must use the character encoding selected above, though the
+    precise name may be approximated if necessary (e.g. newlines could
+    be removed from file names, quotes could be changed to "%22", and
+    characters not expressible in the selected character encoding
+    could be replaced by other characters). User agents must not use
+    the RFC 2231 encoding suggested by RFC 2388.</p> <!-- this isn't a
+    willful violation since 2388 doesn't make it a requirement, it
+    just vaguely suggests it -->
+
     <p>The boundary used by the user agent in generating the return
     value of this algorithm is the <dfn><code
     title="">multipart/form-data</code> boundary string</dfn>. (This