Fix a few links. Mention zlib.

diff --git a/doc/asn.xml b/doc/asn.xml
index 854bc0b..adf59de 100644 (file)
--- a/doc/asn.xml
+++ b/doc/asn.xml
@@ -1,4 +1,4 @@
-<!-- $Id: asn.xml,v 1.13 2003-11-19 21:17:26 adam Exp $ -->
+<!-- $Id: asn.xml,v 1.14 2004-03-19 21:12:13 adam Exp $ -->
  <chapter id="asn"><title>The Z39.50 ASN.1 Module</title>
   <sect1 id="asn.introduction"><title>Introduction</title>
    <para>
@@ -132,7 +132,7 @@
     
    </para>
   </sect1>
-  <sect1 id="asn.oid"><title id="oid">Object Identifiers</title>
+  <sect1 id="asn.oid"><title>Object Identifiers</title>
   <para>
     When you refer to object identifiers in your application, you need to
     be aware that SR and Z39.50 use two different set of OIDs to refer to

diff --git a/doc/frontend.xml b/doc/frontend.xml
index 3c2a701..81366b8 100644 (file)
--- a/doc/frontend.xml
+++ b/doc/frontend.xml
@@ -1,4 +1,4 @@
-<!-- $Id: frontend.xml,v 1.21 2004-01-17 01:20:12 adam Exp $ -->
+<!-- $Id: frontend.xml,v 1.22 2004-03-19 21:12:13 adam Exp $ -->
  <chapter id="server"><title>Generic server</title>
   <sect1><title>Introduction</title>
    
@@ -546,10 +546,10 @@ typedef struct bend_fetch_rr {
      that holds the reference to the desired record.
      The <literal>number</literal> is the offset into the set (with 1
      being the first record in the set). The <literal>format</literal> field
-     is the record format requested by the client (See section
-     <link linkend="oid">Object Identifiers</link>). The value
-     <literal>VAL_NONE</literal> indicates that the client did not
-     request a specific format. The <literal>stream</literal> argument
+     is the record format requested by the client (See
+     <xref linkend="asn.oid"/>).
+     The value <literal>VAL_NONE</literal> indicates that the client did
+     not request a specific format. The <literal>stream</literal> argument
      is an &odr; stream which should be used for
      allocating space for structured data records.
      The stream will be reset when all records have been assembled, and

diff --git a/doc/installation.xml b/doc/installation.xml
index 7dd9986..0d12c23 100644 (file)
--- a/doc/installation.xml
+++ b/doc/installation.xml
@@ -1,4 +1,4 @@
-<!-- $Id: installation.xml,v 1.21 2003-12-16 14:51:45 adam Exp $ -->
+<!-- $Id: installation.xml,v 1.22 2004-03-19 21:12:13 adam Exp $ -->
  <chapter id="installation"><title>Compilation and Installation</title>
   
   <sect1><title>Introduction</title>
@@ -491,7 +491,7 @@
          (<filename>cql.y</filename>).
         </para>
         <para>
-         GNU Bison for Windows is part of 
+         A Windows version of GNU Bison is part of 
          <ulink url="http://unxutils.sourceforge.net/">unxutils</ulink>.
         </para></listitem>
       </varlistentry>
@@ -514,12 +514,20 @@
          If <literal>HAVE_LIBXML2</literal> is set to 1, YAZ is compiled
          with SRW (and SOAP) support. In this configuration, set 
          <literal>LIBXML2_DIR</literal> to the 
-         <ulink url="http://www.xmlsoft.org/">libxml2</ulink> source directory.
+         <ulink url="http://www.xmlsoft.org/">libxml2</ulink> source directory
+        and
+        <literal>ZLIB_DIR</literal> to the zlib directory.
         </para>
 
+       <note>
+        <para>
+         Note that YAZ is not using ZLIB. But libxml2 is.
+        </para>
+       </note>
+
         <para>
-         Windows versions of libxml2 and iconv can be found
-         <ulink url="http://www.zlatkovic.com/projects/libxml/binaries.html">
+         Windows versions of libxml2, zlib and iconv can be found
+        <ulink url="http://www.zlatkovic.com/libxml.en.html">
           here</ulink>.
         </para>
        </listitem>

diff --git a/doc/odr.xml b/doc/odr.xml
index 3ae89c5..2824d6c 100644 (file)
--- a/doc/odr.xml
+++ b/doc/odr.xml
@@ -1,4 +1,4 @@
-<!-- $Id: odr.xml,v 1.11 2003-11-19 21:17:26 adam Exp $ -->
+<!-- $Id: odr.xml,v 1.12 2004-03-19 21:12:13 adam Exp $ -->
  <chapter id="odr"><title>The ODR Module</title>
   
   <sect1 id="odr.introduction"><title>Introduction</title>
@@ -17,15 +17,15 @@
     (<xref linkend="odr.use"/>). Only if you need to
     implement ASN.1 beyond that which has been provided, should you
     worry about the second half of the documentation
-    (section <link linkend="odr-prog">Programming with ODR</link>).
+    (<xref linkend="odr.programming"/>).
     If you use one of the higher-level interfaces, you can skip this
     section entirely.
    </para>
 
    <para>
     This is important, so we'll repeat it for emphasis: <emphasis>You do
-    not need to read section <link linkend="odr-prog">Programming with
-    ODR</link> to implement Z39.50 with &yaz;.</emphasis>
+     not need to read <xref linkend="odr.programming"/>
+     to implement Z39.50 with &yaz;.</emphasis>
    </para>
 
    <para>
@@ -478,7 +478,7 @@ void do_nothing_useful(int value)
    </sect2>
   </sect1>
 
-  <sect1 id="odr.programming"><title id="odr-prog">Programming with ODR</title>
+  <sect1 id="odr.programming"><title>Programming with ODR</title>
 
    <para>
     The API of &odr; is designed to reflect the structure of ASN.1, rather
@@ -704,14 +704,14 @@ int odr_oid(ODR o, Odr_oid **p, int optional, const char *name);
       The C OID representation is simply an array of integers, terminated by
       the value -1 (the <literal>Odr_oid</literal> type is synonymous with
       the <literal>int</literal> type).
-      We suggest that you use the OID database module (see section
-      <link linkend="oid">Object Identifiers</link>) to handle object identifiers
+      We suggest that you use the OID database module (see
+      <xref linkend="asn.oid"/>) to handle object identifiers
       in your application.
      </para>
 
     </sect3>
    </sect2>
-   <sect2><title id="tag-prim">Tagging Primitive Types</title>
+   <sect2 id="tag.prim"><title>Tagging Primitive Types</title>
 
     <para>
      The simplest way of tagging a type is to use the
@@ -853,9 +853,8 @@ int mySequence(ODR o, MySequence **p, int optional, const char *name)
 
     <note>
      <para>
-      See section <link linkend="tag-prim">Tagging Primitive types</link>
-      for information on how to tag the primitive types, as well as types
-      that are already defined.
+      See <xref linkend="tag.prim"/> for information on how to tag
+      the primitive types, as well as types that are already defined.
      </para>
     </note>