From: Bill McClain <wmcclain@salamander.com>
Subject: Re: interaction between \tfx and \os (2nd try)
Date: Wed, 21 Aug 2002 10:35:36 -0500 [thread overview]
Message-ID: <20020821103536.7928785c.wmcclain@salamander.com> (raw)
In-Reply-To: <5.1.0.14.1.20020821162032.0354e628@server-1>
On Wed, 21 Aug 2002 16:21:38 +0200
Hans Hagen <pragma@wxs.nl> wrote:
> i'll look into it, can you try:
>
> \definefont[os][OldStyle]
That makes a difference. The CM and Sabon \tfx \os text is more
reasonably sized and the Jenson example appears to be the same size with
and without \os, which is correct.
There is a side effect: the Jenson \tfa \os combination reduces the text
just slightly (compared to just \tfa), which shouldn't happen.
I don't use \definefont anywhere in my typescripts or jobs. Should I?
-Bill
--
Sattre Press Tales of War
http://sattre-press.com/ by Lord Dunsany
info@sattre-press.com http://tow.sattre-press.com/
next prev parent reply other threads:[~2002-08-21 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 10:37 Bill McClain
2002-08-21 14:21 ` Hans Hagen
2002-08-21 15:35 ` Bill McClain [this message]
2002-08-21 15:47 ` Hans Hagen
2002-08-21 16:47 ` Bruce D'Arcus
2002-08-21 15:43 ` Hans Hagen
2002-08-21 18:34 ` Bill McClain
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=20020821103536.7928785c.wmcclain@salamander.com \
--to=wmcclain@salamander.com \
/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).