- ntg-pdftex - NTG Mailing Lists

Re: [NTG-pdftex] Spurious /NewWindow false
by Martin Schroeder 23 Jul '03

23 Jul '03

On 2003-07-22 17:54:30 +0200, Hartmut Henkel wrote: > ist der Patch unten im neuen 1.11 drin? Hartmut, yes (#3411). :-) - Bugfix: \pdfstartlink would produce spurious /NewWindow entries. Also the syntax of <action spec> and <goto-action spec> has been cleaned up. See http://www.ntg.nl/pipermail/ntg-pdftex/2003-June/000167.html Best regards Martin -- Martin Schröder, MS(a)ArtCom-GmbH.DE ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10

1 0

pdftex: compile errors/warnings
by Thomas Esser 17 Jul '03

17 Jul '03

Today, I have compiled pdftex (today's version from the perforce tree) on a Sparc Solaris machine using the system compilers. First problem: texk/web2c/pdftexdir/utils.c contains three comments written in C++ style which is not allowed: "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/utils.c", line 459: syntax error before or at: / "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/utils.c", line 465: syntax error before or at: / "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/utils.c", line 471: syntax error before or at: / And I did get a few warnings: "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/utils.c", line 94: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/utils.c", line 125: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/../../../libs/zlib/zlib.h", line 838 argument : pointer to char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/utils.c", line 289: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/../../../libs/zlib/zlib.h", line 838 argument : pointer to char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/config.c", line 111: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/writet1.c", line 348: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/writet1.c", line 1000: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/writet1.c", line 1012: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/writet1.c", line 1033: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/writezip.c", line 55: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/writezip.c", line 63: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/writettf.c", line 720: warning: assignment type mismatch: pointer to unsigned char "=" pointer to char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/writettf.c", line 1043: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/writettf.c", line 1097: warning: assignment type mismatch: pointer to char "=" pointer to unsigned char "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/pdftoepdf.cc", line 195: Warning: String literal converted to char* in formal argument fmt in call to pdftex_fail(char*, ...). "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/pdftoepdf.cc", line 266: Warning: String literal converted to char* in formal argument fmt in call to pdftex_fail(char*, ...). "/share/gcc-te-remove-me/teTeX/tetex-src/texk/web2c/pdftexdir/pdftoepdf.cc", line 296: Warning: String literal converted to char* in formal argument 1 in call to pdf_puts(char*). ...and many more of warnings of this kind... Thomas

2 2

1.11a - open issues?
by Martin Schroeder 16 Jul '03

16 Jul '03

Hi, I'm planning to release 1.11a next week. Are there any open issues (patches, bugs, needed features) left? Best regards Martin PS: Compiler warnings will be fixed. :-) -- Martin Schröder, MS(a)ArtCom-GmbH.DE ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10

3 3

still beta?
by Martin Schroeder 16 Jul '03

16 Jul '03

from the REAME: It is still under beta development and all features are liable to change. Despite its beta state, pdfTeX produces excellent PDF code. Is pdfTeX still in beta state? Methinks it has matured enough. :-) Best regards Martin -- Martin Schröder, MS(a)ArtCom-GmbH.DE ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10

2 1

Re: [NTG-pdftex] Re: Patch ShellEscape
by Hans Hagen 14 Jul '03

14 Jul '03

At 13:42 11/07/2003 +0200, Heiko Oberdiek wrote: >* But there is also a disadvantage of the \ifeof18 method: > TeX generates a error message, if \ifeof18 is not supported. > Unhappily TeX does not provide an exception mechanism, so this > error cannot be catched. > For "tex" and "etex" I see no way to avoid this without a new > primitive that can easily checked for existence. The primitive > can be either a command that indicates the presence of the > feature or returns the version number of web2c. > For "pdf(e)tex" this is not a problem, because here > \pdfversion and \pdfrevision can be asked. So packages such > as pdftricks, pdftex.def, ... will be happy. Isn't there a new version of tex coming (dek posted some fixes)? In that case, one can use that version number since the moment that those fixes are in the new distribution sync with the ifeof18 extension. Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma(a)wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------

3 6

Re: [NTG-pdftex] Re: Patch ShellEscape
by Hans Hagen 13 Jul '03

13 Jul '03

At 15:49 10/07/2003 +0200, Heiko Oberdiek wrote: >On Thu, Jul 10, 2003 at 02:57:25PM +0200, Martin Schroeder wrote: > > > On 2003-07-10 14:35:48 +0200, Martin Schröder wrote: > > > - New readonly primitive \pdfshellescape which can be used to test if the > > > > Thinking further (and being reminded by Rolf): Is there a reason > > why this can _not_ be called \shellescape? It's got nothing to do > > with pdf (and would be usefull in all web2c-based TeX engines, no > > matter what they are called). > >\write18 is a property of web2c-based TeX engines, so >\shellescape is the better name and it would be even better, >if this can be added to the other web2c-based TeX engines, too. i have problems with the not that name compatible: \shellescape \write18 so if a dedicated name would be used, we would either have something: \shellescape{some command} \shellescapemode == number or (considering it a channel) \write18 \ifeof18 Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma(a)wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------

2 3

Re: [NTG-pdftex] pdf_version_found > pdf_version_wanted
by Hans Hagen 12 Jul '03

12 Jul '03

At 17:29 10/07/2003 +0200, Martin Schroeder wrote: >On 2003-07-08 17:55:17 +0200, Martin Schröder wrote: > > one to be produced. I want to make this behaviour configurable > > through pdftex.cfg (and a corresponding primitive). pdfTeX would > >Currently the primitive is tentatively named >\pdfoptionpdfversionerrorlevel. Any better idea? ^^^ omit the second pdf -) Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma(a)wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------

