From: Hans Hagen <j.hagen@xs4all.nl>
To: denis.maier@unibe.ch, ntg-context@ntg.nl
Subject: Re: Heading for endnotes / grouped by chapter endnotes
Date: Thu, 1 Jul 2021 00:11:44 +0200 [thread overview]
Message-ID: <033bf485-973e-6071-f00c-1e3d681ec561@xs4all.nl> (raw)
In-Reply-To: <7f0c31b49cd04179b81bb0b18a145de3@unibe.ch>
On 6/30/2021 9:04 PM, denis.maier@unibe.ch wrote:
>
>
>> Von: Hans Hagen <j.hagen@xs4all.nl>
>>
>> On 6/30/2021 4:57 PM, denis.maier@unibe.ch wrote:
>>>
>> [...]
>>>
>>> Will this interfere with how parts are displayed in the regular table
>>> of contents?
>>
>> sure but you can group
>>
>> \start
>> .. flush the list
>> \stop
>>
>> although it's not really needed when you do this at the end of the document
>
> Hmm, but don't you usually style thing before \starttext? (Ok, you can use setups to keep the definitions in one place.)
indeed. one can use setups or define a combined list that has the settings
>>> 2. Does this treat endnotes just like a list entry, with page numbers
>>> and so?
>>
>> indeed
>
> Ok, so you cannot use the regular \setupnotation[endnote][settings] for styling the endnotes?
well, this is typical list usage so .. but if needed one can define a so
called list alternative for it but it probably doesn't pay off.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-06-30 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 11:05 denis.maier
2021-06-29 10:53 ` denis.maier
2021-06-29 14:20 ` Hans Hagen
2021-06-30 8:06 ` denis.maier
2021-06-30 9:27 ` Hans Hagen
2021-06-30 14:57 ` denis.maier
2021-06-30 16:09 ` Hans Hagen
2021-06-30 16:15 ` Hans Hagen
2021-06-30 19:04 ` denis.maier
2021-06-30 22:11 ` Hans Hagen [this message]
2021-06-30 19:39 ` Rik Kabel
2021-07-02 7:50 ` denis.maier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=033bf485-973e-6071-f00c-1e3d681ec561@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=denis.maier@unibe.ch \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).