From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: iso latin 2
Date: Wed, 9 Feb 2005 22:18:43 +0000 [thread overview]
Message-ID: <20050209221843.26175@mail.comp.lancs.ac.uk> (raw)
In-Reply-To: <420A81D5.702@seznam.cz>
Vit Zyka said this at Wed, 9 Feb 2005 22:34:13 +0100:
>The question is how to elegantly switch from standard (st2) tfm to
>extended (st3) tfm when the glyph is not present in st2 - with
>preserving \rm, \bf, \it, \bi.
>
>Example: {\bf Bold text with special char \textplus} where \texplus is
>bold variant from st3 encoded tfm. It is understandable?
Interesting. There are a couple possibilities, I think.
My current favourite, \variant[something], is essentially a convention
that's built on top of the font synonym mechanism. There's an example
given at:
<http://contextgarden.net/Font_Variants>
...but I haven't done a proper write-up yet.
basically, you declare a variant set for a (Serif/Sans/Mono) family:
\definefontvariant [Serif] [exp] [-Expert]
% [fam] [call abbrev] [synonym suffix]
And then you create font synonyms for each of the possible seven
SerifBlah-Expert fonts that would be called, e.g.:
\definefontsynonym [SerifRegular] [AndulkaText]
\definefontsynonym [SerifRegular-Expert] [AndulkaTextExpert]
\definefontsynonym [SerifBold] [AndulkaTextBold]
\definefontsynonym [SerifBold-Expert] [AndulkaTextBoldExpert]
Where the AndulkaText font resolves to your st2 encoding, and
AndulkaTextExpert is in your st3 encoding. (I haven't tried this trick
with different encodings, but it *should* work!)
You can then call the proper variant with {\bf Hi there \Var[exp]+}, or
create a level of indirection with your \textplus macro so that it calls
the [exp] variant and the glyph together.
The Storm fonts are beautiful. Sigh. Have fun with them...
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk
Lancaster University, InfoLab21 +44(0)1524/510.514
Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2005-02-09 22:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 17:29 Hans Hagen
2005-02-09 21:34 ` Vit Zyka
2005-02-09 22:18 ` Adam Lindsay [this message]
2005-02-09 23:33 ` Vit Zyka
2005-02-09 23:41 ` Adam Lindsay
2005-02-10 9:23 ` Hans Hagen
2005-02-11 10:56 ` Vit Zyka
2005-03-15 18:23 ` iso latin 2 ; storm fonts Vit Zyka
2005-03-15 18:29 ` Hans Hagen
2005-03-15 23:25 ` Hans Hagen
2005-03-16 23:52 ` Vit Zyka
2005-03-15 23:45 ` Adam Lindsay
2005-04-10 20:31 ` Vit Zyka
2005-04-11 11:16 ` Adam Lindsay
2005-02-09 22:21 ` iso latin 2 Hans Hagen
2005-02-09 23:52 ` Vit Zyka
2005-02-10 9:26 ` Hans Hagen
2005-02-11 10:17 ` Vit Zyka
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=20050209221843.26175@mail.comp.lancs.ac.uk \
--to=atl@comp.lancs.ac.uk \
--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).