Working in three languages is an operations problem, not a translation problem
Translating an interface is the easy part. The harder part is that your data, templates, notifications and reports all have a language too.
Artemis product team1 min read
A business serving patients in Persian, Turkish and English does not need three interfaces. It needs one system where a service name, a notification template and a document can each exist in three languages without becoming three separate records.
Where language actually shows up
- Master data: service names, categories and statuses a patient may see
- Notification templates, which must read naturally rather than word-for-word
- Generated documents: quotes, invoices and official letters
- Outgoing webhooks, when the receiving system expects a particular language
Handled as translation, each of these becomes a separate copy that drifts. Handled as a property of the data, they stay one thing with three renderings.
Tags
- Multilingual
- Leads
Artemis product team
Product
Writes about how the Business Platform works and why it is built the way it is.