there may be good news ahead for the bidi operations:
our team at ibm is working on a c implementation of the updated bidi algorithm
as it will go into the upcoming version 3.0 of unicode. this will be part of the
IBM Classes for Unicode (icu), which is open source. the xterm team could then
use this if it wanted to.
see http://www.ibm.com/news/1999/06/181.phtml
or http://www.ibm.com/alphaWorks
best regards,
markus
Markus Scherer IBM Cupertino, CA schererm@us.ibm.com
"Mark H. David" <mhd@world.std.com> on 99-08-12 22:44:31
To: Unicode List <unicode@unicode.org>
cc:
Subject: Re: Linux i18n project coordination
Our expert on open software from the UYIP
list (http://www.uyip.org) provided this
feedback on Yiddish/Hebrew: -- Mark
From: raphael@cs.uky.edu (Raphael Finkel)
Date: Thu, 12 Aug 1999 09:40:27 -0400
To: uyip@world.std.com
Subject: Re: Multilingual Linux, etc.
With regards to Linux and unicode:
I downloaded the newest source for xterm (version 112) and compiled it with
the unicode extension. I also got some Unicode fonts from
ftp://crl.nmsu.edu/CLR/multiling/unicode/fonts/
The good news: xterm understands Unicode, and the fonts are in fact Unicode
fonts with a wealth of alphabets.
The medium news: Not all the 20 or so fonts in the package contain the Hebrew
region, and of those that do, most either are missing the vowels (we need
komets, pasekh, and khirik for Yiddish) or the special Yiddish characters
(tsvey-vov, vov-yud). However, two of the fonts appear complete in that
regard:
-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1
-misc-fixed-bold-r-semicondensed--13-120-75-75-c-60-iso10646-1
The bad news: xterm has no facilities for right-to-left, so you need to
reverse your text manually (or learn to read backwards). xterm has no support
for composing characters, so even if you get pasekh-alef, the pasekh will
follow the alef, not be composed with it.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:51 EDT