[Poppler-bugs] [Bug 80093] does not render ligatures for TeX Gyre Termes font anymore

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Sep 20 17:57:46 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=80093

--- Comment #11 from Adrian Johnson <ajohnson at redneon.com> ---
Created attachment 106593
  --> https://bugs.freedesktop.org/attachment.cgi?id=106593&action=edit
map standard and expert ligatures to aglfn names

The problem is with the TeX Gyre Hermes fonts. It is claiming to be a drop in
replacement for the Standard 14 fonts but it is using names that are not
compatible with Standard 14.

It does not matter that Adobe is recommending different names for new fonts. If
TeX Gyre Hermes wants to be a replacement for the Standard 14 is has to provide
the same encoding as defined in ISO32000 Annex D and PS Lang Ref Appendix E.
There is no reason why the TeX fonts can't include both encodings. There are
only five affected glyphs so it would only be a few extra bytes added to the
fonts.

We can patch poppler to add the mapping for the ligatures but there is likely
to be other software that depends on the PDF/PS standard names. So the best fix
would be for TeX Gyre Hermes to support both names.

I don't agree with the patches that implement a generic two way mapping. The
only affected glyphs are "fi" and "fl" in the Standard encoding and "ff",
"ffi", and "ffl" in the Expert encoding. PDFs that are using other ligatures
will have the fonts embedded since the Standard 14 fonts won't have these other
ligatures. The patches are also missing support for the splash backend.

I am attaching a new patch that maps the five ligatures in both the cairo and
splash backends.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/poppler-bugs/attachments/20140921/ea00b5ff/attachment.html>


More information about the Poppler-bugs mailing list