- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Jan 2020 13:07:46 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-text] Writing System prose is currently unimplementable on ICU`, and agreed to the following: * `RESOLVED: Mark this section at risk` <details><summary>The full IRC log of that discussion</summary> <RossenF2F> Topic: [css-text] Writing System prose is currently unimplementable on ICU<br> <RossenF2F> github: https://github.com/w3c/csswg-drafts/issues/4445<br> <emilio> florian: so css-text that says that line-breaking can be changed language behavior<br> <emilio> line-breaking behavior can be changed by language*<br> <emilio> ... most impls use ICU<br> <emilio> ... but the spec says it should depend on the writing-system, not just language<br> <emilio> ... and nobody does it<br> <emilio> ... my feeling it's we'll get there slowly, and it's just not implemented yet<br> <emilio> ... unless we have an objection against it I think we should keep it in the spec<br> <emilio> hober: do you think ICU has a bug?<br> <emilio> florian: whether it's a bug or a feature is fuzzy but sure<br> <emilio> fantasai: I think we don't want to remove that restriction just because ICU doesn't implement it<br> <koji> q+<br> <jfkthame> q+<br> <emilio> hober: I think we should file an ICU bug and if they wontfix remove this from the spec because everybody uses ICU<br> <emilio> florian: seems reasonable<br> <emilio> stantonm: I thought ICU took the language tag as an input<br> <emilio> fantasai: they do but they ignore the script part<br> <RossenF2F> q?<br> <emilio> astearns: should we mark this at risk pointing to the bug?<br> <RossenF2F> Zakim, close queue<br> <Zakim> ok, RossenF2F, the speaker queue is closed<br> <emilio> hober: given we're dependent on ICU here I agree<br> <florian> q?<br> <emilio> koji: is there any use case for this?<br> <emilio> ... I see the spec point of view but don't see any<br> <RossenF2F> ack koji<br> <emilio> fantasai: there are different languages that can be written in multiple writing systems like japanese or chinese text books<br> <emilio> ... they use latin letters, but you don't want to format them as english<br> <emilio> koji: but justification / font-selection / etc don't change by writing system<br> <emilio> ... it probably should change<br> <emilio> florian: justification does change in the arabic / cyrillic languages sometimes<br> <stantonm> s/I thought ICU took the language tag as an input/I thought ICU took the BCP-47 language tag as an input, which includes script/<br> <emilio> ... if you have a book that's written in japanese-latin you shouldn't use a japanese font<br> <emilio> koji: that seems fine to me<br> <florian> q?<br> <emilio> chris: a better example, turkish used to be written in the arabic alphabet<br> <emilio> jfkthame: I'm totally in agreement about filing a bug against ICU<br> <dbaron> some other examples might be Mongolian, Tajik, or Uzbek<br> <fantasai> i/jfkthame/chris: wouldn't you want to use an Arabic font for old turkish?<br> <emilio> ... but I disagree with the idea of ripping it of the spec if the bug is wontfix<br> <dbaron> (Tajik and Uzbek, according to Wikipedia, have had 3 scripts at different times: Arabic, Latin, and Cyrillic.)<br> <emilio> ... I think this is correct behavior and browsers could implement it with additional processing on top of ICU<br> <emilio> hober: goal of the spec is interoperability, if it's wontfix it'd be science fiction<br> <emilio> ACTION: florian file a bug with ICU on this<br> <hober> s/if it's/if the ICU bug is/<br> <emilio> jfkthame: Firefox is not using ICU<br> <emilio> ... and we'd like to fix this<br> <fantasai> faceless: We implement this correctly<br> <emilio> RESOLVED: Mark this section at risk<br> <fantasai> s/risk/risk, and close the issue/<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4445#issuecomment-578122943 using your GitHub account
Received on Friday, 24 January 2020 13:07:47 UTC