Revision History

Click on any of the following titles to view changes.

  • Fixed crash when multimedia references were used in families missing spouses.
  • Improved birth year estimates and data alerts.
  • Restyled footnote numbers.
  • Fixed HTTPS hotlinking.
  • Fixed children with estimated birthdates not being sorted by age. (Gigatrees only)
  • Fixed Monarch dates with offsets of 1 showing full date range instead of only first date. (Gigatrees only)
  • Fixed source page sorting. (Gigatrees only)
  • Fixed source link lists showing only last source reference (Ouch!). Apparently I broke this recently. (Gigatrees only)
  • Removed Security options to remove unused records or unused source records. The _HIDE option can be used to pick and choose which records to hide from the output. (Gigatrees only)
  • Fixed the [Not Applicable] text not being stripped from the output. (Gigatrees only)
  • Fixed a crash reported from field.
  • Added support for Media Gallery and Source Citations.
  • Added support for Related Posts in your blog.
  • Added support for embedding references in blog content and other text areas like notes and sources. References can be embedded for Sources, Blog Posts, Media Images, People and simple text footnotes.
  • Modified the Blog Posts option to remove the blog folder name, category, author and tag prefixes and lists suffix and change the Featured Image to accept Media Ids rather than define them explictly.
  • Modified the Featured images option to accept Media Ids rather than define them explictly.
  • Modified Sources and Source References to show full citations throughout.
  • Added a flag to copy assets files (defaulted to true) to the Plugins option.
  • Added a Server Database Path to the Database option.
  • Fixed a crash occuring when an embedded URL's Internet protocol scheme began at position 6 or 7 of a line.
  • The Database and Blog Posts options are out of beta and are now available to all users.
  • Moved standalone blogging from Gigatrees to Innuendo.
  • Initial Release on Innuendo.
  • Removed named plugins as part of the installation.
  • Fix dates when missing years i.e. 3 NOV.
  • Minor changes having to do with beta availability.
  • Added a new option, "Blog Posts", makes adding posts to your integrated or standalone blog a snap. You no longer need to fiddle with the more complex "Insert Records" and "Append Records" options to add blog posts. The "Blog Posts" option displays an index of your post titles where you can add, remove or edit a post. The post edit page includes all the options/fields that apply to the blog post on a single page. There are only two options that are required when adding a blog post, the record ID and the post title. The filename slug, abstract and featured image will be automatically determined if they are left blank. There is a new "Remove extra line breaks" option on the post edit page that will remove extra line breaks from that post only if the global option is not enabled.
  • If records were added with the Insert Records option, then the CLI does not require that an Input File is specified.
  • Fixed a crash occurring in GEDCOM validator happening in unlikely test case.
  • Added a "-h" command line option for "gigatrees-cli.exe" to display command line syntax help.
  • Updated date handling to fix B.C. dates and include additional formats.
  • Added a sample configuration file that users can run to test out how Gigatrees works and looks.
  • Fixed a crash that was occuring when source references containing multimedia links were attached to individuals.
  • The Option >> Modify Config menu now disables any options not available to the selected report type.
  • Fixed a bug in the blog module that showed up when mixing blog posts and untitled note records in the same GEDCOM file.
  • Moved the Clean Line Breaks option from the Miscellaneous section to the Blog section, although it continues to apply to all text fields including notes. It most likely to be used, however, for Blogs where embedded HTML is more likely to occur.
  • Added two sample blog posts to the default configuration. Users should delete these before deployment. The first post was created by scratch using the Insert Records and Append Records options. The second post commandeers an existing NOTE record of the sample GEDCOM file and uses the Append Records option to add a _TITL tag (making it a blog post) and an _ABST tag to provide the abstract.
  • Gigatrees now has a Windows GUI, making it much easier to configure and use the application.
  • The locations of the default language translation files and coordinates database have been moved to an "includes" subdirectory.
  • Removed the ability to change page menu, file and folder names (except blog). Menu names can still be translated using the translation feature.
  • Fixed a crash that was occuring when source references containing multimedia references were attached to individuals.
  • Gigatrees has always generated its build report in verbose mode, however the vast number of informative messages can be intimidating to new users, so a new Verbose option has been added and forced to be disabled by default.
  • Blog feeds are also no longer enabled by default.
  • Plugins names were not being trimmed of whitespace.
  • The Prefix field has been removed from Pages option. Folders and Files can no longer be set to blank, which effectivley eliminates a flat file structure.
  • For many users, myself included, the thousands of static files and pages that are created during a typical build is less than desirebale. Gigatrees can now be configured to use a SQLite3 database to serve PHP web pages dynamically. This reduces the number of files created during the build process to four (five if feeds are enabled). A new PHPDatabase field has been added to the Extension option. PHPDatabase can be used to set the full or relative file path to your database file.
  • Minor bug fixes
  • Added default batch files for building a Gigatree (Gigatree.bat), and GEDCOM Validation Report (VGedX.bat) and a Data Validation Reports (Bonkers.bat). All three files load the default configuration file, set the import fiel to TGC551.ged, a test GEDCOM file available at (http://www.geditcom.com/gedcom.html), set the output folder to 'temp' and generate a log file (log.txt). This should make it easier for users to get started.
  • Added a Registration id for users based on their installation. Users do not need to register, however those who do will have early access to new features and access to some more advanced features that are not required for general use. Here's the crux though, the only way to register is to make a donation through the website to provide support for future development. It's all one big circle. If you do decide to make a donation, be sure to provide your registration id if you want to also be registered. You can find your registration id at the top of any build report or log file. The registration id is specific to the hardware on your computer, so if you move to another computer, you'll need to register that one as well. If you do not want to make a donation, please enjoy to many freely available features. Currently the only feature that is restricted to registered users are the Ethnicity estimates, however more features are in the pipe.
  • Fixed missing kinship list pages
  • Fixed timeline index
  • Added new PluginsPath and AssetsPath field s to the Required option allowing users to specify where to look for these when building.
  • Added a new SourceType option that lets users associate their source types with source categories.
  • Added a new Maintenance option with SendAnonymousStats and SendErrorReports fields. Both are enabled by default and are included in the default configuration file. These options are being restored from version 4.1.3. When enabled, the application makes calls to the Gigatrees server. All calls are encrypted, and no personal identifiable information is sent. These options are used to gather crash dumps, and information on processing and external service errors so that these can be more easily detected and fixed. Aggregated GEDCOM tag counts and performance statistics are used to help improve application coverage and for determinging where speed and memory optimization can be most beneficial.
  • Added embedded data alerts strings.
  • Added support for new user defined GEDCOM tags to support adding parental associations to individual logical records via the configuration file. (_MREL_SOUR, _MREL_CERT, _FREL_SOUR, _FREL_CERT)
  • Removed the UserStrings options. Users can use the Translation option to provide alternate strings
  • Removed the Display field from the EventTypes option. EventTypes are no longer internally translated, so users should specify these as they appear in their GEDCOM file. If these need to be translated, the ReplaceText option can be used to provide alternate display text for GEDCOM data.
  • Fixed the certainty assessments shown in all ancestor, generation, descendant and kinship lists. The certainty assessment shown in these lists indicates the level of certainty between the root person or descendant and the ancestor shown. i.e. the certainty with the least precendence is shown.
  • Fixed the Disqus file link path as it was missnig the extension, which could cause backlinking problems in HTML builds.
  • Fixed a bug with the location lookup service that under the wrong circumstances would save valid locations as partials or as invalid, preventing them for being readback later and recovered. Unfortunately this means that existing the gigatrees.sqlite databases might have incorrect entires. Users should consider scrapping their existing database and instead using the clean database provided as part of the installation. This will means that all coordinates will need to be refreshed. It is probably a good practice to occasionally removed partials and nodata from the database s that they can be refreshed.
  • There are new default display strings in the translation files (lang.txt and en.txt)
  • Default configuration file no longer defaults to a report type of "Gigatrees". Also, the HideLiving and Privatize security options are no longer set.
  • There are new default display strings in the translation files (lang.txt and en.txt)
  • Removed the UserString.ClaimDisproved. A GEDCOM tag SOUR@.QUAY value of 0 will now be used for marking claims as disproven. The associated certainty assessment associated will be "unreliable". The _CERT extension can still be used to set the certainty assessment to "disproven". Internally they are treated the same with the exception of the display string.
  • Renamed Analysis page to DataAlerts, and the default page folder to "alerts"
  • Data Alerts now validate all birth, baptism, marriage, death and burial events rather then just the primary ones. This may lead to an increase in the number of alerts found. Events with impossible or questionable certainty assessments continue to be ignored.
  • Added a new Ethnicity estimates tab to individual profile pages. The are new configuration options to enable ethnicity estimates, and to restrict displaying them to living persons only.
  • Added new Origin Maps Pages
  • Added Disqus configuration options for DisqusBlogEnabled, DisqusSourceEnabled, DisqusProfileEnabled
  • Updated source categories (@SOUR._QUAL) including allowing the use of the more common @SOUR._TYPE and @SOUR.TYPE tags. New hardcoded source types will now be included in the certainty assessment calculations, but only when no source categories or source reference quality exists.
  • Added numerical source indicies
  • Added source categories to source index page
  • Source index page is now sortable by title/index, source id and source category
  • Created a permanent home for Gigatrees at http://gigatrees.appspot.com. Restored the webpage about dialog to reflect the new URL.
  • Fixed a bug that prevented blog author, tag and category pages from being created.
  • Briefly, feed support has been added to the blog functions, anonymous statistics are no longer being gathered, the download page has been moved to a shared folder on the cloud and the manual is now included in the download archive.
  • I fixed a crash caused when files began with a blank line.
  • I moved the heatmap icons from the Gigatrees assets folder to the Gigatrees heatmaps plugin folder where they belong. I also modified the plugin configuration file to define and load the heatmap icon paths in Header so that they are in place for the application to use.
  • I added a missing colon after Nickname/Alias.
  • Menus :
  • The home button now goes to root instead of domain when the index page is disabled.
  • I added an ExtendMenu option so users can add their own menu items.
  • Blogging :
  • I fixed the blog indexes and item lists for authors, categories and tags to include missing posts.
  • I added a MinTagSize option so users can configure the minimum size to recognize for blog hash tags.
  • I improved cleaning line breaks for tables.
  • The primary change to this release (4.1.1 build 802) is the conversion of the default Header and Footer into plugins. They now make use of the plugin mechanism added in the previous release. In addition, all of the necessary and optional scripts used by Gigatrees have been removed from the default Header and Footer and moved into their own plugins, making use of the DropHeader and DropFooter options to insert themselves into the Header and Footer plugins. This will allow users to easily replace and update plugins to their latest versions. The default configuration file gigatrees.xml now includes at the bottom of the file the default list of plugins the should be loaded. The installation includes all of the default plugins, as well as alternate versions of those that can be loaded from content delivery networks. The Metadata.UseCDNs configuration option is no longer necessary and was removed.
  • One of the new default plugins jquery.rt.responsive.tables adds responsive table support to Gigatrees making the tablular data more easily read on mobile devices. Tables with headnigs that can be reformatted are now transposed on mobile devices when they become too compacted. Also, Bootstrap's table-responsive class has been added for tables that cannot be reformatted, making tables them horizontally scrollale on mobile devices less than 768 pixels across. I also made formatting changes to a number of pages and broke out the colors into a separate stylesheet to allow for easy color theme changes.
  • Two new command line parameters have been added, -b to set the report type to "Blog" from the command line, and -p plugin to include new plugins on the command line.
  • Lastly, the last change broke to path to favicon.ico, so it has been repaired.

  • The latest version of Gigatrees includes numerous blogging changes, including some that allow it to be used as a standalone blogging utility. A new Gigatrees Blog has been added using it in this manner. Lets start with a couple of bug fixes:
  • Extended ASCII characters between 128 and 159 were not being converted into HTML entities properly, so they were not appearing on web pages.
  • Hash tags in article pages at the beginning of lines were not being detected properly.
  • When creating pretty URLs, the period (.) was not being converted to a dash (-) as it should have.
  • Gigatrees now supports index lists on the article/blog pages for articles, authors, categories and tags. It allows several new methods for sorting articles, and allows setting generic featured images that can be used when none are defined for an article. In more detail:
  • The default sorting method of blog articles is reverse publication date. A Blog.ModifySort option has been added that allows sorting blog articles by reversed modified date. The GEDCOM record field NOTE@.CHAN.DATE is the standard method for determing the date an article as last modified. When extending records using the AppendRecordField option, there is no way to define that GEDCOM record field. To get around this, Gigatrees has added support for a user defined level 1 record field, _MOD that can be used to set a modification date. Example:
     
    <AppendRecordField>  
      <RecordId> N1               </RecordId>  
      <Tag>      _MOD             </Tag>  
      <Value>    January 12, 2001 </Value>
    </AppendRecordField>
  • A Blog.IdSort option has also been added that allows sorting blog articles by reverse record id. Records are usually created with incrementing record ids, so using id sort order generally is the same as the default publication date order. However, if using id sort order, you can manually control the display order by modifying the record ids directly. You can for instance set a record id larger than all the others to make it sticky.
  • Two new options, Blog.FeaturedImage and Blog.FeaturedCredit have been added that allows users to preconfigure a set of generic featured images that will be drawn from when an article without a defined image is encountered. Generic images will be pulled from randomly so that different images will be grabbed on each build. The Blog.FeaturedImage option should precede the Blog.FeaturedCredit option and HTML elements must replace "<" and ">' with double brackets. Example:
     
    <Blog>   
      <FeaturedImage>  https://c5.staticflickr.com/1/28/96998932_9bd3f09786_b.jpg   </FeaturedImage>   
      <FeaturedCredit> 
        Photo courtesy of [[a href="https://www.flickr.com/photos/clearlyambiguous/" target="_blank"]]Scott Robinson[[/a]]
      </FeaturedCredit>  
    </Blog>
  • Publication and modified dates are shown in long format by default (i.e. January 12, 2001). Enabling the Blog.ShortDates option will instead display them in short date format (i.e. Jan 12, 2001).
  • Index lists for articles, authors, categories and tags are now automatically created. Each is listed and linked along the bottom of the main articles/blog pages beneath the pagination area. By default, the articles list uses the Page.Articles.File as the filename prefix and "list" as the suffix (i.e. index-list). Author, category and tags index lists use "author", "category" and "tag" as their prefixes and "list" as their suffixes as well. Users can modify these prefixes by setting Blog.AuthorFilenamePrefix, Blog.CategoryFilenamePrefix, and Blog.TagFilenamePrefix, and change their suffix by setting Blog.ListFilenameSuffix. New styles associated with these lists have been added to the default stylesheet (gigatrees.css). New default display strings have also been added to the bottom of the translation files.
  • Users can also prepend their article category to the article title when automatically creating filename slugs by setting the Blog.PrependCategoryToTitle option (i.e. category-title-of-article). When set, the category will also be prepended to the title in the page heading. (i.e. Category: Title of Article)
  • Gigatrees treats all carriage returns (or newlines) found in article text, as well as anywhere else in GEDCOM data as HTML break characters. This is also true for GEDCOM continuation record fields (CONT). This allows files missing continuation tags to be processed correctly. It also allows for logical records inserted during configuration using the InsertRecord option to not require continuation tags to be present. This can result in unexpected line breaks in articles caused when embedding HTML tags within GEDCOM data, because many such tags, such as header, page, and blockquotes have implied line breaks built into their opening and close elements. To minimize these unexpected breaks, users generally need to butt their HTML tags up against one another rather than putting them on separate lines. Gigatrees has a new Misc.CleanLineBreaks option that will convert multiple breaks to single breaks, and remove extra breaks around some of the more common HTML opening and closing tags. When this option is enabled, users can still force extra breaks by adding the HTML non-breaking space characacter entity (&nbsp;) to a blank line. Also when not using GEDCOM continuation tags, lines cannot begin with a "1", because they may be treated as a level 1 subfield of the record and then discarded because the line's arbitrary tag will not be supported. In those rare cases, the "1" should be preceded by a non-breaking space characacter entity as well. Using the Misc.CleanLineBreaks option allows large complex articles embedding HTML to add extra blank lines between HTML sections for improved readability. New styles associated with HTML elements such as paragraphs, blockquotes, preformatted text and images have been added to the default stylesheet (gigatrees.css).
  • Gigatrees used to load its required scripts and stylesheets from content delivery networks (CDNs) for increased speed. This is ideal when hosting a Gigatree online, however many users view their trees offline or may have a need to access their tree on airplanes and other places where they do not have an internet connection. Because of this, Gigatrees now distributes the required files as part of its installation and loads them from the assets folder by default. Users hosting their trees online can still choose to load these files from CDNs by setting the Metadata.UseCDNs option. Google fonts are loaded from their CDN regardless, but fallback to HTML fonts when no internet connection is found.
  • Additionally, Gigatrees used to allow moving the various assets files to alternate folders by configuring WebPaths for scripts, styles and images and then defining substitution macros to represent these paths relatively. This has become to cumbersome to manage, so is no longer supported automatically. Users can still do this functionally by replacing the default Header and Footer using absolute URLs for their assets. Gigatrees now copies the entire assets folder to the Required.OutputPath as it before by default, but now always. There is also a new substitution macro: %AssetsPath%.
  • The last big change for this release is the addition of true, albeit limited, plugin capability. Two plugins are included in the installation, "BasicFancyBox" and "BasicTooltipHandler". Both can be found in the new plugins folder. Both are also loaded in the default configuration file (gigatrees.xml) using the new Plugin option (see below). The BasicFancyBox plugin is used to display photos and images in a popup photo box. When not installed, displaying of photos reverts to the browser's native functions. The BasicTooltipHandler plugin provides formatted Bootstrap 3 tooltips and popovers and is used by many of the Gigatrees pages. When not installed, displaying of tooltips and popovers reverts to the browser's native functions for displaying HTML element titles. For this and other reasons, the default Metadata.Header and Metadata.Footer have changed which files are loaded and from where.
  • The new Plugin option allows users to add non-standard functionality to their Gigatrees and blogs. Plugins can use the Metadata.DropHeader, Metadata.DropFooter options to add scripts and style sheets to the Gigatrees Headers and Footers. The %PluginsPath% substitution macro should be used to access files located in the plugins folder by a relative path. Plugin support allows for using a wide variety of prexisting JQuery scripts to add things like photo galleries, video support, etc. Plugins are required to be located in the Required.OuputPath plugins folder after install. When building a Gigatree, the install folder's plugin folder is copied to the Required.OutputPath. The name must be the same as the name used in the Plugin option and must have a plugin.xml file that will be loaded when buiding a Gigatree. Users when writing their own plugins should provide a ReadMe.txt file that describes installation, setup, and usage. A new Plugins blog will be added that will provide descriptions and download links for new plugins as I develop them. Users can submit new plugins if they want them included in the blog for others to use.
  • Added a new report type: Blog - to make blogging easier.
  • Fixed a bug causing Gigatrees to crash on shutdown - after pages had been generated.
  • Added ReadMe.txt file to the distribution to cover the basics in install and setup.
  • Fixed a bug with auto-hotlinking embedded external URLs.
  • Fixed a bug with the menu when MenuBar.LinkIndex was disabled.
  • Fixed a bug in auto-translating 3-letter GEDCOM tags.
  • Fixed location index sorting.
  • Fixed spellings of referrer.
  • Fixed footer margin.
  • Restyled Articles and Article index as a Blog.
  • Added support to Articles for _ABST, _FEAT, _PIC, _SUBM and _CAT tags.
  • RemoveAllUnusedRecords now defaults to false so that unreferenced Articles are not automatically stripped.
  • Add support for article index pages for Authors, Categories and Tags. Tags must be at lest 6 characters including the leading pound sign (#). Tags are replaced in article text with links to their index pages.
  • Added Pagination support for the Article index pages.
  • Removed support for %PageTitle% and %PageURL% macros from the Footer.
  • Added support for %PreHeader%, %DropBody% and %LangCode% macros to the Header.
  • Added support the HTML <html> "lang" value and <meta http-equiv="Content-Language" value to the Header. By default they are both substituted with the %LangCode% macro.
  • Added Metadata.DropHeader and Metadata.DropFooter options. These can be used to drop in HTML elements at the end of the HTML header or at the end of the HTML footer without having to specify a new Header or Footer. It is an easy way to add loading new style sheets and javascript file.
  • Removed FancyBox support from the default Header and Footer. FancyBox should now be added as a plugin using the new Metadata.DropHeader and Meatadata.DropFooter options.
  • Removed the Tab Extensions from the default Footer. The Tab Extensions can now be added as a plugin using the new Metadata.DropHeader or Meatadata.DropFooter options.
  • Floating MenuBar placement is now determined by the %MenuBar% substitution macro location in the Header. The default Header places the %MenuBar% above the site title. Previously it was place below.
  • Individuals having children from multiple unions, now list their children associated with those unions rather than grouping them all together after listing the marriages.
  • When an individual has multiple spouses, their family notes now show the name of the spouse as well.
  • Ancestor Lists now show the number of generations when AncestorLists.Angus is enabled.
  • Ancestor List migration paths have been cleaned up and in some cases shortened.
  • Ancestor, Descendant and Kinship Lists now show the certainty assessment associated with the parent listed.
  • Some parental associations (PEDI, _FREL, _MREL) missing sources now set their certainty assessment to uncertain.
  • The Coordinates.EnableService option is now disabled by default and has been added to the default configuration file so that it can be easily enabled.
  • The Coordinates.Database option can now be specified and used even if the Coordinates.EnableService option is disabled. This is only useful if the Coordinates.Database already has coordinates added. This allows for both manual entry and for sharing databases among builds.
  • Fixed inadvertent conversion of '://' to ':/' in absolute paths for: Metadata.Domain, WebPaths.ProfilePhotos, WebPaths.SourceImages, WebPaths.Thumbnails, WebPaths.AssetImages, WebPaths.AssetsScripts, WebPaths.AssetsTypes.
  • Cleanup displaying the Validation report by stripping Embedded HTML.
  • Added support for building a Gigatree into a directory tree. This change includes adding a Page.Folder option and a Page.Prefix option. Gigatrees now defaults to this mode. Users wishing to retain their flat tree structure can clear the Page.Folder options and set the Page.File and Page. Prefix names to match their existing naming conventions. Note, filename prefixes no longer hardcode a dash separating the prefix from the file suffix, so users will need to include the dash in the Page.Prefix where needed. The assets are also now copied to an assets folder in the directory tree when no WebPaths are specified.
  • The default directory tree uses "index" as the filename for most pages located in folders. By default, these filenames are included in Gigatrees links. If your server automatically loads http://gigatrees.appspot.com or index.php when a folder is accessed, you can exclude "index" from the menu links by disabling the new option MenuBar.LinkIndex. The sample trees disable this option, so you will not see the filename index being loaded. Offline trees require the this option be enabled (default).
  • Some changes were made to cleanup option names and consistency:
  • Page.Updates and Page.Analysis are now enabled by default.
  • Timeline pages, when appending the filename suffix index, no longer zero fill the index to 2 places, i.e. "02" is now simply "2".
  • Page.Generations renamed to Page.Ancestors.
  • GenerationLists renamed to AncestorLists.
  • GenerationLists.OldStyle renamed to AncestorLists.Agnus and inverted its state. Where enabling GenerationLists.OldStyle converted ancestor lists to the ahnen numbering system. This is now accomplished by disabling AncestorLists.Agnus. Agnus, the default state, stands for Yet Another Genealogy NUmbering System and is the preferred numbering system to use with Gigatrees for its several advantages - bidirectional and compact numbering. Follow the link for a complete description.
  • ProfilePages.EnableGenerationLists renamed to ProfilePages.EnableAncestorLists.
  • Added loading the en.txt language translation file to the default configuration. The is not necessary needed, but is used by the sample trees to load alternate English display strings. The file can be modified by users to define additional alternate display strings.
  • Page.Article filename suffixes now use their title seo slug rather than their logical record id. Users wishing to retain their old names, can use the _SLUG tag to override the slug Gigatrees' automatically creates.
  • Lastly, and most importantly, Gigatrees has added the AppendRecordField option that allows users to added fields to a logical record without needing to modify the GEDCOM file. Some of the most important GEDCOM extensions can be added in this way. Specifically, users can now add source categories, add privacy and living flags,force showing or hiding logical record and create articles by simply adding this option to their configuration file. This works because logical record ids never change. The option has three fields: AppendRecordField.RecordId, AppendRecordField.Tag, and AppendRecordField.Value. For instance to define a source category of original for S1:
     
    <AppendRecordField>  
      <RecordId> S1       </RecordId>  
      <Tag>      _QUAL    </Tag>  
      <Value>    original </Value>
    </AppendRecordField>
  • Fixed detection of a working Internet connection.
  • Completely redid the configuration options and added the Documentation page detailing all aspects of use. Configuration files for earlier versions will no longer work.
  • Improved date handling capabilities, including adding support for the "or", "by" and "maybe" date qualifiers and their alternates.
  • Removed military eras. When the military page is enabled, all military events will now be listed on a single page.
  • There is now even better photo, image and url support, including a <HideLocalLinks> option.
  • This update includes numerous bug and crash fixes as well as many new improvements. There are far too many items to cover here in detail, so I'll run through the most important changes briefly, and then update the documentation accordingly.
  • The validator has been almost completely rewritten. It now includes autodetection of the January 2, 1996 and January 10, 1996 revisions of the GEDCOM 5.5 specification, and validates them according to their unique dictionaries. The validator has added support for character validation to the elements of the grammar including detecting both printable and non-printable control characters in the data. The validator is a GEDCOM grammar and dictionary validator only; support for data (date) validation has been removed. The Gigatrees data analyzer will continue to flag dates that it does not recognize. The validation options have also been completely redone and are now included in the default configuration file as well as the validation configuration file. This is because Gigatrees now shows validation errors, but only for those conditions that it cannot workaround. Gigatrees can work around quite a few issues and support for several new ones have been added like support for MyHeritage exports that do not use CONTinuation tags. New error validation strings have been added to the end of the translation files so that they are easily located for update.
  • Several other options have been modified as well. The <HideLiving> and <Privatize> options now both enabled by default. This is to provide out-of-the-box protection for users using the default options to publish their tree online. All of the various path options now also default to empty, forcing users to set them appropriately. The default configuration file still sets some of these for you. The options that most users will need to set have been moved to the top of the default configuration file also. There is a new <ReplaceText> option that allows you to setup strings to replace in your data. You can replace virtually any of your GEDCOM data content this way. The default <UserStrings> for <ClaimIgnore> has been modified to use brackets, i.e. [ignore]. This is because without brackets, the partial string "ignore" found in any note text would cause the entire note to be discarded. Some of the other changes are improved handling of URLs and images, better location coordinate server interfaces, version checking, error reporting, performance profiling, improved build logging, new silent and verbose options, and UTF-16 support. A number of new vendor specific fields have also been added including RootsWeb's alternate dates, multimedia comments and source webtags.
  • Removed the DLL requirements from the appplication and added the <GeonamesUserId> option.
  • Improved automatic translations by adding support for the Google translation service. I also updated the translation files; now all default display strings should be included.
  • Added support for automatic translations via the Microsoft translation service.
  • Expanded support for Kinship Lines by adding a new "Kinship" page option to <Pages> where you can enable and disable the new Kinship List pages. Kinship Lists are in effect a Descendant List between the most recent common ancestor, and related spouses. When enabled, the most recent common ancestor link on the Kinship Lines tab will link to the appropriate Kinship List. When disabled, it will go back to linking to that person's profile page.
  • I added initial support for translations with the <LanguageFile> option, which specifies the path to a text file that holds all of Gigatrees' translation strings.
  • I added an <AlternateNamesFile> option that specifies the path to a text file that holds alternate given names. Alternate names are used during data analysis to determine similarly named children and also by the Statistics page for determining popular names. Another option was added that allows you to ignore similarly named children whose timelines did not overlap during data analysis.
  • A new test was added during data analysis that will detect persons with unknown genders. I also fixed the text for unknown genders. Another new test will show locations for which no coordinates have been found. I also fixed a bug preventing abbreviated state names from being recognized.
  • Improved handling of non GEDCOM compliant dates and fixed handling of British monarch dates.
  • Fixed handling of Ancestry.com's parental associations via their _FREL and _MREL tags.
  • Added another data analysis test that will detect families having swapped spouses.
  • Ancestry.com requires when editing source citations that the "Details" field be set. On export, this field in put into the page number. I added a special user string of <PageNone> so that users can tell Gigatrees what special text in that field should be discarded.
  • Ancestry.com strips HTML from any text fields such as in sources. Added support for special embedded HTML tags that can be used with Ancestry.com.
  • I added initial support for Kinship Lines by adding a tab on individual profile pages that shows for each related spouse their degree of kinship, relationship and most recent common ancestor. I also added a <CalculateKinshipUsingCanonLaw> option, which allows you to control how the degree of kinship (also called affinity or consanguinity) is calculated. The default calculation method is based on civil law. Enabling the option changes the calculation method to canon law. Both civil courts and churches prohibit a union between spouses too closely related. I added a <ProhibitedDegreeOfKinship> configuration option as well. It allows you to specify the degree at which marriage unions should be considered prohibited (based on your calculation method). This value is then used in during data analysis to detect spouses who should have been denied marriage and are therefore improbably married. This should be very useful to medieval genealogists who are often trying to pinpoint the marriages between similarly named individuals, Finding that a man and a woman were too closely related will help eliminate prospective candidates.
  • This is the initial release of the distribution. New features not previously available in the web service are support for Descendant lists, an Immigrants report, a Nobility report, a Military events timeline, ancestor distribution heatmaps on each person's profile (that flags all their ancestors' earliest event locations), FancyBox support for displaying images, special support for linking to source page numbers, additional data analysis tests, GEDCOM tag naming, and tons of other controls for enabling and disabling features. Individual reports, such as Data Analysis (Bonkers), can still be generated by disabling any pages not needed for that report. The GEDCOm Validator (VGedX) continues to be available by setting the <Project>.