RE: file naming length conventions

I personally like long file names but I dislike the use of spaces in the
names.
Usually a space is a token separator between program elements. CR and
LF and Tab are also separators.
None of these are allowed in file names.

I do not know while long names give you a problem in html. I do not
have problems with long names.

-----Original Message-----
From: aklug-bounce@aklug.org [mailto:aklug-bounce@aklug.org] On Behalf
Of Jim Dory
Sent: Wednesday, June 09, 2004 10:38 AM
To: AKLUG
Subject: file naming length conventions

I just did some googling trying to find a good argument for restricting=20
the length of user filenames. MS Word allows you to save a document with

a name using the complete first sentence of the doc and some users are=20
doing that. Ugh!

I haven't really found a good webpage resource yet that puts anything in

layman terms, or even a necessarily good reason to avoid long names now.

I sense that it is not good, but I don't really know how to put it in=20
words. Figured some sysadmin types out there might have some compelling=20
arguments or thoughts. One problem I have thought of is using wildcards=20
to sort or otherwise process files becomes broken rather quickly with=20
these huge names, but the users in many cases are putting unique=20
identifiers at the start of the name (such as a resolution number or=20
date) so wildcards could work in that case.

Another problem is if I ever have to put these on the webpage- having=20
filenames with spaces and just the messiness of the html code with huge=20
names seems wrong.. but not sure how to make that argument to users.

Any good resources or suggestions out there to look at?

appreciate any help, thanks, Jim
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.

---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Wed Jun 9 11:42:08 2004