- From: Masataka Yakura via GitHub <noreply@w3.org>
- Date: Thu, 03 Jul 2025 06:37:44 +0000
- To: public-css-archive@w3.org
> For `text-autospace`, the more modern, the more people started to prefer no spaces. I guess "prefer on" is still more than half of authors, especially on paper and for professional printing typographers, but the ratio is changing gradually. For example, a style guide from JETF removed the space in their version 3.0, published in 2019. Does that “no space” mean no _U+0020_ (half-width) space, or no spacing at all between Latin and CJK characters? The JETF guide explicitly mentions “半角スペース,” which refers to U+0020. I also find it jarring and excessive to have full U+0020 spaces between Latin and Japanese letters. That said, I actually prefer the current `normal` behavior that inserts 1/8em spaces. I think the amount of space matters—it’s not simply a binary yes-or-no question. Also, I’m curious about the motivation behind JETF’s decision to remove the spaces. Inserting explicit spaces between Latin and Japanese characters is quite tedious—you have to insert the character manually. It also makes things ambiguous for machines—text search and regex can behave differently depending on whether a space is there or not. So I suspect their choice might have been driven more by utility during editing, rather than purely by readability or typographic aesthetics. -- GitHub Notification of comment by myakura Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12386#issuecomment-3031049570 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 July 2025 06:37:44 UTC