Thanks for this. Just to clarify: for this fonts, the metrics seem identical across three options, is that correct? (total: 2457)
-
-
Replying to @mwichary
The total height (including line height) is the same, but the distribution is different.pic.twitter.com/wwd4i0nCd5
2 replies 0 retweets 1 like -
Replying to @aaronbell @mwichary
I usually only set the use typo metrics flag in fonts fir which I need to differ the linespacing from the clipping metrics, usually because the latter need to be huge. As I recall, Cambria Math was the first font to use that flag.
2 replies 0 retweets 1 like -
Replying to @TiroTypeworks @mwichary
Yeah, Cambria Math is a pretty extreme case. Most fonts probably don’t *need* it set to render well enough (since applications fiddle around with line heights as it is), but I think it is generally worth setting. Otherwise we’ll never escape winAscent / winDescent.
1 reply 0 retweets 1 like -
Seems to cause more trouble than it helps, unfortunately. Thinking about removing it from my mastering process.
2 replies 0 retweets 0 likes -
There's no universally compatible way to set font vertical metrics, only 'best practices' that favour one or another compromise. My starting point for any project is to make the , three sets of metrics sum to the same height, at which point I don't need to set the flag. /1
1 reply 0 retweets 0 likes -
Replying to @TiroTypeworks @koeberlin and
I set the TypoAscender and TypoDescender to sum to the UPM body height, which means default leading is expressed using the TypoLinegap value. /2
1 reply 0 retweets 0 likes -
Replying to @TiroTypeworks @koeberlin and
So long as doing so won't result in clipping, I then set the WinAscent and WinDescent metrics to sum to the same height as the combined Typo metrics, providing Windows compatibility regardless of which set of metrics are used for linespacing. /3
1 reply 0 retweets 0 likes -
Replying to @TiroTypeworks @koeberlin and
But a pretty frequent aspect of my work involves adding script support to existing fonts, and this sometimes involves introducing glyphs that exceed the existing WinAscent and WinDescent values. So unless I can change those metrics, those glyphs will get clipped. /4
1 reply 0 retweets 0 likes -
Replying to @TiroTypeworks @koeberlin and
So the use typo metrics flag is pretty much the only chance to maybe, in some environments, maintain backwards compatible linespacing and also avoid clipping. It isn't implemented as widely or as well as it should be after 15 years, but it's still the only option. /5
2 replies 0 retweets 0 likes
This is a very useful explanation, thank you.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.