From: Frederik Eaton Subject: Re: jfs, special characters Date: Sun, 27 Feb 2005 21:42:22 -0800 Message-ID: <20050228054222.GA2445@a5.repetae.net> References: <20050226043439.GA16848@a5.repetae.net> <1109440714.8463.19.camel@localhost> <20050227230012.GA23340@a5.repetae.net> <1109566026.8448.19.camel@localhost> Reply-To: frederik@ofb.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: fsdevel Received: from h34-aclarke.sv.meer.net ([205.217.153.34]:62124 "EHLO ofb3.ofb.net") by vger.kernel.org with ESMTP id S261564AbVB1Fmq (ORCPT ); Mon, 28 Feb 2005 00:42:46 -0500 To: Dave Kleikamp Content-Disposition: inline In-Reply-To: <1109566026.8448.19.camel@localhost> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org > The easiest way to "fix" these files (assuming there aren't too many) is > to mount with iocharset=utf8, rename the files using only ascii > characters, remount again with iocharset=iso8859-1, and rename the files > to their proper names. After that you should be able to mount without > any iocharset flag and get sane behavior. OK, thanks. Frederik