Latest news 2020-07-03: SmashWords sale (ends 31st July 2020): 50% off crime/SF novel The Private Enemy and 100% off (free!) I’ve Heard the Mermaid Sing.

Bug Tracker

ID:96 🔗
Status:Closed (Not a Bug)
Submitted by:Fabian
Date:2015-09-17 01:59:32
Summary:dropping/missing entrys


The combination of tex.xdy and glossaries.sty in [example] resulted in the automated creation of input for xindy. That input if written by a human would clearly show a fundamental misunderstanding how xindy works, says Joachim (xindy).

\newglossaryentry{foo}{..} should append the gls name ("foo") to the xindy-sort-key in order to make it unique (even after application of merge-rules).

MWE at stackexchange: Missing glossaries entry despite using \glsaddall

Discussion in xindy-discuss@... [xindy mailing list] [xindy mailing list] [xindy mailing list]



description={text t}
name={\ensuremath{\Delta t}},
description={missing text delta}
description={text tau}
description={missing text gamma}
\newacronym{abc}{ABC}{the ABC thing}


This isn't a bug. The glossaries documentation states that you must provide the sort key if the name contains commands. For example:
description={missing text gamma}
This is analogous to \index where you can't do \index{\ensuremath{\gamma_k}} but must do \index{gamma_k@\ensuremath{\gamma_k}}.

The suggestion, if implemented in glossaries, would break plenty of existing documents that rely on the sort key behaving as documented (for example, dual-entry glossaries that use a prefixing system for the label). The solution is to either add the sort key for each entry or provide a command that sets the sort key from the label. For example:


description={missing text gamma}}

Update 2020-03-01: note that the glossaries-extra package's symbols option provides \glsxtrnewsymbol which does something very similar.

Add comment or return to search results.

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

E mail:
Confirm E mail:
Confirm Bug ID:

To unsubscribe from all notifications use the notifications page.


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:
[li]first item[/li]
[li]second item[/li]

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

Click on the Preview button to preview the message.

Return to search results.