UTF-8 runtime environment

[rockwell618 at gmail.com]

OK, thanks.  Didn't realize UTF-8 support was "pretty alpha."

Before my original posting, I tried out uClibc with UTF-8 enabled and
whenever my application encountered a multi-byte char in an input
stream during a
fgetwc or fgetws read I received the error EILSEQ - Illegal byte
sequence.  This was the same behavior I saw before I added UTF-8.  My
initial thought was that there was something missing in my runtime
environment.

As far as you know, are multi-byte chars actually supported?  Have you
seen it work?

Thanks,
Todd

On 2/20/07, Mike Frysinger <vapier at gentoo.org> wrote:
> On Tuesday 20 February 2007, rockwell618 at gmail.com wrote:
> > For instance, as with glibc, are the LANG and LC_* env vars used?
>
> the POSIX defined variables are supported ... glibc defines some LC_* vars
> that are not in POSIX
>
> > Should /usr/lib/locale be created to contain the locale data?
> > is the "Pre-generated Locale Data" supposed to reside on the target
> > device -- or is it actually built into uClibc?
>
> it's built into the libc iirc
>
> > It's all been documented I'm sure but I've overlooked it somehow.
>
> i doubt it is ... locale support is pretty alpha and remain so until someone
> steps up to work on it more
> -mike
>
>