Plan a multilingual interface around a concrete task

Start with a record that stays unchanged

Plan a multilingual interface around a complete task: open, review and approve a request. Text must remain understandable, and business data must retain its meaning. A list of translated buttons does not show those relationships.

A fictional project portal will support ten languages. Request R-18 contains the numeric amount 1234.5, currency EUR and calendar date 2026-11-12. For this task, currency, amount, date and approval status remain unchanged when the interface language changes. An English interface does not turn the amount into dollars.

Specify display formats explicitly

The team chooses these three locales, meaning language and region variants, for comparison. The amount is displayed as currency with two decimal places; the date uses a two-digit day and month and a full year. The date comparison explicitly uses the UTC time zone.

Intl.NumberFormat and Intl.DateTimeFormat support language-sensitive displays like these. Locale and options are selected explicitly; the computer’s default must not change the comparison unnoticed. A date representing only a calendar day must not shift to another day when the language changes. If people enter an amount, suitable input and validation rules are also needed: formatted output alone does not define a safe input parser.

Plan for long text and missing states

Check actual labels in narrow and wide views. In the example, the button “Approve the project request after review” must retain its meaning even if a translation needs more space. Planned wrapping or a different arrangement is more useful than an unclear abbreviation. A fixed expansion percentage cannot guarantee that every text will fit.

Language coverage also includes empty lists, loading states and error messages. If the translation for approval.confirm is missing in the example, the portal blocks approval and shows an understandable explanation in the selected language. A mixed fallback language is not silently accepted for this critical step. This is the chosen product rule, not an automatic property of a translation library.

Check language changes during the task

Open the same request in every intended language and switch while editing. In the example, entered data must remain; changing language must not trigger approval. Then check that the amount, calendar day and still-open status are preserved.

Artificially extended test text can reveal layout problems early. You still need to read final translations in context and check them through the complete task. Record for each language whether approval is understandable and possible without data loss, or which specific state is still missing.

Sources

• W3C — Text size in translation

• MDN — Intl.NumberFormat

• MDN — Intl.DateTimeFormat

• Microsoft Learn — Internationalization testing