Family Tree Maker 16.0.350 imports FAN1.GED through FAN13.GED just fine, and
tells you so by showing a messagebox that tells you there were no errors or warning.
When you try try to import FAN14.GED, it displays another message: There were 472 warning(s) and error(s) generated during import.
.
When you check out the FAN14.LST file that Family Tree Maker generated,
you'll note that it contains the same message over and over again: Tag: NAME, name too long, truncated to
.
Family Tree Maker Classic has a rather small maximum name lengths.
The maximum name length that Family Tree Maker will import seems to be just forty characters.
Because of that, its fan value is less than 14.
Whether Family Tree Maker's fan value is 13 or not depends on the quality of its GEDCOM export.
To export a GEDCOM file from Family Tree Maker 16, you need to pay attention.
Family Tree Maker may export to FTW TEXT instead of to GEDCOM, it may export to GEDCOM 4 instead of GEDCOM 5.5, and it encourages the use of several illegal characters encodings.
You need to pay attention to avoid all that, but if you make the right choices in the Export to GEDCOM
dialog box, Family Tree Maker will export an ANSEL-encoded FTW GEDCOM 5.5 file.
The FTW GEDCOM dialect contains various proprietary extensions.
The _SCHEMA, _MREL and _FREL tags,
and the _FA1 through _FA13 tags all start
with an underscore so these are legal GEDCOM extensions.
However, the LABL tag is a GEDCOM 5.3 tag.
It is neither a GEDCOM 5.5 tag, nor a legal extension.
The HEAD.SUBM tag should have a reference to the SUBM record as its value,
but the mandatory SUBM record is absent, and
and the HEAD.SUBM tag contains the illegal value Unknown instead.
To top it off, the HEAD.SOUR.VERS value is too long.
Family Tree Maker 16 does not export valid GEDCOM files, the files it produces do not even start with a valid GEDCOM header, therefore its fan value is zero.
Copyright © Tamura Jones. All Rights reserved.