Kaixo!

On Fri, Sep 20, 2002 at 12:47:16AM +0200, Keld J�rn Simonsen wrote:

> > It is technically possible.
> > But it won't be accepted socially.
> 
> Why not?

I already proposed the idea of having a fs with a known encoding,
then having libs display the names according to the locale encoding;
that idea didn't get much support :)

> The codepage parameter is accepted socially, and

only for alien fs.
And only because they use typically different encodings than linux.
Those fs also impose other restrictions that a pure linux fs has not
(in filename lenght, in acceptable characters etc)

Note also that it is done at the kernel level, in a way it is done *before*
the fs gets available, so for system librairies it gets indistinguishable
from a "native" fs.

Now, if what you meant, was the ability to mount an ext2 partition and
tell to convert its filemanes using the kernel nls modules; yes, it could
be done.

> be done. And I could easly imagine scenarios in my ballpark
> with different users on the same multiuser linux machine not
> wanting to change over to utf-8 at the same time. Or programs in use
> that will not easily convert to utf8 and thus has to still
> run some other encoding.

Those scenarios won't benefit of the implementation of that idea.
The only situation would be once the whole system has switched to another
encoding, the ability to mount old partitions without having to actually
convert the filenames.

I'm not convinced it will be that usefull...
On an ext2 fs you can simply use "mv" to convert the filenames and convert
your partition to a clean one; the usefulness of the charset telling
options for joliet and vfat (and hfs also maybe?) are because you cannot
do that on those fs.

-- 
Ki �a vos v�ye b�n,
Pablo Saratxaga

http://chanae.stben.be/pablo/           PGP Key available, key ID: 0xD9B85466
[you can write me in Walloon, Spanish, French, English, Italian or Portuguese]

Attachment: msg03194/pgp00000.pgp
Description: PGP signature

Reply via email to