[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#742767: TeX Gyre OpenType and wrongly(?) named glyphs



On 6/30/2014 1:15 PM, Boguslaw Jackowski wrote:

Norbert:
here at Debian recently a problem surfaced with respect to the
OpenType TeX Gyre fonts.

The problem is that the ligatures are named
    f_i
etc while display engines like poppler, as well as the orginal
PostScript fonts, use
    fi
etc.

In Debian and Ubuntu, currently the TeX Gyre fonts provide the
*standard* postscript fonts, due to be considered generally
better.

But that means, that at the current moment of one uses the TeX Gyre
fonts as a replacement for the PS fonts, the ligatures will not be
rendered at all.
[...]
Related bug reports are:
* Debian BTS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742767
* FreeDesktop: https://bugs.freedesktop.org/show_bug.cgi?id=73291

Dear Colleagues,

we are more than happy that the TeX Gyre collection
of fonts has been have been chosen as a default
font set in Debian distribution. And we are
sorry that we haven't predicted the problem
of the discrepancy between the "new" and "old"
ligatures name.

Our idea was to provide "partially new" fonts.

More precisely, we have assumed that the fonts in the
Type 1 format should be "as compatible as possible"
with the Adobe original fonts. In particular, we tried
to preserve (with some exceptions, due to obvious Adobe's
bugs) the original font metric and, moreover, we used the
"old-style" names for ligatures.

The fonts in the OTF format, however, we considered "new" ones
(note, e.g., that they have Unicode tables and that they are equipped
with the OTF typografic features, both absent from the original
Adobe fonts) and, therefore, following Adobe's recommendations
for the glyph naming in new fonts (see the mentioned by Karl
documentation http://sourceforge.net/adobe/aglfn/wiki/AGL%20Specification
and also Adam Twardoch's John Hudson's comments --
http://typophile.com/node/18452 and
http://typophile.com/node/33330 , respectively),
we assigned the new-style ligature names.

Indeed, so it's f_i etc and using fi for that and foo_bar_whatever for other ligatures makes no sense ... tounicode logic depends on conventions like the _ as ligature separator.

In the TeX Gyre Math fonts we also have used the new-style
ligature names.

Two questions:

1. What about using Type 1 fonts for "compatibility purposes"?
It seems to us taht it could be the simplest "patch", provided
the font rendering engines are able to handle conveniently
"obsolete" Type 1 fonts.

2. Does it make really sense to make a step
backward and revert to the old-style names in the OTF
TeX Gyre fonts (including TeX Gyre Math)? It is feasible,
but we are rather reluctant to introduce such a change,
as it is likely to cause fuss among TeX Gyre users.

It makes no sense ... if poppler does something with glyphnames (and i'm not sure why it would) it should deal with it properly and recognize "u", "uni", "index", numbers, "_", "." ... as classifiers and separators.

Dealing with inconsistencies in unicode and fonts is already a pain and adding more confusion makes no sense.

btw, If I grep my afm files for f_f and f_l I get lots of hits on linotype fonts like palatino-nova, aldus-nova, palatinosans* so there are type one fonts out there that use _ too.

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------


Reply to: