The approach I've adopted is to use the Full Location to define the name fomally and completely. For non-US locations I've had to devise my own standard and stick to it. This means that there are often excess intermediate commas, as it is essential to unambiguously identify the different parts of each location name.
I then use the Short Location Name to define the name less formally in a way that looks good in reports and charts. So far I've only used this in Legacy. The short location name is exported by Gedcoms but whether other programs use it correctly, I don't know. Legacy also doesn't use it everywhere. Until they do there is a tradeoff to be made between lexical correctness and readability in reports etc. Rob On Sat, 26 Feb 2005 19:49:43 -0700, E.Rodier <[EMAIL PROTECTED]> wrote: > Excess commas may show up in a GEDCOM to another program for wall charts. > Some Canadian provinces need the county name to find a source and other > provinces have no counties. Other locations changed names over time. Geo > database doesn't help. > > ----- Original Message ----- > From: "Rob Weiss" > If you enter "London,,England" Geo correctly interpets London as a County > and doesn't find it either. This applies to any town in England that I have > tried - it's nothing to do with London. > > 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 > 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
