# Bug Tracker

ID 56🔗 2014-03-14 10:27:03 Closed (Not a Bug) glossaries 4.03 .glsdefs file and babel shorthands Win7

## Description

Hi,
I came across the problem that changing acronym-entries didn't led to a change in my document. I found that this is related to this FAQ: I changed the definition of an entry, but it's still using the old definition actually, I define the glossary-entries in separate files and include them via
\AtBeginDocument{
\input{Glossar/GlossarFiles}
}

because of problems with babel-shorthands (for example "= for a hyphen that allows other breaks) otherwise (see babel: adding language shorthands to work inside glossaries) so to use this babel-shorthands, i have to pull glossaries entries at least to the beginning of the document. making glossary entries compatible with babel in header would be a great solution, for example.

## MWE

\documentclass{scrartcl}

\usepackage[ngerman]{babel}

\usepackage{glossaries}
\makeglossaries

\newglossaryentry{Foo}{name={Foo},description={Long"=Foo}}
\AtBeginDocument{
\newglossaryentry{Bar}{name={Bar},description={Long"=Bar}}
}

\begin{document}

This works:

\gls{Foo}

changes in gls"=definition of "Bar"' after a run that created .glsdefs won't have any effect. But the babel-break works:

\gls{Bar}

\printglossaries

\end{document}


## Evaluation

If you move the \AtBeginDocument before you load glossaries, you won't get a .glsdefs file as then the entries will be defined before the definition of \newglossaryentry is changed.

\documentclass{scrartcl}

\usepackage[ngerman]{babel}

\AtBeginDocument{
\newglossaryentry{Bar}{name={Bar},description={Long"=Bar}}
}
\usepackage{glossaries}
\makeglossaries

\newglossaryentry{Foo}{name={Foo},description={Long"=Foo}}

\begin{document}


1 comment.

🔗Comment from anonymous
Date: 2014-03-14 16:53:29

Wow, that's great, thank you! (Didn't expect this order to be working...)
:-)

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.