Salesforce Multi-Language Translation:Translation WorkBench

Salesforce Multi-Language Translation: Translation WorkBench

Import

Create Separate Language Files: Utilize the XML Localization Interchange File Format (.xlf) to create individual files for each language. For .stf files, specify the language code at the beginning of the file.

Language Specification: Ensure language specification within each file. For .xlf files, utilize the target-language attribute, while for .stf files, include the language code.

Translation Attribute Inclusion: If data translation is enabled, incorporate the appropriate translation type attribute in each file, specifying whether it pertains to metadata or data.

Encoding and File Size: Save all import files in UTF-8 encoding. Additionally, adhere to size limitations, with metadata translation files limited to 10 MB each, and data translation files limited to 50 MB each.

Bundle into .zip Files: If necessary, bundle multiple files into .zip archives. Ensure each .zip file contains either metadata or data translations exclusively.

Import Process: Access the Translation Workbench in Salesforce Setup to import prepared translation files. Choose the file, click Import, and wait for the process to complete. A confirmation email is sent afterward.

Error Handling: In case of import failures or exceeding import limits, the confirmation email provides details on the affected files.

Verification of Translations: After import, verify translations by checking metadata labels and data translations within the Salesforce org. Utilize Translation Workbench or the Translation tab within Product. Export data translations for further verification.

• Step 1: Click "Import" is Translation Workbench

• Step 2: Click "Choose file" which will navigate to your Localization

• Translation Attribute Inclusion: If data translation is enabled, incorporate the appropriate translation type attribute in each file, specifying whether it pertains to metadata or data.

• Step 3: Choose the Translated Zipped folder.

• Step 4: Then click "Import" to import the files.

• Step 5: Upon successful completion, a Success message will be displayed on the screen.

• Step 6: In case of import failures or exceeding import limits, the confirmation email provides details on the affected files.

• Step 7: Make the corrections and import files containing fields that have not been translated properly.

Limitations Of the Translation WorkBench

Manual Input Requirement: The Translation Workbench lacks automatic translation features, necessitating manual input for each translation. This manual process can be time-consuming, especially for larger organizations.

Deleting Translations: Deleting a translation value, row, or trans-unit tag in the file doesn't remove the translation after importing. To delete the translations, replace the translated text with placeholders such as file name .stf files or file name .xlf files. Upon import, label reverts to its original value.

Data Translation Export Limits: Data translation export the requests capped at 1 GB of data and 100,000 records. Exceeding these limits results in only a partial file is being exported. To manage this, utilize the language filter for Outdated and translated and Bilingual export types or consider using BULK API for organizations with translations surpassing the limits.

File Size Limits: For metadata translation files, individual uncompressed files are restricted to 10 MB each. While zipping data translation files during import, each .zip file can contains up to 100,000 translation records within up to 2 GB of uncompressed files.

Unique Keys in Translation: During translation, Salesforce generates unique keys or identifiers for each object, picklist value, or page element that are being translated. Altering these names or keys after exporting file can result in mismatches, where Salesforce cannot correctly associate the key with the corresponding name.