Generate Documents by Using User Locale Settings

How Localization Works

Localization makes sure that generated documents show data in the language and format defined by the current user’s locale. Apply translation for supported token data and locale-specific formatting for currency, date, and time. Configure translations by using Translation Workbench. Document generation retrieves translated values at run time when localization is enabled.

Localization applies when you use Context Service as the token mapping type and control it by using the localization flag in the document generation request. If you don’t turn on localization, document generation uses the org’s default language and regional settings.

Key Capabilities

• Translate supported token-based data such as product names.
• Apply localization across document generation scenarios by using a localization flag.
• Control localization behavior at the document level and refine translation at the field level.

Considerations

• Configure translations by using Translation Workbench before enabling localization.
• Use Context Service as the token mapping type for localization.
• Use the Keep Localization setting to control translation at the field level and apply localization selectively.
• Apply default org settings when localization is turned off.
• Apply translation only to fields and metadata that support Translation Workbench.
• Select a font that supports the required languages for document rendering.
• Use language-specific templates if the font doesn’t support the language.
• Support translated text, locale-specific currency, and date and time formats through localization.
• Use the Keep Localization setting in the context definition to exclude translation for specific fields while retaining locale-based formatting, such as currency and date.