Encoding problems in FDK-generated font

[Jens]

Hi!

I generated an OT-CFF font with FDK 2.5 and noticed that some keystrokes like ü, ö, ä, ß are mapped to a wrong glyph.

My command line is:

Code:

makeOTF25.exe -f MyFont.pfa -o MyFont.otf -ff MyFont.fea -mf MyFont.fmndb -gf MyFont.goadb -r -osv 4 -osbOn 7 -osbOn 8 -osbOff 9

I dumped the font using ttx.py from FontTools and compared it to a working font I generated with FontLab Studio 5.04. The biggest notable difference is that the correct font has this entry in the CFF table:

Code:

<Encoding name="StandardEncoding"/>

while in the FDK-generated font that part looks like this:

Code:

<Encoding>
        <map code="0x0" name=".null"/>
        <map code="0xd" name="CR"/>
        <map code="0x20" name="space"/>
        <map code="0x21" name="exclam"/>
        <map code="0x22" name="quotedbl"/>
        <map code="0x23" name="numbersign"/>

...

Code:

<map code="0xdf" name="Thorn"/>
        <map code="0xe0" name="germandbls"/>
        <map code="0xe1" name="agrave"/>
        <map code="0xe2" name="aacute"/>
        <map code="0xe3" name="acircumflex"/>
        <map code="0xe4" name="atilde"/>
        <map code="0xe5" name="adieresis"/>
        <map code="0xe6" name="aring"/>

...

Note that in the beginning the mapping is correct, but in the lower part it is off by one (starting at

Code:

<map code="0xae" name="registered"/>
<map code="0xb0" name="macron"/>

) which explains the keystrokes resulting in wrong glyphs.

I'm not sure why the Encoding part is there at all instead of just using the "StandardEncoding", and why the mapping turns out wrong. Is this a bug in FDK or am I missing some option? In my goadb file the unicodes are correct.

I've attached the complete beginning of the CFF table to this post in case it is relevant.

Thanks for any ideas,
Jens

[Read Roberts (Adobe)]

It sounds like you  have found two levels of bugs in the FDK. The first I was aware of, is that the work flow within makeotf 2.5 now uses the tx tool, and the tx tool will in some cases  convert a font whose Encoding vector is set to StandardEncoding to a custom encoding array. I haven't reported this because the custom array is equivalent to the StandardEncoding vector and in any case, the Encoding key value in a CFF table is supposed to be ignored entirely.

However, I learn from your e-mail that the conversion from StandardEncoding to a custom error may be wrong in some cases, so that the custom array is not equivalent to StandardEncoding.

You should be able to work around this issue by making sure that the glyphs in your source pfa file are in the order specified by the StandardEncoding definition: the case where the conversion happens is the source font does have all the StandardEncoding glyph names, but not the order. Also, a new build of the FDK will be out in a few days which does not cause the change in the Encoding value.

I am also very troubled by your comment that you get the wrong glyphs from keystrokes. This should absolutely not happen, as the CFF encoding is ignored in the context of an OTF, both by specification and in practice - only the cmap table encoding is used, and this specified by the GOADB. This makes me wonder if something more complicated is going on. Can you send me a copy of the build data for this font? I do need the features files and the GOADB file. I do not need the font.pfa if you can send me the dump from 'tx -mtx font.pfa", as I can use that to rearrange a test font with the same glyph names and glyph order.

Regards,
  Read Roberts

[Read Roberts (Adobe)]

FYI: in  FDK build 2140 ( makeotf lib 2.0.21325), the  CFF Encoding vector in a OpenType font is indeed written incorrectly, by makeotf with an off-by-one error, just as described by Jens, when the source Type1 font has a set of glyphs that meet the requirements for a Type 1 StandardEncoding vector, but does not meet the requirements for a CFF StandardEncoding vector.  This does not occur in earlier versions of the FDK, and is fixed in the version currently posted.
- Read Roberts

[pauljay]

Thanks for the tip here on the coding I found this post in Google after much searching,and finally think I have a solution

Much appreciated

Paul

[Tags:]

Jump to: Please select a destination: ----------------------------- News and announcements ----------------------------- => Announcements from the forum’s moderators => News from the font industry ----------------------------- Type design and font technology ----------------------------- => Principles of type design => OpenType Layout feature development => Hinting => Font Formats and OpenType => Web font embedding => Font licensing ===> Electronic EULA Abstract (EEULAA) ----------------------------- Education and collaboration ----------------------------- => Work: Offers => Work: Looking for => Education: Offers => Education: Looking for => Typographic Events and Conferences ----------------------------- FontLab products ----------------------------- => News from FontLab => FontLab Studio ===> FontLab Studio Problems ===> FontLab Studio Tips and Tricks ===> FontLab Studio Wish List ===> FontLab Studio Public Preview => Fontographer ===> Fontographer Problems ===> Fontographer Wish List => TypeTool => AsiaFont Studio => TransType => ScanFont => SigMaker => Other Products ----------------------------- Photofont products ----------------------------- => BitFonter => Photofont WebReady => Photofont Start => Photofont ID => Photofont QX => The Photofont technology ----------------------------- Adobe Type products ----------------------------- => Adobe FDK for OpenType (AFDKO) ----------------------------- Apple Font products ----------------------------- => Apple Font Tools ----------------------------- Microsoft Typography products ----------------------------- => Microsoft Font Validator => Microsoft Visual OpenType Layout Tool (VOLT) => Microsoft Web Embedding Fonts Tool (WEFT) => Microsoft Visual TrueType (VTT) ----------------------------- Other products and Python scripting ----------------------------- => Python scripting => FontTools/TTX => Other font-related tools ----------------------------- Special interest groups ----------------------------- => SBL Fonts ===> SBL Hebrew ===> SBL Greek ===> SBL BibLit ----------------------------- FAQ and TechNotes ----------------------------- => OpenType Layout feature development FAQ and TechNotes => Hinting FAQ and TechNotes => Font Formats and OpenType FAQ and TechNotes => Web font embedding FAQ and TechNotes => Font licensing FAQ and TechNotes => FontLab Studio FAQ and TechNotes => Fontographer FAQ and TechNotes => TypeTool FAQ and TechNotes => AsiaFont Studio FAQ and TechNotes => TransType FAQ and TechNotes => ScanFont FAQ and TechNotes => SigMaker FAQ and TechNotes => BitFonter FAQ and TechNotes => Photofont WebReady FAQ and TechNotes => Photofont Start FAQ and TechNotes => Photofont ID FAQ and TechNotes => Photofont QX FAQ and TechNotes ----------------------------- Archive (MSN Groups) ----------------------------- => Archive: Old FontLab forum ===> Archive: FontLab Tips and Tricks ===> Archive: FontLab Bugs and Problems ===> Archive: FontLab Wish List ===> Archive: FontLab Announcements => Archive: Old Microsoft Font Validator group => Archive: Old Microsoft VOLT group => Archive: Old Microsoft VTT group ===> Archive: VTT Downloads ===> Archive: VTT Support ===> Archive: VTT Suggestions => Archive: Old Microsoft WEFT group ===> Archive: WEFT III ===> Archive: EOT for Email => Archive: Old SBL Fonts group ===> Archive: SBL Hebrew ===> Archive: SBL Greek ----------------------------- Various ----------------------------- => fontlab.com — the FontLab website => forum.fontlab.com — this forum => Other Topics