- ntg-pdftex - NTG Mailing Lists

Re: [NTG-pdftex] pdfpagebox
by Thanh Han The 16 Sep '05

16 Sep '05

On Thu, Sep 15, 2005 at 02:57:59PM +0200, Heiko Oberdiek wrote: > Hello, > > On Thu, Sep 15, 2005 at 04:31:18AM -0700, Thanh Han The wrote: > > > Another issue is that I am implementing a primitive > > requrested by Cho, to grab the BBox of an included pdf. > > What's the purpose? The knowledge of width and height is > important (graphicx, pdfpages, ...). By putting \pdfximage > into a box these values are easily available (see pdftex.def). > I would be interested, in which case the exact offset must > be known. to be honest I don't know either -- because I don't use dvipdfm(x). Just trying to satisfy a request by Cho. > Next issues: > * I assume the box (media, crop, ...) is choosen by > the previous \pdfximage? yes exactly > * What is "1" until "4"? > * It is the first until fourth component > of the box retangle, given in the pdf file? they are the values as returned by xpdf -- page->{x1, y1, x2, y2}. I don't know whether xpdf does normalize them, but I hope so. > * The pdf spec says that the box typically has the form: > [ ll_x ll_y ur_x ur_y ] > (PDF spec for 1.6, section "3.8.4 Rectangle") > But there is a note that says that any two diagonally > opposite corners are acceptable and that applications that > process PDF should be prepared to normalize such rectangles. > The question is now, does pdfTeX normalize the rectangle? > This has the advantage that the numbers "1" until "4" also > have the symbolic meaning "ll_x" until "ur_y". Regards, Thanh

3 2

Re: [NTG-pdftex] pdfpagebox
by Thanh Han The 15 Sep '05

15 Sep '05

or perhaps \pdfximagebox or \pdfximagepagebox? Thanh On Thu, Sep 15, 2005 at 08:39:48PM +0200, Pawel Jackowski wrote: > One afterthought. I'd strongly opt for \pdfimagebox instead of > \pdfpagebox. It suits already used naming convention (\pdfimagegamma, > \pdfimagehicolor etc.)... And if someday one will want to implement > > \pdfpageboxwidth3=200mm > \pdfpageboxheight3=280mm > > to set TrimBox of the page being typeset, \pdfpagebox prefix would be > the most suitable %) > > Regards > -- > Pawe/l Jackowski > P.Jackowski(a)gust.org.pl > _______________________________________________ > ntg-pdftex mailing list > ntg-pdftex(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-pdftex

1 0

\pdfximagebbox
by Thanh Han The 15 Sep '05

15 Sep '05

Hi, I added a new primitive to fetch the BBox of a pdf image. sources and djgpp binaries updated at pdftex.sarovar.org Thanh >From README: [...] - extensions for pdf inclusion: - added \pdfpagebox as the default setting for pagebox specification. Value specified to individual use of \pdfximage will override this setting. When set to 0 CropBox will be used as default. Example: ,-------- | \pdfpagebox=1 % use MediaBox as default | \pdfximage {f.pdf} % use MediaBox | \pdfximage cropbox {f2.pdf} % use CropBox `-------- - added \pdfximagebbox to fetch the BBox of a pdf image. The BBox is taken from the pagebox associated with the image. Example: ,-------- | \pdfximage {f.pdf} % CropBox will be use by default | \dimen1=\pdfximagebbox\pdflastximage 1 % fetch x1 from CropBox | \dimen2=\pdfximagebbox\pdflastximage 2 % fetch y1 from CropBox | \dimen3=\pdfximagebbox\pdflastximage 3 % fetch x2 from CropBox | \dimen4=\pdfximagebbox\pdflastximage 4 % fetch y2 from CropBox `--------

1 0

Re: chofs wishes
by Thanh Han The 14 Sep '05

14 Sep '05

