all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dmitry@gutov.dev
Cc: itaemu@gmail.com, casouri@gmail.com, 64420@debbugs.gnu.org
Subject: bug#64420: string-width of … is 2 in CJK environments
Date: Sat, 05 Aug 2023 18:01:39 +0300	[thread overview]
Message-ID: <837cq9sfcc.fsf@gnu.org> (raw)
In-Reply-To: <83jzuz93rh.fsf@gnu.org> (message from Eli Zaretskii on Sun, 16 Jul 2023 20:15:30 +0300)

> Cc: casouri@gmail.com, 64420@debbugs.gnu.org
> Date: Sun, 16 Jul 2023 20:15:30 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > From: SUNG TAE KIM <itaemu@gmail.com>
> > Date: Mon, 17 Jul 2023 01:59:15 +0900
> > Cc: 64420@debbugs.gnu.org
> > 
> > I see no issue in changing default width of ambiguous characters to
> > narrow except variation selector blocks(FE00..FE0F, E0100..E01EF) and
> > private-use blocks(E000..F8FF, F0000..FFFFD, 100000..10FFFD) because
> > the characters in the former blocks are not standalone[1] and the
> > characters of the latter blocks are reserved for 3rd-party and
> > everything else seems standalone characters.
> > 
> > [1] https://en.wikipedia.org/wiki/Variation_Selectors_(Unicode_block)
> 
> Thanks.
> 
> I said I intend to end at #x324F because use-cjk-char-width-table
> doesn't touch ambiguous characters with higher codepoints, so they are
> already narrow in Emacs, and we don't need to "fix" them.

OK, this is now installed on master.  We have a new user option named
cjk-ambiguous-chars-are-wide; its default is t, but if set to nil, the
characters proclaimed by Unicode as "ambiguous" will have char-width
of 1, not 2.  Note that this option should be set either via 'setopt'
or the Customize interface, not via 'setq'.

Let me know how well this works for you.





  reply	other threads:[~2023-08-05 15:01 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 [this message]
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
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=837cq9sfcc.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.