In the article about switching from Family Tree Maker that I referenced above, Synium states, “Unfortunately the developers of Family Tree Maker made the very poor choice of not importing media files but just linking them. Furthermore, it is entirely possible that media files could be in more than one folder, but MFT expects them all to be in the same folder, which is nonsense. It should only be necessary if the path is invalid or the media are missing from the specified path. This was unnecessary because the full path was specified in the GEDCOM. While importing a GEDCOM, MFT prompted me to select the location of my media files (Fig 1). But see the Cons sections for problems with addresses. + All events can include an Address, Agency, and Cause as allowed by the GEDCOM standard. + Allows associated persons to be included, but they are limited to godparents, birth witnesses, death witnesses, and marriage witnesses (but see below for problems with the latter). + For source citations, it is possible to copy and paste them, similar to the way one can in Family Tree Maker (FTM). It’s also possible to edit citations from this list. + For sources, lists all citations for each source and the events they’re linked to. + Exported GEDCOM file is labelled as version 5.5.1, which is the latest version. + Imported Family Tree Maker’s invalid ALIA tag as an Other Name, which is then exported correctly back to GEDCOM. However, MFT8 does not import a valid ALIA tag correctly it simply imports the pointer (cross-reference), e.g., “I008.” There doesn’t seem to be a proper ALIA field in MFT. + Found no unreadable data entries in my GEDCOM, which is also a good thing since there weren’t any. This is a good thing a genealogy app should always produce a GEDCOM import log listing any data that could not be imported. + Upon importing a GEDCOM, a “GEDCOM Import Warnings” log is produced listing not parseable tags and unreadable data entries. However, see the Cons section for my take on the “Attention: Media file import” section. Importing a GEDCOM file into MFT is straightforward, but MacFamilyTree has an article, “Switch from Family Tree Maker to MacFamilyTree and import your family tree,” on their website. References to the GEDCOM standard are to version 5.5.1. 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. Versions tested: MFT 7.6.2 and MFT 8.0 (thanks to Synium Software for the redeem codes). I don’t feel that I can keep asking Synimum Software for free codes, and even if they provided me one, it seems it would be a waste of my time and effort to review version 10, since they told me in 2016 that version 8 would correct the GEDCOM problems but it did not, and now the problems are even worse in version 10! Just choose the paper size from the provided list of presets.īecause it will reduce PDF size at the cost of some quality, we do not recommend making smaller files that are meant to be used for large format printing.Read Peter’s comment below for full details.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |