From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl (ConTeXt List)
Subject: Re: how to define another part of a document
Date: Fri, 23 Feb 2001 11:52:08 +0100 [thread overview]
Message-ID: <3.0.6.32.20010223115208.01939240@server-1> (raw)
In-Reply-To: <200102211312.OAA01474@anxur.fi.muni.cz>
At 02:12 PM 2/21/01 +0100, Han The Thanh wrote:
>> how can I define another part for a document which has been not pre-defined
>> yet? E.g. something similar \startappendices ... \stopappendices, but for
>> another purpose?
>
>I looked into section 8.5 in the manual, but didn't get it yet. The
>relevent command seems to be \definesectionblock, however after eg
>
>\definesectionblock [myblock] [headnumber=no]
>
>I don't know what is the command to start/stop the block. I tried either
>
>\definesectionblock [myblock] [headnumber=no]
>\startmyblock ... \stopmyblock
>
>
>or
>
>
>\definesectionblock [myblockpart] [headnumber=no]
>\startmyblockmatter ... \stopmyblockmatter
>
>(guessed from \definesectionblock [bodypart] and
>\startbodymatter ... \stopbodymatter)
\definesectionblock [myblock] [myblocks]
\setupsectionblock [myblock] [number=no]
\starttext
\startmyblocks
\chapter{Whow, this is My Block!}
\stopmyblocks
\stoptext
The two argument approach permits definitions of more meaningful commands,
like singular/plural destinction (needed for the
dutch interface) like frontpart for the general name of a block, but
frontmatter for the command [suggested b y sebastian rahtz].
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-02-23 10:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <From thanh at "Feb 20, 1 09:44:26 pm">
2001-02-21 13:12 ` Han The Thanh
2001-02-23 10:52 ` Hans Hagen [this message]
2001-02-23 15:54 ` Han The Thanh
2001-02-23 16:13 ` Hans Hagen
2001-03-21 10:05 ` Peter Jander
2001-03-21 14:32 ` Hans Hagen
2001-03-21 15:25 ` Peter Jander
2001-03-21 15:55 ` Hans Hagen
2001-03-21 17:59 ` Peter Jander
2001-03-22 6:32 ` Hans Hagen
2001-02-20 20:44 Han The Thanh
2001-02-20 21:15 ` Berend de Boer
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=3.0.6.32.20010223115208.01939240@server-1 \
--to=pragma@wxs.nl \
--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).