![]() Note: Once the files were converted to non-Unicode ASCII formats, both Mac Family Tree Maker applications worked. This was an attempt to use both the original Family Tree Maker 2010 for Mac (Left) and Family Tree Maker for Mac 2 (Right) to import a Unicode UTF-8 GEDCOM file. It’s an interesting mystery because supports GEDCOM 5.5.1, and many Windows genealogy applications do as well. This could be due to FTM for Windows not supporting GEDCOM 5.5.1 (draft) standards, choosing to only support GEDCOM 5.5. FTM 2012 does support UTF-8 GEDCOM exports, but it’s not handled well. Tamura Jones covered this in his Family Tree Maker 2012 Fan Value article, discussing the issues with Family Tree Maker not supporting UTF-8 or Unicode. Unicode/UTF-8 support problems exist with the Windows version of Family Tree Maker. They also have a large development and support team and a large global presence (remember the bit about Asian and Eastern European characters/names possibly requiring Unicode support?) As I mentioned in the original post, this is not just a problem with the Mac versions of Family Tree Maker. I am going to bring up Family Tree Maker 2010 for Mac and Family Tree Maker for Mac 2 first, since they are the only two that don’t support Unicode/UTF-8. Note: I did not post screenshots or in-depth information on all Mac genealogy apps – some didn’t have a need for it because they worked fine or there were issues preventing the GEDCOM test files from being imported.įamily Tree Maker 2010 for Mac and Family Tree Maker for Mac 2 Most of us will never run into this issue, but for those who do, it’s nice to know you’re not alone, and it’s nice to know that Unicode support is very robust on the OS X platform. I took a look at all of the major Mac genealogy software, as well as provided a few solutions to dealing with the problem at the Unicode, UTF-8, GEDCOM 5.5.1, GEDCOMs and Macs article. I explain further in the FAQ – Unicode, UTF-8, GEDCOM Files, and Macs article about converting GEDCOM files for use in these applications.īreakdown of individual Mac genealogy applications and their Unicode/UTF-8 support Note: Both Family Tree Makers for Mac, and PAW2U could handle the GEDCOM files once the Unicode characters had been stripped. ![]() * Heredis X.2 10.2.6 – PowerPC only (Note: There is a new Heredis for Mac in development, to take full advantage of Mac OS X Lion, and that might support Unicode). * Osk 4.7.1 seems to have support – you can select it in the dialogue, but it was having a problem with loading in general. Unfortunately MyBlood was last updated in August of 2010. MyBlood may even have the largest list of supported character sets. If you click on the image to the right, it will take you to a larger version hosted at flickr that will show you just how many character sets MyBlood is supposed to support. Whether this has to do with it being in demo mode or not, I’m not sure. 3.1 clearly has support for many character sets including UTF, but it would not advance past the open dialogue. * PAW2U version 100 (see further in the article for an explanation) Unicode Not Fully Supported, UTF-8 Supported This maybe due in part to Gramps and GenealogyJ being developed on or for Unix-like systems such as Linux and Mac OS X. Gramps didn’t put up any notices about problems – either it was robust enough to handle them, or it wasn’t and was ignoring them. GenealogyJ was able to handle some odd things, while ignoring others. Notes: Gramps and MacFamilyTree seemed to handle the odd stuff better than the other applications. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |