- From: Mathias Nater via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Jun 2020 21:10:21 +0000
- To: public-css-archive@w3.org
I'm not convinced and I don't agree. Let's imagine what it could look like in ten years if browsers supported these features: One browser (let's call it LavaLion) supports automatic hyphenation for almost all languages, the other browser (Quicksilver) can only hyphenate a few languages automatically. Web developers use a JavaScript library to insert soft hyphens in Quicksilver for unsupported languages. If, as suggested here, some CSS properties only apply to automatic hyphenation, users will need to define their style settings in two places (CSS and JavaScript). If, on the other hand, the CSS properties apply to manual AND automatic hyphenation, the user can define these settings in one place (CSS) and it doesn't matter whether the possible hyphenation points come from automatic hyphenation or were marked by soft hyphens. You could also put it like this: the "hyphenator" (be it a hyphenation algorithm or a user who inserts soft hyphens) specifies possible hyphenation points, the CSS properties define a style, which of these possible hyphenation points may be used. There -- GitHub Notification of comment by mnater Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5090#issuecomment-642929658 using your GitHub account
Received on Thursday, 11 June 2020 21:10:23 UTC