<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Walter,<br>
<br>
Based on my understanding of the GitHub process, I posted issues
documenting the problems. <br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 04/20/2017 12:09 AM, Walter Bender
wrote:<br>
</div>
<blockquote
cite="mid:CADf7C8szOxqt5W-qOeF+19-=yAq9dzuHk4E4_3O0JpnJ3=egqA@mail.gmail.com"
type="cite">
<div dir="ltr">In the meantime, it may make sense to walk through
all of the repos in sugarlabs on GH and ensure that those with
changes get updated version numbers, new .xo and .gtar files,
and we update ASLO and downloads. It seems our only mechanism
for doing this is manual at the moment. Tony, if you publish the
list of activities that are working properly from your recent
tests, I will begin the process of updating version numbers (and
ensuring that the correct repo path is in the <a
moz-do-not-send="true" href="http://activity.info">activity.info</a>
bundle) and making the new bundles.
<div><br>
</div>
<div>-walter</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Apr 19, 2017 at 10:19 AM, Chris
Leonard <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:cjlhomeaddress@gmail.com" target="_blank">cjlhomeaddress@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On Wed, Apr 19, 2017 at 1:30 AM, Tony Anderson
<<a moz-do-not-send="true"
href="mailto:tony_anderson@usa.net">tony_anderson@usa.net</a>>
wrote:<br>
</span><span class="">> I spent the last two plus days
testing the 137 activities with repositories<br>
> in github/sugarlabs.<br>
<br>
</span>Thank you for this effort, clearly additional follow
up is required<br>
and I hope it occurs.<br>
<span class=""><br>
> Localization also needs some attention. The setup.py
enables a developer to<br>
> generate a master Pot file while building a bundle
for release to ASLO. That<br>
> is probably the limit of the developer's
responsibility. However, existing<br>
> activities over time have developed localization for
many languages. Changes<br>
> to the messages will need new translations. Perhaps
the developer can use<br>
> diff to find differences in the Pot and to eliminate
un-needed changes and<br>
> test that new messages are passed through. This could
enable prompt release<br>
> of a new version without waiting for the localization
team to provide<br>
> translations for dozens of languages.<br>
<br>
</span>For a very long time, instructions to developers have
been "run the<br>
POT generation and never ever touch anything in the PO
directory<br>
again, The L10n team will take care of the rest of it for
you.".<br>
Unfortunately over the course of time, with changes in
Pootle<br>
versions, migration of our repositories to GitHub and the
decay of a<br>
"pootle-helpers" script set originally created by Sayamindu
Dasgupta,<br>
the early tight and hands-free integration between Pootle
and the<br>
repos has suffered and much of the process has returned to
manual<br>
intervention. The best path back to such a L10n nirvana is
an<br>
upcoming release of Pootle (ver 2.8) that brings back repo
integration<br>
through the implementation of the pootle-fs file system.<br>
<br>
At the present time if the messages of an activity are being
changed,<br>
we are still dependent upon periodic refreshes of the POT
file which<br>
can be accomplished with "setup.py genpot". I manually
upload that<br>
renewed template to Pootle and refresh the existing PO files
from the<br>
template and call for completion of any new strings. With
the<br>
gracious help of James Cameron in generating refreshed POT
files, this<br>
process has been initiated (and substantially completed) for
the<br>
entire Fructose collection and I am systematically
committing the<br>
refreshed PO files to the GitHub repos.(feel free to
examine/monitor<br>
pull request activity by github user leonardcj).<br>
<br>
<a moz-do-not-send="true"
href="https://github.com/leonardcj?tab=overview&from=2017-01-01&to=2017-01-31&utf8=%E2%9C%93"
rel="noreferrer" target="_blank">https://github.com/leonardcj?<wbr>tab=overview&from=2017-01-01&<wbr>to=2017-01-31&utf8=%E2%9C%93</a><br>
<br>
As for suggesting the reuse of strings common to already
translated<br>
activities, this is clearly a "best i18n practice", that
should be<br>
encouraged.<br>
<br>
I do envision sheparding us back to an enlightened era where<br>
developers largely can expect localizers to take care of
things for<br>
them (primarily through a migration to the 2.8 version of
pootle when<br>
finally released (or possibly 2.8.1 bug fix version if one
follows<br>
traditional Microsoft upgrade best practices). Ideally,
Pootle would<br>
take care of POT regeneration on the backend, as we used to
have it<br>
do.<br>
<br>
cjl<br>
______________________________<wbr>_________________<br>
Sugar-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.<wbr>org</a><br>
<a moz-do-not-send="true"
href="http://lists.sugarlabs.org/listinfo/sugar-devel"
rel="noreferrer" target="_blank">http://lists.sugarlabs.org/<wbr>listinfo/sugar-devel</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div><font><font>Walter Bender</font></font><br>
<font><font>Sugar Labs</font></font></div>
<div><font><a moz-do-not-send="true"
href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>