From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: SUNG TAE KIM <itaemu@gmail.com>, 64420@debbugs.gnu.org
Subject: bug#64420: string-width of … is 2 in CJK environments
Date: Fri, 14 Jul 2023 13:11:21 -0700 [thread overview]
Message-ID: <C53143B8-6466-440F-BE5F-E57AB77A9732@gmail.com> (raw)
In-Reply-To: <83351q4uvg.fsf@gnu.org>
> On Jul 14, 2023, at 4:04 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: SUNG TAE KIM <itaemu@gmail.com>
>> Date: Fri, 14 Jul 2023 18:21:42 +0900
>> Cc: 64420@debbugs.gnu.org
>>
>> What I meant by default was default in the CJK language environment and the default width of the
>> ambiguous characters in CJK environment should be narrow. Current emacs changes the width of
>> ambiguous characters to wide if the user activates the CJK environment. The unicode standard
>> recommendation is set the width narrow at unclear circumstances but emacs changes the width to
>> wide even if it can't know what font is currently used. For that reason, I don't think such behavior is
>> aligned well with the unicode standard.
>
> We don't blindly follow the Unicode Standard. We seriously consider
> its recommendations, and then do whatever we think is best for our
> users.
>
>> Furthermore, The majority of the default width of those
>> characters in the CJK environment is narrow on contemporary implementation of the terminals from
>> my limited experience. However, Considering the emacs package ecosystem, current emacs
>> behavior is ok as long as there's an easy option for changing such values.
>
> It is not yet clear to me whether handling these characters as narrow
> by default in CJK language-environments is TRT. But adding an option
> to do so is a first step in that direction, if indeed this is the
> right direction: we can in the future make this optional behavior be
> the default, if we arrive at the conclusion that most users configure
> their fonts and their terminal emulators such that these characters
> have the narrow width.
I tend to agree with Sung Tae, but this sounds like a reasonable compromise to me.
Yuan
next prev parent reply other threads:[~2023-07-14 20:11 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 [this message]
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
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
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=C53143B8-6466-440F-BE5F-E57AB77A9732@gmail.com \
--to=casouri@gmail.com \
--cc=64420@debbugs.gnu.org \
--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 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).