zsh-workers
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Mikael Magnusson <mikachu@gmail.com>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: UNICODE Private Use Area characters in BUFFER
Date: Sun, 23 Oct 2022 19:29:15 +0200	[thread overview]
Message-ID: <CAN=4vMohKT=CAx5XoSAHrDvx4J--58535h-ZgCn3dkSqvZKDZg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7a-8TtMcXvrmq6RLHbU-maHdD1Zf2ck_h_kzK61bmEr_A@mail.gmail.com>

On Sun, Oct 23, 2022 at 7:02 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Sun, Oct 23, 2022, 9:45 AM Roman Perepelitsa <roman.perepelitsa@gmail.com> wrote:
>>
>> A few more tests to show that Private Use Area characters work find in
>> zsh with the exception that you cannot put then in BUFFER:
>
>
> I don't have the code handy, but I suspect this is due to the implementation of wisprnt() [sic] returning false for those characters.

You are right, iswprint(0xE0B0) returns 0.

I'm compiling zsh with --enable-unicode9, so instead of iswprint() it
goes into u9_iswprint(). This function explicitly handles this case
and returns 0, just like iswprint(). So we get this:

    WCWIDTH(0xE0B0) => 1
    WC_ISPRINT(0xE0B0) => 0

I think u9_iswprint() should return 1 for Private Use Area characters.

Roman.

P.S.

Why isn't --enable-unicode9 a default?


  reply	other threads:[~2022-10-23 17:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23 10:12 Roman Perepelitsa
2022-10-23 16:29 ` Mikael Magnusson
2022-10-23 16:43   ` Roman Perepelitsa
2022-10-23 17:02     ` Bart Schaefer
2022-10-23 17:29       ` Roman Perepelitsa [this message]
2022-10-23 18:30         ` Unicode9 (was Re: UNICODE Private Use Area characters in BUFFER) Bart Schaefer
2022-10-23 19:30           ` Roman Perepelitsa
2022-10-23 21:57           ` Mikael Magnusson
2022-10-23 18:54         ` UNICODE Private Use Area characters in BUFFER Bart Schaefer
2022-10-23 19:26           ` Roman Perepelitsa
2022-11-04  9:55         ` Jun T
2022-10-23 22:42     ` Mikael Magnusson
2022-10-23 23:16       ` Roman Perepelitsa
2022-10-23 23:35         ` Bart Schaefer
2022-10-23 23:46           ` Bart Schaefer
2022-10-24  1:27             ` Mikael Magnusson
2022-10-24  1:43               ` Bart Schaefer
2022-10-24 10:50                 ` Roman Perepelitsa
2022-11-04 10:31                   ` Jun T
2022-11-04 10:33                     ` Roman Perepelitsa
2022-11-04 11:06                       ` Jun T
2022-11-04 11:09                         ` Roman Perepelitsa
2022-11-04 15:32                           ` Jun T

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='CAN=4vMohKT=CAx5XoSAHrDvx4J--58535h-ZgCn3dkSqvZKDZg@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=mikachu@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).