![]() PAF complained that ASCXX is an unknown character set. In the version number is 5.5.88, the form is LINEAGE-LINKED and character set is ASCXX To make sure PAF is really doing it right, I created an erroneous version of the same file, FamilySearch PAF 5.2.18 accepts the file without any error or warning.I tried a few applications to see how they faired. The results should be an empty database (with your default submitter). Let me stress that last bit: that file is perfectly legal GEDCOM.Ī genealogy application that supports GEDCOM 5.5.1 should read that file without any error or warning. The result is a slightly larger but still perfect legal GEDCOM file. ![]() The GEDCOM form ( and the character encoding ( HEAD.CHAR) over multiple GEDCOM lines. The second example uses CONC records to split the GEDCOM version ( ), The smallest GEDCOM 5.5.5 file, the same file but with eight CONC records, and the minimal GEDCOM 5.5.5 file. There are three GEDCOM examples in this text This article uses it to show a problem with CONC, and by extension, with CONT as well. Test a new genealogy application, or proof that you can fit a GEDCOM file into a tweet. It is a simple GEDCOM file you can use to explain the basics of the GEDCOM format, The smallest GEDCOM 5.5.1 is just ten lines long. Minimal GEDCOM 5.5.5 File Minimal GEDCOM 5.5.1 File
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |