Dot positioning and collision issues

[saadatm]

Dot positioning and collision bugs that I observed in the Urdu translation of Gulzar's website (in Firefox 101.0.1 on a Windows 10 machine). I used the version of Gulzar that was generated in this GitHub Action run.

String	Screenshot	Comment
تقریباً		This word is also used in one of the promo images (which are gorgeous, by the way). However, in that image, there is no collision among the dots, so not sure what's happening. Perhaps, the font version which was used to create the image did not have the collision, but it later regressed?
کو بخوبی		Fixed (tested with the font built after https://github.com/googlefonts/Gulzar/commit/f09210d08fbff35b45ef499a306feba05feba711)
اب بھی		The dot for ب in بھی is usually well-behaved at other places, but in this particular sequence, it is too close to the ب in اب. Fixed (tested with the font built after https://github.com/googlefonts/Gulzar/commit/f09210d08fbff35b45ef499a306feba05feba711)
سمپکنز کمبینیشنز ایپلکیشنز سبز		Dot of ز is too far way and sometimes collides with subsequent words. (The first three words are transliterations, but سبز is Urdu for green and I actually used a synonym (ہرا/ہرے) in the translation to avoid having the dot of ز in سبز collide with the next word.) Generally, some sequences that end with نز or بز disturb the dots, like خنز طنز سبز. Same with sequences ending with نڑ, where the dot of ن and small ط of ڑ seem to be flying away. Also note the collision of ا and dots of ے in ایپلیکیشنز, and the cluster of dots when ایپلیکیشنز is followed by بھی.
زیرِ		The kasra is colliding with dots of ی.
نئی نئے		Dot of ن is too far up. It should be closer to its base, and the mark of hamza may be moved up instead.
پیوستہ		Not sure what's hppening here. It appears fine at one place, but at another place its dots are colliding. (Even when there is no collision, it will look better if the dots of ی are moved towards up-left.)
نتیجہ		This isn't bad, but will look better if the dot of ن could be brought closer to its base.

[simoncozens]

This word is also used in one of the promo images (which are gorgeous, by the way). However, in that image, there is no collision among the dots, so not sure what's happening. Perhaps, the font version which was used to create the image did not have the collision, but it later regressed?

I suspect this was caused by 79c98f6. I'll see if we can find a happy medium.

[saadatm]

I suspect this was caused by https://github.com/googlefonts/Gulzar/commit/79c98f610f4648ca52bd0f59ce2c752c487c1add. I'll see if we can find a happy medium.

This issue is also reproducible with the version of Gulzar currently being used for the website, so its cause is probably older than that commit.

[saadatm]

Not sure what's hppening here. It appears fine at one place, but at another place its dots are colliding. (Even when there is no collision, it will look better if the dots of ی are moved towards up-left.)

Found some more info: Dot collision happens if پیو is preceded by any of د ر و or ہ. Screenshot below:

[saadatm]

After the recent round of bug squashing by @simoncozens, I was curious to see if it also affected any of the problems reported in this issue. کو بخوبی and اب بھی are now fixed. 👍

[simoncozens]

Very nice!

[dboyk]

Very excited for your work! I’m encountering some dot positioning and collision issues when ز is preceded by ب, ن, or ہ. Here are some examples (some are real Urdu words, some not):

[dboyk]

Quick followup – ڑ seems to have the same issues: