That bug has been described on https://launchpad.net/ubuntu/+source/poppler/+bug/26118 "... http://librarian.launchpad.net/4941174/SplashFTFont.cc Modified splash/SplashFTFont.cc from poppler-0.5.4 I think I nailed it! First of all, the exact same issue arises in Edgy, which is what I am using now. However, it's easy to fix. Second, it's a poppler problem, not an Evince problem per se. See file splash/SplashFTFont.cc in poppler-0.5.4 (the Edgy version), lines 180 and following. This is where poppler loads glyphs for the splash output device; this code comes from xpdf, btw. Basically, there is a compile-time check to see whether freetype has the bytecode interpreter enabled; if so, IT IS USED regardless of whether anti-aliasing is on or off. Otherwise, no hinting is used if anti-aliasing is on. Again, this is a compile-time check. The problem is that, for most fonts used with LaTeX (but I'd say for most other fonts, too) it's best to omit hinting altogether. I fixed the problem by simply deleting the portion of the code that is triggered if TT_CONFIG_OPTION_BYTECODE is defined, and instead leaving only the section that is compiled if it is not. Rebuilding with pdebuild and installing with dpkg -i did the trick. Ideally, this should be a gconf setting, I guess. Hope this helps, M ..."
removing code? gconf setting? Can you make a reasonable suggestion, please?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/411.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.