On Tue, 25 Jan 2005 12:35:16 +0300, Pavel Fedin <[EMAIL PROTECTED]> wrote: > > how about just leave the characters unchanged? (remap them to the same > > codes in Unicode). > > But what to do when i convert then from unicode to 8-bit iocharset? This can > lead to that several characters in Mac charset will be converted to the same > character in Linux charset. This will lead to information loss and name will > not be reverse-translatable. > To describe the thing better: i have 8-bit Mac encoding and 8-bit target > encoding (iocharset). I need to convert from (1) to (2) and be able to > convert back. I tried to perform a one-way conversion like in other > filesystems but this didn't work. > Probably NLS tables can be used when iocharset is UTF8. If you wish i can > try to implement it after some time.
remap unicode character missing in filesystem codepage into something like '?'. I believe this is what nls routines do if converter returns -1 (error). You'd loose the new characters, right. But you'd loose them anyway, as they have no place in mac software. > > Unicode, and its encoding UTF8 IS commonly used everywhere. > > And Russia can (and often does) use it just as well. > > Many people say many software is not UTF8-ready yet. Anyway i had problems > when tried to use it. Many russian ASCII documents use 8-bit encoding so i > need to be able to deal with them. Many software assumes that 1 byte is 1 > character. just fix that software instead of polluting the kernel. And besides: software which _does_ work with unicode, can make a good use of an nls module for HFS. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
