Latest news 2022-03-24: new blog post "Book Shop Closed Indefinitely Due to PayPal Removing Support for Encrypted Website Payments".

Bug Tracker

ID 10🔗 2012-12-27 06:50:32 Closed (Not a Bug) glossaries 3.04 cross-referencing not as described

Description

Hi

Section 8 of the manual writes:

"Note that in this case, the entry with the see key will automatically be added to the glossary, but the cross-referenced entry won't."

Contrary to what the manual says, specifying a see key does not automatically add that entry (entry with the see key) to the glossaries as my MWE shows. Does it mean the other way round, as in the cross-referenced entry (the one specified within the see key) will show up even if it is not cited by commands such as \gls. In that case the wording of above is a bit confusing.

In my MWE, I got one of the entry (Empirical) to show up by using \glssee within the description key, but it fails to generate the text "see also".

I can manually write the cross-reference within the description key, but I am curious as to why the see key doesn't seem to do what the manual says.

Even by writing {\glssee[see also]{Empirical}{Blackbox}} and {\glssee[see also]{Mechanistic}{Whitebox}} *after* \makeglossaries, there is no "see also xxx" links within the glossary table for the entries of Empirical and Mechanistic.

Thank you very much

MWE

\documentclass{article}

\usepackage[notree,shortcuts]{glossaries}

\newglossaryentry{Blackbox}
{
name=Blackbox models,
sort=blackbox,
description={--- In system identification, the term \emph{blackbox} modelling refers to the process of modelling a system through non-parametric techniques, without knowledge of physical inner workings of the system, resulting in an \emph{empirical} model}
}
\newglossaryentry{Whitebox}
{
name=Whitebox models,
sort=whitebox,
description={--- In system identification, the term \emph{whitebox} modelling refers to the process of modelling a system through first principles, laws of physics and explicit assumed relationships between the input and output through prior knowledge of the system, resulting in a \emph{mechanistic} model}
}
\newglossaryentry{Mechanistic}
{
name=Mechanistic models,
sort=mechanistic,
description={},
nonumberlist
}
\newglossaryentry{Empirical}
{
name=Empirical models,
sort=empirical,
description={},
nonumberlist
}
\makeglossaries
\begin{document}
\newpage
\printglossary[title={Glossaries}]
\end{document}

Evaluation

Edited 2013-04-21 19:26

I've clarified in the documentation that \makeglossaries must be used before cross-referenced entries are defined.

Edited 2012-12-31 21:09

The user guide is correct, but I will edit it to clarify that \makeglossaries must be used before entries can be added to the external glossary file. Example:

\documentclass{article}

\usepackage[nonumberlist,seeautonumberlist]{glossaries}

\makeglossaries % <- move before entry definitions

\newglossaryentry{Blackbox}
{
name=Blackbox models,
description={cut for brevity}
}
\newglossaryentry{Whitebox}
{
name=Whitebox models,
description={cut for brevity}
}
\newglossaryentry{Mechanistic}
{
name=Mechanistic models,
description={},
}
\newglossaryentry{Empirical}
{
name=Empirical models,
description={},
}

\begin{document}

\printglossary[title={Glossaries}]
\end{document}


This automatically adds "Mechanistic models" and "Empirical models" to the glossary.

You can use the seeautonumberlist package option together with nonumberlist to only show the number list for entries containing "see" or "see also" elements, but if that entry has been referenced in the text you will also get page numbers as well as the "see" or "see also" tag in the location list for that entry. This is because the glossary mechanism works in the same way as \index which suffers from the same drawback.

The alternative is to suppress the location list (with nonumberlist) and use, e.g., see also \gls{Blackbox} in the description of "Empirical" and not use the "see" key (as in the first example in section 8 of the user guide).

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.