RE: Bidi in JSON notes

   Hello, Richard!

I have a few comments.

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.

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.

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."

4) "those decisions have already be taken" => "those decisions have already been taken"

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.


Shalom (Regards),  Mati

-----Original Message-----
From: r12a [mailto:ishida@w3.org] 
Sent: Friday, August 12, 2016 11:07 PM
To: public-i18n-bidi@w3.org
Subject: Bidi in JSON notes

chaps,

i've been trying to think more around the issue of bidi support in JSON in general (ie. not just AS specific), and made some notes for discussion at

http://w3c.github.io/i18n-discuss/notes/json-bidi.html

the structure of the page is somewhat different from the previous wiki page, as i try to build in things i think i have come across recently.

of course, i'm looking for comments, corrections, suggestions.

ri

Received on Sunday, 14 August 2016 21:32:49 UTC