From: John Culleton <john@wexfordpress.com>
Subject: Re: texfont and font mechanism
Date: Sun, 17 Aug 2003 11:25:20 -0400 [thread overview]
Message-ID: <200308171125.20210.john@wexfordpress.com> (raw)
In-Reply-To: <5955E2DC-D0B5-11D7-A168-0030659899AA@fiee.net>
On Sunday 17 August 2003 09:18, Henning Hraban Ramm wrote:
> Digging deep... ;-)
>
> While playing with some freeware fonts by apostrophic labs,
> shy fonts et al., I recognized some limitations of ConTeXt's
> (or TeX's?) font mechanism. I know this was discussed earlier,
> but I can't remember/find and answer.
The primitive \font statement would in fact enable one to use a hundred
different variants if needed. But then they would have to be called
individually in each instance of use. Context as a family of synonyms
which allows for a finite number of different combinations. These could be
used as the font names where applicable, which preserves the usual Context
mechanisms for switching fonts for the usual cases. For the unusual case
one would use the regular TeX font mechanism:
font\foo foobar at 10pt
\foo
Text...
...and so on.
I have felt for some time that the Context font mechanism required too much
work for too little result. So I use it where feasable but don't feel guilty
about dipping back into the \font mechanism where necessary, such as for a
title page font.
But I am only a (perpetual) novice...
John Culleton
next prev parent reply other threads:[~2003-08-17 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 13:18 Henning Hraban Ramm
2003-08-17 15:25 ` John Culleton [this message]
2003-08-18 8:22 ` Hans Hagen
2003-08-18 20:44 ` Henning Hraban Ramm
2003-08-17 21:58 ` Adam Lindsay
2003-08-18 20:53 ` Henning Hraban Ramm
2003-08-18 23:29 ` Adam Lindsay
2003-08-19 14:45 ` Jens-Uwe Morawski
2003-08-19 14:47 ` Adam Lindsay
2003-08-19 17:34 ` Jens-Uwe Morawski
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=200308171125.20210.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).