January 2007 - ntg-pdftex - NTG Mailing Lists

a wrapper for using pdftex as a library call
by Thanh Han The 31 Jan '07

31 Jan '07

Hi, I am working on a wrapper in C so that application can call pdftex via a library call. Can you please have a look at the proposed API and comment on it if you find a potential problem? I attached two files: test0.c: a minimal test file test1.c: the same file with comments Thanks, Thanh

2 2

[ pdftex-Bugs-722 ] PDF generation does not support VF fonts correctly
by noreply＠sarovar.org 31 Jan '07

31 Jan '07

Bugs item #722, was opened at 2007-01-24 08:56 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=722&group_id=106 Category: Fonts Group: v1.40.1 Status: Open Resolution: Accepted Priority: 5 Submitted By: Achim Blumensath (blume) Assigned to: The Thanh Han (hanthethanh) Summary: PDF generation does not support VF fonts correctly Initial Comment: I've a problem with using VF fonts in PDF mode (using pdftex 1.40.1, pdftex 1.20b does work correctly). When using glyphs that are composed of several other glyphs the various parts appear not at their correct position. The following example requires the MnSymbol and the MinionPro packages. \documentclass{minimal} \usepackage[T1]{fontenc} \usepackage[minionint]{MinionPro} \begin{document} $$\iint \quad \oint$$ \end{document} If you create a DVI and use dvips + ps2pdf the output is as expected (one double integral and one closed integral). If you use pdflatex to create a PDF file directly then the output is wrong. The double integral consists of just one integral sign and the closed integral consists of a circle followed by an integral sign. ---------------------------------------------------------------------- >Comment By: Achim Blumensath (blume) Date: 2007-01-31 08:41 Message: Logged In: YES user_id=4173 The patch seems to work fine. Thanks. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-29 19:46 Message: Logged In: YES user_id=710 I made some changes in pdftex. Your test file looks almost ok now :). Can you please try the patch to see whether it works for you. Since I don't have exactly the same fonts you used, it might be helpful if you try the patch with your tex setup. Thanks. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-26 10:55 Message: Logged In: YES user_id=710 indeed this is a bug of pdftex. I found the bug, should be fixed soon. ---------------------------------------------------------------------- Comment By: Achim Blumensath (blume) Date: 2007-01-26 08:47 Message: Logged In: YES user_id=4173 Sorry, I forgot to mention that I couldn't include the pfb for copyright reasons. You need the opticals version of MinionPro to get MinionPro-ItDisp.pfb. If you don't have the optical fonts the easiest workaround is to create a PFB with just one glyph named /integral of width 310 units. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-26 07:47 Message: Logged In: YES user_id=710 I still got: pdfTeX warning: pdftex (file MinionPro-ItDisp.pfb): cannot open Type 1 font file for reading I checked out the cvs version of MinionPro and run the makeall script as described in README-src, but still I didn't see MinionPro-ItDisp.pfb. ---------------------------------------------------------------------- Comment By: Achim Blumensath (blume) Date: 2007-01-26 06:21 Message: Logged In: YES user_id=4173 I've simplified the test case to plain TeX. The requested files are attached. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-01-25 14:01 Message: Logged In: YES user_id=421 Note that the -recorder cmdline switch also works quite well with kpathsea. :-) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-25 08:43 Message: Logged In: YES user_id=710 I tested the file again with the fonts you uploaded, but still I cannot reproduce the problem. I attached a small script that creates a list of all files opened by tex. Usage: unpack, put list-tex-files.vim under ~/vim and run: sh list-tex-files pdflatex testfile it will report the filename of the list, which can be used then to pack everything needed to rerun the job. You may want to review the list to remove a few files that are not relevant, for example the format. ---------------------------------------------------------------------- Comment By: Achim Blumensath (blume) Date: 2007-01-25 06:54 Message: Logged In: YES user_id=4173 In order to preproduce the bug you need the CVS version on MinionPro and perhaps also a recent version of the lcdf-typetools. The problem seems to be that the font MnSymbolFI10.vf refers again to a virtual font MinionPro-It-integral.vf. I've attached the corresponding VPL files. (I didn't have the time to create the requested PDF files. Will do so shortly.) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-24 18:52 Message: Logged In: YES user_id=710 I compiled the test file and got normal output (see attached screenshot). ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-01-24 14:56 Message: Logged In: YES user_id=421 Please attach the PDFs generated by ps2pdf and pdflatex, best generated with \pdfcompresslevel=0. And the log from pdflatex. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=722&group_id=106

1 0

[ pdftex-Bugs-722 ] PDF generation does not support VF fonts correctly
by noreply＠sarovar.org 29 Jan '07

29 Jan '07

