Using XO 1.0 battery to feed external circuit board
cjlhomeaddress at gmail.com
Mon Oct 10 01:30:25 EDT 2011
On Mon, Oct 10, 2011 at 1:04 AM, Yannis Kaskamanidis <kiolalis at gmail.com>wrote:
> How can we include Greek language in every new release. Can someone help me
> by describing the process of integration? We use XO's in my classroom, but
> without Greek.
Per Daniel Drake's e-mail of Feb 4 2011
There is a list of languages included in OLPC builds by default. (German
was added to that list by request).
That e-mail also points out that other langs can be added by request
(although Daniel would have to make that call).
How big is the Greek deployment? That might help influence the decision.
In any event, builds supporting additional languages can always be generated
via the OS Builder toolkit chain and even signed by OLPC for deployment on
locked XOs as a "point release" if there is sufficient justification to do
I am personally supportive of the inclusion of Greek by default, if only
because the Greek L10n team has always demonstrated exemplary diligence in
keeping up with their strings.
However, it is worth remembering that it is essential to make tradeoffs
between the set of included languages in "stock" builds (generally those
with larger deployments) and the image sizes of the builds. It is a
testament to the success of the L10n effort that OLPC builds can no longer
afford to include all of the L10n strings that are available.
I believe that the advances made in developing the OS Builder tool chain
makes it far less important whether or not a given language is included in a
"stock" build, as custom "point release" builds are much easier to generate,
and often will be far preferable for a given deployment as tehy can be made
to include specific content as well.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel