From: Willi Egger <context@boede.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Is it possible to define a custom imposition schema? (sure it is, but how?)
Date: Tue, 29 May 2012 22:21:23 +0200 [thread overview]
Message-ID: <ED50F00C-6D93-4B9E-BA5A-BC75C1FE5284@boede.nl> (raw)
In-Reply-To: <87pq9mvmll.fsf@universe.krase.net>
To my knowledge the printer will have more hand-work than accepting that e.g. the 2*4*2 or the 2*2*4 scheme is used. - Again, if I understand you correctly, then the folding machine can only do a single fold. So after assembling the section with two folded sheets still a manual fold must be made along the spine. I expect that the assembly is quite unstable if it has to be stitched/sewn.
In the first case one can pick two sheets and fold them twice, resulting in a 16 pages section. Such folded sections are stable for stitching/sewing. Even more easy is the 2*2*4 approach, with a single folding over the spine you end up with a section of 16 pages. This kind of section is reasonably stable for stitching/sewing.
Willi
On May 29, 2012, at 9:00 PM, Marco Pessotto wrote:
> Willi Egger <context@boede.nl> writes:
>
>> Hi Marco,
>>
>> If I understand correctly what you need is a system which is basically
>> based on booklet-printing but each booklet should be restricted to 16
>> pages. In this case you might try
>>
>> \setuparranging[2*2*4]
>>
>> This scheme put two pages on the front and two pages on the backside
>> of a sheet of paper. Then it uses 4 sheets to complete the section.
>>
>> Willi
>
> Hello Willi, thanks for your reply.
>
> No, the scheme is quite complicated (from 1 to 16) because the pages are
> first folded, then the two *folded* sheets are inserted one into the
> other, and then signature is bound and trimmed.
>
> So the scheme looks so (R means rotated 180°):
>
>
> 13 R | 4 R
> -----------
> 16 | 1
>
>
> 3 R | 14 R
> -----------
> 2 | 15
>
>
> 9 R | 8 R
> -----------
> 12 | 5
>
> 7R | 10R
> ----------
> 6 | 11
>
>
> Yes, that's crazy (if you ask me). As I said, I'll go with the layers
> and a perl helper, the outcome looks almost fine.
>
> Best wishes
>
> --
> Marco
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-05-29 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 17:06 Marco Pessotto
2012-05-29 17:13 ` Hans Hagen
2012-05-29 18:54 ` Marco Pessotto
2012-05-29 18:04 ` Willi Egger
2012-05-29 19:00 ` Marco Pessotto
2012-05-29 20:21 ` Willi Egger [this message]
2012-05-29 22:16 ` Marco Pessotto
2012-05-30 8:44 ` Marco Pessotto
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=ED50F00C-6D93-4B9E-BA5A-BC75C1FE5284@boede.nl \
--to=context@boede.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).