Date: Thu, 6 Feb 2003 00:51:07 -0500 From: parv <parv_fm@emailgroups.net> To: Bill Moran <wmoran@potentialtech.com> Cc: Walter <walterk1@earthlink.net>, Questions <freebsd-questions@FreeBSD.org> Subject: Re: handling non-printable characters in file names Message-ID: <20030206055107.GA317@moo.holy.cow> In-Reply-To: <3E41BD21.9020508@potentialtech.com> References: <3E41A24E.9090607@earthlink.net> <15937.47061.743702.496178@guru.mired.org> <3E41BD21.9020508@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
in message <3E41BD21.9020508@potentialtech.com>,
wrote Bill Moran thusly...
>
> Mike Meyer wrote:
> >In <3E41A24E.9090607@earthlink.net>, Walter <walterk1@earthlink.net> typed:
> >
> >>There's probably someone who can explain why non-
> >>printable characters are useful in file names, but
> >>I'd really rather disallow them altogether - if
> >>there's a build option or control flag to set.
> >>Anyone?
> >
> >BSD is character-set neutral. Well, it tries. The only two characters
> >that are magic in file names are 0x2f and 0x00, because they both
> >terminate the file name. Other than that, you are free to use whatever
> >character encoding you want to.
...
> What about a feature that allows an administrator to list characters
> that are disallowed in filenames and directory names?
Hey, i personally would love it, but that would cause lot of
troubles, for instance, when saving e-mail attachments or file
generation via slrn MIME decode.
in the meantime check this out (a shameless plug)...
perl program...
http://www103.pair.com/parv/comp/src/perl/sanename.perl
documentation...
http://www103.pair.com/parv/comp/src/perl/sanename.perl.pod
- parv
--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030206055107.GA317>