unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Wang <ptr.wang@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23362@debbugs.gnu.org
Subject: bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly
Date: Mon, 25 Apr 2016 17:18:58 +0800	[thread overview]
Message-ID: <CABpyqyhUDgWYXcYm0S0sW2Nzeqfa2kVusUsOisqZMauZYqEsHA@mail.gmail.com> (raw)
In-Reply-To: <83vb362heh.fsf@gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 1001 bytes --]

Here is a screenshot showing the difference.

On Mon, Apr 25, 2016 at 4:59 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> > 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.
>
> Thanks.
>

[-- Attachment #1.2: Type: text/html, Size: 1580 bytes --]

[-- Attachment #2: emacs_unicode_display.png --]
[-- Type: image/png, Size: 101456 bytes --]

  reply	other threads:[~2016-04-25  9:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-24 17:40 bug#23362: 25.0.93; Unicode chars (such as 0x1F600) are not rendered correctly Peter Wang
2016-04-24 19:30 ` Eli Zaretskii
2016-04-24 20:59   ` Peter Wang
2016-04-25  0:37     ` YAMAMOTO Mitsuharu
2016-04-25  6:01       ` Eli Zaretskii
2016-04-25  8:28         ` YAMAMOTO Mitsuharu
2016-04-25  8:39           ` Peter Wang
2016-04-25  9:06             ` YAMAMOTO Mitsuharu
2016-04-25  8:59           ` Eli Zaretskii
2016-04-25  9:18             ` Peter Wang [this message]
2016-04-25  9:40             ` YAMAMOTO Mitsuharu
2016-04-25  9:59               ` Eli Zaretskii
2016-04-25 10:07                 ` YAMAMOTO Mitsuharu
2016-04-25 10:19                   ` Eli Zaretskii
2016-04-25 10:33                     ` YAMAMOTO Mitsuharu
2016-04-25 11:00                       ` Eli Zaretskii
2016-04-25 11:28                         ` Peter Wang
2016-04-25 11:58                         ` Peter Wang
2016-04-25 11:58                         ` Peter Wang
2016-04-25 23:13                           ` Lars Magne Ingebrigtsen
2016-04-26  5:51                           ` Eli Zaretskii
2016-04-25 11:14                     ` Peter Wang

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=CABpyqyhUDgWYXcYm0S0sW2Nzeqfa2kVusUsOisqZMauZYqEsHA@mail.gmail.com \
    --to=ptr.wang@gmail.com \
    --cc=23362@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).