Manipuri (Bengali script, India) style guide

Apply these local conventions alongside the house voice and localization review. Source acknowledgments are in credits.

Address and terminology

Write clear, respectful Manipuri. Use অদোম for formal address in this guide's product writing. Keep that register consistent across related screens and help pages. Shorter text must still preserve who acts, what changes and whether the result is certain.

This page uses Bengali-script Manipuri, following the supplied locale guide. It does not cover Meetei Mayek spelling. Confirm the intended script before translation; Bengali-script text is not a substitute for a Meetei Mayek deliverable, and sharing a script does not make Manipuri and Bengali interchangeable languages.

Use approved terminology and review the complete phrase. A natural translation can change word order, split a sentence or omit an unnecessary pronoun. It must retain a required actor, owner, object, limit or condition. Avoid word-for-word substitution rules derived from an English example.

Spelling and abbreviations

Bengali script has no uppercase/lowercase distinction. Retained Latin names and identifiers keep their required case. Preserve vowel signs, nasal marks and consonant distinctions in verified Manipuri spellings. A generic instruction about deleting Devanagari nuktas does not apply to this script.

Abbreviate only when the result stays clear. The supplied Monday abbreviation is নিংথৌ, from নিংথৌকাবা. This is a specific lexical abbreviation, not permission to cut any word at an arbitrary position. Ordinary UI abbreviations in the supplied convention do not acquire a final dot solely because English uses one.

The plural marker শিং occurs in forms such as এম.পি.শিং. Preserve plurality in the whole message; do not either append the marker to every acronym or remove it everywhere because abbreviations are said to be invariant. Review lexical abbreviations, spelled-out letter names and complete count expressions separately.

Keep familiar acronyms such as USB and HTML when appropriate. Explain unfamiliar ones in Manipuri. A transliteration of an acronym's letters is not an explanation of its meaning. Keep literal strings such as http and www in their required case.

Punctuation and numbers

Use punctuation to distinguish complete sentences from short UI phrases. Apply the shared punctuation conventions to surrounding prose, and use house UI formatting instead of adding quotation marks around every label. Recast a cumbersome dash-separated sentence without losing a condition or changing a range endpoint.

Use অমসুং for “and” in prose. Keep & when it belongs to a protected name, a token or literal input. Do not replace characters inside markup as if they were ordinary words.

Bengali digits are ০১২৩৪৫৬৭৮৯. Use the product's agreed numeral convention and test its locale formatter. A date such as ০১/০৪/২০২৫ uses day–month–year order. Keep a month-and-year source at that precision, including the month; changing it to a bare year loses information. Do not localize the period or digits inside a protected version such as 4.2.

Keep exact measurements and values numeric. Use 30 cm, 1 h and 20 °C, with a nonbreaking space between value and unit. The minus in −10 °C is not an en dash. Unit symbols keep their fixed spelling and case. Test percentages separately rather than applying a universal spacing rule.

Inclusive and interface review

Avoid unnecessary gender labels and stereotypes. An absence of grammatical gender in a construction does not mean that the language has no words referring to gender. A rewrite must preserve a relevant person, role and ownership relation; do not treat “document” as an automatic replacement for “their document.”

Follow accessible content and preserve the required interface action. Selection, clicking and typing are different tasks. Check complete count messages, placeholders and screen-reader wording with a proficient Manipuri reviewer. Check rendering and copy/paste in the agreed script using scripts and typography.