Hi, see the attached PS file. When running this through ps2pdf14, I get muurbloem:/tmp$ pdffonts type3-2.pdf name type emb sub uni object ID ------------------------------------ ------------ --- --- --- --------- [none] Type 3 yes no yes 11 0 PEMPHJ+BookAntiqua TrueType yes yes no 9 0 The output has a bitmap for o-double acute. When uncommenting the % before odblacute in the encoding vector and rerunning ps2pdf14, the PDF has no bitmaps, and I get muurbloem:/tmp$ pdffonts type3-2.pdf name type emb sub uni object ID ------------------------------------ ------------ --- --- --- --------- TSPQUC+BookAntiqua TrueType yes yes yes 9 0 The ps file uses BKANT.TTF (Book Antiqua), which is shipped by Microsoft with some products. I'll try to attach privately.
Created attachment 1421 [details] test case (prdouces bitmap glyph)
Hi, I can't attach bkant.ttf as its (c) microsoft. If you need it, please attach a comment where to send the file. Thanks! (and of course, many thanks for Ghostscript :-)
Created attachment 1422 [details] book antiqua ttf font.
Also see bug 688017, which has a similar symptom.
Hi, only now I notice that this is actually documented, "ps2pdf will sometimes convert text to high-resolution bitmapped fonts rather than to embedded outline fonts. This will occur when the PostScript file uses Type 3, CIDFontType 1, or CIDFontType 4 fonts, or Type 0 fonts that reference any of these; it may also occur in some cases if the input file uses fonts with non-standard encodings, or in some other rare cases. " I was wondering whether there are workarounds, whether a fix is planned, or how much work a fix would be. (Hey, is this eligible for the $1000 bughunt ? :-) I tried to changing the coding vector on the fly, but then other glyphs get bitmapped again.
See Comment #6 of the bug 688017. *** This bug has been marked as a duplicate of 688017 ***