Doc types aside, whether you are using HTML, XML or the various versions of XHTML, you may still use image file names with uppercase, or mixed case, so long as those file names are enclosed in quotation marks. If any of those web languages could not accept entries enclosed in quotation marks that included uppercase letters, then they would not be able to display simple text sentences, which they obviously can do.
One further note. Legacy has no problem creating a web page using image file names that contain underscores, hyphens or ampersands, nor does it balk at using image file names that contain some, or all uppercase letters. When Legacy creates a web page ALL image file names (as well as folder names) are converted to lower case and stored in the location of your choosing. No further manipulation of those file names is conducted by Legacy. It does not strip away any underscore, hyphen or ampersand symbols from those file names, nor is it unable to display image files whose file names contain any of those symbols. Image files for Legacy-created web pages are kept in a Pictures folder location that can be designated by the user at the time the web page code is generated. Since I choose to use some uppercase letters in my image file names I would designate a separate Pictures folder location for web file images. As the image files I use for Legacy are contained in the following folder structure: C:\Legacy7\Pictures And since there are three subfolders (Docs, Groups and Places) under that main Pictures folder, I would take care that I directed Legacy to place image files for any web page it created in another place. For example: C:\Legacy7\web\zimmerman_web_page\webpictures That way my original picture files would retain their uppercase characteristics. The additional image files created by Legacy for use with the web page take up very little disk space as Legacy reduces the size of the originals for use on the web. Those file sizes are determined by the size you choose for the displayed images in the web page. As an example, an image file that was 42KB and 238x258 pixels in my Legacy Pictures folder was reduced to only 5KB and 161x231 pixels when converted for use on a web page where I chose to display images in Medium size. The entire array of 218 images for that web page took up 1.13MB of disk space in the web page webpictures folder. I notice that one alteration was made to six image file names. Each of them were of Schmidt family members and the file names were converted to lowercase and preceded by the letter "b" followed by an underscore. I have been unable to determine how those six image files differed in any way from the remaining 212 image files. Out of curiosity I altered an image file in the webpictures folder to all uppercase letters. I also altered the HTML code associated with displaying that image file so that the filename it contained was also all uppercase letters. The result was that the image was displayed without incident. I am aware that many Legacy users are not fond of the web pages created by Legacy, but for those of you who choose to use Legacy to create a web page there is no need to alter your image files to make them all lowercase, or to remove underscores, hyphens or ampersands. John Zimmerman Mesa, AZ On 10/15/2012 9:30 AM, R G Strong-genes wrote: > Ron, > It depends on the doc type for the website and whether you wish the site to > be compliant to that doc type. For example if the website is just HTML > coding the ampersand has no problems, however some of the newer types are to > be XHTML compliant and are encoded with PHP coding both of which do have > problems with the ampersand and other characters that should be spelled out > with their code. Also with XHTML everything should be in lowercase. > Russ > > -----Original Message----- > From: Robert Austen > Sent: Sunday, October 14, 2012 9:19 PM > To: [email protected] > Subject: RE: [LegacyUG] What to do with genealogical files after death of > compi ler > > Hi Ron, > > Thanks for this. John also showed everything connected with underscores. I > appreciate the comment regarding creating a website. Time to go back and > fill in the spaces. John also recommended only the hyphen, underscore and > 'ampersand'. I am very inexperienced in HTML coding but I thought I had > heard of problems with the ampersand, particularly in a url unless it's > written as '&'. I suppose the phot file name could show up in a url. > > Your thoughts? > > Bob > > > > -----Original Message----- > From: Ron Ferguson [mailto:[email protected]] > Sent: Sunday, October 14, 2012 5:16 PM > To: [email protected] > Subject: RE: [LegacyUG] What to do with genealogical files after death of > compi ler > > Bob, > > Just a quick piece of advice for those who may at some time consider > creating a website - do not have spaces in your file names, use an > underscore or hyphen instead, otherwise they may well not work. > > In fact it is best only to use alpha-numeric characters in addition to the > above two. > Ron Ferguson > http://www.fergys.co.uk/ > GOONS #5307 > 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 Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
