In real life a large number of corporations (and developers) have their computers configured with English as this is the main language of the coorporation and makes IT-support much easier. (we don't even need to talk about how badly botched many language translations are).
These users will still want Google to return results in their native language.
There is a much much larger number of users like this than travellers from USA.
One thing that bothers me a lot with US websites is that they always assume English language means 12-hour clock.
Apple has learned the above over time: it is much easier today to get a Mac running with English and 24-hour clocks.
> Mac running with English and 24-hour clocks
The UK locale (probably Ireland too) has provided a 24 hour clock in Windows for decades. Although thinking about it, little-endian dates (11 March, 11/03/2022) would probably annoy Americans as much as mixed-endian dates annoy me.
Google thinks they known better - they do not.
It depends. It is definitely the case for tech but not for everything. For philosophy, science, movie reviews, cooking, and of course anything related to French culture, there's a lot of high quality content.
Reading comments so far and the article I think we're mixing up many different use cases and choices.
If I set my browser to English, that means I want the interface language to definitely be English. Do no serve me the interface in Japanese just because I'm in Japan. I won't even be able to find the "Change language here" dropdown ...
Now search results are a different thing. If I type something into www.google.com while being on US soil with en-us as my language setting that is in French, isn't it obvious that I might primarily be served French language content and that is what I want too? While the interface of Google is still in English? Or vice versa? If I type an English language query into www.google.fr while fr-fr is my language setting, I expect worldwide results in English, while my interface is still in French. Sure, restaurant name search results I might want sorted differently based on location and that's a good thing overall, but leave my interface language alone!
Consider this though: It's not an inherently unambiguous and language agnostic format. It just so happens that there is no country that would write the above date as 2022-11-03. If there was, we'd have the same issue again.
> Gregorian, year–day–month (YDM) This date format is used in Kazakhstan, Latvia, Nepal, and Turkmenistan
https://en.wikipedia.org/wiki/Calendar_date#Gregorian,_year–...
it most importantly sorts properly when used at the front of a filename, and it's surprisingly easy to read; and in context I'm mostly looking at the month-date which can be picked off the end, "march 11" which is how we say dates in English anyway
time of day can be appended without messing with the collation (usually i put a space)
I think every time this topic comes up I come across someone with this misconception - usually from a country that celebrates the 4th of July.
But at the same time, "Fourth of July" should not be used to infer anything about how Americans say dates. It doesn't help prove that both orders are used for dates.
In the real world, some people say day-month and some say month-day, and the holiday is called "Fourth of July". In a counterfactual world where everyone switched to month-day, the holiday would still be called "Fourth of July". So you can't use "Fourth of July" to demonstrate what people actually use for dates.
Once upon a time yes.
So that makes it sort of a reason to think those are still possible, but equally validly it acts as a reason to say nobody does that anymore.
So overall it's entirely reasonable to ignore such ambivalent evidence/"evidence".
And month/day is not as confusing as day/month (widely used in Europe) since it doesn't correspond to how we say dates.
moving the year first then using the American MM/DD is the least confusing way to do it
Not trying to argue one way or the other, just adding some extra context.
July 3rd
4th of July
July 5th ...
Also my experience is that only Americans say the month first. Today is the 11th of March.
Confusingly Google will also write some sentences half in english and half in the local language. E.g. "Google is also available in: <insert foreign language here>" (rather than the full sentence being in the foreign language.
It's the kind of attention to detail that I've become accustomed to from them
This specific one might be on purpose to avoid translating language names. If you land in page entirely in Chinese but you see the word "English" in Latin characters under a link, you can click it to escape. But if it's itself in Chinese you'll never find it. I do the same in applications, have a menu for languages but don't translate language names, if you change language by mistake you can always find your way back.
Compare "Rirgwyd rkrgru dlwhgi ro English" to "This page in English". Which is better for people that only read English?
And when a page is in the correct language, I would prefer not to have entire sentences in a different language.
Back to Google - Algorithmically there are likely straightforward reasons for why this is happening. Clearly the contents of the pages are composed from a mixture of sources, for reasons unknown these sources may not be able to detect or receive the localisation settings of the end user. Recent changes to privacy protections and cookie limitations may also be a contributor to these issues. Including the obvious: getting ads in the wrong language.
I'm trying to have English language but metric units, 24 hour clock and ISO dates... Seldom can I achieve that.
On the French-language mandatory corporate Windows laptop, Excel formulas are translated in French - so when searching for recipes on the web I have to translate them !
I enjoy sites such as Thomann.de which have separate settings for language, country and units of measurement.
Best tip I've seen all day!
I just happen to want slightly different choices than it allows.
This[2] askubuntu answer goes into more detail.
[1] https://lh.2xlibre.net/locale/en_US/ [2] https://askubuntu.com/a/162714
I do the same. There is usually a locale available with that, look for English (Ireland), English (Europe), English (Denmark), or English (Germany).
It isn't so. I write half my emails in one email, the other half in another. Often emails will have sections in one language (e.g. quote from another email) and other sections in a different language.
Spelling tools must be able to detect language automatically to be of any value and be able to handle multiple languages within a single sentence!
Says who? This is a baseless assumption.
Just listen to the settings that specify what language the user wants. That's what it's for. And the browser should ask the OS or the user for their language preference. And if IT-support wants one language for the interface in order to facilitate support, they can still set the other language for browser preference.
Just ignoring all settings and making blind assumptions will guarantee you will be wrong many times.
In case you haven't noticed: Users lie. All the time. Every day.
If Google found that "just listening to the settings in the HTTP request header" helped more users than it hurt, Google would have switched to using it a long time ago. The web is a messy place - sometimes you can't even trust a website to report its own encoding correctly.
The browser setting that every browser sends to any server it requests data from. Usually this defaults to the system language, but you can add more languages with a priority. Mine is English (prio 1), German (prio 2), yet I for some reason get tons of spanish content as I am going back and fourth between countries these days just based on Geolocation.
The only one differing is the grandparent, which was asserting first that users might think showing anything other than the local language is an error, and then asserting that users want their native language, and so I'm not really certain what they're asserting since those two are not always the same (maybe that the first is the reason Google does it, the second is asserting the preferred behavior, which is nearly agreement, in that the latter is doable via OS or browser preferences).
I'm as irritated as anyone when something doesn't cater to "power users". But if we're trying to understand the reason behind the decision instead of just venting, then it's instructive to consider just how computer-illiterate the non-power-user is for a product as massive as Google Search, and how annoying characteristics may be a consequence of trying to satisfy both you and them.
It's beyond nuts. And "catering to the computer illiterate" can't be the explanation.
[1] it = the front page. No guarantees that it'll work for other parts or other Google sites like Google Maps[2]. I remember noticing years ago that even with the /ncr, when the front page had a doodle, mousing over it still showed the tooltip in the local language. Billions of dollars, and can't even program a website.
[2] Yeah it still gives me my local currency for hotels in Google Maps. I live in country A, I was visiting country B, and I needed to find a hotel in my home country A. I was logged in. Google knows my address and that my account is tied to Country A (because... Play Store region locking for content, blah blah), but it still showed me the hotel prices for the country I live in and was looking for hotels in, in the foreign currency of the place I was currently sitting at. Fuck you very much, Google!
I just tried, and while the page is in English, the top search results it returned are localized results to the country I happen to live in.
I have this issue with Microsoft. The national language in my country is English. However, Microsoft's store defaults to a local language that I don't speak every single time. My IP is also not from a part of the country that speaks that language either.
There are several layers available to Google though -
- They could use the system language setting
- They could use the browser's language setting
- They could use the user's Google account setting if the user is logged in
Corporations could set the system language, or the browser language, and it could still be overridden by the user in their Google account if they wanted to do that. Instead though, Google chooses to geolocate the user's IP address and use that which works for no one.
That's the most annoying thing. When I travel, I still want to see stuff in imperial units, and Google just switches to Metric and stays stuck that way.
Note that other values for Accept-Language are not ignored. I haven't tried it myself, but I've heard some people say that setting their language to en-GB or en-CA works well.
You can also use &hl=en-US, which always takes precedence.
One sad thing is localization for Canada is kind of broken for a lot of platforms it seems? For a lot of people that I help having their locale has Canada seems to usually base it off of United Kingdom stuff including setting paper size as A4(!)
Which… I wish we used but unfortunately we don’t - we use the US paper system. this causes problems with stricter printers and printing and also just manufacturing stuff like PDFs
DDG does the same, and adds a switcher so you can change between your local language and English. That's great, because depending on the search you want, it may be better done on either language.
The Microsoft site uses your language header on their .Net documentation. That is very bad because no matter what your browser says you prefer, the only document with any reasonable quality is the English one. There is a language switcher that takes some 20 seconds to use (hurrah, javascript!) and they don't bother to save for your next access. That makes the site barely usable instead of completely useless.
What I don't get is, with the amount of information Google makes sure to collect about me, how does it not know that I prefer results not on my main language and verbatim search terms? That is even after I tell them that on their settings.
DDG also has local and global search that you can switch, without switching the language of the site (so if I do a search with !ddgde I get German results but the DDG interface is still in English). Kagi does the same thing with !reg (for regional)
They've finally added back the "Read in English" button they removed years ago for some dumb reason when they migrated the .NET docs to a new domain.
But then why doesn't Google just make it easier to set that setting? Honestly, when I'm in another country, I don't get too upset that Google results are in another language, I just get upset that I can't seem to find a simple way to change it.
Even then I'm probably giving Google too much of a pass, because they know everything about me. This happens even when I'm logged into Chrome. If they're able to target hyper-personalized ads to me, surely they know I'm an English speaker even when I'm in Mexico.
I am a monolingual English speaker. I visited Iceland, and as happens, Google started serving UIs in Icelandic even while I was logged in.
What was interesting was this continued for weeks after returning to my home country. There was no setting I could find to go back to English; I got good at the specific Icelandic keywords I needed to navigate the UI. Then without any ceremony, things suddenly reverted back to English.
Use browser and OS settings, always. Anything else is a mistake that will cost you users and business.
See https://www.apple.com/ch/ (you can also type apple.ch) for an example.
Apple is rarely a good example of giving user a choice.
It drove me crazy too before I saw the data. Geo-IP, while not awesome for exactly the scenario you are describing, is more predictable since it gives a set of baseline language/settings that are ‘right’ based on norms in the area, and people know how to navigate out of generally if they’re not the ‘baseline’ user there. (An English speaker in Japan pretty quickly needs to know how to switch languages or learn Japanese or they aren’t going to be able to even navigate the subway/buy tickets for instance!)
Many of the browser based settings get people stuck, especially since most large websites do the same geoip thing now.
It does make it awkward for folks not doing ‘the norm’ in their area, or who have an IP improperly categorized, but statistically they aren’t as common and they figure out how to handle it usually.
They have randomly served me the page in Russian, Turkish, Spanish, Portugese, Thai, German and Romanian. The only good thing is that the menu to change back to english is less hidden nowdays.
Yet to see it in my native Finnish. And all these without a VPN and from a domestic consumer ISP connection.
Guess they just have one of the buggiest locale detections in the world :)))
EDIT+: ...or maybe too many Chinese users leave their proxy/VPN on when using their site too
They figured out that "la naiba" is better than "perkele" :-p
It doesn't work for some services though but aside from signing in to google there's nothing else I can do.
I suspect they'll shut that down at some point too.
My suspicion is that people who actually write code related to this only speak a single language and only use sites in a single country.
That is truly maddening
Financial services and airlines are the worst offenders. SAS, Degiro, Amazon off the top of my head all do this.
Degiro has the added bonus of totally breaking under Google Translate so I went to the trouble of using a browser extension to rewrite the request for their localisation strings file to fetch the English version. I'm sure there are some legal disclaimers that are missing here and there but it works fine.
My theory is that yes, they don't lose business because of this so why fix it, but mostly because the most valuable country-markets in the world tend to be monolingual, and the US is the most profitable of them all. And everyone uses Google despite of this because well, what else?
If you're right and they're following a numbers-game, Google's reasoning could only make the tiniest bit of sense if they were a disruptive minor player facing stiff competition. As it stands though, however frustrated a native speaker with a misconfigured browser may become, they're not going to flock to an alternative service. Plus, I would argue that a user that is not technically competent enough to change their own browser's language preference is the user least likely to even know where to look for alternatives to Google's services.
This is all the worst considering that a user whose browser is configured for the wrong language only needs to change their settings once. However, a user who happens to physically be in the wrong place for their language does not have the luxury of fixing the problem, short of using a VPN or travelling to a location that Google has decided speaks their language.
What if it's a dark pattern to have more people signed in?
> any company that uses geo-IP location to serve me pages specific to that locale
A company should serve you content based on your geographic location. That's exactly what "localization" is for. E.g. the content should be adapted to local regulations and law whenever necessary and it makes total sense to do that based on the visitors physical location and geo-IP is often the best approximator you have for that. What should be adapted to user's choice is language.
To pick one of a myriad of examples, I often buy software, books, etc. via the web. I don't need sites to assume I want to pay in Euro just because my IP address in that moment happens to be associated with a European IP address block. Paying with my home currency is often much easier. I should not be forced to use a VPN just to avoid this silliness.
I understand where you are coming from, but using IP addresses to determine what "locale" to use is simply not a good practice, and not just for language determination.
That has nothing to with the choice of language. Unless you're using some antique HTTP server that doesn't support it, use Accept-Language.
If you have reasons for filtering content based on geographic location, and you absolutely can't trust the user to tell you, perhaps you shouldn't be serving content over HTTP; the IP address is a poor proxy for geographic location. It's perfectly posible to buy an IP block in one country, and have it routed to another.
> In an Arabic country you might not be allowed to serve images of women in swimwear (or other revealing images).
If you're running your HTTP server in a Moslem[0] country, perhaps you shouldn't be serving those images to anyone. But if not, then it's your user's responsibility to comply with local law.
If the diversity of content that the internet brings is unacceptable to some nation, they can either try to do without the internet (good luck with that!), or try some kind of filtering regime like the Chinese have set up.
> the applicable law is usually based on your physical location at that point in time
"Your", i.e. the site user's location. But if you're geared-up to charge VAT in the first place, then you're able to handle things like delivery addresses in EU countries. At any rate, if your site visitor fails to pay VAT on purchases, it's the user that has committed VAT fraud, not the server operator. So operators should simply ask users where they are, for those purposes.
[0] Not all Moslems are Arabs, and not all Arabs are Moslems.
That is exactly my point. Localization isn't about choice of language and thus the choice of words of GP was wrong. He was talking about language, translation or internationalization. Localization is about adapting your website to a different local target market. The whole premise is of course that the company wants to do business in that area and then they have to follow the local law.
My comment was a response to the GP stating he wants it to be the users choice to set their location, but a company doing business in different countries can't just allow the user to choose with which entity it wants to interact through their website (Netflix being a prime example).
I explicitly said Arabic and "might" as I only know it's a problem in some countries in that geographic region, which is probably due to religious reasons, but I explicitly didn't want to bind it to religion. The biggest Muslim country is afaik Indonesia and they are not nearly as strict in these regards except for maybe the Aceh region.
You shouldn't have to change this setting multiple times when you're in a country that speaks (well, writes, really) a different language than your computer is configured for. You would like the web to respect your configuration.
On the otherhand, the general public shouldn't have to change this setting multiple times when they're in a country that writes a different language than their computers are configured for. They would like the web to respect their location. Even though they imported a computer configured for English and don't know how to (or don't want to) configure the language options for the whole computer or the browser.
If language settings were easily and often set, they'd be respected more; but if there's a good chance people are more likely to want a local language than what the computer thinks they want, then ignoring the preferences is the right thing for most users. Even if it's infuriating for those it missed. When I had the fortune of working on multi-language sites, I would try to have each site have their own urls, but some places insisted on one url, multiple languages. Trying to make a reasonable initial language decision and then a language picker with a cookie was the best I could do.
Its not fun to be a North Indian to work in the South or vice versa- you may often be served a page in a script you cannot decipher fast enough or read at all.
How many of those are "misconfigured" and how many are set to en-US because that's the language they want for their computer.
A year or two later I’m in Tokyo and talk to a new Google product manager based there. I tell her it is insane that Google serves me Japanese pages on my English-configured PowerBook just because I am in Japan. It doesn’t matter that I read Japanese just fine… Making this determination purely based on my IP address is madness, I tell her.
Over two decades later, nothing has changed. Each year I spend several months abroad, and this is one of the most infuriating experiences I encounter. Google is the offender that frustrates me the most, but they are far from the only company to engage in this abhorrent practice. I am tempted to create an Internationalization Wall of Shame just to embarrass the companies that do this. (Not that I expect them to care.)
Why do they do this? My theory has always been that in any given country, there are far more native speakers with misconfigured computing environments than there are visitors and nomadic folks like me. So it’s merely a numbers game: I may be frustrated, but at least Google and other companies aren’t losing business when folks with misconfigured computers close the tab because they got a page served to them in, say, English instead of their native language.
I can’t say for certain whether this is the actual reason for this behavior. What I can say, however, is that I absolutely loathe this practice and actively avoid doing business with any company that uses geo-IP location to serve me pages specific to that locale. If this frustrates you as well, be sure to vote with your feet!