Family Historian User Group

I love Markdown, and I wish more software supported it. It is so much easier to write and transport simple documents rather than using rtf.

Those better versed in Evidence Explained may have a better explanation but I suspect EE is not written with the GEDCOM specification in mind. The FH7 legacy is rooted in the GEDCOM specification in which Repository records share common source details and has only started using EE style templates r...

I am running FH7 on Windows 11 using Parallels, so the Mac-like shortcuts are not always available. FH7 has the capability to directly enter diacritics (without alt kludges) and so the support application AS should likely consider making this available as well. In French genealogy, diacritics are s...

So a RESIdence TYPE could be 'Temporary' or 'Rented', etc. However, the TYPE description field is only accessed via the FH 'All' tab and is not well supported elsewhere. FHUG Knowledge Base Recording a Civil Partnership gives an example of the Type Descriptor to classify a MARRiage event as a Civil...

I had not!


I worked, thanks

I imported a GEDCOM from my primary database. I then copied all of the images from that DB to the Media folder of the FH project. Some of the media was found and associated correctly with the Media_Record, but other images was "not found". Yet I can manually connect the image to the Media_Record rig...

ADC65,

I deal in the wild with a lot of GEDCOM files that include full path, including drive letter, so these are things i see and “fix” in my long experience with GEDCOM!

So nothing specifically needs to be "fixed". Websites simply need to be capable of unpacking ZIP files. Fixing would only need to be done if the file path includes things like program specific directories or if files are saved with long and deep paths that could be shorted to better use the structu...

I don't understand the point of displaying Media after uploading GEDCOM to website software because (except for TNG) websites such as Ancestry, FindMyPast, ZoomPast, etc, do not automatically upload Media linked to GEDCOM at all. Because, today media is not part of the GEDCOM specification (blobs w...

But the vast majority of the land, i.e. of the farms, in that area were part of the same estate belonging to Crewe Hall. That’s one of the big differences UK vs Norway, very little in the way of “Estate”, most farms in Fjord Country were small, we did not really have a small ruling class of propert...

Adrian, I’m not in tune with all cultural aspects in the modern world, particularly in Asia and the Middle East, as it relates to identity. However, I do know that Historically various cultures in Europe, Asia and Indigenous groups, location was a very important aspect of identifying a specific indi...

Elevator, I agree. Since much of my family started their lives on the farm, their identity (not to confused with name) also includes farm name. This is not any different than so many other culture if you go back in time where the city of origin was part of their identity (Leonardo de Vinci comes to ...

Ron,

I’m very familiar with the digital archive, at one time I volunteered at a Norwegian Genealogy Center.

Ah, thanks. No Welsh ancestors in my line (that I know of), but I did consider how to handle my Swedish patronymic names. Should I put patronyms and geonyms in the “/surname/” field of FH7? Yes, I have decided to treat them as surnames. This conforms to the given name-surname binary established in ...

I see that v5.5.1 example, that example and suggestion has been removed in v7 of GEDCOM.

Based on discussion, The inclusion of "//" may in the future indicate "Unknown" and the lack of a "//" would mean no surname!

Many of my relatives had no surname. They used a patronymic naming convention where they did not have a surname. In GEDCOM there is a difference between: 1 NAME Caroline Oldsdatter // {unknown surname} vs 1 NAME Caroline Oldsdatter {no surname} It looks like to me that when I import a GEDCOM, 1 NAME...

Thanks, I had not seen that!

Can a book design be copied from one project to another?

I’m not on the Steering Committee, only a commenter at large. The NOTE change prevented inconsistency issue in the document and definitely a bug to be fixed. The EXID without a TYPE was illogical and also a bug to be fixed. What you you want me to say? Bugs need to be fixed where they can with minim...

Does a change in the cardinality of a tag from {0:1} to {0:M} or from {0:1} to {1:1} constitute a change in structure? If this was a “Normalized” database structure I would say that cardinality should not change in a patch. I don’t recall all of the cases that cardinality change, but the one I do r...

To clarify the release info in a GEDCOM. Only 2 VERS 7.0 is required but VERS 7.0.1 is permitted. The structure of GEDCOM v7 will not change for patches 7.0.1 thru 7.0.xx, any changes produced in a patch will be more resigned to clarifications of definitions for a tag, adding enumerated values to a ...

I agree that the changes are minor between .10 and .12, but my goal was to note that v7 has evolved from the initial release to include multiple enum changes, some definitions of what goes in a tag and other documentary changes. Also note that we are working on v7.1 changes as well and looking to fu...

I agree with Mark1834 regarding the uniqueness (or lack there of) for two independent instances of a specific individual and later merged into the same instance in a third program.

I would place little value in the number and should play little importance in identifying same person.

The .12 version has been verified and registered in GitHub.

I’ve ask for clarification, but I think .12 should used!

The HTML page is at .12 while the PDF is at .10