Ignore:
Timestamp:
Dec 31, 2007, 9:08:48 AM (12 years ago)
Author:
julian.reschke@…
Message:

Resolve #66: categorize ISO-8859 reference as normative, but just cite ISO8859-1. Add references to part 3 and 6 as well.

File:
1 edited

Legend:

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

    r120 r121  
    292292   charset parameter incorrectly to mean "recipient should guess."
    293293   Senders wishing to defeat this behavior &MAY; include a charset
    294    parameter even when the charset is ISO-8859-1 and &SHOULD; do so when
     294   parameter even when the charset is ISO-8859-1 (<xref target="ISO-8859-1"/>) and &SHOULD; do so when
    295295   it is known that it will not confuse the recipient.
    296296</t>
     
    14531453
    14541454<references title="Normative References">
     1455
     1456<reference anchor="ISO-8859-1">
     1457  <front>
     1458    <title>
     1459     Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
     1460    </title>
     1461    <author>
     1462      <organization>International Organization for Standardization</organization>
     1463    </author>
     1464    <date year="1998"/>
     1465  </front>
     1466  <seriesInfo name="ISO/IEC" value="8859-1:1998"/>
     1467</reference>
    14551468
    14561469<reference anchor="Part1">
Note: See TracChangeset for help on using the changeset viewer.