FreeType 2.4.0 enables the bytecode interpreter by default. (This is a major change from FreeType 2.3.x.)
I was able to reproduce the problem here (more or less by accident). If I build Xpdf using the FreeType include files that are installed by default on my system (FreeType 2.3.4 with the bytecode interpreter disabled), then the xpdf binary shows the same problem -- even if it picks up the newer FreeType shared library. My guess is that your xpdf binary was compiled against an older version of FreeType (with the bytecode interpreter disabled), and that's what is causing the problem. - Derek On 2010 Aug 03, jida...@jidanni.org wrote: >>> http://www1.hl.gov.tw/bus/upload/%AA%E1%BD%AC%AB%C8%B9%42%A5%FA%C2%D7%BD%75%AE%C9%B6%A1%AA%ED.pdf > D> I'm not seeing a problem here. > D> What version of FreeType are you using? > Version table: > *** 2.4.0-2 0 > 500 http://ftp.tw.debian.org unstable/main Packages > D> Can you send me a screenshot from that first file that shows the > D> unreadable text? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
