Kashmiri (Devanagari, India) style guide¶
Apply these local conventions alongside the house voice and localization review. Source acknowledgments are in credits.
Script and address¶
This page covers Kashmiri written in Devanagari. Use the separate Kashmiri page for the Arabic-script edition; do not transfer its text direction or numeral choices automatically. Use respectful address, including तोहि in the formal register, and natural Kashmiri sentence structure.
Devanagari has no uppercase/lowercase distinction. Preserve Latin case in FontLab, ID and literal identifiers. Use approved Kashmiri terms and ask a proficient reviewer to resolve disputed forms; a rule for another Devanagari language is not sufficient evidence.
Letters and marks¶
Preserve language-specific letters and vowel signs. The independent vowels ॳ, ॴ, ॵ, ॶ and ॷ have their own encoded characters. Do not replace them with a visually assembled अ plus a vowel sign. Test both display and copied text.
Nukta is the combining mark ़ (U+093C), as in क़. It is not a period placed beside the consonant. Preserve the accepted spelling of a word; do not add or strip marks merely to make it resemble another language's spelling. Font support and normalization must retain the intended characters. See scripts and typography.
Abbreviations and sentences¶
Distinguish a shortened word from an initialism. The abbreviation श्री. includes a period; CD, IIT and PDF do not acquire internal periods under the same rule. Give an unfamiliar term's full form before its acronym, then use the agreed short form consistently.
Plural and gender agreement depend on what the abbreviation names in context. Do not assign masculine gender to every device or append an English s mechanically. An English plural PDFs does not prescribe how to build a Kashmiri phrase. Retain protected format names and let the surrounding wording express the required number.
Use । for declarative sentences in this guide's Devanagari prose. Full-sentence bullets take appropriate sentence punctuation; phrases need none. Keep punctuation in literal UI labels, quoted commands and code unchanged. Quotation marks delimit quoted text; use the guide's UI formatting to identify controls, rather than quotation marks for emphasis.
Numerals, dates and literal values¶
Use Devanagari digits for ordinary numbers in this edition when the surface supports that convention. Keep the digit set consistent within a value:
| Latin digits | Devanagari digits |
|---|---|
| 0 1 2 3 4 | ० १ २ ३ ४ |
| 5 6 7 8 9 | ५ ६ ७ ८ ९ |
For ordinary numeric dates, use day–month–year order, as in २३-१२-२०२५. A month-and-year source must remain month and year, without an invented day. Verify the selected numbering system in the actual formatter; choosing a language tag alone does not prove the intended display.
Do not localize the characters inside a literal identifier. A version supplied as 4.2 stays 4.2; it does not become ४.२. The same boundary applies to filenames, placeholders and values that the user must type exactly. Use nonbreaking spaces to keep a number with its unit where appropriate, without inserting spaces into literal strings.
Use the conjunction त in running prose. Preserve & in protected names, markup, shortcuts and code. For mathematical negatives and units, follow technical notation; an en dash is not a minus sign and °C must retain its scale.
Interface review¶
Use accessible content and interface actions. When a task says to select one file, a shorter translation must still specify one file. Do not turn it into an instruction to select files generally. Test real substituted values, agreement and line wrapping with a proficient Kashmiri reviewer. Avoid mechanically translating English disability labels or importing an unrelated language's supposedly neutral terms.