From: Emanuele Pucciarelli <ep-context@iglu.cc.uniud.it>
Subject: Alternate and Expert Type 1 fonts
Date: Tue, 14 May 2002 17:00:41 +0200 [thread overview]
Message-ID: <20020514170041.A22732@iglu.localnet> (raw)
Hello everyone,
is there any plan to support the extra ligatures and goodies provided by the
"expert" fonts in some Type 1 families? I suppose it's a bit of a pain in
the neck, as they don't belong much in any encoding vectors, and I wonder if
anyone has already thought of a solution. (I guess that the same goes for
OpenType fonts, as a TFM file can store up to 256 glyphs.)
TIA as usual,
Emanuele
reply other threads:[~2002-05-14 15:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020514170041.A22732@iglu.localnet \
--to=ep-context@iglu.cc.uniud.it \
/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).