From: Bill McClain <wmcclain@salamander.com>
Cc: ntg-context@ntg.nl
Subject: Re: Small-Caps and Old-Style numbers
Date: Thu, 19 Sep 2002 14:51:06 -0500 [thread overview]
Message-ID: <20020919145106.3ec3a861.wmcclain@salamander.com> (raw)
In-Reply-To: <24826594.1032463648056.JavaMail.darcusb@muohio.edu>
On Thu, 19 Sep 2002 15:27:28 -0400 (EDT)
"Bruce D'Arcus" <darcusb@muohio.edu> wrote:
> Hmm...so no smallcap italics? And if I have a font that also has
> light sc and medium sc, I need three separate typescripts just to
> access those fonts?
I think that is the case (although I've been wrong before). I'm not sure
how more than two weights (\bf and \rm) could be handled anyway. Is
there anything in the tex world equivalent to \light, \medium and
\heavy?
Multiple typescripts can be created in the same file and can share the
same set of font synonyms, so managing them is not that difficult. A
typescript is just a "view" of your font files. You can make up your own
\light etc macros to do the switching, but I don't see any convenient
way of having {\em \sc \light \os This is goofy 99} work out
automatically. You'd have to explicitly switch to
MyItalticSmallcapsLightOldStyle font.
I think Hans once said that all of this is typographically offensive. In
defense I would say that when composing titles, book covers, and display
art all sorts of things are useful which would not be used in body text.
-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 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 19:27 Bruce D'Arcus
2002-09-19 19:51 ` Bill McClain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-19 11:21 Peter Sojan
2002-09-19 12:08 ` Bill McClain
2002-09-19 22:16 ` Peter Sojan
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=20020919145106.3ec3a861.wmcclain@salamander.com \
--to=wmcclain@salamander.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).