From 7d77cebae2b7af01eb7211f4ca9860217b3d32cb Mon Sep 17 00:00:00 2001 From: Adam Dickmeiss Date: Tue, 9 Apr 2002 19:20:22 +0000 Subject: [PATCH] spell fixes (using ispell) --- CHANGELOG | 2 +- doc/administration.xml | 18 +++++----- doc/introduction.xml | 4 +-- doc/recordmodel.xml | 22 ++++++------ doc/server.xml | 10 +++--- doc/zebra.xml | 91 +++++++++++++++++++++++++++--------------------- doc/zebra.xml.in | 6 ++-- zebra.spec | 2 +- 8 files changed, 84 insertions(+), 71 deletions(-) diff --git a/CHANGELOG b/CHANGELOG index 4d81c53..568c80e 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -1,5 +1,5 @@ ---- 1.2.0 2002/04/05 +--- 1.2.0 2002/MM/DD Multiple registers. New setting in resource 'root' that holds base directory for register(s). A group a databases may be put in separate diff --git a/doc/administration.xml b/doc/administration.xml index b8c1f04..2486f70 100644 --- a/doc/administration.xml +++ b/doc/administration.xml @@ -1,5 +1,5 @@ - + Administrating Zebra @@ -79,7 +79,7 @@ Indexing is a per-record process, in which either insert/modify/delete will occur. Before a record is indexed search keys are extracted from whatever might be the layout the original record (sgml,html,text, etc..). - The Zebra system currently supports two fundamantal types of records: + The Zebra system currently supports two fundamental types of records: structured and simple text. To specify a particular extraction process, use either the command line option -t or specify a @@ -99,7 +99,7 @@ You can edit the configuration file with a normal text editor. - parameter names and values are seperated by colons in the file. Lines + parameter names and values are separated by colons in the file. Lines starting with a hash sign (#) are treated as comments. @@ -318,7 +318,7 @@ Locating Records - The default behaviour of the Zebra system is to reference the + The default behavior of the Zebra system is to reference the records from their original location, i.e. where they were found when you ran zebraidx. That is, when a client wishes to retrieve a record @@ -418,7 +418,7 @@ disk space than simpler indexing methods, but it makes it easier for you to keep the index in sync with a frequently changing set of data. If you combine this system with the safe update - facility (see below), you never have to take your server offline for + facility (see below), you never have to take your server off-line for maintenance or register updating purposes. @@ -472,7 +472,7 @@ Indexing with General Record IDs - When using this method you construct an (almost) arbritrary, internal + When using this method you construct an (almost) arbitrary, internal record key based on the contents of the record itself and other system information. If you have a group of records that explicitly associates an ID with each record, this method is convenient. For example, the @@ -642,8 +642,8 @@ For instance, if you have allocated two disks for your register, and the first disk is mounted - on /d1 and has 200 Mb of free space and the - second, mounted on /d2 has 300 Mb, you could + on /d1 and has 200 MB of free space and the + second, mounted on /d2 has 300 MB, you could put this entry in your configuration file: @@ -658,7 +658,7 @@ your responsibility to ensure that enough space is available, and that other applications do not attempt to use the free space. In a large production system, it is recommended that you allocate one or more - filesystem exclusively to the Zebra register files. + file system exclusively to the Zebra register files. diff --git a/doc/introduction.xml b/doc/introduction.xml index 7ea322d..2175218 100644 --- a/doc/introduction.xml +++ b/doc/introduction.xml @@ -1,5 +1,5 @@ - + Introduction @@ -7,7 +7,7 @@ The Zebra system is a fielded free-text indexing and retrieval engine with a - Z39.50 frontend. You can use any commercial or freeware Z39.50 client + Z39.50 front-end. You can use any commercial or free-ware Z39.50 client to access data stored in Zebra. diff --git a/doc/recordmodel.xml b/doc/recordmodel.xml index d9e5006..0eb13de 100644 --- a/doc/recordmodel.xml +++ b/doc/recordmodel.xml @@ -1,5 +1,5 @@ - + The Record Model @@ -132,7 +132,7 @@ This allows Zebra to read records in the ISO2709 (MARC) encoding standard. In this case, the - last paramemeter abstract syntax names the + last parameter abstract syntax names the .abs file (see below) which describes the specific MARC structure of the input record as well as the indexing rules. @@ -188,7 +188,7 @@ The indentation used above is used to illustrate how Zebra - interprets the markup. The indentation, in itself, has no + interprets the mark-up. The indentation, in itself, has no significance to the parser for the canonical input format, which discards superfluous whitespace. @@ -431,7 +431,7 @@ FINISH - The expression asssociated with this pattern is evaluated + The expression associated with this pattern is evaluated once, before the application terminates. It can be used to release system resources - typically ones allocated in the INIT step. @@ -469,7 +469,7 @@ record - Begin a new record. The followingparameter should be the + Begin a new record. The following parameter should be the name of the schema that describes the structure of the record, eg. gils or wais (see below). The begin record call should precede @@ -826,7 +826,7 @@ Generally, settings are characterized by a single keyword, identifying the setting, followed by a number of parameters. Some settings are repeatable (r), while others may occur only once in a - file. Some settings are optional (o), whicle others again are + file. Some settings are optional (o), while others again are mandatory (m). @@ -1183,7 +1183,7 @@ The names parameter is a list of names by which the tag should be recognized in the input file format. The names should be separated by slashes (/). - The type is th recommended datatype of + The type is the recommended data type of the tag. It should be one of the following: @@ -1697,8 +1697,8 @@ (preceded by x). In addition, the combinations \\, \\r, \\n, \\t, \\s (space — remember that real - space-characters may ot occur in the value definition), and - \\ are recognised, with their usual interpretation. + space-characters may not occur in the value definition), and + \\ are recognized, with their usual interpretation. @@ -1706,7 +1706,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 entroduce the + preceding point), eg. {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. @@ -1806,7 +1806,7 @@ - SUTRS. Again, the mapping is fairly straighforward. Indentation + SUTRS. Again, the mapping is fairly straightforward. Indentation is used to show the hierarchical structure of the record. All "GRS" type records support both the GRS-1 and SUTRS representations. diff --git a/doc/server.xml b/doc/server.xml index ae02803..382a634 100644 --- a/doc/server.xml +++ b/doc/server.xml @@ -1,5 +1,5 @@ - + The Z39.50 Server @@ -52,7 +52,7 @@ Use the Z39.50 protocol (default). These two options complement - eachother. You can use both multiple times on the same command + each other. You can use both multiple times on the same command line, between listener-specifications (see below). This way, you can set up the server to listen for connections in both protocols concurrently, on different local ports. @@ -121,7 +121,7 @@ Set the (approximate) maximum size of - present response messages. Default is 1024 Kb (1 Mb). + present response messages. Default is 1024 KB (1 MB). @@ -204,7 +204,7 @@ Z39.50 protocol, and the option bits for Search, Present, Scan, NamedResultSets, and concurrentOperations will be set, if requested by the client. The maximum PDU size is negotiated down to a maximum of - 1Mb by default. + 1 MB by default. @@ -488,7 +488,7 @@ Sort - Z39.50 specifies three diffent types of sort criterias. + Z39.50 specifies three different types of sort criteria. Of these Zebra supports the attribute specification type in which case the use attribute specifies the "Sort register". Sort registers are created for those fields that are of type "sort" in diff --git a/doc/zebra.xml b/doc/zebra.xml index c1845b5..5d0ad29 100644 --- a/doc/zebra.xml +++ b/doc/zebra.xml @@ -11,44 +11,57 @@ ]> + - - -Zebra Server - Administrators's Guide and Reference - -SebastianHammer - - -AdamDickmeiss - - -1995-2002 -Index Data - - - - -The Zebra information server combines a versatile fielded/free-text -search engine with a Z39.50-1995 frontend to provide a powerful and flexible -information management system. This document explains the procedure for -installing and configuring the system, and outlines the possibilities -for managing data and providing Z39.50 -services with the software. - - -This manual covers version 1.2.0 of Zebra. - - - - -&chap-introduction; -&chap-installation; -&chap-quickstart; -&chap-administration; -&chap-zebraidx; -&chap-server; -&chap-recordmodel; -&app-license; -&app-indexdata; - + + Zebra Server - Administrators's Guide and Reference + + SebastianHammer + + + AdamDickmeiss + + + 1995-2002 + Index Data + + + + The Zebra information server combines a versatile fielded/free-text + search engine with a Z39.50-1995 frontend to provide a powerful and + flexible information management system. + This document explains the procedure for installing and + configuring the system, and outlines the possibilities for + managing data and providing Z39.50 services with the software. + + + This manual covers version 1.2.0 of Zebra. + + + + + &chap-introduction; + &chap-installation; + &chap-quickstart; + &chap-administration; + &chap-zebraidx; + &chap-server; + &chap-recordmodel; + &app-license; + &app-indexdata; + + diff --git a/doc/zebra.xml.in b/doc/zebra.xml.in index ef6956a..74ea169 100644 --- a/doc/zebra.xml.in +++ b/doc/zebra.xml.in @@ -11,10 +11,10 @@ ]> - + - Zebra Server - Administrators's Guide and Reference + Zebra Server - Administrators' Guide and Reference SebastianHammer @@ -28,7 +28,7 @@ The Zebra information server combines a versatile fielded/free-text - search engine with a Z39.50-1995 frontend to provide a powerful and + search engine with a Z39.50-1995 front-end to provide a powerful and flexible information management system. This document explains the procedure for installing and configuring the system, and outlines the possibilities for diff --git a/zebra.spec b/zebra.spec index 42e0307..6518a20 100644 --- a/zebra.spec +++ b/zebra.spec @@ -13,7 +13,7 @@ Summary: Zebra: a fielded free-text engine with a Z39.50 frontend. %description Zebra is a fielded free-text indexing and retrieval engine with a Z39.50 -frontend. You can use any compatible, commercial or freeware Z39.50 client to +front-end. You can use any compatible, commercial or freeware Z39.50 client to access data stored in Zebra. Zebra may be used free-of-charge in non-profit applications by non-commercial organisations. -- 1.7.10.4