- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Apr 2023 19:58:01 +0000
- To: public-css-archive@w3.org
Pending the i18n investigation, I'm seeing three ways forward here: - **Option 1: Do nothing.** - **Option 2: Add `keep-hangul` to `word-break`.** And follow this same break-*/keep-* pattern if we have a few other cases to address. - **Option 3: Add generic `keep(<scriptname>+)` and `break(<scriptname>+)` functions to `word-break`.** These would diff against the `normal` baseline behavior. Recap: The fundamental behavior of `word-break` is to switch certain Letters from behaving like CJK (`break` behavior) to behaving like Latin (`keep` behavior) or vice versa: `break-all` applies break behavior to *all* letters, and `keep-all` applies keep behavior to *all* letters. The proposal here is, essentially, to allow subsetting the switch to Hangul. IMHO: If there aren't use cases for more than one or two values in `break()` and `keep()`, then we are imho better off with the one-off keywords, provided they consistently follow the behavior and syntax pattern that we would use for `break()` and `keep()` (which we should comment into the spec for future us). -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4285#issuecomment-1522340249 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 April 2023 19:58:03 UTC