[Fwd: [pdftex] pdftex 1.40]

[Fwd: [pdftex] pdftex 1.40]

[Taco Hoekwater]

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 <martin@oneiros.de>
To: PDF-TeX mailing list <pdftex@tug.org>

http://sarovar.org/download.php/1139/pdftex-1.40.0.tar.bz2
http://sarovar.org/download.php/1140/pdftex-1.40.0.tgz
http://sarovar.org/download.php/1141/pdftex-1.40.0.zip
http://sarovar.org/download.php/1142/pdftex-1.30.6-1.40.0.diff.gz

The pdfTeX team is happy to announce the release of a new stable version:

===========================================================================
                                pdfTeX 1.40.0
===========================================================================

This is the announcement of pdfTeX 1.40.0, an extended version of TeX that
can create PDF directly from TeX source files and enhance the result of TeX
typesetting with the help of PDF.

===========================================================================
   Main changes of pdfTeX 1.40.0
===========================================================================

- pdfetex (as a separate binary/program) is gone; all extensions are now in
   pdftex. The make files still know about the target pdfetex, but it's just
   a copy of pdftex
- The sources of TeX, eTeX and pdfTeX have been merged into one file
   pdftex.web and one change file pdftex.ch. The sources of TeX and eTeX
   distributed are just there for reference
- New features:
   - pdfTeX can now generate PDF 1.5 object streams, which leads to smaller
     PDFs. This is controlled by setting \pdfobjcompresslevel to a value >0
     (3 compress everything, 2 don't compress /Info, 1 also don't compress
     embedded PDFs) and works only with PDF >=1.5
   - pdfTeX now supports another image file format: JBIG2 files (.jbig2)
   - the memory allocated for objects and destination names now grows
     dynamically
   - pdfTeX now generates smaller PDFs since for char positioning the width
     of chars (/Widths) is stored with more precision and so the chars must
     rarely be positioned separately
   - the PK resolution is now taken from the "pk_dpi" parameter in texmf.cnf
     if it has not been set in the format file or by the user
   - pdfTeX now removes the generated pdf in case of a fatal error
   - pdfTeX now sets /ModDate and /Trapped in the InfoDict by default (the
     values can be overridden with \pdfinfo)
   - the format of warnings and errors issued by pdfTeX has been changed and
     unified
   - the output of -version has been extended and now includes information
     about the libraries actually used, which can be handy when using shared
     libraries
   - rules and their positioning on the page are now inside a qQ group
- New primitives:
   - pdfTeX can now handle colourstacks.
     - \pdfcolorstackinit
       A stack is initialized by \pdfcolorstackinit. It expands to the
       number of the new stack. The common case, the traditinal color stack
       is already initialized as first stack: \pdfcolorstackinit page direct
       {0 g 0 G} The keyword "page" means that this stack is page based. At
       the start of the new page, the current stack value is automatically
       set.
     - \pdfcolorstack
       \pdfcolorstack <stack number> push {<new color>}
       pushes the current value on the stack and sets the <new color>.
       \pdfcolorstack <stack number> pop
       pops and sets the current stack value.
       \pdfcolorstack <stack number> current
       sets the current stack value without changing the stack. This is
       useful for stacks that are initialized without keyword "page".  Thus
       the page start setting can be set manually.
       \pdfcolorstack <stack number> set {<new color>}
       The current value is set to <new color>.
   - Transformation matrices can now be manipulated more cleanly:
     Currently matrix changes are done and hidden inside \pdfliteral nodes;
     pdfTeX doesn't parse its contents and does not know the new settings of
     the transform matrix. Thus the new primitives to save pdfTeX from
     parsing \pdfliteral contents and to notify pdfTeX about matrix changes
     to use them in calculating link and anchor positions.
     - \pdfsetmatrix{<a> <b> <c> <d>}
       is the equivalent to \pdfliteral{<a> <b> <c> <d> 0 0 cm}
     - \pdfsave is the equivalent to \pdfliteral{q}
     - \pdfrestore is the equivalent to \pdfliteral{Q}
   - \pdfprimitive\TeX-primitive executes the original \TeX-primitive even
     if the command has been redefined since. E.g.
       \let\relax\undefined\pdfprimitive\relax
     expands to \relax.
     \ifpdfprimitive\TeX-primitive is true if \TeX-primitive has its
     original meaning
   - \ifpdfabsnum and \ifpdfabsdim are like \ifnum and \ifdim, but don't
     care about negative numbers
   - shell escape: if the first character of a filename for \openin,
     \openout \input is a pipe symbol (|), the filename is assumed to be a
     request for a pipe to a command line that is given in the rest of the
     filename
   - 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
   - \pdfpxdimen (introduced in 1.30) is now a real dimension parameter. It
     allows one base dimensions on pixels. 1px defaults to 1bp (or 72dpi),
     but can be changed with the \pdfpxdimen primitive:
       \pdfpxdimen=1in % 1 dpi
       \divide\pdfpxdimen by 96 % 96 dpi
       \hsize=1200px
     Now \hsize is (1in/96)*1200
   - \pdflastlink returns the object number of the last \pdfstartlink
   - \pdfsavepos now works in DVI mode
