Re: Bidi in JSON notes

I'm not sure that I understand the purpose of this note. JSON is a
serialization protocol and not a display standard. The display is a front
end issue, and at the time the data is displayed, the connection to JSON
has been disconnected. So you might be discussing a subset of JSON used
within certain web standards. This should be made more specific.

But this can be generalized into saying that in order to display text
properly you may need additional meta data. This corresponds to the concept
of a "higher-level protocol" as expressed in UAX #9. But obviously this can
be expressed in any serialization protocol, e.g. protobuf, XML, BSON or
pickle.

On the other hand, the display of structured BiDi text (e.g. JSON and XML)
in a text editor, is indeed an issue that needs various recommendations. In
my opinion the best solution to this is the insertion of of the relatively
new bidi isolate characters according to the syntax right before the
rendering. E.g. The example:

"content" : "‭#bidi PEILUT MUTEMET, w3c"

would be changed before display to:
​
"&FSI;content&PDI;" : "‭&FSI;#bidi PEILUT MUTEMET, w3c&PDI;"

This would ensure that there is no influence of what is inside quotes on
the surrounding. Unfortunately I'm not aware of any editor capable of doing
this today.

Finally, for showing BiDi examples in technical documents, the standard is
to use capital letters for RTL characters and small for other characters.
See:

http://unicode.org/reports/tr9/

Regards,
Dov


On Mon, Aug 15, 2016 at 12:32 AM, Matitiahu Allouche <
matitiahu.allouche@gmail.com> wrote:

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