5 ms·

> It baffles me that there are still so many services that try to 'automagically' intuit which language someone wants to have a service in, instead of just simp

> It baffles me that there are still so many services that try to 'automagically' intuit which language someone wants to have a service in, instead of just simply .. asking. Well, because they should and rightfully so. You shouldn't have to select a language every time you start an app. Instead it should use whatever language was set on your system. Anything else just isn't intuitive and would add more friction before a user could get anything meaningful done. The parent comment was referring to Cortana only working with English and thus assumes the user can't speak English as he has his system set to Spanish. That's an unfortunate edge case but one that could be overcome with advanced settings should they want to deal with it. But again, the anecdote is an edge case and shouldn't be used to go against best practices in regards to localization.

mikeash 11y ago
Localization is all about edge cases, though. If you ignore edge cases, you'll ignore most world languages, after all. By all means, make a guess at what language to use, but always allow the user to choose in case you guess wrong.
- BinaryIdiot 11y ago
  > Localization is all about edge cases, though. If you ignore edge cases, you'll ignore most world languages, after all. The edge case of someone setting their device to a different language than the one they want to use in a specific application is not one of localization but of usability. > By all means, make a guess at what language to use, but always allow the user to choose in case you guess wrong. While I agree I wouldn't call it a guess as it's a setting a user set when setting up their device.
  - Livven 11y ago
    You make the problem sound more obscure than it actually is, which to be fair is very understandable (and I guess common) if you're from an English-speaking country. Many people outside of those know English well enough that they'd rather have a feature in English than not at all. Also, many if not most applications and services that aren't billion-dollar businesses or otherwise have had insane amounts of resources poured into them have terrible localization. And even if the localization is good, it can be beneficial to use the English version. English is the international language, it is taught to children all over the world, it is used in business, academia and so on, all over the world. You know that, everyone knows that, but sadly, to all-English dev teams, it is all too often an afterthought. And that doesn't even take expats, travelers etc. into account, who might want to use their native language system-wide but need certain applications to use the local language, or vice versa.
  - mikeash 11y ago
    I would say that UI language and speech input language are different enough that taking them to be the same would qualify as a good guess, not simply obeying a setting. Apple takes this approach with Siri, for example.
henry_vonfire 11y ago
I'm used to switch between three different languages to take advantage of the prediction thing in the default android keyboard and I think it's very comfortable, just one or two taps and you are ready to go.

mikeash 11y ago

Localization is all about edge cases, though. If you ignore edge cases, you'll ignore most world languages, after all. By all means, make a guess at what language to use, but always allow the user to choose in case you guess wrong.

BinaryIdiot 11y ago
> Localization is all about edge cases, though. If you ignore edge cases, you'll ignore most world languages, after all. The edge case of someone setting their device to a different language than the one they want to use in a specific application is not one of localization but of usability. > By all means, make a guess at what language to use, but always allow the user to choose in case you guess wrong. While I agree I wouldn't call it a guess as it's a setting a user set when setting up their device.
- Livven 11y ago
  You make the problem sound more obscure than it actually is, which to be fair is very understandable (and I guess common) if you're from an English-speaking country. Many people outside of those know English well enough that they'd rather have a feature in English than not at all. Also, many if not most applications and services that aren't billion-dollar businesses or otherwise have had insane amounts of resources poured into them have terrible localization. And even if the localization is good, it can be beneficial to use the English version. English is the international language, it is taught to children all over the world, it is used in business, academia and so on, all over the world. You know that, everyone knows that, but sadly, to all-English dev teams, it is all too often an afterthought. And that doesn't even take expats, travelers etc. into account, who might want to use their native language system-wide but need certain applications to use the local language, or vice versa.
- mikeash 11y ago
  I would say that UI language and speech input language are different enough that taking them to be the same would qualify as a good guess, not simply obeying a setting. Apple takes this approach with Siri, for example.

henry_vonfire 11y ago

I'm used to switch between three different languages to take advantage of the prediction thing in the default android keyboard and I think it's very comfortable, just one or two taps and you are ready to go.