[Fwd: [pdftex] pdftex 1.40]
![](https://secure.gravatar.com/avatar/565476157eb3895a9c928ffce26d988d.jpg?s=120&d=mm&r=g)
Hi,
The next message probably also is interestering to a few of you that
are not subscribed to the pdftex list.
Best, Taco
-------- Original Message --------
Subject: [pdftex] pdftex 1.40
Date: Mon, 1 Jan 2007 17:56:59 +0100
From: Martin Schröder
![](https://secure.gravatar.com/avatar/d0e94fb08d4620cfbd2f8f59a7868637.jpg?s=120&d=mm&r=g)
On Jan 2, 2007, at 3:21 PM, Taco Hoekwater wrote:
Hi,
The next message probably also is interestering to a few of you that are not subscribed to the pdftex list.
Best, Taco
Taco and all other pdftex-developers, congratulations on getting version 1.40 ready for the new year! I had been using it since the first betas and never had any problems; it's great that you're going stable. Just one short remark for all those who may want to upgrade to this version: if you use opentype fonts, the .otf files have now to reside under TEXMF/fonts/opentype; right until the last beta, they were (only?) found under TEXMF/fonts/type1, but this is no longer the case. Apart from this, everything seems to be wonderfully stable. And now we all wait for luatex (or for luatools.lua so we can play around with it)... Best wishes Thomas
![](https://secure.gravatar.com/avatar/cedc4d83943006afe3994fb0a0455f82.jpg?s=120&d=mm&r=g)
On Tue, 2 Jan 2007, Taco Hoekwater wrote:
- draftmode: With \pdfdraftmode=1 or the commandline switch -draftmode pdfTeX doesn't write the output pdf and doesn't actually read any images, thus speeding up compilations when you know you need an extra run but don't care about the output, e.g. just to get the BibTeX references right
Hello, I'm thinking of "\doifnotmode{*last}{\pdfdraftmode=1}", but how do I ask for an additional imposition pass? Cheers and happy new year! Peter -- http://pmrb.free.fr/contact/
![](https://secure.gravatar.com/avatar/c5ae4f9aa0d3a9bd5376e92b322c3e50.jpg?s=120&d=mm&r=g)
On Tue, 2 Jan 2007, Peter Münster wrote:
On Tue, 2 Jan 2007, Taco Hoekwater wrote:
- draftmode: With \pdfdraftmode=1 or the commandline switch -draftmode pdfTeX doesn't write the output pdf and doesn't actually read any images, thus speeding up compilations when you know you need an extra run but don't care about the output, e.g. just to get the BibTeX references right
Hello, I'm thinking of "\doifnotmode{*last}{\pdfdraftmode=1}", but how do I ask for an additional imposition pass?
Interesting idea. I do not (yet) have pdf-1.40 so I can not test this. Does it work for "normal" cases? The modes manual says *last* This mode is set if the last run in a session is taking place. Normally this is not known in advance, unless one has asked for an additional imposition pass. which makes be believe that it will not work for normal cases. However, how about adding a switch to texexec, say --draft, which will run the document in draftmode until no more runs are needed, and will then run a final typesetting run without the draftmode. This may speed up the execution time for long documents significantly. Aditya
![](https://secure.gravatar.com/avatar/d8110a8a8a97be0803549ea5ee2e638b.jpg?s=120&d=mm&r=g)
2007/1/3, Aditya Mahajan
which makes be believe that it will not work for normal cases. However, how about adding a switch to texexec, say --draft, which will run the document in draftmode until no more runs are needed, and will then run a final typesetting run without the draftmode. This may speed up the execution time for long documents significantly.
It helps especially if your document produces a large pdf and/or includes many and/or large images. Best Martin
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
Martin wrote:
2007/1/3, Aditya Mahajan
: which makes be believe that it will not work for normal cases. However, how about adding a switch to texexec, say --draft, which will run the document in draftmode until no more runs are needed, and will then run a final typesetting run without the draftmode. This may speed up the execution time for long documents significantly.
It helps especially if your document produces a large pdf and/or includes many and/or large images.
and it probably also makes a difference when one uses many fonts (hz or so - less file access, no vector calculations, etc) 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 -----------------------------------------------------------------
![](https://secure.gravatar.com/avatar/b16ca16bcbc474a1ba15813999e212da.jpg?s=120&d=mm&r=g)
From the texexec man page:
--fast Typeset the document(s) as fast as possible without causing problems. --final Perform a final run without skipping anything. This option is typically used with --fast. So --fast --final could be the pair of switches to add. But I tried an experiment with mediocre results, using this test file: ====================== q.tex ================= \doifnotmode{*last}{\pdfdraftmode=1} \starttext \completecontent \chapter{A} \dorecurse{500}{\input tufte\par} \chapter{B} \dorecurse{400}{\input tufte\par} \chapter{C} \dorecurse{100}{\input tufte\par} \stoptext ============================================ I ran it with the attached Makefile, which produced this output: ctxtools --purge --all > /dev/null rm -f q.pdf texexec --verbose --fast --final q.tex > run.log Total runs : 4 (counted by grepping run.log for running: pdfetex) Draftmode runs: 3 (counted by grepping run.log for pdfdraftmode) TeXExec | runtime: 7.987485 Then I commented out the first line and reran it: ctxtools --purge --all > /dev/null rm -f q.pdf texexec --verbose --fast --final q.tex > run.log Total runs : 4 Draftmode runs: 0 (just to check) TeXExec | runtime: 8.307869 So the draftmode saves 4% in the runtime. But the fastest is to not use the draftmode and not use --final (which causes an extra run). Maybe I missing a trick, but the draftmode didn't save much time. I guess I should make the test file read in a few huge images? -Sanjoy .PHONY: runit clean runit: clean texexec --verbose --fast --final q.tex > run.log @echo -n "Total runs : " ; grep "running: pdfetex" run.log | wc -l @echo -n "Draftmode runs: " ; grep "pdfdraftmode enabled" run.log | wc -l @grep runtime: run.log clean: ctxtools --purge --all > /dev/null rm -f q.pdf
![](https://secure.gravatar.com/avatar/d8110a8a8a97be0803549ea5ee2e638b.jpg?s=120&d=mm&r=g)
2007/1/3, Sanjoy Mahajan
Maybe I missing a trick, but the draftmode didn't save much time. I guess I should make the test file read in a few huge images?
Yes. And if you then generate PDF 1.5 with object stream and compression, you can gain much. I have a test case which goes from 17.8s to 1.2s. On an AMD64@4200. Best Martin
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
Sanjoy Mahajan wrote:
From the texexec man page:
--fast Typeset the document(s) as fast as possible without causing problems.
--final Perform a final run without skipping anything. This option is typically used with --fast.
So --fast --final could be the pair of switches to add. But I tried an experiment with mediocre results, using this test file:
====================== q.tex ================= \doifnotmode{*last}{\pdfdraftmode=1} \starttext \completecontent
\chapter{A} \dorecurse{500}{\input tufte\par}
\chapter{B} \dorecurse{400}{\input tufte\par}
\chapter{C} \dorecurse{100}{\input tufte\par}
\stoptext ============================================
I ran it with the attached Makefile, which produced this output:
ctxtools --purge --all > /dev/null rm -f q.pdf texexec --verbose --fast --final q.tex > run.log Total runs : 4 (counted by grepping run.log for running: pdfetex) Draftmode runs: 3 (counted by grepping run.log for pdfdraftmode) TeXExec | runtime: 7.987485
Then I commented out the first line and reran it:
ctxtools --purge --all > /dev/null rm -f q.pdf texexec --verbose --fast --final q.tex > run.log Total runs : 4 Draftmode runs: 0 (just to check) TeXExec | runtime: 8.307869
So the draftmode saves 4% in the runtime. But the fastest is to not use the draftmode and not use --final (which causes an extra run). Maybe I missing a trick, but the draftmode didn't save much time. I guess I should make the test file read in a few huge images?
try bigger stuff, say a file with some 100 meg pictures and 25 fonts ; that's what draftmode is for (one of those ideas that popped up during eurotex 2006 at our usual pdftex dev chat). 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 -----------------------------------------------------------------
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
Aditya Mahajan wrote:
which makes be believe that it will not work for normal cases. However, how about adding a switch to texexec, say --draft, which will run the document in draftmode until no more runs are needed, and will then run a final typesetting run without the draftmode. This may speed up the execution time for long documents significantly.
indeed remind me to play with this feature 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 -----------------------------------------------------------------
![](https://secure.gravatar.com/avatar/b16ca16bcbc474a1ba15813999e212da.jpg?s=120&d=mm&r=g)
which makes be believe that it will not work for normal cases. However, how about adding a switch to texexec, say --draft, which will run the document in draftmode until no more runs are needed, and will then run a final typesetting run without the draftmode. This may speed up the execution time for long documents significantly.
indeed
remind me to play with this feature
When you do: --final could do what Aditya suggests by default (if making pdf). Then no need to add another switch to texexec. -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien)
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
Sanjoy Mahajan wrote:
which makes be believe that it will not work for normal cases. However, how about adding a switch to texexec, say --draft, which will run the document in draftmode until no more runs are needed, and will then run a final typesetting run without the draftmode. This may speed up the execution time for long documents significantly.
indeed
remind me to play with this feature
When you do: --final could do what Aditya suggests by default (if making pdf). Then no need to add another switch to texexec.
maybe later, when i feel comfortable enough with it; for the moment i added --draft 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 -----------------------------------------------------------------
![](https://secure.gravatar.com/avatar/c5ae4f9aa0d3a9bd5376e92b322c3e50.jpg?s=120&d=mm&r=g)
On Thu, 4 Jan 2007, Hans Hagen wrote:
Sanjoy Mahajan wrote:
which makes be believe that it will not work for normal cases. However, how about adding a switch to texexec, say --draft, which will run the document in draftmode until no more runs are needed, and will then run a final typesetting run without the draftmode. This may speed up the execution time for long documents significantly.
indeed
remind me to play with this feature
When you do: --final could do what Aditya suggests by default (if making pdf). Then no need to add another switch to texexec.
maybe later, when i feel comfortable enough with it; for the moment i added --draft
Great. Is there someplace where I can download pdftex binaries for windows? The sarovar site only has source code. Aditya
![](https://secure.gravatar.com/avatar/d8110a8a8a97be0803549ea5ee2e638b.jpg?s=120&d=mm&r=g)
2007/1/4, Aditya Mahajan
Is there someplace where I can download pdftex binaries for windows? The sarovar site only has source code.
Akira's W32TeX: http://www.fsci.fuk.kindai.ac.jp/~kakuto/win32-ptex/web2c75-e.html Or get the latest TexLive test image. Best Martin
![](https://secure.gravatar.com/avatar/c5ae4f9aa0d3a9bd5376e92b322c3e50.jpg?s=120&d=mm&r=g)
On Thu, 4 Jan 2007, Martin Schröder wrote:
2007/1/4, Aditya Mahajan
: Is there someplace where I can download pdftex binaries for windows? The sarovar site only has source code.
Akira's W32TeX: http://www.fsci.fuk.kindai.ac.jp/~kakuto/win32-ptex/web2c75-e.html
Thanks Aditya
![](https://secure.gravatar.com/avatar/386a116d129cdc597f2bb6210bbaff7a.jpg?s=120&d=mm&r=g)
On 1/2/07, Taco Hoekwater
Hi,
The next message probably also is interestering to a few of you that are not subscribed to the pdftex list. Oh, i'm one of the few... by the way http://www.logosrl.it/context/pdftex/1.40.0-2.2
Also, greping pdftex list I found http://pdfedit.petricek.net/pdfedit.index_e luigi.
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
luigi scarso wrote:
On 1/2/07, Taco Hoekwater
wrote: Hi,
The next message probably also is interestering to a few of you that are not subscribed to the pdftex list.
Oh, i'm one of the few...
the pdftex list nowadays is mostly a latex bug/support report list ; pdftex and luatex development have their own lists 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 -----------------------------------------------------------------
![](https://secure.gravatar.com/avatar/386a116d129cdc597f2bb6210bbaff7a.jpg?s=120&d=mm&r=g)
the pdftex list nowadays is mostly a latex bug/support report list ; pdftex and luatex development have their own lists
hmm I think this is the complete list. http://www.ntg.nl/mailman/listinfo/dev-context http://www.ntg.nl/mailman/listinfo/ntg-context http://www.ntg.nl/mailman/listinfo/ntg-pdftex http://tug.org/mailman/listinfo/pdftex http://www.ntg.nl/mailman/listinfo/dev-luatex
participants (8)
-
Aditya Mahajan
-
Hans Hagen
-
luigi scarso
-
Martin Schröder
-
Peter Münster
-
Sanjoy Mahajan
-
Taco Hoekwater
-
Thomas A. Schmitz