From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: When and how to register various font backends
Date: Wed, 19 Jun 2019 08:21:49 +0900 [thread overview]
Message-ID: <wlzhmecwdu.wl-mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <83muiest3p.fsf@gnu.org>
On Wed, 19 Jun 2019 02:26:02 +0900,
Eli Zaretskii wrote:
>
> > > Thanks. So I will ask Mitsuharu to please commit his changes, and the
> > > Windows rework will follow.
> >
> > Pushed to master. It includes some changes for Windows, so please
> > check if it works.
>
> Thanks. I needed to tweak that a bit, because on Windows we cannot
> determine whether HarfBuzz supersedes Uniscribe at dump time, we can
> only determine that at Emacs startup time.
Thanks.
> Do we need to fix something in the manuals or NEWS following this
> changeset?
I don't think so. The curent NEWS entry works as it is, and the
property 'font-backend-superseded-by is a bit internal and wouldn't
need documentations for users.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2019-06-18 23:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 19:40 When and how to register various font backends Eli Zaretskii
2019-06-14 9:14 ` Robert Pluim
2019-06-14 12:19 ` Eli Zaretskii
2019-06-14 13:16 ` Robert Pluim
2019-06-14 14:47 ` Eli Zaretskii
2019-06-15 9:50 ` Eli Zaretskii
2019-06-17 3:03 ` Michael Welsh Duggan
2019-06-17 9:41 ` Robert Pluim
2019-06-17 16:01 ` Eli Zaretskii
2019-06-18 1:29 ` YAMAMOTO Mitsuharu
2019-06-18 17:26 ` Eli Zaretskii
2019-06-18 23:21 ` YAMAMOTO Mitsuharu [this message]
2019-06-19 16:42 ` Eli Zaretskii
2019-06-14 16:54 ` Andy Moreton
2019-06-14 10:52 ` YAMAMOTO Mitsuharu
2019-06-14 11:52 ` Robert Pluim
2019-06-14 12:26 ` Eli Zaretskii
2019-06-14 13:24 ` Robert Pluim
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wlzhmecwdu.wl-mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.