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

[Pavel Fedin <sonic_amiga@rambler.ru>]

Anton Altaparmakov wrote:

> No, I have not verified it.  I do not use HFS at all.  But your direct
> translation dynamic table will already be ambiguous if the "right" NLS
> pages were used to create it.

  What do you mean under "right"?

>  Or what do you do when two different
> characters in on NLS page are translated to the _sam_ character in the
> other NLS page?

  Didn't meet such cases. Well, you're right, in this case dynamic table 
building will fail. But at least dynamic table solves problems with 
non-translatable characters.

> Where is the problem with compatibility?  Any sane application will
> translate files on the fly.  On my SUSE 9.3 box (uses UTF8) when I open
> a text file in vim (my editor of choice) and the text file contained
> characters in a codepage, vim translates it to the corresponding UTF8
> character and then translates it back into the original codepage when I
> save the file.  (It shows a "[translated]" message at the bottom of the
> screen after I open such a file so I know this has happened.)

  Well, what will you tell me to do with all my files on my EXT3 with 
russian names? How can i convert them?
  Well, we've just got used to koi8-r. Why can't i continue to use it? 
It satisfies me at 100%. AFAIK Linux is free system where everything is 
a choice. So why do you force me and argue that i'm completely wrong?

-- 
  Kind regards, Pavel Fedin