Multiple issues with UFO file generated

Post your bug reports here. Include information that helps us to understand and reproduce the bug.
Post Reply
NFSL2001
Posts: 2
Joined: Sun Jul 17, 2022 3:51 pm

Multiple issues with UFO file generated

Post by NFSL2001 »

1. In the name table, all multilingual names generated are missing the encodingID.
2. Names that were supposed to be in both name ID = 1 and name ID = 16 only gives name ID = 16, no name ID = 1. name ID = 4 that relies on name ID 1+2 or 16+17 isnt exported too (normally exported font files have those).
3. Generated font files contains platformID=1 platEncID=0 while generated UFO files doesn't.
4. The features.fea file might sometimes contains glyph names that are over 63 characters long. In the generated font files, the names are replaced from human readable names to Unicode values (for ligatures).
5. According to the OpenType Feature File Specification, the class [zero - nine] is not a valid range, but the feature.fea generated contains the range.

Also a wishlist:
1. allow uniXXXX style naming from Adobe.
2. use UTF-8 instead of UTF-8 with BOM for all the text files.
Erwin Denissen
Moderator
Moderator
Posts: 10747
Joined: Fri Oct 04, 2002 12:41 am
Location: Bilthoven, The Netherlands
Contact:

Re: Multiple issues with UFO file generated

Post by Erwin Denissen »

Can you please send us a sample font, so we can look into this?
Erwin Denissen
High-Logic
Proven Font Technology
Erwin Denissen
Moderator
Moderator
Posts: 10747
Joined: Fri Oct 04, 2002 12:41 am
Location: Bilthoven, The Netherlands
Contact:

Re: Multiple issues with UFO file generated

Post by Erwin Denissen »

NFSL2001 wrote: Mon Jan 16, 2023 4:09 pm 1. In the name table, all multilingual names generated are missing the encodingID.
2. Names that were supposed to be in both name ID = 1 and name ID = 16 only gives name ID = 16, no name ID = 1. name ID = 4 that relies on name ID 1+2 or 16+17 isnt exported too (normally exported font files have those).
3. Generated font files contains platformID=1 platEncID=0 while generated UFO files doesn't.
We have made several improvements that will solve the first and probably the other two mentioned issues. Expect the update early February.
NFSL2001 wrote: Mon Jan 16, 2023 4:09 pm 4. The features.fea file might sometimes contains glyph names that are over 63 characters long. In the generated font files, the names are replaced from human readable names to Unicode values (for ligatures).
Is this just an observation or is there something wrong?
NFSL2001 wrote: Mon Jan 16, 2023 4:09 pm 5. According to the OpenType Feature File Specification, the class [zero - nine] is not a valid range, but the feature.fea generated contains the range.
Good point. We will no longer put such ranges in fea code.
NFSL2001 wrote: Mon Jan 16, 2023 4:09 pm Also a wishlist:
1. allow uniXXXX style naming from Adobe.
2. use UTF-8 instead of UTF-8 with BOM for all the text files.
We will add these to the wish list.
Erwin Denissen
High-Logic
Proven Font Technology
Post Reply