- ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-856 ] build.sh can't handle pathnames with spaces
by noreply＠sarovar.org 14 Aug '07

14 Aug '07

Bugs item #856, was opened at 2007-08-14 09:48 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=856&group_id=106 Category: Build process >Group: v1.40.4 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Francky Leyn (leyn) Assigned to: Martin Schröder (oneiros) Summary: build.sh can't handle pathnames with spaces Initial Comment: Dear, I want to compile pdftex for cygwin. I untarred the distribution in /cygdrive/c/Document and Settings/Francky Leyn/My Documents/LaTeX leyn@newyork ~/LaTeX/pdftex-1.40.5 $ ./build.sh ... build.sh stops with the following error: configure: error: can not run /cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub The file exists and is executable: $ ls -lh "/cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub" -rwx------+ 1 leyn None 32K Jul 31 19:00 /cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub The file /cygdrive/c/Documents doesn't exist of course and that is why buid.sh stops its execution. Could the scripts be modified so that they can handle spaces? Best regards, Francky Leyn ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-08-14 10:50 Message: Logged In: YES user_id=421 This needs a new configure script; I've pushed this upstream (to TeXlive). ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=856&group_id=106

1 0

[ pdftex-Bugs-856 ] build.sh can't handle pathnames with spaces
by noreply＠sarovar.org 14 Aug '07

14 Aug '07

Bugs item #856, was opened at 2007-08-14 09:48 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=856&group_id=106 Category: Build process Group: None Status: Open Resolution: None Priority: 5 Submitted By: Francky Leyn (leyn) Assigned to: Martin Schröder (oneiros) Summary: build.sh can't handle pathnames with spaces Initial Comment: Dear, I want to compile pdftex for cygwin. I untarred the distribution in /cygdrive/c/Document and Settings/Francky Leyn/My Documents/LaTeX leyn@newyork ~/LaTeX/pdftex-1.40.5 $ ./build.sh ... build.sh stops with the following error: configure: error: can not run /cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub The file exists and is executable: $ ls -lh "/cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub" -rwx------+ 1 leyn None 32K Jul 31 19:00 /cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub The file /cygdrive/c/Documents doesn't exist of course and that is why buid.sh stops its execution. Could the scripts be modified so that they can handle spaces? Best regards, Francky Leyn ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=856&group_id=106

1 0

[ pdftex-Patches-474 ] Use dynamically linked poppler library instead of xpdf code
by noreply＠sarovar.org 12 Aug '07

12 Aug '07

Patches item #474, was opened at 2006-01-30 17:53 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=474&group_id=106 Category: PDF inclusion Group: v1.30.0 Status: Open >Resolution: Accepted Priority: 6 Submitted By: Frank Küster (frank) Assigned to: Martin Schröder (oneiros) Summary: Use dynamically linked poppler library instead of xpdf code Initial Comment: This has already been applied and tested in Debian and Ubuntu, but we suggest to apply it upstream. There are a few things to do, however, as Martin already pointed out to me in a private mail. I paraphrase the main points: - the pdftex distribution should not ship libpoppler. Instead it should be possible to switch from xpdf to libpoppler using autoconf magic, if libpoppler headers are installed. This needs some coding work - We need a common API for xpdf and poppler. This is the tricky part, because the very reason for poppler's existence is that the xpdf developer, Derek Noonburg, refuses any patches that would lead to a shared library. As Martin said, "for the beginning, a header file with a couple of #ifdef'ed definitions should be enough". I'm going to subscribe to the pdftex devel list soon, but am not yet subscribed currently. ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-08-10 15:40 Message: Logged In: YES user_id=421 HEAD (r228) has now a layer between pdftex and xpdf. Please comment. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-05-08 18:54 Message: Logged In: YES user_id=421 Just an update: SUSE has also started switching to poppler. My idea is to first add an abstraction layer for xpdf/poppler/... and then add the autofoo stuff. ---------------------------------------------------------------------- Comment By: Frank Küster (frank) Date: 2006-08-14 21:20 Message: Logged In: YES user_id=3360 Hi Martin, this is clearly post-1.40, I agree. I have not worked on any autofoo stuff, and I won't be able to do that soon (instead, I try to integrate pdftex-1.40 into teTeX 3.0 which proved to be non-trivial). Regards, Frank ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-08-13 22:02 Message: Logged In: YES user_id=421 Frank, have you done any further work on this? I just had a first look at integrating poppler and see a very different use of configure... :-{ Also your diff only patches the sources, but not the autofoo-stuff. What I want is: - a distribution of poppler in src/libs, which can be used instead of xpdf - a way to switch bewteen xpdf and poppler via configure - for poppler to be able to switch between static and dynamic via configure - and finally, a header file abstracting poppler/xpdf would be nice, but is not really needed, as poppler/xpdf are only used by two source files. Best Martin ---------------------------------------------------------------------- Comment By: Frank Küster (frank) Date: 2006-02-13 08:58 Message: Logged In: YES user_id=3360 I agree that this is something to think over and check very well, so better not push it into 1.40. But I'd appreciate if someone could answer my mail to ntg-pdftex regarding the autoconf setup in pdftex, or if you could tell me whom to ask specifically if nobody among the active developers knows about it. See you in Berlin, Frank ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-02-13 01:50 Message: Logged In: YES user_id=421 I've attached the patch by Frank from http://www.ntg.nl/pipermail/ntg-pdftex/2006-February/001993.html ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-02-13 01:46 Message: Logged In: YES user_id=421 This is too late for 1.40, so I'll postpone it. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=474&group_id=106

