why are website language switchers in the current language?
-
And if they're all displayed in their own language?
byte order, nobody is happy but at least it's sort of equitable
-
What flag is for English? What flag is for Portuguese? What about Austria, do they got a language? What do we put under Chinese flag, Mandarin? Where do Cantonese go? Oh, what about Belarusian? There are at least three options, and two could get you in jail, choose carefully.
I'm just telling you what I've seen used. Typically it's a lot of European flags for languages that originate in Europe. So UK for English, German for German, French for French, Spain for Spanish. Belarusian would be the flag of...Belarus? Not sure why that's a challenge.
To your question about China - What should be used for Swahili? What should be used for Yarouba or Hausa or Shona or Chewa? Africa is the problem, and so the typical method for doing this is very Euro-centric.
-
Is that real?
It's Dutch uwu speak, but the real version would not be much better:
"Oeps! De trein is stuk. Wij zijn heel hard aan het werk om dit te maken. Misschien kan je beter fietsen."(Oops! The train is broken. We're working very hard to repair it. Maybe you'd be better off biking.)
-
There are some German dialects that only survive (barely) in Brazil.
And the German language is much older than Germany.
German dialects are still....German language, yes?
-
We're saying, don't translate the language's names at all, use what the speakers call their own language.
English is always "English" regardless of UI language. French is always "Francais", Then you can switch to any language you can read
Yeah, and the comment you just replied to said: why not both? Language name in language up front, and language name in current language in parens. I think it's a neat idea and absolutely would support that as a standard.
-
Yeah, and the comment you just replied to said: why not both? Language name in language up front, and language name in current language in parens. I think it's a neat idea and absolutely would support that as a standard.
My big question would be what would that add? If you speak Japanese, Spanish and French, 日本語, Español and Français would give you all the information you need. Adding the language name in a second language would increase the work to do, while also not really providing any benefit that I can see. If you manage to change the language to Spanish, or are using somebody else's device, "English" is no less helpful for you than "English (Inglés)" would be.
-
Plus how do you end up in a country selector list in a language you don't understand?
By clicking random buttons hoping to find the one that changes the language to one you can understand?
Sure, but that's a problem with the language selector setting, as I said above, not with the country list.
-
Why not do both tho?
Like "日本語 (Japanese)”
So that if I fuck up my languages for some reason, I can turn backBut you can. Hopefully, you know how your language is called in your language, right?
-
No, flags for languages are a bad thing.
- If you put a Swiss flag, what language would it be? (They speak 4 languages in Switzerland)
- What flag would you use for English? The UK? The US?
More details here: https://localizejs.com/articles/why-using-flag-icons-can-confuse-your-users
You use both obviously
-
German language as we know it now, predates Germany by at least 500 years, originated, roughly speaking, in the area that is now Germany, Austria, Switzerland, and in small part Belgium and Netherlands.
It only simple and easy if you don't know about it and don't care. But people who use the language, surprisingly, do care.Please try and look at this as a reasonable person.
Do you go to Italy, see a QR code on a table in a cafe, and berate them about their online menu showing an Italian flag, but the Italian language predates the Italian Republic?
It's simple because this is someone coding a site in one language, and then likely running it through Google Translate to get other options. Maaaaybe with a single human reviewing it of they're lucky. But likely not even that.
Not every website has a translation team of 20 or 30 PhDs working to ensure optimal linguistic understanding and anthropological and historical accuracy. Likewise, no, I'm very sorry to tell you that people very often don't really care about others. If pay 3 people in India, or ask an LLM, to code a website with German translation, either the drop down will say Deutsch or it'll say that and have a German flag. What should Austria have, a tiny picture of Mozart but the site is still just German?
-
No, typically they aren't, and if they do it's a bad idea. Only 4% of L1 Portuguese speakers live in Portugal. There is 4 languages in Switzerland. German originated in at least 3 countries. USisans will throw a hissy fit if they will have to click on anything but their favourite star spangled banner for their language.
It's a mess.I'm not saying it's a good idea, i just see it a lot. Maybe I'm only paying attention to this in Europe, where it's a bit more clear-cut, rather than tracking down population data to select a template option on a website for something like a cafe menu.
-
I'm pretty sure nobody's doing that based on geoip. Client-side, the browser exposes the user's languages choices. And server side, the HTTP header can help. But geoip is totally unreliable, even a broken salesman would not sell that as a feature.
Well ok they would sell it but get a very heavy glance from the dev team.
Have you used the web and/or VPN lately? I send the language header but am bombarded by content in the wrong language all the time.
-
Sure, but that's a problem with the language selector setting, as I said above, not with the country list.
Ah, sorry, didn't catch the country part.
-
The label for the language picker is an issue, but the choices themselves? In the target language. You want French? You pick "Français". You want Japanese? You pick "日本語". You want english? You pick "English".
Supposedly, if you'd rather have a website in a given language, you must have some level of understanding of that language, and picking its name should not be a challenge in any case. If you somehow change a site/app to a language you don't know, as long as you can identify the language picker, you'll be able to change to something you understand.
It does leave out the case of a user wanting to change to a language they do not understand, but I do not care for those.
Perhaps a universal icon for "pick language" would be helpful, like we have a icons for volume control and share. Good luck getting it adopted though.
-
It's Dutch uwu speak, but the real version would not be much better:
"Oeps! De trein is stuk. Wij zijn heel hard aan het werk om dit te maken. Misschien kan je beter fietsen."(Oops! The train is broken. We're working very hard to repair it. Maybe you'd be better off biking.)
Dutch uwu speak
Logically, it makes sense that this exists, but still not something that I've ever thought about.
-
byte order, nobody is happy but at least it's sort of equitable
wrote on last edited by [email protected]Byte order in which Unicode encoding? UTF-16LE?
-
The scrum master is not a product owner and shouldn't be providing scope or anything for that matter in tickets. No wonder agile is hated and dying, it's been corrupted beyond recognition by people who have no reading comprehension.
No wonder agile is hated
I think that the basic ideas are reasonable. Keep in touch with your team and evaluate the current situation, track progress, stuff like that.
It's just that the excessive codification of the practices becomes overbearing.
-
My big question would be what would that add? If you speak Japanese, Spanish and French, 日本語, Español and Français would give you all the information you need. Adding the language name in a second language would increase the work to do, while also not really providing any benefit that I can see. If you manage to change the language to Spanish, or are using somebody else's device, "English" is no less helpful for you than "English (Inglés)" would be.
wrote on last edited by [email protected]Easy enough. Tells you what languages are supported. Also helps you debug a bad language label. Although does have the disadvantage that you still need the name of every language in every language (the existing state) and you don't get to suddenly sqrt your data requirements for storing that
-
This always annoys me. I land on a site that's in a language I don't understand (say, Dutch), and I want to switch to something else. I open the language selector and... it's all in Dutch too. So instead of Germany/Deutchland, Romania/România, Great Britain, etc, I get Duitsland and Roemenië and Groot-Brittannië...
How does that make any sense? If I don't speak the language, how am I supposed to know what Roemenië even is? In some situations, it could be easier to figure it out, but in some, not so much. "German" in Polish is "Niemiecki"...
Wouldn't it be way more user-friendly to show the names in their native language, like Deutsch, Română, English, Polski, etc?
Is there a reason this is still a thing, or is it just bad UX that nobody bothers to fix?
You don't speak dutch? 🤮
/S
-
No, typically they aren't, and if they do it's a bad idea. Only 4% of L1 Portuguese speakers live in Portugal. There is 4 languages in Switzerland. German originated in at least 3 countries. USisans will throw a hissy fit if they will have to click on anything but their favourite star spangled banner for their language.
It's a mess.USisans will throw a hissy fit if they will have to click on anything but their favourite star spangled banner for their language.
I thought you were trying to convince us not to use flags
