Inaccurate definitions of pre-defined Ligatures

#1

The following Compound Arabic Ligatures have wrong definitions:

“lam_noon_meem-ar”,
“lam_alefMaksura_meem-ar”,
“alefMaksura_reh-ar.fina”,
“alefMaksura_zain-ar.fina”,
“alefMaksura_meem-ar”,
“alefMaksura_meem-ar.fina”,
“alefMaksura_meem-ar.medi”,
“alefMaksura_meem-ar.init”,
“alefMaksura_noon-ar.fina”,
“alefMaksura_heh-ar.medi”,
“alefMaksura_heh-ar.init”,

and the following cases do not exist in Arabic language:
“yehHamzaabove_yehHamzaabove-ar”,
“yehHamzaabove_yehHamzaabove-ar.fina”,

#2

You mean their decomposition? What do you suggest instead?

#3
  1. as Known AlefMaksura is a unique case of Alef that is always either .fina or isolate.
  2. There are no such cases which .fina forms can connect to AlefMaksura as the above mentioned list
  3. the naming should be from right to left (ie. right composite name first)
  4. The internal order of components should also be fixed.
  5. it looks that most of the ligatures refer to this Unicode list and they merely were mixed or mis-ordered;
    so I suggest to get back and pick the essential ligatures from the following;
    “alefMaksura-ar.medi”,
    “alefMaksura-ar.init”,
    “alefMaksura-ar”,
    “alefMaksura-ar.isol”,
    “alefMaksura-ar.fina”,
    “alefMaksuraAlefabove-ar”,
    “alefMaksuraAlefabove-ar.fina”,
    “beh_alefMaksura-ar”,
    “beh_alefMaksura-ar.fina”,
    “teh_jeem_alefMaksura-ar.fina”,
    “teh_khah_alefMaksura-ar.fina”,
    “teh_meem_alefMaksura-ar.fina”,
    “teh_alefMaksura-ar”,
    “teh_alefMaksura-ar.fina”,
    “theh_alefMaksura-ar”,
    “theh_alefMaksura-ar.fina”,
    “jeem_hah_alefMaksura-ar.fina”,
    “jeem_meem_alefMaksura-ar.fina”,
    “jeem_alefMaksura-ar”,
    “jeem_alefMaksura-ar.fina”,
    “hah_meem_alefMaksura-ar.fina”,
    “hah_alefMaksura-ar”,
    “hah_alefMaksura-ar.fina”,
    “khah_alefMaksura-ar”,
    “khah_alefMaksura-ar.fina”,
    “seen_jeem_alefMaksura-ar.fina”,
    “seen_khah_alefMaksura-ar.fina”,
    “seen_alefMaksura-ar”,
    “seen_alefMaksura-ar.fina”,
    “sheen_alefMaksura-ar”,
    “sheen_alefMaksura-ar.fina”,
    “sad_alefMaksura-ar”,
    “sad_alefMaksura-ar.fina”,
    “dad_hah_alefMaksura-ar.fina”,
    “dad_alefMaksura-ar”,
    “dad_alefMaksura-ar.fina”,
    “tah_alefMaksura-ar”,
    “tah_alefMaksura-ar.fina”,
    “ain_meem_alefMaksura-ar.fina”,
    “ain_alefMaksura-ar”,
    “ain_alefMaksura-ar.fina”,
    “ghain_meem_alefMaksura-ar.fina”,
    “ghain_alefMaksura-ar”,
    “ghain_alefMaksura-ar.fina”,
    “feh_alefMaksura-ar”,
    “feh_alefMaksura-ar.fina”,
    “qaf_alefMaksura-ar”,
    “qaf_alefMaksura-ar.fina”,
    “kaf_alefMaksura-ar”,
    “kaf_alefMaksura-ar.fina”,
    “lam_hah_alefMaksura-ar.fina”,
    “lam_alefMaksura-ar”,
    “lam_alefMaksura-ar.fina”,
    “meem_alefMaksura-ar”,
    “noon_jeem_alefMaksura-ar.fina”,
    “noon_hah_alefMaksura-ar.fina”,
    “noon_meem_alefMaksura-ar.fina”,
    “noon_alefMaksura-ar”,
    “noon_alefMaksura-ar.fina”,
    “heh_alefMaksura-ar”,
    “yeh_alefMaksura-ar”,
    “yeh_alefMaksura-ar.fina”,
    “yehHamzaabove_alefMaksura-ar”,
    “yehHamzaabove_alefMaksura-ar.fina”,
#4

You mean the sidebar entries in Font view > Languages > Arabic > Ligatures? We will have a look.

OpenType ligatures do not necessarily imply connection. It just means that these letters are inside one glyph. So alefMaksura_reh-ar.fina would be a final alefMaksura and an isolated reh, perhaps better positioned.

Ah, possible. We will have a look.

#5

It is likely a kerning issue; let’s give priorities to the commonly used ligatures;
:wink: