*******
For glyphs that represent ligatures of standard Unicode characters, there are two suggested formats for their glyph names, as follows:
1. Descriptive. The decomposition is expressed by joining the glyph names of the standard Unicode characters, in order, using an underscore (U+005F; LOW LINE). The glyph names of the characters should specify the "uni" or "u" prefixes and use uppercase hexadecimal digits, as described above, or with a name from AGL. For example, the "o f f i" ligature should be named "o_f_f_i."
2. UV with "uni" prefix. ....
*******
Thus, poppler should check for f_i *as*well*as* fi (for backward compatibility).
Ok, I reopen this bug against poppler, as poppler seems to implement something that is in contradiction to what Adobe recommends.
I refer you to the Adobe Glyph List Specification sourceforge. net/adobe/ aglfn/wiki/ AGL%20Specifica tion/
http://
which clearly states in Section 6. Assigning glyph names for new fonts:
*******
For glyphs that represent ligatures of standard Unicode characters, there are two suggested formats for their glyph names, as follows:
1. Descriptive. The decomposition is expressed by joining the glyph names of the standard Unicode characters, in order, using an underscore (U+005F; LOW LINE). The glyph names of the characters should specify the "uni" or "u" prefixes and use uppercase hexadecimal digits, as described above, or with a name from AGL. For example, the "o f f i" ligature should be named "o_f_f_i."
2. UV with "uni" prefix. ....
*******
Thus, poppler should check for f_i *as*well*as* fi (for backward compatibility).
Thanks
Norbert Preining
TeX Live Team