From: dbailey27@ameritech.net
To: 9fans@cse.psu.edu
Subject: [9fans] Re: Thai Chicken
Date: Mon, 23 Feb 2004 17:46:05 -0500 [thread overview]
Message-ID: <d5095a9d9dfdb3ac914b9dd8dd855c8b@yourdomain.dom> (raw)
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_)
next reply other threads:[~2004-02-23 22:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 22:46 dbailey27 [this message]
2004-02-23 21:56 ` boyd, rounin
2004-02-23 22:51 ` dbailey27
2004-02-24 4:41 ` Martin C.Atkins
2004-02-24 3:57 ` andrey mirtchovski
2004-02-24 8:05 ` [9fans] plan9 web server vdharani
2004-02-24 4:51 ` andrey mirtchovski
2004-02-24 8:32 ` vdharani
2004-02-24 7:33 ` Fco.J.Ballesteros
2004-02-24 8:17 ` boyd, rounin
2004-02-25 0:34 ` vdharani
2004-02-24 22:14 ` David Presotto
2004-02-24 9:35 ` [9fans] Re: Thai Chicken Martin C.Atkins
2004-02-24 9:43 ` Charles Forsyth
2004-02-24 8:52 ` boyd, rounin
2004-02-24 9:53 ` Geoff Collyer
2004-02-24 16:04 ` Rob Pike
2004-02-25 5:52 ` Martin C.Atkins
2004-02-25 5:13 ` andrey mirtchovski
2004-02-25 8:46 ` Chris Hollis-Locke
2004-02-26 5:51 ` boyd, rounin
2004-02-25 19:53 ` rog
2004-02-24 10:04 ` Chris Hollis-Locke
2004-02-24 10:47 ` Lucio De Re
2004-02-25 12:40 ` Dave Lukes
2004-02-25 12:54 ` Lucio De Re
2004-02-26 5:59 ` boyd, rounin
2004-02-28 5:44 ` Martin C.Atkins
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=d5095a9d9dfdb3ac914b9dd8dd855c8b@yourdomain.dom \
--to=dbailey27@ameritech.net \
--cc=9fans@cse.psu.edu \
/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).