Developers
Features for Developers
Eclipse Quneiform® provides numerous tools for analyzing your project at every stage of internationalization. At the initial stage, Quneiform will analyze your source code to uncover various problems. This can include issues such as function misuse, strings not exposed for translation, etc.
At the next stage of i18n, resource catalogs can be analyzed to find issues with the translatable content. Issues here can include confusing messages, concatenated string, and strings that probably shouldn’t be in the resources.
Once your resource catalogs are ready, Quneiform can pseudo-translate them for integration testing. During pseudo-translation testing, display issues, missing content, and even program instability can be uncovered. By performing these tests, your product will be l10n ready before translator hand-off, saving both time and money.
Source code analysis
Detect bad practices that can lead to truncated content, display issues, and program crashes.
Modernize your application
Find and upgrade legacy issues in your code base and resources, such as the use of TCHAR functions or half-width Kanas.
Proactive resource analysis
Detect resources not available for translation, confusing messages, and l10n-unfriendly strings prior to translator hand-off.
Pseudo-translation testing
Pseudo-translate resources to perform integration testing before translation even begins. Numerous options are available for pseudo-translations, such as:
- multiple replacement character sets to choose from
- string length widening
- unique IDs prefixing
- surrounding brackets