From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: unnumbered chapters
Date: Mon, 27 Sep 2010 16:07:09 +0200 [thread overview]
Message-ID: <201009271607.09528.alan.braslau@cea.fr> (raw)
A standard (wiki, manual) means of obtaining an unnumbered chapter
is to use \title, but this does not create an entry into the toc.
So one can create a new head, as in:
\definehead [unnumberedchapter] [chapter]
\setuphead [unnumberedchapter] [number=no]
\definecombinedlist [content] [unnumberedchapter,chapter,section]
\setuplist [unnumberedchapter] [headnumber=no]
Bof! (pardon my French, as they say in polite circles)
Much easier (or cleaner if you wish), using the structured syntax, is:
\startchapter [number=no,incrementnumber=no,
title={Conclusions}]
\stopchapter
(The {} are not necessary, but I believe that this may make things more
readable, given the practice to enclose typeset text within curly braces.)
A problem occurs, though, if we use labels, as in:
\setuplabeltext [chapter={Chapter }] % with trailing space; blank by default
(which Hans *never, ever* uses, by the way...)
We then get:
Chapter 1 First
Chapter 2 Second
Chapter Conclusions
I think that the macros are missing a "label=no" option.
Unless, that is, I am missing something obvious.
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
___________________________________________________________________________________
reply other threads:[~2010-09-27 14:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201009271607.09528.alan.braslau@cea.fr \
--to=alan.braslau@cea.fr \
--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).