- ntg-pdftex - NTG Mailing Lists

\nofontnotfounderror patch
by Taco Hoekwater 17 Sep '07

17 Sep '07

Hi, Attached is a patch for pdftex 1.50 (current trunk) that introduces a new integer parameter named \nofontnotfounderror. If this parameter is non-zero, then (pdf)tex will not complain about font metric files that are not found, but silently skip the font assignment, making the requested csname \ifx-equal to \nullfont. The purpose is to allow macro programmers a way to gracefully recover from a missing or differently named font. I am aware there is a trick that uses \batchmode to test for font existance, but the downside of that is that it calls TeX's error() routine, which clobbers the executable's return value. That makes it a no-no in "make"-like environments where the return value of TeX is checked to decide on further actions. This functionality will also be added to the next versions of xetex and luatex (that's why the name does not start with \pdf...). % simple example usage \def\testfont#1{% \font\junk=#1 \ifx\junk\nullfont \message{Font #1 not found} \else \message{Font #1 found} \fi } {\nofontnotfounderror=1 \testfont{cmr-junk} } \bye Best wishes, Taco PS Martin, what is the status on the trackers? I did not know whether to use sarovar or to enable the one on supelec, that's why it is now on the mailing list.

2 2

[ pdftex-Bugs-861 ] including encrypted pdf
by noreply＠sarovar.org 09 Sep '07

09 Sep '07

Bugs item #861, was opened at 2007-09-07 10:35 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=861&group_id=106 Category: xpdf Group: v1.40.5 Status: Open Resolution: Accepted Priority: 5 Submitted By: Herbert Voss (voss) Assigned to: Martin Schröder (oneiros) Summary: including encrypted pdf Initial Comment: when i insert a page of the http://tug.org/texshowcase/en_gb_eclipse_114.pdf with \documentclass{article} \usepackage{graphicx} \begin{document} \includegraphics[page=1]{en_gb_eclipse_114} \end{document} I'll get an empty page with pdftex 1.40.5 With version 1.40.3 (xpdf 3.01) everything is fine. There is no difference in both logfiles. ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-09-09 20:44 Message: Logged In: YES user_id=421 It also works with 1.40.5 and libs/xpdf from 1.40.3, so the problem is either in xpdf or in our binding. We have contacted Derek. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=861&group_id=106

1 0

[ pdftex-Bugs-861 ] including encrypted pdf
by noreply＠sarovar.org 07 Sep '07

07 Sep '07

Bugs item #861, was opened at 2007-09-07 10:35 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=861&group_id=106 Category: xpdf >Group: v1.40.5 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Herbert Voss (voss) Assigned to: Martin Schröder (oneiros) Summary: including encrypted pdf Initial Comment: when i insert a page of the http://tug.org/texshowcase/en_gb_eclipse_114.pdf with \documentclass{article} \usepackage{graphicx} \begin{document} \includegraphics[page=1]{en_gb_eclipse_114} \end{document} I'll get an empty page with pdftex 1.40.5 With version 1.40.3 (xpdf 3.01) everything is fine. There is no difference in both logfiles. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=861&group_id=106

1 0

[ pdftex-Bugs-861 ] including encrypted pdf
by noreply＠sarovar.org 07 Sep '07

07 Sep '07

Bugs item #861, was opened at 2007-09-07 08:35 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=861&group_id=106 Category: xpdf Group: None Status: Open Resolution: None Priority: 5 Submitted By: Herbert Voss (voss) Assigned to: Martin Schröder (oneiros) Summary: including encrypted pdf Initial Comment: when i insert a page of the http://tug.org/texshowcase/en_gb_eclipse_114.pdf with \documentclass{article} \usepackage{graphicx} \begin{document} \includegraphics[page=1]{en_gb_eclipse_114} \end{document} I'll get an empty page with pdftex 1.40.5 With version 1.40.3 (xpdf 3.01) everything is fine. There is no difference in both logfiles. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=861&group_id=106

1 0

Re: [NTG-pdftex] [pdftex] Forbidding hyphenation at end of page.
by Martin Schröder 24 Aug '07

24 Aug '07

2007/8/24, John R. Culleton <john(a)wexfordpress.com>: > TeX and LaTeX have no effective mechanism for forbidding hyphenation > at the end of a page. Presumably this applies to pdftex, Context etc. > as well. The base TeX program is frozen forever, but pdftex is not. > It conintues to evolve with addons. This could be such an addon, but > it would require surgery to the pagemaking code and possibly the > hyphenation code. It could be in the nature of an increased penalty > or a binary switch. It would also most likely require interaction between the pagebuilder and the parbuilder (if you really want to forbid it), and this makes it hard. > Is such an addon within the charter of the pdftex wizards (Han The > Thanh, Taco Hoekwater etc.)? It's definitely not something for pdftex but for luatex. Best Martin

1 0

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by Akira Kakuto 20 Aug '07

20 Aug '07

Hi David, > Thanks! That is a real life saver for me! As compared with > TeXlive2007, I suppose I will have to regenerate the formats, correct? Yes, you have to regenerate formats. Best regards, Akira

1 0

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by Akira Kakuto 20 Aug '07

20 Aug '07

Hi David, > So can we have the one-liner extending the number of open files to > 2048? And as a bonus point, can somebody tell me how I get a working > Windows executable once this has been done in the source? (1) Plese get ftp://akagi.ms.u-tokyo.ac.jp/pub/TeX/win32/pdftex-w32.tar.gz and expand the tarball in a suitable temporary directory. (2) Copy "pdftex.dll" and "kpathsea356.dll" into bin/win32 of texlive. (3) Copy pdftex.pool into the directory for pool files of texlive. (4) Throw away all files in the tarball except for the above three. Note that pdftex.pool must be replaced, because pdfTeX version is different from TeXLive 2007. Best regards, Akira

2 1

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by Reinhard Kotucha 20 Aug '07

20 Aug '07

Philip TAYLOR writes: > [...] there are ten million computers in the world running *X, and > each and every one of them has different libraries, different > compilers, different versions, different this, different that, > different everything. I'm using Gentoo Linux, a source code distribution, and I'm glad to see how good it works. I'm not a C programmer and I'll certainly have a problem if not everything compiles without manual interaction. But everything works perfectly. Yes, there are many different libraries with different version numbers. But it doesn't matter because programs usually know which (versions of) libraries they need. There are different versions of .DLL files on Windows too, unfortunately the file name doesn't contain the version number. If people always use standard tools to install software, the installer certainly looks into the .DLL file and prevents a recent version from being replaced by an older one. But there are people you called monkeys in a previous mail. And there are many monkeys in the Windows world. I often get CDs containing data sheets. They usually contain PDF files. Some of them come with a toc file in HTML, but some require that you have to install them, whatever this means. Some even require that you have admin rights. These CDs go into the trash can immediately. Either they want to break my system deliberately, what I don't believe because they want me to buy their products, or they are what you call monkeys. I doubt that anybody who doesn't know what an admin account is good for is able to install software on my system properly. There are probably monkeys in the UNIX world too, but I think that the fact that shared libraries provide the version number in the file name is much more robust than the Windows approach (which is definitely not monkey proof). What you said about UNIX was an assumption. If you have some time, why not install a Linux system, maybe on a virtual machine, and play with it? You'll see that all your assumptions are wrong. There are many Linux distributions available but I think that Gentoo is the best one for you because, as far as I know you, it's imortant for you to know how things work. You have to do things manually while other distributions provide menus. But you immediately see how things work. I really hope that you find some time to play with it. > Yes, there is a ?registry? tweak that will stop explorer from > trying to enumerate remote (networked) files; it is a pain, and I > completely agree. When I find the reference, I'll forward it to > you (and your administrators !). That would be nice. The problem exists on XP but not on 9x. My first assumption was that it is a DNS problem but specifying the IP number instead of the hostname didn't help. I now also believe that there is something wrong either in the network setup or the registry. A colleague already looked into the network setup and found a few improvements but the main problem still exists. Fabrice said that the registry is a distributed database, so I assume that I can't make a backup before I edit it. Hence, I'm interested in some hints from people who know what has to be changed. Making own experiments is too dangerous. I'm on vacation at the moment, but I'll come back to the issue later. > P.S. About as "intuitive" as [con]cat[enating] a file with > nothing in order simply to see it on the screen ... You *can* [ab]use 'cat' to print a file to screen but the UNIX tool designed for this task is 'more' and not 'cat'. There is also 'less', which allows you to scroll backwards but it's probably not installed on every UNIX system. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------

4 9

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by David Kastrup 19 Aug '07

19 Aug '07

Philip TAYLOR <Philip-and-LeKhanh(a)Royal-Tunbridge-Wells.Org> writes: > Agreed. I would also add that, as a non-member of the NTG-PdfTeX > list, all of my postings /must/ have been approved by the moderator. > I can therefore only think that the moderator regards them as being > sufficiently on-topic to allow them onto the list, even if Martin > disagrees. I have encountered mailing lists with a heavy-handed moderator like that. On most mailing lists, however, the moderator does not weed out discussions between dissenting adults but rather makes sure that no off-topic or deficient material (spam, sometimes completely inappropriate postings by newcomers, oversized attachments, and so on) gets on. It is a heavy-handed move to actually censor postings, not usually done lightly or without warning, and a warning takes work. Please don't confuse a lack of censorship with personal approval: that is heaping more responsibility/blame on list moderators than they deserve. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum

1 0

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by David Kastrup 19 Aug '07

19 Aug '07

Philip TAYLOR <Philip-and-LeKhanh(a)Royal-Tunbridge-Wells.Org> writes: > David Kastrup wrote: > >> It must be mentioned that one actually needs single-iteration >> for-loops for almost any useful variable manipulation. Quite >> intuitive. > > P.S. About as "intuitive" as [con]cat[enating] a file with > nothing in order simply to see it on the screen ... Nobody does that in Unix and it would not change anything. The Cygwin "cat", in contrast, contains some hackery to interpret ANSI color sequences on Windows, since Windows, surprise, surprise, does not offer a standard-compliant console. In short: you are complaining about a workaround for a deficiency limited to Windows. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum

1 0

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by Martin Schröder 19 Aug '07

19 Aug '07

2007/8/19, Philip TAYLOR <Philip-and-LeKhanh(a)royal-tunbridge-wells.org>: > Martin, it was your "rant" [1] (Hans's terminilogy) that triggered > this debate; you are the last person to be in a position to That wasn't a rant (and it was with tongue in cheek), that was a try to state a fact that David didn't make clear: That his problems (and his fix) where on Windows. This could all have been over sooner if David had given more information up front. If you want to continue this discussion, fine; but please leave ntg-pdftex out of this. Best Martin

2 1

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by Thanh Han The 18 Aug '07

18 Aug '07

fwiw, I find msys http://www.mingw.org/msys.shtml a very useful thing anytime I need to do any shell scripting on windows. Thanh On Sat, Aug 18, 2007 at 11:48:29AM +0200, David Kastrup wrote: > But this does not hold a candle to programming cmd.exe. Something > like > > for i in /opt /usr/local /opt/* /usr/local/* > do > if test -d "$i"/software > then > cd "$i" > subdir="$i" > break > fi > done > > becomes (in a batch file, on the command line it looks different) > > for /D %%I in (C:\ D:\ C:\* D:\*) do ( > if exist %%I\software\NUL ( > %%~dI > cd %%~pnI > set subdir=%%I > goto found > ) > ) > > [...]

3 2

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by Thanh Han The 18 Aug '07

18 Aug '07

On Sat, Aug 18, 2007 at 02:32:03PM +0200, David Kastrup wrote: > > [...] > > > I have written some applications that are used on both *x and > > windows. While it is possible to have a build environment on > > Windows (using Msys), it has been much easier to use a > > cross-compiler under linux, e.g., > > <http://www.stats.ox.ac.uk/pub/Rtools/>. It would be interesting to > > try using these tools to create a build-win32.sh for pdftex. > > A working cross compilation environment would help a _lot_. since the very beginning of pdftex I used to cross-compile pdftex binaries using the following cross-compilers: djgpp mingw32 gnuwin32 (and recently also gcc for linux ppc) Then I didn't need to do that anymore, so I stopped being interested in this issue. But until now I can still cross-compile at least djgpp from the latest pdftex sources. However I heard from Hans that djgpp binaries are not that fast as those compiled by mingw32. IIRC Taco is using mingw32 to build luatex binaries for windows, so he may have more useful input. Anyway, if anyone needs djgpp binaries of pdftex, I can make that immediately. Thanh

1 0

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by David Kastrup 18 Aug '07

18 Aug '07

Philip TAYLOR <Philip-and-LeKhanh(a)Royal-Tunbridge-Wells.Org> writes: > David Kastrup wrote: > >> Have you actually programmed any serious batch scripts under Windows? > > Yes, many : after leaving VMS (a forced migration, not my choice) > I have worked only with Windows. Probably the key to success > is a familiarity with the HELP system : > >> In addition, substitution of FOR variable references has been enhanced. >> You can now use the following optional syntax: >> >> %~I - expands %I removing any surrounding quotes (") >> %~fI - expands %I to a fully qualified path name >> %~dI - expands %I to a drive letter only >> %~pI - expands %I to a path only >> %~nI - expands %I to a file name only >> %~xI - expands %I to a file extension only >> %~sI - expanded path contains short names only >> %~aI - expands %I to file attributes of file >> %~tI - expands %I to date/time of file >> %~zI - expands %I to size of file >> %~$PATH:I - searches the directories listed in the PATH >> environment variable and expands %I to the >> fully qualified name of the first one found. >> If the environment variable name is not >> defined or the file is not found by the >> search, then this modifier expands to the >> empty string >> >> The modifiers can be combined to get compound results: >> >> %~dpI - expands %I to a drive letter and path only >> %~nxI - expands %I to a file name and extension only >> %~fsI - expands %I to a full path name with short names only >> %~dp$PATH:I - searches the directories listed in the PATH >> environment variable for %I and expands to the >> drive letter and path of the first one found. >> %~ftzaI - expands %I to a DIR like output line >> >> In the above examples %I and PATH can be replaced by other valid >> values. The %~ syntax is terminated by a valid FOR variable name. >> Picking upper case variable names like %I makes it more readable and >> avoids confusion with the modifiers, which are not case sensitive. It must be mentioned that one actually needs single-iteration for-loops for almost any useful variable manipulation. Quite intuitive. > Also very useful is Log Parser 2.2 (which does far far more than > parsing log files !) and, of course, Perl. Perl is not exactly creditable to Windows now, is it? -- David Kastrup, Kriemhildstr. 15, 44793 Bochum

1 0

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by Akira Kakuto 18 Aug '07

18 Aug '07

Hi David, > Interesting. "Closed" with "Worksforme" because an application > accumulated file descriptors erroneously. > > The problem is that we actually _have_ this amount of outstanding > images not yet shipped out. No programming error. > > Putting the single line > > _setmaxstdio(2048); > > into web2c startup does not seem like it would be an overly onerous > complication, would it? I've confirmed that by #if defined(pdfTeX) || defined(luaTeX) _setmaxstdio(2048); #endif 2041 files in Vladimir's example are included. Probably 7 are stdin, ... etc. Best regards, Akira

7 13

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by David Kastrup 18 Aug '07

18 Aug '07

Philip TAYLOR <Philip-and-LeKhanh(a)Royal-Tunbridge-Wells.Org> writes: > Reinhard Kotucha wrote: > >> Phil, I respect you because I know that you are an TeX expert. You >> usually know what you are talking about and you are certainly more >> familiar with TeX than anybody else. But what you said about UNIX is >> pure crap and I must admit that I'm quite disappointed. > > Well, it was intentionally provocative, but that doesn't > mean it's not grounded in truth : if you read back over > the TeX live correspondence (which is the list to which > I was referring, rather than PdfTeX or NTGTeX or whatever) > you will see over and over again questions caused by different > libraries, different compilers, different versions, different > modes of linking, etc., etc., etc. Every time I read one, > I ask myself "Why on earth do they bother ?". Because they can. So they are more noticeable than the two people who had actually managed to get it compiled under Windows. The autoconf documentation contains a section about portable shell programming: what kind of stuff you can rely on to work everywhere, and what not. It is a real horror show and a bit of a nuisance to keep everything in mind. The resulting scripts sometimes are a bit awkward. But this does not hold a candle to programming cmd.exe. Something like for i in /opt /usr/local /opt/* /usr/local/* do if test -d "$i"/software then cd "$i" subdir="$i" break fi done becomes (in a batch file, on the command line it looks different) for /D %%I in (C:\ D:\ C:\* D:\*) do ( if exist %%I\software\NUL ( %%~dI cd %%~pnI set subdir=%%I goto found ) ) :found Except that it probably won't work when you are in a subdirectory of C: or D: currently. And passing the found string into Java with "%subdir%" can cause the trailing quote to be added (because it may be backslash-preceded) into the command line argument. And if you use "echo on" in your batch file (the default), what gets echoed back at you is garbage, because Windows does not manage to treat the %%x stuff correctly when echoing. It is _much_ _much_ harder to find the necessary information for batch programming under Windows on the net, and while portability is not much of a concern, the portable subset of shell programming is still much more straightforward and usable than what cmd.exe provides. Have you actually programmed any serious batch scripts under Windows? Or are your opinions not based on working with the system? -- David Kastrup, Kriemhildstr. 15, 44793 Bochum

1 0

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by Akira Kakuto 17 Aug '07

17 Aug '07

Hi Martin, > Let's get back to the facts: I can easily include 10000 different pdfs > on one page (and claim that the number of files is only limited by > memory) -- when \pdfximage is \immediate (which is normally is not). > This works on Linux. Does this not work on Windows? \documentclass[pdftex,a5paper]{book} \usepackage[papersize={8.5in,11in}]{geometry} \usepackage{pdfpages} % \let\mypdfximage\pdfximage \def\pdfximage{\immediate\mypdfximage} % \begin{document} \newcount\i \i=2 \loop \ifnum\i<3000 \includepdf[pages={-}]{\number\i.pdf}% \advance\i by1 \repeat \end{document} works also on Windows. The "immediate" version does not depend on the limitation on the number of open files. Thanks, Akira

1 0

Runtime limitations on open files?
by David Kastrup 17 Aug '07

17 Aug '07

Hi, we are crashing with "too many open files" on PDFTeX from TeXlive. The object id where this happens is 513 or so, and it would be my guess that PDFTeX keeps image files open as long as it has not yet shipped them out. It would appear that the system limitations of win32 are much larger, so I suspect the runtime with which TeXlive2007 has been compiled. Does anybody have a good pointer to where I might look for further information? This is quite a bad roadblock for us. -- David Kastrup

6 10

Re: [NTG-pdftex] [tex-live] Runtime limitations on open files?
by David Kastrup 17 Aug '07

17 Aug '07

Jonathan Kew <jonathan_kew(a)sil.org> writes: > On 17 Aug 2007, at 12:00 pm, David Kastrup wrote: > >> we are crashing with "too many open files" on PDFTeX from TeXlive. >> The object id where this happens is 513 or so, and it would be my >> guess that PDFTeX keeps image files open as long as it has not yet >> shipped them out. >> >> It would appear that the system limitations of win32 are much larger, >> so I suspect the runtime with which TeXlive2007 has been compiled. >> >> Does anybody have a good pointer to where I might look for further >> information? This is quite a bad roadblock for us. > > I believe the W32 binaries in TL were built by Akira using MS Visual > Studio tools, but I don't know whether/how this limit can be > controlled there. See other mail on this: it would appear to be easy to fix this (namely: bump the number to 2048) in the sources. > As a workaround, have you tried alternatives such as generating DVI > output and then running dvipdfmx? It's possible that might handle > things differently. Far too many PDFTeX specific features in use, I am afraid. That road is not open to us at the moment. -- David Kastrup

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: v1.40.4 Status: Open >Resolution: Postponed 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-15 01:52 Message: Logged In: YES user_id=421 I'm sorry, but fixing this needs a change in the whole autofoo system of TL, which is not likely to happen soon. ---------------------------------------------------------------------- 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: 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