Fixed Fonts - v1.143 with names fixed

[kenmcd]

Attached are fixed versions of the v1.143 release (OTF and TTF).
The names have been fixed to have proper RIBBI style groups.
These should work in many applications.
These may fix #68, #70, and #82.

CommitMono-1.143.fixed.names.zip

Note: I did not test these to see if all the other features are working.
Just fixed the names.

There are a few other things which need to be fixed to work with some applications.
Some applications require some PANOSE settings (2) to designate it as a monospace font - or it will not work.
Some applications require another monospace flag be set - or it will not work.

The current fonts will not work properly in most code editors, consoles, etc.
Also will not work properly in LibreOffice, Word, Affinity Publisher, etc.
The names are really a mess.

@eigilnikolajsen
I would be happy to help you with this and help get your process working properly to create fonts that will work in most applications.
I see a "fontlab" folder with a bunch of fonts in it, but I do not see any FontLab source files. Much of this could be fixed in the FL source.
So please upload FL sources to a source folder.
The names can be fixed in FL.
The PANOSE settings can be done in FL, or with a script.
The mono flag can be done with a script.
(and you will need to fix your font customization page)

Really like the fonts. You have done some very nice work.
Just needs a few final tweaks. :-)
Like to help.

[eigilnikolajsen]

You are amazing! I will reply properly later, thank you so much, I'll get back.

[Finii]

The PANOSE settings can be done in FL, or with a script.

The Panose flags are correct in the fontlab fonts [1], but (it seems) get lost on the website's font-customization and zip creation set - it seems. See analysis in #69

[1] https://github.com/eigilnikolajsen/commit-mono/tree/main/src/fonts/fontlab

[Finii]

The Panose values are dropped by the opentype.js processing. There is a PR to fix it:

• os2: Fill Panose when writing font opentypejs/opentype.js#761

Maybe it would have been easier (bug wise, but not as user experience of course) to just publish the untouched Fontlab created files and let people use an established tool to burn in the feature set / alternative glyphs they like via for example https://github.com/mutsuntsai/fontfreeze.
Or maybe switch to another tool, although I do not know any Javascript ones; there are lots out there with (maybe?) less issues.