From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@labs.coraid.com>
Date: Mon, 27 Jun 2011 19:48:53 -0400
To: 9fans@9fans.net
Message-ID: <fa9a8bfc7dd55f10aecc75e109f9ba69@coraid.com>
In-Reply-To: <4E08DDDE.94AB.00CC.0@wlu.ca>
References: <20110625065017.GA638@polynum.com>
	<522e1e2a38aa18c291305563d362abfe@ladd.quanstro.net>
	<20110625150327.GA425@polynum.com> <iu52m9$a54$1@dough.gmane.org>
	<20110625171134.GA3661@polynum.com>
	<BANLkTikoagmZ41qpH8Zqf5xw_btH1iP7Vg@mail.gmail.com>
	<20110626075745.GA395@polynum.com>
	<BANLkTi=WQCj2vL0j=G4FW08FDy_KrYpDMQ@mail.gmail.com>
	<20110627114856.GA7099@polynum.com>
	<9308c52f360f6274e0730399741278ce@ladd.quanstro.net>
	<4E08DDDE.94AB.00CC.0@wlu.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] [RFC] fonts and unicode/utf [TeX]
Topicbox-Message-UUID: f781d554-ead6-11e9-9d60-3106f5b1d025

> I don't know who told you that...  just because there is a codepoint
> for something does not mean that one has to access that codepoint
> directly in all cases.  Software at various levels can render a
> ligature on the basis of various actual character sequences (e.g.  f +
> i, or f, i when ligatures are forced, etc.
>
> It's simply a level of what support one wishes to offer....

+1.

- erik