AVAVERELI
CompanyProductsKnowledgeResearchDocumentationDevelopersSupportSearchCustomer portal

Languages & regions

Translate meaning, not merely words.

The platform is internationalisation-ready, but only English (United Kingdom) is active. A locale becomes public only after terminology, review, source ownership, accessibility, and SEO controls are approved.

Default localeen-GB
Active locales1
Approved translations0
Locale routingNOT_ENABLED

Locale registry

One active language. One candidate.

Active

English (United Kingdom)

en-GB · LTRApproved
Candidate

Nederlands

nl-NL · LTRNot public
01

Extract

Bind translatable content to its source identifier and version.

02

Translate

Use approved terminology; AI may assist but cannot self-publish.

03

Review

Language and domain reviewers verify meaning, safety, links, and layout.

04

Approve

The original content owner authorises the locale-specific record.

05

Publish

P003 emits locale routes, metadata, hreflang, sitemap, and fallback controls.

06

Maintain

Source changes mark dependent translations stale until re-approved.

Publication boundary

No silent machine translation.

AI-assisted translation is permitted only as a drafting method. Every public translation requires accountable human review, the authoritative content owner’s approval, source-version traceability, approved terminology, and an explicit last-approved date.

Accessibility posture →Platform transparency →
Fallback
Explicit English
Mixed-language pages
Prohibited
Automatic redirect
Disabled
Locale preference
Not stored

Regionalisation scope

Locale affects more than copy.

Dates, numbers, currencies, time zones, plural rules, address formats, legal terms, support availability, screenshots, search indexes, structured data, and bidirectional layout must be tested independently. Product availability and price may never be inferred from language selection.