- From: Nat McCully via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Mar 2024 01:33:27 +0000
- To: public-css-archive@w3.org
Talking to Ned from Apple, he says their algorithm is quite involved, and allows for both compression and expansion of the default spacing, and some spacing will take the glyph ink into account as part of the logic. So, this leads me to believe that we need to approach this problem with a bit more rigor and nuance. For example: - Solve the Unicode SJIS unification issue with [Variation Selectors](https://www.unicode.org/L2/L2023/23212r-quotes-svs-proposal.pdf) - Verify the minimum spacing behavior variations and define spacing classes on the Unicode ranges + VSs - Define the spacing behavior patterns (what is the minimum, desired, maximum spacing amount; what are the compression and expansion conditions and priorities) - Advocate for fonts to standardize their glyph designs to conform to the Unicode + VSs, and their defined spacing behaviors - Advocate for layout engines to implement the spacing rules according to the spacing behavior variations All this is to say that the [proposal from Koji](https://www.unicode.org/L2/L2024/24057-auto-spacing-prop.pdf) may not be sufficient to solve the Latin-to-J or Latin-to-CJK spacing issue, and that that issue is merely a single case of the generic spacing rules issue defined in JLReq or JIS X 4051 and so it should try for a higher bar from the beginning. -- GitHub Notification of comment by macnmm Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9479#issuecomment-2011023853 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 March 2024 01:33:28 UTC