Translating Methods

There are two methods available in Unifier for translating custom strings:

• User Interface

  Use this translation method when you add or modify a limited number of custom strings, only.

• Export/Import

  Use this translation method when you need to translate a large number of custom strings. This method is particularly useful to professional product-translator because the system provides a file format (.XLIFF) that streamlines the translation efforts (Export). After the translations are completed, the Company Administrator, or a User with appropriate permissions, can access the Internationalization node and import the translated file back into Unifier (Import). The translation is done for one language at a time.

To use the User Interface translation method

1. Go to the Internationalization node.
2. Select the custom string that you want to translate.
3. Click Open from the toolbar to open the Modify Translation String window. The Source Type and Source String fields are read only.
4. In the Note field enter a description explaining the context and usage of the custom string that you are about to translate.
5. Modify, or add to, the existing translations. You can enter multiple languages for the custom string.
6. When finished, click Apply and then OK.

About Source Type and Source String

Each custom string is unique according to the custom string Source Type and Source String. The Source Type displays the Source String category. Data Structure, uDesigner, and Reports are some of the options under Source Type.

Example

A designers designs a Data Element (DE) with the label: Vendors. The Business Process is also name: Vendors. Since both the DE and BP constitute a design element, the Source Type is: uDesigner.

Language codes

Use the following information to match the language settings:

• Chinese (Simplified): zh_CH
• Chinese (Traditional): zh_TW
• English: en
• French: fr
• German: de
• Italian: it
• Japanese: ja
• Korean: ko
• Portuguese (Brazil): pt_BR
• Russian: ru
• Spanish: es

To use the Export/Import translation method

1. Go to the Internationalization node.
2. Select the custom string that you want to translate.
3. Click Export from the toolbar to open the Export Options window.
4. Select values for the following fields:
   • Source Language

     The current language of the custom string. (Example: English)

   • Target Language

     The language that the source custom string has to be translated into. You can select one language, only. (Example: German)

   • Source Type

     To allow you to filter the custom string for export base on a particular Source Type. The drop-down list contains values such as: Data Structure, Reports, etc. (Example: Business Process Setup)

   • Include Translated Strings

     This is an optional parameter. By default, this option is selected.

     - If selected, the custom strings (source strings) that are currently translated into the selected language will be exported, also.

     - If deselected, only the custom strings (source strings) that are not translated into the selected language will be exported.

5. Click Export to open the File Download window. The file download operation follows the Unifier standard file download process.

   The exported file is in ".XLIFF" format and the file name contains "Unifier" (Unifier+-+<Language Name>.XLIFF).

   The number of characters allowed in the file name is based on Unifier standard. For supported version of the "XLIFF" file refer to the Primavera Unifier Tested Configurations in the Primavera Unifier Documentation Library.

   The exported file contains the following information: ID, Source String, Target Language, and Note.

   The Source String is the base for all translations, the Target Language is the language selected, and the Note is a placeholder, which stores notes for the translators. The source language attribute for the exported file originates from the Source language selection at the time of export.

6. Save the file in your local folder and open the file using a program such as Notepad or WordPad.
7. Open the saved XLIFF file, review the declaration information, and search for <source>. Example:

   <source>Assets</source>

8. Enter a new line, include the target language information, and save the file. Example:

   <target>Aktiva</target>

9. Change the value of "approved" to "yes." Example:

   <trans-unit id="o8oRKk8ZYDv+BJodINqTIBpmz+fhygs3" approved="yes">

10. Proceed to import the file back to Unifier.

When the file is ready, use the Import option to bring the translated file back into Unifier.

1. Go to the Internationalization node.
2. Click Import from the toolbar to open the Unifier standard File Upload window.
3. Click Browse, and import the translated file (Unifier-,Language Name.XLIFF). Basic file replacement and override apply.

At this point, the translated custom strings map to the appropriate language settings and ready to be used.

Note: The Oracle Database column size must not exceed the storage size of 4000 bytes.

See Also

Translating Custom Strings (Internationalization)

Internationalization Node Properties

Displaying Custom Strings and System Strings

Assigning Permissions

Internationalizing Unifier Environments

Legal Notices | Your Privacy Rights
Copyright © 1998, 2020

Last Published Monday, October 4, 2021