- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Sep 2019 00:48:13 +0000
- To: public-css-archive@w3.org
@kojiishi > Does it work for Hangul/Hanja mixed-content? Depends what you mean by work. It would break between the Hanja, and not between the Hangul. This is not the ideal behavior, which would also keep Hanja of a single word together, but: * Hangul/Hanja mixed content is increasingly rare, and even when mixed, the Hanja are few. * In cases where the language is not tagged, we cannot know (without using heuristics on the whole content) if we have a case of Korean with mixed hangul/hanja, or a case of multilingual text with Korean mixed with Japanese or Chinese. And if it is the later, disallowing breaks within Hanja/Hanzi/Kanji words would be problematic, as we could end up with long strings of Japanese/Chinese text with no breaks at all. * In cases where the language is tagged, it is possible to use a `lang(ko)` selector to apply the `keep-all` value. ---- @tabatkins > Is there a reason to give Korean a special value here, versus just changing the behavior of "normal" to better reflect current Korean writing practice? Korean writing/typography culture is undergoing a transition. The `keep-all` style is increasingly common, but not universal (yet). There are authors who do continue to expect the current `normal` behavior, and might not be too happy if it changed. Also, it is likely (I don't have data, but it is logically probable) that there are websites out there that would break if we changed the default: * sites with tightly sized elements, such as menus, buttons, etc, where the content wouldn't fit if line-breaking happened differently * old/traditional text didn't even have spaces at all. Even among authors who do not prefer the `keep-all` behavior, the modern practice is to put spaces between words. But pages containing older text may not have spaces, and a `keep-all` type of behavior on these would suppress all/most line breaking opportunities, which would be bad. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4285#issuecomment-529721096 using your GitHub account
Received on Tuesday, 10 September 2019 00:48:15 UTC