Elizabeth, so you're saying that you would like to see this comma removal too, right (plus some other fixes)? I do think it's great that the database allows the user to separate place names with commas. I do not mind seeing the leading commas on the screen when part of the location is unknown or not applicable. However, on reports and on web pages, the extra leading commas look awkward and confusing to the reader. I assume I don't know anything about TreeDraw, so I can't comment there.
You mentioned that some locations have counties and some don't have them. You also mentioned the need to address changing county names. Here's what I do. My index sort string (for a USA town) shows: Country, state, county, township - town, (later became county Y). In my location field on the screen it shows, "Township - town, county X, state, country, (later became county Y)." This still doesn't read extremely well in reports, but at least it alerts the reader that there was a county boundary change at some point. Then I create an event to state exactly what part of place X became place Y and when the change occurred. I usually do this all free-form within an event called "boundary change." I use this if the person didn't move, but a new county/locality was formed. I also use this if the place was X when the person was living there (or when the event occurred), but where a present day person would find it in place Y. This isn't always easy to determine, but where I have information, I like to document it. My research is mostly in the United States, but I guess this could apply to other countries as well. Sorry this is long, but mainly I would like to see the comma removal fix so my web page will read well. Thanks for your comments. Gail Rich Nestor E.Rodier wrote: "Web pages and family history reports saved as HTML for CD-Recordables do not read well with excess commas. Leading commas were reported by a user of Legacy Companion charts. Are they also in TreeDraw charts? Some Canadian provinces have counties and some do not. Many research locations changed names over time so I do not use the Geo location database. All locations are entered for printing and usually avoid repeat of city, county, province, country for every event. GEDCOM transfer includes leading commas and sometimes Y in the death location field from the use of "Living? No" selection without a death date or location. Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
