4 ms·
> but it's just to far into the browsers settings to be something that a normal user would adjust. Most users are on mobile these days, and picking your prefer
by simonw 2y ago
> but it's just to far into the browsers settings to be something that a normal user would adjust.
Most users are on mobile these days, and picking your preferred language is an unskippable step of setting up a new phone.
My hunch is that accept-language is far more accurate today than it used to be.
- myfonj 2y ago> […] picking your preferred language is an unskippable step of setting up a new phone. This does not address, or more precisely it even prevents the notion of: > I might prefer some sites in Danish, but others I'd like to have en English. , i.e. what you set in your OS or UA (browser) is always one preferred and optionally some fallback languages. I second that granular per-site control would be preferable for me either: some texts I prefer in my mother tongue (news, non-tech encyclopedic articles), the rest, namely technical documentation I prefer in English. (Also, I have very bad experiences with localised GUIs, where 1. familiarity with English "original" vastly helps when searching and 2. translations tend to range from bad to hilariously comical.) But I must admit that most websites serving of content in multiple languages, support client-side pref pretty well, so the situation is not so terrible, in my experience. Yet, the problematic of content negotiation and user <-> agent <-> author (provider) information passing is interesting and I'd say even under-engineered, and currently terribly suffer from security (anti-tracking) constraints. (Lately, there was some development in "Client Hints": https://developer.mozilla.org/en-US/docs/Web/HTTP/Client_hints https://developer.mozilla.org/en-US/docs/Web/HTTP/Client_hin... )
- peanut-walrus 2y agoI do not ever use any OS or other software in my native language, however I do want most non-technical websites to display in it when possible. How do I communicate that?
- brlewis 2y agoMy hunch is that Accept-Language became the best way to determine a user's language about the time it became common to bring a laptop while traveling. People use arguments today against Accept-Language that have been wrong for decades. EDIT: Best initial way to determine a user's language. MDN is right that overrides should be possible. https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_negotiation#the_accept-language_header https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_ne...
- bluGill 2y agoaccept-language is a list. Do I want English or Spanish first? What if your content is better in the second? I'm much better at English than Spanish, but I'm better at Spanish than the AI translation to English. Plus I may be watching that video in German to learn German even though I'm so bad at German I wouldn't put it in... Accept-language is accurate, but just isn't easy change it which is required to handle all the possible situations and get the right answer. Still everything else is worse.
- jeltz 2y agoNo they don't? I have never got that at least. It asks for my UX language, not for my preferred languages for websites. My preferred UX language is always English since most translations to Swedish are horrible while Swedish made websites are best read in Swedish and not a potentially bad English translation.