From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: chapter with letters rather than numbers?
Date: Tue, 18 Apr 2006 09:00:50 -0400 (EDT) [thread overview]
Message-ID: <Pine.WNT.4.63.0604180856490.3068@nqvgln> (raw)
In-Reply-To: <443F4910.4060509@nibua-r.org>
On Fri, 14 Apr 2006, Renaud AUBIN wrote:
> Johannes Graumann a écrit :
>
>> Hi,
>>
>> How would I use \setuphead[chapter] to have consecutive letters
>> rather than numbers assigned to chapters (in my appendix)?
>>
> Use the following structure:
>
> \startfrontmatter ... \stopfrontmatter
> \startbodymatter ... \stopbodymatter
> \startappendices ... \stopappendices
> \startbackmatter ... \stopbackmatter
which is the right way to do things. However, if you do want to change
chapter numbering,
\setupsection
[section-2]
[bodypartconversion=Character]
will do the trick.
Aditya
--
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008
prev parent reply other threads:[~2006-04-18 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 5:41 Johannes Graumann
2006-04-14 7:02 ` Renaud AUBIN
2006-04-14 7:10 ` Johannes Graumann
2006-04-18 13:00 ` Aditya Mahajan [this message]
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=Pine.WNT.4.63.0604180856490.3068@nqvgln \
--to=adityam@umich.edu \
--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).