bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug #43122] texi2dvi does not compile enough times to get toc


From: Vincent Belaïche
Subject: Re: [bug #43122] texi2dvi does not compile enough times to get toc
Date: Fri, 21 Aug 2015 23:18:30 +0200

My answers below:

Le 21/08/2015 17:25, Gavin Smith a écrit :
>> So yes the .toc and the other output files are there, and that does not
>> suffice for texi2dvi to trigger one more run. As I said the problem is
>> that MikTeX pdftex does not traces the \openout into the log file.
>
> Here's a report of a similar problem for a different TeX engine, now
> fixed: http://tracker.luatex.org/view.php?id=909 . If you can confirm
> that this problem occurs with MikTeX, it would be a good idea for us
> to report it as a bug.


Hello,

Here is what I get:

bash-3.1$ cat > openout.tex <<EOF
> \newwrite \ourwrite
> \openout \ourwrite dum.dum
> \bye
> EOF
bash-3.1$ pdftex openout.tex
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (MiKTeX 2.9 64-bit)
entering extended mode
(c:\Nos_Programmes\msys\local\projects\metafont-for-beginners\openout.tex
[1{C:/Users/Vincent/AppData/Local/MiKTeX/2.9/pdftex/config/pdftex.map}] )<C:/Pr
ogrammes/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmr10.pfb>
Output written on openout.pdf (1 page, 8405 bytes).
Transcript written on openout.log.
bash-3.1$ rm dum.dum
bash-3.1$ luatex openout.tex
This is LuaTeX, Version beta-0.76.0-2013062821 (rev 4627)
(c:/Nos_Programmes/msys/local/projects/metafont-for-beginners/openout.tex
[1{C:/Users/Vincent/AppData/Local/MiKTeX/2.9/pdftex/config/pdftex.map}] )<C:/Pro
grammes/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmr10.pfb>
Output written on openout.pdf (1 page, 8399 bytes).
Transcript written on openout.log.
bash-3.1$ rm dum.dum
bash-3.1$ xetex openout.tex
This is XeTeX, Version 3.1415926-2.5-0.9999.3 (MiKTeX 2.9 64-bit)
entering extended mode
(c:\Nos_Programmes\msys\local\projects\metafont-for-beginners\openout.tex )
No pages of output.
Transcript written on openout.log.

As you can see there is no such thing as any \openout trace in the .log
file, for any of pdftex, luatex or xetex engines.

I fully agree with the argument by Karl: even though the --recorder
option now exists on most engines, we should not break the world.

However it is rather easy to check whether the --recorder option is
supported like that:

bash-3.1$ if pdftex --recorder '\bye' > /dev/null; then recorder_support=yes; 
else recorder_support=no; fi
bash-3.1$ echo $recorder_support
yes

  Vincent.






---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
http://www.avast.com




reply via email to

[Prev in Thread] Current Thread [Next in Thread]