Latest news 2021-06-05: New blog post: Dickimaw Books Site Account.

Bug Tracker

ID 162🔗
Date: 2020-06-14 11:19:55
Status Open
Sign in if you want to bump this report.
Category glossaries
Version 4.45
Summary Using \glspl on acronym while \glsnoexpandfields is active produces wrong output

Sign in to subscribe to notifications about this report.

Description

In the documentation it states that if one has problems with commands in acronyms one should use the \glsnoexpandfields option.

It solved my problem of using siunitx commands in acronyms but produces an unfortunate side-effect.

Acronym plural usages are not displayed correctly anymore. Instead of the actual acronym being displayed the last defined acronym is displayed instead.

I made a minimal example to reproduce this bug:

\documentclass{scrbook}

\usepackage{glossaries}
\glsnoexpandfields


\newacronym{right}{RIGHT}{right acronym}
\newacronym{wrong}{WRONG}{wrong acronym}

\begin{document}

\glspl{right}. This is \glspl{right}.
        
\end{document}
It will display the `WRONG` acronym in the PDF instead of the `RIGHT` one.

MWE

Download (232B)

\documentclass{scrbook}

\usepackage{glossaries}
\glsnoexpandfields


\newacronym{right}{RIGHT}{right acronym}
\newacronym{wrong}{WRONG}{wrong acronym}

\begin{document}

\glspl{right}. This is \glspl{right}.
        
\end{document}

Evaluation

It seems that the original acronym mechanism (which is currently in effect by default) conflicts with \glsnoexpandfields. As a workaround, I recommend switching to the newer acronym mechanism with \setacronymstyle. For example:

\documentclass{scrbook}

\usepackage{glossaries}
\glsnoexpandfields

\setacronymstyle{long-short}

\newacronym{right}{RIGHT}{right acronym}
\newacronym{wrong}{WRONG}{wrong acronym}

\begin{document}

\glspl{right}. This is \glspl{right}.

\end{document}

Comments

0 comments.


Add Comment

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.

Page permalink: https://www.dickimaw-books.com/bugtracker.php?key=162