Localization wizard
Step 4: Export Translations

Use this form to create the ZIP translation packs. The form displays a download button for each language. To create a package, do the following:

1. Select whether or not to include example files for translators.
2. Click theDownload for translation button to start the process, which can take a few minutes. During this time, the package components are assembled. When complete, the process creates a ZIP translation package.
3. Save the ZIP file to a local directory. Return to the Localization wizard and click the next download button if you are creating more than one package.
4. When you are finished creating your packages, click Next to update the wizard status in the Wizards in progress form. The confirmation form appears.
5. In the confirmation form, click Close to exit the Localization wizard.

About the ZIP translation package

The naming convention of the ZIP file is:

< Translation_language_ DateStamp_TimeStamp .zip >

For example: Translation_French_2007-04-27_14-27-01.zip

The file includes:

• A file named TextToTranslate.xml, which serves as the translator's worksheet. The contents of this file are used in the Localization wizard import process.
• An .htm file containing instructions for the translator.
• A folder for each correspondence, correspondence fragment, and HTML paragraph rule that contains HTML text. The text is located in a pair of .txt files within each folder. (The text is translated within the .txt files; not in the TextToTranslate.xml file.) To enable easy access, the XML file contains hypertext links to the text files.
• Folders containing graphics and HTML used to provide context examples for the translator.

Caution: When working with the contents in the package, always extract the ZIP file first. Do not work directly inside the file.

Before you send the translation package

Before you send the package to translators:

1. Make a copy of the package for reference and backup. You can rename the ZIP file or the top-level folder; there are no name restrictions.
2. Unzip the file and open the TextToTranslate.xml file using Microsoft Excel.
3. In Microsoft Excel, perform the following steps:
   • Delete rows that you do not want to translate.
   • Optional: To make it easier to read the contents of the cells, format the cells to wrap the text.
   • Hide the Key column to restrict access to the contents in that column. Be sure to communicate this restriction to your translator when you send the package.
   When you finish working in the file, save it and then zip up the folders so they are ready to send out.
4. If more than one translator is engaged in the project, make a copy of the entire package for each translator. In each package, delete the rows from the TextToTranslate.xml file and delete the .txt files that are not required for that translator, zip the folders, and send the appropriate package to each translator. When you get the files back, import each one separately.

Caution: Do not attempt to merge the TextToTranslate.xml files using Excel's copy and paste functions. Using Excel's copy and paste functions to merge the files might corrupt the format and cause the import process to fail.

Standardizing field values in the TextToTranslate file

As a best practice, review the list of field values in the TextToTranslate file to check for consistency and spelling. For example, assume that there are values for "forever" and "for ever", which you want to standardize as "forever." To do so, determine what rules reference these values.

• If the field value has an instance, (for example, a message label has RULE-OBJ-FIELDVALUE @BASECLASS PYMESSAGELABEL!FOR EVER #20070406T154426.215 GMT in the file's Key column) open the Field Value form and click the Related Rules button () to use the Referencing Rules tool.
• If the field value has no instance (for example, pyCaption forever is in the Key column), run the standard list view rule Index-Reference.ListReferencesForFieldValue. Enter the value from the key column (pyCaption forever) as the Rule Name parameter and click run.

After you have made your updates and saved the rules, go back through the wizard and recreate the package. To do this:

1. Select Designer Studio>User Interface > Localization Tools > Translations in Progress.
2. Click the Import item in the list.
3. In the wizard, click Back and create the package again.

Translating Calculation Builder function option text

When translating the text for the function options in the Select a function field in the Calculation Builder, do not change the values in the curly brackets. These values represent parameters used by pyPattern to display the Function input field that is displayed based on the function selected. If these values are changed, the fields to enter the values will not be displayed in the Function input field.

For example, for the following function:

• The difference in days between {Earlier Data Value} and {Later Date Value}

Translate only the text that is not in the curly brackets.

Translating HTML paragraphs and correspondence

Text used in HTML paragraphs, correspondence, and correspondence fragment rules is packaged in a pair of .txt files called Base.txt and Translation.txt. Both files initially contain the same text; the translator puts the translated text into the Translation.txt files. HTML paragraphs are imported into the localized ruleset like the text strings.

As a best practice, a localized application sends correspondence in the language of the recipient, rather than the language of the user. Typically these correspondence rules use circumstance properties rather than ruleset to identify the locale.

For example, a user may primarily speak in German but may create correspondence for a customer who speaks French. Rather than save correspondence rules in a localized ruleset, the application can use a circumstance property setting like .pyCustomer.pyCountry = FR to define localized variations of correspondence rules.

During localization, you must manually create the correspondence rules and copy the translated text from the Translation.txt file. Make sure that your translators are experienced with HTML coding. Tagging errors are likely to prevent the rules from working correctly.

Correspondence — Concepts and Terms About HTML rules

About the Localization wizard

Open topic with navigation