I really wish for a language setting that says: If the original text is in one of the following languages, use the original text. I might not be equally fluent in all of those languages, but reading the original text is better than reading a translation most of the time.
MacOS has this feature under Settings -> General -> Language & Region -> Preferred Languages. Here you can have an ordered list of languages you wish apps and websites (I _think_ only works for Safari) to use. I don't know how widespread this is in other OS'es or browsers.
That's just the standard Accept-Language header, not unique to Safari or macOS at all. It's up to the server to interpret and respond to the header, and they mostly don't do what gp wants, i.e. they usually serve the translated language with a higher q rather than the original language even if it's in the list (and it's mostly ignored anyway in favor of geoip/manual region/language picker).
It is not the accept-languages header - it affects the accept-languages header. Like the parent said, it is also used for apps (which includes your browser's UI).
Unfortunately, that just specifies which languages you prefer, regardless of what the original language is.
I speak Dutch and English, but have English set as my preferred language, because most of the time that multiple languages are available, that is the original language. However, sometimes I'll be visiting a Dutch site that has a (usually badly-)translated English version available, and I'd rather get the Dutch version.
This is expressed as the quality parameter. To make the system GP proposed work atop HTTP content-negotiation, a server operator should assign a very small number to the automatically translated content.
(Also note that I wasn't talking about automatically translated content necessarily. Manually translated content still often is of worse quality than the original language.)
It is; but also there is a server counter-part with its own quality weights. If that does not make sense, play with the code in http://p3rl.org/HTTP::Negotiate and read the HTTP spec.
You could probably also trick websites into serving the original language by setting a language they probably don't support (how many websites have a version available in Akkadian anyway?) but you'd need to pick something that the Google Translate widget found on many websites doesn't pick up and try to use.
No, because then it will probably serve it in the original language regardless of the languages I speak. If the original language is French, I'd still prefer to have it in English.
(To be clear, with how widespread English is, and how often Dutch sites are Dutch-only, this is a minor issue - having English, then Dutch as my preference is usually good enough.)
Yeah, this is has become of pet peeve of mine since moving to Spain. US sites that automatically redirect me to their Spanish site (which often doesn't have the actual article the original link pointed to!)
It does not "fix" that at all, and breaks so many other things. I don't wanna see US/UK/Australian prices just because I happen to live in Spain but prefer English when browsing the web (literally same boat as parent).
I agree that it's most stupid and most annoying kind of localizing.
I search for some specific product (or other information), get a link to an English version of the page (and perhaps the only one). But when I follow the link I get redirected to my language version of the site, most often its portal page. Sometimes because the language specific site does not have a page for the thing I searched, but most often because the site is lazy. And then I have to search again but using the site tools instead of my search engine of choice.
Yeah I've worked with geolocation databases in the past and they're essentially just hot air. It's wild that even google can't guess my location anywhere close to home. And I live in a big german city, it wouldn't be that difficult to be right. But they've actually never been right about my location. Sketchy is a fitting description.
> You don’t override screen resolution or color scheme with your own guess
They absolutely do lol.
Like it or not, people like you are outnumbered by people who set their Accept-Language header wrong and don't know how to fix it. Those people probably buy more too (or at least buy more that shows up in tracking, since you sound like the kind of person who disables cookies etc. too).
Actually, yes. Google and Facebook invests in translation significantly more than Microsoft in languages in Africa and Asia (to the point that you cannot set Windows do not have that language in question), for example, the various non-colonial languages in the African continent. In those countries, the computer is set to English/French because not of practicality but of significantly broken/no translation by Microsoft.
This doesn't explain why Google then also uses their crappy heuristics in countries whose languages are well supported by all major operating systems and browsers.
Windows + Edge populates it for me. I consider it a form of tracking so I definitely will look into it how to override it, this hasn't happened yet tho.
But my system language is English. Closest english speaking country is 2000+ km away.
And you know what? I didn't pay so much attention to what English I'm selecting so part of my devices are set to UK english and part to US english. It's all English to me, just don't translate my File menu!
Then create some status bar (or even a popup if necessary) that informs the user about their Accept-Language header-IP address mismatch (in terms understandable to a non-technical user), offering the option to choose either page.
My biggest annoyance is with Google. They know who I am, they know I am traveling, they know my language preferences (English) and yet I still get language based on my location on certain pages.
I let you track me Google, please use it for some good UX and not just advertising.
What incentives does Google have to improve UX in this way? I absolutely agree that it should be the case, but the people for whom it matters are (1) completely insignificant wrt to the whole user base and (2) mostly care about tracking and try to circumvent it.
>(1) completely insignificant wrt to the whole user base and
At any one time, there's got to be tens of millions of people accessing Google from a country which has a primary language unknown to the traveller. Even if this number is insignificant compared to Google's full user base, the cost for Google to service 20-30mn people with a feature is presumably lower than their annual ad revenues across 20-30mn people.
There are 700+ million people living in Europe. The countries are tiny, most have bunch of official languages. The fix would be to use users selected language and not to flip flop it based on location. IP based location guessing doesn’t work even down to right country in here.
That is not an incentive. There is nothing in to for Google.
It is of course useful for those 700+million, but they are not customers of Google, they users/the product. So long as you won't go elsewhere (in mass) you don't matter.
Indeed, somehow Google is the worst offender with this.
Lately they've decided that auto translating the local language into English in Maps reviews is the wrong thing to do. They translate every other language into English but somehow since I live in this place I must speak the local language too, so I don't need that in English.
Ditto for search results. Surely you want Wikipedia in the local language! I mean you've been there for so long! You search for things in the local language, surely that's a sign of your preference and not the fact that searching for things locally requires use of the local language.
This also applies to so much other "we must make our software so smart and guess all your preferences". Google fails so consistently at this I cannot understand why they persist other than some sort of misplaced corporate self regard.
Still applies. I don't want to have google forcing the "local" language on me even in the country I live in (which is also the country on my passport).
He told me that for efficiency, they had different stages in the content rendering and that the main page structure didn't have your user information yet. That's rubbish IMHO because the accept language header should be readily available in that phase.
I've seen similar dysfunctions in other big orgs where a feature or bugfix would need to cross team boundaries and the outcome inhabits zones of vaguely defined responsibility.
The guy you argued with sounds like they were semi-justifying this with the typical "noogler" rose colored glasses.
Yeah it's amazing that Google is the worst offender.
I think this is because half of Google live their entire career in California, so they don't know about other languages, units, time zones at all.
It's weird, because they employ SO many foreigners, bringing them to California. But somehow upon arrival they all get memory wiped about the existence of anything outside the bay area.
Other companies do this right. Google is user hostile.
No. I will NEVER navigate by bike, foot, or public transport in these strange America-only units.
When I was in Romania for my IELTS, I could not use Google Maps. Despite my Google account specifying my preferred languages as English, Ukrainian, Russian in that order and my Accept Language header set only to English, that was not enough to not discount those preferences as a configuration error and serve me Romanian.
Using Google search, which luckily did not decide to show me "local" results to an English query like it often does home, I found a support thread suggesting I set my Accept Language to have something other than English as a second language. Lo and behold, the page decided to now respect it.
Indeed. Catalan speakers have Spanish forced down their throat no matter if Spanish has never been associated to the Google account in any way, nor in the system or browser language preferences.
In my case, I live in the United States, but Google is determined to serve me Spanish results even for Catalan-related queries. E.g. preferring the Spanish Wikipedia. The search engine's behavior has had ups and downs over the years, but it has never been great.
This is very much a problem for my children, who don't understand Spanish, as well as for the Catalan-speaking regions of the world that are not in Spain, including Andorra.
In my experience, Gemini easily flags any Catalan content as unsafe and prevents the conversation from continuing. Even for prompts like "summarize this article". This may have improved lately, but still.
Google used to be an example in sensitivity to the world's diversity, being a responsible major player. Way back. Now, although I applaud some efforts multiple teams continue making, it is obvious this is no longer a priority.
My worst experience was that after arriving in a new country the Play store didn't show local apps because my Google account was assigned to the old country. And changing the country wasn't easy and meant abandoning the old country and it's apps. Since I travel a bit back and forth I ended up buying a second phone and creating an account for the new country.
You solve it the best way to fit your case I guess. On android I created a set of alternative accounts that each belong to a different country.
All accounts can be active at the same time on the same phone, there is a dropdown to switch in the Store app, and that works even with a work profile on the side. I've yet to see real downsides, except for course remembering which account is on which country and manually switching.
This is indeed extremely annoying and I never understood why so many apps are configured to only be available in specific countries. Like what at all do they stand to gain doing this?
Google will then go on to complain about users installing APKs from shady sources but this practice pushes users to do so. I'm sure a decent amount of users ended up with malware on their phones just because they wanted to install an app that wasn't available in their listed country.
Its strange that Google knows I live in the UK and speak English. When I'm signed in to a TV in a hotel room in Spain watching English YouTube videos it then shows me a Spanish advert. Just feels really silly when I don't understand it and they know full well that I don't understand it - still they can charge the advertisers.
That's so annoying, every time I'm on a new device/browser, Google and all their services start in Hebrew. Even though I'm signed in and have changed it to English a million times already. It's not that I can't read it, I'd just rather have everything in a universal language rather than a translation
About a decade ago Google decided that all maps in Finland should have the street names in Swedish.
Which is kinda valid, in the southern and south-western parts this is done because there is a significant Swedish-speaking minority so most cities and streets have names in both languages.
But at the time I lived in central Finland, where the streets DIDN'T have official Swedish names, they just ... translated them. Which was super fun for navigating.
And also make it easy on the site to change languages. Just because my OS is in US English, doesn't mean that I don't prefer certain sites to be in other languages when I choose to. Many of us are multilingual.
That should not be the business of the site, but of the browser. It is precisely what Accept-Language is for. The site should respect the header, allowing circumvention should be a very low accessibility priority.
The site should respect explicit user actions. A get request to a /en/ domain, or a button click to a language icon should result changing to that language. Respecting implicit preferences that are more likely than not be just plain wrong anyways should be a very low priority, ideally shouldn't be done at all.
This. Related: if I had a penny for every time I needed a VPN just to load the payment method selection screen (but not for the actual payment, it's not geolocked) just to be able to pay somewhere, I'd get a lot of products for free by now...
Why not let germans select iDeal and dutch users Giropay? They'll not click it if it's not useful for them. Adjusting the sort for what's most commonly used makes sense, but why actively thwart users from paying by geolocking payment methods by IP address...
Because then companies would have to charge all users the same price for the exact same service.
Charging customers from countries with higher average purchasing power more and hiding the fact behind "charging people in the local currency for convenience" is much more profitable!
I'm talking about those online stores that don't have a (customer hostile) thought out price for every locale, but they have some auto conversion.
When price is set to $9.99 which works out to 47.89287237634 in your local currency. Although it would work out to 45.89327782 if you used your bank's conversion instead of the "helpful" service.
In those cases i don't think the seller makes any extra money, they get their $9.99 minus payment processor's fees. They just think they're helpful but make you spend more for no good reason.
Hadnt thought of that, but the price is the same between the two countries I had in mind. Indeed, if there are measures in place to keep products affordable for less lucky/affluent regions, by all means keep those. Just show them all available payment methods, irrespective of the adjusted price
> Your payment provider's automatic conversion is most likely more predatory than my bank's so I don't want to use it.
As of a few days ago, Stripe is forcing all their partners to offer their customers the predatory currency conversion. There is no way to opt out, except switching to another payment provider with their own problems.
Don't guess my anything. If you're not sure what I want, ask, or at best do nothing. You don't actually know what I want, and every time you decide you think you do, you make everything worse, not better.
> Every browser sends an Accept-Language header. It tells you what language the user prefers, not based on location, not based on IP, based on their OS or browser config. And yes, users can tweak it if they care enough.
This is also a broken assumption.
First, Accept-Language is an ordered list, and most daily-multilingual people don't have an absolute order of preference, and more a topical list of preferences.
If I read an English news site that has a translated French version, it doesn't matter if I'm most proficient in French, I'll want the English version.
Then, as an affect of the first point, users will specify their most practical language, not some actual preference. For instance local non-English sites tend to do less shenanigans than international English ones, so having one's language set as English only will force English display for the former, with few impact on most other sites.
A French site ignoring all preferences and just pushing the French version by default actually helps in that case.
If anything, I just wish site owners stopped trying to be cute or clever and just had a very obvious and quick interface to switch to other versions. Wikipedia does it decently well for instance.
> Then, as an affect of the first point, users will specify their most practical language, not some actual preference.
Where does this assumption come from? Given the fact that many (most? almost all?) sites don't honor the Accept-Language header, I doubt that there's much game theory going on in users' head when deciding this configuration.
They're right. Try to find a Dutch IT person with a laptop not set to English. Only a small fraction will realise you can set more than one language and put Dutch as a second, even though many struggle beyond basic reading comprehension in English. They're not picking it because they're just as good, much less better, at English compared to Dutch
We definitely pick languages that work as opposed to languages that we speak. Setting it to Dutch is just worse: UX doesn't fit, english search results wouldn't show up (way fewer results/content/info), and translations often don't make sense (imagine a button called "you shut it" on a modal window, it's a literal translation of one interpretation of the string "close it" but you'll be confused as to what that button will do)
The language set defaults to the language set in the OS, which is usually the preferred language for most users.
You have people working in IT who set their language to English for easier troubleshooting (i.e. not needing to Google error codes), but they're a small minority.
Anyone handling more than one language daily will be doing an explicit choice, and I wouldn't say they're a minority.
If your native tongue is Spanish but you live in the US for instance, the "preferred" language in your browser has IMHO a higher chance of being English. Same if you live in India probably.
I'd assume most WordPress based sites handling multiple locales will switch based on the Accept-Language ? Same if they let a framework handle the switch instead of a home-baked solution.
Even for auto-translated content, I wouldn't be surprised if it was off-the-shelf plugins that handle the switch.
All in all, I think it takes more effort to ignore the Accept-Language header. That won't prevent sites from tweaking it or doing their own cooking, but it kinda requires intent.
> First, Accept-Language is an ordered list, and most daily-multilingual people don't have an absolute order of preference, and more a topical list of preferences.
IMO there is a lot of improvements that can be made by both the browser and websites:
Websites should probably allow users to override the browser-requested language. But browsers should also allow users to choose between "Site default", "Request system default language", "Request English", "Request Chinese", "Request Spanish", etc. on a per site basis.
Most optimally however: sites should expose a list of supported languages, maybe in the manifest.json: https://developer.mozilla.org/en-US/docs/Web/Progressive_web... Format would be something like: `Map<iso639Code: string, Tuple<translationQuality: float, comments: string>>`
Language selection should be done on the client side, not on the server.
Fundamentally the issue for me is, this behavior can't be automated in an elegant way.
Having priorities and weight and language lists in the manifest help for negociation, but at the core of it, the user will want to choose language based on context and content.
> Language selection should be done on the client side, not on the server.
Yes.
Using a site specific list on the client side could also do it (let's say I always want Facebook in a language and Google in another, Linkedin in yet another etc.). It still will be pretty cumbersome, probably needs an auto-save and sync of the preferences, and still hits problematic cases, but it would be the most pragmatic solution.
The worst instance of it is IMHO the way Google Maps work, changing language based on the country gives the best display (local names in the proper writing, no internationalization), I wish there was an easier way than screwing with the Google account preferences. As you point out, having clients able to unambiguously request a specific version at each requests would gives us so many more options.
That's IMO the original sin: no automatic selection will cover 99% of use cases, that in itself it to me a fantasy that isn't worth pursuing.
People are complicated and having simple heuristics to predict what more than half of them want is not feasible at our level of technology.
Sure any single person will have somewhat simple rules to decide what languages they want, you could come up with simple rules for the people in your life. But you're not trying to solve it for a specific group of people. The target is 8 billion people, most of which we have no idea what their life is.
> Having priorities and weight and language lists in the manifest help for negociation, but at the core of it, the user will want to choose language based on context and content.
Yup, agreed. I highly doubt most websites even look at those weights in the Accept-Language header anyways.
Having a list of supported langs in the manifest costs nothing. Lazy-load the manifest when the user goes to use the language selection dropdown, or when the response from the server is in a different language than the one requested in Accept-Language (check Content-Language or html `lang` attr).
No, please, don't force a language list. I don't have a "ranking of the languages I want to read". I want the original language of the content, with a quick button to switch.
> If I read an English news site that has a translated French version, it doesn't matter if I'm most proficient in French, I'll want the English version.
The solution there is not to abandon the very useful Accept-Language header, but to never offer half-baked translations. Is your website multilingual? Fine, but only offer fully translated and verified translation sets. It's OK to have your UI and your own content translated in a few languages — for a company that may make sense depending on their target clientele — but you'll have to maintain all of these and keep them in sync.
However, user content is off-limits. No automatic translations unless you only offer those under a button to be helpful (like 'Spanish detected, click to show an automatic translation into English'), but really, leave that to the user's browser.
Use Accept-Language to pick a language, and then offer me a way to switch in addition to that. That's all there is to it.
> Wikipedia does it decently well for instance.
Wikipedia doesn't do that. Each language is its own instance, where content may be ported to by translating it (or parts of it), but outside of the Mediawiki UI texts, it is not a translation of the same content. The Dutch version of the lemma 'Language' is a different article in a different language with some overlap. There is no claim made that it is the same article in Dutch. It is hosted on a different sub-domain and path on purpose.
We can look at the reaction from smaller youtubers as auto-dub rolled out. Most are sympathetic to the quality issues but are seeing it as either a "good enough" or at least a "better than nothing" feature that helps them expand their audience with no visible cost on their side.
Or official government sites that have explicitely disclosed AI translations and didn't bother passing it through a regular translator.
This situation just won't get better. Except perhaps the day AI is actually intelligent and we have human being level translators running on cloud servers.
> Wikipedia
Yes, those are not translations, but in that specific case they also don't need to: the quality of the article will vary depending on the editor, but there's no "original" article, so nothing to translate from IMHO.
> Fine, but only offer fully translated and verified translation sets
No, I do not want the translation at all, unless I say so. Really. Even if it is the best translation in the world. I want and need to choose the language I will read or watching something in.
> First, Accept-Language is an ordered list, and most daily-multilingual people don't have an absolute order of preference, and more a topical list of preferences.
No, it's a partially ordered list.
> If I read an English news site that has a translated French version, it doesn't matter if I'm most proficient in French, I'll want the English version.
I have told the story here before, but I built a neat little system to parse Accept-Language weighing the users priorities and using the closest thing we have on offer to the users preferences. As an example, we have a Brazilian Portuguese translation but not Portugal Portuguese, so we would offer the prior to users requesting the latter for instance unless they had a lower priority but more exact match.
From my technical standpoint it worked really well and the code was very slick. It was a lot of fun to build.
From a user standpoint most of our users really just wanted English regardless of their Accept-Language header. They had the option to change it in the footer but this apparently wasn't obvious enough.
Yes! I still want to default to accept-language, but asking is key. What is your pattern for giving the user an option? I like this article in that it rejects icons, but I don’t like how they arrive at one language for multiple regions https://usersnap.com/blog/design-language-switch/
We literally just have a box that pops up with "<language> (<region>)" in each of the native languages. It gets saved to a long lived cookie rather than the user's account for some business reasons.
You ask, as in, whenever I visit the site without having your cookies stored, I'll get a language selector wall first?
I run into those regularly and it's always a struggle to know how to stay on the damn page I clicked on: will the "continue" button use the preselected value or will it dismiss the pop-up and continue on the current page?If the former, is the preselected value the page I'm on or a different language? Can I guess which locale I'm on to select that and dismiss the pop-up then? Can I inspect-element→delete this modal and just sidestep the whole problem? Even just a small close button is a luxury on these language walls...
95 out of 100 times, I'm fine with whatever language I clicked on, and if I want your German version for locale-adjusted shipping info or payment options or whatnot, I'll look for a language selector on the top right or, alternatively, in the page footer. If it's in one of those two places, I'd be much happier about a web without JavaScript-based pop-ups constantly
We're a paid SaaS so I don't think it's as much of an annoyance to be asked once per browser.
It's just a separate page you hit after signing in if we don't have your preference. You click on the language you want and you are redirected to the dashboard.
The option to change it still exists in the footer.
Okay, must say that does sound like a very acceptable flow. You'll have the user logged in at that point so can store it and never need to ask again. Was expecting you built this for regular websites, my bad!
Timely. I’m working on this right now for a product and have everything in place using the accept-language header and then adding a url param.
I’m currently agonizing about how to let the user change their language, because I want to respect locale as well (es-MX vs es-ES for example). And I haven’t found a good UX pattern for changing language+locale. I’ll likely just implement a big list that the user can select, and have the current language be a link that they can click to change via a modal.
As someone who lives in one of those locations mentioned in the article: split out locale and language into different settings. Because they are not the same thing. This article explains that nicely. [1]
You want your users to be able to change their location (and, therefore, locale) and their language independently. The Accept-Language header could be used as a sentinel for language. Then again, I wouldn't outright rely on geoIP to set the locale which is an umbrella for regional differing variables like timezone, date formatting, currency, VAT / Taxes,...
I think it's okay to have your content served, by default, in a language that reflects either the majority of your target audience; or the culture / place you're based in. Changing the locale / language should follow a clear UI pattern e.g. a language switcher & locale switcher in the header; or a clear navigational aid pointing to a context menu. That's how Hetzner works, for instance. Another example is Deliveroo.
Thanks for the advice! I wasn’t planning on using geoIP at all for several reasons - the main two being inaccuracies AND that I’d need to use a paid 3rd party.
I also hate the youtube "feature" that translates the titles of videos to your setting's language. This is so annoying. I can understand English and don't need these automatic translations.
Using Brave on iOS I haven't encountered it yet. Perhaps it strips some information? But with the official YT app I have, and it was both fascinating and annoying.
My computer is set to English even though I'm German, and sometimes Youtube will treat me to this really uncanny machine voice with really weird phrases because it auto-translated some German video or advert.
Lidl is worth it, ja!
> Why is it so hard to just add something as a setting/feature and offer it to people without forcing it on the user?
Office politics. Google is famously "performance-driven", so the manager in charge of that feature needs usage metrics to be high for the sake of their own career.
That's a funny idea—if the KPI was boosting adoption of a feature and the PM just made that feature the default and suddenly adoption was through the roof.
Same here. My native tongue is German, I live in Switzerland, but my settings on all devices are English.
I do this on purpose, because I find everything is more searchable. I don't even know any German terms for most technical things I might search or look for. So even if the automatic translations were good, which they aren't, this would be a non-feature.
My browser already tells them what my preferred language is. Just use it.
Living in Zurich (German part of Switzerland for those who don't know), Windows 10 in English, the built-in Microsoft Store used to offer content in... French.
Now it's a mix of German and English, e.g. 1 heading is "Spiele-Bestseller", and the next is "Best selling apps". And prices displayed as "28,00 CHF" (correct would be to use the decimal point).
So much this. I suspect the idea that a person speaks more than one language is absent in US silicon valley. Else I can't explain why youtube only lets you set one language. Heck, even google allows you to configure all spoken languages in your account, the very same google account you use for youtube. Yet youtube ignores it and has its own settings.
I think it's more a matter of "why would they have their system language set to X if they speak Y? If they want Y, they should just set their system language to Y!"
It's the idea that the user has a preference for something, and it applies always and everywhere, even when it's not applicable.
It should be absolutely clear, when i speak English and German, do not auto-translate any video title in those languages to the other. You wouldn't believe how bad the translations are, and how unwanted by me (the user). Worse when you speak a third or fourth language, and tend to watch videos. It gets messy.
It was more of an example in how they pick up on _some_ signal about a users language preference and then arrogantly assume they're correct in their decision, and that it's the user's fault if they assumed wrong.
This is actually something that foreigners working at Big Tech US companies should be able to understand very well, because English as a system language is often how software developers set things up for themselves regardless of their native language.
But they don't make those decisions. It's a UX thing, which means that in practice whoever is in charge of "driving up the numbers" is going to be making the decision; the engineers just get to cuss while implementing it.
I think the issue is not speaking more than one language, but not preferring your native language over the original content's language. This is a very American-English-centric view of the world, where content is made for your language and your demographic. Consumption from outside the US is the exception.
In the rest of the world, and especially in Europe, this is the norm, not the exception. On one hand there is the prevalence of US English media (hello hollywood), US english literature (esp. in tech); and on the other hand cross-consumption between EU countries is much more common.
Oh, and the content ends up being in English too, because that's how to reach many people. We don't want those to be translated, because we don't want a double translation. This is something that the US / Silicon Valley mind cannot comprehend.
Now Reddit results are translated as well in Google, Kagi, so you think you have found a relevant response in your language, but it's just a machine translation from an English post.
It's interesting that the quality is so low. You can do very good translations for many languages today even with fairly cheap LMs, but for some reason (cost?) automated translation online seems to be still mostly at Google Translate level.
Leads to foreign-language posts on English-speaking small subreddits as well. I see plenty of Portugese, Spanish, Italian and German in communities that barely have enough traffic to debate in a single language.
Thanks for the link, good to know. Gives me a fuzzy feeling to pay for a search engine whose devs you can actually interact with and are actually working on improving their product.
Hear! Hear! It enrages me. They also automatically turn the subtitles ON, making you constantly have to disable them. There is no way for multilingual users to add a list of the languages they understand, which is an insane limitation that's been driving me crazy for years at this point. Wtf are they even working on at youtube's HQ? Making video thumbnails larger still?
I don't even get the point of that. If I need a translation of the title, I won't be able to watch the video anyways. At least ot makes some sense with the horribly auto-translated videos now, but they had the title translation for a long time while the video was still the original language.
I get you and normally wouldn't either. I was a little impressed when I could switch to like 10 diff languages on the fly. As a foreign language learner seems like it could be pretty helpful.
It's probably most useful for utility or news content. Not 'high effort videos' about an interesting topic. I'm imagining you find a video in another language that fixes a problem you have and can switch to your language to watch.
I sometime watch videos in English with the automatic subtitles. Sometimes I can't understand a few words and the subtitles help me. Most of the time I watch them without subtitles, and rewind the video a few seconds to rewatch a short part with the subtitles enabled.
Not only the titles, but also the audio track. There's a few youtubers I regularly watch who are trying to branch out into some additional languages by providing fan-made translated audio tracks, and english is sometimes one of those. Every single time I watch one of those videos, I have to manually set the language back to the original because often the translations lose some of the word play or hidden meaning in the original language. Often it also means I need to rewind the video because it started playing before all the controls have loaded (because youtube hates FF with youtube-related extensions) and I could swap the language track back.
One of the sister replies linked to an extension to help with that, which I'm going to give a try, but it's annoying that there's not a simple toggle in the youtube settings to tell it to always use the original language. On the rare occasion that I want to use the translated audio track, I can do _that_ on my own; I speak enough languages that this is a very rare occasion with the type of content I watch.
This isn't even something I can understand as them being hostile to ad blocking or wanting to push ads. This is a 'convenience' feature that is just poorly implemented. But I'm sure there's some PM that got a pat on the back for it.
It is not just that these translations are not needed, they are often - in my case German - of a low quality, contain errors and lose information which the original language contained. And the roboter voices loses all the interesting modulations of the original voice. Even a Fireship video sounds terrible when translated.
I'm sure YouTube's algorithm rewards people for using this feature and making their "content accessible", but if you serve me up an ugly machine translated Norwegian title rather than the English one I could read just fine, that's from my experience a signal that your YouTube channel is low quality algorithm-chasing garbage, so I click "never recommend this channel".
What a catastrophe. You punish the wrong person, and even worse, a channel owner will not even receive that signal! The vast majority of channel owners with English content is not aware what's going on. A friendly e-mail to the channel owner explaining the problem and asking to manually disable auto-translation is much more likely to achieve what you want.
If you want to get rid of auto-translation on a systematic level, provide feedback to the operators of Youtube through their official communication.
Youtube really doesn't make it obvious that a title got auto-translated. I now realize that I've seen this happen before, with a video that had a different title on my TV than on my computer, but up until this very second I thought it was my TV's fault.
Even being aware of this - how do I know that it's an auto-translation, rather than someone making AI slop in my native language, without watching the video?
So what you're saying: Please complain through proper channels and hope they accept your input?
Or should he just keep using the signals he gets and immediately clean up his feed?
I actually see this as a feature. YouTube recommends a lot of garbage. I suggested that they improved my feed but they implemented this signal instead. I use the exactly this method to weed out a lot of content I do not care for.
You cannot tell the 500 pound gorilla anything. I prefer my videos without subtitles. I have that set as a preference. Yet when chromecasting it is common for the subtitles to spontaneously turn on. And has done so for a long time.
English is not my first language and my first language is not widely used. Hence I am not used to dubbed movies/programming and I am used to seeing subtitles.
If a native english speaker could understand the horror show that the machine generated subtitles are. If you are used to subtitles they are extremely hard to ignore. You will then read and get the understanding (often hilariously wrong) before the audio catches up and you might end up rather confused.
I can understand an American might have a hard time watching a subbed German movie. Thats natural because it is not common. But when you grew up with subtitles it is actually effortless. Except when they are poor. Then it becomes worse because of the cognitive load of 2 languages and the effort to figure out what is correct.
Dear english only speakers: Translation is hard. A poor translation is worse that no translation as it obfuscates the message. AI is not there yet at all. Maybe impressive but often not helpful or plain and simply distorts the real message.
What I wanted to transport is the following idea: attacking a channel owner (who is most likely innocent and did nothing wrong) with a metaphoric sledge-hammer when a more gentle and precise tool will do is not a great way to conduct oneself in society. vintermann and clan have a feed now without content that bothers them, but at the cost of lowering the channel owner's reputation in the eyes of the operators of Youtube, with the effect of slashing recommendations for the videos of the channel owner at large and his earnings. That's not nice, we should be considerate of the consequence of our actions. Does this make sense, do you understand this perspective?
This behaviour rankles me, I think is on the same level as the misuse of the feature "report this as spam (to some upstream entity/3rd party)" for e-mail messages that are not actually spam.
Attacking? By saying "don't recommend this", I'm just saying I want to give someone else the chance to be seen, rather than the ones who will make their stuff objectively worse in order to juice their stats for the algorithm.
I'm sure my "don't recommend this" clicks don't in any way make up for Google's promotion of channels that "make their content accessible", because it doesn't even stop them from recommending me more machine-translated videos.
They base the feed on user input. The feed is then (supposedly) adjusted to what I like.
What I call a signal you call an attack.
I signal that I do not like Minecraft videos. But I do not attack them.
Your anger is misdirected. You should be mad at YouTube because they do not seem to understand that there can be multiple signals at once.
The chances that I click on a Minecraft video is low. Autotranslated even lower.
So we differ strongly in opinion on how the platform should work. I read your "attack" argument as I should write to the Minecraft creators and tell them their content would be better if they played Minesweeper instead.
I do not punish anyone. I just pursue a clean and (for me) high quality feed.
If you are up in arms that I punish your channel that is another signal that I am probably not your target audience.
When dealing with audiences at scale you need to listen to these signals as handling personal opinions in mails from the discerning viewer is not feasible.
The channel I'm interested in would be of great interest to English speakers. There are only a few people brave/stupid enough to travel to dangerous places (Ukraine near the front) to do a documentary. I cannot blame the author for turning on the translate, it likely overall expands his reach and is a good thing for those who are not interested in his native language. However I'm trying to learn his native language and getting dropped to English out of my control is not helpful to me.
The vast majority of videos are not translated into borked machine-Norwegian, so if this isn't something you opt in to, it's something everyone opts out of (I doubt it).
> A friendly e-mail to the channel owner explaining the problem and asking to manually disable auto-translation is much more likely to achieve what you want.
No it isn't, because I see what kinds of channels do this, over and over again. They're very clearly publishers who don't care that they make something objectively worse as long as the algorithm rewards them for it.
> If you want to get rid of auto-translation on a systematic level, provide feedback to the operators of Youtube through their official communication.
Ha, as if they ever read that. Probably more Google employees will read this comment than will ever read any of my (many) "please stop translating things without asking, I know where to find machine translation if I need it, doing it without asking that means I have to translate back from broken Norwegian into English in order to understand what the hell you were trying to say" feedback reports.
While i appreciate the effort that Mark Rober puts in his Youtube videos making them multilanguage, i absolutely hate that native voice. It's one of the few Youtube shorts i have to play twice because of it.
Gosh this annoys me so much. I am native Portuguese speaker but have all my settings in English. It always tries to auto-dub Portuguese content into English, how do I turn that off?
What I don't get is how the feature works. I see it for veeery few videos and those are usually highly profitable clickbait and/or big budget productions, so my assumption has been this is actually something the uploader has to enable or even fill out. My language is very "small", so it makes sense that only the broadly-popuar and highly-profitable would be worth translating the titles for.
Unfortunately, all the translations are machine-translated garbage and there is no setting to turn this off as a viewer, so it's just incredibly annoying.
It's even worse for videos with "official" dubs. I have been jump scared by German and French dubs on certain videos recently, I distinctly remember MrBeast, Mark Rober and Nick DiGiovanni. I have set my language to English and my Region to US (worldwide) I don't know what gave YT the idea to preselect these dubs for me, I have seldomly even watched a video that is not English.
Jesus H Christ, I once a month google to see if there's a proper way of stopping this (You can block this with TamperMonkey)
2 things that absolutely kill my experience,
1. Messing up with titles, specially if the contents of the video are still in a different language, Which Kurzgesagt will I get today? Only YouTube knows, this is annoying if I know the youtuber could use a different language in the title to make a joke
2. Messing up with the default audio tracks, I don't mind if the YouTuber has a dubbed track, that's awesome for getting more exposure, but I already know and expect a specific voice and it's extremely jarring
> I can understand English and don't need these automatic translations
I think it is far worse than that:
1. If I don't understand a language, probably that video is not for me. Most videos targeted for international audience are in English, or at least the author translated it by theirself.
2. Titles are small sentences, and they don't have enough context to be translated. Once I saw a video called something like "Vamos assistir uma conexão com o passado", which in Portuguese means "Let's watch a connection to the past". I needed to de-translate it in my brain to understand that the original title was "Let's play A Link to the Past"
3. Online resources are a great way to exercise a second language. So, please, don't underestimate my capabilities. At least let me try to read in the original language by myself, if I need the translation I how to use Google Translate or a dictionary.
I reckon that this feature makes the access to online content more democratic, it's ok. But at least let me disable that since it makes the experience worse
There's a video that Youtube keeps sending me with a translated title "O segredo das lavadouras" (what translates to "the secret of washing machines") that is about picking screw washers...
But the real problem is when it decides to translate the titles of some perfectly watchable videos in English into something that uses the Cyrillic alphabet, what has no relation to my accepted languages, and is only used half-way across the world from where I am.
Worse is the auto-dubbing in some channels. Which cannot be disabled. That has resulted in me stopping to watch a channel completely due to the inability to select the original language (youtube mobile website).
By the by, one quirk of poor language handling that I think it probably harming YouTube is advert language.
Every one of my subscriptions is an English language channel, and my language choice on all Google properties (where possible) including YouTube is English. It's not hard to judge that English is my favoured language.
And yet... every video advert I receive when travelling is served in the local country's language. It doesn't especially bother me, since I actively avoid listening to adverts (and indeed, now pay for Premium lite to avoid them almost altogether) but it's a weird not-so-edge case that I'd have thought a company as large as Google might have addressed already. They've absolutely got the tech to deliver adverts in any language. (And it could be powerful: imagine receiving adverts for local businesses in your native language while on holiday.)
Do you have en-US or en-GB as an alternate, lower-priority language?
If an English variant is in your Accept-Lang: headers, I'd hope YT wouldn't auto-translate English titles.
The other thing that Google might properly use is account-specific language settings. But if they're using GeoIP as has been suggested, I agree they're doing it wrong.
I mean, I can deal with the titles, but recently it has been auto selecting machine translated sound tracks, without any way to disable it. And they're bad, like maybe one level above 2010 phone TTS system
And most of the times, the translation misses a core part of the title, making it harder or even impossible to understand. A recent example is "I booted windows from Google Drive (part 2)", which got translated to "inicié ventanas de Google Drive", which misses the whole point. Luckily for me, the miniature said what the video was about, and I could understand and watch it.
About the translation, sure, "boot" ≈ "iniciar", "window" = "ventana", but for (microsoft) windows, and other names in foreign languages, the same name must be kept.
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)
Every couple months, Facebook's web interface glitches out and displays the geolocation-based language instead of my preferred language in parts of the UI.
I don't know how that happens. Like, do individual teams within Meta have to re-learn that users in their own system have a language preference? (Not even talking about Accept-Language, it's a Facebook user setting.)
I live in Finland where they have two native languages: Finnish & Swedish. In a lot of places you'll see both the Finnish & Swedish place name on road signs. Without getting into politics, it's a good assumption to assume that Finnish is the mother-tongue of most of the population - with some areas having Swedish as their native language but also perfectly capable of speaking Finnish fluently.
I have my phone's language set to English as a native English speaker. Google maps reads me the Swedish road signs, in English.
I live in Ontario where major highway road signs are bilingual, e.g. “427 North/Nord”. Google has ingested these, blindly translates the French part, and tells me to take “427 North North”.
Fwiw, you can set (on Android at least) the language of Google Maps independently of the rest of the system. I also have my phone set to English, but maps set to Dutch because otherwise the reading out of street names can be incomprehensible compared to their proper pronunciation.
This does mean your navigation instructions are also in that language, which may or may not be a problem, depending on your fluency (but there's not really a whole lot of phrases to learn.)
Yes I discovered this, this weekend. As you mention, that relies on it being your native language. But it's absurd that if I'm in driving in a foreign country it would attempt to read the names of the streets in your own language's dialect.
Maps is so annoying for that: I travel to France, Italy and Germany on the road, and language is set to English on the phone, so it tries to pronounce everything the English way, and I can’t understand anything.
I wish I could set a "read location/road names in local language" setting.
It's worse in Taiwan where road signs are in both Chinese and Pinyin (romanized chinese) and Google Maps will randomly shown you only one of them for turn instructions. Good luck recognizing some obscure character for a town name in time if you are not fluent in Chinese. I would be surprised if this hasn't caused any accidents.
Also: don't guess shipping options or other stuff based on my browser's language!
My computers are all set to English even though I'm a German living in Germany, and I absolutely hate it when local business websites give me the "we don't ship abroad, sorry" just because of my browser's language settings.
When we added translation features to our news site I went down this rabbit hole and wholly agree with the author. I checked what others were doing and very often there was this ip lookup happening, and then a redirect or other unnecessary behavior.
In our case, less is more. We decided to not do any of that, and were a bit paranoid that maybe we were going against a 'best practice' somehow?
All we do is look at navigator.language to get the language code:
and if we support that language then we will change the "Translate" button label to that language and default behavior to shortcut to that language version (you can still get the full list).
This was the bane of my existence when I lived in Uruguay! Despite having the Accept-Language header set permanently to en_US, Google would constantly reset my UI language to Spanish, despite being logged in and having the account language set to English.
The worst offender was eBay which would machine-translate listings from English to Spanish.
Not accepting Accept-Language is one of my major pet peeves. What makes it worse is that many multilingual websites translate their language-switching buttons and the list of languages to the current language .... which is beyond fucking stupid and defeats the purpose. Wikipedia does this right. The button to switch languages is clear, using a universal multilanguage icon, and a list of languages (using the name of the language in that same language) in alphabetical order, with the most likely candidates on the top (presumably based on geoip).
E.g. an English Wikipedia page will present me with the following language suggestions:
Suggested languages
Deutsch
Français
Nederlands
When you assume a language, you make an ass of you and of me. Don't be an ass. Be like Wikipedia.
Oh nice! I never noticed that "Suggested languages" shows languages I previously selected.
But additionally, I like how it's not simply "pushing to the top", it does shows a previously selected language on the top, but it still keeps it duplicate in the list below, in case the user is going by muscle memory.
To me this is the best way.
Either make it VERY OBVIOUS that you're removing the item from the bottom of the list (which wouldn't be possible here), or don't remove it at all.
If I had a cent for each time a SaaS made my life harder by trying to "help me" I would be CEO of every SaaS I use.
Well, it's in an order, but I don't know about alphabetical. I clicked on today's English featured article and looked at the languages: "中文", "Italiano" are "suggested", then the remainder are grouped by geographic region, and aren't particularly alphabetical. They appear to be in groups which are still not alphabetical. Europe seems to have a Cyrillic group but "Қазақша" is shown after "Українська" which isn't accurate in Kazakh and probably also unexpected for anybody who isn't familiar with the letter Қ (Қ isn't a letter in Russian, this is probably why this happens). The Chinese languages don't seem to be in stroke order (no expert here), although Korean is below them (because of course, K for Korean alphabetizes after C for Chinese).
Anyways, no hate for Wikipedia; they do a great job of localizing. Just a bit of nuance/pedantry about how you can't "alphabetize" language names in their own language.
Yes, that’s confusing and probably hard to find a good balance. Someone speaking Greek or Czech may expect to find their language around E (Ελληνικά) or C (Čeština), but nope, on Wiki it’s all the way after Z.
Don’t special characters always go after the Latin alphabet? I think this is pretty common, and fairly expected behaviour. Of course nothing is perfect but I feel like the way Wikipedia handles it is consistent.
Well in my language "é" is absolutely not special, and should definitively be placed near "e" (to the point that uppercase é is often written E instead of É)
> If you want to see bizarre sort rules, look up how french sorts accent characters.
I tried to do this, but there do not appear to be any sources addressing this question.
I did find a French Stack Exchange question asking for this exact information, and complaining that there are no sources (other than an uncited wikipedia page) that address it. There is no answer posted, but there is a comment from a French guy suggesting that there are no official rules.
I notice that post suggests that Académie française specifies that accents should be sorted in reverse, and includes a link over the words "Académie française", and yet that link doesn't go to a supporting document.
A while ago I complained on this forum that Amazon's hyphenation for Kindle ebooks is abysmally bad. (Which is still true.) Someone responded to say that the hyphenation algorithm for English requires this. I pointed out that the hyphenation algorithm for English is a lookup table; each word has its hyphenation defined in the table, and when you need to hyphenate a word, you look up the hyphenation points.
Another response linked me to a paper describing how this table can be stored as a set of rules that provide hyphenation points in arbitrary letter sequences rather than dictionary words. That paper is very clear about its goals; it is an advance in data compression, proposing a method of storing a lookup table that takes less space than the table does. It carefully goes over how to produce the ruleset from the table.
But somewhere along the line, people confused the data compression algorithm (of storing the lookup table as a ruleset) for the hyphenation algorithm. They will now tell you with a straight face that a single ruleset that seems to have gone around represents the hyphenation algorithm for English, even if the word you want to hyphenate wasn't in the table that that ruleset was prepared from. And this is false.
It looks to me like something similar has happened in English speakers' understanding of French sorting order. It's very easy to explain why the example quadruplet has the sorting order it does:
cote
côte
coté
côté
(Note that the Stack Exchange question from 2024 and the blog post from 2004 use exactly the same example.)
These four words have two pronunciations, and the pronunciations are grouped with each other. After that, "cote" comes first by virtue of bearing no accents, and "o" comes before "ô" for the same reason.
What's happening here is that although French generally pretends that "e" and "é" are the same letter, they aren't, which forces -e (not pronounced) to come before -é (pronounced!). "o" and "ô" actually are the same letter, and can be ordered flexibly.
The rule "sort the accents in reverse" arises as a coincidence; it happens to be the case that this distinction is most significant at the end of French words. But French speakers would reject this ordering:
cetot
cétot
cetôt
cétôt
This doesn't come up because those words don't exist.
That’s English hegemony. Languages have their own sorting that they expect. You can’t impose rules to other languages.
Of course at some point Unicode needs to be ordered, but you don’t get to impose technical details to people around the world because it matches with how English does it.
That’s where geo-ip guessing becomes relevant. Show a list with the most likely languages at the top.
Or use the Accept-Language. Since we already know the User understands that one, it's probably a reasonable choice for which sort order they expect too.
If I recall correctly, the default propose a first list that push items which are guessed most likely what the user expect, then a list more complete, and in any case let you filter by typing. I think it also can change the way it behave if you are connected and tweaked your preferences in the matter for your account.
Wikipedia uses UCA sort order in categories (depending on which lang wikipedia you are reading). Most other lists just sort using unicode codepoint order (in NFC). So it depends, but yes, for generated lists other than categories ascii characters usually come first.
The problem may be is that you need to set the locale in order to get certain alphabetization, but setting the locale won't happen until after the language is chosen.
A reasonable approach might be to sort the list of names by using, as the sort keys, the strings projected through a Unicode normalization function, followed by folding to upper case. Then Čestina gets mapped to CESTINA and at least appears among the C's.
Not so, this sort order has been standardised as part of Unicode for at least 28 years. To see it in action, pipe the list of languages as a text file through a conforming tool like `ucsort`. When Қ is falsely sorted after Ч, then the wrong algorithm or no algorithm at all has been used.
> because of course, K for Korean alphabetizes after C for Chinese
Yes, the DUCET is bound to disappoint everybody (especially users of the Latin script with diacritics, as none of them agree on the sort order and everyone’s preferences are tied to the specific subset of diacritics they need), but at least it disappoints everybody more or less equally.
(Do yourself a favor, though, and use the CLDR root collation instead of the raw DUCET—they are basically the same, except, and I’m quoting the standard here[1], “the DUCET is not entirely well-formed”.)
It's a circular dependency: how do you sort and list the locales or languages for someone to pick one, when by definition you don't know their locale yet?
You have to either make some best-guess approximation (IP geo, browser headers, etc) or use a locale-invariant sort, both of which will be wrong in some cases.
We can find a sorting order with the minimal total distance between where we place a language entry and where this entry would be in that language. If there’s no pair of languages A and Ä such that A > Ä in one and Ä > A in the other, then (I guess???) this total distance will be zero.
That’s also part of the reason I’ve chosen it for a placeholder / variable name! The actual placing is not important as long as it’s where speakers of the Ä language expect to find it.
Or suppose there’s languages Ä₁ and Ä₂, where in Ä₁ the ‘ä’ is the umlauted ‘a’ and in Ä₂ it’s a distinct letter. The language list would be displayed as:
A Ä₁ B C Z Ä₂
The only problem / corner case would be such a language Ä₀ that would e.g. sort ‘ä’ before ‘a’. I would still put it after, since it’s where most other readers would expect to find it.
can't you just sort all as int? the codepages usually come roughly sorted, and while no one knows which of 檎 or 橙 comes first, I don't think it'll be particularly offensive whichever way a random app did, to most.
That would be one locale-invariant sort as I said. Sure, you can pick some way of doing it that's least-bad. The codepages are roughly sorted, but what we're debating is the cases where that fails some definition of correctness. The point is there can be no universally correct answer for sorting locales before the user picks one, because that can depend on already knowing the locale itself.
> The Chinese languages don't seem to be in stroke order (no expert here)
They are for me. In the Asia section, 中文 ["Chinese"] is listed first, followed by 吴语 ["Wu"] and then 粤语 ["Cantonese"]. Stroke order is first by stroke count and then by an obscure criterion that I don't know (and that, in my experience, Chinese people living in China also don't know), but stroke count is unambiguous and these are in order: 中 4, 吴 7, 粤 12.
Note that they aren't in alphabetical order: 中 Z, 吴 W, 粤 Y.
Japanese appears between Wu and Cantonese for unclear reasons.
It is sorted FIRST by radical and SECOND by stroke order. This is roughly equivalent to the Unicode codepoint sort if you stay in the basic multilingual plane. The order also puts literary chinese afer wu Chinese, which breaks with a pure stroke-count sort:
Dictionary lookup is done first by radical and second by stroke count. Collation is not. Stroke count is first.
For example, I have a book of 成语 stories that gives its table of contents in non-alphabetical order. (Since nobody understands the traditional ordering, I also have several such books that put their table of contents in alphabetical order.)
Note that 三's radical is 一, the first Kangxi radical, and that 一 is listed first. Your theory is wrong. 三 isn't even first among the 3-stroke characters, which start (among these) with 口.
Why did you make up a false answer to this question?
The Wikipedia sort for the languages is as I stated above, with Literary Chinese and Japanese between Wu Chinese and Yue Chinese. I explained why it was sorted that way, because radical is considered first. You could not explain why Japanese appeared between Wu and Yue because you insisted and continue to insist that radicals are not used.
I didn't say sorting is never done by stroke count alone. But I have seen radical+residual stroke count much more often than stroke count alone. Probably a result of the content I'm accessing. It's mostly Japanese and not intended for children.
The dictionary and non-dictionary sorting distinction that you make doesn't sound like a real thing. The audience, the country, and the number of items sorted are bigger factors. But you're not wrong in that stroke count is sometimes used alone.
> You could not explain why Japanese appeared between Wu and Yue because you insisted and continue to insist that radicals are not used.
I can't explain that because it's part of a different logical group, with its name written in a different script.† This puts it parallel to the Chinese options and to Korean.
> The Wikipedia sort for the languages is as I stated above
I took you to be describing the sort order for characters, not for wikipedia. Wikipedia doesn't obey that order either. You can check the page for Jiangsu, where all of the languages mentioned so far appear before the "Latin alphabet" style languages, but 閩南語 and 閩東語 appear after them.
† I also can't explain why wikipedia seems to have chosen 吴语 but 粵語, 客家語, and 贛語. Jiangsu is on the mainland... and so are Jiangxi and Guangdong.
> all of the languages mentioned so far appear before the "Latin alphabet"
> style languages, but 閩南語 and 閩東語 appear after them.
Could it have something to do with Minnan and Mindong Chinese articles being written in a Latin script, (despite the language name showing in both Chinese characters and Latin letters) ?
I can give a perfect bad example: the Youtube app on my iPhone somehow determined to change to Amharic. This is the Google support article: https://support.google.com/youtube/answer/87604 telling me the buttons to press in English. Also, I don't know/speak Amharic, and so at the time had no idea what language it was, and the iPhone translate doesn't even recognize this Ethiopian language. Bit of a pickle that could have easily been mitigated by a universal multilanguage icon.
Yes, actually. Is there an article about it? After updating to iOS 18.4, Amharic was appended to the end of the list of preferred languages in the iPhone Settings app. However, what's interesting is it was ranked below English, and apps are supposed to use the languages list in order, but perhaps Youtube is alphabetically sorting the list?
Or the ChatGPT app which can be baffling. My phone language is English, I've set ChatGPT app specifically to English in the app settings, I ask my questions in English, and every now and then it still decides to answer in German.
My favorite is the sites who do parse Accept-Languages, but then pick the last one in the list instead of the first. I have mine in rough order of my competence in them, which gets me my least-competent language on some sites even when my most-competent is supported.
I get a kick out of it when I see it, because you can understand how it happens. "Well, at least you tried."
It is wrong to blame the server here. For better results in content-negotiation, a user-agent should allow you to assign numeric weights instead of just a list (implying the same level of preference). Example:
Accept-Language: en;q=0.7,pt;q=0.3
If you already send something similar to this, and the server gets it wrong, then this is an outright bug, the software or its operator is out of compliance with HTTP.
This parameter, at first glance, appears to be used as numeric weights for automatic translations served by default, what turns browsing very uncomfortable (wrong translations, distorted texts).
Ie. Google, Youtube, Reddit.
Automatic translations should never be served by default, but only be loaded if the user requests it. The classical "do you want translate".
I don't need help, I'm criticising the use of the automatic translations served by default, and that are being used the weights of this parameter to do it.
The full picture? The weights seem to be more useful for fingerprinting and perhaps for server SEO than to help the users. Users who in the end will have to give the same weight to all the languages, or rewrite the outgoing headers, in order to be able to browse the Internet.
99% agree, but there is a problem on mobile, to switch from Spanish to English when I click the glass to search for alternatives. I have to type "Ing" (that are the first letters of "Inglés") while it shows "English" in the list of matches. It would be better if I can type both "Ing" or "Eng".
It's even more amusing when the displayed list looks like it's sorted randomly, but in reality it's sorted alphabetically in a different language to the display language..
e.g.
Nederlands
English
Français
Deutsch
Espagnol
(but if sorted in English: Dutch, English, French, German, Spanish)
I don't understand why you would want to select Inglés instead of English? You want to selecf English, or Español, or Nederlands, or Deutsch, or whatever language. If makes no sense for it to be translated.
Only in a very few weird corner cases. If it's an article about a city in Germany, I may like to see the article in German and use autotranslation to read t in English or Spanish.
Sometimes the article in the local language has more info. I had that problem in comments about places or events in Argentina. Sometimes the English article has less info than the Spanish article, so I made a link to the autotranslation.
There are two levels of this. If I get some other European language, I can generally figure out which is their word for English and it's not a big deal to switch. But if it gives me a script I don't know, like Bengali or something, it's a problem.
Perhaps every "choose language" menu should include English and Chinese in non-localized form, as an escape hatch, since almost every web users can recognize enough of them to navigate a menu to find their actual language.
Just include languages in their own script only. Why would a user need to select a language from that menu for which they DON’T know the target script? Showing Bengali in Bengali script is exactly what you want.
A related issue that has me fuming is when, after arriving at a page of interest from a search engine, a modal popup forces me to select the country I'm from, and then promptly redirects me to the homepage of the regional website.
Some have a X button to close said dialog, but many don't which is really aggravating.
Google does this. I want to check out the new device they just released - "sorry, this product is not available in your country". I just wanted to read the specs, not buy.
Ironically, given TFA, it seems to be primarily using the user's IP:
> How does Universal Language Selector determine which languages I may understand
> ULS queries a service that determines your originating country based on your IP address. This is inaccurate in some cases. Based on the country code, most often spoken languages are suggested for you.
Indeed. Wikimedia wikis' language selection feature relies on Unicode CLDR language-territory data. This is very complex to maintain (and there are still many mistakes to fix), because reliable data is expensive to collect.
Going one step further: do not guess my regional preferences from my language. I want to have an American English UI but use little-endian dates, whitespace and comma as thousands and decimal separators, ISO week numbers in calendars (with Monday being the first day of the week), and metric units. I want English subtitles, but not ones meant for the hearing impaired.
Mmm... understandable, but less trivial to implement than the OP. What you're requesting is quite a lot of localization customization. Reasonable to expect this from say, Google Sheets, but you might be out of luck with apps with smaller budgets.
This is a real pain in the ass in Belgium. Many websites assume I speak French while my native language is Dutch. Some websites only offer a French version of their Belgian storefront, even though Dutch accounts for ~60% of Belgians. I can't imagine what it's like for German-speaking Belgians.
This is not only an issue on websites but also on apps. For example, the Books and Podcasts apps on iOS show me both Dutch-speaking and French-speaking titles. I tried to raise this issue back when I worked at Apple but they only have 1 storefront per country and didn't feel like changing it.
Once upon a time French was used even in the Dutch speaking parts, in government, economy, high society. That was long before the internet got popular though. We've had a long fight to get rid of French in Flanders. Dutch is the only official language in Flanders, and it's the language people speak (except expats, or migrants who haven't learned the language yet).
So when companies still assume Belgium == French, it's not only wrong, but it comes across as very condescending. It feels like they haven't outgrown the times where Dutch was suppressed in favor of French.
And why? If a company wants to use only one language for the whole country, it's better of choosing Dutch (as we indeed account for about 60% of the population). Many of those companies do have a perfectly good Dutch translation, which they use for their site when viewed from the Netherlands. Even if they don't, I much prefer English over French.
You'll be glad to hear (I guess) that the pain is shared by french speaking Belgians.
It happens all the god damn time that the websites render in Dutch (or I guess Flemish) instead of the set Accept Language I have (EN then FR). Google is regularly showing me results in Dutch, most online stores default to Dutch even if they have English and French versions available.
Just imagine, all the websites that correctly (for you) display in Dutch, are websites that we have to change to French. I would guess there are more Dutch-defaulting websites than French ones, but I can't know for sure.
Btw, our neighbor is huge and french speaking too, so I'm not surprised companies coming from there favor French on their site. The same way that NL companies operate in Flanders but less so in Wallonia have their default to Dutch.
Also I'd argue that companies operating in Belgium should default to asking the language instead of guessing, otherwise you'll always anger half of the population.
Glad to hear how the other side of the country experiences things -- that happens not nearly enough, we (and our media) tend to focus too much on our part of the country (in my opinion).
Not glad to hear you have the same problems (only different).
I wasn't really talking about French companies though; I've seen it with large American or Korean companies. I'm gonna say companies like Nvidia or Samsung; I'm not sure about these two exactly, but I've certainly seen it with companies of that caliber.
One of the many, many tedious things about the modern globe-spanning internet, used by hundreds of millions of people who regularly travel far and wide, is this bizarre, stupid forced algorithmic balkanization in which you're pigeonholed right into either being denied access to certain content based on your location, or having your supposed language tendencies modified by default.
I'm not sure what the purpose of this idiocy is. Is it a dark pattern of some kind? Or is it just so hard for grey, cubicle-dwelling functionaries at companies that are themselves often very international to set systems for leaving one's language defaults static unless otherwise adjusted by said site user?
If you're already tracking me and every single one of my digital activities through my devices, then at least give me some modicum of convenience from all the bother.
391 comments
[ 3.2 ms ] story [ 335 ms ] threadIf websites really need translation (which they very likely do not!), this should be the norm as well.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/...
I wrote about it once; https://dijit.svbtle.com/trusting-the-user-they-know-what-la...
Outlook web actually respects this, which is refreshing.
I speak Dutch and English, but have English set as my preferred language, because most of the time that multiple languages are available, that is the original language. However, sometimes I'll be visiting a Dutch site that has a (usually badly-)translated English version available, and I'd rather get the Dutch version.
I would think the ideal prioritisation should probably be:
* Exact (en_GB)
* Exact (fr_CA)
* Soft (en_*) // Any variant of English you might have available
* Soft (fr_*) // Any variant of French you might have available
* Translated. (to first preferred)
for Accept-Language: “en_GB,fr_CA”
(Also note that I wasn't talking about automatically translated content necessarily. Manually translated content still often is of worse quality than the original language.)
You could probably also trick websites into serving the original language by setting a language they probably don't support (how many websites have a version available in Akkadian anyway?) but you'd need to pick something that the Google Translate widget found on many websites doesn't pick up and try to use.
(To be clear, with how widespread English is, and how often Dutch sites are Dutch-only, this is a minor issue - having English, then Dutch as my preference is usually good enough.)
but then you have to -know- at which geo you want to operate.
The internet has long been broken as a global field imho
It does not "fix" that at all, and breaks so many other things. I don't wanna see US/UK/Australian prices just because I happen to live in Spain but prefer English when browsing the web (literally same boat as parent).
i meant it fixes allowing you to pretend to be phsycally somewhere else, but as you say introduces a whole can of new problems/hurdles
idk man i just switch it on and off depending on site
They absolutely do lol.
Like it or not, people like you are outnumbered by people who set their Accept-Language header wrong and don't know how to fix it. Those people probably buy more too (or at least buy more that shows up in tracking, since you sound like the kind of person who disables cookies etc. too).
Is this actually something that you can back up with data, or are you just guessing?
I find it hard to imagine that would be the case, considering this header generally gets populated by the user's system locale/language.
And you know what? I didn't pay so much attention to what English I'm selecting so part of my devices are set to UK english and part to US english. It's all English to me, just don't translate my File menu!
I have to run into strong britishisms* like lad, tad, cuppa to remember there are differences across the pond.
* strong britishisms to me the non native speaker, at least.
I challenge you to find one person that matches that description.
I let you track me Google, please use it for some good UX and not just advertising.
At any one time, there's got to be tens of millions of people accessing Google from a country which has a primary language unknown to the traveller. Even if this number is insignificant compared to Google's full user base, the cost for Google to service 20-30mn people with a feature is presumably lower than their annual ad revenues across 20-30mn people.
It is of course useful for those 700+million, but they are not customers of Google, they users/the product. So long as you won't go elsewhere (in mass) you don't matter.
Lately they've decided that auto translating the local language into English in Maps reviews is the wrong thing to do. They translate every other language into English but somehow since I live in this place I must speak the local language too, so I don't need that in English.
Ditto for search results. Surely you want Wikipedia in the local language! I mean you've been there for so long! You search for things in the local language, surely that's a sign of your preference and not the fact that searching for things locally requires use of the local language.
This also applies to so much other "we must make our software so smart and guess all your preferences". Google fails so consistently at this I cannot understand why they persist other than some sort of misplaced corporate self regard.
People like us are an edge case.
Many EU country have more than one official languages.
Most previous colony is bilingual.
He told me that for efficiency, they had different stages in the content rendering and that the main page structure didn't have your user information yet. That's rubbish IMHO because the accept language header should be readily available in that phase.
The guy you argued with sounds like they were semi-justifying this with the typical "noogler" rose colored glasses.
That's called premature optimization.
I think this is because half of Google live their entire career in California, so they don't know about other languages, units, time zones at all.
It's weird, because they employ SO many foreigners, bringing them to California. But somehow upon arrival they all get memory wiped about the existence of anything outside the bay area.
Other companies do this right. Google is user hostile.
No. I will NEVER navigate by bike, foot, or public transport in these strange America-only units.
Using Google search, which luckily did not decide to show me "local" results to an English query like it often does home, I found a support thread suggesting I set my Accept Language to have something other than English as a second language. Lo and behold, the page decided to now respect it.
In my case, I live in the United States, but Google is determined to serve me Spanish results even for Catalan-related queries. E.g. preferring the Spanish Wikipedia. The search engine's behavior has had ups and downs over the years, but it has never been great.
This is very much a problem for my children, who don't understand Spanish, as well as for the Catalan-speaking regions of the world that are not in Spain, including Andorra.
In my experience, Gemini easily flags any Catalan content as unsafe and prevents the conversation from continuing. Even for prompts like "summarize this article". This may have improved lately, but still.
Google used to be an example in sensitivity to the world's diversity, being a responsible major player. Way back. Now, although I applaud some efforts multiple teams continue making, it is obvious this is no longer a priority.
I'm curious, what are the keywords that trigger that?
All accounts can be active at the same time on the same phone, there is a dropdown to switch in the Store app, and that works even with a work profile on the side. I've yet to see real downsides, except for course remembering which account is on which country and manually switching.
Google will then go on to complain about users installing APKs from shady sources but this practice pushes users to do so. I'm sure a decent amount of users ended up with malware on their phones just because they wanted to install an app that wasn't available in their listed country.
Which is kinda valid, in the southern and south-western parts this is done because there is a significant Swedish-speaking minority so most cities and streets have names in both languages.
But at the time I lived in central Finland, where the streets DIDN'T have official Swedish names, they just ... translated them. Which was super fun for navigating.
https://qutebrowser.org/doc/help/settings.html#content.heade...
I assume other developer-centric browsers have similar options.
That's a silly solution in any case, since you literally use the browser for other sites. Dozens of tabs.
Your payment provider's automatic conversion is most likely more predatory than my bank's so I don't want to use it.
And even if you guess my location right, how do you know I want a badly/machine translated web site?
Why not let germans select iDeal and dutch users Giropay? They'll not click it if it's not useful for them. Adjusting the sort for what's most commonly used makes sense, but why actively thwart users from paying by geolocking payment methods by IP address...
Charging customers from countries with higher average purchasing power more and hiding the fact behind "charging people in the local currency for convenience" is much more profitable!
When price is set to $9.99 which works out to 47.89287237634 in your local currency. Although it would work out to 45.89327782 if you used your bank's conversion instead of the "helpful" service.
In those cases i don't think the seller makes any extra money, they get their $9.99 minus payment processor's fees. They just think they're helpful but make you spend more for no good reason.
Billing address is not a sure way to predict currency.
As of a few days ago, Stripe is forcing all their partners to offer their customers the predatory currency conversion. There is no way to opt out, except switching to another payment provider with their own problems.
This is also a broken assumption.
First, Accept-Language is an ordered list, and most daily-multilingual people don't have an absolute order of preference, and more a topical list of preferences.
If I read an English news site that has a translated French version, it doesn't matter if I'm most proficient in French, I'll want the English version.
Then, as an affect of the first point, users will specify their most practical language, not some actual preference. For instance local non-English sites tend to do less shenanigans than international English ones, so having one's language set as English only will force English display for the former, with few impact on most other sites.
A French site ignoring all preferences and just pushing the French version by default actually helps in that case.
If anything, I just wish site owners stopped trying to be cute or clever and just had a very obvious and quick interface to switch to other versions. Wikipedia does it decently well for instance.
Where does this assumption come from? Given the fact that many (most? almost all?) sites don't honor the Accept-Language header, I doubt that there's much game theory going on in users' head when deciding this configuration.
We definitely pick languages that work as opposed to languages that we speak. Setting it to Dutch is just worse: UX doesn't fit, english search results wouldn't show up (way fewer results/content/info), and translations often don't make sense (imagine a button called "you shut it" on a modal window, it's a literal translation of one interpretation of the string "close it" but you'll be confused as to what that button will do)
You have people working in IT who set their language to English for easier troubleshooting (i.e. not needing to Google error codes), but they're a small minority.
If your native tongue is Spanish but you live in the US for instance, the "preferred" language in your browser has IMHO a higher chance of being English. Same if you live in India probably.
Even for auto-translated content, I wouldn't be surprised if it was off-the-shelf plugins that handle the switch.
All in all, I think it takes more effort to ignore the Accept-Language header. That won't prevent sites from tweaking it or doing their own cooking, but it kinda requires intent.
Technically Accept-Language allows you to specify a "quality value"/weight for each language... https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/...
IMO there is a lot of improvements that can be made by both the browser and websites:
Websites should probably allow users to override the browser-requested language. But browsers should also allow users to choose between "Site default", "Request system default language", "Request English", "Request Chinese", "Request Spanish", etc. on a per site basis.
Most optimally however: sites should expose a list of supported languages, maybe in the manifest.json: https://developer.mozilla.org/en-US/docs/Web/Progressive_web... Format would be something like: `Map<iso639Code: string, Tuple<translationQuality: float, comments: string>>`
Language selection should be done on the client side, not on the server.
Having priorities and weight and language lists in the manifest help for negociation, but at the core of it, the user will want to choose language based on context and content.
> Language selection should be done on the client side, not on the server.
Yes.
Using a site specific list on the client side could also do it (let's say I always want Facebook in a language and Google in another, Linkedin in yet another etc.). It still will be pretty cumbersome, probably needs an auto-save and sync of the preferences, and still hits problematic cases, but it would be the most pragmatic solution.
The worst instance of it is IMHO the way Google Maps work, changing language based on the country gives the best display (local names in the proper writing, no internationalization), I wish there was an easier way than screwing with the Google account preferences. As you point out, having clients able to unambiguously request a specific version at each requests would gives us so many more options.
People are complicated and having simple heuristics to predict what more than half of them want is not feasible at our level of technology.
Sure any single person will have somewhat simple rules to decide what languages they want, you could come up with simple rules for the people in your life. But you're not trying to solve it for a specific group of people. The target is 8 billion people, most of which we have no idea what their life is.
Yup, agreed. I highly doubt most websites even look at those weights in the Accept-Language header anyways.
Having a list of supported langs in the manifest costs nothing. Lazy-load the manifest when the user goes to use the language selection dropdown, or when the response from the server is in a different language than the one requested in Accept-Language (check Content-Language or html `lang` attr).
Looks like there's a name for this, but no standard: https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Con...
The solution there is not to abandon the very useful Accept-Language header, but to never offer half-baked translations. Is your website multilingual? Fine, but only offer fully translated and verified translation sets. It's OK to have your UI and your own content translated in a few languages — for a company that may make sense depending on their target clientele — but you'll have to maintain all of these and keep them in sync.
However, user content is off-limits. No automatic translations unless you only offer those under a button to be helpful (like 'Spanish detected, click to show an automatic translation into English'), but really, leave that to the user's browser.
Use Accept-Language to pick a language, and then offer me a way to switch in addition to that. That's all there is to it.
> Wikipedia does it decently well for instance.
Wikipedia doesn't do that. Each language is its own instance, where content may be ported to by translating it (or parts of it), but outside of the Mediawiki UI texts, it is not a translation of the same content. The Dutch version of the lemma 'Language' is a different article in a different language with some overlap. There is no claim made that it is the same article in Dutch. It is hosted on a different sub-domain and path on purpose.
Sadly that ship has sailed.
We can look at the reaction from smaller youtubers as auto-dub rolled out. Most are sympathetic to the quality issues but are seeing it as either a "good enough" or at least a "better than nothing" feature that helps them expand their audience with no visible cost on their side.
Or official government sites that have explicitely disclosed AI translations and didn't bother passing it through a regular translator.
This situation just won't get better. Except perhaps the day AI is actually intelligent and we have human being level translators running on cloud servers.
> Wikipedia
Yes, those are not translations, but in that specific case they also don't need to: the quality of the article will vary depending on the editor, but there's no "original" article, so nothing to translate from IMHO.
No, I do not want the translation at all, unless I say so. Really. Even if it is the best translation in the world. I want and need to choose the language I will read or watching something in.
No, it's a partially ordered list.
> If I read an English news site that has a translated French version, it doesn't matter if I'm most proficient in French, I'll want the English version.
Then you should have both with the same priority.
From my technical standpoint it worked really well and the code was very slick. It was a lot of fun to build.
From a user standpoint most of our users really just wanted English regardless of their Accept-Language header. They had the option to change it in the footer but this apparently wasn't obvious enough.
We just ask now, and our users are happier.
I run into those regularly and it's always a struggle to know how to stay on the damn page I clicked on: will the "continue" button use the preselected value or will it dismiss the pop-up and continue on the current page?If the former, is the preselected value the page I'm on or a different language? Can I guess which locale I'm on to select that and dismiss the pop-up then? Can I inspect-element→delete this modal and just sidestep the whole problem? Even just a small close button is a luxury on these language walls...
95 out of 100 times, I'm fine with whatever language I clicked on, and if I want your German version for locale-adjusted shipping info or payment options or whatnot, I'll look for a language selector on the top right or, alternatively, in the page footer. If it's in one of those two places, I'd be much happier about a web without JavaScript-based pop-ups constantly
It's just a separate page you hit after signing in if we don't have your preference. You click on the language you want and you are redirected to the dashboard.
The option to change it still exists in the footer.
I’m currently agonizing about how to let the user change their language, because I want to respect locale as well (es-MX vs es-ES for example). And I haven’t found a good UX pattern for changing language+locale. I’ll likely just implement a big list that the user can select, and have the current language be a link that they can click to change via a modal.
You want your users to be able to change their location (and, therefore, locale) and their language independently. The Accept-Language header could be used as a sentinel for language. Then again, I wouldn't outright rely on geoIP to set the locale which is an umbrella for regional differing variables like timezone, date formatting, currency, VAT / Taxes,...
I think it's okay to have your content served, by default, in a language that reflects either the majority of your target audience; or the culture / place you're based in. Changing the locale / language should follow a clear UI pattern e.g. a language switcher & locale switcher in the header; or a clear navigational aid pointing to a context menu. That's how Hetzner works, for instance. Another example is Deliveroo.
[1] https://translatepress.com/locale-vs-language/
Why is it so hard to just add something as a setting/feature and offer it to people without forcing it on the user?
I can speak german, I don't need forced subtitles for the nazis
Office politics. Google is famously "performance-driven", so the manager in charge of that feature needs usage metrics to be high for the sake of their own career.
(Speculating, of course.)
The sad part is we can't rule that out.
just dislike video and move on. I'm guessing Google wants uploader penalized, and I do feel sorry but it's not my problem.
At least I know I didn't mess anything on my WebOS TV.
I do this on purpose, because I find everything is more searchable. I don't even know any German terms for most technical things I might search or look for. So even if the automatic translations were good, which they aren't, this would be a non-feature.
My browser already tells them what my preferred language is. Just use it.
Now it's a mix of German and English, e.g. 1 heading is "Spiele-Bestseller", and the next is "Best selling apps". And prices displayed as "28,00 CHF" (correct would be to use the decimal point).
Like Van Halen's brown M&Ms, it just shows how sloppily this thing is programmed: https://www.snopes.com/fact-check/brown-out/
Exactly, it's like they've never left their own state levels of ignorance
Which has been baffling to me considering how many foreigners work at these companies.
It's the idea that the user has a preference for something, and it applies always and everywhere, even when it's not applicable.
If only they respected my system language. All my language settings are set to English, yet I routinely get autotranslated crap to my native language.
But they don't make those decisions. It's a UX thing, which means that in practice whoever is in charge of "driving up the numbers" is going to be making the decision; the engineers just get to cuss while implementing it.
In the rest of the world, and especially in Europe, this is the norm, not the exception. On one hand there is the prevalence of US English media (hello hollywood), US english literature (esp. in tech); and on the other hand cross-consumption between EU countries is much more common.
Oh, and the content ends up being in English too, because that's how to reach many people. We don't want those to be translated, because we don't want a double translation. This is something that the US / Silicon Valley mind cannot comprehend.
But nobody pays to get answers, so it's alright.
[0] https://kagifeedback.org/d/5212-low-quality-translated-reddi...
It's probably most useful for utility or news content. Not 'high effort videos' about an interesting topic. I'm imagining you find a video in another language that fixes a problem you have and can switch to your language to watch.
One of the sister replies linked to an extension to help with that, which I'm going to give a try, but it's annoying that there's not a simple toggle in the youtube settings to tell it to always use the original language. On the rare occasion that I want to use the translated audio track, I can do _that_ on my own; I speak enough languages that this is a very rare occasion with the type of content I watch.
This isn't even something I can understand as them being hostile to ad blocking or wanting to push ads. This is a 'convenience' feature that is just poorly implemented. But I'm sure there's some PM that got a pat on the back for it.
If you want to get rid of auto-translation on a systematic level, provide feedback to the operators of Youtube through their official communication.
Even being aware of this - how do I know that it's an auto-translation, rather than someone making AI slop in my native language, without watching the video?
Or should he just keep using the signals he gets and immediately clean up his feed?
I actually see this as a feature. YouTube recommends a lot of garbage. I suggested that they improved my feed but they implemented this signal instead. I use the exactly this method to weed out a lot of content I do not care for.
You cannot tell the 500 pound gorilla anything. I prefer my videos without subtitles. I have that set as a preference. Yet when chromecasting it is common for the subtitles to spontaneously turn on. And has done so for a long time.
English is not my first language and my first language is not widely used. Hence I am not used to dubbed movies/programming and I am used to seeing subtitles.
If a native english speaker could understand the horror show that the machine generated subtitles are. If you are used to subtitles they are extremely hard to ignore. You will then read and get the understanding (often hilariously wrong) before the audio catches up and you might end up rather confused.
I can understand an American might have a hard time watching a subbed German movie. Thats natural because it is not common. But when you grew up with subtitles it is actually effortless. Except when they are poor. Then it becomes worse because of the cognitive load of 2 languages and the effort to figure out what is correct.
Dear english only speakers: Translation is hard. A poor translation is worse that no translation as it obfuscates the message. AI is not there yet at all. Maybe impressive but often not helpful or plain and simply distorts the real message.
> A poor translation is worse than no translation
This behaviour rankles me, I think is on the same level as the misuse of the feature "report this as spam (to some upstream entity/3rd party)" for e-mail messages that are not actually spam.
I'm sure my "don't recommend this" clicks don't in any way make up for Google's promotion of channels that "make their content accessible", because it doesn't even stop them from recommending me more machine-translated videos.
They base the feed on user input. The feed is then (supposedly) adjusted to what I like.
What I call a signal you call an attack.
I signal that I do not like Minecraft videos. But I do not attack them.
Your anger is misdirected. You should be mad at YouTube because they do not seem to understand that there can be multiple signals at once.
The chances that I click on a Minecraft video is low. Autotranslated even lower.
So we differ strongly in opinion on how the platform should work. I read your "attack" argument as I should write to the Minecraft creators and tell them their content would be better if they played Minesweeper instead.
I do not punish anyone. I just pursue a clean and (for me) high quality feed.
If you are up in arms that I punish your channel that is another signal that I am probably not your target audience.
When dealing with audiences at scale you need to listen to these signals as handling personal opinions in mails from the discerning viewer is not feasible.
> A friendly e-mail to the channel owner explaining the problem and asking to manually disable auto-translation is much more likely to achieve what you want.
No it isn't, because I see what kinds of channels do this, over and over again. They're very clearly publishers who don't care that they make something objectively worse as long as the algorithm rewards them for it.
> If you want to get rid of auto-translation on a systematic level, provide feedback to the operators of Youtube through their official communication.
Ha, as if they ever read that. Probably more Google employees will read this comment than will ever read any of my (many) "please stop translating things without asking, I know where to find machine translation if I need it, doing it without asking that means I have to translate back from broken Norwegian into English in order to understand what the hell you were trying to say" feedback reports.
Unfortunately, all the translations are machine-translated garbage and there is no setting to turn this off as a viewer, so it's just incredibly annoying.
- If I select German subtitles for a German video, it will auto-translate all English subtitles to German in the future.
- If I select subtitles for an English video, same.
- If the video has an Arabic, Hindi, French human-made subtitle to help that audience, it shows it to me instead of the automatic captions
Horrible.
2 things that absolutely kill my experience,
1. Messing up with titles, specially if the contents of the video are still in a different language, Which Kurzgesagt will I get today? Only YouTube knows, this is annoying if I know the youtuber could use a different language in the title to make a joke
2. Messing up with the default audio tracks, I don't mind if the YouTuber has a dubbed track, that's awesome for getting more exposure, but I already know and expect a specific voice and it's extremely jarring
I know what Mark Rober sound like, leave it be
I think it is far worse than that:
1. If I don't understand a language, probably that video is not for me. Most videos targeted for international audience are in English, or at least the author translated it by theirself.
2. Titles are small sentences, and they don't have enough context to be translated. Once I saw a video called something like "Vamos assistir uma conexão com o passado", which in Portuguese means "Let's watch a connection to the past". I needed to de-translate it in my brain to understand that the original title was "Let's play A Link to the Past"
3. Online resources are a great way to exercise a second language. So, please, don't underestimate my capabilities. At least let me try to read in the original language by myself, if I need the translation I how to use Google Translate or a dictionary.
I reckon that this feature makes the access to online content more democratic, it's ok. But at least let me disable that since it makes the experience worse
But the real problem is when it decides to translate the titles of some perfectly watchable videos in English into something that uses the Cyrillic alphabet, what has no relation to my accepted languages, and is only used half-way across the world from where I am.
Every one of my subscriptions is an English language channel, and my language choice on all Google properties (where possible) including YouTube is English. It's not hard to judge that English is my favoured language.
And yet... every video advert I receive when travelling is served in the local country's language. It doesn't especially bother me, since I actively avoid listening to adverts (and indeed, now pay for Premium lite to avoid them almost altogether) but it's a weird not-so-edge case that I'd have thought a company as large as Google might have addressed already. They've absolutely got the tech to deliver adverts in any language. (And it could be powerful: imagine receiving adverts for local businesses in your native language while on holiday.)
Very annoying, because instead of just seeing the english post, which I'm easily able to understand, I see half-broken german...
If an English variant is in your Accept-Lang: headers, I'd hope YT wouldn't auto-translate English titles.
The other thing that Google might properly use is account-specific language settings. But if they're using GeoIP as has been suggested, I agree they're doing it wrong.
Your hope is unfortunately entirely misplaced. Google is one of the worst offenders for assuming language and region from users' IP.
About the translation, sure, "boot" ≈ "iniciar", "window" = "ventana", but for (microsoft) windows, and other names in foreign languages, the same name must be kept.
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.
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)
I don't know how that happens. Like, do individual teams within Meta have to re-learn that users in their own system have a language preference? (Not even talking about Accept-Language, it's a Facebook user setting.)
I have my phone's language set to English as a native English speaker. Google maps reads me the Swedish road signs, in English.
This does mean your navigation instructions are also in that language, which may or may not be a problem, depending on your fluency (but there's not really a whole lot of phrases to learn.)
I wish I could set a "read location/road names in local language" setting.
My computers are all set to English even though I'm a German living in Germany, and I absolutely hate it when local business websites give me the "we don't ship abroad, sorry" just because of my browser's language settings.
In our case, less is more. We decided to not do any of that, and were a bit paranoid that maybe we were going against a 'best practice' somehow?
All we do is look at navigator.language to get the language code:
and if we support that language then we will change the "Translate" button label to that language and default behavior to shortcut to that language version (you can still get the full list).Thats it. Keep it simple.
Example: https://restofworld.org/2024/filipino-ai-chatbot-launches-20...
(translation UI in the byline area, under lead image)
The worst offender was eBay which would machine-translate listings from English to Spanish.
E.g. an English Wikipedia page will present me with the following language suggestions:
When you assume a language, you make an ass of you and of me. Don't be an ass. Be like Wikipedia.But additionally, I like how it's not simply "pushing to the top", it does shows a previously selected language on the top, but it still keeps it duplicate in the list below, in case the user is going by muscle memory.
To me this is the best way.
Either make it VERY OBVIOUS that you're removing the item from the bottom of the list (which wouldn't be possible here), or don't remove it at all.
If I had a cent for each time a SaaS made my life harder by trying to "help me" I would be CEO of every SaaS I use.
Well, it's in an order, but I don't know about alphabetical. I clicked on today's English featured article and looked at the languages: "中文", "Italiano" are "suggested", then the remainder are grouped by geographic region, and aren't particularly alphabetical. They appear to be in groups which are still not alphabetical. Europe seems to have a Cyrillic group but "Қазақша" is shown after "Українська" which isn't accurate in Kazakh and probably also unexpected for anybody who isn't familiar with the letter Қ (Қ isn't a letter in Russian, this is probably why this happens). The Chinese languages don't seem to be in stroke order (no expert here), although Korean is below them (because of course, K for Korean alphabetizes after C for Chinese).
Anyways, no hate for Wikipedia; they do a great job of localizing. Just a bit of nuance/pedantry about how you can't "alphabetize" language names in their own language.
Also, we regard 'Ch' as its own letter. So yeah, try sorting alphabetically. I'll wait.
If you want to see bizarre sort rules, look up how french sorts accent characters.
I tried to do this, but there do not appear to be any sources addressing this question.
I did find a French Stack Exchange question asking for this exact information, and complaining that there are no sources (other than an uncited wikipedia page) that address it. There is no answer posted, but there is a comment from a French guy suggesting that there are no official rules.
https://french.stackexchange.com/questions/54217/french-dict...
How were you imagining I would look this up?
Or a more technical version at https://www.unicode.org/reports/tr10/#Backward
Another case that is kind of weird is thai https://www.unicode.org/reports/tr10/#Rearrangement
I notice that post suggests that Académie française specifies that accents should be sorted in reverse, and includes a link over the words "Académie française", and yet that link doesn't go to a supporting document.
A while ago I complained on this forum that Amazon's hyphenation for Kindle ebooks is abysmally bad. (Which is still true.) Someone responded to say that the hyphenation algorithm for English requires this. I pointed out that the hyphenation algorithm for English is a lookup table; each word has its hyphenation defined in the table, and when you need to hyphenate a word, you look up the hyphenation points.
Another response linked me to a paper describing how this table can be stored as a set of rules that provide hyphenation points in arbitrary letter sequences rather than dictionary words. That paper is very clear about its goals; it is an advance in data compression, proposing a method of storing a lookup table that takes less space than the table does. It carefully goes over how to produce the ruleset from the table.
But somewhere along the line, people confused the data compression algorithm (of storing the lookup table as a ruleset) for the hyphenation algorithm. They will now tell you with a straight face that a single ruleset that seems to have gone around represents the hyphenation algorithm for English, even if the word you want to hyphenate wasn't in the table that that ruleset was prepared from. And this is false.
It looks to me like something similar has happened in English speakers' understanding of French sorting order. It's very easy to explain why the example quadruplet has the sorting order it does:
(Note that the Stack Exchange question from 2024 and the blog post from 2004 use exactly the same example.)These four words have two pronunciations, and the pronunciations are grouped with each other. After that, "cote" comes first by virtue of bearing no accents, and "o" comes before "ô" for the same reason.
What's happening here is that although French generally pretends that "e" and "é" are the same letter, they aren't, which forces -e (not pronounced) to come before -é (pronounced!). "o" and "ô" actually are the same letter, and can be ordered flexibly.
The rule "sort the accents in reverse" arises as a coincidence; it happens to be the case that this distinction is most significant at the end of French words. But French speakers would reject this ordering:
This doesn't come up because those words don't exist.But in the language native locale, no.
Of course at some point Unicode needs to be ordered, but you don’t get to impose technical details to people around the world because it matches with how English does it.
That’s where geo-ip guessing becomes relevant. Show a list with the most likely languages at the top.
U+005A LATIN CAPITAL LETTER Z
U+010C LATIN CAPITAL LETTER C WITH CARON
U+0395 GREEK CAPITAL LETTER EPSILON
A reasonable approach might be to sort the list of names by using, as the sort keys, the strings projected through a Unicode normalization function, followed by folding to upper case. Then Čestina gets mapped to CESTINA and at least appears among the C's.
Not so, this sort order has been standardised as part of Unicode for at least 28 years. To see it in action, pipe the list of languages as a text file through a conforming tool like `ucsort`. When Қ is falsely sorted after Ч, then the wrong algorithm or no algorithm at all has been used.
> because of course, K for Korean alphabetizes after C for Chinese
That's not how it works.
(Do yourself a favor, though, and use the CLDR root collation instead of the raw DUCET—they are basically the same, except, and I’m quoting the standard here[1], “the DUCET is not entirely well-formed”.)
[1] https://www.unicode.org/reports/tr10/#Well_Formed_DUCET
You have to either make some best-guess approximation (IP geo, browser headers, etc) or use a locale-invariant sort, both of which will be wrong in some cases.
Coincidentally, the expected position of "Ä" can vary wildly. Is it an umlauted A, normalized as AE, or a distinct letter coming after Z?
Or suppose there’s languages Ä₁ and Ä₂, where in Ä₁ the ‘ä’ is the umlauted ‘a’ and in Ä₂ it’s a distinct letter. The language list would be displayed as:
A Ä₁ B C Z Ä₂
The only problem / corner case would be such a language Ä₀ that would e.g. sort ‘ä’ before ‘a’. I would still put it after, since it’s where most other readers would expect to find it.
OT, but this looks like an adorably blushing hen to me
This depends on whether you are viewing desktop site or mobile site. It also depends on if you have a non-default skin set in your preferences.
Seems like desktop (vector-2023) does the region thing.
Mobile does alphabetical by language name (i imagine codepoint order but i didnt check)
Some other skins are alphabetical by bcp47 code.
They are for me. In the Asia section, 中文 ["Chinese"] is listed first, followed by 吴语 ["Wu"] and then 粤语 ["Cantonese"]. Stroke order is first by stroke count and then by an obscure criterion that I don't know (and that, in my experience, Chinese people living in China also don't know), but stroke count is unambiguous and these are in order: 中 4, 吴 7, 粤 12.
Note that they aren't in alphabetical order: 中 Z, 吴 W, 粤 Y.
Japanese appears between Wu and Cantonese for unclear reasons.
中文 - 中 = 丨 + 3 strokes
吴语 - 吴 = 口 + 4 strokes
文言 - 文 = 文 + 0 strokes
日本語 - 日 = 日 + 0 strokes
粵語 - 粵 = 米 + 7 strokes
For example, I have a book of 成语 stories that gives its table of contents in non-alphabetical order. (Since nobody understands the traditional ordering, I also have several such books that put their table of contents in alphabetical order.)
Here is the collation order in the book:
一 七 八 入 九 人 口 千 小 三 亡 大 不 专 天 井 见 毛 月 文 风 为 心 水 四 ...
Note that 三's radical is 一, the first Kangxi radical, and that 一 is listed first. Your theory is wrong. 三 isn't even first among the 3-stroke characters, which start (among these) with 口.
Why did you make up a false answer to this question?
I didn't say sorting is never done by stroke count alone. But I have seen radical+residual stroke count much more often than stroke count alone. Probably a result of the content I'm accessing. It's mostly Japanese and not intended for children.
The dictionary and non-dictionary sorting distinction that you make doesn't sound like a real thing. The audience, the country, and the number of items sorted are bigger factors. But you're not wrong in that stroke count is sometimes used alone.
I can't explain that because it's part of a different logical group, with its name written in a different script.† This puts it parallel to the Chinese options and to Korean.
> The Wikipedia sort for the languages is as I stated above
I took you to be describing the sort order for characters, not for wikipedia. Wikipedia doesn't obey that order either. You can check the page for Jiangsu, where all of the languages mentioned so far appear before the "Latin alphabet" style languages, but 閩南語 and 閩東語 appear after them.
† I also can't explain why wikipedia seems to have chosen 吴语 but 粵語, 客家語, and 贛語. Jiangsu is on the mainland... and so are Jiangxi and Guangdong.
Was this about 6 weeks ago?
Not that I know of. It just happened to me, too, around then. I thought it had to do with my pet fascination with the Ethiopian civil war and GERD.
I get a kick out of it when I see it, because you can understand how it happens. "Well, at least you tried."
Ie. Google, Youtube, Reddit.
Automatic translations should never be served by default, but only be loaded if the user requests it. The classical "do you want translate".
The full picture? The weights seem to be more useful for fingerprinting and perhaps for server SEO than to help the users. Users who in the end will have to give the same weight to all the languages, or rewrite the outgoing headers, in order to be able to browse the Internet.
e.g.
(but if sorted in English: Dutch, English, French, German, Spanish)Sometimes the article in the local language has more info. I had that problem in comments about places or events in Argentina. Sometimes the English article has less info than the Spanish article, so I made a link to the autotranslation.
Perhaps every "choose language" menu should include English and Chinese in non-localized form, as an escape hatch, since almost every web users can recognize enough of them to navigate a menu to find their actual language.
Some have a X button to close said dialog, but many don't which is really aggravating.
> How does Universal Language Selector determine which languages I may understand
> ULS queries a service that determines your originating country based on your IP address. This is inaccurate in some cases. Based on the country code, most often spoken languages are suggested for you.
(from https://www.mediawiki.org/wiki/Universal_Language_Selector/F...)
https://www.mediawiki.org/wiki/Universal_Language_Selector/F...
This is not only an issue on websites but also on apps. For example, the Books and Podcasts apps on iOS show me both Dutch-speaking and French-speaking titles. I tried to raise this issue back when I worked at Apple but they only have 1 storefront per country and didn't feel like changing it.
Once upon a time French was used even in the Dutch speaking parts, in government, economy, high society. That was long before the internet got popular though. We've had a long fight to get rid of French in Flanders. Dutch is the only official language in Flanders, and it's the language people speak (except expats, or migrants who haven't learned the language yet).
So when companies still assume Belgium == French, it's not only wrong, but it comes across as very condescending. It feels like they haven't outgrown the times where Dutch was suppressed in favor of French.
And why? If a company wants to use only one language for the whole country, it's better of choosing Dutch (as we indeed account for about 60% of the population). Many of those companies do have a perfectly good Dutch translation, which they use for their site when viewed from the Netherlands. Even if they don't, I much prefer English over French.
It happens all the god damn time that the websites render in Dutch (or I guess Flemish) instead of the set Accept Language I have (EN then FR). Google is regularly showing me results in Dutch, most online stores default to Dutch even if they have English and French versions available.
Just imagine, all the websites that correctly (for you) display in Dutch, are websites that we have to change to French. I would guess there are more Dutch-defaulting websites than French ones, but I can't know for sure.
Btw, our neighbor is huge and french speaking too, so I'm not surprised companies coming from there favor French on their site. The same way that NL companies operate in Flanders but less so in Wallonia have their default to Dutch.
Also I'd argue that companies operating in Belgium should default to asking the language instead of guessing, otherwise you'll always anger half of the population.
Not glad to hear you have the same problems (only different).
I wasn't really talking about French companies though; I've seen it with large American or Korean companies. I'm gonna say companies like Nvidia or Samsung; I'm not sure about these two exactly, but I've certainly seen it with companies of that caliber.
I'm not sure what the purpose of this idiocy is. Is it a dark pattern of some kind? Or is it just so hard for grey, cubicle-dwelling functionaries at companies that are themselves often very international to set systems for leaving one's language defaults static unless otherwise adjusted by said site user?
If you're already tracking me and every single one of my digital activities through my devices, then at least give me some modicum of convenience from all the bother.