Automotive & Software Localization

04 / Automotive UX

Interface localization · Terminology
Hypothetical infotainment system

Language for a screen that demands clarity.

Vehicle interfaces rely on clear instructions, short labels and consistent terminology. Here are 20 illustrative English-to-Danish UI strings.

English source	Danish localization	Reviewer note
Navigation	Navigation	Recognizable menu term
Search destination	Søg efter destination	Explicit action
Start route	Start rute	Short button label
Route recalculating	Ruten genberegnes	Status, not command
Turn right in 200 m	Drej til højre om 200 m	Natural navigational phrase
Continue straight	Fortsæt ligeud	Concise driving instruction
You have arrived	Du er fremme	Direct confirmation
Save destination	Gem destination	Consistent imperative
Traffic ahead	Trafik længere fremme	Does not invent a congestion warning
Estimated arrival	Forventet ankomst	Label assumes time value shown separately
Connect device	Tilslut enhed	Confirm protocol context
Pair new device	Par ny enhed	Bluetooth pairing terminology
Connection lost	Forbindelsen er afbrudt	Clear status
Bluetooth settings	Bluetooth-indstillinger	Danish hyphenation
Low battery	Lavt batteriniveau	Battery type requires context
Charging in progress	Opladning i gang	Short status
Charging complete	Opladning fuldført	Completion status
Lane keeping assist	Vognbaneassistent	Check OEM termbase
Check tire pressure	Kontrollér dæktrykket	Imperative; safety-review required
Restore default settings	Gendan standardindstillinger	Familiar software term

Localization notes

Pair vs connect: Bluetooth pairing and connecting may be different operations. Par and tilslut are applied according to the product context.

Ambiguous warnings: “Low battery” could refer to the vehicle, key or connected device. The battery must be identified before approval.

Space constraints: Compact text is useful, but character limits must be checked against the actual UI, dynamic variables and screen size. No production UI testing is claimed here.

Safety context: Warning severity and actions must be confirmed with the product team and applicable terminology guidance.

Demonstrates: Terminology discipline, technical precision, interface awareness and context-dependent linguistic QA. Not a claim of manufacturer-approved work.

← Back to selected work Discuss a project ↗