documentation: parameters of \setuplist
I tried to complete https://wiki.contextgarden.net/Command/setuplist, but I don’t understand all parameters. Can anyone explain these please: * state (start stop): what does this en-/disable? collecting entries? * label (yes no none Name): language dependent labels? as a prefix or what? * location (none, here): disable placement? when makes this sense? * aligntitle (yes no): align which part to what? * symbol (one two three none default): where is this used? Expect more questions… Hraban
Hi Hraban,
I can help with one - aligntitle means an unnumbered section will align in
the table of contents under the number rather than the title. So for
example if you have a TOC combining \section and \subject entries, they
would look like this:
1 ... A section
A subject
rather than
1 ... A section
...... A subject
Duncan
On Mon, 22 Apr 2024 at 17:09, Henning Hraban Ramm
Henning Hraban Ramm schrieb am 23.04.2024 um 21:43:
You can use the key to set language dependent texts for the section counters in the list entry, with "yes" the values from the document are used but you can also set whatever label you want. \setuplabeltext [en] [chapter=Chapter , appendix=Appendix , hraban=Hraban ] %\setuplist[chapter][label=hraban,width=3cm] \setuplist[chapter][label=yes,width=3cm] \starttext \startfrontmatter \completecontent \stopfrontmatter \startbodymatter \chapter{First chapter} \chapter{Second chapter} \stopbodymatter \startappendices \chapter{First appendix} \stopappendices \stoptext Wolfgang
Am 23.04.24 um 23:14 schrieb Wolfgang Schuster:
Thank you! So it is related to \setuplabeltext as I suspected, while I didn’t understand why we need label _and_ prefix, until I recognized there’s only pageprefix… (I had prefix in my list of parameters, maybe some MkII leftover).
Yes, now I understand. Hraban
In the source there is a comment relating to location: %D Regular list entries are bound to a specific location in order to get the right %D pagenumber etc.\ associated. When pushing something inbetween (in mkiv) it ends %D up directtly in the list. This is the default because otherwise users will wonder %D why spacing might get messed up (due to an unseen but present node). It is %D possible to force a location by explicitly setting \type {location} to \type %D {here}. %D %D Another way to force a certain order is to set the \type {order} variable when %D placing a list. The \type {command} option only pushes commands into the right %D order, and \type {all} orders all entries (which might be too much). In this case %D no specific location is needed with the inbetween method. Maybe additional %D mechanisms show up some day. See \type {inbetween-001.tex} for an example. I don't really understand what capability the comment is referring to let alone be able to create an example demonstrating the difference. — Bruce Horrocks Hampshire, UK
participants (4)
-
Bruce Horrocks -
Duncan Hothersall -
Henning Hraban Ramm -
Wolfgang Schuster