Adding New Language Translations

You can create your own translation if you need to provide users with a language that is not 1 of supported languages.

The content translation occurs outside the Archer application, so the translator does not need to be an Archer user. After the translation is complete, the translator returns the language file to the same access location so you can import it into Archer.

Translation String Formats

You can export and import translation strings in both CSV and ResX formats.

The following table describes each format and its recommended use.

Format	Description	Recommended Use
ResX	ResX export includes resources from the database in the industry standard ResX format used by professional translators. This format is difficult for manual translations. ResX import does not include an indication of which values were translated.	Use ResX for full translations sent to professional translators.
CSV	CSV export includes resources from the database in an easy to use table format. CSV import includes a column for the design value and a column for the translated value to show which values were translated.	Use CSV for partial translations or translations not sent to professional translators. This format enables the translator to choose from a variety of software tools to complete the translation.

Task 1: Add a new language

1. Go to the Manage Languages page.

   1. From the menu, click .
   2. Under Globalization, click Languages.
2. Click .
3. In the General Information section, enter a name and a description for the new language.
4. In the Options section, do the following:
   1. Click Active.
   2. In the Locale(s) section, select the locales that you want to assign to the language.
5. Click Save.

Task 2: Export the language file for translation

1. Go to the Manage Languages page.

   1. From the menu, click .
   2. Under Globalization, click Languages.
2. For the language you want to export, under the Actions column, click .
3. In the Generate File for Translation dialog, do the following:
   1. Select a Translation Object.
   2. Select an Export Format.
   3. Click Export.
4. When the Export completes, click .
5. Use the Web browser to save the downloaded file in a specific location.

Task 3: Translate objects into the new language

1. Move the downloaded language file to a location that the translator can access.
2. For every property name in every CSV file, ResX file, or both that you exported, have the translator provide a Translation Value. For a completed example, see Translated File Example.
3. Using the default Windows file compression utility, zip all translated CSV files, ResX files, or both, and the original manifest into a zip file.

Task 4: Encode the translation in UTF-8

Note: This step is only required if the files that you receive from the translator are not already encoded in UTF-8.

1. Extract the translated .csv or .resx files from the ZIP file you received from the translator.
2. Open a CSV or ResX file in the Windows Notepad text editor application.
3. In the File menu, click Save As.
4. From the Save as type list, select All Files.
5. In the File name box, ensure that the file name extension is .csv for a CSV file, or .resx for ResX.
6. From the Encoding list, select UTF-8.
7. Click Save.
8. Compress all encoded UTF-8 CSV or ResX files in a .zip file in the same folder in which you extracted them.

Important: Be sure to include the same manifest file created in the original language export.

Task 5: Import the translation

Translated characters in the returned CSV or ResX files must be encoded using the UTF-8 character set. If the returned CSV or ResX files do not use UTF-8 characters, the import will not work, or might result in some unintelligible characters appearing after the import process completes. UTF-8 is a comprehensive character set that accommodates most languages, whereas many characters are not found in ASCII or ANSI.

Consider the following before importing translated languages:

• You must import the translated language files into the same instance of Archer platform from which the language was exported for translation.
• You must use the default Windows file compression utility to create the ZIP file that contains the translated language files to import.
• The translated language ZIP file that you import must contain all the files that you originally exported. These files include the CSV or ResX files that were updated with the translations of the translatable properties, as well as the manifest file.
  • The CSV and ResX files and the manifest file must reside in the same folder from which they originated.
  • All files must be correctly formatted.
• Translator responsibilities are as follows:
  • The translator must update only the Translated Value column in the CSV or ResX file.
  • The translator must ensure that property names with associated translated text appear in the Translation Value column of the CSV or ResX file. For more information, see Translated File Example.
• Depending on the size of the ZIP file and the attributes of your Archer environment, the import process can take several minutes to complete.
  • On the Manage Languages page, during installation, the language has a Pending status.
  • If the import fails, on the Manage Languages page, the language has a Failed link. Click the link to display information about the failed import.
  • When the import process is complete, an email notification is sent.

Note: You must import the translated language files into the same instance of Archer from which the language was exported for translation.

Procedure

1. Go to the Manage Languages page.

   1. From the menu, click .
   2. Under Globalization, click Languages.
2. For the language you want to import, under the Actions column, click .
3. Do 1 of the following:
   • Drag and drop the translated language ZIP file.
   • Click Browse.
     1. Navigate to the translated language ZIP file to import.
     2. Select the file.
     3. Click Open.
4. Click Import.
5. Activate the language.