From: Hans Hagen <pragma@wxs.nl>
To: Alan BRASLAU <alan.braslau@cea.fr>
Cc: ntg-context@ntg.nl
Subject: Re: mkiv structure
Date: Fri, 03 Jul 2009 16:04:07 +0200 [thread overview]
Message-ID: <4A4E0FD7.4040903@wxs.nl> (raw)
In-Reply-To: <200907031012.35046.alan.braslau@cea.fr>
Alan BRASLAU wrote:
> 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.
there will be presets but i had no time yet to make them
> Obsolete in mkii?
> Shouldn't basic use (read standard users)
> treat source text transparently
> between mkii and mkiv?
no, this is one of the few places where there will be a difference; we
have way more control now (also to the detail of setting up styles for
each separator in a composed number) but that comes at a price; i don't
want to complicate the mkiv code with too many compatibility hacks
Hans
-----------------------------------------------------------------
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-07-03 14:04 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
2009-07-03 14:04 ` Hans Hagen [this message]
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=4A4E0FD7.4040903@wxs.nl \
--to=pragma@wxs.nl \
--cc=alan.braslau@cea.fr \
--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).