<chapter id="fields-and-charsets">
- <!-- $Id: field-structure.xml,v 1.13 2007-12-19 09:30:29 adam Exp $ -->
<title>Field Structure and Character Sets
</title>
</para>
<para>
- Zebra 1.3 and Zebra 2.0 series require that the field type is
- a single character, e.g. <literal>w</literal> (for word), and
- <literal>p</literal> for phrase. Zebra 2.1 allows field types to
- be any string. This allows for greater flexibility - in particular
+ Zebra 1.3 and Zebra versions 2.0.18 and earlier required that the field
+ type is a single character, e.g. <literal>w</literal> (for word), and
+ <literal>p</literal> for phrase. Zebra 2.0.20 and later allow field types
+ to be any string. This allows for greater flexibility - in particular
per-locale (language) fields can be defined.
</para>
</listitem></varlistentry>
</variablelist>
</para>
- <example>
+ <example id="field-types">
<title>Field types</title>
<para>
Following are three excerpts of the standard
Use the yaz-icu program to test your icuchain rules.
</para>
</tip>
- <example><title>Indexing Greek text</title>
+ <example id="indexing-greek-example"><title>Indexing Greek text</title>
<para>
Consider a system where all "regular" text is to be indexed
using as Greek (locale: EL).
which is an ICU chain version of <filename>default.idx</filename>.
</para>
- <example><title>MARCXML indexing using ICU</title>
+ <example id="indexing-marcxml-example"><title>MARCXML indexing using ICU</title>
<para>
The directory <filename>examples/marcxml</filename> includes
a complete sample with MARCXML recordst that are DOM XML indexed