Countours & MyFonts

Iqblfrds · October 7, 2019, 8:43am

I have a problem with the font validator MyFonts

. How do I check every glyph path that is not clockwise?

mekkablue · October 7, 2019, 10:06am

There’s a mekkablue script called New Tab with Path Problems.

Iqblfrds · October 8, 2019, 2:00pm

I already used the script and the script reported there were no problems with the path. but why does the error still occur when uploading to the font MyFonts validator. Am I missing something?

GeorgSeifert · October 8, 2019, 3:10pm

Do they tell you the glyph that cause the problem?

Iqblfrds · October 9, 2019, 12:24am

No, they only tell as in the screenshot above. it makes me confuse.

GeorgSeifert · October 9, 2019, 5:08pm

Could you ask them to give more details?

jakob_runge · October 9, 2019, 5:17pm

My inappropriate comment on that:

The myFonts validator is crap. Doesn’t allow other stylelinking than regular<->bold, can’t proper handle super-families, if something is invalid you may have to resubmit typeface as a new project again.
Might spot bad production mistakes but no help for professionals.

So problem might be in the service not in glyphsapp.

GeorgSeifert · October 9, 2019, 8:08pm

You can try to use this: https://github.com/HinTak/Font-Validator/releases/download/FontVal-2.1.1-py/Mac.OS.X.FontValGUI-Seifert-2.1.1.zip

and see if it reports the same problem.

Iqblfrds · October 10, 2019, 12:10am

can you explain what that means? Is E4100 a Unicode code that has problems?

GeorgSeifert · October 10, 2019, 5:49am

That is the ID of the test. You can ignore this. On that point, the validator is outdated.

FranciscoTorres · February 7, 2020, 1:58pm

It’s happening a similar problem with me. Did you find a solution?
In my case, it’s just the yellow warning, ( “Yellow warnings will not prevent your fonts from being submitted”).

I’m pretty sure everything is fine. Still, I would like to know where might be the problem.
@GeorgSeifert Does this ‘Font Validator’ still work?

I get this error every time:

mekkablue · February 7, 2020, 2:07pm

You can submit requests and bug reports for Font Validator here:

GeorgSeifert · February 7, 2020, 5:53pm

That error might be caused by the Mac wrappper. Can you post a screenshot of the settings you used? And what version of Font Validation and MacOS do you have?

FranciscoTorres · February 7, 2020, 6:36pm

I used the link you posted here some time ago. It seems to be 2.1.1.
I just updated, but the problem remains.

Which settings? Do you mean this?

mekkablue · February 8, 2020, 2:10am

As indicated in the reply you got, perhaps try to restart the app with an English number locale.

FranciscoTorres · February 10, 2020, 11:27am

It worked fine when I restarted my Macbook in English. Thanks for the tip @mekkablue.

FranciscoTorres · February 10, 2020, 11:38am

Btw, since I use Glyphs, do you know what might be creating this error?

GeorgSeifert · February 10, 2020, 11:50am

You can ignore those. Fontvalidator is not up to date with the latest openType spec.

Iqblfrds · June 19, 2020, 2:17am

Halo, Has this script been deleted? I can’t find it.

mekkablue · June 19, 2020, 7:00am

I merged it with a few other scripts and it is now called Path Problem Finder.

You need to be patient because it has some performance issues when the tab it opens contains a lot of glyphs.