- ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-874 ] problem with writettf?
by noreply＠sarovar.org 12 Oct '07

12 Oct '07

Bugs item #874, was opened at 2007-10-11 14:34 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106 Category: Fonts Group: v1.40.5 Status: Open Resolution: None Priority: 5 Submitted By: Stefan Becuwe (sbecuwe) Assigned to: Hartmut Henkel (hhenkel) Summary: problem with writettf? Initial Comment: Hello I'm using texlive 2007 and encountered the following problem with a truetype font: [...] {/usr/local/apps/texlive-2007/texmf/fonts/enc/ttf2pk/ba se/T1-WGL4.enc}<Auto1-Light.ttfpdflatex: ../../../../texk/web2c/pdftexdir/writettf.c:848: prepend_subset_tags: Assertion `index > 0 && index < name_record_num && fd_cur->subset_tag != ((void *)0)' failed. Upgrading pdftex to 1.40.5 still produces the same error. My previous texlive version (2005 or 2006) didn't have that problem. Replacing Auto1-Light.ttf by another ttf, such as technicn.ttf, does not result in an error. So it's probably related to the Auto1-Light.ttf file itself, but it seems the behaviour of pdftex has changed over the years... Best regards Stefan ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2007-10-12 20:59 Message: Logged In: YES user_id=929 seems in the TTF 'name' table normally the name_id is the same number as the running entry index i. Then everything runs fine. But with the Auto1-Light font that's not the case: at i = 0 there is name_id = 1. So AFAICS the font file might be a little unusual but it's ok, and pdftex/luatex should be patched. Regards, Hartmut ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-10-12 13:36 Message: Logged In: YES user_id=929 ah the font file is in your testcase tar, thanks! ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-10-12 13:31 Message: Logged In: YES user_id=929 thanks a lot for the test, but the fact that it works after the patch suggests that actually your TT font is broken (not pdftex) -- which might even generate broken or non-standard PDF files, beware! Seems the index = 0 should never happen with a normal font. So it would help a lot to have your font for inspection. Regards, Hartmut ---------------------------------------------------------------------- Comment By: Stefan Becuwe (sbecuwe) Date: 2007-10-12 09:54 Message: Logged In: YES user_id=4723 Changing index > 0 into index >= 0 did solve the problem. I have attached anyway the minimal testcase (generated after the suggested patch). Thanks for solving this problem! Stefan ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-10-11 19:21 Message: Logged In: YES user_id=421 Can you create a minimal testcase and attach it here together with the font? systems/mkjobtexmf from CTAN might be helpful. ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-10-11 16:14 Message: Logged In: YES user_id=929 does it go away if you change in pdftex-1.40.5, writettf.c in function prepend_subset_tag() the line assert(index > 0... into assert(index >= 0...? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106

1 0

[\immediate]\pdfximage
by David Kastrup 12 Oct '07

12 Oct '07

Hi, in an application of ours, we have the situation that quite a number of graphics files are checked for their size and stuff, and then a decision is made whether to use them in the resulting PDF. If we do the checks using \pdfximage, the resulting file handle (and internal data structures) are kept open until the end of the TeX run, waiting to see whether actually a \pdfrefximage will ever occur. Bad. We actually run out of file handles on some platforms because of that. If we do the checks using \immediate\pdfximage, then the graphics file will be written out to the PDF even though it will never get displayed or used. Since probably only one of five files actually _is_ supposed to be printed, this will blow up the PDF completely unnecessarily. Any idea how to deal with this? How about something like [\immediate]\pdfcloseximage which makes PDFTeX forget all about a previously included file, freeing the resources? Or is there something I don't understand? -- David Kastrup

2 1

[ pdftex-Bugs-874 ] problem with writettf?
by noreply＠sarovar.org 12 Oct '07

12 Oct '07

