- From: Ken Lunde <lunde@adobe.com>
- Date: Wed, 17 Dec 2014 00:23:04 +0000
- To: Koji Ishii <kojiishi@gmail.com>
- CC: (wrong string) ˜·•þML <public-html-ig-zh@w3.org>
Koji, In my opinion, I wouldn't worry too much about the EAW=A property value, mainly because it seems that U+2022 and U+2027 have been used for this Traditional Chinese punctuation for many years, and nothing has exploded yet. ;-) Regards... --- Ken > On Dec 14, 2014, at 8:23 PM, Koji Ishii <kojiishi@gmail.com> wrote: > > 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 Wednesday, 17 December 2014 00:23:37 UTC