- From: r12a <ishida@w3.org>
- Date: Mon, 15 Aug 2016 20:17:44 +0100
- To: Matitiahu Allouche <matitiahu.allouche@gmail.com>, public-i18n-bidi@w3.org
hi Mati, thanks for the comments. See below... On 14/08/2016 22:32, Matitiahu Allouche wrote: > 1) You announce: "we'll use Hebrew to avoid the confusing effects of Arabic letters joining backwards." > However, the first 2 examples show Arabic text. Another Arabic example appears later. That was meant to be just for where we "show characters from left-to-right in the order in which they are stored in memory", but it wasn't particularly clear. Changed the sentence to: "Where code examples below show characters from left-to-right in the order in which they are stored in memory, we'll use Hebrew to avoid the confusing effects of Arabic letters joining backwards." > 2) You wrote: "Indications of direction change inline would just be carried over from whatever the original author used." > I don't understand what you mean. I meant that if a user has created some text with multiple lines/paragraphs that requires a mix of base directions, they will probably have to do something during input to the paragraphs after the first one to make the base direction change. Take for example, a textarea in html with several lines of text - either the user will have to rely on getting the righth first strong characters in place for paragraphs after the first if they want the base direction to change in lines/paras 2 and beyond. That information will be captured with the string. It's only the first para that relies on the direction setting of the textarea. (I know that sometimes the user may not be able to get what they want during input, but scripts can't make assumptions about whether the user did or didn't know how to do what they wanted.) > 3) You wrote: "It can be argued that Twitter's approach produces less predictable output than first-strong, but that's beside the point." > I suggest a more diplomatic variant: "Which approach is better is beside the point." ok, done > 4) "those decisions have already be taken" => "those decisions have already been taken" fixed > 5) You wrote: "Furthermore, RLM characters are not commonly available on user keyboards, especially for mobile devices.)" > Note that the standard keyboard layout promoted by the Israeli Bureau of Standards (SII) includes LRM and RLM (on the parentheses keys in conjunction with AltGr). This layout is also the default for Windows since Win8 , if I am not mistaken. However, I suspect that the overwhelming majority of users is not aware of their existence on the keyboard. > I am not sure if you should modify your text accordingly. thanks, ri > http://w3c.github.io/i18n-discuss/notes/json-bidi.html
Received on Monday, 15 August 2016 19:17:56 UTC