- From: Michael Taranto via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Aug 2024 23:48:54 +0000
- To: public-css-archive@w3.org
@fantasai 100% agree (this was part of [my original feedback]) — I was merely trying to follow the design presented in [the draft spec] (Figure 5) to keep the discussion here focused. I too disagree with the conflation of the `ascent` and `cap height` metrics, but something to address throughout the spec separately. Worth noting, Figure 5 in [the draft spec] also has a mistake, the value in the middle example should be `cap` not `text` which was the cause of my mis-representation of `text` being ascent to descent. I would say I find these comments above to be contradictory: > For a lot of fonts, the ascent is actually much higher than the cap height > For English, for example, basically nothing goes above the cap height except small bits of serifs etc which as we are saying, the ascenders and other diacritic marks certainly do extend beyond cap height in many fonts. Honestly i don't mind having to specify both edges, but i do find it a little confusing that CSS has decided to choose what terms it shares with typography and font metrics. For example, providing `cap` as a unit, trim edge etc and it not being relevant to all character sets, while diverging from `baseline` in favour of `alphabetic` to try and scope to some character sets (yes i have read the [naming stuff discussion], and i agree with @jwssnr's comments). I would love to see: ```css text-edge: cap baseline; ``` It's even illustrated as `baseline` in the spec images! But hey, thats my opinion. Happy to discuss further, and appreciate all your time on this. [my original feedback]: https://github.com/seek-oss/capsize/issues/205#issuecomment-2185365588 [the draft spec]: https://drafts.csswg.org/css-inline-3/#text-edges [naming stuff discussion]: https://github.com/w3c/csswg-drafts/issues/8067 -- GitHub Notification of comment by michaeltaranto Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10703#issuecomment-2287406087 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 August 2024 23:48:55 UTC