Recent news (2017-04-18): glossaries-extra v1.14 released.

# Bug Tracker

ID 3 Closed (fixed) glossaries v3.04 N/A xindy can't find module for language german

## Report

When the document language is (n)german and the inputenc package is loaded xindy currently can't find a suitable module and thus has to resort to language "general" in the end.

Excerpt from the terminal output generated by makeglossaries:

xindy -L german -C utf8 -I xindy ...

Cannot locate xindy module for language german in codepage utf8.

Retrying using default codepage.

xindy -L german -I xindy ...
Cannot locate xindy module for language german.

Retrying with -L general

xindy -L general -I xindy ...

Opening logfile ...

MWE:
\documentclass[ngerman]{article}

\usepackage{babel}

\usepackage[utf8]{inputenc}

\usepackage[xindy]{glossaries}

\makeglossaries

\newglossaryentry{Begriff}{name={Begriff}, description={Ein Begriff}}

\begin{document}

\printglossary

\end{document}


## Evaluation

For German, xindy needs to know whether to use "din5007" or "duden".

As from makeglossaries version 2.06 (glossaries v3.05) I've added "din5007" as the default to makeglossaries if the language is set to german.

## Workaround for Earlier Versions

Either use
\GlsSetXdyCodePage{duden-utf8}

or
\GlsSetXdyCodePage{din5007-utf8}


Comment from anonymous
Date: 2015-03-18 10:19:40 CDT

The issum mentioned above exists in v 4.12(Tex Live 2014). It can be reproduced by invoking makeglossaries on a file containing the MWE above, while the workaround is still applicable.

Comment from Nicola Talbot
Date: 2015-07-09 10:22 BST

This should now be fixed in makeglossaries version 2.16 (glossaries version 4.16).

## Watch This Report

If you would like to add a comment regarding this bug report, please fill in the form below, but don't use it for a different bug or feature request, even if it's related. Instead fill out a new bug report or feature request. (If you want to link it to this report, make a note of the ID number at the top of the page.)

 Name (Optional) Comment You can use the following markup: [pre]Displayed verbatim[/pre] [tt]monospace font[/tt] [url]web address[/url] which will be converted to:
Displayed verbatim