279560 - Translate products's description pages into different languages

Status: RESOLVED WONTFIX

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

Description

[Artem Skoretskiy]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ru-RU; rv:1.7.5) Gecko/20041108 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru-RU; rv:1.7.5) Gecko/20041108 Firefox/1.0

As far as Mozilla community set a goal to get a large market share, we should
think about more active distribution of Firefox and other our products.

At the same time, i live in Russia, and i know a lot of people that are ordinary
users, that doesn't know what, for example, Firefox is, its advantages and features.

Also, i see a lot of localized builds, that can satisfy their needs.
But there's a small gap between users and products, that are made for them, -
the SITE.

So, i suggest to translate site into different languages and show content
according to user's language. It wouldn't take much effort (in comparison with
localization of builds), but will be very useful for reaching our goal.

By the way, i've got an idea how to organize it - do the same as it is done with
localization builds.

Reproducible: Always

Steps to Reproduce:
Visit mozilla.org
Actual Results:  
See a lots of pages written in English. Can't understand a lot.

Expected Results:  
See the most pages (except news from related sites and discussions) in my native
language. Understand the most and feel happy :-)

Comment 1

[Anne (:annevk)]

Russia should be part of Mozilla Europe <http://www.mozilla-europe.org/>.

Comment 2

[Artem Skoretskiy]

I'd like to raise a question - may be there should be only ONE site? Not
mozilla.org and mozilla-europe.org ?

I think it is more logical! New users won't enter exacly Mozilla Europe. It will
enter Mozilla.org. Of course, there may be a redirection mozilla.org ->
mozilla-europe.org if your language is not en-US, but it's only workaround..

Anyway, domain name doesn't change the subject.

Comment 3

[Nicolás Lichtmaier]

Mozilla.org server should be properly configured to automatically show the right
language. This is very easy and it would be automatically for users. The server
would decide the right language based on the Accept-Language header (
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.4 ). It's how
Google does it.

Comment 4

[Anne (:annevk)]

Google uses the IP address actually, which kind a sucks.

Comment 5

[Artem Skoretskiy]

Doesn't matter how Google works.

The most client browsers send right Accept-Language header. So it is the most
convenient way to detect user's native language.

If browser is not localized or configured inproperly - let users change language
themselfes.

Comment 6

[Daniel Wang]

Can anyone find out how the organization want this? The last time we did this
(the start page translation) was a bad time because the l10n communities were
all busy doing other 1.0 launch projects. It would be better if the l10n
communities can be alerted ahead of time about this so we don't get out of sync.
(And if the organization isn't sure about the schedule, we could just throw in a
caveat.)

Comment 7

[David Boswell]

The Firefox and Thunderbird product pages on www.mozilla.com are translated into a large number of languages, so I'm closing this as wontfix since these product pages are no longer on www.mozilla.org.  We do plan to localize some of the content on www.mozilla.org however.