It's entirely ridiculous when you're abroad. Also annoying when in your home country, but the localized versions are not equivalent like e.g. programming documentation. Even in the ideal case you'd probably prefer the English original, but often they're machine-translated anyway and much worse.
Another extremely annoying thing I've noticed more often now are machine-translated versions of content in the search results. Reddit for example does this now, and it's just terrible. One of the main reasons I use non-English search terms is to get non-English results, e.g. because I'm looking for information on topics that is not globally applicable.
Right. You can basically hear the product team at Reddit humming star-spangled banner while conceiving this feature for themselves as monolingual people. The rest of the world can understand multiple languages just fine, thank you very much.
Yes, oh my Lord I've been getting seriously frustrated with Mongo's documentation lately. I'm not sure if it picks the language based on location or Accept-Language, never played around with it, but it's behavior is deeply rage-inducing.
I do a web search and get a list of results for the English version, open it and it automatically changes to PT-br as soon as JS loads, but then, after a few seconds, once the page is fully loaded, it jumps back to English, while keeping the /pt-br/ slug in the URL...
What the heck??
And yeah, the translation is very obviously not human made or reviewed. Furthermore, I'm PT-pt, so the differences to PT-br just make the experience even more annoying X)
Another extremely annoying thing I've noticed more often now are machine-translated versions of content in the search results. Reddit for example does this now, and it's just terrible. One of the main reasons I use non-English search terms is to get non-English results, e.g. because I'm looking for information on topics that is not globally applicable.