• Details
• Metrics
• Errors

Categories:

Free Tagging:

internationalization localization tapiji

Login or register to tag items

TapiJI represents a set of smart tools that integrate into the Eclipse IDE for Java developers with the goal to reduce effort of Internationalization. This is accomplished by creating a productive environment for building multilingual applications. In practice, Internationalization based on the basic Java API is a tedious task and introduces additional complexity into development. For example, typical faults are:

• The export of culture-neutral configuration strings
• The incomplete export of constant string literals
• To hard code constant string literals
• To build static format strings and
• To reuse externalized literals in different contexts

These problems are eliminated by making tasks of Internationalization transparent. Even developers with less experience in developing multilingual applications are permanently advised to ensure high and constant code quality. Hard coded cultural aspects as well as broken Internationalizations are reported to the problem view and can be immediately resolved with a rich set of quick fixes.

At the current stage of development, assistance is especially implemented for the Eclipse integrated Java editor as well as the XHTML/JSF editor of the WTP project. But tooling-architecture is designed with openness in mind and so support can be easily extended to other editors too. Further contribution is provided by a separate Resource-Bundle editor. The traditional way of editing Resource-Bundles in Eclipse is the use of the Property-File editor. This editor is not particularly suitable since its primary focus is to edit configuration properties. It therefore is not aware of multi-lingual aspects of Resource-Bundles and doesn't consider aspects like:

• Handling of none-ASCII characters
• Different text-directionalities
• The translation of long text-fragments
• Simultaneous loading and synchronization of multiple property files of a Resource-Bundle

The implemented editor is based on the Essiembre Resource-Bundle editor, which considers the whole Resource-Bundle as the object under modification instead of a single property file. Furthermore, a Resource-Bundle view adds rich functionality for browsing resources and directly comparing different languages. In parallel, an RCP based stand-alone application enables the translation personnel to translate resources without the need of programming skills.