Getting crh locale into VCS

["Reşat SABIQ"]

Hi,

I'd like to get crh locale into VCS in the shortest path, without any run-arounds.

I thought

https://bugzilla.mozilla.org/show_bug.cgi?id=350639

would be the way to do it, but was pointed here.

Regards,
Reşat.

[Francesco Lodolo [:flod]]

Hi,
Thanks for moving the discussion here (I'm the same person who replied
in the bug, just in case it's not clear).

It looks like the language pack on AMO has been updated very recently,
but I wonder how much you've been keeping up with localization changes
at Mozilla since the bug was filed (in CVS era).

For example, a recent change is that we ask localizers to work against
Nightly (language pack is for release)
https://blog.mozilla.org/l10n/2017/04/18/localizing-nightly-by-default/

And we're shortly moving towards a scenario where only one Mercurial
repository will be used to ship all versions of Firefox (cross-channel).

As explained in the bug, these days VCS is not the first choice when it
comes to new languages. We prefer to set up online tools, track progress
on them, and start looking into setting up repositories only once we've
verified the ability from the localization team to keep up with the
release schedule
https://pontoon.mozilla.org/
https://mozilla.locamotion.org/

Localizing Firefox is not a small task, quite the contrary. And it comes
with baggage, like localizing mozilla.org (how do you download Firefox
if the main download channel is not localized?), which is another big
amount of work.

There are a few things in the discussion in bug 350639 that struck me:
* It looks like you're alone in this effort, and you don't have a lot of
time to dedicate to it. Is that correct? That would be a concern, we
have a few one-man teams that manage to translate everything, but that's
not something we encourage. It's going to lead to poor experience for
you (burn-outs) and your users.
* There are privacy concerns related to the use of this language in some
regions (not the first case). It becomes really hard to promote a
language/localization in this context, also based on previous experiences.

Both points make we think that a language pack is still the most
suitable avenue for this language. I'd like to hear other people's
opinion on this though.

I hope it's clear that it doesn't represent a judgement on the language,
we have plenty of languages that ship as language packs on AMO, either
due to technical limitations or limited resources.

Francesco

> _______________________________________________
> dev-l10n-new-locales mailing list
> dev-l10n-n...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n-new-locales

["Reşat SABIQ"]

Hi,

The langpack has been around since 2009 (v3.5). AMO is also giving me run-arounds, & a few weeks ago a dude there marked all versions disabled. Then i made some changes he wanted, & now only v53 is enabled.

 

You don't need pontoon to see if it keeps up: just look at all there versions on AMO, once i talk them into re-enabling everything that got disabled in an inexplicable fashion.

 

After 8 years as an addon on AMO, I'm interested in getting crh locale into VCS. Pontoon doesn't give me or anybody else anything (especially, after 8 years of work). It's gonna take months to release even if gets into VCS tomorrow. Pontoon, is a completely unnecessary run-around, IMHO.

Like the current extension, would like it to look like Turkish User-Agent from outside: Accept-Language (& hopefully other things like Firefox Help too).

Regards,
Reşat.

 

Envoyé: mercredi 26 avril 2017 à 23:49
De: "Francesco Lodolo [:flod]" <fl...@lodolo.net>
À: dev-l10n-n...@lists.mozilla.org
Objet: Re: Getting crh locale into VCS

["Reşat SABIQ"]

Hi,

Jorge, could you please get all the versions that were approved since 2009 shown on the following page:

https://addons.mozilla.org/en-US/firefox/addon/QIRIMTATARCA-til-destesi/versions/

Andreas somehow & for some reason disabled all versions instead of just v52 that he intended to modify a few weeks ago.

 

I don't have time for Pontoon now, & might never have it. The above, might help avoid unnecessary run-arounds with Pontoon based on there having been an addon that's been keeping up with everything since 2009 (in some aspects even better than Turkish, etc.).

Regards,
Reşat.

 

Envoyé: jeudi 27 avril 2017 à 01:51
De: "Reşat SABIQ" <ha...@gmx.fr>

[Jeff Beatty]

Hi Resat,

We appreciate your involvement. Do you use another computer-assisted
translation (CAT) tool, like OmegaT or SDL Trados to translate Mozilla
projects?

Pontoon & Pootle, like OmegaT or SDL Trados, have become necessities in the
process of producing an official localization. Each provides critical
components to maintain the quality and consistency of the localization
within an open source project, such as translation memory, terminology
suggestions, error reporting, etc. They provide transparency and openness
to the process, as anyone is easily able to view the status of any
localization project and make contributions without leaping over a high
technical barrier to entry. Using one of these CAT tools is a requirement
to receive repositories or become an official localization. You're also
always welcome to continue publishing the localization as an add-on.

Thanks,
Jeff

On Fri, Apr 28, 2017 at 12:06 AM, "Reşat SABIQ" <ha...@gmx.fr> wrote:

> Hi,
>
> Jorge, could you please get all the versions that were approved since 2009
> shown on the following page:
> https://addons.mozilla.org/en-US/firefox/addon/QIRIMTATARCA-
> til-destesi/versions/
> Andreas somehow & for some reason disabled all versions instead of just
> v52 that he intended to modify a few weeks ago.
>
> I don't have time for Pontoon now, & might never have it. The above, might
> help avoid unnecessary run-arounds with Pontoon based on there having been
> an addon that's been keeping up with everything since 2009 (in some aspects
> even better than Turkish, etc.).
>
> Regards,
> Reşat.
>

