Built an English/Danish i18n system
Established an English/Danish internationalization system carrying
12,027 messages per locale across 458 namespace files, with
linter‑enforced vocabulary and a 400‑line budget per file.
2025

Situation. The platform runs in English and Danish, and translation
systems have a way of sprawling into a mess. The files grow without
limit, keys leak — present in one locale, missing in the other — and
the language‑specific conventions get applied unevenly, so one
locale ends up reading like it was translated by a committee that
didn't talk to each other. For a professional product that's not a
small blemish; it reads as carelessness.

Task. The internationalization setup had to scale — keeping both
languages consistent and correct, and the files something a person
could still maintain a year in.

Action. It's built on next‑intl with rules the tooling actually
enforces. The Danish side has a locked vocabulary and style —
literal æøå, the informal "du", the right imperative accents, and
semantic mappings for compound nouns so they're translated by
meaning rather than word‑for‑word — and a linter holds it to that.
There's a hard 400‑line budget per namespace file, with a
split‑and‑merge approach so a big area divides into nested files
that merge back cleanly instead of one file growing forever; that
budget is why 12,027 messages per locale live in 458 files rather
than a handful of enormous ones. A linter check compares keys across
locales so nothing leaks or goes missing. And stored overrides are
merged catalogue‑driven rather than with fragile top‑level fallbacks
— the same deep‑merge idea used for preferences.

Result. Both locales stay correct and consistent at 24,054 messages
between them, and the files stay maintainable as the string count
climbs. Tooling enforces the recorded vocabulary, style and
catalogue rules on every commit; assessing each translation's
meaning and idiom still requires contextual reading. The budget is
the load‑bearing part: without a limit per file, 458 files would
have been twelve, and nobody would open them.

Categories:
1Frontend Engineering	/categories/frontend/	software.engineer.company	70
1Full‑Stack Development	/categories/full-stack/	software.engineer.company	70
1Automation & CI/CD	/categories/automation/	software.engineer.company	70
1Internationalization	/categories/i18n/	software.engineer.company	70
1Documentation	/categories/documentation/	software.engineer.company	70

Services:
1Frontend Development	/services/frontend-development/	software.engineer.company	70
1Internationalization & Localization	/services/i18n-localization/	software.engineer.company	70

hThis page on the web	URL:https://software.engineer.company/portfolio/built-an-english-danish-i18n-system/	software.engineer.company	70
