Platform Internationalization

Overview#

A joint task force brings together investigators from five countries. Each person speaks their national language fluently but works in English with varying proficiency. A platform that only serves one language creates friction, slows down the less confident operators, and introduces transcription errors when people work outside their primary language. The Platform Internationalization module removes that barrier: every interface, notification, report, and help article renders in the operator's preferred language, and the system handles all the formatting details automatically.

The module manages translation storage, delivery, and synchronisation through Cloudflare KV edge caching, ensuring translated content loads with minimal latency regardless of user location. It covers static UI translations and dynamic content formatting including dates, numbers, currencies, and pluralisation rules specific to each locale.

Key Features#

Complete Language Coverage: Full translation of all platform interfaces, notifications, reports, and help content. Core support covers English, Spanish, French, German, Dutch, and Portuguese, with the platform's next-intl infrastructure supporting 40+ languages for extended deployments.
Edge-Cached Translations: Translation bundles stored in Cloudflare KV are served from edge locations worldwide, delivering sub-millisecond translation loading regardless of user geography.
Nested Translation Architecture: Organised translation namespaces with hierarchical key structures support domain-specific terminology and modular translation management, reducing conflicts across large deployments.
Static Client-Side Imports: Optimised translation loading for client-side components with static imports that eliminate runtime translation fetch overhead and enable offline operation.
KV Synchronisation: Automated synchronisation of translation files to the Cloudflare KV edge network, with support for nested directory structures and incremental updates to minimise deployment time.
Locale-Aware Formatting: Automatic formatting of dates, times, numbers, currencies, and measurement units according to locale conventions, including support for right-to-left text direction for future language expansion.
Translation Completeness Tracking: Automated scanning identifies untranslated strings across all supported languages, generating coverage reports and flagging regressions when new strings are added without corresponding translations.
Accessibility Compliance: All translated content maintains WCAG 2.2 AAA compliance including proper language attributes, screen reader pronunciation hints, and accessible label translations.

Use Cases#

Multinational Operations: European organisations with personnel across multiple countries deploy a single platform instance where each operator works in their national language while collaborating on shared cases and data.
Allied Force Coordination: Joint operations between nations use the platform with each participating force operating in their own language while viewing shared intelligence, alerts, and situational awareness in their preferred locale.
Citizen-Facing Services: Public-facing portals automatically present content in the citizen's browser language, with manual language selection for multilingual users.
Training and Onboarding: Training materials and help documentation are available in all supported languages, reducing onboarding time for personnel not comfortable operating in English.

Integration#

The internationalization module is embedded across all platform components including the web application, evidence management system, PSAP dispatch console, administrative interfaces, and reporting engine. Translation management integrates with the CI/CD pipeline for automated coverage validation and with the Cloudflare KV infrastructure for edge distribution.

Open Standards#

BCP 47 / IETF Language Tags (RFC 5646): Locale identifiers throughout the platform (such as en-US, fr-FR, ar-SA, pt-BR) follow the IETF BCP 47 language tag syntax, ensuring interoperability with browsers, operating systems, and third-party services.
W3C WCAG 2.2: All translated interfaces are validated to WCAG 2.2 AAA conformance, including colour-contrast ratios, keyboard navigation, focus management, and reduced-motion support across every supported locale.
W3C WAI-ARIA 1.2: Translated UI components use ARIA roles, labels, and live regions so that screen readers announce content correctly in each language, including right-to-left locales.
ECMAScript Internationalisation API (ECMA-402) / Unicode CLDR: Date, time, number, and currency values are formatted using the browser-native Intl.DateTimeFormat and Intl.NumberFormat APIs, which are backed by Unicode Common Locale Data Repository (CLDR) data for locale-correct presentation.
HTTP Content Negotiation, Accept-Language (RFC 9110): The platform reads the HTTP Accept-Language request header for locale detection and applies it as part of the device-fingerprint verification pipeline, ensuring language preference is honoured at the network edge.
W3C HTML lang Attribute: The root HTML document sets the lang attribute to the active BCP 47 locale tag on every page render, enabling browsers and assistive technologies to apply correct language rules for hyphenation, spell-checking, and text-to-speech pronunciation.
JSON (RFC 8259): Translation message bundles are stored, validated, and distributed as JSON files, allowing straightforward toolchain integration, CI coverage checks, and edge-cache delivery via Cloudflare KV.
GraphQL: Locale preferences and supported-locale configuration are exposed through the platform's GraphQL API, enabling client applications and integrations to query and mutate internationalisation settings using a standard typed interface.

Availability#

Enterprise Plan: All supported languages included.
Professional Plan: English and one additional language included; additional languages available as add-ons.

Last Reviewed: 2026-03-02 Last Updated: 2026-04-14