From: Hans Hagen <pragma@wxs.nl>
Cc: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Re: style fallbacks
Date: Tue, 29 Jan 2002 11:36:48 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20020129113416.041ea958@server-1> (raw)
In-Reply-To: <3C55D6CF.F2AC5FA5@salamander.com>
At 04:55 PM 1/28/2002 -0600, Bill McClain wrote:
>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?
not al all, i sim0ply didn't add them (yet), so now i added the three extra
fallbacks.
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
fall-back web server:
www.pragma-pod.nl
-------------------------------------------------------------------------
prev parent reply other threads:[~2002-01-29 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 22:55 Bill McClain
2002-01-29 10:36 ` Hans Hagen [this message]
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=5.1.0.14.1.20020129113416.041ea958@server-1 \
--to=pragma@wxs.nl \
--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).