From: Bill McClain <wmcclain@salamander.com>
Subject: Re: Small-Caps and Old-Style numbers
Date: Thu, 19 Sep 2002 07:08:52 -0500 [thread overview]
Message-ID: <20020919070852.4d46a764.wmcclain@salamander.com> (raw)
In-Reply-To: <20020919112104.GA14492@zargon-client1.chello.at>
On Thu, 19 Sep 2002 13:21:05 +0200
Peter Sojan <ilikeunix@gmx.net> wrote:
> 1. Bold-Caps, how do I access them? Is something like
> "SerifBoldCaps" allowed?
I don't think so (perhaps Hans will correct me?) I would define a new
typescript such as "MyGaramondBold" where the [SerifCaps] synonym
references the bold small caps font. You'll have to \switchtobodyfont to
use that font.
> 2. How should I integrate Old-Style numbers, so that a switch with
> \os works? Under Latex the solution from the packager was to
> reimplement all fonts with a different filename. That is
> instead of padr9e, padr9d would be used for Garamond-Roman with
> Old-Style numbers. Obviously this (virtual) font maps-in old
> style number-glyphs from the adobe extension font and keeps
> everything else as is.
This works:
\definefontsynonym [OldStyle] [xxx]
Where "xxx" is a reference to the font file with the old-style figures.
What is lacking, I think, is [OldStyleBold] and [OldStyleItalic]. So you
can't usefully combine \os with \it or \bf. (Am I wrong about that?)
> One solution would be to setup another typescript with old-style
> fonts and switch to it everytime directly by \usetypescript and
> \switchtobodyfont.
That's what I've done when I've wanted an old-style roman, italic and
bold by default. If you just need roman, you can define [OldStyle] as
above.
-Bill
--
Sattre Press Pagan Papers
http://sattre-press.com/ by Kenneth Grahame
info@sattre-press.com http://pp.sattre-press.com/
next prev parent reply other threads:[~2002-09-19 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 11:21 Peter Sojan
2002-09-19 12:08 ` Bill McClain [this message]
2002-09-19 22:16 ` Peter Sojan
2002-09-19 19:27 Bruce D'Arcus
2002-09-19 19:51 ` 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=20020919070852.4d46a764.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).