Known bugs or issues in the current stable release
- Ftree can write SOUR records containing QUAY tags that are not strictly
GEDCOM conformant. I need to think a bit more about this bit...
Thanks to Jack Godfrey for spotting this.
- FTree assumes individuals are either BURIed or CREMated because my mind
is simple that way. Strictly speaking both records can exist and if they do an error is generated
and one will be lost. This is also true of CHRisten and BAPtisM.
Thanks to John Creswell for finding that.
GEDCOM imposes limits on many field lengths. At this time, FTree does
not police or enforce those limits. As such FTree can write files that
applications that rely on the limits may have problems with.
Limitations in the current release
- There are lots of things in the print sections that need attention. In
particular it relies on groff and nenscript to print. It may not work for you.
Commands used are
nenscript -B -1 -W -fCourier8 -Pxxxx
where the 'xxxx' is taken from the printer field in the GUI.
Ideally it should all just write postscript directly (plot does already).
groff -t -mgm -Tps | lpr -Pxxxx
Last modified: 22nd September 2016