From: Eli Zaretskii <eliz@gnu.org>
To: Oleh Krehel <ohwoeowho@gmail.com>
Cc: 20793@debbugs.gnu.org
Subject: bug#20793: 25.0.50; Some Unicode glyphs aren't monospaced
Date: Fri, 12 Jun 2015 16:43:13 +0300 [thread overview]
Message-ID: <83twudqbym.fsf@gnu.org> (raw)
In-Reply-To: <87lhfpulwk.fsf@gmail.com>
> From: Oleh Krehel <ohwoeowho@gmail.com>
> Date: Fri, 12 Jun 2015 14:54:51 +0200
>
> My preferred font is "DejaVu Sans Mono". When using the Unicode
> character "✜", its width is more than the standard char width. This
> causes alignment problems for me.
Which alignment problems? Can you describe them?
In general, Emacs cannot ensure all characters it displays will be of
the same pixel width, this is simply impossible, especially when some
characters require the use of non-default fonts.
> This issue doesn't occur in Emacs 24.5.2. There, the char has the same
> width as all others.
>
> Details on the char in Emacs 25:
>
> position: 227 of 348 (65%), column: 35
> character: ✜ (displayed as ✜) (codepoint 10012, #o23434, #x271c)
> preferred charset: unicode (Unicode (ISO10646))
> code point in charset: 0x271C
> script: symbol
> syntax: w which means: word
> category: .:Base
> to input: type "C-x 8 RET 271c" or "C-x 8 RET HEAVY OPEN CENTRE CROSS"
> buffer code: #xE2 #x9C #x9C
> file code: #xE2 #x9C #x9C (encoded by coding system utf-8-emacs-unix)
> display: by this font (glyph code)
> xft:-unknown-Symbola-normal-normal-semicondensed-*-15-*-*-*-*-0-iso10646-1 (#x9F9)
>
> Character code properties: customize what to show
> name: HEAVY OPEN CENTRE CROSS
> old-name: HEAVY OPEN CENTER CROSS
> general-category: So (Symbol, Other)
> decomposition: (10012) ('✜')
>
> There are text properties here:
> fontified t
>
> Details on the char in Emacs 24.5.2:
>
> position: 1819 of 2174 (84%), column: 5
> character: ✜ (displayed as ✜) (codepoint 10012, #o23434, #x271c)
> preferred charset: unicode (Unicode (ISO10646))
> code point in charset: 0x271C
> script: symbol
> syntax: w which means: word
> category: .:Base
> to input: type "C-x 8 RET HEX-CODEPOINT" or "C-x 8 RET NAME"
> buffer code: #xE2 #x9C #x9C
> file code: #xE2 #x9C #x9C (encoded by coding system utf-8-unix)
> display: by this font (glyph code)
> xft:-unknown-DejaVu Sans Mono-normal-normal-normal-*-15-*-*-*-m-0-iso10646-1 (#xAD1)
As you see, Emacs 25.0.50 used a different font for this character.
Why did you expect it to use DejaVu Sans Mono? What is your frame's
default font? Do you have any font-related customizations, and if so,
could you please show them?
Also, when was your Emacs 25 built? There were changes lately in this
area, so it's important to know whether your binary is recent or not.
(The output of "M-x report-emacs-bug RET" will be appreciated.)
next prev parent reply other threads:[~2015-06-12 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 12:54 bug#20793: 25.0.50; Some Unicode glyphs aren't monospaced Oleh Krehel
2015-06-12 13:43 ` Eli Zaretskii [this message]
2015-06-12 13:51 ` Oleh Krehel
2015-06-12 14:22 ` 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=83twudqbym.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20793@debbugs.gnu.org \
--cc=ohwoeowho@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).