Changeset 1101 for draft-ietf-httpbis/latest/p1-messaging.xml

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:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (7 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -15 +15 @@
   <!ENTITY ID-MONTH "January">
   <!ENTITY ID-YEAR "2011">
+  <!ENTITY mdash "&#8212;">
   <!ENTITY caching-overview       "<xref target='Part6' x:rel='#caching.overview' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY cache-incomplete       "<xref target='Part6' x:rel='#errors.or.incomplete.response.cache.behavior' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -961 +962 @@
    the "https" scheme (below) is used for servers that require an SSL/TLS
    transport layer on a connection. Other protocols might also be used to
-   provide access to "http" identified resources --- it is only the
+   provide access to "http" identified resources &mdash; it is only the
    authoritative interface used for mapping the namespace that is
    specific to TCP.
@@ -3569 +3570 @@
         </t>
         <t hangText="msgtype:">
-          The message type -- "request" or "response". If not
+          The message type &mdash; "request" or "response". If not
           present, the type can be determined from the first
           line of the body.
@@ -3638 +3639 @@
         </t>
         <t hangText="msgtype:">
-          The message type -- "request" or "response". If not
+          The message type &mdash; "request" or "response". If not
           present, the type can be determined from the first
           line of the body.
@@ -3725 +3726 @@
 <section title="Upgrade Token Registration" anchor="upgrade.token.registration">
 <t>
-   The registration procedure for HTTP Upgrade Tokens -- previously defined
-   in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/> -- is now defined
+   The registration procedure for HTTP Upgrade Tokens &mdash; previously defined
+   in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/> &mdash; is now defined
    by <xref target="upgrade.token.registry"/> of this document.
 </t>
@@ -3895 +3896 @@
 <t>
    HTTP has evolved considerably over the years. It has
-   benefited from a large and active developer community--the many
-   people who have participated on the www-talk mailing list--and it is
+   benefited from a large and active developer community &mdash; the many
+   people who have participated on the www-talk mailing list &mdash; and it is
    that community which has been most responsible for the success of
    HTTP and of the World-Wide Web in general. Marc Andreessen, Robert
@@ -5267 +5268 @@
     <t>
       Add rules for terms imported from URI spec ("absoluteURI", "authority",
-      "path-absolute", "port", "query", "relativeURI", "host) -- these will
+      "path-absolute", "port", "query", "relativeURI", "host) &mdash; these will
       have to be updated when switching over to RFC3986.
     </t>