Date: Sun, 16 Jan 2005 21:28:20 -0800 From: David Yu <chiahsing@gmail.com> To: Christopher Vance <c@nu.org> Cc: freebsd-current@freebsd.org Subject: Re: NTFS unicode converting problem Message-ID: <ad2ada4b0501162128515533f3@mail.gmail.com> In-Reply-To: <20050117032255.GC630@nu.org> References: <ad2ada4b05011613445601befe@mail.gmail.com> <20050117020039.GB630@nu.org> <ad2ada4b05011618258c80402@mail.gmail.com> <20050117032255.GC630@nu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
The problem is that I have to default XLAT16_ACCEPT_3BYTE_CHR in both libkiconv and module/libiconv.ko. Though it works, I don't it is a good way to use translation table since UCS-2 to UTF-8 is so straightforward. Maybe we need to write a new kernel side iconv converter for this? I have no idea about those iconv codes in the kernel at all. On Mon, 17 Jan 2005 14:22:55 +1100, Christopher Vance <c@nu.org> wrote: > On Sun, Jan 16, 2005 at 06:25:52PM -0800, David Yu wrote: > >In my case, those Chinese filenames are still in UCS-2LE, and all > >characters are in plane 0. I tried to modify codes so that it can > >directly store the conversion result into the dirent structure, but > >the convchr() funtion failed everytime for Chinese character while > >there is no problem with Ascii characters. I thought converting from > >UCS-2 to UTF-8 should be very easy? > > Maybe the conversion routine disagrees with you about byte order? > > -- > Christopher Vance >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ad2ada4b0501162128515533f3>