Latest news 2024-03-02: Ebook sale (3rd–9th March 2024): short story cybercrime fiction Unsocial Media free; short story noir crime fiction I’ve Heard the Mermaid Sing free; crime fiction novel The Private Enemy US$1.99; illustrated children’s story The Foolish Hedgehog US$0.99. For further details, see latest blog post.

Bug Tracker RSS feed

I’m currently working on a major new version of the datatool package. This may take a while. Please be patient. (Experimental version available for testing.)

ID 163🔗
Date: 2020-06-23 09:21:26
Status Closed (Not a Bug)
Category glossaries
Version 4.43
Summary Inverted crossref (see and seealso) behavior

Sign in to subscribe to notifications about this report.


It seems cross-references (i.e. "see" and "seealso" attributes of glossaryentries) are inverted (relative behavior of \gls) when building the glossary. Example: These glossary entries exist and are referencing each other in the following way: Output in glossary: Expected output in glossary: See fuller description at [TeX.SX Link]


Download (932B)




        description={Item 1 see}
        description={Item 1 seealso}
        description={Item 1 gls}
        description={Item2 2, not like \gls{item1gls} at all.},
        description={Item 3 see},
        description={Item 3 seealso},

  I reference \gls{item2}, but none of the others directly in the text.




This is the documented behaviour of the see and seealso keys. The description of the see key in chapter 4 of the glossaries user manual starts as follows (emphasis in the original):

see Cross-reference another entry. Using the see key will automatically add this entry to the glossary, but will not automatically add the cross-referenced entry.
As mentioned in the glossaries manual, the see key essentially provides a convenient shortcut that performs
\glssee[tag]{label}{xr-label list}
after the entry has been defined. It's this command that performs the indexing.

If you want to avoid this automatic indexing, consider using bib2gls instead, which provides much better handling of these cross-references.



Add Comment

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.


You can use the following markup:


[pre]Displayed verbatim[/pre]
[quote]block quote[/quote]

In line:

[file]file/package/class name[/file]
[em]emphasized text[/em]
[b]bold text[/b]
[url]web address[/url] [sup]superscript[/sup]

Ordered list:
[li]first item[/li]
[li]second item[/li]

Unordered list:
[li]first item[/li]
[li]second item[/li]

You can use the Preview button to review your message formatting before submitting.

Page permalink: