ABBR is exported by default in a GEDCOM intended for opening by *Legacy* software. Older versions of non-Legacy genealogy programs sometimes require Standard or Basic GEDCOM because there are unknown details in the default GEDCOM.
ABBR is not exported in a _Standard GED 5.5_ from Legacy 5. 0 _PLAC_DEFN Any GEDCOM tag with _ like _PLAC_DEFN is custom data entry and likely to be ignored by non-Legacy programs used to import the file. "Line 35 : Tag: _PLAC_DEFN, unknown custom tag, line ignored." Simple wall charts are limited to one birth, one death and a few other individual/marriage events. Advanced wall charts allow multiples of births, baptisms with alternate (conflicting) dates/locations and multiple sources for each event date or variation in location. A "tidy" master location list with every event in the same city, county, state, country would result in a very large box chart compared to the amount of useful information. If the goal is to use a GEDCOM to a non-Legacy product for a web site or a wall chart, the location must be entered in Legacy 5 for the destination purpose. If the Legacy location has excess commas for missing town & county, those commas will show after the standard GEDCOM transfer. -- Elizabeth ----- Original Message ----- From: "Rob Weiss" > GEDCOMS have two text fields for locations. One for the full location > (PLAC) and an abbreviated name (ABBR) for each location. Each is just a > copy of the respective field you see in the Add/Edit Location dialogue > box, commas and all. So Locations should transfer just fine, provided the > programs at either end don't get too smart in trying to decipher which > bits of the text string are which! 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
