From: "Joseph D. Wagner" <theman@josephdwagner.info>
To: "'Matthew Wilcox'" <willy@debian.org>
Cc: <linux-fsdevel@vger.kernel.org>
Subject: RE: RFC: Illegal Characters in File Names
Date: Mon, 19 Jul 2004 14:21:08 -0500 [thread overview]
Message-ID: <S265487AbUGSTVK/20040719192110Z+665@vger.kernel.org> (raw)
In-Reply-To: <20040719092628.GL4080@parcelfarce.linux.theplanet.co.uk>
> 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
next prev parent reply other threads:[~2004-07-19 19:21 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 0:41 RFC: Illegal Characters in File Names Joseph Wagner
2004-07-19 8:47 ` Jan Hudec
2004-07-19 19:21 ` Joseph D. Wagner
2004-07-19 20:08 ` Pat LaVarre
2004-07-19 20:54 ` Joseph D. Wagner
2004-07-20 6:33 ` Jan-Benedict Glaw
2004-07-20 16:25 ` Joseph D. Wagner
2004-07-20 20:42 ` Stephen Rothwell
[not found] ` <20040720162549.857014B7E7@dvmwest.gt.owl.de>
2004-07-20 16:52 ` Jan-Benedict Glaw
[not found] ` <20040719192145.50750578E5@jabberwock.ucw.cz>
2004-07-19 21:01 ` Jan Hudec
2004-07-20 16:40 ` Bryan Henderson
2004-07-20 16:54 ` Guy
2004-07-20 18:10 ` viro
2004-07-20 20:44 ` Guy
2004-07-20 21:27 ` Matthew Wilcox
2004-07-20 21:37 ` Jan Hudec
2004-07-20 21:40 ` Matthew Wilcox
2004-07-20 21:45 ` Jan Hudec
2004-07-20 21:49 ` Guy
2004-07-20 22:04 ` Jan Hudec
2004-07-20 22:11 ` Paul Stewart
2004-07-20 22:16 ` Joseph D. Wagner
2004-07-21 12:26 ` Jan-Benedict Glaw
2004-07-21 15:28 ` Guy
2004-07-21 16:25 ` Jan-Benedict Glaw
2004-07-21 12:24 ` Jan-Benedict Glaw
2004-07-20 21:41 ` Bryan Henderson
2004-07-21 12:21 ` Jan-Benedict Glaw
2004-07-21 15:25 ` Guy
2004-07-22 18:04 ` Matthew Wilcox
2004-07-22 18:35 ` Guy
2004-07-20 20:57 ` Jan Hudec
2004-07-20 21:09 ` Guy
2004-07-20 21:36 ` Jan Hudec
2004-07-20 22:13 ` viro
2004-07-20 22:44 ` Jan Hudec
2004-07-20 22:51 ` viro
2004-07-20 23:30 ` Guy
2004-07-21 20:25 ` Bryan Henderson
2004-07-22 3:17 ` John Newbigin
2004-07-22 3:24 ` Matthew Wilcox
2004-07-22 6:01 ` viro
2004-07-22 22:12 ` Bryan Henderson
2004-07-22 14:51 ` Jan-Benedict Glaw
2004-07-22 22:44 ` Bryan Henderson
2004-07-22 22:47 ` Jan Hudec
2004-07-23 18:10 ` Bryan Henderson
2004-07-20 23:52 ` John Newbigin
2004-07-21 3:26 ` Joseph D. Wagner
2004-07-21 4:15 ` viro
2004-07-21 5:03 ` Guy
2004-07-21 12:28 ` Jan-Benedict Glaw
2004-07-21 15:30 ` Guy
2004-07-21 16:26 ` Jan-Benedict Glaw
2004-07-21 16:33 ` Jan Hudec
2004-07-21 16:41 ` Guy
2004-07-21 17:01 ` Jan Hudec
2004-07-20 22:16 ` Joseph D. Wagner
2004-07-21 12:43 ` Jan-Benedict Glaw
2004-07-20 22:31 ` viro
2004-07-20 18:27 ` Bryan Henderson
2004-07-19 9:26 ` Matthew Wilcox
2004-07-19 19:21 ` Joseph D. Wagner [this message]
[not found] ` <E1BmdhG-0004NG-00@master.debian.org>
2004-07-20 2:43 ` Matthew Wilcox
2004-07-20 3:16 ` Joseph D. Wagner
2004-07-20 8:45 ` Jan Hudec
2004-07-20 16:25 ` Joseph D. Wagner
2004-07-20 16:41 ` Guy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=S265487AbUGSTVK/20040719192110Z+665@vger.kernel.org \
--to=theman@josephdwagner.info \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).