<chapter id="administration">
- <!-- $Id: administration.xml,v 1.11 2002-10-20 14:02:02 mike Exp $ -->
+ <!-- $Id: administration.xml,v 1.12 2002-10-30 11:09:39 adam Exp $ -->
<title>Administrating Zebra</title>
<!-- ### It's a bit daft that this chapter (which describes half of
the configuration-file formats) is separated from
<para>
Specifies a directory base for Zebra. All relative paths
given (in profilePath, register, shadow) are based on this
- directory. This setting is useful if if you Zebra server
+ directory. This setting is useful if your Zebra server
is running in a different directory from where
<literal>zebra.cfg</literal> is located.
</para>
<chapter id="record-model">
- <!-- $Id: recordmodel.xml,v 1.11 2002-10-20 14:02:03 mike Exp $ -->
+ <!-- $Id: recordmodel.xml,v 1.12 2002-10-30 11:09:39 adam Exp $ -->
<title>The Record Model</title>
<para>
input filter by preparing conversion rules based on regular
expressions and possibly augmented by a flexible scripting language
(Tcl).
- The input filter produces as output an internal representation:
+ The input filter produces as output an internal representation,
+ a tree structure.
</para>
</listitem>
subsequent sections.
Zebra can read structured records in many different formats.
How this is done is governed by additional parameters after the
- "grs" keyboard, separated by "." characters.
+ "grs" keyword, separated by "." characters.
</para>
<para>
Each element is terminated by a closing tag - beginning
with <literal><</literal>/, and containing the same symbolic
tag-name as the corresponding opening tag.
- The general closing tag - <literal><</literal>/> -
+ The general closing tag - <literal></></literal> -
terminates the element started by the last opening tag. The
structuring of elements is significant.
The element <emphasis>Telephone</emphasis>,
<listitem>
<para>
- The Tag set (again, this can consist of several different sets).
+ The tag set (again, this can consist of several different sets).
This is used when reading the records from a file, to recognize the
different tags, and when transmitting the record to the client -
mapping the tags to their numerical representation, if they are