Nukta: Devanagari consonant distinctions
Quick copy
Details for U+0958
DEVANAGARI LETTER QA
Exact sequence: क़
U+0958
- Properties
Lo; CCC 0- HTML
क़- Word Alt+X
0958- Normalization
NFC: U+0915 U+093C; NFD: U+0915 U+093C; NFKC: U+0915 U+093C; NFKD: U+0915 U+093C
Details for U+093C
DEVANAGARI SIGN NUKTA
Exact sequence: ़
U+093C
- Properties
Mn; CCC 7- HTML
़- Word Alt+X
093C- Normalization
NFC: U+093C; NFD: U+093C; NFKC: U+093C; NFKD: U+093C
Click a character to copy it. Use Details for its technical record.
Devanagari nukta U+093C modifies a consonant, commonly appearing as a dot below it. It is a script-specific sign with its own combining class. [4], [6], [2]
Copy exact examples
Details for U+0915 U+093C
DEVANAGARI LETTER KA + DEVANAGARI SIGN NUKTA
Exact sequence: क़
U+0915 U+093C
Details for U+091C U+093C
DEVANAGARI LETTER JA + DEVANAGARI SIGN NUKTA
Exact sequence: ज़
U+091C U+093C
Uses and scope
Unicode describes nukta as extending the consonant inventory for additional sounds. Devanagari languages do not necessarily use all nukta letters equally. The table includes encoded consonants with canonical nukta decompositions and leaves the language-specific spelling decision to the relevant orthography. [6], [2]
Similar shapes, different characters
Some precomposed Devanagari nukta letters are composition exclusions. NFC therefore need not recreate the single character after decomposition. A Latin combining dot below U+0323 is not a substitute: its properties and shaping behavior differ. Preserve the exact selected spelling even when two canonically equivalent forms look identical. [1], [2], [6], [2]
Typing and text forms
Copying is exact; preview circles are excluded. Compare normalization forms.
- Word for Windows
- Select a hex code, then Alt+X; repeat for each scalar.
- Mac and mobile
- Hold a letter for supported variants; use Character Viewer on Mac or a language keyboard on mobile.
- HTML
- Use UTF-8 text or the numeric references in Details, in order.
Full typing instructions ·HTML, CSS and JavaScript entry ·Verified Alt codes.
Searchable character table
The records include listed signs and encoded letters whose canonical decomposition contains one of this page's combining signs. This Unicode relationship does not prove membership in the languages discussed above. [1], [2]
12 records
| Copy | Unicode identity and entry |
|---|---|
DEVANAGARI LETTER NNNADetails
| |
DEVANAGARI LETTER RRADetails
| |
DEVANAGARI LETTER LLLADetails
| |
DEVANAGARI LETTER KHHADetails
| |
DEVANAGARI LETTER GHHADetails
| |
DEVANAGARI LETTER ZADetails
| |
DEVANAGARI LETTER DDDHADetails
| |
DEVANAGARI LETTER RHADetails
| |
DEVANAGARI LETTER FADetails
| |
DEVANAGARI LETTER YYADetails
|
No matching records. Clear the search to restore the complete table.
Sources and method
Usage statements link to the authority that supports their scope. Character names, categories, combining classes and normalization results come from the pinned Unicode data. A canonical decomposition does not establish language membership or spelling frequency.
Source access date: 2026-09-14.
- [4] Unicode combining mark names and annotations. Names, cross references and narrowly attributed usage annotations. Historical annotations are not automatically current recommendations.
- [6] Unicode 17: Devanagari. Section 12.1: dependent vowel signs, candrabindu, anusvara, visarga, nukta and virama. Language-specific pronunciation is outside this source's scope.
- [2] Unicode normalization, UAX #15.
- [1] Unicode Character Database 17.0.0.
- [10] Microsoft: Unicode character entry in Word.
- [11] Apple: enter characters with accent marks.
- [12] Google: use Gboard.
- [13] Unicode: fonts and keyboards FAQ.
- [14] HTML numeric character references.
Read the editorial method and inspect the underlying datasets.
Related reading
Sources, versions and limits
- Encoded properties
- Properties use Unicode 17.0.0. Normalization follows UAX #15; grapheme boundaries follow UAX #29. Script associations describe encoded properties, not language use.
- Language evidence
- CLDR 48.2and the IANA registry dated 2026-08-08. Main and auxiliary exemplars are distinct. CLDR exemplars are not complete orthographies.
- Review and limitations
- The dataset is derived from the sources above. Editorial guides cite additional scoped authorities. No native or specialist orthography approval is implied. Release scope date: 14 September 2026. Historic or specialist usage needs separate evidence. Registry-only records have unknown orthography in this release.
- Reproduction and corrections
- Downloads and licences · Coverage and held routes · Suggest a source-backed correction