On Mon, 25 Feb 2002 14:56:09 -0500 Jimmy Kaplowitz <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 25, 2002 at 02:38:13PM -0500, Michael B Allen wrote: > > What's the ultimate goal here? Are any of these functions *supposed* > > to work on multi-byte characters, or will there be mbs* functions? > > I haven't tested this, nor really done anything relating to programming > with i18n, but based on looking at man pages, you can use one of three > functions (mbstowcs, mbsrtowcs, or mbsnrtowcs) to convert your multibyte > string to a wide character string (an array of type wchar_t, one wchar_t > per *character*), and then use the many wcs* functions to do various > tests. My recollection of the consensus on this list is that for > internal purposes, wchar_t is the way to go, and conversion to multibyte > strings of char is necessary only for I/O, and there only when you can't > use functions like fwprintf. I'm writing a library that does a sort of "I/O" and cannot assume that the user will be using wchar_t. I will be providing wchar_t support as a compile time option as well. > However, wchar_t is only guaranteed to be > Unicode (which encoding?) when the macro __STDC_ISO_10646__ is defined, It just means that wchar_t values are UCS codes so it doesn't really have any particular "encoding". Thanks, Mike -- May The Source be with you. -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
