Revision 5.4.8

Although many of the changes in this release will affect specific users or specific exporting applications (Family Historian, Legacy, Ancestry.com), others, such as the way sources are handled, may affect all users.

Changes

1. Improved handling of the Ancestry's SOUR@.PAGE field, which if you did not know, embeds source details in Name/Value (NV) pairs. NV pairs are delimited using colons and semicolons (e.g. Name: Value; Another Name: Another Value). The trailing semicolon is optional. Ancestry also includes standalone values that do not include a name. In this case, Gigatrees will use the first one defined as the page number, unless a page number is included in the NV Pairs. Otherwise and additionally, standalone values are added to the "Other Items" source detail. Any of the source details defined here will be displayed on the Source page, and can be used to populate your configured <SourceTemplates>. To make use of this feature, you will need to enable the <SpecialSourcePageHandler> option.
2. When using Ancestry.com, users will often copy and paste content from the source record to the details (as they suggest). Doing so usually embeds Name/Value (NV) pairs into its contents, which is then exported to the SOUR@.DATA.TEXT GEDCOM field. Gigatrees now supports treating this field as a list of NV pairs, delimited by semicolons ( ; ) when the <SpecialSourceTextHandler> option is emabled. Any of the source details defined will be displayed on the Source page under the page referenced and can be used to populate your configured <SourceTemplates>.
3. Added support for including source details 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. The GEDCOM specifications limit sources to a single TEXT field, but allow multiple NOTE fields, so in order to add source text for multiple pages to the @SOUR field directly, you will need to use bother the TEXT and NOTE field. Gigatrees allows converting NOTE field to TEXT field internally by attaching a page number to the NOTE field. You can do this by defining a @SOUR.NOTE._PAGE field, or by embedding the page number in the NOTE using the square brackets. For example to add a volume and page number more than one source TEXT field, you would need to do the following:

     0 @S1@ SOUR
     1 TEXT [Volume: 3; Page: 22]
     2 CONC some 
     2 CONT text
     1 NOTE [Volume: 3; Page: 23-25]
     2 CONC some 
     2 CONT more 
     2 CONT text
     1 NOTE [Volume: 3; Page: 28]
     2 CONC and 
     2 CONT some 
     2 CONT more
     2 CONT text
   

   Note that Ancestry and other platforms add multiple pages to a source using the SOUR@.PAGE and SOUR@.DATA.TEXT. The main disavantage of using this method is that when the same source text is referenced from multiple places, it must be duplicated. If you are using an application that does not fill in those source reference fields under the hood, it becomes unwieldy to use. Adding the pages to the source directly reduces the bloat and Gigatrees handles matching the page numbers ... under the hood.
4. 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>.
5. Modified the default source templates and fixed handling of configured <SourceTemplates>.
6. Modified the way source and source reference metadata is displayed on source pages and in source reference link tooltips.
7. 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. When defined, Gigatrees will use the , <:fsid:> and placeholders defined in the 'gigatrees' plugin to display the link. You can override the default behavior by redefining the placeholders inside your configuration. FSID links will also be used to link the names for skipped persons in DNA charts and tables who you have flagged using either @INDI._SKIP Y, <GedcomRecords>, or the <Security> <SkipIds> option. When FSIDs are NOT provided for skipped persons, their names are shown in the DNA charts and tables, but not be otherwise linked.
8. 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'.
9. Changed the <HideLocalLinks> default option from true to false.
10. Added support for some app specific GEDCOM tags and GEDCOM 7:

      @FAM.EVEN.AGE.PHRASE (G7)
      @FAM.NO - non event (G7)
      @INDI.CREA - creation date
      @INDI.EVEN.AGE.PHRASE (G7)
      @INDI.NO - non event (G7)
      @OBJE._NOTA - notation/caption
      @OBJE._ORIG._URL
      @_RNOT (partial - it is treated as a NOTE)
      @REPO._PLAC
      @SNOTE - shared note (G7)
      @SOUR.CREA - creation date
      @SOUR.NOTE._URL
      @SOUR._FIELD - source details
      @TMP - source template
      OBJE@.TITL (G7)