[css-text-4] `text-spacing` and OpenType halt/vhal/chws/vchw features
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
Related with #8292 but I think this part is easier to discuss by splitting into a separate issue, so here it is.
When the text-spacing property makes some assumption on how glyphs are designed, such as specific parts of the glyph spaces are empty, it's great if font designers can override the behavior when they need.
To do this, I'd like to suggest that:
- For the adjacent trimming, if the font has
chwsorvchw, the trimming should be deferred to the feature. - For other trimming, or for the adjacent trimming with the font without
chwsnorvchw, if the font hashaltorvhal, the trimming should use the feature. - For other cases, if UA wants to synthesize the trimming, #8292 can discuss more.
Thoughts? /cc @litherum @fantasai @frivoal @MurakamiShinyu @macnmm
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CSS Text Level 4 text-spacing property and the proposed behavior for OpenType chws, vchw, halt, and vhal features. Review the related issue #8292 and the existing discussion before proposing wording. Done means the Working Group reaches agreement on the trimming rules and the specification is updated accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100