W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2004

Re: [WAI-IG] Serving my page in the right language

From: Tina Holmboe <tina@greytower.net>
Date: Sun, 21 Mar 2004 15:19:16 +0100 (CET)
Message-Id: <200403211419.i2LEJGW3006815@asterix.andreasen.se>
To: w3c-wai-ig@w3.org

On 21 Mar, Jesper Tverskov wrote:

> Google is an example of a bad implementation.  If you go to
>  <http://www.google.com> www.google.com, you are always redirected
> to the language version of Google, like  <http://www.google.dk/> www.google.dk,
>  based on the HTTP language header. From the language version you have a link
> to google.com. If the link is followed a cookie is set and from now on Google 

  That's interesting. I have set the Accept-Language to English, and I
  *always* without fail get google.se - without any link to select
  anything else.

  Google *is* a good example of a bad implementation, yes.



> Language negotiation could also fail in some use cases, if the browser is
> not personal but public: libraries, internet cafés, kiosks, etc. Even if
> language negotiation succeeded for all users, it would be less obvious
> for all that we have an international or national web site serving several
> languages equally prominent.

  The use of the Accept-Language header to choose the initial content
  tree as well as cross-tree links solves both this problem and the one
  shown so clearly by Google, as well as making it emminently clear to
  the user that there are multiple language.

  It even makes cookies unnecessary. This discussion has, however, made
  it quite clear to me that more information on this topic is sorely
  needed. Perhaps time for an article.

  Thankyou, Jesper.

-- 
 -    Tina Holmboe                    Greytower Technologies
   tina@greytower.net                http://www.greytower.net/
   [+46] 0708 557 905
Received on Sunday, 21 March 2004 09:19:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:32 UTC