From: Alan Braslau <alan.braslau@cea.fr>
To: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TOC : Chapter title under its number (separate lines)
Date: Fri, 27 May 2011 11:14:26 +0200 [thread overview]
Message-ID: <20110527091426.GB17312@iram-ha-003840.extra.cea.fr> (raw)
In-Reply-To: <46593206-7C30-4DB8-AD80-FA6BE32CFC7F@googlemail.com>
On Thu, May 26, 2011 at 08:16:21PM +0200, Wolfgang Schuster wrote:
>
> Am 26.05.2011 um 18:48 schrieb Alan Braslau:
>
> > \setuplist[chapter][label=yes,alternative=vertical,command=\ChapterList,interaction=all]
> >
> > Almost works. Almost in that all lines get indented by one level,
> > and then the page number (and the title if it is long and multi-line)
> > stick(s) out by this much on the right.
> >
> > The manual is a bit cryptic concerning horizontal and vertical:
> > "As an alternative for none, we can use horizontal and vertical.
> > Both commands have their spacing tuned for typesetting lists in
> > for instance menus."
>
> I don’t read the manual very often, so i missed this.
Before asking for help, I always
1) experiment
2) look in the manual(s)
3) search the mailing list
4) consult the wiki
5) try to understand the sources
I'm sure that you start with the last step.
>
> There are two ways to have a interactive list:
>
> 1. Patch the command alternative
>
> 2. Introduce a new alternative which has interactive support
> plus a few more missing features (e.g. label support)
>
> Wolfgang
In fact,
\setuplist [chapter] [label=yes]
should work "out of the box".
Currently, one must set:
\setuplabeltext [chapter=Chapter ] % with trailing space; blank by default
\setuplabeltext [appendix=Appendix ] % with trailing space; blank by default
(This *should* be included in the language files, not redefined by the user. Indeed, "\setuphead [chapter] [label=no]" could be the default, not blanking out the labeltext.)
Secondly, the spacing of the TOC is all wrong. This should not need patching to yield an acceptable result.
Alan
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-05-27 9:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 22:59 Mathieu DUPONT
2011-05-24 11:42 ` Wolfgang Schuster
2011-05-24 13:09 ` Mathieu DUPONT
2011-05-24 13:33 ` Mathieu DUPONT
2011-05-24 14:04 ` Wolfgang Schuster
2011-05-24 14:13 ` Mathieu DUPONT
2011-05-24 14:20 ` Wolfgang Schuster
2011-05-24 14:34 ` Mathieu DUPONT
2011-05-26 15:13 ` Alan Braslau
2011-05-26 15:30 ` Wolfgang Schuster
2011-05-26 16:48 ` Alan Braslau
2011-05-26 18:16 ` Wolfgang Schuster
2011-05-27 9:14 ` Alan Braslau [this message]
2011-05-27 13:33 ` Mathieu DUPONT
2011-05-27 14:00 ` Alan Braslau
2011-05-27 14:04 ` Mathieu DUPONT
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=20110527091426.GB17312@iram-ha-003840.extra.cea.fr \
--to=alan.braslau@cea.fr \
--cc=ntg-context@ntg.nl \
--cc=schuster.wolfgang@googlemail.com \
/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).