[poky] Enabling UTF-8
Keskinarkaus, Teemu
teemu.keskinarkaus at crosscontrol.com
Tue Dec 13 02:02:37 PST 2016
I found the problem. I was using external toolchain and for some reason those recipes dropped the en-us. I switched to use yocto toolchain so now I have en-us too. I also added LOCALE_UTF8_ONLY="1" to local.conf.
Still I don't have any UTF-8 named locales in /usr/share/locale. I'm not sure if there even should be?
I'm testing utf-8 functionality by using Scandinavic characters (äö) in either shell or trying to edit file with nano/vi and adding those characters. I can add those characters in editor but if I move cursor the text get messed up so I assume UTF-8 isn't working. Those tests work just fine with x86 Linux (for example Ubuntu) that has UTF-8 locales.
Teemu Keskinarkaus
Software system engineer
CrossControl
making machines smart, safe and productive
-----Original Message-----
From: Khem Raj [mailto:raj.khem at gmail.com]
Sent: 12. joulukuuta 2016 9:49
To: Keskinarkaus, Teemu
Cc: poky at yoctoproject.org
Subject: Re: [poky] Enabling UTF-8
> On Dec 11, 2016, at 11:01 PM, Keskinarkaus, Teemu <teemu.keskinarkaus at crosscontrol.com> wrote:
>
> Hi,
>
> I did that and this was result: GLIBC_GENERATE_LOCALES="en_GB.UTF-8 en_GB en_US"
>
> So for some reason en_US.UTF-8 was dropped. Also only en-gb made to actual image.
Figure out why it was dropped, I think you might have additional places where this variable it being modified. Save the output of bitbake -e and inspect it manually for the value of GLIBC_GENERATE_LOCALES
> I'm not sure if you can put more than one language in IMAGE_LINGUAS.
you can put multiple values in IMAGE_LINGUAS
>
> I read/heard somewhere that nowadays UTF-8 locales don't have UTF-8 in their filenames anymore but en_GB has also UTF-8. Seems that it defaults to POSIX - locale, but when I do `locale en-gb` I get en-gb locale except I also get these errors:
>
> locale: Cannot set LC_CTYPE to default locale: No such file or
> directory
> locale: Cannot set LC_MESSAGES to default locale: No such file or
> directory
> locale: Cannot set LC_ALL to default locale: No such file or directory
> locale: unknown name "en-gb"
>
> But if I connect to device with Putty configured to UTF-8 I can't use UTF-8 properly (I use Scandic characters (äö) to test with) even after manually setting locale to en-gb (there is no utf-8 names locale). They work just fine if I test in PC with Ubuntu.
>
> Teemu Keskinarkaus
> Software system engineer
> CrossControl
> making machines smart, safe and productive
>
> -----Original Message-----
> From: Khem Raj [mailto:raj.khem at gmail.com]
> Sent: 12. joulukuuta 2016 8:29
> To: Keskinarkaus, Teemu
> Cc: poky at yoctoproject.org
> Subject: Re: [poky] Enabling UTF-8
>
> On Thu, Dec 8, 2016 at 12:02 AM, Keskinarkaus, Teemu <teemu.keskinarkaus at crosscontrol.com> wrote:
>> Hi,
>>
>>
>>
>> I’m trying to get UTF-8 support enabled to my image. For whatever
>> reason I don’t seem to get it working. I have following lines in my local.conf.
>>
>>
>>
>> GLIBC_GENERATE_LOCALES = "en_GB en_US en_GB.UTF-8 en_US.UTF-8"
>>
>> IMAGE_LINGUAS = "en-gb en-us"
>
> check if this is really reflected in final metadata. you can check
> with
>
> bitbake -e <your-image> | grep -e "^GLIBC_GENERATE_LOCALES="
>
>>
>>
>>
>> I get only en and en_GB locales to image (/usr/share/locale).
>>
>>
>>
>> I’m using Yocto 1.6.1, but I’ve tested it on Yocto 2.1 too without
>> any difference. I’m using valleyisland-32 – machine if that has
>> anything to do with it.
>>
>>
>>
>> Is there something else needed to be done to force UTF-8 locales
>> being generated? Seems that those lines don’t change anything. Same
>> locales are generated with or without those lines in local.conf.
>>
>>
>>
>> Teemu Keskinarkaus
>> Software system engineer
>> Cell: +358 400 330047
>> Fax: +358 207 669199
>> www.crosscontrol.com
>>
>> CrossControl
>>
>> making machines smart, safe and productive
>>
>>
>>
>>
>> ________________________________
>>
>> Actuant Corporation Email Notice
>>
>> This message is intended only for the use of the Addressee and may
>> contain information that is PRIVILEGED and/or CONFIDENTIAL.
>> This email is intended only for the personal and confidential use of
>> the
>> recipient(s) named above. If the reader of this email is not an
>> intended recipient, you have received this email in error and any
>> review, dissemination, distribution or copying is strictly prohibited.
>> If you have received this email in error, please notify the sender
>> immediately by return mail and permanently delete the copy you received.
>>
>> Thank you.
>>
>> --
>> _______________________________________________
>> poky mailing list
>> poky at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>>
>
> ________________________________
>
> Actuant Corporation Email Notice
>
> This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
> This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
> If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.
>
> Thank you.
________________________________
Actuant Corporation Email Notice
This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.
Thank you.
More information about the poky
mailing list