Latest news 2024-03-02: Ebook sale (3rd–9th March 2024): short story cybercrime fiction Unsocial Media free; short story noir crime fiction I’ve Heard the Mermaid Sing free; crime fiction novel The Private Enemy US$1.99; illustrated children’s story The Foolish Hedgehog US$0.99. For further details, see latest blog post.

Bug Tracker RSS feed

I’m currently working on a major new version of the datatool package. This may take a while. Please be patient. (Experimental version available for testing.)

ID 63🔗
Date: 2014-07-18 11:15:46
Status Closed (Not a Bug)
Category glossaries
Version 4.07
Summary Use of \acrfull before first use of \gls should cause \gls to show abbreviation instead of full entry

Sign in to subscribe to notifications about this report.

Description

Essentially as the summmary says, if \acrfull{} is used before \gls{} then \gls{} should output the acronym. Currently it outputs the full entry.

MWE

Download (312B)

\documentclass{article}

\usepackage[acronym]{glossaries}  % provides support for glossaries and acronyms
\makeglossaries
\newacronym{ft}{FT}{Fourier transform}

\begin{document}

This is some text about \acrfull{ft}. And again we mention \gls{ft}, but really
we like \gls{ft}.

\printglossaries

\end{document}

Evaluation

This isn't a bug. It's documented behaviour. From the manual (chapter 13) regarding commands like \acrfull:

There are commands similar to \glstext (described in §6 Links to Glossary Entries) that allow you to access just the short form, just the long form or the full form, without affecting the first use flag. (Note that the full form isn’t necessarily the same as the text produced on first use.)
Since \acrfull doesn't affect the first use flag, it doesn't affect the behaviour of \gls.

Comments

1 comment.

🔗Comment from anonymous
Date: 2014-07-18 17:30:00

Ah, missed that in the manual. Sorry for the unnecessary bug report!

Replying to Comment #36:

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.


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