From: Bill McClain <wmcclain@salamander.com>
Subject: style fallbacks
Date: Mon, 28 Jan 2002 16:55:11 -0600 [thread overview]
Message-ID: <3C55D6CF.F2AC5FA5@salamander.com> (raw)
Are style fallbacks a supported part of the system, or are they local to
type-buy.tex?
This typescript doesn't work because of missing Slant styles:
\starttypescript [serif] [charter] [name]
\definefontsynonym [Serif] [Charter-Roman]
\definefontsynonym [SerifBold] [Charter-Bold]
\definefontsynonym [SerifItalic] [Charter-Italic]
\definefontsynonym [SerifBoldItalic] [Charter-Bold-Italic]
\stoptypescript
Adding \usetypescriptfile[type-buy] at the top and
\usetypescript[serif][fallback] within the typescript fixes that
problem, but the job still fails because of missing SerifCaps
definition, which isn't in the fallback typescript.
Adding this fixes it:
\starttypescript [serif] [fallback]
\definefontsynonym [SerifCaps] [Serif]
\stoptypescript
Or, I could add dummy SerifCaps to the definition. Using the fallback
mechanism is more elegant. Is there a reason SmallCaps should be treated
differently than the Slant styles?
-Bill
next reply other threads:[~2002-01-28 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 22:55 Bill McClain [this message]
2002-01-29 10:36 ` 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=3C55D6CF.F2AC5FA5@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).