# Bug Tracker

ID 112🔗 2016-06-09 05:32:09 Closed (Not a Bug) glossaries 4.24 Glossary Label With Backslash Characters?

## Description

It seems glossary label can contains math but backslash, e.g.:
newacronym{$\beta$}{$\beta$}{$\beta$}

Is it possible to support labels with backslash characters in the future?

Actually, I am designing a LyX module for glossaries package. If labels with backslashes are possible, it can design a LyX \gls inset to preview maths containing backslashes directly in LyX and the maths are also glossary labels which are used as ordinary glossary labels. Thus, I need the support of glossary labels with backslashes.

## MWE

%% LyX 2.2.0 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[english]{article}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}

\makeatletter
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Textclass specific LaTeX commands.
\usepackage[acronym,symbols]{glossaries}
\makeglossaries

\makeatother

\usepackage{babel}
\begin{document}

\newglossaryentry{dummy}{
name={dummy},
description={dummy.}
}
\newacronym{$\beta$}{$\beta$}{$\beta$}

\printglossary[type=\acronymtype]{}
\end{document}


## Evaluation

No, I'm sorry, it's not possible for the same reason that you can't do \label{$\alpha$}. As mentioned in the user guide, the label can't contain any active or special characters (which includes backslash). The reason for this is that the label is used behind the scenes to define associated internal commands that store the relevant information. The label also needs to be fully expandable to allow it to work in iterative contexts (for example, commands like \glsunsetall require this).

(Unrelated, but note also that the manual recommends defining entries in the preamble not in the document environment.)

Since this is a documented feature I'm going to have to close this as not a bug.

1 comment.

🔗Comment from Meng-Yuan Huang
Date: 2016-06-09 11:54:42

I see. Thank you.

Replying to Comment #56:

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.

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.