Family Historian

Gedcom Publisher has been tested with Family Historian GEDCOM files and supports them quite well. Documentation for Family Historian's GEDCOM extensions and customizations is available online and that was a great help.


Family Historian user Mike Tate publishes a popular "Export Gedcom File" plug-in that provides customized GEDCOM exports from Family Historian. It's not required to use the plug-in to export a file for Gedcom Publisher, and Gedcom Publisher will read the main Family Historian data file (which is a GEDCOM file) or exports from Family Historian. However, Mike's export includes tag type (AKA "Fact") definitions that provide role and sentence information that is otherwise not available. If you want to use the default sentences for tags that are managed via Family Historian's Tools > Fact Types window, then you must export a GEDCOM file using Mike Tate's plug-in. The plug-in is free.

You can download the "Export Gedcom File" plug-in from the Family Historian plug-in store: Export Gedcom File

When using the "Export Gedcom File" plug-in:

  • Make sure you have version 3.1, or newer, of the plug-in.
  • On the Basic Options page:
    • Set the export mode to "(GST) GedSite".
    • Set the character encoding to "(UTF8) UTF-8 with a Byte Order Mark".
    • Set the multimedia conversion to "(FILE~ABS) Multimedia via Absolute Link Records".
  • On the Extra Options page:
    • Leave the options at the default values.
  • On the Other Options page:
    • Leave the options at the default values.

The GEDCOM file will be written under the following folder:

Documents\Family Historian Projects\project-folder\Public\Export

Be careful to choose the correct GEDCOM file. If you use a GEDCOM file that is not written by the plug-in, you'll lose the ability to use global sentences.

Witnesses and Roles

Gedcom Publisher supports Family Historian's witness and role GEDCOM extensions.

Sentence Templates

Gedcom Publisher's sentence processing engine is flexible and has been customized to support sentence templates as supplied by several different genealogy programs, including Family Historian. Read on for more details.

Gedcom Publisher includes support for local sentences from Family Historian GEDCOM files.

Gedcom Publisher includes support for global sentences from Family Historian GEDCOM files if the GEDCOM file is exported via the plug-in described above.

Gedcom Publisher supports Family Historian's "Template Codes". The Template Codes are mapped to Gedcom Publisher variables, with some differences in the exact definitions of the values.

Family Historian supports prefixes and suffixes for Template Codes using the same structure as a single-expression in Gedcom Publisher's conditional expression format:

< prefix {variable} suffix >

Family Historian users should typically not use the Add Note to Global Sentence option or the Add Note to Local Sentence option; use the "{note}" variable in the sentence to control whether the note is added or not.

Data References and Functions

Family Historian sentence templates may use "Functions" and "Data References". Gedcom Publisher does not support Family Historian functions. The following subset of Data References are supported.

FH Data Reference Description Gedcom Publisher Variable
{%CUR_PRIN%} Current principal or P1 [C]
Primary name of current principal or P1 [C]
{%CUR_PRIN.FAMC>HUSB>%} Current principal's father [C:FATHER]
{%CUR_PRIN.FAMC>WIFE>%} Current principal's mother [C:MOTHER]
{%CUR_PRIN.BIRT.DATE%} Current principal's birth date [C:PB:D]
{%CUR_PRIN.BIRT.DATE:YEAR%} Current principal's birth year [C:PB:D]
{%CUR_PRIN.DEAT.DATE%} Current principal's death date [C:PD:D]
{%CUR_PRIN.DEAT.DATE:YEAR%} Current principal's death year [C:PD:D]
{%CUR_PRIN2%} Other principal or P2 [CO]
Primary name of other principal or P2 [C]
{%CUR_PRIN2.FAMC>HUSB>%} Other principal's father [CO:FATHER]
{%CUR_PRIN2.FAMC>WIFE>%} Other principal's mother [CO:MOTHER]
{%CUR_PRIN2.BIRT.DATE%} Other principal's birth date [CO:PB:D]
{%CUR_PRIN2.BIRT.DATE:YEAR%} Other principal's birth year [CO:PB:D]
{%CUR_PRIN2.DEAT.DATE%} Other principal's death date [CO:PD:D]
{%CUR_PRIN2.DEAT.DATE:YEAR%} Other principal's death year [CO:PD:D]
{%CUR~WITN>%} Current witness [S]
{%CUR~WITN.NOTE2%} Current witness memo [WM]
{%CUR~WITN.ROLE%} Current witness role [S:RL]

The .NAME Data References support the FIRST, GIVEN, and FULL options.


Flag values in Family Historian GEDCOM files are imported into attribute values. You may display the attribute value(s) using the Person Entry Attribute item. You may also use attribute values to filter people using the Attribute Text filter term.

The Family Historian flag name is used as the attribute name. Family Historian flags do not have any value other than the name, but Gedcom Publisher attributes require a value, so Gedcom Publisher sets the value to "Y".

Media Item Keywords

Family Historian Media Items include a Keywords property. You may use the Keywords property to assign a keyword that modifies how Gedcom Publisher processes the exhibit. The available keywords are listed below. The keywords have the same effect as shown in the Exhibit Codes section of the Exhibits help page.

Gedcom Publisher supports the following keywords for Image Exhibits:


Gedcom Publisher does not float images, so it converts the following keywords to Exhibit-Embed:


For other exhibit types, Gedcom Publisher supports:


If an external file cannot be embedded in a book due to its file format, the exhibit is ignored regardless of any exhibit keywords.

Here is an example of adding an exhibit keyword in Family Historian:

screenshot of Edit Media Item window in Family Historian showing 'Exhibit-Embed-Right' keyword inside a red border
On This Page