why are website language switchers in the current language?
-
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.
-
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.
Valid comment to some degree, but putting language options in the selected language is always dumber than providing them in the only world language.
-
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.
Which flag do we use for English?
I won't allow the stars and stripes
-
that's all fine and dandy until you get a porch of geese angry at you for using the brazilian flag or vice versa
They're going to hiss at me aren't they?
-
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
I mean, if they insist on everything being in Dutch then at least include a flag. If you're going this deep on the UK obviously having the list in the native language is preferable.
The reason for the list above being all in Dutch might be because it's a list of countries, not a list of languages. (I speak some Dutch)
-
Which flag do we use for English?
I won't allow the stars and stripes
Have different locales for uk and us
-
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.
Haha, to avoid exactly this conundrum we prefixed languages with their iso code in a dropdown. So DE - Deutsch or EN - English.
-
Which flag do we use for English?
I won't allow the stars and stripes
I have seen at least one site where they used the English flag. Luckily I have watched the European Cup a few times and could recognize it.
-
Valid comment to some degree, but putting language options in the selected language is always dumber than providing them in the only world language.
Nobody's arguing that it's the right way to do it, we're just saying that breaking out words like "dumb" after the fact from the comfort of our keyboards, over problems that aren't necessarily obvious at development time if you've not had i18n training, is kind of harsh.
-
Which flag do we use for English?
I won't allow the stars and stripes
Zimbabwe obviously
ah fuck -
Nobody's arguing that it's the right way to do it, we're just saying that breaking out words like "dumb" after the fact from the comfort of our keyboards, over problems that aren't necessarily obvious at development time if you've not had i18n training, is kind of harsh.
The only thing I know about i18n is that it is an annoying shitload of language installer packages for both firefox and libreoffice ^^
That said, however, how you need training for a localization package to provide a language menu(!) - not the translations, mind you - in English, is beyond me. I can't follow the point you seem to be trying to make.
There's no reason to not hardcode (in English) a language selection menu, and then display the list of available site languages (and these should be a country flag with the name of language next to it in what may be the language itself) -
Best answer up to this point
-
Which flag do we use for English?
I won't allow the stars and stripes
Every time I make a tool like this, I try to wind up any Americans in the company by putting the US flag as
English (simplified)and the Union Jack asEnglishIt's a fun back and forth we have switching it between the two (inevitably someone makes a PR to put it back, and we go on)
-
Out of curiosity, would you put Deutsch before or after 日本語?
Since we're using Unicode we sort by first on left to right or last letter on right to left languages by their code point
