From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 27403@debbugs.gnu.org, adam.niederer@gmail.com
Subject: bug#27403: 26.0.50; Indentation misalignment with Unicode code points >65535
Date: Sat, 17 Jun 2017 13:28:09 +0300 [thread overview]
Message-ID: <83shiyzz5y.fsf@gnu.org> (raw)
In-Reply-To: <m2wp8b10om.fsf@linux-m68k.org> (message from Andreas Schwab on Sat, 17 Jun 2017 10:24:41 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Adam Niederer <adam.niederer@gmail.com>, 27403@debbugs.gnu.org
> Date: Sat, 17 Jun 2017 10:24:41 +0200
>
> On Jun 17 2017, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > That's because U+1F44D is a double-width character:
> >
> > (char-width ?👍) => 2
>
> The list in international/character.el is outdated.
I think the intent was to produce it from the Unicode data
(EastAsianWidth.txt). I don't recall why this didn't happen; patches
are welcome. Alternatively, synching the data with the latest Unicode
manually would be good as a stopgap.
> > So as long as indentation works in columns and not in pixels, this is
> > a "feature".
>
> You surely don't want indentation to depend on font selection.
Patches for doing indentation in pixels are welcome, of course.
next prev parent reply other threads:[~2017-06-17 10:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 6:28 bug#27403: 26.0.50; Indentation misalignment with Unicode code points >65535 Adam Niederer
2017-06-17 7:18 ` Andreas Schwab
2017-06-17 8:05 ` Eli Zaretskii
2017-06-17 8:24 ` Andreas Schwab
2017-06-17 10:28 ` Eli Zaretskii [this message]
2017-06-17 12:09 ` Andreas Schwab
2017-06-17 13:39 ` Eli Zaretskii
2017-06-17 18:07 ` Andreas Schwab
2017-06-17 18:21 ` Eli Zaretskii
2022-02-03 20:25 ` Lars Ingebrigtsen
2022-02-04 7:05 ` Eli Zaretskii
2022-02-05 6:40 ` Lars Ingebrigtsen
2022-02-05 7:51 ` Eli Zaretskii
2022-02-05 7:55 ` Lars Ingebrigtsen
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=83shiyzz5y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27403@debbugs.gnu.org \
--cc=adam.niederer@gmail.com \
--cc=schwab@linux-m68k.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).