From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: A font question.
Date: Fri, 23 Dec 2005 08:45:00 +0100 [thread overview]
Message-ID: <43ABAAFC.9000902@elvenkind.com> (raw)
In-Reply-To: <200512221811.13808.john@wexfordpress.com>
Hi John,
John R. Culleton wrote:
> I use Context for highly formatted non-fiction, but I am a bit
> reluctant to use it for much of my work because of the strange
> (to me) font handling arrangements. I see no purpose for the
> multiple synonyms of the same font. That just adds layers of
> extra work.
It also adds layers of configurability. Clearly you do not
need that (your font setups is extremely simple and low-level),
but lots of other people do. For example, I have documents that
use 6 totally different font sets, because all 'examples' and
'definitions' are typeset in font families that differ from
the normal text font family. It would be a nightmare if I had to
define and remember the 200+ font definitions by hand.
> If the page comes up a line short because of strict widow
> prevention then the extra space is distributed imperceptibly
> among the lines.
It is only imperceptible if the paper you print on does not
shine through at all, and if you use a noteblock (head) binding
instead of book (back) binding, so it is not something I would
recommend for general use.
> This kind of fine tuning by users is perhaps foreign to Context as it now
> exists. Font sizes are in fixed steps for one thing.
The fixed steps (of .1pt) are actually an optimization, and it
is possible to circumvent that, using either
\chardef\fontdigits=2
or
\def\normalizebodyfontsize#1\to#2{\setvalue{#2}{#1}}
> So here is my question. If I set up my own font definition
> system and as part of it I have statements like:
> \font\tfa bchr8r at 10.45pt
> \font\tfb bchr8r at 11.37pt
> ...
> ... will the rest of Context accept the above tfb font and size in places
> where a heading macro automatically defaults to tfb?
Only if you never make any \{setup,switchto}bodyfont switches after
your new font definitions.
Cheers,
Taco
next prev parent reply other threads:[~2005-12-23 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 23:11 John R. Culleton
2005-12-23 7:45 ` Taco Hoekwater [this message]
2005-12-23 9:19 ` Hans Hagen
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=43ABAAFC.9000902@elvenkind.com \
--to=taco@elvenkind.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).