Minor changes here and there. Still FIXMEs left.

diff --git a/doc/administration.xml b/doc/administration.xml
index 5ebfcd3..51d3025 100644 (file)
--- a/doc/administration.xml
+++ b/doc/administration.xml
@@ -1,5 +1,5 @@
 <chapter id="administration">
- <!-- $Id: administration.xml,v 1.6 2002-08-28 08:14:47 mike Exp $ -->
+ <!-- $Id: administration.xml,v 1.7 2002-10-10 14:27:18 heikki Exp $ -->
  <title>Administrating Zebra</title>
  
  <para>
@@ -436,9 +436,8 @@
    in order to modify the indexes correctly at a later time.
   </para>
   
-  <para>
-   FIXME - There must be a simpler way to do this with Adams string tags -H
-  </para>
+   <!--FIXME - There must be a simpler way to do this with Adams string tags -H
+     -->
 
   <para>
    For example, to update records of group <literal>esdd</literal>
@@ -776,14 +775,13 @@
     In order to make changes to the system take effect for the
     users, you'll have to submit a "commit" command after a
     (sequence of) update operation(s).
-    You can ask the indexer to commit the changes immediately
-    after the update operation:
    </para>
    
    <para>
     
     <screen>
-     $ zebraidx update /d1/records update /d2/more-records commit
+     $ zebraidx update /d1/records 
+     $ zebraidx commit
     </screen>
     
    </para>
@@ -795,7 +793,7 @@
    <para>
     
     <screen>
-     $ zebraidx -g books update /d1/records update /d2/more-records
+     $ zebraidx -g books update /d1/records  /d2/more-records
      $ zebraidx -g fun update /d3/fun-records
      $ zebraidx commit
     </screen>

diff --git a/doc/examples.xml b/doc/examples.xml
index 53f839d..f2af444 100644 (file)
--- a/doc/examples.xml
+++ b/doc/examples.xml
@@ -1,5 +1,5 @@
 <chapter id="examples">
- <!-- $Id: examples.xml,v 1.7 2002-10-08 08:09:43 mike Exp $ -->
+ <!-- $Id: examples.xml,v 1.8 2002-10-10 14:27:18 heikki Exp $ -->
  <title>Example Configurations</title>
 
  <sect1>
@@ -150,6 +150,7 @@
     $ zebraidx update records
     00:45:46-08/10: ../../index/zebraidx(5016) [warn] records/genera.xml:0 Couldn't open GENUS.abs [No such file or directory]
    </screen>
+   <!-- FIXME ### This needs more text -->
   </para>
  </sect1>
 </chapter>
@@ -161,7 +162,7 @@
      The master configuration file, <literal>zebra.cfg</literal>,
      which is as short and simple as it can be:
      <screen>
-       # $Header: /home/cvsroot/idis/doc/examples.xml,v 1.7 2002-10-08 08:09:43 mike Exp $
+       # $Header: /home/cvsroot/idis/doc/examples.xml,v 1.8 2002-10-10 14:27:18 heikki Exp $
        # Bare-bones master configuration file for Zebra
        profilePath: .:../../tab:../../../yaz/tab
      </screen>
@@ -178,7 +179,7 @@
      The BIB-1 attribute set configuration file,
      <literal>bib1.att</literal>, which is also as short as possible:
      <screen>
-       # $Header: /home/cvsroot/idis/doc/examples.xml,v 1.7 2002-10-08 08:09:43 mike Exp $
+       # $Header: /home/cvsroot/idis/doc/examples.xml,v 1.8 2002-10-10 14:27:18 heikki Exp $
        # Bare-bones BIB-1 attribute set file for Zebra
        reference Bib-1
      </screen>

diff --git a/doc/introduction.xml b/doc/introduction.xml
index e305382..d93603c 100644 (file)
--- a/doc/introduction.xml
+++ b/doc/introduction.xml
@@ -1,5 +1,5 @@
 <chapter id="introduction">
- <!-- $Id: introduction.xml,v 1.14 2002-10-08 08:09:43 mike Exp $ -->
+ <!-- $Id: introduction.xml,v 1.15 2002-10-10 14:27:18 heikki Exp $ -->
  <title>Introduction</title>
  
  <sect1>
@@ -109,7 +109,7 @@
       Zebra is written in portable C, so it runs on most Unix-like systems 
       as well as Windows NT.  A binary distribution for Windows NT is
       available at
-      <ulink url="http://indexdata.dk/zebra/###"/>
+      <ulink url="http://ftp.indexdata.dk/pub/zebra/win32/">
      </para>
     </listitem>
     
@@ -315,13 +315,16 @@
    announcements from the authors (new
    releases, bug fixes, etc.) and general discussion.  You are welcome
    to seek support there.  Join by sending email to
-   <email>zebra-subscribe-###@mailman.indexdata.dk</email>
+   <email>zebra-request@indexdata.dk</email>. Put the word 'subscribe'
+   in the body of the message.
+   <!-- zebra-subscribe-###@mailman.indexdata.dk-->
   </para>
   <para>
    Third, it's possible to buy a commercial support contract, with
    well defined service levels and response times, from Index Data.
    See
-   <ulink url="http://www.indexdata.dk/support/###"/>
+   <ulink url="http://www.indexdata.dk/support/?lang=en"/>
+   <!-- ulink url="http://www.indexdata.dk/support/###"/-->
    for details.
   </para>
  </sect1>  
@@ -390,7 +393,7 @@
   <para>
    If you think it's all really neat, you're welcome to drop us a line
    saying that, too. You can email us on
-   <email>indo@indexdata.dk</email>
+   <email>info@indexdata.dk</email>
    or check the contact info at the end of this manual.
   </para>
   

diff --git a/doc/recordmodel.xml b/doc/recordmodel.xml
index 960cc37..87db1df 100644 (file)
--- a/doc/recordmodel.xml
+++ b/doc/recordmodel.xml
@@ -1,5 +1,5 @@
  <chapter id="record-model">
-  <!-- $Id: recordmodel.xml,v 1.5 2002-08-28 09:39:45 mike Exp $ -->
+  <!-- $Id: recordmodel.xml,v 1.6 2002-10-10 14:27:18 heikki Exp $ -->
   <title>The Record Model</title>
   
   <para>
@@ -198,14 +198,17 @@
 
     </para>
 
-    <note>
-     <para>
+    <!-- There is no indentation in the example above!  -H
+    -note-
+     -para-
       The indentation used above is used to illustrate how Zebra
       interprets the mark-up. The indentation, in itself, has no
       significance to the parser for the canonical input format, which
       discards superfluous whitespace.
-     </para>
-    </note>
+     -/para-
+    -/note-
+    -->
+
     <para>
      The keywords surrounded by &lt;...&gt; are
      <emphasis>tags</emphasis>, while the sections of text
@@ -607,6 +610,7 @@
      ROOT 
      AUTHOR    "Robert Pirsig"
     </screen>
+   <!-- FIXME That screen makes no sense! -H  -->
 
    </para>
 
@@ -624,6 +628,7 @@
      AUTHOR
      SURNAME    "Pirsig"
     </screen>
+   <!-- FIXME That screen makes even less sense! -H  -->
 
    </para>