ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "John R. Culleton" <john@wexfordpress.com>
Subject: A font question.
Date: Thu, 22 Dec 2005 18:11:13 -0500	[thread overview]
Message-ID: <200512221811.13808.john@wexfordpress.com> (raw)

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.  And I am used to tweaking both the font size and the
baselineskip by fractional amounts to help in getting the
pagination just right and the spacing on the individual page
correct. For example I have the main body font on a current
project defined thus:

\font\rm=8r-AGaramond-Regular at 10.5pt
and this:
\baselineskip 12.0pt plus .25pt

If the page comes up a line short because of strict widow
prevention then the extra space is distributed imperceptibly
among the lines. \parskip is 0 pt for this novel. With a fixed
baselineskip the extra space is distributed only at paragraph breaks,
which gives an ugly result. 

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. 

However abandoning the typescript etc. process deprives one of
the useful feature of using tfa, tfb, tfx etc. to adjust font
sizes semi-automatically.

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?


John Culleton

             reply	other threads:[~2005-12-22 23:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22 23:11 John R. Culleton [this message]
2005-12-23  7:45 ` Taco Hoekwater
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=200512221811.13808.john@wexfordpress.com \
    --to=john@wexfordpress.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).