3 2

make depend :-(
by Martin Schröder 10 Aug '07

10 Aug '07

Hi, I just tried a "make depend" in pdftexdir and found it broken; and my knowlegde of make/sh/grep/sed/autofoo/... is not sufficient to fix it. If some kind soul here could fix it, I'd be grateful. Best Martin PS: And "make depend" in libs/xpdf/xpdf is also not producing the expected result... :-(

1 0

Re: [NTG-pdftex] [pdftex] PTEX.FileName contains file system information
by Hans Hagen 06 Aug '07

06 Aug '07

Stephan Hennig wrote: > But I'm concerned about pdfTeX unintentionally revealing: > > (a) file naming conventions, > (b) infrastructure information, > (c) identity information. i see not problem with adding a \ptexinfo=0|1 with 1 being the default (since we don't want to break downward compatibiity). We can put it on the wishlist 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 -----------------------------------------------------------------

4 7

[ pdftex-Patches-846 ] \pdfsuppressptexinfo
by noreply＠sarovar.org 06 Aug '07

06 Aug '07

Patches item #846, was opened at 2007-08-06 12:25 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=846&group_id=106 Category: Primitives >Group: v1.50.0 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Heiko Oberdiek (oberdiek) >Assigned to: Martin Schröder (oneiros) Summary: \pdfsuppressptexinfo Initial Comment: Subject: \pdfsuppressptexinfo Date: 2007/08/06 Author: Heiko Oberdiek The patch is based on pdftex-1.40.5. There is a discussion in the mailing lists (ntg-)pdftex about suppressing entries "/PTEX.*". The patch tries to summarize the discussion and provides an implementation. New primitive of type integer: \pdfsuppressptexinfo The number is interpreted as bit field (Martin Schröder): Bit 0: /PTEX.Fullbanner Bit 1: /PTEX.FileName Bit 2: /PTEX.PageNumber Bit 3: /PTEX.InfoDict Default is 0, all entries are written. pdftex.web.diff patches pdftexdir/pdftex.web pdftoepdf.cc.diff patches pdftexdir/pdftoepdf.cc Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-08-06 13:21 Message: Logged In: YES user_id=421 This patch will be included in the upcoming 1.50 ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=846&group_id=106

1 0

[ pdftex-Patches-846 ] \pdfsuppressptexinfo
by noreply＠sarovar.org 06 Aug '07

06 Aug '07

