Supported languages
Better Comply ships the user interface and completion certificates in eleven languages. Training and controlled-document content can also be generated or translated into these languages with AI.
The eleven locales
| Language | Code |
|---|---|
| Spanish | es |
| English | en |
| Portuguese | pt |
| German | de |
| Polish | pl |
| Turkish | tr |
| Bulgarian | bg |
| Romanian | ro |
| Hungarian | hu |
| Russian | ru |
| Italian | it |
The authoritative list is the SUPPORTED_LANGUAGES constant in @betterknow/shared. All eleven locales are first-class: every user-facing string in the web application is translated, accents and diacritics are correct (no accent-stripped Spanish or Portuguese), and there are no English-only fallbacks in the UI. A CI lint check enforces catalog parity across all eleven locales.
Selecting a language
In the web application - open the language selector in the top bar (the globe icon or your current language flag) and choose from the list. The selection is saved to your browser and restored the next time you log in.
For training content - the training viewer also includes a language selector. If an approved version exists in the selected language, the viewer loads it. If it does not, the viewer falls back to the assigned available version and shows a banner with the displayed language.
For certificates - the language on a completion certificate matches the training version the learner completed, not just the learner's browser language. This ensures the certificate matches the actual content used for completion.
Localized outputs
| Output | Localized? | How |
|---|---|---|
| Web application UI | Yes, all 11 locales | Language selector in the top bar |
| Training content | Yes, all 11 locales when translated versions exist | The learner can choose a language in the viewer; unavailable languages fall back to the assigned version |
| Completion certificate (PDF) | Yes, all 11 locales | Follows the completed training version's configured language |
| Supervisor weekly digest email | Yes, Spanish / English / Portuguese / German | Server-rendered from a four-locale copy map; each supervisor receives the digest in the language their BetterKnow deployment is configured for |
| AI-generated training content | Yes, all 11 locales | The author selects the target language when creating or translating a training version |
| AI-translated controlled documents | Yes, all 11 locales | The author selects the target language in the content-document editor, reviews the translated Markdown, then saves an audited version |
| System email notifications | English | Planned for future releases |
Language and certificates
Completion certificates embed the learner's name, training name, and completion date, all rendered in the certificate's configured locale. The certificate also uses the correct character sets for each locale:
- Latin-extended characters (Spanish, Portuguese, German, Polish, Romanian, Hungarian, Italian, Turkish) - full diacritic support.
- Cyrillic characters (Russian, Bulgarian) - embedded font covers the full Cyrillic block.
Names containing characters outside the supported ranges are processed as-is where possible; unsupported glyphs are silently dropped rather than causing the certificate generation to fail.
Language and the supervisor digest
The weekly supervisor digest email is sent by the server-side scan job. The digest body is rendered in one of four languages (Spanish, English, Portuguese, or German) using a server-side copy map - it is independent of the web application's i18n catalog. Every learner name and training name interpolated into the digest is escaped to prevent HTML injection.
Supervisors whose accounts use an emailless identity (no corporate email address) are skipped and recorded in the delivery ledger as skipped_no_email.
Adding or changing a training's language
Administrators set the language when creating or editing a training version through the Training Materials authoring flow. The language affects:
- The language the AI uses to generate content and quiz questions.
- The version the learner can select in the training viewer.
- The language printed on completion certificates.
Changing or translating the language creates a new training version and goes through the standard review and approval workflow.
Translating controlled documents
Content-type controlled documents can be translated from the edit page. Select a target language, run Translate with AI, review the Markdown result, and save it with a documented change reason. The save creates an audited translated version variant linked to the source version.
When someone reads the controlled document, the viewer tries to show the selected document language. If that translated variant is not available, Better Comply shows the available source version and displays a fallback banner.