Re: Ligatures (was: Unify the Platforms: Cairo+FreeType+Harfbuzz Everywhere (except TTY))

[Clément Pit-Claudel]

On 20/05/2020 14.49, Eli Zaretskii wrote:
>> Cc: address@hidden, address@hidden, address@hidden
>> From: Clément Pit-Claudel <address@hidden>
>> Date: Wed, 20 May 2020 14:33:24 -0400
>>
>> On 20/05/2020 14.01, Eli Zaretskii wrote:
>>>> But regardless, what's the issue with ⇒?
>>>
>>> The issue with ⟹ is that the stem doesn't seem to be splittable into 2
>>> parts, whereas "==" are two characters.
>>
>> Oh, I see the worry, but I don't think it's a problem — it's a feature to 
>> split the stem into two parts :)
> 
> Then I guess we have very different views of what is a "feature".  To
> me, this looks like a terrible kludge.

Yet, that's what everyone else is doing, so at least it's a predictable (and 
convenient) kludge.

>> In a monospace font, it should look obvious what's happening, since ⟹ will 
>> occupy three columns.
> 
> Here it occupies only two.

Do you have a font with ligatures that composes ==> into ⟹, taking only two 
characters?

Most of the monospace fonts on my machine show ⇒ as one character and ⟹ as two 
— but the ones that have ligatures changing => into ⇒ and ==> into ⟹ all 
respect the widths of the characters they compose, so ⇒ is two characters wide 
and ⟹ is three characters wide.

I don't think the width of ⟹ as a non-composed character is too relevant, since 
we won't break it up, right?