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

Bug Tracker

ID 54🔗
Date: 2014-03-13 09:55:57
Status Closed (Fixed)
Category glossaries
Version 4.06
Summary Acronyms defined in document body result in wrong firstplural
OS OSX10.9

Sign in to subscribe to notifications about this report.

Description

Let's assume we put
\newacronym[description={Decision Support System}]{dss}{DSS}{decision support system}
in the preamble, everything works fine when using \glspl{dss} in text, resulting in "decision support systems (DSSs)"

However, when putting the acronym definition within the document body, a .glsdefs file is created with the firstplural key set to

"decision support systems(DSS)".
Note the missing space before the bracket.

MWE

Download (363B)

\documentclass{article}

\usepackage[xindy, toc, acronym, section, nopostdot]{glossaries}
\makeglossaries
\newacronym[description={Decision Support System}]{dss}{DSS}{decision support system}

\begin{document}

\newacronym[description={Decision Support System}]{dss2}{DSS}{decision support system}

Works: \glspl{dss}

Missing space: \glspl{dss2}

\end{document}

Evaluation

Fixed in version 4.08

2014-03-13 15:51 GMT

I think this may be another technical issue. I'll see if I can fix it when I work on the next version of glossaries, but it's a low priority bug as the simple workaround is to move the definition to the preamble.

2014-03-14 08:43 GMT

Another workaround is to use \setacronymstyle{long-short}:

\documentclass{article}
\usepackage[xindy, toc, acronym, section, nopostdot]{glossaries}
\makeglossaries

\setacronymstyle{long-short}

\newacronym[description={Decision Support
System}]{dss}{DSS}{decision support system}

\begin{document}

\newacronym[description={Decision Support
System}]{dss2}{DSS}{decision support system}

Works: \glspl{dss}

Missing space: \glspl{dss2}

\end{document}
The new acronyms styles that are set via \setacronymstyle don't use the first or firstplural keys.

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=54