# Bug Tracker

ID 196🔗 2022-02-08 13:16:52 Open Sign in if you want to bump this report. glossaries 1.48 Incompatibility between xindy and LuaLatex

## Description

Consider the following MWE:

\documentclass{article}
\usepackage{shellesc}
\usepackage[acronym, automake=immediate, xindy]{glossaries-extra}

\newacronym{test}{TEST}{This is a test}
\makeglossaries

\begin{document}
\gls{test}
\printglossary[type=\acronymtype]
\end{document}
If I compile the following MWE with PDFLatex, there is no problem, I get the desired result. However, if I use LuaLaTeX to compile, I get no result even after several compilations. Using automake=immediate doesn't seem to do anything.

Ulrike Fischer proposes the following solution:
\documentclass{article}
\usepackage{shellesc}

\usepackage[acronym, automake=immediate, xindy={codepage=utf8}]{glossaries-extra}

\newacronym{test}{TEST}{This is a test}
\makeglossaries

\begin{document}
\gls{test}
\printglossary[type=\acronymtype]
\end{document}

## MWE

\documentclass{article}
\usepackage{shellesc}
\usepackage[acronym, automake=immediate, xindy]{glossaries-extra}

\newacronym{test}{TEST}{This is a test}
\makeglossaries

\begin{document}
\gls{test}
\printglossary[type=\acronymtype]
\end{document}

## Evaluation

I've changed the status from glossaries-extra to glossaries.

Note that if you run xindy via the shell escape you need to ensure that you set the codepage and language. For example:

\documentclass{article}
\usepackage{shellesc}
\usepackage[acronym,
automake=immediate,
xindy={language=english,codepage=utf8}
]{glossaries}

\newacronym{test}{TEST}{This is a test}
\makeglossaries

\begin{document}
\gls{test}
\printglossary[type=\acronymtype]
\end{document}
It's not always necessary, but the language names used by xindy don't always correspond to the document language name.

The switches are normally determined by the makeglossaries script. If you don't use that script you need to ensure they are correctly set. (This isn't causing the issue reported here. Your MWE doesn't set the codepage but it doesn't cause a syntax error because the actual command isn't being run.)

In summary, there are two issues here:

1. The codepage isn't being set correctly in the xindy call (you need to explicitly set it until this issue is fixed)
2. The xindy call isn't actually been run in the shell escape with LuaLaTeX (use the shellesc package as a workaround).
I will investigate both issues when I next update glossaries, but since there are simple workarounds they're not high priority.

1 comment.

🔗Comment from anonymous
Date: 2022-06-09 20:13:01

Hi All,

I would just like to report as another affected user on the LuaLaTeX shell escape issue. In the hope that shellesc can be incorporated eventually.

Kind regards,
Gustavo

Name (optional):

Are you human? Please confirm the bug report ID (which can be found at the top of this page) or login if you have an account.

Comment:

You can use the following markup:

Block:

[pre]Displayed verbatim[/pre]
[quote]block quote[/quote]

In line:

[tt]code[/tt]
[file]file/package/class name[/file]
[em]emphasized text[/em]
[b]bold text[/b]
[url]web address[/url] [sup]superscript[/sup]
[sub]subscript[/sub]

Ordered list:
[ol]
[li]first item[/li]
[li]second item[/li]
[/ol]

Unordered list:
[ul]
[li]first item[/li]
[li]second item[/li]
[/ul]

You can use the Preview button to review your message formatting before submitting.

Name (optional):

Are you human? Please confirm the bug report ID (which can be found at the top of this page) or login if you have an account.

Comment:

You can use the following markup:

Block:

[pre]Displayed verbatim[/pre]
[quote]block quote[/quote]

In line:

[tt]code[/tt]
[file]file/package/class name[/file]
[em]emphasized text[/em]
[b]bold text[/b]
[url]web address[/url] [sup]superscript[/sup]
[sub]subscript[/sub]

Ordered list:
[ol]
[li]first item[/li]
[li]second item[/li]
[/ol]

Unordered list:
[ul]
[li]first item[/li]
[li]second item[/li]
[/ul]

You can use the Preview button to review your message formatting before submitting.