-
Notifications
You must be signed in to change notification settings - Fork 71
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
New script: which characters in a TTF are not in any GF .nam
subset?
#6
Comments
I've just implemented this and will send a pull request |
to tell us which characters in a TTF are not in any GF .nam subset. (issue googlefonts#6 and fonttools/fontbakery#1466)
to tell us which characters in a TTF are not in any GF .nam subset. (issue #6 and fonttools/fontbakery#1466)
@davelab6 You can test it by cloning this repo and running, from within the root dir the I'll later package this, according to #3 and fonttools/fontbakery#1639 |
Please let me know if you need further improvements to the script. |
@davelab6 Reopen if you need anything else here. |
Also, after packaging, the script will be available as a subcommand (just like we do in FontBakery). Something like this:
|
But these are in our sets.
|
I updated this in 91ee82e |
ok, I fixed a silly mistake in the logic of that. This is what we get now: @davelab6 what do you think? |
Some of the codepoints missing, as listed in the output above are:
|
is it good now, @davelab6 ? |
Yes I think so
…On Oct 31, 2017 10:34 PM, "Felipe Corrêa da Silva Sanches" < ***@***.***> wrote:
is it good now, @davelab6 <https://github.com/davelab6> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAP9y372fCZCuFN6NPYK4ZOHXPaY7uS4ks5sx9jOgaJpZM4QNZxp>
.
|
Is the intent of this tool to find characters the production API wouldn't support? - if so you should use the nam files that prod uses instead. |
@davelab6 said:
Originally requested at:
fonttools/fontbakery#1466
The text was updated successfully, but these errors were encountered: