![]() ![]() if the is 5.5, but the actual GEDCOM version is 5.5.1, issue a non-fatal error.None of the previous rules matched? Assume it is 5.5 as stated.if the header contains a ._WWW record, it must be GEDCOM 5.5.if the header contains a ._FAX record, it must be GEDCOM 5.5.if the header contains a ._EMAIL record, it must be GEDCOM 5.5.Check for user-defined tags being used instead of GEDCOM 5.5.1 tags.See the table below for more products and version numbers.if the version number is 5.0 or more, it is GEDCOM 5.5.1.if the version number is less than 5.0, it is GEDCOM 5.5.Perform the known product / version number checks.if you managed extract it, issue a non-fatal error and continue with that version number.if you failed to extract it, issue a fatal error and abort.try to extract the version number (see section on Family Tree Maker below).If the ( HEAD.VERS line value isn't a proper version number.If the ( HEAD.VERS line value is missing, issue a fatal error and abort.if you managed to identify it, issue a non-fatal error and continue with that system identifier.if you failed to identify it, issue a fatal error and abort.try to identify the correct system identifier by other means (see section on MacFamilyTree below).If the ( HEAD.SOUR line value is missing (illegal!).if the system identifier is too long (it is for The Next Generation of Genealogy Sitebuilding), issue a non-fatal error and continue.Make sure you have a system identifier.if the header contains a record, it is GEDCOM 5.5.1.if the header contains a 3 record, it is GEDCOM 5.5.1.Check for tags introduced in GEDCOM 5.5.1.if the character encoding is UTF-8, it is GEDCOM 5.5.1.If there is a match, it's definitely GEDCOM 5.5, and not GEDCOM 5.5.1. (Optional): check the system identifier ( HEAD.SOUR line value)Īgainst a list of system identifiers for products discontinued before (or some time after) the introduction of GEDCOM 5.5.1:.if the value is 5.5, it may be either GEDCOM 5.5 or GEDCOM 5.5.1.if the value is 5.5.1, it is GEDCOM 5.5.1.Numbered step should be performed in the order shown.Īs soon as a rule matches and the actual GEDCOM version is known, no further tests should be performed. This is a the algorithm for distinguishing between GEDCOM 5.5 and GEDCOM 5.5.1. However, a GEDCOM reader should be able to determine the actual GEDCOM version without looking beyond the GEDCOM header. ![]() if the GEDCOM files contains a PLAC.MAP record, it is GEDCOM 5.5.1.if the GEDCOM files contains a OBJE.BLOB record, it is GEDCOM 5.5.It is possible to distinguish between GEDCOM 5.5 and GEDCOM 5.5.1 files based on their content, for example with the following rules: GEDCOM 5.5 versus GEDCOM 5.5.1 file content It does not matter whether or when the developers fixed their product to starting labelling their GEDCOM 5.5.1 files correctly. Some products appear in both list because some versions of the product get it wrong, while later versions get it right.įor the detection algorithm presented here, all that matters is when products started using GEDCOM 5.5.1 yet continued to label their GEDCOM files (incorrectly) as GEDCOM 5.5. Some products that correctly identify their use of GEDCOM 5.5.1 include The Next Generation of Genealogy Sitebuilding (TNG), Other products that use GEDCOM 5.5.1 but lie that they are using GEDCOM 5.5 include In fact, nowadays, most GEDCOM files that claim to be GEDCOM 5.5 files are probably GEDCOM 5.5.1 files.įamilySearch PAF is the best known application to lie about the GEDCOM version used, but not the only one. With a value of 5.5 instead of the correct 5.5.1. GEDCOM 5.5.1 version detection is complicated by the fact that several applications produce GEDCOM 5.5.1 files GEDCOM 5.5.1 Version Detection GEDCOM 5.5.x files are not always what they say they are complication ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |