This guide adapts rules and examples from Microsoft’s Kashmiri (Devanagari) Localization Style Guide (originally written for software/UI localization). The underlying linguistic rules apply broadly — to legal, medical, marketing, and any Kashmiri Devanagari translation work. Restructured and reformatted as a general translator reference by ChatsControl.

Kashmiri (Devanagari) Translation Style Guide — Voice, Word Choice & Common Pitfalls (Legal, Medical, Marketing, IT)¶

TL;DR¶

• Kashmiri (Devanagari) translation across spheres (legal, medical, marketing, IT) uses warm, conversational, scannable register — literal translation produces unnatural, sometimes ridiculous Kashmiri.
• Devanagari script conventions apply: full stop is danda (।), no space before punctuation, Devanagari numerals (० १ २ ३ ४ ५ ६ ७ ८ ९) instead of Arabic digits.
• Nuqta (़) is a diacritic for non-native sounds borrowed from Urdu, Arabic, Farsi and English — apply per established convention; some Persian-origin words tolerate Nuqta-less spellings.
• Avoid gendered titles (पुरुष उस्ताद / जननी उस्ताद) — use neutral forms (उस्ताद, डॉक्टर) that cover both genders, and use generic verbs (चुनिव, not क्लिक करीव) that work across input methods.
• Acronyms follow no-period convention (PDF → पीडीएफ़्स) with masculine gender for device/tool acronyms; well-known English acronyms (CD, IIT) stay in Latin script.

Register and tone for modern Kashmiri (Devanagari) translation¶

Register is the level of formality, warmth, and conversational ease the target text projects. The modern Kashmiri (Devanagari) register for consumer-facing content is warm and relaxed, crisp and clear, and ready to lend a hand — short, easy-to-read sentences, not literal translations. Be pleasant; keep explanations appropriate for the audience and as enjoyable to read as possible. Slang is to be avoided; colloquialism is allowed in moderation — a conversational tone is fine when you stay professional.

Literal translation should be avoided. It often fails to carry intended meaning and sounds unnatural, even ridiculous. Split or merge sentences when needed.

Why this matters: Bureaucratic, literal Kashmiri damages outcomes across spheres. In marketing copy it kills conversion — readers disengage when text reads as foreign-imported instead of native Kashmiri. In patient-facing medical materials it reduces comprehension and compliance — patients skip what they cannot parse. In software UI it produces button labels users hesitate over. In consumer-facing legal documents (privacy notices, terms of service) it produces text regulators increasingly reject in favor of plain language. Only sworn legal translation and pure technical specifications retain the older formal register.

Tone of voice and form of address¶

Why this matters: The address-form decision propagates across legal documents (the consumer must be addressed consistently), medical patient leaflets (the second-person form determines how directly instructions land), marketing copy (familiar vs. formal “you” shifts emotional tone), and software UI (the entire interface voice cascades from this one choice). Inconsistency between formal and informal address signals careless translation.

Abbreviations¶

Abbreviations save space, especially in UI strings, but they must follow Kashmiri Devanagari conventions, not English ones.

• In Kashmiri (Devanagari), abbreviated terms follow conventions similar to other Devanagari-script languages, with context-driven variation.
• A period is generally used after an abbreviated term, especially for initialisms or acronyms — paralleling English use after “Dr.” or “Mr.”
• Example: श्री. for “श्रीमान”
• Abbreviations can be pluralized by adding the plural marker after the abbreviation, often keeping the period.
• Example: numbers (नंबरस) abbreviates to नं.

Why this matters: Abbreviation discipline matters most where space is scarce and ambiguity is expensive. Medical prescriptions and dosing labels use heavy abbreviation — the wrong period or missing plural marker can change a dispensed quantity. Legal contracts define abbreviations on first use; inconsistent later expansion creates dispute risk. IT/software UI labels lose meaning when truncated incorrectly. Marketing taglines that mix English-style and Devanagari-style abbreviation look careless.

Acronyms¶

Acronyms are words made up of the initial letters of major parts of a compound term. Examples include DNS (Domain Name Server) and HTML (Hypertext Markup Language).

• Acronyms typically do not have periods. Plural markers can be added if necessary, especially for informal contexts.

• Gender assignment to acronyms does not always follow strict grammatical patterns. It depends on context, usage, and analogy to existing words. For example, USB — treated as a device or tool — takes masculine gender, following the pattern for words referring to instruments, machines, or technology. Many devices take masculine gender in Kashmiri (Devanagari).
• When using an English acronym throughout a text, on first occurrence write full form (acronym). In subsequent occurrences, use only the acronym.
• Some English acronyms are kept in English due to wide acceptance and usage.
• Examples: CD, IIT

Why this matters: Acronym handling is high-leverage across spheres. Legal drafting must define every acronym on first use and never silently switch case or script — a contract referencing both “PDF” and “पीडीएफ” inconsistently creates ambiguity. Medical translation handles many English-origin acronyms (MRI, CT, ICU) — keep widely-accepted ones in Latin script per the convention. IT/software documentation gets the acronym density wrong constantly — every protocol, every format is an acronym, and consistent gender plus consistent script choice keeps the text scannable. Marketing brand acronyms must align with the brand’s chosen presentation.

Capitalization¶

Capitalization does not apply to Kashmiri (Devanagari). Devanagari has a single form per letter — no upper- and lowercase distinction exists in the script.

Why this matters: A common machine-translation artifact is preserving English-source capitalization patterns in the target — capitalized first letters mid-sentence, title-case headers — which is meaningless in Devanagari and signals untouched MT output. Legal translators must remember that emphasis through capitalization (the English convention of ALL-CAPS warnings in contracts) needs a different mechanism in Kashmiri Devanagari (bold, repetition, or restructured wording).

Punctuation¶

Punctuation in Kashmiri (Devanagari) generally follows other Devanagari-script languages, with distinct adaptations specific to Kashmiri.

Full stop (danda)¶

The full stop in Kashmiri (Devanagari) is represented by the danda (।) — a vertical line placed at the end of a sentence. It marks the end of declarative sentences or completed thoughts.

Just as in Hindi and other Devanagari languages, commas and periods are not preceded by a space.

Bulleted lists¶

Bulleted lists present information in a clear, organized manner. Punctuation depends on whether items are complete sentences or phrases:

• Complete sentences in bulleted lists end with the danda (।) or appropriate punctuation (question marks, exclamation marks).
• Incomplete phrases or items typically take no end punctuation.
• A colon (:) introduces a bulleted list.

Dashes and hyphens¶

Hyphen¶

The hyphen (-) is the shortest of the three dash characters. Use hyphens for:

• Compound words
• Breaking words at the end of a line
• Page numbers, dates, and other number intervals
• To establish relationships between two concepts

En dash¶

The en dash (–) is obtained with Alt + 0150 or Ctrl + - (num) in Windows. Use for arithmetic operations and negative numbers.

Em dash¶

The em dash (—) is obtained with Alt + 0151 or Ctrl + Alt + - (num) in Windows. Avoid extensive use of the English em dash; substitute commas or parentheses, or start a new sentence. Feel free to drop the em dash so the sentence reads more naturally in Kashmiri (Devanagari).

Quotation marks¶

Straight quotation marks (” “) are used in Kashmiri (Devanagari). Use them for direct speech, quotations, or to highlight specific terms or phrases.

Why this matters: Punctuation conventions are sphere-critical. In legal documents the danda terminates clauses with the same legal weight a period carries in English — using a Latin period instead introduces interpretive doubt. In medical instructions, bullet-list punctuation rules determine whether each bullet reads as a complete instruction or a fragment depending on the same sublist. In IT/software UI strings, em-dash overuse imported from English creates lines that don’t wrap well in Devanagari rendering. In marketing copy, mismatched quotation styles (curly vs. straight) signal sloppy production.

Usage of Nuqta¶

The Nuqta is a diacritic used in the Devanagari script to describe modern sounds borrowed from languages not native to Devanagari — mainly Urdu (Arabic, Farsi) and English. It is a dot, used in letters like क़ in क़ुरान.

Nuqta is not used for native Kashmiri sounds already represented by standard Devanagari consonants.

Exceptions¶

While Nuqta is generally used to represent specific foreign sounds, exceptions exist — particular words might deviate from the general pattern. These arise from language evolution, regional variation, or influence of other scripts like Urdu.

Example: ख़ुशबू (Khushboo) — fragrance. Although the word comes from Persian, it is sometimes written as खुशबू, without Nuqta, especially in casual settings or older literature.

Why this matters: Nuqta application is a recurring source of inconsistency across professionally translated text. In legal documents proper-name spellings (places, persons, parties to a contract) must remain identical across all references — sliding between क़ुरान and कुरान in a contract creates referential ambiguity. In medical drug-name transliteration, Nuqta affects pronunciation guidance for patient-facing materials. In IT/software terminology, brand and product names imported from English routinely require Nuqta-bearing consonants (ज़, फ़, ख़); inconsistent application across UI strings, help, and marketing breaks search and findability.

