Bug 241717 – Lack of font support for Kashmiri characters makes text deviate from true semantics

• Component: Text
• Status: NEW

[r12a]

Created attachment 460299 [details]
Example glyph forms for Kashmiri.

This issue is applicable to Kashmiri written with the Perso-arabic script.

Kashmiri is written using the nastaliq style of Arabic writing. However, there are almost no fonts that properly support Kashmiri written in that orthography. (Noto Nastaliq Urdu was only updated in Feb 2022 to support Kashmiri.)

The result of this is that people resort to using inappropriate characters in their text so that the content looks visually more like they are expecting, and even then gaps remain. For example, to make the sukun look like an inverted v rather than a circle, users often use U+065B ARABIC VOWEL SIGN INVERTED SMALL V ABOVE, which is supposed to be used as an African vowel diacritic. There are several such problems in Kashmiri. Lists can be found here and here

Keyboards and input methods also need to be configured to insert the correct characters, but this doesn't help while there are so few fonts available that can display the characters.

This issue is not likely to be fixed by specifications or browser fixes, but does cause a significant constraint for Kashmiris wishing to use the Web.

There is an additional issue, however, related to pre-installed fonts on macOS (see below).

Tests & results:
interactive test, A given font will correctly render characters needed for Kashmiri in the perso-arabic script.
https://w3c.github.io/i18n-tests/exploratory/vanilla?text=%D8%A7%D9%9F%09%DB%8C%D9%9A%DB%8C%D9%9A%DB%8C%D9%9A%09%D9%88%D9%9A%09%D8%AD%D9%94%09%D8%B1%D9%94%09%D8%A8%D9%94%D8%A8%D9%94%D8%A8%D9%94%09%DB%8C%DB%8C%DB%8C%09%DA%A9%DA%A9%DA%A9%09%D8%A0%D8%A0%D8%A0%20%D8%A0%09%D9%BE%D9%92%09%DB%84&lang=ks&fontSize=49&fontFamily=Noto%20Nastaliq%20Urdu&width=845&height=292&a=A%20given%20font%20will%20correctly%20render%20characters%20needed%20for%20Kashmiri%20in%20the%20perso-arabic%20script.&i=Test%20passes%20if%20the%20shapes%20of%20the%20characters%20match%20those%20at%20https%3A%2F%2Fgithub.com%2Fw3c%2Falreq%2Fissues%2F249.%20%20In%20particular%3A%20farsi%20yeh%20with%20small%20v%20above%20should%20join%20to%20the%20left%3B%20the%204%20forms%20of%20kashmiri%20yeh%20should%20appear%3B%20hamzas%20should%20use%20the%20round%20form%3B%20the%20sukun%20over%20PA%20should%20be%20an%20inverted%20v.%20Use%20the%20control%20below%20to%20test%20various%20fonts.


The glyph shapes when the text in the test are displayed should resemble those in the image just below. In particular: farsi yeh with small v above should join to the left; the 4 forms of kashmiri yeh should appear; hamzas should use the round form; the sukun over PA should be an inverted v.

See the attached image.

As of March 2022, the latest version of Noto Nastaliq Urdu supports the needed glyphs, if the language is set to 'ks', and displays correctly on Windows10. However, on macOS 12.2.1 the pre-installed version of the font cannot be overwritten and is used to display Kashmiri text in browsers, meaning that there is no support on macOS at the time of writing.

SIL's Awami Nastaliq font succeeds in correctly rendering all but one feature: the hamza is s-shaped, as used for Urdu, rather than rounded. However, this is a Graphite font, and so only works currently on Gecko browsers.

The Gulmarg Nastaleeq font supports some features in Windows, but appears to not have glyphs for KASHMIRI YEH or for LETTER WAW WITH RING. It also doesn't work on macOS, presumbly for the same reason as the Noto font.

[r12a]

This bug report is being tracked by the W3C at https://www.w3.org/TR/2022/DNOTE-arab-ks-gap-20220617/#issue249_fonts

[Alexey Proskuryakov]

Is the request here to ship a different font with macOS? If so, that's outside the scope of WebKit open source project.

[r12a]

I'm not suggesting any particular solution, just asking that it be possible for Kashmiri users (and others) to write and read their language on the Web.  Safari/Webkit browsers don't appear to allow that at the moment (unlike Blink & Gecko browsers). I'm hoping that you can help unblock that situation.

[Radar WebKit Bug Importer]

<rdar://problem/95855676>