From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: 3SIDE imposition schema weirdness
Date: Wed, 10 Jun 2009 23:23:12 +0200 [thread overview]
Message-ID: <97C87AEE-B079-4D9F-A7B4-FDB49CA40013@gmail.com> (raw)
In-Reply-To: <51b0095d0906100247s1709c8a3k8a50dbedd90e3731@mail.gmail.com>
Am 10.06.2009 um 11:47 schrieb Nicolas Girard:
> * If so, I don't understand how can \dosetuparrangement{3}{1}{6}{4}{2}
> give 1|2|3 // 4|5|6 . What's the rationale ? Why no page 5 among the
> arguments of \dosetuparrangement ?
The placement of the pages is defined \pusharrangedpageTHREESIDE, the
values
above mean:
• number of columns: 3
• number of rows: 1
• total number of pages: 6 (ConTeXt collects 6 pages and arrange them
before
they are written to the pdf file but in Willi's code 3 had been
enough)
• number of crop marks in x direction: 4 (columns + 1)
• number of crop mark in y direction: 2 (rows + 1)
> * What if one wants to fold the resulting brochure ? How to adapt the
> code (besides by try and error) for the resulting arrangement to be
> 3|6|1 // 2|4|5 ?
The page order in a brochure is 5|6|1 and 2|3|4.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2009-06-10 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 9:47 Nicolas Girard
2009-06-10 10:08 ` Henning Hraban Ramm
2009-06-10 11:21 ` Wolfgang Schuster
2009-06-10 12:53 ` Nicolas Girard
2009-06-10 21:24 ` Wolfgang Schuster
2009-06-10 21:23 ` Wolfgang Schuster [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=97C87AEE-B079-4D9F-A7B4-FDB49CA40013@gmail.com \
--to=schuster.wolfgang@googlemail.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).