Re:It’s probably never going to work in German
by AnabeeKnox on Tuesday February 26, 2019 @04:26PM
(#19258428)
Me too. I've had to start using DuckDuckGo, NOT for privacy reasons, but it get around Google's lunatic forced geolocated search.
Re:It’s probably never going to work in German
by TeMPOraL on Tuesday February 26, 2019 @03:09PM
(#19257891)
My previous job had me traveling between Germany and China; during that time, Google's ridiculous localization of search results was becoming unbearable. I ended up permanently overriding my default search engine to point to this URL: https://www.google.com/search?hl=en&q=%s.
(It broke auto-suggesting search terms in the omnibar, but the actual search results are again sane.)
Re:It’s probably never going to work in German
by blattimwind on Tuesday February 26, 2019 @07:03PM
(#19259648)
You cut to the core of the problem; user-preferred language for content is arbitrarily context-dependent.
Re:It’s probably never going to work in German
by anoncake on Tuesday February 26, 2019 @07:22PM
(#19259762)
For most search queries, identifying the user-preferred language is quite easy though: It's the language the user used for his query.
Of course, Google goes to great lengths to ignore this hint.
If I search for "std::vector", I get https://de.cppreference.com/w/cpp/container/vector as the first result and https://en.cppreference.com/w/cpp/container/vector as the second. The German translation is just awful and completely trips you up if you know English. I don't understand why it keeps pushing them up.