Hello Colin,
On Fri, Jan 03, 2003 at 09:50:26PM -0500, Colin Walters wrote:
> In summary, UTF-8 is the *only* sane character set to use for
> filenames.
At least I agree to this :-)
I think that we need filename conversion between UTF-8 and the user's
character set, because we cannot ban all non-UTF8 terminal types. In
my opinion the main problem is, where this conversion should take
place.
Because a lot of programs is affected, it would gain us much, if we
could move this as deep as into libc or even into the kernel. I
remember there are some questions about character sets in the kernel
configuration. Are there file-systems with in-kernel character set
conversion?
> And like Tollef said, Red Hat 8 has already switched to defaulting to
> UTF-8 for new systems.
Does anybody know: how do they solve the problems we discuss here?
Where do they convert filenames, e.g. when I login via ssh and
type "ls -l Bär*" from my LC_CTYPE=ISO-8859-15 system?
> Again, major chunks of upstream software which have Unicode support
> (like GNOME), are *already* defaulting to interpreting filenames as
> UTF-8 by default.
And how is the conversion done there?
> > 2) How should already existing files with non-ASCII names
> > be converted?
>
> There are lots of different options; we could have a package
> 'unicode-transition' ...
Ok, I see that this is no real problem.
Jochen
--
Omm
(0)-(0)
http://www.mathematik.uni-kl.de/~wwwstoch/voss/index.html
Attachment:
pgpm92dBY2Li5.pgp
Description: PGP signature