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

Bug Tracker

ID 140🔗
Date: 2020-01-16 19:30:18
Status Closed (Not a Bug)
Category glossaries-extra
Version v1.41
Summary long-short-sc style ⇒ \acrlong in small caps

Sign in to subscribe to notifications about this report.

Description

If long-short-sc style is used, \acrlong (and long part of \acrfull) is, in the text, typeset in small caps instead of normal font (no problem in the glossary).

MWE

Download (401B)

\listfiles

\documentclass{article}
\usepackage{libertine}
\usepackage{glossaries-extra}
\makeglossaries%
\setabbreviationstyle[acronym]{long-short-sc}
\newacronym{laser}{laser}{light amplification by stimulated
  emission of radiation}
%
\begin{document}
\begin{itemize}
\item \gls{laser}
\item \acrshort{laser}
\item \acrlong{laser}
\item \acrfull{laser}
\end{itemize}
\printglossary
\end{document}

Evaluation

The \acrshort, \acrlong and \acrfull commands are for the original acronym mechanism of the base glossaries package. The glossaries-extra package has new commands that are designed to work with the new abbreviation mechanism: \glsxtrshort, \glsxtrlong and \glsxtrfull. Example:

\documentclass{article}
\usepackage{libertine}
\usepackage{glossaries-extra}
\makeglossaries%
\setabbreviationstyle[acronym]{long-short-sc}
\newacronym{laser}{laser}{light amplification by stimulated
  emission of radiation}
%
\begin{document}
\begin{itemize}
\item \gls{laser}
\item \acrshort{laser} vs \glsxtrshort{laser}
\item \acrlong{laser} vs \glsxtrlong{laser}
\item \acrfull{laser} vs \glsxtrfull{laser}
\end{itemize}
\printglossary
\end{document}

Comments

1 comment.

🔗Comment from anonymous
Date: 2020-01-16 20:40:00

Ooops, sorry for the noise! I'm a bit lost between the two packages.

As I said, I would dream of a glossaries2 package, with the features of glossaries-extra but without the longish and confusing "xtr" (in fact, each time a user is facing a macro name containing "xtr", he has to mentally remove this string in order to figure out what this command is supposed to do).

Many thanks, anyway!

Replying to Comment #63:

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