> sorry..... Intel platform running Redhat Linux 7.0.......... also, what
functions are better for internationalization??? since wchar_t is 4
bytes should I use 16 bit unsinged int type and gettext??? Is there a
way to determine if it is installed (gettext functionality that
is)...... trying to implement Unicode on a redhat system that will
eventually be embedded and must support sveral European languages as
well as CJK....
On RedHat Linux you can choose between what the glibc offers (UCS-4 for
wchar_t, w* functions manipulate UCS-4, iconv(3) charset conversions) and
using IBM's ICU. I made a quick attempt at a RPM spec file for ICU 1.6,
which would give a good start to package the 1.8 release, out a few days ago
(I use Debian, so maintaining RPMs is hard). The advantage I see in using
ICU is that it gives you access to the whole world of Unicode, including
character properties, Unicode collation, etc., and what you'll learn using
ICU will be reusable on other platforms that it supports (many Unices,
Windows, OS/xxx). The advantage of glibc is that it's shipped w/ RedHat
already, and your code will be smaller since you won't need extra libs,
which may be important in an embedded system.
YA
This archive was generated by hypermail 2.1.2 : Fri Jul 06 2001 - 00:17:15 EDT