From: "Uwe Koloska" <uwe.koloska@mailbox.tu-dresden.de>
Subject: chars for appendix sections
Date: Wed, 31 Jan 2001 12:32:14 +0100 [thread overview]
Message-ID: <01013112321400.30780@bilbo> (raw)
Hello,
I just tried to make a document (equivalent to LaTeX article) with section
as the highest sectioning command. And I want the appendix sections marked
with chars. I followed the advice in the manual -- but still no chars.
What went wrong?
Here comes the simples testfile:
\setupsection
[section-3] % also tried sectionlevel-3
[appendixconversion=Character, % Watch the capital
previousnumber=no]
\starttext
\completecontent
\startbodymatter
\section{no. one}
\section{no. two}
\stopbodymatter
\startappendices
\section{Oh, no!}
\section{Help, \dots}
\stopappendices
\stoptext
Could you please help me (yeah, yeah, yeah yeaaaah)
Uwe
--
mailto:koloska@rcs.urz.tu-dresden.de
http://rcswww.urz.tu-dresden.de/~koloska/
-- --
right now the web page is in german only
but this will change as time goes by ;-)
next reply other threads:[~2001-01-31 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 11:32 Uwe Koloska [this message]
2001-01-31 13:40 ` Hans Hagen
2001-01-31 14:45 ` S2P development
2001-01-31 15:46 ` Hans Hagen
2001-01-31 14:32 ` Hans Hagen
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=01013112321400.30780@bilbo \
--to=uwe.koloska@mailbox.tu-dresden.de \
/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).