Привіт Віталій!
So even with just one axis. It is definitely could be something on their end. I think you need to send them the report too, so they will know it is not the only one case.
1 Like
@mekkablue
Here’s some information from Vitaliy who asked ChatGPT about it. I don’t know how accurate this information is (because you know, it’s AI…), so I quote it as is:
Monotype Platform updated their style grouping validation engine a few months ago. They announced it partly in Slack and Discord groups. Previously they were more loyal when font styles have fsSelection = 64 (i.e. Regular bit), even if it is Thin or Black. Now they have introduced a stricter rule - only the style that you want to see as Regular can have Regular bit in style linking.
@GeorgSeifert
Here are the comments one and two from Frank E. Blokland about “Regular” word in Full Name, Name ID1 and ID2. Can you check how Glyphs handle these fields at the export stage?
For now, there are at least 3 type designers (all uses Glyphs) have this error, and perhaps there will be more eventually. Moritz Kleinsorge on TypeDrawers: I get the same error with a font that I want to release this/next week.
That the word Regular ends up in ID1 is an error that I believe is fixed in the latest cutting edge version.
Edit: in the upcoming cutting edge version.
I didn’t get to check this but Tim said in another thread that it is new in the cutting edge version. I’ll check it tomorrow and fix it.
2 Likes
Just in case, there are Fontlab users have the same Monotype error: Same boat … I use fontlab 8.