![]() I may be able check these claims and also media transfer with a trial version of MacFamilyTree (Desktop version) direct from Synium, but the MobileFamilyTree App can only be purchased through the iTunes AppStore, so no trial version is available. Improved and configureable character encoding detection Better handling of custom GEDCOM tags from other genealogy apps Much improved compatibility with other apps Synium Software claim that Version 8 of both MacFamilyTree and MobileFamilyTree provide: YKS Northowram (Heywood URC Heywood Close).jpg was changed to 0ACE8CDF-C124-4DA7-A561-7C936C935F6E-664-00000067BCDB0BB8.jpg with no option for a return to the original filename on export. One thing from personal knowledge is that media files and links to media files were not readily transferable to/from MacFamilyTree to other programs in MFT Version 7, as the software converted all imported media file names to it's own internal naming structure which seems impossible for mere mortals to interpret, e.g. ilytree-7/ although the focus is on the potential implications of moving data between FamilyTreeMaker and MacFamilyTree. ![]() There is some commentary on MacFamilyTree 7 (and therefore also MobileFamilyTree 7) GEDCOM import and export here. MacFamilyTree 8 and MobileFamilyTree 8 have just been released so I am not sure yet sure what detailed changes have been made from the previous Version 7, but both the Mac Desktop Software and the MobileFamilyTree software (available on iOS devices only) appear to employ exactly the same SQLite database structure. ![]() One feature that is unique to FH is its Face/Detail Frames for Media, and that most definitely will not survive a round trip from FH to MobileFamilyTree (or any other product) and back to FH via GEDCOM. However, it still makes migrating databases to and from products fraught with pitfalls unless you can find a common subset they both support.įor some background examples see the glossary:gedcom_extension_list|> GEDCOM Extension List for FH dialect, and see the plugins:help:export_gedcom_file:output_formats|> Export Gedcom File Plugin > Output Formats for other product dialects. It is quite common for different genealogy products to use different dialects of GEDCOM that sometimes use valid formats and sometimes not. There appears to be no free trial to experiment with, and what I can glean from a Google search is that it may use GEDCOM 5.5.1 Draft format, which has a few significant differences to the GEDCOM 5.5 Standard Release used by FH.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |