[Tex/LaTex] MiKTeX and Xindy problems

glossariesmiktexxindy

Today's updates of MiKTeX include Xindy (at last!). This is great news, but unfortunately I can't get it to work. With the following minimal example:

\documentclass{article}
\usepackage[xindy]{glossaries}
\newacronym{AKA}{AKA}{Also Known As}
\makeglossaries
\begin{document}
\glsaddall
\printglossaries
\end{document}

makeglossaries fails with exit code 25. This is the contents of the .glg file:

;; This logfile was generated automatically by `xindy'
;; at 20.06.2015  07:29:59
;; Indexstyle: "5i3SDna0ed", Rawindex: "Yl65BHMXsP", Output: "test1.gls"

ERROR: "" is not a valid filename !

*** Unable to execute: '"xindy"  -L english  -I xindy -M "test1" -t "test1.glg" -o "test1.gls" "test1.glo"' ***

Failed with error code 1.

Status report:

Opening logfile "test1.glg" (done)
Reading indexstyle...
Loading module "5i3SDna0ed"...

Error in line 1:
(require "")
ERROR: "" is not a valid filename !

and this is the contents of the generated 5i3SDna0ed file

(require "")
(require "test1.xdy")

Do I need to configure something to get Xindy to work?

Best Answer

The problem is indeed related to a MiKTeX installation in a path containing spaces. It can be solved by a small edit in C:\Program Files\MiKTeX2.9\scripts\xindy\xindy.pl

replace in line 779

        @styles = glob("$lang_dir/$variant$cp*-lang.xdy");

        @styles = glob("'$lang_dir/$variant$cp*-lang.xdy'");

Related Solutions

[Tex/LaTex] How to use Xindy with MiKTeX

My following answer is obsolete since end of June, 2015. I’ve got the internal MiKTeX version with the update from 25 of June 2015, but apparently others got it already one week earlier.

Note, that for now there is an issue, if you’ve installed MiKTeX into a path containing spaces – as it is the default, when you used the C:\\Program Files\ or C:\\Program Files (x86)\ system folders. See wolfi’s answer to the according question MiKTeX and Xindy problems .

Yes, it is possible.

^{Remark: Several posts have been made to LaTeX-Community.org – see Installing Xindy in MikteX and finally Xindy for MiKTeX, but you will find some issues there. First, the user “lartkma” provided some files, which were uploaded to Megaupload.com, but this service is down for known reasons (see Megaupload legal case on Wikipedia). Second, I strongly discourage his advice on how to install Xindy into the main MiKTeX installation path. I wrote about this in my answer to Purpose of local texmf trees. But in the end all following instructions are still derived from lartkma’s work.

More recently a feature request has been made to include xindy in MikTeX, which also includes detailed, up-to-date installation advice.}

Prerequisite: You need a Perl interpreter – you need it anyway for the Perl scripts in MiKTeX, cf. my answer to MiKTeX and Perl scripts for advices.

If Perl is properly installed, follow the directions!

If you didn’t already have created a local texmf path, do it now. See Create a local texmf tree in MiKTeX.

For Xindy you will need this structure:
```
<localtexmf>
     |
     |--doc
     |   |
     |   +--xindy
     |
     |--miktex
     |   |
     |   +--bin
     |
     |--scripts
     |     |
     |     +--xindy
     |
     +--xindy
         |
         +--modules
