From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: itaemu@gmail.com, dmitry@gutov.dev, 64420@debbugs.gnu.org
Subject: bug#64420: string-width of … is 2 in CJK environments
Date: Fri, 11 Aug 2023 21:36:53 +0300 [thread overview]
Message-ID: <83v8dlfmt6.fsf@gnu.org> (raw)
In-Reply-To: <4B239A5E-0878-4304-8C28-FEEC1EBC1B4E@gmail.com> (message from Yuan Fu on Fri, 11 Aug 2023 11:07:26 -0700)
> From: Yuan Fu <casouri@gmail.com>
> Date: Fri, 11 Aug 2023 11:07:26 -0700
> Cc: dmitry@gutov.dev,
> itaemu@gmail.com,
> 64420@debbugs.gnu.org
>
> On terminal, I saw an interesting option, “Ambiguous characters are double-width” (terminal-setting.png), which is the same as cjk-ambiguous-chars-are-wide. If I turn it on all the ambiguous characters are indeed displayed in double-width. (terminal-narrow.png, terminal-wide.png)
And in that case, you need to set cjk-ambiguous-chars-are-wide non-nil
to have Emacs display those characters correctly? Or does that option
have no effect on the correctness of the |Emacs display on that
terminal?
> 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.
Is the actual width closer to 1 or to 2?
Thanks.
next prev parent reply other threads:[~2023-08-11 18:36 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 [this message]
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
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=83v8dlfmt6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64420@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=dmitry@gutov.dev \
--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.