[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered cor
From: |
YAMAMOTO Mitsuharu |
Subject: |
bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly |
Date: |
Mon, 25 Apr 2016 18:40:16 +0900 |
User-agent: |
Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (Shijō) APEL/10.6 Emacs/22.3 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI) |
>>>>> On Mon, 25 Apr 2016 11:59:18 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> Date: Mon, 25 Apr 2016 17:28:23 +0900
>> From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
>> Cc: ptr.wang@gmail.com,
>> 23362@debbugs.gnu.org
>>
>> > Could you perhaps write a short entry about the consequences of this
>> > in NEWS, and perhaps also in PROBLEMS? I guess we will be receiving
>> > such complaints in the future, so it would be nice to have a place
>> > to point people at.
>>
>> I've just added a NEWS entry that explains why it was included and
>> then disabled.
> Thanks. However, the OP seems to imply that the Emoji symbols are
> rendered incorrectly, or not displayed at all, when multicolor fonts
> are used, not just that the colors are not shown. If that is true (is
> it?), I'd suggest to have in NEWS a workaround (use a different
> font?), not just a statement of the fact that we don't support these
> fonts.
With the current 25.0.93, an attempt to display emoji (where only
Apple Color Emoji provides its glyph) results in the same appearance
(i.e., not displaying at all) regardless of the explicit font setting
given by the OP. Even the default setting in 24.5 looks the same.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Peter Wang, 2016/04/24
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Eli Zaretskii, 2016/04/24
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Peter Wang, 2016/04/24
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, YAMAMOTO Mitsuharu, 2016/04/24
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Eli Zaretskii, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, YAMAMOTO Mitsuharu, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Peter Wang, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, YAMAMOTO Mitsuharu, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Eli Zaretskii, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Peter Wang, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly,
YAMAMOTO Mitsuharu <=
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Eli Zaretskii, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, YAMAMOTO Mitsuharu, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Eli Zaretskii, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, YAMAMOTO Mitsuharu, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Eli Zaretskii, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Peter Wang, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Peter Wang, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Lars Magne Ingebrigtsen, 2016/04/25
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Eli Zaretskii, 2016/04/26
- bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly, Peter Wang, 2016/04/25