- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Nov 2016 14:25:57 +0000
- To: public-i18n-archive@w3.org
A few tests do produce some surprising results on both Firefox and Chrome. Take a bidi mix of characters like the following: U+0061 U+0061 LATIN SMALL LETTER A U+0020 U+0020 SPACE U+0647 U+0647 ARABIC LETTER HEH U+200D U+200D ZERO WIDTH JOINER U+0020 U+0020 SPACE U+0062 U+0062 LATIN SMALL LETTER B U+0020 U+0020 SPACE U+200D U+200D ZERO WIDTH JOINER U+0647 U+0647 ARABIC LETTER HEH U+200D U+200D ZERO WIDTH JOINER U+0020 U+0020 SPACE U+0063 U+0063 LATIN SMALL LETTER C U+0020 U+0020 SPACE U+200D U+200D ZERO WIDTH JOINER U+0647 U+0647 ARABIC LETTER HEH Displayed as HTML in a LTR context it looks like:  and in a RTL context like:  In a textarea, in a LTR context it looks like:  and only in a textarea with RTL context does it look like you might expect, ie.  I wonder whether it's something to do with the browser trying to determine the directionality first, then packaging up the runs of characters in such a way that the ZWJ becomes isolated from the arabic character it is adjacent to. -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/i18n-discuss/issues/2#issuecomment-262253816 using your GitHub account
Received on Tuesday, 22 November 2016 14:26:03 UTC