neroaround.blogg.se

Ifamily for mac review
Ifamily for mac review












ifamily for mac review

iFamily expects GEDCOMs to be formatted according to GEDCOM 5.5 for import, so it undoubtedly exports them as 5.5. The iFamily website states, “As GEDCOM export is disabled in our demo, hold it’s performance to the same standard as our GEDCOM import process.” Fortunately, iFamily uses GEDCOM tags for its Event Types, so I could at least surmise what tags it would use to export a GEDCOM. GEDCOM 5.5.1:As noted above, the iFamily Demo does not include GEDCOM export. This shortcoming also leads to the next problem. That’s probably why it imported my invalid event description into the Event Name field. But here’s the problem: iFamily doesn’t have a separate event description field it has only the Event Name field, so if there’s both a description and a name (which is really a type), it can import only one or the other. On its website, iFamily gives even worse advice on the Tutorials page under Tips it states, “Enter ‘Y’ for a birthdate or deathdate if you want it to be searchable during consistency checks.” If a date is unknown, you should not enter “Y” in the date field (or the place field) you should enter it in the event description. Fortunately, iFamily doesn’t squawk if you leave the date blank. If a date is unknown, it must be left blank (unless it can be estimated). Also notice in Fig 2 the statement, “An event must have a Date, a Type and a Name.” I agree an event must have a type, but a Name is required only for user-defined events like Arrival or Departure, and I strongly disagree that an event must have a date. The Event Name is the Event Type spelled out, such as “Birth” or “Death.” But where it should say “Birth,” it imported the invalid description instead, and there’s no way to change it. iFamily also violated this rule it imported invalid event descriptions into the Event Name (Fig 2). Many genealogy apps violate this rule, including Family Tree Maker (FTM), which enabled me to include it in my test GEDCOM file. Invalid event description: The only entry that a birth, death, or marriage event description (called a “descriptor” in the standard) may have is the letter “Y” to assert that the event occurred if and only if both the date and place are blank. Obviously with the release of new operating systems, it made sense to change to name to a much better, and much more appropriate name, considering it now works with OSX systems beyond Leopard. In fact it is simply a renamed one, having periously been known as iFamily for Tiger and iFamily for Leopard.

Ifamily for mac review software#

This is the genealogy application that Mac users have been waiting for! Whereas other genealogy software tends to emphasize the family unit, this software's focus is on each individual person. IFamily for Mac is a richly featured Genealogy application with a healthy community of users. If you want good options, try Ifamily (feature packed, good interface), MacFamilyTree (slick, excellent for the basics) or Reunion (most features, overall best, but kinda crummy interface and feel).

ifamily for mac review

This Mac version appears to be little more than just a means to generate income for the company that sells it.














Ifamily for mac review