On 19 March 2014 08:21, Ankit Patel <
an...@redhat.com> wrote:
> On 03/18/2014 10:17 PM, arky wrote:
>
>> Hi Ankit,
>>
>> I completed Gujarati translations well on time (directly through hg
>>> or mercurial) during the first release of Firefox OS, but
>>> unfortunately Gujarati couldn't be included in the release because
>>> of non-support for the language!
>>>
>>>
>> Let's finish the localization and make sure there is Gujarati
>> keyboard and dictionary. Geeksphone builds and ships quite a few
>> languages for Keon and Peak series.
>>
>>
http://downloads.geeksphone.com/
>>
>>
> Absolutely. Jeff has already approached each of us individually for this
> task.
>
>
>
Tech...@translate.org.za - Could you guys please remove Gujarati from
> firefoxos translations? Gujarati localization team is quite comfortable
> with traditional way of managing translations through hg (or mercurial).
>
No Problem will do that as soon as I send off this email.
I would just like to clarify some things as this does leave the impression
that the Pootle tech-team just does whatever it wants and doesn't consider
language teams. Which is very far from the truth.
Firstly, when we get request to join teams we send those off to the team
whether they use Pootle or not. When we are asked for translation rights
for a hosted team we at most will give suggestion rights and point the
person to the teams wiki page. The rights assignment is for the team to
do. We also only host teams if they ask.
Just for some clarity, Gujarati is on Pootle because, as per the first
commit in PO
*Author: Dwayne Bailey <
dwa...@translate.org.za
<
dwa...@translate.org.za>>Date: Sun Nov 18 18:05:04 2012 +0800
Various: MozCamp Asia b2g sprint*
So we've simply hosted the files since that sprint. Sorry if that was some
kind of overlap with the team, I assumed most of the participants at that
sprint where team members as that's how they would have been at that
MozCamp.
In terms of your existing translation, I would recommend you actually get
it into Mercurial since there is nothing there now except what I committed
after the sprint and subsequently.
Lastly, and I think this applies to all teams. Choose what works for you,
Pootle works really well for many teams. Some teams have access to deep
technical skills and find it less useful. But I would caution you being
comfortable with you current process is sometimes not the best approach to
getting others involved in localisation. And from what I've seen in other
teams they'd love others to help and choosing Pootle has lowered their
barrier to entry for new participants, spreading the load.
--
Dwayne
*Translate*
+27 12 460 1095 (work)