5 ms·
Somewhere more prominent, in the main UI. The user may want to see different pages in different languages (e.g. to avoid garbage translations). Or perhaps expli
by anoncake 5y ago
Somewhere more prominent, in the main UI. The user may want to see different pages in different languages (e.g. to avoid garbage translations). Or perhaps explicitly ask the user.
- mavhc 5y agoAgain, 99% of people want the default language, annoying them isn't helpful, nor is adding 100 more menu options
- squiggleblaz 5y agoI think that's true however you slice it. There's lots of possibilities for defining the default: but the language the user has chosen to use for their system is vastly more likely to be right than a best guess. The other one is: pick to one language and stick to it. If the page I'm reading is in some European language, please show the GDPR messages in that European language not some other language. If it's a French blogspot blog being visited by a user in Germany, show the messages in French! This is almost guaranteed to be 100% reliable. It's not like Google is ignorant of the language of the page. (I can understand not having GDPR messages translated into say Indonesian. But if you do, then again - match the language of the page.)
- anoncake 5y ago99% < 100%. If the Accept-Language header is set correctly reliably enough, why don't websites respect it?
- mavhc 5y agoIn the beginning it wasn't set and was hard to change, and thus websites offered options within the site. And now I'd bet that many people writing websites don't know it exists, further reducing its usefulness, and probability of being offered as an easy to change option to the user. See also: client side certificates
- anoncake 5y agoThat probability depends only on what the browser makers decide to do. And there is no other way to determine the user's preferences.