The Complete Genealogy Reporter will process GEDCOM files created in either ANSI or UTF-8 (see below) format.  

The current version of The Complete Genealogy Reporter supports the following GEDCOM record types and subordinate data types:

Dates read from the GEDCOM file are processed in order to produce a consistent formatting style within the report.  

Expression

• Full dates will be reported in the form "21 January 1882".  GEDCOM records containing "21 Jan 1882", "Jan 21 1882", 21/1/1882" or "1/21/1882" will all result in "21 January 1882" or "January 21, 1882" being reported, depending upon the selected date format option.
• Dates may include "BC" or "BCE".
• Dates may include dual years (such as 1246/7).  The former year is used in sorting and reporting birth and death years in family tree diagrams.
• An ambiguous numeric date will be interpreted as DD/MM or MM/DD depending on the format of other non-ambiguous dates in the GEDCOM file.  For example, "2/4/1882" will be interpreted as "2 April 1882" if another numeric date is found in the file to be unambiguously of the DD/MM format, such as "16/8/1677".  Conversely, "2/4/1882"will be interpreted as "4 February 1882" if another numeric date is found in the file to be unambiguously of the MM/DD format, such as "8/16/1677".
• Dates may include most European month names and abbreviations; e.g., "2 Avril 1882".
• Dates may include GEDCOM standard calendar escape strings (e.g., "@#DHEBREW@").  These will be reported within the narrative in addition to the Gregorian date, if both are specified for an event.  Hebrew and French Republican calendar month abbreviations will be expanded to full names (e.g., "TSH" will be reported as "Tishrei").

Qualification

• A date field in the GEDCOM file which is preceded by "c", "circa", "cal", "calc", "abt", or "about" (irrespective of case) is interpreted as meaning an approximate year and is reported as "c" (short form) or "about" (long form) within the report.
• A date field in the GEDCOM file which is preceded by "<", "b", "by","bef", or "before" (irrespective of case) is interpreted as meaning the latest possible year and is reported as "b" (short form) or "before" (long form) within the report.  
• A date field in the GEDCOM file which is preceded by ">", "a", "aft", or "after" (irrespective of case) is interpreted as meaning the earliest possible year and is reported as "a" (short form) or "after" (long form) within the report.  
• A date field in the GEDCOM file which contains "bet" or "between" and "and" is interpreted as indicating a date range.
• A date field in the GEDCOM file which contains "fr" or "from" and "to" is interpreted as indicating a date range.
• A date field in the GEDCOM file which contains "-" is interpreted as indicating a date range. 
• A date field in the GEDCOM file which is preceded by "int" (irrespective of case) is interpreted as indicating a date which has been estimated from the interpretative data shown in parentheses.  e.g., "INT May 1888 (from reported age at that time)".
• Date ranges are expressed within the narrative of the form "between July 1888 and 1 May 1892".

Sortation and Calculation

• The average of a date range is used in sorting and reporting birth and death years in family tree diagrams.
• When dates are sorted, they are sorted by year.  If the year is the same, the sortation within that year is firstly dates annotated "before", then precise dates, then dates annotated "about", then dates annotated "after".  If the date is expressed as a date range, the first year of the range is used for sorting.
• When it is determinable, the age at death is included in the report.   Ages at events (included marriages) may also be reported.  When calculating ages, if a month is not recorded, July 1st of the year is used.  If a month is recorded, but a day is not recorded, the 15th of the month is used.  Ages will be reported as exact, about, more than, or less than, depending upon the about, before, or after annotations of each of the dates and whether the day and/or month were assumed.

If the date processor within The Complete Genealogy Reporter should prove unable to interpret the dates in your GEDCOM file appropriately, you may specify that date information be reported exactly as recorded in the file.

UTF-8 Format Files

Some GEDCOM file exports are created in UTF-8 format by default.  An example would be a GEDCOM file exported by the phpGedView web-based software.

In such cases, the characters shown below would normally be misrepresented on the report. The word "née", for example, which had been exported to a UTF-8 format GEDCOM file would be misreported as "née". This occurs because these characters are stored as two-bytes in the UTF-8 format.

However, if the header section of the GEDCOM file specifies that the file uses the UTF-8 character format, The Complete Genealogy Reporter will automatically convert the data as it is processed from the GEDCOM file so that each of the following characters will appear correctly in the report:

¢   £  ¤   ¥   ¦   §   ¨   ©   ª   «   ¬   ­   ®   ¯   °   ±   ²   ³   ´   µ   ¶   ·   ¸   ¹   º   »   ¼   ½   ¾   ¿  

À   Á      à  Ä   Å   Æ   Ç   È   É   Ê   Ë   Ì   Í   Π  Ï   Р  Ñ   Ò   Ó   Ô   Õ   Ö   ×   Ø   Ù   Ú   Û   Ü   Ý   Þ   ß

à   á   â   ã   ä   å   æ   ç   è   é   ê   ë   ì   í   î   ï   ð   ñ   ò   ó   ô   õ   ö   ÷   ø   ù   ú   û   ü   ý   þ   ÿ  

Limits

• 32,767 different last names.
• 32,767 individuals per last name.
• If there are more than fifteen children in a family, only the first fourteen children are shown individually in a tree chart.  The fifteenth box then indicates the number of additional children that are reported in the narrative section.

(Return to top of page)
 

© 2006-2008 Nigel Bufton. All rights reserved.