1 0

Re: [NTG-pdftex] PDF inclusion with annotations
by Hans Hagen 12 Jul '03

12 Jul '03

At 14:01 10/07/2003 +0200, Martin Schroeder wrote: >I must confess I have not cared for annotations yet so I just >hope that this is correct (it certainly sounds so) and leave that >to the experts. an option is to support this under user control: \pdfmergeannots=0 : not enabled \pdfmergeannots=1 : enabled defaulting to 0 (not enabled) that way macro packages can control it also, it will need some extensive testing, esp for user annotations which may have object references, resources etc; since this would involve parsing of content, it's also a dangerous excersise (hard to make foolproof); this means that we should be able to control this at the annotation level: - links - widgets - etc so, we should need something \pdfmergelinkannots=1 etc as well > > Another important this which happens within the function out_image, > > is the calculation to the new coordinates of the annotation's /Rect. > > There are no big problems if an images is scaled with the help of > > <rule spec> of \pdfximage. But their are a lot of problems if > > macro packages do something like \pdfliteral{.5 0 0 .5 0 0 cm} > > for scaling and similar things for rotating images. To calculate > > the coordinates of /Rect, pdftex must know exactly which coordinate > > transformations are actually taking place. So I introduced two > > new primitives: \pdfsetctm and \pdfresetctm. > >This I find much more interesting. this problem is more general, since it also concerns normal (not xpdf related) code; i remember discussing this with thanh a few years a go but forgot about the implications, but for out_image situations it sounds ok to me >[...] > > > Since TeX does not have a function to scan floating-point numbers, > > I used scan_dimen as a work around to scan the arguments of \pdfsetctm. > > That's why you must write > > > > \pdfsetctm 0bp 1bp -1bp 0bp 0bp > > > > so far. It should be no problem to change this in the future. > >This could be added. i don't like the unit; we could use numbers here and assume that they are scaled points (as happened in some dvi postprocessors); an alternative is to make it a token list \pdfsetctm{....} and treat each component as what it is: floating point or dimension. Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma(a)wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------

1 0

Re: [NTG-pdftex] 1.10b
by Heiko Oberdiek 11 Jul '03

11 Jul '03

At Tue, 11 Feb 2003 17:41:42 +0100 Hans Hagen wrote: > > At 04:36 PM 2/11/2003 +0100, Martin Schroeder wrote: > >On 2003-02-07 19:51:27 +0100, Thomas Esser wrote: > > > > also on the todo list: > > > > > > What about the things that Heiko Oberdieck has proposed: > > > http://omnibus.uni-freiburg.de/~oberdiek/pdftex.html > > >The map files need a bit more thinking. > > indeed, esp since the optimization only looks at the first 8 chars of a > filename if i remember right; No, you have already given that hint last year and I have changed the patch using all chars. To make it clear, the patch improves the performance of the *current* map file handling of pdfTeX. It saves me *much* time in comparison to the binary of TeXLive 7. But for *future* versions we should find an agreement about the behaviour of pdfTeX regarding map files, eg: * Map files: * Where can they specified? * config file (pdftex.cfg) * support of other config files * config files given on command line * map files given on command line * config files given by command * map files given by command * ... * When they are evaluated? * static, first use * dynamic changes possible? * Which order? * default, if no map file is given? * adding mapfiles * replacing mapfiles * order ... * ... * Map entries: * later entries are ignored with warning (current) * later entries replaces older ones silently * syntax ... * ... I hope I will find some time next days to give a suggestion for a specification. One aim can be to make the behaviour similar to dvips. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de>

8 28

Patch ShellEscape
by Heiko Oberdiek 11 Jul '03

11 Jul '03

Patch ShellEscape Packages such as pdftricks.sty, epstopdf.sty (or pdftex.def) call external programs. They do not work at all, if the \write18 feature is not enabled. Therefore a robust method would be useful in order to inform the user. For security reasons the \write18 featuer must not be set by TeX macro code. Thus the patch introduces a new readonly primitive \pdfshellescape that expands to "0" if the \write 18 feature is disabled and "1" in the other case. Use, for instance: \ifnum\pdfshellescape=0 \message{The \string\write18 feature is disabled.} \else \message{The \string\write18 feature is enabled.} \fi Patch files: pdftex.ch.diff for TeX/texk/web2c/pdftexdir/pdftex.ch pdfetex.ch2.diff for TeX/texk/web2c/pdfetexdir/pdfetex.ch2 Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> --

5 11