Bug Tracker

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

Report

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

\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

Comment from anonymous. 2020-01-16 20:40 GMT

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!

Add comment or return to search results.

Watch This Report

If you would like to be notified whenever updates are made to this report, please fill in your email address in the box below and click on "Notify Me of Changes" button. (Please ensure the address is valid.) Your details won't be passed on to third parties in line with this site's Privacy Policy.

If you supply your name, it will be used in the email greeting, which provides a more personal message, otherwise you'll just get a generic greeting. If you have previously supplied your name when signing up for notifications, you don't need to resupply it unless you want to change it.

If you have previously subscribed to notifications for this report, you can unsubscribe by clicking on the "Stop Notification" button.

The "Confirm Bug ID" field helps to protect against spambots. Please enter the bug ID (which you can find at the top of this page).

(Optional.)
E mail:
Confirm E mail:
Confirm Bug ID:

To unsubscribe from all notifications use the notifications page.

Comment

You can append a comment to the report using the form below. Comments are checked first before being added. Any spam or offensive content will be removed first according to this site's Terms of Website Use. Please bear in mind that I develop and maintain free software in my spare time. If you want commerical level support then you can hire a TeX consultant.

The "Confirm Bug ID" field helps to protect against spambots. Please enter the bug ID (which you can find at the top of this page).

(Optional. If provided, it will be shown with the comment.)
Confirm Bug ID:

You can use the following markup:

[pre]Displayed verbatim[/pre]
[tt]monospace text[/tt]
[em]emphasized text[/em]
[b]bold text[/b]
[url]web address[/url]

Ordered list:
[ol]
[li]first item[/li]
[li]second item[/li]
[/ol]

Unordered list:
[ul]
[li]first item[/li]
[li]second item[/li]
[/ul]

Click on the Preview button to preview the message.

Return to search results.