[thelist] file names

[Means, Eric D]

>  -----Original Message-----
> From: 	Adam [mailto:adam at hallinteractive.com]
> Sent:	Wednesday, June 05, 2002 9:04 AM
> To:	thelist at lists.evolt.org
> Subject:	[thelist] file names
>
> Hey all
> Here's another quick one. I was taught that using file names like
> "Steve-#1.jpg" could cause problems with certain OS's/programs. This was
> '97-'98.
> I am however seeing an increasing number of recent grads using file names
> like this (this one just came to me: Steve-#1.jpg)

The only illegal filename character on MacOS (pre-OSX), AFAIK, is the colon.
In OSX (by extension from Unix-like OSes) I believe that a filename may
include any character as long as they are properly escaped.

Under Windows, filenames cannot include the following characters: ? [ ] / \
= + < > : ; " ,
Also, NT Server doesn't like filenames that end with either a dot or a
space.

Finally, Windows doesn't like files that are named the same as the various
PC ports, including com1 thru com9, lpt1 thru lpt9, con, nul, and prn (not
exhaustive).

# is not an illegal file name character in any widely-used OS to the best of
my knowledge.