RolfBremer / in-dexter

Automatically create a handcrafted index in typst.
Apache License 2.0
57 stars 7 forks source link

Support for multi-page indexing? #21

Open ironupiwada opened 3 months ago

ironupiwada commented 3 months ago

Is support for multi-page indexing anticipated in the future (to print, for example, 50-52)? In LaTeX, there is such a support, for example using the \index environment (an instance below cited for https://en.wikibooks.org/wiki/LaTeX/Indexing):

\index{Quantum Mechanics!History|(}
In 1901, Max Planck released his theory of radiation dependent on quantized energy.
While this explained the ultraviolet catastrophe in the spectrum of 
blackbody radiation, this had far larger consequences as the beginnings of quantum mechanics.
...
\index{Quantum Mechanics!History|)}

Optionally, is there any advanced workaround to output multi-page indexes manually with this package?

hurzl commented 3 months ago

And automatic f. and ff. ... The page range is also done automatically by makeindex ...

ironupiwada commented 3 months ago

The page range is also done automatically by makeindex ...

Well, I don't think so:

obraz

Using the latest versions of Typst (0.11.1) and in-dexter (0.5.3), I'm unable to merge multi-page indices (such as 189-194, which I intend to output). The documentation provided in the sample usage PDF doesn't offer any guidance on this issue.

hurzl commented 3 months ago

Well, I don't think so:

makeindex means LaTeX

RolfBremer commented 3 months ago

Currently there is no support for multi page indexing in in-dexter, but the functionality is sure very nice to have. We will have a deeper look into it. Same for "ff.", "f.".

Thanks!

RolfBremer commented 1 month ago

We just committed 0.6.0 with support for index reference ranges and continuations(f., ff.). If no issues appear, we will submit it to the typst universe soon.

hurzl commented 1 month ago

It's nice to have explicit ranges, but can it find the ranges automatically like in my example?

RolfBremer commented 1 month ago

It's nice to have explicit ranges, but can it find the ranges automatically like in my example?

We will have a look into that as well.