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

NotoColorEmoji.ttf is not a valid TrueType or OpenType font #288

Closed
paulyc opened this issue Jan 23, 2020 · 1 comment
Closed

NotoColorEmoji.ttf is not a valid TrueType or OpenType font #288

paulyc opened this issue Jan 23, 2020 · 1 comment

Comments

@paulyc
Copy link

paulyc commented Jan 23, 2020

TrueType fonts require glyf/loca tables, OpenType fonts require CFF tables, NotoColorEmoji.ttf has neither and is simply rejected as invalid by many font engines. fontlint output follows

Copyright (c) 2000-2019. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
 with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
 Version: 20190801
 Based on sources from 19:31 UTC  4-Nov-2019-ML-D-GDK3.
Attempt to unget two characters
CHECKING     NotoColorEmoji.ttf
This font contains neither "CFF " nor "glyf"/"loca" tables
The following table(s) in the font have been ignored by FontForge
  Ignoring 'CBDT' color bitmap data table
  Ignoring 'CBLC' color bitmap location table
No (useable) bitmap strikes in this TTF font: /home/paulyc/Downloads/NotoColorEmoji.ttf
Couldn't find a font file named /home/paulyc/Downloads/NotoColorEmoji.ttf
NotoColorEmoji.ttf is not in a known format (or uses features of that format fontforge does not support, or is so badly corrupted as to be unreadable)
Open: Failed to open: NotoColorEmoji.ttf
Called from...
 /usr/bin/fontlint: line 282
@paulyc
Copy link
Author

paulyc commented Jun 5, 2020

Guess that's Working As Intended™ unsure it's even realistically possible to implement as one, so I'll close this and leave it as Nice To Have™ now that it's [An] Officially Documented [Feature-Not-A-Bug]™ and blame the font engines for likely demanding a "Valid Font" extension

@paulyc paulyc closed this as completed Jun 5, 2020
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

1 participant