Re: Making a string, file-safe (file-encode??)
- From: Tim Smith <reply_in_group@xxxxxxxxxxxxxxxx>
- Date: Wed, 18 Jun 2008 08:27:23 -0700
In article <48580cd6$0$12749$7836cce5@xxxxxxxxxxxxx>,
Daniel Pitts <newsgroup.spamfilter@xxxxxxxxxxxxxxxxxxx> wrote:
? is not invalid on all system, linux handles it perfectly. The
characters that are invalid are system specific, and some systems don't
have limitations at all.
Offhand, I can't recall any system that doesn't have some limitations on
characters that can be used in filenames. What systems are you thinking
of?
In particular, every system I recall that supports directories and
allows access of files by a full path name prohibits the use of the path
separator in filenames.
--
--Tim Smith
.
- References:
- Making a string, file-safe (file-encode??)
- From: adamorn
- Re: Making a string, file-safe (file-encode??)
- From: Daniel Pitts
- Making a string, file-safe (file-encode??)
- Prev by Date: Re: how does an application server works?
- Next by Date: Re: Doing one last thing to a WeakReference
- Previous by thread: Re: Making a string, file-safe (file-encode??)
- Next by thread: Re: Making a string, file-safe (file-encode??)
- Index(es):
Relevant Pages
|
