AABanner2.gif (2436 bytes)

 

Revision History

Version 2.9y Released 26 May 2018

hspacer.gif (824 bytes)

Version 2.9y fixes a bug related to empty GEDCOM NOTE records.

  • 2.9x produced an 'assertion error' that would occur on zero length notes attached to BIRT, DEAT, and other GEDCOM event records. The error looked like this: AA Assertion Failure (strlen(string) > 0) in file ..\Ged2Doc\srctbl.cpp, line 55. This has been fixed.

This is a FREE upgrade to existing customers.


Previous Releases

2.9x (18 May 2018)

  • AA would sometimes stall or hang during report generation - but only if date sorting was turned on (Options->Sorting Dates). This has been fixed.

2.9w (9 Jan 2018)

  • Cosmetic changes and bug fixes.

2.9v (3 Feb 2017)

  • Annual update - cosmetic changes.

2.9u (17 Mar 2016)

  • The download file has been 'signed' with a renewed software certificate. This should make the download more secure, and will avoid some of the alarming warnings issued by Internet Explorer, and other browsers.
  • Normally AA does not support the UTF-8 character encoding in GEDCOM files, even though the GEDCOM standard allows UTF-8 encodings. Instead, AA supports the ANSI (ISO-Latin-1) character encoding. GEDCOMs that contain foreign character sets (Chinese, Farsi, Thai, etc) must be encoded in UTF-8; but Western character sets (English, most European languages) do not require UTF-8; ANSI is sufficient.

    Some genealogy programs export UTF-8 encoded GEDCOM files anyway, even if ANSI would be sufficient. AA can usually handle these GEDCOM files, as long as the characters are standard ISO-Latin-1. Sometimes, though, non ISO-Latin-1 characters will sneak in. AA will now convert these to ISO-Latin-1 whenever there is an equivalent.

2.9t (8 Jan 2016)

  • Cosmetic updates and bug fixes.

2.9q (19 Feb 2015)

  • Added checks for unsupported GEDCOM character sets.

  • Increased the maximum number of GEDCOM errors that are tolerated before AA refuses to read the rest of the GEDCOM.

  • Fixed several bugs.

2.9o (5 Jan 2014)

  • A new GEDCOM option has been added to control the treatment of CONT text records. In previous versions of AA, the text in CONT records was placed on the same line as the text from a previous record (CONT, CONC, NOTE); it was wrapped to the new line only if the end of the current line had been reached.

    The new option forces the text from CONT records to be placed on a new line. This approach aligns with the GEDCOM 5.5 standard. 

    To choose the new option, press the OPTIONS button, select the GEDCOM tab, and check the "Check here to force newlines CONT." box.

  • Increased maximum number of images that can be embedded in the PDF document from 1000 to 5000.

  • Added support for the GEDCOM RESI tag. Residence information is now output for each individual in the report.

  • Added support for the GEDCOM ADDR tag. Residence, Census, and other GEDCOM attributes will now include address information.

  • A bug related to date formats has been fixed. Dates of the form
    "FROM date1 TO date2" were incorrectly reported as "FROM date1 ABOUT date2". This has been fixed.

  • Several additional bugs have been fixed.

Version 2.9d (3 Jan 2012)

  • Maximum number of hyperlinks has been increased from 1.5 million to 4.5 million. The page limit has increased from 24,000 to 72,000.

  • The GEDCOM reading speed is no much faster.

  • Ported to Windows 64-bit operating systems. The 64-bit version of AA is automatically installed on 64-bit versions of Windows, and will process much larger GEDCOM files than the standard 32-bit version of AA.

    To see if you are running the 64-bit version of AA, press the ABOUT button. You should see the following version string:

    Ancestral Author 2.9d - 64 bit

In addition, the following bugs have been fixed:

  • Fixed a crash that occurred if the root of the descendant report was not found.