<div dir="ltr"><div class="gmail_extra">Hi Tony!</div><div class="gmail_extra"><br><div class="gmail_quote">On 3 April 2016 at 01:45, Tony Anderson <span dir="ltr"><<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">I can't imagine the process is so simple. The overwritten
translations were probably on <a href="http://translate.sugarlabs.org" target="_blank">translate.sugarlabs.org</a>. <br></div></blockquote><div><br></div><div>Yes, that is the Pootle instance I referred to in my previous email, sorry that I wasn't clear on this point.</div><div><br></div><div>(I had not looked at that site until this thread came up, and when I looked at that page, I saw that the most completely translated Activity was "Favourite Fonts" - and since I am passionate about the fonts topic, I explored it, and found that I could create an account and overwrite the strings within a few minutes.) </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
Sugar developers need to determine which Pootle files to install in
an image. Each individual Sugar activity has an independent set of
translations which needs to be updated into a new version of the
Activity.<br></div></blockquote><div><br></div><div>(I am not sure what you mean by "Pootle files"? I wonder perhaps you mean PO files, since Pootle is an acronym for PO O.nline T.ranslation L.ocalization E.ngine, and PO is an acronym for P.ortable O.bjects, the file type for translation strings used by GNU GetText :) </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">As Sugar, we need a process to handle this. I strongly believe it is
a mistake to do perform localization directly on the Pootle server.
It would be better <br>
to do the localization at the locale and verify it by use by the
native language speakers (primary school children). Update for
activities is to submit new po <br>
files in an updated version of the acitivity (version += 1). This
process is under git version control. These updates, once vetted,
can be updated on <a href="http://translate.sugarlabs.org" target="_blank">translate.sugarlabs.org</a>. On a new Sugar release,
OLPC or someone determines which activities and which versions of
those activities to include in the image.<span class=""><font color="#888888"><br></font></span></div></blockquote></div><br><div class="gmail_extra">If the above was carried out, then what would you see as the purpose of <a href="http://translate.sugarlabs.org">translate.sugarlabs.org</a>?</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div>My understand is that:</div><div><br></div><div>1. Sugar <i>distributors</i> need to determine which PO files to include in a SOAS (or installation) disk image. </div><div><br></div><div>2. Each individual Sugar activity has an independent set of translations, which needs to be updated by the individual Activity's section of the community for each new version of the Activity, and these translations are stored in a PO file. </div></div><div class="gmail_extra"><br></div><div class="gmail_extra">3. <a href="http://translate.sugarlabs.org">translate.sugarlabs.org</a> is a Pootle instance that manages a collection PO files for many Activities, including the "core" ones developed at OLPC 10 years ago, and the most important/popular ones developed by members of the Sugar Labs community. </div><div class="gmail_extra"><br></div><div class="gmail_extra">4. Currently the <a href="http://translate.sugarlabs.org">translate.sugarlabs.org</a> Pootle is configured to use a 'wiki style' permissions model where any user can overwrite any string. </div><div class="gmail_extra"><br></div>I proposed that the <a href="http://translate.sugarlabs.org">translate.sugarlabs.org</a> Pootle be re-configured to use a 'pull-request style' permissions model, where any user can suggest changes to any string, and those changes must then be reviewed and approved by someone with a 'trusted' account. </div><div class="gmail_extra"><br></div><div class="gmail_extra">I understand that your proposal is also to move to a 'pull-request style' permissions model, where translators use desktop PO-file editors (such as those listed at <a href="http://stackoverflow.com/a/394632/1174651">http://stackoverflow.com/a/394632/1174651</a>) and submit the PO file via an actual git pull request. </div><div class="gmail_extra"><br></div><div class="gmail_extra">I fully support your proposal, since it is a different strategy to realise the same goal (to change the permissions model) and in fact I probably prefer it to mine: git is a "powerful idea" in the Papert/Kay sense, and the more that git pull requests are used as a strategy to develop all aspects of Sugar, the better :) </div><div class="gmail_extra"><br></div><div class="gmail_extra">However, all else being equal, web based editors are more convenient than desktop editors and so likely to see higher engagement. </div><div class="gmail_extra"><br></div><div class="gmail_extra">-- <br><div class="gmail_signature">Cheers<br>Dave</div>
</div></div>