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 97🔗
Date: 2015-09-22 12:44:24
Status Closed (Not a Bug)
Category glossaries
Version v4.18
Summary Not bold smallcaps even with fonts that support them

Sign in to subscribe to notifications about this report.

Description

Even with fonts that support bold smallcaps:
\setacronymstyle{long-sc-short}
leads by default to bold but not in small caps entries' names. AFAIK, this breaks previous glossaries' behavior.

Note that bold smallcaps entries' names are still available if explicitly asked by:

\renewcommand{\glsnamefont}[1]{\textsc{\bfseries #1}}

MWE

Download (311B)

\listfiles
\documentclass{article}
\usepackage{kpfonts}
\usepackage[xindy]{glossaries}
%
\makeglossaries
\newacronym{foo}{foo}{Foo Oof Oof}
\setacronymstyle{long-sc-short}
% \renewcommand{\glsnamefont}[1]{\textsc{\bfseries #1}}
%
\begin{document}
\textbf{\textsc{foo}}: \gls{foo}.
\printglossary
\end{document}

Evaluation

This isn't a bug. As stated in the manual (13.1 Changing the Acronym Style) you need to set the style before using \newacronym. The following works as expected:

\documentclass{article}
\usepackage{kpfonts}
\usepackage[xindy]{glossaries}
%
\makeglossaries
\setacronymstyle{long-sc-short}
\newacronym{foo}{foo}{Foo Oof Oof}
% \renewcommand{\glsnamefont}[1]{\textsc{\bfseries #1}}
%
\begin{document}
\textbf{\textsc{foo}}: \gls{foo}.
\printglossary
\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=97