![]() That way you can see the data and correct it. GEDitCOM imported the ALIA tag the way it should be, as an Associated Record on the person window, which is good to preserve the data. The closest the GEDCOM standard has to “Also Known As” is the Nickname field, whose tag is NICK, or the Name Type tag, which is rarely used. The ALIA tag should be used to provide a cross-reference to another person who may be the same. + FTM’s invalid use of the ALIA tag: Older versions of Family Tree Maker (FTM) and a few other apps incorrectly use the ALIA tag in GEDCOMs for the “Also Known As” field. It would also be nice if the report listed problems by GEDCOM line number to make it easier to find them. It’s clear from the report that GEDitCOM expects GEDCOMs to be in version 5.5 format, but more about this under Cons. + GEDCOM import log: All good genealogy apps should produce a GEDOM import error log, and GEDitCOM produces one called a GEDCOM Validation Report. I suggest you highlight, copy, and paste the text into a text editor and save it for reference, although you can access it again from the main screen if needed. One tip I have to offer is to save your file periodically because it does not save automatically. ![]() Importing a GEDCOM file into GEDitCOM is straightforward, since it is a GEDCOM editor, but instructions are on their website and in the Help menu if you need help. References to the GEDCOM standard are to version 5.5.1 unless stated otherwise. Portions of text in all capital letters that are not acronyms are GEDCOM tags, with the rest of the plain text field name in lowercase. The trial has a time limit of 15 days but is otherwise fully funtional. Version tested: GEDitCOM II 2.1 trial version. ![]() GenSoftReviews: 5 stars out of 5 (4 ratings) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |