This guide adapts rules and examples from Microsoft’s Localization Style Guide for Odia (originally written for software/UI localization). The underlying linguistic rules apply universally — to legal contracts, medical documents, marketing copy, and any Odia translation work. Restructured and reformatted as a general Odia translator reference by ChatsControl.
Odia Translation Style Guide — Voice, Word Choice & Common Pitfalls (Legal, Medical, Marketing, IT)¶
TL;DR¶
- Odia translation across all spheres (legal, medical, marketing, IT) requires a warm, conversational, scannable register — overly Sanskritized or bureaucratic Odia feels alien in modern consumer-facing content.
- Use transliteration of established English technical terms when no natural Odia equivalent exists (ୱାଲେଟ୍ for wallet, କ୍ଲାଉଡ୍ for cloud, ଡିଭାଇସ୍ for device) — but only for terms users encounter in daily life.
- Address the user as ଆପଣ (formal you) directly; avoid third-person references like ଉପଭୋକ୍ତା (“user”) which sound institutional in consumer contexts.
- Odia compounds should be transparent and short — avoid overly long Sanskrit-style compounds when a periphrastic construction reads more naturally.
- Use the Odia full-stop daṇḍa (।), not the Latin period, at sentence end; Odia has no grammatical articles, no grammatical gender on inanimate nouns, and only lexical gender distinctions on certain animate nouns.
- TL;DR
- Register and tone for modern Odia translation
- Word choice: approved terminology and conversational vocabulary
- Transliteration: when to keep the English word
- Sample voice: addressing the user to take action
- Inclusive language
- Language-specific grammar standards
- Localization considerations
- Voice video considerations
- Reference materials: authoritative Odia language references
- FAQ
- What’s the modern register for Odia translation across professional contexts?
- When should I transliterate English terms vs. translate them into Odia?
- How should I address users in Odia translation?
- What punctuation differences should I respect in Odia translation?
- Which Odia normative references should I follow?
- How does Odia handle gender in translation?
- How should I handle compounds in Odia translation?
- Sources
Register and tone for modern Odia translation¶
Register is the level of formality, warmth, and conversational ease the target text projects. Modern Odia readers across consumer-facing spheres expect a register that feels human rather than bureaucratic — heavily Sanskritized administrative Odia signals distance and institutional indifference to most contemporary audiences.
Three principles define the modern Odia register for consumer-facing content:
- Warm and relaxed. Sounds like honest conversation, not a formal notice. Less institutional, more grounded — matching how Odia speakers actually talk.
- Crisp and clear. Written for scanning first, reading second. Sentences short enough to parse on a phone screen. Simplicity is the default.
- Ready to help. Anticipates what the reader needs and offers it at the right moment, rather than burying it under qualifications.
Why this matters: Bureaucratic register damages outcomes across spheres. In marketing copy it kills conversion — readers bounce when text sounds like a tax form. In patient-facing medical materials it reduces comprehension and compliance. In software UI it creates friction at every interaction. In consumer-facing legal documents (terms of service, privacy notices) regulators increasingly demand plain language. Only sworn legal translation and pure technical specifications retain the older formal register.
Audience targeting: technical vs. consumer vocabulary¶
The same source text requires different vocabulary depending on who reads the translation. Use technical terms for technical audiences; for consumers use common words. A clinical drug monograph for prescribers uses precise pharmacological terminology; the patient leaflet for the same drug uses everyday Odia. A software API reference uses developer jargon; the end-user help article uses plain Odia.
This applies in every sphere. Legal translation for corporate counsel uses Sanskrit-derived legal terminology and procedural shorthand; consumer-facing versions need plain-Odia framing. Medical translation for clinicians keeps Greek/Latin nomenclature; for patients it switches to common terms. IT translation uses developer jargon in engineer-facing docs, natural Odia in end-user help — often with transliterated English terms users already know.
Word choice: approved terminology and conversational vocabulary¶
Approved terminology is the project-specific bank of fixed translations for key terms, product names, technical concepts, and recurring phrases. Every serious translation project has one. Consistency within the bank matters more than the individual choice — switching renderings of a defined term across a document signals carelessness.
Short, everyday words are preferred over long formal ones wherever both exist and the audience is non-specialist. Shorter words save screen space and parse faster.
Common word-choice examples (en-US → Odia)¶
| en-US source | Odia preferred | Usage notes |
|---|---|---|
| App | ଆପ୍ | Use ଆପ୍ instead of application or program. |
| Choose/pick | େୟନ କେନ୍ତୁ / ବାଛନ୍ତୁ | Use ବାଛନ୍ତୁ in lighter, friendlier contexts; େୟନ କେନ୍ତୁ for general selection. |
| Drive | ଡ୍ରାଇଭ | For general reference to any drive type (hard drive, external hard drive, etc.). Use specific drive type if necessary. |
| Get | ଆଣିବା / ପାଇବା | Synonym for “obtain” or “come into possession of”; avoid for other general meanings. |
| Info | ସୂଚନା | Use info when pointing reader elsewhere (“for more info, see “). |
| PC | ପିସି | Use for personal computing devices. Use ୟ୍ୟୁଟର (computer) for situations about PCs and Macs. |
| You | ଆପଣ | Address user as you, directly or indirectly through second-person pronoun ଆପଣ. Avoid third-person ଉପଭୋକ୍ତା (“user”) — sounds formal and impersonal. |
| …is in process | …ପ୍ରକ୍ରିୟାରେ ଅଛି / ପ୍ରକ୍ରିୟାରେ | Either form is acceptable. |
| …is retrying | …ପୁନଃ ପ୍ରୟାସ କରୁଛି | Idiomatic for retry operations. |
Words and phrases to avoid (unnecessary formality)¶
Odia translation that mirrors heavy English Latinate vocabulary one-for-one produces unnecessarily formal text. Prefer plain equivalents:
| en-US word/phrase to avoid | Preferred en-US (and Odia mapping) |
|---|---|
| Achieve | Do (କରନ୍ତୁ) |
| As well as | Also, too (ମଧ୍ୟ) |
| Attempt | Try (ପ୍ରୟାସ କରନ୍ତୁ) |
| Configure | Set up (ସେଟ୍ ଅପ୍ କରନ୍ତୁ) |
| Encounter | Meet (ସାମନା କରନ୍ତୁ) |
| Execute | Run (ଚଲାନ୍ତୁ) |
| Halt | Stop (ବନ୍ଦ କରନ୍ତୁ) |
| Have an opportunity | Can (ପାରିବେ) |
| However | But (କିନ୍ତୁ) |
| Give/provide guidance, give/provide information | Help (ସାହାଯ୍ୟ କରନ୍ତୁ) |
| In addition | Also (ମଧ୍ୟ) |
| In conjunction with | With (ସହିତ) |
| Locate | Find (ଖୋଜନ୍ତୁ) |
| Make a recommendation | Recommend (ସୁପାରିଶ କରନ୍ତୁ) |
| Modify | Change (ବଦଳାନ୍ତୁ) |
| Navigate | Go (ଯାଆନ୍ତୁ) |
| Obtain | Get (ପାଆନ୍ତୁ) |
| Perform | Do (କରନ୍ତୁ) |
| Purchase | Buy (କିଣନ୍ତୁ) |
| Refer to | See (ଦେଖନ୍ତୁ) |
| Resolve | Fix (ସମାଧାନ କରନ୍ତୁ) |
| Subsequent | Next (ପରବର୍ତ୍ତୀ) |
| Suitable | Works well (ଭଲ କାମ କରେ) |
| Terminate | End (ସମାପ୍ତ) |
| Toggle | Switch (ସୁଇଚ୍ କରନ୍ତୁ) |
| Utilize | Use (ବ୍ୟବହାର କରନ୍ତୁ) |
Old vs. new word choices in Odia¶
| en-US source | Odia old word/phrase | Odia preferred new word/phrase |
|---|---|---|
| Select | େୟନ କେନ୍ତୁ | େୟନ |
| Furthermore | ଏହା ବ୍ୟତୀତ | ଏହା ସହିତ |
| Therefore | ସେଥିପାଇଁ | ଏଥିପାଇଁ |
Why this matters: These distinctions appear in legal templates and government forms out of institutional habit but feel alien in modern consumer products, patient-facing medical materials, brand-led marketing, and user-friendly software. A privacy policy opening with a heavy Sanskrit construction reads as bureaucratic indifference; the same idea expressed in plain Odia reads as the product talking to its user.
Transliteration: when to keep the English word¶
Modern Odia speakers use many English technical terms in daily life. When no simple, easy-to-understand local Odia word exists for a technical concept, transliteration (writing the English term in Odia script) is acceptable — and often preferred over forced translation.
The objective: the product UI should be easy to use and represent local Odia at its core strength. Transliteration is part of how modern Odia handles technology vocabulary, not a failure of translation.
| Source | Possible Odia translation | Transliteration (preferred when in daily use) |
|---|---|---|
| wallet | ପର୍ସ | ୱାଲେଟ୍ |
| cloud | ଲେଘ | କ୍ଲାଉଡ୍ |
| device | ଉପକରଣ | ଡିଭାଇସ୍ |
| Client | ଗ୍ରାହକ | କ୍ଲାଏଣ୍ଟ |
Why this matters: In IT/software translation users searching documentation expect the terms they already use — translating “cloud” to ଲେଘ when everyone says କ୍ଲାଉଡ୍ creates a discoverability gap. In medical patient materials transliterating drug names (ଆସ୍ପିରିନ୍, ପାରାସିଟାମଲ୍) prevents pharmacy errors. In legal translation transliteration is more constrained — terms of art often have established Odia equivalents that must be used for legal validity.
Sample voice: addressing the user to take action¶
The Odia versions reshape sentences to address the user directly using ଆପଣ and imperative verb forms — producing translations that read as the product talking to the user, not at the user.
| US English | Odia target | Explanation |
|---|---|---|
| The password isn’t correct, so please try again. Passwords are case-sensitive. | ପାସ୍ୱାର୍ଡ ସଠିକ ନାହିଁ, ତେଣୁ ପୁନଃ ପ୍ରୟାସ କରନ୍ତୁ। ପାସ୍ୱାର୍ଡଗୁଡିକ କେସ୍-ସେନ୍ସିଟିଭ ଅଟନ୍ତି। | User entered incorrect password; provide short, friendly message with action to try again. |
| This product key didn’t work. Please check it and try again. | ଏହି ଉତ୍ପାଦ କୀ କାର୍ଯ୍ୟ କରୁ ନାହିଁ। ଦୟାକରି ଏହା ଯାଞ୍ଚ କରନ୍ତୁ ଏବଂ ପୁନଃ ଚେଷ୍ଟା କରନ୍ତୁ। | Casual and polite request to check and retry. |
| All ready to go | ସବୁକିଛି ପ୍ରସ୍ତୁତ ଅଛି | Casual short message confirming setup completion. |
| Would you like to continue? | ଆପଣ ଜାରି ରଖିବାକୁ ଚାହିଁବେ କି? | Second-person ଆପଣ to politely ask if user wants to continue. |
| Give your PC a name—any name you want. If you want to change the background color, turn high contrast off in PC settings. | ଆପଣଙ୍କ ପିସିକୁ ଏକ ନାମ ଦିଅନ୍ତୁ — ଆପଣ ଇଚ୍ଛା ମୁତାବକ ଯେକୌଣସି ଏକ ନାମ। ଯଦି ଆପଣ ପୃଷ୍ଠଭୂମି ରଙ୍ଗ ବଦଳାଇବାକୁ ଚାହୁଁଛନ୍ତି, ତେବେ ପିସି ସେଟିଂସରେ ଉଚ୍ଚ କଣ୍ଟ୍ରାଷ୍ଟ ଅଫ କରିଦିଅନ୍ତୁ। | Address user directly using second person to take action. |
Promoting a feature¶
| US English | Odia target | Explanation |
|---|---|---|
| Picture password is a new way to help you protect your touchscreen PC. You choose the picture—and the gestures you use with it—to create a password that’s uniquely yours. | ଆପଣଙ୍କର ଟଚ୍ସ୍ୱୀନ ପିସିକୁ ସୁରକ୍ଷିତ ରଖିବା ପାଇଁ ଛବି ପାସୱାର୍ଡ ଏକ ନୂଆ ଉପାୟ। ଆପଣଙ୍କ ନିଜର ଏକ ଅଦ୍ୱିତୀୟ ପାସ୍ୱାର୍ଡ ବନାଇବା ପାଇଁ ଆପଣ ଛବି — ଏବଂ ତାହା ସହିତ ବ୍ୟବହୃତ ସଂକେତକୁ ବାଛନ୍ତୁ। | Promote with em-dash for emphasis on specific feature requirements. |
| Let apps give you personalized content based on your PC’s location, name, account picture, and other domain info. | ଆପରିକେସନ୍ ଆପଣଙ୍କ ପିସିର ସ୍ଥାନ, ନାମ, ଏକାଉଣ୍ଟ ଛବି, ଏବଂ ଅନ୍ୟ ଡୋମେନ୍ ସୂଚନା ଉପରେ ଆଧାରିତ ହୋଇ ଆପଣଙ୍କୁ ବ୍ୟକ୍ତିଗତ ତଥ୍ୟ ପ୍ରଦାନ କରେ। | Use everyday word “PC” for familiarity. |
Providing how-to guidelines¶
| US English | Odia target |
|---|---|
| To go back and save your work, click Cancel and finish what you need to. | ପଛକୁ ଯାଇ ନିଜର କାର୍ଯ୍ୟକୁ ସଞ୍ଚୟ କରିବା ପାଇଁ କ୍ୟାନ୍ସେଲ କ୍ଲିକ୍ କରନ୍ତୁ ଓ ଆପଣ ସମ୍ପୂର୍ଣ୍ଣ କରିବାକୁ ଚାହୁଁଥିବା କାର୍ଯ୍ୟଟି କରନ୍ତୁ। |
| To confirm your current picture password, just watch the replay and trace the example gestures shown on your picture. | ଆପଣଙ୍କର ବର୍ତ୍ତମାନର ଛବି ପାସ୍ୱାର୍ଡକୁ ସୁନିଶ୍ଚିତ କରିବା ପାଇଁ, ପୁନଃ ପ୍ରଦର୍ଶନକୁ ଦେଖନ୍ତୁ। |
| It’s time to enter the product key. When you connect to the Internet, we’ll activate Windows for you. | ଡକ୍ୟୁମେଣ୍ଟ କୀ ପ୍ରବେଶ କରିବାର ସମୟ ହୋଇଯାଇଛି। ଯେତେବେଳେ ଆପଣ ଇଣ୍ଟରନେଟ ସହିତ ସଂଯୋଜନରେ ଆସନ୍ତି, ଆମେ ଆପଣଙ୍କ ପାଇଁ Windows ସକ୍ରୀୟ କରିଦେବୁ। |
Explanatory text and support¶
| US English | Odia target |
|---|---|
| The updates are installed, but Windows Setup needs to restart for them to work. After it restarts, we’ll keep going from where we left off. | ଏହି ଅଦ୍ୟତନଗୁଡିକ ପ୍ରବେଶ ହୋଇଗଲାଣି, କିନ୍ତୁ Windows ୮ ସେଟଅପ ଏଗୁଡିକୁ କାର୍ଯ୍ୟକାରୀ କରିବା ପାଇଁ ପୁନଃ ପ୍ରାରମ୍ଭ ଆବଶ୍ୟକ କରୁଛି। ଏହା ପୁନଃପ୍ରାରମ୍ଭ ହେବା ପରେ, ଆମେ ଯେଉଁଠୁ ଛାଡିଥିଲୁ ସେଠୁ ପୁଣି ଆରମ୍ଭ କରିବୁ। |
| If you restart now, you and any other people using this PC could lose unsaved work. | ଯଦି ଆପଣ ଏବେ ପୁନଃପ୍ରାରମ୍ଭ କରିବ, ତେବେ ଆପଣ ଓ ଏହି ପିସିକୁ ବ୍ୟବହାର କରୁଥିବା ଅନ୍ୟ ବ୍ୟକ୍ତି ମାନେ ଅସଞ୍ଚିତ କାର୍ଯ୍ୟ ହରେଇ ପାରନ୍ତି। |
Inclusive language¶
Inclusive language is communication that avoids habits leading unintentionally to marginalization, offense, misrepresentation, or perpetuation of stereotypes.
General principles:
- Comply with local language laws.
- Use plain, concrete, familiar words. Plain language helps people of all learning levels.
- Be mindful of regional references; if naming cities/countries/regions, avoid politically disputed ones; in examples referring to several regions, use equivalent references (don’t mix countries with states or continents).
- Represent diverse perspectives in text and images.
- Don’t generalize or stereotype by region, culture, age, or gender — even positively.
- Don’t use profane, derogatory, or military/politically charged terms.
Term replacements¶
| Use this (English) | Not this | Use this (Odia) | Not this (Odia) |
|---|---|---|---|
| primary/subordinate | master/slave | ପ୍ରାଥମିକ/ଅଧିନସ୍ଥ | ମାଲିକ/ଦାସ |
| perimeter network | demilitarized zone (DMZ) | ପେରିମିଟର ନେଟୱାର୍କ | ବିମିଲିଟ୍ରୀକରଣ ଜୋନ୍ (DMZ) |
| stop responding | hang | ପ୍ରତିକ୍ରିୟା ଦେବା ବନ୍ଦ କରନ୍ତୁ | ଝୁଲି ଯିବା |
| expert | guru | ବିଶେଷଜ୍ଞ | ଗୁରୁ |
| meeting | pow wow | ମିଟିଂ | ପାଓ ୱା |
| colleagues; everyone; all | guys; ladies and gentlemen | ସହକର୍ମୀ; ସମସ୍ତେ; ସମସ୍ତ | ଯୁବକ; ମହିଳା ଏବଂ ସଜ୍ଜନ |
| lunch and learn; learning session | brown bag session | ମଧ୍ୟାହ୍ନ ଭୋଜନ କରନ୍ତୁ ଏବଂ ଶିଖନ୍ତୁ; ଶିକ୍ଷଣ ଅଧିବେଶନ | ବ୍ରାଉନ୍ ବ୍ୟାଗ୍ ଅଧିବେଶନ |
| parent | mother or father | ପିତାମାତା | ମାତା କିମ୍ବା ପିତା |
Avoiding gender bias¶
Use gender-neutral alternatives. Avoid compounds containing gender-specific terms (ପୁରୁଷ, ସ୍ତ୍ରୀ ইତ୍ୟାଦି).
| Use this | Not this | Comments |
|---|---|---|
| ଛାତ୍ର | ବାଳକ ଛାତ୍ର / ବାଳିକା ଛାତ୍ର | Gender-specific terms for ‘student’ should not be used. ଛାତ୍ର is widely used in Odia as gender-neutral. |
| ଇଞ୍ଜିନିୟର | ପୁରୁଷ ଇଞ୍ଜିନିୟର / ମହିଳା ଇଞ୍ଜିନିୟର | A person should not be confined by gender. |
| ଡ୍ରାଇଭର | ମହିଳା ଡ୍ରାଇଭର / ପୁରୁଷ ଡ୍ରାଇଭର | No designation should be addressed on the basis of gender. |
| କବି | ମହିଳା କବି / ପୁରୁଷ କବି | Literary capability should not be judged by gender. |
When presenting generalization, use plural noun forms (e.g., ଲୋକ, ବ୍ୟକ୍ତି, ଛାତ୍ର, ইତ୍ୟାଦି):
| Use this | Not this | Comments |
|---|---|---|
| ଲୋକମାନେ | ଲୋକ | No gender-specific pronouns in Odia. When addressing mass people, use plural form. |
| ଛାତ୍ରମାନେ | ଛାତ୍ର | When addressing mass people, use plural form. |
Gender-specific pronouns are not used in Odia. For he/she, use ସେ; for him/her, use ତାଙ୍କୁ.
Accessibility¶
Focus on people, not disabilities. Don’t use words implying pity (ଏକ ଅକ୍ଷମତା କିମ୍ବା ଯେକୌଣସି ରୋଗରେ ପୀଡିତ). Don’t mention a disability unless it’s relevant.
| Use this | Not this | Use this (Odia) | Not this (Odia) |
|---|---|---|---|
| person with a disability | handicapped | ଅକ୍ଷମତା ଥିବା ବ୍ୟକ୍ତି | ଭିନ୍ନକ୍ଷମ or ଦିବ୍ୟାଙ୍ଗ |
| person without a disability | normal person; healthy person | ଅକ୍ଷମତା ନଥିବା ବ୍ୟକ୍ତି | ସାଧାରଣ ବ୍ୟକ୍ତି; ସୁସ୍ଥ ବ୍ୟକ୍ତି |
| Select | Click | େୟନ କେନ୍ତୁ | କିକି କେନ୍ତୁ |
Use generic verbs that apply to all input methods (touch, voice, mouse) — avoid verbs that don’t make sense with alternative input methods. Keep paragraphs short, aim for one verb per sentence, and spell out symbols like & (“ଏବଂ”) since screen readers misread them.
Language-specific grammar standards¶
Abbreviations¶
First letter of a word with a (.) indicates abbreviated form in Odia. Sometimes first two letters or first and last letter are used.
| Expression | Acceptable abbreviation |
|---|---|
| ବିଷୟ | ବି. |
| କ୍ରିୟା | କ୍ରି. |
| ବିଶେଷଣ | ବିଂ |
| କ୍ରିୟା ବିଶେଷଣ | କ୍ରି.ବିଂ |
| ଅବ୍ୟୟ | ଅ. |
| ଉପପଦ | ଉପ. |
| ଉପସର୍ଗ | ଉ. |
| ସ୍ୱରବର୍ଣ୍ଣ | ସ୍ୱ.ବ. |
| ତାରିଖ | ତା. |
| ପୂର୍ବ | ପୂ. |
| ଦକ୍ଷିଣ | ଦ. |
| ଉତ୍ତର | ଉ. |
| ପୁଂଲିଙ୍ଗ | ପୁଂ. |
| ସ୍ତ୍ରୀଲିଙ୍ଗ | ସ୍ତ୍ରୀ. |
| ଗ୍ରାମ୍ | ଗ୍ରା. |
| ଜିଲ୍ଲା | ଜି. |
| ପ୍ରଦେଶ | ପ୍ର. |
| ଡକ୍ଟର | ଡ. |
| କିଲୋମିଟର | କି.ମି. |
| କମ୍ପାନୀ | କୋ. |
| କ୍ରମିକ ନମ୍ବର | କ୍ର.ନଂ. |
| ଇନଫରମେସନ ଟେକନୋଲୋଜି | ଆଇ.ଟି. |
Use a non-breaking space (CTRL+SHIFT+SPACEBAR) inside abbreviations. If non-breaking spaces cannot be used (Help files, for example), write abbreviations without space to avoid orphan letters at line break.
Do not abbreviate currency, units, or measurement names: ପାଉଣ୍ଡ୍, ଡିଗ୍ରୀ, ରୁବେଲ, ୟୁଆନ୍, ୟେନ୍.
Acronyms¶
Acronyms are words made up of initial letters of major parts of a compound term (WYSIWYG, DNS, HTML).
Localized acronyms: On first instance in a text, spell out or transliterate the words, then keep the English version in brackets. Later occurrences use only the spelled-out form. Common Odia acronyms include: ଓ.ସା.ଏ (ଓଡ଼ିଶା ସାହିତ୍ୟ ଏକାଡେମୀ), ଉ.ପ୍ରା. (ଉଚ୍ଚ ପ୍ରାଥମିକ), ନି.ପ୍ରା. (ନିମ୍ନ ପ୍ରାଥମିକ), ଓ.ଭା.ପ୍ର. (ଓଡ଼ିଆ ଭାଷା ପ୍ରତିଷ୍ଠାନ), ଲ.ସା.ଗୁ (ଲଘିଷ୍ଠ ସାଧାରଣ ଗୁଣିତକ), ଗ.ସା.ଗୁ (ଗରିଷ୍ଠ ସାଧାରଣ ଗୁଣନୀୟକ).
Unlocalized acronyms: Standardized international acronyms remain untranslated and are only followed by English full spelling if the acronym needs to be explained. Examples: ANSI, ISO — do not localize or spell out.
Adjectives¶
Odia adjectives describe or modify another person or object. Adjectives usually precede the nouns but follow the pronouns. Examples: ଖରାପ ପିଲା (“bad child”), ଭଲ ପିଲା (“good child”).
Possessive adjectives in Odia:
| Subject pronoun | Possessive adjective |
|---|---|
| ମୁଁ (I) | ମୋର (my) |
| ତୁ (you) | ତୁମର (your) |
| ଆମେ (we) | ଆମର (our) |
| ତୁମେ (you formal) | ତୁମ୍ଭ (your formal) |
Example: ତାହା ମୋର ଫୋଲ୍ଡର ଅଟେ (“That’s my folder”) — ମୋର is the possessive adjective.
Articles¶
Odia has no articles. Many English error messages vary use of articles, demonstrative, and possessive pronouns — be consistent in Odia.
There are two demonstrative pronouns: e (this) and se (that), occurring with inanimate nouns. Variants are e/ehi/se/sei.
Possessive pronouns: mu, tumara, tara, eha, amar.
| English example | Odia example | Explanation |
|---|---|---|
| File already exists / The file already exists / This file already exists | ଫାଇଲ ପୂର୍ବରୁ ଅଛି | In complete sentences, use determiners consistently even if the US string does not. |
| Not enough memory to complete this operation. | ଏହି ବ୍ୟବସ୍ଥାକୁ ସମ୍ପୂର୍ଣ୍ଣ କରିବା ପାଇଁ ଯଥେଷ୍ଟ ମେମୋରି ନାହିଁ। | No need to use a demonstrative construction unless it’s important in context. |
| Windows cannot start your system. If the problem persists, contact your network administrator. | Windows ଆପଣଙ୍କ ସିଷ୍ଟମକୁ ପ୍ରାରମ୍ଭ କରିପାରୁନାହିଁ। ଯଦି ଏହି ଅସୁବିଧା ରହୁଛି ନିଜର ନେଟୱାର୍କ ପ୍ରଶାସକଙ୍କୁ ସମ୍ପର୍କ କରନ୍ତୁ। | Avoid possessive marker “your” unless ownership is important in context. |
Unlocalized feature names: Trademarked product names take no genitive “s” (no Microsoft’s products → Microsoft products / Products by Microsoft). Treat product and unlocalized feature names as proper nouns.
Localized feature names: Translated feature names are used like common nouns (with definite/indefinite article in English; in Odia, no article).
English borrowed terms: When facing an English loan word, consider: Motivation (does the English word integrate into Odia noun class?), Analogy (is there an equivalent Odia term?), Frequency (is it used in other technical documentation?). The article “the” in English is not used in Odia (The Homepage → ମୂଳପୃଷ୍ଠା).
Compounds¶
Compounds should be understandable and clear to the user. Overly long or complex compounds should be avoided by verbally expressing the relationship among various components. Unintuitive compounds are ultimately an intelligibility and usability issue.
In Odia, a compound noun is not merely juxtaposition of two independent words but a construction with underlying semantic structure. Two main types: subordinate constructions (one constituent modifies the other, endocentric) and coordinate constructions. Odia words fall into three etymological types: tatsama, tadbhava, and desaja.
Various types of modification in Odia compounds:
- Modified by noun in accusative case (case marker deleted in compound): machha-ku dhara → machhadhara (fish catching).
- Modified by a base with pai (for): khaiba pai tela (oil for eating).
- Modified by base with instrumental case marker -dwara or -re: machine-re buna (machine woven).
- Ablative case marker -ru: bilata-ru feranta (returned from foreign).
- Genitive case marker -ra: phala-ra rasa (juice of fruit).
- Joining words deleted: suna tiari hara (gold made chain).
- Coordinate compound with o/au: poka o joka (worm and leech).
- Idiomatic compounds: akasa-ganga (sky+river = milky way).
| English example | Odia example |
|---|---|
| Internet Accounts | ଇଣ୍ଟରନେଟ ଆକାଉଣ୍ଟ୍ସ |
| Logon script processing | ଲଗ ଅନ୍ ସ୍କ୍ରିପ୍ଟ ପ୍ରକ୍ରିୟାକରଣ |
| Internet News Server Name | ଇଣ୍ଟରନେଟ ସମାଚାର ସର୍ଭର ନାମ |
Compounds with product names (trademark unchanged, additions via hyphen or periphrastic construction):
| English example | Odia example |
|---|---|
| Windows password | Windows ପାସୱାର୍ଡ |
| Microsoft Word document | Microsoft Word ଲିଖିତ ପ୍ରମାଣପତ୍ର |
| Microsoft SQL Server Database | Microsoft SQL Server ଡାଟାବେସ୍ |
| Microsoft Dynamics product family | Microsoft Dynamics ଉତ୍ପାଦ ପରିବାର |
Compounds with acronyms, abbreviations or numerals:
| English example | Odia example |
|---|---|
| USB drive | USB ଡ୍ରାଇଭ |
| 3D Maps | 3D ମାନଚିତ୍ର |
| 24-bit color value | 24 ବିଟ ରଙ୍ଗ ମାନ |
| absolute URL | ସମ୍ପୂର୍ଣ୍ଣ URL |
Conjunctions¶
For modern Odia voice, use of conjunctions helps convey a conversational tone. Starting a sentence with a conjunction can convey an informal tone.
| en-US old | en-US new (conversational) |
|---|---|
| As |
But because of these features older content may not display correctly. |
| en-US source | Odia old | Odia new (conversational) |
|---|---|---|
| While data are saved on storage, it is not possible to add a new reader. | ଡାଟା ଷ୍ଟୋରେଜ୍ରେ ସଞ୍ଚୟ କରାଯାଉଥିବା ବେଳେ, ଏକ ନୂତନ ପାଠକ ଯୋଡିବାକୁ ଏହା ସମ୍ଭବ ନୁହେଁ। | ଯେତେବେଳେ ଡାଟା ଷ୍ଟୋରେଜ୍ରେ ସଞ୍ଚୟ କରାଯାଉଥିବା ବେଳେ, ଏକ ନୂତନ ପାଠକ ଯୋଡିବାକୁ ଏହା ସମ୍ଭବ ନୁହେଁ। |
| While the document is open, it is not possible to create a copy. | ଡକ୍ୟୁମେଣ୍ଟ ଖୋଲା ରହିଥିବା ଯୋଗୁ କପି କରିବା ସମ୍ଭବ ନୁହେଁ। | ଡକ୍ୟୁମେଣ୍ଟ ଖୋଲା ରହିଥିବା ବେଳେ, କପି କରିବା ସମ୍ଭବ ନୁହେଁ। |
| While your computer is being updated, you can keep working. | ଆପଣଙ୍କର କମ୍ପୁଟର ଅଦ୍ୟତନ କରୁଥିବା ସମୟରେ ଆପଣ କାର୍ଯ୍ୟ ଜାରି ରଖିପାରିବେ। | ଆପଣଙ୍କର କମ୍ପୁଟର ଅଦ୍ୟତନ ହେଉଥିବା ବେଳେ, ଆପଣ କାର୍ଯ୍ୟ ଜାରି ରଖି ପାରିବେ। |
Gender¶
In Odia, gender is not grammatical. Only animate subjects distinguish gender. Gender is indicated by sex via qualifying terms, different words, or suffixes.
Translators should recognize audience sensitivity to gender stereotypes. Use neutral language; create balance in role/function assignments. Use general terms like “people,” “users,” or “persons” instead of separately mentioning two genders.
Avoid writing sentences that refer to a single person whose gender is unknown — rewrite to make subject plural where possible. Don’t use “he or she,” “him or her,” or slashes to combine genders.
Strategies for gender-neutral Odia:
| Linguistic method | Example | Context |
|---|---|---|
| Use a neutral noun | ବ୍ୟକ୍ତି, ନେତା, ଗୋଷ୍ଠୀ, ନେତୃତ୍ୱଦକ୍ଷ, କର୍ମଚାରୀ, ବ୍ୟବହାରକାରୀ | Concept descriptions, explanations |
| Combined both genders by one common word such as ସେ | ସେ (he/she) | Only in exceptional cases — License Terms, table headers/titles |
Odia lexical gender exists for some nouns (Buddha-budhhi, Abhinetaa-Abhinetri, Sikhyaka-sikhyayitri) and adjectives (Sundara-sundari). Nouns with lexical gender don’t change pronouns; pronouns themselves don’t change in gender.
Rephrasing examples to avoid gender:
- “A custom dictionary can only be used by the user who created it.” → “A custom dictionary can only be used by the person who created it.” → ଗୋଟିଏ କଷ୍ଟମ ଡିକ୍ସନାରୀ ସେହି ବ୍ୟକ୍ତି ଦ୍ୱାରା ବ୍ୟବହୃତ ହୋଇପାରିବ କେବଳ ଯିଏ ଏହାକୁ ସୃଷ୍ଟି କରିଛି।
- “All users who use this feature” → “All who use this feature” → ସମସ୍ତେ ଯେଉଁମାନେ ଏହି ଫିଚରକୁ ବ୍ୟବହାର କରୁଛନ୍ତି।
- “If you have fun, your friends and relatives will be…” → “If one is having fun, friends and relatives will be…” → ଯଦି ଜଣେ କୌତୁକିଆ ଅଟନ୍ତି, ସାଙ୍ଗ ଓ ସମ୍ପର୍କୀୟମାନେ ହେବେ…
Genitive¶
Odia has six cases: nominative, accusative, genitive, instrumental, ablative, locative.
The genitive is adjectival in function: realized as -ro (singular) and -nko/-nko-ro (plural). The noun in genitive case collocates with other nouns and generally indicates possession. The oblique base of pronouns serves as base for all other cases and functions as genitive in isolation.
Pronoun oblique bases:
- 1st singular: mo (my)
- 2nd singular: to (your)
- 3rd singular: ta (his/her)
- 1st plural: amo (our)
- 2nd plural: tume (your)
- 3rd plural: se-mano-nko (their)
Examples: ei-ta mo ghoro (“This is my house”). To emphasize the relation: ei-ta mo:-ro ghoro tumoro nuhe (“this is my house, not yours”).
Twelve sambandha (relation) types in Odia genitive — examples covering kinship, master-servant, container-contained, part-whole, cause-effect, postpositional, metaphorical, extent, propositional, attributive, distinctional, purposive.
Genitive convention: Don’t attach genitive “s” to trademarked product names (“Microsoft Office Word,” not “Microsoft Office Word’s“). Lifeless materials (table, umbrella, etc.) don’t use English-style possessive: “leg of the table” → ଟେବୁଲର ଗୋଡ (not ଟେବୁଲ’ର ଗୋଡ); “hand of the umbrella” → ଛତାର ମୁଠା (not ଛତା’ର ମୁଠା).
Localizing colloquialism, idioms, and metaphors¶
Three options:
- Do not attempt to replace the source colloquialism with an Odia colloquialism unless it’s a perfect and natural fit.
- Translate the intended meaning (not literally), but only if the colloquialism’s meaning is integral and can’t be omitted.
- If the colloquialism can be omitted without affecting meaning, omit it.
Modifiers¶
Modifiers (words, phrases, clauses providing description) in Odia: adverbs and adjectives prototypically function as modifiers but have other functions. Other constituents can also function as modifiers.
| Type | Odia example |
|---|---|
| Adjective modifier | ମନୋନୀତ ଫାଇଲ ବହୁତ ବଡ କିମ୍ବା ବହୁତ ଛୋଟ ଅଛି (“The file selected is either too big or too small”) |
| Adverb modifier | Windows ସ୍ୱତଃସ୍ଫୂର୍ତ୍ତ ଭାବେ ଏହି ବାର୍ତ୍ତା ସଂଗୃହୀତ ହୋଇଛି (“Windows automatically archived this message”) |
Nouns¶
English loan words must be integrated into Odia noun class via motivation, analogy, or frequency criteria. In Odia, analogy refers to partial similarity and is noun-based.
| English example | Odia example |
|---|---|
| Delete it from server. | Server ରୁ ଏହାକୁ ଡିଲିଟ କରନ୍ତୁ |
| Enter a password to log into the server | Server କୁ ପ୍ରବେଶ କରିବା ପାଇଁ ଗୋଟିଏ ପାସୱାର୍ଡ ଲଗ କରନ୍ତୁ |
| DNS cannot resolve the server IP address | DNS server IP ଠିକଣାକୁ ସମାଧାନ କରିପାରିବ ନାହିଁ |
| Verify the name of the server’s certificate | Server ପ୍ରମାଣପତ୍ରର ନାମ ଯାଞ୍ଚ କରନ୍ତୁ |
Inflection of English loanwords for number in Odia:
| English example | Odia example |
|---|---|
| Clients | କ୍ଲାଏଣ୍ଟ୍ସ |
| Websites | ୱେବସାଇଟ୍ସ |
| Downloads | ଡାଉନଲୋଡ୍ସ |
| Proxys | ପ୍ରୋକ୍ସିସ୍ |
| Administrators | ଆଡ଼ମିନିଷ୍ଟ୍ରେଟର୍ସ |
Plural formation: Generally formed from singular by adding suffixes — ଫାଇଲ ଗୁଡିକ, ବ୍ୟବହାରକାରୀଗଣ, ଫୋଲ୍ଡର ଗୁଡିକ.
Prepositions¶
Many translators influenced by English omit prepositions or change word order. For modern Odia voice, use of prepositions helps convey conversational tone. Starting or ending a sentence with a preposition is acceptable.
| en-US old | en-US new |
|---|---|
| Developers can go to the application management site to find the apps for which they are looking. | Developers can go to the application management site to find the apps they are looking for. |
Pronouns¶
Odia has a distinctive script that cannot be easily confused with other Indian languages. Marked features of Odia language are found in its pronouns and verbs: ଆପଣ (you formal), ଆପଣଙ୍କର (your formal), ଆମ୍ଭେମାନେ (we), ଆମ୍ଭମାନଙ୍କର (our), ତମେ (you informal), ସେମାନେ (they).
Common Odia verb forms: ଖାଉଛି (eating), ଯାଉଛନ୍ତି (going honorific), କରିଛନ୍ତି (have done), ଶୁଣିଥିଲି (I had heard), ଯିବି (I will go), ଦେଖିବ (you will see), ଆଣିଥାନ୍ତି (would have brought), ଆସିଥାନ୍ତେ (would have come).
Punctuation¶
Bulleted lists: Same sign as in English.
Comma (“,”): Separator when several names or items are written consecutively; also for short pauses. The comma is the most versatile punctuation — indicates the smallest interruption in continuity of thought or sentence structure.
Colon (“:”): Same as English. Usually used after interjection or exclamation to indicate strong feeling. Example: Microsoft ଅନୁମୋଦନ କରୁଛି ଯେ ଉପଭୋକ୍ତା ଗଣ 1280 x 1024 କିମ୍ବା 1280 x 800 ର ଏକ ସର୍ବନିମ୍ନ ସ୍କ୍ରିନ ରିଜୋଲ୍ୟୁସନ୍ ଟର୍ନ୍ ଅନ୍ କରନ୍ତୁ:
Dashes and hyphens:
- Hyphen (-) divides words between syllables, links compound words, connects parts of inverted or imperative verb forms. Same as English. Examples: ଇ-ମେଲ, ଡ୍ରପ-ଡାଉନ୍.
- En Dash (–) [Alt+0150] structures sentences (indicating a clause summing up previous clauses, dividing more clearly). Used as minus sign (space before numeral: 225 – 17), for negative values (no space before numeral: –9 °C), and number ranges (1–10).
- Em Dash is not used in standard Odia writing.
Ellipses (…): Use in incomplete writings (story, novel) expected to continue in the next edition/chapter. Use with words like କ୍ରମଶଃ (continue), ଏହିପରି (so on). In exceptional cases (limited space, lots of content), ellipses can be used.
Period: Latin period (.) ends declarative sentences and follows many abbreviations. Odia has its own full-stop mark: । (daṇḍa). General rules:
- Always use the local daṇḍa (।) between adjoining messages where a string contains two sentences or phrases.
- End a long or punctuated sentence with the local daṇḍa. For translation, follow English structure and just replace full stop with daṇḍa wherever it occurs.
Sentence fragments (headers, button names, menu items, other non-complete-sentence text) take no full-stop/exclamation/question mark (except some TTS strings and single-word past-tense strings in notifications). Strings designed as “NPBODY” never take a full-stop even if they’re a full sentence.
Full-stop with parentheses: Belongs inside parentheses if they enclose an independent sentence; outside if the enclosed matter comes at the end of an including sentence.
Quotation marks: Two types — single (’ ‘), double (” “). Called udhruti chinha (ଉଦ୍ଧୃତି ଚିହ୍ନ). Both denote speech or quotation.
Parentheses: Same rules as for period above.
Sentence fragments¶
For modern Odia voice, sentence fragments help convey a conversational tone. Use whenever possible — short and to the point.
| en-US long form | en-US sentence fragment |
|---|---|
| Use the following steps. | Here’s how |
| en-US source | Odia long form | Odia sentence fragment |
|---|---|---|
| For more information, visit: | ଅଧିକ ସୂଚନା ପାଇଁ, ଭ୍ରମଣ କରନ୍ତୁ: | ଅଧିକ ସୂଚନା ଏଠାରେ ରହିଛି: |
| Select the account which… | ସେହି ଏକାଉଣ୍ଟକୁ େୟନ କେନ୍ତୁ ଯାହା… | ସେହି ଏକାଉଣ୍ଟ େୟନ କେନ୍ତୁ ଯାହା… |
| Select the object you want to change. | ଆପଣ ପରିବର୍ତ୍ତନ କରିବାକୁ ଚାହୁଁଥିବା ଅବଜେକ୍ଟ େୟନ କେନ୍ତୁ। | ପରିବର୍ତ୍ତନ ପାଇଁ ଅବଜେକ୍ଟ େୟନ କରନ୍ତୁ। |
Subjunctive¶
The subjunctive is a verb mood expressing speaker’s reaction (doubt, uncertainty, denial, desire/wish, command, emotional attitude). In Odia, subjunctive mood is specifically associated with past tense + hoithante (ହୋଇଥାନ୍ତେ).
Example: “If my father was a teacher, he would teach me” → ଯଦି ମୋ ବାପା ଜଣେ ଶିକ୍ଷକ ହୋଇଥାନ୍ତେ ତେବେ ସେ ମୋତେ ପଠା ପଢାଇଥାନ୍ତେ।
Symbols and non-breaking spaces¶
A symbol represents something else by association/resemblance/convention.
| Symbol | Meaning in Odia |
|---|---|
| ☺ | ହସ (smile) |
| ☼ | ସୂର୍ଯ୍ୟ (sun) |
| ♥ | ପ୍ରେମ (love) |
| =D> | ତାଳି ମାରିବା (clapping) |
| ♀ | ସ୍ତ୍ରୀ (female) |
| ♫ | ସଙ୍ଗୀତ (music) |
The non-breaking space (HTML ) prevents line breaks between elements that belong together. Example: ଲୋଡ କରୁଛି…
Verbs¶
For modern Odia voice, simple tenses help convey clarity. Simple present is easiest to understand. Avoid future tense unless describing something that will really happen in the future and simple present is inapplicable. Use simple past for events that already happened.
Sometimes an English verb can be used as a loan word in Odia, following Odia syntactic/morphological rules.
| English | Odia verbal noun | Odia past | Odia present continuous |
|---|---|---|---|
| chat | ଚାଟ କରିବା | ଚାଟ କଲି | ଚାଟ କରୁଛି |
| crawl | କ୍ରଲ କରିବା | କ୍ରଲ କଲି | କ୍ରଲ କରୁଛି |
| debug | ଡିବଗ୍ କରିବା | ଡିବଗ୍ କଲି | ଡିବଗ୍ କରୁଛି |
Continuous operations (English gerund) translated into Odia:
- Send—Sending: ପ୍ରେରଣ — ପ୍ରେରଣ କରୁଛି
- Edit—Editing: ସମ୍ପାଦନ — ସମ୍ପାଦନ କରୁଛି
- Delete—Deleting: ବିଲୋପ — ବିଲୋପ କରୁଛି
Localization considerations¶
Accessibility¶
Some accessible products and services may not be available in Odia-speaking markets. General accessibility information at https://www.microsoft.com/en-us/accessibility/.
Applications, products, and features¶
Application/product names are often trademarked and rarely translated. Feature names are occasionally trademarked too (IntelliSense™). Before translating any application, product, or feature name, verify that it is in fact translatable and not protected.
Odia has no specific rules for trademarking applications, products, and features.
Version numbers always contain a period (e.g., Version 4.2). Example: WCAG 6.2 → WCAG 6.2.
Translation of version strings: Version strings containing copyright information should always be translated. Use approved translations for “All rights reserved” and “Microsoft Corporation” from Microsoft Terminology.
Trademarks¶
Trademarked names and the name Microsoft Corporation shouldn’t be localized unless local laws require translation and an approved translated form is available. List of Microsoft trademarks at https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks.
Error messages¶
Error messages are messages sent by system or program informing the user of an error that must be corrected for the program to continue running. They can prompt action or inform of an error requiring reboot.
Translators should apply modern voice principles to ensure target translation is natural, empathetic, not robot-like.
| English Term | Correct Odia translation |
|---|---|
| Something went wrong. | କିଛି ଭୁଲ ହୋଇଛି। |
| Not enough memory to process this command. | ଏହି ନିର୍ଦ୍ଦେଶ ପ୍ରକ୍ରିୟାଗତ କରିବାକୁ ପର୍ଯ୍ୟାପ୍ତ ମେମୋରୀ ନାହିଁ। |
Use consistent terminology and language style. Main principles: clarity, comprehensibility, consistency.
Standard phrases in error messages — try to use these consistent target phrases:
| English phrase | Odia preferred example |
|---|---|
| Cannot / Could not | ଫାଇଲ ଖୋଲିହେବ ନାହିଁ |
| Failed to… / Failure of… | ସମ୍ପର୍କ ସ୍ଥାପନ କରିବାରେ ବିଫଳ ହେଲା |
| Cannot find / Could not find / Unable to find / Unable to locate | ଡ୍ରାଇଭର ସଫ୍ଟୱେୟାର ଖୋଜିପାରୁ ନାହିଁ |
| Not enough / Insufficient / There is not enough memory | ଯଥେଷ୍ଟ ମେମୋରୀ ନାହିଁ |
| …is not available / …is unavailable | ନିର୍ଦ୍ଦେଶ ମିଳୁ ନାହିଁ |
Error messages with placeholders: %d, %ld, %u, %lu mean <number>; %c means <letter>; %s means <string>. In Odia, numeral placeholders typically precede the noun (e.g., %d ଦିନରେ; %d ମିନିଟରେ).
| English example | Message user sees | Odia example |
|---|---|---|
| Replace invalid %s? | Replace invalid file? | ଅବୈଧ %s ବଦଳାଅ? |
| %s already exists | File already exists / Name already exists | %s ପୂର୍ବରୁ ରହିଛି |
| %s is now set as your personal contact. | Regina is now set as your personal contact | ଆପଣଙ୍କର ବ୍ୟକ୍ତିଗତ ଠିକଣାରେ ବର୍ତ୍ତମାନ %s ସେଟ ହୋଇଛନ୍ତି। |
| %s stopped working and was closed | The application stopped working and was closed | %s କାର୍ଯ୍ୟ କରିବା ବନ୍ଦ କରିଛି ଏବଂ ବନ୍ଦ ହୋଇଯାଇଛି |
Keys¶
References to key names appear in normal text. Names of keys appearing on the keyboard should not be translated.
| English Key Name | Odia Key Name |
|---|---|
| Alt | Alt |
| Backspace | Backspace |
| Caps Lock | Caps Lock |
| Ctrl | Control |
| Delete | Delete |
| Down Arrow | ନିମ୍ନ ତୀର |
| End | End |
| Enter | Enter |
| Esc | Escape |
| Home | Home |
| Insert | Insert |
| Left Arrow | ବାମ ତୀର |
| Num Lock | Num Lock |
| Page Down | Page Down |
| Page Up | Page Up |
| Right Arrow | ଡାହାଣ ତୀର |
| Scroll Lock | Scroll Lock |
| Shift | Shift |
| Spacebar | ସ୍ପେସବାର |
| Tab | Tab |
| Up Arrow | ଉପର ତୀର |
| Windows key | Windows କୀ |
| Menu Key | ମେନୁ କୀ |
| Print Screen | Print Screen |
Keyboard shortcuts¶
Odia follows InScript keyboard. Recommendation: do not localize keyboard shortcuts — even localized, they wouldn’t be consistent with other Indic languages, and Odia has strong transliteration support in native search engines, text editors, mail websites.
| Keyboard shortcut special option | Allowed? | Notes |
|---|---|---|
| “Slim characters” (I, l, t, r, f) | Yes | Odia characters cannot be termed “slim” compared to Roman ones. |
| Characters with downstrokes (g, j, y, p, q) | No | Odia characters are not written simply with downstroke but with downward movement. |
| Extended characters | No | Odia conjuncts (combinations of two consonants) cannot be used. Simple Odia letters (e.g., ହ) not considered extension of others. |
| Letter between brackets after item name | No | Such letters, if they occur, cannot be used as shortcuts. |
| Number between brackets after item name | Yes | Numbers can be used as keyboard shortcuts. |
| Punctuation sign between brackets after item name | No | Punctuation not needed when many clear/simple letters are available. |
| Duplicate keyboard shortcuts | Yes | Allowed when no other character is available, with instruction from MS. |
| No keyboard shortcut when no characters available | No | Cannot be left unassigned for minor options. |
Odia has 19 single-stroke characters usable as keyboard shortcuts: ବ, ହ, ଗ, ଦ, ଜ, ଡ, ପ, େ, କ, ତ, ର, ଟ, ୟ, ମ, ନ, ବ, ଲ, ସ, ଯ. Numbers 0-9 are also allowed (all case-insensitive).
Term distinctions:
- Access key: Subtype of keyboard shortcut. Letter or number used to access UI controls with text labels. Most use Alt key (e.g., F in Alt+F). UI marking: H&ome.
- Key tip: Letter/number appearing in ribbon when Alt is pressed. Last character after “
" in localization strings (Home\H). - Shortcut key: Subtype of keyboard shortcut. Key combination performing common action without UI navigation. Most use Ctrl key (Ctrl+N, Ctrl+V). Ctrl+letter and function keys (F1-F12) are usually best for shortcut keys.
Numeric keypad¶
Recommend avoiding distinguishing numeric keypad keys from other keys unless required by the application. If it’s not obvious which keys to press, provide explanations.
Standard shortcut keys (selected)¶
| US Command | US Shortcut Key | Odia Command | Odia Shortcut |
|---|---|---|---|
| Help window | F1 | ସହାୟତା ୱିଣ୍ଡୋ | F1 |
| Cancel | Esc | ବାତିଲ | Esc |
| Activate/Deactivate menu bar mode | F10 | ମେନୁ ଦଣ୍ଡିକା ମୋଡ ସକ୍ରିୟ/ନିଷ୍କ୍ରିୟ କରନ୍ତୁ | F10 |
| Switch to next primary application | Alt+Tab | ପରବର୍ତ୍ତୀ ପ୍ରାଥମିକ ଆପ୍ଲିକେସନକୁ ସୁଇଚ୍ କରନ୍ତୁ | Alt+Tab |
| Close active application window | Alt+F4 | ସକ୍ରିୟ ଆପ୍ଲିକେସନ ୱିଣ୍ଡୋ ବନ୍ଦ କରନ୍ତୁ | Alt+F4 |
| Access Start button in taskbar | Ctrl+Esc | ଟାସ୍କବାରରେ ଆରମ୍ଭ ବଟନ୍ ପ୍ରବେଶ କରନ୍ତୁ | Ctrl+Esc |
| File New | Ctrl+N | ଫାଇଲ ନୂତନ | Ctrl+N |
| File Open | Ctrl+O | ଫାଇଲ ଖୋଲନ୍ତୁ | Ctrl+O |
| File Close | Ctrl+F4 | ଫାଇଲ ବନ୍ଦ କରନ୍ତୁ | Ctrl+F4 |
| File Save | Ctrl+S | ଫାଇଲ ସଞ୍ଚୟ କରନ୍ତୁ | Ctrl+S |
| File Save as | F12 | ଭାବେ ଫାଇଲ ସଞ୍ଚୟ କରନ୍ତୁ | F12 |
| File Print | Ctrl+P | ଫାଇଲ ମୁଦ୍ରଣ | Ctrl+P |
| File Exit | Alt+F4 | ଫାଇଲ ପ୍ରସ୍ଥାନ | Alt+F4 |
| Edit Undo | Ctrl+Z | ପୂର୍ବବତ ସମ୍ପାଦନ କରନ୍ତୁ | Ctrl+Z |
| Edit Cut | Ctrl+X | ଛେଦନ ସମ୍ପାଦନ | Ctrl+X |
| Edit Copy | Ctrl+C | କପି ସମ୍ପାଦନ କରନ୍ତୁ | Ctrl+C |
| Edit Paste | Ctrl+V | ପେଷ୍ଟ ସମ୍ପାଦନ କରନ୍ତୁ | Ctrl+V |
| Edit Select All | Ctrl+A | ସମସ୍ତ େୟନ ସମ୍ପାଦନ କରନ୍ତୁ | Ctrl+A |
| Edit Find | Ctrl+F | ସନ୍ଧାନ ସମ୍ପାଦନ କରନ୍ତୁ | Ctrl+F |
| Italic | Ctrl+I | ଇଟାଲିକ | Ctrl+I |
| Bold | Ctrl+G | ବୋଲ୍ଡ | Ctrl+G |
| Underlined / Word underline | Ctrl+U | ରେଖାଙ୍କିତ / ଶବ୍ଦ ରେଖାଙ୍କିତ | Ctrl+U |
| Centered | Ctrl+E | କେନ୍ଦ୍ରୀୟ | Ctrl+E |
| Left aligned | Ctrl+L | ବାମ ଶ୍ରେଣୀବଦ୍ଧ | Ctrl+L |
| Right aligned | Ctrl+R | ଡାହାଣ ଶ୍ରେଣୀବଦ୍ଧ | Ctrl+R |
| Justified | Ctrl+J | ଉପଯୁକ୍ତ | Ctrl+J |
Voice video considerations¶
A good Odia voice video addresses only one intent (one customer problem), is not too long, has high audio quality, has visuals that add information, and uses the right language variant/dialect/accent in voiceover.
Successful techniques:
- Focus on the intent. Show best way to achieve the most common task and stick to it.
- Show empathy. Understand and acknowledge the viewer’s situation.
- Use SEO. Include search phrases in title, description, headers.
- Talk to the customer as if they’re next to you, watching you explain.
- Record a scratch audio file. Check for length, pace, and clarity.
English pronunciation¶
English terms and product names left unlocalized should be pronounced the English way. If your language has an established pronunciation for some common term (such as “server”), local pronunciation should be used. Pronunciation can be adapted to Odia phonetic system if original sounds very awkward in Odia.
| Example | Phonetics |
|---|---|
| SecurID | [sɪ’kjuər aɪ diː] |
| .NET | [dot net] |
| Skype | [skaip] |
Acronyms pronounced like real words, adapted to local pronunciation:
| Acronym | Odia phonetics |
|---|---|
| RADIUS | ରାଡିୟସ୍ |
| RAS | ରେସ୍ |
| ISA | ଆଇଏସଏ |
| LAN | ଲେନ୍ |
| WAN | ୱାନ୍ |
| WAP | ୱାପ |
| MAPI | ମାପି |
| POP | ପପ |
| URL | ୟୁଆରଏଲ |
Other abbreviations pronounced letter by letter: ICMP (ଆଇସିଏମପ), IP (ଆଇପି), TCP/IP (ଟିସିପି/ଆଇପି), XML (ଏକ୍ସଏମଏଲ), HTML (ଏଚଟିଏମଏଲ), OWA (ଓଡବ୍ଲିଏ), SQL (ଏକ୍ୟୁଏଲ).
URLs: “http://” should be left out. “www” pronounced as ଡବ୍ଲିୁଡବ୍ଲିୁଡବ୍ଲିୁ. The “dot” may be omitted or read out (then pronounced ଡଟ in Odia).
Example: http://www.microsoft.com/en-in → ଡବ୍ଲିୁଡବ୍ଲିୁଡବ୍ଲିୁଡଟ ମାଇକ୍ରୋସଫ୍ଟ ଡଟ କମ.
Punctuation marks mostly implied by voice (? ! : ; ,). En dash (–) used to emphasize an isolated element — pronounced as a comma (short pause).
Special characters (/ \ ˘ < > + -) pronounced using Odia translations approved in Microsoft Terminology.
Tone¶
Use a tone matching the target audience. More informal/playful for most Microsoft products, games; formal/informative/factual for technical texts.
Tone should be appropriate for the audience: address with appropriate tone, level of grammar, formality, and reading level. Easy to understand.
Example: “You are now connected to the Internet.” → ବର୍ତ୍ତମାନ ଆପଣ ଇଣ୍ଟରନେଟ ସହ ସଂଯୁକ୍ତ ହେଲେ।
Video voice checklist¶
- Apply principles: single intent, clarity, everyday language, friendliness, relatable context.
- Title includes the intent and keywords for search.
- Intro (10 seconds): put the problem into a relatable context.
- Action and sound: keep something happening visually and audibly while maintaining appropriate pace; synchronize visuals with voice-over.
- Visuals: guide the eye through the procedure with smooth pointer motions, judicious callout use, appropriate motion graphics and branding-approved visuals.
- Ending: recaps are unnecessary.
Reference materials: authoritative Odia language references¶
Use these normative sources for orthography, grammar, terminology when this guide doesn’t specify. Deviation from them automatically fails most strings.
- Sarbasara Byakarana — Ed. Narayana Mahapatra, Sridhara Das, Red. 2001.
- Purnachandra Odia Bhasakosa — Ed. Gopal Chandra Praharaj, 1931-40.
- Sabdatatwabodha Abhidhana — Ed. Gopinath Nandasarma; Red. 1995.
- Oriya Bhashakosha — Ed. Girish Chandra Misra & group of Editors, 1997-2006.
- Oxford English-Oriya Dictionary — Ed. K.M. Pattanaik, B.K. Tripathy; 2004.
- Modern Oriya Grammar and Composition — Dr. Kishore Chandra Dash and Jay Krushna Mishra, 2006.
- A Synchronic Grammar of Oriya — Bijay Prashad Mahapatra, CIIL, 2007.
Informative references (supplementary):
- Evolution of Oriya Language and Script — K.B. Tripathy (1956)
- The People, Language and Culture of Orissa — Suniti Kumar Chatterji (1966)
- Matrubhasa Oriya — Bijaya Prasad Mahapatra, 2001
FAQ¶
What’s the modern register for Odia translation across professional contexts?¶
Warm, conversational, scannable. Applies to medical patient materials, marketing copy, software UI, consumer-facing legal documents. Sworn legal translation and pure technical specifications retain more formal register.
When should I transliterate English terms vs. translate them into Odia?¶
Transliterate when the English term is in daily Odia speech and no natural Odia equivalent exists or feels comfortable to users (ୱାଲେଟ୍, କ୍ଲାଉଡ୍, ଡିଭାଇସ୍, କ୍ଲାଏଣ୍ଟ). Translate when a natural Odia term is widely used. Goal: the UI should be easy to use and represent local Odia at full strength.
How should I address users in Odia translation?¶
Address directly with ଆପଣ (second-person formal). Avoid third-person ଉପଭୋକ୍ତା/ବ୍ୟବହାରକାରୀ (“user”) in consumer-facing text — it sounds formal and impersonal. Imperative voice (େୟନ କେନ୍ତୁ — “select”) is standard for instructions.
What punctuation differences should I respect in Odia translation?¶
Odia has its own full-stop mark (।) — use it at end of declarative sentences, not the Latin period. Quotation marks (’ ‘/ ‘’ ‘’) match English usage. Sentence fragments (headers, button names, menu items) take no terminal punctuation.
Which Odia normative references should I follow?¶
Sarbasara Byakarana (Ed. Narayana Mahapatra, 2001), Purnachandra Odia Bhasakosa (1931-40), Oriya Bhashakosha (Misra et al., 1997-2006), Oxford English-Oriya Dictionary (Pattanaik & Tripathy, 2004), Modern Oriya Grammar and Composition (Dash & Mishra, 2006), A Synchronic Grammar of Oriya (Mahapatra, CIIL, 2007).
How does Odia handle gender in translation?¶
Gender is not grammatical in Odia. Only animate subjects distinguish gender via lexical means (different words, suffixes), not via grammatical agreement. Use neutral plural nouns (ଲୋକମାନେ, ଛାତ୍ରମାନେ) and neutral pronoun ସେ. Avoid stereotyped role assignments.
How should I handle compounds in Odia translation?¶
Avoid overly long or complex compounds. Express the relationship verbally (periphrastically) when a single compound becomes opaque. Compounds with product names use hyphens or paraphrase rather than direct concatenation (Windows ପାସୱାର୍ଡ, not Windows-ପାସୱାର୍ଡ).