From: Peter Verthez <Peter.Verthez@advalvas.be>
Date: Mon, 30 Dec 2002 14:02:29 +0000 (+0000)
Subject: Finishing up for release.
X-Git-Url: https://git.dlugolecki.net.pl/?a=commitdiff_plain;h=8a88e96477f9bbb3075ec651f34839a97639231d;p=gedcom-parse.git

Finishing up for release.
---

diff --git a/ChangeLog b/ChangeLog
index d6aed35..ee0992e 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2002-12-30  Peter Verthez  <Peter.Verthez@advalvas.be>
 
+	* release 0.20.0
+
 	* gedcom/write.c: Give warning if character set in HEAD.CHAR is not
 	the same as current character set (and force value).
 
diff --git a/NEWS b/NEWS
index ff9e55f..41fbeda 100644
--- a/NEWS
+++ b/NEWS
@@ -1,6 +1,9 @@
 NOTE: NO BACKWARD COMPATIBILITY IS GUARANTEED FOR 0.x RELEASES !!
 
-release 0.20.0 (NOT RELEASED YET):
+release 0.20.0 (30 December 2002):
+
+ - The release numbering scheme is changed to a three-part version number.
+   Patches will just update the last digit.
 
  - The library should now be portable, i.e it should work on any POSIX system.
    On systems lacking glibc, libiconv is needed (see README).
@@ -19,6 +22,7 @@ release 0.20.0 (NOT RELEASED YET):
         - support for writing Gedcom files
      - development support:
         - m4 macro that can be used in configure.in
+        - gedcom-config script for linking and compilation flags
 
  - The library now comes with an extra shared library (libutf8tools),
    which needs to be linked in in any programs that use the gedcom parser
diff --git a/README b/README
index d2dbe71..43a4379 100644
--- a/README
+++ b/README
@@ -1,7 +1,8 @@
 The Gedcom parser library (release @VERSION@)
 -------------------------
 The Gedcom parser library is a C library that provides an API to applications
-to parse and process arbitrary genealogy files in the standard gedcom format.
+to parse, process and write arbitrary genealogy files in the standard gedcom
+format.
 
 Its main features are:
 
@@ -23,13 +24,15 @@ Its main features are:
  - internationalization of the error and warning messages
 
  - specific parsing of date values to a calendar-neutral date system (Julian
-   days aka serial day numbers); the date parser can be called separately
+   days aka serial day numbers); the date parser can be called separately and
+   dates can be manipulated
 
  - specific parsing and checking of cross-references
 
  - specific parsing of age values
 
- - support for writing Gedcom files
+ - support for writing Gedcom files (both in line-by-line format, or via the
+   Gedcom object model)
 
  - "compatibility-mode" parsing, to allow for not-exactly-standard syntaxes
    used by other genealogy programs; currently, compatibility is added for:
@@ -92,6 +95,11 @@ This is simply:
   make
   make install
 
+If libiconv is not automatically found, you can give its path to configure,
+for example, if the library lives in /home/mydir/lib:
+
+  ./configure --with-libiconv-prefix=/home/mydir
+
 You can also run some tests via:
   make check
 
diff --git a/utf8/AUTHORS b/utf8/AUTHORS
index e69de29..f91063f 100644
--- a/utf8/AUTHORS
+++ b/utf8/AUTHORS
@@ -0,0 +1,7 @@
+Authors of utf8tools:
+
+Design and implementation:
+  Peter Verthez <Peter.Verthez@advalvas.be>
+
+# $Id$
+# $Name$
diff --git a/utf8/ChangeLog b/utf8/ChangeLog
index aef4ab7..3420dab 100644
--- a/utf8/ChangeLog
+++ b/utf8/ChangeLog
@@ -1,3 +1,7 @@
+2002-12-30  Peter Verthez  <Peter.Verthez@advalvas.be>
+
+	* release 0.1.0
+
 2002-12-28  Peter Verthez  <Peter.Verthez@advalvas.be>
 
 	* doc/utf8tools.html: Documentation for the library
diff --git a/utf8/NEWS b/utf8/NEWS
index e69de29..df7fa0f 100644
--- a/utf8/NEWS
+++ b/utf8/NEWS
@@ -0,0 +1,6 @@
+release 0.1.0 (30 December 2002):
+
+ - This initial release is part of gedcom-parse 0.20.0.
+  
+# $Id$
+# $Name$
diff --git a/utf8/README b/utf8/README
index e69de29..d3ba6ff 100644
--- a/utf8/README
+++ b/utf8/README
@@ -0,0 +1,9 @@
+This is libutf8tools, a library with tools to manipulate and convert
+UTF-8 strings.  It is installed together with gedcom-parse.
+
+See the doc subdirectory for documentation.
+
+
+###############################################################################
+# $Id$
+# $Name$