The PANOSE numbers are incorrect for a monospaced font.

[djrrb]

Reposting this PANOSE issue from the main repo since it is Mono-specific:

I don’t think that there are any practical consequences to not having these values

Well it would have a consequence for Ubuntu Mono. At least Microsoft's Windows Terminal seems to rely on Panose Proportion Monospace to make a particular font selectable. See here.

Originally posted by @Finii in canonical/Ubuntu-Sans-fonts#16 (comment)

This appears in fontbakery as a fail:

🔥 FAIL: Checking correctness of monospaced metadata. (com.google.fonts/check/monospace)

🔥 FAIL: The PANOSE numbers are incorrect for a monospaced font. Note: Family Type is set to 0, which does not seem right. [code: mono-bad-panose]

AFAIK this value is stored correctly in the sources, but the values do not propagate to the instances. More discussion on what to do with PANOSE here: googlefonts/fontmake#953

I realize it would be possible to patch the exported fonts, but I am marking this as “blocked” as I would prefer to keep the sources and build process as clean and unhacky as possible and let this get addressed in the build tools.