- From: Asbjørn Riis-Knudsen via GitHub <sysbot+gh@w3.org>
- Date: Sat, 23 Apr 2022 08:30:46 +0000
- To: public-css-archive@w3.org
@HeikkiYlipaavalniemi For me, the way forward is pretty clear: The Working Group needs to acknowledge that this was not thought through properly and that is was a mistake to change the spec in the way it was. We all make mistakes occasionally, and as long as we own up to our mistakes, that is OK. From that, it follows that the change should be reverted as soon as possible, encouraging browser vendors to make the change quickly. That will leave with a hyphenation system that works for most languages in most cases. Then, careful thought should be given to how the specific issues (like not wanting certain words hyphenated) can be addressed in a language-agnostic way. This should involve a group of people from around the world with experience with various different languages so that a solution can be designed taking into account the needs of all languages. This might involve adding additional properties to control various aspects of hyphenation, as seen in page layout software like Adobe InDesign. -- GitHub Notification of comment by arknu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3927#issuecomment-1107432019 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 08:30:47 UTC