On this page
- Decide what “bilingual” means for your product
- Fonts and rendering
- Script and font choice
- Practical tips
- Web performance
- Mobile
- Input and keyboards
- How users type Odia
- What to do about it
- Translation workflow
- Separate text from code
- Plan for grammar
- Who translates
- Keep translations in sync
- Design and layout
- Testing
- Common pitfalls
- Where to start
Odia is spoken by tens of millions of people, and many of them use apps and websites in English only because the Odia version either does not exist or does not work well. If your users are in Odisha, an Odia interface can be the difference between an app people try and one they keep using.
Adding Odia is not just translating strings. This post covers what to plan: fonts, input, translation workflow, layout and testing.
Decide what “bilingual” means for your product
Start with scope, because it changes the work.
- Interface only. Buttons, menus and messages are available in Odia and English. Users’ own content stays as they typed it.
- Content too. Your catalogue, articles or notices exist in both languages. That means a content process, not just a UI one.
- User input in Odia. Users type names, addresses, search queries or messages in Odia. This affects database, search and validation.
- Voice or messaging. Notifications, SMS and WhatsApp templates in Odia have their own rules.
Write down which of these you need for the first release. Interface and notifications first, content later, is a common sensible path.
Fonts and rendering
Script and font choice
Odia uses its own script with many conjuncts (joined consonants) and vowel signs that attach in several positions. Rendering depends on a font that has complete glyph coverage and a rendering engine that handles shaping correctly.
Noto Sans Oriya is a solid free choice. It is open-licensed, has broad coverage and gives a clean, readable look that pairs well with Latin fonts. The script name “Oriya” appears in font names for historical reasons, even though the language is called Odia.
Practical tips
- Pair it deliberately. Choose a Latin font and an Odia font of similar visual weight and x-height, so mixed text does not look uneven.
- Mind the size. Odia glyphs usually need a little more size and line height than Latin text. Test body text at a size that is comfortable to read, and do not shrink it to match English.
- Check conjuncts. Test words with complex joined letters to confirm they render, not as broken boxes or separated characters.
- Weights. Confirm the weights you want (regular, medium, bold) exist for Odia. Fake bold can degrade shapes.
Web performance
Odia fonts are large. On the web, subset the font to the characters you need, serve WOFF2, host it yourself and use font-display: swap. Load the Odia font only when the Odia language is selected. Our post on website speed and Core Web Vitals covers why this matters.
Mobile
Android and iOS include Odia system fonts in recent versions, but older or budget Android devices may render poorly. Bundling a font with the app gives consistent results, at the cost of app size. Decide based on the devices your users own, and test them.
Input and keyboards
How users type Odia
Users type Odia in several ways: a built-in Odia keyboard, a phonetic or transliteration keyboard (typing “namaskar” in English letters and getting Odia), or a third-party keyboard app. You cannot control which one they use.
What to do about it
- Use standard text inputs so every keyboard works. Avoid custom input handling that breaks composition.
- Do not restrict characters in names and addresses to ASCII. Allow the full Unicode range for Odia.
- Normalise text. Unicode can represent the same visible text in different code-point sequences. Normalise before storing and comparing, or search and duplicate checks will miss matches.
- Consider transliteration search. Users may search in English letters for Odia content or the reverse. Supporting both improves results.
- Store as UTF-8 end to end: database, APIs, exports and emails.
Translation workflow
Separate text from code
Keep all user-facing strings in resource files with keys, never hard-coded. Use your platform’s localisation system: ARB files in Flutter, i18n libraries in React and React Native, or string resources on native Android.
Plan for grammar
Do not build sentences by joining fragments. Odia word order and grammar differ from English, so “Hello, “ + name + “!” may not work. Use full-sentence strings with placeholders, and provide plural and gender handling where needed.
Who translates
Machine translation is a useful first draft but make a native Odia speaker review everything users will see. Tone matters: formal or conversational, and which register your audience expects. Create a short glossary for key terms such as “order”, “account” and “payment”, so the app stays consistent. Decide when an English word is better left as is, since many Odia users are comfortable with common English tech terms.
Keep translations in sync
Every new feature adds strings. Set up a process: developers add English keys, a script flags missing Odia keys, and a translator fills them in before release. Make missing translations visible in test builds instead of silently showing English.
Design and layout
- Text length. Translated text may be longer or shorter. Do not size buttons to fit English exactly. Allow wrapping and flexible widths.
- Line height. Odia has marks above and below the line. Tight line height clips them.
- Language switcher. Place it where users can find it, and label it in its own script (ଓଡ଼ିଆ and English) so people who cannot read the current language can still find it.
- Remember the choice. Save the user’s language preference, and default sensibly based on device settings.
- Dates, numbers and currency. Use locale-aware formatting. Decide whether to show Western or Odia numerals and be consistent.
- Icons and images. Avoid text baked into images, because it cannot be translated without redoing the asset.
Testing
Bilingual products need their own test pass.
- Visual check on real devices. Include low-end Android phones, which are common in many parts of Odisha.
- Broken rendering. Search for boxes, missing conjuncts and clipped text.
- Long and short strings. Check every screen for overflow.
- Input tests. Type Odia with different keyboards, paste Odia text, and save and reload it.
- Search and sorting. Confirm Odia text is searchable and sorted sensibly.
- Notifications and emails. Check that SMS, push and email templates render correctly in Odia.
- Native-speaker review. Have an Odia speaker go through the whole flow, as a user, not as a proofreader.
Common pitfalls
- Using a font that lacks full Odia coverage
- Hard-coded English strings that slip through
- Truncating text with ellipsis in the middle of a conjunct
- Forgetting the Odia version of error messages
- Translating once, and never again as features change
- Assuming every user has a good Odia keyboard
Where to start
Pick the screens users meet first: onboarding, the main list and the key action. Build those in both languages with a clean string setup, test on real devices, and expand from there. Getting the foundations right at the start is much cheaper than retrofitting.
If you are planning a product for users in Odisha, talk to us. See also our work on mobile app development and web development, or read about what a mobile app costs to build in Odisha to scope the work.