- ntg-pdftex - NTG Mailing Lists

pdftexbin
by Martin Schroeder 05 Aug '03

05 Aug '03

pdftexdir/pdftex.mk has these lines: <blockquote> # pdftex binaries archive pdftexbin: rm -f pdtex*.zip $(pdftex_bin) XLDFLAGS=-static $(MAKE) $(pdftex_bin) if test "x$(CC)" = "xdos-gcc"; then \ $(MAKE) pdftexbin-djgpp; \ elif test "x$(CC)" = "xi386-mingw32-gcc"; then \ $(MAKE) pdftexbin-mingw32; \ elif test "x$(CC)" = "xgnuwin32gcc"; then \ $(MAKE) pdftexbin-gnuwin32; \ else \ $(MAKE) pdftexbin-native; \ fi pdftexbin-native: strip $(pdftex_bin) zip pdftex-native-`datestr`.zip $(pdftex_bin) $(pdftex_pool) pdftexbin-djgpp: dos-strip $(pdftex_bin) dos-stubify $(pdftex_bin) zip pdftex-djgpp-`datestr`.zip $(pdftex_exe) $(pdftex_pool) pdftexbin-mingw32: i386-mingw32-strip $(pdftex_bin) for f in $(pdftex_bin); do mv $$f $$f.exe; done zip pdftex-mingw32-`datestr`.zip $(pdftex_exe) $(pdftex_pool) pdftexbin-gnuwin32: gnuwin32strip $(pdftex_bin) for f in $(pdftex_bin); do mv $$f $$f.exe; done zip pdftex-gnuwin32-`datestr`.zip $(pdftex_exe) $(pdftex_pool) </blockquote> It's clear what these lines should do, but unfortunately they currently don't work: - the binaries made are _very_ static: they don't work. We make static linux binaries by setting LDFLAGS=-static before configure... - datestr is undefined. - I can't test non-native plattforms, so I don't know if they still work Can this be fixed or should the targets go? 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

reserveobjnum (was: release notes for pdfTeX 1.11a (draft))
by Martin Schroeder 01 Aug '03

01 Aug '03

On 2003-07-30 18:56:42 +0200, Hans Hagen wrote: > At 16:58 30/07/2003 +0200, Martin Schroeder wrote: > > >- The syntax of \pdfobj has been extended: > > \pdfobj <object type spec> (h, v, m) > > <object type spec> --> reserveobjnum > > | [useobjnum <number>] [<attr spec>] [stream > >[<attr spec>]] <object contents> > > <object contents> --> <file spec> > > | <general text> > > When the optional keyword `reserveobjnum' and `useobjnum' is not given, > > the behaviour is unchanged. > > what is <number> in reserveobj, any number? how is the user supposed to > know which numbers are free? > > \pdfobj reserveobjnum 123 {} > \pdfobj useobjnum 123 {} > > do both flush content? what if 123 is already taken? That's wrong; it must be \pdfobj reserveobjnum {} \pdfobj useobjnum \pdflastobj {} See also http://tug.org/mailman/htdig/pdftex/2003-March/003814.html <blockquote src=pdftex.ch> @ The \.{\\pdfobj} primitive is to create a ``raw'' object in PDF output file. The object contents will be hold in memory and will be written out only when the object je referenced by \.{\\pdfrefobj}. When \.{\\pdfobj} is used with \.{\\immediate}, the object contents will be written out immediately. Object referenced in current page are appended into |pdf_obj_list|. </blockquote> 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

Re: [NTG-pdftex] pdftex documentation
by Hans Hagen 31 Jul '03

31 Jul '03

