Notation-list

[Paul Emigh]

Is there any way to get a notation-list to show only a subset of things tagged with notation (specifically, all the notations in a given chapter)?  I'd like to be able to show all the important definitions and principles from a given chapter in one list at the end of the chapter.  <list-of> will make such a list, but it isn't as compact and aesthetic as the table that notation-list creates, since you have to click on any item to actually see what it is.

[Rob Beezer]

Dear Paul,

Interesting idea. As I am sure you have noticed, you can probably place a
#notation-list just about anywhere you want.

It is designed on the idea that it will be the majority of the content of an
#appendix in the #backmatter. You have to build and title that appendix, and
then #notation-list "generates" all the content.

Can you tell us where you might locate a chapter-filtered version for a
#chapter? What is the structure of the #chapter (with #section, or not?), and
*exactly* how would you place #notation-list? (I.e., more precisely than "at
the end".)

*Anybody* who thinks they might use this someday is free to answer those last
two questions, not just Paul.

Rob

> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to pretext-dev...@googlegroups.com <mailto:pretext-
> dev+uns...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-
> dev/87b6197a-878c-42ab-bcf2-5cee430fbe5cn%40googlegroups.com <https://
> groups.google.com/d/msgid/pretext-dev/87b6197a-878c-42ab-
> bcf2-5cee430fbe5cn%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Andrew Scholer]

Someone related...

It would be nice to be able to automatically generate a chapter level vocabulary list like this:
https://runestone.academy/ns/books/published/chemeketa_cs161_fall25_inperson/variables-operators_vocabulary.html

I would want to do it by making a page and on it putting something like <index-list for="label-name"/>. Using that, one could chose to have section level mini indexes, chapter level ones, part level ones, etc...

I could see wanting to do the same with notation-list were I using it.

Andrew

To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/MTAwMDAzMC5iZWV6ZXI.1764694031%40pnsh.

[Andrew Scholer]

Sorry, the link I provided was a local only one. Here is a generic link to the chapter level vocabulary page:
https://runestone.academy/ns/books/published/welcometoprogramming/variables-operators_vocabulary.html?mode=browsing

[Andrew Scholer]

And again without a typo. (*sigh*)
https://runestone.academy/ns/books/published/welcomeprogramming/variables-operators_vocabulary.html?mode=browsing

[Paul Emigh]

I author and publish a physics textbook with something like 30 chapters, each of which has anywhere from 8-15 sections.  I was imagining making a new section at the end of each chapter (or potentially at the end of a group of related chapters) with a set of key definitions, principles, equations, etc.  I found this is possible to do with list-of (e.g., <list-of elements="definition principle conjecture" divisions="chapter" empty="yes" scope="chapter" />), where the scope="chapter" narrows it down to only having elements of the requested type, but it just doesn't look as elegant to the viewer because you have to go click on each definition or what-not rather than seeing the pre-built table that notation-list outputs.  Andrew's Vocabulary section also has a nice-looking format, but presumably had to be built by hand.  The way I had hoped it would work was that <notation-list> would take the same scope="chapter" option as <list-of>, but I think notation-list has to be empty by definition.

[Rob Beezer]

Thanks for the further clarification, Paul.

> but it just doesn't look as elegant to the viewer

Yes, I get that part.

> I was imagining making a new section

Good answer. That would have been my first guess. ;-)

> at the end of a group of related chapters

Well, we don't really have a way to say chapters are related, except for #part,
and then a notation list for the part would most naturally go into a #chapter,
which would not be so bad, but maybe a bit grand.

I need to go remind myself how @scope is implemented and see if we can perhaps
easily mimic that device. Another option is to have the scope implied by the
location of #notation-list (like setting the scope to the grandparent of the
#notation-list), but that might not be so general-purpose or fool-proof.

I'll look into this as I am able, but am occupied with a few big inititatives
right now (EPUB, website, introductions).

Rob

On 12/2/25 10:22, Paul Emigh wrote:
> I author and publish a physics textbook with something like 30 chapters, each of
> which has anywhere from 8-15 sections.  I was imagining making a new section at
> the end of each chapter (or potentially at the end of a group of related
> chapters) with a set of key definitions, principles, equations, etc.  I found
> this is possible to do with list-of (e.g., <list-of elements="definition
> principle conjecture" divisions="chapter" empty="yes" scope="chapter" />), where
> the scope="chapter" narrows it down to only having elements of the requested
> type, but it just doesn't look as elegant to the viewer because you have to go
> click on each definition or what-not rather than seeing the pre-built table that
> notation-list outputs.  Andrew's Vocabulary section also has a nice-looking
> format, but presumably had to be built by hand.  The way I had hoped it would
> work was that <notation-list> would take the same scope="chapter" option as
> <list-of>, but I think notation-list has to be empty by definition.
>
> On Tuesday, December 2, 2025 at 10:10:34 AM UTC-8 asch...@chemeketa.edu wrote:
>
> And again without a typo. (*sigh*)
> https://runestone.academy/ns/books/published/welcomeprogramming/variables-

> operators_vocabulary.html?mode=browsing <https://runestone.academy/ns/books/
> published/welcomeprogramming/variables-operators_vocabulary.html?mode=browsing>

>
> On Tuesday, December 2, 2025 at 10:09:23 AM UTC-8 Andrew Scholer wrote:
>
> Sorry, the link I provided was a local only one. Here is a generic link
> to the chapter level vocabulary page:
> https://runestone.academy/ns/books/published/welcometoprogramming/

> variables-operators_vocabulary.html?mode=browsing <https://
> runestone.academy/ns/books/published/welcometoprogramming/variables-
> operators_vocabulary.html?mode=browsing>

>
> On Tuesday, December 2, 2025 at 9:01:13 AM UTC-8 Andrew Scholer wrote:
>
> Someone related...
>
> It would be nice to be able to automatically generate a chapter
> level vocabulary list like this:
> https://runestone.academy/ns/books/published/
> chemeketa_cs161_fall25_inperson/variables-operators_vocabulary.html

> <https://runestone.academy/ns/books/published/
> chemeketa_cs161_fall25_inperson/variables-operators_vocabulary.html>

> msgid/pretext- <https://groups.google.com/d/msgid/pretext->
> > dev/87b6197a-878c-42ab-bcf2-5cee430fbe5cn%40googlegroups.com
> <http://40googlegroups.com> <https://
> > groups.google.com/d/msgid/pretext-dev/87b6197a-878c-42ab-
> <http://groups.google.com/d/msgid/pretext-dev/87b6197a-878c-42ab->
> > bcf2-5cee430fbe5cn%40googlegroups.com?
> utm_medium=email&utm_source=footer <http://40googlegroups.com?

> utm_medium=email&utm_source=footer>>.
>
> --
> You received this message because you are subscribed to the
> Google Groups "PreTeXt development" group.
>
> To unsubscribe from this group and stop receiving emails from
> it, send an email to pretext-dev...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/

> pretext-dev/MTAwMDAzMC5iZWV6ZXI.1764694031%40pnsh <https://
> groups.google.com/d/msgid/pretext-dev/
> MTAwMDAzMC5iZWV6ZXI.1764694031%40pnsh>.

>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email

> to pretext-dev...@googlegroups.com <mailto:pretext-
> dev+uns...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-

> dev/9e58de38-f07f-4c40-945f-f83e1869dd6fn%40googlegroups.com <https://
> groups.google.com/d/msgid/pretext-dev/9e58de38-f07f-4c40-945f-
> f83e1869dd6fn%40googlegroups.com?utm_medium=email&utm_source=footer>.