Updated doc about PQF. Spell fixes.

[yaz-moved-to-github.git] / doc / installation.xml

diff --git a/doc/installation.xml b/doc/installation.xml
index ae46e14..101ec67 100644 (file)
--- a/doc/installation.xml
+++ b/doc/installation.xml
@@ -1,4 +1,4 @@
-<!-- $Id: installation.xml,v 1.9 2001-11-18 21:14:22 adam Exp $ -->
+<!-- $Id: installation.xml,v 1.12 2002-08-17 07:55:51 adam Exp $ -->
  <chapter id="installation"><title>Compilation and Installation</title>
   
   <sect1><title>Introduction</title>
@@ -22,7 +22,8 @@
        <listitem><para>HP/UX</para></listitem>
        <listitem><para>SunOS/Solaris</para></listitem>
        <listitem><para>DEC Unix</para></listitem>
-       <listitem><para>OpenBSD/FreeBSD</para></listitem>
+       <listitem><para>BSDs: FreeBSD, OpenBSD, NetBSD, MAC OSX
+        </para></listitem>
        <listitem><para>Linux</para></listitem>
        <listitem><para>IBM AIX</para></listitem>
        <listitem><para>Data General DG/UX (with some CFLAGS tinkering)
@@ -45,8 +46,8 @@
     let us know about it. If you run into difficulties, we will try to help
     if we can, and if you solve the problems, we would be happy to include
     your fixes in the next release. So far, we have mostly avoided
-    &num;ifdefs for individual platforms, and we'd like to keep it that
-    way as far as it makes sense.
+    <literal>&num;ifdefs</literal> for individual platforms, and we'd
+    like to keep it that way as far as it makes sense.
    </para>
    
    <para>
@@ -54,7 +55,9 @@
     bug-fixes, as well as general discussion. Subscribe by sending mail to
     <ulink url="mailto:yaz-request@indexdata.dk">
      yaz-request@indexdata.dk
-    </ulink>.
+    </ulink> or fill-in the form
+    <ulink url="http://www.indexdata.dk/mailman/listinfo/yazlist">
+     here</ulink>.
     General questions and problems can be directed at 
     <ulink url="mailto:yaz-help@indexdata.dk">
      yaz-help@indexdata.dk
@@ -67,14 +70,14 @@
    <para>
     Note that if your system doesn't have a native ANSI C compiler, you may
     have to acquire one separately. We recommend
-    <ulink url="http://gcc.gnu.org">GCC</ulink>.
+    <ulink url="http://gcc.gnu.org/">GCC</ulink>.
    </para>
    <para>
     For UNIX, the GNU tools
     <ulink url="http://www.gnu.org/software/autoconf/">Autoconf</ulink>,
     <ulink url="http://www.gnu.org/software/automake/">Automake</ulink> and
     <ulink url="http://www.gnu.org/software/libtool/">Libtool</ulink>
-    is used to generate Makefiles and configure &yaz; for the system.
+    are used to generate Makefiles and configure &yaz; for the system.
     You do <emphasis>not</emphasis> these tools unless you're using the
     CVS version of &yaz;.
     Generally it should be sufficient to run configure without options,
@@ -127,7 +130,7 @@
      <varlistentry><term><literal>--with-openssl</literal></term>
       <listitem><para>&yaz; will be linked with the OpenSSL libraries and
         an SSL COMSTACK will be provided. Note that SSL support is still
-        exterimental.
+        experimental.
        </para></listitem>
      </varlistentry>
      <varlistentry><term><literal>--enable-shared</literal></term>
@@ -329,7 +332,7 @@
     is located. Customize the installation by editing the
     <filename>makefile</filename> file (for example by using notepad).
     
-    The following summarises the most important settings in that file:
+    The following summarizes the most important settings in that file:
 
     <variablelist>
      <varlistentry><term><literal>DEBUG</literal></term>
@@ -423,7 +426,7 @@
      Some people are confused by the fact that we use the nmake
      tool to build &yaz;. They think they have to do that too - in order
      to make their WIN32 applications work with &yaz;. The good news is that
-     you don't have to. You can use the integrated environement of
+     you don't have to. You can use the integrated environment of
      Visual Studio if desired for your own application.
     </para>
     <para>