At 20:08 30/07/2003 +0200, Staszek Wawrykiewicz wrote: >Since we have so many changes in pdftex, is there any chance >having pdf documentation updated. There are still some documents >in pdf format in texmf/doc/pdftex/ , but... from Nov, 2 2001 > >Anyway I'd suggest adding texmf/doc/pdftex/NEWS > >Ps. I'm bombarded by mails concerning, e.g., adjusting spaces, fontexpand, >efcode, etc., but cannot help :-( i'll look at the docu later this year; with regards to adjusting: this needs a closer look since there is a discrepancy between than's thesis and pdftex itself, as well as that thanh wants to clean up that code. 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

pdftex documentation
by Staszek Wawrykiewicz 30 Jul '03

30 Jul '03

Since we have so many changes in pdftex, is there any chance having pdf documentation updated. There are still some documents in pdf format in texmf/doc/pdftex/ , but... from Nov, 2 2001 Anyway I'd suggest adding texmf/doc/pdftex/NEWS Ps. I'm bombarded by mails concerning, e.g., adjusting spaces, fontexpand, efcode, etc., but cannot help :-( Thanks, -- Staszek Wawrykiewicz StaW(a)gust.org.pl

1 0

Bug: <hex> string to () string
by Heiko Oberdiek 30 Jul '03

30 Jul '03

Hello, I wanted to include pdf slides from: http://ais.informatik.uni-freiburg.de/lehre/ss03/ki/slides/01-intro.pdf by pdfTeX, but the colors in some of the images are terrible wrong. Driver file: % test.tex \nopagenumbers \pdfcompresslevel=0 \pdfximage width 297bp height 210bp page 14 {01-intro.pdf} % similar page 9, ... \pdfrefximage\pdflastximage \bye Analysis: 01-intro.pdf / test.pdf /Page object: 107 0 / 3 0 It references via /XObject the /Image object: /Image object: 110 0 / 8 0 With /ColorSpace object: 111 0 / 7 0 Start of object 111 0 of 01-intro.pdf: 111 0 obj [/Indexed /DeviceRGB 255 <0402070402300402500402700402840402EC3502066E021585020A9A02159C02 ... Start of object 7 0 of test.pdf with one line break for readability: 7 0 obj [/Indexed/DeviceRGB 255 (\004\002\007\004\0020\004\002P\004\002p\004\002\37777777604 \004\002\377777777545\002\006n\002\025\37777777605\002... ==> The translation of 8-bit characters that have set it eighth bit get terrible wrong: hex(84) --> string(\37777777604) hex(EC) --> string(\37777777754) It seems that the octal number is written as 32 bit number instead of a 8 bit number. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de>

3 5

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

Tracking Bugs, Patches and Feature Requests
by Martin Schroeder 11 Jul '03

11 Jul '03

Hi, the pdfTeX project needs a system for tracking bugs, patches and feature requests (whenever I integrate all the latest patches and look for open bugs I fear I forget one). We could of course set up the needed software by ourself, but there are already places that offer the needed services. I did a quick survey: - Sourceforge (http://sf.net) - Tracker for bugs, support requests, patches, feature requests - Limited to OSI-compatible software (which pdfTeX is) - Savannah (savannah.nongnu.org) - Tracker for bugs, support requests, patches - Limited to GPL-compatible software (which pdfTeX is) - Emphasises on freeness - Berlios (berlios.de): - Tracker for bugs, support requests, patches - Not limited to OSI-compatible software (which pdfTeX is) - It seems you can't automatically get mail about new bugs/patches - Management is german It seems Sourceforge is offering the most with the least strings attached. I propose we set up pdfTeX at Sourceforge in the near future (post-Hawaii) for project management but keep the sources in the p4 repository at DANTE/TeXlive (it works perfectly). Comments? 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

4 4

pdf_version_found > pdf_version_wanted
by Martin Schroeder 11 Jul '03

11 Jul '03

Hi, current pdfTeX will not embed pdfs with a newer version than the one to be produced. I want to make this behaviour configurable through pdftex.cfg (and a corresponding primitive). pdfTeX would then only emit a warning but embed the pdf anyway (like older versions did). Reason is to be backwards-compatible: We have installations where we want to upgrade the pdfTeX-installation but not the TeX-producing application. Objections? 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 5

Patch OutlineAttr
by Heiko Oberdiek 10 Jul '03

10 Jul '03

Hello, Patch OutlineAttr Since PDF 1.3/1.4 further entries are supported in the outline item dictionary: /SE, /C, /F. Especially the last to keys can be interesting. Currently there is no support in pdfTeX to set these entries. Therefore I have added the possibility to specify further attributes to the \pdfoutline command: \pdfoutline <outline spec> <outline spec> --> <attr spec> <action spec> [count <number>] <general text> Patch files, based on 2002/06/05 v1.11a: pdftex.ch.diff for pdftexdir/pdftex.ch pdftex-syntax.txt for pdftexdir/pdftex-syntax.txt Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> --

2 1

Re: ANNOUNCE: Xpdf 2.02 - a PDF viewer for X
by Martin Schroeder 10 Jul '03

10 Jul '03

On 2003-03-24 19:58:02 -0000, Derek B. Noonburg wrote: > Glyph & Cog, LLC is pleased to announce a new version of Xpdf, the > open source Portable Document Format (PDF) viewer for X. The Xpdf > project also includes a PDF text extractor, PDF-to-PostScript > converter, and various other utilities. > > Xpdf runs under the X Window System on Unix, VMS, and OS/2. The non-X > components (pdftops, pdftotext, etc.) also run on Win32 systems and > should run on pretty much any system with a decent C++ compiler. > > Major changes: > * Rewrote the text extractor code that assembles words into lines to > better handle vertically overlapping lines. > * Add the "match" option for paper size (in PostScript output). > * Added support for external 16-bit TrueType fonts; added the > displayCIDFontTT and displayNamedCIDFontTT commands to the xpdfrc > file. > * Added an Arabic language support package. > * Added the Windows-1255 encoding to the Hebrew language package. > > See the `CHANGES' file for a complete list of changes. I'll integrate it next week (i.e. hopefully before DANTE2003) and thus start work on 1.11a 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

4 10

PDF inclusion with annotations
by Andreas Matthias 10 Jul '03

10 Jul '03

Last month on pdftex mailing list we had a short discussion, whether annotations of external PDFs could be copied when including PDFs. I gave it a try and now I have a first partial success. The code is far from being complete and there are still a lot of bugs in it. Nevertheless I think it is the right time now to show you the code, so we can discuss whether this is the right way to go on. You can download the patches at: http://stud3.tuwien.ac.at/~e9225580/pdftex-1.10b-incl-annot.tar.bz2 Here is a short description of the changes I did: (1)While reading the image (function read_pdf_info), the annotations of this image are read, too, and a map with all relevant details about the annotations is set up. (2)While writing the reference (/Im1 Do) to the content stream (function out_image), a dummy annotation node is created to get a correct /Annots array. Those dummy annotations nodes are caught during module @<Flush out PDF annotations@> and are just delete; no dummy annotation object it written out. (3)Eventually in function epdf_write all annotation objects of this image are copied are written out. 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. Instead of \pdfximage {doc.pdf} \pdfliteral{q 0 1 -1 0 0 0 cm} \pdfrefximage\pdflastximage \pdfliteral{Q} macro packages should do \pdfximage {doc.pdf} \pdfsetctm 0 1 -1 0 0 0 \pdfrefximage\pdflastximage \pdfresetctm Now pdftex does know about the current transformation matrix and can calculate the correct coordinates of /Rect. 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. The primitives \pdfsetctm and \pdfresetctm create whatsit nodes. When these nodes a shipped out \pdfsetctm pushed its arguments on a stack and \pdfresetctm pop them again. When a \pdfrefximage node is shipped out it can look at the stack to get the current CTM and calculate a correct /Rect. The tarball contains 2 plain TeX files and 2 LaTeX files which show some examples. To compile the LaTeX files you must apply the patch pdftex.def.diff to pdftex.def. And now comes the unpleasant part. Here is a list of major bugs that those patches have :-( * If an image is included several times, all copies have the same image number. Unfortunately I used this image number as the key to the map of annotations. That's why you cannot include pages several times, without getting false /Rects. This bug shouldn't be too difficult to fix. * \pdfsetctm should only be used in horizontal mode. I have not idea why it chokes in vertical mode. * There should be no material between \pdfsetctm and \pdfrefximage. Any material there would cause pdftex to call pdf_set_origin, which introduces a new CTM not taken into account by \pdfsetctm. * LaTeX, graphicx: foolish things like \includegraphics[angle=90, angle=90]{doc.pdf} causes the call of the function pdf_set_origin and therefore don't work either. * There must not be a page break between \pdfsetctm and \pdfresetctm. * There are probably more ... Ciao Andreas

2 1

Re: [NTG-pdftex] PandaLex
by Tom Kacvinsky 21 May '03

21 May '03

Second try: first time this went to Martin instead of the list. D'oh! As Martin should know, as I figure he is the best person around for forwarding from one list to the other. ;-) Well, maybe Nelson Beebe can take that "title". Tom On 2003/05/19 at 15:01, Martin Schroeder <ms(a)artcom-gmbh.de> wrote: > On 2003-05-19 14:41:21 +0200, Rolf Niepraschk wrote: > <snip> NOTE: http://www.tinyurl.com is great for long links in emails. > Thanks. > > It's from the author of the comp.text.pdf USENET frequently asked > questions document. :-) >

1 0

PandaLex
by Rolf Niepraschk 19 May '03

19 May '03

About: PandaLex is the PDF parsing code from Panda, which has been split into its own project to increase its utility. It is a flex and bison description of the PDF specification, which allows programmers to define callbacks to handle different document elements. ==> http://www.stillhq.com/cgi-bin/getpage?area=pandalex&page=index.htm ...Rolf -- || Rolf Niepraschk c/o Physikalisch-Technische Bundesanstalt || || Abbestr. 2-12; D-10587 Berlin, Germany || || Tel/Fax: ++49-30-3481-316/490, email: Rolf.Niepraschk(a)ptb.de ||

2 1

Re: [NTG-pdftex] SockeTeX :-)
by Hans Hagen 01 Apr '03

01 Apr '03

At 08:11 PM 3/30/2003 -0500, Tom Kacvinsky wrote: >Hi all, > >Cool. Fabrice, didn't you work on something similar? I remember you >showing me some work you were doing on use of URLs in TeX documents >at EuroTeX 2001 (in Kerkrade). Whatever became of that? that should work out of the box: \input http://someplace.somewhere/somefile.sometype 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 -------------------------------------------------------------------------

4 4

splitting pdftex
by The Thanh Han 01 Apr '03

01 Apr '03

Hi all, I am considering to split pdftex into 3 programs: 1) pdftex -- a (hopefully) stable version that contains only features often used by regular users 2) pdfetex -- pdftex + etex 3) pdfxtex ('x' stands for experiment; suggestions for another name are much welcome) -- contains features that are normally not used + features being tested; ie pdftex + etex + all testing and buggy features ;) This version is for brave only ;) Please let me know what you think of it? Thanh

2 1

Re: [pdftex] Bug in 1.10a: \pdfximage with pdf file and width
by Hans Hagen 25 Feb '03

25 Feb '03

At 07:44 PM 2/24/2003 +0100, you wrote: >On Mon, 24 Feb 2003, Hans Hagen wrote: > > > mediaboxes (in xforms etc) should also be as accurate as possible since > > otherwise the viewers clip engine starts spoiling things > >Scaling seems to be precise everywhere now. There is no scale in the >xforms, the /Matrix [1 0 0 1 0 0] is used. > >But /BBox dimensions ARE rounded to these decimal_digits when written >out, as are also still the width and height of the PDF images. > >Do you suggest, that even the width and height of images and xforms >should be written out with max. number digits? It costs nearly nothing, >but this is currently NOT done. If you complain quickly enough, it might >go into the next release. :-) This is in pdftex.ch code lines 3549, >3550, 8274, 8275, 8286, 8290. those dimensions should indeed be precise (and better be rounded up (nth digit) than down in order not to clip lines 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