[twg-tds] storing scripts in the texmf tree

Reinhard Kotucha reinhard.kotucha at web.de
Tue Feb 10 01:23:08 CET 2004

>>>>> "Karl" == Karl Berry <karl at freefriends.org> writes:

    >     scripts in texmf trees is to have wrappers in bin/arch.  So,
    > is the purpose of the scripts/ directory to make the wrapper be
    > faster / more robust?  Are there other benefits?

It is slower because the wrapper has to run kpsewhich, but
nevertheless, I think that this is a clean solution.  As Hans Hagen
said, if you need to modify a script you can have a local copy in

BTW, I dont't think that we need a directory for each programming
language.  /texmf/scripts should be ok.

    > Looking at the top level of TL03, I also see java (with one
    > file, pp4p.jar).  Seems like it could go there too, [...]

Yes, of course.  It is not executable and requires a wrapper script.
It makes sense that the wrapper uses kpsewhich to find the jar file.

    > although it's not a "scripting" language exactly.

Maybe "scripts" is not the best name for this directory, do you (or
anybody else) know a better one?  

On the other hand we talk about "binaries" when we mean "executables".
We talk about "outlines" if we mean "scaleble fonts".  We even talk
about "bitmaps" if we mean "scalable fonts" (yes, metafont produces
scalable fonts).  Why not talk about "scripts" if we mean somtehing
different? :)


Reinhard Kotucha			              Phone: +49-511-4592165
Marschnerstr. 25
D-30167 Hannover	                      mailto:reinhard.kotucha at web.de
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.

More information about the twg-tds mailing list