Hi Clytie, *, On Mon, Dec 18, 2006 at 04:54:11PM +1030, Clytie Siddall wrote: > 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: > >>[...] > > > >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".
Well, wouldn't it still be a good guess if you want onother language (besides the last one, but I don't really think anybody would connect the map with that one)? Do you have another suggestion for a different iconography? > >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. That's not my point. It is not that it would not work technically, but that it doesn't make sense in this case. > >>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. Yes, but you miss the real point again it seems :-) The point is: Native-lang projects have varying focus, you cannot serve sites depending on language since the nl-projects don't all offer the same content. The only place where this could work as of today is the why.ooo pages. > [...] > 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. I don't deny that, but redirecting the user to a different page than www.ooo by any of the fancy language-detections things is not the way to go in my opinion. What would maybe work as is to dynamically add a link in the user's language at the top of the native-language page. (saying approx: "Visit the pages of the <language> native-lang project") But the only technology we could use for this is javascript... ciao Christian -- NP: Silverchair - Anthem For The Year 2000 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