Numbers, symbols, and non-breaking spaces¶

Numbers¶

Devanagari numerals are used to represent numbers in Kashmiri. These are distinct from Arabic numerals (0–9):

• 0 — ०
• 1 — १
• 2 — २
• 3 — ३
• 4 — ४
• 5 — ५
• 6 — ६
• 7 — ७
• 8 — ८
• 9 — ९

Example: 23 December → २३ दिसंबर

Non-breaking space¶

Non-breaking spaces can be used in Kashmiri (Devanagari), especially in dates, numeric values, or terms that should appear together without breaking.

Example: March 2024 → माच २०२४

  stands for non-breaking space. It keeps the words on the same line.

Ampersand¶

Always translate “&” as “त” when it refers to running text. Do not keep “&” in the target unless it is part of a tag, placeholder, shortcut, or other code.

Why this matters: Numeric notation is sphere-critical. Medical dosing instructions must use Devanagari numerals consistently or risk dispensing errors when readers misread mixed-script numbers. Legal contracts depend on unambiguous quantities — mixing २३ and 23 in the same document creates dispute fodder. IT/software version numbers, error codes, and timestamps must follow consistent script for searchability. Marketing price displays in Devanagari numerals signal localization quality.

Date¶

Date format in Kashmiri (Devanagari) follows the day-month-year (DD-MM-YYYY) sequence, similar to many other Indian languages.

Example: २३ दिसम्बर २०२५ (23 December 2025)

When only the month and year are included (such as “March 2025”), use the Month YYYY format.

Why this matters: Date formatting failures break trust across spheres. Legal contracts reference dates as binding facts — DD-MM-YYYY versus MM-DD-YYYY confusion has caused real contract disputes (07-04-2024: is that April 7 or July 4?). Medical prescriptions and patient records depend on date precision for treatment continuity. IT/software timestamps and logs depend on date consistency for debugging. Marketing campaign dates that follow English MM-DD-YYYY in a Kashmiri context look unlocalized.

Inclusive language¶

Microsoft technology reaches every part of the globe, so all communications should be inclusive and diverse.

General guidelines¶

• Comply with local language laws.
• Use plain language.
• Be mindful when referring to various parts of the world.
• In text and images, represent diverse perspectives and circumstances.
• Don’t generalize or stereotype people by region, culture, age, or gender — not even if the stereotype is positive.
• Don’t use profane or derogatory terms.
• Don’t use slang that could be considered cultural appropriation.
• Don’t use terms that may carry unconscious racial bias or terms associated with military actions, politics, or controversial historical events and eras.

Avoid gender bias¶

Use gender-neutral alternatives for common terms. Avoid compounds containing gender-specific terms (पुरुष, जननी, etc.).

Accessibility¶

Microsoft devices and services empower everyone, including people with disabilities. Focus on people, not disabilities. Don’t use words that imply pity, such as पेठ मबतला. Don’t mention a disability unless it’s relevant.

Use generic verbs that apply to all input methods and devices. In procedures and instructions, avoid verbs that don’t make sense with alternative input methods used for accessibility.

Keep paragraphs short and sentence structure simple — aim for one verb per sentence. Read text aloud and imagine it spoken by a screen reader.

Spell out words like एंड, प्लस, and एबाउट. Screen readers can misread text that uses special characters like the ampersand (&), plus sign (+), and tilde (~).

Why this matters: Inclusive language is not optional across spheres. Legal drafting that defaults to masculine forms exposes organizations to discrimination claims; gender-neutral defaults (उस्ताद, डॉक्टर) are safer. Medical patient materials must address everyone — gendered assumptions about role (the assumption a nurse is जननी, a doctor is पुरुष) reduce trust and compliance. IT/software with “Click” verbs excludes touch, voice, and assistive-input users — Select-style verbs work for all. Marketing brands with exclusionary language lose market segments measurable in revenue.

Application, products, and features¶

Application or product names that are trademarked are not translatable. Before translating any application, product, or feature name, verify it is in fact translatable and not protected.

Version numbers¶

Version numbers always contain a period.

