> do you use Accept-Language? Or IP sniffing? Or user prefs in cookies? How do you think they picked which language to serve me in the first place? ;) What yo

> do you use Accept-Language? Or IP sniffing? Or user prefs in cookies? How do you think they picked which language to serve me in the first place? ;) What you're saying is true about eliminating ambiguity but parent commenter just linked to microsoft.com. When I had to do this for a site, the waterfall I settled on was: 1. Did they just manually pick a language/is it in the URL? (serve that language, set cookie) 2. Do they have a cookie? (serve that language) 3. Do we support any of their Accept-Language prefs? (serve that language, set cookie) 4. Serve en-us (fallback) My points being a) Microsoft.com is using langauge-accept (probably) and b) you can support URL picking & language-accept and not always have an ugly URL. EDIT: oops, changing my language to ``es``, clearing cookies & revisiting microsoft.com didn't change the language. I guess they are just serving everyone at .com English :p