I think I'm a bit closer in understanding the issue. Thanx to Marcel's PDF creations (thank you Marcel, very appreciated), I've had a file for comparison. As I suspected, there is an "encoding"-problem or maybe rather an "encoding-interpretation"-problem. When creating a PDF through PostScript, the issue becomes "ironed" out, so this issue only arises when creating PDFs directly (like on-demand, streaming PDF's on the internet). My guess is that when Evince encounters an encoding that hasn't been implemented or can't be read, it assumes the encoding should be "Identity-H" (see the following links)
http://indesignsecrets.com/cid-identity-h-fonts-are-back.php http://www.talkgraphics.com/showthread.php?33648-What-is-identity-H Where as xPDF and Adobe Reader, either has the encoding implemented or assumes the encoding is "Custom", but display it as "Ansi". Evince displays it as "Identity-H" an tries to draw the text/letters as some weird font or attached vector-graphics image. So there is probably two issues ...one is the PDF creation, which is not always done "beautifully" ...two is the rendering, which doesn't always account for PDF-format discrepancies. But either way, I would still recommend that the interpretation of discrepancies in Evince should be the same as Adobe Reader and xpdf. (even though I'm a believer of creating data-files according to their definition as agreed) For further testing, you would proberly need to create a PDF that uses the non-embedded fonts AND is created directly, without using any form of PostScript. (I'll would suggest PDFLib - www.pdflib.com) -- Non-embedded standard fonts in PDF files are not displayed/rendered correctly https://bugs.launchpad.net/bugs/667752 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
