all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31588@debbugs.gnu.org, jpa4q@virginia.edu
Subject: bug#31588: 26.1; format counts some Unicode characters as two
Date: Sun, 03 Jun 2018 12:29:20 -0400	[thread overview]
Message-ID: <87muwb96lb.fsf@gmail.com> (raw)
In-Reply-To: <83lgc89r6b.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 May 2018 09:37:32 +0300")

close 31588
quit

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Noam Postavsky <npostavs@gmail.com>
>> Date: Thu, 24 May 2018 20:50:45 -0400
>> Cc: 31588@debbugs.gnu.org
>> 
>> > As far as I can tell, something is off about the styled_format and how
>> > it counts characters- I suspect something about counting
>> > multibyte characters, but it's a little beyond me.
>> 
>> I think it's intended, ➖ and ❌ are wide characters:
>> 
>>     (mapcar #'char-width '(?➖ ?❌ ?▶ ?✚ ?▷ ?◼))
>>     ;=> (2 2 1 1 1 1)
>
> Yes, that's the reason.
>
>> Although in my current font the width seems to be more like 1.8 or
>> something.
>
> Unfortunately, the actual width depends on the font, and what's more,
> sometimes varies significantly between different fonts.  Maybe we
> should have a variant of char-width that actually looks at the font
> (of course, such a variant will need a window or frame as one of its
> arguments).

Well, I don't know if format could do anything useful with a non-integer
width anyway.

> But with the current state of our support for wide characters, this is
> not a bug.

Okay, I'm closing this report.






      reply	other threads:[~2018-06-03 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25  0:36 bug#31588: 26.1; format counts some Unicode characters as two James P. Ascher
2018-05-25  0:50 ` Noam Postavsky
2018-05-25  6:37   ` Eli Zaretskii
2018-06-03 16:29     ` Noam Postavsky [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87muwb96lb.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=31588@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jpa4q@virginia.edu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.