X-Git-Url: http://jsfdemo.indexdata.com/?a=blobdiff_plain;f=doc%2Ffield-structure.xml;h=1387f3b06f13cbd55b9ba71cfb5209168a32e86d;hb=629a83e117bdc40fbec9b3015c834dfa866c86ac;hp=b9fe2edc99bd49fb5964d4d2332b5a74ce764dc5;hpb=97a7adeb9e5059463f039495cc01cfa448463a27;p=idzebra-moved-to-github.git
diff --git a/doc/field-structure.xml b/doc/field-structure.xml
index b9fe2ed..1387f3b 100644
--- a/doc/field-structure.xml
+++ b/doc/field-structure.xml
@@ -29,7 +29,7 @@
- Version 2.1 of Zebra can also be configured - per field - to use the
+ Version 2.0.20 of Zebra can also be configured - per field - to use the
ICU library to perform tokenization and
normalization of strings. This is an alternative to the "charmap"
files which has been part of Zebra since its first release.
@@ -84,9 +84,9 @@
(non-space characters) separated by single space characters
(normalized to " " on display). When completeness is
disabled, each word is indexed as a separate entry. Complete subfield
- indexing is most useful for fields which are typically browsed (eg.
+ indexing is most useful for fields which are typically browsed (e.g.,
titles, authors, or subjects), or instances where a match on a
- complete subfield is essential (eg. exact title searching). For fields
+ complete subfield is essential (e.g., exact title searching). For fields
where completeness is disabled, the search engine will interpret a
search containing space characters as a word proximity search.
@@ -146,7 +146,7 @@
to them:
# Traditional word index
- # Used if completenss is 'incomplete field' (@attr 6=1) and
+ # Used if completeness is 'incomplete field' (@attr 6=1) and
# structure is word/phrase/word-list/free-form-text/document-text
index w
completeness 0
@@ -295,7 +295,7 @@
Curly braces {} may be used to enclose ranges of single
characters (possibly using the escape convention described in the
- preceding point), eg. {a-z} to introduce the
+ preceding point), e.g., {a-z} to introduce the
standard range of ASCII characters.
Note that the interpretation of such a range depends on
the concrete representation in your local, physical character set.
@@ -304,8 +304,8 @@
- paranthesises () may be used to enclose multi-byte characters -
- eg. diacritics or special national combinations (eg. Spanish
+ parentheses () may be used to enclose multi-byte characters -
+ e.g., diacritics or special national combinations (e.g., Spanish
"ll"). When found in the input stream (or a search term),
these characters are viewed and sorted as a single character, with a
sorting value depending on the position of the group in the value
@@ -515,7 +515,7 @@
MARCXML indexing using ICU
The directory examples/marcxml includes
- a complete sample with MARCXML recordst that are DOM XML indexed
+ a complete sample with MARCXML records that are DOM XML indexed
using ICU chain rules. Study the
README in the marcxml
directory for details.