Re: [PATCH] Full NLS support for HFS (classic) filesystem

[Roman Zippel <zippel@linux-m68k.org>]

Hi,

On Tue, 31 May 2005, Pavel Fedin wrote:

> > > /dev/cdrom /mnt/cdrom iso9660,udf,hfsplus,hfs
> > > user,noauto,iocharset=koi8-r,codepage=866,hfscodepage=10007 0 0
> > 
> > Use different mount points. This is not a reason to create a lot of
> > different options all doing the same.
> 
>  Why??? It's incomfortable for the user!

Because it's a user space problem, if you want to use different codepages 
for different cd's tell it to mount. The kernel only provides the 
functionality, giving the same functionality several different names is 
not an option.

> > This is not HFS specific problem, you have this problem with any fs using
> > nls. fat does the comparison using the translated names, but that just means
> > it may find the wrong file instead of no file.
> 
>  Yes, it may find wrong file. But i mean here that HFS does not use string
> comparison at all for finding a file but some specific hashing (i tried to
> understand how it actually works and was unable to, too difficult). So it just
> will not find many files at all, even if names are translated correctly. As i
> say, i tried this, it completely failed.

If the names were translated correctly, HFS would have found them. You 
need to give me an example, which should have worked, but failed.

>  Don't understand about dynamic NLS module. What code should it contain?

Create the tables in a nls module and you can do whatever you want in the 
uni2char/char2uni functions.

>  P.S. I think you know the HFS implementation better than me. Why don't you
> beleive me that there is no other solution?

Why don't you believe me there is a better solution? :)

bye, Roman