Changeset 1143 for draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

Timestamp:

26/02/11 11:26:02 (11 years ago)

Author:

julian.reschke@…

Message:

use consistent quoting style for parameter names

File:

• draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml (modified) (4 diffs)

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

@@ -836 +836 @@
 <t>
   <list style="symbols">
-    <t>Include a 'filename' parameter when US-ASCII is sufficiently
+    <t>Include a "filename" parameter when US-ASCII is sufficiently
     expressive.</t>
     <t>Use the 'token' form of the filename parameter only when it does not
@@ -851 +851 @@
     most existing implementations will decode them as ISO-8859-1, some
     will apply heuristics to detect UTF-8, and thus might fail on certain names.</t>
-    <t>Include a 'filename*' parameter where the desired filename cannot be
-    expressed faithfully using the 'filename' form. Note that legacy user
-    agents will not process this, and will fall back to using the 'filename'
+    <t>Include a "filename*" parameter where the desired filename cannot be
+    expressed faithfully using the "filename" form. Note that legacy user
+    agents will not process this, and will fall back to using the "filename"
     parameter's content.
     </t>
-    <t>When a 'filename*' parameter is sent, to also generate a 'filename'
-    parameter as a fallback for user agents that do not support the 'filename*'
+    <t>When a "filename*" parameter is sent, to also generate a "filename"
+    parameter as a fallback for user agents that do not support the "filename*"
     form, if possible. This can be done by substituting characters with
     US-ASCII sequences (e.g., Unicode character point U+00E4 (LATIN SMALL
@@ -863 +863 @@
     some locales. 
     </t>
-    <t>When a 'filename' parameter is included as a fallback (as per above),
-    'filename' should occur first, due to parsing problems in some existing
+    <t>When a "filename" parameter is included as a fallback (as per above),
+    "filename" should occur first, due to parsing problems in some existing
     implementations.
     <cref anchor="fallbackbug" source="jre">
@@ -870 +870 @@
     Firefox 5.</cref>
     </t>
-    <t>Use UTF-8 as the encoding of the 'filename*' parameter, when present,
+    <t>Use UTF-8 as the encoding of the "filename*" parameter, when present,
     because at least one existing implementation only implements that encoding.</t>
   </list>