From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Joseph D. Wagner" Subject: RE: RFC: Illegal Characters in File Names Date: Mon, 19 Jul 2004 14:21:08 -0500 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: References: <20040719092628.GL4080@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8BIT Cc: Return-path: Received: from ssa8.serverconfig.com ([209.51.129.179]:18918 "EHLO ssa8.serverconfig.com") by vger.kernel.org with ESMTP id S265487AbUGSTVK convert rfc822-to-8bit (ORCPT ); Mon, 19 Jul 2004 15:21:10 -0400 To: "'Matthew Wilcox'" In-Reply-To: <20040719092628.GL4080@parcelfarce.linux.theplanet.co.uk> List-Id: linux-fsdevel.vger.kernel.org > Where are "we" considering this? I didn't see any > discussion on ext2-devel. OK, "we" are mostly me. > Possibly it would be of interest to include a utf8 > converter in e2fsck like the -s option... [trimmed] That would be too much work. One thing at a time... Baby steps... You have to crawl before you can walk... ... and all that jazz. > I do see the utility of checking for non-printing > characters as they're normally only inserted by > accident. But this could be done by a cronjob (like > locatedb) rather than putting more functionality > into e2fsck. I'm not just talking about checking for non-printing characters; I'm talking about making those non-printing characters illegal. According to ISO 8859, the lower 128 characters are all the same. It's the upper 128 characters that differ with iso-8859-1, iso-8859-2, etc. Hence, the proposed change should be OK regardless of the encoding mechanism. Joseph D. Wagner