Bugs item #874, was opened at 2007-10-11 14:34 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106 Category: Fonts Group: v1.40.5 Status: Open Resolution: None Priority: 5 Submitted By: Stefan Becuwe (sbecuwe) Assigned to: Hartmut Henkel (hhenkel) Summary: problem with writettf? Initial Comment: Hello I'm using texlive 2007 and encountered the following problem with a truetype font: [...] {/usr/local/apps/texlive-2007/texmf/fonts/enc/ttf2pk/ba se/T1-WGL4.enc}<Auto1-Light.ttfpdflatex: ../../../../texk/web2c/pdftexdir/writettf.c:848: prepend_subset_tags: Assertion `index > 0 && index < name_record_num && fd_cur->subset_tag != ((void *)0)' failed. Upgrading pdftex to 1.40.5 still produces the same error. My previous texlive version (2005 or 2006) didn't have that problem. Replacing Auto1-Light.ttf by another ttf, such as technicn.ttf, does not result in an error. So it's probably related to the Auto1-Light.ttf file itself, but it seems the behaviour of pdftex has changed over the years... Best regards Stefan ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2007-10-12 13:36 Message: Logged In: YES user_id=929 ah the font file is in your testcase tar, thanks! ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-10-12 13:31 Message: Logged In: YES user_id=929 thanks a lot for the test, but the fact that it works after the patch suggests that actually your TT font is broken (not pdftex) -- which might even generate broken or non-standard PDF files, beware! Seems the index = 0 should never happen with a normal font. So it would help a lot to have your font for inspection. Regards, Hartmut ---------------------------------------------------------------------- Comment By: Stefan Becuwe (sbecuwe) Date: 2007-10-12 09:54 Message: Logged In: YES user_id=4723 Changing index > 0 into index >= 0 did solve the problem. I have attached anyway the minimal testcase (generated after the suggested patch). Thanks for solving this problem! Stefan ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-10-11 19:21 Message: Logged In: YES user_id=421 Can you create a minimal testcase and attach it here together with the font? systems/mkjobtexmf from CTAN might be helpful. ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-10-11 16:14 Message: Logged In: YES user_id=929 does it go away if you change in pdftex-1.40.5, writettf.c in function prepend_subset_tag() the line assert(index > 0... into assert(index >= 0...? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106

1 0

[ pdftex-Bugs-874 ] problem with writettf?
by noreply＠sarovar.org 12 Oct '07

12 Oct '07

Bugs item #874, was opened at 2007-10-11 14:34 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106 Category: Fonts Group: v1.40.5 Status: Open Resolution: None Priority: 5 Submitted By: Stefan Becuwe (sbecuwe) Assigned to: Hartmut Henkel (hhenkel) Summary: problem with writettf? Initial Comment: Hello I'm using texlive 2007 and encountered the following problem with a truetype font: [...] {/usr/local/apps/texlive-2007/texmf/fonts/enc/ttf2pk/ba se/T1-WGL4.enc}<Auto1-Light.ttfpdflatex: ../../../../texk/web2c/pdftexdir/writettf.c:848: prepend_subset_tags: Assertion `index > 0 && index < name_record_num && fd_cur->subset_tag != ((void *)0)' failed. Upgrading pdftex to 1.40.5 still produces the same error. My previous texlive version (2005 or 2006) didn't have that problem. Replacing Auto1-Light.ttf by another ttf, such as technicn.ttf, does not result in an error. So it's probably related to the Auto1-Light.ttf file itself, but it seems the behaviour of pdftex has changed over the years... Best regards Stefan ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2007-10-12 13:31 Message: Logged In: YES user_id=929 thanks a lot for the test, but the fact that it works after the patch suggests that actually your TT font is broken (not pdftex) -- which might even generate broken or non-standard PDF files, beware! Seems the index = 0 should never happen with a normal font. So it would help a lot to have your font for inspection. Regards, Hartmut ---------------------------------------------------------------------- Comment By: Stefan Becuwe (sbecuwe) Date: 2007-10-12 09:54 Message: Logged In: YES user_id=4723 Changing index > 0 into index >= 0 did solve the problem. I have attached anyway the minimal testcase (generated after the suggested patch). Thanks for solving this problem! Stefan ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-10-11 19:21 Message: Logged In: YES user_id=421 Can you create a minimal testcase and attach it here together with the font? systems/mkjobtexmf from CTAN might be helpful. ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-10-11 16:14 Message: Logged In: YES user_id=929 does it go away if you change in pdftex-1.40.5, writettf.c in function prepend_subset_tag() the line assert(index > 0... into assert(index >= 0...? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106

