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/p3-payload.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 notation-abnf            "<xref target='Part1' x:rel='#notation.abnf' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    607608<section title="Multipart Types" anchor="multipart.types">
    608609<t>
    609    MIME provides for a number of "multipart" types -- encapsulations of
     610   MIME provides for a number of "multipart" types &mdash; encapsulations of
    610611   one or more representations within a single message-body. All multipart
    611612   types share a common syntax, as defined in <xref target="RFC2046" x:sec="5.1.1" x:fmt="of"/>,
     
    824825   which representation, among those available from the server,
    825826   would be best for the server to deliver. For this reason, HTTP
    826    provides mechanisms for "content negotiation" -- a process of
     827   provides mechanisms for "content negotiation" &mdash; a process of
    827828   allowing selection of a representation of a given resource,
    828829   when more than one is available.
     
    14011402</t>
    14021403<t>
    1403    Content-Language &MAY; be applied to any media type -- it is not
     1404   Content-Language &MAY; be applied to any media type &mdash; it is not
    14041405   limited to textual documents.
    14051406</t>
     
    15441545   or Content-Encoding header field, it is assumed that the content
    15451546   of the body-part has had the encoding applied, and the body-part is
    1546    included in the Content-MD5 digest as is -- i.e., after the
     1547   included in the Content-MD5 digest as is &mdash; i.e., after the
    15471548   application. The Transfer-Encoding header field is not allowed within
    15481549   body-parts.
     
    28872888    <t>
    28882889      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/68"/>:
    2889       "Encoding References Normative" -- rephrase the annotation and reference
     2890      "Encoding References Normative" &mdash; rephrase the annotation and reference
    28902891      <xref target="BCP97"/>.
    28912892    </t>
Note: See TracChangeset for help on using the changeset viewer.