Ignore:
Timestamp:
Jul 23, 2010, 2:19:25 AM (9 years ago)
Author:
julian.reschke@…
Message:

change citing style to match RFC Editor expectations (see <http://www.rfc-editor.org/rfc-style-guide/rfc-style>, Section 3.3)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r874 r879  
    408408  <t>
    409409    <x:h>Note:</x:h> This use of the term "character set" is more commonly
    410     referred to as a "character encoding." However, since HTTP and
     410    referred to as a "character encoding". However, since HTTP and
    411411    MIME share the same registry, it is important that the terminology
    412412    also be shared.
     
    444444<t>
    445445   Some HTTP/1.0 software has interpreted a Content-Type header without
    446    charset parameter incorrectly to mean "recipient should guess."
     446   charset parameter incorrectly to mean "recipient should guess".
    447447   Senders wishing to defeat this behavior &MAY; include a charset
    448448   parameter even when the charset is ISO-8859-1 (<xref target="ISO-8859-1"/>) and &SHOULD; do so when
     
    10291029<t>
    10301030   &SHOULD; be interpreted as "I prefer audio/basic, but send me any audio
    1031    type if it is the best available after an 80% mark-down in quality."
     1031   type if it is the best available after an 80% mark-down in quality".
    10321032</t>
    10331033<t>
     
    10491049   the preferred media types, but if they do not exist, then send the
    10501050   text/x-dvi representation, and if that does not exist, send the text/plain
    1051    representation."
     1051   representation".
    10521052</t>
    10531053<t>
     
    11801180         the Accept-Encoding field, then it is acceptable, unless it is
    11811181         accompanied by a qvalue of 0. (As defined in &qvalue;, a
    1182          qvalue of 0 means "not acceptable.")</t>
     1182         qvalue of 0 means "not acceptable".)</t>
    11831183
    11841184      <t>The special "*" symbol in an Accept-Encoding field matches any
     
    12611261<t>
    12621262   would mean: "I prefer Danish, but will accept British English and
    1263    other types of English."
     1263   other types of English".
    12641264   (see also <xref target="RFC4647" x:sec="2.3" x:fmt="of"/>)
    12651265</t>
     
    13861386   Multiple languages &MAY; be listed for content that is intended for
    13871387   multiple audiences. For example, a rendition of the "Treaty of
    1388    Waitangi," presented simultaneously in the original Maori and English
     1388   Waitangi", presented simultaneously in the original Maori and English
    13891389   versions, would call for
    13901390</t>
     
    13961396   does not mean that it is intended for multiple linguistic audiences.
    13971397   An example would be a beginner's language primer, such as "A First
    1398    Lesson in Latin," which is clearly intended to be used by an
     1398   Lesson in Latin", which is clearly intended to be used by an
    13991399   English-literate audience. In this case, the Content-Language would
    14001400   properly only include "en".
Note: See TracChangeset for help on using the changeset viewer.