<chapter id="examples">
- <!-- $Id: examples.xml,v 1.12 2002-10-18 08:31:37 mike Exp $ -->
+ <!-- $Id: examples.xml,v 1.15 2002-10-30 14:45:42 adam Exp $ -->
<title>Example Configurations</title>
<sect1>
driven by a master configuration file, which may refer to other
subsidiary configuration files. By default, they try to use
<filename>zebra.cfg</filename> in the working directory as the
- master file; but this can be changed using the <literal>-t</literal>
+ master file; but this can be changed using the <literal>-c</literal>
option to specify an alternative master configuration file.
</para>
<para>
minimal file that just tells <literal>zebraidx</literal> where to
find the default indexing rules, and how to parse the records:
<screen>
- profilePath: .:../../tab:../../../yaz/tab
+ profilePath: .:../../tab
recordType: grs.sgml
</screen>
</para>
was perhaps the tallest. With its head raised, it stood 60 feet (nearly
20 m) tall. </P>
</ESSAY>
-
<idzebra xmlns="http://www.indexdata.dk/zebra/">
- <size>593</size>
- <localnumber>891</localnumber>
- <filename>records/genera.xml</filename>
- </idzebra>
+ <size>593</size>
+ <localnumber>891</localnumber>
+ <filename>records/genera.xml</filename>
+ </idzebra>
</GENUS>
</screen>
</para>
structure of the documents in order to find them. For example,
when we wanted to know the genera for which Matt Wedel is an
author
- (<phrase role="taxon">Sauroposeidon proteles</phrase>),
+ (<foreignphrase role="taxon">Sauroposeidon proteles</foreignphrase>),
we had to formulate a complex XPath
<literal>1=/GENUS/SPECIES/AUTHOR/@name</literal>
which embodies the knowledge that author names are specified in the