I suspect this is because FTB expects multimedia records to be in GEDCOM 5.5 format, which was different from 5.5.1. Multimedia: Failed to import media titles, dates, and notes. However, it exported the field correctly. Failed to import a residence field, even though it imported part of the address and date attached to it. ![]() Failed to display reference numbers (tag REFN) on relationships, although it exported them. Imported the field label “ Ancestral File Number” but failed to import the field contents (the description). Imported the words “ Height” and “ Weight” from EVEN.TYPE structures into the Description field, but failed to import the accompanying descriptions. For example, it imported EVEN.TYPE Namesake as “Named after” and “Employment” as “Occupation.” Apps must import the TYPE tag verbatim. Failed to import the exact text from the TYPE tag on some EVENt structures. However, all the LDS ordinance fields were exported to GEDCOM. This is a serious omission for members of the LDS Church. ![]() Failed to display LDS ordinance fields, even though all of them use standard GEDCOM tags except for Initiatory. Failed to parse the valid GEDCOM 5.5.1 tag FACT. Failed to display an ADDRess tag, even though it imported the other elements of the address structure, including the city, state, and postal code. However, none of the references even existed in my GEDCOM file so they were neither defined nor referenced.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |