Ignore:
Timestamp:
Feb 26, 2011, 3:26:02 AM (9 years ago)
Author:
julian.reschke@…
Message:

use consistent quoting style for parameter names

Location:
draft-ietf-httpbis-content-disp/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

    r1142 r1143  
    910910      <p id="rfc.section.D.p.2"> </p>
    911911      <ul>
    912          <li>Include a 'filename' parameter when US-ASCII is sufficiently expressive.</li>
     912         <li>Include a "filename" parameter when US-ASCII is sufficiently expressive.</li>
    913913         <li>Use the 'token' form of the filename parameter only when it does not contain disallowed characters (e.g., spaces); in such
    914914            cases, the quoted-string form should be used.
    … …  
    923923            some will apply heuristics to detect UTF-8, and thus might fail on certain names.
    924924         </li>
    925          <li>Include a 'filename*' parameter where the desired filename cannot be expressed faithfully using the 'filename' form. Note
    926             that legacy user agents will not process this, and will fall back to using the 'filename' parameter's content.
    927          </li>
    928          <li>When a 'filename*' parameter is sent, to also generate a 'filename' parameter as a fallback for user agents that do not support
    929             the 'filename*' form, if possible. This can be done by substituting characters with US-ASCII sequences (e.g., Unicode character
     925         <li>Include a "filename*" parameter where the desired filename cannot be expressed faithfully using the "filename" form. Note
     926            that legacy user agents will not process this, and will fall back to using the "filename" parameter's content.
     927         </li>
     928         <li>When a "filename*" parameter is sent, to also generate a "filename" parameter as a fallback for user agents that do not support
     929            the "filename*" form, if possible. This can be done by substituting characters with US-ASCII sequences (e.g., Unicode character
    930930            point U+00E4 (LATIN SMALL LETTER A WITH DIARESIS) by "ae"). Note that this may not be possible in some locales.
    931931         </li>
    932          <li>When a 'filename' parameter is included as a fallback (as per above), 'filename' should occur first, due to parsing problems
     932         <li>When a "filename" parameter is included as a fallback (as per above), "filename" should occur first, due to parsing problems
    933933            in some existing implementations. <span class="comment" id="fallbackbug">[<a href="#fallbackbug" class="smpl">fallbackbug</a>: Firefox is known to pick the wrong parameter; a bug fix is scheduled for Firefox 5. --jre]</span>
    934934         </li>
    935          <li>Use UTF-8 as the encoding of the 'filename*' parameter, when present, because at least one existing implementation only implements
     935         <li>Use UTF-8 as the encoding of the "filename*" parameter, when present, because at least one existing implementation only implements
    936936            that encoding.
    937937         </li>

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

    r1142 r1143  
    836836<t>
    837837  <list style="symbols">
    838     <t>Include a 'filename' parameter when US-ASCII is sufficiently
     838    <t>Include a "filename" parameter when US-ASCII is sufficiently
    839839    expressive.</t>
    840840    <t>Use the 'token' form of the filename parameter only when it does not
    … …  
    851851    most existing implementations will decode them as ISO-8859-1, some
    852852    will apply heuristics to detect UTF-8, and thus might fail on certain names.</t>
    853     <t>Include a 'filename*' parameter where the desired filename cannot be
    854     expressed faithfully using the 'filename' form. Note that legacy user
    855     agents will not process this, and will fall back to using the 'filename'
     853    <t>Include a "filename*" parameter where the desired filename cannot be
     854    expressed faithfully using the "filename" form. Note that legacy user
     855    agents will not process this, and will fall back to using the "filename"
    856856    parameter's content.
    857857    </t>
    858     <t>When a 'filename*' parameter is sent, to also generate a 'filename'
    859     parameter as a fallback for user agents that do not support the 'filename*'
     858    <t>When a "filename*" parameter is sent, to also generate a "filename"
     859    parameter as a fallback for user agents that do not support the "filename*"
    860860    form, if possible. This can be done by substituting characters with
    861861    US-ASCII sequences (e.g., Unicode character point U+00E4 (LATIN SMALL
    … …  
    863863    some locales.
    864864    </t>
    865     <t>When a 'filename' parameter is included as a fallback (as per above),
    866     'filename' should occur first, due to parsing problems in some existing
     865    <t>When a "filename" parameter is included as a fallback (as per above),
     866    "filename" should occur first, due to parsing problems in some existing
    867867    implementations.
    868868    <cref anchor="fallbackbug" source="jre">
    … …  
    870870    Firefox 5.</cref>
    871871    </t>
    872     <t>Use UTF-8 as the encoding of the 'filename*' parameter, when present,
     872    <t>Use UTF-8 as the encoding of the "filename*" parameter, when present,
    873873    because at least one existing implementation only implements that encoding.</t>
    874874  </list>
Note: See TracChangeset for help on using the changeset viewer.