Changeset 265

yaz/trunk/fuentes/ChangeLog

-                      r255
+                      r265
+commit 738b345708b245e67cded6d917393a80b5bd4eca
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Jan 11 13:06:41 2016 +0000
+    Version 5.15.2
+commit f43944a7ffc80bfcf8ec6a5ec1935c354d4bcac2
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Jan 11 11:04:38 2016 +0100
+    Happy new year
+commit d35bb455afe361c1f8ed360cce55e8fb75c6eec7
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Jan 11 11:04:11 2016 +0100
+    Mention configure as a script
+commit 2eb6e27fe677e40f53327f5af456d39df5b24edf
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Jan 11 11:01:00 2016 +0100
+    Mention Github + buildconf.sh
+commit ccfd0bb7d8af350d358e70a3b4bedb289e2be042
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Jan 11 11:00:15 2016 +0100
+    Update list of Debian packages for buildconf.sh
+commit 4c57a37b6ff798585433440641d9c86a25c9092c
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Jan 6 11:26:26 2016 +0100
+    Use submodules from Github
+commit 7b112287740b44d1dd939cea0ecca217356affd5
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Thu Nov 26 10:06:18 2015 +0100
+    No more manifest files
+commit d4514445a1caea19faff82c3541a716ddfdc2b0f
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Nov 24 14:14:20 2015 +0100
+    Include links to pre-compiled ICU binaries
+commit b687939804570b289122ca78f25b5f255ed36326
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Nov 24 14:14:11 2015 +0100
+    Update list of supported platforms
+commit 05f7afcaa053728864a9b1b6d7bd1a6a48701f2c
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Nov 24 14:13:35 2015 +0100
+    Update doc/common
+commit ebfa76b327665398553785b6a00e69d119ba9297
+Merge: b1a5a64 4e71d4a
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Nov 24 13:54:30 2015 +0100
+    Merge branch 'master' of ssh://git.indexdata.com:222/home/git/pub/yaz
+commit b1a5a6402e767afee10073381d842642d3a640d0
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Nov 24 13:52:36 2015 +0100
+    Win32/64 split. Use ICU compiled with VS2015
+commit 4e71d4a715bca8fc6a9a1010ffa00def8c63ab1b
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Nov 17 15:14:06 2015 +0100
+    Remove <info> from ref entry header
+commit 81358822816ed75a14af31a0656550de1329c33a
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Nov 16 16:01:50 2015 +0100
+    README.md
+commit 319ea8d6f518d08c1f50d8ec80899e1bc6ca7923
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Nov 16 13:27:13 2015 +0100
+    Update URL for Bison Windows version
+    It used to be part of Git for Windows. It no longer is.
+commit 02b4f0ab937b62d892d3e0918439da770fe720c2
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Thu Nov 12 08:54:19 2015 +0000
+    Version 5.15.1
+commit 2bfb0b990bbbe0f9c5ef9e78b094a2063bc45f33
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Thu Nov 12 09:48:02 2015 +0100
+    Add test case for YAZ-861 YAZ-865
+commit 8484857deb143d2a71498d3b8b7a345328dac969
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Nov 11 21:52:15 2015 +0100
+    sha1: Work around older VS compilers
+commit 92e9ead954f1292391afde93235f0fd25891da8e
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Nov 11 21:51:05 2015 +0100
+    Current YAZ are made with VS 2015
+commit a6b61b9f8b6576e8159a4e7e6aee88bba7e5d07d
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Nov 11 15:32:28 2015 +0100
+    Avoid using non-portable debian.h
+    Instead use autoconf's AC_C_BIGENDIAN
+commit 4eb90d87b9374b30b8ea4f9d5e70d509a11d9a58
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Nov 11 14:50:27 2015 +0100
+    Fix rpn2cql fails for Bib-1 set in qry+conf YAZ-865
+commit 94a0aa1a3d45b41484ac4bf81b85f90dca7f7181
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Nov 11 14:13:31 2015 +0100
+    Bundle sha1 rather than use libgcrypt/nettle
+commit 1b29294f1ba913fb798c3556e3fda09bfc46bb67
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Nov 11 09:04:25 2015 +0000
+    Version 5.15.0
+commit 71e94b6a27e3dd1dcd8a781254a4c329de020f34
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Nov 11 09:03:41 2015 +0000
+    Add Ubuntu Wily Werewolf
+commit 240156e69d3a6390699644756e367fffd42891d1
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Nov 10 13:47:18 2015 +0100
+    CCL: fix other inherited attributes
+commit 31596bdcae098f8acea695d44c44ee5f646b4c1f
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Nov 10 13:26:00 2015 +0100
+    CCL: fix r=o, r=r WRT inherited attributes YAZ-864
+commit 13da404f1294cb29e30100e71b76c4b44e06cf89
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Nov 9 12:48:24 2015 +0000
+    Version 5.14.12
+commit 8b9999744362603b448a74f779ff7a2b4d76c89d
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Nov 9 13:47:46 2015 +0100
+    Set VS_REDIST_EXE for all architectures
+commit dae688b0b3ebe96d6b65385b2fa0e627ab6ce451
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Nov 9 13:29:01 2015 +0100
+    No more reachable memory with yaz_deinit_globals
+    At least when nettle is in use (libgcrypt is hopeless)
+commit 84153486e91926be04dd28d4f2bda6c6ade0e005
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Nov 9 12:01:12 2015 +0000
+    Revert "Build without redis on Debian squeeze, Ubuntu Lucid"
+    This reverts commit ad2e8b3190adb77733a744a26a08927ed026396d.
+    We don't build for Debian squeeze and Ubuntu Lucid anymore, so this
+    hack is redundant.
+    Conflicts:
+        debian/control
+        debian/rules
+commit 2487937ef218d16b41294bf7d1845d164e17bfe2
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Nov 9 11:55:39 2015 +0000
+    Build with nettle on Debian/Ubuntu
+commit 60f0955d87a511503ce48de0e99f697e112ff3d0
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Nov 9 12:45:04 2015 +0100
+    Allow use of Nettle as an alternative to gcrypt
+commit 756129c2a4eaa8a0cc4e0acbc8b401083024c1e2
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Nov 9 12:00:14 2015 +0100
+    yaz_deinit_globals closes FILE log
+commit eec02e3b60802638aa3a105f3037814cf32af3b6
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Thu Nov 5 12:50:26 2015 +0100
+    cs_get_host_args: allow unix:path:args notation
+commit 7207680c8f685c9ed33536bfd4a4878cb2616d99
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Oct 28 11:08:40 2015 +0100
+    Build with VS 2015 (2014 runtime)
+commit 70ce06b6fcbe3a53e94111ecedf0312848647c1b
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Oct 28 11:08:01 2015 +0100
+    Fix registry keys for VC runtime
+commit a4a4e9d375bfbcc823e8b3820ffb23272e919004
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Oct 27 15:40:03 2015 +0100
+    Prepare to bundle VC 2015 Runtime 14.0.23026
+commit 917d2c4a288a19c0da7fa98ad514288d0e045413
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Oct 27 15:39:38 2015 +0100
+    make64 does not build yaz4j
+commit d438b90ac17fbae25ba2554dd76f4e156f420437
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Thu Oct 22 16:31:26 2015 +0200
+    Cleanup de-init function YAZ-863
+    New function yaz_deinit_globals
+commit 7cf33bcd4c625c2197101ebffd38513e44271be6
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Fri Oct 9 15:09:34 2015 +0000
+    Version 5.14.11
+commit 59830038599648515b34784fbab8f5befa63e185
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Fri Oct 9 15:09:17 2015 +0000
+    Remove Ubuntu utopic
+commit e8001c3381e00a846e96fab5a1c6f7ca00df4f55
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Fri Oct 9 16:15:42 2015 +0200
+    Fix RPN to CQL rejects local Bib-1 attribute set YAZ-861
+commit 39671a069c30f6cc508de7692f49a01f413a5a16
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Oct 7 16:06:25 2015 +0200
+    cs_errmsg never writes to static buffer
+    For the CSYSERR applications should check errno themselves
+commit ab99e2d94176eef3b1b23ef3f0f180c6d5077ea6
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Oct 7 16:04:43 2015 +0200
+    ZOOM C: tweak when connection failed is returned
+    For cases with multiple socket addresses for some hostname, eg
+    localhost IPV4+IPV6, the code now properly returns "connection
+    failed" rather than "connection lost".
+commit 38f746ee0f3da5e620bbf3b60eb2ccc1bc647d19
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Oct 7 11:29:21 2015 +0200
+    Update doc/common
+commit 323805b6779bcf1befdc7cdd7f10c23b06885e0d
+Author: David Crossley <dcrossley@indexgeo.com.au>
+Date:   Wed Oct 7 12:57:33 2015 +1100
+    Various minor text tweaks.
+commit 0ec12c344e05f3637af9f48e6aa28a54d99f8343
+Author: David Crossley <dcrossley@indexgeo.com.au>
+Date:   Mon Oct 5 15:22:20 2015 +1100
+    Various minor text tweaks.
+commit 2a624ff1daa841601aebca86c0196039da6978b3
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Sep 16 14:21:04 2015 +0200
+    Fix windows uninstall does not remove start menu shortcuts YAZ-860
+commit 3cdd02c11b85c98430021bbc6413fcceda754354
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Sep 16 09:10:07 2015 +0000
+    Version 5.14.10
+commit 4db60a9b1f537de4c0f04587b44be32d0701a64f
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Sep 15 19:43:54 2015 +0200
+    prevent huge expansions in CCL s=sl YAZ-859
+commit ba19dacdfe290bee024a23673a6e75f451e2c013
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Sep 15 09:02:49 2015 +0000
+    Version 5.14.9
+commit 1426a3da9b0390bb0d928a6ee56ebf5fa0ceb0ef
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Sep 15 10:13:27 2015 +0200
+    Fix segv in ZOOM_connection_fire_event_socket YAZ-858
+    The odr_in memory taken by handle_srw_response, and, thus if result
+    set is destructed before we expect the HTTP response (hres) it may
+    be come invalid. Therefore we inspect hres before the call to
+    ZOOM_handle_sru.
+commit 7c6b3363478950a3a5c7f448e5bfa6f4ea19fbab
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Sep 15 10:05:10 2015 +0200
+    Fix possible deadlock in backtrace (2nd attempt) YAZ-856
+    An alarm is set up so that backtrace is terminated if it hangs.
+    Even if backtrace the handler also attempts to spawn gdb.
+commit 30af0a1ebbea75c3e757eb03d3f988c61fce8511
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Sep 14 13:53:34 2015 +0000
+    Version 5.14.8
+commit c5b92d32f5619eae0b99c4bfb39374e8ef675e34
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Sep 14 15:49:47 2015 +0200
+    Remove ununsed function ccl_rpn_dup
+commit 4f3f16d519137001a916178e28ad1dff8b986a7d
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Sep 14 15:48:43 2015 +0200
+    Fix SEGV for s=sl for 3 terms and syntax error YAZ-857
+commit de94629a46584eafe114f740ed3000b26dd42ffb
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Sun Sep 13 19:31:45 2015 +0000
+    Version 5.14.7
+commit fcb40f9ed16ce6a8ef86997890057af0f7692377
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Sun Sep 13 21:12:40 2015 +0200
+    backtrace: add \n in error msg
+commit 7cda3530b0d64128462118433a9f69645f49a39b
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Sun Sep 13 21:08:30 2015 +0200
+    Fix possible deadlock in backtrace YAZ-856
+commit b0afe9a4eb412d5d605450ea715dcd033f45b878
+Merge: e94e943 a7261ce
+Author: Wolfram Schneider <wosch@indexdata.dk>
+Date:   Tue Sep 8 12:21:49 2015 +0000
+    Merge branch 'master' of ssh://git.indexdata.com:222/home/git/pub/yaz
+commit e94e943c08f4f9265c2ff211d74984166b289841
+Author: Wolfram Schneider <wosch@indexdata.dk>
+Date:   Tue Sep 8 11:45:37 2015 +0000
+    documentation: libreadline5-dev is retired, recommend to install libreadline-gplv2-dev
+commit 44c26c79fddc6d28b4da0a0fd5788eca526b390e
+Author: Wolfram Schneider <wosch@indexdata.dk>
+Date:   Tue Sep 8 11:42:23 2015 +0000
+    update documentation / help text
+commit a7261ce1171ca8e90561b2055e6198e15208bcd6
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Sep 8 09:02:05 2015 +0200
+    Fix docpath example
+commit a996c33edb96a3273c81d799189b33437ad6ae18
+Author: David Crossley <dcrossley@indexgeo.com.au>
+Date:   Tue Sep 8 14:10:10 2015 +1000
+    Various minor text tweaks.
+commit 086d0dd7b180c786daf78359e1a7b94c656dd855
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Sep 7 17:26:20 2015 +0200
+    yaz-ztest: set named_result_sets flag
+commit d802116821b20c1dac70011b1ff36edfc4a3119b
+Author: David Crossley <dcrossley@indexgeo.com.au>
+Date:   Thu Sep 3 15:53:19 2015 +1000
+    Various minor text tweaks.
+commit f332be40c2edee783d37633597b4f7ac3b22fc3e
+Author: David Crossley <dcrossley@indexgeo.com.au>
+Date:   Wed Sep 2 12:26:12 2015 +1000
+    Refer to full name of Apache products at first mention, as per ASF trademark guidelines.
+commit 3b046fa5df64b76cc6a28f562c135c06d7a428a7
+Author: David Crossley <dcrossley@indexgeo.com.au>
+Date:   Wed Sep 2 12:19:38 2015 +1000
+    Various minor text tweaks.
+commit 02ef0ddc8ff17fa5053089af7d5d93ea1f2182ea
+Author: David Crossley <dcrossley@indexgeo.com.au>
+Date:   Wed Sep 2 12:18:15 2015 +1000
+    Various minor text tweaks.
+commit 87faebe8ef5cab8f6df86f387e8b919b7b9897a8
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Aug 17 12:41:33 2015 +0000
+    Version 5.14.6
+commit 473f3071b86a40479e38e3fe4d434c0d2bf03379
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Mon Aug 17 14:38:01 2015 +0200
+    Fix yaz-client command args parsing broken YAZ-855
+    Bug introduced in 5be87e7a04c7219b31cefc0a3
+commit 686414b0ac6446cd55610d5203d61a32672e2203
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Thu Aug 6 10:23:41 2015 +0000
+    Version 5.14.5
+commit 7673cf27f5be351a18a5d3ea1baf6c4aee06eb3b
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Aug 5 13:43:22 2015 +0000
+    Remove Debian squeeze (compat 8)
+commit 8e27c4a44da61c8d639187f2b914ef7d432baed5
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Aug 5 15:29:19 2015 +0200
+    debian compat 9 YAZ-854
+commit d7909431b9e73132e227463279bc8fe614c49184
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Aug 5 13:23:29 2015 +0200
+    rpn2cql diagnostics: provide use attribute addinfo YAZ-853
+commit 5ae31048f134f9f9db937db6847edef583123a90
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Aug 4 12:19:09 2015 +0000
+    deb: deprecated substitution ${Source-Version} YAZ-852
+commit 5be87e7a04c7219b31cefc0a3bd02fe5a255430c
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Jul 29 15:36:51 2015 +0200
+    Fix yaz-client: semicolon terminates arguments YAZ-851
+commit f575db041e99b9c7455e5251fe677d145c98f6f0
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Wed Jul 29 08:54:34 2015 +0000
+    Version 5.14.4
+commit eb556013557ef8c9e76c52614f88c059ec443c95
+Author: Adam Dickmeiss <adam@indexdata.dk>
+Date:   Tue Jul 28 13:04:55 2015 +0200
+    Solr >= 5.1 / content type text/xml YAZ-850
 commit 74168354bcd4a020093adb4a1c0981e35ed340db
 Author: Adam Dickmeiss <adam@indexdata.dk>

yaz/trunk/fuentes/IDMETA

-                      r255
+                      r265
 DEBIAN_DIST="jessie wheezy squeeze"
 UBUNTU_DIST="vivid utopic trusty precise"
+DEBIAN_DIST="jessie wheezy"
+UBUNTU_DIST="wily vivid trusty precise"
 CENTOS_DIST="centos5 centos6 centos7"
 VERSION=5.14.3
+VERSION=5.15.2

yaz/trunk/fuentes/LICENSE

r255	r265
1		Copyright (c) 1995-2015, Index Data
	1	Copyright (c) 1995-2016, Index Data
2	2	All rights reserved.
3	3	Redistribution and use in source and binary forms, with or without

yaz/trunk/fuentes/Makefile.am

r255	r265
17	17
18	18	SPEC_FILE=$(PACKAGE).spec
19		EXTRA_DIST=$(SPEC_FILE) IDMETA README LICENSE NEWS m4/id-config.sh \
	19	EXTRA_DIST=$(SPEC_FILE) IDMETA README.md LICENSE NEWS m4/id-config.sh \
20	20	yaz-config.in yaz.pc.in m4/yaz.m4 m4/yaz_libxml2.m4 buildconf.sh \
21	21	Doxyfile.in m4/acx_pthread.m4 m4/ac_check_icu.m4

yaz/trunk/fuentes/Makefile.in

-                      r255
+                      r265
         $(srcdir)/yaz-config.in $(srcdir)/yaz.pc.in \
         $(srcdir)/Doxyfile.in $(top_srcdir)/win/version.nsi.in \
         ChangeLog NEWS README config/compile config/config.guess \
+        ChangeLog NEWS config/compile config/config.guess \
         config/config.sub config/depcomp config/install-sh \
         config/missing config/ylwrap config/ltmain.sh \
 …
 EXEEXT = @EXEEXT@
 FGREP = @FGREP@
-GCRYPT_LIBS = @GCRYPT_LIBS@
 GREP = @GREP@
 HIREDIS_LIBS = @HIREDIS_LIBS@
 …
 libdir = @libdir@
 libexecdir = @libexecdir@
-libgcrypt = @libgcrypt@
 localedir = @localedir@
 localstatedir = @localstatedir@
 …
 pkgconfig_DATA = yaz.pc
 SPEC_FILE = $(PACKAGE).spec
 EXTRA_DIST = $(SPEC_FILE) IDMETA README LICENSE NEWS m4/id-config.sh \
+EXTRA_DIST = $(SPEC_FILE) IDMETA README.md LICENSE NEWS m4/id-config.sh \
         yaz-config.in yaz.pc.in m4/yaz.m4 m4/yaz_libxml2.m4 buildconf.sh \
         Doxyfile.in m4/acx_pthread.m4 m4/ac_check_icu.m4

yaz/trunk/fuentes/NEWS

-                      r255
+                      r265
+--- 5.15.2 2016/01/11
+Re-organize Windows build. Use ICU compiled with VS 2015 to use
+same runtime as rest of components (YAZ, Libxml2, etc).
+Move YAZ and many other software components to GitHub.
+--- 5.15.1 2015/11/12
+Bundle sha1 rather than use libgcrypt/nettle. This means that
+configure no longer accepts --with-gcrypt and --with-nettle.
+Fix rpn2cql fails for Bib-1 set in qry+conf YAZ-865
+--- 5.15.0 2015/11/11
+CCL: fix r=o, r=r WRT inherited attributes YAZ-864
+--- 5.14.12 2015/11/09
+Build with nettle on Debian/Ubuntu
+test system calls yaz_deinit_globals for better memory leak detection
+cs_get_host_args: allow unix:path:args notation
+Windows: build YAZ with VC 2015 and bundle it with runtime
+version 14.0.23026.
+--- 5.14.11 2015/10/09
+Fix RPN to CQL rejects local Bib-1 attribute set YAZ-861
+ZOOM C: tweak when connection failed is returned
+For cases with multiple socket addresses for some hostname, eg
+localhost IPV4+IPV6, the code now properly returns "connection
+failed" rather than "connection lost".
+Various minor documenation tweaks from David Crossley. Thanks.
+Fix windows uninstall does not remove start menu shortcuts YAZ-860
+--- 5.14.10 2015/09/16
+Prevent huge expansions in CCL s=sl YAZ-859
+--- 5.14.9 2015/09/15
+Fix segv in ZOOM_connection_fire_event_socket YAZ-858
+The odr_in memory taken by handle_srw_response, and, thus if result
+set is destructed before we expect the HTTP response (hres) it may
+be come invalid. Therefore we inspect hres before the call to
+ZOOM_handle_sru.
+Fix possible deadlock in backtrace (2nd attempt) YAZ-856
+An alarm is set up so that backtrace is terminated if it hangs.
+Even if backtrace the handler also attempts to spawn gdb.
+--- 5.14.8 2015/09/14
+Fix SEGV for s=sl for 3 terms and syntax error YAZ-857
+--- 5.14.7 2015/09/13
+Fix possible deadlock in backtrace YAZ-856
+Various minor text tweaks in documentation
+--- 5.14.6 2015/08/17
+Fix yaz-client command args parsing broken YAZ-855
+Bug introduced in 5be87e7a04c7219b31cefc0a3 - version 5.14.5
+--- 5.14.5 2015/08/06
+Stop building packages for obsolete Debian squeeze and use DH
+version 9. YAZ-854
+rpn2cql diagnostics: provide use attribute addinfo YAZ-853
+deb: deprecated substitution ${Source-Version} YAZ-852
+Fix yaz-client: semicolon terminates arguments YAZ-851
+--- 5.14.4 2015/07/29
+Windows: Bundle VC runtime exe YAZ-848
+Omit Content-Type for HTTP requests to Solr YAZ-850
 --- 5.14.3 2015/06/29

yaz/trunk/fuentes/buildconf.sh

-                      r255
+                      r265
 When building from Git, you need these Debian packages:
   autoconf automake libtool gcc bison tcl8.4
+  autoconf automake libtool gcc bison tclsh
   xsltproc docbook docbook-xml docbook-xsl
   libxslt1-dev libgnutls-dev libreadline5-dev libwrap0-dev
   pkg-config libicu-dev
+  libxslt1-dev libgnutls-dev libreadline--dev libwrap0-dev
+  pkg-config libicu-dev make
 And if you want to make a Debian package: dpkg-dev fakeroot debhelper

yaz/trunk/fuentes/client/Makefile.in

-                      r255
+                      r265
 EXEEXT = @EXEEXT@
 FGREP = @FGREP@
-GCRYPT_LIBS = @GCRYPT_LIBS@
 GREP = @GREP@
 HIREDIS_LIBS = @HIREDIS_LIBS@
 …
 libdir = @libdir@
 libexecdir = @libexecdir@
-libgcrypt = @libgcrypt@
 localedir = @localedir@
 localstatedir = @localstatedir@

yaz/trunk/fuentes/client/client.c

-                      r255
+                      r265
+{
     int i, res;
+    char word[32], arg[10240];
+    char word[32], *arg;
+    int no_read = 0;
 #if HAVE_GETTIMEOFDAY
 …
 #endif
+    if ((res = sscanf(line, "%31s %10239[^;]", word, arg)) <= 0)
+    sscanf(line, "%31s%n", word, &no_read);
+    if (no_read == 0)
+    {
         strcpy(word, last_cmd);
         *arg = '\0';
+    }
     else if (res == 1)
         *arg = 0;
+        arg = line + strlen(line);
+    }
+    else
+        arg = line + no_read;
     strcpy(last_cmd, word);
