Update installation instructions and put mostly everything in one place.

Also, some editing in PL/Perl and PL/Python chapters.

doc/src/sgml/charset.sgml

-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.27 2002/08/14 02:45:09 ishii Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.28 2002/09/18 20:09:31 petere Exp $ -->
 
 <chapter id="charset">
  <title>Localization</>
@@ -889,30 +889,6 @@ RESET CLIENT_ENCODING;
     </para>
    </sect2>
 
-   <sect2>
-    <title>About Unicode</title>
-
-    <indexterm><primary>Unicode</></>
-
-    <para>
-     An automatic encoding translation between Unicode and other
-     encodings has been supported since <productname>PostgreSQL</> 7.1.
-     For 7.1 it was not enabled by default.
-     To enable this feature, run configure with the
-     <option>--enable-unicode-conversion</option> option. Note that this requires
-     the <option>--enable-multibyte</option> option also.
-    </para>
-    <para>
-    For 7.2, <option>--enable-unicode-conversion</option> is not necessary.
-    The Unicode conversion functionality is automatically enabled
-    if <option>--enable-multibyte</option> is specified.
-    </para>
-    <para>
-    For 7.3, <option>--enable-unicode-conversion</option> nor
-    <option>--enable-multibyte</option> is needed.
-    </para>
-   </sect2>
-
    <sect2>
     <title>What happens if the translation is not possible?</title>
 

doc/src/sgml/client-auth.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.37 2002/09/14 18:35:46 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.38 2002/09/18 20:09:31 petere Exp $
 -->
 
 <chapter id="client-authentication">
@@ -583,10 +583,9 @@ local   db1,db2,@demodbs  all                                       md5
 
    <para>
     In order to use <productname>Kerberos</>, support for it must be
-    enabled at build time. Both Kerberos 4 and 5 are supported
-    (<literal>./configure --with-krb4</> or <literal>./configure
-    --with-krb5</> respectively), although only one version can be
-    supported in any one build.
+    enabled at build time.  See <xref linkend="installation"> for more
+    information.  Both Kerberos 4 and 5 are supported, but only one
+    version can be supported in any one build.
    </para>
 
    <para>

doc/src/sgml/jdbc.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.36 2002/03/22 19:20:11 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.37 2002/09/18 20:09:31 petere Exp $
 -->
 
  <chapter id="jdbc">
@@ -51,92 +51,34 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.36 2002/03/22 19:20:11
    </para>
 
    <para>
-    Alternatively you can build the driver from source.  Although you 
-    should only need to do this if you are making changes to the source
-    code.
+    Alternatively you can build the driver from source, but you
+    should only need to do this if you are making changes to the
+    source code.  For details, refer to the PostgreSQL installation
+    instructions.  After installation, the driver should be found in
+    <filename><replaceable>PREFIX</>/share/java/postgresql.jar</filename>.
+    The resulting driver will be built for the version of Java you are
+    running.  If you build with a 1.1 JDK you will build a version
+    that supports the JDBC 1 specification, if you build with a Java 2
+    JDK (e.g., JDK 1.2 or JDK 1.3) you will build a version that
+    supports the JDBC 2 specification.
    </para>
-
-   <para>
-    Starting with <productname>PostgreSQL</productname> version 7.1,
-    the <acronym>JDBC</acronym> driver is built using
-    <application>Ant</application>, a special tool for building
-    Java-based packages.  You should download
-    <application>Ant</application> from the <ulink
-    url="http://jakarta.apache.org/ant/index.html"><application>Ant</application>
-    web site</ulink> and install it before proceeding.  Precompiled
-    <application>Ant</application> distributions are typically set up
-    to read a file <filename>.antrc</filename> in the current user's
-    home directory for configuration.  For example, to use a different
-    <acronym>JDK</acronym> than the default, this may work:
-<programlisting>
-JAVA_HOME=/usr/local/sun-jdk1.3
-JAVACMD=$JAVA_HOME/bin/java
-</programlisting>
-   </para>
-
-   <para>
-    To build the driver, add the <option>--with-java</option> option to your
-    <filename>configure</filename> command line, e.g.,
-<screen>
-<prompt>$</prompt> <userinput>./configure --prefix=<replaceable>xxx</replaceable> --with-java ...</userinput>
-</screen>
-    This will build and install the driver along with the rest of the
-    <productname>PostgreSQL</productname> package when you issue the
-    <literal>make/gmake</literal> and <literal>make/gmake install</literal>
-    commands.  If you only want to build the driver and not the rest
-    of <productname>PostgreSQL</productname>, change into the
-    directory <filename
-    class="directory">src/interfaces/jdbc</filename> and issue the
-    respective <literal>make/gmake</literal> command there.  Refer to the
-    <productname>PostgreSQL</productname> installation instructions
-    for more information about the configuration and build process.
-   </para>
-
-   <para>When building the driver from source the jar file that is created
-    will be named <filename>postgresql.jar</filename>.  The build will 
-    create this file in the <filename>src/interfaces/jdbc/jars</filename>
-    directory.  The resulting driver will be built for the version of 
-    Java you are running.  If you build with a 1.1 JDK you will build
-    a version that supports the jdbc1 specification, if you build with a 
-    Java2 JDK (i.e. JDK1.2 or JDK1.3) you will build a version that 
-    supports the jdbc2 specification. 
-   </para>
- 
-   <note>
-    <para>
-     Do not try to build the driver by calling <command>javac</command> 
-     directly, as the driver uses some dynamic loading techniques for
-     performance reasons, and <command>javac</command> cannot cope.
-     Do not try to run <command>ant</command> directly either, because
-     some configuration information is communicated through the
-     makefiles.  Running <command>ant</command> directly without
-     providing these parameters will result in a broken driver.
-    </para>
-   </note>
   </sect2>
 
   <sect2 id="jdbc-classpath">
    <title>Setting up the Class Path</title>
 
    <para>
