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

Bug#742767: marked as done (fonts-texgyre: Termes font in does not render ligatures in evince)

Your message dated Fri, 9 Aug 2019 19:49:34 +0200
with message-id <80e5c943-abae-998f-09bd-73e3c83e7ad5@web.de>
and subject line Re: Bug#742767: fonts-texgyre: Termes font in does not render ligatures in evince
has caused the Debian Bug report #742767,
regarding fonts-texgyre: Termes font in does not render ligatures in evince
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
742767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742767
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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.

--- End Message ---
--- Begin Message --- 
Am 09.08.2019 um 19:01 teilte Haas, Roland mit:

Hi Roland,

therefore I take the freedom to close the issue. Thanks for response!

Hilmar

> I can no longer reproduce the issue and the sample file
> http://www.cs.dartmouth.edu/~doug/mdmspe.pdf renders correctly with both evince and xpdf.
> 
> So this seems to have been fixed one way or the other.
> 
> Thank you for following up!
> 
> Installed packages are:
> 
> fonts-texgyre:
> 
> ii  fonts-texgyre	20180621-3
> 
> evince:
> 
> ii  evince	3.30.2-3
> 
> Versions of packages evince depends on:
> ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
> ii  evince-common                                3.30.2-3
> ii  gsettings-desktop-schemas                    3.28.1-1
> ii  libatk1.0-0                                  2.32.0-2
> ii  libc6                                        2.28-10
> ii  libcairo-gobject2                            1.16.0-4
> ii  libcairo2                                    1.16.0-4
> ii  libevdocument3-4                             3.30.2-3
> ii  libevview3-3                                 3.30.2-3
> ii  libgdk-pixbuf2.0-0                           2.38.1+dfsg-1
> ii  libglib2.0-0                                 2.60.6-1
> ii  libgnome-desktop-3-17                        3.30.2.1-2
> ii  libgtk-3-0                                   3.24.10-1
> ii  libnautilus-extension1a                      3.30.5-2
> ii  libpango-1.0-0                               1.42.4-7
> ii  libpangocairo-1.0-0                          1.42.4-7
> ii  libsecret-1-0                                0.18.7-1
> ii  shared-mime-info                             1.10-1
> 
> xpdf:
> 
> Versions of packages xpdf depends on:
> ii  libc6         2.28-10
> ii  libgcc1       1:9.1.0-10
> ii  libpaper1     1.1.28
> ii  libpoppler82  0.71.0-5
> ii  libstdc++6    9.1.0-10
> ii  libx11-6      2:1.6.7-1
> ii  libxm4        2.3.8-2
> ii  libxt6        1:1.1.5-1+b3
> 
> System information:
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (1000, 'testing'), (900, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.19.0-5-amd64 (SMP w/24 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Yours,
> Roland
> 
>> Am 27.03.2014 um 06:00 teilte Roland Haas mit:
>>
>> Hi Roland,
>>
>> I'm going through some old bugs.
>>
>> This bug went back and forward and different people identified different
>> root causes (poppler or the fonts itself).
>>
>> In the sample document from the bug report I can't see this issue. Both
>> pieces of software (tex-gyre and poppler) got new upstream releases in
>> the meantime. Are you still able to reproduce the issue?
>>
>> Hilmar
> 
> 
> 


-- 
sigfault
#206401 http://counter.li.org

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: