Closed Bug 1159514 Opened 10 years ago Closed 8 years ago

Ensure www.mozilla.org web experiences are translated into Vietnamese

Categories

(www.mozilla.org :: L10N, defect)

Product:
www.mozilla.org
Component:
L10N
Version:
Production
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: cmore, Unassigned)

Details

We have had a sudden surge in people in Vietnam downloading the vi version of Firefox. Currently, the /firstrun/ and /whatsnew/ pages are not translated into vi. Given that vi is one of the top browsers downloaded now, we should make it part of the priority locales to ensure we have most of the major places of www.mozilla.org translated. It's being downloaded more often than German now.
:flod :pascalc: any thoughts here?
Web parts are not up to date, and haven't seen any active contribution on them in a while. Not much that we can do. https://l10n.mozilla-community.org/webdashboard/?locale=vi https://l10n.mozilla-community.org/~pascalc/web_l10n_stats/?locale=vi CCing also Arky who's in touch with the community and works on community in that area.
Setting locale field. To be honest, first time experience is the least of our problem right now. https://l10n.mozilla.org/teams/vi
Locale: vi / Vietnamese
(In reply to Francesco Lodolo [:flod] (UTC+2) from comment #3) > Setting locale field. To be honest, first time experience is the least of > our problem right now. > https://l10n.mozilla.org/teams/vi Also, first run is going to be changing. Arky: thoughts on how we can get some L10N contribution in Vietnam? This is related to my email a few days ago about the sudden growth of Vietnam downloads/users.
Flags: needinfo?(hitmanarky)
Flags: needinfo?(hitmanarky)
I have added Vietnamese l10n team to this bug. They have lot to catch up on web parts localization.
(In reply to arky [:arky] from comment #5) > I have added Vietnamese l10n team to this bug. They have lot to catch up on > web parts localization. Products don't seem in good shape either, and I assume (hope) the team is aware of that. The last sign-off for Firefox is fx32, which means users are seeing a lot of strings in English right now, even in prominent parts of the UI.
Yes I agree. Been trying to reach out to them to reactivate the l10n effort.
(In reply to Francesco Lodolo [:flod] (UTC+2) from comment #6) > (In reply to arky [:arky] from comment #5) > > I have added Vietnamese l10n team to this bug. They have lot to catch up on > > web parts localization. > > Products don't seem in good shape either, and I assume (hope) the team is > aware of that. > > The last sign-off for Firefox is fx32, which means users are seeing a lot of > strings in English right now, even in prominent parts of the UI. That's not good for a growing market that prefers vi lang. Thanks for checking it out. Is there anything we need to do to mark vi as a priority locale?
(In reply to Chris More [:cmore] from comment #8) > That's not good for a growing market that prefers vi lang. Thanks for > checking it out. > > Is there anything we need to do to mark vi as a priority locale? There's really no such thing as a priority locale. Localization is done by volunteers, if the team doesn't have resources the only thing we can do is try to help them find new volunteers. But it's not something that gives results right away, since they'll need to have resources to train them. Anyhow, someone is doing a lot of localization work in the last hours on mozilla.org, given that we moved from 710 strings missing to 447.
(In reply to Francesco Lodolo [:flod] (UTC+2) from comment #9) > > Anyhow, someone is doing a lot of localization work in the last hours on > mozilla.org, given that we moved from 710 strings missing to 447. Hi :flod, that was me. We have been notified by :arky yesterday and fortunately, it's a long public holiday here in Vietnam so I was able to clean things up a bit. Frankly, the team's morale has not been at its best for the last year. This is not helped by the fact that we are currently also very low on quality contributors since l10n is extremely hard to get right and a bad translation is worse than no translation at all.
(In reply to Chris More [:cmore] from comment #8) > (In reply to Francesco Lodolo [:flod] (UTC+2) from comment #6) > > (In reply to arky [:arky] from comment #5) > > > I have added Vietnamese l10n team to this bug. They have lot to catch up on > > > web parts localization. > > > > Products don't seem in good shape either, and I assume (hope) the team is > > aware of that. > > > > The last sign-off for Firefox is fx32, which means users are seeing a lot of > > strings in English right now, even in prominent parts of the UI. > > That's not good for a growing market that prefers vi lang. Thanks for > checking it out. > > Is there anything we need to do to mark vi as a priority locale? Jeff, Arky and myself added Vietnamese to the list of locales we are going to help grow now. Key Web parts for Vietamese on mozilla.org are in a much better shape today thanks to a localization sprint that was organized this month, pages in the download/install process should all be translated now. You can see the effect of the sprint on this graph: https://l10n.mozilla-community.org/~pascalc/web_l10n_stats/?locale=vi On the product side, I will let Jeff and Arky see how we can improve the situation quickly. On the web site.
(In reply to Trung Ngo from comment #10) > > Frankly, the team's morale has not been at its best for the last year. This > is not helped by the fact that we are currently also very low on quality > contributors since l10n is extremely hard to get right and a bad translation > is worse than no translation at all. Hi Trung, thanks for the help! Expect an email from me soon, I think I am one of the l10n-drivers focused on community building closest to your timezone, so I'll see how I can help your team grow and get back into the train of releases :)
Vietnamese is in good shape these days https://l10n.mozilla-community.org/webdashboard/?locale=vi
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.