August 2007 - ntg-pdftex - NTG Mailing Lists

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 19 Aug '07

19 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