From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Thu, 30 Jun 2011 19:12:10 +0200
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-ID: <20110630171210.GA1684@polynum.com>
References: <9308c52f360f6274e0730399741278ce@ladd.quanstro.net>
	<20110627172006.GA497@polynum.com> <4E08DDDE.94AB.00CC.0@wlu.ca>
	<20110628111915.GA498@polynum.com> <4E0B804C.94AB.00CC.0@wlu.ca>
	<20110630130254.GA7276@polynum.com> <4E0C5549.94AB.00CC.0@wlu.ca>
	<20110630162524.GA442@polynum.com>
	<59e4d419ba69189bc467a330651c7044@ladd.quanstro.net>
	<20110630170048.GA999@polynum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110630170048.GA999@polynum.com>
User-Agent: Mutt/1.4.2.3i
Subject: Re: [9fans] [RFC] fonts and unicode/utf [TeX]
Topicbox-Message-UUID: f8b25692-ead6-11e9-9d60-3106f5b1d025

On Thu, Jun 30, 2011 at 07:00:48PM +0200, tlaronde wrote:
>
> This does not preclude the user from directly entering the unicode
> codepoint: in the TFM, if you want, the glyph information is duplicated,
> in the conventional plain TeX position, and as a literal in the unicode
> position.

More precisely (I hope), since the "latin minuscule ae" is duplicated
too in the conventional TeX positions (overwriting only ASCII range
control positions that are useless), the plain TeX conventions work,
while user can also enter directly the unicode for this.
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C