What are the key UX considerations for internationalisation (i18n) in Salesforce UI?
Suggested answer
Internationalisation in Salesforce UX involves:
1. Translation Workbench: Field labels, picklist values, custom object names, validation rule messages, and help text can all be translated. Enable the Translation Workbench in Setup and add supported languages.
2. Text expansion: Translated text can be 30–50% longer than English — design layouts with flexible containers, avoid fixed-width buttons, and test all components with German or Finnish translations (some of the longest expansions).
3. Date, time, and number formats: Salesforce automatically formats these based on the user's locale setting — never hardcode format assumptions in custom components.
4. RTL languages: Arabic and Hebrew require right-to-left layout mirroring. SLDS has RTL support but custom components must be tested.
5. Icon meaning: Some icons carry cultural meaning that does not translate — thumbs up, postal icons, and colour associations vary by region.
6. Currency: Use Salesforce's multi-currency or advanced currency management for orgs operating across regions.
Practice content for interview preparation; not an official vendor answer. Verify details against current product documentation.
Community comments (0)
No comments yet.
Sign in or create a free account to add a comment. Comments are moderated before they appear.