- From: Ragdoll via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 May 2019 19:04:42 +0000
- To: public-css-archive@w3.org
Hello, I’m the person filing these bugs. I appreciate the discussion. For the record, here's the bug I sent to Blink, too: https://bugs.chromium.org/p/chromium/issues/detail?id=963039&can=2&q=hyphen%20proper%20nouns I do recognize that it will be difficult to find the perfect solution that works for everyone, but I think there can be more sensible defaults. People don’t like it when their name gets broken at the end of a line. Companies don’t like it when their own materials add hyphens into the middle of their brand names. Hyphenation should be a progressive enhancement. Over the last 10+ years, I haven’t been able to use it in a professional setting, because I’m always asked to turn it off the instant someone sees their brand name or their own name broken across a line. That’s not an enhancement. I understand that we can turn it off on a case-by-case basis with `.name` or something similar, but that puts the burden on content owners to wrap every name in a span. That’s not an enhancement either. I wonder, too, if we could add a new value to the `hyphens` property, `all`, instead of having a whole separate property. `auto` would be updated to hyphenate capitalized words based on language (e.g. in German, but not English) and `all` would hyphenate capitalized words regardless of language. Or keep `auto` as currently defined and add `no-capitalized-words` as the new value. -- GitHub Notification of comment by revoltpuppy Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3927#issuecomment-492368185 using your GitHub account
Received on Tuesday, 14 May 2019 19:04:43 UTC