Re: [NTG-pdftex] 1.20b/1.21a
Martin wrote:
I have problems compiling the latest sources out-of-tree, most likely because of changes to utils.c: The definition of ptexbanner has moved.
ptexbanner is defined in texmfmp.c. I think you probably did not replace texmfmp.c with the new one. Best regards, Akira
On 2004-11-19 06:01:01 +0900, Akira Kakuto wrote:
I think you probably did not replace texmfmp.c with the new one.
Yes, that did it. I'll upload a tarball tomorrow. Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
On 2004-11-18 23:48:08 +0100, Martin Schröder wrote:
I'll upload a tarball tomorrow.
1.20b-beta-20041119 is in p4 (#6534). Please check all open bugs at sarovar and close them if the beta fixes them. -------------------------------------------------------------- pdfTeX 3.141592-1.20b-beta-20041119 was released on 2004-11-19 -------------------------------------------------------------- - Fixed numerous bugs: 112, 113, 115, 116, 199, 210 - pdfTeX uses xpdf 3.00pl1 - pdfTeX uses libpng 1.2.8beta4, which should fix various png-related bugs. -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
On Fri, 19 Nov 2004, Martin Schröder wrote:
On 2004-11-18 23:48:08 +0100, Martin Schröder wrote:
-------------------------------------------------------------- pdfTeX 3.141592-1.20b-beta-20041119 was released on 2004-11-19 -------------------------------------------------------------- - Fixed numerous bugs: 112, 113, 115, 116, 199, 210
- pdfTeX uses xpdf 3.00pl1
- pdfTeX uses libpng 1.2.8beta4, which should fix various png-related bugs.
- The /Producer key now shows the real engine name, e. g. /Producer (pdfTeX-1.20b) ooops, not yet! something went wrong here. - The info line "output format initialized to PDF/DVI" isn't shown anymore, as this info wasn't reliable (bug 112). - Now the PDF-related statistics (PDF objects...) in the .log file is only shown in PDF output mode. It start with a line "PDF statistics:". - \pdfimageresolution is not limited to 2400 [dpi] anymore, can now be between 0 and 65535 [dpi]. Regards, Hartmut
On Fri, 19 Nov 2004, Hartmut Henkel wrote:
- The /Producer key now shows the real engine name, e. g. /Producer (pdfTeX-1.20b)
ooops, not yet! something went wrong here.
the files pdfetexdir/pdfetex.ch2 and pdfxtexdir/pdfxtex.ch2 are still the old ones. Regards, Hartmut
"Hartmut" == Hartmut Henkel
writes:
- \pdfimageresolution is not limited to 2400 [dpi] anymore, can now be between 0 and 65535 [dpi].
Hi Hartmut, what does \pdfimageresolution=0 mean? Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------
On Sat, 20 Nov 2004, Reinhard Kotucha wrote:
"Hartmut" == Hartmut Henkel
writes: - \pdfimageresolution is not limited to 2400 [dpi] anymore, can now be between 0 and 65535 [dpi].
Hi Hartmut, what does \pdfimageresolution=0 mean?
Ok. I tried it with a tweaked image. The PC did _not_ explode. :-) This is anyhow used only if there is no resolution info coming with an image. If then \pdfimageresolution=0, a resolution value 72 dpi hardcoded in pdftex.ch is used as last resort. When you say \pdfimageresolution=1, you obviously get a HUGE image possibly with some TeX dimension overflow warning. Regards, Hartmut
"Hartmut" == Hartmut Henkel
writes:
Ok. I tried it with a tweaked image. The PC did _not_ explode. :-) This is anyhow used only if there is no resolution info coming with an image. If then \pdfimageresolution=0, a resolution value 72 dpi hardcoded in pdftex.ch is used as last resort. When you say \pdfimageresolution=1, you obviously get a HUGE image possibly with some TeX dimension overflow warning.
So 0 is something magic here, like 10000 in TeX, which means infinity... I hope that it doesn't confuse people. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------
On Sat, 20 Nov 2004, Reinhard Kotucha wrote:
"Hartmut" == Hartmut Henkel
writes: Ok. I tried it with a tweaked image. The PC did _not_ explode. :-) This is anyhow used only if there is no resolution info coming with an image. If then \pdfimageresolution=0, a resolution value 72 dpi hardcoded in pdftex.ch is used as last resort. When you say \pdfimageresolution=1, you obviously get a HUGE image possibly with some TeX dimension overflow warning.
So 0 is something magic here, like 10000 in TeX, which means infinity... I hope that it doesn't confuse people.
Yes it's a special case. Would happen only in combination with special images missing a resolution info. And like this it has been there for long time. And you find it in the manual. Should be ok... But there is some chance of confusion with \pdfimageresolution itself as it's set most time outside the document (e. g. in the format). So if this changes, the document would get images with different sizes. Not very portable. Regards, Hartmut
On 2004-11-19 23:34:21 +0100, Hartmut Henkel wrote:
- The info line "output format initialized to PDF/DVI" isn't shown anymore, as this info wasn't reliable (bug 112).
That's unfortunate. Any idea how to fix this? Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
Martin Schröder wrote:
On 2004-11-19 23:34:21 +0100, Hartmut Henkel wrote:
- The info line "output format initialized to PDF/DVI" isn't shown anymore, as this info wasn't reliable (bug 112).
That's unfortunate. Any idea how to fix this?
does it need a fix, i found it an annoying message anyway, let's get rid of it Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
p4 describe -s 6569 Change 6569 by ms@artcom on 2004/11/22 16:50:19
pdftex: pdfTeX 1.20b-beta-20041122 Affected files ... ... //depot/Build/source.development/TeX/libs/xpdf/xpdf/GlobalParams.h#10 edit ... //depot/Build/source.development/TeX/texk/web2c/pdfetexdir/pdfetex.ch2#18 edit ... //depot/Build/source.development/TeX/texk/web2c/pdfetexdir/pdfetex.mk#25 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/ChangeLog#5 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/avl.h#3 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/epdf.h#15 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.ch#152 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.mk#31 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftoepdf.cc#50 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/writet1.c#20 edit ... //depot/Build/source.development/TeX/texk/web2c/pdfxtexdir/pdfxtex.ch2#11 edit Thanh, you have also opened pdftex.ch -- beware. Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
On Mon, 22 Nov 2004, Martin Schröder wrote:
p4 describe -s 6569 Change 6569 by ms@artcom on 2004/11/22 16:50:19
pdftex: pdfTeX 1.20b-beta-20041122
Have tried it on linux debian woody i686. Compiles out of the box. All tests on bug-112...bug-210 test files successful. Includes all van Schaik test PNGs ok. HZ even in combination with autoexpand works flawless AFAICT. Also Chinese with many .enc files seems to run smoothly. :-) Best Regards Hartmut
Change 6581 by ms@artcom on 2004/11/23 10:50:31 pdftex: 1.20b-rc0 Affected files ... ... //depot/Build/source.development/TeX/texk/web2c/pdfetexdir/pdfetex.mk#26 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/NEWS#70 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/README#23 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.ch#153 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.mk#32 edit ... //depot/Build/source.development/TeX/texk/web2c/pdfxtexdir/pdfxtex.mk#18 edit This only fixes some garbage in the .mk files (noticed by Thomas) and updates NEWS and README. It's also at sarovar: http://pdftex.sarovar.org/experimental/pdftex-1.20b-rc0.tar.bz2 Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
p4 describe -s 6595 Change 6595 by ms@artcom on 2004/11/24 18:07:58
pdftex: 1.20b-rc1 Affected files ... ... //depot/Build/source.development/TeX/libs/libpng/ANNOUNCE#11 edit ... //depot/Build/source.development/TeX/libs/libpng/CHANGES#11 edit ... //depot/Build/source.development/TeX/libs/libpng/INSTALL#11 edit ... //depot/Build/source.development/TeX/libs/libpng/KNOWNBUG#11 edit ... //depot/Build/source.development/TeX/libs/libpng/LICENSE#11 edit ... //depot/Build/source.development/TeX/libs/libpng/README#11 edit ... //depot/Build/source.development/TeX/libs/libpng/Y2KINFO#11 edit ... //depot/Build/source.development/TeX/libs/libpng/libpng.3#11 edit ... //depot/Build/source.development/TeX/libs/libpng/libpng.txt#11 edit ... //depot/Build/source.development/TeX/libs/libpng/libpngpf.3#11 edit ... //depot/Build/source.development/TeX/libs/libpng/png.5#11 edit ... //depot/Build/source.development/TeX/libs/libpng/png.c#15 edit ... //depot/Build/source.development/TeX/libs/libpng/png.h#15 edit ... //depot/Build/source.development/TeX/libs/libpng/pngconf.h#16 edit ... //depot/Build/source.development/TeX/libs/libpng/pngerror.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pnggccrd.c#11 edit ... //depot/Build/source.development/TeX/libs/libpng/pngget.c#11 edit ... //depot/Build/source.development/TeX/libs/libpng/pngmem.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pngpread.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pngread.c#11 edit ... //depot/Build/source.development/TeX/libs/libpng/pngrio.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngrtran.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pngrutil.c#11 edit ... //depot/Build/source.development/TeX/libs/libpng/pngset.c#11 edit ... //depot/Build/source.development/TeX/libs/libpng/pngtest.c#18 edit ... //depot/Build/source.development/TeX/libs/libpng/pngtrans.c#11 edit ... //depot/Build/source.development/TeX/libs/libpng/pngvcrd.c#11 edit ... //depot/Build/source.development/TeX/libs/libpng/pngwio.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngwrite.c#11 edit ... //depot/Build/source.development/TeX/libs/libpng/pngwtran.c#11 edit ... //depot/Build/source.development/TeX/libs/libpng/pngwutil.c#11 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/NEWS#71 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.ch#154 edit This updates libpng to 1.2.8rc1 It will be at sarovar soon. Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
p4 describe -s 6617 Change 6617 by ms@artcom on 2004/11/25 17:32:18
pdftex: 1.20b-rc2 Affected files ... ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/NEWS#72 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/mapfile.c#25 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.ch#155 edit mapfile.c has the latest patch from Hartmut tarball to appear at sarovar soon. Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
p4 describe -s 6625 Change 6625 by ms@artcom on 2004/11/26 12:07:37
pdftex: 1.20b-rc3 Affected files ... ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/NEWS#73 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/mapfile.c#26 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.ch#156 edit mapfile.c is the latest version from Thanh. tarball is at sarovar. Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
p4 describe -s 6638 Change 6638 by ms@artcom on 2004/11/29 12:52:38
pdftex: 1.20b-rc4 Affected files ... ... //depot/Build/source.development/TeX/libs/libpng/ANNOUNCE#12 edit ... //depot/Build/source.development/TeX/libs/libpng/CHANGES#12 edit ... //depot/Build/source.development/TeX/libs/libpng/INSTALL#12 edit ... //depot/Build/source.development/TeX/libs/libpng/KNOWNBUG#12 edit ... //depot/Build/source.development/TeX/libs/libpng/LICENSE#12 edit ... //depot/Build/source.development/TeX/libs/libpng/Makefile.in#6 edit ... //depot/Build/source.development/TeX/libs/libpng/README#12 edit ... //depot/Build/source.development/TeX/libs/libpng/Y2KINFO#12 edit ... //depot/Build/source.development/TeX/libs/libpng/example.c#10 edit ... //depot/Build/source.development/TeX/libs/libpng/libpng.3#12 edit ... //depot/Build/source.development/TeX/libs/libpng/libpng.txt#12 edit ... //depot/Build/source.development/TeX/libs/libpng/libpngpf.3#12 edit ... //depot/Build/source.development/TeX/libs/libpng/png.5#12 edit ... //depot/Build/source.development/TeX/libs/libpng/png.c#16 edit ... //depot/Build/source.development/TeX/libs/libpng/png.h#16 edit ... //depot/Build/source.development/TeX/libs/libpng/pngconf.h#17 edit ... //depot/Build/source.development/TeX/libs/libpng/pngerror.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pnggccrd.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pngget.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pngmem.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngpread.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngread.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pngrio.c#14 edit ... //depot/Build/source.development/TeX/libs/libpng/pngrtran.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngrutil.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pngset.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pngtest.c#19 edit ... //depot/Build/source.development/TeX/libs/libpng/pngtrans.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pngvcrd.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pngwio.c#14 edit ... //depot/Build/source.development/TeX/libs/libpng/pngwrite.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pngwtran.c#12 edit ... //depot/Build/source.development/TeX/libs/libpng/pngwutil.c#12 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/NEWS#74 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.ch#157 edit This updates libpng to rc3 tarball is at pdftex.sarovar.org and in the beta branch at http://sarovar.org/projects/pdftex/ -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
p4 describe -s 6651 Change 6651 by ms@artcom on 2004/12/09 16:48:46
pdftex: 1.20b-rc5 Affected files ... ... //depot/Build/source.development/TeX/libs/libpng/ANNOUNCE#13 edit ... //depot/Build/source.development/TeX/libs/libpng/CHANGES#13 edit ... //depot/Build/source.development/TeX/libs/libpng/KNOWNBUG#13 edit ... //depot/Build/source.development/TeX/libs/libpng/LICENSE#13 edit ... //depot/Build/source.development/TeX/libs/libpng/README#13 edit ... //depot/Build/source.development/TeX/libs/libpng/Y2KINFO#13 edit ... //depot/Build/source.development/TeX/libs/libpng/example.c#11 edit ... //depot/Build/source.development/TeX/libs/libpng/libpng.3#13 edit ... //depot/Build/source.development/TeX/libs/libpng/libpng.txt#13 edit ... //depot/Build/source.development/TeX/libs/libpng/libpngpf.3#13 edit ... //depot/Build/source.development/TeX/libs/libpng/png.5#13 edit ... //depot/Build/source.development/TeX/libs/libpng/png.c#17 edit ... //depot/Build/source.development/TeX/libs/libpng/png.h#17 edit ... //depot/Build/source.development/TeX/libs/libpng/pngconf.h#18 edit ... //depot/Build/source.development/TeX/libs/libpng/pngerror.c#14 edit ... //depot/Build/source.development/TeX/libs/libpng/pnggccrd.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngget.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngmem.c#14 edit ... //depot/Build/source.development/TeX/libs/libpng/pngpread.c#14 edit ... //depot/Build/source.development/TeX/libs/libpng/pngread.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngrio.c#15 edit ... //depot/Build/source.development/TeX/libs/libpng/pngrtran.c#14 edit ... //depot/Build/source.development/TeX/libs/libpng/pngrutil.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngset.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngtest.c#20 edit ... //depot/Build/source.development/TeX/libs/libpng/pngtrans.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngvcrd.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngwio.c#15 edit ... //depot/Build/source.development/TeX/libs/libpng/pngwrite.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngwtran.c#13 edit ... //depot/Build/source.development/TeX/libs/libpng/pngwutil.c#13 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/NEWS#75 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/mapfile.c#27 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.ch#158 edit This updates libpng to 1.2.8 proper and has patch-242c.tgz tarball is at pdftex.sarovar.org and in the beta branch at http://sarovar.org/projects/pdftex/ Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
When trying to use the GoudyIn.pfb font with its demo .tex file (all on CTAN), i get a segfault from pdftex. This font has very complicated glyphs, so that the alloc_array macro in writet1.c has to re-allocate memory; this normally never happens -- only with a few fonts as large as GoudyIn.pfb. Unfortunately these are also the nicer fonts that give an icing to pdftex... The problem with such a huge font is, that the xretalloc() function called by alloc_array moves the array base to another address, so any pointer relying on the former array place will now point into nirvana. And there seem to be a few pointers of this type :-( Thorougly fixing this weird re-allocation stuff in writet1.c looks like a complicated and risky thing. A q&d cure to get font GoudyIn.pfb and similar ones running is to once again increase T1_BUF_SIZE in writet1.c: #define T1_BUF_SIZE 0x8000 (Looks safe, and nowadays memory is cheap.) Then it works ok, but only as no re-allocation is needed. It will crash again when even larger glyphs appear, so it's definitely an ugly kludge. (In former times the alloc_array macro itself had a bug, but this has been fixed by Thanh.) What to do? Regards, Hartmut
On 2004-12-11 17:15:32 +0100, Hartmut Henkel wrote:
What to do?
As you say: increase the buf size now, and fix the re-allocation in the next version. Can we replace the calls to re-allocation calls that will fail with an error message in the meantime? Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
Hi Martin,
The problem is not that re-allocation fails, the problem is that it succeeds.
Sometimes (usually?) this means that the base memory address changes, and any
pointers that have been 'sampled' using the old address have now suddenly become
invalidated. There's no easy way to trap an 'error' in that (not in C, at least).
Hartmut's patch in all likelyhood solves the entire issue: there are
not that many 'potentially problematic' variables in writet1.c, so the
chance that he missed one is quite slim.
But: the original code is not written in a particularly stuctured manner,
so it is quite important that all patches get tested thoroughly. I've looked
at it for only one hour, and that's just not enough for me to be confident
about the patch in the general case. It works for me, though. :-)
Greetings. Taco
On Sat, 11 Dec 2004 23:32:14 +0100
Martin Schröder
On 2004-12-11 17:15:32 +0100, Hartmut Henkel wrote:
What to do?
As you say: increase the buf size now, and fix the re-allocation in the next version. Can we replace the calls to re-allocation calls that will fail with an error message in the meantime?
Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de _______________________________________________ ntg-pdftex mailing list ntg-pdftex@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-pdftex
Hartmut's patch in all likelyhood solves the entire issue: there are not that many 'potentially problematic' variables in writet1.c, so the chance that he missed one is quite slim.
Maybe, I totally miss the point, but since the patch sets T1_BUF_SIZE to 0x10 (which is a setting that shall trigger reallocations very often, I guess?), shouldn't it be sufficient to typeset a number of documents or a few large documents and preview and print? I mean, if T1_BUF_SIZE would have a value that makes reallocations happen seldomly, I'd agree that testing is not easy, but in this case!? Thomas
p4 describe -s 6664 Change 6664 by ms@artcom on 2004/12/20 17:34:46
pdftex: 1.20b-rc6 Affected files ... ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/NEWS#76 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.ch#159 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/writet1.c#21 edit This has the last patch from Hartmut for bug #250. If nothing serious happens I plan a release on Wednesday. tarball is at pdftex.sarovar.org and in the beta branch at http://sarovar.org/projects/pdftex/ Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
Change 6686 by ms@artcom on 2004/12/22 15:35:06 pdftex: 1.20b Affected files ... ... //depot/Build/source.development/TeX/libs/xpdf/xpdf/Gfx.cc#11 edit ... //depot/Build/source.development/TeX/libs/xpdf/xpdf/GfxState.cc#12 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/NEWS#77 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/README#24 edit ... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.ch#160 edit This has the last patch for xpdf (xpdf 3.00pl2). tarball is at pdftex.sarovar.org (in current) and at http://sarovar.org/projects/pdftex/ CTAN will follow soon. Best regards Martin PS: I've closed all open bugs; they should be fixed in 1.20b -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
On 2004-12-22 16:01:23 +0100, Martin Schröder wrote:
This has the last patch for xpdf (xpdf 3.00pl2).
It also has the last changes from Olaf. Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
On 2004-11-24 18:09:56 +0100, Martin Schröder wrote:
This updates libpng to 1.2.8rc1
Which is still buggy. rc3 is fixed; the final 1.2.8 is expected for 20041201, so I expect the final 1.20b for Friday. :-) Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
On Mon, Nov 22, 2004 at 04:51:47PM +0100, Martin Schroeder wrote:
p4 describe -s 6569 Change 6569 by ms@artcom on 2004/11/22 16:50:19
pdftex: pdfTeX 1.20b-beta-20041122
Affected files ...
.... //depot/Build/source.development/TeX/libs/xpdf/xpdf/GlobalParams.h#10 edit .... //depot/Build/source.development/TeX/texk/web2c/pdfetexdir/pdfetex.ch2#18 edit .... //depot/Build/source.development/TeX/texk/web2c/pdfetexdir/pdfetex.mk#25 edit .... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/ChangeLog#5 edit .... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/avl.h#3 edit .... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/epdf.h#15 edit .... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.ch#152 edit .... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftex.mk#31 edit .... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/pdftoepdf.cc#50 edit .... //depot/Build/source.development/TeX/texk/web2c/pdftexdir/writet1.c#20 edit .... //depot/Build/source.development/TeX/texk/web2c/pdfxtexdir/pdfxtex.ch2#11 edit
Thanh, you have also opened pdftex.ch -- beware.
Thanks. I did a `p4 revert' on the above files. I shall not touch 1.20b-* on p4 at all, unless some bug is discovered. Release 1.20b when you consider reasonable. Thanh
participants (8)
-
Akira Kakuto
-
Hans Hagen
-
Hartmut Henkel
-
Martin Schröder
-
Reinhard Kotucha
-
Taco Hoekwater
-
The Thanh Han
-
Thomas Esser