Re: [Jfs-discussion] Problems with charset.
Brought to you by:
blaschke-oss,
shaggyk
From: Antonio A. <ap...@fa...> - 2004-06-28 22:39:03
|
From: Dave Kleikamp <sh...@au...> Subject: Re: [Jfs-discussion] Problems with charset. Date: Mon, 28 Jun 2004 10:57:25 -0500 > iocharset=utf8 tells jfs that the pathnames are utf-8, but that is not > the character set being used. 0xea is ê in iso8859-1. It could be a > valid byte of a utf-8 character, but the next two bytes would have to > have the high order bit set, and I assume they don't. (I'm sure they > are 's' and '.'.) > > > I have the iocharset=utf8 mount option set in fstab. > > Are you sure your system is configured in a utf-8 locale? (What is > $LANG?) > > > Needless to say that the filenames in the directory are garbled. > > > > I'm using a 2.4.26 kernel. Is there a way around this? > > The way around it is to specify the iocharset that matches the systems's > locale. I don't believe it is utf-8. You're right it isn't. I fixed it: I set iocharset=iso8859-1. Thanks. I had it set to UTF8 so as to not have problems when running slocate and going through the unicode files under /usr/share/doc/console-lib-tools, if they give problems I'll just delete them. As far as I can remember it worked well when I installed the previous version of the portuguese dictionary, and the iocharset option was already set to utf8. Could it be that now JFS enforces this option more strictly? Thanks, António, **** enjoy music, savour art, live life http://perusio.com **** |