Changeset 116


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

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

File:
1 edited

Legend:

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

    r115 r116  
    658658 
    659659  <t>For example, the IRI
    660     <vspace/>"http://r&amp;#xE9;sum&amp;#xE9;.example.org"<vspace/> will be
     660    <vspace/><aonly>"http://r&amp;#xE9;sum&amp;#xE9;.example.org"</aonly><ionly>"http://résumé.example.org"</ionly><vspace/> will be
    661661    converted to <vspace/>"http://r%C3%A9sum%C3%A9.example.org".</t>
    662662
     
    690690
    691691<t>For example, the IRI
    692 <vspace/>"http://r&amp;#xE9;sum&amp;#xE9;.example.org"<vspace/> is
     692  <vspace/><aonly>"http://r&amp;#xE9;sum&amp;#xE9;.example.org"</aonly><ionly>"http://résumé.example.org"</ionly><vspace/> is
    693693converted to <vspace/>"http://xn--rsum-bad.example.org".</t>
    694694  <t>This conversion for ireg-name will be better able to deal with legacy
     
    705705necessary conversions at the appropriate point. Example: Trying to
    706706validate the Web page at<vspace/>
    707 http://r&amp;#xE9;sum&amp;#xE9;.example.org would lead to an IRI of
    708 <vspace/>http://validator.w3.org/check?uri=http%3A%2F%2Fr&amp;#xE9;sum&amp;#xE9;.<vspace/>example.org,
     707  <aonly>http://r&amp;#xE9;sum&amp;#xE9;.example.org</aonly><ionly>http://résumé.example.org</ionly>
     708  would lead to an IRI of
     709  <vspace/>http://validator.w3.org/check?uri=http%3A%2F%2F<aonly>r&amp;#xE9;sum&amp;#xE9;</aonly><ionly>résumé</ionly><vspace/>.example.org,
    709710which would convert to a URI
    710711of<vspace/>http://validator.w3.org/check?uri=http%3A%2F%2Fr%C3%A9sum%C3%A9.<vspace/>example.org.
    711712The server-side implementation is responsible for making the
    712713necessary conversions to be able to retrieve the Web page.</t>
    713 
     714 
    714715<t hangText="Note:">In this process, characters allowed in URI
    715716references and existing percent-encoded sequences are not encoded further.
     
    718719
    719720For example, an IRI of
    720 <vspace/>"http://www.example.org/red%09ros&amp;#xE9;#red"
    721 (in XML notation) is converted to
     721<vspace/><aonly>"http://www.example.org/red%09ros&amp;#xE9;#red"
     722  (in XML notation)</aonly><ionly>"http://www.example.org/red%09rosé#red"</ionly>
     723  is converted to
    722724<vspace/>"http://www.example.org/red%09ros%C3%A9#red", not to
    723725something like
     
    857859<t hangText="3.">http://www.example.org/D&lt;c3&gt;&lt;bc&gt;rst</t>
    858860<t hangText="4.">http://www.example.org/D&lt;c3&gt;&lt;bc&gt;rst</t>
    859 <t hangText="5.">http://www.example.org/D&amp;#xFC;rst</t>
    860 <t hangText="6.">http://www.example.org/D&amp;#xFC;rst</t>
     861  <t hangText="5."><aonly>http://www.example.org/D&amp;#xFC;rst</aonly><ionly>http://www.example.org/Dürst</ionly></t>
     862  <t hangText="6."><aonly>http://www.example.org/D&amp;#xFC;rst</aonly><ionly>http://www.example.org/Dürst</ionly></t>
    861863</list>
    862864</t>
Note: See TracChangeset for help on using the changeset viewer.