Tim Forsyth has released a major update to Gigatrees, Gigatrees 5.4.8. If you’re not familiar with it, it’s a free Windows family tree website generator that generates HTML-based websites (or local SQLite3 databases) from your genealogy software’s GEDCOM files (GEDCOM 5.x to GEDCOM 7.0+). You can see it in action on Gigatrees.com (link).
This update has many changes that will specifically affect/help those who use Family Historian, Ancestry.com, and Legacy Family Tree.
Gigatrees supports an embedded blog within the website, which most such programs that generate family tree websites do not.
Gigatrees has extensive support for hundreds of third-party GEDCOM tags, and you can see a list of the more commonly used export applications below:
Gigatrees – Supported Exporting Applications
You can download it here: Downloads – Gigatrees
Quick Start Guide: Quick Start Guide – Gigatrees
Gigatrees 5.4.8 – November 7, 2024 (Extensive Release Notes here) |
Improved handling of the Ancestry’s SOUR@.PAGE field which if you did not know, embeds source metadata in Name/Value (NV) pairs. NV Pairs are delimited using colons and semicolons (e.g. Name: Value; Another Name: Another Value). |
Added support for Ancestry’s SOUR@.DATA.TEXT field which embeds source citation metadata, also in NV pairs |
Added support for including source citation metadata in both the @SOUR.TEXT and @SOUR.NOTE fields by embedded NV pairs within square brackets ([]). The left square bracket MUST be the 1st character in the text field, otherwise it will be treated as regular text. (please see the release notes on Gigatrees.com for details) |
Modified the <Sources> option by replacing most of the predefined suboptions with the ability to configure source metadata using NV pairs. This allows you to define ANY metadata necessary to populate your configured <SourceTemplates>. |
Modified the default source templates and fixed handling of configured <SourceTemplates>. |
Modified the way source and source reference metadata is displayed on source pages and in source reference link tooltips. |
Added support for @INDI._FSID. If you have the ability to add your own GEDCOM tags (Family Historian), you can use this tag to add family search ids to individuals. If your do not have the ability to add your own tags, you can use the <GedcomRecords> using the <AddRecordField> option to add this tag to ANY Individual Record. |
Added (some) international character support for sorting Individual Names so they will appear in the Index and Name pages such that ‘ß’ will appear under ‘S’ and ‘Å’ will appear under it’s equivalent Latin character, ‘A’. |
Added support for some app specific GEDCOM tags and GEDCOM 7 |