Patches item #846, was opened at 2007-08-06 12:25 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=846&group_id=106 Category: Primitives Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Heiko Oberdiek (oberdiek) Assigned to: Nobody (None) Summary: \pdfsuppressptexinfo Initial Comment: Subject: \pdfsuppressptexinfo Date: 2007/08/06 Author: Heiko Oberdiek The patch is based on pdftex-1.40.5. There is a discussion in the mailing lists (ntg-)pdftex about suppressing entries "/PTEX.*". The patch tries to summarize the discussion and provides an implementation. New primitive of type integer: \pdfsuppressptexinfo The number is interpreted as bit field (Martin Schröder): Bit 0: /PTEX.Fullbanner Bit 1: /PTEX.FileName Bit 2: /PTEX.PageNumber Bit 3: /PTEX.InfoDict Default is 0, all entries are written. pdftex.web.diff patches pdftexdir/pdftex.web pdftoepdf.cc.diff patches pdftexdir/pdftoepdf.cc Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=846&group_id=106

1 0

Re: [NTG-pdftex] pdftosrc from Tex Live 2007 packages
by Frank Küster 31 Jul '07

31 Jul '07

Hi, pdfTeX contains sources for pdftosrc and ttf2afm, but "make all" in pdftexdir does not compile them: # pdftex_bin = pdftex ttf2afm pdftosrc pdftex_bin = pdftex A user of TeXLive in Debian complained that pdftosrc is missing, and at a first glance I thought that the lines above were all that needs to be changed. But then I found that ttf2afm is built in TeXLive nevertheless, by some other dependencies probably (it seems to be built from "make ctangle", hm, strange). Is there a rationale for enabling one but not the other? You don't know, by chance, the clean way to enable pdftosrc, don't you? Interestingly, the manpage for pdftosrc is still there: "R (Chandra) Chandrasekhar" <chandra(a)ee.uwa.edu.au> wrote: > File Path Package > ===========================================================-================= > /usr/share/man/man1/pdftosrc.1.gz texlive-extra-utils > > but no indication of an executable. TIA, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)

4 4

[ pdftex-Feature Requests-316 ] cmap, pdftex, distiller
by noreply＠sarovar.org 30 Jul '07

30 Jul '07

Feature Requests item #316, was opened at 2005-03-21 17:28 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=316&group_id=106 Category: None Group: None Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Michael Zedler (zedler) Assigned to: Nobody (None) Summary: cmap, pdftex, distiller Initial Comment: Hello, In order to make pdf files searchable for non-latin characters (e.g. polytonic greek) one needs to include so-called cmap files into the pdf. As far as I know such a pdf can be generated by either 1) using pdflatex with cmap.sty and an appropriate .cmap file 2) using dvips+Distiller (not ps2pdf) Adobe Distiller seems to contain extra logic to automatatically generate appropriate cmaps and also translate ligatures into single-letter cmap entries. Generating cmap files by hand is pretty tedious, in particular if the encoding is automatically generated by e.g. a tool like otftotfm (non-standard ligatures are automatically but into free encoding slots; depending on the font version the assignment varies). Thus for the pdftex approach it'd be very nice to have this automatism, too. Possible? Michael ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-07-30 13:45 Message: Logged In: YES user_id=710 This feature has been implemented in pdftex (patch #580). ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=316&group_id=106

1 0

[ pdftex-Feature Requests-316 ] cmap, pdftex, distiller
by noreply＠sarovar.org 30 Jul '07

30 Jul '07

Feature Requests item #316, was opened at 2005-03-21 16:28 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=316&group_id=106 Category: None Group: None >Status: Closed Resolution: None Priority: 5 Submitted By: Michael Zedler (zedler) Assigned to: Nobody (None) Summary: cmap, pdftex, distiller Initial Comment: Hello, In order to make pdf files searchable for non-latin characters (e.g. polytonic greek) one needs to include so-called cmap files into the pdf. As far as I know such a pdf can be generated by either 1) using pdflatex with cmap.sty and an appropriate .cmap file 2) using dvips+Distiller (not ps2pdf) Adobe Distiller seems to contain extra logic to automatatically generate appropriate cmaps and also translate ligatures into single-letter cmap entries. Generating cmap files by hand is pretty tedious, in particular if the encoding is automatically generated by e.g. a tool like otftotfm (non-standard ligatures are automatically but into free encoding slots; depending on the font version the assignment varies). Thus for the pdftex approach it'd be very nice to have this automatism, too. Possible? Michael ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2007-07-30 11:45 Message: Logged In: YES user_id=710 This feature has been implemented in pdftex (patch #580). ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=316&group_id=106

1 0