```
Don't forget to add the folder <localtexmf>\miktex\bin to the system variable Path in Windows.

Nota bene: In earlier versions of this answer the recommended binary path was <localtexmf>\bin, and I personally still prefer this path. What I actually did – and want to give as advice to you – was that I created a symbolic link from <localtexmf>\miktex\bin to <localtexmf>\bin, and I did not add the new link to the system path variable. Cf. also Wikipedia: Symbolic link in Microsoft Windows. As long as you are on the same drive it does not matter, whether you use a soft link or a junction (see also on Superuser.com: directory junction vs directory symbolic link?). BTW instead of Microsoft’s own command line tools I prefer Link Shell Extension.
Get the Xindy package provided by W32TeX: http://mirror.ctan.org/systems/win32/w32tex/xindy-w32.tar.xz – this file contains all you need.

^{Remark: Ensure the date of the file is 16.4.2014 or later. The file tex2xindy.exe in the bin folder should have a date of 14.4.2014 or later. If unsure download directly from the W32TeX website.}
Extract all files into a temporary folder. You need a program, which can unpack XZ files (and also TAR, but that’s common). My suggestion is 7-Zip or PeaZip.

The files tex2xindy.exe, xindy.mem, and xindy-list.exe from the bin folder go into <localtexmf>\miktex\bin (the two .dll-files and the other two .exe-files and are not needed anymore), all contents of share\texmf-dist\doc go into <localtexmf>\doc and so on for the others.
If you’ve copied the files xindy.exe and texindy.exe into <localtexmf>\miktex\bin, delete them.

In the <localtexmf>\miktex\bin folder create two empty text files with the names xindy.bat and texindy.bat. If you like this more, you can also choose .cmd as file extension, but the filenames must not be changed!

Copy the following lines into xindy.bat and adjust the script path to your settings:
```
@echo off
set ScriptPath=<localtexmf>\scripts\xindy
perl %ScriptPath%\xindy.pl %*
```
For texindy.bat the content must be slightly different, of course:
```
@echo off
set ScriptPath=<localtexmf>\scripts\xindy
perl %ScriptPath%\texindy.pl %*
```
^{Remark: The second and third line could be merged in both cases, but in my opinion the above version is far more readable.}

If you use the default text editor Notepad, in the save dialogue make sure, that you do not save to a file with .txt extension: Save with double quotes "xindy.bat".
Refresh your filename data base (FNDB). How to do, is (for instance) also described in Create a local texmf tree in MiKTeX.
In your favorite TeX editor you perhaps need to add a call to Xindy. Because this is different for every editor, I cannot write anything about this here.

Happy Indexing!

Here two test cases, in your favorite task manager you will see the execution of perl.exe and xindy-lisp.exe:

Creating an index:

For convenience I used the package imakeidx, because with the option xindy you get there an automatic call to Xindy (actually it’s texindy!) without any configuration, but for this you must first add the switch --enable-write18 to the call of pdflatex (or the alias --shell-escape).
_{Note, with texifyit’s a bit different: --tex-option="--enable-write18".}

\documentclass{article}
\usepackage[latin,english]{babel} % needed for "blindtext",
                                  % "english" is the active language
\usepackage{blindtext,lipsum,kantlipsum}

\usepackage[xindy]{imakeidx}
\makeindex[columns=1]

\begin{document}

\section*{Package \texttt{blindtext}}

\subsection*{English blindtext}\index{blindtext (package)!english}
%%% see below before section "kantlipsum" for
%%% \index{blindtext (package)!english|seealso{kantlipsum}}
\blindtext[1]

\subsection*{Latin blindtext}\index{blindtext (package)!latin}
%%% see below before section "kantlipsum" for
%%% \index{blindtext (package)!latin|seealso{lipsum}}
{\selectlanguage{latin}% note the grouping
\blindtext[1]}

\newpage

\index{blindtext (package)!english|seealso{kantlipsum}}
\index{blindtext (package)!latin|seealso{lipsum}}

\section*{Package \texttt{kantlipsum}}\index{kantlipsum}
%%% see below before "\printindex" for
%%% \index{kantlipsum|seealso{blindtext (package) with english option}}
\kant[123]

\section*{Package \texttt{lipsum}}\index{lipsum}
%%% see below before "\printindex" for
%%% \index{lipsum|seealso{blindtext (package) with latin option}}
{\selectlanguage{latin}% actually not needed here
\lipsum[123]}% note the grouping again

\newpage

\index{kantlipsum|seealso{blindtext (package) with english option}}
\index{lipsum|seealso{blindtext (package) with latin option}}

\printindex

\end{document}

Creating a glossary with package glossaries:

testfile.tex:
```
\documentclass{article}

\usepackage[xindy]{glossaries}
\makeglossaries

\newglossaryentry{gloss}{
name=glossaries,
description=A package for generating glossaries in many styles
}

\begin{document}

\texttt{\gls{gloss}} is a great package!

\printglossaries
\end{document}
```
After one latex compilation, run makeglossaries testfile on command line. With options and filename above this will in background make a call of

xindy -L english -I xindy -M "testfile" -t "testfile.glg" -o "testfile.gls" "testfile.glo"

After a second latex run you should see the result. For other settings you must read the documentation of glossaries.

[Tex/LaTex] Problems with xindy and glossaries

You must set document language to german to let glossaries know how it should sort entries. Due to xindy bug, you also have to set encoding manually:

\documentclass[10pt,twoside,a4paper,fleqn]{book}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage[german]{babel}
\usepackage{ifthen, xkeyval, xfor, amsgen}
\usepackage[xindy]{glossaries}
\GlsSetXdyCodePage{duden-utf8}
\usepackage{translator}
\makeglossaries

\begin{document}

\newglossaryentry{real number}
{
    name={real number},
    description={include both rational numbers and irrational numbers},
    symbol={\ensuremath{\mathbb{R}}}
}

\newglossaryentry{Agypten}
{
    name = {{Ä}gypten},
    description = {German:Egypt}
}

\chapter{Model chapter for a report}

This is the first chapter of the report. Most certainly it will have
    some \glspl{real number}. Maybe there will be
    something in German, like \gls{Agypten}

\printglossary

\end{document}

Important lines are \usepackage[german]{babel} and \GlsSetXdyCodePage{duden-utf8}. Note that you missed comma in Agypten glossary entry.

Edit: if makeglossaries still don't work, try this:

xindy -M lang/german/duden-utf8 -I xindy -M test -t test.glg -o test.gls test.glo

Best Answer

Related Solutions

[Tex/LaTex] How to use Xindy with MiKTeX

[Tex/LaTex] Problems with xindy and glossaries

Related Question