From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Status of multicolor fonts? Date: Sat, 27 Apr 2019 11:45:50 +0300 Message-ID: <837ebfx2dd.fsf@gnu.org> References: <567169C8.9010006@gmail.com> <83d1u61o31.fsf@gnu.org> <5671E3C4.3030403@gmail.com> <83v9z33o9m.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="98934"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org To: mituharu@math.s.chiba-u.ac.jp Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Apr 27 10:46:16 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hKIyO-000PdO-2v for ged-emacs-devel@m.gmane.org; Sat, 27 Apr 2019 10:46:16 +0200 Original-Received: from localhost ([127.0.0.1]:57389 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hKIyN-0006qg-4d for ged-emacs-devel@m.gmane.org; Sat, 27 Apr 2019 04:46:15 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:47121) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hKIyF-0006q6-7q for emacs-devel@gnu.org; Sat, 27 Apr 2019 04:46:08 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:43104) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hKIyE-0006Gh-3g; Sat, 27 Apr 2019 04:46:06 -0400 Original-Received: from [176.228.60.248] (port=2020 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hKIyD-0000hn-HS; Sat, 27 Apr 2019 04:46:05 -0400 In-reply-to: (mituharu@math.s.chiba-u.ac.jp) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:235982 Archived-At: > Date: Sat, 27 Apr 2019 17:13:24 +0900 > From: mituharu@math.s.chiba-u.ac.jp > Cc: emacs-devel@gnu.org > > >> Does it count as multicolor font support on free platforms? > > > > I think it does, yes. Thanks for working on this. > > I've added some NEWS entries, and re-enabled multicolor fonts > for the mac-ct font backend driver. Thanks. > > As long as I have your attention: could you please help in finishing > > the development of the harfbuzz branch and landing it on master? For > > Posix platforms, there are just a few finishing touches left, I think, > > the main one being make a separate font backend that uses HarfBuzz > > interfaces for as many backend facilities as possible (I will tell the > > details if you can offer help). I'd appreciate help in this area. > > TIA. > > I don't know if I'll be of any help, but could you explain the details? I think I can, but please ask more specific questions. The general idea is to use HarfBuzz as a font backend which supports layout of complex scripts, as a replacement for libm17n-flt on GNU/Linux and as a replacement for Uniscribe on MS-Windows. The current code on the branch uses compile-time CPP directives to select HarfBuzz as the shaper for xftfont and other font back-ends, but I would like to make it a separate font backend instead, so that people could choose which one to use. I also think not every existing font backend needs to be able to use HarfBuzz, only those which support OTF and TTF font features should. > Is it OK to merge master to the harfbuzz branch as the first step > so as to resolve some conflicts caused by my recent commits? Yes, please. In fact, seeing your Cairo changes was what prompted me to ask you for help in the first place. The HarfBuzz people wrote the initial code of the branch, but they said some time ago they didn't have enough time to work on this, although they will answer questions regarding HarfBuzz functionality (there's a mailing list dedicate to HarfBuzz development and use). TIA