Re: [csswg-drafts] [css-inline] Consistent vertical positioning of large and medium-sized text across operating systems

> I think we could solve this with a new descriptor inside @font-face that takes a raw number that represents the font ascent (and another one for descent). The raw number would be a multiplier on the used font-size. If present, the browser would use this number instead of whatever is in the font file.

I mostly agree with @litherum in this thread, but I would strictly prefer not have per-@font-face overrides for metrics. Implementing and maintaining such overrides introduces a big maintenance burden and unnecessary implementation cost, I doubt this is the right solution to this problem.

> c) Fixing each font:

>> Currently, the most practical approach to fix this seems to be to edit the font data and synchronize these different platform-specific *ascent and *descent metrics (e.g. the FontSquirrel's web font generator has the "Auto-Adjust Vertical Metrics" option in the Expert mode, and you can always adjust them manually with a font-editing tool like FontForge as a last resort).

> Not efficient. A client pays me to do web dev, not for fixing each font I use. Also, have you looked at the license of commercial web fonts? If I remember correctly, some do not allow any modifications. Oh, and many web developers (unfortunately) insist on having their web fonts hosted eg by Google - in that setup they couldn't fix the fonts either.

If there are technical issues with the fonts, it is possible to contact the vendor and get them fixed. I've seen that process work (one of several examples [here](  Google Fonts updates the fonts as well if the original source has updates or fixes. A browser-side override is not a reasonable solution to work around fonts with inconsistent metrics. 

GitHub Notification of comment by drott
Please view or discuss this issue at using your GitHub account

Received on Monday, 25 June 2018 15:46:38 UTC