localize

Start with an i18n readiness audit covering string externalization, layout flexibility for text expansion, locale-aware formatting, and RTL support. Then produce a cultural adaptation brief per target market covering tone, imagery, trust signals, and compliance requirements.

Translation converts words between languages, while localization adapts the entire experience including layout direction, date and number formats, color meaning, iconography, payment flows, and legal compliance. A translated interface can still fail culturally and functionally in a new market.

Use CSS logical properties like inline-start and inline-end instead of left and right, set dir="rtl" on the root element, and flip directional icons and navigation order. Numbers, media controls, and brand logos do not flip. Test with real RTL content and native users, not mirrored screenshots.

German expands roughly 30 percent and Finnish 40 percent over English, while string concatenation breaks word order and pluralization rules in most languages. Use ICU MessageFormat with CLDR plural rules and test layouts with pseudo-localized strings expanded 30 to 50 percent.

GDPR requires unbundled consent and data deletion rights in the EU, PIPL mandates data localization in China, and CCPA requires a Do Not Sell link in California. Accessibility laws like the European Accessibility Act and payment rules like PSD2 also directly shape interface design.

Frameworks like high-context versus low-context communication are starting hypotheses, not design rules, and individuals vary widely within every market. They should generate research questions validated through user research and behavioral data, never serve as stereotypes to design by.