Sebastian, As you are probably aware, but I will mention it anyhow!
Just because Legacy gives a box a name does not mean that you you have to use it that way. For example, if one regularly uses the mapping function then it is probably best to use the modern name in the Long Name - I don't, I enter the name at the time of the Event. The Short Name field could contain the historical name instead of the abbreviations (which are only understood by locals) if the modern name is used in the Long Name, I would like to see Legacy develop alternative uses of these functions, and perhaps add others, such as Long Name, Short Name, Mapping Name and Historic Name, but these may not work with other software eg. those for web pages. This is not just a Legacy problem, but rather because there is a general lack of recognition of the international nature of genealogy. Ron Ferguson http://www.fergys.co.uk/ -----Original Message----- From: Sebastian Masch Sent: Wednesday, December 04, 2013 8:10 AM To: [email protected] Subject: Re: [LegacyUG] Geobase international location questions John B. Lisle schrieb am 03.12.2013 20:25: > Pam, > > Please indulge me to talk about Location in > Legacy 8. Actually, little has changed since > Legacy 7 but many users do not have a strategy > for locations and mapping and such. > > --> Sometimes, neither works. This is when I go > to Wikipedia or Google to have one of them try to > show me where the place is. Then "transfer" those > coordinates to Legacy. I will make a lot of use > of the Bing satellite views to try to place the > pin at the most favorable location. > > Once I have the location resolved, I will then > create a new location with the historical name, > prefixed by the current name. When editing the > name, I check the box that says do not automatically geocode. > > Then I go to the present day location, showing > the pin where the place is, then move to > historical named place and right click the pin to > the same place. Then edit the location to remove > the prefix new name which I only added so the two > places were next to each other in the place list. > > This may sound confusing, but once you have done > it once or twice it becomes easy. And you can > figure out shortcuts to the process. > > I have done 1000s of locations using these techniques. So where are two places in your database when where is actually only one? Perhaps Legacy should not include only long and short names for a place, but also historical and romanized names - simply prepare Legacy for international use. For example Volgograd: it's actually ÒþûóþóрðÌÂô, it's historical name is æðрøÌÂцыý​, the romanized name is Volgograd. Perhaps alternative names could be used too, like for individuals, then the names Tsaritsyn and Stalingrad could be added. It would be beautiful to have the possibility to not just choose short location names in reports but also choose historical and add some alternative names in brackets. Sebastian 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
