For the purpose of Internationalization Java provides PropertyResourceBundle class. It's the most common way to implement Internationalization in Java. This class loads strings from locale-specific properties files and provides access to them.
Like many other companies we have also worked a lot with properties files in different internationalized projects. This experience allowed us to detect most common Java Internationalization problems, like:
- missing properties file for a locale, which is defined for other properties files
- same key defined twice in the single properties files
- properties files for different locales of the same resource bundle define different sets of keys
- wrong encoding of a properties file prevented usage of language specific symbol (like German 'ß' or 'ä')
- incorrectly used apostrophe in a string intended for MessageFormat class
- differently ordered keys in files of same resource bundle
- spelling errors
- recurrence typos like like here
- many more
Internationalization Inspector can detect them and provides possibilities to fix detected problems on the fly. After thorough inspection and processing of detected problems you can get your files with all the fixes. You can even integrate Internationalization Inspector into your unit tests in order to check the internationalization quality fully automatically during continuous integration.
Try Internationalization Inspector now!