From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3D21BF4E.9A3A6A39@gsyc.escet.urjc.es> From: FJ Ballesteros MIME-Version: 1.0 To: 9fans@cse.psu.edu Subject: Re: [9fans] blanks in file names References: <20020702110848.F30EA19992@mail.cse.psu.edu> <003d01c221bf$0dfd9d30$6501a8c0@xpire> <3D21AAC0.D307E3AB@strakt.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 2 Jul 2002 16:57:18 +0200 Topicbox-Message-UUID: bf905f46-eaca-11e9-9e20-41e7f4b1d025 > > Some characters were just not meant to be in filenames, which would avoid the > above. But they are, even in my system there're many files with blanks on their names (and I never choose such names). Since IFAIK none of the authors have anything against the proposal that came out of 9fans (see my previous post, where I tried to summarize it), what if I change the source just to do it? - let Alt-spc generate our unicode blank character - change the system to translate blanks in file names to the same character. - change the quote library so it does not quote that character. I don't have much time right know and that's why I ask before changing the code. I'm willing to implement it if there's agreement, so please, don't ignore the proposal just becase there's no code attached by now, just let me know.