- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2020 03:39:30 +0000
- To: public-css-archive@w3.org
Thank you Mike for the investigation, this is really helpful. [This code snippet in WebKit](https://trac.webkit.org/browser/webkit/trunk/Source/WebCore/platform/graphics/FontCascade.cpp#L1239) may help developing the list too. Maybe we should agree on the expected accuracy first. My basic idea is: 1. I do not expect the perfectly accuracy in all cases. It is a heuristic algorithm, which can't be perfect anyway. This is ok, as long as browsers are interoperable, it should not be too hard to find the failures of the heuristic algorithm. 2. I would like this algorithm to be simple and fast. This logic is a bit "hot"; runs on every source line for all pages including English pages, consumes battery and CPU cache spaces for all users. 3. In my opinion, I think we should avoid excessive removal for non-CJK scripts. This means that when ambiguous, choose not to remove. Not ideal for CJK authors, and may not look consistent in some cases, but still a great improvement, and authors can learn as long as implementations are interoperable. 4. The basic philosophy we applied for `text-orientation` is to use one Unicode property, or ask Unicode to add a new property. If you found other properties than the Unicode Block that can produce better results, I don't insist on the Unicode Block at all, but I prefer to stick on using one property. Do these look reasonable? Any opinions, additions, or change suggestions? -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/337#issuecomment-591222652 using your GitHub account
Received on Wednesday, 26 February 2020 03:39:32 UTC