On 7/1/2014 1:05 AM, Norbert Preining wrote:
On Mon, 30 Jun 2014, Hans Hagen wrote:
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.
Interestingly I cannot trigger the bug with xelatex and Palatino Sans,
for example.
If I understand right, the bug has to do with viewing (rendering) a
glyph in a pdf file. In pdf the page stream has numbers pointing to a
(normally) subset index which in turn maps onto the font slots (can be
any order). Normally no glyph name is involved in that. Those names
might kick in when copying is involved and no tounicode mapping is
present in the pdf.
As you mention in a previous mail, it's a bug in poppler (or maybe some
library it uses) that somehow used glyph names. I agree that there is no
need to change the font (and I cannot predict what other issues might
show up by duplicating glyph names; for instance turning f + i into an
fi glyph .. it would still map onto the one associated with f_i). Using
the unicode ligature sis a bad idea anyway as all these ligs in unicode
make not much sense and is just there to suit bad old times.
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
-----------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
