The Translation Request File contains the translation requests for one or more attributes for one or more records for a specific repository. The file name does not need to follow any specific naming convention since its contents are self-identifying but it is recommended as a best practice. Each file name should include the following information:
- Repository Name (for example Brand, SKU, or Item). There's no need to distinguish between Staging and Production since all translations should be performed on Staging only.
- Source Language Extension – if it is possible for anything but the default language (English) to be translated, the source language for the file should be included in the file name, such as fr, sp, or de.
- Target Language Extension – the extension of the target language, such as fr, sp, or de.
- Unique Identifier – A unique identifier to make the resulting file unique, such as Export Job attribute value.
An example file format would be: Brand_en_fr_12345.xlsx – which would indicate the file is for the Brand repository and contain values in English to be translated to French.
The request file must have the following columns:
| Column Name | Description |
|---|---|
| CN_Translation_Name | Name of the translation. This name is defined in the CN_Translation_Name column in the Change Notification Translation Registry. By using this name instead of the actual repository name, multiple translations can be defined for the same repository. For example, this may be necessary if there are multiple parts due to a large number of multi-language attributes (for example, Brand1, Brand2, and Brand3.) |
| CN_Attribute_Language | Extension of the source language (e.g., en, sp, de, etc.) |
| CN_Translate_Language | Extension of the target language (e.g., en, sp, de, etc.) |
| <primaryKeyAttribute> | One column for each primary key attribute, the column names containing the attribute name (instead of the generic such as PK1 and PK2). One column per attribute. |
| <descriptiveAttribute> | Optional descriptive attributes. Determined by the settings in the Translation Registry. One column per attribute. |
| CN_Attribute_Name | Name of the attribute to be translated |
| CN_Attribute_Value | Value that needs to be translated |
| Old Translated Value | [FUTURE] Current translated value for attribute (would be blank for new records). |
| CN_Attribute_Translated_Value | Translated value (populated by translation company) |
The following sample file shows translation requests from French to English:
The same file format is used for the translated files returned from the Translation company. The only difference between the two files is the request file will have an empty Translated Value column and the translated files will have it populated:
If a request file contains more than one multi-language attribute for the same repository record, the attributes must be in consecutive rows in the file. Otherwise the pivot pre-processing done for the translated files will contain more than one record for the same repository record, resulting in multiple updates, which includes multiple history records.
The Services Language Translation supports the translation of up to the number of multi-language attributes in a single repository determined by the following formula:
1,000 – (number_of_primary_key_attributes)For example, if the primary key for a repository being translated contains 3 primary key attributes, then up to 997 multi-language attributes can be translated in a single group. If there are more multi-language attributes in a repository, additional imports and exports can be defined to accommodate them. Each part must be defined as a separate translation (e.g., Brand1, Brand2) having its own Translation Registry entry, Scheduled Export, and Import Template. If the multi-language attributes are category specific, the number of attributes that can be included in a single import may be further limited.