Changeset 1101 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

08/01/11 14:27:21 (10 years ago)

Author:

julian.reschke@…

Message:

use mdash for long dashes, make use of dashes consistent

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (6 diffs)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -15 +15 @@
   <!ENTITY ID-MONTH "January">
   <!ENTITY ID-YEAR "2011">
+  <!ENTITY mdash "&#8212;">
   <!ENTITY notation                   "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -573 +574 @@
    HTTP/1.1, and an example set of corresponding Reason-Phrase values, are
    presented below. The reason phrases listed here are only
-   recommendations -- they &MAY; be replaced by local equivalents without
+   recommendations &mdash; they &MAY; be replaced by local equivalents without
    affecting the protocol.
 </t>
@@ -1159 +1160 @@
 </artwork></figure>
 <t>
-   Other HTTP mechanisms can be used normally with the CONNECT method --
+   Other HTTP mechanisms can be used normally with the CONNECT method &mdash;
    except end-to-end protocol Upgrade requests, since the
    tunnel must be established first.
@@ -1854 +1855 @@
    individuals no longer working at the server's site. It is not
    necessary to mark all permanently unavailable resources as "gone" or
-   to keep the mark for any length of time -- that is left to the
+   to keep the mark for any length of time &mdash; that is left to the
    discretion of the server owner.
 </t>
@@ -2105 +2106 @@
 </t>
 <t>
-   A proxy &MUST-NOT; modify the Allow header field -- it does not need to
+   A proxy &MUST-NOT; modify the Allow header field &mdash; it does not need to
    understand all the methods specified in order to handle them according to
    the generic message handling rules.
@@ -2550 +2551 @@
 <section title="Status Code Registry" anchor="status.code.registration">
 <t>
-   The registration procedure for HTTP Status Codes -- previously defined
-   in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/> -- is now defined
+   The registration procedure for HTTP Status Codes &mdash; previously defined
+   in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/> &mdash; is now defined
    by <xref target="status.code.registry"/> of this document.
 </t>