[SoaS] Missing gettext dependency needed for localised activities

Simon Schampijer simon at schampijer.de
Thu Sep 23 03:49:11 EDT 2010


On 09/21/2010 07:22 PM, Gary Martin wrote:
> Hi Simon,
>
> On 20 Sep 2010, at 11:30, Simon Schampijer wrote:
>
>> On 09/18/2010 04:01 PM, Gary Martin wrote:
>>> On 18 Sep 2010, at 10:52, "pbrobinson at gmail.com"<pbrobinson at gmail.com>   wrote:
>>>
>>>> On Fri, Sep 17, 2010 at 9:57 PM, Gary C Martin
>>>> <garycmartin at googlemail.com>   wrote:
>>>>> Hi Folks,
>>>>>
>>>>> Just wanted to email this ticket out and make sure the gettext package makes it into the Soas and Dextrose distros. Without it none of the activity po files will be built at bundle install time, thus failing to create the locale directory binary .mo files. Without this, activity translations will not work. This appears to be a break going back to at least Soas Mirabelle.
>>>>
>>>> Yep, it was dropped in Mirabelle because it pulled in horrific
>>>> dependencies and when I asked about it I was told it was historical
>>>> and that all the Activities should be pre-generating the translations
>>>> and that they shouldn't generated on local install.
>>>
>>> Ouch, that is news to me, no wonder activity localization is broken. Can you point me to the thread/ticket/wiki with that discussion? Including the binary .mo locale files in the source and/or .xo bundles is, to the best of my knowledge, not the usual workflow for activity releases.
>>
>> When you use the sugar tools it should just work fine:
>> "./setup.py dist_source" will create a tarball with just the *.po files.
>
> Oooh, so it does, learn't something new today, thanks :)

Excellent :)

>> "./setup.py dist_xo" will create the bundle with a locales folder that contains the .mo for the activity.
>
> Hmmm, now the question is does dist_xo build the locale folder and then make the bundle with it in, or do you have to manually build first before dist_xo?
>
> I've just looked through a mix of past .xo releases of mine, some have locale directories and some don't (aargh!). I'm pretty sure I alway use ./setup.py dist_xo on an XO-1 running an official OLPC 0.82 or 0.84 to build my official .xo bundle releases.

The code should do the right thing [1]. And from my testing it works 
fine as well. Not sure what might have went wrong on your end :/ Can you 
retry?

Regards,
    Simon

[1] 
http://git.sugarlabs.org/projects/sugar-toolkit/repos/mainline/blobs/sucrose-0.84/src/sugar/activity/bundlebuilder.py#line283


More information about the SoaS mailing list