On 11/21/2016 5:47 PM, Philippe Verdy wrote:
Look at where the Asian quotes are partially "moved" by the ASCII
quotes in Chrome.
How does Chrome enter into this? (What I posted is a screenshot from
Thunderbird on Windows 7).
It seems to fully match up the the example using the UPPER/lower case
convention.
A./
May be the reason is that Chrome still does not use the new rules.
You probably use another browser that implement other rules.
2016-11-21 23:58 GMT+01:00 Asmus Freytag <asm...@ix.netcom.com
<mailto:asm...@ix.netcom.com>>:
On 11/21/2016 2:17 PM, Philippe Verdy wrote:
2016-11-21 23:02 GMT+01:00 Philippe Verdy <verd...@wanadoo.fr
<mailto:verd...@wanadoo.fr>>:
You don't need them, I just used lowercase letters for strong
LTR characters and uppercase for RTL, just like in the
existing Bidi test page. Use some random Arabic or Japanese
words if you prefer.
2016-11-21 22:40 GMT+01:00 Asmus Freytag (c)
<asm...@ix.netcom.com <mailto:asm...@ix.netcom.com>>:
On 11/21/2016 1:17 PM, Philippe Verdy wrote:
Examples were in the initial post I sent in this thread,
or in other replies.
In encoded order, it should be testing this:
ARABIC-ONE "【japanese1】japanese2: “english1, « french1
», or「 japanese3」”。" ARABIC-TWO
Replacing "japanese" by its translation in Japanese, and
translating ARABIC-ONE and TWO into Arabic (Note: japanese3 is
been also translated in Arabic):
العربية واحدة "【日本の1】日本の2: “english1, « french1 »,
or「اليابانية واحد」。" العربية-اثنين
The CJK square quote are not mirrored, they are just swapped, but
still do not embed their content as pairs...
This is an example of where the simple assignement of direction
for quotes from the paragraph direction only does not work, and
where detecting pairs or quotes would be necessary to fix their
enclosure as isolates at inner levels.n
I get
where is the problem?
A./
