[Systems] translate.sl.o

[Rafael Ortiz]

I think we can make an step back and think what we need for a fully working
pootle and a translation workflow, i think that sebastian and I can work on
this because is transversal to our work on activities. #pootle irc channel
is crucial for that purpose.

-What we have now is a patched 2.0.1 pootle, (I had to patch it)(but we need
to upgrade it)

- We have problems re-generating .pots (sayamindu's scripts have to be
rechecked and fixed).

-There are broken things on workflows that have to be standarized or
documented. this can be done via email as we tested creating sugar-0.92
branch.

- We  present bugs involving gettext and other involving merge or pulling
conflicts in activities that generate  differences in pots and thus in
translation strings and templates.(In this i expect that the most serious
bit is gettext bugs)

As conclusion I don't think that pootle is a bad tool, it just have to be
well maintained and we have to spend more time working on it.
Still I would like to see  transifex or other tools that should be
implemented if a) Don't affect critically our already established workflows
b) Present a better admin-ship experience.





On Tue, Apr 19, 2011 at 11:04 PM, Bernie Innocenti <bernie at sugarlabs.org>wrote:

> On Tue, 2011-04-19 at 17:28 -0500, Sebastian Silva wrote:
> > Hi Chris,
> > First of all let me reaffirm that I share your notion of the
> > importance of i18n for this project and greatly value the contribution
> > you have done. I think I was too fast in +1'ing the proposal without
> > all the information you have kindly shared. So -1 on "dropping"
> > pootle! :-P
>
> I'm also with you and CJL on trying to support the work of translators,
> but I've run out of ideas. Could we perhaps get the Pootle developers
> interested in helping us with updating, configuring and maintaining our
> Pootle instance?
>
>
> > There remains an issue as I said that we have very poor connection
> > thrughout deployments and this makes working with pootle as the only
> > option difficult. In Peru alone there are 61 native languages and I
> > think it is vital to try to support them. Of course an "unhosted"
> > workflow is only part of the story for this.
>
> Does Pootle support exporting and importing po files? This would solve
> the problem for translators who prefer to (or have to) work off-line.
>
>
> > I would love to work on this with you when we have the resources for
> > making another go at native languages.
>
> Very nice :)
>
> --
> Bernie Innocenti
> Sugar Labs Infrastructure Team
> http://wiki.sugarlabs.org/go/Infrastructure_Team
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/private/systems/attachments/20110419/eb16f551/attachment.html>