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?
I’ve seen language switchers with translated language names that were sorted by the English name. So “Deutsch” was sorted under G.
Yeah that happened on Microsofts knowledgebase sites for years…
So annoying. But cant blame such a small company for not fixing that, they probably couldn’t afford to fix it /s
It’s not my fault if the Scrum Master can’t provide a proper scope in the ticket. They said change the names, not the sorting.
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.
The product owner often doesn’t understand technology well enough to know that mapping labels and sorting are different. They don’t know what they don’t know. The SM needs to help bridge that gap.
Sure, part of the job of the SM is to teach a PO that they need to research the market, but bridging the gap sounds like your saying the SM should find these things out for themselves and that’s just not true. The SM by definition is less technically minded that the PO. They deal with processes, data and people, not with product specs and market research.
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.
True, what you described is basically all there is to it, but in my opinion the corrupted versions where the SM is doing backlog management or where the rest of the company structure doesn’t change just the dev team are more damaging than the more codified versions of it.
Out of curiosity, would you put Deutsch before or after 日本語?
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.
Haha, to avoid exactly this conundrum we prefixed languages with their iso code in a dropdown. So DE - Deutsch or EN - English.
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
What language would you sort them by?
If everything is displayed in the same language then sort by the displayed language. You don’t want to have to search for Spanish near the E letter because it’s sorted by the original espanol in the background since that’s not what you as the user sees.
And if they’re all displayed in their own language?
byte order, nobody is happy but at least it’s sort of equitable
Byte order in which Unicode encoding? UTF-16LE?
Why would anyone pick UTF-16LE? All the disadvantages of UTF-8, none of the advantages. The only reason to use it is when dealing with legacy systems that used it.
Code point order would be somewhat decent, but even better is to use the user’s chosen coallation order from their locale settings if possible.