- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Dec 2022 02:29:14 +0000
- To: public-css-archive@w3.org
@r12a @xfq We've added a short table of examples illustrating the spelling changes (which are normatively noted in the paragraph above) here: https://drafts.csswg.org/css-text-3/#hyphenation If you have other examples you want to add, we can do that; but please remember we're not trying to make the spec examples exhaustive. :) It might be useful to compile your more exhaustive notes into the Typography index, though, and we can link there if you want. We also clarified the spec to say that hyphenation character changes must, and spelling changes should, apply. (The SHOULD is because, if the spelling differs between hyphenated and unhyphenated forms, depending on where the author ended up inserting the UA might not be able to match up the author's chosen hyphenation opportunity against its hyphenation dictionary.) We did not make any changes for WBR, see @frivoal's comments in https://github.com/w3c/csswg-drafts/issues/5972#issuecomment-826582035 and https://github.com/whatwg/html/issues/6326#issuecomment-826595860 . Note that if HTML does introduce a way to mark up explicit hyphenation opportunities in the future, the spec is written to be generic to such mechanisms already. Agenda+ for CSSWG review. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5973#issuecomment-1366321015 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 December 2022 02:29:16 UTC