Bug#720953: Bug#742767: fonts-texgyre: Termes font in does not render ligatures in evince
Hi Norbert et al.,
this reads a bit complicated. So (a) Tex Gyre Termes has an incorrectly
named fl-ligature glyph and (b) this has become obvious in a recent
update of the poppler libraries and (c) a bug has been filed against
fontconfig because it registers Termes as an alternative to Times
despite this incompatibility.
Please note that the change I proposed back then was to register Termes
as an alternative to Times by means of a fontconfig file. This has been
implemented and is currently shipped in the Debian package. However, in
the mean time, this configuration sniplet has made its way upstream into
fontconfig itself, rendering our own configuration files obsolete. I
have informed you about this in #735143 and you confirmed to remove the
Debian-specific fontconfig configuration files in the next upload.
So, I don't think that fontconfig or its configuration files are at
fault here. After all, Termes *is* a replacement font for Times, it has
just an incompatibly named ligature glyph. In my opinion, either the
font should get fixed (prefered) or poppler should get fixed/hacked to
include a workaround and be less picky about the glyph names - it worked
in previous releases after all.
Hope that helps!
- Fabian
Am Dienstag, den 20.05.2014, 12:09 +0900 schrieb Norbert Preining:
> Hi Fabian,
>
> last September on your suggestions we have changed the fontconfig
> hinting for tex-gyre.
>
> Now Roland (in cc, as well as both bugs) seems to have found
> an incompatibility which might require a rethinking.
>
> I would like to ask your opinion on this matter.
>
> Thanks for any comments
>
> Norbert
>
> On Wed, 26 Mar 2014, Roland Haas wrote:
> > Package: fonts-texgyre
> > Version: 2.004.2-4
> > Severity: normal
> > Tags: upstream
> >
> > Dear Maintainer,
> >
> > * What led up to the situation?
> > Updating the system so that fonts-gyrex is used as a replacement for Times.
> > Possibly due to changes in fontconfig priorities.
> > * What exactly did you do (or not do) that was effective (or
> > ineffective)?
> > Opening a pdf file containing fi or fl ligatures.
> > * What was the outcome of this action?
> > fi and fl ligatures do not render correctly, they show up as whitespace but can
> > be copied and pasted fine.
> > * What outcome did you expect instead?
> > fi and fl should show up.
> >
> > This is the same bug (I think) as reported on freedesktop's bug tracking
> > system:
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=73291
> >
> > where also a link to a sample pdf file is provided.
> >
> > -- System Information:
> > Debian Release: jessie/sid
> > APT prefers testing
> > APT policy: (500, 'testing')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> >
> > Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
> > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> > Shell: /bin/sh linked to /bin/dash
> >
> > Versions of packages fonts-texgyre depends on:
> > ii dpkg 1.17.6
> > ii tex-common 4.04
> >
> > fonts-texgyre recommends no packages.
> >
> > fonts-texgyre suggests no packages.
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-tex-maint-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> > Archive: https://lists.debian.org/20140327050053.27494.352.reportbug@horizon.tapir.caltech.edu
> >
>
> On Thu, 27 Mar 2014, Roland Haas wrote:
> >
> >
> > Hello Norbert,
> >
> > > On Wed, 26 Mar 2014, Roland Haas wrote:
> > >> fi and fl ligatures do not render correctly, they show up as
> > >> whitespace but can be copied and pasted fine.
> > >
> > >
> > >> From what I read at the freedesktop bug this is a problem with
> > >> the
> > > poppler libs ... I *really* don't understand what is the bug here
> > > in the texgyre fonts?
> > The issue seems to be that the Termes font uses the wrong name for the
> > fi and fl ligatures. See comment 7
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=73291#c7
> >
> > I am not sure if it the responsibility of the render (poppler) to map
> > both fi and f_i to the same glyph. Apparently there was some
> > uncertainty if this is a poppler bug
> > (https://bugs.freedesktop.org/show_bug.cgi?id=73291#c14) but
> > eventually was marked as being an issue with the font (last comment
> > https://bugs.freedesktop.org/show_bug.cgi?id=73291#c17 ).
> >
> > According to the comments in there the ligature shows up in gv since
> > gv prefers the gsfonts fonts over gyretex.
> >
> > Yours,
> > Roland
>
>
> ------------------------------------------------------------------------
> PREINING, Norbert http://www.preining.info
> JAIST, Japan TeX Live & Debian Developer
> GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
> ------------------------------------------------------------------------
>
Reply to: