Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.postscript > #199
| From | ken <ken@spamcop.net> |
|---|---|
| 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) |
| Date | 2011-05-14 15:57 +0100 |
| Message-ID | <MPG.2838a8bd456d44b698983d@usenet.plus.net> (permalink) |
| References | <752070ef-92c1-4d14-b97b-b0923a89ee9a@d1g2000yqm.googlegroups.com> <ddcd5686-723d-485e-a424-1db52310bdae@g12g2000yqd.googlegroups.com> <b349b104-e238-49dd-91fe-0deb38492f30@l18g2000yql.googlegroups.com> <937cveFsqU1@mid.individual.net> |
In article <937cveFsqU1@mid.individual.net>, h.blischke@acm.org says...
> > 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).
In fact I think its worse than that, the Encoding in the fonts isn't
even used, and consists of only one entry, the /.notdef anyway. All the
text appears to be rendered using glyphshow, which takes the glyph name
as an argument. Since the glyphs are all named with unhelpful numeric
names, eg:
/0 {<~!WN-%s*t@S^^pJ'+8>7h_=2r)pjW9_rr<&u!!)uu!<)rus8VTgs7
$'gnGiO`rs/?!"7UdFn:(]4
5EF_Es54FfJ-Z)S!WN-"GQ7~> 21 26 g} def
There is no obvious way to map the glyph names to anything else. Even if
there were, these fonts contain more than 256 glyphs, so they won't fit
into a single PDF type 3 font either.
As Helge rightly says, there is no way you are going to produce a
searchable PDF from this PostScript file.
Ken
Back to comp.lang.postscript | Previous | Next — Previous in thread | Find similar | Unroll thread
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) Peng Yu <pengyu.ut@gmail.com> - 2011-05-13 20:45 -0700
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) luser- -droog <mijoryx@yahoo.com> - 2011-05-13 22:41 -0700
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) Peng Yu <pengyu.ut@gmail.com> - 2011-05-14 05:36 -0700
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) Helge Blischke <h.blischke@acm.org> - 2011-05-14 15:04 +0200
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) John Reiser <jreiserfl@comcast.net> - 2011-05-14 07:53 -0700
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) ken <ken@spamcop.net> - 2011-05-14 15:57 +0100
csiph-web