266856 - Hard to find localized builds

Status: VERIFIED WORKSFORME

(www.mozilla.org :: General, enhancement)

Description

[Xavier Robin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-FR; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: 

When non english-speaking people wants to download Mozilla, they have either to :

1. Find their localization project. Unfortunately there are no link to
localization projects on products pages. Links cannot be found via the search tool.

2. Find the "Other Systems and Languages" page. Remember theese people often
don't speak english. For Firefox 1.0 PR the localized builds are located at the
half of the page and the languages are in english. If the current version is not
localized, there are absolutely no link to the last available version.

I don't know any other way to find localized builds.

Reproducible: Always
Steps to Reproduce:




Access to localized buils need to be simplified.
Here are some possible ways :
1. Make mozilla.org front page and products pages localizable. The user language
should be found for example via the accept-language header. Give a way for users
to change page language manually (for exemple : list all available languages for
a page).
2. Put links to localization projects on the front page and/or the products pages.
3. Find another easyer way to find localized builds, not depending on english
knowledge.

Comment 1

[Daniel Wang]

dupe of bug 248353, which is dupe of 247675

*** This bug has been marked as a duplicate of 247675 ***

Comment 2

[Xavier Robin]

Sorry, I really don't see how the bug 247675 would resolve this.
Downloading the file from an european FTP won't make the file localized...

And the problem still stay that people can't find locale communities, "Support
Forum" always points to Mozillazine...

Shall I report this on bug 247675 ?

Comment 3

[Ben Fowler]

Whilst I agree with the Reporter, I would suggest that where there are
active localisation projects, finding the localised builds is not
(necessarily) that hard.

If it is (to take the example from Bug 248353) really unduly hard
to find a German Mozilla, then I would agree that something needs
to be done to improve the systems for downloads.

I filed Bug 201853 (invalid) over the fact that it is not easy to
make a localised build. If it were easy to make/configure a localised
build one could at least share the problem of finding a localised
build with that of making a localised build, if not transform the
former totally into the latter.

I suspect that few of the developers actively work on localising 
projects still less with localised builds (there are probably good
reasons for this), otherwise this would have eliminated ages
ago.

Having said that, IIRC, localised milestones and releases do happen
promptly.

Comment 4

[Xavier Robin]

I have found a simple and efficient way to link to localization projects at the
OOo Home Page : http://www.openoffice.org/. It's a simple scroll-list.
It could be easy to do the same for Mozilla.

Comment 5

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

When we start distributing localized builds (along with the aviary 1.0
releases), they'll probably become a good bit easier to find.

Comment 6

[Daniel Wang]

> 1. Find their localization project. Unfortunately there are no link to
localization projects on products pages. Links cannot be found via the search tool.

we need to publicize www.mozilla.org/community/intl/

Comment 7

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

No, what we need to do is publicize our official localized builds.  IMO,
mozilla.org really shouldn't be pushing contributed builds of unknown quality.

Comment 8

[Anne (:annevk)]

This WORKSFORME. There is a visual link on mozilla.org "Other Systems and
Languages" which points you to official l10n builds.