From: Adam Dickmeiss Date: Fri, 19 Mar 2004 21:12:13 +0000 (+0000) Subject: Fix a few links. Mention zlib. X-Git-Tag: YAZ.2.0.18~3 X-Git-Url: http://sru.miketaylor.org.uk/?a=commitdiff_plain;h=4cc34f9a4eec65d0eb629d070150dd55c5977522;p=yaz-moved-to-github.git Fix a few links. Mention zlib. --- diff --git a/doc/asn.xml b/doc/asn.xml index 854bc0b..adf59de 100644 --- a/doc/asn.xml +++ b/doc/asn.xml @@ -1,4 +1,4 @@ - + The Z39.50 ASN.1 Module Introduction @@ -132,7 +132,7 @@ - Object Identifiers + Object Identifiers When you refer to object identifiers in your application, you need to be aware that SR and Z39.50 use two different set of OIDs to refer to diff --git a/doc/frontend.xml b/doc/frontend.xml index 3c2a701..81366b8 100644 --- a/doc/frontend.xml +++ b/doc/frontend.xml @@ -1,4 +1,4 @@ - + Generic server Introduction @@ -546,10 +546,10 @@ typedef struct bend_fetch_rr { that holds the reference to the desired record. The number is the offset into the set (with 1 being the first record in the set). The format field - is the record format requested by the client (See section - Object Identifiers). The value - VAL_NONE indicates that the client did not - request a specific format. The stream argument + is the record format requested by the client (See + ). + The value VAL_NONE indicates that the client did + not request a specific format. The stream argument is an &odr; stream which should be used for allocating space for structured data records. The stream will be reset when all records have been assembled, and diff --git a/doc/installation.xml b/doc/installation.xml index 7dd9986..0d12c23 100644 --- a/doc/installation.xml +++ b/doc/installation.xml @@ -1,4 +1,4 @@ - + Compilation and Installation Introduction @@ -491,7 +491,7 @@ (cql.y). - GNU Bison for Windows is part of + A Windows version of GNU Bison is part of unxutils. @@ -514,12 +514,20 @@ If HAVE_LIBXML2 is set to 1, YAZ is compiled with SRW (and SOAP) support. In this configuration, set LIBXML2_DIR to the - libxml2 source directory. + libxml2 source directory + and + ZLIB_DIR to the zlib directory. + + + Note that YAZ is not using ZLIB. But libxml2 is. + + + - Windows versions of libxml2 and iconv can be found - + Windows versions of libxml2, zlib and iconv can be found + here. diff --git a/doc/odr.xml b/doc/odr.xml index 3ae89c5..2824d6c 100644 --- a/doc/odr.xml +++ b/doc/odr.xml @@ -1,4 +1,4 @@ - + The ODR Module Introduction @@ -17,15 +17,15 @@ (). Only if you need to implement ASN.1 beyond that which has been provided, should you worry about the second half of the documentation - (section Programming with ODR). + (). If you use one of the higher-level interfaces, you can skip this section entirely. This is important, so we'll repeat it for emphasis: You do - not need to read section Programming with - ODR to implement Z39.50 with &yaz;. + not need to read + to implement Z39.50 with &yaz;. @@ -478,7 +478,7 @@ void do_nothing_useful(int value) - Programming with ODR + Programming with ODR The API of &odr; is designed to reflect the structure of ASN.1, rather @@ -704,14 +704,14 @@ int odr_oid(ODR o, Odr_oid **p, int optional, const char *name); The C OID representation is simply an array of integers, terminated by the value -1 (the Odr_oid type is synonymous with the int type). - We suggest that you use the OID database module (see section - Object Identifiers) to handle object identifiers + We suggest that you use the OID database module (see + ) to handle object identifiers in your application. - Tagging Primitive Types + Tagging Primitive Types The simplest way of tagging a type is to use the @@ -853,9 +853,8 @@ int mySequence(ODR o, MySequence **p, int optional, const char *name) - See section Tagging Primitive types - for information on how to tag the primitive types, as well as types - that are already defined. + See for information on how to tag + the primitive types, as well as types that are already defined.