CODEWITHSUNDEEP
javainternationalization
Jonathan Solorzano
Jonathan Solorzano

Reputation: 7032

Internationalize a Java Application?

I have a Java Desktop App, the users of the application have the availability to set the aplications language.

By now i manage it in the database, i call the value of a field called - userLanguage - which is an Integer, and when the user has logged in depending on this value i set the corresponding text to each element on the app by using a switch ( case 1: set labels text ENGLISH, case 2: set labels text SPANISH ... etc)

But i've heard that control the language from the database is an insult, and i would like to know which's a nice way to do it, or what's the best way to do so, it doesn't matter how difficult it would be but the efficence of the method to internationallize an app is what metters for me.

Upvotes: 0

Views: 144

Answers (3)

Paweł Dyda
Paweł Dyda

Reputation: 18662

You've received two answers, both of which are plainly wrong. If you have Java Desktop Application, you should this code:

Locale locale = Locale.getDefault(Locale.Category.DISPLAY);

This will give you valid User Interface language for your application - the one user set in his OS preferences. If you want to keep the language in a database or in some kind of preferences, you'll be forcing users to chose language. What for? I've already set what language I want. If you don't have it, let Java fall back to your application's default.
In case you wonder, if you use ResourceBundle, the default would be the one without a Locale in its name. That is unless you override this process by using custom ResourceBundle.Control.

Upvotes: 0

Evandro Pomatti
Evandro Pomatti

Reputation: 15144

Java Preferences is what you are looking for then.

Or, instead of using XML file you can use Properties.

...i've heard that control the language from the database is an insult...

I do not agree with that. I think it is scenario dependent, and in your case I think you should keep it the way it is to avoid unnecessary work, unless there is an absolute need for keeping the preferred idiom outside your DB.

Upvotes: 1

HowYaDoing
HowYaDoing

Reputation: 862

I would actually handle this problem using the Java Preferences. It keeps the preferences for each user separately in a system independent way (for you at least). If you use XML you need to create a SAX/DOM parser or if you use a DB you need to use jdbc. Neither XML or the DB is a bad or a tough solution, I just think the preferences are the easiest.

For internationalization, I would use a ResourceBundle that localized for different Locales. It is a pretty big topic see The Java internationalization (I18n) tutorial

Upvotes: 1

Related Questions