Source Translation Files

Note Salesforce recommends the XML Localization Interchange File Format (.xlf) for translation files. See Considerations for Working with Translation Files for tips on editing translation files and how to translate rich text field content.

To prepare the translation file for your translators:

• Create one copy of the Source file for each language you’re translating into.
• In the header of each Source file, change the language code from the organization's default language to the translation language. For example, replace en_US for English (US) with es for Spanish.
• Ensure that the headers are in the organization’s default language. To confirm, export a translation file and copy the headers.

XML Localization Interchange File Format (.xlf) Source Translation Files

Source .xlf translation file content is organized into translation units. Translation units for translated labels contain a target tag with the translated value. Untranslated labels have a source tag, but no target tag.

Tell your translators:

• After each source tag, add a target tag that contains the translated value.
• If a target tag exists and the translation is out of date, replace the text in the target tag. Outdated labels have a value of outOfDate="true" within the trans-unit tag.
• When translating text in a rich text area field, include all HTML tags such as <p></p> and <b></b>.

Important A translated value for the data in the record’s Name field is required to translate data in other fields for that record. For example, you must provide a German translation for the name of a Product before you can translate its description into German.

For example, if you build a custom Nickname field on the Account object, the original file contains this trans-unit tag in the exported Source .xlf file.

<trans-unit id="CustomField.Account.Nickname.FieldLabel" maxwidth="40" size-unit="char">
    <source>Nickname</source>
    <note>The person’s nickname, or what they prefer to be called.</note>
</trans-unit>

To translate this label, add a target tag containing the translated value to the corresponding trans-unit tag after the source tag.

<trans-unit id="CustomField.Account.Nickname.FieldLabel" maxwidth="40" size-unit="char">
    <source>Nickname</source>
    <target>Apodo</target>
    <note>The person’s nickname, or what they prefer to be called.</note>
</trans-unit>

Salesforce Translation Format (.stf) Source Translation Files

Note Salesforce doesn’t recommend the STF format for translation files. If you choose to use this format, we don’t recommend editing the file with Microsoft Excel. For more information and restrictions, see Considerations for Working with Translation Files.

Tell your translators to replace the untranslated values in the LABEL column with translated values.

Important A translated value for the data in the record’s Name field is required to translate data in other fields for that record. For example, you must provide a German translation for the name of a Product before you can translate its description into German.

For example, if you build a custom Nickname field on the Account object, the original file contains this row in the exported Source .stf file.

To translate this label, replace the LABEL text in that row with the translated value.

Important Don't add columns to or remove columns from the .stf translation file.