-    To use the driver, the jar archive (named
+    To use the driver, the JAR archive (named
     <filename>postgresql.jar</filename> if you built from source, otherwise
     it will likely be named <filename>jdbc7.2-1.1.jar</filename> or 
-    <filename>jdbc7.2-1.2.jar</filename> for the jdbc1 and jdbc2 versions
+    <filename>jdbc7.2-1.2.jar</filename> for the JDBC 1 and JDBC 2 versions
     respectively)
     needs to be included in the
     class path, either by putting it in the <envar>CLASSPATH</envar>
     environment variable, or by using flags on the
-    <command>java</command> command line.  By default, the jar archive
-    is installed in the directory <filename
-    class="directory">/usr/local/pgsql/share/java</filename>.  You may
-    have it in a different directory if you used the
-    <option>--prefix</option> option when you ran
-    <filename>configure</filename>, or if you are using a binary distribution
-    that places it in some different location.
+    <command>java</command> command line.
    </para>
 
-   <informalexample>
     <para>
      For instance, I have an application that uses the
      <acronym>JDBC</acronym> driver to access a large database
@@ -163,7 +105,6 @@ java Finder
      Loading the driver from within the application is covered in
      <xref linkend="jdbc-use">.
     </para>
-   </informalexample>
   </sect2>
 
   <sect2 id="jdbc-prepare">
@@ -183,7 +124,7 @@ java Finder
     Also, the client authentication setup in the
     <filename>pg_hba.conf</filename> file may need to be configured.
     Refer to the <citetitle>Administrator's Guide</citetitle> for
-    details.  The <acronym>JDBC</acronym> Driver supports trust,
+    details.  The <acronym>JDBC</acronym> Driver supports the trust,
     ident, password, md5, and crypt authentication methods.
    </para>
   </sect2>

doc/src/sgml/maintenance.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.17 2002/06/23 03:51:55 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.18 2002/09/18 20:09:32 petere Exp $
 -->
 
 <chapter id="maintenance">
@@ -424,14 +424,13 @@ VACUUM
 
   <para>
    The simplest production-grade approach to managing log output is to
-   send it all to <application>syslog</> and let <application>syslog</>
-   deal with file rotation. To do this, make sure
-   <productname>PostgreSQL</> was built with the
-   <option>--enable-syslog</> configure option, and set
+   send it all to <application>syslog</> and let
+   <application>syslog</> deal with file rotation. To do this, set
    <literal>syslog</> to 2 (log to syslog only) in
    <filename>postgresql.conf</>. Then you can send a
-   <literal>SIGHUP</literal> signal to the <application>syslog</> daemon
-   whenever you want to force it to start writing a new log file.
+   <literal>SIGHUP</literal> signal to the <application>syslog</>
+   daemon whenever you want to force it to start writing a new log
+   file.
   </para>
 
   <para>

doc/src/sgml/ref/psql-ref.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.74 2002/08/27 20:16:48 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.75 2002/09/18 20:09:32 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -2274,33 +2274,6 @@ $endif
     <application>readline</application> feature. Read its documentation
     for further details.)
     </para>
-
-    <para>
-    If you have the readline library installed but
-    <application>psql</application> does not seem to use it, you must
-    make sure that <productname>PostgreSQL</productname>'s top-level
-    <filename>configure</filename> script finds it.
-    <filename>configure</filename> needs to find both the library
-    <filename>libreadline.a</filename> (or a shared library equivalent)
-    <emphasis>and</emphasis> the header files
-    <filename>readline.h</filename> and <filename>history.h</filename>
-    (or <filename>readline/readline.h</filename> and
-    <filename>readline/history.h</filename>) in appropriate directories.
-    If you have the library and header files installed in an obscure
-    place you must tell <filename>configure</filename> about them, for
-    example:
-<programlisting>
-$ ./configure --with-includes=/opt/gnu/include --with-libs=/opt/gnu/lib  ...
-</programlisting>
-    Then you have to recompile <application>psql</application> (not
-    necessarily the entire code tree).
-    </para>
-
-    <para>
-    The <acronym>GNU</acronym> readline library can be obtained from the
-    <acronym>GNU</acronym> project's <acronym>FTP</acronym> server at
-    <ulink URL="ftp://ftp.gnu.org">ftp://ftp.gnu.org</ulink>.
-    </para>
    </refsect3>
   </refsect2>
  </refsect1>

doc/src/sgml/runtime.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.136 2002/09/17 21:41:47 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.137 2002/09/18 20:09:32 petere Exp $
 -->
 
 <Chapter Id="runtime">
@@ -973,8 +973,8 @@ env PGOPTIONS='-c geqo=off' psql
         to turn this on, as it might expose programming mistakes. To use
         this option, the macro <literal>USE_ASSERT_CHECKING</literal>
         must be defined when <productname>PostgreSQL</productname> is
-        built (see the configure option
-        <literal>--enable-cassert</literal>). Note that
+        built (accomplished by the configure option
+        <option>--enable-cassert</option>). Note that
         <literal>DEBUG_ASSERTIONS</literal> defaults to on if
         <productname>PostgreSQL</productname> has been built with
 	assertions enabled.
@@ -1176,11 +1176,6 @@ env PGOPTIONS='-c geqo=off' psql
         <systemitem>syslog</> is off. This option must be set at server
         start.
        </para>
-       <para>
-        To use <systemitem>syslog</>, the build of
-        <productname>PostgreSQL</productname> must be configured with
-        the <option>--enable-syslog</option> option.
-       </para>
       </listitem>
      </varlistentry>