Chris, Till, thanks for putting me on track. I get the picture more clearly now. Although, I am a bit in the dark how the CIDFonts turn up. To my understanding the PDF produced for printing can't contain CIDFonts, since (as Chris explained) they are an exclusive PostScript construct. So, it must be the `ps2write` filter creating PostScript level 3 ad-hoc that introduces the CIDFonts along the way. Am I right about that?
Till, the workaround for PDF printing you propose is perfectly valid of course, were it not that I am developing a cups-pdf like solution myself, and I am looking for a way to get the PDF, meant for printing, streamed directly into my CUPS backend. How can I prevent conversion of the PDF print stream to PostScript? As you applied a patch to cups-pdf to make it accept PDF as input, can you please give me some pointers? (Should I use a special PPD format for that? My CUPS backend is currently tied to a printer configured with the ghostpdf.ppd) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/942866 Title: Ubuntu 11.10: printing to PDF produces unsearchable PDF (contrary to 10.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-pdf/+bug/942866/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
