Closed Bug 1281144 Opened 10 years ago Closed 8 years ago

Missing translations in mozilla.org

Categories

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

Production
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: a, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 YaBrowser/16.6.0.8608 Yowser/2.5 Safari/537.36 Steps to reproduce: This file issets only in Japanese locale https://github.com/mozilla-l10n/bedrock-l10n/blob/fc16c1768e4a0acb9e660600848042dc17944e52/ja/firefox/all.lang I can't even see it in English locale. Actual results: When I visit these pages I see only English and Japanese version of these pages https://www.mozilla.org/en-US/firefox/all/ https://www.mozilla.org/en-US/firefox/organizations/all/ Expected results: You should add "firefox/all.lang" to all locales in Pontoon/Pootle because these are very popular pages.
> This file issets only in Japanese locale > https://github.com/mozilla-l10n/bedrock-l10n/blob/ > fc16c1768e4a0acb9e660600848042dc17944e52/ja/firefox/all.lang I can't even > see it in English locale. This is because the community/office translated everything on their own.
Status: UNCONFIRMED → NEW
Ever confirmed: true
After speaking with Flod, here is the initial assessment: (In reply to Victor Bychek from comment #1) > Also I think we should consider adding other locales for these pages: In general,https://careers.mozilla.org/position/o4zy3fwY > https://www.mozilla.org/firefox/system-requirements/ > https://www.mozilla.org/thunderbird/system-requirements/ There is not a lot to localize on these pages, as there are system and version names. These pages are probably part of the release notes, so they can't be localized at the moment. > > And release notes pages: > https://www.mozilla.org/firefox/releasenotes > https://www.mozilla.org/firefox/android/releasenotes/ > https://www.mozilla.org/firefox/ios/releasenotes/ Some of these pages are orphaned and not localizable. There has been some redesigning going on with many of these pages. They are slowly rolling out in Q3 and Q4. These links have been moved around as a result. In fact what you provided here are broken now because they have been moved to new locations. Let's wait until the wave of new design is over, we can look into how these pages are mapped and connected, and consider opening these pages up for localization. In general, none of these pages are set up on localization side. The reason Japanese is localized is because they installed bedrock and extracted strings to localize.
¡Hola Jeff! Ended up here due to a fellow #sumo contributor (Noah) trying to answer https://twitter.com/sergiodnila/status/756345047163998208 It seems like the "Update Firefox" story doesn't retain the locale between "scenes" or something. https://www.mozilla.org/es-MX/firefox/new/ > "Descarga gratuita" > https://www.mozilla.org/en-US/firefox/new/?scene=2 And from there the download link is en-US too https://download.mozilla.org/?product=firefox-stub&os=win&lang=en-US With the right set of clicks almost everyone can end up there from getfirefox.com Please consider adding these to Pontoon too. ¡Gracias! Alex
Flags: needinfo?(jbeatty)
It's in the hands of the mozilla.org team to make those pages localizable. I support the idea.
Flags: needinfo?(jbeatty)
(In reply to alex_mayorga from comment #4) > It seems like the "Update Firefox" story doesn't retain the locale between > "scenes" or something. > https://www.mozilla.org/es-MX/firefox/new/ > "Descarga gratuita" > > https://www.mozilla.org/en-US/firefox/new/?scene=2 And from there the > download link is en-US too > https://download.mozilla.org/?product=firefox-stub&os=win&lang=en-US Note: this has nothing to do with translating firefox/all (which is currently a pretty hidden page, see bug 1278315). It sounds like bug 1241969 instead.
(In reply to Francesco Lodolo [:flod] from comment #6) > It sounds like bug 1241969 instead. To clarify: that's assuming the browser is set with en-US as first locale in accept_languages, and the fact that the first page is es-MX is ignored when accessing the second scene. If that's the case (someone needs to verify it), it's worth filing a bug specifically for /new, since it's a serious issue.
Ciao flod! As I got multiple confirms on #mozilla-mexico I've filed https://bugzilla.mozilla.org/show_bug.cgi?id=1290962 Could you please check component, tags, etc. so it gets the right set of eyes? Grazie! Alex
Flags: needinfo?(francesco.lodolo)
Component looks good, CCing a couple of developers. It would be great if someone could find a reliable way to reproduce it with simple steps.
Flags: needinfo?(francesco.lodolo)
firefox/all is now translated. Considering this bug fixed per comment 0, even if it got messier along the way.
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.