From Gramps
Jump to: navigation, search

GEDCOM stands for Genealogical Data Communications and is a file format specification developed by the Family and Church History Department of The Church of Jesus Christ of Latter-day Saints. It allows different genealogical software programs to share data with each other.

GEDCOM References

GEDCOM Testing

Converting ANSEL to Unicode and back

  • Gramps exports and imports ANSEL GEDCOM, but not all codes are supported. Test the output on the character ? which is used if a character is not understood
  • Perl MARC::Charset module: Available on cpan, and well supported . Can convert MARC8 to Unicode and back. As ANSEL is a subset of MARC8 (consisting of the (extended) latin characters) it will convert all ANSEL GEDCOMS to Unicode. (:arrow:) More info, and a script that can convert: see the attachment to bug 831.
  • marc4j - Java implementation of a convertor, also MARC8 to Unicode. Unclear if it converts correctly combined unicode characters.

ANSEL/MARC References

Unofficial ANSEL to Unicode conversion lists

These cover the original ANSEL spec, now preseded by MARC8.

See also

Current open Feature request for Gramps
  • 6023 Export Family Historian GEDCOM Extensions
  • 688 Support for Gedcom 5.5EL (or Gedcom-L the more recent standard)
  • 9249 GEDCOM import improvements to support, FTM 2012/2014 and FTM for MAC 3
  • GEDCOM 7 support

Collections of GEDCOM extension tags used in different programs

Others projects

  • GEDCOM ( is a project for parsing objects ignored by a model. It includes classes and attributes for every GEDCOM tag sequence appearing in more than 4% of the 7000 GEDCOMs submitted to over the past five years, with the exception of four software-specific schema tags: SCHEMA, _EVENT_DEFN, _PLAC_DEFN, and _EVDEF, generated by Family Tree Maker, Personal Ancestral File, Legacy, and RootsMagic respectively.
  • Dallan Quass GitHub GEDCOM repository incudes the demo. GEDCOM -> model -> json -> model -> GEDCOM round-trip shows the GEDCOM tags that are represented in the model as extensions, and tags that cannot be represented.
  • Specification differences between the object model and the GEDCOM 5.5 Specification.
  • set of UML diagrams illustrating the core GEDCOM class and each of the top-level objects.