Changeset 150


Ignore:
Timestamp:
Oct 19, 2012, 9:00:07 PM (7 years ago)
Author:
duerst@…
Message:

adding Arabic and Latin to testing example and tweaking surrounding text

File:
1 edited

Legend:

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

    r149 r150  
    125125          the HTML, PDF, and UTF-8 plaintext versions show non-Unicode characters directly.
    126126          This often makes it easier to understand examples, and readers are therefore strongly advised
    127           to consult these versions in preference or as a supplement to the ASCII version.</t>
     127          to consult one of these versions in preference to or as a supplement to the ASCII version.</t>
    128128        <t><ionly>This version of this document contains bidirectional examples.
    129129          In order to correctly understand the examples, it is important to view this document
    130130          with a tool that correctly implements the Unicode Bidirectional Algorithm <xref target="UNI9"/>.
    131            Many text viewers and text editors, and most browsers, currently implement
    132            the Unicode Bidirectional Algorithm, but there are some exceptions.
     131           Many text viewers and text editors, and all major browsers, currently implement
     132           the Unicode Bidirectional Algorithm.
    133133           Also, all users who are reading RTL text on a regular basis have tools
    134134           that implement this algorithm, because otherwise, they would be unable
    135135           to read even the simplest texts.
    136136           In order to check whether a tool implements the Unicode Bidirectional Algorithm,
    137             please observe the line of Hebrew characters below:
    138            <vspace/><span dir='ltr'>א, אב, אבג, אבגד, אבגדה, אבגדהו</span>
    139            <vspace/>If the shortest word (one character) is on the right, and the longest word (six characters)
    140            is on the left, and the words get longer and longer from right to left,
    141            and the commas are between the words, but on the right of the spaces,
    142            then your tool should be okay. Otherwise, please use another tool.
    143            Please note that the example is only in Hebrew because in Arabic,
    144            it is difficult to count characters for people who are not familiar
    145            with the script.</ionly></t>
     137            please observe the following three lines:
     138           <vspace/>FEDCBA ,EDCBA ,DCBA, CBA, BA, A
     139          <vspace/><span dir='ltr'>ب, بت, بتث, بتثج, بتثجح, بتثجحخ</span>'
     140          <vspace/><span dir='ltr'>א, אב, אבג, אבגד, אבגדה, אבגדהו</span>
     141           <vspace/>The first line contains upper-case Latin letters,
     142           the second line contains Arabic letters,
     143           and the third line contains Hebrew letters.
     144           Your tool will be okay if in all three lines, the shortest word (one character)
     145           is on the right, and the longest word (six characters) on the left,
     146           the words are getting longer and longer from right to left,
     147           and the commas are between the words, but on the right of the spaces.
     148           Otherwise, please use another tool.
     149           In the second line, the characters in each word should all be connected,
     150           and change shape slighly on context. In the first and third line,
     151           no characters should be connected.</ionly></t>
    146152      </section>
    147153      <section title="Notation">
Note: See TracChangeset for help on using the changeset viewer.