all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: itaemu@gmail.com, casouri@gmail.com, 64420@debbugs.gnu.org
Subject: bug#64420: string-width of … is 2 in CJK environments
Date: Sun, 13 Aug 2023 13:48:42 +0300	[thread overview]
Message-ID: <81c993ab-eefd-26ee-df73-ef1e3a57740a@gutov.dev> (raw)
In-Reply-To: <83sf8ncy62.fsf@gnu.org>

On 13/08/2023 08:24, Eli Zaretskii wrote:
>> Date: Sun, 13 Aug 2023 03:22:41 +0300
>> Cc:itaemu@gmail.com,64420@debbugs.gnu.org
>> From: Dmitry Gutov<dmitry@gutov.dev>
>>
>> On 11/08/2023 21:07, Yuan Fu wrote:
>>> On GUI display, the later-half of the ambiguous characters are definitely wider than one char, but they aren’t quite 2 chars wide either. But I guess it doesn’t matter too much since one should use pixel size on GUI anyway.
>> BTW, I think most double-width characters on GUI are less than 2
>> characters wide?
>>
>> So the point here would be that some "ambiguous" ones are still wider
>> than 1, I guess.
> According to Yuan, at least in his environment those characters have a
> width that is closer to 2 than to 1.  In which case using 2 would
> produce better alignment.  Of course, using string-pixel-width will
> produce an even better alignment.

In GUI, that is. But if they are displayed with width 1 in terminal, we 
better make string-width return 1 for them too.

That might be slightly worse for certain applications (like popup in 
company), but at least the basic rendering and navigation bugs in 
terminal will be fixed this way. And the new popup rendering for company 
(using string-width and spacing instructions) is close to being ready 
anyway.





  reply	other threads:[~2023-08-13 10:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-02 12:57 bug#64420: string-width of … is 2 in CJK environments Dmitry Gutov
2023-07-02 13:10 ` Eli Zaretskii
2023-07-02 13:20   ` Dmitry Gutov
2023-07-02 13:43     ` Eli Zaretskii
2023-07-07  2:13       ` Dmitry Gutov
2023-07-07  6:29         ` Eli Zaretskii
2023-07-11  2:13           ` Dmitry Gutov
2023-07-11 11:41             ` Eli Zaretskii
2023-07-11  2:23       ` Dmitry Gutov
2023-07-11 11:48         ` Eli Zaretskii
2023-07-11 18:13           ` Dmitry Gutov
2023-07-11 18:45             ` Eli Zaretskii
2023-07-12  1:17               ` Dmitry Gutov
2023-07-12 19:54                 ` Dmitry Gutov
2023-07-12 21:11                 ` Yuan Fu
2023-07-13  5:23                   ` Eli Zaretskii
2023-07-27  1:52                     ` Dmitry Gutov
2023-07-14  4:45 ` SUNG TAE KIM
2023-07-14  6:58   ` Eli Zaretskii
2023-07-16 11:51     ` Eli Zaretskii
2023-07-14  9:21 ` SUNG TAE KIM
2023-07-14 11:04   ` Eli Zaretskii
2023-07-14 20:11     ` Yuan Fu
2023-07-16 16:59 ` SUNG TAE KIM
2023-07-16 17:15   ` Eli Zaretskii
2023-08-05 15:01     ` Eli Zaretskii
2023-08-10 21:58       ` Yuan Fu
2023-08-11  5:53         ` Eli Zaretskii
2023-08-11 18:07           ` Yuan Fu
2023-08-11 18:36             ` Eli Zaretskii
2023-08-12 20:18               ` Yuan Fu
2023-08-11 22:34             ` Dmitry Gutov
2023-08-13  0:22             ` Dmitry Gutov
2023-08-13  5:24               ` Eli Zaretskii
2023-08-13 10:48                 ` Dmitry Gutov [this message]
2023-08-13 12:01                   ` Eli Zaretskii
2023-08-13 12:53                     ` Dmitry Gutov
2023-08-11 23:52       ` Dmitry Gutov
2023-08-12  5:50         ` Eli Zaretskii
2023-08-12 16:40           ` Dmitry Gutov
2023-08-12 17:09             ` 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

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

  git send-email \
    --in-reply-to=81c993ab-eefd-26ee-df73-ef1e3a57740a@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=64420@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=itaemu@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 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.