Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent crash in case of multiple entries in glossary. Changed description of glossary-collection #445

Merged
merged 1 commit into from
Jan 16, 2024

Conversation

fsteimke
Copy link
Contributor

When there are more than one entries for a glossterm, a warning was emitted and than the transformation failed with a runtime error. This was changed so that only the first of many entries will be referenced. Testcase glossary.001 was extended and will cover two entries for one term (Pepper).

The description for glossary-collection was changed. It suggested the necessity for a lot of empty glossentries which must match external entries by xml:id. It is not that difficult. In fact, it seems to be pretty easy, see test glossary.002 and the new description.

  • just create an empty glossary with role='auto'. That's all
  • we dont need @xml:id in glossentries

…ption of glossary-collection.

When there were more than one entries for a glossterm, a warning was emitted and than the transformation failed with a runtime error.
This was changed so that only the first of many entries will be referenced.
Testcase glossary.001 was extended and will cover two entries for one term Pepper.

The description for glossary-collection was changed.
It suggested the necessity for a lot of empty glossentries which must match external entries by xml:id.
Seems to be pretty easy, see test glossary.002.

- just create an empty glossary with role='auto'. That's all
- we dont need @xml:id in glossentries
@ndw ndw merged commit 32dacdf into docbook:main Jan 16, 2024
1 of 3 checks passed
@fsteimke fsteimke deleted the 444-multiple-glossentries branch January 16, 2024 17:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants