922180 - Localized download box falling back to unsupported Firefox 3.6 version instead of a beta version for the locale or the latest version in en-US

Status: RESOLVED DUPLICATE of bug 924347

(www.mozilla.org :: Pages & Content, defect)

Description

[Pascal Chevrel:pascalc (PTO until April 26)]

bn-IN is a locale we lost in the past (we had release builds) and that we have been reviving in the last year. We have a team working on localizing mozilla.org now.

https://www-demo3.allizom.org/bn-IN/

on the demo server we can see that the download box logic is falling back to the 3.6 bn-IN build which is the latest we shipped for their locale.

We can't propose that, it's no longer supported.

The Php site on such situations proposes the en-US build instead:
http://www.mozilla.org/bn-IN/firefox/new

On vedrock the download logic should be more clever too.

I think we should propose an Aurora build in that case because we need users for the locale to create a localization community and to get feedback on the current localization.

The possibilities at hand seem to be:
- show en-US download box
- show bn-IN Aurora download box 
- don't show a download bow at all (for the homepage)

I am fine with either solution but we should make sure we don't prevent a team from having localized pages because they don't have Firefox ready that would be very demotivating for the localizers.

So I am interested in a short term solution that allows us to have a home page for locales we don't have Firefox for and a long term solution with more clever fallback solution for the download box (preferable an Aurora download box)

Comment 1

[Chris More [:cmore]]

I'm not a big fan of adding logic to bedrock buttons to show different download locations and builds by locale. It could make the bedrock download button logic more complicated than it should be. For example, this current download page points to an en-US build. http://www.mozilla.org/bn-IN/firefox/new/

Comment 2

[Pascal Chevrel:pascalc (PTO until April 26)]

This page shows en-US because we no longer have a recent bn-IN build to offer to our users, which may change in the future (sometimes we loose locales and we get them back later) and we need to offer a Firefox download to Bengali visitors. We could redirect them to en-US instead but that doesn't change the fact that we have download buttons on other locations than the download page itself, in this case the homepage. And it is also possible that we will suport locales on mozilla.org that will never have a Firefox build (Firefox OS only locales for example).

Comment 3

[Chris More [:cmore]]

ok, given that, how about we redirect /bn-IN/firefox/new/ to /en-US/firefox/new/ even though that is not much different than now since they still get the en-US build if they download from a localized Bengali page. Agree that it is possible to support more locales on mozilla.org than our products, but I would like to keep our download pages as close to a 1:1 for the page:browser available languages.

Comment 4

[Pascal Chevrel:pascalc (PTO until April 26)]

Yes that's ok, but what do we do for the home page? The team should send their translation to svn tomorrow.

Comment 5

[Kohei Yoshino [:kohei]]

dup?