18 ms·
I'm non-native English speaker and all my software is in English. Still I understand why developers/publishers want to default to my local language. It all dep
by zokier 15y ago
I'm non-native English speaker and all my software is in English. Still I understand why developers/publishers want to default to my local language.
It all depends on your target demographic. If you are targeting young, geeky people then it's OK to have English around. But if you are targeting every joe sixpack and grandma, then it's probably smarter to present localized versions.
Optimum of course would be to query the underlying platform for locale information. That way everybody gets what they want almost always.
And while we are talking about localization, I need to point out that localization is much more than just translating the UI texts. It also includes stuff like date and number formats, correct units, and lots of other stuff. I'd even argue that those are more important than translations.
- Snoddas 15y ago"Optimum of course would be to query the underlying platform for locale information. " - This isn't true. Most people are not in control of that. For many many years I had to work on Swedish version of windows, because that is what the company paid for. But that doesn't mean I want my CD-burner application or whatever to talk to me in "bad" Swedish. Never mind trying to Google localized error messages, that's a another pain I'd rather be without.
- zokier 15y agoThat situation has somewhat improved in Windows 7. In Enterprise and Ultimate editions users may choose their language freely, and MS docs are bit unclear, but apparently there is Language Interface Packs for other editions too. And I think system locale is settable even without the corresponding language pack, but I'm not sure what it actually does. But yes, I forgot that in Windows language settings are bit strange.