Bugzilla – Bug 15142
Add UTF-8 locales for TinySC
Last modified: 2010-04-08 17:25:00 UTC
We need UTF-8 locales or the scanner doesn't read filenames properly.
Richard, I cannot find where locale installation is excluded for SqueezeOS. In poky/meta-squeezeos/packages/meta/external-csl-toolchain/SUPPORTED is a list of 4 locales (we probably only need 1) but none seem to get installed.
FWIW: adding --charset=utf8 to the startup arguments seems to fix this issue. I did this and was able to browse and play "Ali Farka Tour�/Niafunk�" perfectly fine. Or we hard-code this in S::U::OS::SqueezeOS::localeDetails.
Here's what I've been using on SlimNAS (which doesn't come with all the locale data neither, for the same reasons): sub localeDetails { my $class = shift; my @locale = $class->SUPER::localeDetails(); shift @locale; return ('utf8', @locale); }
I think we're OK as far as reading filenames, but we still need the locales installed in order to do correct sorting. That may be less of an issue right now though.
Update hours
== Auto-comment from SVN commit #8298 to the jive repo by ayoung == == https://svn.slimdevices.com/jive?view=revision&revision=8298 == Fixed bug 15142: Add UTF-8 locales for TinySC Modify external-csl-toolchain_2009q1-203.bb recipe to generate binary locales packages using the names locale-binary-*. This is probably wrong and I suspect that names such as glibc-binary-localedata-* should really be used and then referenced with a dependency from a locale-base-* package. The binary locales were already available in the external-csl-toolchain_2009q1-203 tree but were not being generated into packages due to the relevant pieces from glibc-package.bbclass being missing. Include an install dependence for local-binary-en-us.utf8 in fab4.conf. I guess that this should really be part of the squeezecenter recipe but I cannot make that work with either INSTALL_IMAGES or RDEPENDS. Set the LANG environment variable in the TinySC startup script to use en_US.utf8.
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release. If you are still seeing this issue, please let us know!