Re: [NTG-context] mkiv structure

2009-07-09 Thread Hans Hagen
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

Re: [NTG-context] mkiv structure

2009-07-09 Thread Alan BRASLAU
On Thursday 09 July 2009 09:38:07 Hans Hagen wrote: part is just the first level of sectioning and happens to be configured in such a way that it does not show a title; really nothing special It is a question of default setup. \part is configured differently : no title, additional page number,

Re: [NTG-context] mkiv structure

2009-07-09 Thread Wolfgang Schuster
Am 09.07.2009 um 09:59 schrieb Alan BRASLAU: On Thursday 09 July 2009 09:38:07 Hans Hagen wrote: part is just the first level of sectioning and happens to be configured in such a way that it does not show a title; really nothing special It is a question of default setup. \part is

Re: [NTG-context] mkiv structure

2009-07-08 Thread Hans Hagen
Wolfgang Schuster wrote: Am 03.07.2009 um 16:04 schrieb Hans Hagen: 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

Re: [NTG-context] mkiv structure

2009-07-08 Thread Hans Hagen
Hi Wolfgang 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

Re: [NTG-context] mkiv structure

2009-07-06 Thread Hans Hagen
Alan BRASLAU wrote: On Friday 03 July 2009 16:04:07 Hans Hagen wrote: 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

Re: [NTG-context] mkiv structure

2009-07-05 Thread Alan BRASLAU
On Friday 03 July 2009 16:04:07 Hans Hagen wrote: 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

Re: [NTG-context] mkiv structure

2009-07-03 Thread Alan BRASLAU
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

Re: [NTG-context] mkiv structure

2009-07-03 Thread Hans Hagen
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

Re: [NTG-context] mkiv structure

2009-07-02 Thread Alan BRASLAU
On Monday 15 June 2009 10:02:35 Hans Hagen wrote: I was wondering ... the last time quite some nice small test samples were posted for testing the structure code % Example taken from cont-enp.pdf % However, adding \part{} is problematic... % (maybe someone can correct this?) %

Re: [NTG-context] mkiv structure

2009-07-02 Thread Hans Hagen
Alan BRASLAU wrote: On Monday 15 June 2009 10:02:35 Hans Hagen wrote: I was wondering ... the last time quite some nice small test samples were posted for testing the structure code % Example taken from cont-enp.pdf % However, adding \part{} is problematic... % (maybe someone can correct

[NTG-context] mkiv structure

2009-06-15 Thread Hans Hagen
Hi, I was wondering ... the last time quite some nice small test samples were posted for testing the structure code maybe we can set up a repository with such test files (but someone needs to coordinate it) where they can end up after posting and fixing possible errors in the examples; we