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

Bug Tracker

ID 49🔗
Date: 2013-12-19 05:33:25
Status Closed (Not a Bug)
Category glossaries
Version 4.02
Summary \Glsentry... don't give the expected result in bookmarks

Sign in to subscribe to notifications about this report.

Description

Page 76 of glossaries' documentation, it is advised to use commands listed in Section 9 (such as \glsentrytext) in the arguments of sectioning commands. As poined out by the joined MWE, that works with \glsentry... commands but not with their "first letter upper case" counterparts \Glsentry...: the corresponding bookmarks contain only the entries' labels.

MWE

Download (401B)

\listfiles

\documentclass{article}
\usepackage{hyperref}
\usepackage{glossaries}
%
\makeglossaries
%
\newglossaryentry{foo}{name=name of foo,description=description of foo}
%
\begin{document}
\section{\glsentrytext{foo}}
\section{\glsentrytext{foo}}
\section{\glsentryplural{foo}}
\section{\Glsentrytext{foo}}
\section{\Glsentrytext{foo}}
\section{\Glsentryplural{foo}}
\printglossary
\end{document}

Evaluation

Section 9 states:

Commands that aren't expandable will be ignored by PDF bookmarks, so you will need to provide an alternative via hyperref's \texorpdfstring if you want to use them in sectioning commands. (This isn't specific to the glossaries package.) See the hyperref documentation for further details. All the commands that convert the first letter to upper case aren't expandable.
and below the definition of \glsentrytext and \Glsentrytext it states:
These commands display the subsequent use text for the glossary entry given by <label>, as specified by the text key. \Glsentrytext makes the first letter upper case. The first form is expandable (unless the text contains unexpandable commands). The second form is not expandable.
so it's not a bug but a documented feature, but I will add a reminder to that this only applies to the non-case changing commands.

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