Wrong sequence for Arabic ligature marks(FC5E-FC62, FCF2-FCF4)

Richard Wordingham richard.wordingham at ntlworld.com
Sat Feb 19 07:05:44 CST 2022


On Sat, 19 Feb 2022 09:38:22 +0200
Eli Zaretskii via Unicode <unicode at corp.unicode.org> wrote:

> > Date: Fri, 18 Feb 2022 23:24:01 +0000
> > From: Richard Wordingham via Unicode <unicode at corp.unicode.org>

> > Irritatingly, I had to use some of these characters just this week
> > because the shaping in Arabic fonts for basic installations of
> > Windows 10 and Ubuntu didn't include the ligatures we were
> > discussing - in particular that of U+FCCA ARABIC LIGATURE LAM WITH
> > HAH INITIAL FORM. (The ligature was germane to the discussion.)
> > Many of the ligatures are not essential for proper shaping. I've
> > now found and lawfully installed a font that gives me the ligature
> > from normal Arabic letters.  
> 
> Which font is that, please?

Amiri.

> And does anyone here know why the Courier New font on Windows XP does
> produce the ligature from those two characters, but the same font on
> Windows 10 doesn't?  Is this ligature somehow deemed inappropriate or
> problematic?  I'm not asking about U+FCCA, I'm asking about the
> display of the two characters U+0644 and U+062D -- should it ligate or
> shouldn't it?

Well, as Courier New is generally seen as a plain 'typewriter' font,
such ligatures would seem out of place in a font of that name.  One can
find claims that the only compulsory ligature is lam-alif.

Richard.


More information about the Unicode mailing list