Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

namecheck.fontdata.com site is down creating error #4905

Open
mitradranirban opened this issue Nov 14, 2024 · 3 comments
Open

namecheck.fontdata.com site is down creating error #4905

mitradranirban opened this issue Nov 14, 2024 · 3 comments

Comments

@mitradranirban
Copy link

Observed behaviour

The fontdata_namecheck giving following error
ERROR
Failed to access: http://namecheck.fontdata.com/. 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

on checking I found that the site is down for weeks

Expected behaviour

Like fontbakery maintains a cached data of vendor_id from https://www.microsoft.com/typography/links/vendorlist.aspx, a similar cached data of font names should be maintained at fontnakery server to check against.

@mitradranirban mitradranirban changed the title namecheck.fontdata.con site is down creating error namecheck.fontdata.com site is down creating error Nov 14, 2024
@felipesanches
Copy link
Collaborator

Well... this database is (as far as I can tell) currently kept private.

@davelab6, do I recall correctly that you talked to the maintainer of namecheck.fontdata.com in the past, regarding hosting a cache of the database on a public repo? I do not remember exactly what was their response to that request.

@mitradranirban
Copy link
Author

Instead of relying on private data of an individual, it is better googlefonts should maintain its own data of copyrighted fonts curated through Google search, so that a font name with same name as a copyrighted commercial font does not get included in Google font causing legal issues.

@felipesanches
Copy link
Collaborator

To be a bit more precise, this is not a matter of Google Fonts policy exclusively, but instead it is a general one. This check belongs to the Universal profile as it is useful for everyone. Nobody wants to release a new font reusing a preexisting family name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants