Latest news 2021-09-06: new blog post "Legacy Documents and TeX Live Docker Images".

# Bug Tracker

ID 89🔗 2015-06-24 11:16:02 Closed (Not a Bug) glossaries 4.15 breaking space between long acronym and acronym

## Description

Glossaries default style (current texlive version) allows for a line break between Acronym (acr) i.e.

Acronym
(acr)

This line break can fall onto a page break.

Fix: i guess replacing \space with ~ should work. If there are reasons against this please let me know.

## MWE

    \documentclass{article}
\usepackage{glossaries}
\setlength{\textwidth}{1cm}

\newacronymstyle{long-short-nolbr}%
{%
\ifglshaslong{\glslabel}{\glsgenacfmt}{\glsgenentryfmt}%
}%
{%
\renewcommand*{\GenericAcronymFields}{description={\the\glslongtok}}%
\renewcommand*{\genacrfullformat}[2]{%
\glsentrylong{##1}##2~
(\protect\firstacronymfont{\glsentryshort{##1}})%
}%
\renewcommand*{\Genacrfullformat}[2]{%
\Glsentrylong{##1}##2~
(\protect\firstacronymfont{\glsentryshort{##1}})%
}%
\renewcommand*{\genplacrfullformat}[2]{%
\glsentrylongpl{##1}##2~
(\protect\firstacronymfont{\glsentryshortpl{##1}})%
}%
\renewcommand*{\Genplacrfullformat}[2]{%
\Glsentrylongpl{##1}##2~
(\protect\firstacronymfont{\glsentryshortpl{##1}})%
}%
\renewcommand*{\acronymentry}[1]{\acronymfont{\glsentryshort{##1}}}
\renewcommand*{\acronymsort}[2]{##1}%
\renewcommand*{\acronymfont}[1]{##1}%
\renewcommand*{\firstacronymfont}[1]{\acronymfont{##1}}%
\renewcommand*{\acrpluralsuffix}{\glspluralsuffix}%
}

\makeglossaries
\setacronymstyle{long-short-nolbr}
\setacronymstyle{long-short}
\newacronym{nfa}{NFA}{nondeterministic finite automata}
\begin{document}
\gls{nfa}

\end{document}

## Evaluation

This is a feature request, so I've had to close it as not a bug. (There are plenty of long abbreviations, especially technical or medical ones, where a non-breakable space is undesirable. The existing styles behave as documented so there's no bug to fix.) However, version 4.16 now has two new styles called long-sp-short and long-sp-short-desc. These will use a non-breakable space if "(short)" is less than 3em otherwise it will use a regular space. For these styles, the space is inserted using \glsacspace{label} which can be redefined as required.

🔗Comment from Malte Vesper
Date: 2015-07-09 11:22:42

While probably not quite the place, I would like you to know that I did not just move on, after reporting this, so: Thank you very much.

Just as an idea for the future: would it make sense to have the 3em be user defineable? (Package parameter: downside only configurable for one glossary, style parameter or maybe create a command wrapper to generate this style).

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.

🔗Comment from Nicola Talbot 🦜
Date: 2015-07-08 11:27:00

I did consider making the length configurable by providing a new length register, but glossaries already uses up so many resources (which has resulted in complaints) that I didn't want to add any more. It's difficult to get a good balance between providing customization and document build efficiency.

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.

🔗Comment from Nicola Talbot 🦜
Date: 2020-03-01 20:38:00

The glossaries-extra package has made it easier to provide new features. Some of the abbreviation styles with the extension package use

\glsxtrfullsep{label}

between the long and short forms which can be configured as required.

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.