On Tue, 2004-05-11 at 15:09, Hans Petter Holen wrote:
This is for instance also used by many services to 'localize' the data. Eg when you use www.google.com you will be redirected to google.nl when in .nl or google.ch when in .ch.
This is really bad - my knowledge of Dutch is not getting any better when my coputer has an IP address tagged to be in the NL - or even worse, my understanding of French is still nil - even with a "French" IP address.
You should have been dutch then, as in that case you could at least partially have understood those languages, having had them in school ;)
My browser however knows what languages I prefer - so it would be nice is theese providers could listen to my browser rather than second guessing my language preferences.
That is indeed the Accept-Languages: option I mentioned. But even though my browser passes it: "Accept-Language: en-us,en;q=0.5" (stolen from a nc on localhost) google.com redirects me to google.ch with: "Google.ch angeboten in: English Français Italiano" Pointing to http://www.google.ch/en, http://www.google.ch/fr + /it The PHP variant is a bit nicer in that respect, typing: http://www.php.net/date redirects one to http://ch.php.net/date which is a quite-close at least country-local version of the site but in english. Though doing a small telnet to nl.php.net 80 and a simple "GET /date HTTP/1.1\nHost: nl.php.net\n\n" returns the page partially in dutch. I guess they can't pick from the three languages here in .ch or they don't have a translation ready. But these are just one of the few reasons that the country attribute should not be removed, optional okey, but removed no. Greets, Jeroen