Glyph position for "wavyhamzabelow-ar" in GlyphData.xml

Glyphs
1

In the main GlyphData.xml I think the location (sortName) field for “wavyhamzabelow-ar” should be ar2882; it’s currently 2880 which is already used by “gafsarkashcenter-ar” two letters up, and it’s sandwiched between 2881 and 2883.

	<glyph name="gafsarkashcenter-ar" sortName="ar2880" category="Mark" subCategory="Nonspacing" script="arabic" direction="RTL" description="ARABIC GAFSARKASH CENTER" anchors="_center" />
	<glyph name="doublestroke-ar" sortName="ar2881" category="Mark" subCategory="Nonspacing" script="arabic" direction="RTL" description="ARABIC DOUBLE STROKE" anchors="_center" />
	<glyph unicode="065F" name="wavyhamzabelow-ar" sortName="ar2880" category="Mark" subCategory="Nonspacing" script="arabic" production="uni065F" direction="RTL" description="ARABIC WAVY HAMZA BELOW" anchors="_bottom, bottom" />
	<glyph name="ring-ar" sortName="ar2883" category="Mark" subCategory="Nonspacing" script="arabic" direction="RTL" description="ARABIC RING" />
2

And LamAlef with wasla final form also maybe needs to be changed from “ar0100_ar1152.3” to “ar0010_ar1152.3”.

	<glyph name="lam_alefWasla-ar" sortName="ar0010_ar1152.2" decompose="lam_alef-ar, wasla-ar" category="Letter" subCategory="Ligature" script="arabic" production="uni06440671" direction="RTL" description="ARABIC LIGATURE LAM WITH ALEF WASLA ISOLATED FORM" anchors="top_1, top_2, bottom_1, bottom_2" />
	<glyph name="lam_alefWasla-ar.fina" sortName="ar0100_ar1152.3" decompose="lam_alef-ar.fina, wasla-ar" category="Letter" subCategory="Ligature" script="arabic" production="uni06440671.fina" direction="RTL" description="ARABIC LIGATURE LAM WITH ALEF WASLA FINAL FORM" anchors="top_1, top_2, bottom_1, bottom_2" />
3

I fixed the double sort name. I’m not sure about the sort names of “lam_alefWasla-ar”. Fixing them would change the sorting of the ligatures and cause unneeded changed to peoples files.

4

Thanks! And that makes sense about the LamalefWasla, I can just change it my own xml :slight_smile:

5

What different sorting would you like to see?

6

Ideally the final form would be just after its isolated form like the rest of the other lamalefs. Right now it jumps somewhat arbitrarily which is mainly noticeable if there are other ligatures that happen to fall in between that 0010 and 0100 location (otherwise it’s mostly with the rest).

Here’s what happens currently if, say, you add some tooth+yehbarri ligatures:

1892×676 103 KB

For what it’s worth, I’ve sorted the same data above in my GlyphsData.xml file like this, but moving just the lam_alefWasla-ar.fina ligature next to its isolated buddy would be nice for most people I’d think:

1904×692 89.1 KB

7

You are right. That order should be fixed. I’ll have a look.

8

There are many more cases like this. I changed it for the next big update (where changes like this can be expected).

9

Awesome, thanks! Would that only be in 3.5+, or available in cutting edge versions?

10

Not sure in what version I’ll put this.

11

Will just keep an eye out, thanks again! :+1: