ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: 2DOWN imposition gives blank pages
Date: Thu, 24 Aug 2006 12:10:07 +0100	[thread overview]
Message-ID: <E1GGD67-0007Ly-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Thu, 24 Aug 2006 08:54:45 +0200." <44ED4D35.8050307@elvenkind.com>

Taco wrote:
> Don't you need:
> 
>    \setuppapersize[A5,landscape][A4,landscape]
>    \setuparranging[2DOWN,rotated]
> 

The following produces a first page with p.1 on the right half, but a
blank 2nd page:

\setuppapersize[A5,landscape][A4,landscape]
\setuparranging[2DOWN,rotated]
\starttext
\input tufte
\stoptext

That looks okay, except for the blank 2nd page.

But shouldn't it also work to impose two A5's on one landscape A4?
Here's a few more puzzles related to that.  If they are doing what
they are supposed to, let me know -- then I need to understand the
imposition system more.

\setuppapersize[A5][A4,landscape]
\setuparranging[2UP]
\starttext
\input tufte
\page
\input tufte
\stoptext

produces a two-page document:

p.1: |   | 1 |  (i.e. blank left half, and original p.1 on the right half)
p.2: | 2 |   |  (i.e. original p.2 on left half, blank right half)

Shouldn't it produce

p.1: | 1 | 2 |

Here's my reasoning.  Two A5's (with their long directions vertical)
fit side by side to make one A4 in landscape orientation with text
running down along the short direction, which looks like 2-column text
done the hard way.  So, for a two-page original document, 2UP
arranging should produce either

p.1: | 1 | 2 |

or

p.1: | 2 | 1 |


So in case I've confused the directions of 2UP and 2DOWN, I also tried:

\setuppapersize[A5][A4,landscape]
\setuparranging[2DOWN]
\starttext
\input tufte
\page
\input tufte
\stoptext

It produces:

p.1: |   |   |
p.2: | 2 |   |

The original p.1 disappeared, which I don't understand.  Also I don't
understand why it results in two output pages.

But this hack:

\setuppapersize[A5][A4,landscape]
\setuparranging[2UP]
\starttext
\null\page
\input tufte
\page
\input tufte
\stoptext

produces the following arrangement, which is close to what I expect:

p.1: |   | 1 |  (where the original p.1 is blank except for the page num)
p.2: | 2 | 3 |

Once I understand what's going on, I'll wikify!

-Sanjoy

  reply	other threads:[~2006-08-24 11:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24  4:00 Sanjoy Mahajan
2006-08-24  6:54 ` Taco Hoekwater
2006-08-24 11:10   ` Sanjoy Mahajan [this message]
2006-08-24 17:48     ` Taco Hoekwater
2006-08-26 19:10     ` Willi Egger
2006-08-27 13:40       ` Sanjoy Mahajan
2006-08-27 15:16         ` Willi Egger
2006-08-29  0:38           ` Sanjoy Mahajan
2006-08-29 16:25             ` Willi Egger
2006-08-29 20:00               ` Sanjoy Mahajan
2006-09-08  1:13                 ` Mojca Miklavec
2006-09-06  4:00       ` Sanjoy Mahajan
2006-09-06 17:06         ` Willi Egger
2006-09-06 17:57         ` Aditya Mahajan
     [not found] <mailman.485.1156434474.2039.ntg-context@ntg.nl>
2006-08-25 21:22 ` wwl

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=E1GGD67-0007Ly-00@skye.ra.phy.cam.ac.uk \
    --to=sanjoy@mrao.cam.ac.uk \
    --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).