The following text says: "This setting determines the way in which the run contents are presented in the document when punctuation characters are part of the run’s contents. When this property is specified, each part of the run between a punctuation mark shall be laid out right to left on the line."
Then appears an example of English text "This is a list: one, two, three." which will be presented as follows when "rtl" is specified: ".three ,two ,one :This is a list"
a) The example does not implement the description: it shows how the parts are ordered relative to one another, and not that "each part is laid out right to left".
b) It is not clear what is considered punctuation. In particular, are signs like full stop, comma, hyphen-minus, solidus considered as punctuation when appearing within numbers
c) If to judge by the example, this definition of run direction has no practical value. It is hard to find a real-life use case where such an implementation of "rtl" would be useful.
d) The run is not well defined as relative to direction:
- can a run contain both LTR and RTL text
- can a run contain RTL text together with numbers
e) What specifies the base direction of the run if it contains both LTR and RTL text
f) What specifies how successive runs with different directions are laid out relative to one another
g) The specification does not seem to support directionality at more than 2 levels. How can it handle a Hebrew sentence containing some Latin words quoted inside a LTR paragraph
Then appears an example of English text "This is a list: one, two, three." which will be presented as follows when "rtl" is specified: ".three ,two ,one :This is a list"
a) The example does not implement the description: it shows how the parts are ordered relative to one another, and not that "each part is laid out right to left".
b) It is not clear what is considered punctuation. In particular, are signs like full stop, comma, hyphen-minus, solidus considered as punctuation when appearing within numbers
c) If to judge by the example, this definition of run direction has no practical value. It is hard to find a real-life use case where such an implementation of "rtl" would be useful.
d) The run is not well defined as relative to direction:
- can a run contain both LTR and RTL text
- can a run contain RTL text together with numbers
e) What specifies the base direction of the run if it contains both LTR and RTL text
f) What specifies how successive runs with different directions are laid out relative to one another
g) The specification does not seem to support directionality at more than 2 levels. How can it handle a Hebrew sentence containing some Latin words quoted inside a LTR paragraph
Suggested change to the text to say "how each phrase is laid out, where a phrase is any text between two punctuation characters"
Provide a list of possible punctuations
Provide a real life scenario and examples. Consult with NB in Israel to provide the examples.
The handling of directionality has to be explained much more clearly.
There is a need to specify the text base direction at a level above runs (i.e. paragraph), because a piece of text typically contains several runs. The "bidi" property cannot be use for that purpose, since it explicitly states that it "shall not affect the layout of text within the contents of this paragraph."
Provide a list of possible punctuations
Provide a real life scenario and examples. Consult with NB in Israel to provide the examples.
The handling of directionality has to be explained much more clearly.
There is a need to specify the text base direction at a level above runs (i.e. paragraph), because a piece of text typically contains several runs. The "bidi" property cannot be use for that purpose, since it explicitly states that it "shall not affect the layout of text within the contents of this paragraph."
"rtl (Right To Left Text)"
, page 213 .
Section 2.3.2.28
te
Proposed Disposition of DIS 29500 Comment IL-0005 (Modified: 2008-01-02) Based on the response to comment IL-0004, we agree that the current text for the rtl element needs to be replaced. As our intent is that based on those changes, these issues are resolved. Overall, it is noted that the Unicode BiDi algorithm is intended for use by consumers of OOXML (with the addition of the higher-level logic specified in the rtl element’s updated description). Responding to the specific questions: a) Agreed; a new, clearer example replaces it. b) Agreed; the text now clearly specifies when the override applies. c) Agreed; hopefully, the new text makes the use of this property clearer. d) No (only RTL and neutral characters, clarified); Yes (which are processed as described by that element) e) This is based on the bidi element on the parent paragraph (which defines the base paragraph direction). f) This is as defined in the Unicode algorithm (with the character override applied). g) Use of bidi and rtl would accomplish this set bidi to set the paragraph direction to RTL, then apply the rtl element to runs with Hebrew text, and rtl = false to the runs with the English text.
