[Localization] Complicated Procedure, Restricted Wiki

[Jim Gettys]

There are two issues here:

1) Fedora and translations for packages used by OLPC from Fedora (or
Linux in general; Launchpad translations are also useful; just may take
longer to get upstream to Fedora until Fedora updates packages from
upstream).

2) Localization of OLPC activities. Translations for OLPC's activities
are now very, very urgent to complete.

OLPC is not in a position to directly affect the Fedora project, who, at
the moment, have the bigger problem; OLPC's problem is relatively small
as we're not concerned with translating all of a full Linux
distribution, a seriously large challenge, and which I am fully
sympathetic to the difficulties involved.

But we've tried on a number of occasions to get problems resolved there,
and haven't succeeded, and we've run out of time.

Volunteers working on OLPC have been configuring Pootle and have that
working, though have been having trouble with the localization back end
for Git, to commit the changes back into repositories.  We have a
volunteer to help with that until such time as the Git backend can be
made to work.

Their work is documented here: http://wiki.laptop.org/go/Pootle. A
suggested possible workflow until git support can be worked out
(volunteers?  It's been harder than Xavi or Rafael have expected to get
GIT support worked out).

Xavi's proposal is attached.

Unless I hear complaint, I plan to go ahead with this plan.

Comments?
                                Best Regards,
                                    - Jim Gettys


On Wed, 2007-10-10 at 20:50 -0700, big one wrote:
> I want to help in Fedora translation project, but unfortunately there is no languange coordinator for a certain language.
> 
> The procedure for becoming a language coordinator is difficult/complicated and I don't have the time/ skill.
> 
> I suggest other methods:
> 1. One person or a group of local users fluent in the language become initial user group who screened translation result. The person who want to do the translation can send the "*.pot" file to the team using e-mail attachment (text inside zip file). If the team agree, the "*.pot" file is accepted as official translation.
> 
> 2. Protection for name / email address of the translators from spam.
> 
> 3. Restricted Wiki: the translator can apply for user name and password and the tranlator can do the modification online. If the result is incorrect / bad, the translator may be banned / the user id revoked.
> 
> Is the above idea possible?
> 
> A question: If I have a complete set of tranlated "*.pot" files for certain language, where should I sent the files to, if there is no language coordinator?
> 
> Thank you.
> 
> _____________________________________________________________
> = You want FREE web-based email ? 
> = You want your own @qon.lao.net address??
> = Then you want LaoNet's WebMail !
> = Get it at http://webmail.lao.net !!
> _______________________________________________
> Localization mailing list
> Localization at lists.laptop.org
> http://lists.laptop.org/listinfo/localization
-- 
Jim Gettys
One Laptop Per Child

-------------- next part --------------
An embedded message was scrubbed...
From: Xavier Alvarez <xavi.alvarez at gmail.com>
Subject: l10n + Pootle
Date: Thu, 11 Oct 2007 02:51:53 -0300
Size: 6760
Url: http://lists.laptop.org/pipermail/localization/attachments/20071011/d652cb41/attachment.eml