Tue, 05 Sep 2000 13:03:21 +0100, Markus Kuhn <[EMAIL PROTECTED]> pisze:
> > I am aware that wchar_t needs not to be Unicode but don't know what
> > else can I do than to provide functions usable only in cases where
> > wchar_t is Unicode.
>
> If wchar_t is Unicode, then the C compiler will have the macro
>
> __STDC_ISO_10646__ An integer constant of the form yyyymmL
On glibc-2.1.3 wchar_t is Unicode but the macro is not defined.
Moreover, if it's not Unicode then I see no good way to sensibly
convert between its encoding and Unicode anyway.
So from a position of a language that uses Unicode internally, text
interchange between it and C's wchar_t is possible only if wchar_t
is Unicode.
For the default encoding of files, it's not much better. Using iconv
would have too much limitations :-(
I wonder what Java implementations do. Java-1.0 spec that I have does
not address file encodings other than a modified UTF-8, but later
Java versions have done something with that, right?
--
__("< Marcin Kowalczyk * [EMAIL PROTECTED] http://qrczak.ids.net.pl/
\__/
^^ SYGNATURA ZASTĘPCZA
QRCZAK
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
