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

[Pavel Fedin <sonic_amiga@rambler.ru>]

Anton Altaparmakov wrote:

> NLS is fundamentally broken so there is no point in trying to use clever
> dynamic tables to do it.  Just ignore it is IMO the correct way.
> 
> btw. not having mappings is not even the biggest problem.  It gets much
> worse and even Pavel's dynamic mappings are not actually going to work.
> For example there are some characters in asian languages which when
> translated will give a character but when you then reverse translate
> this character you end up with something that is not the same as the
> starting character.

  Did you verify this or just suggest? My dynamic mapping should work 
because reverse translation table is created by reversing "direct" 
translation dynamic table, which is built from two NLSes.

> a lot of asian people have complained
> to me about ntfs when used with codepages.  All of them went away happy
> when I told them to tell the ntfs driver to use utf8...

  Yes, with utf8 everything really works because every character is 
reverse-translatable in this case. With HFS too - look at my 
implementation, it handles iocharset=utf8 as a special case where direct 
and reverse translation is done directly via NLS module and there's no 
need for dynamic tables.
  But in Russia UTF-8 is not widely used because of no need to. We 
prefer direct compatibility with ASCII files from other systems.

-- 
  Kind regards, Pavel Fedin