On Thu, Jan 12, 2017 at 04:32:53PM +0100, Fabian Greffrath wrote: > Am Donnerstag, den 12.01.2017, 12:25 +0100 schrieb Fabian Greffrath: > > Although poppler isn't really the root of the problem, it is best to > > fix > > it there. I re-assign this bug to poppler (I assume you are using the > > version in stable, right?) and try to find a patch over the weekend > > for > > upstream application. > > Well, strange! I was just going to reproduce this issue on my own > testing/unstable system, but -- although I am using the fonts from > fonts-texgyre as substitutes for the base fonts -- I am not able to > reproduce this bug. > > Well, there are 22 revisions between the poppler versions in stable and > testing, so I assume the bug has been fixed in between (it has not been > fixed in the fonts-texgyre package between stable and testing, I have > checked that). > > So, not sure what to do with this bug report then...
I believe this has been partially fixed in poppler with https://bugs.freedesktop.org/96994, though it's probably still possible to have missing characters, depending on the PDF and on which fonts are chosen. At one time I had attempted to improve on the way poppler chooses fonts, but it's a little tricky to do that in a way that doesn't harm the rendering of some documents. Ideally more documents would embed the fonts so these issues could be avoided.