+    /* removed tailing spaces from the arg command */
+    {
+        char* p = arg;
+        char* lastnonspace=NULL;
+        for (; *p; ++p)
+    /* whitespace chop */
+    {
+        char *p;
+        char *lastnonspace = 0;
+        while (*arg && yaz_isspace(*arg))
+            arg++;
+        for (p = arg; *p; ++p)
+        {
             if (!yaz_isspace(*p))
 …
     else
+    {
         char arg[10240],word[32];
         int i ,res;
         if ((res = sscanf(rl_line_buffer, "%31s %10239[^;]", word, arg)) <= 0)
+        char word[32];
+        int i;
+        if (sscanf(rl_line_buffer, "%31s", word) <= 0)
+        {
             rl_attempted_completion_over = 1;

yaz/trunk/fuentes/configure

-                      r255
+                      r265
 #! /bin/sh
 # Guess values for system-dependent variables and create Makefiles.
 # Generated by GNU Autoconf 2.69 for yaz 5.14.3.
+# Generated by GNU Autoconf 2.69 for yaz 5.15.2.
+#
 # Report bugs to <yaz-help@indexdata.dk>.
 …
 PACKAGE_NAME='yaz'
 PACKAGE_TARNAME='yaz'
 PACKAGE_VERSION='5.14.3'
 PACKAGE_STRING='yaz 5.14.3'
+PACKAGE_VERSION='5.15.2'
+PACKAGE_STRING='yaz 5.15.2'
 PACKAGE_BUGREPORT='yaz-help@indexdata.dk'
 PACKAGE_URL=''
 …
 MEMCACHED_LIBS
 HIREDIS_LIBS
-libgcrypt
-GCRYPT_LIBS
 XSL_DIR
 DSSSL_DIR
 …
 with_docbook_dsssl
 with_docbook_xsl
-with_libgcrypt
 with_redis
 with_memcached
 …
   # This message is too long to be a string in the A/UX 3.1 sh.
   cat <<_ACEOF
 \`configure' configures yaz 5.14.3 to adapt to many kinds of systems.
+\`configure' configures yaz 5.15.2 to adapt to many kinds of systems.
 Usage: $0 [OPTION]... [VAR=VALUE]...
 …
 if test -n "$ac_init_help"; then
   case $ac_init_help in
      short | recursive ) echo "Configuration of yaz 5.14.3:";;
+     short | recursive ) echo "Configuration of yaz 5.15.2:";;
    esac
   cat <<\_ACEOF
 …
   --with-docbook-dsssl=DIR use Docbook DSSSL in DIR/{html,print}/docbook.dsl
   --with-docbook-xsl=DIR  use Docbook XSL in DIR/{htmlhelp,xhtml}
-  --with-libgcrypt=DIR    use libgcrypt-config in DIR
   --with-redis            hiredis library
   --with-memcached        Memcached library
 …
 if $ac_init_version; then
   cat <<\_ACEOF
 yaz configure 5.14.3
+yaz configure 5.15.2
 generated by GNU Autoconf 2.69
 …
 running configure, to aid debugging if configure makes a mistake.
 It was created by yaz $as_me 5.14.3, which was
+It was created by yaz $as_me 5.15.2, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 …
 # Define the identity of the package.
  PACKAGE='yaz'
  VERSION='5.14.3'
+ VERSION='5.15.2'
 …
+ { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether byte ordering is bigendian" >&5
+$as_echo_n "checking whether byte ordering is bigendian... " >&6; }
+if ${ac_cv_c_bigendian+:} false; then :
+  $as_echo_n "(cached) " >&6
+else
+  ac_cv_c_bigendian=unknown
+    # See if we're dealing with a universal compiler.
+    cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h.  */
+#ifndef __APPLE_CC__
+               not a universal capable compiler
+             #endif
+             typedef int dummy;
+_ACEOF
+if ac_fn_c_try_compile "$LINENO"; then :
+        # Check for potential -arch flags.  It is not universal unless
+        # there are at least two -arch flags with different values.
+        ac_arch=
+        ac_prev=
+        for ac_word in $CC $CFLAGS $CPPFLAGS $LDFLAGS; do
+         if test -n "$ac_prev"; then
+           case $ac_word in
+             i?86 | x86_64 | ppc | ppc64)
+               if test -z "$ac_arch" || test "$ac_arch" = "$ac_word"; then
+                 ac_arch=$ac_word
+               else
+                 ac_cv_c_bigendian=universal
+                 break
+               fi
+               ;;
+           esac
+           ac_prev=
+         elif test "x$ac_word" = "x-arch"; then
+           ac_prev=arch
+         fi
+       done
+fi
+rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
+    if test $ac_cv_c_bigendian = unknown; then
+      # See if sys/param.h defines the BYTE_ORDER macro.
+      cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h.  */
+#include <sys/types.h>
+             #include <sys/param.h>
+int
+main ()
+{
+#if ! (defined BYTE_ORDER && defined BIG_ENDIAN \
+                     && defined LITTLE_ENDIAN && BYTE_ORDER && BIG_ENDIAN \
+                     && LITTLE_ENDIAN)
+              bogus endian macros
+             #endif
+  ;
+  return 0;
+}
+_ACEOF
+if ac_fn_c_try_compile "$LINENO"; then :
+  # It does; now see whether it defined to BIG_ENDIAN or not.
+         cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h.  */
+#include <sys/types.h>
+                #include <sys/param.h>
+int
+main ()
+{
+#if BYTE_ORDER != BIG_ENDIAN
+                 not big endian
+                #endif
+  ;
+  return 0;
+}
+_ACEOF
+if ac_fn_c_try_compile "$LINENO"; then :
+  ac_cv_c_bigendian=yes
+else
+  ac_cv_c_bigendian=no
+fi
+rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
+fi
+rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
+    fi
+    if test $ac_cv_c_bigendian = unknown; then
+      # See if <limits.h> defines _LITTLE_ENDIAN or _BIG_ENDIAN (e.g., Solaris).
+      cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h.  */
+#include <limits.h>
+int
+main ()
+{
+#if ! (defined _LITTLE_ENDIAN || defined _BIG_ENDIAN)
+              bogus endian macros
+             #endif
+  ;
+  return 0;
+}
+_ACEOF
+if ac_fn_c_try_compile "$LINENO"; then :
+  # It does; now see whether it defined to _BIG_ENDIAN or not.
+         cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h.  */
+#include <limits.h>
+int
+main ()
+{
+#ifndef _BIG_ENDIAN
+                 not big endian
+                #endif
+  ;
+  return 0;
+}
+_ACEOF
+if ac_fn_c_try_compile "$LINENO"; then :
+  ac_cv_c_bigendian=yes
+else
+  ac_cv_c_bigendian=no
+fi
+rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
+fi
+rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
+    fi
+    if test $ac_cv_c_bigendian = unknown; then
+      # Compile a test program.
+      if test "$cross_compiling" = yes; then :
+  # Try to guess by grepping values from an object file.
+         cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h.  */
+short int ascii_mm[] =
+                  { 0x4249, 0x4765, 0x6E44, 0x6961, 0x6E53, 0x7953, 0 };
+                short int ascii_ii[] =
+                  { 0x694C, 0x5454, 0x656C, 0x6E45, 0x6944, 0x6E61, 0 };
+                int use_ascii (int i) {
+                  return ascii_mm[i] + ascii_ii[i];
+                }
+                short int ebcdic_ii[] =
+                  { 0x89D3, 0xE3E3, 0x8593, 0x95C5, 0x89C4, 0x9581, 0 };
+                short int ebcdic_mm[] =
+                  { 0xC2C9, 0xC785, 0x95C4, 0x8981, 0x95E2, 0xA8E2, 0 };
+                int use_ebcdic (int i) {
+                  return ebcdic_mm[i] + ebcdic_ii[i];
+                }
+                extern int foo;
+int
+main ()
+{
+return use_ascii (foo) == use_ebcdic (foo);
+  ;
+  return 0;
+}
+_ACEOF
+if ac_fn_c_try_compile "$LINENO"; then :
+  if grep BIGenDianSyS conftest.$ac_objext >/dev/null; then
+              ac_cv_c_bigendian=yes
+            fi
+            if grep LiTTleEnDian conftest.$ac_objext >/dev/null ; then
+              if test "$ac_cv_c_bigendian" = unknown; then
+                ac_cv_c_bigendian=no
+              else
+                # finding both strings is unlikely to happen, but who knows?
+                ac_cv_c_bigendian=unknown
+              fi
+            fi
+fi
+rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
+else
+  cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h.  */
+$ac_includes_default
+int
+main ()
+{
+             /* Are we little or big endian?  From Harbison&Steele.  */
+             union
+             {
+               long int l;
+               char c[sizeof (long int)];
+             } u;
+             u.l = 1;
+             return u.c[sizeof (long int) - 1] == 1;
+  ;
+  return 0;
+}
+_ACEOF
+if ac_fn_c_try_run "$LINENO"; then :
+  ac_cv_c_bigendian=no
+else
+  ac_cv_c_bigendian=yes
+fi
+rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \
+  conftest.$ac_objext conftest.beam conftest.$ac_ext
+fi
+    fi
+fi
+{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_c_bigendian" >&5
+$as_echo "$ac_cv_c_bigendian" >&6; }
+ case $ac_cv_c_bigendian in #(
+   yes)
+     $as_echo "#define WORDS_BIGENDIAN 1" >>confdefs.h
+;; #(
+   no)
+      ;; #(
+   universal)
+$as_echo "#define AC_APPLE_UNIVERSAL_BUILD 1" >>confdefs.h
+     ;; #(
+   *)
+     as_fn_error $? "unknown endianness
+ presetting ac_cv_c_bigendian=no (or yes) will help" "$LINENO" 5 ;;
+ esac
 for ac_header in dirent.h fnmatch.h wchar.h locale.h langinfo.h pwd.h unistd.h sys/select.h sys/socket.h sys/stat.h sys/time.h sys/times.h sys/types.h sys/un.h sys/wait.h sys/prctl.h netdb.h arpa/inet.h netinet/tcp.h netinet/in_systm.h execinfo.h
 do :
 …
 fi
-libgcryptpath=NONE
-# Check whether --with-libgcrypt was given.
-if test "${with_libgcrypt+set}" = set; then :
-  withval=$with_libgcrypt; libgcryptpath=$withval
-fi
-if test "$libgcryptpath" != "no"; then
-    if test "$libgcryptpath" = "NONE"; then
-        # Extract the first word of "libgcrypt-config", so it can be a program name with args.
-set dummy libgcrypt-config; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if ${ac_cv_path_libgcrypt+:} false; then :
-  $as_echo_n "(cached) " >&6
-else
-  case $libgcrypt in
-  [\\/]* | ?:[\\/]*)
-  ac_cv_path_libgcrypt="$libgcrypt" # Let the user override the test with a path.
-  ;;
-  *)
-  as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
-  IFS=$as_save_IFS
-  test -z "$as_dir" && as_dir=.
-    for ac_exec_ext in '' $ac_executable_extensions; do
-  if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
-    ac_cv_path_libgcrypt="$as_dir/$ac_word$ac_exec_ext"
-    $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
-    break 2
-  fi
-done
-  done
-IFS=$as_save_IFS
-  test -z "$ac_cv_path_libgcrypt" && ac_cv_path_libgcrypt="NONE"
-  ;;
-esac
-fi
-libgcrypt=$ac_cv_path_libgcrypt
-if test -n "$libgcrypt"; then
-  { $as_echo "$as_me:${as_lineno-$LINENO}: result: $libgcrypt" >&5
-$as_echo "$libgcrypt" >&6; }
-else
-  { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-    elif test -x $libgcryptpath/libgcrypt-config; then
-        libgcrypt=$libgcryptpath/libgcrypt-config
-    else
-        libgcrypt=$libgcryptpath
-    fi
-    { $as_echo "$as_me:${as_lineno-$LINENO}: checking for libgcrypt" >&5
-$as_echo_n "checking for libgcrypt... " >&6; }
-    if "$libgcrypt" --version >/dev/null 2>&1; then
-        libgcryptversion=`$libgcrypt --version`
-        libgcryptversion2=`echo "$libgcryptversion" | awk 'BEGIN { FS = "."; } { printf "%d", $1 * 1000 + $2;}'`
-        { $as_echo "$as_me:${as_lineno-$LINENO}: result: $libgcryptversion" >&5
-$as_echo "$libgcryptversion" >&6; }
-        if test $libgcryptversion2 -ge 1002; then
-            GCRYPT_LIBS="`$libgcrypt --libs`"
-            CFLAGS="$CFLAGS `$libgcrypt --cflags`"
-$as_echo "#define HAVE_GCRYPT_H 1" >>confdefs.h
-        else
-            if test "$libgcryptpath" = "NONE"; then
-                { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: Only libgcrypt version 1.2 and later supported" >&5
-$as_echo "$as_me: WARNING: Only libgcrypt version 1.2 and later supported" >&2;}
-            else
-                as_fn_error $? "Only libgcrypt version 1.2 and later supported" "$LINENO" 5
-            fi
-            libgcryptversion=""
-        fi
-    else
-        { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-    fi
-fi
 hiredis=default
 …
 fi
 if test "$hiredis" != "no" -a "$pkgconfigpath" != "NONE" -a "$libgcryptversion"; then
+if test "$hiredis" != "no" -a "$pkgconfigpath" != "NONE"; then
     { $as_echo "$as_me:${as_lineno-$LINENO}: checking for redisCommandArgv in -lhiredis" >&5
 $as_echo_n "checking for redisCommandArgv in -lhiredis... " >&6; }
 …
 fi
 if test "$memcached" != "no" -a -n "$libgcryptversion" -a "$pkgconfigpath" != "NONE"; then
+if test "$memcached" != "no" -a "$pkgconfigpath" != "NONE"; then
     { $as_echo "$as_me:${as_lineno-$LINENO}: checking for libmemcached" >&5
 $as_echo_n "checking for libmemcached... " >&6; }
 …
 fi
 : "${CONFIG_STATUS=./config.status}"
 ac_write_fail=0
 …
 # values after options handling.
 ac_log="
 This file was extended by yaz $as_me 5.14.3, which was
+This file was extended by yaz $as_me 5.15.2, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 …
 ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
 ac_cs_version="\\
 yaz config.status 5.14.3
+yaz config.status 5.15.2
 configured by $0, generated by GNU Autoconf 2.69,
   with options \\"\$ac_cs_config\\"

yaz/trunk/fuentes/configure.ac

-                      r255
+                      r265
 dnl
 dnl
+AC_C_BIGENDIAN
 AC_CHECK_HEADERS([dirent.h fnmatch.h wchar.h locale.h langinfo.h pwd.h unistd.h sys/select.h sys/socket.h sys/stat.h sys/time.h sys/times.h sys/types.h sys/un.h sys/wait.h sys/prctl.h netdb.h arpa/inet.h netinet/tcp.h netinet/in_systm.h execinfo.h],[],[],[])
 AC_CHECK_HEADERS([net/if.h netinet/in.h netinet/if_ether.h],[],[],[
 …
 fi
 AC_CHECK_FUNC([gethostbyname], ,[AC_CHECK_LIB(nsl, main, [LIBS="$LIBS -lnsl"])])
+dnl ------ libgcrypt
+AC_SUBST([GCRYPT_LIBS])
+libgcryptpath=NONE
+AC_ARG_WITH(libgcrypt, [  --with-libgcrypt=DIR    use libgcrypt-config in DIR],[libgcryptpath=$withval])
+if test "$libgcryptpath" != "no"; then
+    if test "$libgcryptpath" = "NONE"; then
+        AC_PATH_PROG([libgcrypt],[libgcrypt-config],[NONE])
+    elif test -x $libgcryptpath/libgcrypt-config; then
+        libgcrypt=$libgcryptpath/libgcrypt-config
+    else
+        libgcrypt=$libgcryptpath
+    fi
+    AC_MSG_CHECKING([for libgcrypt])
+    if "$libgcrypt" --version >/dev/null 2>&1; then
+        libgcryptversion=`$libgcrypt --version`
+        libgcryptversion2=`echo "$libgcryptversion" | awk 'BEGIN { FS = "."; } { printf "%d", [$]1 * 1000 + [$]2;}'`
+        AC_MSG_RESULT([$libgcryptversion])
+        if test $libgcryptversion2 -ge 1002; then
+            GCRYPT_LIBS="`$libgcrypt --libs`"
+            CFLAGS="$CFLAGS `$libgcrypt --cflags`"
+            AC_DEFINE([HAVE_GCRYPT_H],[1],[Define to 1 if libgcrypt is present])
+        else
+            if test "$libgcryptpath" = "NONE"; then
+                AC_MSG_WARN([Only libgcrypt version 1.2 and later supported])
+            else
+                AC_MSG_ERROR([Only libgcrypt version 1.2 and later supported])
+            fi
+            libgcryptversion=""
+        fi
+    else
+        AC_MSG_RESULT([no])
+    fi
+fi
+dnl
 dnl ------ redis
 hiredis=default
 AC_SUBST([HIREDIS_LIBS])
 AC_ARG_WITH([redis], [  --with-redis            hiredis library], [hiredis=$withval])
 if test "$hiredis" != "no" -a "$pkgconfigpath" != "NONE" -a "$libgcryptversion"; then
+if test "$hiredis" != "no" -a "$pkgconfigpath" != "NONE"; then
     AC_CHECK_LIB([hiredis],[redisCommandArgv],[HIREDIS_LIBS=-lhiredis])
     AC_MSG_CHECKING([for redis])
 …
 AC_SUBST([MEMCACHED_LIBS])
 AC_ARG_WITH([memcached], [  --with-memcached        Memcached library], [memcached=$withval])
 if test "$memcached" != "no" -a -n "$libgcryptversion" -a "$pkgconfigpath" != "NONE"; then
+if test "$memcached" != "no" -a "$pkgconfigpath" != "NONE"; then
     AC_MSG_CHECKING([for libmemcached])
     if $pkgconfigpath --cflags libmemcached >/dev/null 2>&1 ; then
 …
     fi
 fi
+dnl
+dnl
+dnl
 dnl ------ GNU TLS
 AC_SUBST([SSL_CFLAGS])

yaz/trunk/fuentes/debian/.gitignore

-                      r255
+                      r265
 *.postinst.debhelper
 *.postrm.debhelper
+copyright
+files
+libyaz5
+libyaz5-dbg
+libyaz5-dev
+yaz-icu
+yaz-illclient
+tmp
+yaz
+yaz-doc
+*.debhelper.log
+*.substvars
+*.postinst.debhelper
+*.postrm.debhelper

yaz/trunk/fuentes/debian/changelog

-                      r256
+                      r265
+yaz (5.15.2-1.indexdata) unstable; urgency=medium
+  * Upstream.
+ -- Adam Dickmeiss <adam@indexdata.dk>  Mon, 11 Jan 2016 13:13:26 +0000
 yaz (5.14.3-1.indexdata+lliurex3) xenial; urgency=medium

yaz/trunk/fuentes/debian/compat

r255	r265
	1	9
1	2	7

yaz/trunk/fuentes/debian/control

-                      r255
+                      r265
+Source: yaz
+Section: devel
+Standards-Version: 3.6.2
+Maintainer: Adam Dickmeiss <adam@indexdata.dk>
+Priority: extra
+Build-Depends: debhelper (>= 7),
+        pkg-config,
+        libxslt1-dev,
+        libgnutls28-dev|libgnutls-dev,
+        libreadline-dev|libreadline5-dev,
+        libwrap0-dev,
+        libmemcached-dev,
+        libhiredis-dev,
+        libicu-dev
+Package: libyaz5
+Section: libs
+Architecture: any
+Depends: ${shlibs:Depends}
+Conflicts: idzebra (<= 1.3.4-2), php4-yaz (<= 4.1.2-5)
+Description: libraries for the Z39.50 toolkit
+ YAZ is a toolkit that allows you to develop software using the
+ ANSI Z39.50/ISO23950 standard for information retrieval.
+ .
+ This package includes runtime files.
+Package: libyaz5-dbg
+Section: debug
+Architecture: any
+Depends: libyaz5 (= ${binary:Version}), ${misc:Depends}
+Description: debugging symbols for libyaz5
+ YAZ is a toolkit that allows you to develop software using the
+ ANSI Z39.50/ISO23950 standard for information retrieval.
+ .
+ This package contains the debugging symbols for libyaz5.
+Package: yaz
+Section: utils
+Architecture: any
+Depends: ${shlibs:Depends}
+Conflicts: yaz-runtime, yaz-ssl
+Description: utilities for the Z39.50 toolkit
+ YAZ is a toolkit that allows you to develop software using the
+ ANSI Z39.50/ISO23950 standard for information retrieval.
+ .
+ This package includes utility programs.
+Package: yaz-doc
+Section: doc
+Architecture: all
+Description: documentation for the Z39.50 toolkit
+ YAZ is a toolkit that allows you to develop software using the
+ Z39.50/ISO23950 standard for information retrieval.
+ .
+ This package includes HTML documentation for YAZ.
+Package: libyaz5-dev
+Depends: libyaz5 (= ${source:Version}),
+        libxslt1-dev,
+        libicu-dev,
+        tclsh
+Provides: libyaz-dev
+Replaces: libyaz-dev
+Conflicts: libyaz2-dev, libyaz3-dev, libyaz-dev
+Section: libdevel
+Architecture: any
+Suggests: yaz-doc
+Description: development files for the Z39.50 toolkit
+ YAZ is a toolkit that allows you to develop software using the
+ ANSI Z39.50/ISO23950 standard for information retrieval.
+ .
+ This package includes development libraries and C/C++ header files.
+Package: yaz-illclient
+Section: utils
+Depends: ${shlibs:Depends}
+Architecture: any
+Description: ILL utility for the Z39.50 toolkit
+ YAZ is a toolkit that allows you to develop software using the
+ ANSI Z39.50/ISO23950 standard for information retrieval.
+ .
+ This package includes the yaz-illclient program which sends ILL
+ (Inter-Library-Loan) requests to a server and decodes the response.
+Package: yaz-icu
+Section: utils
+Depends: ${shlibs:Depends}
+Architecture: any
+Description: ICU utility for the Z39.50 toolkit
+ YAZ is a toolkit that allows you to develop software using the
+ ANSI Z39.50/ISO23950 standard for information retrieval.
+ .
+ This package includes the yaz-icu program which exposes the ICU chain
+ facility of Z39.50 toolkit.
 Source: yaz
 Section: devel

yaz/trunk/fuentes/debian/libyaz5-dev.install

-                      r255
+                      r265
+debian/tmp/usr/include/yaz
+debian/tmp/usr/lib/*/pkgconfig/yaz.pc
+debian/tmp/usr/lib/*/libyaz*.a
+debian/tmp/usr/lib/*/libyaz*.so
+debian/tmp/usr/bin/yaz-config
+debian/tmp/usr/bin/yaz-asncomp
+debian/tmp/usr/share/aclocal/yaz.m4
+debian/tmp/usr/share/yaz
 debian/tmp/usr/include/yaz
 debian/tmp/usr/lib/pkgconfig/yaz.pc

yaz/trunk/fuentes/debian/libyaz5-dev.manpages

r255	r265
2	2	debian/tmp/usr/share/man/man7/yaz.7
3	3	debian/tmp/usr/share/man/man1/yaz-config.1
	4	debian/tmp/usr/share/man/man1/yaz-asncomp.1
	5	debian/tmp/usr/share/man/man7/yaz.7
	6	debian/tmp/usr/share/man/man1/yaz-config.1

yaz/trunk/fuentes/debian/libyaz5.install

r255	r265
	1	debian/tmp/usr/lib//lib.so.*
1	2	debian/tmp/usr/lib/lib.so.

yaz/trunk/fuentes/debian/rules

-                      r255
+                      r265
+#!/usr/bin/make -f
+export DH_VERBOSE=1
+%:
+        dh $@ --without python-support
+override_dh_auto_configure:
+        dh_auto_configure -- \
+                --enable-tcpd --with-xslt --with-gnutls --with-icu \
+                --with-memcached --with-redis
+override_dh_strip:
+        dh_strip --dbg-package=libyaz5-dbg
+override_dh_auto_install:
+        dh_auto_install
+        mv debian/tmp/usr/share/doc/yaz debian/tmp/usr/share/doc/yaz-doc
+override_dh_makeshlibs:
+        dh_makeshlibs -V 'libyaz5 (>= 5.13.0)'
+override_dh_installchangelogs:
+        dh_installchangelogs NEWS
+override_dh_installdocs:
+        cp LICENSE debian/copyright
+        dh_installdocs -A README.md
 #!/usr/bin/make -f
 export DH_VERBOSE=1

yaz/trunk/fuentes/debian/yaz-doc.install

r255	r265
1	1	debian/tmp/usr/share/doc/yaz-doc
2	2	debian/tmp/usr/share/doc/yaz-doc/common
	3	debian/tmp/usr/share/doc/yaz-doc
	4	debian/tmp/usr/share/doc/yaz-doc/common

yaz/trunk/fuentes/debian/yaz-icu.install

r255	r265
1	1	debian/tmp/usr/bin/yaz-icu
	2	debian/tmp/usr/bin/yaz-icu

yaz/trunk/fuentes/debian/yaz-icu.manpages

r255	r265
1	1	debian/tmp/usr/share/man/man1/yaz-icu.1
	2	debian/tmp/usr/share/man/man1/yaz-icu.1

yaz/trunk/fuentes/debian/yaz-illclient.install

r255	r265
1	1	debian/tmp/usr/bin/yaz-illclient
	2	debian/tmp/usr/bin/yaz-illclient

yaz/trunk/fuentes/debian/yaz-illclient.manpages

r255	r265
1	1	debian/tmp/usr/share/man/man1/yaz-illclient.1
	2	debian/tmp/usr/share/man/man1/yaz-illclient.1

yaz/trunk/fuentes/debian/yaz.install

-                      r255
+                      r265
 debian/tmp/usr/bin/yaz-json-parse
 debian/tmp/usr/bin/yaz-url
+debian/tmp/usr/bin/yaz-client
+debian/tmp/usr/bin/yaz-ztest
+debian/tmp/usr/bin/zoomsh
+debian/tmp/usr/bin/yaz-marcdump
+debian/tmp/usr/bin/yaz-iconv
+debian/tmp/usr/bin/yaz-json-parse
+debian/tmp/usr/bin/yaz-url

yaz/trunk/fuentes/debian/yaz.manpages

-                      r255
+                      r265
 debian/tmp/usr/share/man/man1/yaz-json-parse.1
 debian/tmp/usr/share/man/man1/yaz-url.1
+debian/tmp/usr/share/man/man1/yaz-client.1
+debian/tmp/usr/share/man/man8/yaz-ztest.8
+debian/tmp/usr/share/man/man1/zoomsh.1
+debian/tmp/usr/share/man/man1/yaz-marcdump.1
+debian/tmp/usr/share/man/man1/yaz-iconv.1
+debian/tmp/usr/share/man/man7/yaz-log.7
+debian/tmp/usr/share/man/man7/bib1-attr.7
+debian/tmp/usr/share/man/man1/yaz-json-parse.1
+debian/tmp/usr/share/man/man1/yaz-url.1

yaz/trunk/fuentes/doc/Makefile.in

-                      r255
+                      r265
 EXEEXT = @EXEEXT@
 FGREP = @FGREP@
-GCRYPT_LIBS = @GCRYPT_LIBS@
 GREP = @GREP@
 HIREDIS_LIBS = @HIREDIS_LIBS@
 …
 libdir = @libdir@
 libexecdir = @libexecdir@
-libgcrypt = @libgcrypt@
 localedir = @localedir@
 localstatedir = @localstatedir@

yaz/trunk/fuentes/doc/asn.external.html

-                      r255
+                      r265
     <code class="literal">octet_aligned</code> arm of the union.
    </p><p>
     Some servers return ASN.1 structured data values (eg. database
+    Some servers return ASN.1 structured data values (e.g. database
     records) as BER-encoded records placed in the
     <code class="literal">octet-aligned</code> branch of the EXTERNAL CHOICE.
 …
    Z_ext_typeent *z_ext_gettypebyref(const oid *oid);
    </pre><p>
     Can be used to retrieve information about the known, external data
     types. The function return a pointer to a static area, or NULL, if no
+    can be used to retrieve information about the known, external data
+    types. The function returns a pointer to a static area, or NULL, if no
     match for the given direct reference is found. The
     <code class="literal">Z_ext_typeent</code>
 …
    </p><p>
     If you want to <span class="emphasis"><em>send</em></span> EXTERNALs containing
     ASN.1-structured values in the occtet-aligned branch of the CHOICE, this
+    ASN.1-structured values in the octet-aligned branch of the CHOICE, this
     is possible too. However, on the encoding phase, it requires a somewhat
     involved juggling around of the various buffers involved.

yaz/trunk/fuentes/doc/asn.html

r255	r265
11	11	</p><p>
12	12	The Z39.50 ASN.1 module is located in sub directory <code class="filename">z39.50</code>.
13		There you'll find C files that implements encoders and decoders for the
	13	There you'll find C files that implement encoders and decoders for the
14	14	Z39.50 types. You'll also find the protocol definitions:
15	15	<code class="filename">z3950v3.asn</code>, <code class="filename">esupdate.asn</code>,

yaz/trunk/fuentes/doc/asn.preparing.html

-                      r255
+                      r265
     <code class="function">odr_malloc()</code>, you can release all of the
     allocated data in a single operation, independent of any pointers and
     relations between the data. <code class="function">odr_malloc()</code> is based on a
     "nibble-memory"
+    relations between the data. The <code class="function">odr_malloc()</code> function
+    is based on a "nibble-memory"
     scheme, in which large portions of memory are allocated, and then
     gradually handed out with each call to <code class="function">odr_malloc()</code>.
 …
     Z_&lt;type&gt; *zget_&lt;type&gt;(ODR o);
    </pre><p>
     eg.:
+    e.g.:
    </p><pre class="synopsis">
     Z_InitRequest *zget_InitRequest(ODR o);

yaz/trunk/fuentes/doc/bib1-attr-man.xml

-                      r255
+                      r265
   <productname>YAZ</productname>
   <productnumber>&version;</productnumber>
   <info><orgname>Index Data</orgname></info>
+  <orgname>Index Data</orgname>
  </refentryinfo>
 …
  <refsect1><title>TYPES</title>
   <para>
    The Bib-1 attribute defines six attribute types: Use (1), Relation (2),
    Position (3), Structure (4), Truncation (5) and completeness (6).
+   The Bib-1 attribute set defines six attribute types: Use (1), Relation (2),
+   Position (3), Structure (4), Truncation (5) and Completeness (6).
   </para>
  </refsect1>
 …
  </refsect1>
  <refsect1><title>COMPLETENSS (6)</title>
+ <refsect1><title>COMPLETENESS (6)</title>
   <para>
    <screen>

yaz/trunk/fuentes/doc/bib1-attr.7

-                      r255
+                      r265
 .\"    Author: Index Data
 .\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
 .\"      Date: 06/29/2015
+.\"      Date: 01/11/2016
 .\"    Manual: Conventions and miscellaneous
 .\"    Source: YAZ 5.14.3
+.\"    Source: YAZ 5.15.2
 .\"  Language: English
 .\"
 .TH "BIB\-1 ATTRIBUTE SET" "7" "06/29/2015" "YAZ 5.14.3" "Conventions and miscellaneous"
+.TH "BIB\-1 ATTRIBUTE SET" "7" "01/11/2016" "YAZ 5.15.2" "Conventions and miscellaneous"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 …
 .SH "TYPES"
 .PP
 The Bib\-1 attribute defines six attribute types: Use (1), Relation (2), Position (3), Structure (4), Truncation (5) and completeness (6)\&.
+The Bib\-1 attribute set defines six attribute types: Use (1), Relation (2), Position (3), Structure (4), Truncation (5) and Completeness (6)\&.
 .SH "USE (1)"
 .PP
 …
 .\}
 .sp
 .SH "COMPLETENSS (6)"
+.SH "COMPLETENESS (6)"
 .PP
 .if n \{\
 …
 .PP
 \m[blue]\fBAttibute Set Bib\-1 Semantics\fR\m[]\&\s-2\u[2]\d\s+2\&.
+.SH "AUTHORS"
+.PP
+\fBIndex Data\fR
 .SH "NOTES"
 .IP " 1." 4

yaz/trunk/fuentes/doc/bib1.html

-                      r255
+                      r265
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Bib-1 Attribute Set</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="YAZ User's Guide and Reference"><link rel="up" href="reference.html" title="Reference"><link rel="prev" href="yaz-url.html" title="yaz-url"><link rel="next" href="yaz-json-parse.html" title="yaz-json-parse"></head><body><link rel="stylesheet" type="text/css" href="common/style1.css"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Bib-1 Attribute Set</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="yaz-url.html">Prev</a> </td><th width="60%" align="center">Reference</th><td width="20%" align="right"> <a accesskey="n" href="yaz-json-parse.html">Next</a></td></tr></table><hr></div><div class="refentry"><a name="bib1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>bib1-attr &#8212; Bib-1 Attribute Set</p></div><div class="refsect1"><a name="idp48545008"></a><h2>DESCRIPTION</h2><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Bib-1 Attribute Set</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="YAZ User's Guide and Reference"><link rel="up" href="reference.html" title="Reference"><link rel="prev" href="yaz-url.html" title="yaz-url"><link rel="next" href="yaz-json-parse.html" title="yaz-json-parse"></head><body><link rel="stylesheet" type="text/css" href="common/style1.css"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Bib-1 Attribute Set</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="yaz-url.html">Prev</a> </td><th width="60%" align="center">Reference</th><td width="20%" align="right"> <a accesskey="n" href="yaz-json-parse.html">Next</a></td></tr></table><hr></div><div class="refentry"><a name="bib1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>bib1-attr &#8212; Bib-1 Attribute Set</p></div><div class="refsect1"><a name="idm46170480248784"></a><h2>DESCRIPTION</h2><p>
    This reference entry lists the Bib-1 attribute set types and values.
   </p></div><div class="refsect1"><a name="idp48546160"></a><h2>TYPES</h2><p>
    The Bib-1 attribute defines six attribute types: Use (1), Relation (2),
    Position (3), Structure (4), Truncation (5) and completeness (6).
   </p></div><div class="refsect1"><a name="idp48547376"></a><h2>USE (1)</h2><p>
+  </p></div><div class="refsect1"><a name="idm46170480247632"></a><h2>TYPES</h2><p>
+   The Bib-1 attribute set defines six attribute types: Use (1), Relation (2),
+   Position (3), Structure (4), Truncation (5) and Completeness (6).
+  </p></div><div class="refsect1"><a name="idm46170480246416"></a><h2>USE (1)</h2><p>
    </p><pre class="screen">
      Personal-name
 …
   Author-Title-Subject
    </pre><p>
   </p></div><div class="refsect1"><a name="idp48554048"></a><h2>RELATION (2)</h2><p>
+  </p></div><div class="refsect1"><a name="idm46170480239744"></a><h2>RELATION (2)</h2><p>
    </p><pre class="screen">
 Less than
 …
 AlwaysMatches
    </pre><p>
   </p></div><div class="refsect1"><a name="idp48555968"></a><h2>POSITION (3)</h2><p>
+  </p></div><div class="refsect1"><a name="idm46170480237824"></a><h2>POSITION (3)</h2><p>
    </p><pre class="screen">
 First in field
 …
 Any position in field
    </pre><p>
   </p></div><div class="refsect1"><a name="idp48557776"></a><h2>STRUCTURE (4)</h2><p>
+  </p></div><div class="refsect1"><a name="idm46170480236016"></a><h2>STRUCTURE (4)</h2><p>
    </p><pre class="screen">
 Phrase
 …
 Numeric-string
    </pre><p>
   </p></div><div class="refsect1"><a name="idp48559808"></a><h2>TRUNCATION (5)</h2><p>
+  </p></div><div class="refsect1"><a name="idm46170480233984"></a><h2>TRUNCATION (5)</h2><p>
    </p><pre class="screen">
 Right truncation
 …
 Process * ! regular: *=.*, !=.
    </pre><p>
   </p></div><div class="refsect1"><a name="idp48563056"></a><h2>COMPLETENSS (6)</h2><p>
+  </p></div><div class="refsect1"><a name="idm46170480230736"></a><h2>COMPLETENESS (6)</h2><p>
    </p><pre class="screen">
 Incomplete subfield
 …
 Complete field
    </pre><p>
   </p></div><div class="refsect1"><a name="idp48564864"></a><h2>SORTING (7)</h2><p>
+  </p></div><div class="refsect1"><a name="idm46170480228928"></a><h2>SORTING (7)</h2><p>
    </p><pre class="screen">
 ascending
 …
     Type 7 is an Index Data extension to RPN queries that allows
     embedding a sort critieria into a query.
   </p></div><div class="refsect1"><a name="idp48567184"></a><h2>SEE ALSO</h2><p>
+  </p></div><div class="refsect1"><a name="idm46170480226608"></a><h2>SEE ALSO</h2><p>
    <a class="ulink" href="http://www.loc.gov/z3950/agency/defns/bib1.html" target="_top">Bib-1 Attribute Set</a>
   </p><p>

yaz/trunk/fuentes/doc/book.xml

-                      r255
+                      r265
      <para>
       Supports
       <ulink url="&url.solr;">Solr</ulink> Web Service version 1.4.x
+      <ulink url="&url.solr;">Apache Solr</ulink> Web Service version 1.4.x
       (client side only)
      </para>
 …
    <para>
     Most implementors only need to read a fraction of the
     material in thie manual, so a quick walkthrough of the chapters
+    material in this manual, so a quick walkthrough of the chapters
     is in order.
    </para>
 …
      <para>
       <xref linkend="installation"/> contains installation
       instructions for &yaz;. You don't need reading this
+      instructions for &yaz;. You don't need to read this
       if you expect to download &yaz; binaries.
       However, the chapter contains information about how
 …
      <para>
       <xref linkend="zoom"/> describes the ZOOM API of &yaz;.
       This is definitely worth a read if you wish to develop a Z39.50/SRU
+      This is definitely worth reading if you wish to develop a Z39.50/SRU
       client.
      </para>
 …
      <para>
       <xref linkend="yaz-client"/> describes how to use the &yaz; Z39.50
       client. If you're developer and wish to test your server
+      client. If you're a developer and wish to test your server
       or a server from another party, you might find this chapter
       useful.
 …
       ODR module which is the work horse that encodes and decodes
       BER packages. Implementors using ZOOM only, do <emphasis>not</emphasis>
       need reading this.
+      need to read this.
       Most other Z39.50 implementors only need to read the first two
       sections (<xref linkend="odr.introduction"/> and
 …
    </para>
    <para>
     The YAZ toolkit modules is shown in figure <xref linkend="yaz.layer"/>.
+    The YAZ toolkit modules are shown in figure <xref linkend="yaz.layer"/>.
    </para>
    <figure id="yaz.layer">
 …
     <para>
      If you are using the premade definitions of the &asn; module, and you
      are not adding new protocol of your own, the only parts of &odr; that you
+     are not adding a new protocol of your own, the only parts of &odr; that you
      need to worry about are documented in
      <xref linkend="odr.use"/>.
 …
     <ulink url="&url.freebsd;">FreeBSD (i386)</ulink>,
     <ulink url="&url.macosx;">MAC OSX</ulink>,
+    <ulink url="&url.solaris;">Solaris</ulink>,
+    Windows 7, Windows XP.
+   </para>
+   <para>
+    Some versions have be known to work on HP/UX,
+    Windows 10.
+   </para>
+   <para>
+    Some versions have be known to work on Windows XP, Solaris, HP/UX,
     DEC Unix, <ulink url="&url.netbsd;">NetBSD</ulink>,
     <ulink url="&url.openbsd;">OpenBSD</ulink>,
 …
     <title>Compiling from source on Unix</title>
     <para>
+     Note that if your system doesn't have a native ANSI C compiler, you may
+     have to acquire one separately. We recommend
+     <ulink url="&url.gcc;">GCC</ulink>.
+     You can choose to compile YAZ from official tar releases from
+     <ulink url="&url.yaz.download;"/>
+     or clone it via Github
+     <ulink url="https://github.com/indexdata/yaz.git"/>.
     </para>
     <para>
 …
      <ulink url="&url.libtool;">Libtool</ulink>
      are used to generate Makefiles and configure &yaz; for the system.
      You do <emphasis>not</emphasis> these tools unless you're using the
+     You do <emphasis>not</emphasis> need these tools unless you're using the
      Git version of &yaz;.
     </para>
 …
      written in <ulink url="&url.tcl;">Tcl</ulink>.
      But as for Bison you do not need it unless you're using Git
      version of &yaz; or you're using the compiler to built own codecs
+     version of &yaz; or you're using the compiler to build your own codecs
      for private ASN.1.
     </para>
     <para>
+     Generally it should be sufficient to run configure without options,
+     like this:
+     If you are checking out from Git, run:
+     <screen>
+      ./buildconf.sh
+     </screen>
+     This will create the <filename>configure</filename> script and Makefiles.
+    </para>
+    <para>
+     The next step is always:
     </para>
     <screen>
 …
         search for iconv on the system. Use this option if it
         doesn't find iconv. Alternatively,
         <literal>--without-iconv</literal>, can be uset to force &yaz;
+        <literal>--without-iconv</literal>, can be used to force &yaz;
         not to use iconv.
         </para>
 …
         Use this option if you want XSLT and XML support.
         By default, configure will
         search for libxslt on the system. Use this option if it
+        search for libxslt on the system. Use this option if
         libxslt is not found automatically. Alternatively,
         <literal>--without-xslt</literal>, can be used to force &yaz;
 …
         Use this option if you want &yaz; to use XML and support SRU/Solr.
         By default, configure will
         search for libxml2 on the system. Use this option if it
+        search for libxml2 on the system. Use this option if
         libxml2 is not found automatically. Alternatively,
         <literal>--without-xml2</literal>, can be used to force &yaz;
 …
       <varlistentry>
        <term>
-        <literal>--with-libgcrypt</literal>[=<replaceable>prefix</replaceable>]
-       </term>
-       <listitem>
-        <para>&yaz; will be linked with
-        <ulink url="&url.libgcrypt;">Libgcrypt</ulink> in the prefix if given.
-        If prefix is not given, the libraries exposed by the script
-        <application>libgcrypt-config</application> will be used if found.
-        </para>
-       </listitem>
-      </varlistentry>
-      <varlistentry>
-       <term>
         <literal>--with-memcached</literal>
        </term>
 …
         <ulink url="&url.libmemcached;">libMemcached</ulink> to allow
         for result-set caching for ZOOM.
+        The prefix can not be given. Note that YAZ will only search
+        for libMemcached if Libgcrypt is also enabled.
+        The prefix can not be given.
         Note that 0.40 of libmemcached is required.
        </para>
 …
         to allow for result-set caching for ZOOM on a
         <ulink url="&url.redis;">redis</ulink> server.
+        The prefix can not be given. Note that YAZ will only search
+        for hiredis if Libgcrypt is also enabled.
+        The prefix can not be given.
        </para>
        </listitem>
 …
      applications using the &yaz; toolkit.
      If you're used to Makefiles this shouldn't be hard. As for
      other libraries you have used before, you have to set a proper include
+     other libraries you have used before, you need to set a proper include
      path for your C/C++ compiler and specify the location of
      &yaz; libraries. You can do it by hand, but generally we suggest
 …
    <para>The easiest way to install YAZ on Windows is by downloading
    an installer from
+   <ulink url="&url.yaz.download.win32;">here</ulink>.
+   <ulink url="&url.yaz.download.win32;">
+    Index Data's Windows support area
+   </ulink>.
    The installer comes with source too - in case you wish to
    compile YAZ with different compiler options, etc.
 …
      with <ulink url="&url.vstudio;">
      Microsoft Visual Studio</ulink>. It has been tested with
      Microsoft Visual Studio 2013.
+     Microsoft Visual Studio 2015.
     </para>
     <para>
 …
        </para>
        <para>
+        A Windows version of GNU Bison is part of
+        <ulink url="&url.gitwindows;">Git for Windows</ulink>.
+        A Windows version of GNU Bison can be fetched from here:
+        <ulink
+          url="&url.indexdata.support.windows;bison-2.4.1-setup.exe">
+          Index Data's Windows support area
+        </ulink>.
        </para></listitem>
       </varlistentry>
 …
         <note>
          <para>
           libxslt depends libxml2.
+          libxslt depends on libxml2.
          </para>
         </note>
 …
          <literal>ICU_DIR</literal> to the
          <ulink url="&url.icu;">ICU</ulink> source directory.
+        </para>
+        <para>
+         Pre-compiled ICU libraries for various versions of Visual Studio
+         can be found
+         <ulink url="http://www.npcglib.org/~stathis/blog/precompiled-icu/">
+          here
+         </ulink> or from Index Data's <ulink
+          url="&url.indexdata.support.windows;">Windows support site</ulink>.
         </para>
        </listitem>
 …
        <listitem><para>This program exposes the ICU wrapper library if that
        is enabled for YAZ. Only if ICU is available this program is
        build.
+       built.
       </para></listitem>
       </varlistentry>
 …
        <filename>bin/zoomtst2.exe</filename>, ..</term>
        <listitem><para>
         Several small applications that demonstrates the ZOOM API.
+        Several small applications that demonstrate the ZOOM API.
       </para></listitem>
       </varlistentry>
 …
    became available,
    an implementation for &yaz; was quickly developed. For the first time, it is
+   now as easy (or easier!) to develop clients than servers with &yaz;. This
+   now as easy (or easier!) to develop clients as it is to develop
+   servers with &yaz;. This
    chapter describes the &zoom; C binding. Before going further, please
    reconsider whether C is the right programming language for the job.
 …
    such as C++, Java, etc. For example, you'll have to manually,
    destroy all objects you create, even though you may think of them as
    temporary. Most objects has a <literal>_create</literal> - and a
+   temporary. Most objects have a <literal>_create</literal> - and a
    <literal>_destroy</literal> variant.
    All objects are in fact pointers to internal stuff, but you don't see
 …
     default scheme is <literal>tcp</literal> (Z39.50 protocol).
     The scheme <literal>http</literal> selects SRU/get over HTTP by default,
     but can overridded to use SRU/post, SRW and the Solr protocol.
+    but can overridden to use SRU/post, SRW, and the Solr protocol.
    </para>
    <para>
 …
        encoded in the otherInfo area of a Z39.50 PDU with OID
 .2.840.10003.10.1000.81.3. Holds the original IP addreses
        of a client. Is used of ZOOM is used in a gateway of some sort.
+       of a client. Is used if ZOOM is used in a gateway of some sort.
       </entry><entry>none</entry></row>
       <row><entry>
 …
       <row><entry>
        databaseName</entry><entry>One or more database names
        separated by character plus (<literal>+</literal>), which to
+       separated by character plus (<literal>+</literal>), which is to
        be used by subsequent search requests on this Connection.
       </entry><entry>Default</entry></row>
 …
       <row><entry>
        mediumSetPresentNumber</entry><entry>This value represents
        the number of records to be returned as part of a search when when
+       the number of records to be returned as part of a search when
        hits is less than or equal to large set lower bound and if hits
        is greater than small set upper bound.
 …
       <row><entry>
        mediumSetElementSetName</entry><entry>
        The element set name to be for medium-sized result sets.
+       The element set name to be used for medium-sized result sets.
       </entry><entry>none</entry></row>
       <row><entry>
 …
        sru_version</entry><entry>
        SRU/SRW version. Should be <literal>1.1</literal>, or
        <literal>1.2</literal>. This is , prior to connect, the version
+       <literal>1.2</literal>. This is, prior to connect, the version
        to offer (highest version). And following connect (in fact
        first operation), holds the negotiated version with the server
 …
       <row id="zoom.facets.option"><entry>
        facets</entry><entry>
        Requested or recommend facets may be given before a search is sent.
+       Requested or recommended facets may be given before a search is sent.
        The value of this setting is described in <xref linkend="facets"/>
        For inspection of the facets returned, refer to the functions
 …
        option is supplied for an earlier version of YAZ, it is
        <emphasis>ignored</emphasis>.
        The value of this option is a set options, similar to that
+       The value of this option is a set of options, similar to that
        of the memcached setting. At this stage only --server=host[:port]
        and --expire=seconds is supported.
+       and --expire=seconds are supported.
       </entry><entry>none</entry></row>
      </tbody>
 …
      <function>ZOOM_connection_connect</function> establishes a TCP/IP
      connection and sends an Initialize Request to the target if
      possible. In addition, the calls waits for an Initialize Response
+     possible. In addition, the calls wait for an Initialize Response
      from the target and the result is inspected (OK or rejected).
     </para>
 …
     <title>SRU/Solr Protocol behavior</title>
     <para>
      The HTTP based protocols (SRU, SRW, Solr) doesn't feature an
+     The HTTP based protocols (SRU, SRW, Solr) do not feature an
      Inititialize Request, so  the connection phase merely establishes a
      TCP/IP connection with the HTTP server.
 …
     <function>ZOOM_query_sortby</function> but allows a strategy for
     sorting. The reason for the strategy parameter is that some
     protocols offers multiple ways of performing sorting.
+    protocols offer multiple ways of performing sorting.
     For example, Z39.50 has the standard sort, which is performed after
     search on an existing result set.
 …
    <para>
     Function <function>ZOOM_connection_search</function> creates
     a result set given a connection and query.
+    a result set, given a connection and query.
     Destroy a result set by calling
     <function>ZOOM_resultset_destroy</function>.
     Simple clients may using PQF only may use function
+    Simple clients using PQF only, may use the function
     <function>ZOOM_connection_search_pqf</function> in which case
     creating query objects is not necessary.
 …
    </para>
    <para>
     The number of hits also called result-count is returned by
+    The number of hits, also called result-count, is returned by
     function <function>ZOOM_resultset_size</function>.
    </para>
 …
        <entry>searchresult.size</entry>
        <entry>
         number of search result entries. This option is-nonexistant
+        number of search result entries. This option is non-existent
         if no entries are returned by the server.
        </entry>
 …
      <function>ZOOM_resultset_sort</function> and
      <function>ZOOM_resultset_sort1</function> both sort an existing
      result-set. The sort_type parameter is not use. Set it to "yaz".
+     result-set. The sort_type parameter is not used. Set it to "yaz".
      The sort_spec is same notation as ZOOM_query_sortby and identical
      to that offered by yaz-client's
 …
      the result set with a given start offset. When you use this mode
      the client will automatically use piggyback if that is possible
      with the target and perform one or more present requests as needed.
+     with the target, and perform one or more present requests as needed.
      Even if the target returns fewer records as part of a present response
      because of a record size limit, etc. the client will repeat sending
 …
      Current version of &yaz; does not take advantage of a result set id
      returned by the SRU server. Future versions might do, however.
      Since, the ZOOM driver does not save result set IDs any
+     Since the ZOOM driver does not save result set IDs, any
      present (retrieval) is transformed to a SRU SearchRetrieveRequest
      with same query but, possibly, different offsets.
 …
     </para>
     <para>
      Solr queries has to be done in Solr query format.
     </para>
     <para>
      Unfortunately, SRU or Solr does not define a database setting. Hence,
+     Solr queries need to be done in Solr query format.
+    </para>
+    <para>
+     Unfortunately, SRU and Solr do not define a database setting. Hence,
      <literal>databaseName</literal> is unsupported and ignored.
      However, the path part in host parameter for functions
 …
     a number of records from a result set. Parameter <literal>start</literal>
     and <literal>count</literal> specifies the range of records to
     be returned. Upon completion array
+    be returned. Upon completion, the array
     <literal>recs[0], ..recs[count-1]</literal>
     holds record objects for the records. The array of records
      <literal>recs</literal> should be allocated prior the call
     <function>ZOOM_resultset_records</function>. Note that for those
     records that couldn't be retrieved from the target
+    records that couldn't be retrieved from the target,
     <literal>recs[ ..]</literal> is set to <literal>NULL</literal>.
    </para>
 …
     <variablelist>
      <varlistentry><term><literal>database</literal></term>
       <listitem><para>Database of record is returned
+      <listitem><para>The Database of the record is returned
         as a C null-terminated string. Return type
         <literal>const char *</literal>.
 …
      <varlistentry><term><literal>render</literal></term>
       <listitem><para>The record is returned in a display friendly
         format. Upon completion buffer is returned
+        format. Upon completion, buffer is returned
         (type <literal>const char *</literal>) and length is stored in
         <literal>*len</literal>.
 …
      The functions may block (and perform network I/O)  - even though option
      <literal>async</literal> is 1, because they return records objects.
      (and there's no way to return records objects without retrieving them!).
+     (And there's no way to return records objects without retrieving them!)
      </para>
     <para>
 …
     <function>ZOOM_resultset_facets</function>. The length of the array is
     given by <function>ZOOM_resultset_facets_size</function>. The array is
     zero-based and last entry will be at
+    zero-based and the last entry will be at
     <function>ZOOM_resultset_facets_size(result_set)</function>-1.
    </para>
 …
     It is possible to interate over facets by name, by calling
     <function>ZOOM_resultset_facets_names</function>.
     This will return an const array of char * where each string can be used
+    This will return a const array of char * where each string can be used
     as parameter for <function>ZOOM_resultset_get_facet_field</function>.
    </para>
 …
     If the operation was successful, the size of the scan set can be
     retrieved by a call to <function>ZOOM_scanset_size</function>.
     Like result sets, the items are numbered 0,..size-1.
+    Like result sets, the items are numbered 0..size-1.
     To obtain information about a particular scan term, call function
     <function>ZOOM_scanset_term</function>. This function takes
 …
    </itemizedlist>
    <para>
     To create an extended service operation a <literal>ZOOM_package</literal>
+    To create an extended service operation, a <literal>ZOOM_package</literal>
     must be created. The operation is a five step operation. The
     package is created, package is configured by means of options,
     the package is send, result is inspected (by means of options),
+    the package is sent, result is inspected (by means of options),
     the package is destroyed.
    </para>
 …
        <entry>package-name</entry>
        <entry>Extended Service Request package name. Must be specified
        as part of a request</entry>
+       as part of a request.</entry>
        <entry>none</entry>
       </row>
       <row>
        <entry>user-id</entry>
        <entry>User ID of Extended Service Package. Is a request option</entry>
+       <entry>User ID of Extended Service Package. Is a request option.</entry>
        <entry>none</entry>
       </row>
 …
           to record - and <literal>record</literal> option (above) is
           ignored if recordOpaque is set. This option is only available in
           YAZ 3.0.35 and later and is meant to facilitate Updates with
+          YAZ 3.0.35 and later, and is meant to facilitate Updates with
           servers from OCLC.
         </entry>
 …
     <note>
      <para>
       The database create, drop and commit services are privately defined
+      The database create, drop, and commit services are privately defined
       operations.
       Refer to <filename>esadmin.asn</filename> in YAZ for the ASN.1
 …
    <para>
     Most &zoom; objects provide a way to specify options to change behavior.
     From an implementation point of view a set of options is just like
+    From an implementation point of view, a set of options is just like
     an associative array / hash.
    </para>
 …
     <function>ZOOM_query_cql2rpn</function> translates the CQL string,
     client-side, into RPN which may be passed to the server.
     This is useful for server's that don't themselves
+    This is useful for servers that don't themselves
     support CQL, for which <function>ZOOM_query_cql</function> is useless.
     `conn' is used  only as a place to stash diagnostics if compilation
+    'conn' is used  only as a place to stash diagnostics if compilation
     fails; if this information is not needed, a null pointer may be used.
     The CQL conversion is driven by option <literal>cqlfile</literal> from
     connection conn. This specifies a conversion file (eg pqf.properties)
+    connection conn. This specifies a conversion file (e.g. pqf.properties)
     which <emphasis>must</emphasis> be present.
    </para>
 …
     The conversion is driven by the specification given by
     <literal>config</literal>. Upon completion 0 is returned on success; -1
     is returned on on failure. Om failure <literal>error_string</literal> and
     <literal>error_pos</literal> holds error message and position of
+    is returned on failure. On failure <literal>error_string</literal> and
+    <literal>error_pos</literal> hold the error message and position of
     first error in original CCL string.
    </para>
 …
     <literal>no</literal> and an array of connections in
     <literal>cs</literal> (<literal>cs[0] ... cs[no-1]</literal>).
     A pending event could be a sending a search, receiving a response,
+    A pending event could be sending a search, receiving a response,
     etc.
     When an event has occurred for one of the connections, this function
 …
     When no events are pending for the connections, a value of zero is
     returned.
     To ensure that all outstanding requests are performed call this function
+    To ensure that all outstanding requests are performed, call this function
     repeatedly until zero is returned.
    </para>
    <para>
     If <function>ZOOM_event</function> returns and returns non-zero, the
+    If <function>ZOOM_event</function> returns, and returns non-zero, the
     last event that occurred can be expected.
    </para>
 …
       <row>
        <entry>ZOOM_EVENT_RECV_DATA</entry>
        <entry>Data has been received)</entry>
+       <entry>Data has been received</entry>
       </row>
       <row>
 …
       <row>
        <entry>ZOOM_EVENT_RECV_SEARCH</entry>
        <entry>A search result been received</entry>
+       <entry>A search result has been received</entry>
       </row>
      </tbody>
 …
    <para>
     If you have a database system that you would like to make available by
     means of Z39.50 or SRU, &yaz; basically offers your two options. You
+    means of Z39.50 or SRU, &yaz; basically offers two options. You
     can use the APIs provided by the &asn;, &odr;, and &comstack;
     modules to
 …
        A boolean value, which determines whether the server
        will fork on each incoming request (TRUE), or not (FALSE). Default is
        TRUE. This flag is only read by UNIX-based servers (WIN32 based servers
        doesn't fork).
+       TRUE. This flag is only read by UNIX-based servers (WIN32-based servers
+       do not fork).
      </para></listitem>
      </varlistentry>
 …
       <listitem><para>
        A boolean value, which determines whether the server
        will operates under a UNIX INET daemon (inetd). Default is FALSE.
+       will operate under a UNIX INET daemon (inetd). Default is FALSE.
      </para></listitem>
      </varlistentry>
 …
       command line options have been parsed - but before the server
       starts listening.
       For forked UNIX servers this handler is called in the mother
       process; for threaded servers this handler is called in the
+      For forked UNIX servers, this handler is called in the mother
+      process; for threaded servers, this handler is called in the
       main thread.
       The default value of this pointer is NULL in which case it
       isn't invoked by the frontend server.
       When the server operates as an NT service this handler is called
+      When the server operates as an NT service, this handler is called
       whenever the service is started.
       </para></listitem>
 …
       has stopped listening for incoming connections. This function pointer
       has a default value of NULL in which case it isn't called.
       When the server operates as an NT service this handler is called
+      When the server operates as an NT service, this handler is called
       whenever the service is stopped.
       </para></listitem>
 …
     The pointer returned by <literal>statserv_getcontrol</literal> points to
     a static area. You are allowed to change the contents of the structure,
     but the changes will not take effect before you call
+    but the changes will not take effect until you call
    </para>
    <synopsis>
 …
    <note>
     <para>
      that you should generally update this structure before calling
+     You should generally update this structure before calling
      <function>statserv_main()</function>.
     </para>
 …
      Unlike previous versions of YAZ, the <function>bend_init</function> also
      serves as a handler that defines the Z39.50 services that the backend
      wish to support. Pointers to <emphasis>all</emphasis> service handlers,
+     intends to support. Pointers to <emphasis>all</emphasis> service handlers,
      including search - and fetch must be specified here in this handler.
     </para>
 …
     <para>
      The <literal>auth</literal> member holds the authentication information
      part of the Z39.50 Initialize Request. Interpret this if your serves
+     part of the Z39.50 Initialize Request. Interpret this if your server
      requires authentication.
     </para>
 …
     <para>
      The <function>bend_search</function> handler is a fairly close
      approximation of a protocol Z39.50 Search Request - and Response PDUs
+     approximation of a protocol Z39.50 Search Request - and Response PDUs.
      The <literal>setname</literal> is the resultSetName from the protocol.
      You are required to establish a mapping between the set name and whatever
 …
     <title>Delete</title>
     <para>
      For back-ends that supports delete of a result set only one handler
+     For back-ends that supports delete of a result set, only one handler
      must be defined.
     </para>
 …
     This backend server handles both Z39.50 scan
     and SRU scan. In order for a handler to distinguish between SRU (CQL) scan
     Z39.50 Scan , it must check for a non-NULL value of
+    Z39.50 Scan, it must check for a non-NULL value of
     <literal>scanClause</literal>.
    </para>
    <note>
     <para>
      if designed today, it would be a choice using a union or similar,
+     If designed today, it would be a choice using a union or similar,
      but that would break binary compatibility with existing servers.
     </para>
 …
     </para>
     <para>
      The above for the Apache 1.3 series.
+     The above is for the Apache 1.3 series.
     </para>
    </example>
 …
     <title>Running a server with local access only</title>
     <para>
      Servers that is only being accessed from the local host should listen
      on UNIX file socket rather than a Internet socket. To listen on
+     A server that is only being accessed from the local host should listen
+     on UNIX file socket rather than an Internet socket. To listen on
      <filename>/tmp/mysocket</filename> start the server as follows:
      <screen>
 …
    <para>
     The &asn; module is located in sub directory <filename>z39.50</filename>.
     There you'll find C files that implements encoders and decoders for the
+    There you'll find C files that implement encoders and decoders for the
     Z39.50 types. You'll also find the protocol definitions:
     <filename>z3950v3.asn</filename>, <filename>esupdate.asn</filename>,
 …
     <function>odr_malloc()</function>, you can release all of the
     allocated data in a single operation, independent of any pointers and
     relations between the data. <function>odr_malloc()</function> is based on a
     &quot;nibble-memory&quot;
+    relations between the data. The <function>odr_malloc()</function> function
+    is based on a &quot;nibble-memory&quot;
     scheme, in which large portions of memory are allocated, and then
     gradually handed out with each call to <function>odr_malloc()</function>.
 …
    </synopsis>
    <para>
     eg.:
+    e.g.:
    </para>
    <synopsis>
 …
    </para>
    <para>
     Some servers return ASN.1 structured data values (eg. database
+    Some servers return ASN.1 structured data values (e.g. database
     records) as BER-encoded records placed in the
     <literal>octet-aligned</literal> branch of the EXTERNAL CHOICE.
 …
    </screen>
    <para>
     Can be used to retrieve information about the known, external data
     types. The function return a pointer to a static area, or NULL, if no
+    can be used to retrieve information about the known, external data
+    types. The function returns a pointer to a static area, or NULL, if no
     match for the given direct reference is found. The
     <literal>Z_ext_typeent</literal>
 …
    <para>
     If you want to <emphasis>send</emphasis> EXTERNALs containing
     ASN.1-structured values in the occtet-aligned branch of the CHOICE, this
+    ASN.1-structured values in the octet-aligned branch of the CHOICE, this
     is possible too. However, on the encoding phase, it requires a somewhat
     involved juggling around of the various buffers involved.
 …
    <para>
     &yaz; uses a very simple implementation of
     <ulink url="&url.soap;">SOAP</ulink> that only,
     currenly, supports what is sufficient to offer SRU SOAP functionality.
+    <ulink url="&url.soap;">SOAP</ulink> that only
+    (currently) supports what is sufficient to offer SRU SOAP functionality.
     The implementation uses the
     <ulink url="&url.libxml2.api.tree;">tree API</ulink> of
 …
    <para>
     The <literal>fault</literal> and <literal>soap_error</literal>
     arms represent both a SOAP fault - struct
+    arms both represent a SOAP fault - struct
     <literal>Z_SOAP_Fault</literal>. Any other generic
     (valid) package is represented by <literal>Z_SOAP_Generic</literal>.
 …
     inspects the XML content
     and tries to match one of the services namespaces of the
     supplied handlers. If there is a match a handler function
+    supplied handlers. If there is a match. a handler function
     is invoked which decodes that particular SOAP package.
     If successful, the returned <literal>Z_SOAP</literal> package will be
     of type <literal>Z_SOAP_Generic</literal>.
     Member <literal>no</literal> is
     set the offset of handler that matched; <literal>ns</literal>
     is set to namespace of matching handler; the void pointer
+    set the offset of the handler that matched; <literal>ns</literal>
+    is set to namespace of the matching handler; the void pointer
     <literal>p</literal> is set to the C data structure assocatiated
     with the handler.
    </para>
    <para>
     When a NULL namespace is met (member <literal>ns</literal> bwlow),
+    When a NULL namespace is met (member <literal>ns</literal> below),
     that specifies end-of-list.
    </para>
 …
 } Z_SOAP_Handler;
     </synopsis>
     The <literal>ns</literal> is namespace of service associated with
     handler <literal>f</literal>. <literal>client_data</literal>
     is user-defined data which is passed to handler.
+    The <literal>ns</literal> is the namespace of the service associated with
+    handler <literal>f</literal>. The <literal>client_data</literal>
+    is user-defined data which is passed to the handler.
    </para>
    <para>
 …
     and is a pointer to the <literal>Body</literal> element
     of the SOAP package. The <parameter>handler_data</parameter>
     is an opaque pointer to a C definitions associated with the
     SOAP service. <parameter>client_data</parameter> is the pointer
+    is an opaque pointer to C definitions associated with the
+    SOAP service. The <parameter>client_data</parameter> is the pointer
     which was set as part of the <literal>Z_SOAP_handler</literal>.
     Finally, <parameter>ns</parameter> the service namespace.
+    Finally, <parameter>ns</parameter> is the service namespace.
    </para>
   </sect1>
 …
     as a char pointer (<literal>char *</literal>). A null pointer
     means that the element is absent.
     Data of type xsd:integer is representd as a pointer to
+    Data of type xsd:integer is represented as a pointer to
     an int (<literal>int *</literal>). Again, a null pointer
     us used for absent elements.
+    is used for absent elements.
    </para>
    <para>
 …
     </synopsis>
     The <literal>num_records</literal> and <literal>num_diagnostics</literal>
     is number of returned records and diagnostics respectively and also
+    is number of returned records and diagnostics respectively, and also
     correspond to the "size of" arrays <literal>records</literal>
     and <literal>diagnostics</literal>.
 …
   <para>
    In support of the service API - primarily the ASN module, which
    provides the pro-grammatic interface to the Z39.50 APDUs, &yaz; contains
+   provides the programmatic interface to the Z39.50 APDUs, &yaz; contains
    a collection of tools that support the development of applications.
   </para>
 …
     <note>
      <para>
       The PQF have been adopted by other parties developing Z39.50
+      The PQF has been adopted by other parties developing Z39.50
       software. It is often referred to as Prefix Query Notation
       - PQN.
 …
     <para>
      The PQF is defined by the pquery module in the YAZ library.
      There are two sets of function that have similar behavior. First
+     There are two sets of functions that have similar behavior. First
      set operates on a PQF parser handle, second set doesn't. First set
      set of functions are more flexible than the second set. Second set
+     of functions are more flexible than the second set. Second set
      is obsolete and is only provided to ensure backwards compatibility.
     </para>
 …
      <function>yaz_pqf_create</function> and
      <function>yaz_pqf_destroy</function> respectively.
      Function <function>yaz_pqf_parse</function> parses query given
+     Function <function>yaz_pqf_parse</function> parses the query given
      by string <literal>qbuf</literal>. If parsing was successful,
      a Z39.50 RPN Query is returned which is created using ODR stream
 …
      <function>yaz_pqf_error</function> which returns an error code and
      modifies <literal>*msg</literal> to point to an error description,
      and modifies <literal>*off</literal> to the offset within last
      query were parsing failed.
+     and modifies <literal>*off</literal> to the offset within the last
+     query where parsing failed.
     </para>
     <para>
 …
      an attribute type, an equals sign, and an attribute value, like this:
      <literal>@attr 1=1003</literal>.
      The type is always an integer but the value may be either an
+     The type is always an integer, but the value may be either an
      integer or a string (if it doesn't start with a digit character).
      A string attribute-value is encoded as a Type-1 ``complex''
+     A string attribute-value is encoded as a Type-1 "complex"
      attribute with the list of values containing the single string
      specified, and including no semantic indicators.
 …
        @prox <replaceable>exclusion</replaceable> <replaceable>distance</replaceable> <replaceable>ordered</replaceable> <replaceable>relation</replaceable> <replaceable>which-code</replaceable> <replaceable>unit-code</replaceable>
       </screen>
       in which the meanings of the parameters are as described in in
+      in which the meanings of the parameters are as described in
       the standard, and they can take the following values:
       <itemizedlist>
 …
         <literal>k</literal>
         (the unit-code parameter is taken from the well-known list
         of alternatives described in below) or
+        of alternatives described below) or
         <literal>private</literal>
         or
         <literal>p</literal>
         (the unit-code paramater has semantics specific to an
+        (the unit-code parameter has semantics specific to an
         out-of-band agreement such as a profile).
        </para>
 …
         <listitem>
          <para>
           which-code is ``known'', so the standard unit-codes are used
+          which-code is "known", so the standard unit-codes are used
          </para>
         </listitem>
 …
        both occur in the record, in that order, differing in position
        by three or fewer words (i.e. with two or fewer words between
        them.)  The query would find ``Bob Dylan, aka. Robert
        Zimmerman'', but not ``Bob Dylan, born as Robert Zimmerman''
+       them.)  The query would find "Bob Dylan, aka. Robert
+       Zimmerman", but not "Bob Dylan, born as Robert Zimmerman"
        since the distance in this case is four.
       </para>
 …
 indicates West Bounding Coordinate and
 indicates East Bounding Coordinate,
        so the query is for areas extending from -114 degrees
        to no more than -109 degrees.
+       so the query is for areas extending from -114 degrees longitude
+       to no more than -109 degrees longitude.
       </para>
      </example>
 …
      <para>
       The CCL parser obeys the following grammar for the FIND argument.
       The syntax is annotated by in the lines prefixed by
+      The syntax is annotated using lines prefixed by
       <literal>--</literal>.
      </para>
 …
       </screen>
       <para>
        Assuming that the qualifiers <literal>ti</literal>,
        <literal>au</literal>
        and <literal>date</literal> are defined we may use:
+       Assuming that the qualifiers <literal>ti</literal>
+       and <literal>au</literal>
+       and <literal>date</literal> are defined, we may use:
       </para>
       <screen>
 …
       <para>
        where <replaceable>qualifier-name</replaceable> is the name of the
        qualifier to be used (eg. <literal>ti</literal>),
+       qualifier to be used (e.g. <literal>ti</literal>),
        <replaceable>type</replaceable> is attribute type in the attribute
        set (Bib-1 is used if no attribute set is given) and
        <replaceable>val</replaceable> is attribute value.
        The <replaceable>type</replaceable> can be specified as an
        integer or as it be specified either as a single-letter:
+       integer, or as a single-letter:
        <literal>u</literal> for use,
        <literal>r</literal> for relation,<literal>p</literal> for position,
        <literal>s</literal> for structure,<literal>t</literal> for truncation
+       <literal>r</literal> for relation, <literal>p</literal> for position,
+       <literal>s</literal> for structure,<literal>t</literal> for truncation,
        or <literal>c</literal> for completeness.
        The attributes for the special qualifier name <literal>term</literal>
 …
             Use attribute (1). Common use attributes are
 Personal-name, 4 Title, 7 ISBN, 8 ISSN, 30 Date,
 Subject, 1003 Author), 1016 Any. Specify value
+Subject, 1003 Author, 1016 Any. Specify value
             as an integer.
            </entry>
 …
            <entry>
             Truncation attribute (5). Values: 1 right, 2 left,
 left&amp; right, 100 none, 101 process #, 102 regular-1,
+left and right, 100 none, 101 process #, 102 regular-1,
 regular-2, 104 CCL.
            </entry>
 …
            <entry><literal>s=al</literal></entry>
            <entry>
             Each token in the term is ANDed. (and-list).
+            Each token in the term is ANDed (and-list).
             This does not set the structure at all.
            </entry>
 …
           <row><entry><literal>s=ol</literal></entry>
           <entry>
            Each token in the term is ORed. (or-list).
+           Each token in the term is ORed (or-list).
            This does not set the structure at all.
           </entry>
 …
           <row><entry><literal>r=o</literal></entry>
           <entry>
            Allows ranges and the operators greather-than, less-than, ...
+           Allows ranges and the operators greater-than, less-than, ...
            equals.
            This sets Bib-1 relation attribute accordingly (relation
 …
           <entry>
            This will omit relation=equals (@attr 2=3) when r=o / r=r
            is used. This is useful for servers that somehow breaks
+           is used. This is useful for servers that somehow break
            when an explicit relation=equals is used. Omitting the
            relation is usually safe because "equals" is the default
 …
           <row><entry><literal>t=b</literal></entry>
           <entry>
            Allows term to be both left&amp;right truncated.
+           Allows term to be both left-and-right truncated.
            If term is of the form <literal>?x?</literal>, the
            resulting term is <literal>x</literal> and trunctation is
            set to both left&amp;right.
+           set to both left and right.
           </entry>
           </row>
 …
            Allows masking anywhere in a term, thus fully supporting
            # (mask one character) and ? (zero or more of any).
            If masking is used, trunction is set to 102 (regexp-1 in term)
+           If masking is used, truncation is set to 102 (regexp-1 in term)
            and the term is converted accordingly to a regular expression.
           </entry>
 …
            Allows masking anywhere in a term, thus fully supporting
            # (mask one character) and ? (zero or more of any).
            If masking is used, trunction is set to 104 (Z39.58 in term)
+           If masking is used, truncation is set to 104 (Z39.58 in term)
            and the term is converted accordingly to Z39.58 masking term -
            actually the same truncation as CCL itself.
 …
         sets the use-attribute to 4. <literal>au</literal> sets the
         use-attribute to 1.
         When no qualifiers are used in the query the structure-attribute is
+        When no qualifiers are used in the query, the structure-attribute is
         set to free-form-text (105) (rule for <literal>term</literal>).
         The <literal>date</literal> sets the relation attribute to
 …
       which takes the CCL profile (<literal>bibset</literal>) and query
       (<literal>str</literal>) as input. Upon successful completion the RPN
       tree is returned. If an error occur, such as a syntax error, the integer
+      tree is returned. If an error occurs, such as a syntax error, the integer
       pointed to by <literal>error</literal> holds the error code and
       <literal>pos</literal> holds the offset inside query string in which
 …
       </synopsis>
       The functions <function>cql_parser_stream</function> and
       <function>cql_parser_stdio</function> parses a CQL query
+      <function>cql_parser_stdio</function> parse a CQL query
       - just like <function>cql_parser_string</function>.
       The only difference is that the CQL query can be
 …
      <title>CQL tree</title>
      <para>
       The the query string is valid, the CQL parser
+      If the query string is valid, the CQL parser
       generates a tree representing the structure of the
       CQL query.
 …
 struct cql_node *cql_parser_result(CQL_parser cp);
       </synopsis>
       <function>cql_parser_result</function> returns the
+      <function>cql_parser_result</function> returns
       a pointer to the root node of the resulting tree.
      </para>
 …
       <literal>*addinfop</literal> to point to a string containing
       additional information about the error that occurred: for
       example, if the error code is 15 (``Illegal or unsupported context
       set''), the additional information is the name of the requested
+      example, if the error code is 15 ("Illegal or unsupported context
+      set"), the additional information is the name of the requested
       context set that was not recognised.
      </para>
 …
          </para>
          <para>
           For terms not bound by an index the pattern
+          For terms not bound by an index, the pattern
           <literal>index.cql.serverChoice</literal> is used.
           Here, the prefix <literal>cql</literal> is defined as
 …
          <para>
           This pattern specifies how a CQL relation is mapped to RPN.
           <replaceable>pattern</replaceable> is name of relation
+          The <replaceable>pattern</replaceable> is name of relation
           operator. Since <literal>=</literal> is used as
           separator between CQL pattern and RPN, CQL relations
 …
          <para>
           This pattern specifies how a CQL structure is mapped to RPN.
           Note that this CQL pattern is somewhat to similar to
+          Note that this CQL pattern is somewhat similar to
           CQL pattern <literal>relation</literal>.
           The <replaceable>type</replaceable> is a CQL relation.
 …
       Conversion from CQL to XCQL is trivial and does not
       require a mapping to be defined.
       There three functions to choose from depending on the
+      There are three functions to choose from depending on the
       way you wish to store the resulting output (XML buffer
       containing XCQL).
 …
       </synopsis>
       Function <function>cql_to_xml_buf</function> converts
       to XCQL and stores result in a user supplied buffer of a given
+      to XCQL and stores the result in a user-supplied buffer of a given
       max size.
      </para>
      <para>
       <function>cql_to_xml</function> writes the result in
       a user defined output stream.
+      a user-defined output stream.
       <function>cql_to_xml_stdio</function> writes to a
       a file.
 …
    <para>
     An OID can either be declared as a automatic variable or it can
     allocated using the memory utilities or ODR/NMEM. It's
+    be allocated using the memory utilities or ODR/NMEM. It's
     guaranteed that an OID can fit in <literal>OID_SIZE</literal> integers.
    </para>
 …
    <para>
     And OID may also be filled from a string-based representation using
     dots (.). This is achieved by function
+    dots (.). This is achieved by the function
     <screen>
      int oid_dotstring_to_oid(const char *name, Odr_oid *oid);
 …
    <example id="tools.oid.bib1.2"><title>Using oid_oiddotstring_to_oid</title>
     <para>
      We can fill the Bib-1 attribute set OID easier with:
+     We can fill the Bib-1 attribute set OID more easily with:
      <screen>
       Odr_oid bib1[OID_SIZE];
 …
    </example>
    <para>
     We can also allocate an OID dynamically on a ODR stream with:
+    We can also allocate an OID dynamically on an ODR stream with:
     <screen>
     Odr_oid *odr_getoidbystr(ODR o, const char *str);
     </screen>
     This creates an OID from string-based representation using dots.
+    This creates an OID from a string-based representation using dots.
     This function take an &odr; stream as parameter. This stream is used to
     allocate memory for the data elements, which is released on a
 …
     <title>Using odr_getoidbystr</title>
     <para>
      We can create a OID for the Bib-1 attribute set with:
+     We can create an OID for the Bib-1 attribute set with:
      <screen>
       Odr_oid *bib1 = odr_getoidbystr(odr, "1.2.840.10003.3.1");
 …
    <para>
     OIDs can be copied with <function>oid_oidcpy</function> which takes
     two OID lists as arguments. Alternativly, an OID copy can be allocated
     on a ODR stream with:
+    two OID lists as arguments. Alternatively, an OID copy can be allocated
+    on an ODR stream with:
     <screen>
      Odr_oid *odr_oiddup(ODR odr, const Odr_oid *o);
 …
     <para>
      A YAZ database handle is of type <literal>yaz_oid_db_t</literal>.
      Actually that's a pointer. You need not think deal with that.
+     Actually that's a pointer. You need not deal with that.
      YAZ has a built-in database which can be considered "constant" for
      most purposes.
      We can get hold that by using function <function>yaz_oid_std</function>.
+     We can get hold of that by using function <function>yaz_oid_std</function>.
     </para>
     <para>
 …
     <para>
      All the object identifers in the standard OID database as returned
      by <function>yaz_oid_std</function> can referenced directly in a
+     by <function>yaz_oid_std</function> can be referenced directly in a
      program as a constant OID.
      Each constant OID is prefixed with <literal>yaz_oid_</literal> -
 …
     memory-management system of the &odr; subsystem (see
     <xref linkend="odr.use"/>). However, in some circumstances
     where you might otherwise benefit from using a simple nibble memory
+    where you might otherwise benefit from using a simple nibble-memory
     management system, it may be impractical to use
     <function>odr_malloc()</function> and <function>odr_reset()</function>.
 …
    </para>
    <para>
     The nibble memory pool is shared amongst threads. POSIX
+    The nibble-memory pool is shared amongst threads. POSIX
     mutex'es and WIN32 Critical sections are introduced to keep the
     module thread safe. Function <function>nmem_init()</function>
     initializes the nibble memory library and it is called automatically
+    initializes the nibble-memory library and it is called automatically
     the first time the <literal>YAZ.DLL</literal> is loaded. &yaz; uses
     function <function>DllMain</function> to achieve this. You should
 …
     Due to name clash with syslog and some math utilities the logging
     interface has been modified as of YAZ 2.0.29. The obsolete interface
     is still available if in header file <filename>yaz/log.h</filename>.
+    is still available in header file <filename>yaz/log.h</filename>.
     The key points of the interface are:
    </para>
 …
    </para>
    <para>
     Each module should check what log bits it should be used, by calling
+    Each module should check what log bits should be used, by calling
     <function>yaz_log_module_level</function> with a suitable name for the
     module. The name is cleared from a preceding path and an extension, if any,
+    module. The name is cleared of a preceding path and an extension, if any,
     so it is quite possible to use <literal>__FILE__</literal> for it. If the
     name has been passed to <function>yaz_log_mask_str</function>, the routine
 …
     debugging of yaz itself.
     Of course, any program using yaz is welcome to define as many new
     ones, as it needs.
+    ones as it needs.
    </para>
    <para>
 …
     YAZ provides a fast utility for working with MARC records.
     Early versions of the MARC utility only allowed decoding of ISO2709.
     Today the utility may both encode - and decode to a varity of formats.
+    Today the utility may both encode - and decode to a variety of formats.
    </para>
    <synopsis><![CDATA[
 …
    </para>
    <para>
     All other function operate on a <literal>yaz_marc_t</literal> handle.
+    All other functions operate on a <literal>yaz_marc_t</literal> handle.
     The output is specified by a call to <function>yaz_marc_xml</function>.
     The <literal>xmlmode</literal> must be one of
 …
        <para>
         A simple line-by-line format suitable for display but not
         recommend for further (machine) processing.
+        recommended for further (machine) processing.
        </para>
       </listitem>
 …
       <listitem>
        <para>
         <ulink url="&url.marc_in_json;">MARC-in_JSON</ulink> format.
+        <ulink url="&url.marc_in_json;">MARC-in-JSON</ulink> format.
        </para>
       </listitem>
 …
     <function>yaz_marc_decode_buf</function> and
     <function>yaz_marc_decode_wrbuf</function> which decodes and encodes
     a MARC record. The former function operates on simple buffers, the
+    a MARC record. The former function operates on simple buffers, and
     stores the resulting record in a WRBUF handle (WRBUF is a simple string
     type).
 …
      Applications like
      Pazpar2 uses XSLT to convert an XML encoded MARC record to an internal
      representation. This conversion mostly check the tag of a MARC field
+     representation. This conversion mostly checks the tag of a MARC field
      to determine the basic rules in the conversion. This check is
      costly when that is tag is encoded as an attribute in MARCXML.
+     costly when that tag is encoded as an attribute in MARCXML.
      By having the tag value as the element instead, makes processing
      many times faster (at least for Libxslt).
 …
         with the tag value of the control field if the tag value
         matches the regular expression <literal>[a-zA-Z0-9]*</literal>.
         If the tag value do not match the regular expression
+        If the tag value does not match the regular expression
         <literal>[a-zA-Z0-9]*</literal> the control field is encoded
         as element <literal>c</literal> and attribute <literal>code</literal>
         will hold the tag value.
         This rule ensure that in the rare cases where a tag value might
         result in a non-wellformed XML YAZ encode it as a coded attribute
+        This rule ensures that in the rare cases where a tag value might
+        result in a non-well-formed XML, then YAZ will encode it as a coded attribute
         (as in MARCXML).
        </para>
        <para>
         The control field content is the the text value of this element.
+        The control field content is the text value of this element.
         Indicators are encoded as attribute names
         <literal>i1</literal>, <literal>i2</literal>, etc.. and
+        <literal>i1</literal>, <literal>i2</literal>, etc. and
         corresponding values for each indicator.
        </para>
 …
         with the tag value of the data field or using the attribute
         <literal>code</literal> as described in the rules for control fields.
         The children of the data field element is subfield elements.
+        The children of the data field element are subfield elements.
         Each subfield element is encoded as <literal>s</literal>
         concatenated with the sub field code.
         The text of the subfield element is the contents of the subfield.
         Indicators are encoded as attributes for the data field element similar
+        Indicators are encoded as attributes for the data field element, similar
         to the encoding for control fields.
       </para>
 …
     configuration is neither Z39.50 ZeeRex or SRU ZeeRex. But it
     should be easy to generate both of them from the XML configuration.
     (unfortunately the two versions
     of ZeeRex differ substantially in this regard).
+    (Unfortunately the two versions
+    of ZeeRex differ substantially in this regard.)
    </para>
    <sect2 id="tools.retrieval.format">
 …
         <para>
          Defines the name of the retrieval format. This can be
          any string. For SRU, the value, is equivalent to schema (short-hand);
+         any string. For SRU, the value is equivalent to schema (short-hand);
          for Z39.50 it's equivalent to simple element set name.
          For YAZ 3.0.24 and later this name may be specified as a glob
 …
         <para>
          Defines the URI schema name of the retrieval format. This can be
          any string. For SRU, the value, is equivalent to URI schema.
+         any string. For SRU, the value is equivalent to URI schema.
          For Z39.50, there is no equivalent.
         </para>
 …
     <para>
      The attributes, <literal>name</literal> and <literal>syntax</literal>
      may be specified for the <literal>backend</literal> element. These
+     may be specified for the <literal>backend</literal> element. The
      semantics of these attributes is equivalent to those for the
      <literal>retrieval</literal>. However, these values are passed to
 …
     </para>
     <para>
      The <literal>backend</literal> element may includes one or more
+     The <literal>backend</literal> element may include one or more
      conversion instructions (as children elements). The supported
      conversions are:
 …
              <literal>marc</literal> (for ISO2709), <literal>xml</literal>
              (MARCXML/MarcXchange) and <literal>json</literal>
              (<ulink url="&url.marc_in_json;">MARC-in_JSON</ulink>).
+             (<ulink url="&url.marc_in_json;">MARC-in-JSON</ulink>).
             </para>
            </listitem>
 …
              <literal>marcxhcange</literal> (for MarcXchange),
              or <literal>json</literal>
              (<ulink url="&url.marc_in_json;">MARC-in_JSON </ulink>).
+             (<ulink url="&url.marc_in_json;">MARC-in-JSON </ulink>).
             </para>
            </listitem>
 …
      <title>MARCXML backend</title>
      <para>
       SRW/SRU and Solr backends returns records in XML.
+      SRW/SRU and Solr backends return records in XML.
       If they return MARCXML or MarcXchange, the retrieval module
       can convert those into ISO2709 formats, most commonly USMARC
 …
    <para>
     In SRU/Solr, however, the model is different. Here, sorting is specified
     during the the search operation. Note, however, that SRU might
+    during the search operation. Note, however, that SRU might
     perform sort as separate search, by referring to an existing result-set
     in the query (result-set reference).
 …
     <title>Using the Z39.50 sort service</title>
     <para>
      yaz-client and the ZOOM API supports the Z39.50 sort facility. In any
+     yaz-client and the ZOOM API support the Z39.50 sort facility. In any
      case the sort sequence or sort critiera is using a string notation.
      This notation is a one-line notation suitable for being manually
      entered or generated and allows for easy logging (one liner).
+     entered or generated, and allows for easy logging (one liner).
      For the ZOOM API, the sort is specified in the call to ZOOM_query_sortby
      function. For yaz-client the sort is performed and specified using
 …
     </para>
     <para>
      The sort is triggered by the presence of type 7 and the value of type 7
+     The sort is triggered by the presence of type 7, and the value of type 7
      specifies the
      <ulink url="http://www.loc.gov/z3950/agency/asn1.html#SortKeySpec">
       sortRelation
      </ulink>
+     </ulink>.
      The value for type 7 is 1 for ascending and 2 for descending.
      For the
 …
      sortField, then attribute type 1 is present and the value is
      sortField (InternationalString). If generic sortKey is of type
      sortAttributes, then the attributes in list is used . generic sortKey
+     sortAttributes, then the attributes in the list are used. Generic sortKey
      of type elementSpec is not supported.
     </para>
 …
    <title>Facets</title>
    <para>
     YAZ supports facets for in Solr, SRU 2.0 and Z39.50 protocols.
+    YAZ supports facets in the Solr, SRU 2.0 and Z39.50 protocols.
    </para>
    <para>
 …
    </para>
    <para>
     For ZOOM C the facets are given by option "facets"
     For yaz-client it is used for the facets command.
+    For ZOOM C the facets are given by option "facets".
+    For yaz-client it is used for the 'facets' command.
    </para>
    <para>
 …
     </literallayout>
     The notation is inspired by PQF. The string following '@attr'
     may not include blanks and is of the form
+    must not include blanks and is of the form
     <replaceable>type</replaceable><literal>=</literal><replaceable>value</replaceable>,
     where <replaceable>type</replaceable> is an integer and
 …
        <entry>1</entry>
        <entry>
         Field-name. This is often a string, eg "Author", "Year", etc.
+        Field-name. This is often a string, e.g. "Author", "Year", etc.
        </entry>
       </row>
 …
    <title>Introduction</title>
    <para>
     &odr; is the BER-encoding/decoding subsystem of &yaz;. Care as been taken
+    &odr; is the BER-encoding/decoding subsystem of &yaz;. Care has been taken
     to isolate &odr; from the rest of the package - specifically from the
     transport interface. &odr; may be used in any context where basic
 …
      small bits of space, the system maintains a free-list of larger chunks
      of memory, which are handed out in small bits. This scheme is
      generally known as a <emphasis>nibble memory</emphasis> system.
+     generally known as a <emphasis>nibble-memory</emphasis> system.
      It is very useful for maintaining short-lived constructions such
      as protocol PDUs.
 …
      </synopsis>
      before encoders or decoders are being invoked.
      It is also possible to direct the output to a buffer (of indeed
+     It is also possible to direct the output to a buffer (or indeed
      another file), by using the more generic mechanism:
      <synopsis>
 …
      if NULL for the function is provided, it will not be invoked.
      The <replaceable>stream_write</replaceable> takes the ODR handle
      as parameter, the user defined handle, a type
+     as parameter, the user-defined handle, a type
      <literal>ODR_OCTETSTRING</literal>, <literal>ODR_VISIBLESTRING</literal>
      which indicates the type of contents is being written.
+     which indicates the type of contents being written.
     </para>
     <para>
 …
      which returns a list of current elements that ODR deals with at the
      moment. For the returned array, say <literal>ar</literal>,
      <literal>ar[0]</literal> is the top level element,
+     then <literal>ar[0]</literal> is the top level element,
      <literal>ar[n]</literal> is the last. The last element has the
      property that <literal>ar[n+1] == NULL</literal>.
 …
       that holds the octetstring. The <literal>len</literal> field holds the
       actual length.
       The character array need not be null terminated.
+      The character array need not be null-terminated.
      </para>
      <para>
       To make things a little easier, an alternative is given for string
       types that are not expected to contain embedded NULL characters (eg.
+      types that are not expected to contain embedded NULL characters (e.g.
       VisibleString):
      </para>
 …
      </synopsis>
      <para>
       Which encoded or decodes between OCTETSTRING representations and
       null-terminates C strings.
      </para>
      <para>
       Functions are provided for the derived string types, eg:
+      which encodes or decodes between OCTETSTRING representations and
+      null-terminated C strings.
+     </para>
+     <para>
+      Functions are provided for the derived string types, e.g.:
      </para>
      <synopsis>
 …
      <para>
       The opaque type <literal>Odr_bitmask</literal> is only suitable for
       holding relatively brief bit strings, eg. for options fields, etc.
+      holding relatively brief bit strings, e.g. for options fields, etc.
       The constant <literal>ODR_BITMASK_SIZE</literal> multiplied by 8
       gives the maximum possible number of bits.
 …
      the data stream. <literal>size</literal> bytes of memory are allocated,
      and <literal>*p</literal> is set to point to this space.
      <function>odr_sequence_end()</function> is called at the end of the
+     The <function>odr_sequence_end()</function> is called at the end of the
      complex function. Assume that a type is defined like this:
     </para>
 …
      <para>
       Assume that the IMPLICIT in the type definition above were replaced
       with EXPLICIT (or that the IMPLICIT keyword were simply deleted, which
+      with EXPLICIT (or that the IMPLICIT keyword was simply deleted, which
       would be equivalent). The structure definition would look the same,
       but the function would look like this:
 …
       simple: Explicitly tagged, constructed types are fairly rare in
       the protocols that we care about, so the
       esthetic annoyance (not to mention the dangers of a cluttered
+      aesthetic annoyance (not to mention the dangers of a cluttered
       interface) is less than the time that would be required to develop a
       better interface. Nevertheless, it is far from satisfying, and it's a
 …
     </para>
     <para>
      The ASN.1 specifications naturally requires that each member of a
+     The ASN.1 specifications naturally require that each member of a
      CHOICE have a distinct tag, so they can be told apart on decoding.
      Sometimes it can be useful to define a CHOICE that has multiple types
 …
      provides this functionality. When called, it leaves a notice for the next
      call to <function>odr_choice()</function> to be called on the decoding
      stream <literal>o</literal> that only the <literal>arm</literal> entry with
+     stream <literal>o</literal>, that only the <literal>arm</literal> entry with
      a <literal>which</literal> field equal to <literal>what</literal>
      should be tried.
 …
      The <function>cs_create</function> function returns a null-pointer
      if a system error occurs.
      The <literal>blocking</literal> parameter should be one if
      you wish the association to operate in blocking mode, zero otherwise.
+     The <literal>blocking</literal> parameter should be '1' if
+     you wish the association to operate in blocking mode, and '0' otherwise.
      The <literal>protocol</literal> field should be
      <literal>PROTO_Z3950</literal> or <literal>PROTO_HTTP</literal>.
 …
      and <literal>len</literal>, until the buffer has been transmitted.
      When a full buffer has been sent, the function will return 0 for
      success. -1 indicates an error condition (see below).
+     success. The return value -1 indicates an error condition (see below).
     </para>
     <synopsis>
 …
      calling
      <function>cs_get</function>
      for the fist time, the buffer can be initialized to the null pointer,
      and the length should also be set to 0 - cs_get will perform a
+     for the first time, the buffer can be initialized to the null pointer,
+     and the length should also be set to 0 (cs_get will perform a
      <function>malloc(2)</function>
      on the buffer for you. When a full buffer has been read, the size of
      the package is returned (which will always be greater than 1). -1
      indicates an error condition.
+     on the buffer for you). When a full buffer has been read, the size of
+     the package is returned (which will always be greater than 1).
+     The return value -1 indicates an error condition.
     </para>
     <para>
 …
     </synopsis>
     <para>
      Returns the file descriptor of the association. Use this when
+     returns the file descriptor of the association. Use this when
      file-level operations on the endpoint are required
      (<function>select(2)</function> operations, specifically).
 …
     <para>
      You may need to use this function with some care if your
      name server service is slow or unreliable
+     name server service is slow or unreliable.
     </para>
    </note>
 …
     is similar to that described for <function>cs_straddr</function>
     but with a prefix denoting the &comstack; type. Prefixes supported
     are <literal>tcp:</literal>, <literal>unix:</literal> and
     <literal>ssl:</literal> for TCP/IP, UNIX and SSL respectively.
+    are <literal>tcp:</literal> and <literal>unix:</literal> and
+    <literal>ssl:</literal> for TCP/IP and UNIX and SSL respectively.
     If no prefix is given, then TCP/IP is used.
     The <parameter>blocking</parameter> is passed to
 …
     </synopsis>
     Returns the SSL handle, <literal>SSL *</literal> for comstack. If comstack
     is not of type SSL, NULL is returned.
+    is not of type SSL, then NULL is returned.
    </para>
    <para>
 …
    <para>
     You can the textual representation of the error code
     by using <function>cs_errmsg</function> - which
     works like <function>strerror(3)</function>
+    by using <function>cs_errmsg</function>, which
+    works like <function>strerror(3)</function>.
    </para>
    <synopsis>
 …
    </synopsis>
    <para>
     It is also possible to get straight to the textual represenataion
     without the error code by using
+    It is also possible to get straight to the textual representation
+    without the error code, by using
     <function>cs_strerror</function>.
    </para>

yaz/trunk/fuentes/doc/common/Makefile.in

-                      r255
+                      r265
 EXEEXT = @EXEEXT@
 FGREP = @FGREP@
-GCRYPT_LIBS = @GCRYPT_LIBS@
 GREP = @GREP@
 HIREDIS_LIBS = @HIREDIS_LIBS@
 …
 libdir = @libdir@
 libexecdir = @libexecdir@
-libgcrypt = @libgcrypt@
 localedir = @localedir@
 localstatedir = @localstatedir@

yaz/trunk/fuentes/doc/common/common.ent

-                      r255
+                      r265
 <!ENTITY url.marcxml "http://www.loc.gov/standards/marcxml/">
 <!ENTITY url.marcxchange "http://www.loc.gov/standards/iso25577/">
 <!ENTITY url.ill "http://www.nlc-bnc.ca/iso/ill/">
+<!ENTITY url.ill "http://www.nlc-bnc.ca/iso/ill/standard.htm">
 <!ENTITY url.ber.over.tcpip "http://www.faqs.org/rfcs/rfc1729.html">
 <!ENTITY url.http "http://www.w3.org/Protocols/">
 …
 <!ENTITY url.libxslt "http://xmlsoft.org/XSLT/">
 <!ENTITY url.libxml2.download.windows "http://ftp.indexdata.dk/pub/support/windows/">
+<!ENTITY url.indexdata.support "http://ftp.indexdata.dk/pub/support/">
+<!ENTITY url.indexdata.support.windows "http://ftp.indexdata.dk/pub/support/windows/">
 <!ENTITY url.expat "http://expat.sourceforge.net/">
 <!ENTITY url.autoconf "http://www.gnu.org/software/autoconf/">

yaz/trunk/fuentes/doc/comstack.addresses.html

-                      r255
+                      r265
     is similar to that described for <code class="function">cs_straddr</code>
     but with a prefix denoting the <acronym class="acronym">COMSTACK</acronym> type. Prefixes supported
     are <code class="literal">tcp:</code>, <code class="literal">unix:</code> and
     <code class="literal">ssl:</code> for TCP/IP, UNIX and SSL respectively.
+    are <code class="literal">tcp:</code> and <code class="literal">unix:</code> and
+    <code class="literal">ssl:</code> for TCP/IP and UNIX and SSL respectively.
     If no prefix is given, then TCP/IP is used.
     The <em class="parameter"><code>blocking</code></em> is passed to

yaz/trunk/fuentes/doc/comstack.common.html

-                      r255
+                      r265
      The <code class="function">cs_create</code> function returns a null-pointer
      if a system error occurs.
      The <code class="literal">blocking</code> parameter should be one if
      you wish the association to operate in blocking mode, zero otherwise.
+     The <code class="literal">blocking</code> parameter should be '1' if
+     you wish the association to operate in blocking mode, and '0' otherwise.
      The <code class="literal">protocol</code> field should be
      <code class="literal">PROTO_Z3950</code> or <code class="literal">PROTO_HTTP</code>.
 …
      and <code class="literal">len</code>, until the buffer has been transmitted.
      When a full buffer has been sent, the function will return 0 for
      success. -1 indicates an error condition (see below).
+     success. The return value -1 indicates an error condition (see below).
     </p><pre class="synopsis">
      int cs_get(COMSTACK handle, char **buf, int *size);
 …
      calling
      <code class="function">cs_get</code>
      for the fist time, the buffer can be initialized to the null pointer,
      and the length should also be set to 0 - cs_get will perform a
+     for the first time, the buffer can be initialized to the null pointer,
+     and the length should also be set to 0 (cs_get will perform a
      <code class="function">malloc(2)</code>
      on the buffer for you. When a full buffer has been read, the size of
      the package is returned (which will always be greater than 1). -1
      indicates an error condition.
+     on the buffer for you). When a full buffer has been read, the size of
+     the package is returned (which will always be greater than 1).
+     The return value -1 indicates an error condition.
     </p><p>
      See also the <code class="function">cs_more()</code> function below.
 …
      int cs_fileno(COMSTACK h);
     </pre><p>
      Returns the file descriptor of the association. Use this when
+     returns the file descriptor of the association. Use this when
      file-level operations on the endpoint are required
      (<code class="function">select(2)</code> operations, specifically).

yaz/trunk/fuentes/doc/comstack.diagnostics.html

-                      r255
+                      r265
    </pre><p>
     You can the textual representation of the error code
     by using <code class="function">cs_errmsg</code> - which
     works like <code class="function">strerror(3)</code>
+    by using <code class="function">cs_errmsg</code>, which
+    works like <code class="function">strerror(3)</code>.
    </p><pre class="synopsis">
     const char *cs_errmsg(int n);
    </pre><p>
     It is also possible to get straight to the textual represenataion
     without the error code by using
+    It is also possible to get straight to the textual representation
+    without the error code, by using
     <code class="function">cs_strerror</code>.
    </p><pre class="synopsis">

yaz/trunk/fuentes/doc/comstack.server.html

r255	r265
41	41	</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
42	42	You may need to use this function with some care if your
43		name server service is slow or unreliable
	43	name server service is slow or unreliable.
44	44	</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="comstack.client.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="comstack.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="comstack.addresses.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4. Client Side </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 6. Addresses</td></tr></table></div></body></html>

yaz/trunk/fuentes/doc/comstack.ssl.html

r255	r265
4	4	</pre><p>
5	5	Returns the SSL handle, <code class="literal">SSL *</code> for comstack. If comstack
6		is not of type SSL, NULL is returned.
	6	is not of type SSL, then NULL is returned.
7	7	</p><p>
8	8	</p><pre class="synopsis">

yaz/trunk/fuentes/doc/entities.ent

r255	r265
14	14	<!ENTITY reference-tools-cql-map "<xref linkend='cql.to.rpn'/>">
15	15	<!ENTITY reference-tools-ccl-qualifiers "<xref linkend='ccl.qualifiers'/>">
16		<!ENTITY copyright-year "1995-2015">
	16	<!ENTITY copyright-year "1995-2016">
17	17	<!ENTITY soversion "5">

yaz/trunk/fuentes/doc/facets.html

-                      r255
+                      r265
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>8. Facets</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="YAZ User's Guide and Reference"><link rel="up" href="tools.html" title="Chapter 7. Supporting Tools"><link rel="prev" href="sorting.html" title="7. Sorting"><link rel="next" href="odr.html" title="Chapter 8. The ODR Module"></head><body><link rel="stylesheet" type="text/css" href="common/style1.css"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">8. Facets</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sorting.html">Prev</a> </td><th width="60%" align="center">Chapter 7. Supporting Tools</th><td width="20%" align="right"> <a accesskey="n" href="odr.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="facets"></a>8. Facets</h2></div></div></div><p>
     YAZ supports facets for in Solr, SRU 2.0 and Z39.50 protocols.
+    YAZ supports facets in the Solr, SRU 2.0 and Z39.50 protocols.
    </p><p>
     Like Type-1/RPN, YAZ supports a string notation for specifying
 …
     <code class="function">yaz_pqf_parse_facet_list</code>.
    </p><p>
     For ZOOM C the facets are given by option "facets"
     For yaz-client it is used for the facets command.
+    For ZOOM C the facets are given by option "facets".
+    For yaz-client it is used for the 'facets' command.
    </p><p>
     The grammar of this specification is as follows:
 …
     </p></div><p>
     The notation is inspired by PQF. The string following '@attr'
     may not include blanks and is of the form
+    must not include blanks and is of the form
     <em class="replaceable"><code>type</code></em><code class="literal">=</code><em class="replaceable"><code>value</code></em>,
     where <em class="replaceable"><code>type</code></em> is an integer and
 …
     The Facets specification is not Bib-1. The following types apply:
    </p><div class="table"><a name="facet.attributes"></a><p class="title"><b>Table 7.4. Facet attributes</b></p><div class="table-contents"><table summary="Facet attributes" border="1"><colgroup><col class="type"><col class="description"></colgroup><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>
         Field-name. This is often a string, eg "Author", "Year", etc.
+        Field-name. This is often a string, e.g. "Author", "Year", etc.
        </td></tr><tr><td>2</td><td>
         Sort order. Value should be an integer.

yaz/trunk/fuentes/doc/gfs-options.xml

-                      r255
+                      r265
   <listitem><para>
    Operate the server in threaded mode. The server creates a thread
    for each connection rather than a fork a process. Only available
    on UNIX systems that offers POSIX threads.
+   for each connection rather than fork a process. Only available
+   on UNIX systems that offer POSIX threads.
   </para></listitem>
  </varlistentry>
 …
   <term><literal>-w </literal><replaceable>dir</replaceable></term>
   <listitem><para>
    The server changes to this directory during before listening
    on incoming connections. This option is useful
+   The server changes to this directory before listening
+   to incoming connections. This option is useful
    when the server is operating from the <application>inetd</application>
    daemon (see <literal>-i</literal>).
 …
  </term>
  <listitem><para>
   Specifies that the server should write its Process ID to
+  Specifies that the server should write its Process ID to the
   file given by <replaceable>pidfile</replaceable>.
   A typical location would be <filename>/var/run/yaz-ztest.pid</filename>.

yaz/trunk/fuentes/doc/gfs-virtual.xml

-                      r255
+                      r265
 <note>
  <para>
   Not all Z39.50 clients allows the VHOST information to be set.
   For those the selection of the backend must rely on the
+  Not all Z39.50 clients allow the VHOST information to be set.
+  For those, the selection of the backend must rely on the
   TCP/IP information alone (port and address).
  </para>
 …
     <listitem>
      <para>
       identifier for this listener. This may be referred to from
+      Identifier for this listener. This may be referred to from
       server sections.
      </para>
 …
     <para>
      Specifies a working directory for this backend server. If
      specifid, the YAZ fronend changes current working directory
+     specified, the YAZ frontend changes current working directory
      to this directory whenever a backend of this type is
      started (backend handler bend_start), stopped (backend handler hand_stop)
 …
     <para>
      Specifies a filename that includes CQL to RPN conversion for this
      backend server. See &reference-tools-cql-map;
+     backend server. See &reference-tools-cql-map;.
      If given, the backend server will only "see" a Type-1/RPN query.
     </para>
 …
     <para>
      Specifies a filename that includes CCL to RPN conversion for this
      backend server. See &reference-tools-ccl-qualifiers;
+     backend server. See &reference-tools-ccl-qualifiers;.
      If given, the backend server will only "see" a Type-1/RPN query.
     </para>
 …
     <para>
      Specifies the stylesheet reference to be part of SRU HTTP responses
      when the client does not specify one. If neither this is given, nor
      the client specifies one, no stylesheet reference is part of the
+     when the client does not specify one. If none is given, then if
+     the client does not specify one, then no stylesheet reference is part of the
      SRU HTTP response.
     </para>
 …
     <para>
      Specifies a path for local file access using HTTP. All URLs with
      a leading prefix (/ exluded) that matches the value of docpath
+     a leading prefix (/ excluded) that matches the value of <literal>docpath</literal>
      are used for file access. For example, if the server is to offer
      access in directory <literal>xsl</literal>, the docpath would be
      <literal>xsl</literal> and all URLs of the form
      <literal>http://host/exl</literal> will result in a local file access.
+     <literal>http://host/xsl</literal> will result in a local file access.
     </para>
    </listitem>
 …
      Specifies SRW/SRU ZeeRex content for this server. Copied verbatim
      to the client. As things are now, some of the Explain content
      seeem redundant because host information, etc. is also stored
+     seem redundant because host information, etc. is also stored
      elsewhere.
     </para>
 …
     <para>
      Specifies maximum record size/message size, in bytes. This
      value also servers as maximum size of <emphasis>incoming</emphasis>
+     value also serves as the maximum size of <emphasis>incoming</emphasis>
      packages (for Record Updates etc). It's the same value as that
      given by the <literal>-k</literal> option.
 …
    <listitem>
     <para>
      Enables the retrieval facility supporting conversions and
+     Enables the retrieval facility to support conversions and
      specifications of record formats/types.
      See <xref linkend="tools.retrieval"/> for
 …
  <literal>"server2"</literal> is reached by the two listeners specified.
  In order to distinguish between the two, a virtual host has
  been specified for each of server in the <literal>host</literal>
+ been specified for each server in the <literal>host</literal>
  elements.
 </para>

yaz/trunk/fuentes/doc/index.html

-                      r255
+                      r265
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>YAZ User's Guide and Reference</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="description" content="This document is the programmer's guide and reference to the YAZ package version 5.14.3. YAZ is a compact toolkit that provides access to the Z39.50 and SRU/Solr protocols, as well as a set of higher-level tools for implementing the server and client roles, respectively. The documentation can be used on its own, or as a reference when looking at the example applications provided with the package. "><link rel="home" href="index.html" title="YAZ User's Guide and Reference"><link rel="next" href="introduction.html" title="Chapter 1. Introduction"></head><body><link rel="stylesheet" type="text/css" href="common/style1.css"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">YAZ User's Guide and Reference</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="introduction.html">Next</a></td></tr></table><hr></div><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idp43484400"></a>YAZ User's Guide and Reference</h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Sebastian</span> <span class="surname">Hammer</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Adam</span> <span class="surname">Dickmeiss</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Mike</span> <span class="surname">Taylor</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Heikki</span> <span class="surname">Levanto</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Dennis</span> <span class="surname">Schafroth</span></h3></div></div></div><div><p class="releaseinfo">5.14.3</p></div><div><p class="copyright">Copyright © 1995-2015 Index Data</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>YAZ User's Guide and Reference</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="description" content="This document is the programmer's guide and reference to the YAZ package version 5.15.2. YAZ is a compact toolkit that provides access to the Z39.50 and SRU/Solr protocols, as well as a set of higher-level tools for implementing the server and client roles, respectively. The documentation can be used on its own, or as a reference when looking at the example applications provided with the package. "><link rel="home" href="index.html" title="YAZ User's Guide and Reference"><link rel="next" href="introduction.html" title="Chapter 1. Introduction"></head><body><link rel="stylesheet" type="text/css" href="common/style1.css"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">YAZ User's Guide and Reference</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="introduction.html">Next</a></td></tr></table><hr></div><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idm46170485011888"></a>YAZ User's Guide and Reference</h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Sebastian</span> <span class="surname">Hammer</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Adam</span> <span class="surname">Dickmeiss</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Mike</span> <span class="surname">Taylor</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Heikki</span> <span class="surname">Levanto</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Dennis</span> <span class="surname">Schafroth</span></h3></div></div></div><div><p class="releaseinfo">5.15.2</p></div><div><p class="copyright">Copyright © 1995-2016 Index Data</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
     This document is the programmer's guide and reference to the YAZ
     package version 5.14.3. YAZ is a compact toolkit that provides
+    package version 5.15.2. YAZ is a compact toolkit that provides
     access to the Z39.50 and SRU/Solr protocols, as well as a set of
     higher-level tools for implementing the server and client
 …
    </p><p>
     <span class="inlinemediaobject"><img src="common/id.png"></span>
    </p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="introduction.html">1. Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a href="introduction.html#introduction.reading">1. Reading this Manual</a></span></dt><dt><span class="sect1"><a href="introduction.api.html">2. The API</a></span></dt></dl></dd><dt><span class="chapter"><a href="installation.html">2. Compilation and Installation</a></span></dt><dd><dl><dt><span class="sect1"><a href="installation.html#installation-introduction">1. Introduction</a></span></dt><dt><span class="sect1"><a href="installation.unix.html">2. UNIX</a></span></dt><dd><dl><dt><span class="sect2"><a href="installation.unix.html#installation.source.unix">2.1. Compiling from source on Unix</a></span></dt><dt><span class="sect2"><a href="installation.unix.html#installation-linking-yaz-unix">2.2. How to make apps using YAZ on UNIX</a></span></dt></dl></dd><dt><span class="sect1"><a href="installation.win32.html">3. Windows</a></span></dt><dd><dl><dt><span class="sect2"><a href="installation.win32.html#installation.win32.source">3.1. Compiling from Source on Windows</a></span></dt><dt><span class="sect2"><a href="installation.win32.html#installation-linking-yaz-win32">3.2. How to make apps using YAZ on Windows</a></span></dt><dt><span class="sect2"><a href="installation.win32.html#installation.windows.libxml2">3.3. Compiling Libxml2 and Libxslt on windows</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="zoom.html">3. ZOOM</a></span></dt><dd><dl><dt><span class="sect1"><a href="zoom.html#zoom-connections">1. Connections</a></span></dt><dd><dl><dt><span class="sect2"><a href="zoom.html#zoom-connection-z39.50">1.1. Z39.50 Protocol behavior</a></span></dt><dt><span class="sect2"><a href="zoom.html#zoom.sru.init.behavior">1.2. SRU/Solr Protocol behavior</a></span></dt></dl></dd><dt><span class="sect1"><a href="zoom.query.html">2. Queries</a></span></dt><dt><span class="sect1"><a href="zoom.resultsets.html">3. Result sets</a></span></dt><dd><dl><dt><span class="sect2"><a href="zoom.resultsets.html#zoom.z3950.resultset.sort">3.1. Z39.50 Result-set Sort</a></span></dt><dt><span class="sect2"><a href="zoom.resultsets.html#zoom.z3950.resultset.behavior">3.2. Z39.50 Protocol behavior</a></span></dt><dt><span class="sect2"><a href="zoom.resultsets.html#zoom.sru.resultset.behavior">3.3. SRU Protocol behavior</a></span></dt></dl></dd><dt><span class="sect1"><a href="zoom.records.html">4. Records</a></span></dt><dd><dl><dt><span class="sect2"><a href="zoom.records.html#zoom.z3950.record.behavior">4.1. Z39.50 Protocol behavior</a></span></dt><dt><span class="sect2"><a href="zoom.records.html#zoom.sru.record.behavior">4.2. SRU/Solr Protocol behavior</a></span></dt></dl></dd><dt><span class="sect1"><a href="zoom.facets.html">5. Facets</a></span></dt><dt><span class="sect1"><a href="zoom.scan.html">6. Scan</a></span></dt><dt><span class="sect1"><a href="zoom.extendedservices.html">7. Extended Services</a></span></dt><dd><dl><dt><span class="sect2"><a href="zoom.extendedservices.html#zoom.item.order">7.1. Item Order</a></span></dt><dt><span class="sect2"><a href="zoom.extendedservices.html#zoom.record.update">7.2. Record Update</a></span></dt><dt><span class="sect2"><a href="zoom.extendedservices.html#zoom.database.create">7.3. Database Create</a></span></dt><dt><span class="sect2"><a href="zoom.extendedservices.html#zoom.database.drop">7.4. Database Drop</a></span></dt><dt><span class="sect2"><a href="zoom.extendedservices.html#zoom.commit">7.5. Commit Operation</a></span></dt><dt><span class="sect2"><a href="zoom.extendedservices.html#zoom.extended.services.behavior">7.6. Protocol behavior</a></span></dt></dl></dd><dt><span class="sect1"><a href="zoom.options.html">8. Options</a></span></dt><dt><span class="sect1"><a href="zoom.queryconversions.html">9. Query conversions</a></span></dt><dt><span class="sect1"><a href="zoom.events.html">10. Events</a></span></dt></dl></dd><dt><span class="chapter"><a href="server.html">4. Generic server</a></span></dt><dd><dl><dt><span class="sect1"><a href="server.html#server.introduction">1. Introduction</a></span></dt><dt><span class="sect1"><a href="server.frontend.html">2. The Database Frontend</a></span></dt><dt><span class="sect1"><a href="server.backend.html">3. The Backend API</a></span></dt><dt><span class="sect1"><a href="server.main.html">4. Your main() Routine</a></span></dt><dt><span class="sect1"><a href="server.backendfunctions.html">5. The Backend Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="server.backendfunctions.html#server.init">5.1. Init</a></span></dt><dt><span class="sect2"><a href="server.backendfunctions.html#server.search.retrieve">5.2. Search and Retrieve</a></span></dt><dt><span class="sect2"><a href="server.backendfunctions.html#server.delete">5.3. Delete</a></span></dt><dt><span class="sect2"><a href="server.backendfunctions.html#server.scan">5.4. Scan</a></span></dt></dl></dd><dt><span class="sect1"><a href="server.invocation.html">6. Application Invocation</a></span></dt><dt><span class="sect1"><a href="server.vhosts.html">7. GFS Configuration and Virtual Hosts</a></span></dt></dl></dd><dt><span class="chapter"><a href="asn.html">5. The Z39.50 ASN.1 Module</a></span></dt><dd><dl><dt><span class="sect1"><a href="asn.html#asn.introduction">1. Introduction</a></span></dt><dt><span class="sect1"><a href="asn.preparing.html">2. Preparing PDUs</a></span></dt><dt><span class="sect1"><a href="asn.external.html">3. EXTERNAL Data</a></span></dt><dt><span class="sect1"><a href="asn.pdu.html">4. PDU Contents Table</a></span></dt></dl></dd><dt><span class="chapter"><a href="soap.html">6. SOAP and SRU</a></span></dt><dd><dl><dt><span class="sect1"><a href="soap.html#soap.introduction">1. Introduction</a></span></dt><dt><span class="sect1"><a href="soap.http.html">2. HTTP</a></span></dt><dt><span class="sect1"><a href="soap.xml.html">3. SOAP Packages</a></span></dt><dt><span class="sect1"><a href="soap.srw.html">4. SRU</a></span></dt></dl></dd><dt><span class="chapter"><a href="tools.html">7. Supporting Tools</a></span></dt><dd><dl><dt><span class="sect1"><a href="tools.html#tools.query">1. Query Syntax Parsers</a></span></dt><dd><dl><dt><span class="sect2"><a href="tools.html#PQF">1.1. Prefix Query Format</a></span></dt><dd><dl><dt><span class="sect3"><a href="tools.html#PQF-prox">1.1.1. Using Proximity Operators with PQF</a></span></dt><dt><span class="sect3"><a href="tools.html#pqf-examples">1.1.2. PQF queries</a></span></dt></dl></dd><dt><span class="sect2"><a href="tools.html#CCL">1.2. CCL</a></span></dt><dd><dl><dt><span class="sect3"><a href="tools.html#ccl.syntax">1.2.1. CCL Syntax</a></span></dt><dt><span class="sect3"><a href="tools.html#ccl.qualifiers">1.2.2. CCL Qualifiers</a></span></dt><dt><span class="sect3"><a href="tools.html#ccl.api">1.2.3. CCL API</a></span></dt></dl></dd><dt><span class="sect2"><a href="tools.html#cql">1.3. CQL</a></span></dt><dd><dl><dt><span class="sect3"><a href="tools.html#cql.parsing">1.3.1. CQL parsing</a></span></dt><dt><span class="sect3"><a href="tools.html#cql.tree">1.3.2. CQL tree</a></span></dt><dt><span class="sect3"><a href="tools.html#cql.to.pqf">1.3.3. CQL to PQF conversion</a></span></dt><dt><span class="sect3"><a href="tools.html#cql.to.rpn">1.3.4. Specification of CQL to RPN mappings</a></span></dt><dt><span class="sect3"><a href="tools.html#cql.xcql">1.3.5. CQL to XCQL conversion</a></span></dt><dt><span class="sect3"><a href="tools.html#rpn.to.cql">1.3.6. PQF to CQL conversion</a></span></dt></dl></dd></dl></dd><dt><span class="sect1"><a href="tools.oid.html">2. Object Identifiers</a></span></dt><dd><dl><dt><span class="sect2"><a href="tools.oid.html#tools.oid.database">2.1. OID database</a></span></dt><dt><span class="sect2"><a href="tools.oid.html#tools.oid.std">2.2. Standard OIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="tools.nmem.html">3. Nibble Memory</a></span></dt><dt><span class="sect1"><a href="tools.log.html">4. Log</a></span></dt><dt><span class="sect1"><a href="marc.html">5. MARC</a></span></dt><dd><dl><dt><span class="sect2"><a href="marc.html#tools.turbomarc">5.1. TurboMARC</a></span></dt></dl></dd><dt><span class="sect1"><a href="tools.retrieval.html">6. Retrieval Facility</a></span></dt><dd><dl><dt><span class="sect2"><a href="tools.retrieval.html#tools.retrieval.format">6.1. Retrieval XML format</a></span></dt><dt><span class="sect2"><a href="tools.retrieval.html#tools.retrieval.examples">6.2. Retrieval Facility Examples</a></span></dt><dt><span class="sect2"><a href="tools.retrieval.html#tools.retrieval.api">6.3. API</a></span></dt></dl></dd><dt><span class="sect1"><a href="sorting.html">7. Sorting</a></span></dt><dd><dl><dt><span class="sect2"><a href="sorting.html#idp46954032">7.1. Using the Z39.50 sort service</a></span></dt><dt><span class="sect2"><a href="sorting.html#idp46957856">7.2. Type-7 sort</a></span></dt></dl></dd><dt><span class="sect1"><a href="facets.html">8. Facets</a></span></dt></dl></dd><dt><span class="chapter"><a href="odr.html">8. The ODR Module</a></span></dt><dd><dl><dt><span class="sect1"><a href="odr.html#odr.introduction">1. Introduction</a></span></dt><dt><span class="sect1"><a href="odr.use.html">2. Using ODR</a></span></dt><dd><dl><dt><span class="sect2"><a href="odr.use.html#odr.streams">2.1. ODR Streams</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.memory.management">2.2. Memory Management</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.encoding.and.decoding">2.3. Encoding and Decoding Data</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.printing">2.4. Printing</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.diagnostics">2.5. Diagnostics</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.summary.and.synopsis">2.6. Summary and Synopsis</a></span></dt></dl></dd><dt><span class="sect1"><a href="odr.programming.html">3. Programming with ODR</a></span></dt><dd><dl><dt><span class="sect2"><a href="odr.programming.html#odr.primitive.asn1.types">3.1. The Primitive ASN.1 Types</a></span></dt><dd><dl><dt><span class="sect3"><a href="odr.programming.html#odr.integer">3.1.1. INTEGER</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.boolean">3.1.2. BOOLEAN</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.real">3.1.3. REAL</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.null">3.1.4. NULL</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.octet.string">3.1.5. OCTET STRING</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.bit.string">3.1.6. BIT STRING</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.object.identifier">3.1.7. OBJECT IDENTIFIER</a></span></dt></dl></dd><dt><span class="sect2"><a href="odr.programming.html#odr.tagging.primitive.types">3.2. Tagging Primitive Types</a></span></dt><dt><span class="sect2"><a href="odr.programming.html#odr.constructed.types">3.3. Constructed Types</a></span></dt><dt><span class="sect2"><a href="odr.programming.html#odr.tagging.constructed.types">3.4. Tagging Constructed Types</a></span></dt><dd><dl><dt><span class="sect3"><a href="odr.programming.html#odr.implicit.tagging">3.4.1. Implicit Tagging</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.explicit.tagging">3.4.2. Explicit Tagging</a></span></dt></dl></dd><dt><span class="sect2"><a href="odr.programming.html#odr.sequence.of">3.5. SEQUENCE OF</a></span></dt><dt><span class="sect2"><a href="odr.programming.html#odr.choice.types">3.6. CHOICE Types</a></span></dt></dl></dd><dt><span class="sect1"><a href="odr.debugging.html">4. Debugging</a></span></dt></dl></dd><dt><span class="chapter"><a href="comstack.html">9. The COMSTACK Module</a></span></dt><dd><dl><dt><span class="sect1"><a href="comstack.html#comstack.synopsis">1. Synopsis (blocking mode)</a></span></dt><dt><span class="sect1"><a href="comstack.introduction.html">2. Introduction</a></span></dt><dt><span class="sect1"><a href="comstack.common.html">3. Common Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="comstack.common.html#comstack.managing.endpoints">3.1. Managing Endpoints</a></span></dt><dt><span class="sect2"><a href="comstack.common.html#comstack.data.exchange">3.2. Data Exchange</a></span></dt></dl></dd><dt><span class="sect1"><a href="comstack.client.html">4. Client Side</a></span></dt><dt><span class="sect1"><a href="comstack.server.html">5. Server Side</a></span></dt><dt><span class="sect1"><a href="comstack.addresses.html">6. Addresses</a></span></dt><dt><span class="sect1"><a href="comstack.ssl.html">7. SSL</a></span></dt><dt><span class="sect1"><a href="comstack.diagnostics.html">8. Diagnostics</a></span></dt><dt><span class="sect1"><a href="comstack.summary.html">9. Summary and Synopsis</a></span></dt></dl></dd><dt><span class="chapter"><a href="future.html">10. Future Directions</a></span></dt><dt><span class="reference"><a href="reference.html">I. Reference</a></span></dt><dd><dl><dt><span class="refentrytitle"><a href="yaz-client.html">yaz-client</a></span><span class="refpurpose"> &#8212; Z39.50/SRU client for implementors</span></dt><dt><span class="refentrytitle"><a href="yaz-ztest.html">yaz-ztest</a></span><span class="refpurpose"> &#8212; Z39.50/SRU Test Server</span></dt><dt><span class="refentrytitle"><a href="yaz-config.html">yaz-config</a></span><span class="refpurpose"> &#8212; Script to get information about YAZ.</span></dt><dt><span class="refentrytitle"><a href="yaz.html">yaz</a></span><span class="refpurpose"> &#8212; Z39.50 toolkit.</span></dt><dt><span class="refentrytitle"><a href="zoomsh.html">zoomsh</a></span><span class="refpurpose"> &#8212; ZOOM shell</span></dt><dt><span class="refentrytitle"><a href="yaz-asncomp.html">yaz-asncomp</a></span><span class="refpurpose"> &#8212; YAZ ASN.1 compiler</span></dt><dt><span class="refentrytitle"><a href="yaz-marcdump.html">yaz-marcdump</a></span><span class="refpurpose"> &#8212; MARC record dump utility</span></dt><dt><span class="refentrytitle"><a href="yaz-iconv.html">yaz-iconv</a></span><span class="refpurpose"> &#8212; YAZ Character set conversion utility</span></dt><dt><span class="refentrytitle"><a href="yaz-log.html">yaz-log</a></span><span class="refpurpose"> &#8212; Log handling in all yaz-based programs</span></dt><dt><span class="refentrytitle"><a href="yaz-illclient.html">yaz-illclient</a></span><span class="refpurpose"> &#8212; ILL client</span></dt><dt><span class="refentrytitle"><a href="yaz-icu.html">yaz-icu</a></span><span class="refpurpose"> &#8212; YAZ ICU utility</span></dt><dt><span class="refentrytitle"><a href="yaz-url.html">yaz-url</a></span><span class="refpurpose"> &#8212; YAZ URL fetch utility</span></dt><dt><span class="refentrytitle"><a href="bib1.html">Bib-1 Attribute Set</a></span><span class="refpurpose"> &#8212; Bib-1 Attribute Set</span></dt><dt><span class="refentrytitle"><a href="yaz-json-parse.html">yaz-json-parse</a></span><span class="refpurpose"> &#8212; YAZ JSON parser</span></dt></dl></dd><dt><span class="appendix"><a href="list-oids.html">A. List of Object Identifiers</a></span></dt><dt><span class="appendix"><a href="bib1-diagnostics.html">B. Bib-1 diagnostics</a></span></dt><dt><span class="appendix"><a href="sru-diagnostics.html">C. SRU diagnostics</a></span></dt><dt><span class="appendix"><a href="license.html">D. License</a></span></dt><dd><dl><dt><span class="sect1"><a href="license.html#license.indexdata">1. Index Data Copyright</a></span></dt></dl></dd><dt><span class="appendix"><a href="indexdata.html">E. About Index Data</a></span></dt><dt><span class="appendix"><a href="credits.html">F. Credits</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>1.1. <a href="introduction.api.html#yaz.layer">YAZ layers</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>3.1. <a href="zoom.html#zoom-connection-options">ZOOM Connection Options</a></dt><dt>3.2. <a href="zoom.query.html#zoom-sort-strategy">ZOOM sort strategy</a></dt><dt>3.3. <a href="zoom.resultsets.html#zoom.resultset.options">ZOOM Result set Options</a></dt><dt>3.4. <a href="zoom.resultsets.html#zoom.search.info.report.options">Search Info Report Options</a></dt><dt>3.5. <a href="zoom.scan.html#zoom.scanset.options">ZOOM Scan Set Options</a></dt><dt>3.6. <a href="zoom.extendedservices.html#zoom.extendedservices.type">Extended Service Type</a></dt><dt>3.7. <a href="zoom.extendedservices.html#zoom.extendedservices.options">Extended Service Common Options</a></dt><dt>3.8. <a href="zoom.extendedservices.html#zoom.item.order.options">Item Order Options</a></dt><dt>3.9. <a href="zoom.extendedservices.html#zoom.illrequest.options">ILL Request Options</a></dt><dt>3.10. <a href="zoom.extendedservices.html#zoom.record.update.options">Record Update Options</a></dt><dt>3.11. <a href="zoom.extendedservices.html#zoom.database.create.options">Database Create Options</a></dt><dt>3.12. <a href="zoom.extendedservices.html#zoom.database.drop.options">Database Drop Options</a></dt><dt>3.13. <a href="zoom.events.html#zoom.event.ids">ZOOM Event IDs</a></dt><dt>5.1. <a href="asn.pdu.html#asn.default.initialize.request">Default settings for PDU Initialize Request</a></dt><dt>5.2. <a href="asn.pdu.html#asn.default.initialize.response">Default settings for PDU Initialize Response</a></dt><dt>5.3. <a href="asn.pdu.html#asn.default.search.request">Default settings for PDU Search Request</a></dt><dt>5.4. <a href="asn.pdu.html#asn.default.search.response">Default settings for PDU Search Response</a></dt><dt>5.5. <a href="asn.pdu.html#asn.default.present.request">Default settings for PDU Present Request</a></dt><dt>5.6. <a href="asn.pdu.html#asn.default.present.response">Default settings for PDU Present Response</a></dt><dt>5.7. <a href="asn.pdu.html#asn.default.delete.result.set.request">Default settings for Delete Result Set Request</a></dt><dt>5.8. <a href="asn.pdu.html#asn.default.delete.result.set.response">Default settings for Delete Result Set Response</a></dt><dt>5.9. <a href="asn.pdu.html#asn.default.scan.request">Default settings for Scan Request</a></dt><dt>5.10. <a href="asn.pdu.html#asn.default.scan.response">Default settings for Scan Response</a></dt><dt>5.11. <a href="asn.pdu.html#asn.default.trigger.resource.control.request">Default settings for Trigger Resource Control Request</a></dt><dt>5.12. <a href="asn.pdu.html#asn.default.resource.control.request">Default settings for Resource Control Request</a></dt><dt>5.13. <a href="asn.pdu.html#asn.default.resource.control.response">Default settings for Resource Control Response</a></dt><dt>5.14. <a href="asn.pdu.html#asn.default.access.control.request">Default settings for Access Control Request</a></dt><dt>5.15. <a href="asn.pdu.html#asn.default.access.control.response">Default settings for Access Control Response</a></dt><dt>5.16. <a href="asn.pdu.html#asn.default.segment">Default settings for Segment</a></dt><dt>5.17. <a href="asn.pdu.html#asn.default.close">Default settings for Close</a></dt><dt>7.1. <a href="tools.html#ccl.common.bib1.attributes">Common Bib-1 attributes</a></dt><dt>7.2. <a href="tools.html#ccl.special.attribute.combos">Special attribute combos</a></dt><dt>7.3. <a href="tools.html#ccl.directives.table">CCL directives</a></dt><dt>7.4. <a href="facets.html#facet.attributes">Facet attributes</a></dt><dt>8.1. <a href="odr.use.html#odr.error.codes">ODR Error codes</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>4.1. <a href="server.invocation.html#server.example.running.unix">Running the GFS on Unix</a></dt><dt>4.2. <a href="server.invocation.html#server.example.apache.sru">Setting up Apache as SRU Frontend</a></dt><dt>4.3. <a href="server.invocation.html#server.example.local.access">Running a server with local access only</a></dt><dt>7.1. <a href="tools.html#example.pqf.simple.terms">PQF queries using simple terms</a></dt><dt>7.2. <a href="tools.html#pqf.example.pqf.boolean.operators">PQF boolean operators</a></dt><dt>7.3. <a href="tools.html#example.pqf.result.sets">PQF references to result sets</a></dt><dt>7.4. <a href="tools.html#example.pqf.attributes">Attributes for terms</a></dt><dt>7.5. <a href="tools.html#example.pqf.proximity">PQF Proximity queries</a></dt><dt>7.6. <a href="tools.html#example.pqf.search.term.type">PQF specification of search term type</a></dt><dt>7.7. <a href="tools.html#example.pqf.mixed.queries">PQF mixed queries</a></dt><dt>7.8. <a href="tools.html#example.ccl.queries">CCL queries</a></dt><dt>7.9. <a href="tools.html#example.ccl.profile">CCL profile</a></dt><dt>7.10. <a href="tools.html#example.cql.to.rpn.mapping">CQL to RPN mapping file</a></dt><dt>7.11. <a href="tools.html#example.cql.to.rpn.string">CQL to RPN string attributes</a></dt><dt>7.12. <a href="tools.html#example.cql.to.rpn.bathprofile">CQL to RPN using Bath Profile</a></dt><dt>7.13. <a href="tools.oid.html#tools.oid.bib1.1">Create OID on stack</a></dt><dt>7.14. <a href="tools.oid.html#tools.oid.bib1.2">Using oid_oiddotstring_to_oid</a></dt><dt>7.15. <a href="tools.oid.html#tools.oid.bib1.3">Using odr_getoidbystr</a></dt><dt>7.16. <a href="tools.oid.html#tools.oid.bib1.4">Create OID with YAZ DB</a></dt><dt>7.17. <a href="tools.oid.html#tools.oid.bib1.5">Use a built-in OID</a></dt><dt>7.18. <a href="marc.html#example.marc.display">Display of MARC record</a></dt><dt>7.19. <a href="tools.retrieval.html#tools.retrieval.marc21">MARC21 backend</a></dt><dt>7.20. <a href="tools.retrieval.html#tools.retrieval.marcxml">MARCXML backend</a></dt><dt>8.1. <a href="odr.use.html#example.odr.encoding.and.decoding.functions">Encoding and decoding functions</a></dt><dt>8.2. <a href="odr.use.html#example.odr.encoding.of.integer">Encoding and decoding of an integer</a></dt><dt>8.3. <a href="odr.use.html#example.odr.element.path.record">Element Path for record</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="introduction.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. Introduction</td></tr></table></div></body></html>
+   </p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="introduction.html">1. Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a href="introduction.html#introduction.reading">1. Reading this Manual</a></span></dt><dt><span class="sect1"><a href="introduction.api.html">2. The API</a></span></dt></dl></dd><dt><span class="chapter"><a href="installation.html">2. Compilation and Installation</a></span></dt><dd><dl><dt><span class="sect1"><a href="installation.html#installation-introduction">1. Introduction</a></span></dt><dt><span class="sect1"><a href="installation.unix.html">2. UNIX</a></span></dt><dd><dl><dt><span class="sect2"><a href="installation.unix.html#installation.source.unix">2.1. Compiling from source on Unix</a></span></dt><dt><span class="sect2"><a href="installation.unix.html#installation-linking-yaz-unix">2.2. How to make apps using YAZ on UNIX</a></span></dt></dl></dd><dt><span class="sect1"><a href="installation.win32.html">3. Windows</a></span></dt><dd><dl><dt><span class="sect2"><a href="installation.win32.html#installation.win32.source">3.1. Compiling from Source on Windows</a></span></dt><dt><span class="sect2"><a href="installation.win32.html#installation-linking-yaz-win32">3.2. How to make apps using YAZ on Windows</a></span></dt><dt><span class="sect2"><a href="installation.win32.html#installation.windows.libxml2">3.3. Compiling Libxml2 and Libxslt on windows</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="zoom.html">3. ZOOM</a></span></dt><dd><dl><dt><span class="sect1"><a href="zoom.html#zoom-connections">1. Connections</a></span></dt><dd><dl><dt><span class="sect2"><a href="zoom.html#zoom-connection-z39.50">1.1. Z39.50 Protocol behavior</a></span></dt><dt><span class="sect2"><a href="zoom.html#zoom.sru.init.behavior">1.2. SRU/Solr Protocol behavior</a></span></dt></dl></dd><dt><span class="sect1"><a href="zoom.query.html">2. Queries</a></span></dt><dt><span class="sect1"><a href="zoom.resultsets.html">3. Result sets</a></span></dt><dd><dl><dt><span class="sect2"><a href="zoom.resultsets.html#zoom.z3950.resultset.sort">3.1. Z39.50 Result-set Sort</a></span></dt><dt><span class="sect2"><a href="zoom.resultsets.html#zoom.z3950.resultset.behavior">3.2. Z39.50 Protocol behavior</a></span></dt><dt><span class="sect2"><a href="zoom.resultsets.html#zoom.sru.resultset.behavior">3.3. SRU Protocol behavior</a></span></dt></dl></dd><dt><span class="sect1"><a href="zoom.records.html">4. Records</a></span></dt><dd><dl><dt><span class="sect2"><a href="zoom.records.html#zoom.z3950.record.behavior">4.1. Z39.50 Protocol behavior</a></span></dt><dt><span class="sect2"><a href="zoom.records.html#zoom.sru.record.behavior">4.2. SRU/Solr Protocol behavior</a></span></dt></dl></dd><dt><span class="sect1"><a href="zoom.facets.html">5. Facets</a></span></dt><dt><span class="sect1"><a href="zoom.scan.html">6. Scan</a></span></dt><dt><span class="sect1"><a href="zoom.extendedservices.html">7. Extended Services</a></span></dt><dd><dl><dt><span class="sect2"><a href="zoom.extendedservices.html#zoom.item.order">7.1. Item Order</a></span></dt><dt><span class="sect2"><a href="zoom.extendedservices.html#zoom.record.update">7.2. Record Update</a></span></dt><dt><span class="sect2"><a href="zoom.extendedservices.html#zoom.database.create">7.3. Database Create</a></span></dt><dt><span class="sect2"><a href="zoom.extendedservices.html#zoom.database.drop">7.4. Database Drop</a></span></dt><dt><span class="sect2"><a href="zoom.extendedservices.html#zoom.commit">7.5. Commit Operation</a></span></dt><dt><span class="sect2"><a href="zoom.extendedservices.html#zoom.extended.services.behavior">7.6. Protocol behavior</a></span></dt></dl></dd><dt><span class="sect1"><a href="zoom.options.html">8. Options</a></span></dt><dt><span class="sect1"><a href="zoom.queryconversions.html">9. Query conversions</a></span></dt><dt><span class="sect1"><a href="zoom.events.html">10. Events</a></span></dt></dl></dd><dt><span class="chapter"><a href="server.html">4. Generic server</a></span></dt><dd><dl><dt><span class="sect1"><a href="server.html#server.introduction">1. Introduction</a></span></dt><dt><span class="sect1"><a href="server.frontend.html">2. The Database Frontend</a></span></dt><dt><span class="sect1"><a href="server.backend.html">3. The Backend API</a></span></dt><dt><span class="sect1"><a href="server.main.html">4. Your main() Routine</a></span></dt><dt><span class="sect1"><a href="server.backendfunctions.html">5. The Backend Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="server.backendfunctions.html#server.init">5.1. Init</a></span></dt><dt><span class="sect2"><a href="server.backendfunctions.html#server.search.retrieve">5.2. Search and Retrieve</a></span></dt><dt><span class="sect2"><a href="server.backendfunctions.html#server.delete">5.3. Delete</a></span></dt><dt><span class="sect2"><a href="server.backendfunctions.html#server.scan">5.4. Scan</a></span></dt></dl></dd><dt><span class="sect1"><a href="server.invocation.html">6. Application Invocation</a></span></dt><dt><span class="sect1"><a href="server.vhosts.html">7. GFS Configuration and Virtual Hosts</a></span></dt></dl></dd><dt><span class="chapter"><a href="asn.html">5. The Z39.50 ASN.1 Module</a></span></dt><dd><dl><dt><span class="sect1"><a href="asn.html#asn.introduction">1. Introduction</a></span></dt><dt><span class="sect1"><a href="asn.preparing.html">2. Preparing PDUs</a></span></dt><dt><span class="sect1"><a href="asn.external.html">3. EXTERNAL Data</a></span></dt><dt><span class="sect1"><a href="asn.pdu.html">4. PDU Contents Table</a></span></dt></dl></dd><dt><span class="chapter"><a href="soap.html">6. SOAP and SRU</a></span></dt><dd><dl><dt><span class="sect1"><a href="soap.html#soap.introduction">1. Introduction</a></span></dt><dt><span class="sect1"><a href="soap.http.html">2. HTTP</a></span></dt><dt><span class="sect1"><a href="soap.xml.html">3. SOAP Packages</a></span></dt><dt><span class="sect1"><a href="soap.srw.html">4. SRU</a></span></dt></dl></dd><dt><span class="chapter"><a href="tools.html">7. Supporting Tools</a></span></dt><dd><dl><dt><span class="sect1"><a href="tools.html#tools.query">1. Query Syntax Parsers</a></span></dt><dd><dl><dt><span class="sect2"><a href="tools.html#PQF">1.1. Prefix Query Format</a></span></dt><dd><dl><dt><span class="sect3"><a href="tools.html#PQF-prox">1.1.1. Using Proximity Operators with PQF</a></span></dt><dt><span class="sect3"><a href="tools.html#pqf-examples">1.1.2. PQF queries</a></span></dt></dl></dd><dt><span class="sect2"><a href="tools.html#CCL">1.2. CCL</a></span></dt><dd><dl><dt><span class="sect3"><a href="tools.html#ccl.syntax">1.2.1. CCL Syntax</a></span></dt><dt><span class="sect3"><a href="tools.html#ccl.qualifiers">1.2.2. CCL Qualifiers</a></span></dt><dt><span class="sect3"><a href="tools.html#ccl.api">1.2.3. CCL API</a></span></dt></dl></dd><dt><span class="sect2"><a href="tools.html#cql">1.3. CQL</a></span></dt><dd><dl><dt><span class="sect3"><a href="tools.html#cql.parsing">1.3.1. CQL parsing</a></span></dt><dt><span class="sect3"><a href="tools.html#cql.tree">1.3.2. CQL tree</a></span></dt><dt><span class="sect3"><a href="tools.html#cql.to.pqf">1.3.3. CQL to PQF conversion</a></span></dt><dt><span class="sect3"><a href="tools.html#cql.to.rpn">1.3.4. Specification of CQL to RPN mappings</a></span></dt><dt><span class="sect3"><a href="tools.html#cql.xcql">1.3.5. CQL to XCQL conversion</a></span></dt><dt><span class="sect3"><a href="tools.html#rpn.to.cql">1.3.6. PQF to CQL conversion</a></span></dt></dl></dd></dl></dd><dt><span class="sect1"><a href="tools.oid.html">2. Object Identifiers</a></span></dt><dd><dl><dt><span class="sect2"><a href="tools.oid.html#tools.oid.database">2.1. OID database</a></span></dt><dt><span class="sect2"><a href="tools.oid.html#tools.oid.std">2.2. Standard OIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="tools.nmem.html">3. Nibble Memory</a></span></dt><dt><span class="sect1"><a href="tools.log.html">4. Log</a></span></dt><dt><span class="sect1"><a href="marc.html">5. MARC</a></span></dt><dd><dl><dt><span class="sect2"><a href="marc.html#tools.turbomarc">5.1. TurboMARC</a></span></dt></dl></dd><dt><span class="sect1"><a href="tools.retrieval.html">6. Retrieval Facility</a></span></dt><dd><dl><dt><span class="sect2"><a href="tools.retrieval.html#tools.retrieval.format">6.1. Retrieval XML format</a></span></dt><dt><span class="sect2"><a href="tools.retrieval.html#tools.retrieval.examples">6.2. Retrieval Facility Examples</a></span></dt><dt><span class="sect2"><a href="tools.retrieval.html#tools.retrieval.api">6.3. API</a></span></dt></dl></dd><dt><span class="sect1"><a href="sorting.html">7. Sorting</a></span></dt><dd><dl><dt><span class="sect2"><a href="sorting.html#idm46170481838848">7.1. Using the Z39.50 sort service</a></span></dt><dt><span class="sect2"><a href="sorting.html#idm46170481835024">7.2. Type-7 sort</a></span></dt></dl></dd><dt><span class="sect1"><a href="facets.html">8. Facets</a></span></dt></dl></dd><dt><span class="chapter"><a href="odr.html">8. The ODR Module</a></span></dt><dd><dl><dt><span class="sect1"><a href="odr.html#odr.introduction">1. Introduction</a></span></dt><dt><span class="sect1"><a href="odr.use.html">2. Using ODR</a></span></dt><dd><dl><dt><span class="sect2"><a href="odr.use.html#odr.streams">2.1. ODR Streams</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.memory.management">2.2. Memory Management</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.encoding.and.decoding">2.3. Encoding and Decoding Data</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.printing">2.4. Printing</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.diagnostics">2.5. Diagnostics</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.summary.and.synopsis">2.6. Summary and Synopsis</a></span></dt></dl></dd><dt><span class="sect1"><a href="odr.programming.html">3. Programming with ODR</a></span></dt><dd><dl><dt><span class="sect2"><a href="odr.programming.html#odr.primitive.asn1.types">3.1. The Primitive ASN.1 Types</a></span></dt><dd><dl><dt><span class="sect3"><a href="odr.programming.html#odr.integer">3.1.1. INTEGER</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.boolean">3.1.2. BOOLEAN</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.real">3.1.3. REAL</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.null">3.1.4. NULL</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.octet.string">3.1.5. OCTET STRING</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.bit.string">3.1.6. BIT STRING</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.object.identifier">3.1.7. OBJECT IDENTIFIER</a></span></dt></dl></dd><dt><span class="sect2"><a href="odr.programming.html#odr.tagging.primitive.types">3.2. Tagging Primitive Types</a></span></dt><dt><span class="sect2"><a href="odr.programming.html#odr.constructed.types">3.3. Constructed Types</a></span></dt><dt><span class="sect2"><a href="odr.programming.html#odr.tagging.constructed.types">3.4. Tagging Constructed Types</a></span></dt><dd><dl><dt><span class="sect3"><a href="odr.programming.html#odr.implicit.tagging">3.4.1. Implicit Tagging</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.explicit.tagging">3.4.2. Explicit Tagging</a></span></dt></dl></dd><dt><span class="sect2"><a href="odr.programming.html#odr.sequence.of">3.5. SEQUENCE OF</a></span></dt><dt><span class="sect2"><a href="odr.programming.html#odr.choice.types">3.6. CHOICE Types</a></span></dt></dl></dd><dt><span class="sect1"><a href="odr.debugging.html">4. Debugging</a></span></dt></dl></dd><dt><span class="chapter"><a href="comstack.html">9. The COMSTACK Module</a></span></dt><dd><dl><dt><span class="sect1"><a href="comstack.html#comstack.synopsis">1. Synopsis (blocking mode)</a></span></dt><dt><span class="sect1"><a href="comstack.introduction.html">2. Introduction</a></span></dt><dt><span class="sect1"><a href="comstack.common.html">3. Common Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="comstack.common.html#comstack.managing.endpoints">3.1. Managing Endpoints</a></span></dt><dt><span class="sect2"><a href="comstack.common.html#comstack.data.exchange">3.2. Data Exchange</a></span></dt></dl></dd><dt><span class="sect1"><a href="comstack.client.html">4. Client Side</a></span></dt><dt><span class="sect1"><a href="comstack.server.html">5. Server Side</a></span></dt><dt><span class="sect1"><a href="comstack.addresses.html">6. Addresses</a></span></dt><dt><span class="sect1"><a href="comstack.ssl.html">7. SSL</a></span></dt><dt><span class="sect1"><a href="comstack.diagnostics.html">8. Diagnostics</a></span></dt><dt><span class="sect1"><a href="comstack.summary.html">9. Summary and Synopsis</a></span></dt></dl></dd><dt><span class="chapter"><a href="future.html">10. Future Directions</a></span></dt><dt><span class="reference"><a href="reference.html">I. Reference</a></span></dt><dd><dl><dt><span class="refentrytitle"><a href="yaz-client.html">yaz-client</a></span><span class="refpurpose"> &#8212; Z39.50/SRU client for implementors</span></dt><dt><span class="refentrytitle"><a href="yaz-ztest.html">yaz-ztest</a></span><span class="refpurpose"> &#8212; Z39.50/SRU Test Server</span></dt><dt><span class="refentrytitle"><a href="yaz-config.html">yaz-config</a></span><span class="refpurpose"> &#8212; Script to get information about YAZ.</span></dt><dt><span class="refentrytitle"><a href="yaz.html">yaz</a></span><span class="refpurpose"> &#8212; Z39.50 toolkit.</span></dt><dt><span class="refentrytitle"><a href="zoomsh.html">zoomsh</a></span><span class="refpurpose"> &#8212; ZOOM shell</span></dt><dt><span class="refentrytitle"><a href="yaz-asncomp.html">yaz-asncomp</a></span><span class="refpurpose"> &#8212; YAZ ASN.1 compiler</span></dt><dt><span class="refentrytitle"><a href="yaz-marcdump.html">yaz-marcdump</a></span><span class="refpurpose"> &#8212; MARC record dump utility</span></dt><dt><span class="refentrytitle"><a href="yaz-iconv.html">yaz-iconv</a></span><span class="refpurpose"> &#8212; YAZ Character set conversion utility</span></dt><dt><span class="refentrytitle"><a href="yaz-log.html">yaz-log</a></span><span class="refpurpose"> &#8212; Log handling in all yaz-based programs</span></dt><dt><span class="refentrytitle"><a href="yaz-illclient.html">yaz-illclient</a></span><span class="refpurpose"> &#8212; ILL client</span></dt><dt><span class="refentrytitle"><a href="yaz-icu.html">yaz-icu</a></span><span class="refpurpose"> &#8212; YAZ ICU utility</span></dt><dt><span class="refentrytitle"><a href="yaz-url.html">yaz-url</a></span><span class="refpurpose"> &#8212; YAZ URL fetch utility</span></dt><dt><span class="refentrytitle"><a href="bib1.html">Bib-1 Attribute Set</a></span><span class="refpurpose"> &#8212; Bib-1 Attribute Set</span></dt><dt><span class="refentrytitle"><a href="yaz-json-parse.html">yaz-json-parse</a></span><span class="refpurpose"> &#8212; YAZ JSON parser</span></dt></dl></dd><dt><span class="appendix"><a href="list-oids.html">A. List of Object Identifiers</a></span></dt><dt><span class="appendix"><a href="bib1-diagnostics.html">B. Bib-1 diagnostics</a></span></dt><dt><span class="appendix"><a href="sru-diagnostics.html">C. SRU diagnostics</a></span></dt><dt><span class="appendix"><a href="license.html">D. License</a></span></dt><dd><dl><dt><span class="sect1"><a href="license.html#license.indexdata">1. Index Data Copyright</a></span></dt></dl></dd><dt><span class="appendix"><a href="indexdata.html">E. About Index Data</a></span></dt><dt><span class="appendix"><a href="credits.html">F. Credits</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>1.1. <a href="introduction.api.html#yaz.layer">YAZ layers</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>3.1. <a href="zoom.html#zoom-connection-options">ZOOM Connection Options</a></dt><dt>3.2. <a href="zoom.query.html#zoom-sort-strategy">ZOOM sort strategy</a></dt><dt>3.3. <a href="zoom.resultsets.html#zoom.resultset.options">ZOOM Result set Options</a></dt><dt>3.4. <a href="zoom.resultsets.html#zoom.search.info.report.options">Search Info Report Options</a></dt><dt>3.5. <a href="zoom.scan.html#zoom.scanset.options">ZOOM Scan Set Options</a></dt><dt>3.6. <a href="zoom.extendedservices.html#zoom.extendedservices.type">Extended Service Type</a></dt><dt>3.7. <a href="zoom.extendedservices.html#zoom.extendedservices.options">Extended Service Common Options</a></dt><dt>3.8. <a href="zoom.extendedservices.html#zoom.item.order.options">Item Order Options</a></dt><dt>3.9. <a href="zoom.extendedservices.html#zoom.illrequest.options">ILL Request Options</a></dt><dt>3.10. <a href="zoom.extendedservices.html#zoom.record.update.options">Record Update Options</a></dt><dt>3.11. <a href="zoom.extendedservices.html#zoom.database.create.options">Database Create Options</a></dt><dt>3.12. <a href="zoom.extendedservices.html#zoom.database.drop.options">Database Drop Options</a></dt><dt>3.13. <a href="zoom.events.html#zoom.event.ids">ZOOM Event IDs</a></dt><dt>5.1. <a href="asn.pdu.html#asn.default.initialize.request">Default settings for PDU Initialize Request</a></dt><dt>5.2. <a href="asn.pdu.html#asn.default.initialize.response">Default settings for PDU Initialize Response</a></dt><dt>5.3. <a href="asn.pdu.html#asn.default.search.request">Default settings for PDU Search Request</a></dt><dt>5.4. <a href="asn.pdu.html#asn.default.search.response">Default settings for PDU Search Response</a></dt><dt>5.5. <a href="asn.pdu.html#asn.default.present.request">Default settings for PDU Present Request</a></dt><dt>5.6. <a href="asn.pdu.html#asn.default.present.response">Default settings for PDU Present Response</a></dt><dt>5.7. <a href="asn.pdu.html#asn.default.delete.result.set.request">Default settings for Delete Result Set Request</a></dt><dt>5.8. <a href="asn.pdu.html#asn.default.delete.result.set.response">Default settings for Delete Result Set Response</a></dt><dt>5.9. <a href="asn.pdu.html#asn.default.scan.request">Default settings for Scan Request</a></dt><dt>5.10. <a href="asn.pdu.html#asn.default.scan.response">Default settings for Scan Response</a></dt><dt>5.11. <a href="asn.pdu.html#asn.default.trigger.resource.control.request">Default settings for Trigger Resource Control Request</a></dt><dt>5.12. <a href="asn.pdu.html#asn.default.resource.control.request">Default settings for Resource Control Request</a></dt><dt>5.13. <a href="asn.pdu.html#asn.default.resource.control.response">Default settings for Resource Control Response</a></dt><dt>5.14. <a href="asn.pdu.html#asn.default.access.control.request">Default settings for Access Control Request</a></dt><dt>5.15. <a href="asn.pdu.html#asn.default.access.control.response">Default settings for Access Control Response</a></dt><dt>5.16. <a href="asn.pdu.html#asn.default.segment">Default settings for Segment</a></dt><dt>5.17. <a href="asn.pdu.html#asn.default.close">Default settings for Close</a></dt><dt>7.1. <a href="tools.html#ccl.common.bib1.attributes">Common Bib-1 attributes</a></dt><dt>7.2. <a href="tools.html#ccl.special.attribute.combos">Special attribute combos</a></dt><dt>7.3. <a href="tools.html#ccl.directives.table">CCL directives</a></dt><dt>7.4. <a href="facets.html#facet.attributes">Facet attributes</a></dt><dt>8.1. <a href="odr.use.html#odr.error.codes">ODR Error codes</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>4.1. <a href="server.invocation.html#server.example.running.unix">Running the GFS on Unix</a></dt><dt>4.2. <a href="server.invocation.html#server.example.apache.sru">Setting up Apache as SRU Frontend</a></dt><dt>4.3. <a href="server.invocation.html#server.example.local.access">Running a server with local access only</a></dt><dt>7.1. <a href="tools.html#example.pqf.simple.terms">PQF queries using simple terms</a></dt><dt>7.2. <a href="tools.html#pqf.example.pqf.boolean.operators">PQF boolean operators</a></dt><dt>7.3. <a href="tools.html#example.pqf.result.sets">PQF references to result sets</a></dt><dt>7.4. <a href="tools.html#example.pqf.attributes">Attributes for terms</a></dt><dt>7.5. <a href="tools.html#example.pqf.proximity">PQF Proximity queries</a></dt><dt>7.6. <a href="tools.html#example.pqf.search.term.type">PQF specification of search term type</a></dt><dt>7.7. <a href="tools.html#example.pqf.mixed.queries">PQF mixed queries</a></dt><dt>7.8. <a href="tools.html#example.ccl.queries">CCL queries</a></dt><dt>7.9. <a href="tools.html#example.ccl.profile">CCL profile</a></dt><dt>7.10. <a href="tools.html#example.cql.to.rpn.mapping">CQL to RPN mapping file</a></dt><dt>7.11. <a href="tools.html#example.cql.to.rpn.string">CQL to RPN string attributes</a></dt><dt>7.12. <a href="tools.html#example.cql.to.rpn.bathprofile">CQL to RPN using Bath Profile</a></dt><dt>7.13. <a href="tools.oid.html#tools.oid.bib1.1">Create OID on stack</a></dt><dt>7.14. <a href="tools.oid.html#tools.oid.bib1.2">Using oid_oiddotstring_to_oid</a></dt><dt>7.15. <a href="tools.oid.html#tools.oid.bib1.3">Using odr_getoidbystr</a></dt><dt>7.16. <a href="tools.oid.html#tools.oid.bib1.4">Create OID with YAZ DB</a></dt><dt>7.17. <a href="tools.oid.html#tools.oid.bib1.5">Use a built-in OID</a></dt><dt>7.18. <a href="marc.html#example.marc.display">Display of MARC record</a></dt><dt>7.19. <a href="tools.retrieval.html#tools.retrieval.marc21">MARC21 backend</a></dt><dt>7.20. <a href="tools.retrieval.html#tools.retrieval.marcxml">MARCXML backend</a></dt><dt>8.1. <a href="odr.use.html#example.odr.encoding.and.decoding.functions">Encoding and decoding functions</a></dt><dt>8.2. <a href="odr.use.html#example.odr.encoding.of.integer">Encoding and decoding of an integer</a></dt><dt>8.3. <a href="odr.use.html#example.odr.element.path.record">Element Path for record</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="introduction.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. Introduction</td></tr></table></div></body></html>

yaz/trunk/fuentes/doc/installation.html

-                      r255
+                      r265
     <a class="ulink" href="http://www.freebsd.org/" target="_top">FreeBSD (i386)</a>,
     <a class="ulink" href="http://www.apple.com/macosx/" target="_top">MAC OSX</a>,
+    <a class="ulink" href="http://www.oracle.com/solaris" target="_top">Solaris</a>,
+    Windows 7, Windows XP.
+    Windows 10.
    </p><p>
     Some versions have be known to work on HP/UX,
+    Some versions have be known to work on Windows XP, Solaris, HP/UX,
     DEC Unix, <a class="ulink" href="http://www.netbsd.org" target="_top">NetBSD</a>,
     <a class="ulink" href="http://www.openbsd.org" target="_top">OpenBSD</a>,

yaz/trunk/fuentes/doc/installation.unix.html

-                      r255
+                      r265
       <a class="ulink" href="http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/net/yaz/README.html" target="_top">http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/net/yaz/README.html</a>
      </p></li></ul></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="installation.source.unix"></a>2.1. Compiling from source on Unix</h3></div></div></div><p>
+     Note that if your system doesn't have a native ANSI C compiler, you may
+     have to acquire one separately. We recommend
+     <a class="ulink" href="http://gcc.gnu.org" target="_top">GCC</a>.
+     You can choose to compile YAZ from official tar releases from
+     <a class="ulink" href="http://ftp.indexdata.com/pub/yaz/" target="_top">http://ftp.indexdata.com/pub/yaz/</a>
+     or clone it via Github
+     <a class="ulink" href="https://github.com/indexdata/yaz.git" target="_top">https://github.com/indexdata/yaz.git</a>.
     </p><p>
      If you wish to use character set conversion facilities in YAZ or if you
 …
      <a class="ulink" href="http://www.gnu.org/software/libtool/" target="_top">Libtool</a>
      are used to generate Makefiles and configure YAZ for the system.
      You do <span class="emphasis"><em>not</em></span> these tools unless you're using the
+     You do <span class="emphasis"><em>not</em></span> need these tools unless you're using the
      Git version of YAZ.
     </p><p>
 …
      written in <a class="ulink" href="http://www.tcl.tk/" target="_top">Tcl</a>.
      But as for Bison you do not need it unless you're using Git
      version of YAZ or you're using the compiler to built own codecs
+     version of YAZ or you're using the compiler to build your own codecs
      for private ASN.1.
     </p><p>
+     Generally it should be sufficient to run configure without options,
+     like this:
+     If you are checking out from Git, run:
+     </p><pre class="screen">
+      ./buildconf.sh
+     </pre><p>
+     This will create the <code class="filename">configure</code> script and Makefiles.
+    </p><p>
+     The next step is always:
     </p><pre class="screen">
      ./configure
 …
         search for iconv on the system. Use this option if it
         doesn't find iconv. Alternatively,
         <code class="literal">--without-iconv</code>, can be uset to force YAZ
+        <code class="literal">--without-iconv</code>, can be used to force YAZ
         not to use iconv.
         </p></dd><dt><span class="term">
 …
         Use this option if you want XSLT and XML support.
         By default, configure will
         search for libxslt on the system. Use this option if it
+        search for libxslt on the system. Use this option if
         libxslt is not found automatically. Alternatively,
         <code class="literal">--without-xslt</code>, can be used to force YAZ
 …
         Use this option if you want YAZ to use XML and support SRU/Solr.
         By default, configure will
         search for libxml2 on the system. Use this option if it
+        search for libxml2 on the system. Use this option if
         libxml2 is not found automatically. Alternatively,
         <code class="literal">--without-xml2</code>, can be used to force YAZ
 …
         <span class="application">icu-config</span> will be used if found.
         </p></dd><dt><span class="term">
-        <code class="literal">--with-libgcrypt</code>[=<em class="replaceable"><code>prefix</code></em>]
-       </span></dt><dd><p>YAZ will be linked with
-        <a class="ulink" href="http://www.gnu.org/software/libgcrypt/" target="_top">Libgcrypt</a> in the prefix if given.
-        If prefix is not given, the libraries exposed by the script
-        <span class="application">libgcrypt-config</span> will be used if found.
-        </p></dd><dt><span class="term">
         <code class="literal">--with-memcached</code>
        </span></dt><dd><p>YAZ will be linked with
         <a class="ulink" href="http://libmemcached.org/" target="_top">libMemcached</a> to allow
         for result-set caching for ZOOM.
+        The prefix can not be given. Note that YAZ will only search
+        for libMemcached if Libgcrypt is also enabled.
+        The prefix can not be given.
         Note that 0.40 of libmemcached is required.
        </p></dd><dt><span class="term">
 …
         to allow for result-set caching for ZOOM on a
         <a class="ulink" href="http://redis.io/" target="_top">redis</a> server.
+        The prefix can not be given. Note that YAZ will only search
+        for hiredis if Libgcrypt is also enabled.
+        The prefix can not be given.
        </p></dd></dl></div><p>
     </p><p>
 …
      applications using the YAZ toolkit.
      If you're used to Makefiles this shouldn't be hard. As for
      other libraries you have used before, you have to set a proper include
+     other libraries you have used before, you need to set a proper include
      path for your C/C++ compiler and specify the location of
      YAZ libraries. You can do it by hand, but generally we suggest

yaz/trunk/fuentes/doc/installation.win32.html

-                      r255
+                      r265
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>3. Windows</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="YAZ User's Guide and Reference"><link rel="up" href="installation.html" title="Chapter 2. Compilation and Installation"><link rel="prev" href="installation.unix.html" title="2. UNIX"><link rel="next" href="zoom.html" title="Chapter 3. ZOOM"></head><body><link rel="stylesheet" type="text/css" href="common/style1.css"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3. Windows</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="installation.unix.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Compilation and Installation</th><td width="20%" align="right"> <a accesskey="n" href="zoom.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="installation.win32"></a>3. Windows</h2></div></div></div><p>The easiest way to install YAZ on Windows is by downloading
    an installer from
+   <a class="ulink" href="http://ftp.indexdata.com/pub/yaz/win32/" target="_top">here</a>.
+   <a class="ulink" href="http://ftp.indexdata.com/pub/yaz/win32/" target="_top">
+    Index Data's Windows support area
+   </a>.
    The installer comes with source too - in case you wish to
    compile YAZ with different compiler options, etc.
 …
      with <a class="ulink" href="http://www.visualstudio.com" target="_top">
      Microsoft Visual Studio</a>. It has been tested with
      Microsoft Visual Studio 2013.
+     Microsoft Visual Studio 2015.
     </p><p>
      Start a command prompt and switch the sub directory
 …
         (<code class="filename">cql.y</code>).
        </p><p>
+        A Windows version of GNU Bison is part of
+        <a class="ulink" href="http://msysgit.github.io/" target="_top">Git for Windows</a>.
+        A Windows version of GNU Bison can be fetched from here:
+        <a class="ulink" href="http://ftp.indexdata.dk/pub/support/windows/bison-2.4.1-setup.exe" target="_top">
+          Index Data's Windows support area
+        </a>.
        </p></dd><dt><span class="term"><code class="literal">HAVE_ICONV</code>,
        <code class="literal">ICONV_DIR</code></span></dt><dd><p>
 …
          <a class="ulink" href="http://xmlsoft.org/XSLT/" target="_top">libxslt</a> source directory.
         </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
           libxslt depends libxml2.
+          libxslt depends on libxml2.
          </p></div></dd><dt><span class="term"><code class="literal">HAVE_ICU</code>,
        <code class="literal">ICU_DIR</code></span></dt><dd><p>
 …
          <code class="literal">ICU_DIR</code> to the
          <a class="ulink" href="http://www.icu-project.org/" target="_top">ICU</a> source directory.
+        </p><p>
+         Pre-compiled ICU libraries for various versions of Visual Studio
+         can be found
+         <a class="ulink" href="http://www.npcglib.org/~stathis/blog/precompiled-icu/" target="_top">
+          here
+         </a> or from Index Data's <a class="ulink" href="http://ftp.indexdata.dk/pub/support/windows/" target="_top">Windows support site</a>.
         </p></dd></dl></div><p>
     </p><p>
 …
       </p></dd><dt><span class="term"><code class="filename">bin/yaz-icu.exe</code></span></dt><dd><p>This program exposes the ICU wrapper library if that
        is enabled for YAZ. Only if ICU is available this program is
        build.
+       built.
       </p></dd><dt><span class="term"><code class="filename">bin/zoomsh.exe</code></span></dt><dd><p>
         Simple console application implemented on top of the
 …
       </p></dd><dt><span class="term"><code class="filename">bin/zoomtst1.exe</code>,
        <code class="filename">bin/zoomtst2.exe</code>, ..</span></dt><dd><p>
         Several small applications that demonstrates the ZOOM API.
+        Several small applications that demonstrate the ZOOM API.
       </p></dd></dl></div><p>
     </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="installation-linking-yaz-win32"></a>3.2. How to make apps using YAZ on Windows</h3></div></div></div><p>

yaz/trunk/fuentes/doc/introduction.api.html

-                      r255
+                      r265
     toolkit offers several different levels of access to the
     <a class="ulink" href="http://www.loc.gov/z3950/agency/" target="_top">ISO23950/Z39.50</a>,
     <a class="ulink" href="http://www.nlc-bnc.ca/iso/ill/" target="_top">ILL</a> and
+    <a class="ulink" href="http://www.nlc-bnc.ca/iso/ill/standard.htm" target="_top">ILL</a> and
     <a class="ulink" href="http://www.loc.gov/standards/sru/" target="_top">SRU</a>
     protocols.
 …
     level APIs of YAZ.
    </p><p>
     The YAZ toolkit modules is shown in figure <a class="xref" href="introduction.api.html#yaz.layer" title="Figure 1.1. YAZ layers">Figure 1.1, &#8220;YAZ layers&#8221;</a>.
+    The YAZ toolkit modules are shown in figure <a class="xref" href="introduction.api.html#yaz.layer" title="Figure 1.1. YAZ layers">Figure 1.1, &#8220;YAZ layers&#8221;</a>.
    </p><div class="figure"><a name="yaz.layer"></a><p class="title"><b>Figure 1.1. YAZ layers</b></p><div class="figure-contents"><div class="mediaobject"><img src="apilayer.png" alt="YAZ layers"></div></div></div><br class="figure-break"><p>
     There are four layers.
 …
    </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
      If you are using the premade definitions of the Z39.50 ASN.1 module, and you
      are not adding new protocol of your own, the only parts of <acronym class="acronym">ODR</acronym> that you
+     are not adding a new protocol of your own, the only parts of <acronym class="acronym">ODR</acronym> that you
      need to worry about are documented in
      <a class="xref" href="odr.use.html" title="2. Using ODR">Section 2, &#8220;Using ODR&#8221;</a>.

yaz/trunk/fuentes/doc/introduction.html

-                      r255
+                      r265
     </p></li><li class="listitem"><p>
       Includes BER encoders/decoders for the
       <a class="ulink" href="http://www.nlc-bnc.ca/iso/ill/" target="_top">ISO ILL</a>
+      <a class="ulink" href="http://www.nlc-bnc.ca/iso/ill/standard.htm" target="_top">ISO ILL</a>
       protocol.
     </p></li><li class="listitem"><p>
       Supports
       <a class="ulink" href="http://lucene.apache.org/solr/" target="_top">Solr</a> Web Service version 1.4.x
+      <a class="ulink" href="http://lucene.apache.org/solr/" target="_top">Apache Solr</a> Web Service version 1.4.x
       (client side only)
      </p></li><li class="listitem"><p>
 …
   </p><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="introduction.reading"></a>1. Reading this Manual</h2></div></div></div><p>
     Most implementors only need to read a fraction of the
     material in thie manual, so a quick walkthrough of the chapters
+    material in this manual, so a quick walkthrough of the chapters
     is in order.
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
       <a class="xref" href="installation.html" title="Chapter 2. Compilation and Installation">Chapter 2, <i>Compilation and Installation</i></a> contains installation
       instructions for YAZ. You don't need reading this
+      instructions for YAZ. You don't need to read this
       if you expect to download YAZ binaries.
       However, the chapter contains information about how
 …
      </p></li><li class="listitem"><p>
       <a class="xref" href="zoom.html" title="Chapter 3. ZOOM">Chapter 3, <i>ZOOM</i></a> describes the ZOOM API of YAZ.
       This is definitely worth a read if you wish to develop a Z39.50/SRU
+      This is definitely worth reading if you wish to develop a Z39.50/SRU
       client.
      </p></li><li class="listitem"><p>
 …
     </p></li><li class="listitem"><p>
       <a class="xref" href="yaz-client.html" title="yaz-client"><span class="refentrytitle">yaz-client</span>(1)</a> describes how to use the YAZ Z39.50
       client. If you're developer and wish to test your server
+      client. If you're a developer and wish to test your server
       or a server from another party, you might find this chapter
       useful.
 …
       ODR module which is the work horse that encodes and decodes
       BER packages. Implementors using ZOOM only, do <span class="emphasis"><em>not</em></span>
       need reading this.
+      need to read this.
       Most other Z39.50 implementors only need to read the first two
       sections (<a class="xref" href="odr.html#odr.introduction" title="1. Introduction">Section 1, &#8220;Introduction&#8221;</a> and

yaz/trunk/fuentes/doc/license.html

r255	r265
1	1	<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Appendix D. License</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="YAZ User's Guide and Reference"><link rel="up" href="index.html" title="YAZ User's Guide and Reference"><link rel="prev" href="sru-diagnostics.html" title="Appendix C. SRU diagnostics"><link rel="next" href="indexdata.html" title="Appendix E. About Index Data"></head><body><link rel="stylesheet" type="text/css" href="common/style1.css"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix D. License</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sru-diagnostics.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="indexdata.html">Next</a></td></tr></table><hr></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="license"></a>Appendix D. License</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="sect1"><a href="license.html#license.indexdata">1. Index Data Copyright</a></span></dt></dl></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="license.indexdata"></a>1. Index Data Copyright</h2></div></div></div><p>
2		Copyright © 1995-2015 Index Data.
	2	Copyright © 1995-2016 Index Data.
3	3	</p><p>
4	4	All rights reserved.

yaz/trunk/fuentes/doc/local.ent

r255	r265
1		<!ENTITY version "5.1~~4.3~~">
	1	<!ENTITY version "5.15.2">

yaz/trunk/fuentes/doc/manref.xml

-                      r255
+                      r265
  <refentryinfo>
   <productname class="trade">YAZ</productname>
   <productnumber>5.14.3</productnumber>
   <info><orgname>Index Data</orgname></info>
+  <productnumber>5.15.2</productnumber>
+  <orgname>Index Data</orgname>
  </refentryinfo>
 …
      <listitem><para>
        If specified, logging of protocol packages will be appended
        file given. If <replaceable>filename</replaceable> is
+       to the file given. If <replaceable>filename</replaceable> is
        specified as <literal moreinfo="none">-</literal>, the output is written
        to <literal moreinfo="none">stdout</literal>.
 …
        connect to a proxy on the address and port given.
        The actual target will be specified as part of the InitRequest
        to inform the proxy about actual target.
+       to inform the proxy about the actual target.
       </para></listitem>
     </varlistentry>
 …
     <listitem>
      <para>Sets the name(s) of the database(s) to search. One or more
       databases may be specified separated by blanks. This commands overrides
+      databases may be specified, separated by blanks. This command overrides
       the database given in <replaceable>zurl</replaceable>.
      </para>
 …
       position given by
       <replaceable>start</replaceable>
       a number of records given by <replaceable>number</replaceable>. If
+      and a number of records given by <replaceable>number</replaceable>. If
       <replaceable>start</replaceable> is not given, then the client
       will fetch from position of the last retrieved record plus 1. If
+      will fetch from the position of the last retrieved record plus 1. If
       <replaceable>number</replaceable> is not given, then one record will
       be fetched at a time.
 …
      <simpara>
       Sets preferred position for scan. This value
       is used in next scan. By default position is 1.
+      is used in the next scan. By default, position is 1.
      </simpara>
     </listitem>
 …
     <listitem>
      <simpara>
       Set step-size for scan. This value is used in next scan
+      Set step-size for scan. This value is used in the next scan
       sent to the target. By default step-size is 0.
      </simpara>
 …
     </term>
     <listitem>
      <para>Sets up a authentication string if a server requires
+     <para>Sets up an authentication string if a server requires
       authentication (v2 OpenStyle). The authentication string is first
       sent to the server when the
 …
     </term>
     <listitem>
      <para>Sets the number of records should be returned if the
+     <para>Sets the number of records that should be returned if the
       number of records in the result set is between the values of
       <literal moreinfo="none">lslb</literal> and <literal moreinfo="none">ssub</literal>.
 …
     <listitem>
      <para>Sets the element set name for the records. Many targets support
       element sets are B (for brief) and F (for full).
+      element sets B (for brief) and F (for full).
      </para>
     </listitem>
 …
       <literal moreinfo="none">cql</literal> for CQL (Type-104 search with CQL OID),
       <literal moreinfo="none">ccl2rpn</literal> for
       <link linkend="CCL">CCL</link> to RPN conversion (Type-1 Query).
+      <link linkend="CCL">CCL</link> to RPN conversion (Type-1 Query),
       <literal moreinfo="none">cql2rpn</literal> for
       CQL to RPN conversion (Type-1 Query).
 …
       "&lt;", then the following characters are treated as a filename
       with the records to be updated. Otherwise doc is treated as
       a document itself. The doc may also be quited in double quotes.
+      a document itself. The doc may also be quoted in double quotes.
       If doc is omitted, the last received record (as part of present
       response or piggybacked search response) is used for the update.
 …
     <listitem>
      <para>Executes list of commands from
       file <replaceable>filename</replaceable>, just like source on
+      file <replaceable>filename</replaceable>, just like 'source' on
       most UNIX shells. A single dot (<literal moreinfo="none">.</literal>) can be used
       as an alternative.
 …
     </term>
     <listitem>
      <para>Specifies whether YAZ client automatically reconnect if
+     <para>Specifies whether YAZ client automatically reconnects if the
       target closes connection (Z39.50 only).
      </para>
 …
      <para>Specifies whether YAZ client should wait for
       response protocol packages after a request.
       By default YAZ client waits (on) for response packages immediately
+      By default YAZ client waits (<literal moreinfo="none">on</literal>) for response packages immediately
       after a command (find, show) has been issued. If <literal moreinfo="none">off</literal>
       is used, YAZ client does not attempt to receive packages automatically.
 …
      </para>
      <para>
       If <replaceable>marcharset</replaceable> is given, it specifies name
+      If <replaceable>marccharset</replaceable> is given, it specifies name
       of the character set of retrieved MARC records from server. See
       also <literal moreinfo="none">marcharset</literal> command.
+      also <literal moreinfo="none">marccharset</literal> command.
      </para>
      <note>
 …
       name for the OID, <replaceable>class</replaceable> is the
       class, and <replaceable>OID</replaceable> is the raw OID in
       dot notation. Class is one <literal moreinfo="none">appctx</literal>,
+      dot notation. Class is one of: <literal moreinfo="none">appctx</literal>,
       <literal moreinfo="none">absyn</literal>, <literal moreinfo="none">attet</literal>,
       <literal moreinfo="none">transyn</literal>, <literal moreinfo="none">diagset</literal>,
 …
     f "donald knuth"
    </screen>
    In those queries no attributes was specified.
+   In those queries, no attributes were specified.
    This leaves it up to the server what fields to search but
    most servers will search in all fields. Some servers does not
+   most servers will search in all fields. Some servers do not
    support this feature though, and require that some attributes
    are defined. To add one attribute you could do:
 …
  <refentryinfo>
   <productname class="trade">YAZ</productname>
   <productnumber>5.14.3</productnumber>
   <info><orgname>Index Data</orgname></info>
+  <productnumber>5.15.2</productnumber>
+  <orgname>Index Data</orgname>
  </refentryinfo>
 …
   </para>
   <para>
    For UNIX local socket the address is the filename of the local socket.
+   For UNIX local socket, the address is the filename of the local socket.
   </para>
  </refsect1>
 …
   <listitem><para>
    Operate the server in threaded mode. The server creates a thread
    for each connection rather than a fork a process. Only available
    on UNIX systems that offers POSIX threads.
+   for each connection rather than fork a process. Only available
+   on UNIX systems that offer POSIX threads.
   </para></listitem>
  </varlistentry>
 …
   <term><literal moreinfo="none">-w </literal><replaceable>dir</replaceable></term>
   <listitem><para>
    The server changes to this directory during before listening
    on incoming connections. This option is useful
+   The server changes to this directory before listening
+   to incoming connections. This option is useful
    when the server is operating from the <application moreinfo="none">inetd</application>
    daemon (see <literal moreinfo="none">-i</literal>).
 …
  </term>
  <listitem><para>
   Specifies that the server should write its Process ID to
+  Specifies that the server should write its Process ID to the
   file given by <replaceable>pidfile</replaceable>.
   A typical location would be <filename moreinfo="none">/var/run/yaz-ztest.pid</filename>.
 …
     to return any number of hits. <command moreinfo="none">yaz-ztest</command> includes
 MARC records for testing. Hit counts exceeding 24 will make
     <command moreinfo="none">yaz-ztest</command> return the same record batch over and over..
     So record at position 1, 25, 49, etc .. are equivalent.
+    <command moreinfo="none">yaz-ztest</command> return the same record batch over and over.
+    So record at position 1, 25, 49, etc. are equivalent.
    </para>
    <para>
     For XML if no element set is given or element has value "marcxml",
+    For XML, if no element set is given or element has value "marcxml",
     MARCXML is returned (each of the 24 dummy records converted from
     ISO2709 to XML). For element set OP, OPAC XML is returned.
+    ISO2709 to XML). For element set OP, then OPAC XML is returned.
    </para>
    <para>
     yaz-ztest may also return predefined XML records (for testing).
     This is enabled if <literal moreinfo="none">YAZ_ZTEST_XML_FETCH</literal> environment
     variable is defined. A record is fetched form a file (one record per file).
+    variable is defined. A record is fetched from a file (one record per file).
     The path for the filename is
     <replaceable>F</replaceable><replaceable>E</replaceable><literal moreinfo="none">.</literal><replaceable>d</replaceable><literal moreinfo="none">.xml</literal>
 …
      value which specifies the delay in seconds.
      Alternatively the value may be given as two floating point numbers
      separated by colon, which wil make <command moreinfo="none">yaz-ztest</command> perform
+     separated by colon, which will make <command moreinfo="none">yaz-ztest</command> perform
      a random sleep between the first and second number.
    </para>
 …
 <note>
  <para>
   Not all Z39.50 clients allows the VHOST information to be set.
   For those the selection of the backend must rely on the
+  Not all Z39.50 clients allow the VHOST information to be set.
+  For those, the selection of the backend must rely on the
   TCP/IP information alone (port and address).
  </para>
 …
     <listitem>
      <para>
       identifier for this listener. This may be referred to from
+      Identifier for this listener. This may be referred to from
       server sections.
      </para>
 …
     <para>
      Specifies a working directory for this backend server. If
      specifid, the YAZ fronend changes current working directory
+     specified, the YAZ frontend changes current working directory
      to this directory whenever a backend of this type is
      started (backend handler bend_start), stopped (backend handler hand_stop)
 …
     <para>
      Specifies a filename that includes CQL to RPN conversion for this
      backend server. See <xref linkend="cql.to.rpn"/>
+     backend server. See <xref linkend="cql.to.rpn"/>.
      If given, the backend server will only "see" a Type-1/RPN query.
     </para>
 …
     <para>
      Specifies a filename that includes CCL to RPN conversion for this
      backend server. See <xref linkend="ccl.qualifiers"/>
+     backend server. See <xref linkend="ccl.qualifiers"/>.
      If given, the backend server will only "see" a Type-1/RPN query.
     </para>
 …
     <para>
      Specifies the stylesheet reference to be part of SRU HTTP responses
      when the client does not specify one. If neither this is given, nor
      the client specifies one, no stylesheet reference is part of the
+     when the client does not specify one. If none is given, then if
+     the client does not specify one, then no stylesheet reference is part of the
      SRU HTTP response.
     </para>
 …
     <para>
      Specifies a path for local file access using HTTP. All URLs with
      a leading prefix (/ exluded) that matches the value of docpath
+     a leading prefix (/ excluded) that matches the value of <literal moreinfo="none">docpath</literal>
      are used for file access. For example, if the server is to offer
      access in directory <literal moreinfo="none">xsl</literal>, the docpath would be
      <literal moreinfo="none">xsl</literal> and all URLs of the form
      <literal moreinfo="none">http://host/exl</literal> will result in a local file access.
+     <literal moreinfo="none">http://host/xsl</literal> will result in a local file access.
     </para>
    </listitem>
 …
      Specifies SRW/SRU ZeeRex content for this server. Copied verbatim
      to the client. As things are now, some of the Explain content
      seeem redundant because host information, etc. is also stored
+     seem redundant because host information, etc. is also stored
      elsewhere.
     </para>
 …
     <para>
      Specifies maximum record size/message size, in bytes. This
      value also servers as maximum size of <emphasis>incoming</emphasis>
+     value also serves as the maximum size of <emphasis>incoming</emphasis>
      packages (for Record Updates etc). It's the same value as that
      given by the <literal moreinfo="none">-k</literal> option.
 …
    <listitem>
     <para>
      Enables the retrieval facility supporting conversions and
+     Enables the retrieval facility to support conversions and
      specifications of record formats/types.
      See <xref linkend="tools.retrieval"/> for
 …
  <literal moreinfo="none">"server2"</literal> is reached by the two listeners specified.
  In order to distinguish between the two, a virtual host has
  been specified for each of server in the <literal moreinfo="none">host</literal>
+ been specified for each server in the <literal moreinfo="none">host</literal>
  elements.
 </para>
 …
  <refentryinfo>
   <productname class="trade">YAZ</productname>
   <productnumber>5.14.3</productnumber>
   <info><orgname>Index Data</orgname></info>
+  <productnumber>5.15.2</productnumber>
+  <orgname>Index Data</orgname>
  </refentryinfo>
 …
     <term>-V</term>
     <listitem><para>
       veturns YAZ SHA1 ID (from Git) and version.
+      Returns YAZ SHA1 ID (from Git) and version.
      </para></listitem>
    </varlistentry>
 …
  <refentryinfo>
   <productname class="trade">YAZ</productname>
   <productnumber>5.14.3</productnumber>
   <info><orgname>Index Data</orgname></info>
+  <productnumber>5.15.2</productnumber>
+  <orgname>Index Data</orgname>
  </refentryinfo>
 …
  <refsect1><title>COPYRIGHT</title>
   <para>
    Copyright © 1995-2015 Index Data.
+   Copyright © 1995-2016 Index Data.
   </para>
   <para>
 …
  <refentryinfo>
   <productname class="trade">YAZ</productname>
   <productnumber>5.14.3</productnumber>
   <info><orgname>Index Data</orgname></info>
+  <productnumber>5.15.2</productnumber>
+  <orgname>Index Data</orgname>
  </refentryinfo>
 …
  <refentryinfo>
   <productname class="trade">YAZ</productname>
   <productnumber>5.14.3</productnumber>
   <info><orgname>Index Data</orgname></info>
+  <productnumber>5.15.2</productnumber>
+  <orgname>Index Data</orgname>
  </refentryinfo>
 …
    <command moreinfo="none">yaz-asncomp</command> allows you to specify name of
    resulting source via options. Alternatively, you can specify
    a DEFINISIONS file, which provides customized output to
+   a DEFINITIONS file, which provides customized output to
    many output files - if the ASN.1 specification file consists
    of many modules.
 …
    traditional rules for Shell like configuration files.
    That is # denotes the beginning of a comment. Definitions
    are line oriented. The definitions files usually consists of
+   are line oriented. The definitions files usually consist of
    a series of variable assignments of the form:
   </para>
 …
        <replaceable>name</replaceable> in module
        <replaceable>module</replaceable> to value.
        Value consists of to or three tokens. The first token
+       Value consists of two or three tokens. The first token
        is name of the integer in the <literal moreinfo="none">union</literal> that
        is used as selector for the <literal moreinfo="none">union</literal> itself.
 …
  <refentryinfo>
   <productname class="trade">YAZ</productname>
   <productnumber>5.14.3</productnumber>
   <info><orgname>Index Data</orgname></info>
+  <productnumber>5.15.2</productnumber>
+  <orgname>Index Data</orgname>
  </refentryinfo>
 …
     <term>-f <replaceable>from</replaceable></term>
     <listitem><para>
       Specify the character set <replaceable>from</replaceable>
+      Specify the character set
       of the input MARC record.
       Should be used in conjunction with option <literal moreinfo="none">-t</literal>.
 …
     <term>-t <replaceable>to</replaceable></term>
     <listitem><para>
       Specify the character set <replaceable>of</replaceable>
+      Specify the character set
       of the output.
       Should be used in conjunction with option <literal moreinfo="none">-f</literal>.
 …
       Writes a chunk of records to a separate file with prefix given,
       i.e. splits a record batch into files with only at most
       "chunk" ISO2709 record per file. By default chunk is 1 (one record
+      "chunk" ISO2709 records per file. By default chunk is 1 (one record
       per file). See option <literal moreinfo="none">-C</literal>.
      </para></listitem>
 …
     <term>-p</term>
     <listitem><para>
       Makes yaz-marcdump prints record number and input file offset
+      Makes yaz-marcdump print record number and input file offset
       of each record read.
      </para></listitem>
 …
     <term>-n</term>
     <listitem><para>
       MARC output is omitted so that MARC input is only checkecd.
+      MARC output is omitted so that MARC input is only checked.
      </para></listitem>
    </varlistentry>
 …
  <refentryinfo>
   <productname class="trade">YAZ</productname>
   <productnumber>5.14.3</productnumber>
   <info><orgname>Index Data</orgname></info>
+  <productnumber>5.15.2</productnumber>
+  <orgname>Index Data</orgname>
  </refentryinfo>
 …
  <refsect1><title>DESCRIPTION</title>
   <para>
    <command moreinfo="none">yaz-iconv</command> converts data in file in character
+   <command moreinfo="none">yaz-iconv</command> converts data in the character
    set specified by <replaceable>from</replaceable> to output in
    character set as specified by <replaceable>to</replaceable>.
   </para>
   <para>
    This <command moreinfo="none">yaz-iconv</command> utility similar to the
+   the character set as specified by <replaceable>to</replaceable>.
+  </para>
+  <para>
+   This <command moreinfo="none">yaz-iconv</command> utility is similar to the
    <command moreinfo="none">iconv</command> found on many POSIX systems (Glibc, Solaris, etc).
   </para>
 …
    <filename moreinfo="none">yaz/yaz-iconv.h</filename> is a wrapper for the
    library system call iconv. But YAZ' iconv utility also implements
    conversions on its own. The table below lists characters sets (or encodings).
+   conversions on its own. The table below lists characters sets (or encodings)
    that are supported by YAZ. Each character set is marked with either
    <emphasis>encode</emphasis> or <emphasis>decode</emphasis>. If
    an encoding is encode-enabled YAZ may convert <emphasis>to</emphasis>
    to the designated encoding. If an encoding is decode-enabled, YAZ
+   an encoding is encode-enabled, YAZ may convert <emphasis>to</emphasis>
+   the designated encoding. If an encoding is decode-enabled, YAZ
    may convert <emphasis>from</emphasis> the designated encoding.
   </para>
 …
     <listitem>
      <para>
       Like MARC8 but with conversion prefers non-combined characters
+      Like MARC8 but conversion prefers non-combined characters
       in the Latin-1 plane over combined characters.
      </para>
 …

Context Navigation

Legend: