From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/7861
Path: main.gmane.org!not-for-mail
From: Emanuele Pucciarelli <ep-context@iglu.cc.uniud.it>
Newsgroups: gmane.comp.tex.context
Subject: Alternate and Expert Type 1 fonts
Date: Tue, 14 May 2002 17:00:41 +0200
Sender: owner-ntg-context@let.uu.nl
Message-ID: <20020514170041.A22732@iglu.localnet>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: main.gmane.org 1035398303 22971 80.91.224.250 (23 Oct 2002 18:38:23 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 18:38:23 +0000 (UTC)
Original-To: ntg-context@ntg.nl
Xref: main.gmane.org gmane.comp.tex.context:7861
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:7861

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