[pdftex] gs warning: Warning: Encoding not present.
hartmut_henkel at gmx.de
Sat Apr 14 23:03:34 CEST 2007
On Sat, 14 Apr 2007, Stephan Hennig wrote:
> when processing the output of pdflatex containing TT fonts with
> GhostScript it complains about a missing encoding.
> > >gswin32c -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile=palatinox2.pdf -fpalatinox.pdf
> > GPL Ghostscript 8.56 (2007-03-14)
> > Copyright (C) 2007 artofcode LLC, Benicia, CA. All rights reserved.
> > This software comes with NO WARRANTY: see the file PUBLIC for details.
> > Processing pages 1 through 1.
> > Page 1
> > **** Warning: Encoding not present.
> > **** This file had errors that were repaired or ignored.
> > **** The file was produced by:
> > **** >>>> MiKTeX pdfTeX-1.40.3 <<<<
> > **** Please notify the author of the software that produced this
> > **** file that it does not conform to Adobe's published PDF
> > **** specification.
> File palatinox.pdf has been generated with pdflatex 1.40.3 from MiKTeX
> 2.6 Beta 3 (code below).
> > >pdflatex -version
> > MiKTeX-pdfTeX 2.6.2644 (1.40.3) (MiKTeX 2.6 Beta 3)
> > Copyright (C) 1982 D. E. Knuth, (C) 1996-2006 Han The Thanh
> > TeX is a trademark of the American Mathematical Society.
> The same warning is raised with pdflatex 1.30.6 form MiKTeX 2.5 and with
> other TTFs. File palatinox2.pdf seems to be ok. And it's a warning
> only. Should I care about that?
it looks as if gs searches for the /Encoding key (see file pdf_font.ps
within gs sources) in the /Font object within the PDF file and doesn't
find it (it's optional according to the PDF Ref.). Maybe it should
better check the TTF font for the encoding, but it seems that this
doesn't happen. As an experiment: one gets rid of the gs warning if one
manipulates a fake
/Encoding << /Differences  >>
into the /Font object.
> % Needs package truetypemetrics from CTAN.
> % Activates TTF Palatino Linotype distributed with Windows XP.
> text 1234
More information about the pdftex