Internationalization of the UI

[javadch]

Is there any settings, feature, or hidden feature to enable internationalization, e.g., right-to-left UI, multi-language interface, language selection for the end user either for the whole client or per account?

[chylex]

The app is based on TweetDeck which doesn't support any other languages, but even it did I found that accepting community localization and then maintaining it is too much overhead for me. Your best bet would be forking the project, localizing it, and releasing your own version for those who need it.

[javadch]

I can possibly do that and have already forked it. However, I need some guidance. Can you guide me through the steps I need to follow to localize the Winforms, the browsers, and the resources?

[chylex]

I don't have experience with .NET's internationalization. I can tell you about some things TweetDuck does right now, but usually to prevent default i18n rules.

• https://github.com/chylex/TweetDuck/blob/master/lib/TweetLib.Core/Lib.cs changes default culture of every thread to "invariant". The main reason for that is to stop .NET from localizing exceptions, since often I'm the one who has to read them, and even though I speak several languages the localized exception messages are useless to me even if I understand them. However this also affects which i18n rules are used for displaying things like numbers. The actual default culture is preserved in Lib.Culture and used in places that need to take into account the system language, but you will have to figure out if that's enough or you will want to stop TweetDuck from changing the default.
• In JS, you would I think use navigator.language to get the browser language, but that might also be affected by the previous change of defaults. I can't remember or find anything that changes the browser's language specifically, so you will have to check CefSharp's APIs or test whether default culture affects it.
• Since TweetDuck is not localizable, all strings are hard-coded in forms, browser scripts, official plugins, error messages, etc. I don't know the best way to do localization when you have so many separate components and technologies.