>I'm curious about the state of multi-byte locale support for BSD.
>In particular, it would be nice if you could answer some of the
>following questions:
> - Does/will the BSD C library support UTF-8 locales, such that
> the standard C functions mbsrtowcs and wcsrtombs convert between
> UTF-8 and UCS-4?
> - Does/will BSD define a policy that for all locales the values
> in wchar_t shall always be encoded according to ISO 10646 only, which
> the ISO C 99 standard says should be signaled to software by defining
> the C macro __STDC_ISO_10646__ ?
> <http://www.cl.cam.ac.uk/~mgk25/volatile/ISO-C-FDIS.1999-04.txt>
> - Does/will BSD support the C library function nl_langinfo(CODESET)
> and the command line call "locale charmap" to determine the name
> of the current locale encoding?
> <http://www.opengroup.org/onlinepubs/7908799/xsh/langinfo.h.html>
> - Does/will BSD support the C library function iconv good enough such
> that is passes the test suite in libiconv?
> <http://www.opengroup.org/onlinepubs/7908799/xsh/iconv.html>
> <http://clisp.cons.org/~haible/packages-libiconv.html>
>The answer is yes for all three for Linux since glibc 2.2, but I wonder
>what the status/plan is for *BSD here.
from what i understand for Citrus codebase:
- yes, if and only if you have specified one of locales that use
UCS-4/UTF-8 to setlocale().
- no (and will not). reasons - see my Freenix2001 paper.
- i'm not really sure, but i guess Citrus will.
- working on it.
correct me if i'm wrong > Citrus guys
beware that there is no single BSD - there are at least four or five
of them and status/plans vary.
NetBSD, OpenBSD, FreeBSD, BSD/OS, and MacOS X :-)
itojun
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
