From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: upshaped \textmu
Date: Fri, 10 Jun 2005 14:40:14 +0100 [thread overview]
Message-ID: <20050610134014.25703@mail.comp.lancs.ac.uk> (raw)
In-Reply-To: <42A92F4B.8040803@elvenkind.com>
Taco Hoekwater said this at Fri, 10 Jun 2005 08:12:27 +0200:
>> Isn't there a possibility to use
>> ec-encoding for the main-font, and for some exceptions such as \textmu
>> another encoding?
>
>I'd been wrestling with that for a while before I wrote the remark,
>but I could not make that work in ConTeXt. Perhaps somebody else
>knows.
I really like what Vit did with his Storm font support, and I think it's
probably the way to support "Companion" encodings in general.
<http://typokvitek.com/typokv-download-TeX-en.html>
Basically, he adopts a variant convention in his typescripts (main
encoding, and the companion font is typesynonym'd to main encoding +
suffix [e.g., ec-hoekwater and ec-hoekwater-companion]), and then
defines the extra characters and font \variant[]s of the main encoding.
Pretty clean, in my opinion.
I brought this up with TS1/Companion encodings before on the list, but
got the strong impression people weren't interested. :)
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
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-06-10 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 18:16 Peter Münster
2005-06-10 6:12 ` Taco Hoekwater
2005-06-10 13:40 ` Adam Lindsay [this message]
2005-06-10 14:05 ` Taco Hoekwater
2005-06-10 16:13 ` Peter Münster
2005-06-11 9:39 ` Peter Münster
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=20050610134014.25703@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).