ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: James Fisher <jameshfisher@gmail.com>
To: ntg-context@ntg.nl
Subject: Margin terminology -- badly documented, undocumented, or 	misdocumented
Date: Thu, 25 Feb 2010 04:39:55 +0000	[thread overview]
Message-ID: <771da05a1002242039x6086f7bbi31d0b1090634f842@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1731 bytes --]

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://getfo.org/context_xml/page3.html ,
which the first page recommends.
More, the two pages seem pretty contradictory.

Consider my situation: I'm trying to set up an A4 page with the following
margins (I use the term margin to mean the space from the edge of the
physical paper to the edge of the body text area):

top: 2.97cm
bottom: 2.97cm
left: 2.1cm
right: 2.1cm

For the moment, I don't care at all about header and footer space, nor notes
in the margins; I'm just trying to get the above margins.
However, with all conceivable combinations of commands at both of those
pages, I've been unable to set anything like this up.

Based on the getfo.org page, I should be able to set up these left and right
margins with:

backspace=2.1cm,
cutspace=2.1cm

But, looking at the result, and also with using \showlayout (which for some
reason, AFAICS, generates four identical pages at the beginning of the
document), this quite obviously doesn't do what getfo.org claims.

I have also tried setting everything to 0cm with the exception of any random
one of the measurements that go into making a margin, which I would set to
2.1cm.  No avail here, either.

Can someone give me the configuration I would need for the above required
margins?  Even better, can someone give me the definitive definitions of all
the terms used in http://wiki.contextgarden.net/Layout, algebraically rather
than as ambiguous tables of "Remarks"?  This would help a bunch.


Many thanks,


James Fisher

[-- Attachment #1.2: Type: text/html, Size: 2108 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2010-02-25  4:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25  4:39 James Fisher [this message]
2010-02-25 10:23 ` Hans Hagen
2010-02-25 10:57   ` R. Bastian
2010-02-25 20:17   ` James Fisher
2010-02-26  9:03     ` luigi scarso
2010-03-02 11:03     ` Hans Hagen
2010-03-02 21:33       ` James Fisher
2010-03-02 21:42         ` Wolfgang Schuster
2010-03-02 21:59           ` James Fisher
2010-03-02 23:18         ` luigi scarso
2010-03-08  9:21         ` 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=771da05a1002242039x6086f7bbi31d0b1090634f842@mail.gmail.com \
    --to=jameshfisher@gmail.com \
    --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).