ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: mkiv structure
Date: Fri, 3 Jul 2009 10:12:34 +0200	[thread overview]
Message-ID: <200907031012.35046.alan.braslau@cea.fr> (raw)
In-Reply-To: <4A4D25E5.7070105@wxs.nl>

In my experience, a \part is generally
(except in some rather technical documents)
not treated as a super-chapter, that is
chapter numbers (and titles) are not reset
and retain their status as if the book was not
divided into parts.

A very long work is commonly broken into "volumes".
Here, each volume may or may not reset chapter numbers.
Page numbering may or may not reflect the volume number.
This is a sylistic choice.

In my understanding, \part serves to delimit
logical sections of related chapters, not volumes.
Maybe I am wrong in this interpretation;
maybe \part is to be used to delimit volumes.
Nevertheless, it should be relatively simple
for the basic user to be able to select the desired behavior
without having to acquire an understanding of the inner workings
such as prefixsets and sectionsegments.

Alan

On Thursday 02 July 2009 23:25:57 Hans Hagen wrote:
> keys like partnumber (<section>number) are obsolete ... and replace by
> prefxset etc (see strc-def.mkiv for example definitions)

Obsolete in mkii?
Shouldn't basic use (read standard users)
treat source text transparently
between mkii and mkiv?

\setuphead[part][placehead=yes,resetnumber=no]
\doifmodeelse{mkiv}{
	\setuphead[part][sectionsegments=1:1]
	\setupstructureheads[sectionsegments=2:5]
} {
	\setuppagenumbering[partnumber=no]
	\setuplist[chapter,section,subsection,subsubsection]
		[partnumber=no]
}

___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2009-07-03  8:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15  8:02 Hans Hagen
2009-07-02 18:34 ` Alan BRASLAU
2009-07-02 21:25   ` Hans Hagen
2009-07-03  8:12     ` Alan BRASLAU [this message]
2009-07-03 14:04       ` Hans Hagen
2009-07-05  9:32         ` Wolfgang Schuster
2009-07-08  8:28           ` Hans Hagen
2009-07-08 10:10           ` Hans Hagen
2009-07-05 22:20         ` Alan BRASLAU
2009-07-06 11:44           ` Hans Hagen
2009-07-09  7:38       ` Hans Hagen
2009-07-09  7:59         ` Alan BRASLAU
2009-07-09 12:27           ` Wolfgang Schuster
2009-07-09 12:39             ` Hans Hagen
2009-07-02 19:17 ` references (mainlanguage) Alan BRASLAU
2009-07-02 21:07   ` Willi Egger
2009-07-03  7:07     ` Alan BRASLAU
2009-07-02 21:22   ` 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=200907031012.35046.alan.braslau@cea.fr \
    --to=alan.braslau@cea.fr \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).