Latest news 2019-11-04: The giveaway of two signed copies of “Quack, quack, quack. Give my hat back!” has closed and the winning entrants have been selected. Thank you to everyone who took part.

# Bug Tracker

ID 3 Closed (Fixed) glossaries v3.04 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 supply your name, it will be used in the email greeting, which provides a more personal message, otherwise you'll just get a generic greeting. If you have previously supplied your name when signing up for notifications, you don't need to resupply it unless you want to change it.

If you have previously subscribed to notifications for this report, you can unsubscribe by clicking on the "Stop Notification" button.

The "Confirm Bug ID" field helps to protect against spambots. Please enter the bug ID (which you can find at the top of this page).

Name: (Optional.)

## Comment

You can append a comment to the report using the form below. Comments are checked first before being added. Any spam or offensive content will be removed first according to this site's Terms of Website Use. Please bear in mind that I develop and maintain free software in my spare time. If you want commerical level support then you can hire a TeX consultant.

The "Confirm Bug ID" field helps to protect against spambots. Please enter the bug ID (which you can find at the top of this page).

Name: (Optional. If provided, it will be shown with the comment.) Message: You can use the following markup: [pre]Displayed verbatim[/pre] [tt]monospace text[/tt] [em]emphasized text[/em] [b]bold text[/b] [url]web address[/url] Ordered list: [ol] [li]first item[/li] [li]second item[/li] [/ol] Unordered list: [ul] [li]first item[/li] [li]second item[/li] [/ul]

Click on the Preview button to preview the message.