unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Georges Ko <gko@gko.net>
To: 24699@debbugs.gnu.org
Subject: bug#24699: Some characters should have char-width of 2
Date: Sun, 16 Oct 2016 00:59:39 +0800	[thread overview]
Message-ID: <yd8reg3hpmys.fsf@gko.net> (raw)
In-Reply-To: <yd8rr37h28rp.fsf@gko.net>

Eli Zaretskii <eliz@gnu.org> writes:

> Not all characters of a code block have the same width attribute.

OK, understood. I'll use EastAsianWidth.txt as reference.

>> (char-width ?🍁) => 2
>> (char-width ?🐻) => 1
>
> Yes, the 1F400..1F43E range was missing.  I now fixed that on the
> emacs-25 branch, so both of the above expressions return 2.

OK.

>> Could the EastAsianWidth.txt (not found in Emacs sources) used to
>> generate was an old version?
>
> It's more probable that this range was simply omitted.

>> Is the generated output in characters.el starting from this line?
>
> It's not aut-generated, it was written by hand.

Shouldn't all current char-width be checked against EastAsianWidth.txt?
I'll check for discrepancies...

>> A side effect of having non-consistent char-width is badly aligned
>> org-mode tables. A table with a MAPLE LEAF (width=2) and a BEAR FACE
>> (width=1) is aligned like this by org-mode:
>
> The width attribute will only help in alignment of text if the font
> used for these characters is monospaced, and then if the font
> designers indeed kept the width according to Unicode.  Most fonts that
> support these characters are variable-pitch fonts, so you won't have
> any alignment anyway, unless org-table aligns columns on the pixel
> level, by using the pixel size of the text.
>
>> E | W | Char  | Code Point       | Name
>> --+---+-------+------------------+-------------------------------
>> 2 | 1 | 🐀    | #x1F400 (128000) | RAT
>> 2 | 1 | 🐁    | #x1F401 (128001) | MOUSE
>> 2 | 1 | 🐂    | #x1F402 (128002) | OX
>
> On my display, these columns are not aligned at all, even for
> characters whose char-width is 2.  And I don't expect them to be
> aligned, because the font used is Symbola, which is not monospaced.

Segoe UI Symbol seems better in this regard, unfortunately, it has less
displayable characters.

> OK to close this bug now?

OK.

Georges
-- 
 Georges Ko                     gko@gko.net                      2016-10-16






  reply	other threads:[~2016-10-15 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-15 10:42 bug#24699: Some characters should have char-width of 2 Georges Ko
2016-10-15 12:17 ` Eli Zaretskii
2016-10-15 14:31   ` Georges Ko
2016-10-15 15:05     ` Eli Zaretskii
2016-10-15 16:59       ` Georges Ko [this message]
2016-10-15 17:14         ` 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=yd8reg3hpmys.fsf@gko.net \
    --to=gko@gko.net \
    --cc=24699@debbugs.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).