Re: Joining Arabic Letters

From: Philippe Verdy <>
Date: Sat, 31 Mar 2012 18:35:46 +0200

I am testing it in the latest version of chrome, which was release
long after the latest Unicode addition to the Arabic letters (notably
the last update of Arabic joining types in the UCD). So may be it's
the internal engine used in Chrome that still does not support these
mandatory joining types.

But then, it would consider by default those characters as
**non-joining** (because this is explicitly the default value of the
joining type for all characters in the UCD that have not been assigned
joining types). This is not the case, the implementation considers
these characters as right-joining, so this is is clearly an
implementation bug.

Le 31 mars 2012 10:37, Khaled Hosny <> a écrit :
> On Sat, Mar 31, 2012 at 08:55:28AM +0200, Philippe Verdy wrote:
>> For now I've not seen any existing Arabic font that exhibit the
>> correct normative joining behavior for these letters such as  U+063D
>> (the Farsi Yeh with an inverted v above, which is dual-joining like
>> the Farsi Yeh at U+06CC without the inverted v above, and in the same
>> joining group; those fonts only map a single non-joining glyph for
>> U+063D, but behave correctly for U+06CC). This is true even for all
>> Arabic fonts shipped with Windows 7.
> Check my free Amiri font (, it has full Unicode 6.0
> Arabic coverage, with 6.1 additions under the way. But if you are using
> a layout engine that predates the addition of that character into
> Unicode, even a good font will not help here since the engine will be
> using the older Unicode character database where the joining behaviour
> of this letter is undefined.
> Regards,
>  Khaled
Received on Sat Mar 31 2012 - 11:43:22 CDT

This archive was generated by hypermail 2.2.0 : Sat Mar 31 2012 - 11:43:24 CDT