Closed Bug 846792 (fx-l10n-az) Opened 11 years ago Closed 10 years ago

[az] Firefox release tracker Azerbaijani

Categories

(Mozilla Localizations :: az / Azerbaijani, defect)

Product:
Mozilla Localizations
Component:
az / Azerbaijani
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Pike, Unassigned)

References

(Blocks 1 open bug)

Details

This is a tracker bug for releasing Firefox az.

Your team's dashboard should be up on http://l10n.mozilla.org/teams/az. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibilty to your work.

The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug.

We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds mozilla generates, and puts on ftp.

If you're unsure what any of the terminology means, feel free to ask. Good places are http://www.mozilla.org/about/forums/#dev-l10n-new-locales or #l10n. Ask in public, you shouldn't assume that you're the only one with the question.
Depends on: 846793
Depends on: 846794
Depends on: 846795
Depends on: 846796
Depends on: 846797
Depends on: 846800
Depends on: 846801
Depends on: 772802
Depends on: 846804
Depends on: 846806
Depends on: 846805
Component: Other → az / Azerbaijani
I landed the nits I had on intl.properties as http://hg.mozilla.org/releases/l10n/mozilla-aurora/az/rev/969022862397, and also added them as suggestions to pootle. Mostly because I needed a changeset to try something out.
These bugs are solved. Any others?
Flags: needinfo?(l10n)
Hi Emin,