Bugs item #722, was opened at 2007-01-24 08:56 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=722&group_id=106 Category: Fonts Group: v1.40.1 Status: Open Resolution: Accepted Priority: 5 Submitted By: Achim Blumensath (blume) Assigned to: The Thanh Han (hanthethanh) Summary: PDF generation does not support VF fonts correctly Initial Comment: I've a problem with using VF fonts in PDF mode (using pdftex 1.40.1, pdftex 1.20b does work correctly). When using glyphs that are composed of several other glyphs the various parts appear not at their correct position. The following example requires the MnSymbol and the MinionPro packages. \documentclass{minimal} \usepackage[T1]{fontenc} \usepackage[minionint]{MinionPro} \begin{document} $$\iint \quad \oint$$ \end{document} If you create a DVI and use dvips + ps2pdf the output is as expected (one double integral and one closed integral). If you use pdflatex to create a PDF file directly then the output is wrong. The double integral consists of just one integral sign and the closed integral consists of a circle followed by an integral sign. ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2007-01-29 19:46 Message: Logged In: YES user_id=710 I made some changes in pdftex. Your test file looks almost ok now :). Can you please try the patch to see whether it works for you. Since I don't have exactly the same fonts you used, it might be helpful if you try the patch with your tex setup. Thanks. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-26 10:55 Message: Logged In: YES user_id=710 indeed this is a bug of pdftex. I found the bug, should be fixed soon. ---------------------------------------------------------------------- Comment By: Achim Blumensath (blume) Date: 2007-01-26 08:47 Message: Logged In: YES user_id=4173 Sorry, I forgot to mention that I couldn't include the pfb for copyright reasons. You need the opticals version of MinionPro to get MinionPro-ItDisp.pfb. If you don't have the optical fonts the easiest workaround is to create a PFB with just one glyph named /integral of width 310 units. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-26 07:47 Message: Logged In: YES user_id=710 I still got: pdfTeX warning: pdftex (file MinionPro-ItDisp.pfb): cannot open Type 1 font file for reading I checked out the cvs version of MinionPro and run the makeall script as described in README-src, but still I didn't see MinionPro-ItDisp.pfb. ---------------------------------------------------------------------- Comment By: Achim Blumensath (blume) Date: 2007-01-26 06:21 Message: Logged In: YES user_id=4173 I've simplified the test case to plain TeX. The requested files are attached. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-01-25 14:01 Message: Logged In: YES user_id=421 Note that the -recorder cmdline switch also works quite well with kpathsea. :-) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-25 08:43 Message: Logged In: YES user_id=710 I tested the file again with the fonts you uploaded, but still I cannot reproduce the problem. I attached a small script that creates a list of all files opened by tex. Usage: unpack, put list-tex-files.vim under ~/vim and run: sh list-tex-files pdflatex testfile it will report the filename of the list, which can be used then to pack everything needed to rerun the job. You may want to review the list to remove a few files that are not relevant, for example the format. ---------------------------------------------------------------------- Comment By: Achim Blumensath (blume) Date: 2007-01-25 06:54 Message: Logged In: YES user_id=4173 In order to preproduce the bug you need the CVS version on MinionPro and perhaps also a recent version of the lcdf-typetools. The problem seems to be that the font MnSymbolFI10.vf refers again to a virtual font MinionPro-It-integral.vf. I've attached the corresponding VPL files. (I didn't have the time to create the requested PDF files. Will do so shortly.) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-24 18:52 Message: Logged In: YES user_id=710 I compiled the test file and got normal output (see attached screenshot). ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-01-24 14:56 Message: Logged In: YES user_id=421 Please attach the PDFs generated by ps2pdf and pdflatex, best generated with \pdfcompresslevel=0. And the log from pdflatex. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=722&group_id=106

1 0

Another valgrind warning.
by Taco Hoekwater 29 Jan '07

29 Jan '07

Hi, Valgrind said that 'Jump depends on uninitialized value' in this case as well: @ @<Output the cross-reference stream dictionary@>= .... print_ID(output_file_name); pdf_print_nl; pdf_begin_stream; for k := 0 to sys_obj_ptr do From other bits of code, it looks like the initial value of k should be one, not zero? Best, Taco

1 1

[ pdftex-Patches-726 ] in writezip.c replace deflateEnd() - deflateInit() by deflateReset()
by noreply＠sarovar.org 29 Jan '07

29 Jan '07

Patches item #726, was opened at 2007-01-28 14:57 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=726&group_id=106 >Category: Memory allocation >Group: v1.50.0 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Hartmut Henkel (hhenkel) >Assigned to: Martin Schröder (oneiros) Summary: in writezip.c replace deflateEnd() - deflateInit() by deflateReset() Initial Comment: This patch removes unnecessary free()/alloc() calls of zlib internal structures, reduces sys time. As before, \pdfcompresslevel change is still possible in mid document. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=726&group_id=106

