Why mistakes happen in Rohingya translation
Rohingya translation errors arise from a combination of factors: a small pool of qualified translators, lack of standardisation, script complexity, and commissioning organisations that don’t know what to look for. Understanding the most common mistakes helps both translators and clients produce better work.
Mistake 1: Substituting a Chittagonian or Bengali speaker
The most common and serious mistake is using a Bengali or Chittagonian speaker as a Rohingya translator or interpreter.
Why it happens: Commissioners assume the languages are mutually intelligible.
Why it’s wrong: While there is overlap, Rohingya has distinct vocabulary, grammar, and phonology. A Chittagonian speaker cannot reliably translate legal, medical, or sensitive material into Rohingya. Important nuance, terminology, and meaning will be lost or distorted.
Fix: Only commission translators who identify as native Rohingya speakers and can demonstrate their skills.
See also: Is Rohingya different from Chittagonian?
Mistake 2: Not specifying the target script
Rohingya can be written in Hanifi, Fonna (Arabic), or Rohingyalish. If a client doesn’t specify, the translator will choose — and it may not be the right choice for the audience.
Example: A health leaflet produced in Rohingyalish for an elderly community where most adults are Fonna-literate will be unreadable by the target audience.
Fix: Always specify script in your brief. Consult with someone who knows your specific target community.
Mistake 3: Over-relying on machine translation
Google Translate and other machine translation tools have extremely limited Rohingya support. Machine output in Rohingya is often inaccurate, inconsistent, or completely wrong.
Fix: Use human translators. Machine translation can be used as a starting point for a translator to post-edit, but never as a final product.
Mistake 4: No quality review
Many commissioning organisations accept the first translation without any review. For a language like Rohingya where qualified translators are scarce and standardisation is limited, unchecked translation is risky.
Fix: Require at minimum a second native speaker review of any important document.
Mistake 5: Ignoring dialect variation
Rohingya spoken in Cox’s Bazar may differ from Rohingya spoken in Malaysia, the Gulf, or among older diaspora communities in the UK.
Fix: Match your translator’s background to your target audience where possible. Brief translators on the specific community they are translating for.
Mistake 6: Literal translation of idiomatic English
English legal, medical, and NGO language is full of idioms and technical terms with no direct Rohingya equivalent. Literal translations often produce nonsense.
Examples of problematic English:
- “Right to remain silent” — requires careful cultural and legal explanation, not literal translation
- “Informed consent” — has no direct equivalent; must be explained
- “Follow up” — in medical context needs clear, plain-language rendering
Fix: Work with translators who have sector experience. Provide glossaries. Allow them to use explanatory translation rather than literal equivalents.
Mistake 7: Not briefing interpreters before sensitive sessions
Using an interpreter who is unprepared for traumatic, legal, or medical content leads to errors, interpreter distress, and poor outcomes.
Fix: Always brief interpreters before sessions. See the Rohingya interpreter guide.
Mistake 8: Assuming literacy
Not all Rohingya speakers can read any script. Literacy rates vary significantly, especially among those who spent years in camps with limited access to education.
Fix: Always check literacy before distributing written materials. Audio versions of important information are often more accessible.
Getting it right
Professional Rohingya translation requires qualified translators, a clear brief, appropriate script selection, and quality review. Our translation services follow all of these principles.