fonttools
ERROR: Failed to access: http://namecheck.fontdata.com.
Observed behaviour
>> com.google.fonts/check/fontdata_namecheck
Familyname must be unique according to namecheck.fontdata.com
with ./Fonts/ttf/Petrona-ExtraBoldItalic.ttf
Rationale:
We need to check names are not already used, and today the best place to
check that is http://namecheck.fontdata.com
* ERROR: Failed to access: http://namecheck.fontdata.com.
Please report this issue at: https://github.com/googlefonts/fontbakery/issues [code: namecheck-service]
It told me to report, so I did.
I hope a unique name won't lead to a failure anyway, because some fonts that we add are actually already listed there.
@felipesanches @yanone,
I'm getting the same thing.
- 💔 ERROR Failed to access: http://namecheck.fontdata.com. Please report this issue at: https://github.com/googlefonts/fontbakery/issues [code: namecheck-service]
was that only a temporary hiccup on the website? Or do we still get this ERROR?
was that only a temporary hiccup on the website?
Does it matter? It's an external service, maybe we should expect that it can fail and catch that ERROR and make it a FAIL.
I prefer to keep this as an ERROR because we want people to report it here whenever the site stops working, as we may need to address eventual changes in the integration with the service. And FAIL is dedicated to problems with the font project, while ERRORs are for problems with the setup.
Ok. Then maybe catch that ERROR, add some explanation, about what is happening, like:
This check relies on the external service http://namecheck.fontdata.com via the internet.
While the service cannot be reached or does not respond this check is broken.
You can exclude this check with the command line option:
"-x com.google.fonts/check/fontdata_namecheck"
or wait until the service is available again. If the problem persists please report this
issue at: https://github.com/googlefonts/fontbakery/issues.
original error message: {error.message}
And raise it as new ERROR again.
May I suggest to look into implementing the Fontdata API instead and/or update the current request URL to use https instead?
instead
Using the API and/or using HTTPS will not spare us from an unresponding service or bad network.
implementing the Fontdata API
All I can find about the API is https://namecheck.fontdata.com/about/
Developers / API
Even this tool is in an very early stage there is an API provided to programtically access the data.
@larsschwarz where is the documentation on how to use the API?
@graphicore See https://github.com/googlefonts/fontbakery/issues/2684#issuecomment-559297019
It's back online. As every 5 years I'd like to remind of this comment here
https://github.com/fonttools/fontbakery/issues/2684#issuecomment-559297019
The site offers an API since 2019, no need to scrape/parse old fashioned HTML ;)