Changeset 118


Ignore:
Timestamp:
Jul 10, 2012, 3:23:35 AM (7 years ago)
Author:
duerst@…
Message:

converted remaining examples to <aonly>/<ionly> alternatives

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-iri-3987bis/draft-ietf-iri-3987bis.xml

    r117 r118  
    897897<t hangText="4.">http://xn--99zt52a.example.org/%E2%80%AE</t>
    898898<t hangText="5.">http://xn--99zt52a.example.org/%E2%80%AE</t>
    899 <t hangText="6.">http://&amp;#x7D0D;&amp;#x8C46;.example.org/%E2%80%AE</t>
     899  <t hangText="6."><aonly>http://&amp;#x7D0D;&amp;#x8C46;.example.org/%E2%80%AE</aonly><ionly>http://納豆.example.org/%E2%80%AE</ionly></t>
    900900</list></t>
    901901
    902902<t>Note that the label "xn--99zt52a" is converted to U+7D0D U+8C46
    903 (Japanese Natto). ((EDITOR NOTE: There is some inconsistency in this note.))</t>
     903(Japanese Natto<ionly>, 納豆</ionly>). ((EDITOR NOTE: There is some inconsistency in this note.))</t>
    904904
    905905</section> <!-- examples -->
     
    10191019<t>For example, for a document with a URI
    10201020of<vspace/>"http://www.example.org/r%C3%A9sum%C3%A9.html", it is
    1021 possible to construct a corresponding IRI (in XML notation, see <xref
    1022 target="sec-Notation"/>):
    1023 "http://www.example.org/r&amp;#xE9;sum&amp;#xE9;.html" ("&amp;#xE9;"
    1024 stands for the e-acute character, and "%C3%A9" is the UTF-8 encoded
    1025 and percent-encoded representation of that character). On the other
    1026 hand, for a document with a URI of
     1021possible to construct a corresponding IRI
     1022  <aonly>(in XML notation, see <xref target="sec-Notation"/>):
     1023    "http://www.example.org/r&amp;#xE9;sum&amp;#xE9;.html"
     1024    ("&amp;#xE9;" stands for the e-acute character, and "%C3%A9" is the UTF-8 encoded
     1025    and percent-encoded representation of that character).</aonly>
     1026  <ionly>: "http://www.example.org/résumé.html"
     1027    ("é" is the e-acute character, and "%C3%A9" is the UTF-8 encoded
     1028    and percent-encoded representation of that character).</ionly>
     1029  On the other hand, for a document with a URI of
    10271030"http://www.example.org/r%E9sum%E9.html", the percent-encoded octets
    10281031cannot be converted to actual characters in an IRI, as the
     
    10711074where the document name is encoded in iso-8859-1 based on server
    10721075settings, but where the fragment identifier is encoded in UTF-8 according
    1073 to <xref target="XPointer"/>. The IRI corresponding to the above
    1074 URI would be (in XML notation)<vspace/>"http://www.example.org/r%E9sum%E9.xml#r&amp;#xE9;sum&amp;#xE9;".</t>
     1076to <xref target="XPointer"/>. The IRI corresponding to the above URI would be
     1077  <aonly>(in XML notation)<vspace/>"http://www.example.org/r%E9sum%E9.xml#r&amp;#xE9;sum&amp;#xE9;".</aonly>
     1078  <ionly><vspace/>"http://www.example.org/r%E9sum%E9.xml#résumé".</ionly>
     1079</t>
    10751080
    10761081<t>Similar considerations apply to query parts. The functionality
     
    13291334identifiers should make the appropriate transformations. For example,
    13301335if a file system contains a file named
    1331 "r&amp;#xE9;sum&amp;#xE9;.html", a server should expose this as
     1336  <aonly>"r&amp;#xE9;sum&amp;#xE9;.html"</aonly><ionly>"résumé.html"</ionly>,
     1337  a server should expose this as
    13321338"r%C3%A9sum%C3%A9.html" in a URI, which allows use of
    1333 "r&amp;#xE9;sum&amp;#xE9;.html" in an IRI, even if locally the file
     1339  <aonly>"r&amp;#xE9;sum&amp;#xE9;.html"</aonly><ionly>"résumé.html"</ionly>
     1340  in an IRI, even if locally the file
    13341341name is kept in a character encoding other than UTF-8.
    13351342</t>
Note: See TracChangeset for help on using the changeset viewer.