why are website language switchers in the current language?
-
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
-
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?
because most web developers are morons
-
Before, since D and G are both before N ("nihongo") and J ("japanese")
I think his point was that they are using different alphabets, and therefore can't be sorted "alphabetically"... there's no N or J in 日本語. In order to sort alphabetically, we would have to pick an alphabet, which will in some cases contradict the alphabet of the language's native speakers.
-
You use both obviously
Like this?
English
English (simplified) -
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.
wrote on last edited by [email protected]YouTube (and Google in general) has been horrible for multilingual users (and users who want to see content in a different language than the default for whatever country they're browsing from) for quite some time, but lately it's getting downright unusable without untranslator browser extensions.
-
What flag do you use for english ?
-
because most web developers are morons
It's more like "localization is hard and you have a week to add support for it"
-
It's more like "localization is hard and you have a week to add support for it"
Yes, this one. i18n was a three day training course at my last workplace, because things that seem really obvious if you’re an Arabic speaker browsing a Russian website, aren’t at all visible to the original developer who has their environment set to English, develops in English, puts all the frontend labels in a “messages” config file to be sent for translation by another department in another country, and will likely never even see the end result.
-
Probably not so funny other way around hah
It really isn't funny either way
-
It really isn't funny either way
I mean if it was done accidentally then the sheer shitshowyness of that blunder would be pretty funny to me
-
Yes, this one. i18n was a three day training course at my last workplace, because things that seem really obvious if you’re an Arabic speaker browsing a Russian website, aren’t at all visible to the original developer who has their environment set to English, develops in English, puts all the frontend labels in a “messages” config file to be sent for translation by another department in another country, and will likely never even see the end result.
The translators often have zero context and don’t know what the UI even looks like or what the software does.
-
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?
This should be a universal symbol. Like a flag in the corner you can pretty safely assume might be for language. And then yeah each language listed in that language.
-
It would be way more user-friendly to use the language in the HTTP headers. As a web developer the fact that websites are too stupid to do this really grinds my gears. This is just as bad as assuming the language/region from the geolocation of the IP address.
C’mon guys…
It wouldn't be too much work to hook the request language up to a CMS and then a translation service. You could produce in a couple of popular languages upfront and then when someone with a new language visits a landing page, translate it at high priority (few seconds), then the cascade the next most likely click-throughs in order of popularity (or callout weight if it's new). The translations can then be queued for review, and it will mean you only translate when you need to, and the user only experiences a second or so delay as the translation streams the content above the fold.
