-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Unexpected Subfamily 'Book' #1046
Comments
|
https://learn.microsoft.com/en-us/typography/opentype/spec/name#name-ids
Fontforge name is Making mental note |
[why] Sometimes we set an empty string as SubFamily name. That ends up as 'Book' which is unexpected. [how] The translation from empty to "Book" is done by Fontforge, at least with version 20220308. Make sure we always have a SubFamily, and if we don't that must be a 'Regular'. [note] This was only a problem with the old naming engine. --makegroups got this right always. Fixes: #1046 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why] Sometimes we set an empty string as SubFamily name. That ends up as 'Book' which is unexpected. [how] The translation from empty to "Book" is done by Fontforge, at least with version 20220308. Make sure we always have a SubFamily, and if we don't that must be a 'Regular'. [note] This was only a problem with the old naming engine. --makegroups got this right always. Fixes: #1046 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why] Sometimes we set an empty string as SubFamily name. That ends up as 'Book' which is unexpected. [how] The translation from empty to "Book" is done by Fontforge, at least with version 20220308. Make sure we always have a SubFamily, and if we don't that must be a 'Regular'. [note] This was only a problem with the old naming engine. --makegroups got this right always. Fixes: #1046 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference. |
[why] Sometimes we set an empty string as SubFamily name. That ends up as 'Book' which is unexpected. [how] The translation from empty to "Book" is done by Fontforge, at least with version 20220308. Make sure we always have a SubFamily, and if we don't that must be a 'Regular'. [note] This was only a problem with the old naming engine. --makegroups got this right always. Fixes: ryanoasis#1046 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Hmm,
Indeed what would be
Regular
isBook
.And it is not from the sourcefont.
Investigating
Originally posted by @Finii in #780 (comment)
The text was updated successfully, but these errors were encountered: