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 76🔗
Date: 2014-12-19 04:18:58
Status Closed (Not a Bug)
Category glossaries
Version 4.12
Summary Nested glossary items fail when capitalizing

Sign in to subscribe to notifications about this report.

Description

When nesting glossary items, capitalization functions (\Gls, \Glspl, etc) fail when the nested glossary item is the first word. In the MWE notice how PFS works but HTTPS fails.

MWE

Download (277B)

\documentclass{article}
\usepackage{glossaries}
\newacronym{fs}{FS}{forward secrecy}
\newacronym{pfs}{PFS}{perfect \gls{fs}}
\newacronym{http}{HTTP}{Hypertext Transfer Protocol}
\newacronym{https}{HTTPS}{\gls{http} Secure}
\begin{document}
\Gls{pfs}
\Gls{https}
\end{document}

Evaluation

This isn't a bug but a documented feature of \makefirstuc. From the glossaries manual (section 6.1):

For the former [\Gls], the uppercasing of the first letter is performed by \makefirstuc. For further details, including its limitations, see the mfirstuc user manual.
From the mfirstuc user manual:
The glossaries bundle includes the package mfirstuc which provides the command:
\makefirstuc{⟨stuff⟩}
This makes the first object of ⟨stuff⟩ uppercase unless ⟨stuff⟩ starts with a control sequence followed by a non-empty group, in which case the first object in the group is converted to uppercase.
In this case the first object of ⟨stuff⟩ is \gls so the uppercasing is applied to the argument, which fails because the argument is a label.

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