From: Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: can we do binding correction?
Date: Mon, 18 Mar 2024 17:35:03 +0100 [thread overview]
Message-ID: <542533e8-8505-483c-86d8-ea166c381f18@fiee.net> (raw)
In-Reply-To: <a93e8e56-b200-d58e-886f-907f3f287693@gmail.com>
Am 17.03.24 um 23:54 schrieb Wolfgang Schuster:
> Hraban Ramm schrieb am 17.03.2024 um 22:48:
>> Hi, this question was rised in my ConTeXt beginners workshop* at
>> Chemnitz Linux Days today:
>>
>> Can I configure binding correction for saddle-stitched or
>> thread-bound booklets, and if, does it only work with arranging
>> (imposition) or can I enable it somehow for the layout (if the
>> printshop does the imposition)?
>
> 1. \definepageshift + \setuppageshift
>
> 2. \setuplayout[horoffset=<DIMENSION>]
>
>> Also I recognized I'm not sure about the difference of the layout
>> parameters backspace and cutspace.
>
> backspace is the inner margin and cutspace the outer
>
Hi Wolfgang, thank you! Seems like I was too dense to understand the
description for the \setuplayout parameters in the wiki (and there are
more that I never used, oh my…), and since I never use ConTeXt’s
imposition for serious print products (and never set up a scheme
myself), I didn’t know about pageshift.
Ok, if I leave imposition to the printshop and they don't do binding
correction in their workflow, I'd need to set horoffset differently for
every single page (i.e. first, second, second-to-last and last the same;
3th, 4th and from back the same etc.). Or is pageshift applied
independently from arranging?
And then, it makes no sense to add the same value all the time. I don’t
know if BCOR works this way in LaTeX, but one value (paper thickness)
should be enough in combination with an imposition schema. I.e. if I
define a paper thickness and the number of pages that are in one booklet
(as a single booklet or part of a "proper" book), then the page shift
should work automatically.
Well, for a single booklet, it could. In a book, booklets can have
different numbers of pages, and then you'd need to define a list… Okay,
too complicated. It’s the printshops's responsibility anyway, and nobody
complained about my books so far. (I'm not perfectionist enough to care.)
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-03-18 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 21:48 [NTG-context] " Hraban Ramm
2024-03-17 22:54 ` [NTG-context] " Wolfgang Schuster
2024-03-18 16:35 ` Hraban Ramm [this message]
2024-03-19 16:01 ` Willi Egger
2024-03-19 20:56 ` Hraban Ramm
2024-03-19 22:42 ` Willi Egger
2024-03-20 6:56 ` Hraban Ramm
2024-03-20 5:07 Andres Conrado Montoya
2024-03-20 8:50 ` Hraban Ramm
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=542533e8-8505-483c-86d8-ea166c381f18@fiee.net \
--to=texml@fiee.net \
--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).