[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emacs-27 7ec66a5: Document spacing issues with Xft for some fonts
From: |
Robert Pluim |
Subject: |
Re: emacs-27 7ec66a5: Document spacing issues with Xft for some fonts |
Date: |
Tue, 14 Jan 2020 17:27:19 +0100 |
>>>>> On Tue, 14 Jan 2020 18:00:26 +0200, Eli Zaretskii <address@hidden> said:
>> From: Robert Pluim <address@hidden>
>> Date: Tue, 14 Jan 2020 11:45:28 +0100
>>
>> Eli, is it too soon for this?
Eli> Hmm... soon? no, I don't think so. I just am not sure this is the
Eli> best approach. First, I don't think we have enough data and
Eli> experience to commit ourselves to remove Xft in Emacs 29, we should
Eli> first see how painful such a removal will be wrt our users.
Eli> Therefore, it might be better to turn Cairo ON by default on master,
Eli> and only use Xft if Cairo is unavailable. If that proves to be a
Eli> reliable configuration (i.e., we aren't flooded by complaints about
Eli> the Cairo problems), then perhaps we will be able to remove Xft in
Eli> Emacs 29 after all.
Turning on cairo by default I did earlier today in
88efc736f562656efab778d35c32d549ef6270d7 . That automatically ends up
not using Xft if Cairo is detected.
Eli> WDYT? If you agree, then instead of mentioning the removal in Emacs
Eli> 29, I'd prefer saying in NEWS that Xft is not actively maintained and
Eli> has known problems with some modern fonts, and therefore we recommend
Eli> against using it, as long as alternatives are available, Cairo being
Eli> the best one of those.
OK, I can go with that.
Robert