W3C home > Mailing lists > Public > www-style@w3.org > February 2015

Re: [css-text][css-writing-modes] Line breaking around Emoji, Gaiji, U+FFFC, and text-combine-horizontal

From: Koji Ishii <kojiishi@gmail.com>
Date: Mon, 2 Feb 2015 00:36:18 +0900
Message-ID: <CAN9ydbUsvS1qdi51bKoObwAd_N6zq0ejqJ1XeUmCjwauKAK21w@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: "www-style@w3.org" <www-style@w3.org>
Taking back what I said for text-combine:

On Mon, Jan 26, 2015 at 8:31 PM, Koji Ishii <kojiishi@gmail.com> wrote:
> Thank you for the great summary.
>
> On Mon, Jan 26, 2015 at 7:29 AM, fantasai <fantasai.lists@inkedblade.net> wrote:
>>
>> 1. text-combine-upright
>> -----------------------
>>
>>    Result of text-combine-upright should break as ID, not as U+FFFC.
>>    Current spec requires treating as actual contents for line-breaking.
>>    So there is some misunderstanding of the text;
>>    unclear whether there is an issue here to fix.
>>
>>    Proposal A: Leave spec as-is: TCY treated as its own text.
>>    Proposal B: Make TCY always treated as ideographic character.
>
> Hm, the change was made in 2012[1]. I merely remember we discussed,
> but don't remember why we changed.
>
> Though I lost that context, thinking now, I think B works the best.

I prefer A, for the following reasons:
1. Proposal A, B, or U+FFFC do not give differences in any real
scenario I can think of.
2. For WebKit and Blink, Proposal A makes impl far much simpler.
If any impls prefer Proposal B or U+FFFC, I'm fine to allow both,
because of the reason #1 above.

/koji
Received on Sunday, 1 February 2015 15:36:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:01 UTC