All your your suggestions except the first which uses spaces are perfectly
valid. This is absolutely nothing to do with either Legacy or Microsoft but
variable standards (?) used throughout the industry. As I said previously
the problem only really arises if one starts to create websites. As
Susan wrote:
I've also heard there might be issues with capital letters. But that
is probably more about internet files. Like David suggested, I
wouldn't use underscores, but maybe you could use dashes instead.
Where I work, I have a Windoze XP Pro workstation.
In the lab we use all kinds of
Kay:
You are on the right path.
The issue with spaces in file names is the web hosting server.
If the web server Unix box, then Unix does not recognize files with
blanks in the file names.
If the web server is a Windows server, it is OK with blanks in the file names.
I would highly recommend
On 11 Jun 2006 Kay Keating wrote:
I'm now in the process of renaming files where I used spaces and
dashes:
C://Program Files/Legacy/images/census/
Keating_1900_James_LA.jpg
Keating_1910_James_LA.jpg
Keating_1920_James_GA.jpg
Keating_1930_James_MD.jpg
Kay,
I've also heard there might be issues with capital letters. But that
is probably more about internet files. Like David suggested, I
wouldn't use underscores, but maybe you could use dashes instead.
My naming convention suggestion would be to start a file with last
name, then the first name,
To: LegacyUserGroup@mail.millenniacorp.com
Subject: Re: [LegacyUG] Naming source files
Date: Sun, 11 Jun 2006 15:29:06 -0500
Kay,
I've also heard there might be issues with capital letters. But that
is probably more about internet files. Like David suggested, I
wouldn't use underscores, but maybe you could use