I’ve got a report from my customer who says my monospaced font is not being recognised as such even when isFixedPitch is checked in custom parameter. According to him, NULL was set to 0, a glyph that I didn’t have in the Glyphs file but added on export.
Does it make sense to automatically enforce the width to such glyphs?
How did you add the glyph?
I would simply ignore the NULL
I didn’t, Glyphs seems to have added it on export.
You mean “I” as a random app developer?
This was reported because different apps determine the monospaced-ness in different ways. In this case, Kitty recently changed to only allow monospaced fonts, and by checking glyph widths of all fonts.
I can of course add NULL preemptively and set the monospaced width, but I would expect Glyphs to apply the same width when the custom parameter is active.
It shouldn’t add null or CR. Which app build are you using?
I don’t remember the build I used at the time of the last update, actually. If it doesn’t do it now, I suppose that’s also acceptable.