From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 39340@debbugs.gnu.org, ynyaaa@gmail.com
Subject: bug#39340: 26.3; "Noto Emoji" font not displayed
Date: Mon, 03 Feb 2020 20:22:59 +0200 [thread overview]
Message-ID: <83sgjrh6nw.fsf@gnu.org> (raw)
In-Reply-To: <m2k153lfa7.fsf@gmail.com> (message from Robert Pluim on Mon, 03 Feb 2020 19:03:12 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: 39340@debbugs.gnu.org, ynyaaa@gmail.com
> Date: Mon, 03 Feb 2020 19:03:12 +0100
>
> font-log with the attached patch applied is below. Basically
> fontp->driver->has_char and fontp->driver->encode_char are both
> failing for Ebrima when uniscribe is used. When harfbuzz is used, only
> has_char fails, but encode_char succeeds (see second attachment)
has_char always fails in w32 font backends, so that's expected.
encode_char is the problem. Can you tell where in
uniscribe_encode_char do we fail? does ScriptItemize fail or is it
ScriptShape?
This could be a symptom of Microsoft deprecating Uniscribe.
Thanks.
next prev parent reply other threads:[~2020-02-03 18:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 4:12 bug#39340: 26.3; "Noto Emoji" font not displayed ynyaaa
2020-01-29 18:22 ` Eli Zaretskii
2020-01-30 5:13 ` ynyaaa
2020-01-30 14:38 ` Eli Zaretskii
2020-01-31 2:20 ` ynyaaa
2020-01-31 8:46 ` Eli Zaretskii
2020-01-31 10:43 ` Eli Zaretskii
2020-02-01 3:54 ` ynyaaa
2020-02-01 9:14 ` Eli Zaretskii
2020-02-01 11:52 ` YAGI Tatsuya
2020-02-01 12:46 ` Eli Zaretskii
2020-02-03 16:27 ` Robert Pluim
2020-02-03 16:58 ` Eli Zaretskii
2020-02-03 18:03 ` Robert Pluim
2020-02-03 18:22 ` Eli Zaretskii [this message]
2020-02-03 19:45 ` Robert Pluim
2020-02-03 19:57 ` Eli Zaretskii
2020-09-20 10:08 ` Lars Ingebrigtsen
2020-09-20 10:49 ` Eli Zaretskii
2020-09-20 10:55 ` Lars Ingebrigtsen
2020-09-20 11:09 ` Eli Zaretskii
2020-02-01 11:34 ` Eli Zaretskii
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=83sgjrh6nw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39340@debbugs.gnu.org \
--cc=rpluim@gmail.com \
--cc=ynyaaa@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.