From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: Sun Lin <sunlin7@yahoo.com>, 38202@debbugs.gnu.org
Subject: bug#38202: 26.2; emacs GUI can not display unicode 01F176
Date: Thu, 14 Nov 2019 05:32:48 +0100 [thread overview]
Message-ID: <87eeybt6vj.fsf@gnus.org> (raw)
In-Reply-To: <c4cff64c5b0329b410cebbe71550c8ca@webmail.orcon.net.nz> (Phil Sainty's message of "Thu, 14 Nov 2019 15:42:54 +1300")
Phil Sainty <psainty@orcon.net.nz> writes:
> On 2019-11-14 14:50, Sun Lin via "Bug reports for GNU Emacs, the Swiss
> army knife of text editors" wrote:
>> The U+1F176 (" v") should be NEGATIVE SQUARED LATIN CAPITAL LETTER
>> G.
>> But it's displayed as an square with hexel value in emacs GUI (in both
>> X11 and Win32).
>
> It displays fine for me in Emacs. Check the fonts you're using.
Yes, it probably means that a font that can display the character isn't
installed. It works fine for me, too, and my Emacs is using:
ftcrhb:-Free-Symbola-normal-normal-semicondensed-*-29-*-*-*-*-0-iso10646-1 (#x1EB5)
So this doesn't seem to be a bug, and I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-11-14 4:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <738140564.3723222.1573696245647.ref@mail.yahoo.com>
2019-11-14 1:50 ` bug#38202: 26.2; emacs GUI can not display unicode 01F176 Sun Lin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-11-14 2:42 ` Phil Sainty
2019-11-14 4:32 ` Lars Ingebrigtsen [this message]
2019-11-14 5:27 ` Phil Sainty
2019-11-14 5:33 ` Lars Ingebrigtsen
2019-11-14 6:18 ` via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-11-14 6:53 ` via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87eeybt6vj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=38202@debbugs.gnu.org \
--cc=psainty@orcon.net.nz \
--cc=sunlin7@yahoo.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.