Followup to: <[EMAIL PROTECTED]>
By author: Glenn Maynard <[EMAIL PROTECTED]>
In newsgroup: linux.utf8
>
> But I can't see the BOM; ls just shows "hello". That's why I'm
> suggesting that zero-width characters not useful in filenames be
> escaped as the above by "ls" and friends. (Nothing new; ls already
> escapes ASCII control characters and other things.)
>
Agreed. "ls -b" in particular needs to be extra careful here. This
*does* beg the question what wisprint() and friends actually return.
At some point (and sooner rather than later) we probably need an API
which can read out all the Unicode character attributes.
>
> The unclear parts are 1: which characters can be escaped like this
> (probably the vast majority of unprinting characters), and 2: what to do
> about the characters that can't.
>
I guess my answer to 2) is that "ls -b" should obey the "if you can't
see it, escape it" rule.
>
> (By the way, you're reiterating stuff I and others have already said
> about filesystems not normalizing; we've been there already, and
> as a rarity, nobody's disagreeing. :)
>
Yes, I didn't quite notice that I was responding to some fairly old
messages. Sorry 'bout that. It's just that it's really important.
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <[EMAIL PROTECTED]>
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
