ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Delayed page layout change?
Date: Sun, 11 Jan 2015 11:39:24 +0100	[thread overview]
Message-ID: <54B252DC.10909@wxs.nl> (raw)
In-Reply-To: <54B1B79B.7090805@bcs.co.nz>

On 1/11/2015 12:36 AM, David Brooks wrote:
> Hi,
>
> I'm new to ConTeXt (although have used LaTeX in various ways over a long
> time) and am impressed! Many thanks for a great system.
>
> I'm wanting some pages in a book to have a different layout to others,
> and am using \definelayout and \setuplayout to do so. This all works,
> including adding layers to the different layouts. However the layout
> change (specified by \setuplayout) occurs immediately after the command
> is given, which means following paragraphs on the page have the layout's
> new width and not the width used for earlier text on the page: i.e:
>
> +            +
>     xxxxxxxxx
>     xxxxxxxxx
>     xxxxxxxxx
> <-- \setuplayout
>     xxxxx
>     xxxxx
> +            +
> +            +
>     xxxxx
>     xxxxx
>     xxxxx
> xxxxx
>     xxxxx
>     xxxxx
> +            +
>
> Is there anyway to defer the change in layout so that it occurs when the
> next page starts?? I can obviously force my own page breaks using \page
> and give \setuplayout immediately afterwards, but this doesn't allow for
> paragraph text to flow over the page boundary.

\setuppagenumbering[alternative=doublesided]

\setuplayout         [width=11cm]
\definelayout [odd]  [backspace=1cm,height=18cm]
\definelayout [even] [backspace=4cm,height=19cm]
\definelayout [5]    [backspace=5cm,height=20cm]
\definelayout [6]    [backspace=5cm]
\definelayout [-2]   [backspace=0cm,cutspace=0cm]
\definelayout [last] [backspace=0cm,cutspace=0cm]

\checkcurrentlayout \showframe

\starttext
     \dorecurse{20} {\input knuth \endgraf \input tufte \endgraf}
\stoptext

so you can play with these settings

Hans

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

  reply	other threads:[~2015-01-11 10:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-10 23:36 David Brooks
2015-01-11 10:39 ` Hans Hagen [this message]
2015-01-11 18:04   ` David Brooks
2015-01-11 18:30     ` Hans Hagen
2015-01-11 18:58       ` David Brooks
2015-01-11 21:56         ` 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=54B252DC.10909@wxs.nl \
    --to=pragma@wxs.nl \
    --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).