3 ms·

> This is a the browser-side problem... No, it sounds like a protocol problem to me. How do I state in an HTTP request: "I speak English and German; if you can

by rlpb 9y ago

> This is a the browser-side problem... No, it sounds like a protocol problem to me. How do I state in an HTTP request: "I speak English and German; if you can serve both and the article was written in one and translated to the other, then give me the original please". That was a long sentence, but it wouldn't have been particularly hard to define well and put into the protocol when it was originally drafted. It's a bit late now, obviously. For example, one could define provenance of a translation much like NTP defines strata. Accept-Language could then have taken this into account.

sangnoir 9y ago
> No, it sounds like a protocol problem to me. How do I state in an HTTP request: "I speak English and German; if you can serve both and the article was written in one and translated to the other, then give me the original please". That is a problem with the quality of the translation/translators - not the protocol. The protocol is neutral on languages and considers all versions as equivalent, it only expects that you would pick one. The specific behaviour you are expecting can be trivially built into the server side without modifying the current protocol.