Latest news 2019-12-05: new blog post "RSS Feeds and Other Notifications."

Bug Tracker

ID89
StatusClosed (Not a Bug)
Categoryglossaries
Version4.15
Summarybreaking space between long acronym and acronym

Report

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.

Malte Vesper

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 05:22:42 CDT

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 comand wrapper to generate this style).

Comment from Nicola Talbot
Date: 2015-07-08 11:27 BST

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.

Add comment.

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 list.

© 2019 Dickimaw Books. "Dickimaw", "Dickimaw Books" and the Dickimaw parrot logo are trademarks. The Dickimaw parrot was painted by Magdalene Pritchett.

Terms of Use Privacy Policy Cookies Site Map FAQs