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

Can I put the glossary at the start of the document ? #106

Open
filchristou opened this issue Feb 11, 2025 · 6 comments
Open

Can I put the glossary at the start of the document ? #106

filchristou opened this issue Feb 11, 2025 · 6 comments
Assignees
Milestone

Comments

@filchristou
Copy link

I see that all examples have the glossary at the end. E.g. https://github.com/typst-community/glossarium/blob/master/examples/import-terms-from-yaml-file/main.typ

I tried putting #print-glossary(entries, show-all: false) before and obviously it didn't work.

Can you suggest a way to put the glossary with references and all before the actual text ?

@quachpas quachpas self-assigned this Feb 12, 2025
@quachpas quachpas added this to the 0.5.4 milestone Feb 12, 2025
@quachpas
Copy link
Collaborator

Hello, this is not possible ATM. I will see to adding a feature for that.

@tfachada
Copy link

In case this info is useful: this was doable in Typst 0.12, meaning it was broken by either Typst 0.13 or Glossarium 0.5.3.

@quachpas
Copy link
Collaborator

Yes, I inadvertently broke this, when I fixed another issue. I'll see that it's brought back correctly.

@q-wertz
Copy link

q-wertz commented Feb 18, 2025

Just as additional information: it also doesn't work on typst 0.12.0 and glossarium 0.5.2.

@tfachada
Copy link

I noticed that this issue came from commits 19606fa and 0af6b40, and I assume, from the description of one of them, that they're related to the changelog entry Fix layout divergence when glossary descriptions are nested.. @quachpas what did you mean with "nested" here?

@quachpas
Copy link
Collaborator

I changed querying so it queried backwards, to fix refs in description but that breaks more things than it fixes. I might just revert it in the next release, depending on if I find a way to preserve both behaviours

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

No branches or pull requests

4 participants