Hi, I am looking at what Hans was talking about. Before doing any changes, I would like to ask for explanation of a few things, as pdf inclusion is the speciality of Martin. - we have \pdfforcepagebox (\or pdfoptionalwaysusepdfpagebox) to force the pagebox being use, which can be: (1) media box, (2) crop box, (3) bleed box, (4) trim box, and (5) artbox. - then when a pdf image is included, one can say: mediabox|cropbox|bleedbox|trimbox|artbox to specify the box being used. The corresponding value are @!pdf_pdf_box_spec_media = 0; @!pdf_pdf_box_spec_crop = 1; @!pdf_pdf_box_spec_bleed = 2; @!pdf_pdf_box_spec_trim = 3; @!pdf_pdf_box_spec_art = 4; There are 2 points that might be need re-consideration: 1) to use \pdfforcepagebox one has to say the correct number, which is not that comfortable 2) there is some inconsistency in those above definitions, which requires more work to handle them in pdftoepdf.cc Any idea what can be done here? Thanh On Mon, Sep 12, 2005 at 05:15:38PM +0200, Hans Hagen wrote: > > [...] > > choff had another wish: the ability to determine the size of a graphic, > so we need something: > > \pdfcheckimage [artbox|bleedbox|...] {filename} > > that returns the llx etc in > > \pdfimagebbox == llx lly urx ury > > (or \pdfimagellx \pdfimagelly etc) > > That way pdftex can be used (in dvi mode) with dvipdfmx image inclusion. > > 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 > ----------------------------------------------------------------- >

1 0

new pdftex extensions
by Thanh Han The 14 Sep '05

14 Sep '05

Hi, I uploaded a patch for various new extensions to pdftex to pdftex.sarovar.org/src Support for extensions for paragraph formatting is already included in the beta version of microtype. Many thanks to Robert. Thanh >From README: This is a patch for various extensions to pdftex. How to apply: ~~~~~~~~~~~~~ ,-------- | - this patch applies to the pristine pdftex-1.30.3 sources only; if you have | applied another patch(es) to the sources, please discard them and start from | the fresh ones. | | - how to apply: | | cd /path/to/pdftex-1.30.0-srcdir/src | zcat /path/to/the/gzipped/patch | patch -p1 | ./configure | cd texk/web2c | make pdfetex | | If you want to be careful, try patch with the option '--dry-run' | first to see whether the patch can be applied wihout problems. `-------- Included extensions: ~~~~~~~~~~~~~~~~~~~~ - \pdfinsertht: return the height of an insert; this primitive has similar syntax to \pdftexrevision. Example: ,-------- | \dimen0=\pdfinsertht\footins `-------- - snapping: support for grid typesetting. New primitives: - \pdfsnaprefpoint: insert a whatsit node representing a reference point - \pdfsnapy: insert a whatsit node that cause the position of the ``drawing pen'' to be moved onto a grid. This happens only during shipping phase. Example: after a display math it is difficult to get the next line to be on the grid. With snapping it might look like following: ,-------- | <text before displayed math> | $$ <some math> $$ | \vadjust pre{\pdfsnapy \snapunit plus .8\snapunit minus .2\snapunit} | <text after displayed math> `-------- \snapunit is a dimen, typically it would be \baselineskip. To make it work, there is one thing more: \pdfsnaprefpoint must be inserted into each page, typically in header. Let's call the y-position of this whatsit node Y1. The above example says roughly this: when pdftex reachs the \pdfsnapy node, it can move the drawing pen up and down in range (-.2\snapunit,.8\snapunit) to snap to a point with y-position Y2 so that (Y2-Y1) is a multiple of \snapunit. The \pdfsnapy node must be inserted before the text line following the displayed math, so we use \vadjust pre{...} to insert it (\vajdust with "pre" is an extension of pdftex). - \pdfsnapycomp: insert a whatsit node for snapping compensation The problem with the previous example is that sometimes the space after math is changed too much, while the space before math remains unchanged. Hence the result may look ugly, because the spaces around the math are not proportional. So it is better that the movement after math is somehow compensated into the space before math too. \pdfsnapycomp is for this purpose. The previous example with \pdfsnapycomp will look like: ,-------- | <text before displayed math> | \vadjust{\pdfsnapycomp 500} | $$ <some math> $$ | \vadjust pre{\pdfsnapy \snapunit plus .8\snapunit minus .2\snapunit} | <text after displayed math> `-------- So the skip at \pdfsnapy will be distributed to 50% at \pdfcompsnap and 50% at \pdfsnapy. - some extensions for paragraph formatting: - \pdfadjustinterwordglue: enable adjustment of interword glue - \knbscode -- kern before space code. Syntax is similar to \rpcode. Example: ,-------- | \pdfadjustinterwordglue=1 | \knsbcode\font`\.=200 | <some text> `-------- means that after each period, the interword glue will be increased by an amount of .2em. - \stbscode -- stretch before space code \shbscode -- shrink before space code Similar to \knbscode but apply to the stretch and shrink component of the interword glue. - \pdfprependkern -- enable auto-prepending kern before a char - \knbccode -- kern before char code. Syntax is similar to \rpcode. This is mainly intended for typesetting languagues like French or German where a small kern is required before certain punctuations, eg : ; ? Example: ,-------- | \pdfprependkern=1 | \knbccode\font`\:=200 | <some text> `-------- would cause that a kern of .2em will be prepended before each colon - \pdfappendkern -- enable auto-appending kern after a char - \knaccode -- kern after char code. Syntax is similar to \rpcode. Example: ,-------- | \pdfappendkern=1 | \knaccode\font`\:=200 | <some text> `-------- would cause that a kern of .2em will be append after each colon. Possible usage (from a mail from Robert Schlicht): ,-------- | French typography requires (among other things) guillemets to be | typeset as: | | \guillemotleft\kern0.8em word\kern0.8em\guillemotright `-------- Another application is letterspacing -- a very rough example would look like following: ,-------- | \pdfappendkern=1 | \pdfprependkern=1 | \newcount\n | \n=0 | \loop | \knbccode\font\n=50 | \knaccode\font\n=50 | \advance\n 1 | \ifnum \n < 256 \repeat | | A father had two sons, of whom the eldest was clever | and bright, and always knew what he was about; but the | youngest was stupid, and couldn't learn or understand | ... `-------- - support for subfonts: allow to have a single map entry for each set of subfonts. Example: ,-------- | cyberbit@Unicode@ <cyberbit.ttf PidEid=3,1 `-------- would cause pdftex to read Unicode.sfd to create all needed map entries for subfonts of cyberbit, and when embedding those subfonts pdftex will use the following mappings: 8-bit char in tfm ==> 16-bit charcode in Unicode.sfd ==> glyph in cyberbit.ttf using cmap with PidEid=3,1 The subfont TFM's however must be created manually.

2 1

new pdftex extensions
by Thanh Han The 14 Sep '05

14 Sep '05

I forgot to mention that the djgpp binaries (for pdfetex only) is also available a pdftex.sarovar.org/djgpp Thanh > Hi, > > I uploaded a patch for various new extensions to pdftex to > pdftex.sarovar.org/src > > Support for extensions for paragraph formatting is already > included in the beta version of microtype. Many thanks to > Robert. > > Thanh

1 0

[ pdftex-Feature Requests-431 ] support for changebar
by noreply＠sarovar.org 12 Sep '05

12 Sep '05

Feature Requests item #431, was opened at 2005-09-12 05:24 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=431&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rob MacLeod (rsmacleod) Assigned to: Nobody (None) Summary: support for changebar Initial Comment: There appears to be a fix to the problems in pdflatex with the changebar.sty and I wonder if this fix could become part of the standard release. Without this, each time we do a local update (via teTeX and fink) we have to install the patch and do a manual update. We love using pdflatex but not having changebar capability is a real problem for our grant writing activities. Thanks for your support of the system!!! Cheers, Rob (University of Utah) ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=431&group_id=106

1 0

[ pdftex-Feature Requests-429 ] Make PDF documents accessible to visually imparied.
by noreply＠sarovar.org 12 Sep '05

12 Sep '05

Feature Requests item #429, was opened at 2005-09-11 18:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=429&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Timothy O'Brien (oberon101) Assigned to: Nobody (None) Summary: Make PDF documents accessible to visually imparied. Initial Comment: Adobe Reader has a'reflow' feature that allows visually impaired users to zoom into properly formatted documents and read them without having to move the viewable area back and forth across the page. PDFs made in MikteX eith pdfte are not properly formatted and reflow without interword spacing, redering them unreadable. I contacted the MikteX people and they referred me here. I beleive Scientific Word also uses pdftex with the same result. Any chance this could be fixed? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=429&group_id=106

1 0

[ pdftex-Patches-427 ] Character positioning patch
by noreply＠sarovar.org 11 Sep '05

11 Sep '05

Patches item #427, was opened at 2005-09-11 12:39 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=427&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Nobody (None) Summary: Character positioning patch Initial Comment: Experimental patch increases resolution of /Widths array by 1 fractional digit, makes corrections of type ")-1(" and ")1(" in the TJ array happen much less often, particularily for CM fonts. Gives e. g. 1 % PDF file size shrink for pdfetex web sources compiled into PDF. Rough patch only, not for production. Testing welcome. Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=427&group_id=106

1 0

Re: [NTG-pdftex] pdftex-1.30.2 is broken
by Thanh Han The 02 Sep '05

02 Sep '05

Hi Akira, indeed after applying your patch the problem is gone. Many thanks. Regards, Thanh On Fri, Sep 02, 2005 at 09:36:05AM +0900, Akira Kakuto wrote: > Hi Thanh, > > > After some tries I found that that when shell_escape is set > > to 'f' then there is a problem with the new version but not > > with the old version. However when it is set to 't' then the > > problem went away in both versions. > > > > Please test by applying (temporarily) the following patch to tex.ch: > > Thanks > Akira > > > --- tex.ch.orig Sat Aug 13 20:47:02 2005 > +++ tex.ch Fri Sep 02 09:26:13 2005 > @@ -4967,7 +4967,7 @@ > end; > pool_ptr:=str_start[str_ptr]; {erase the string} > end > - else begin print("disabled"); > + else begin print("disabled"); pool_ptr:=str_start[str_ptr]; > end; > print_char("."); print_nl(""); print_ln; > end;

1 0

pdftex 1.30.3-rc1
by Martin Schröder 02 Sep '05

02 Sep '05

http://sarovar.org/download.php/709/pdftex-1.30.3-rc1.tar.bz2 pdfTex itself is unchanged; the only change is the bugfix for \write18 by Akira & Olaf. Best Martin -- http://www.tm.oneiros.de

1 0

Re: [NTG-pdftex] pdftex-1.30.2 is broken
by Akira Kakuto 02 Sep '05

02 Sep '05

Hi Thanh, > After some tries I found that that when shell_escape is set > to 'f' then there is a problem with the new version but not > with the old version. However when it is set to 't' then the > problem went away in both versions. > Please test by applying (temporarily) the following patch to tex.ch: Thanks Akira --- tex.ch.orig Sat Aug 13 20:47:02 2005 +++ tex.ch Fri Sep 02 09:26:13 2005 @@ -4967,7 +4967,7 @@ end; pool_ptr:=str_start[str_ptr]; {erase the string} end - else begin print("disabled"); + else begin print("disabled"); pool_ptr:=str_start[str_ptr]; end; print_char("."); print_nl(""); print_ln; end;

1 0

Re: [NTG-pdftex] pdftex-1.30.2 is broken
by Thanh Han The 01 Sep '05

01 Sep '05

On Wed, Aug 31, 2005 at 01:27:05PM +0200, Martin Schr?der wrote: > On 2005-08-29 15:38:44 -0700, Thanh Han The wrote: > > it seems that pdftex-1.30.2 is broken. When I run it on a > > rather complex document, it couldn't find some files in the > > current directory or in the standard texmf tree. This > > doesn't happen with 1.30.0. I am sorry that I cannot send > > the files to reproduce the bug. The error happens randomly > > and took me a few hours before I tried to run 1.30.0 against > > it. > > Do you have more details? Has anybody else seen the same > problems? Radhakrisnan has experienced the same problem on Mac OSX, with pdftex binaries built from sources. Plus another guy with Linux Redhat i386. I have been gazing at the diff in sources in 1.30.0 and 1.30.2, but couldn't find anything that seem suspicious. I will try to make some set of log files from kpathsea for comparison. Maybe Olaf or Karl can find something wrong. Thanh

2 1

Re: [NTG-pdftex] pdftex-1.30.2 is broken
by Thanh Han The 01 Sep '05

01 Sep '05

Hi Martin, I uploaded the log files to pdftex.sarovar.org/misc/log.zip After some tries I found that that when shell_escape is set to 'f' then there is a problem with the new version but not with the old version. However when it is set to 't' then the problem went away in both versions. Maybe the old version should fail as well and this is not a new bug but a bug discovery in the old version :) kpathsea experts probably can tell more what went wrong. Thanh On Thu, Sep 01, 2005 at 05:24:24PM +0200, The Thanh Han wrote: > On Wed, Aug 31, 2005 at 01:27:05PM +0200, Martin Schr?der wrote: > > On 2005-08-29 15:38:44 -0700, Thanh Han The wrote: > > > it seems that pdftex-1.30.2 is broken. When I run it on a > > > rather complex document, it couldn't find some files in the > > > current directory or in the standard texmf tree. This > > > doesn't happen with 1.30.0. I am sorry that I cannot send > > > the files to reproduce the bug. The error happens randomly > > > and took me a few hours before I tried to run 1.30.0 against > > > it. > > > > Do you have more details? Has anybody else seen the same > > problems? > > Radhakrisnan has experienced the same problem on Mac OSX, > with pdftex binaries built from sources. Plus another guy > with Linux Redhat i386. > > I have been gazing at the diff in sources in 1.30.0 and > 1.30.2, but couldn't find anything that seem suspicious. > > I will try to make some set of log files from kpathsea for > comparison. Maybe Olaf or Karl can find something wrong. > > Thanh

1 0

pdftex-1.30.2 is broken
by Thanh Han The 31 Aug '05

31 Aug '05

Hi Martin, it seems that pdftex-1.30.2 is broken. When I run it on a rather complex document, it couldn't find some files in the current directory or in the standard texmf tree. This doesn't happen with 1.30.0. I am sorry that I cannot send the files to reproduce the bug. The error happens randomly and took me a few hours before I tried to run 1.30.0 against it. I know that it makes little sense to talk about the bug without the files needed to reproduce the bug. However I think it's good to have the problem reported, just for case someone runs into similar problems. For the moment I will make my patches againts 1.30.0. Thanh

2 1

[ pdftex-Feature Requests-421 ] \pdf shell escape addition
by noreply＠sarovar.org 27 Aug '05

27 Aug '05

Feature Requests item #421, was opened at 2005-08-26 20:32 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106 Category: None Group: None Status: Open >Resolution: Accepted Priority: 5 Submitted By: ivo welch (iaw4) >Assigned to: Taco Hoekwater (taco) Summary: \pdf shell escape addition Initial Comment: I would humbly request that in addition add to \write18 ('--shell-escape'), you add a new command, say \input18 (or \pdftexshellinput18), which like \write18 executes a system() command on its argument, but which then pushes the stdout output from this shell command into the stdin stream that TeX is processing. (no, writing to a file and then inputting it does not do the job.) I cannot contribute to the code base of TeX, which seems like black magic to me. But I can offer $300 for this facility. If someone was planning to spend the time to do this anyway, this may push him/her over the margin. However, it is important to me that this enters the standard feature set of pdftex, so that it will persist through future versions, so this would be part of the bargain here. regards, /ivo welch ---------------------------------------------------------------------- >Comment By: Taco Hoekwater (taco) Date: 2005-08-27 09:01 Message: Logged In: YES user_id=1608 I have an idea on how to do this, so I've assigned it to myself ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106

1 0

[ pdftex-Feature Requests-421 ] \pdf shell escape addition
by noreply＠sarovar.org 26 Aug '05

26 Aug '05

Feature Requests item #421, was opened at 2005-08-26 18:32 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: ivo welch (iaw4) Assigned to: Nobody (None) >Summary: \pdf shell escape addition Initial Comment: I would humbly request that in addition add to \write18 ('--shell-escape'), you add a new command, say \input18 (or \pdftexshellinput18), which like \write18 executes a system() command on its argument, but which then pushes the stdout output from this shell command into the stdin stream that TeX is processing. (no, writing to a file and then inputting it does not do the job.) I cannot contribute to the code base of TeX, which seems like black magic to me. But I can offer $300 for this facility. If someone was planning to spend the time to do this anyway, this may push him/her over the margin. However, it is important to me that this enters the standard feature set of pdftex, so that it will persist through future versions, so this would be part of the bargain here. regards, /ivo welch ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106

1 0

[ pdftex-Feature Requests-421 ] \pdf
by noreply＠sarovar.org 26 Aug '05

26 Aug '05

Feature Requests item #421, was opened at 2005-08-26 18:32 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: ivo welch (iaw4) Assigned to: Nobody (None) Summary: \pdf Initial Comment: I would humbly request that in addition add to \write18 ('--shell-escape'), you add a new command, say \input18 (or \pdftexshellinput18), which like \write18 executes a system() command on its argument, but which then pushes the stdout output from this shell command into the stdin stream that TeX is processing. (no, writing to a file and then inputting it does not do the job.) I cannot contribute to the code base of TeX, which seems like black magic to me. But I can offer $300 for this facility. If someone was planning to spend the time to do this anyway, this may push him/her over the margin. However, it is important to me that this enters the standard feature set of pdftex, so that it will persist through future versions, so this would be part of the bargain here. regards, /ivo welch ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106

1 0

Re: [pdftex] pdftex 1.30.2
by Thomas Esser 25 Aug '05

25 Aug '05

> The pdfTeX team is happy to announce the release of a new stable version: Hm... pdftex.ch seems to be unchanged (-rc1): $ tar xf /t/not_ctan/pdftex-1.30.2.tar.bz2 -C /build $ grep 1.30.2 /build/pdftex-1.30.2/src/texk/web2c/pdftexdir/pdftex.ch @d pdftex_version_string=='-1.30.2-rc1' {current \pdfTeX\ version} ^^^^ !!! $ md5sum /t/not_ctan/pdftex-1.30.2.tar.bz2 4b0480114a4e1fc38b555a5a1b697174 /t/not_ctan/pdftex-1.30.2.tar.bz2 $ ls -l /t/not_ctan/pdftex-1.30.2.tar.bz2 -rw-r--r-- 1 te users 3353139 2005-08-25 20:16 /t/not_ctan/pdftex-1.30.2.tar.bz2 Thomas

2 1

pdftex 1.30.2-rc1
by Martin Schröder 23 Aug '05

23 Aug '05

http://sarovar.org/download.php/700/pdftex-1.30.2-rc1.tar.bz2 The only change is the latest patches from Olaf and Thomas in TexLive; I prefer a new release to silently updating the archives (and all links to them and ctan and ...). Olaf & Thomas, please have a look at the rc. :-} Best Martin -- http://www.tm.oneiros.de

3 3

pdftex 1.30.1-rc1
by Martin Schröder 19 Aug '05

19 Aug '05

http://sarovar.org/download.php/694/pdftex-1.30.1-rc1.tar.bz2 The only changes are xpdf 3.01 and kpathsea/web2c updates from TL. Thomas, please check the xpdf update; especially because I updated xpdf/depend.mk Best Martin -- http://www.tm.oneiros.de

1 1

[ pdftex-Patches-415 ] various extensions and fixes
by noreply＠sarovar.org 19 Aug '05

19 Aug '05

Patches item #415, was opened at 2005-08-19 07:09 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=415&group_id=106 Category: Primitives Group: v1.30.0 Status: Open Resolution: None Priority: 5 Submitted By: The Thanh Han (hanthethanh) Assigned to: Martin Schröder (oneiros) Summary: various extensions and fixes Initial Comment: This is a patch for various experimental extensions: - \pdfinsertht: return the height of an insert (requested by Hans); this has similar syntax to \pdftexrevision. - do not fail when \pdfobj is used with an invalid object number (requested by Hans) - snapping: support for grid typesetting -- see snap.txt for details - kern before space: allow changing interword glues in a flexible way and inserting a kern before certain characters -- see kern-before-interword-glue.txt for details The notes in snap.txt and kern-before-interword-glue.txt are from email correspondence with people interested in; hence these notes are somewhat informal, inaccurate or out-of-date. How to apply: ~~~~~~~~~~~~~ cd /path/to/pdftex-1.30.0-srcdir/src/texk patch -p1 < /path/to/pdftex-20050818.patch cd web2c make pdfetex ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=415&group_id=106

1 0

Xpdf 3.01 - a PDF viewer for X
by Martin Schröder 18 Aug '05

18 Aug '05

----- Forwarded message from "Derek B. Noonburg" <derekn(a)foolabs.com> ----- Date: 17 Aug 2005 21:51:23 -0000 Message-ID: <20050817215123.11144.qmail(a)foolabs.com> To: martin(a)oneiros.de From: "Derek B. Noonburg" <derekn(a)foolabs.com> Subject: ANNOUNCE: Xpdf 3.01 - a PDF viewer for X 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: * Added the continuous view mode, including the '-cont' switch and the 'continuousView' config file option. * At high zoom levels, don't rasterize the entire page - this avoids problems running out of memory. * Added "search backward" and "match case" options to the find dialog. * Support explicitly masked images and soft masked images. See the `CHANGES' file for a complete list of changes. Source (C++ and C) is available, and it should be fairly easy to compile for UNIX, VMS, OS/2, and Win32. More information, source code, and precompiled binaries are on the xpdf web page and ftp site: http://www.foolabs.com/xpdf/ ftp://ftp.foolabs.com/pub/xpdf/ For information on commercial licensing and consulting, please see the Glyph & Cog web site: http://www.glyphandcog.com/ ----- End forwarded message ----- I'll have a look and might make a new release (1.30.1) together with the latest changes to web2c. Best Martin -- http://www.tm.oneiros.de

