- From: asmusf via GitHub <sysbot+gh@w3.org>
- Date: Sat, 23 Apr 2022 06:43:45 +0000
- To: public-css-archive@w3.org
I repeat my suggestion that correct way to make hyphenation decisions uses ranking/weighting/prioritizing to meet the conflicting goals of avoiding either a loose line (on the one hand) or awkward hyphenation on the other. Any method that attempts to do this with on/off switches for selecting features will get things badly wrong - and the edge cases will show up. So you get nonsense like not hyphenating the only word on the line, even if it exceeds total line length just because it fits some on/off criterion. Or nonsense like a half-empty line. The right way, clearly, is to recognize that at some point, avoiding an extremely unbalanced line (or avoiding overflow) takes precedent over avoiding things like hyphenating a name (or avoiding hyphenating an hyphenated compound). Those restrictions are fine as long as they don't cause edge cases. So the way to deal with that is to have a way for any automated setting to override them in layout emergencies. If we had this understanding then we would most probably not have this discussion, because even a non-optimal set of priorities (paying attention to the rules for one language over others) would not have managed to cause such extreme edge cases. -- GitHub Notification of comment by asmusf Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3927#issuecomment-1107397432 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 23 April 2022 06:43:46 UTC