From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Justin Heyes-Jones <justinhj@gmail.com>, 33207@debbugs.gnu.org
Subject: bug#33207: 26.1; Incorrect display of braille unicode
Date: Tue, 30 Oct 2018 20:54:31 -0400 [thread overview]
Message-ID: <87muqvhr5k.fsf@gmail.com> (raw)
In-Reply-To: <83muqvjq91.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 30 Oct 2018 19:31:06 +0200")
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> The problem is that the braille unicode character BRAILLE PATTERN BLANK (0x2800) doesn't display as
>> blank but appears as what looks like a different character. I have submitted a question to stackoverflow which
>> includes screen shots of what the code should look like in both terminal and in emacs. I am running on
>> macOS Mojave 10.14.
>
> Probably macOS specific: that character displays fine on MS-Windows.
On my GNU/Linux box with both GTK and Lucid builds, I see that the
blanked dots do show up, similar to what the OP shows in their linked
screenshot. Interestingly, I *don't* see the blanked dots in the
completion window for C-x 8 RET braille TAB.
[-- Attachment #2: screenshot of braille characters --]
[-- Type: image/png, Size: 85943 bytes --]
[-- Attachment #3: Type: text/plain, Size: 360 bytes --]
Doing C-u C-x = on the character in the completion window shows (where
it's blanked out as expected)
xft:-unknown-DejaVu Serif-normal-italic-normal-*-15-*-*-*-*-0-iso10646-1 (#xA6F)
whereas, the same character in other places shows (where it's not
entirely blanked out)
xft:-unknown-Unifont-normal-normal-normal-*-15-*-*-*-d-0-iso10646-1 (#x2803)
next prev parent reply other threads:[~2018-10-31 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 15:50 bug#33207: 26.1; Incorrect display of braille unicode Justin Heyes-Jones
2018-10-30 17:31 ` Eli Zaretskii
2018-10-31 0:54 ` Noam Postavsky [this message]
2018-10-31 16:09 ` Eli Zaretskii
[not found] ` <CAHO-RXn_D3C+rjR_0EWDRb6WKoRPS-FMUwffPmYN+mm5myp1Wg@mail.gmail.com>
2018-11-04 12:49 ` 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
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=87muqvhr5k.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=33207@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=justinhj@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 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).