Re: [NTG-context] Margin terminology -- badly documented, undocumented, or misdocumented

2010-03-08 Thread Hans Hagen
On 2-3-2010 22:33, James Fisher wrote: A minor other thing confusing me is the terminology; mainly 'cut' and 'back'. Are these ConTeXt-specific terms or are they found elsewhere? 'Back' would make more sense to me as 'binding' or 'spine', and the edge referred to as 'cut' is referred to in Wiki

Re: [NTG-context] Margin terminology -- badly documented, undocumented, or misdocumented

2010-03-02 Thread luigi scarso
On Tue, Mar 2, 2010 at 10:33 PM, James Fisher wrote: > That makes sense. > > The main thing confusing me on contextgarden is: > >    if cutspace == 0pt then >       cutspace = backspace >    end > > Which I would guess is meant to allow you to just specify backspace if you > want symmetrical margi

Re: [NTG-context] Margin terminology -- badly documented, undocumented, or misdocumented

2010-03-02 Thread James Fisher
Fairy muff! James On Tue, Mar 2, 2010 at 9:42 PM, Wolfgang Schuster < schuster.wolfg...@googlemail.com> wrote: > Am 02.03.10 22:33, schrieb James Fisher: > > That makes sense. >> >> The main thing confusing me on contextgarden is: >> >> if cutspace == 0pt then >> cutspace = backspace >>

Re: [NTG-context] Margin terminology -- badly documented, undocumented, or misdocumented

2010-03-02 Thread Wolfgang Schuster
Am 02.03.10 22:33, schrieb James Fisher: That makes sense. The main thing confusing me on contextgarden is: if cutspace == 0pt then cutspace = backspace end Which I would guess is meant to allow you to just specify backspace if you want symmetrical margins; but what if we want a 0

Re: [NTG-context] Margin terminology -- badly documented, undocumented, or misdocumented

2010-03-02 Thread James Fisher
That makes sense. The main thing confusing me on contextgarden is: if cutspace == 0pt then cutspace = backspace end Which I would guess is meant to allow you to just specify backspace if you want symmetrical margins; but what if we want a 0pt cutspace? A minor other thing confusing

Re: [NTG-context] Margin terminology -- badly documented, undocumented, or misdocumented

2010-03-02 Thread Hans Hagen
On 25-2-2010 21:17, James Fisher wrote: Hi Hans, Thanks for the reply -- and sorry for the rather grumpy way in which I posed the question. The problem for me was this mysterious "width=middle", "height=middle" -- this is fairly undocumented at http://wiki.contextgarden.net/Layout . There is

Re: [NTG-context] Margin terminology -- badly documented, undocumented, or misdocumented

2010-02-26 Thread luigi scarso
On Thu, Feb 25, 2010 at 9:17 PM, James Fisher wrote: > document this myself, but what is it that "width=middle" actually *does*? I suppose if cutspace == 0pt then cutspace = backspace end makeupwidth = paperwidth- backspace -cutspace (as wiki says, from page-lay.mkiv, 2009-11-

Re: [NTG-context] Margin terminology -- badly documented, undocumented, or misdocumented

2010-02-25 Thread James Fisher
Hi Hans, Thanks for the reply -- and sorry for the rather grumpy way in which I posed the question. The problem for me was this mysterious "width=middle", "height=middle" -- this is fairly undocumented at http://wiki.contextgarden.net/Layout . There is a mention of "width=middle", but it's just

Re: [NTG-context] Margin terminology -- badly documented, undocumented, or misdocumented

2010-02-25 Thread R. Bastian
On Thu, 25 Feb 2010 11:23:04 +0100 Hans Hagen scribit: > On 25-2-2010 5:39, James Fisher wrote: > > Hi all. > > > > > > I am trying to understand the terminology for the \definelayout and > > \setuplayout commands. > > Unfortunately the documentation at > > http://wiki.contextgarden.net/Layoutdoe

Re: [NTG-context] Margin terminology -- badly documented, undocumented, or misdocumented

2010-02-25 Thread Hans Hagen
On 25-2-2010 5:39, James Fisher wrote: Hi all. I am trying to understand the terminology for the \definelayout and \setuplayout commands. Unfortunately the documentation at http://wiki.contextgarden.net/Layoutdoesn't correspond to the actual output I get. Nor does the 'documentation' at http://