1 0

[ pdftex-Bugs-874 ] problem with writettf?
by noreply＠sarovar.org 12 Oct '07

12 Oct '07

Bugs item #874, was opened at 2007-10-11 14:34 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106 Category: Fonts Group: v1.40.5 Status: Open Resolution: None Priority: 5 Submitted By: Stefan Becuwe (sbecuwe) Assigned to: Hartmut Henkel (hhenkel) Summary: problem with writettf? Initial Comment: Hello I'm using texlive 2007 and encountered the following problem with a truetype font: [...] {/usr/local/apps/texlive-2007/texmf/fonts/enc/ttf2pk/ba se/T1-WGL4.enc}<Auto1-Light.ttfpdflatex: ../../../../texk/web2c/pdftexdir/writettf.c:848: prepend_subset_tags: Assertion `index > 0 && index < name_record_num && fd_cur->subset_tag != ((void *)0)' failed. Upgrading pdftex to 1.40.5 still produces the same error. My previous texlive version (2005 or 2006) didn't have that problem. Replacing Auto1-Light.ttf by another ttf, such as technicn.ttf, does not result in an error. So it's probably related to the Auto1-Light.ttf file itself, but it seems the behaviour of pdftex has changed over the years... Best regards Stefan ---------------------------------------------------------------------- >Comment By: Stefan Becuwe (sbecuwe) Date: 2007-10-12 09:54 Message: Logged In: YES user_id=4723 Changing index > 0 into index >= 0 did solve the problem. I have attached anyway the minimal testcase (generated after the suggested patch). Thanks for solving this problem! Stefan ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-10-11 19:21 Message: Logged In: YES user_id=421 Can you create a minimal testcase and attach it here together with the font? systems/mkjobtexmf from CTAN might be helpful. ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-10-11 16:14 Message: Logged In: YES user_id=929 does it go away if you change in pdftex-1.40.5, writettf.c in function prepend_subset_tag() the line assert(index > 0... into assert(index >= 0...? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106

1 0

Docs for xpdf libraries or poppler?
by David Kastrup 11 Oct '07

11 Oct '07

Having cloned the source repository of poppler, I could not fail to notice that there is no API documentation that I could discern. Now PDFTeX obviously _has_ been able to make sense of the libraries. What source of information has been used for this? Key point is that I have to read some PDF files, process them at some rather shallow object level, and write out the results. So far, I have not even been able to figure out whether one of those libs would be suitable for that. Since PDFTeX does reading and writing of PDF (also of included PDF files), some basic facility would seem to be there? -- David Kastrup

2 3

[ pdftex-Bugs-874 ] problem with writettf?
by noreply＠sarovar.org 11 Oct '07

11 Oct '07

Bugs item #874, was opened at 2007-10-11 14:34 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106 Category: Fonts Group: v1.40.5 Status: Open Resolution: None Priority: 5 Submitted By: Stefan Becuwe (sbecuwe) Assigned to: Hartmut Henkel (hhenkel) Summary: problem with writettf? Initial Comment: Hello I'm using texlive 2007 and encountered the following problem with a truetype font: [...] {/usr/local/apps/texlive-2007/texmf/fonts/enc/ttf2pk/ba se/T1-WGL4.enc}<Auto1-Light.ttfpdflatex: ../../../../texk/web2c/pdftexdir/writettf.c:848: prepend_subset_tags: Assertion `index > 0 && index < name_record_num && fd_cur->subset_tag != ((void *)0)' failed. Upgrading pdftex to 1.40.5 still produces the same error. My previous texlive version (2005 or 2006) didn't have that problem. Replacing Auto1-Light.ttf by another ttf, such as technicn.ttf, does not result in an error. So it's probably related to the Auto1-Light.ttf file itself, but it seems the behaviour of pdftex has changed over the years... Best regards Stefan ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-10-11 19:21 Message: Logged In: YES user_id=421 Can you create a minimal testcase and attach it here together with the font? systems/mkjobtexmf from CTAN might be helpful. ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-10-11 16:14 Message: Logged In: YES user_id=929 does it go away if you change in pdftex-1.40.5, writettf.c in function prepend_subset_tag() the line assert(index > 0... into assert(index >= 0...? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106

