unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 27403@debbugs.gnu.org, schwab@linux-m68k.org, adam.niederer@gmail.com
Subject: bug#27403: 26.0.50; Indentation misalignment with Unicode code points >65535
Date: Sat, 05 Feb 2022 07:40:10 +0100	[thread overview]
Message-ID: <87y22perzp.fsf@gnus.org> (raw)
In-Reply-To: <831r0j3ycz.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 04 Feb 2022 09:05:48 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> In the fonts I use, it's definitely wide.  But so is ☺, which is marked
>> as narrow.
>> 
>> So ❓
>
> I don't see how this can be solved as long as indentation works in
> columns.  If some font produces a glyph whose width isn't anywhere
> close to the Unicode width specifications, what can we do except tell
> people not to use those fonts?
>
> Alternatively, if it turns out that most fonts use different width, we
> could amend our char-width table to be consistent with those fonts.

Yes, it would be nice if this worked better out-of-the-box for most
people, but I wouldn't want to manually maintain a list of typical char
widths, either.

By the way, ☺ in the terminal here (Debian/bullseye) does take 1
character while 👍 takes two, so perhaps they're also using the same
Unicode data that we're using...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-02-05  6:40 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
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 [this message]
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=87y22perzp.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=27403@debbugs.gnu.org \
    --cc=adam.niederer@gmail.com \
    --cc=eliz@gnu.org \
    --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).