unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: mituharu@math.s.chiba-u.ac.jp
Cc: emacs-devel@gnu.org
Subject: Re: Status of multicolor fonts?
Date: Sat, 27 Apr 2019 11:45:50 +0300	[thread overview]
Message-ID: <837ebfx2dd.fsf@gnu.org> (raw)
In-Reply-To: <a1937598a6088e09eed7d819c04b8ea5.squirrel@weber.math.s.chiba-u.ac.jp> (mituharu@math.s.chiba-u.ac.jp)

> 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



  reply	other threads:[~2019-04-27  8:45 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16 13:40 Status of multicolor fonts? Clément Pit--Claudel
2015-12-16 14:10 ` Eli Zaretskii
2015-12-16 15:54   ` Clément Pit--Claudel
2015-12-16 22:20   ` Clément Pit--Claudel
2015-12-17  2:47     ` Yuri Khan
2015-12-17  3:14       ` Clément Pit--Claudel
2015-12-17 16:11         ` Eli Zaretskii
2015-12-19  9:43         ` Rüdiger Sonderfeld
2016-01-06  3:51     ` YAMAMOTO Mitsuharu
2016-01-06  6:23       ` John Wiegley
2016-04-11 22:34         ` YAMAMOTO Mitsuharu
2016-04-11 23:19           ` John Wiegley
2016-04-11 23:34             ` YAMAMOTO Mitsuharu
2019-04-24  3:45               ` YAMAMOTO Mitsuharu
2019-04-24  6:34                 ` Eli Zaretskii
2019-04-27  8:13                   ` mituharu
2019-04-27  8:45                     ` Eli Zaretskii [this message]
2019-05-03  9:59                       ` landing harfbuzz branch (Re: Status of multicolor fonts?) mituharu
2019-05-03 20:56                         ` Alan Third
2019-05-03 21:46                           ` mituharu
2019-05-04  8:54                         ` Eli Zaretskii
2019-05-04 23:42                           ` mituharu
2019-05-05 16:02                             ` Eli Zaretskii
2019-04-24 15:03                 ` Status of multicolor fonts? Stefan Monnier
2015-12-16 14:37 ` Yuri Khan
2015-12-16 15:32   ` Elias Mårtenson
2015-12-16 15:48     ` Eli Zaretskii
2015-12-16 16:03       ` Clément Pit--Claudel
2015-12-16 17:10         ` Eli Zaretskii
2015-12-16 18:22           ` Clément Pit--Claudel
2015-12-16 16:10       ` Elias Mårtenson
2015-12-16 16:41       ` Random832
2015-12-16 16:56         ` David Kastrup
2015-12-17  4:58           ` Richard Stallman
2015-12-17 17:25             ` John Wiegley
2015-12-16 17:17         ` Eli Zaretskii
2015-12-16 18:31           ` Clément Pit--Claudel
2015-12-16 18:54             ` Eli Zaretskii
2015-12-16 18:31           ` Random832
2015-12-16 16:00   ` Clément Pit--Claudel
2015-12-16 17:08     ` Eli Zaretskii
2015-12-22  0:59   ` David De La Harpe Golden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=837ebfx2dd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).