Work with Translation Files
Translate metadata labels or data translation text, or review existing translations, with XML Localization Interchange File Format (.xlf) or Salesforce Translation Format (.stf) files.
Required Editions
| Metadata translation available in: Salesforce Classic and Lightning Experience |
| Data translation available in: Lightning Experience |
| Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions |
| Data translation applies to: B2B Commerce |
Translation files can contain metadata translations or data translations. Metadata translations are for customizations that you made to your Salesforce organization, such as custom picklist values and custom field labels. Data translations are for the data stored within fields, such as the text in the Product object’s Name and Description fields.
For metadata and data translation files, there are three file types.
- Source: Use to translate labels for the first time.
- Outdated and untranslated: Use to translate labels after the first translation pass.
- Bilingual: Use to review and edit translations.
Translation files are identified with either the .xlf or .stf extension. Salesforce recommends the XML Localization Interchange File Format (.xlf) for translation files.
- Considerations for Working with Translation Files
Review some important considerations to ensure that your edited translation file can be successfully imported. - Source Translation Files
Use the Source file to translate an organization's labels or data for the first time. The Source file contains labels for all of a Salesforce org's translatable metadata or data in the org's default language. - Outdated and Untranslated Translation Files
Use the Outdated and untranslated file to translate labels or data that need translation. The file includes labels or data changed since the last translation and labels that haven't been translated. One Outdated and untranslated file is generated for each language. When multiple files are generated, they're exported to a .zip file containing a file for each translation language. - Bilingual Translation Files
Use the Bilingual file to review translations, edit existing translations, and add translations for labels or data that haven't been translated. One Bilingual file is generated for each translation language. - Translation File IDs and Keys
Each translatable item has a unique identifier in the translation file. In .xlf files, it’s the id within a trans-unit tag. In .stf files, it’s the key. The structure of these identifiers differs for metadata and data translation files. - Flow Identifiers in Translation Files
In a translation file exported from Translation Workbench, a unique key or trans-unit ID attribute identifies a flow metadata label.
