unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: 43058@debbugs.gnu.org, lists.gnu.org@mavit.org.uk
Subject: bug#43058: 27.1; Support for other colour font formats
Date: Thu, 22 Sep 2022 10:10:53 +0300	[thread overview]
Message-ID: <831qs3ubnm.fsf@gnu.org> (raw)
In-Reply-To: <wl7d1wgma9.wl-mituharu@math.s.chiba-u.ac.jp> (message from YAMAMOTO Mitsuharu on Thu, 22 Sep 2022 11:45:02 +0900)

> Date: Thu, 22 Sep 2022 11:45:02 +0900
> From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> Cc: Eli Zaretskii <eliz@gnu.org>,
> 	43058@debbugs.gnu.org
> 
> This font is rejected by the ftcr(hb) font backend because its average
> width is computed as 0.  The average width is approximated by that of
> all ASCII chars, and the width of glyph ID 0 is used for missing ones.
> OpenMoji Color does not have several ASCII chars, and the width of
> glyph ID 0 is 0.  That's why the average width becomes 0 there.
> 
> The patch below avoids this by taking the average of non-zero width of
> the ASCII chars.  But glyphs are not displayed because SVG-in-OpenType
> support in cairo is still in progress:
> https://gitlab.freedesktop.org/cairo/cairo/-/merge_requests/319

Does this mean the patch, if installed, will not reject the font, but
will also not display its glyphs?  If so, doesn't it mean we should
install this patch conditioned on some (future) Cairo version, where
these glyphs will be displayed?  As long as Cairo doesn't support
that, I think rejecting these fonts is the best we can do, right?

Thanks.





  reply	other threads:[~2022-09-22  7:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 12:24 bug#43058: 27.1; Support for other colour font formats Peter Oliver
2020-08-26 12:33 ` Eli Zaretskii
2020-08-26 15:12   ` Peter Oliver
2022-09-22  2:45     ` YAMAMOTO Mitsuharu
2022-09-22  7:10       ` Eli Zaretskii [this message]
2022-09-25  6:40         ` YAMAMOTO Mitsuharu
2022-09-25  8:03           ` Eli Zaretskii
2022-09-26  1:05             ` YAMAMOTO Mitsuharu
2022-09-25 22:47       ` Peter Oliver

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=831qs3ubnm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=43058@debbugs.gnu.org \
    --cc=lists.gnu.org@mavit.org.uk \
    --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).