January 2007 - ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-721 ] Missing /Font object of PK file not found
by noreply＠sarovar.org 24 Jan '07

24 Jan '07

Bugs item #721, was opened at 2007-01-23 21:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=721&group_id=106 Category: Fonts Group: v1.40.1 Status: Open >Resolution: Accepted >Priority: 7 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Hartmut Henkel (hhenkel) Summary: Missing /Font object of PK file not found Initial Comment: There are several cases, the buggy one is no. 3. See test files test1...4.tex in the attached file. 1. No TFM file found in the 1st place. ---> No TeX font will be started. Ok. See test1.tex. 2. TFM file found, map entry existing, but no PFB font file in map line ---> "pdfTeX warning: pdftex: font `CMR' is not a standard font; I suppose it is available to your PDF viewer then". Ok. See test2.tex. 3. TFM file found, no map entry, and no PK font available. ---> "pdfTeX warning: pdftex (file mf-nonexist): Font mf-nonexist at 600 not found". Not ok. See test3.tex. Here a /Font object is referenced, which is not existing, rendering the resulting PDF file buggy. There should be either pdftex_fail() or or at least a /Font object with a dummy /FontDescriptor object should be created (the latter filled with defaults from the TFM file), and the same warning should be given as in case 4 below, since these cases are similar: fontfile expected, but not available. 4. TFM file found, map entry with PFB font file existing, but no PFB font file found. ---> "pdfTeX warning: pdftex (file t1-nonexist.pfb): cannot open Type 1 font file for reading". /FontDescriptor without /FontFile, correct. Ok. See test4.tex. Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=721&group_id=106

1 0

Unknown font tag 'F42'
by Hartmut Henkel 23 Jan '07

23 Jan '07

Hi, when viewing english live.pdf from TeX Live 2007 inst 070123 by xpdf, i get quite a few of these: Error: font resource is not a dictionary Error: Unknown font tag 'F42' Error: font resource is not a dictionary Error: Unknown font tag 'F42' Error: font resource is not a dictionary Error: Unknown font tag 'F42' Error: Unknown font tag 'F42' No idea why. And why especially 42? :-) Creator: LaTeX with hyperref package Producer: pdfTeX-1.40.1 CreationDate: Mon Jan 22 00:18:24 2007 ModDate: Mon Jan 22 00:18:24 2007 Regards, Hartmut

4 10

[ pdftex-Bugs-721 ] Missing /Font object of PK file not found
by noreply＠sarovar.org 23 Jan '07

23 Jan '07

Bugs item #721, was opened at 2007-01-23 21:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=721&group_id=106 Category: Fonts Group: v1.40.1 Status: Open Resolution: None Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Hartmut Henkel (hhenkel) Summary: Missing /Font object of PK file not found Initial Comment: There are several cases, the buggy one is no. 3. See test files test1...4.tex in the attached file. 1. No TFM file found in the 1st place. ---> No TeX font will be started. Ok. See test1.tex. 2. TFM file found, map entry existing, but no PFB font file in map line ---> "pdfTeX warning: pdftex: font `CMR' is not a standard font; I suppose it is available to your PDF viewer then". Ok. See test2.tex. 3. TFM file found, no map entry, and no PK font available. ---> "pdfTeX warning: pdftex (file mf-nonexist): Font mf-nonexist at 600 not found". Not ok. See test3.tex. Here a /Font object is referenced, which is not existing, rendering the resulting PDF file buggy. There should be either pdftex_fail() or or at least a /Font object with a dummy /FontDescriptor object should be created (the latter filled with defaults from the TFM file), and the same warning should be given as in case 4 below, since these cases are similar: fontfile expected, but not available. 4. TFM file found, map entry with PFB font file existing, but no PFB font file found. ---> "pdfTeX warning: pdftex (file t1-nonexist.pfb): cannot open Type 1 font file for reading". /FontDescriptor without /FontFile, correct. Ok. See test4.tex. Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=721&group_id=106

1 0

Re: [NTG-pdftex] [NTG-context] pdfetex 1.40.1 + ghosscript problem?
by Thanh Han The 19 Jan '07

