From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <d5095a9d9dfdb3ac914b9dd8dd855c8b@yourdomain.dom>
To: 9fans@cse.psu.edu
From: dbailey27@ameritech.net
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] Re: Thai Chicken
Date: Mon, 23 Feb 2004 17:46:05 -0500
Topicbox-Message-UUID: f2e5343c-eacc-11e9-9e20-41e7f4b1d025

Hm, I think I get this.

So, each font has to have a map file that can redirect
certain clusters of codes to certain clusters of characters
stored somewhere.

Thus, the unicode font, itself, may not have mappings
for a given set of codes, unless there is a defined map
to files that specify proper translation.

So, if I were to implement Thai support in my favorite
font (/lib/font/bit/lucida/unicode.7.font) I would need
to alter unicode.7.font to point to a file that contains
specific Thai encodings?

unicode.7.font
	map ASCII? -> internal?
	map Cyrillic -> /lib/font/bit/lucida/cyrillic.??.?
	map Thai -> external or undefined mapping

Am I on the right track here?

Don (north_)