3 ms·
That’s not localization, though. That’s market segmentation based on location detection, which is a different thing, strictly speaking. I mean, they could sti
by teddyh 8y ago
That’s not localization, though. That’s market segmentation based on location detection, which is a different thing, strictly speaking.
I mean, they could still show me the UK-only site if they determine that I am in the UK, but show me the UK site in German, with German units, dates and time codes, etc., because that’s what my browser might tell them that I prefer.
- C1sc0cat 8y agoHave you any idea how much work that is and how many things can go wrong I might have a dozen or more locales / languages and if you then want to see any locale in any language that's a huge amount of different urls Ok so you want German content in the UK do I show you the German locale and products legally available in Germany? the UK locale and products legally available in the UK translated into German? And do I age gate you based on German law or English what happens if I show you a BOGOF offer do I obey German law or English What happens if google messes up. What happens if your in Quebec and I accidently show you an illegal competition What T&C's do I show you
- jfoucher 8y agoNo need to have different urls for different languages. If you detect that the user's location is in the UK display the UK site, comply with UK laws etc... If that same user sends a German Accept-Language header, show them the UI in German. Doesn't seem much more complex that what you're already doing...
- C1sc0cat 8y agoYou might want to translate the url for any number of reasons mostly SEO related. But the main problem what if google gets confused and messes up and lands you on the wrong potentially problematic url - do you want to be the developer explain to the General counsel why the company is in trouble.
- megous 8y agoYou can't go wrong with ?p=564. You might want to skip 666, 13, and some other numbers too, though. :D
- deleted 8y ago[deleted]