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: Jesper Tverskov <jesper.tverskov@mail.tele.dk>
Date: Tue, 16 Mar 2004 08:23:48 +0100
To: <w3c-wai-ig@w3.org>
Message-ID: <000001c40b27$a036ea00$440bc650@tversdata>


An URL to a web page should be a uniform resource locator serving the
same content to all people, what is served should not depend on the
browser or user agent people use.

It is bad practice to use the HTTP Accept-Language header as a code fork
for what an URL should mean.

Cheers
Jesper Tverskov


David Woolley wrote:
The main disadvantages (assuming a client mediated redirect, so that at
least the bulk of the page is cachable) are:

- it is difficult to make an offline copy of a site;
- it is difficult to look at the text in a different language than 
  your own (and remember that many more browsers think that US English
  is the user's only language than there are users with that as their
  first language);
- a user bookmarking a page in preparation to link to it will end up
with
  the language specific page, not the language negotiating version.

Jesper Tverskov wrote:
I am not sure that language detection is a good thing. When I use an
English browser (I do) I want a French web site, a Russian website, etc.
to be in the original language when arriving. Then I can change language
if I need to. If I am in Spain and start looking at Danish web sites in
some local browser, I would hate if they were suddenly not in Danish.
Received on Tuesday, 16 March 2004 02:16:06 UTC

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