1 0

[ pdftex-Bugs-874 ] problem with writettf?
by noreply＠sarovar.org 11 Oct '07

11 Oct '07

Bugs item #874, was opened at 2007-10-11 14:34 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106 Category: Fonts Group: v1.40.5 Status: Open Resolution: None Priority: 5 Submitted By: Stefan Becuwe (sbecuwe) Assigned to: Hartmut Henkel (hhenkel) Summary: problem with writettf? Initial Comment: Hello I'm using texlive 2007 and encountered the following problem with a truetype font: [...] {/usr/local/apps/texlive-2007/texmf/fonts/enc/ttf2pk/ba se/T1-WGL4.enc}<Auto1-Light.ttfpdflatex: ../../../../texk/web2c/pdftexdir/writettf.c:848: prepend_subset_tags: Assertion `index > 0 && index < name_record_num && fd_cur->subset_tag != ((void *)0)' failed. Upgrading pdftex to 1.40.5 still produces the same error. My previous texlive version (2005 or 2006) didn't have that problem. Replacing Auto1-Light.ttf by another ttf, such as technicn.ttf, does not result in an error. So it's probably related to the Auto1-Light.ttf file itself, but it seems the behaviour of pdftex has changed over the years... Best regards Stefan ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2007-10-11 16:14 Message: Logged In: YES user_id=929 does it go away if you change in pdftex-1.40.5, writettf.c in function prepend_subset_tag() the line assert(index > 0... into assert(index >= 0...? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106

1 0

[ pdftex-Bugs-874 ] problem with writettf?
by noreply＠sarovar.org 11 Oct '07

11 Oct '07

Bugs item #874, was opened at 2007-10-11 14:34 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106 Category: Fonts Group: v1.40.5 Status: Open Resolution: None Priority: 5 Submitted By: Stefan Becuwe (sbecuwe) Assigned to: Hartmut Henkel (hhenkel) Summary: problem with writettf? Initial Comment: Hello I'm using texlive 2007 and encountered the following problem with a truetype font: [...] {/usr/local/apps/texlive-2007/texmf/fonts/enc/ttf2pk/ba se/T1-WGL4.enc}<Auto1-Light.ttfpdflatex: ../../../../texk/web2c/pdftexdir/writettf.c:848: prepend_subset_tags: Assertion `index > 0 && index < name_record_num && fd_cur->subset_tag != ((void *)0)' failed. Upgrading pdftex to 1.40.5 still produces the same error. My previous texlive version (2005 or 2006) didn't have that problem. Replacing Auto1-Light.ttf by another ttf, such as technicn.ttf, does not result in an error. So it's probably related to the Auto1-Light.ttf file itself, but it seems the behaviour of pdftex has changed over the years... Best regards Stefan ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=874&group_id=106

1 0

increasing max_strings
by David Kastrup 10 Oct '07

10 Oct '07

Hi, because of exceeded TeX capacity, I increased the following limit in the source: svn diff Index: source/src/texk/web2c/tex.ch =================================================================== --- source/src/texk/web2c/tex.ch (Revision 241) +++ source/src/texk/web2c/tex.ch (Arbeitskopie) @@ -200,7 +200,7 @@ @y @d file_name_size == maxint @d ssup_error_line = 255 -@d ssup_max_strings == 262143 +@d ssup_max_strings == 500000 {Larger values than 65536 cause the arrays consume much more memory.} @d ssup_trie_opcode == 65535 @d ssup_trie_size == @"3FFFFF Does anybody know offhand whether I can expect bad effects? After all, why would the ssup-setting not be the maximum possible value? And if there was a reason to set it that way, what other things would I have to change? I ask because the job that was now able to compile produced a corrupt PDF. There can be a number of other reasons for that, but since the run is quite slow, I'd want to have this ruled out if possible. Thanks, -- David Kastrup, Kriemhildstr. 15, 44793 Bochum

2 2