Ignore:
Timestamp:
Jan 8, 2011, 6:27:21 AM (9 years ago)
Author:
julian.reschke@…
Message:

use mdash for long dashes, make use of dashes consistent

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1099 r1101  
    1515  <!ENTITY ID-MONTH "January">
    1616  <!ENTITY ID-YEAR "2011">
     17  <!ENTITY mdash "&#8212;">
    1718  <!ENTITY notation                   "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1819  <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    573574   HTTP/1.1, and an example set of corresponding Reason-Phrase values, are
    574575   presented below. The reason phrases listed here are only
    575    recommendations -- they &MAY; be replaced by local equivalents without
     576   recommendations &mdash; they &MAY; be replaced by local equivalents without
    576577   affecting the protocol.
    577578</t>
     
    11591160</artwork></figure>
    11601161<t>
    1161    Other HTTP mechanisms can be used normally with the CONNECT method --
     1162   Other HTTP mechanisms can be used normally with the CONNECT method &mdash;
    11621163   except end-to-end protocol Upgrade requests, since the
    11631164   tunnel must be established first.
     
    18541855   individuals no longer working at the server's site. It is not
    18551856   necessary to mark all permanently unavailable resources as "gone" or
    1856    to keep the mark for any length of time -- that is left to the
     1857   to keep the mark for any length of time &mdash; that is left to the
    18571858   discretion of the server owner.
    18581859</t>
     
    21052106</t>
    21062107<t>
    2107    A proxy &MUST-NOT; modify the Allow header field -- it does not need to
     2108   A proxy &MUST-NOT; modify the Allow header field &mdash; it does not need to
    21082109   understand all the methods specified in order to handle them according to
    21092110   the generic message handling rules.
     
    25502551<section title="Status Code Registry" anchor="status.code.registration">
    25512552<t>
    2552    The registration procedure for HTTP Status Codes -- previously defined
    2553    in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/> -- is now defined
     2553   The registration procedure for HTTP Status Codes &mdash; previously defined
     2554   in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/> &mdash; is now defined
    25542555   by <xref target="status.code.registry"/> of this document.
    25552556</t>
Note: See TracChangeset for help on using the changeset viewer.