July 2005 - ntg-pdftex - NTG Mailing Lists

Re: [NTG-pdftex] 1.30.0-rc4
by Akira Kakuto 23 Jul '05

23 Jul '05

> Your -etex switch patch looks reasonable, though I might make some > changes (variable names &c) when I check in the code. I forgot to consider aleph (eobase.ch and eoext.ch). Please check in also those files. Thanks, -- Akira Kakuto

1 0

Re: [NTG-pdftex] no etex while dump
by Akira Kakuto 22 Jul '05

22 Jul '05

> To summarize; under bash (linux or cygwin) environment and gcc as a > builder, things are consistent, although seems to be mysterious. To be > on safe side, a star should be quoted. Under windows the behaviour is > environment/compiler dependent. Binaries made by M$ compiler behaves > quite well; the star is not expanded anyhow by shell and is passed to > TeX as is. Consequently, it CAN'T be quoted with backslash, since TeX > reports `Undefined control sequence \*' then. Windows binaries made by > gcc under cyg environment works like those under linux. That is the > whole mystery. -etex commandline option will fix the inconsistency. diff -Nur web2c-orig/etexdir/etex.ch web2c/etexdir/etex.ch --- web2c-orig/etexdir/etex.ch Wed Oct 13 06:29:47 2004 +++ web2c/etexdir/etex.ch Sat Jul 23 00:36:24 2005 @@ -3051,10 +3051,11 @@ is a run-time switch. @<Enable \eTeX, if requested@>= -@!init if (buffer[loc]="*")and(format_ident=" (INITEX)") then +@!init if ((buffer[loc]="*")or etex_extension_p)and(format_ident=" (INITEX)") then begin no_new_control_sequence:=false; @<Generate all \eTeX\ primitives@>@; - incr(loc); eTeX_mode:=1; {enter extended mode} + if (buffer[loc]="*") then incr(loc); + eTeX_mode:=1; {enter extended mode} @<Initialize variables for \eTeX\ extended mode@>@; end; tini@;@/ @@ -3094,6 +3095,7 @@ @<Glob...@>= @!eTeX_mode: 0..1; {identifies compatibility and extended mode} +@!etex_extension_p : boolean; @ @<Initialize table entries...@>= eTeX_mode:=0; {initially we are in compatibility mode} diff -Nur web2c-orig/lib/texmfmp.c web2c/lib/texmfmp.c --- web2c-orig/lib/texmfmp.c Tue Jul 05 20:16:44 2005 +++ web2c/lib/texmfmp.c Sat Jul 23 00:51:48 2005 @@ -778,6 +778,9 @@ { "no-shell-escape", 0, &shellenabledp, -1 }, { "debug-format", 0, &debugformatfile, 1 }, { "src-specials", 2, 0, 0 }, +#if defined (eTeX) || defined (pdfeTeX) + { "etex", 0, &etexextensionp, 1 }, +#endif #endif /* TeX */ #if defined (TeX) || defined (MF) || defined (MP) { "file-line-error-style", 0, &filelineerrorstylep, 1 }, diff -Nur web2c-orig/texmfmp-help.h web2c/texmfmp-help.h --- web2c-orig/texmfmp-help.h Sun Aug 29 06:29:38 2004 +++ web2c/texmfmp-help.h Sat Jul 23 00:41:45 2005 @@ -93,6 +93,7 @@ " If no arguments or options are specified, prompt for input.", "", "-enc enable encTeX extensions such as \\mubyte", + "-etex enable e-TeX extensions in INITEX", "[-no]-file-line-error disable/enable file:line:error style messages", "-fmt=FMTNAME use FMTNAME instead of program name or a %& line", "-halt-on-error stop processing at the first error", @@ -408,6 +409,7 @@ " If no arguments or options are specified, prompt for input.", "", "-enc enable encTeX extensions such as \\mubyte", + "-etex enable e-TeX extensions in INITEX", "[-no]-file-line-error disable/enable file:line:error style messages", "-fmt=FMTNAME use FMTNAME instead of program name or a %& line", "-halt-on-error stop processing at the first error",

2 1

changes in forthcomming release
by The Thanh Han 22 Jul '05

22 Jul '05

Hi, I have applied most of patches and suggestions from Hartmut. There are still a few pending issues: 1) while we are renaming some promitives to be consistent, would it be better to change the following as well: pdfoptionpdfminorversion -> pdfminorversion pdfoptionalwaysusepdfpagebox -> pdfforcepagebox pdfoptionpdfinclusionerrorlevel -> ??? 2) what about moving everything from pdfxtex to pdftex and remove pdfxtex? 3) should the pkmode and microinterval patches be in as well? Martin, can you please wait for a few days, I want to make another snapshot this week. Thanh

5 7

no etex while dump
by Pawel Jackowski 22 Jul '05

22 Jul '05

