Multilingual guidance

Translation principles

Approach Yoruba, Hausa, Igbo and Nigerian Pidgin as first-class product languages — translated for meaning, reviewed by speakers, tested with users.

Translate meaning, not words#

Word-for-word translation produces text that is technically each language and actually none of them. Brief translators on the job of each string — what the user must understand or do — and let them write it natively.

Principles#

1. Source text must be plain first#

Idioms, jokes and corporate English fail in translation. Fix the English with plain language before translating; it halves translation cost and error.

2. Use professional speakers, review with users#

Machine translation may draft, but a native-speaking reviewer signs off — and high-stakes flows (money, consent, legal) get usability-tested in each language.

3. Respect register#

Each language has its own politeness system. Yoruba honourifics, Hausa formality, the warmth of Pidgin — a single "friendly" brand voice does not map one-to-one. Define tone per language with native writers.

4. Pidgin is a full language#

Nigerian Pidgin reaches across regions and literacy levels. Treat it with the same rigour as the others: consistent orthography, glossary, reviewer. Don't "season" English with Pidgin words and call it localisation.

5. Keep money terms stable#

Amounts, fees, dates and IDs follow the same currency and numbers rules in every language. Numbers don't translate; their labels do.

6. Plan for expansion#

Translations run longer than English. Design buttons and layouts for +35% text length, and never truncate a warning to fit.

Building a glossary#

Maintain a term base per language for product-critical words (transfer, wallet, fee, verify). The glossary is part of the product, versioned with it, and contributors can propose changes.

Spotted a problem with this page? Suggest an edit on GitHub.