UTF-8 runtime environment
Brian Clarke
brian.clarke at oxsemi.com
Fri Feb 23 11:19:58 UTC 2007
Hi Todd,
I've been using a non-locale Buildroot/uClibc ARM based system for many
months now without problems.
I too am now trying to build uClibc locale support into a Buildroot
built root filesystem with the aim of being able to process UTF-8
encoded multibyte strings.
I selected Locale support from the Buildroot menus, which appears to
select to download the pre-generated local data using Buildroot's
toolchain/uClibc/uClibc.config-locale config file for uClibc.
I do not seem to get any functioning locale support, as for example the
date command from Busybox returns a corrupt string (ÓÈÊ sön 1
00:54:37 UTC 2006) and if I compile and run the tst_nl_langinfo.c locale
test program from uClibc's extra/locale directory, I get "couldn't set
locale" for any locale I try, including not specifying a locale which
should I believe select the default locale.
Do you see any evidence on your ARM system that there is any functioning
locale support present?
Brian.
rockwell618 at gmail.com wrote:
>Hi,
>
>I am trying to enable support for the en_US.UTF-8 locale in an ARM/
>linux 2.6.18 environment, using uClibc-0.9.28.
>
>Using Buildroot, I compiled uClibc after selecting the String and
>Stdio Support->Wide Character Support options: "Locale Support, " "Use
>Pre-generated Locale Data, "
>and "Automatically Download the "Pre-generated Locale Data (if necessary)."
>
>My problem is that I do not have a sense for how the runtime
>environment should be configured on the target device so that the
>locale support can actually be used by my application. For instance,
>as with glibc, are the LANG and LC_* env vars used? Should
>/usr/lib/locale be created to contain the locale data? If not, where
>is the "Pre-generated Locale Data" supposed to reside on the target
>device -- or is it actually built into uClibc? It's all been
>documented I'm sure but I've overlooked it somehow.
>
>I would greatly appreciate any pointers to documentation (or other
>guidance) on the proper runtime environment for uClibc UTF-8 support.
>
>Thanks,
>Todd
>_______________________________________________
>uClibc mailing list
>uClibc at uclibc.org
>http://busybox.net/cgi-bin/mailman/listinfo/uclibc
>
>
More information about the uClibc
mailing list