- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Feb 2023 17:56:10 +0000
- To: public-i18n-archive@w3.org
cc @kulpreetchilana Gurmukhi, like other indic scripts (and in fact Unicode text generally), deletes text in different ways for backwards and forwards spacing. Gurmukhi seems to be less problematic in approach than some other indic scripts. On Mac and Windows all browsers remove single code points during backwards deletion. During forward deletion, however, Firefox deletes one grapheme cluster at a time, whereas Chrome & Safari swallow up whole orthographic syllables with each bite. See https://r12a.github.io/scripts/guru/pa.html#webSegmentation The divergence between Gecko and Blink/WebKit engines for forward deletion may need to be looked at, but i don't think the difference between forward vs backward deletion is problematic. One code point at a time deletion (backwards delete) can be very useful for indic scripts when you want to delete just one component of a complex akshara without having to reconstruct the whole thing again. I'm not yet convinced about the confusion factor, given that (a) people writing Gurmukhi generally have to insert a virama to create the stacks, and (b) i think people will quickly get used to deleting the virama. -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/iip/issues/97#issuecomment-1419509848 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 February 2023 17:56:12 UTC