<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello Browse developers,<br>
<br>
I'm in the process of integrating Aymara translations into the
Operating System image currently being tested for deployment in
Peru. This image has Sugar 0.94 and thus only supports activities
built with GTK2.<br>
<br>
This means in some cases we will be using older, compatible versions
of Activities such as Browse 129.<br>
<br>
Even though the translation project in Pootle is up to date, Browse
129 did not have these translations.<br>
<br>
Now, we're using Sugar Network to provide feedback and support
channels for activities. This means that we can only include
Activities which have been released into ASLO [because Sugar Network
uses ASLO as source].<br>
<br>
I've put a great deal of thought into how to backport translations
to older versions and have come up with the following procedure (to
produce <a class="moz-txt-link-freetext" href="http://people.sugarlabs.org/icarito/Browse-129.1.xo">http://people.sugarlabs.org/icarito/Browse-129.1.xo</a>):<br>
<br>
<tt># To be done within a clone of
git://git.sugarlabs.org/browse/mainline.git<br>
<br>
# Get v129<br>
git checkout v129<br>
<br>
# Get updated translation from HEAD<br>
git checkout origin/HEAD po/ayc.po<br>
<br>
# Merge translations with proper template for this version<br>
msgmerge po/ayc.po po/Browse.pot -o po/ayc.po<br>
<br>
# Use your favourite text editor to bump version of
activity/activity.info<br>
<br>
# Add and commit<br>
git add po/ayc.po<br>
git commit -m "backport ayc translation"<br>
git add activity/activity.info<br>
git commit -m "bump v129.1"<br>
<br>
# Tag new version<br>
git tag v129.1<br>
<br>
# Make bundle (I like this way, or use setup.py from within Sugar
0.94)<br>
sweets dist_xo<br>
<br>
# The (hopefully) resulting dist/Browse-129.1.xo should be fine
for release (tested by me)<br>
# Find my version at
<a class="moz-txt-link-freetext" href="http://people.sugarlabs.org/icarito/Browse-129.1.xo">http://people.sugarlabs.org/icarito/Browse-129.1.xo</a></tt><br>
<br>
The resulting xo works fine and has Aymara translations.<br>
For your convenience I've also attached the resulting commits as
patches.<br>
<br>
Now <u>I need your help getting this version into ASLO</u>! Will it
be possible to release a 129.1 with this updated translation? <br>
<br>
Note we are expected to continue the process of adding native
languages (and we have about 60 of them in Peru) so probably we'll
have to do this again sometime in the future. Any suggestions for a
better process are welcome.<br>
<br>
Thanks for your hard work and for supporting deployments,<br>
Sebastian<br>
</body>
</html>