Changeset 133


Ignore:
Timestamp:
Oct 12, 2012, 1:39:26 AM (7 years ago)
Author:
duerst@…
Message:

internal reformatting of examples in preparation of adding Arabic/Hebrew? versions; adding some additional explanatory text

File:
1 edited

Legend:

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

    r132 r133  
    124124          While all these versions are identical in their technical content,
    125125          the HTML, PDF, and UTF-8 plaintext versions show non-Unicode characters directly.
    126           This often makes it easier to understand examples, and readers are therefore advised
     126          This often makes it easier to understand examples, and readers are therefore strongly advised
    127127          to consult these versions in preference or as a supplement to the ASCII version.</t>
    128128      </section>
    129129      <section title="Notation">
    130         <t>In this document, "Bidi Notation" is used for the given Bidi IRI
     130        <t>In this document, "Bidi Notation", abbreviated "BN" is used for the given Bidi IRI
    131131          examples as follows: Lower case letters a-z stand for characters that
    132132          are written with a left to right ordering (such as Latin characters),
    133133          whereas upper case letters A-Z represent characters that are written
    134           right to left (such as Arqbic or Hebrew characters). Numbers and
     134          right to left (such as Arabic or Hebrew characters). Numbers and
    135135          symbols are the same.</t>
    136136        <t> In this document, the key words "MUST", "MUST NOT", "REQUIRED",
     
    261261        block (including slashes and other special characters) from right to
    262262        left, then continue at the next unread ltr character.</t>
     263      <t>Please note that "BN" stands for "Bidi Notation", see <eref target="Notation" /></t>
     264
    263265      <t>Example 1: A single component with rtl characters is inverted:
    264         <vspace/>Logical representation:
    265         "http://ab.CDEFGH.ij/kl/mn/op.html"<vspace/>Visual representation:
    266         "http://ab.HGFEDC.ij/kl/mn/op.html"<vspace/>Components can be read one
     266
     267        <vspace/>Logical representation (BN): "http://ab.CDEFGH.ij/kl/mn/op.html"
     268        <vspace/>Visual representation (BN): "http://ab.HGFEDC.ij/kl/mn/op.html"
     269
     270        <vspace/>Components can be read one
    267271        by one, and each component can be read in its natural direction.</t>
     272
    268273      <t>Example 2: More than one consecutive component with rtl characters is
    269         inverted as a whole: <vspace/>Logical representation:
    270         "http://ab.CDE.FGH/ij/kl/mn/op.html"<vspace/>Visual representation:
    271         "http://ab.HGF.EDC/ij/kl/mn/op.html"<vspace/> A sequence of rtl
     274        inverted as a whole:
     275
     276        <vspace/>Logical representation (BN): "http://ab.CDE.FGH/ij/kl/mn/op.html"
     277        <vspace/>Visual representation (BN): "http://ab.HGF.EDC/ij/kl/mn/op.html"
     278
     279        <vspace/> A sequence of rtl
    272280        components is read rtl, in the same way as a sequence of rtl words is
    273281        read rtl in a bidi text.</t>
     282
    274283      <t>Example 3: All components of an IRI (except for the scheme) are rtl.
    275         All rtl components are inverted overall: <vspace/>Logical
    276         representation: "http://AB.CD.EF/GH/IJ/KL?MN=OP;QR=ST#UV"<vspace/>Visual
    277         representation: "http://VU#TS=RQ;PO=NM?LK/JI/HG/FE.DC.BA"<vspace/> The
     284        All rtl components are inverted overall:
     285
     286        <vspace/>Logical representation (BN): "http://AB.CD.EF/GH/IJ/KL?MN=OP;QR=ST#UV"
     287        <vspace/>Visual representation (BN): "http://VU#TS=RQ;PO=NM?LK/JI/HG/FE.DC.BA"
     288
     289        <vspace/> The
    278290        whole IRI (except the scheme) is read rtl. Delimiters between rtl
    279291        components stay between the respective components; delimiters between
    280292        ltr and rtl components don't move.</t>
     293
    281294      <t>Example 4: Each of several sequences of rtl components is inverted on
    282         its own: <vspace/>Logical representation:
    283         "http://AB.CD.ef/gh/IJ/KL.html"<vspace/>Visual representation:
    284         "http://DC.BA.ef/gh/LK/JI.html"<vspace/> Each sequence of rtl components
     295        its own:
     296
     297        <vspace/>Logical representation (BN): "http://AB.CD.ef/gh/IJ/KL.html"
     298        <vspace/>Visual representation (BN): "http://DC.BA.ef/gh/LK/JI.html"
     299
     300        <vspace/> Each sequence of rtl components
    285301        is read rtl, in the same way as each sequence of rtl words in an ltr
    286302        text is read rtl.</t>
     303
    287304      <t>Example 5: Example 2, applied to components of different kinds:
    288         <vspace/>Logical representation: "http://ab.cd.EF/GH/ij/kl.html"
    289         <vspace/>Visual representation: "http://ab.cd.HG/FE/ij/kl.html"<vspace/>
     305
     306        <vspace/>Logical representation (BN): "http://ab.cd.EF/GH/ij/kl.html"
     307        <vspace/>Visual representation (BN): "http://ab.cd.HG/FE/ij/kl.html"
     308
     309        <vspace/>
    290310        The inversion of the domain name label and the path component may be
    291311        unexpected, but it is consistent with other bidi behavior. For
     
    294314        Bidirectional Algorithm. After "http://ab.cd." one reads the RTL block
    295315        "E-F-slash-G-H", which corresponds to the logical representation. </t>
     316
    296317      <t>Example 6: Same as Example 5, with more rtl components:
    297         <vspace/>Logical representation:
    298         "http://ab.CD.EF/GH/IJ/kl.html"<vspace/>Visual representation:
    299         "http://ab.JI/HG/FE.DC/kl.html"<vspace/> The inversion of the domain
     318        <vspace/>Logical representation (BN): "http://ab.CD.EF/GH/IJ/kl.html"
     319        <vspace/>Visual representation (BN): "http://ab.JI/HG/FE.DC/kl.html"
     320       
     321        <vspace/> The inversion of the domain
    300322        name labels and the path components may be easier to identify because
    301323        the delimiters also move.</t>
    302       <t>Example 7: A single rtl component includes digits: <vspace/>Logical
    303         representation: "http://ab.CDE123FGH.ij/kl/mn/op.html"<vspace/>Visual
    304         representation: "http://ab.HGF123EDC.ij/kl/mn/op.html"<vspace/> Numbers
     324     
     325      <t>Example 7: A single rtl component includes digits:
     326
     327        <vspace/>Logical representation (BN): "http://ab.CDE123FGH.ij/kl/mn/op.html"
     328        <vspace/>Visual representation (BN): "http://ab.HGF123EDC.ij/kl/mn/op.html"
     329
     330        <vspace/> Numbers
    305331        are written ltr in all cases but are treated as an additional embedding
    306332        inside a run of rtl characters. This is completely consistent with usual
    307333        bidirectional text.</t>
     334
    308335      <t>Example 8 (not allowed): Numbers are at the start or end of an rtl
    309         component:<vspace/>Logical representation:
    310         "http://ab.cd.ef/GH1/2IJ/KL.html"<vspace/>Visual representation:
    311         "http://ab.cd.ef/LK/JI1/2HG.html"<vspace/> The sequence "1/2" is
     336        component:
     337       
     338        <vspace/>Logical representation (BN): "http://ab.cd.ef/GH1/2IJ/KL.html"
     339        <vspace/>Visual representation (BN): "http://ab.cd.ef/LK/JI1/2HG.html"
     340       
     341        <vspace/> The sequence "1/2" is
    312342        interpreted by the Bidirectional Algorithm as a fraction, fragmenting the
    313343        components and leading to confusion. There are other characters that are
    314344        interpreted in a special way close to numbers; in particular, "+", "-",
    315345        "#", "$", "%", ",", ".", and ":".</t>
     346
    316347      <t>Example 9 (not allowed): The numbers in the previous example are
    317         percent-encoded: <vspace/>Logical representation:
    318         "http://ab.cd.ef/GH%31/%32IJ/KL.html",<vspace/>Visual representation:
    319         "http://ab.cd.ef/LK/JI%32/%31HG.html"</t>
    320       <t>Example 10 (allowed but not recommended): <vspace/>Logical
    321         representation: "http://ab.CDEFGH.123/kl/mn/op.html"<vspace/>Visual
    322         representation: "http://ab.123.HGFEDC/kl/mn/op.html"<vspace/> Components
     348        percent-encoded:
     349       
     350        <vspace/>Logical representation (BN): "http://ab.cd.ef/GH%31/%32IJ/KL.html"
     351        <vspace/>Visual representation (BN): "http://ab.cd.ef/LK/JI%32/%31HG.html"
     352      </t>
     353     
     354      <t>Example 10 (allowed but not recommended):
     355       
     356        <vspace/>Logical representation (BN): "http://ab.CDEFGH.123/kl/mn/op.html"
     357        <vspace/>Visual representation (BN): "http://ab.123.HGFEDC/kl/mn/op.html"
     358       
     359        <vspace/> Components
    323360        consisting of only numbers are allowed (it would be rather difficult to
    324361        prohibit them), but these may interact with adjacent RTL components in
    325362        ways that are not easy to predict.</t>
    326       <t>Example 11 (allowed but not recommended): <vspace/>Logical
    327         representation: "http://ab.CDEFGH.123ij/kl/mn/op.html"<vspace/>Visual
    328         representation: "http://ab.123.HGFEDCij/kl/mn/op.html"<vspace/>
     363
     364      <t>Example 11 (allowed but not recommended):
     365       
     366        <vspace/>Logical representation (BN): "http://ab.CDEFGH.123ij/kl/mn/op.html"
     367        <vspace/>Visual representation (BN): "http://ab.123.HGFEDCij/kl/mn/op.html"
     368       
     369        <vspace/>
    329370        Components consisting of numbers and left-to-right characters are
    330371        allowed, but these may interact with adjacent RTL components in ways
Note: See TracChangeset for help on using the changeset viewer.