Bug#740801: zathura: Ligatures, like fi, are not rendered. (fwd)
Hi, On 2014-07-04 01:39, Norbert Preining wrote: As I'm currently writing, the patch has been considered a good starting point but it is not complete yet, nor it has been ACKed. Agreed. But the whole point is that it is a *regression* because in older versions of poppler it did work. So there should be code or a way to find what caused the problem. Sure, just like any other regression. I will wait when there's at least a complete fix upstream, otherwise it is piling up hacks on hacks. But I am not sure whether it will be included. The devs stated in https://bugs.freedesktop.org/show_bug.cgi?id=73291 that the *font* should be fixed, which means they are not acknowledging that the problem is within the proper interpretation for glyph names in poppler. The only poppler developer talking in that bug is Adrian Johnson (comments #5, #7, #8, #10), which only notes the issue is about the different glyph naming used by texgyretermes-bold.ttx. I don't see how that implies the font is buggy nor we won't change poppler, nor how you can draw such conclusions from it, especially when Adrian is quite skilled. The rest of the comments there are by simple users. OTOH, the font developers have a clear stand and try to be according to the guidelines put forth by Adobe. Poppler upstream maintainers seem to be ignorant about this, and even worse, seem to be completely incooperative. Pointers to this? In both the freedesktop bugs (#73291 and #80093), See the abov bug report where in comment 19 Christopher Yeleighton states that it is a bug in the fonts. It seems you missed what I said about him. Simply ignore what he says, really. As a side note: If you follow https://bugs.freedesktop.org/show_bug.cgi?id=25240 then you will see what the attitude of (at least one) poppler developer is concerning bugs including patches. This regards just one specific feature, I don't see how that should represent the official view on what poppler developers say or do, and having contributed to poppler for many years I can tell you quite a lot of features and bugfixes have been added over the years. Please don't generalize. Moreover, few months ago I contacted you about testing poppler the 0.25.x pre-releases of 0.26 and other details, and never got anything I know, I was busy packaging 2014, and maybe you don't know through which library hell I had to go due to libpng maintainers keeping libpng = 1.5 out of Debian. OK, but if you don't reply, even in a short way, telling me so, how can I know? I can imagine you could be busy, yet a bit of testing from a core component like TeX with newer poppler series would be nice to have. I have spent weeks trying to fix these problems - I honestly cannot invest more time just to test compatibilities. I do think it would be a very useful thing to do, especially to not be later in a situation where a new poppler version causes some issue (regression or not), and then I read bad remarks about poppler... And with the above email I suggested to include a fix since my feeling from the two freedesktop bugs is that poppler will not fix this regression. Can you please try to not be that pessimist like that, for a moment? I told you above that the first review of the patch in fdo#80093 considered it a good starting point, and that I will handle the issue in Debian once there is an ACKed patch upstream. There is no secret plot or whatever meant to make the interaction with TeX worse; just like you said above you were busy, also poppler people are. Thanks for the patience, -- Pino Toscano -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740801: zathura: Ligatures, like fi, are not rendered. (fwd)
Hi Pino, On Fri, 04 Jul 2014, Pino Toscano wrote: There is no secret plot or whatever meant to make the interaction with TeX worse; just like you said above you were busy, also poppler people are. Sorry, don't get me wrong ... *I* don't care for that This has *nothing* to do with TeX - nothing at all ... TeX will embed the fonts and there will be no problem. It was all about having the TG fonts as standard replacement for the Adobe PS fonts, an agenda set forth not by me, I just took some patches for the fonts-texgyre ;-) If it is for the TeX world, there is nothing to change ;-) And concerning the testing of new popplers - there is something I have to admit - since several releases I don't think too much about this anymore, as it works out of the box in 99.99% of the cases. Poppler was a problem in the beginning (0.6, 0.8 or so), when every release brought a change in API of things the TeX progrs use. This is not anymore the case. So again, for me poppler is not the main problem anymore, that is libpng, harfbuzz, cairo etc! Thanks for your understanding Norbert 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740801: zathura: Ligatures, like fi, are not rendered. (fwd)
Hi, On 2014-07-01 01:25, Norbert Preining wrote: This bug report seems to be related: https://bugs.freedesktop.org/show_bug.cgi?id=73291 This fix is not in fontconfig, nor in the TeX Gyre fonts, but poppler needs to be fixed. From what I see, the fontconfig change was just a workaround/hack, not a real fix. I suggest the Debian poppler maintainers to adopt the patch by Sebatisan to the poppler source to make ligatures in new style fonts again available, given in this freedesktop bug: https://bugs.freedesktop.org/show_bug.cgi?id=80093 As I'm currently writing, the patch has been considered a good starting point but it is not complete yet, nor it has been ACKed. I will wait when there's at least a complete fix upstream, otherwise it is piling up hacks on hacks. Poppler upstream maintainers seem to be ignorant about this, and even worse, seem to be completely incooperative. Pointers to this? In both the freedesktop bugs (#73291 and #80093), the only poppler developers writing are Adrian Johnson and James Cloos; other people (especially Christopher Yeleighton, known also as Křištof Želechovski, which pretends to know stuff, and did the initial reassign) are not. Also, Norbert, it would be nice if you could stop this kind of aggressive attitude and sneaky remarks towards poppler, since there's simply no reason for them, and they surely won't help cooperation. Sure, poppler has bugs and sometimes regressions, like in this case, but reacting with such anger (especially when none of the right poppler people, upstream or also in Debian (which would be me) is contacted) is not productive. Moreover, few months ago I contacted you about testing poppler the 0.25.x pre-releases of 0.26 and other details, and never got anything back from you. Cooperation usually goes in both directions, not one side tries to improve, and gets nothing but yell from the other side on issues. Thanks, -- Pino Toscano -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740801: zathura: Ligatures, like fi, are not rendered. (fwd)
Hi Pino, As I'm currently writing, the patch has been considered a good starting point but it is not complete yet, nor it has been ACKed. Agreed. But the whole point is that it is a *regression* because in older versions of poppler it did work. So there should be code or a way to find what caused the problem. I will wait when there's at least a complete fix upstream, otherwise it is piling up hacks on hacks. But I am not sure whether it will be included. The devs stated in https://bugs.freedesktop.org/show_bug.cgi?id=73291 that the *font* should be fixed, which means they are not acknowledging that the problem is within the proper interpretation for glyph names in poppler. OTOH, the font developers have a clear stand and try to be according to the guidelines put forth by Adobe. Poppler upstream maintainers seem to be ignorant about this, and even worse, seem to be completely incooperative. Pointers to this? In both the freedesktop bugs (#73291 and #80093), See the abov bug report where in comment 19 Christopher Yeleighton states that it is a bug in the fonts. Maybe he is not a developer, but by now I haven't seen any clear statement in *either* of the bugs that the developers consider this a regression. As a side note: If you follow https://bugs.freedesktop.org/show_bug.cgi?id=25240 then you will see what the attitude of (at least one) poppler developer is concerning bugs including patches. Honestly, this does *not* give me a good feeling about ideal cooperation. I asked in that bug report for arguments, never an answer, nobody got an answer. This is the interaction I don't want to have. Sure, poppler has bugs and sometimes regressions, like in this case, but reacting with such anger (especially when none of the right poppler people, upstream or also in Debian (which would be me) is contacted) is not productive. I did not contact you but upstream, this is where the original bug was filed. Moreover, few months ago I contacted you about testing poppler the 0.25.x pre-releases of 0.26 and other details, and never got anything I know, I was busy packaging 2014, and maybe you don't know through which library hell I had to go due to libpng maintainers keeping libpng = 1.5 out of Debian. I have spent weeks trying to fix these problems - I honestly cannot invest more time just to test compatibilities. And why did I not contact you - because it is not a Debian bug, but an upstream bug. And with the above email I suggested to include a fix since my feeling from the two freedesktop bugs is that poppler will not fix this regression. Anyway, it was never considered a remark on *your* work packaging poppler in Debian, just a suggestion to include a patch to make poppler again standard compliant (in some sense). Norbert 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740801: zathura: Ligatures, like fi, are not rendered. (fwd)
Dear Debian Poppler Maintainers, dear all, This bug report seems to be related: https://bugs.freedesktop.org/show_bug.cgi?id=73291 This fix is not in fontconfig, nor in the TeX Gyre fonts, but poppler needs to be fixed. Adobe Glyph specification states clearly that new fonts should use f_i etc as glyph names for ligatures. See my last post in the above freedesktop bug. I suggest the Debian poppler maintainers to adopt the patch by Sebatisan to the poppler source to make ligatures in new style fonts again available, given in this freedesktop bug: https://bugs.freedesktop.org/show_bug.cgi?id=80093 Poppler upstream maintainers seem to be ignorant about this, and even worse, seem to be completely incooperative. I *STRONGLY* suggest that this patch is included in the Debian poppler packages. that bug report, and linked to a commit: http://cgit.freedesktop.org/fontconfig/commit/?id=c6aa4d4bfcbed14f39d070fe7ef90a4b74642ee7 Which is the wrong approach taken by fontconfig. Norbert 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740801: zathura: Ligatures, like fi, are not rendered. (fwd)
Hi there, fonts-texgyre maintainers.
I am forwarding this (see below, from bug 740801) as the upstream poppler
maintainers believe that there is a bug in TeX Gyre Termes.
I have not yet verified the source code to see if the ligature is
incorrectly implemented, but temporarily uninstalling fonts-texgyre makes
the problem go away for programs that use poppler (like qpdfview, evince,
atril).
To avoid having the font blacklisted in fontconfig (which would simply kill
the font for all purposes), perhaps a small patch could be implemented?
When contacting me, please, keep me in CC's, as I am not subscribed to the
bug, nor to the mailing list.
Thanks,
Rogério.
- Forwarded message from Florian fb...@gmx.net -
Date: Mon, 02 Jun 2014 17:07:55 +0200
From: Florian fb...@gmx.net
To: Debian Bug Tracking System 740...@bugs.debian.org
Subject: Re: zathura: Ligatures, like fi, are not rendered.
X-Mailer: reportbug 6.5.0
Message-ID: 20140602150755.21588.54814.report...@arne.uni-graz.at
Package: libpoppler-glib8
Version: 0.24.5-4
Followup-For: Bug #740801
This bug report seems to be related:
https://bugs.freedesktop.org/show_bug.cgi?id=73291
There is also a fix (or workaround, in fontconfig) mentioned in
that bug report, and linked to a commit:
http://cgit.freedesktop.org/fontconfig/commit/?id=c6aa4d4bfcbed14f39d070fe7ef90a4b74642ee7
Since this bug affects most of the pdfs I am using for quite some
time now, I would be happy if this patch could be applied.
Thanks for your work, Florian
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libpoppler-glib8 depends on:
ii libc6 2.18-7
ii libcairo2 1.12.16-2
ii libfreetype6 2.5.2-1
ii libglib2.0-0 2.40.0-3
ii libpoppler44 0.24.5-4
ii libstdc++6 4.9.0-5
ii multiarch-support 2.18-7
libpoppler-glib8 recommends no packages.
libpoppler-glib8 suggests no packages.
-- no debconf information
- End forwarded message -
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
