- From: Yasuo Kida （木田泰夫） via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Jun 2024 09:05:21 +0000
- To: public-css-archive@w3.org
Discussed at today's JLReq TF meeting and reached a consensus. As a unified position, JLReq TF recommends option B: in normal, forbid breaks before small kana, as well as the prolonged sound mark U+30FC. The current JLReq also forbids small kana from appearing at the beginning of lines, as stated in [section 3.1.7](https://www.w3.org/TR/jlreq/#characters_not_starting_a_line). In [appendix C.3 addendum](https://www.w3.org/TR/jlreq/#addendum_a3), it defines looser levels that allow breaks before small kana and some other characters. In traditional printing, there has been pressure to avoid kinsoku (prohibition of line breaks at certain points) as much as possible to reduce the need for adjustments for justification, which affects the productivity of line layout work. Additionally, when a justified line is shorter, the adjustments result in visible widening of character spacing. The looser levels were defined to accommodate such requirements. Text on the web has different properties. The cost of line adjustment is negligible. The default on the web is ragged right, meaning that adjustments do not negatively affect character spacing. Another reason to avoid separating small kana is that they are diacritical marks modifying the phonetic value of the previous character. Separating them forces readers to read the base character differently. Upon reaching the beginning of the next line, readers find that it actually had a different pronunciation. This effect would be worse for people with reading difficulties. These reasons underpin the recommendation. It is important that editors and designers have options. For example, when a line is shorter and justified, one might prefer looser rules to prevent spacing between characters from becoming too wide. -- GitHub Notification of comment by kidayasuo Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10363#issuecomment-2188370646 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 June 2024 09:05:22 UTC