W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2019

Re: [csswg-drafts] [css-text-3] Assorted editorial clarifications/requests (#3461)

From: fantasai via GitHub <sysbot+gh@w3.org>
Date: Tue, 05 Feb 2019 23:40:26 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-460848610-1549410025-sysbot+gh@w3.org>
> I'm not sure that preserving it is doing authors any favors.

If the author didn't want it there, he shouldn't have put it there.

> Can't we do better somehow?

Open to suggestions...

> Ah, I see. It's pretty unfortunate we have to have special cases for Unicode. Presumably other text engines don't have these special cases, which means other editors should have the special cases, or CSS should adopt whatever behavior the other editors have.

Text engines generally don't do white space collapsing, which is the only place we're using EAW, so that's not something they need to think about, only we do. Wrt text orientation, we did end up with UAX50. Then there's justification which references things in https://www.w3.org/TR/css-text-3/#justify-symbols, which is outside the scope of Unicode and somewhat handwavy anyway... I don't see there's much benefit in getting Unicode involved here.

-- 
GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3461#issuecomment-460848610 using your GitHub account
Received on Tuesday, 5 February 2019 23:40:27 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:43 UTC