3 ms·
> If you don’t provide a language in your URL, you are implicitly sending the message that the documentation will never be translated. Is the `accept-language`
by randallsquared 8y ago
> If you don’t provide a language in your URL, you are implicitly sending the message that the documentation will never be translated.
Is the `accept-language` header basically dead, these days?
- a1369209993 8y agoYes, and good riddance; a GET request for a given URL should return bit-for-bit identical results[1] regardless of browser differences[0]. 0: Explicitly stateful features such as API endpoints or "logged in as" fields aren't browser differences. 1: The resulting file, not necessarily the TCP stream used to transfer it. 2: Yes, there are exceptions (eg http://canhazip.com/more http://canhazip.com/more), but documentation is almost the diametric opposite of being one of them.
- Tomte 8y agoThank God, yes. I mean, in theory it's great. In practice you always got cringeworthily bad translated versions of the Debian web site. (A few years ago Debian's German pages got much better)
- jessaustin 8y agoWhy would choosing language via URL be any different than choosing language via header, with respect to the quality of the translation?