Platform · Module
Localization
UI, templates and content in Indian languages, with glossaries and human review
Localization manages UI strings, templates and content translations across every app with glossaries, translation memory and AI-assisted translation that humans review. Language rollouts are gated by task-success evaluation.
More than translated strings
One3's goal is that people can do their work in their own language, not just read translated labels. Localization, planned for Wave 3, manages UI strings, templates and content translations across every app and tenant. In Year 1 the substitute is translation string files inside each app with English, Hindi and Tamil.
How it works
A string key registry is built from app manifests and UI code, with extraction in CI. The translation editor shows context such as a screenshot or the object, and handles plural and gender rules with ICU MessageFormat. Glossaries per tenant, brand and platform hold do-not-translate terms. AI translation runs through Model Hub with the glossary applied, and UI strings always need human review before publish. Translation memory is reused across apps.
Quality for Indian languages
Indic QA checks script correctness, number and date formats, truncation and code-mixed style guides. Tenants can override terminology, for example "client" instead of "customer", without forking an app. Language rollout gates are tied to the language evaluation dimension, so a language launches only when people can complete tasks in it. Content translation covers notification, WhatsApp and email templates and knowledge articles.
Later
RTL layout support and pseudo-localisation tests are planned for Wave 4. Further Indian languages, including Telugu, Kannada, Malayalam, Marathi and Bengali, are planned for Waves 3–4, subject to evaluation gates.
How it fits
Localization is shared by every One3 app, so a glossary or terminology override applies across CRM, Marketing, Service Desk and the rest at once. Copilot languages follow the same evaluation gates.
Features
What Localization includes
String key registry
From app manifests and UI code, with CI extraction. W3.
Translation editor with context
Screenshots or objects, plural and gender rules. W3.
Glossaries
Per tenant, brand and platform, including do-not-translate terms. W3.
AI translation with review
Glossary-aware drafts; human review before UI strings publish. W3.
Translation memory
Reuse across apps. W3.
Indic QA
Script, number and date formats, truncation and code-mixed style. W3.
Tenant terminology overrides
Change terms without forking an app. W3.
Language rollout gates
Launch only after task-success evaluation. W3.
Content translation
Notification, WhatsApp and email templates and knowledge articles. W3.
More Indian languages and RTL
Telugu, Kannada, Malayalam, Marathi, Bengali; RTL and pseudo-localisation. W3–W4.
Workflow
Launch a new language
- 1
Strings are extracted into the registry.
- 2
AI drafts translations with the glossary.
- 3
Reviewers approve in the editor with context.
- 4
Indic QA checks run.
- 5
The language passes its evaluation gate and is enabled.
AI
AI skills and Digital Employees
Glossary-aware translation
Drafts translations for review; UI strings never auto-publish.
Indic QA
Automatic checks for script correctness, formats, truncation and style.
Digital Employees that use this module
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
Which languages are available in Year 1?
English, Hindi and Tamil are planned through string files in each app. The Localization module itself is planned for Wave 3.
Is AI translation published automatically?
No. UI strings always need human review before publish.
Can I change product terminology?
Tenant terminology overrides are planned, so you can say "client" instead of "customer" without forking an app.
See Localization in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.