ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: John Culleton <john@wexfordpress.com>
Subject: Re: Comment on new "Page Design" Chapter for new manual.
Date: Fri, 28 Jan 2011 16:24:04 +0100	[thread overview]
Message-ID: <4D42DF94.8080102@wxs.nl> (raw)
In-Reply-To: <201101271741.36502.john@wexfordpress.com>

On 27-1-2011 11:41, John Culleton wrote:
> The question of page dimensions can be very confusing for the raw
> beginner. I suggest the something like the following as a lead in:
> -----------------------------------------------------------
> For a printed page we really have to deal with three different sets of
> dimensions. The body of the text exclusive of headers, footers etc. is
> called the type block. In TeX the measurements of the type block are
> called \hsize and \vsize. When text is being laid out each paragraph
> is generally no wider than the \hsize and when \vsize is exceeded the
> page is ended and a new one is started.

hsize and vsize are more general and depend on where one accesses them, 
setting them will seldom work out well as they get set (and 
synchronized) depending on \setuplayout asignments

> The actual page size of the finished document is measured with
> \pdfpagewidth and \pdfpageheight. For most documents this is the last
> set of dimensions needed. In a few cases "camera ready copy" is
> required which means that the final printed page image is centered on a
> larger piece of paper stock, often with trim marks indicating the
> boundaries of the page size.

pdfpagewidth and pdfpageheight are not to be used directly in context, 
\setuppapersize is to be used; setting the dimensions directly will have 
side effects

> For example here are the dimensions for a book recently printed:
> hsize =4.25 in
> vsize =7 in
>
> pdfpagewidth = 6 in
> pdfpageheight = 9 in
>
> stockwidth = 8.5 in
> stockheight = 11 in.




-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      parent reply	other threads:[~2011-01-28 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 22:41 John Culleton
2011-01-28  9:49 ` Taco Hoekwater
2011-01-28 15:24 ` Hans Hagen [this message]

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=4D42DF94.8080102@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=john@wexfordpress.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).