> *Envoyé:* jeudi 27 avril 2017 à 01:51
> *De:* "Reşat SABIQ" <ha...@gmx.fr>
> *À:* dev-l10n-n...@lists.mozilla.org
> *Objet:* Re: Getting crh locale into VCS

> Hi,
>
> The langpack has been around since 2009 (v3.5). AMO is also giving me
> run-arounds, & a few weeks ago a dude there marked all versions disabled.
> Then i made some changes he wanted, & now only v53 is enabled.
>
> You don't need pontoon to see if it keeps up: just look at all there
> versions on AMO, once i talk them into re-enabling everything that got
> disabled in an inexplicable fashion.
>
> After 8 years as an addon on AMO, I'm interested in getting crh locale
> into VCS. Pontoon doesn't give me or anybody else anything (especially,
> after 8 years of work). It's gonna take months to release even if gets into
> VCS tomorrow. Pontoon, is a completely unnecessary run-around, IMHO.
> Like the current extension, would like it to look like Turkish User-Agent
> from outside: Accept-Language (& hopefully other things like Firefox Help
> too).
>
> Regards,
> Reşat.
>

> *Envoyé:* mercredi 26 avril 2017 à 23:49
> *De:* "Francesco Lodolo [:flod]" <fl...@lodolo.net>
> *À:* dev-l10n-n...@lists.mozilla.org
> *Objet:* Re: Getting crh locale into VCS

--
Thanks,
Jeff

[Romi Hardiyanto]

2017-04-28 8:19 GMT+02:00 Jeff Beatty <jbe...@mozilla.com>:
> Hi Resat,
>
> We appreciate your involvement. Do you use another computer-assisted
> translation (CAT) tool, like OmegaT or SDL Trados to translate Mozilla
> projects?

Somewhere in the bug there was a mention of MozillaTranslator

I think the general idea is to use MozillaTranslator using the current
mercurial layout. Then upload each files/the whole locale to
Pontoon/Pootle.

--
Romi

["Reşat SABIQ"]

Hi,

Yes, for time management reasons i'd like to keep using Mozilla Translator (that i've been using all these years). If it's easy to just push the raw files or an archive into a tool like Pontoon i can spend some time on that too, if you are certain that you need it, but i don't have much extra time... If at some Mozilla Translator becomes unsuitable, or there's another convincing, actual & proven need, then it would be justified to look into spending time on giving it up & changing the workflow.

 

I've been keeping some progress stats for myself: please see attached screenshots.[1] Hopefully, Jorge & AMO team fix the AMO versions page.

 

[1]

Tercime Etilgen: Translated

Tüklü: in MozTrans lingo Fuzzy (but really it means "inherited from Turkish", with just a few strings in English (& those few can be easily translated before any Mozilla release)). Example: dil (Turkish, Azeri (Oghuz in general)), til (Crimean Tatar, Uzbek (Qipchaq in general)).

Topyekün: Total.

Regards,
Reşat.

 

Envoyé: vendredi 28 avril 2017 à 00:42
De: "Romi Hardiyanto" <romihar...@gmail.com>
À: dev-l10n-n...@lists.mozilla.org
Cc: "Jorge Villalobos" <jo...@mozilla.com>
Objet: Re: Getting crh locale into VCS

["Reşat SABIQ"]

The footnote[1] refers to image attachments on the previous email. It seems there stripped out due to size. Just in case, I'm trying to send them 1 by one after resizing and saving as .gif.

["Reşat SABIQ"]

But it seems attachments are always stripped out, so i'm giving up on attaching them.

In a few words, in v3.5 57.26% was translated, the reset was "fuzzy"; by v53 83.28% is translated, the reset is "fuzzy".

 

And the approach is: keep up with translating all the new changes (with shortcut being "inheriting from Turkish" (sometimes, under devtools), when there is not enough time to stick to it 100%).

 

Regards,

Resat.

["Reşat SABIQ"]

Typos fixed:

In a few words, in v3.5 57.26% was translated, the rest was "fuzzy"; by v53 83.28% is translated, the rest is "fuzzy".

 

Envoyé: samedi 29 avril 2017 à 17:48
De: "Reşat SABIQ" <ha...@gmx.fr>

À: dev-l10n-n...@lists.mozilla.org
Cc: "Jorge Villalobos" <jo...@mozilla.com>
Objet: Re: Getting crh locale into VCS