From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roman Zippel Subject: Re: [PATCH] Full NLS support for HFS (classic) filesystem Date: Tue, 31 May 2005 17:28:09 +0200 (CEST) Message-ID: References: <429B1E35.2040905@rambler.ru> <429C68A0.20003@rambler.ru> <429CBC75.2030605@rambler.ru> <429CD545.1070308@rambler.ru> <1117550958.8073.30.camel@imp.csi.cam.ac.uk> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Pavel Fedin , linux-fsdevel@vger.kernel.org Return-path: Received: from scrub.xs4all.nl ([194.109.195.176]:56462 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S261887AbVEaP2L (ORCPT ); Tue, 31 May 2005 11:28:11 -0400 To: Anton Altaparmakov In-Reply-To: <1117550958.8073.30.camel@imp.csi.cam.ac.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi, On Tue, 31 May 2005, Anton Altaparmakov wrote: > So unless you use UTF8, any other conversion using NLS/code pages will > always have failure cases... No suprise. :) Anyone working with different encodings and doesn't use utf8, simply has to expect problems. > > So create two functions uni2char/char2uni, which provide perfect reverse > > mapping. Sorry, but I don't understand what your problem is here. > > It seems you're making it more complex than it really is. > > That is impossible due to the problems with compatibility characters I > explained above which why I would agree with you that such magic > conversions should never happen, just put "use utf8 if you have > problems" in the mount man page... He only wants to convert from one 8-bit encoding to another 8-bit encoding. It's a hack, but it's a hack which can be done transparently via the nls layer, so it doesn't has to be done in the filesystem. bye, Roman