- Fonts:
   - support for subfonts: This creates all needed map entries for subfonts
     automatically and handles Unicode mappings
   - ToUnicode entries for Type1 fonts (patch 580)
- HZ:
   - added patch 462: HZ font expansion in autoexpand mode now produces
     smaller pdf files, as it works by modififying the text matrix for
     single fonts instead of embedding many expanded font versions.
     Therefore HZ now can be used also for TrueType fonts and even for
     non-embedded fonts (e.g.  Times-Roman)
- Bugfixes:
   - the PDF statistics in the log are now correct
   - added JFIF detection patch to writejpg.c (bug 548)
   - bugfix: invalid pdf created if font name contains space (509)
   - bugfix: truetype OS/2 v3 fonts (594)
   - bugfix: Type1C (CFF) fonts of embedded pdfs didn't get replaced

For complete release notes see http://www.pdftex.org/NEWS

===========================================================================
   Legal notice / license
===========================================================================

pdfTeX is copyright (c) 1996-2007 Han The Thanh, <thanh@pdftex.org>

pdfTeX is free software; you can redistribute it and/or modify it under the
terms of the GNU General Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your option) any later
version.

For a complete README (with a full discussion of the license)
please look at http://www.pdftex.org/README

===========================================================================
   The files / installation
===========================================================================

You should first try to get a new version of pdfTeX through your
distribution.

If you want to compile it yourself, have a look at http://www.pdftex.org --
there you can find links to the pdfTeX sources on CTAN. And some useful
documentation.

===========================================================================
   Mailing lists / web pages:
===========================================================================

   Mailing list:
     http://tug.org/mailman/listinfo/pdftex

   Related web pages:
     http://www.pdftex.org
     http://sarovar.org/projects/pdftex/
     http://www.tug.org/tex-live/
     http://www.tug.org/tetex/
     http://www.tex.ac.uk/cgi-bin/texfaq2html?introduction=yes
     http://www.dante.de/
     http://tug.org/
     http://www.pragma-ade.com/

Have fun and a happy new year!

Martin Schröder (martin@pdftex.org) for the pdfTeX team, January 2007
_______________________________________________
pdftex mailing list
pdftex@tug.org
http://tug.org/mailman/listinfo/pdftex

Re: [Fwd: [pdftex] pdftex 1.40]

[Thomas A. Schmitz]

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

Re: [Fwd: [pdftex] pdftex 1.40]

[Peter Münster]

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/

Re: [Fwd: [pdftex] pdftex 1.40]

[Aditya Mahajan]

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

Re: [Fwd: [pdftex] pdftex 1.40]

[Martin Schröder]

2007/1/3, Aditya Mahajan <adityam@umich.edu>:
> 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

Re: [Fwd: [pdftex] pdftex 1.40]

[Sanjoy Mahajan]

[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]

>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


[-- Attachment #2: Makefile --]
[-- Type: text/plain, Size: 311 bytes --]

.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

[-- Attachment #3: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [Fwd: [pdftex] pdftex 1.40]

[Martin Schröder]

2007/1/3, Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>:
> 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

Re: [Fwd: [pdftex] pdftex 1.40]

[Hans Hagen]

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
-----------------------------------------------------------------

Re: [Fwd: [pdftex] pdftex 1.40]

[luigi scarso]

On 1/2/07, Taco Hoekwater <taco@elvenkind.com> 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...
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.

Re: [Fwd: [pdftex] pdftex 1.40]

[Hans Hagen]

luigi scarso wrote:
> On 1/2/07, Taco Hoekwater <taco@elvenkind.com> 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
-----------------------------------------------------------------

Re: [Fwd: [pdftex] pdftex 1.40]

[Hans Hagen]

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
-----------------------------------------------------------------

Re: [Fwd: [pdftex] pdftex 1.40]

[Hans Hagen]

Martin wrote:
> 2007/1/3, Aditya Mahajan <adityam@umich.edu>:
>   
>> 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
-----------------------------------------------------------------

Re: [Fwd: [pdftex] pdftex 1.40]

[Sanjoy 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.
> >   
> 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)

Re: [Fwd: [pdftex] pdftex 1.40]

[Hans Hagen]

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
-----------------------------------------------------------------

Re: [Fwd: [pdftex] pdftex 1.40]

[Aditya Mahajan]

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

Re: [Fwd: [pdftex] pdftex 1.40]

[Martin Schröder]

2007/1/4, Aditya Mahajan <adityam@umich.edu>:
> 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

Re: [Fwd: [pdftex] pdftex 1.40]

[Aditya Mahajan]

On Thu, 4 Jan 2007, Martin Schröder wrote:

> 2007/1/4, Aditya Mahajan <adityam@umich.edu>:
> > 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

Re: [Fwd: [pdftex] pdftex 1.40]

[luigi scarso]

> 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