1 NOTE: NO BACKWARD COMPATIBILITY IS GUARANTEED FOR 0.x RELEASES !!
5 - New features (see documentation):
6 - function gedcom_get_by_xref
8 - INTERFACE CHANGE: the callback functions now take an extra argument: the
9 record/element identifier (that is also used as first argument in the
10 *_subscribe_* functions). The extra argument is the first argument.
12 - INTERFACE CHANGE: Age values are now parsed: an extra type is added to
13 the types possible in a Gedcom_val: an age_value (see documentation for
14 details). So, instead of GEDCOM_STRING, you now need to use GEDCOM_AGE
16 As a quick change, you can use the raw_value instead of the parsed_value
17 until you make the real change of using the struct age_value.
19 - INTERFACE CHANGE: The type of an xref_value can also be XREF_ANY, if
20 the actual type is not known yet. This is e.g. used in the case of an
21 association (ASSO): the cross-reference can be any object type, the
22 actual type is given by the TYPE subtag.
24 release 0.16 (16 August 2002):
26 - Another bugfixing release.
28 - Some compatibility with Lifelines 3.0.2 is added (not necessarily complete).
30 release 0.15 (27 March 2002):
32 - Again mainly a bugfixing release
34 - Compatibility with ftree is added, all GEDCOM files written by ftree
37 - Note for developers: you now have to call the function gedcom_init()
38 as soon as possible in your program (before any character set handling
39 is done, see documentation for details). If the function has not been
40 called, gedcom_parse_file() will return an error.
42 release 0.14 (20 January 2002):
44 - This is mainly a bugfixing release, no extra features have been added.
46 - Some example code is available on how to convert from UTF-8 to the locale
47 system, and how to check the library version via configure.in (see the
48 documentation for details).
50 release 0.13 (5 January 2002):
52 - Cross-references are now parsed and checked. For this, an extra type is
53 added to the types possible in a Gedcom_val: an xref pointer. This means
54 that GEDCOM_XREF_PTR has to be used now in some places instead of
56 A quick change is to replace
59 GEDCOM_XREF_PTR(val)->string
60 where applicable. But you can also store an object in the 'object' member
61 of the struct returned by GEDCOM_XREF_PTR (see documentation).
63 - Other interface changes in the callbacks:
64 - parsed tag value (integer) is passed next to the string value
65 - the start record callbacks now also contain a Gedcom_val (the NOTE can
68 - Further, various bugfixes have been made.
70 release 0.12 (31 December 2001):
72 - The calling of callbacks is now completed.
74 - Some initial documentation is available.
76 - The parsed value that is returned in callbacks can now be:
79 - a date (struct date_value)
80 See the documentation for more info. Parsing and checking of cross-
81 references will be added next.
83 release 0.11 (15 December 2001):
85 - Initial release from Sourceforge.net (developers only !)