From: Andrey Borzenkov <arvidjaar@newmail.ru>
To: zsh-workers@sunsite.dk
Subject: Re: [PATCH] zle_refresh multibyte fix
Date: Fri, 25 Feb 2005 22:17:45 +0300 [thread overview]
Message-ID: <200502252217.46201.arvidjaar@newmail.ru> (raw)
In-Reply-To: <200502231457.j1NEvfBI032390@news01.csr.com>
On Wednesday 23 February 2005 17:57, Peter Stephenson wrote:
>
> > Actually I find wc stuff very easy and suitable for using as internal
> > representation in zsh core. But this is separate topic.
>
> Apart from the inefficiency of extending every byte that comes into the
> shell into (typically) a four-byte integer, we can't rely on input and
> output bytes being a valid wide character in the current locale at all.
> I think the shell has to handle arbitrary strings of bytes without
> mutilating them. Consider, for example:
>
> # Pass secret byte to my utility
> my_utility $'\xff'
>
> (or any other string you like, the only point being that it isn't a
> valid multibyte character string). I don't see why we should
> arbitrarily decide that doesn't work because it doesn't convert to a
> wide character. It will simply break far too many things.
>
I do not have easy answer, but what would be semantic of
- regexps ([[:print:]] et al.)?
- $foo[n,m] for scalar?
- Upper/Lower conversion?
- comparison (collating)?
apparently at least bash treats things byte-oriented:
bash-3.00$ echo к$(zsh -c "echo $'\xff\xff\xff'") | xxd
0000000: d0ba ffff ff0a ......
bash-3.00$ echo к$(zsh -c "echo $'\xff\xff\xff'") | { read foo; case "$foo"
in ???? ) echo yes;; * ) echo no; esac; }
no
but
bash-3.00$ zsh -c "echo $'\xff\xff\xff'" | { read foo; case "$foo" in ??? )
echo yes;; * ) echo no; esac; }
yes
and has definite problem editing non-ASCII input line (actually the same as
zsh had - cursor position is wrong).
But it is hardly acceptable for zsh. It depends (completion code in the first
place) too much on correct character handling.
OTOH does mb -> wc -> mb preserves original byte sequence? It is true for
UTF-8 (at least in current revision), but I am not sure that it is true for
arbitrary encoding.
-andrey
next prev parent reply other threads:[~2005-02-25 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 14:27 Andrey Borzenkov
2005-02-23 14:57 ` Peter Stephenson
2005-02-25 19:17 ` Andrey Borzenkov [this message]
2005-02-28 10:41 ` Peter Stephenson
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=200502252217.46201.arvidjaar@newmail.ru \
--to=arvidjaar@newmail.ru \
--cc=zsh-workers@sunsite.dk \
/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).