Source: https://r12a.github.io/scripts/arab/ks.html
In your notes, you mentioned that using U+0652 (SUKUN) is semantically correct and should be used instead of U+065B (ARABIC VOWEL SIGN INVERTED SMALL V ABOVE), even though the latter appears visually more accurate by default on almost all fonts.
However, in practice, most people prefer using U+065B. The reason is simple: convenience and out-of-the-box rendering take priority over semantic correctness. Only a few specific fonts properly render U+0652 as expected, and even then, only when the language attribute is explicitly set to Kashmiri (ks). On the average user's device with default Arabic fonts, U+065B reliably displays the glyph people expect to see.
Insisting on U+0652 creates technical friction, as it forces users to set or change the language tag to ks across every platform, app, or word editor they use. Furthermore, many people avoid using Noto Nastaliq Urdu altogether and opt for other Unicode Naskh fonts because Noto Nastaliq by default renders the Arabic Hamza (both above and below) as an unfamiliar glyph that Kashmiri users do not expect.
Due to this language-tag dependencies, it seems there is a real need for a 'Nastaliq Kashmiri' font, as expecting the general public to change complex language settings on every platform is simply unrealistic.
For instance Kashmiri Wikipedia uses U+065B
Source: https://r12a.github.io/scripts/arab/ks.html
In your notes, you mentioned that using U+0652 (SUKUN) is semantically correct and should be used instead of U+065B (ARABIC VOWEL SIGN INVERTED SMALL V ABOVE), even though the latter appears visually more accurate by default on almost all fonts.
However, in practice, most people prefer using U+065B. The reason is simple: convenience and out-of-the-box rendering take priority over semantic correctness. Only a few specific fonts properly render U+0652 as expected, and even then, only when the language attribute is explicitly set to Kashmiri (ks). On the average user's device with default Arabic fonts, U+065B reliably displays the glyph people expect to see.
Insisting on U+0652 creates technical friction, as it forces users to set or change the language tag to ks across every platform, app, or word editor they use. Furthermore, many people avoid using Noto Nastaliq Urdu altogether and opt for other Unicode Naskh fonts because Noto Nastaliq by default renders the Arabic Hamza (both above and below) as an unfamiliar glyph that Kashmiri users do not expect.
Due to this language-tag dependencies, it seems there is a real need for a 'Nastaliq Kashmiri' font, as expecting the general public to change complex language settings on every platform is simply unrealistic.
For instance Kashmiri Wikipedia uses U+065B