[tex-live] Xindy searchpath
jschrod at acm.org
Fri Jun 18 09:09:28 CEST 2010
T T writes:
> On 17 June 2010 03:06, Robert Eckl <eckl.r at gmx.de> wrote:
> > T T <t34www at googlemail.com> wrote:
> > (searchpath
> > ".:h:/texlive/2010/texmf/xindy/modules:h:/texlive/2010/texmf/xindy/modules
> > /base")
> This seems to be a bug in xindy.pl script. Not much you can do about
> unless you have skills to write a patch for this. I CCed the relevant
That's strange; I will compare the TL 2010 code with TL 2009 if I
forgot some of Vladimir's Windows patches.
> Notes for xindy devs:
> * As Akira said in another message the colon character can't be used
> as a path separator on Windows. The `searchpath ...' part in clisp's
> expression should use semicolon (in most likelihood but depends on
> whether bin/win32/xindy-lisp.exe is a native windows port of clisp).
FYI: Search path interpretation is done by xindy code itself, not by
any supplied library. So colon vs. semicolon is handled in our own
> * Passing arguments with x0A (newline) char (as it happens for clisp
> expression AFAICS from the sources) may or may not work depending on
> whether the system shell is used or not and on how command line is
> parsed. On win32 it's not possible to directly pass argument array to
> a spawned process like on Unix - the argument array is always
> converted to a single command line string before spawning a process.
In Perl under Unix, I assure that an intermediate shell is avoided and
direct exec() call is used. There is an official documented way to do
that and I use it. I hope that Perl's Windows port keeps that
documented behaviour. It seemed to work for TL 2009, so I don't think
we will have problems here.
Btw, the command line option to log what happens in the xindy script
is "--debug script".
Joachim Schrod Email: jschrod at acm.org
xindy maintainer http://www.xindy.org/
More information about the tex-live