Yes, Mike, it does only apply when used in websites, but for me good practice is good practice in all cases and starts at birth!!
When one first starts out with genealogy and Legacy, how does one know where it is going to lead? When I first started out I had no idea that my own website would by my main way of publishing my work. If I had used commas in file names I would have had to change every one and reconnect them individually to their appropriate Legacy Source/Event/whathaveyou. At that time, thank goodness I knew more about PC's then I did about genealogy. I am afraid that I will continue to draw attention to bad practice when I meet it, I do not regard it as a confusion, but rather in the same light as those who demand compliance with genealogy "standards", although somewhat more important. Ron Ferguson http://www.fergys.co.uk/ -----Original Message----- From: Mike Fry Sent: Tuesday, November 09, 2010 10:45 AM To: [email protected] Subject: Re: [LegacyUG] Digitized Files On 2010/11/09 03:30, Ron Ferguson wrote: > Initially let me comment on the file name which you give at the end of > your > post: '6100 Marriage Records, XYZ County, TN' is not an acceptable file > name > as it contains commas. Commas are only used to define a path and to > include > them in a file name can only cause confusion. Don't confuse people, Ron! Doesn't this restriction only apply to references within an HTML page? If you're not going to publish your data with images on a website, then there is no problem. -- Regards, Mike Fry Johannesburg Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
