GNU bug report logs -
#39799
28.0.50; Most emoji sequences don’t render correctly
Previous Next
Reported by: Mike FABIAN <mfabian <at> redhat.com>
Date: Wed, 26 Feb 2020 14:30:03 UTC
Severity: normal
Found in version 28.0.50
Fixed in version 28.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #125 received at 39799 <at> debbugs.gnu.org (full text, mbox):
>>>>> On Fri, 28 Feb 2020 22:55:10 +0200, Eli Zaretskii <eliz <at> gnu.org> said:
>> From: Robert Pluim <rpluim <at> gmail.com>
>> Cc: 39799 <at> debbugs.gnu.org, mfabian <at> redhat.com
>> Date: Fri, 28 Feb 2020 21:38:07 +0100
>>
>> (set-fontset-font "fontset-default" '(#x2460 . #x24FF)
>> '("Noto Color Emoji" . "iso10646-1") nil
>> 'prepend)
>>
>> gives me:
>>
>> Debugger entered--Lisp error: (error "Fontset ‘default-fontset’ does not exist")
>> set-fontset-font("default-fontset" (9312 . 9471) ("Noto Color Emoji" . "iso10646-1") nil prepend)
>> (progn (set-fontset-font "default-fontset" '(9312 . 9471) '("Noto Color Emoji" . "iso10646-1") nil 'prepend))
>> eval((progn (set-fontset-font "default-fontset" '(9312 . 9471) '("Noto Color Emoji" . "iso10646-1") nil 'prepend)) t)
Eli> You used "default-fontset" instead of "fontset-default", thus the
Eli> error.
D'oh. Friday night strikes again :-)
With that fixed, neither the range or specific char variant makes any
difference, I need to use nil.
One other thing: the #x24C2 is not composed with the following #xFE0F
when itʼs displayed using Google Noto Sans. If I get it to display
with Noto Color Emoji it *is* composed, even though I haven't set up
any composition-function-table entries for it. Where is that
composition coming from?
Robert
This bug report was last modified 3 years and 256 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.