A while ago we wanted to store internationalisation for a project in database to allow (a subset of) users to create and update internationalisation using the application itself. When we searched the web for existing projects that allow to do this we did not find a good and ready to use solution. This is why we decided to write the code ourselves and make it available to others, especially since there was some public demand and it will probably not be shipped by SpringSource (check out Google for details).
Tag Archives: i18n
Last week I spent some time hunting down an internationalization-issue that came along while developing for a recent project. Let me explain what happened:
Message-Lookup - of course - always stands together with Locales (
java.util.Locale) of the client the message is resolved for. The problem was, that messages for the English users were not resolved to the English translation, but to the German one.