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/p1-messaging.xml

    r1099 r1101  
    1515  <!ENTITY ID-MONTH "January">
    1616  <!ENTITY ID-YEAR "2011">
     17  <!ENTITY mdash "&#8212;">
    1718  <!ENTITY caching-overview       "<xref target='Part6' x:rel='#caching.overview' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1819  <!ENTITY cache-incomplete       "<xref target='Part6' x:rel='#errors.or.incomplete.response.cache.behavior' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    961962   the "https" scheme (below) is used for servers that require an SSL/TLS
    962963   transport layer on a connection. Other protocols might also be used to
    963    provide access to "http" identified resources --- it is only the
     964   provide access to "http" identified resources &mdash; it is only the
    964965   authoritative interface used for mapping the namespace that is
    965966   specific to TCP.
     
    35693570        </t>
    35703571        <t hangText="msgtype:">
    3571           The message type -- "request" or "response". If not
     3572          The message type &mdash; "request" or "response". If not
    35723573          present, the type can be determined from the first
    35733574          line of the body.
     
    36383639        </t>
    36393640        <t hangText="msgtype:">
    3640           The message type -- "request" or "response". If not
     3641          The message type &mdash; "request" or "response". If not
    36413642          present, the type can be determined from the first
    36423643          line of the body.
     
    37253726<section title="Upgrade Token Registration" anchor="upgrade.token.registration">
    37263727<t>
    3727    The registration procedure for HTTP Upgrade Tokens -- previously defined
    3728    in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/> -- is now defined
     3728   The registration procedure for HTTP Upgrade Tokens &mdash; previously defined
     3729   in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/> &mdash; is now defined
    37293730   by <xref target="upgrade.token.registry"/> of this document.
    37303731</t>
     
    38953896<t>
    38963897   HTTP has evolved considerably over the years. It has
    3897    benefited from a large and active developer community--the many
    3898    people who have participated on the www-talk mailing list--and it is
     3898   benefited from a large and active developer community &mdash; the many
     3899   people who have participated on the www-talk mailing list &mdash; and it is
    38993900   that community which has been most responsible for the success of
    39003901   HTTP and of the World-Wide Web in general. Marc Andreessen, Robert
     
    52675268    <t>
    52685269      Add rules for terms imported from URI spec ("absoluteURI", "authority",
    5269       "path-absolute", "port", "query", "relativeURI", "host) -- these will
     5270      "path-absolute", "port", "query", "relativeURI", "host) &mdash; these will
    52705271      have to be updated when switching over to RFC3986.
    52715272    </t>
Note: See TracChangeset for help on using the changeset viewer.