olpc-os-builder -- injecting Sugar translations

2010-10-14 Thread Martin Langhoff
[ working with a deployment team on planning... ]

We have 4 local languages that are not in Sugar nor Linux/Fedora
localizations. The plan so far is to start working on Sugar's Pootle
for Sugar and Activities. The timeframes don't allow for a full cycle
upstream (not even glibc knows about them).

How do we inject them into an OS image? I suspect we'll need an
os-image-builder module to

 - frob libc locales list (if required)
 - install sugar translations
 - install activity translations

Is there a better way? Am I missing anything?


m
-- 
 martin.langh...@gmail.com
 mar...@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: olpc-os-builder -- injecting Sugar translations

2010-10-14 Thread Daniel Drake
On 14 October 2010 16:58, Martin Langhoff martin.langh...@gmail.com wrote:
 We have 4 local languages that are not in Sugar nor Linux/Fedora
 localizations. The plan so far is to start working on Sugar's Pootle
 for Sugar and Activities. The timeframes don't allow for a full cycle
 upstream (not even glibc knows about them).

 How do we inject them into an OS image? I suspect we'll need an
 os-image-builder module to

  - frob libc locales list (if required)

This already happens based on the configured languages.

  - install sugar translations
  - install activity translations

The problem with force installing activity translations into the
regular place like this is that they'll get blown away on activity
update.

 Is there a better way? Am I missing anything?

If glibc doesn't know about them then you'll have to add all the
locale data as well. I suspect that is also a prerequisite for adding
a language to Pootle.

You could look at the code used to generate language packs and rework
that into a more generic archive which could be fed to
olpc-os-builder.

Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel