I have just followed the method of Speravir (see How to use Xindy with MiKTeX?). My MiKTeX installation is
D:\MiKTeX 2.9, and I already had a
D:\LocalTeXMF for files that are not in the distribution. Unfortunately, trying to test with the example file (that I named
testxindy.tex) and to use
xindy on the resulting
.idx file from the command line, it didn't work.
One reason is that it is not quite clear for the novice which executable to use in which case. Schematically, there are two possibilities for the (simplest) command line:
In the 1st case, the answer was:
failed to find script. The documentation mentions a
makeindex4 wrapper for
xindy. Unfortunately, this wrapper can't be found in the distribution. Is it some obsolete wrapper?
In the 2nd case, the answer was:
writing attribute names to file testxindy.idx, the program seeming either to be waiting for some answer or to have an endless loop.
Finally, it worked launching directly the
texindy.pl script. However there were strange things in the
.ilg file (strange to me, at least):
Loading module YcBEHsZUlK ........ Finished loading module YcBEHsZUlK
All other modules loaded have 'normal' names… So ? Could it be related to the fact that my editor uses
Anyway I can't understand how to make the
.exe files work, which, I guess, is the normal way.
Subsidiary question: in a
MiKTeX installation, shouldn't the bin directory be in
\LocalTeXMF\miktex\bin rather than in
\LocalTeXMF\bin? If so, where should really be
texmf.cnf – \LocalTeXMF or
\LocalTeXMF\MiKTeX, or even
I would be very grateful for any help.