Chrome sends the HTTP_ACCEPT_LANGUAGE header sets to the language of its interface, which for English is "en-US,en;q=0.8".
If every website did the right thing this would probably be a sensible thing to do. One problem which arises often enough is that most multi-language web-sites (at least in multi-lingual locales) figure that having only en-US is equivalent to not having the language preference set at all. This, as I understand it, on the grounds that people who do not bother (or do not know how) setting it have en-US as their only language-accept header. With a settings other than en-US only (even en-US;en-CA) these websites send users to the page of the appropriate language, otherwise they send users to a default page (which can be a random language for the locale or a language-selection page). This can make it frustrating when you always get the page of the wrong language or the selection page when the website should _know_ which page to display based on the HTTP_ACCEPT_LANGUAGE header. Some better web-sites use a cookie to store the selection a user makes on the language selection page. This is better but does not work when cookies are disabled, blocked or in incognito mode. The question is what to do about it? Mozilla simply gives a UI for users to manually set accept language and order them according to preferences. It certainly low-level but gets the job done. - Itai --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
