Every product invents its own shorthand. In HeedPost, "Most weight" is a way of sorting posts by the money behind them. "Shipped" is a status. "Follow" means you'll be emailed when something changes. English speakers who use the product learn these meanings quickly. A translator who sees the words on their own does not.
That's the hard part of translating software, and it's invisible to every test.
Correct words, wrong meaning
Some of the slips we caught while preparing our 21 languages:
- "Most weight" was first translated into Bengali as weight on a scale: physical heaviness. The product means the most money behind a post. Grammatically perfect, entirely wrong.
- "Most wanted", our label for sorting by votes, came out in Malay as the phrase used for wanted criminals.
- "Request", in Simplified Chinese, was first the word for a network request. We meant a want, something a customer asks for, which is a different word.
None of these would fail a spell check. All of them would make a reader pause, or laugh, or lose trust.
Translate from the screen, not the string
The fix was to stop translating strings and start translating screens. Every message was read again against the page that shows it: what is this button for, what happens when you press it, what would a person here call that? Only then was it written in each language.
Keep a glossary
Products repeat their core words everywhere: post, board, request, release, follow, workspace. Each needs one agreed translation per language, used consistently. We keep a glossary of these for every language, so the word for "release" on the changelog matches the word in the email and the word on the roadmap.
It also records the cases where a language prefers to borrow. Some languages' users say "issue" in English when talking about their tracker, and others use their own word. The glossary follows what people actually say.
Leave the customer's words alone
There's one category of text we don't translate at all: the words your team and customers typed. Status names, board names, labels and posts belong to the workspace. If you name a status "Coming soon", that's your phrase, in your language, and we show it as written.
Ask a reader
A glossary and careful drafting get you most of the way. The rest comes from people who read the language every day. If a word on your board sounds odd to your customers, they're right, and we'd like to hear about it.