- From: Fuqiao Xue via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 May 2018 08:27:39 +0000
- To: public-i18n-archive@w3.org
xfq has just created a new issue for https://github.com/w3c/clreq: == Suggestions to the gap analysis == Here are some suggestions to the [gap analysis](https://w3c.github.io/clreq/gap-analysis/) document. Any further comment is welcome! ----- [Fonts](https://w3c.github.io/clreq/gap-analysis/#fonts): I propose changing it from `tbd` to `advanced`. One issue we might want to mention is that font matching/fallback for variation sequences is not implemented correctly: https://github.com/w3c/csswg-drafts/issues/1710 ----- [Ruby annotation](https://w3c.github.io/clreq/gap-analysis/#ruby): Mention the lack of support of Bopomofo ruby and difficulties selecting ruby text. ----- [Text decoration](https://w3c.github.io/clreq/gap-analysis/#textdecoration): Punctuations should be skipped by default for emphasis marks. [Emphasis & highlights](https://w3c.github.io/clreq/gap-analysis/#emphasis): It's related to [text decoration](https://w3c.github.io/clreq/gap-analysis/#textdecoration). I propose changing it from `ok` to `advanced`. ----- [Line breaking](https://w3c.github.io/clreq/gap-analysis/#linebreak): Browsers differ in how they handle line breaks for `IDEOGRAPHIC SPACE (U+3000)`. [UAX #14](https://www.unicode.org/reports/tr14/) doesn't make sense for quotation marks in Chinese: https://www.w3.org/2018/05/14-clreq-minutes.html#x02 ----- [Counters, lists, etc.](https://w3c.github.io/clreq/gap-analysis/#counters): `@counter-style` is only supported in Firefox. ----- [Page numbering, running headers, etc.](https://w3c.github.io/clreq/gap-analysis/#pageheaders): We can use some text text in the [Hungarian Gap Analysis](https://w3c.github.io/typography/gap-analysis/docs/latn-hu#pageheaders), since it applies to Chinese too: > Although there exist software that supports page numbers and running headers, none of the browsers do. Complex running headers (containing math, tables or other complex content) are not supported anywhere. Please view or discuss this issue at https://github.com/w3c/clreq/issues/179 using your GitHub account
Received on Tuesday, 29 May 2018 08:27:49 UTC