1 0

[ pdftex-Patches-726 ] in writezip.c replace deflateEnd() - deflateInit() by deflateReset()
by noreply＠sarovar.org 28 Jan '07

28 Jan '07

Patches item #726, was opened at 2007-01-28 14:57 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=726&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Nobody (None) Summary: in writezip.c replace deflateEnd() - deflateInit() by deflateReset() Initial Comment: This patch removes unnecessary free()/alloc() calls of zlib internal structures, reduces sys time. As before, \pdfcompresslevel change is still possible in mid document. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=726&group_id=106

1 0

potential problem? (z_stream initalization)
by Taco Hoekwater 27 Jan '07

27 Jan '07

Hi, While debugging luatex, I ran into this warning from valgrind that seems to affect regular pdftex as well: ==4016== Conditional jump or move depends on uninitialised value(s) ==4016== at 0x80F851B: longest_match (deflate.c:1143) ==4016== by 0x80F9848: deflate_slow (deflate.c:1595) ==4016== by 0x80F8D98: deflate (deflate.c:790) ==4016== by 0x80DAE88: write_zip (writezip.c:58) ==4016== by 0x80729A2: pdf_flush (luatex1.c:10926) ==4016== by 0x80757BD: pdf_end_stream (luatex1.c:11068) ==4016== by 0x809AA68: zpdf_ship_out (luatex2.c:2057) ==4016== by 0x809C913: zship_out (luatex2.c:2770) ==4016== by 0x80A168B: handle_right_brace (luatex3.c:2431) ==4016== by 0x80A8D28: main_control (luatex3.c:2912) ==4016== by 0x805A796: main_body (luatexini.c:5910) ==4016== by 0x80AE866: main (luatexextra.c:378) (this is from luatex, but I get the same warnings for 1.40.1) It is a bit of a mystery to me what the right way to set up the z_stream is, so I thought I'd first ask if somebody else knows. Best, Taco

2 4

Re: [NTG-pdftex] subroutines declared as forward must be parameterless -- how to deal with this?
by Thanh Han The 27 Jan '07

27 Jan '07

On Sat, Jan 27, 2007 at 01:15:46PM +0100, Taco Hoekwater wrote: > Thanh Han The wrote: > >Hi, > > > >the web language requires that subroutines declared as > >forward cannot have any parameters. Is there a way to remove > >this restriction? > > If you are willing to tie yourself to web2c, then you can use > the @define construct in pdftex.defines instead of using a proper > forward declaration. I just tried that, it works fine. > > Otherwise, you will have to change the 'tangle' program, afaik. ha, I have also tried to workaround by using a wrapper C function. Your trick is nicer. Thanks, Thanh

1 0

subroutines declared as forward must be parameterless -- how to deal with this?
by Thanh Han The 27 Jan '07

27 Jan '07

Hi, the web language requires that subroutines declared as forward cannot have any parameters. Is there a way to remove this restriction? Thanh

2 1

Re: [NTG-pdftex] potential problem? (z_stream initalization)
by Thanh Han The 26 Jan '07

26 Jan '07

Hi, I get those warnings all the time too. No idea how to fix it, but they seem harmless. I set \pdfcompresslevel=0 to turn off those warnings :) Thanh On Fri, Jan 26, 2007 at 04:39:15PM +0100, Taco Hoekwater wrote: > Hi, > > While debugging luatex, I ran into this warning from valgrind that > seems to affect regular pdftex as well: > > ==4016== Conditional jump or move depends on uninitialised value(s) > ==4016== at 0x80F851B: longest_match (deflate.c:1143) > ==4016== by 0x80F9848: deflate_slow (deflate.c:1595) > ==4016== by 0x80F8D98: deflate (deflate.c:790) > ==4016== by 0x80DAE88: write_zip (writezip.c:58) > ==4016== by 0x80729A2: pdf_flush (luatex1.c:10926) > ==4016== by 0x80757BD: pdf_end_stream (luatex1.c:11068) > ==4016== by 0x809AA68: zpdf_ship_out (luatex2.c:2057) > ==4016== by 0x809C913: zship_out (luatex2.c:2770) > ==4016== by 0x80A168B: handle_right_brace (luatex3.c:2431) > ==4016== by 0x80A8D28: main_control (luatex3.c:2912) > ==4016== by 0x805A796: main_body (luatexini.c:5910) > ==4016== by 0x80AE866: main (luatexextra.c:378) > > (this is from luatex, but I get the same warnings for 1.40.1) > > It is a bit of a mystery to me what the right way to set up the > z_stream is, so I thought I'd first ask if somebody else knows. > > > Best, Taco > > > _______________________________________________ > ntg-pdftex mailing list > ntg-pdftex(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-pdftex

1 0