From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Thai Chicken
Date: Mon, 23 Feb 2004 15:32:58 -0700 [thread overview]
Message-ID: <dc2f8956f5c9bbd82dd5795d3d3372bc@plan9.ucalgary.ca> (raw)
In-Reply-To: <49feece7c70c205ed8b1ccf674932f0c@yourdomain.dom>
> Hey all,
> According to the UTF documentation I should
> be able to type Thai characters using the plan9 compose
> sequence: ALT+X+4digit. However, when I type any of
> the Thai characters listed in /lib/unicode (with a Unicode
> font), they produce nothing.
>
> Also, the full Thai alphabet is not implemented in
> the list /lib/unicode presents. Am I missing something?
> I'm just beginning to learn about UTF/Unicode/Runes, so
> please forgive me if I am a bit behind.
>
> Don (north_)
Most likely the font you're using doesn't have glyphs for thai
characters.
Thai is in the range 0x0E00-0x0E70. if you use the unicode command on
plan9 you can see whether your current font supports them. for
example the font i normally use for terminal (10646 by markus kuhn)
has some of them:
http://pages.cpsc.ucalgary.ca/~mirtchov/screenshots/thai.gif
So does arialuni (Arial Unicode MS):
http://pages.cpsc.ucalgary.ca/~mirtchov/screenshots/thai2.gif
While both the default Acme fonts don't have any glyphs for Thai characters.
For the glyphs as they're defined by unicode.org look here:
http://www.unicode.org/charts/PDF/U0E00.pdf
To type the 0e01-th unicode character i type:
alt+X+0e01
andrey
ps: 10646 and other rather complete fonts can be obtained from:
http://pages.cpsc.ucalgary.ca/~mirtchov/p9/
prev parent reply other threads:[~2004-02-23 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 22:02 dbailey27
2004-02-23 22:32 ` andrey mirtchovski [this message]
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=dc2f8956f5c9bbd82dd5795d3d3372bc@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).