From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Kleikamp Subject: Re: jfs, special characters Date: Sun, 27 Feb 2005 22:47:06 -0600 Message-ID: <1109566026.8448.19.camel@localhost> References: <20050226043439.GA16848@a5.repetae.net> <1109440714.8463.19.camel@localhost> <20050227230012.GA23340@a5.repetae.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: fsdevel Received: from e32.co.us.ibm.com ([32.97.110.130]:24560 "EHLO e32.co.us.ibm.com") by vger.kernel.org with ESMTP id S261554AbVB1ErK (ORCPT ); Sun, 27 Feb 2005 23:47:10 -0500 Received: from westrelay01.boulder.ibm.com (westrelay01.boulder.ibm.com [9.17.195.10]) by e32.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j1S4l95j238688 for ; Sun, 27 Feb 2005 23:47:09 -0500 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by westrelay01.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j1S4l9e3166448 for ; Sun, 27 Feb 2005 21:47:09 -0700 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j1S4l8M9026406 for ; Sun, 27 Feb 2005 21:47:09 -0700 To: frederik@ofb.net In-Reply-To: <20050227230012.GA23340@a5.repetae.net> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sun, 2005-02-27 at 15:00 -0800, Frederik Eaton wrote: > Thanks, you were right that I recently upgraded to 2.6 (actually I > transferred the hard drive between machines), and with a "mount /home= -o > remount,iocharset=3Dutf8" at least I can access the files now. But th= e > names aren't what they should be, for instance I see: >=20 > 04-The_Dark_Of_The_Matin=CE=98e.ogg >=20 > (that's a theta). Were they supposed to be correct?=20 Not necessarily. Even if the character returned is correct utf8, the terminal (xterm?) displaying the name may be assuming a different character set. It's also possible that on the older system, CONFIG_NLS_DEFAULT was not set to the same locale that the system used, so the character stored in the name was not the right unicode, but it was accessed consistently on the old system so it worked as long as nothing changed. > As an aside, now, I just tried "mount /home -o > remount,iocharset=3Diso8859-1", and got same problem This is no surprise. iso8859-1 has the same mapping as iocharset=3Dnon= e (the 2.6 default). (The "none" keyword is first supported in 2.6.11-rc4-mm1 and 2.4.30-pre2, so you probably won't be able to use it.) > ls: '/home/shared/frederik/Franz_Ferdinand/Franz_Ferdinand/04-The_Dar= k_Of_The_Matin?e.ogg': No such file or directory >=20 > But when I repeated the "mount /home -o remount,iocharset=3Dutf8" > command, the listing didn't show the name with a theta character, but > instead with two question marks: >=20 > 04-The_Dark_Of_The_Matin??e.ogg >=20 > Strange behavior. I.e., upon changing the mount options and then > changing them back I get a different listing. That I wouldn't expect. I really have no clue why it isn't consistent. The easiest way to "fix" these files (assuming there aren't too many) i= s to mount with iocharset=3Dutf8, rename the files using only ascii characters, remount again with iocharset=3Diso8859-1, and rename the fi= les to their proper names. After that you should be able to mount without any iocharset flag and get sane behavior. > Frederik --=20 David Kleikamp IBM Linux Technology Center - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html