On 1.30-rc2 I made the following z.tex file: \catcode`\{=1 \catcode`\}=2 \edef\z{\the\eTeXversion} \dump Then I hit pdfetex -ini *z.tex and got This is pdfeTeXk, Version 3.141592-1.30.0-rc2-2.2 (Web2C 7.5.4) (INITEX) 22 JUL 2005 00:22 \write18 enabled. %&-line parsing enabled. **z.tex (./z.tex ! Undefined control sequence. l.3 \edef\z{\the\eTeXversion } Clues? Sorry, for the moment I can't try on rc3. BR, -- Pawe/l Jackowski P.Jackowski(a)gust.org.pl

6 12

Re: [NTG-pdftex] no etex while dump
by Akira Kakuto 22 Jul '05

22 Jul '05

> pdfetex --ini '*z' works. > pdfetex --ini '*z.tex' fails. > > I cannot understand the reason. It was a funny shell effect. Many thanks to Hartmut. -- Akira Kakuto

1 0

Re: [NTG-pdftex] no etex while dump
by Akira Kakuto 22 Jul '05

22 Jul '05

> Sorry. I was wrong. > pdfeinitex \*z.tex worked. Correction: pdfetex --ini '*z' works. pdfetex --ini '*z.tex' fails. I cannot understand the reason. -- Akira Kakuto

1 0

Re: [NTG-pdftex] no etex while dump
by Akira Kakuto 22 Jul '05

22 Jul '05

> It seemes that } is forbidden after \the in the > case of \edef: > > pdfetex --ini '*z.tex' > This is pdfeTeX, Version 3.141592-1.30.0-rc3-2.2 (Web2C 7.5.5) (INITEX) > (./z.tex > ! Undefined control sequence. > l.3 \edef\z{\the\eTeXversion > } > ? > ! You can't use `end-group character }' after \the. > l.3 \edef\z{\the\eTeXversion} Sorry. I was wrong. pdfeinitex \*z.tex worked. -- Akira Kakuto

1 0

Re: [NTG-pdftex] no etex while dump
by Akira Kakuto 22 Jul '05

22 Jul '05

> This is pdfeTeXk, Version 3.141592-1.30.0-rc2-2.2 (Web2C 7.5.4) (INITEX) > 22 JUL 2005 00:22 > \write18 enabled. > %&-line parsing enabled. > **z.tex > (./z.tex > ! Undefined control sequence. > l.3 \edef\z{\the\eTeXversion > } > Clues? Sorry, for the moment I can't try on rc3. It seemes that } is forbidden after \the in the case of \edef: pdfetex --ini '*z.tex' This is pdfeTeX, Version 3.141592-1.30.0-rc3-2.2 (Web2C 7.5.5) (INITEX) (./z.tex ! Undefined control sequence. l.3 \edef\z{\the\eTeXversion } ? ! You can't use `end-group character }' after \the. l.3 \edef\z{\the\eTeXversion} -- Akira Kakuto

1 0

Re: [NTG-pdftex] no etex while dump
by Pawel Jackowski 22 Jul '05

22 Jul '05

> Hartmut > it works also here without quote even in rc3! Same bash. I don't > understand this. Needs checking... I haven't noticed this behaviour on rc1. Give me some time, I will try to compile rc1 once again and check with the same conditions. > Taco: > Are you sure? Yes I am sure that something differs depending on something :) I'm not sure if it is a bug. I'm sure that the same command (without quoted *) on the same shell works differently on pdfTeX 1.20a and pdfTeX 1.30.0-rc2. Meybe it is a question of compiler? One was compiled under M$ Visual C, the second under gcc. Checking... > Hans: > indeed; it's a feature request -) I always assume I don't know something important :) Anyway, I strongly support this request. -- Pawe/l Jackowski P.Jackowski(a)gust.org.pl

2 2

[ pdftex-Bugs-359 ] pdftex generates errors when it does not have to - eg \pdfinfo
by noreply＠sarovar.org 22 Jul '05

22 Jul '05

Bugs item #359, was opened at 2005-05-30 19:51 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=359&group_id=106 Category: None >Group: v1.21a >Status: Closed >Resolution: Fixed Priority: 3 Submitted By: Taco Hoekwater (taco) Assigned to: Nobody (None) Summary: pdftex generates errors when it does not have to - eg \pdfinfo Initial Comment: The following submitted on behalf of Jonathan Fine: pdftex generates errors when it does not have to. This fault prevents the build of Python docs on some platforms. The fix may be to remove the error-generating code· For more details, see my posting to comp.text.tex. Google link: <http://groups-beta.google.com/group/comp.text.tex/msg/4b4842202ce88cda?hl=en> Copy and paste ============== There is, in my opinion, a problem with pdftex. (This is not to say that the macros used could not be improved.) pdftex exits on \pdfinfo error. TeX does not exit on error. == $ pdftex This is pdfTeX, Version 3.14159-1.10b (Web2C 7.4.5) **\pdfoutput 0 {/usr/share/texmf/pdftex/config/pdftex.cfg} *\pdfinfo pdfTeX error (ext1): \pdfinfo used while \pdfoutput is not set. <*> \pdfinfo No pages of output. Transcript written on texput.log. == The present semantics of \pdfinfo are confused. For example, I _can_ use \pdfinfo and generate dvi! I just have to be a bit sneaky. == $ pdftex This is pdfTeX, Version 3.14159-1.10b (Web2C 7.4.5) **\pdfoutput 1 {/usr/share/texmf/pdftex/config/pdftex.cfg} *\pdfinfo {} *\pdfoutput 0 *\shipout\hbox{} [1] *\end Output written on texput.dvi (1 page, 128 bytes). == Here, if pdf is not being generated, pdfinfo is ignored. Suppose the semantics of \pdfinfo were something like: \pdfinfo{ ... } Stores information that is written to the PDF file, if pdftex generates a PDF file. Otherwise ignored. Then the error that prompted this thread would not have occurred. -- ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-07-22 11:10 Message: Logged In: YES user_id=421 This has been fixed in 1.30.0 ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2005-05-30 20:05 Message: Logged In: YES user_id=1608 Relevant bit of code: procedure check_pdfoutput(s: str_number); begin if pdf_output <= 0 then begin print_nl("pdfTeX error (ext1): "); print(s); print(" used while \pdfoutput is not set"); succumb; end; end The fastest resolution, of course, is to change the test to "pdf_output < 0" so that the error is also generated in dvi processing mode. But Jonathan's proposal is also valid, at least for mode-independant commands like \pdfinfo. Or maybe generate a normal TeX error message? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=359&group_id=106

1 0