ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Still confused about \setuplayout
Date: Wed, 27 Aug 2008 17:07:50 +0200	[thread overview]
Message-ID: <48B56DC6.90105@elvenkind.com> (raw)
In-Reply-To: <326847810808270705s633a3586g4d356d08e43e782f@mail.gmail.com>

Alan Stone wrote:
> 
> CanItBeAnyMoreConfusingText ?

 From left to right, you have:

   (left)edge
   (left)edgedistance
   (left)margin
   (left)margindistance
   width
   (right)margindistance
   (right)margin
   (right)edgedistance
   (right)edge

The location of all this on the paper is defined by backspace, which
gives the distance between the appropriate (left or right) edge of the
text width and the physical paper edge.

Similar logic applies in the vertical direction. \showlayout will
give the current values and keys (put it after \starttext, it generates 
four pages of typeset information).  I am somewhat confused myself as to
why this is generally considered to  be so confusing.

In vertical mode, it goes like this

    top
    topdistance
    header
    headerdistance
    textheight
    footerdistance
    footer
    bottomdistance
    bottom

"height" sets up the dimension that controls the inner five areas
(header ... footer). "topspace" is the distance between the vertical
top edge of the paper and the top of "header".

You can put \showlayout after \starttext. It will generate four pages
of settings (because of double-sided ness).

Best wishes,
Taco


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


  parent reply	other threads:[~2008-08-27 15:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 16:29 Alan Stone
2008-08-26  9:17 ` Aditya Mahajan
2008-08-27  7:23   ` Alan Stone
2008-08-27 11:22   ` Alan Stone
2008-08-27 11:27     ` Hans Hagen
2008-08-27 12:36       ` Alan Stone
2008-08-27 12:41         ` Hans Hagen
2008-08-27 13:31           ` Alan Stone
2008-08-27 13:36             ` Hans Hagen
2008-08-27 14:05               ` Alan Stone
2008-08-27 14:47                 ` Hans Hagen
2008-08-27 15:12                   ` Alan Stone
2008-08-27 15:53                     ` Patrick Gundlach
2008-08-28  8:15                       ` Alan Stone
2008-08-28  8:34                         ` Yue Wang
2008-08-28  9:54                           ` Arthur Reutenauer
2008-08-28 14:03                             ` Alan Stone
2008-08-27 15:07                 ` Taco Hoekwater [this message]
2008-08-27 15:42                   ` Alan Stone
2008-08-27 16:15                     ` Taco Hoekwater
2008-08-27 16:37                       ` Alan Stone
2008-08-27 16:47                         ` Taco Hoekwater
2008-08-27 13:09         ` Taco Hoekwater
2008-08-27 13:28           ` Alan Stone
2008-08-26 16:54 ` Peter Rolf
2008-08-26 17:07   ` Alan Stone
2008-08-26 18:43     ` Peter Rolf

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=48B56DC6.90105@elvenkind.com \
    --to=taco@elvenkind.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).