Italic styles have corrupt OS/2 metrics!

[northgardner]

Please remove if this is not the appropriate channel for this report. I have been using TT2020 in various text editors that will render italics for Markdown (among other uses). On a few that I have tried, when using TT2020Base or TT2020 Style E, using italics will cause either the italic word or the whole line to move lower relative to the line above it. The editors this happens with include Atom, Sublime Text, VS Codium, and Mark Text. I'll attach one screenshot from Sublime Text and one from Atom that show both behaviors.

[ctrlcctrlv]

I believe that the metrics are clashing in a way I did not intend. I probably failed to make some element of the metrics equivalent, even though in the browser and most WYSIWYG editors they are equivalent.

After I switch to a fontmake based build, I need to verify that the metrics are absolutely equivalent.

[ctrlcctrlv]

Woah woah woah. This is not a simple mismatch!

FontForge is sometimes shockingly bad software. How in the world did this happen? It knows that the ascent is supposed to be above 700 and decent above 200, and yet it decides to put zeros in the metrics tables!!!!!!

[ctrlcctrlv]

Thankfully the TTF is not as corrupt as the SFD, but it is still very corrupt!

https://twitter.com/fr_brennan/status/1503236785278758912

[micampe]

hi, I was about to report that xMax is wrong in TT2020StyleE-Regular.ttf but reading here and on Twitter it sounds like it might be the same FontForge bug.

[ctrlcctrlv]

Likely :S

[wahlstedt]

I encountered this bug after testing out replacing a font in an existing document with TT2020 Style E. Every line that had an italicised word got displaced. Is a fix planned, or can we manually edit the metrics values?