--- parser3/INSTALL	2002/01/31 11:11:43	1.2
+++ parser3/INSTALL	2002/02/13 13:04:33	1.5
@@ -3,15 +3,19 @@
 
 1.What is the process to compile Parser3? 
 
-  As most UNIX libraries Parser3 follows the "standard":
+  As most UNIX programs Parser3 follows the "standard":
 
   mkdir $D/parser3project
   cd $D/parser3project
-  gunzip -c parser3src.xxx.tar.gz | tar xvf -
+  gunzip -c parser3-x.x.tar.gz | tar xvf -
+  mv parser3-x.x parser3
   cd parser3
   ./configure --prefix=/usr/local
   make
   
+  That renaming is needed for SQL drivers to be able to find 
+  necessary include-file in Parser3 sources.
+
   By default your would get 'parser3' binary without support of these features:
 	* cache(hashfile class) 
 	* xml(xdoc and xnode classes)
@@ -26,9 +30,10 @@
     $prefix/etc/
       parser3.conf        -- main configuration file
       parser3.charsets/   -- charset definition files
-        windows-1251.cfg  -- cyrillic charset [windows-1251 encoding]
         koi8-r.cfg        -- cyrillic charset [KOI8-R encoding]
         windows-1250.cfg  -- central europian charset [windows-1250 encoding]
+        windows-1251.cfg  -- cyrillic charset [windows-1251 encoding]
+        windows-1257.cfg  -- baltic charset [windows-1257 encoding]
 
   NOTE:
     For subsequent compilations+installs 
@@ -110,9 +115,14 @@
     cp libgdome/gdomecore/gdome-xml-document.h $D/gnome/include/libgdome/gdomecore
     
 
-    Parser3 configure option is --with-gnome-xml=$D/gnome
+    Parser3 configure option:
+        --with-gnome-xml=$D/gnome
 
+    NOTE:
+    In case your glib as installed into some other prefix,
+    specify it's configuration file with
+        --with-glib-config=/path/to/your/glib-config
  
-Alexandr Petrosian(PAF) <paf@design.ru>
+Alexandr Petrosian <paf@design.ru> (http://paf.design.ru)
 
-$Id: INSTALL,v 1.2 2002/01/31 11:11:43 paf Exp $
+$Id: INSTALL,v 1.5 2002/02/13 13:04:33 paf Exp $