The bug is in fontconfig. Fontconfig added the Gyre font names to the list of suitable replacements for the base PostScript fonts because the shapes and metrics are compatible.
What they didn’t notice (until the bug reports started) is that the Gyre authors use the names /f_i, /f_l, /f_f, /f_f_i and /f_f_l for the f-ligs, whereas the original PS fonts — which predate the current glyph name best practices — used the names /fi, /fl. When rendering a pdf file which uses fonts but does not embed them or embed subsets of them, the renderer needs to find a substitute. If fontconfig is used to find such a substitute, and it returns a font which lacks the glyph names said renderer wants — even if it has the glyphs under a different name — the desired glyph will not get painted. Ideally, renderers would notice that the glyph name they want is unavailable and look for alternate names. Or in the case of a known ligature fall back to the un-ligated glyphs. But that hasn’t been written. The quick fix is to limit font equivilents to those which also have the same glyph naming scheme. Fontconfig did that in commit c6aa4d4bfc, in responce to the freedesktop bug report noted above. Distributions should make the same change in their fontconfig packaging. Distributions should do the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317599 Title: Evince doesn't show "fi"-ligatures in a pdf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-gyre/+bug/1317599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