No other bugs to complete. All that remains is to translate the remaining strings in the user and config goals within Pootle ( http://mozilla.locamotion.org/az/firefox/goals ). How has testing the translation quality been progressing in the Firefox builds?

I also see that there are about 18 regular users of the locale. Has the l10n team done any social media campaigning to encourage more people to download and use the Azerbaijani localization?

Thank you,
Jeff
Flags: needinfo?(l10n)
(In reply to Jeff Beatty [:gueroJeff] from comment #3)
> Hi Emin,
> 
> No other bugs to complete. All that remains is to translate the remaining
> strings in the user and config goals within Pootle (
> http://mozilla.locamotion.org/az/firefox/goals ). How has testing the
> translation quality been progressing in the Firefox builds?
> 
> I also see that there are about 18 regular users of the locale. Has the l10n
> team done any social media campaigning to encourage more people to download
> and use the Azerbaijani localization?
> 
> Thank you,
> Jeff

Hi Jeff,

I'm also Ubuntu Azerbaijan LoCo team leader and ex Google Developer Group Baku member, so it wasn't so hard to announce about it. We made community, Mozilla Azerbaijan and we are getting more members everyday, and they are helping us to decide for example which services to use in Azerbaijani locale of Firefox (search plugins, webcal, mailto handlers and etc.).
We have little dictionary to avoid multiple translations to some words and phrases. Github account for users who like Github, Google translators who helps us to make some standards for technical words and support by most Azerbaijan blogs, websites and tech magazine which announced about us when we started to search for users. And today we will start testing Aurora with our users, then tech blogs will announce about them. We already have page where users can submit errors in translation and Q&A to help with technical problems.

Thanks for help,
Emin
Great! Sounds like you're taking many precautions and being as thorough as possible. I'm also happy to hear that more people are getting involved and also using the Aurora builds. Please continue to complete the translation in Pootle. Once the user and config goals are complete, please notify us and we can proceed with performing a sign-off review for launching Azerbaijani.
Hi Jeff, we finished till goal 5. Anything else? http://mozilla.locamotion.org/az/firefox/goals
Flags: needinfo?(jbeatty)
Hi Emin, thanks for the note. I just spoke with Axel. We're both comfortable will taking the localization in Aurora right now, pending a sign-off review. I also wanted to ask you about what the teams workflow for web parts is? It seems that you have a web parts project open in Pootle (which would commit into your SVN repo), but it also seems that you're translating strings locally and committing them directly to SVN yourself. This looks like it could cause merge conflicts when there are competing workflows like this. Could you explain that a bit please?
Flags: needinfo?(jbeatty)
(In reply to Jeff Beatty [:gueroJeff] from comment #7)
Web parts are currently in github account as some contributers were not comfortable with pootle. Also pootle sometimes gives system errors, today we had same problem again. So, I downloaded them from SVN and also added to github, translated all current web parts by myself and community finished translation for healthreport part (it will be committed after review of all pull requests).
So, for now web parts are translated using SVN and I know that Pootle is not checking them, so we don't use pootle for web parts. Any suggestions how we can add all translation to pootle?
I confirm that we disabled import from Pootle for az a while ago.

@Emin
You can ask Dwayne to import strings in Pootle from SVN, but at some point you need to choose between one of them, we can't have both without conflicts.
(In reply to Francesco Lodolo [:flod] from comment #9)
ok, we can remove web parts (only webparts) from pootle. For now there is no a lot translation in web files (there are few things and we use dashboard for that files). Using SVN is enough for now.
But for other projects we will continue to use pootle
(In reply to Emin Mastizada from comment #10)
> (In reply to Francesco Lodolo [:flod] from comment #9)
> ok, we can remove web parts (only webparts) from pootle. For now there is no
> a lot translation in web files (there are few things and we use dashboard
> for that files). Using SVN is enough for now.
> But for other projects we will continue to use pootle

Sounds good to me. I'll kick off the sign-off review this week. If you could update the web parts translations, we should be good to go by the end of the week.
(In reply to Jeff Beatty [:gueroJeff] from comment #11)
wanted to add them (upload) to pootle, but in pootle files have 'lang' in name. There is 5 new sentences in svn, waiting for my new rsa key to be added to commit new translations to svn too.
I commented in the other bug: you don't need a public key to use SVN, just use https:// instead of ssh:// (and I doubt that a user can have more than one key anyway).

Pootle uses .po files, not .lang files, you can't simply upload the original source files, you'd need to convert them.
Hi Emin, I'm doing your sign-off review right now. I see some blended English/Azerbaijani in devtools files. Looking at Pootle, it seems that devtools are halfway translated. I mention this because devtools are a piece of Firefox that can go either way for a locale: it may be more appropriate for devtools to be 100% translated or 100% in English. Having a half-translated module, like devtools can cause confusion for the user and give the impression of a "work-in-progress" level of quality to a user. Do you have a strategy/vision for what devtools should look like within the Azerbaijani localization?
Flags: needinfo?(emin)
Most of them came from old translations. 1 ago we discussed with developers, and they all said that they will use Firefox in their language if devtools will be in English. Same for me, as developer using devtools i  English helps me to solve errors quickly. So, we want to have devtools in English. Is there anything I must do for that? (ex. deleting all translations for devtools in pootle)
Flags: needinfo?(emin)
yes, that will need to happen in order to be sure that future commits into your repo from Pootle do not include those translations. In the mean time, what I can do is replace these devtools files with those in en-US and we can watch compare-locales and the conflicting accesskey report to see if there are any problems that accompany this. Can you confirm that you'd like me to take this course of action?
Yes, that would be good.
Alright, I've reverted devtools back to en-US in both Pootle and your hg repo. I'll proceed with the review now.
(In reply to Jeff Beatty [:gueroJeff] from comment #18)
> Alright, I've reverted devtools back to en-US in both Pootle and your hg
> repo. I'll proceed with the review now.

Hi Jeff, any results?
I see an accepted changeset for Firefox Aurora
https://l10n.mozilla.org/teams/az
(In reply to Francesco Lodolo [:flod] from comment #20)
> I see an accepted changeset for Firefox Aurora
> https://l10n.mozilla.org/teams/az

Is there anything that we must do now? (We - Mozilla Azerbaijan Community, Azerbaijani Localizers)
No, unless there's something I'm missing it should move to beta next week.
Your team page shows a few things on the website, I think they're exposed on pootle on http://mozilla.locamotion.org/az/mozilla_lang/goals
Emin is working directly on SVN for Web Parts, and all the missing strings are pretty recent additions, so that part is definitely in good shape.
http://l10n.mozilla-community.org/webdashboard/?locale=az
There is few new strings in repository, will commit them as soon as possible.
(In reply to Emin Mastizada from comment #19)
> (In reply to Jeff Beatty [:gueroJeff] from comment #18)
> > Alright, I've reverted devtools back to en-US in both Pootle and your hg
> > repo. I'll proceed with the review now.
> 
> Hi Jeff, any results?

Hi Emin, sorry for not speaking up. I accepted a changeset in Firefox Aurora. Congratulations, Fx33 will be the first official Azerbaijani release!
Today Firefox 33 beta released but there is no Azerbaijani version between them:
https://www.mozilla.org/en-US/firefox/beta/all/

In repository for 33.0b1 there is Firefox in Azerbaijani:
https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/33.0b1/linux-i686/
but in the same repository for latest-beta /az/ is absent:
https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/latest-beta/linux-i686/
Flags: needinfo?(jbeatty)
Flags: needinfo?(francesco.lodolo)
Depends on: 1063767
I just filed a bug to correct this. Thanks for pointing it out.
Flags: needinfo?(jbeatty)
Flags: needinfo?(francesco.lodolo)
Alright, I'm closing this out! Contact your local reps to arrange a party to celebrate your efforts, you deserve it!! :-)

reps.mozilla.org/people
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Thanks, finally we finished it, and now we have contributers who is contributing projects regularly. Now we will make little online event to make ideas for announcing Azerbaijani Firefox in Azerbaijan, later in Winter we will make party to celebrate it. Thanks everyone who helped us.
You need to log in before you can comment on or make changes to this bug.