Moved some parts to the corresponding file in utf8.

[gedcom-parse.git] / NEWS

diff --git a/NEWS b/NEWS
index 10c8c829a7d8990359f7ad45a4928419fe5b52b6..644def364a92077c16412af5ae4721f25998035b 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,6 +1,40 @@
 NOTE: NO BACKWARD COMPATIBILITY IS GUARANTEED FOR 0.x RELEASES !!
 
-release 0.17 (??):
+release 0.18 (NOT RELEASED YET):
+
+ - The library should now be portable, i.e it should work on any POSIX system.
+   On systems lacking glibc, libiconv is needed (see README).
+
+ - New features (see documentation):
+     - callback interface:
+        - functions to manipulate cross-references (add, delete, link and
+          unlink)
+        - functions to manipulate dates (strings to numbers and vice versa,
+          conversion between calendars, ...)
+        - support for writing Gedcom files
+        - complete concatenated text (e.g. for notes) is now passed in the
+          end callback
+     - C object model interface:
+        - functions for string retrieval and modification
+        - support for writing Gedcom files
+     - development support:
+        - m4 macro that can be used in configure.in
+
+ - INTERFACE CHANGE: the end record callback function now takes an extra
+   argument (similar to the end element callback): a Gedcom_val, which
+   contains in the case of a REC_NOTE the complete concatenated string.
+
+ - INTERFACE CHANGE: the return value of gedcom_init() has changed from
+   void to int to be able to return a status.
+
+ - Various bugfixes.
+
+release 0.17 (12 September 2002):
+
+ - New features (see documentation):
+     - new function gedcom_get_by_xref
+     - age values are parsed
+     - gedcom object model in C
 
  - INTERFACE CHANGE: the callback functions now take an extra argument: the
    record/element identifier (that is also used as first argument in the
@@ -13,6 +47,11 @@ release 0.17 (??):
    As a quick change, you can use the raw_value instead of the parsed_value
    until you make the real change of using the struct age_value.
 
+ - INTERFACE CHANGE: The type of an xref_value can also be XREF_ANY, if
+   the actual type is not known yet.  This is e.g. used in the case of an
+   association (ASSO): the cross-reference can be any object type, the
+   actual type is given by the TYPE subtag.
+
 release 0.16 (16 August 2002):
 
  - Another bugfixing release.