Review:
This article discusses an interesting and slightly unusual approach to creating “localized” text in a midlet. Many times a midlet will need to support many different languages. In order to do this, the developer can hard-code all the menu options in some sort of data structure, such as a hashtable, and then retrieve the appropriate options at runtime. This approach has the disadvantage of increasing JAR size and memory usage. Alternatively, developers can use the approach described in this article, which creates a UTF-8 encoded resource file for each supported language. The appropriate file can then be loaded at run-time and the appropriate language displayed to the user according to his/her locale.
The author does a good job of motivating his implementation choices, and provides useful example code for creating the appropriate resource files (in Java SE) and reading from these files (in Java ME). The code examples are well written and clearly documented, making them fairly easy to understand. The advantages and disadvantages of this approach compared to other solutions to the same problem are also discussed and analysed. In summary, this is a well-written article which should be useful for anybody writing a midlet which needs to support multiple languages.
--Larry101 16:16, 23 September 2009 (UTC)