From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Rik Kabel <context@rik.users.panix.com>,
Idris Samawi Hamid <ishamid@colostate.edu>
Subject: Re: Printing catchword or kustode
Date: Tue, 8 Oct 2019 11:10:21 +0200 [thread overview]
Message-ID: <b6ddc54e-9e46-f03f-e212-46eac3339a19@xs4all.nl> (raw)
In-Reply-To: <3cece4bd-a299-e955-0a49-6bcb8fa5c865@rik.users.panix.com>
On 10/7/2019 7:13 PM, Rik Kabel wrote:
> On 8/10/2019 10:14, Hans Hagen wrote:
>> On 8/10/2019 2:25 PM, Jan Ulrich Hasecke wrote:
>>> Hi all,
>>>
>>> Visiting a museum in Straßburg I saw an old book from Gutenbergs
>>> times where the
>>> first word of the next page was printed below the last line of the
>>> current page.
>>>
>>> The word, sometimes only a syllable of the first word from the next
>>> page, is
>>> called catchword or Kustode. They used it to ensure that they bind
>>> the pages in
>>> the right order.
>>>
>>> I think that it can also be of help if you read a book.
>>>
>>> Is this possible with ConTeXt?
>> not that hard to implement if really needed
>>
>>
>
> Here is a vote for implementing it. I find myself writing catchwords by
> hand on speeches I have to give. An automated system of generating them
> would be most welcome.
>
> I suggest that they should optionally be sensitive to the page spread.
> That is, for two-sided documents there should be an option to print them
> only on recto pages. Perhaps some tuning for length, defaulting to one
> word, as well. Placement is traditionally in the bottom inside of the
> outside margin (directly below the text block, flush right).
let's not go over the top for such a feature (no big deal to make it odd
or even page only if needed, but first use it)
> I do not know if this practice is found in RTL languages, but I do not
> see why it would not be adaptable to them as well.
i have no clue what it means but no one asked for it so we can relax
about it
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2019-10-08 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 12:25 Jan Ulrich Hasecke
2019-08-10 14:14 ` Hans Hagen
2019-10-07 17:13 ` Rik Kabel
2019-10-07 19:20 ` Henning Hraban Ramm
2019-10-08 9:07 ` Hans Hagen
2019-10-08 11:26 ` Henning Hraban Ramm
2019-10-08 9:10 ` Hans Hagen [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=b6ddc54e-9e46-f03f-e212-46eac3339a19@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=context@rik.users.panix.com \
--cc=ishamid@colostate.edu \
--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).