I do a mixture of both. I keep as close to the original location name for the dated event but I also place a comment in the master location list (notes) on how it changed. I mindful of how the data will look if posted to websites via gedcom, when all the Legacy extras get dropped. By adding notes to the Master Location notes, it then underlines the Location dropdown arrow at the end of the location field in Family View - a reminder that there is extra information. Alan
-----Original Message----- From: Jerry [mailto:[email protected]] Sent: 29 October 2011 15:04 To: [email protected] Subject: RE: [LegacyUG] Showing historical locations. I wholeheartedly agree. Detroit was known by about five different names in its 300 year plus history. Seems extremely silly to use those five different names for the exact same spot on the map. Instead, I use the adjacent NOTE fields to explain needed historical names. Jerry Jennifer Crockett <[email protected]> wrote: >Tony, > >As person born in Queensland, Australia, I would say to just use Clermont, >Queensland, Australia. Much simpler than having two names for the same place. >Yes, Queensland was a colony before Federation in 1901, but only became one >after separation from New South Wales in 1859. > >Regards, > >Jennifer >http://colston-wenck.com > >-----Original Message----- >From: Tony Rolfe [mailto:[email protected]] >Sent: Saturday, 29 October 2011 4:50 PM >To: [email protected] >Subject: [LegacyUG] Showing historical locations. > > > >What about Clermont, Queensland, Australia vs Clermont, Queensland Colony? > >Is it worth having two location names for the same place to get >historical accuracy or is it better to simplify and forego history? > >As person born in Queensland, Australia, I would say to just use Clermont, >Queensland, Australia. > > > >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 > > 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 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
