Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!newsfeed.kamp.net!newsfeed.kamp.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Helge Blischke Newsgroups: comp.lang.postscript Subject: Re: How to convert this ps file to a pdf file w/ searchable text? (pkfix-helper: No Type 3 fonts were encountered in the input file) Followup-To: comp.lang.postscript Date: Sat, 14 May 2011 15:04:45 +0200 Lines: 32 Message-ID: <937cveFsqU1@mid.individual.net> References: <752070ef-92c1-4d14-b97b-b0923a89ee9a@d1g2000yqm.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Trace: individual.net VmZRL0D4tZ60a9wBymb13QOIEniXYoDiEOYit+vaWKrLklj6pf Cancel-Lock: sha1:v3fg0QiZ3Fp6yOWWnKnoM7P/d54= User-Agent: KNode/0.99.01 Xref: x330-a1.tempe.blueboxinc.net comp.lang.postscript:197 Peng Yu wrote: > On May 14, 12:41 am, luser- -droog wrote: >> On May 13, 10:45 pm, Peng  Yu wrote: >> >> > I try to use pkfix-helper to fix the pdf and then run ps2pdf on it. >> > But I get the following error. Could you please let me know if there >> > is any other way to generate a searchable pdf file? >> >> > $pkfix-helper 0375.ps >> > Reading 0375.ps ... done. >> > Number of Type 3 fonts encountered: 0 >> > pkfix-helper: No Type 3 fonts were encountered in the input file >> >> That looks more like a "nothing to do" message than an "error" >> per se. If we could see some of the postscript, ... > > I forgot post the postscript. Here is it. > > http://books.nips.cc/papers/files/nips01/0375.ps.gz The PostScript file has been produced by a (?) DjVu application, and id *does* contain Type3 fonts the glyphs of which are bitmaps. But the file is by no means DSC compliant, so that is probably why the pkfix-helper complains. And, as the Type3 fonts in this document do not provide a proper encoding array, the PDF is de facto not searchable (the converted text looks like garbage). Helge