- From: Najib Tounsi via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Mar 2021 12:58:53 +0000
- To: public-i18n-archive@w3.org
ntounsi has just created a new issue for https://github.com/w3c/i18n-drafts:
== [articles/vertical-text/index] Subsectionning of "Identifying Base Direction of Content" ==
[source] (https://w3c.github.io/i18n-drafts/articles/lang-bidi-use-cases/index.en) [en]
My comments are about the Section "[Identifying the Base Direction of Content](https://w3c.github.io/i18n-drafts/articles/lang-bidi-use-cases/index.en#bidi_use_case)"
and the grouping of examples.
Instead of this (sub)sectioning:
```
Identifying the Base Direction of Content
Getting things to appear in the right place
Problems with initial Latin text in RTL strings
Bidirectional text ordering
Interpreting HTML markup
Neutral LTR text
Spill-over effects
What consumers of strings need to do
In-string direction changes
```
I suggest the following:
```
Identifying the Base Direction of Content
* Getting things to appear in the right place
- Problems with initial Latin text in RTL strings
- Bidirectional text ordering
- Neutral LTR text
- Spill-over effects
* Interpreting HTML markup
* What consumers of strings need to do
* In-string direction changes
```
Bring "_Neutral LTR text_" and "_Spill-over effects_" as subsections of "_Getting things..._".
I think all use-case examples can fall into this section: examples requiring Base Direction as well as examples with Isolate/Numerals.
Another small comment (nothing to do with above).
Paragraph after Fig-11. "_If a bidirectional string is inserted into a LTR context without specifying the RTL base direction for the inserted string, it can produce unreadable text._"
And 'vice versa' ?
Please view or discuss this issue at https://github.com/w3c/i18n-drafts/issues/279 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 March 2021 12:58:55 UTC