19 Jan '07

Hi, I tried the test file from Hartmut with all pdf browsers that I have and didn't get any warning. Can someone verify whether the same file compiled with pdftex 1.30.6 caused any warnings with gs? Anyway, fwiw, pdf spec has been improved a lot to clarify how truetype fonts are treated by adobe viewers. See p399, section "Encodings for TrueType Fonts". The current implementation was done using a trial-and-error approach, since that time the (old) pdf spec didn't say how TTF are treated. We can change pdftex to conform the spec (not a big change). But this may have some big impact on backward compability. Thanh On Fri, Jan 19, 2007 at 01:46:33AM +0100, Hartmut Henkel wrote: > On Fri, 19 Jan 2007, Hartmut Henkel wrote: > > > On Fri, 19 Jan 2007, Martin Schr�der wrote: > > > > > 2007/1/18, Michal Kvasnicka <quasar(a)econ.muni.cz>: > > > > Excuse me this off-topic, I don't know where should I ask. > > > > > > The pdftex mailing list would be a better place. See > > > http://www.pdftex.org/README > > > > > > [...] > > > > > > > Can anybody tell me what's wrong, and if there is a ghostscript > > > > version capable to view the output of pdftex 1.40.1? Without it it > > > > is useless for me. :-( > > > > > > I can view sample2e.pdf or the pdftex manual fine with gs 8.54. > > > > e. g. when i run this test file through pdftex-1.40.1 > > > > %$Id: test4.tex,v 1.3 2006/01/06 20:24:10 hahe Exp hahe $ > > \pdfcompresslevel=0 > > \nopagenumbers > > \pdfmapline{qtmr <8r.enc <qtmr.ttf} > > ok, this <8r.enc is the wrong encoding for this, so it's not surprising > that glyphs in this test file PDF come out wrongly. > > > \font\qtmr qtmr at 10pt > > \pdffontexpand\qtmr 30 30 5 autoexpand > > \pdfadjustspacing=2 > > \qtmr > > > > \input tufte > > \input tufte > > \input tufte > > \input tufte > > > > \bye > > > > then gs 8.54 tells "**** Warning: Encoding not present." But it looks > > ok. Could there be anything missing inside the embedded TTF font? > > Would this warning go away if one uses the right encoding vector? > > Regards, Hartmut > _______________________________________________ > ntg-pdftex mailing list > ntg-pdftex(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-pdftex

1 0

Re: [NTG-pdftex] [NTG-context] pdfetex 1.40.1 + ghosscript problem?
by Hartmut Henkel 19 Jan '07

19 Jan '07

Hi Thanh, On Fri, 19 Jan 2007, Martin Schröder wrote: > 2007/1/18, Michal Kvasnicka <quasar(a)econ.muni.cz>: > > Excuse me this off-topic, I don't know where should I ask. > > The pdftex mailing list would be a better place. See > http://www.pdftex.org/README > > [...] > > > Can anybody tell me what's wrong, and if there is a ghostscript > > version capable to view the output of pdftex 1.40.1? Without it it > > is useless for me. :-( > > I can view sample2e.pdf or the pdftex manual fine with gs 8.54. e. g. when i run this test file through pdftex-1.40.1 %$Id: test4.tex,v 1.3 2006/01/06 20:24:10 hahe Exp hahe $ \pdfcompresslevel=0 \nopagenumbers \pdfmapline{qtmr <8r.enc <qtmr.ttf} \font\qtmr qtmr at 10pt \pdffontexpand\qtmr 30 30 5 autoexpand \pdfadjustspacing=2 \qtmr \input tufte \input tufte \input tufte \input tufte \bye then gs 8.54 tells "**** Warning: Encoding not present." But it looks ok. Could there be anything missing inside the embedded TTF font? Regards, Hartmut

4 5

pdftex libc problem with x64_86 in tex-live 070117-inst
by Hartmut Henkel 17 Jan '07

17 Jan '07

Hi, do you have any clue what this fatal error means (similar also outside gdb): (/usr/local/texlive/2007/texmf-dist/tex/latex/microtype/microtype.sty (/usr/local/texlive/2007/texmf-dist/tex/latex/graphics/keyval.sty) (/usr/local/texlive/2007/texmf-dist/tex/latex/microtype/microtype.cfg/usr/local/texlive/2007/bin/x86_64-linux/pdflatex: relocation error: /usr/local/texlive/2007/bin/x86_64-linux/pdflatex: symbol regexec, version GLIBC_2.3.4 not defined in file libc.so.6 with link time reference Program exited with code 0177. (gdb) Regards, Hartmut

2 2

Re: [NTG-pdftex] /Font resources must be indirect?
by Thanh Han The 17 Jan '07

17 Jan '07

> On Tue, 16 Jan 2007, Martin Schr�der wrote: > > > Hi, copyFontResources in pdftoepdf.cc requires the fonts to be > > specified indirectly in a font resource dictionary. Why? I cannot recall the reason for this. Maybe it was not allowed in pdf-1.2 or ealier (couldn't find a pdf spec older than 1.3 to verify this), or this was just my assumption. Thanh

1 0

/Font resources must be indirect?
by Martin Schröder 16 Jan '07

16 Jan '07

Hi, copyFontResources in pdftoepdf.cc requires the fonts to be specified indirectly in a font resource dictionary. Why? Background: I've got a pdf (from http://www.stillhq.com/pdfdb/000623/info.html) that directly includes the font dictionaries in the font resource dictionary, and pdftex fails while including it. kpdf and AR7 display the file without problems, but gs 8.54 barfs. Best Martin

2 1

manual update
by Paweł Jackowski 11 Jan '07

11 Jan '07

Hi, I've updated the manual with \pdfcolorstackinit \pdfcolorstack \pdfsetmatrix \pdfsave \pdfrestore on the base of Heiko's patch note. Check welcome. -- Pawe/l Jackowski P.Jackowski(a)gust.org.pl

1 0

[ pdftex-Bugs-719 ] few buglets in build.sh
by noreply＠sarovar.org 07 Jan '07

07 Jan '07

Bugs item #719, was opened at 2007-01-02 04:39 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=719&group_id=106 Category: Build process Group: v1.40.0 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Sanjoy Mahajan (sanjoy) Assigned to: Martin Schröder (oneiros) Summary: few buglets in build.sh Initial Comment: Just compiled 1.40.0 using build.sh. I had to make a few changes to get it to run on my system (Ubuntu 6.10, i386). The purpose of the chunks in the attached diff: 1. The JOBS variable wasn't used, so I changed its name be descriptive for parallel builds, and used it (and a related load variable) in the line that appends to the MAKE variable. Also, without the necessary double quotes around that line, the rest of the line after $MAKE is interpreted as a command rather than as stuff to append to MAKE (run build.sh with "--parallel" to see the problem). I used the short option names for make, to keep the line within 80 chars. 2. "-a build" is an (incomplete) AND statement, rather than a test for the "build" directory existing. The test should be "-e build" to check for existence. 3. Brace expansion is suboptimal in sh and not very portable to different reimplementations of sh. According to the bash man page: "Brace expansion introduces a slight incompatibility with historical versions of sh. sh does not treat opening or closing braces specially when they appear as part of a word, and preserves them in the output. Bash removes braces from words as a consequence of brace expansion. For example, a word entered to sh as file{1,2} appears identically in the output." I don't know the full story, but the fake sh on my system (actually 'dash') doesn't do brace expansion at all. And if the bash man page is right, even if it did the expansion, it wouldn't help since build.sh uses braces in the middle of a word. So I rewrote the two uses of brace expansion to avoid it. The resulting "build.sh --parallel" worked fine in my limited tests. It still complained that it couldn't find the texmf tree, but I figure that's okay since pdftex'll eventually (I hope) use kpathsea and texmf.cnf. -Sanjoy ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-01-07 22:41 Message: Logged In: YES user_id=421 Thanks. I'll include your changes in the next version. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=719&group_id=106

1 0