Summary: | CID font render issues, specific to ghostscript | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | ant |
Component: | PDF Interpreter | Assignee: | Alex Cherepanov <alex> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | ||
Priority: | P4 | ||
Version: | 8.71 | ||
Hardware: | PC | ||
OS: | Linux | ||
Customer: | Word Size: | --- | |
Attachments: | example of the bad font rendering using CID -> ttf replacement (company logos and contact details removed). |
Description
ant
2011-03-02 05:22:44 UTC
The supplied example doesn't seem to be the same file as supplied for bug #691345 which makes it difficult to compare. However the first thing I would do is alter the (Unicode) to (Identity) in cidfmap. Note however that both work for me with the current version of GS and the file from bug #691345. My cidfmap entry is: /Arial << /FileType /TrueType /SubfontID 0 /Path (/windows/fonts/arial.ttf) /CSI [(Identity) 0] >> ; Which works apparently corectly with the only file I have to test against. Note; the use of a TrueType font on disk as a substitute for a missing CIDFont is not guaranteed (the two font technologies haev differences), though it does often produce acceptable results. Much better to embed the font in the first place. Hi Ken, I tested with your cidfmap line (but with the linux path to the font of course) and ghostscript 9.01 behaves correctly. /Arial << /FileType /TrueType /SubfontID 0 /Path (/usr/share/fonts/truetype/arial.ttf) /CSI [(Identity) 0] >> ; Now if only everyone on the internet was to check this bug for detail instead of the other million wrong versions out there! Thanks again, closed. |