Hi, is this behaviour desired? $ pdftex -ini '\pdfoutput=1 \end' This is pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) (INITEX) \write18 enabled. %&-line parsing enabled. output format initialized to DVI 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 Tue, 7 Sep 2004, Reinhard Kotucha wrote:
is this behaviour desired?
$ pdftex -ini '\pdfoutput=1 \end' This is pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) (INITEX) \write18 enabled. %&-line parsing enabled. output format initialized to DVI
well, it seems that the last line reflects the status of the -output-format switch, which defaults to DVI. The \pdfoutput directive comes after the printing of this line. You see this also if you put \pdfoutput=1 \end into a file. Regards, Hartmut
"Hartmut" == Hartmut Henkel
writes:
>> $ pdftex -ini '\pdfoutput=1 \end' >> This is pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) >> (INITEX) >> \write18 enabled. >> %&-line parsing enabled. >> output format initialized to DVI > well, it seems that the last line reflects the status of the > -output-format switch, which defaults to DVI. The \pdfoutput > directive comes after the printing of this line. You see this > also if you put \pdfoutput=1 \end into a file. Yes, maybe the message should be deferred until the output file is opened. When the output file is opened, pdftex definitely knows whether it produces DVI or PDF. Unfortunately then in my example the message wouldn't appear at all. 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 Wed, 8 Sep 2004, Reinhard Kotucha wrote:
"Hartmut" == Hartmut Henkel
writes: >> $ pdftex -ini '\pdfoutput=1 \end' >> This is pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) >> (INITEX) >> \write18 enabled. >> %&-line parsing enabled. >> output format initialized to DVI
Yes, maybe the message should be deferred until the output file is opened. When the output file is opened, pdftex definitely knows whether it produces DVI or PDF.
Have tried it. A good place for the check and message seems to be procedure fix_pdfoutput, which freezes the output mode once and forever. Then one gets: This is pdfeTeX, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) entering extended mode (./xx.tex (output format initialized to PDF) [1{/usr/lo... Needs this blank and some kind of brackets () around the string, and unclear is which convention to follow, as ( officially already means open file and [ means begin page...
Unfortunately then in my example the message wouldn't appear at all.
Right, but who would care? Regards, Hartmut
"Hartmut" == Hartmut Henkel
writes:
>> Yes, maybe the message should be deferred until the output file >> is opened. When the output file is opened, pdftex definitely >> knows whether it produces DVI or PDF. > Have tried it. A good place for the check and message seems to > be procedure fix_pdfoutput, which freezes the output mode once > and forever. Then one gets: > This is pdfeTeX, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) > entering extended mode > (./xx.tex (output format initialized to PDF) > [1{/usr/lo... > Needs this blank and some kind of brackets () around the string, > and unclear is which convention to follow, as ( officially > already means open file and [ means begin page... Hartmut, many thanks for the response. Maybe it can be done like this: This is pdfeTeX, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) entering extended mode (./xx.tex pdfeTeX: output format initialized to PDF [1(/usr/lo... 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 Wed, 8 Sep 2004, Reinhard Kotucha wrote:
Maybe it can be done like this:
This is pdfeTeX, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) entering extended mode (./xx.tex pdfeTeX: output format initialized to PDF [1(/usr/lo...
Yes, indeed. And you wrote before:
Unfortunately then in my example the message wouldn't appear at all.
Actually also this can be solved, if one puts the fix_pdfoutput also at the begin of the format \dump function, and into the final cleanup. Then when a format is dumped, you also get the right message, and if nothing is done (as in your example), you also get it. This is simple, since fix_pdfoutput is executing only once. But i haven't tried it. Regards, Hartmut
"Hartmut" == Hartmut Henkel
writes:
> Actually also this can be solved, if one puts the fix_pdfoutput > also at the begin of the format \dump function, and into the > final cleanup. Then when a format is dumped, you also get the > right message, and if nothing is done (as in your example), you > also get it. This is simple, since fix_pdfoutput is executing > only once. But i haven't tried it. It's nice to hear that it is not too difficult to accomplish this. But it's more important to avoid messages like this: $ pdftex '\relax\pdfoutput=0 abc \bye' This is pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) output format initialized to PDF This might confuse people. And I hope that someone can fix this before TexLive is released. 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 2004-09-09 00:18:52 +0200, Reinhard Kotucha wrote:
$ pdftex '\relax\pdfoutput=0 abc \bye' This is pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) output format initialized to PDF
This might confuse people. And I hope that someone can fix this before TexLive is released.
It _is_ confusing, but I don't see it as a reason to delay the release further. But if someone (Hartmut?) has a fix _now_... 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-09-09 00:18:52 +0200, Reinhard Kotucha wrote:
$ pdftex '\relax\pdfoutput=0 abc \bye' This is pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) output format initialized to PDF
This might confuse people. And I hope that someone can fix this before TexLive is released.
It _is_ confusing, but I don't see it as a reason to delay the release further. But if someone (Hartmut?) has a fix _now_...
just trow out that line, no one will read it anyway (in de time it could go in the statistics part at the end when asked for) 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 -----------------------------------------------------------------
participants (4)
-
Hans Hagen
-
Hartmut Henkel
-
Martin Schröder
-
Reinhard Kotucha