[Localization] Language packs - testing needed

Chris Leonard cjlhomeaddress at gmail.com
Sun Oct 9 10:26:43 EDT 2011


Samy,

Thank you for the detailed feedback, your investigation of mg_MG will
hopefully allow us to improve the overall utility of the lang-packs
generated.

We will be posting the code that generated the langpacks in the SL git, to
make it easier to understand how the lang packs are built and hopefully
identify ways to improve that.

I truly appreciate you taking the time on this and it will help the entire
L10n community as we begin to sort it out and fix up this sadly neglected
(but very important) element of the localization testing infrastructure.

See below for additional threads to follow.

On Sun, Oct 9, 2011 at 6:06 AM, samy boutayeb <s.boutayeb at free.fr> wrote:

> Hi, Here is an update from my former exploration of the Language packs
> (fr & mg on a XO 1.75 with Sugar 0.94).
>
> 1. Download of fr_lang_pack_v2.sh and mg_lang_pack_v2.sh
> Success
>
> 2. Execute of
> bash-4.1# sh fr_lang_pack_v2.sh
> and
> bash-4.1# sh mg_lang_pack_v2.sh
> Success
>
> 3. Restarting
>
> 4. $ sugar-control-panel -h
> Success
>
> 5. $ sugar-control-panel -g languages
> French/France
>
> 6. $ sugar-control-panel -h languages
> None
>
> 7. $ sugar-control-panel -s languages French/France
> To apply your changes you have to restart sugar.
>
> 8. $ sugar-control-panel -s languages mg
> Sorry I do not speak 'mg'
>
>

There are a number of places to investigate the cause of this error message:

One is the ALL_LINGUAS line of the local Sugar (0.94) install.

It may have been modified from what is in git during the build process on an
OLPC build.

http://git.sugarlabs.org/sugar/mainline/blobs/sucrose-0.94/configure.ac#line21

Please recall that recent OLPC builds (since 11.2.0, if not earlier) have
limited the set of "supported" languages to those relevant to major
deployments.

http://lists.laptop.org/pipermail/devel/2011-February/031016.html

(with the addition of lang-de to that list)

This was a necessary compromise due to the size restraints of including all
of the L10n on more rarely used languages.  The general idea is that support
for additional languages in "signed" builds would be addressed by a
"point-release" created with OS Builder:

http://wiki.laptop.org/go/OS_Builder

I must admit that am not very familiar with the build process myself, so I
cannot provide a lot of additional guidance in that area.

Another area to investigate is the presence or absence of the glibc locale
for mg_MG on the local machine.  It may have been left out in the build, but
I can't be sure.

http://sourceware.org/git/?p=glibc.git;a=blob;f=localedata/locales/mg_MG;h=996f2c53e345f606dbd507735a0813d5d640a4d1;hb=refs/heads/release/2.14/master

cjl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/localization/attachments/20111009/86c2ebc1/attachment.html>


More information about the Localization mailing list