Why this matters: Product-name discipline matters across spheres. Legal documents must reference trademarked names exactly — translating “Microsoft” or “Windows” creates trademark exposure. Medical software (electronic health records, imaging systems) carries trademark protection — translating product names breaks regulatory documentation. IT/software support flows depend on exact product-name matches between UI, help, and tickets. Marketing copy that translates brand names dilutes brand equity.

Trademarks¶

Trademarked names and the name Microsoft Corporation should not be localized unless local laws require translation and an approved translated form of the trademark is available. A list of Microsoft trademarks is available at: https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks

Why this matters: Trademark handling is legally consequential across spheres. Legal drafting that translates a trademark without authorization risks invalidating clauses or creating infringement exposure. Medical regulatory submissions reference branded drugs and devices by trademarked name — translation breaks the regulatory chain. IT/software documentation references third-party trademarks (Windows, Android, AWS) that must remain in original form. Marketing copy that “translates” the brand name destroys SEO and brand recognition.

Reference information¶

Terminology¶

Approved terminology related to the translation project — including product names — will be provided in the translation editing environment. It is also available at the Microsoft Terminology Search page, but translators should be aware that the website terminology is not as current as the editing-environment terminology. The site does provide terminology across all Microsoft products.

Use approved terminology, especially for key terms, technical terms, and product names.

Normative references¶

Adhere to these normative references. When more than one solution is possible, consult the other topics in this guide for guidance.

1. www.lexilogos.com
2. https://kashmirculturaltrust.in/op/ModernKashmiriGrammar.pdf
3. https://archive.org/details/dli.ernet.509601

Note: If more than one spelling is acceptable, opt always for the spelling adopted on Microsoft approved terminology and in the normative dictionaries mentioned above. Use a consistent spelling across all products and documents.

FAQ¶

What register should Kashmiri (Devanagari) translation use across professional contexts?¶

Warm and relaxed, crisp and clear, ready to help — across software UI, marketing, medical patient materials, and consumer-facing legal documents. Microsoft privacy content uses the formal tone with the तोहह form of address; other consumer-facing content prefers conversational phrasing. Pure technical specs and sworn legal translation retain more formality, but even there, clarity beats bureaucratic register.

How should I handle abbreviations and acronyms in Kashmiri Devanagari?¶

Abbreviations take a period (श्री. for श्रीमान); plural markers can be added while keeping the period (नं. for नंबरस). Acronyms do not take periods (PDF → पीडीएफ़्स). On first occurrence, write the full form followed by the acronym in parentheses; thereafter use the acronym alone. Well-known English acronyms like CD or IIT stay in Latin script.

How does Devanagari punctuation differ from Latin punctuation in Kashmiri?¶

The full stop is the danda (।) not a Latin period. No space precedes commas or periods. Bulleted lists with complete sentences end in danda or other end punctuation; phrase-style items take no end punctuation. A colon (:) introduces a list. Em dash use should be minimized — replace with commas, parentheses, or a sentence break.

When is Nuqta required in Kashmiri Devanagari?¶

Nuqta is a diacritic dot under or beside a Devanagari letter (क → क़) marking sounds borrowed from Urdu, Arabic, Farsi, or English that the base Devanagari consonant cannot represent. Apply it for non-native sounds (क़ुरान, ज़, फ़, ख़). Native Kashmiri sounds already covered by standard consonants take no Nuqta. Persian-origin words like ख़ुशबू sometimes appear as खुशबू in casual or older texts.

How should I write numbers and dates in Kashmiri Devanagari?¶

Use Devanagari numerals (० १ २ ३ ४ ५ ६ ७ ८ ९) not Arabic digits — 23 December becomes २३ दिसंबर. Date format follows DD-MM-YYYY (२३ दिसम्बर २०२५) — when only month and year, use Month YYYY (माच २०२४). Use non-breaking spaces ( ) to keep date components together on one line.

What inclusive-language rules apply to Kashmiri Devanagari translation?¶

Avoid gendered compounds (पुरुष उस्ताद, जननी उस्ताद) — use the neutral form (उस्ताद, डॉक्टर) that covers both genders. For accessibility, focus on people not disabilities; never use pity-implying terms. Use generic verbs that work across input methods (चुनिव not क्लिक करीव). Spell out symbols like एंड, प्लस, एबाउट so screen readers don’t misread &, +, ~.

Sources¶

• Microsoft Localization Style Guide for Kashmiri (Devanagari) (PDF)
• Microsoft Globalization Style Guides hub
• Microsoft Terminology Search
• Modern Kashmiri Grammar (Kashmir Cultural Trust)
• Lexilogos — Kashmiri resources