- From: Koji Ishii <kojiishi@gmail.com>
- Date: Mon, 15 Dec 2014 13:23:55 +0900
- To: Ken Lunde <lunde@adobe.com>
- Cc: Martin J. Dürst <duerst@it.aoyama.ac.jp>, Bobby Tung <bobbytung@wanderer.tw>, "public-zhreq@w3.org" <public-zhreq@w3.org>, CJK discussion <public-i18n-cjk@w3.org>, 中文HTML5同樂會ML <public-html-ig-zh@w3.org>
On Mon, Dec 15, 2014 at 12:31 PM, Ken Lunde <lunde@adobe.com> wrote: > Koji, > > For this issue, and for similar characters, what Traditional Chinese IMEs emit, in terms of Unicode values, and how Traditional Chinese fonts encode the corresponding glyphs, are much more important factors than UAX #11 (East Asian Width) property values. > > For Traditional Chinese, the target character is clearly Big Five 0xA145, and this seems to correspond to U+2022 or U+2027, depending on the OS. Understood, actually that matches to what I guessed (and feared ;). The challenge would be on the layout engine side to handle EAW=A correctly. It's not only for this code point, so we might need a good solution for EAW=A someday, but just wanted to head up that it's likely to cause some layout problems on most platforms today. /koji
Received on Monday, 15 December 2014 04:24:23 UTC