(Show Contents)

Greek Testing a New Application or Extension

If you have written a new application or extension, the first step to localizing it is to Greek test it, that is to substitute strings that contain dummy translated characters and then to test the application's functionality. The test shows if you have tagged all visible user interface strings as translatable, and if your application's functionality works on special characters, such as U's with umlauts or Chinese ideographic characters.

Within larger teams, it is a best practice to have the integrator who created the extension perform the Greek test before the localization process starts. This practice avoids many trivial errors that can require much back and forth between engineering and localization staffers.

To test your application or extension, you use the Technologies/Localization/Greek All Localization Tables action. This action has commands for reading your application strings into the localization kit, "greeking" the strings to perform a mock translation, and then publishing the localized application (that is, publishing the mock-translated database strings and the mock ".lang" file). The mock translation appends specialized European or Asian characters, or both, to each of the strings of your application.

You then walk through the application to:

• Review screens: Any string that appears in "un-Greeked" English was not properly tagged as translatable.
• Test functionality: Perform tests on the specialized European or Asian characters to make certain that your application's logic works on these characters. In particular, test any application-specific features that compare or sort strings.

To perform a Greek test:

1. Read strings from your .axvw, .js, and .java files. See Reading or Writing Translatable Files.
2. Add the translatable tables to the localization tables. See Reading or Writing Translatable Tables.

   All of the strings in your application's user interface are in the localization kit and will be Greeked. Therefore, when you are testing, any field that is not Greeked has an error.

3. Create a "Greeked" version of your strings:
   1. Select the Greek All Localization Tables task.
   2. From the Language list, select the target language. See About the Language Selection.
   3. Select to use European characters, Asian characters, or both in the Greek test.
   4. Click the Greek Localization Tables button.

      The strings are created with the selected special characters added.

4. Write the "Greeked" strings to the program:
   1. Select the Read or Write Translatable Tables task. See Reading or Writing Translatable Tables.
   2. Click the Write Tables button.
   3. Select Read or Write Translatable Files. See Reading or Writing Translatable Files.
   4. Click the Write Files button.
5. Test your application.
6. If the application passes the Greek test, then substitute the real translations for the "Greeked" strings.