Re: bash handles bytes instead of chars

[Chet Ramey]

®om wrote:

> printf was only a way to send 0xe282ac on stdin of each tool, it doesn't
> matter how printf interprets the bytes. What is important is how the
> tool ("cut" for example, or read -n) interprets them :)

I don't have any control over the various implementations of `cut' out
there.  The `read -n' issue already generated debate, and I decided to
change it to act on multibyte characters in the next version of bash.

Chet


-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/