1 0

Re: [NTG-pdftex] url links in included pdf documents,
by Thanh Han The 16 Aug '05

16 Aug '05

there was a patch to copy links in embedded pdf's, but it was not integrated to pdf. The patch was not that simple and none of pdftex maintainers (including me) was willing to take care of it. I think a compromise would be allowing certain kind of annotation to be copied, for example URI. But I cannot make any promise, sorry. Regards, Thanh On Wed, Aug 10, 2005 at 07:56:42AM +0200, Janko Hauser wrote: > Hello, I have the need to include pdf pages as backgrounds into a > latex document. I would like to keep the url-links in these > background pdf's. Searching the mailinglists it turns out, that > pdftex does strip all links from included pdf's. Has this changed in > recent versions? How should one proceed to look for this in the code > of pdftex? > > With regards, > > __Janko Hauser > > _______________________________________________ > ntg-pdftex mailing list > ntg-pdftex(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-pdftex

2 1

Re: [NTG-pdftex] redundant resources
by Thanh Han The 16 Aug '05

16 Aug '05

Hi Hans, does it relate to the ToUnicode object only, or something else as well? I think the ToUnicode object can be generated by pdftex, as pdftex knows the current encoding vector and can find out the corresponding unicode for a given glyph name by looking into the AGL? It would also save some space, as fonts having the same encoding vector (eg 8r.enc) can share a single ToUnicode object. But I am not sure, have to recheck the ToUnicode description. Postponing the object refered by \pdffontattr is not that easy to do, as pdftex does no parsing of the parameter of \pdffontattr (like in case of many other parameters). Thanh On Mon, Aug 15, 2005 at 01:04:07PM +0200, Hans Hagen wrote: > Hi, > > There are situations where unused resources can end up in a pdf file; > think for instance of a font system that sets up tounicode vector > inclusion. For practical purposes, one needs to have a font loaded > before the document preamble is scanned. If not, it is impossible to > deal with certain dimensions. So, it that case, we have something > > \pdffontattr\font{/ToUnicode ... 0 R} > > But imagine that we never use that font. If the rest of the document > fonts use the same vector, this is no problem, but when we switch to > another font encoding, we end up with a non used to unicode vector. Or > think of docs with only graphics (or other pdf pages) where no such > vector is needed. > > Because the object reference ... 0 R is not seen, pdftex cannot decide > either or not to include the object, so we need to use \immediate\obj > which result sin the non wanted entry. A solution is > > \pdffontvector <obj num> > > but a more generic solution is > > \pdffontattr\font{/ToUnicode ... \refobjnum <objnum>} > > which will tag the object (number) as being used but only when the font > desciption object is really flushed (so \refobjnum fullfils a signal > function) > > this means that a (later) \pdfobj{...} will not be flushed when it is > not really refered > > 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 > ----------------------------------------------------------------- > > _______________________________________________ > ntg-pdftex mailing list > ntg-pdftex(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-pdftex

2 1