From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: new structure code
Date: Sun, 14 Jun 2009 15:16:20 +0200 [thread overview]
Message-ID: <4A34F824.9010908@wxs.nl> (raw)
In-Reply-To: <200906141330.26279.alan.braslau@cea.fr>
Alan BRASLAU wrote:
> Hello,
>
> Different structuring behavior mkiv and mkii;
> How can the following minimal example be achieved under mkiv?
> (mkii gives the desired behavior)
>
> Alan
>
> \setuphead[part][resetnumber=no,placehead=yes]
> \setuplist[part,chapter,section][partnumber=no]
> \starttext
> \part{part one}
> \chapter{chapter one}
> \section{section one}
> \section{section two}
> \chapter{chapter two}
> \section{section one}
> \section{section two}
> \part{part two}
> \chapter{chapter three}
> \section{section one}braslau
> \section{section two}
> \chapter{chapter four}
> \section{section one}
> \section{section two}
> \stoptext
keys like 'partnumber' are gone in mkiv; we now have sets and segments;
here is the variant with segments: (2 = section 2 == chapter)
\setuphead[part] [resetnumber=no,placehead=yes]
% \setuphead[chapter][sectionsegments=2:100]
% \setuphead[section][sectionsegments=2:100]
\setupstructureheads[sectionsegments=2:100]
you can tune each number (also at list placement time or whatever)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-06-14 13:16 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 13:38 Wolfgang Schuster
2009-04-10 17:09 ` Wolfgang Schuster
2009-04-10 20:01 ` Wolfgang Schuster
2009-04-14 12:21 ` Hans Hagen
2009-04-14 20:56 ` Hans Hagen
2009-04-15 16:04 ` Yanrui Li
2009-04-15 16:09 ` Hans Hagen
2009-04-16 7:59 ` Hans Hagen
2009-04-16 14:44 ` Yanrui Li
2009-04-16 15:35 ` Bug in mkiv: \setupinteraction (Was: new structure code) Otared Kavian
2009-04-16 16:23 ` Yanrui Li
2009-04-16 20:56 ` new structure code Hans Hagen
2009-04-10 20:11 ` Peter Münster
2009-04-10 20:35 ` Wolfgang Schuster
2009-04-13 11:53 ` Hans Hagen
2009-04-10 20:24 ` Khaled Hosny
2009-04-10 20:28 ` Wolfgang Schuster
2009-04-10 21:27 ` Khaled Hosny
2009-04-10 21:45 ` Wolfgang Schuster
2009-04-10 23:29 ` Hans Hagen
2009-04-11 0:32 ` Yanrui Li
2009-04-11 1:46 ` Yanrui Li
2009-04-13 11:12 ` Hans Hagen
2009-04-12 11:06 ` Wolfgang Schuster
2009-04-12 12:43 ` Hans Hagen
2009-04-13 13:09 ` Wei-Wei Guo
2009-04-16 0:43 ` Wei-Wei Guo
2009-04-16 7:55 ` Hans Hagen
2009-04-20 7:58 ` Wolfgang Schuster
2009-04-20 8:37 ` Hans Hagen
2009-04-13 15:54 ` Longmin Wang
2009-04-24 17:22 ` Kevin D. Robbins
2009-04-24 17:37 ` Wolfgang Schuster
2009-04-24 17:44 ` Kevin D. Robbins
2009-04-24 18:36 ` Hans Hagen
2009-04-24 18:54 ` Kevin D. Robbins
2009-04-24 20:54 ` Hans Hagen
2009-06-14 11:30 ` Alan BRASLAU
2009-06-14 13:16 ` Hans Hagen [this message]
2009-06-14 18:16 ` Alan BRASLAU
2009-06-14 18:23 ` Hans Hagen
2009-06-14 18:54 ` Alan BRASLAU
2009-06-15 7:23 ` Hans Hagen
2009-04-24 18:28 ` Kevin D. Robbins
2009-04-24 18:34 ` 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=4A34F824.9010908@wxs.nl \
--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).