From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Character and word spacing
Date: Sun, 01 Jun 2014 01:17:40 +0200 [thread overview]
Message-ID: <538A6314.3040206@wxs.nl> (raw)
In-Reply-To: <5389E3CF.4060403@rik.users.panix.com>
On 5/31/2014 4:14 PM, Rik Kabel wrote:
> My issue with Dowding (and with Gill) is that they suggest that the compositor
> has an obligation to change the author's text, without consultation and
> agreement, in order to meet his concept of better page makeup. Dowding's
> sensitivity to the appearance of the page, on the other hand, is sadly missing
> from much of book publishing today.
Long ago I have been thinking of improving some \oneof {bad}
{suboptimal} paragraphs by applying 'alternative' words, i.e. one could
\optional {for instance} write like this.
> Gross manipulation of the space factors is probably too crude to accomplish much
> in implementing the style Dowding promotes, although the tightness in the second
> tufte from your example (modifying the punctuation) may be a starting point.
>
> With XeTeX, one can use \interchartoks to handle general (non-font-specific)
> kerning between punctuation and certain letter shapes (sloped left or right,
> ascender, descender, ...) beyond what any particular font's kerning tables
> provide. I see nothing in MKIV that provides this, and thought that perhaps
> \definecharacterspacing might fill the role. Hence the original question in this
> thread.
you can play with (subtle) expansion (hz) and specific stretch vectors
.. imo kerning other than what the font designer has in mind is normally
a bad idea; another option is to use a font with different glyphs for
the same character but I don't know of such fonts
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2014-05-31 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 18:15 Rik Kabel
2014-05-29 23:29 ` Hans Hagen
2014-05-31 14:14 ` Rik Kabel
2014-05-31 23:17 ` 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=538A6314.3040206@wxs.nl \
--to=pragma@wxs.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).