[native-lang] Re: [website-dev] Re: [native-lang] Main Page - maybe translate it?

Hello all :)

On 18/12/2006, at 3:33 AM, Christian Lohmaier wrote:
>
> On Sun, Dec 17, 2006 at 10:38:18AM +0100, Johan Beckers wrote:
>> Clytie Siddall schreef:
>>> On 17/12/2006, at 1:43 AM, Konrad Stobiecki wrote:
>> [...]
>>>> I tried to imagine that I am an entrepreneur who does not know  
>>>> English.
>>>> I enter www.openoffice.org and see "Native Language" leading to  
>>>> native
>>>> projects. But if I do not know English, I leave the web page  
>>>> convinced
>>>> that I am not able to find the language version of  
>>>> OpenOffice.org that
>>>> suits me.
>
> Well, theres still the image of the worldmap inside that button, so  
> even
> when you don't know what "native language" means, you could guess from
> the image.

Not necessarily. It could be "Our products are distributed worldwide"  
or "Get our product from different locations" or even "The best  
product in the world".
>
> I don't like detecting of browser langauge or language by IP or
> something for the content of a webpage. It might work well for
> mirror-selection (select a mirror geographically near you), but  
> doesn't
> work very well for website content.

I don't agree. Content negotiation is designed especially for website  
content, and language choice is one of its strongest features. It  
serves content in the language requested by the user, via their  
browser prefs, _not_ the language of the browser itself, nor of one's  
location.
>
>> the appropriate NL project. Every NL project could place a link to:
>> OpenOffice.org International, or OpenOffice.org Worldwide.
>
> The big problem is that by far not every nl-project provides the info
> the english pages have. You can always visit your NL-project directly
> using your <language-code>.openoffice.org - a scheme very widespread
> across all possible websites.

But not necessarily known by the user.
>
> So I'd rather not have automatic selection.
>
> The job of the native-language projects furthermore not not to  
> translate
> everything that is in english, but to create a community in the
> respective language. There are lot's of common points of course..

Indeed, but all of us provide a lot of OOo-specific information in  
the user's language, including a general introduction, download links  
and help info linked to further info in English. We are the most  
effective entry point for non-English speakers.

from Clytie (vi-VN, Vietnamese free-software translation team / nhóm  
Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN