Changeset 265
- Timestamp:
- Feb 2, 2016, 6:13:30 PM (5 years ago)
- Location:
- yaz/trunk
- Files:
-
- 1 added
- 3 deleted
- 158 edited
Legend:
- Unmodified
- Added
- Removed
-
yaz/trunk/fuentes/ChangeLog
r255 r265 1 commit 738b345708b245e67cded6d917393a80b5bd4eca 2 Author: Adam Dickmeiss <adam@indexdata.dk> 3 Date: Mon Jan 11 13:06:41 2016 +0000 4 5 Version 5.15.2 6 7 commit f43944a7ffc80bfcf8ec6a5ec1935c354d4bcac2 8 Author: Adam Dickmeiss <adam@indexdata.dk> 9 Date: Mon Jan 11 11:04:38 2016 +0100 10 11 Happy new year 12 13 commit d35bb455afe361c1f8ed360cce55e8fb75c6eec7 14 Author: Adam Dickmeiss <adam@indexdata.dk> 15 Date: Mon Jan 11 11:04:11 2016 +0100 16 17 Mention configure as a script 18 19 commit 2eb6e27fe677e40f53327f5af456d39df5b24edf 20 Author: Adam Dickmeiss <adam@indexdata.dk> 21 Date: Mon Jan 11 11:01:00 2016 +0100 22 23 Mention Github + buildconf.sh 24 25 commit ccfd0bb7d8af350d358e70a3b4bedb289e2be042 26 Author: Adam Dickmeiss <adam@indexdata.dk> 27 Date: Mon Jan 11 11:00:15 2016 +0100 28 29 Update list of Debian packages for buildconf.sh 30 31 commit 4c57a37b6ff798585433440641d9c86a25c9092c 32 Author: Adam Dickmeiss <adam@indexdata.dk> 33 Date: Wed Jan 6 11:26:26 2016 +0100 34 35 Use submodules from Github 36 37 commit 7b112287740b44d1dd939cea0ecca217356affd5 38 Author: Adam Dickmeiss <adam@indexdata.dk> 39 Date: Thu Nov 26 10:06:18 2015 +0100 40 41 No more manifest files 42 43 commit d4514445a1caea19faff82c3541a716ddfdc2b0f 44 Author: Adam Dickmeiss <adam@indexdata.dk> 45 Date: Tue Nov 24 14:14:20 2015 +0100 46 47 Include links to pre-compiled ICU binaries 48 49 commit b687939804570b289122ca78f25b5f255ed36326 50 Author: Adam Dickmeiss <adam@indexdata.dk> 51 Date: Tue Nov 24 14:14:11 2015 +0100 52 53 Update list of supported platforms 54 55 commit 05f7afcaa053728864a9b1b6d7bd1a6a48701f2c 56 Author: Adam Dickmeiss <adam@indexdata.dk> 57 Date: Tue Nov 24 14:13:35 2015 +0100 58 59 Update doc/common 60 61 commit ebfa76b327665398553785b6a00e69d119ba9297 62 Merge: b1a5a64 4e71d4a 63 Author: Adam Dickmeiss <adam@indexdata.dk> 64 Date: Tue Nov 24 13:54:30 2015 +0100 65 66 Merge branch 'master' of ssh://git.indexdata.com:222/home/git/pub/yaz 67 68 commit b1a5a6402e767afee10073381d842642d3a640d0 69 Author: Adam Dickmeiss <adam@indexdata.dk> 70 Date: Tue Nov 24 13:52:36 2015 +0100 71 72 Win32/64 split. Use ICU compiled with VS2015 73 74 commit 4e71d4a715bca8fc6a9a1010ffa00def8c63ab1b 75 Author: Adam Dickmeiss <adam@indexdata.dk> 76 Date: Tue Nov 17 15:14:06 2015 +0100 77 78 Remove <info> from ref entry header 79 80 commit 81358822816ed75a14af31a0656550de1329c33a 81 Author: Adam Dickmeiss <adam@indexdata.dk> 82 Date: Mon Nov 16 16:01:50 2015 +0100 83 84 README.md 85 86 commit 319ea8d6f518d08c1f50d8ec80899e1bc6ca7923 87 Author: Adam Dickmeiss <adam@indexdata.dk> 88 Date: Mon Nov 16 13:27:13 2015 +0100 89 90 Update URL for Bison Windows version 91 92 It used to be part of Git for Windows. It no longer is. 93 94 commit 02b4f0ab937b62d892d3e0918439da770fe720c2 95 Author: Adam Dickmeiss <adam@indexdata.dk> 96 Date: Thu Nov 12 08:54:19 2015 +0000 97 98 Version 5.15.1 99 100 commit 2bfb0b990bbbe0f9c5ef9e78b094a2063bc45f33 101 Author: Adam Dickmeiss <adam@indexdata.dk> 102 Date: Thu Nov 12 09:48:02 2015 +0100 103 104 Add test case for YAZ-861 YAZ-865 105 106 commit 8484857deb143d2a71498d3b8b7a345328dac969 107 Author: Adam Dickmeiss <adam@indexdata.dk> 108 Date: Wed Nov 11 21:52:15 2015 +0100 109 110 sha1: Work around older VS compilers 111 112 commit 92e9ead954f1292391afde93235f0fd25891da8e 113 Author: Adam Dickmeiss <adam@indexdata.dk> 114 Date: Wed Nov 11 21:51:05 2015 +0100 115 116 Current YAZ are made with VS 2015 117 118 commit a6b61b9f8b6576e8159a4e7e6aee88bba7e5d07d 119 Author: Adam Dickmeiss <adam@indexdata.dk> 120 Date: Wed Nov 11 15:32:28 2015 +0100 121 122 Avoid using non-portable debian.h 123 124 Instead use autoconf's AC_C_BIGENDIAN 125 126 commit 4eb90d87b9374b30b8ea4f9d5e70d509a11d9a58 127 Author: Adam Dickmeiss <adam@indexdata.dk> 128 Date: Wed Nov 11 14:50:27 2015 +0100 129 130 Fix rpn2cql fails for Bib-1 set in qry+conf YAZ-865 131 132 commit 94a0aa1a3d45b41484ac4bf81b85f90dca7f7181 133 Author: Adam Dickmeiss <adam@indexdata.dk> 134 Date: Wed Nov 11 14:13:31 2015 +0100 135 136 Bundle sha1 rather than use libgcrypt/nettle 137 138 commit 1b29294f1ba913fb798c3556e3fda09bfc46bb67 139 Author: Adam Dickmeiss <adam@indexdata.dk> 140 Date: Wed Nov 11 09:04:25 2015 +0000 141 142 Version 5.15.0 143 144 commit 71e94b6a27e3dd1dcd8a781254a4c329de020f34 145 Author: Adam Dickmeiss <adam@indexdata.dk> 146 Date: Wed Nov 11 09:03:41 2015 +0000 147 148 Add Ubuntu Wily Werewolf 149 150 commit 240156e69d3a6390699644756e367fffd42891d1 151 Author: Adam Dickmeiss <adam@indexdata.dk> 152 Date: Tue Nov 10 13:47:18 2015 +0100 153 154 CCL: fix other inherited attributes 155 156 commit 31596bdcae098f8acea695d44c44ee5f646b4c1f 157 Author: Adam Dickmeiss <adam@indexdata.dk> 158 Date: Tue Nov 10 13:26:00 2015 +0100 159 160 CCL: fix r=o, r=r WRT inherited attributes YAZ-864 161 162 commit 13da404f1294cb29e30100e71b76c4b44e06cf89 163 Author: Adam Dickmeiss <adam@indexdata.dk> 164 Date: Mon Nov 9 12:48:24 2015 +0000 165 166 Version 5.14.12 167 168 commit 8b9999744362603b448a74f779ff7a2b4d76c89d 169 Author: Adam Dickmeiss <adam@indexdata.dk> 170 Date: Mon Nov 9 13:47:46 2015 +0100 171 172 Set VS_REDIST_EXE for all architectures 173 174 commit dae688b0b3ebe96d6b65385b2fa0e627ab6ce451 175 Author: Adam Dickmeiss <adam@indexdata.dk> 176 Date: Mon Nov 9 13:29:01 2015 +0100 177 178 No more reachable memory with yaz_deinit_globals 179 180 At least when nettle is in use (libgcrypt is hopeless) 181 182 commit 84153486e91926be04dd28d4f2bda6c6ade0e005 183 Author: Adam Dickmeiss <adam@indexdata.dk> 184 Date: Mon Nov 9 12:01:12 2015 +0000 185 186 Revert "Build without redis on Debian squeeze, Ubuntu Lucid" 187 188 This reverts commit ad2e8b3190adb77733a744a26a08927ed026396d. 189 190 We don't build for Debian squeeze and Ubuntu Lucid anymore, so this 191 hack is redundant. 192 193 Conflicts: 194 debian/control 195 debian/rules 196 197 commit 2487937ef218d16b41294bf7d1845d164e17bfe2 198 Author: Adam Dickmeiss <adam@indexdata.dk> 199 Date: Mon Nov 9 11:55:39 2015 +0000 200 201 Build with nettle on Debian/Ubuntu 202 203 commit 60f0955d87a511503ce48de0e99f697e112ff3d0 204 Author: Adam Dickmeiss <adam@indexdata.dk> 205 Date: Mon Nov 9 12:45:04 2015 +0100 206 207 Allow use of Nettle as an alternative to gcrypt 208 209 commit 756129c2a4eaa8a0cc4e0acbc8b401083024c1e2 210 Author: Adam Dickmeiss <adam@indexdata.dk> 211 Date: Mon Nov 9 12:00:14 2015 +0100 212 213 yaz_deinit_globals closes FILE log 214 215 commit eec02e3b60802638aa3a105f3037814cf32af3b6 216 Author: Adam Dickmeiss <adam@indexdata.dk> 217 Date: Thu Nov 5 12:50:26 2015 +0100 218 219 cs_get_host_args: allow unix:path:args notation 220 221 commit 7207680c8f685c9ed33536bfd4a4878cb2616d99 222 Author: Adam Dickmeiss <adam@indexdata.dk> 223 Date: Wed Oct 28 11:08:40 2015 +0100 224 225 Build with VS 2015 (2014 runtime) 226 227 commit 70ce06b6fcbe3a53e94111ecedf0312848647c1b 228 Author: Adam Dickmeiss <adam@indexdata.dk> 229 Date: Wed Oct 28 11:08:01 2015 +0100 230 231 Fix registry keys for VC runtime 232 233 commit a4a4e9d375bfbcc823e8b3820ffb23272e919004 234 Author: Adam Dickmeiss <adam@indexdata.dk> 235 Date: Tue Oct 27 15:40:03 2015 +0100 236 237 Prepare to bundle VC 2015 Runtime 14.0.23026 238 239 commit 917d2c4a288a19c0da7fa98ad514288d0e045413 240 Author: Adam Dickmeiss <adam@indexdata.dk> 241 Date: Tue Oct 27 15:39:38 2015 +0100 242 243 make64 does not build yaz4j 244 245 commit d438b90ac17fbae25ba2554dd76f4e156f420437 246 Author: Adam Dickmeiss <adam@indexdata.dk> 247 Date: Thu Oct 22 16:31:26 2015 +0200 248 249 Cleanup de-init function YAZ-863 250 251 New function yaz_deinit_globals 252 253 commit 7cf33bcd4c625c2197101ebffd38513e44271be6 254 Author: Adam Dickmeiss <adam@indexdata.dk> 255 Date: Fri Oct 9 15:09:34 2015 +0000 256 257 Version 5.14.11 258 259 commit 59830038599648515b34784fbab8f5befa63e185 260 Author: Adam Dickmeiss <adam@indexdata.dk> 261 Date: Fri Oct 9 15:09:17 2015 +0000 262 263 Remove Ubuntu utopic 264 265 commit e8001c3381e00a846e96fab5a1c6f7ca00df4f55 266 Author: Adam Dickmeiss <adam@indexdata.dk> 267 Date: Fri Oct 9 16:15:42 2015 +0200 268 269 Fix RPN to CQL rejects local Bib-1 attribute set YAZ-861 270 271 commit 39671a069c30f6cc508de7692f49a01f413a5a16 272 Author: Adam Dickmeiss <adam@indexdata.dk> 273 Date: Wed Oct 7 16:06:25 2015 +0200 274 275 cs_errmsg never writes to static buffer 276 277 For the CSYSERR applications should check errno themselves 278 279 commit ab99e2d94176eef3b1b23ef3f0f180c6d5077ea6 280 Author: Adam Dickmeiss <adam@indexdata.dk> 281 Date: Wed Oct 7 16:04:43 2015 +0200 282 283 ZOOM C: tweak when connection failed is returned 284 285 For cases with multiple socket addresses for some hostname, eg 286 localhost IPV4+IPV6, the code now properly returns "connection 287 failed" rather than "connection lost". 288 289 commit 38f746ee0f3da5e620bbf3b60eb2ccc1bc647d19 290 Author: Adam Dickmeiss <adam@indexdata.dk> 291 Date: Wed Oct 7 11:29:21 2015 +0200 292 293 Update doc/common 294 295 commit 323805b6779bcf1befdc7cdd7f10c23b06885e0d 296 Author: David Crossley <dcrossley@indexgeo.com.au> 297 Date: Wed Oct 7 12:57:33 2015 +1100 298 299 Various minor text tweaks. 300 301 commit 0ec12c344e05f3637af9f48e6aa28a54d99f8343 302 Author: David Crossley <dcrossley@indexgeo.com.au> 303 Date: Mon Oct 5 15:22:20 2015 +1100 304 305 Various minor text tweaks. 306 307 commit 2a624ff1daa841601aebca86c0196039da6978b3 308 Author: Adam Dickmeiss <adam@indexdata.dk> 309 Date: Wed Sep 16 14:21:04 2015 +0200 310 311 Fix windows uninstall does not remove start menu shortcuts YAZ-860 312 313 commit 3cdd02c11b85c98430021bbc6413fcceda754354 314 Author: Adam Dickmeiss <adam@indexdata.dk> 315 Date: Wed Sep 16 09:10:07 2015 +0000 316 317 Version 5.14.10 318 319 commit 4db60a9b1f537de4c0f04587b44be32d0701a64f 320 Author: Adam Dickmeiss <adam@indexdata.dk> 321 Date: Tue Sep 15 19:43:54 2015 +0200 322 323 prevent huge expansions in CCL s=sl YAZ-859 324 325 commit ba19dacdfe290bee024a23673a6e75f451e2c013 326 Author: Adam Dickmeiss <adam@indexdata.dk> 327 Date: Tue Sep 15 09:02:49 2015 +0000 328 329 Version 5.14.9 330 331 commit 1426a3da9b0390bb0d928a6ee56ebf5fa0ceb0ef 332 Author: Adam Dickmeiss <adam@indexdata.dk> 333 Date: Tue Sep 15 10:13:27 2015 +0200 334 335 Fix segv in ZOOM_connection_fire_event_socket YAZ-858 336 337 The odr_in memory taken by handle_srw_response, and, thus if result 338 set is destructed before we expect the HTTP response (hres) it may 339 be come invalid. Therefore we inspect hres before the call to 340 ZOOM_handle_sru. 341 342 commit 7c6b3363478950a3a5c7f448e5bfa6f4ea19fbab 343 Author: Adam Dickmeiss <adam@indexdata.dk> 344 Date: Tue Sep 15 10:05:10 2015 +0200 345 346 Fix possible deadlock in backtrace (2nd attempt) YAZ-856 347 348 An alarm is set up so that backtrace is terminated if it hangs. 349 Even if backtrace the handler also attempts to spawn gdb. 350 351 commit 30af0a1ebbea75c3e757eb03d3f988c61fce8511 352 Author: Adam Dickmeiss <adam@indexdata.dk> 353 Date: Mon Sep 14 13:53:34 2015 +0000 354 355 Version 5.14.8 356 357 commit c5b92d32f5619eae0b99c4bfb39374e8ef675e34 358 Author: Adam Dickmeiss <adam@indexdata.dk> 359 Date: Mon Sep 14 15:49:47 2015 +0200 360 361 Remove ununsed function ccl_rpn_dup 362 363 commit 4f3f16d519137001a916178e28ad1dff8b986a7d 364 Author: Adam Dickmeiss <adam@indexdata.dk> 365 Date: Mon Sep 14 15:48:43 2015 +0200 366 367 Fix SEGV for s=sl for 3 terms and syntax error YAZ-857 368 369 commit de94629a46584eafe114f740ed3000b26dd42ffb 370 Author: Adam Dickmeiss <adam@indexdata.dk> 371 Date: Sun Sep 13 19:31:45 2015 +0000 372 373 Version 5.14.7 374 375 commit fcb40f9ed16ce6a8ef86997890057af0f7692377 376 Author: Adam Dickmeiss <adam@indexdata.dk> 377 Date: Sun Sep 13 21:12:40 2015 +0200 378 379 backtrace: add \n in error msg 380 381 commit 7cda3530b0d64128462118433a9f69645f49a39b 382 Author: Adam Dickmeiss <adam@indexdata.dk> 383 Date: Sun Sep 13 21:08:30 2015 +0200 384 385 Fix possible deadlock in backtrace YAZ-856 386 387 commit b0afe9a4eb412d5d605450ea715dcd033f45b878 388 Merge: e94e943 a7261ce 389 Author: Wolfram Schneider <wosch@indexdata.dk> 390 Date: Tue Sep 8 12:21:49 2015 +0000 391 392 Merge branch 'master' of ssh://git.indexdata.com:222/home/git/pub/yaz 393 394 commit e94e943c08f4f9265c2ff211d74984166b289841 395 Author: Wolfram Schneider <wosch@indexdata.dk> 396 Date: Tue Sep 8 11:45:37 2015 +0000 397 398 documentation: libreadline5-dev is retired, recommend to install libreadline-gplv2-dev 399 400 commit 44c26c79fddc6d28b4da0a0fd5788eca526b390e 401 Author: Wolfram Schneider <wosch@indexdata.dk> 402 Date: Tue Sep 8 11:42:23 2015 +0000 403 404 update documentation / help text 405 406 commit a7261ce1171ca8e90561b2055e6198e15208bcd6 407 Author: Adam Dickmeiss <adam@indexdata.dk> 408 Date: Tue Sep 8 09:02:05 2015 +0200 409 410 Fix docpath example 411 412 commit a996c33edb96a3273c81d799189b33437ad6ae18 413 Author: David Crossley <dcrossley@indexgeo.com.au> 414 Date: Tue Sep 8 14:10:10 2015 +1000 415 416 Various minor text tweaks. 417 418 commit 086d0dd7b180c786daf78359e1a7b94c656dd855 419 Author: Adam Dickmeiss <adam@indexdata.dk> 420 Date: Mon Sep 7 17:26:20 2015 +0200 421 422 yaz-ztest: set named_result_sets flag 423 424 commit d802116821b20c1dac70011b1ff36edfc4a3119b 425 Author: David Crossley <dcrossley@indexgeo.com.au> 426 Date: Thu Sep 3 15:53:19 2015 +1000 427 428 Various minor text tweaks. 429 430 commit f332be40c2edee783d37633597b4f7ac3b22fc3e 431 Author: David Crossley <dcrossley@indexgeo.com.au> 432 Date: Wed Sep 2 12:26:12 2015 +1000 433 434 Refer to full name of Apache products at first mention, as per ASF trademark guidelines. 435 436 commit 3b046fa5df64b76cc6a28f562c135c06d7a428a7 437 Author: David Crossley <dcrossley@indexgeo.com.au> 438 Date: Wed Sep 2 12:19:38 2015 +1000 439 440 Various minor text tweaks. 441 442 commit 02ef0ddc8ff17fa5053089af7d5d93ea1f2182ea 443 Author: David Crossley <dcrossley@indexgeo.com.au> 444 Date: Wed Sep 2 12:18:15 2015 +1000 445 446 Various minor text tweaks. 447 448 commit 87faebe8ef5cab8f6df86f387e8b919b7b9897a8 449 Author: Adam Dickmeiss <adam@indexdata.dk> 450 Date: Mon Aug 17 12:41:33 2015 +0000 451 452 Version 5.14.6 453 454 commit 473f3071b86a40479e38e3fe4d434c0d2bf03379 455 Author: Adam Dickmeiss <adam@indexdata.dk> 456 Date: Mon Aug 17 14:38:01 2015 +0200 457 458 Fix yaz-client command args parsing broken YAZ-855 459 460 Bug introduced in 5be87e7a04c7219b31cefc0a3 461 462 commit 686414b0ac6446cd55610d5203d61a32672e2203 463 Author: Adam Dickmeiss <adam@indexdata.dk> 464 Date: Thu Aug 6 10:23:41 2015 +0000 465 466 Version 5.14.5 467 468 commit 7673cf27f5be351a18a5d3ea1baf6c4aee06eb3b 469 Author: Adam Dickmeiss <adam@indexdata.dk> 470 Date: Wed Aug 5 13:43:22 2015 +0000 471 472 Remove Debian squeeze (compat 8) 473 474 commit 8e27c4a44da61c8d639187f2b914ef7d432baed5 475 Author: Adam Dickmeiss <adam@indexdata.dk> 476 Date: Wed Aug 5 15:29:19 2015 +0200 477 478 debian compat 9 YAZ-854 479 480 commit d7909431b9e73132e227463279bc8fe614c49184 481 Author: Adam Dickmeiss <adam@indexdata.dk> 482 Date: Wed Aug 5 13:23:29 2015 +0200 483 484 rpn2cql diagnostics: provide use attribute addinfo YAZ-853 485 486 commit 5ae31048f134f9f9db937db6847edef583123a90 487 Author: Adam Dickmeiss <adam@indexdata.dk> 488 Date: Tue Aug 4 12:19:09 2015 +0000 489 490 deb: deprecated substitution ${Source-Version} YAZ-852 491 492 commit 5be87e7a04c7219b31cefc0a3bd02fe5a255430c 493 Author: Adam Dickmeiss <adam@indexdata.dk> 494 Date: Wed Jul 29 15:36:51 2015 +0200 495 496 Fix yaz-client: semicolon terminates arguments YAZ-851 497 498 commit f575db041e99b9c7455e5251fe677d145c98f6f0 499 Author: Adam Dickmeiss <adam@indexdata.dk> 500 Date: Wed Jul 29 08:54:34 2015 +0000 501 502 Version 5.14.4 503 504 commit eb556013557ef8c9e76c52614f88c059ec443c95 505 Author: Adam Dickmeiss <adam@indexdata.dk> 506 Date: Tue Jul 28 13:04:55 2015 +0200 507 508 Solr >= 5.1 / content type text/xml YAZ-850 509 1 510 commit 74168354bcd4a020093adb4a1c0981e35ed340db 2 511 Author: Adam Dickmeiss <adam@indexdata.dk> -
yaz/trunk/fuentes/IDMETA
r255 r265 1 DEBIAN_DIST="jessie wheezy squeeze"2 UBUNTU_DIST=" vivid utopictrusty precise"1 DEBIAN_DIST="jessie wheezy" 2 UBUNTU_DIST="wily vivid trusty precise" 3 3 CENTOS_DIST="centos5 centos6 centos7" 4 VERSION=5.1 4.34 VERSION=5.15.2 -
yaz/trunk/fuentes/LICENSE
r255 r265 1 Copyright (c) 1995-201 5, Index Data1 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 84 84 $(srcdir)/yaz-config.in $(srcdir)/yaz.pc.in \ 85 85 $(srcdir)/Doxyfile.in $(top_srcdir)/win/version.nsi.in \ 86 ChangeLog NEWS READMEconfig/compile config/config.guess \86 ChangeLog NEWS config/compile config/config.guess \ 87 87 config/config.sub config/depcomp config/install-sh \ 88 88 config/missing config/ylwrap config/ltmain.sh \ … … 261 261 EXEEXT = @EXEEXT@ 262 262 FGREP = @FGREP@ 263 GCRYPT_LIBS = @GCRYPT_LIBS@264 263 GREP = @GREP@ 265 264 HIREDIS_LIBS = @HIREDIS_LIBS@ … … 363 362 libdir = @libdir@ 364 363 libexecdir = @libexecdir@ 365 libgcrypt = @libgcrypt@366 364 localedir = @localedir@ 367 365 localstatedir = @localstatedir@ … … 390 388 pkgconfig_DATA = yaz.pc 391 389 SPEC_FILE = $(PACKAGE).spec 392 EXTRA_DIST = $(SPEC_FILE) IDMETA README LICENSE NEWS m4/id-config.sh \390 EXTRA_DIST = $(SPEC_FILE) IDMETA README.md LICENSE NEWS m4/id-config.sh \ 393 391 yaz-config.in yaz.pc.in m4/yaz.m4 m4/yaz_libxml2.m4 buildconf.sh \ 394 392 Doxyfile.in m4/acx_pthread.m4 m4/ac_check_icu.m4 -
yaz/trunk/fuentes/NEWS
r255 r265 1 --- 5.15.2 2016/01/11 2 3 Re-organize Windows build. Use ICU compiled with VS 2015 to use 4 same runtime as rest of components (YAZ, Libxml2, etc). 5 6 Move YAZ and many other software components to GitHub. 7 8 --- 5.15.1 2015/11/12 9 10 Bundle sha1 rather than use libgcrypt/nettle. This means that 11 configure no longer accepts --with-gcrypt and --with-nettle. 12 13 Fix rpn2cql fails for Bib-1 set in qry+conf YAZ-865 14 15 --- 5.15.0 2015/11/11 16 17 CCL: fix r=o, r=r WRT inherited attributes YAZ-864 18 19 --- 5.14.12 2015/11/09 20 21 Build with nettle on Debian/Ubuntu 22 23 test system calls yaz_deinit_globals for better memory leak detection 24 25 cs_get_host_args: allow unix:path:args notation 26 27 Windows: build YAZ with VC 2015 and bundle it with runtime 28 version 14.0.23026. 29 30 --- 5.14.11 2015/10/09 31 32 Fix RPN to CQL rejects local Bib-1 attribute set YAZ-861 33 34 ZOOM C: tweak when connection failed is returned 35 For cases with multiple socket addresses for some hostname, eg 36 localhost IPV4+IPV6, the code now properly returns "connection 37 failed" rather than "connection lost". 38 39 Various minor documenation tweaks from David Crossley. Thanks. 40 41 Fix windows uninstall does not remove start menu shortcuts YAZ-860 42 43 --- 5.14.10 2015/09/16 44 45 Prevent huge expansions in CCL s=sl YAZ-859 46 47 --- 5.14.9 2015/09/15 48 49 Fix segv in ZOOM_connection_fire_event_socket YAZ-858 50 The odr_in memory taken by handle_srw_response, and, thus if result 51 set is destructed before we expect the HTTP response (hres) it may 52 be come invalid. Therefore we inspect hres before the call to 53 ZOOM_handle_sru. 54 55 Fix possible deadlock in backtrace (2nd attempt) YAZ-856 56 An alarm is set up so that backtrace is terminated if it hangs. 57 Even if backtrace the handler also attempts to spawn gdb. 58 59 --- 5.14.8 2015/09/14 60 61 Fix SEGV for s=sl for 3 terms and syntax error YAZ-857 62 63 --- 5.14.7 2015/09/13 64 65 Fix possible deadlock in backtrace YAZ-856 66 67 Various minor text tweaks in documentation 68 69 --- 5.14.6 2015/08/17 70 71 Fix yaz-client command args parsing broken YAZ-855 72 Bug introduced in 5be87e7a04c7219b31cefc0a3 - version 5.14.5 73 74 --- 5.14.5 2015/08/06 75 76 Stop building packages for obsolete Debian squeeze and use DH 77 version 9. YAZ-854 78 79 rpn2cql diagnostics: provide use attribute addinfo YAZ-853 80 81 deb: deprecated substitution ${Source-Version} YAZ-852 82 83 Fix yaz-client: semicolon terminates arguments YAZ-851 84 85 --- 5.14.4 2015/07/29 86 87 Windows: Bundle VC runtime exe YAZ-848 88 89 Omit Content-Type for HTTP requests to Solr YAZ-850 90 1 91 --- 5.14.3 2015/06/29 2 92 -
yaz/trunk/fuentes/buildconf.sh
r255 r265 35 35 36 36 When building from Git, you need these Debian packages: 37 autoconf automake libtool gcc bison tcl 8.437 autoconf automake libtool gcc bison tclsh 38 38 xsltproc docbook docbook-xml docbook-xsl 39 libxslt1-dev libgnutls-dev libreadline 5-dev libwrap0-dev40 pkg-config libicu-dev 39 libxslt1-dev libgnutls-dev libreadline--dev libwrap0-dev 40 pkg-config libicu-dev make 41 41 42 42 And if you want to make a Debian package: dpkg-dev fakeroot debhelper -
yaz/trunk/fuentes/client/Makefile.in
r255 r265 200 200 EXEEXT = @EXEEXT@ 201 201 FGREP = @FGREP@ 202 GCRYPT_LIBS = @GCRYPT_LIBS@203 202 GREP = @GREP@ 204 203 HIREDIS_LIBS = @HIREDIS_LIBS@ … … 302 301 libdir = @libdir@ 303 302 libexecdir = @libexecdir@ 304 libgcrypt = @libgcrypt@305 303 localedir = @localedir@ 306 304 localstatedir = @localstatedir@ -
yaz/trunk/fuentes/client/client.c
r255 r265 5185 5185 { 5186 5186 int i, res; 5187 char word[32], arg[10240]; 5187 char word[32], *arg; 5188 int no_read = 0; 5188 5189 5189 5190 #if HAVE_GETTIMEOFDAY … … 5191 5192 #endif 5192 5193 5193 if ((res = sscanf(line, "%31s %10239[^;]", word, arg)) <= 0) 5194 sscanf(line, "%31s%n", word, &no_read); 5195 if (no_read == 0) 5194 5196 { 5195 5197 strcpy(word, last_cmd); 5196 *arg = '\0';5197 } 5198 else if (res == 1)5199 *arg = 0;5198 arg = line + strlen(line); 5199 } 5200 else 5201 arg = line + no_read; 5200 5202 strcpy(last_cmd, word); 5201 5203 5202 /* removed tailing spaces from the arg command */ 5203 { 5204 char* p = arg; 5205 char* lastnonspace=NULL; 5206 5207 for (; *p; ++p) 5204 /* whitespace chop */ 5205 { 5206 char *p; 5207 char *lastnonspace = 0; 5208 5209 while (*arg && yaz_isspace(*arg)) 5210 arg++; 5211 for (p = arg; *p; ++p) 5208 5212 { 5209 5213 if (!yaz_isspace(*p)) … … 5289 5293 else 5290 5294 { 5291 char arg[10240],word[32];5292 int i ,res;5293 if ( (res = sscanf(rl_line_buffer, "%31s %10239[^;]", word, arg)) <= 0)5295 char word[32]; 5296 int i; 5297 if (sscanf(rl_line_buffer, "%31s", word) <= 0) 5294 5298 { 5295 5299 rl_attempted_completion_over = 1; -
yaz/trunk/fuentes/configure
r255 r265 1 1 #! /bin/sh 2 2 # Guess values for system-dependent variables and create Makefiles. 3 # Generated by GNU Autoconf 2.69 for yaz 5.1 4.3.3 # Generated by GNU Autoconf 2.69 for yaz 5.15.2. 4 4 # 5 5 # Report bugs to <yaz-help@indexdata.dk>. … … 591 591 PACKAGE_NAME='yaz' 592 592 PACKAGE_TARNAME='yaz' 593 PACKAGE_VERSION='5.1 4.3'594 PACKAGE_STRING='yaz 5.1 4.3'593 PACKAGE_VERSION='5.15.2' 594 PACKAGE_STRING='yaz 5.15.2' 595 595 PACKAGE_BUGREPORT='yaz-help@indexdata.dk' 596 596 PACKAGE_URL='' … … 656 656 MEMCACHED_LIBS 657 657 HIREDIS_LIBS 658 libgcrypt659 GCRYPT_LIBS660 658 XSL_DIR 661 659 DSSSL_DIR … … 798 796 with_docbook_dsssl 799 797 with_docbook_xsl 800 with_libgcrypt801 798 with_redis 802 799 with_memcached … … 1359 1356 # This message is too long to be a string in the A/UX 3.1 sh. 1360 1357 cat <<_ACEOF 1361 \`configure' configures yaz 5.1 4.3to adapt to many kinds of systems.1358 \`configure' configures yaz 5.15.2 to adapt to many kinds of systems. 1362 1359 1363 1360 Usage: $0 [OPTION]... [VAR=VALUE]... … … 1429 1426 if test -n "$ac_init_help"; then 1430 1427 case $ac_init_help in 1431 short | recursive ) echo "Configuration of yaz 5.1 4.3:";;1428 short | recursive ) echo "Configuration of yaz 5.15.2:";; 1432 1429 esac 1433 1430 cat <<\_ACEOF … … 1462 1459 --with-docbook-dsssl=DIR use Docbook DSSSL in DIR/{html,print}/docbook.dsl 1463 1460 --with-docbook-xsl=DIR use Docbook XSL in DIR/{htmlhelp,xhtml} 1464 --with-libgcrypt=DIR use libgcrypt-config in DIR1465 1461 --with-redis hiredis library 1466 1462 --with-memcached Memcached library … … 1548 1544 if $ac_init_version; then 1549 1545 cat <<\_ACEOF 1550 yaz configure 5.1 4.31546 yaz configure 5.15.2 1551 1547 generated by GNU Autoconf 2.69 1552 1548 … … 1971 1967 running configure, to aid debugging if configure makes a mistake. 1972 1968 1973 It was created by yaz $as_me 5.1 4.3, which was1969 It was created by yaz $as_me 5.15.2, which was 1974 1970 generated by GNU Autoconf 2.69. Invocation command line was 1975 1971 … … 2837 2833 # Define the identity of the package. 2838 2834 PACKAGE='yaz' 2839 VERSION='5.1 4.3'2835 VERSION='5.15.2' 2840 2836 2841 2837 … … 11814 11810 11815 11811 11812 { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether byte ordering is bigendian" >&5 11813 $as_echo_n "checking whether byte ordering is bigendian... " >&6; } 11814 if ${ac_cv_c_bigendian+:} false; then : 11815 $as_echo_n "(cached) " >&6 11816 else 11817 ac_cv_c_bigendian=unknown 11818 # See if we're dealing with a universal compiler. 11819 cat confdefs.h - <<_ACEOF >conftest.$ac_ext 11820 /* end confdefs.h. */ 11821 #ifndef __APPLE_CC__ 11822 not a universal capable compiler 11823 #endif 11824 typedef int dummy; 11825 11826 _ACEOF 11827 if ac_fn_c_try_compile "$LINENO"; then : 11828 11829 # Check for potential -arch flags. It is not universal unless 11830 # there are at least two -arch flags with different values. 11831 ac_arch= 11832 ac_prev= 11833 for ac_word in $CC $CFLAGS $CPPFLAGS $LDFLAGS; do 11834 if test -n "$ac_prev"; then 11835 case $ac_word in 11836 i?86 | x86_64 | ppc | ppc64) 11837 if test -z "$ac_arch" || test "$ac_arch" = "$ac_word"; then 11838 ac_arch=$ac_word 11839 else 11840 ac_cv_c_bigendian=universal 11841 break 11842 fi 11843 ;; 11844 esac 11845 ac_prev= 11846 elif test "x$ac_word" = "x-arch"; then 11847 ac_prev=arch 11848 fi 11849 done 11850 fi 11851 rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext 11852 if test $ac_cv_c_bigendian = unknown; then 11853 # See if sys/param.h defines the BYTE_ORDER macro. 11854 cat confdefs.h - <<_ACEOF >conftest.$ac_ext 11855 /* end confdefs.h. */ 11856 #include <sys/types.h> 11857 #include <sys/param.h> 11858 11859 int 11860 main () 11861 { 11862 #if ! (defined BYTE_ORDER && defined BIG_ENDIAN \ 11863 && defined LITTLE_ENDIAN && BYTE_ORDER && BIG_ENDIAN \ 11864 && LITTLE_ENDIAN) 11865 bogus endian macros 11866 #endif 11867 11868 ; 11869 return 0; 11870 } 11871 _ACEOF 11872 if ac_fn_c_try_compile "$LINENO"; then : 11873 # It does; now see whether it defined to BIG_ENDIAN or not. 11874 cat confdefs.h - <<_ACEOF >conftest.$ac_ext 11875 /* end confdefs.h. */ 11876 #include <sys/types.h> 11877 #include <sys/param.h> 11878 11879 int 11880 main () 11881 { 11882 #if BYTE_ORDER != BIG_ENDIAN 11883 not big endian 11884 #endif 11885 11886 ; 11887 return 0; 11888 } 11889 _ACEOF 11890 if ac_fn_c_try_compile "$LINENO"; then : 11891 ac_cv_c_bigendian=yes 11892 else 11893 ac_cv_c_bigendian=no 11894 fi 11895 rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext 11896 fi 11897 rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext 11898 fi 11899 if test $ac_cv_c_bigendian = unknown; then 11900 # See if <limits.h> defines _LITTLE_ENDIAN or _BIG_ENDIAN (e.g., Solaris). 11901 cat confdefs.h - <<_ACEOF >conftest.$ac_ext 11902 /* end confdefs.h. */ 11903 #include <limits.h> 11904 11905 int 11906 main () 11907 { 11908 #if ! (defined _LITTLE_ENDIAN || defined _BIG_ENDIAN) 11909 bogus endian macros 11910 #endif 11911 11912 ; 11913 return 0; 11914 } 11915 _ACEOF 11916 if ac_fn_c_try_compile "$LINENO"; then : 11917 # It does; now see whether it defined to _BIG_ENDIAN or not. 11918 cat confdefs.h - <<_ACEOF >conftest.$ac_ext 11919 /* end confdefs.h. */ 11920 #include <limits.h> 11921 11922 int 11923 main () 11924 { 11925 #ifndef _BIG_ENDIAN 11926 not big endian 11927 #endif 11928 11929 ; 11930 return 0; 11931 } 11932 _ACEOF 11933 if ac_fn_c_try_compile "$LINENO"; then : 11934 ac_cv_c_bigendian=yes 11935 else 11936 ac_cv_c_bigendian=no 11937 fi 11938 rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext 11939 fi 11940 rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext 11941 fi 11942 if test $ac_cv_c_bigendian = unknown; then 11943 # Compile a test program. 11944 if test "$cross_compiling" = yes; then : 11945 # Try to guess by grepping values from an object file. 11946 cat confdefs.h - <<_ACEOF >conftest.$ac_ext 11947 /* end confdefs.h. */ 11948 short int ascii_mm[] = 11949 { 0x4249, 0x4765, 0x6E44, 0x6961, 0x6E53, 0x7953, 0 }; 11950 short int ascii_ii[] = 11951 { 0x694C, 0x5454, 0x656C, 0x6E45, 0x6944, 0x6E61, 0 }; 11952 int use_ascii (int i) { 11953 return ascii_mm[i] + ascii_ii[i]; 11954 } 11955 short int ebcdic_ii[] = 11956 { 0x89D3, 0xE3E3, 0x8593, 0x95C5, 0x89C4, 0x9581, 0 }; 11957 short int ebcdic_mm[] = 11958 { 0xC2C9, 0xC785, 0x95C4, 0x8981, 0x95E2, 0xA8E2, 0 }; 11959 int use_ebcdic (int i) { 11960 return ebcdic_mm[i] + ebcdic_ii[i]; 11961 } 11962 extern int foo; 11963 11964 int 11965 main () 11966 { 11967 return use_ascii (foo) == use_ebcdic (foo); 11968 ; 11969 return 0; 11970 } 11971 _ACEOF 11972 if ac_fn_c_try_compile "$LINENO"; then : 11973 if grep BIGenDianSyS conftest.$ac_objext >/dev/null; then 11974 ac_cv_c_bigendian=yes 11975 fi 11976 if grep LiTTleEnDian conftest.$ac_objext >/dev/null ; then 11977 if test "$ac_cv_c_bigendian" = unknown; then 11978 ac_cv_c_bigendian=no 11979 else 11980 # finding both strings is unlikely to happen, but who knows? 11981 ac_cv_c_bigendian=unknown 11982 fi 11983 fi 11984 fi 11985 rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext 11986 else 11987 cat confdefs.h - <<_ACEOF >conftest.$ac_ext 11988 /* end confdefs.h. */ 11989 $ac_includes_default 11990 int 11991 main () 11992 { 11993 11994 /* Are we little or big endian? From Harbison&Steele. */ 11995 union 11996 { 11997 long int l; 11998 char c[sizeof (long int)]; 11999 } u; 12000 u.l = 1; 12001 return u.c[sizeof (long int) - 1] == 1; 12002 12003 ; 12004 return 0; 12005 } 12006 _ACEOF 12007 if ac_fn_c_try_run "$LINENO"; then : 12008 ac_cv_c_bigendian=no 12009 else 12010 ac_cv_c_bigendian=yes 12011 fi 12012 rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \ 12013 conftest.$ac_objext conftest.beam conftest.$ac_ext 12014 fi 12015 12016 fi 12017 fi 12018 { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_c_bigendian" >&5 12019 $as_echo "$ac_cv_c_bigendian" >&6; } 12020 case $ac_cv_c_bigendian in #( 12021 yes) 12022 $as_echo "#define WORDS_BIGENDIAN 1" >>confdefs.h 12023 ;; #( 12024 no) 12025 ;; #( 12026 universal) 12027 12028 $as_echo "#define AC_APPLE_UNIVERSAL_BUILD 1" >>confdefs.h 12029 12030 ;; #( 12031 *) 12032 as_fn_error $? "unknown endianness 12033 presetting ac_cv_c_bigendian=no (or yes) will help" "$LINENO" 5 ;; 12034 esac 12035 11816 12036 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 11817 12037 do : … … 12075 12295 fi 12076 12296 12077 12078 libgcryptpath=NONE12079 12080 # Check whether --with-libgcrypt was given.12081 if test "${with_libgcrypt+set}" = set; then :12082 withval=$with_libgcrypt; libgcryptpath=$withval12083 fi12084 12085 if test "$libgcryptpath" != "no"; then12086 if test "$libgcryptpath" = "NONE"; then12087 # Extract the first word of "libgcrypt-config", so it can be a program name with args.12088 set dummy libgcrypt-config; ac_word=$212089 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&512090 $as_echo_n "checking for $ac_word... " >&6; }12091 if ${ac_cv_path_libgcrypt+:} false; then :12092 $as_echo_n "(cached) " >&612093 else12094 case $libgcrypt in12095 [\\/]* | ?:[\\/]*)12096 ac_cv_path_libgcrypt="$libgcrypt" # Let the user override the test with a path.12097 ;;12098 *)12099 as_save_IFS=$IFS; IFS=$PATH_SEPARATOR12100 for as_dir in $PATH12101 do12102 IFS=$as_save_IFS12103 test -z "$as_dir" && as_dir=.12104 for ac_exec_ext in '' $ac_executable_extensions; do12105 if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then12106 ac_cv_path_libgcrypt="$as_dir/$ac_word$ac_exec_ext"12107 $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&512108 break 212109 fi12110 done12111 done12112 IFS=$as_save_IFS12113 12114 test -z "$ac_cv_path_libgcrypt" && ac_cv_path_libgcrypt="NONE"12115 ;;12116 esac12117 fi12118 libgcrypt=$ac_cv_path_libgcrypt12119 if test -n "$libgcrypt"; then12120 { $as_echo "$as_me:${as_lineno-$LINENO}: result: $libgcrypt" >&512121 $as_echo "$libgcrypt" >&6; }12122 else12123 { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&512124 $as_echo "no" >&6; }12125 fi12126 12127 12128 elif test -x $libgcryptpath/libgcrypt-config; then12129 libgcrypt=$libgcryptpath/libgcrypt-config12130 else12131 libgcrypt=$libgcryptpath12132 fi12133 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for libgcrypt" >&512134 $as_echo_n "checking for libgcrypt... " >&6; }12135 if "$libgcrypt" --version >/dev/null 2>&1; then12136 libgcryptversion=`$libgcrypt --version`12137 libgcryptversion2=`echo "$libgcryptversion" | awk 'BEGIN { FS = "."; } { printf "%d", $1 * 1000 + $2;}'`12138 { $as_echo "$as_me:${as_lineno-$LINENO}: result: $libgcryptversion" >&512139 $as_echo "$libgcryptversion" >&6; }12140 if test $libgcryptversion2 -ge 1002; then12141 GCRYPT_LIBS="`$libgcrypt --libs`"12142 CFLAGS="$CFLAGS `$libgcrypt --cflags`"12143 12144 $as_echo "#define HAVE_GCRYPT_H 1" >>confdefs.h12145 12146 else12147 if test "$libgcryptpath" = "NONE"; then12148 { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: Only libgcrypt version 1.2 and later supported" >&512149 $as_echo "$as_me: WARNING: Only libgcrypt version 1.2 and later supported" >&2;}12150 else12151 as_fn_error $? "Only libgcrypt version 1.2 and later supported" "$LINENO" 512152 fi12153 libgcryptversion=""12154 fi12155 else12156 { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&512157 $as_echo "no" >&6; }12158 fi12159 fi12160 12297 hiredis=default 12161 12298 … … 12166 12303 fi 12167 12304 12168 if test "$hiredis" != "no" -a "$pkgconfigpath" != "NONE" -a "$libgcryptversion"; then12305 if test "$hiredis" != "no" -a "$pkgconfigpath" != "NONE"; then 12169 12306 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for redisCommandArgv in -lhiredis" >&5 12170 12307 $as_echo_n "checking for redisCommandArgv in -lhiredis... " >&6; } … … 12248 12385 fi 12249 12386 12250 if test "$memcached" != "no" -a -n "$libgcryptversion" -a"$pkgconfigpath" != "NONE"; then12387 if test "$memcached" != "no" -a "$pkgconfigpath" != "NONE"; then 12251 12388 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for libmemcached" >&5 12252 12389 $as_echo_n "checking for libmemcached... " >&6; } … … 13776 13913 fi 13777 13914 13915 13778 13916 : "${CONFIG_STATUS=./config.status}" 13779 13917 ac_write_fail=0 … … 14172 14310 # values after options handling. 14173 14311 ac_log=" 14174 This file was extended by yaz $as_me 5.1 4.3, which was14312 This file was extended by yaz $as_me 5.15.2, which was 14175 14313 generated by GNU Autoconf 2.69. Invocation command line was 14176 14314 … … 14238 14376 ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`" 14239 14377 ac_cs_version="\\ 14240 yaz config.status 5.1 4.314378 yaz config.status 5.15.2 14241 14379 configured by $0, generated by GNU Autoconf 2.69, 14242 14380 with options \\"\$ac_cs_config\\" -
yaz/trunk/fuentes/configure.ac
r255 r265 28 28 dnl 29 29 dnl 30 AC_C_BIGENDIAN 30 31 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],[],[],[]) 31 32 AC_CHECK_HEADERS([net/if.h netinet/in.h netinet/if_ether.h],[],[],[ … … 62 63 fi 63 64 AC_CHECK_FUNC([gethostbyname], ,[AC_CHECK_LIB(nsl, main, [LIBS="$LIBS -lnsl"])]) 64 dnl ------ libgcrypt 65 AC_SUBST([GCRYPT_LIBS]) 66 libgcryptpath=NONE 67 AC_ARG_WITH(libgcrypt, [ --with-libgcrypt=DIR use libgcrypt-config in DIR],[libgcryptpath=$withval]) 68 if test "$libgcryptpath" != "no"; then 69 if test "$libgcryptpath" = "NONE"; then 70 AC_PATH_PROG([libgcrypt],[libgcrypt-config],[NONE]) 71 elif test -x $libgcryptpath/libgcrypt-config; then 72 libgcrypt=$libgcryptpath/libgcrypt-config 73 else 74 libgcrypt=$libgcryptpath 75 fi 76 AC_MSG_CHECKING([for libgcrypt]) 77 if "$libgcrypt" --version >/dev/null 2>&1; then 78 libgcryptversion=`$libgcrypt --version` 79 libgcryptversion2=`echo "$libgcryptversion" | awk 'BEGIN { FS = "."; } { printf "%d", [$]1 * 1000 + [$]2;}'` 80 AC_MSG_RESULT([$libgcryptversion]) 81 if test $libgcryptversion2 -ge 1002; then 82 GCRYPT_LIBS="`$libgcrypt --libs`" 83 CFLAGS="$CFLAGS `$libgcrypt --cflags`" 84 AC_DEFINE([HAVE_GCRYPT_H],[1],[Define to 1 if libgcrypt is present]) 85 else 86 if test "$libgcryptpath" = "NONE"; then 87 AC_MSG_WARN([Only libgcrypt version 1.2 and later supported]) 88 else 89 AC_MSG_ERROR([Only libgcrypt version 1.2 and later supported]) 90 fi 91 libgcryptversion="" 92 fi 93 else 94 AC_MSG_RESULT([no]) 95 fi 96 fi 65 dnl 97 66 dnl ------ redis 98 67 hiredis=default 99 68 AC_SUBST([HIREDIS_LIBS]) 100 69 AC_ARG_WITH([redis], [ --with-redis hiredis library], [hiredis=$withval]) 101 if test "$hiredis" != "no" -a "$pkgconfigpath" != "NONE" -a "$libgcryptversion"; then70 if test "$hiredis" != "no" -a "$pkgconfigpath" != "NONE"; then 102 71 AC_CHECK_LIB([hiredis],[redisCommandArgv],[HIREDIS_LIBS=-lhiredis]) 103 72 AC_MSG_CHECKING([for redis]) … … 130 99 AC_SUBST([MEMCACHED_LIBS]) 131 100 AC_ARG_WITH([memcached], [ --with-memcached Memcached library], [memcached=$withval]) 132 if test "$memcached" != "no" -a -n "$libgcryptversion" -a"$pkgconfigpath" != "NONE"; then101 if test "$memcached" != "no" -a "$pkgconfigpath" != "NONE"; then 133 102 AC_MSG_CHECKING([for libmemcached]) 134 103 if $pkgconfigpath --cflags libmemcached >/dev/null 2>&1 ; then … … 151 120 fi 152 121 fi 122 dnl 123 dnl 124 dnl 153 125 dnl ------ GNU TLS 154 126 AC_SUBST([SSL_CFLAGS]) -
yaz/trunk/fuentes/debian/.gitignore
r255 r265 13 13 *.postinst.debhelper 14 14 *.postrm.debhelper 15 copyright 16 files 17 libyaz5 18 libyaz5-dbg 19 libyaz5-dev 20 yaz-icu 21 yaz-illclient 22 tmp 23 yaz 24 yaz-doc 25 *.debhelper.log 26 *.substvars 27 *.postinst.debhelper 28 *.postrm.debhelper -
yaz/trunk/fuentes/debian/changelog
r256 r265 1 yaz (5.15.2-1.indexdata) unstable; urgency=medium 2 3 * Upstream. 4 5 -- Adam Dickmeiss <adam@indexdata.dk> Mon, 11 Jan 2016 13:13:26 +0000 6 1 7 yaz (5.14.3-1.indexdata+lliurex3) xenial; urgency=medium 2 8 -
yaz/trunk/fuentes/debian/compat
r255 r265 1 9 1 2 7 -
yaz/trunk/fuentes/debian/control
r255 r265 1 Source: yaz 2 Section: devel 3 Standards-Version: 3.6.2 4 Maintainer: Adam Dickmeiss <adam@indexdata.dk> 5 Priority: extra 6 Build-Depends: debhelper (>= 7), 7 pkg-config, 8 libxslt1-dev, 9 libgnutls28-dev|libgnutls-dev, 10 libreadline-dev|libreadline5-dev, 11 libwrap0-dev, 12 libmemcached-dev, 13 libhiredis-dev, 14 libicu-dev 15 16 Package: libyaz5 17 Section: libs 18 Architecture: any 19 Depends: ${shlibs:Depends} 20 Conflicts: idzebra (<= 1.3.4-2), php4-yaz (<= 4.1.2-5) 21 Description: libraries for the Z39.50 toolkit 22 YAZ is a toolkit that allows you to develop software using the 23 ANSI Z39.50/ISO23950 standard for information retrieval. 24 . 25 This package includes runtime files. 26 27 Package: libyaz5-dbg 28 Section: debug 29 Architecture: any 30 Depends: libyaz5 (= ${binary:Version}), ${misc:Depends} 31 Description: debugging symbols for libyaz5 32 YAZ is a toolkit that allows you to develop software using the 33 ANSI Z39.50/ISO23950 standard for information retrieval. 34 . 35 This package contains the debugging symbols for libyaz5. 36 37 Package: yaz 38 Section: utils 39 Architecture: any 40 Depends: ${shlibs:Depends} 41 Conflicts: yaz-runtime, yaz-ssl 42 Description: utilities for the Z39.50 toolkit 43 YAZ is a toolkit that allows you to develop software using the 44 ANSI Z39.50/ISO23950 standard for information retrieval. 45 . 46 This package includes utility programs. 47 48 Package: yaz-doc 49 Section: doc 50 Architecture: all 51 Description: documentation for the Z39.50 toolkit 52 YAZ is a toolkit that allows you to develop software using the 53 Z39.50/ISO23950 standard for information retrieval. 54 . 55 This package includes HTML documentation for YAZ. 56 57 Package: libyaz5-dev 58 Depends: libyaz5 (= ${source:Version}), 59 libxslt1-dev, 60 libicu-dev, 61 tclsh 62 Provides: libyaz-dev 63 Replaces: libyaz-dev 64 Conflicts: libyaz2-dev, libyaz3-dev, libyaz-dev 65 Section: libdevel 66 Architecture: any 67 Suggests: yaz-doc 68 Description: development files for the Z39.50 toolkit 69 YAZ is a toolkit that allows you to develop software using the 70 ANSI Z39.50/ISO23950 standard for information retrieval. 71 . 72 This package includes development libraries and C/C++ header files. 73 74 Package: yaz-illclient 75 Section: utils 76 Depends: ${shlibs:Depends} 77 Architecture: any 78 Description: ILL utility for the Z39.50 toolkit 79 YAZ is a toolkit that allows you to develop software using the 80 ANSI Z39.50/ISO23950 standard for information retrieval. 81 . 82 This package includes the yaz-illclient program which sends ILL 83 (Inter-Library-Loan) requests to a server and decodes the response. 84 85 Package: yaz-icu 86 Section: utils 87 Depends: ${shlibs:Depends} 88 Architecture: any 89 Description: ICU utility for the Z39.50 toolkit 90 YAZ is a toolkit that allows you to develop software using the 91 ANSI Z39.50/ISO23950 standard for information retrieval. 92 . 93 This package includes the yaz-icu program which exposes the ICU chain 94 facility of Z39.50 toolkit. 95 1 96 Source: yaz 2 97 Section: devel -
yaz/trunk/fuentes/debian/libyaz5-dev.install
r255 r265 1 debian/tmp/usr/include/yaz 2 debian/tmp/usr/lib/*/pkgconfig/yaz.pc 3 debian/tmp/usr/lib/*/libyaz*.a 4 debian/tmp/usr/lib/*/libyaz*.so 5 debian/tmp/usr/bin/yaz-config 6 debian/tmp/usr/bin/yaz-asncomp 7 debian/tmp/usr/share/aclocal/yaz.m4 8 debian/tmp/usr/share/yaz 1 9 debian/tmp/usr/include/yaz 2 10 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 1 #!/usr/bin/make -f 2 export DH_VERBOSE=1 3 4 %: 5 dh $@ --without python-support 6 7 override_dh_auto_configure: 8 dh_auto_configure -- \ 9 --enable-tcpd --with-xslt --with-gnutls --with-icu \ 10 --with-memcached --with-redis 11 12 override_dh_strip: 13 dh_strip --dbg-package=libyaz5-dbg 14 15 override_dh_auto_install: 16 dh_auto_install 17 mv debian/tmp/usr/share/doc/yaz debian/tmp/usr/share/doc/yaz-doc 18 19 override_dh_makeshlibs: 20 dh_makeshlibs -V 'libyaz5 (>= 5.13.0)' 21 22 override_dh_installchangelogs: 23 dh_installchangelogs NEWS 24 25 override_dh_installdocs: 26 cp LICENSE debian/copyright 27 dh_installdocs -A README.md 1 28 #!/usr/bin/make -f 2 29 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 6 6 debian/tmp/usr/bin/yaz-json-parse 7 7 debian/tmp/usr/bin/yaz-url 8 debian/tmp/usr/bin/yaz-client 9 debian/tmp/usr/bin/yaz-ztest 10 debian/tmp/usr/bin/zoomsh 11 debian/tmp/usr/bin/yaz-marcdump 12 debian/tmp/usr/bin/yaz-iconv 13 debian/tmp/usr/bin/yaz-json-parse 14 debian/tmp/usr/bin/yaz-url -
yaz/trunk/fuentes/debian/yaz.manpages
r255 r265 8 8 debian/tmp/usr/share/man/man1/yaz-json-parse.1 9 9 debian/tmp/usr/share/man/man1/yaz-url.1 10 debian/tmp/usr/share/man/man1/yaz-client.1 11 debian/tmp/usr/share/man/man8/yaz-ztest.8 12 debian/tmp/usr/share/man/man1/zoomsh.1 13 debian/tmp/usr/share/man/man1/yaz-marcdump.1 14 debian/tmp/usr/share/man/man1/yaz-iconv.1 15 debian/tmp/usr/share/man/man7/yaz-log.7 16 debian/tmp/usr/share/man/man7/bib1-attr.7 17 debian/tmp/usr/share/man/man1/yaz-json-parse.1 18 debian/tmp/usr/share/man/man1/yaz-url.1 -
yaz/trunk/fuentes/doc/Makefile.in
r255 r265 238 238 EXEEXT = @EXEEXT@ 239 239 FGREP = @FGREP@ 240 GCRYPT_LIBS = @GCRYPT_LIBS@241 240 GREP = @GREP@ 242 241 HIREDIS_LIBS = @HIREDIS_LIBS@ … … 340 339 libdir = @libdir@ 341 340 libexecdir = @libexecdir@ 342 libgcrypt = @libgcrypt@343 341 localedir = @localedir@ 344 342 localstatedir = @localstatedir@ -
yaz/trunk/fuentes/doc/asn.external.html
r255 r265 59 59 <code class="literal">octet_aligned</code> arm of the union. 60 60 </p><p> 61 Some servers return ASN.1 structured data values (e g. database61 Some servers return ASN.1 structured data values (e.g. database 62 62 records) as BER-encoded records placed in the 63 63 <code class="literal">octet-aligned</code> branch of the EXTERNAL CHOICE. … … 68 68 Z_ext_typeent *z_ext_gettypebyref(const oid *oid); 69 69 </pre><p> 70 Can be used to retrieve information about the known, external data71 types. The function return a pointer to a static area, or NULL, if no70 can be used to retrieve information about the known, external data 71 types. The function returns a pointer to a static area, or NULL, if no 72 72 match for the given direct reference is found. The 73 73 <code class="literal">Z_ext_typeent</code> … … 99 99 </p><p> 100 100 If you want to <span class="emphasis"><em>send</em></span> EXTERNALs containing 101 ASN.1-structured values in the oc ctet-aligned branch of the CHOICE, this101 ASN.1-structured values in the octet-aligned branch of the CHOICE, this 102 102 is possible too. However, on the encoding phase, it requires a somewhat 103 103 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 implement sencoders and decoders for the13 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 31 31 <code class="function">odr_malloc()</code>, you can release all of the 32 32 allocated data in a single operation, independent of any pointers and 33 relations between the data. <code class="function">odr_malloc()</code> is based on a34 "nibble-memory"33 relations between the data. The <code class="function">odr_malloc()</code> function 34 is based on a "nibble-memory" 35 35 scheme, in which large portions of memory are allocated, and then 36 36 gradually handed out with each call to <code class="function">odr_malloc()</code>. … … 69 69 Z_<type> *zget_<type>(ODR o); 70 70 </pre><p> 71 e g.:71 e.g.: 72 72 </p><pre class="synopsis"> 73 73 Z_InitRequest *zget_InitRequest(ODR o); -
yaz/trunk/fuentes/doc/bib1-attr-man.xml
r255 r265 13 13 <productname>YAZ</productname> 14 14 <productnumber>&version;</productnumber> 15 < info><orgname>Index Data</orgname></info>15 <orgname>Index Data</orgname> 16 16 </refentryinfo> 17 17 … … 35 35 <refsect1><title>TYPES</title> 36 36 <para> 37 The Bib-1 attribute defines six attribute types: Use (1), Relation (2),38 Position (3), Structure (4), Truncation (5) and completeness (6).37 The Bib-1 attribute set defines six attribute types: Use (1), Relation (2), 38 Position (3), Structure (4), Truncation (5) and Completeness (6). 39 39 </para> 40 40 </refsect1> … … 219 219 </refsect1> 220 220 221 <refsect1><title>COMPLETEN SS (6)</title>221 <refsect1><title>COMPLETENESS (6)</title> 222 222 <para> 223 223 <screen> -
yaz/trunk/fuentes/doc/bib1-attr.7
r255 r265 3 3 .\" Author: Index Data 4 4 .\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/> 5 .\" Date: 0 6/29/20155 .\" Date: 01/11/2016 6 6 .\" Manual: Conventions and miscellaneous 7 .\" Source: YAZ 5.1 4.37 .\" Source: YAZ 5.15.2 8 8 .\" Language: English 9 9 .\" 10 .TH "BIB\-1 ATTRIBUTE SET" "7" "0 6/29/2015" "YAZ 5.14.3" "Conventions and miscellaneous"10 .TH "BIB\-1 ATTRIBUTE SET" "7" "01/11/2016" "YAZ 5.15.2" "Conventions and miscellaneous" 11 11 .\" ----------------------------------------------------------------- 12 12 .\" * Define some portability stuff … … 35 35 .SH "TYPES" 36 36 .PP 37 The Bib\-1 attribute defines six attribute types: Use (1), Relation (2), Position (3), Structure (4), Truncation (5) and completeness (6)\&.37 The Bib\-1 attribute set defines six attribute types: Use (1), Relation (2), Position (3), Structure (4), Truncation (5) and Completeness (6)\&. 38 38 .SH "USE (1)" 39 39 .PP … … 246 246 .\} 247 247 .sp 248 .SH "COMPLETEN SS (6)"248 .SH "COMPLETENESS (6)" 249 249 .PP 250 250 .if n \{\ … … 281 281 .PP 282 282 \m[blue]\fBAttibute Set Bib\-1 Semantics\fR\m[]\&\s-2\u[2]\d\s+2\&. 283 .SH "AUTHORS" 284 .PP 285 \fBIndex Data\fR 283 286 .SH "NOTES" 284 287 .IP " 1." 4 -
yaz/trunk/fuentes/doc/bib1.html
r255 r265 1 <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 — Bib-1 Attribute Set</p></div><div class="refsect1"><a name="id p48545008"></a><h2>DESCRIPTION</h2><p>1 <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 — Bib-1 Attribute Set</p></div><div class="refsect1"><a name="idm46170480248784"></a><h2>DESCRIPTION</h2><p> 2 2 This reference entry lists the Bib-1 attribute set types and values. 3 </p></div><div class="refsect1"><a name="id p48546160"></a><h2>TYPES</h2><p>4 The Bib-1 attribute defines six attribute types: Use (1), Relation (2),5 Position (3), Structure (4), Truncation (5) and completeness (6).6 </p></div><div class="refsect1"><a name="id p48547376"></a><h2>USE (1)</h2><p>3 </p></div><div class="refsect1"><a name="idm46170480247632"></a><h2>TYPES</h2><p> 4 The Bib-1 attribute set defines six attribute types: Use (1), Relation (2), 5 Position (3), Structure (4), Truncation (5) and Completeness (6). 6 </p></div><div class="refsect1"><a name="idm46170480246416"></a><h2>USE (1)</h2><p> 7 7 </p><pre class="screen"> 8 8 1 Personal-name … … 106 106 1036 Author-Title-Subject 107 107 </pre><p> 108 </p></div><div class="refsect1"><a name="id p48554048"></a><h2>RELATION (2)</h2><p>108 </p></div><div class="refsect1"><a name="idm46170480239744"></a><h2>RELATION (2)</h2><p> 109 109 </p><pre class="screen"> 110 110 1 Less than … … 119 119 103 AlwaysMatches 120 120 </pre><p> 121 </p></div><div class="refsect1"><a name="id p48555968"></a><h2>POSITION (3)</h2><p>121 </p></div><div class="refsect1"><a name="idm46170480237824"></a><h2>POSITION (3)</h2><p> 122 122 </p><pre class="screen"> 123 123 1 First in field … … 125 125 3 Any position in field 126 126 </pre><p> 127 </p></div><div class="refsect1"><a name="id p48557776"></a><h2>STRUCTURE (4)</h2><p>127 </p></div><div class="refsect1"><a name="idm46170480236016"></a><h2>STRUCTURE (4)</h2><p> 128 128 </p><pre class="screen"> 129 129 1 Phrase … … 144 144 109 Numeric-string 145 145 </pre><p> 146 </p></div><div class="refsect1"><a name="id p48559808"></a><h2>TRUNCATION (5)</h2><p>146 </p></div><div class="refsect1"><a name="idm46170480233984"></a><h2>TRUNCATION (5)</h2><p> 147 147 </p><pre class="screen"> 148 148 1 Right truncation … … 162 162 106 Process * ! regular: *=.*, !=. 163 163 </pre><p> 164 </p></div><div class="refsect1"><a name="id p48563056"></a><h2>COMPLETENSS (6)</h2><p>164 </p></div><div class="refsect1"><a name="idm46170480230736"></a><h2>COMPLETENESS (6)</h2><p> 165 165 </p><pre class="screen"> 166 166 1 Incomplete subfield … … 168 168 3 Complete field 169 169 </pre><p> 170 </p></div><div class="refsect1"><a name="id p48564864"></a><h2>SORTING (7)</h2><p>170 </p></div><div class="refsect1"><a name="idm46170480228928"></a><h2>SORTING (7)</h2><p> 171 171 </p><pre class="screen"> 172 172 1 ascending … … 176 176 Type 7 is an Index Data extension to RPN queries that allows 177 177 embedding a sort critieria into a query. 178 </p></div><div class="refsect1"><a name="id p48567184"></a><h2>SEE ALSO</h2><p>178 </p></div><div class="refsect1"><a name="idm46170480226608"></a><h2>SEE ALSO</h2><p> 179 179 <a class="ulink" href="http://www.loc.gov/z3950/agency/defns/bib1.html" target="_top">Bib-1 Attribute Set</a> 180 180 </p><p> -
yaz/trunk/fuentes/doc/book.xml
r255 r265 79 79 <para> 80 80 Supports 81 <ulink url="&url.solr;"> Solr</ulink> Web Service version 1.4.x81 <ulink url="&url.solr;">Apache Solr</ulink> Web Service version 1.4.x 82 82 (client side only) 83 83 </para> … … 139 139 <para> 140 140 Most implementors only need to read a fraction of the 141 material in thi emanual, so a quick walkthrough of the chapters141 material in this manual, so a quick walkthrough of the chapters 142 142 is in order. 143 143 </para> … … 146 146 <para> 147 147 <xref linkend="installation"/> contains installation 148 instructions for &yaz;. You don't need readingthis148 instructions for &yaz;. You don't need to read this 149 149 if you expect to download &yaz; binaries. 150 150 However, the chapter contains information about how … … 156 156 <para> 157 157 <xref linkend="zoom"/> describes the ZOOM API of &yaz;. 158 This is definitely worth a readif you wish to develop a Z39.50/SRU158 This is definitely worth reading if you wish to develop a Z39.50/SRU 159 159 client. 160 160 </para> … … 170 170 <para> 171 171 <xref linkend="yaz-client"/> describes how to use the &yaz; Z39.50 172 client. If you're developer and wish to test your server172 client. If you're a developer and wish to test your server 173 173 or a server from another party, you might find this chapter 174 174 useful. … … 203 203 ODR module which is the work horse that encodes and decodes 204 204 BER packages. Implementors using ZOOM only, do <emphasis>not</emphasis> 205 need readingthis.205 need to read this. 206 206 Most other Z39.50 implementors only need to read the first two 207 207 sections (<xref linkend="odr.introduction"/> and … … 245 245 </para> 246 246 <para> 247 The YAZ toolkit modules isshown in figure <xref linkend="yaz.layer"/>.247 The YAZ toolkit modules are shown in figure <xref linkend="yaz.layer"/>. 248 248 </para> 249 249 <figure id="yaz.layer"> … … 326 326 <para> 327 327 If you are using the premade definitions of the &asn; module, and you 328 are not adding new protocol of your own, the only parts of &odr; that you328 are not adding a new protocol of your own, the only parts of &odr; that you 329 329 need to worry about are documented in 330 330 <xref linkend="odr.use"/>. … … 384 384 <ulink url="&url.freebsd;">FreeBSD (i386)</ulink>, 385 385 <ulink url="&url.macosx;">MAC OSX</ulink>, 386 <ulink url="&url.solaris;">Solaris</ulink>, 387 Windows 7, Windows XP. 388 </para> 389 <para> 390 Some versions have be known to work on HP/UX, 386 Windows 10. 387 </para> 388 <para> 389 Some versions have be known to work on Windows XP, Solaris, HP/UX, 391 390 DEC Unix, <ulink url="&url.netbsd;">NetBSD</ulink>, 392 391 <ulink url="&url.openbsd;">OpenBSD</ulink>, … … 464 463 <title>Compiling from source on Unix</title> 465 464 <para> 466 Note that if your system doesn't have a native ANSI C compiler, you may 467 have to acquire one separately. We recommend 468 <ulink url="&url.gcc;">GCC</ulink>. 465 You can choose to compile YAZ from official tar releases from 466 <ulink url="&url.yaz.download;"/> 467 or clone it via Github 468 <ulink url="https://github.com/indexdata/yaz.git"/>. 469 469 </para> 470 470 <para> … … 497 497 <ulink url="&url.libtool;">Libtool</ulink> 498 498 are used to generate Makefiles and configure &yaz; for the system. 499 You do <emphasis>not</emphasis> these tools unless you're using the499 You do <emphasis>not</emphasis> need these tools unless you're using the 500 500 Git version of &yaz;. 501 501 </para> … … 509 509 written in <ulink url="&url.tcl;">Tcl</ulink>. 510 510 But as for Bison you do not need it unless you're using Git 511 version of &yaz; or you're using the compiler to buil town codecs511 version of &yaz; or you're using the compiler to build your own codecs 512 512 for private ASN.1. 513 513 </para> 514 514 <para> 515 Generally it should be sufficient to run configure without options, 516 like this: 515 If you are checking out from Git, run: 516 <screen> 517 ./buildconf.sh 518 </screen> 519 This will create the <filename>configure</filename> script and Makefiles. 520 </para> 521 <para> 522 The next step is always: 517 523 </para> 518 524 <screen> … … 613 619 search for iconv on the system. Use this option if it 614 620 doesn't find iconv. Alternatively, 615 <literal>--without-iconv</literal>, can be use tto force &yaz;621 <literal>--without-iconv</literal>, can be used to force &yaz; 616 622 not to use iconv. 617 623 </para> … … 628 634 Use this option if you want XSLT and XML support. 629 635 By default, configure will 630 search for libxslt on the system. Use this option if it636 search for libxslt on the system. Use this option if 631 637 libxslt is not found automatically. Alternatively, 632 638 <literal>--without-xslt</literal>, can be used to force &yaz; … … 645 651 Use this option if you want &yaz; to use XML and support SRU/Solr. 646 652 By default, configure will 647 search for libxml2 on the system. Use this option if it653 search for libxml2 on the system. Use this option if 648 654 libxml2 is not found automatically. Alternatively, 649 655 <literal>--without-xml2</literal>, can be used to force &yaz; … … 683 689 <varlistentry> 684 690 <term> 685 <literal>--with-libgcrypt</literal>[=<replaceable>prefix</replaceable>]686 </term>687 <listitem>688 <para>&yaz; will be linked with689 <ulink url="&url.libgcrypt;">Libgcrypt</ulink> in the prefix if given.690 If prefix is not given, the libraries exposed by the script691 <application>libgcrypt-config</application> will be used if found.692 </para>693 </listitem>694 </varlistentry>695 <varlistentry>696 <term>697 691 <literal>--with-memcached</literal> 698 692 </term> … … 701 695 <ulink url="&url.libmemcached;">libMemcached</ulink> to allow 702 696 for result-set caching for ZOOM. 703 The prefix can not be given. Note that YAZ will only search 704 for libMemcached if Libgcrypt is also enabled. 697 The prefix can not be given. 705 698 Note that 0.40 of libmemcached is required. 706 699 </para> … … 715 708 to allow for result-set caching for ZOOM on a 716 709 <ulink url="&url.redis;">redis</ulink> server. 717 The prefix can not be given. Note that YAZ will only search 718 for hiredis if Libgcrypt is also enabled. 710 The prefix can not be given. 719 711 </para> 720 712 </listitem> … … 858 850 applications using the &yaz; toolkit. 859 851 If you're used to Makefiles this shouldn't be hard. As for 860 other libraries you have used before, you haveto set a proper include852 other libraries you have used before, you need to set a proper include 861 853 path for your C/C++ compiler and specify the location of 862 854 &yaz; libraries. You can do it by hand, but generally we suggest … … 929 921 <para>The easiest way to install YAZ on Windows is by downloading 930 922 an installer from 931 <ulink url="&url.yaz.download.win32;">here</ulink>. 923 <ulink url="&url.yaz.download.win32;"> 924 Index Data's Windows support area 925 </ulink>. 932 926 The installer comes with source too - in case you wish to 933 927 compile YAZ with different compiler options, etc. … … 940 934 with <ulink url="&url.vstudio;"> 941 935 Microsoft Visual Studio</ulink>. It has been tested with 942 Microsoft Visual Studio 201 3.936 Microsoft Visual Studio 2015. 943 937 </para> 944 938 <para> … … 984 978 </para> 985 979 <para> 986 A Windows version of GNU Bison is part of 987 <ulink url="&url.gitwindows;">Git for Windows</ulink>. 980 A Windows version of GNU Bison can be fetched from here: 981 <ulink 982 url="&url.indexdata.support.windows;bison-2.4.1-setup.exe"> 983 Index Data's Windows support area 984 </ulink>. 988 985 </para></listitem> 989 986 </varlistentry> … … 1027 1024 <note> 1028 1025 <para> 1029 libxslt depends libxml2.1026 libxslt depends on libxml2. 1030 1027 </para> 1031 1028 </note> … … 1042 1039 <literal>ICU_DIR</literal> to the 1043 1040 <ulink url="&url.icu;">ICU</ulink> source directory. 1041 </para> 1042 <para> 1043 Pre-compiled ICU libraries for various versions of Visual Studio 1044 can be found 1045 <ulink url="http://www.npcglib.org/~stathis/blog/precompiled-icu/"> 1046 here 1047 </ulink> or from Index Data's <ulink 1048 url="&url.indexdata.support.windows;">Windows support site</ulink>. 1044 1049 </para> 1045 1050 </listitem> … … 1139 1144 <listitem><para>This program exposes the ICU wrapper library if that 1140 1145 is enabled for YAZ. Only if ICU is available this program is 1141 buil d.1146 built. 1142 1147 </para></listitem> 1143 1148 </varlistentry> … … 1155 1160 <filename>bin/zoomtst2.exe</filename>, ..</term> 1156 1161 <listitem><para> 1157 Several small applications that demonstrate sthe ZOOM API.1162 Several small applications that demonstrate the ZOOM API. 1158 1163 </para></listitem> 1159 1164 </varlistentry> … … 1298 1303 became available, 1299 1304 an implementation for &yaz; was quickly developed. For the first time, it is 1300 now as easy (or easier!) to develop clients than servers with &yaz;. This 1305 now as easy (or easier!) to develop clients as it is to develop 1306 servers with &yaz;. This 1301 1307 chapter describes the &zoom; C binding. Before going further, please 1302 1308 reconsider whether C is the right programming language for the job. … … 1317 1323 such as C++, Java, etc. For example, you'll have to manually, 1318 1324 destroy all objects you create, even though you may think of them as 1319 temporary. Most objects ha sa <literal>_create</literal> - and a1325 temporary. Most objects have a <literal>_create</literal> - and a 1320 1326 <literal>_destroy</literal> variant. 1321 1327 All objects are in fact pointers to internal stuff, but you don't see … … 1362 1368 default scheme is <literal>tcp</literal> (Z39.50 protocol). 1363 1369 The scheme <literal>http</literal> selects SRU/get over HTTP by default, 1364 but can overridde d to use SRU/post, SRWand the Solr protocol.1370 but can overridden to use SRU/post, SRW, and the Solr protocol. 1365 1371 </para> 1366 1372 <para> … … 1450 1456 encoded in the otherInfo area of a Z39.50 PDU with OID 1451 1457 1.2.840.10003.10.1000.81.3. Holds the original IP addreses 1452 of a client. Is used of ZOOM is used in a gateway of some sort.1458 of a client. Is used if ZOOM is used in a gateway of some sort. 1453 1459 </entry><entry>none</entry></row> 1454 1460 <row><entry> … … 1489 1495 <row><entry> 1490 1496 databaseName</entry><entry>One or more database names 1491 separated by character plus (<literal>+</literal>), which to1497 separated by character plus (<literal>+</literal>), which is to 1492 1498 be used by subsequent search requests on this Connection. 1493 1499 </entry><entry>Default</entry></row> … … 1506 1512 <row><entry> 1507 1513 mediumSetPresentNumber</entry><entry>This value represents 1508 the number of records to be returned as part of a search when when1514 the number of records to be returned as part of a search when 1509 1515 hits is less than or equal to large set lower bound and if hits 1510 1516 is greater than small set upper bound. … … 1516 1522 <row><entry> 1517 1523 mediumSetElementSetName</entry><entry> 1518 The element set name to be for medium-sized result sets.1524 The element set name to be used for medium-sized result sets. 1519 1525 </entry><entry>none</entry></row> 1520 1526 <row><entry> … … 1533 1539 sru_version</entry><entry> 1534 1540 SRU/SRW version. Should be <literal>1.1</literal>, or 1535 <literal>1.2</literal>. This is 1541 <literal>1.2</literal>. This is, prior to connect, the version 1536 1542 to offer (highest version). And following connect (in fact 1537 1543 first operation), holds the negotiated version with the server … … 1545 1551 <row id="zoom.facets.option"><entry> 1546 1552 facets</entry><entry> 1547 Requested or recommend facets may be given before a search is sent.1553 Requested or recommended facets may be given before a search is sent. 1548 1554 The value of this setting is described in <xref linkend="facets"/> 1549 1555 For inspection of the facets returned, refer to the functions … … 1605 1611 option is supplied for an earlier version of YAZ, it is 1606 1612 <emphasis>ignored</emphasis>. 1607 The value of this option is a set o ptions, similar to that1613 The value of this option is a set of options, similar to that 1608 1614 of the memcached setting. At this stage only --server=host[:port] 1609 and --expire=seconds issupported.1615 and --expire=seconds are supported. 1610 1616 </entry><entry>none</entry></row> 1611 1617 </tbody> … … 1641 1647 <function>ZOOM_connection_connect</function> establishes a TCP/IP 1642 1648 connection and sends an Initialize Request to the target if 1643 possible. In addition, the calls wait sfor an Initialize Response1649 possible. In addition, the calls wait for an Initialize Response 1644 1650 from the target and the result is inspected (OK or rejected). 1645 1651 </para> … … 1677 1683 <title>SRU/Solr Protocol behavior</title> 1678 1684 <para> 1679 The HTTP based protocols (SRU, SRW, Solr) do esn't feature an1685 The HTTP based protocols (SRU, SRW, Solr) do not feature an 1680 1686 Inititialize Request, so the connection phase merely establishes a 1681 1687 TCP/IP connection with the HTTP server. … … 1743 1749 <function>ZOOM_query_sortby</function> but allows a strategy for 1744 1750 sorting. The reason for the strategy parameter is that some 1745 protocols offer smultiple ways of performing sorting.1751 protocols offer multiple ways of performing sorting. 1746 1752 For example, Z39.50 has the standard sort, which is performed after 1747 1753 search on an existing result set. … … 1799 1805 <para> 1800 1806 Function <function>ZOOM_connection_search</function> creates 1801 a result set given a connection and query.1807 a result set, given a connection and query. 1802 1808 Destroy a result set by calling 1803 1809 <function>ZOOM_resultset_destroy</function>. 1804 Simple clients may using PQF only may use function1810 Simple clients using PQF only, may use the function 1805 1811 <function>ZOOM_connection_search_pqf</function> in which case 1806 1812 creating query objects is not necessary. … … 1821 1827 </para> 1822 1828 <para> 1823 The number of hits also called result-countis returned by1829 The number of hits, also called result-count, is returned by 1824 1830 function <function>ZOOM_resultset_size</function>. 1825 1831 </para> … … 1919 1925 <entry>searchresult.size</entry> 1920 1926 <entry> 1921 number of search result entries. This option is -nonexistant1927 number of search result entries. This option is non-existent 1922 1928 if no entries are returned by the server. 1923 1929 </entry> … … 1962 1968 <function>ZOOM_resultset_sort</function> and 1963 1969 <function>ZOOM_resultset_sort1</function> both sort an existing 1964 result-set. The sort_type parameter is not use . Set it to "yaz".1970 result-set. The sort_type parameter is not used. Set it to "yaz". 1965 1971 The sort_spec is same notation as ZOOM_query_sortby and identical 1966 1972 to that offered by yaz-client's … … 2005 2011 the result set with a given start offset. When you use this mode 2006 2012 the client will automatically use piggyback if that is possible 2007 with the target and perform one or more present requests as needed.2013 with the target, and perform one or more present requests as needed. 2008 2014 Even if the target returns fewer records as part of a present response 2009 2015 because of a record size limit, etc. the client will repeat sending … … 2031 2037 Current version of &yaz; does not take advantage of a result set id 2032 2038 returned by the SRU server. Future versions might do, however. 2033 Since , the ZOOM driver does not save result set IDsany2039 Since the ZOOM driver does not save result set IDs, any 2034 2040 present (retrieval) is transformed to a SRU SearchRetrieveRequest 2035 2041 with same query but, possibly, different offsets. … … 2059 2065 </para> 2060 2066 <para> 2061 Solr queries hasto be done in Solr query format.2062 </para> 2063 <para> 2064 Unfortunately, SRU or Solr doesnot define a database setting. Hence,2067 Solr queries need to be done in Solr query format. 2068 </para> 2069 <para> 2070 Unfortunately, SRU and Solr do not define a database setting. Hence, 2065 2071 <literal>databaseName</literal> is unsupported and ignored. 2066 2072 However, the path part in host parameter for functions … … 2120 2126 a number of records from a result set. Parameter <literal>start</literal> 2121 2127 and <literal>count</literal> specifies the range of records to 2122 be returned. Upon completion array2128 be returned. Upon completion, the array 2123 2129 <literal>recs[0], ..recs[count-1]</literal> 2124 2130 holds record objects for the records. The array of records 2125 2131 <literal>recs</literal> should be allocated prior the call 2126 2132 <function>ZOOM_resultset_records</function>. Note that for those 2127 records that couldn't be retrieved from the target 2133 records that couldn't be retrieved from the target, 2128 2134 <literal>recs[ ..]</literal> is set to <literal>NULL</literal>. 2129 2135 </para> … … 2186 2192 <variablelist> 2187 2193 <varlistentry><term><literal>database</literal></term> 2188 <listitem><para> Database ofrecord is returned2194 <listitem><para>The Database of the record is returned 2189 2195 as a C null-terminated string. Return type 2190 2196 <literal>const char *</literal>. … … 2207 2213 <varlistentry><term><literal>render</literal></term> 2208 2214 <listitem><para>The record is returned in a display friendly 2209 format. Upon completion buffer is returned2215 format. Upon completion, buffer is returned 2210 2216 (type <literal>const char *</literal>) and length is stored in 2211 2217 <literal>*len</literal>. … … 2286 2292 The functions may block (and perform network I/O) - even though option 2287 2293 <literal>async</literal> is 1, because they return records objects. 2288 ( and there's no way to return records objects without retrieving them!).2294 (And there's no way to return records objects without retrieving them!) 2289 2295 </para> 2290 2296 <para> … … 2357 2363 <function>ZOOM_resultset_facets</function>. The length of the array is 2358 2364 given by <function>ZOOM_resultset_facets_size</function>. The array is 2359 zero-based and last entry will be at2365 zero-based and the last entry will be at 2360 2366 <function>ZOOM_resultset_facets_size(result_set)</function>-1. 2361 2367 </para> … … 2363 2369 It is possible to interate over facets by name, by calling 2364 2370 <function>ZOOM_resultset_facets_names</function>. 2365 This will return a nconst array of char * where each string can be used2371 This will return a const array of char * where each string can be used 2366 2372 as parameter for <function>ZOOM_resultset_get_facet_field</function>. 2367 2373 </para> … … 2422 2428 If the operation was successful, the size of the scan set can be 2423 2429 retrieved by a call to <function>ZOOM_scanset_size</function>. 2424 Like result sets, the items are numbered 0 ,..size-1.2430 Like result sets, the items are numbered 0..size-1. 2425 2431 To obtain information about a particular scan term, call function 2426 2432 <function>ZOOM_scanset_term</function>. This function takes … … 2542 2548 </itemizedlist> 2543 2549 <para> 2544 To create an extended service operation a <literal>ZOOM_package</literal>2550 To create an extended service operation, a <literal>ZOOM_package</literal> 2545 2551 must be created. The operation is a five step operation. The 2546 2552 package is created, package is configured by means of options, 2547 the package is sen d, result is inspected (by means of options),2553 the package is sent, result is inspected (by means of options), 2548 2554 the package is destroyed. 2549 2555 </para> … … 2624 2630 <entry>package-name</entry> 2625 2631 <entry>Extended Service Request package name. Must be specified 2626 as part of a request </entry>2632 as part of a request.</entry> 2627 2633 <entry>none</entry> 2628 2634 </row> 2629 2635 <row> 2630 2636 <entry>user-id</entry> 2631 <entry>User ID of Extended Service Package. Is a request option </entry>2637 <entry>User ID of Extended Service Package. Is a request option.</entry> 2632 2638 <entry>none</entry> 2633 2639 </row> … … 2869 2875 to record - and <literal>record</literal> option (above) is 2870 2876 ignored if recordOpaque is set. This option is only available in 2871 YAZ 3.0.35 and later and is meant to facilitate Updates with2877 YAZ 3.0.35 and later, and is meant to facilitate Updates with 2872 2878 servers from OCLC. 2873 2879 </entry> … … 2996 3002 <note> 2997 3003 <para> 2998 The database create, drop and commit services are privately defined3004 The database create, drop, and commit services are privately defined 2999 3005 operations. 3000 3006 Refer to <filename>esadmin.asn</filename> in YAZ for the ASN.1 … … 3008 3014 <para> 3009 3015 Most &zoom; objects provide a way to specify options to change behavior. 3010 From an implementation point of view a set of options is just like3016 From an implementation point of view, a set of options is just like 3011 3017 an associative array / hash. 3012 3018 </para> … … 3048 3054 <function>ZOOM_query_cql2rpn</function> translates the CQL string, 3049 3055 client-side, into RPN which may be passed to the server. 3050 This is useful for server 's that don't themselves3056 This is useful for servers that don't themselves 3051 3057 support CQL, for which <function>ZOOM_query_cql</function> is useless. 3052 `conn' is used only as a place to stash diagnostics if compilation3058 'conn' is used only as a place to stash diagnostics if compilation 3053 3059 fails; if this information is not needed, a null pointer may be used. 3054 3060 The CQL conversion is driven by option <literal>cqlfile</literal> from 3055 connection conn. This specifies a conversion file (e gpqf.properties)3061 connection conn. This specifies a conversion file (e.g. pqf.properties) 3056 3062 which <emphasis>must</emphasis> be present. 3057 3063 </para> … … 3061 3067 The conversion is driven by the specification given by 3062 3068 <literal>config</literal>. Upon completion 0 is returned on success; -1 3063 is returned on on failure. Omfailure <literal>error_string</literal> and3064 <literal>error_pos</literal> hold serror message and position of3069 is returned on failure. On failure <literal>error_string</literal> and 3070 <literal>error_pos</literal> hold the error message and position of 3065 3071 first error in original CCL string. 3066 3072 </para> … … 3079 3085 <literal>no</literal> and an array of connections in 3080 3086 <literal>cs</literal> (<literal>cs[0] ... cs[no-1]</literal>). 3081 A pending event could be asending a search, receiving a response,3087 A pending event could be sending a search, receiving a response, 3082 3088 etc. 3083 3089 When an event has occurred for one of the connections, this function … … 3086 3092 When no events are pending for the connections, a value of zero is 3087 3093 returned. 3088 To ensure that all outstanding requests are performed call this function3094 To ensure that all outstanding requests are performed, call this function 3089 3095 repeatedly until zero is returned. 3090 3096 </para> 3091 3097 <para> 3092 If <function>ZOOM_event</function> returns and returns non-zero, the3098 If <function>ZOOM_event</function> returns, and returns non-zero, the 3093 3099 last event that occurred can be expected. 3094 3100 </para> … … 3127 3133 <row> 3128 3134 <entry>ZOOM_EVENT_RECV_DATA</entry> 3129 <entry>Data has been received )</entry>3135 <entry>Data has been received</entry> 3130 3136 </row> 3131 3137 <row> … … 3151 3157 <row> 3152 3158 <entry>ZOOM_EVENT_RECV_SEARCH</entry> 3153 <entry>A search result been received</entry>3159 <entry>A search result has been received</entry> 3154 3160 </row> 3155 3161 </tbody> … … 3171 3177 <para> 3172 3178 If you have a database system that you would like to make available by 3173 means of Z39.50 or SRU, &yaz; basically offers yourtwo options. You3179 means of Z39.50 or SRU, &yaz; basically offers two options. You 3174 3180 can use the APIs provided by the &asn;, &odr;, and &comstack; 3175 3181 modules to … … 3316 3322 A boolean value, which determines whether the server 3317 3323 will fork on each incoming request (TRUE), or not (FALSE). Default is 3318 TRUE. This flag is only read by UNIX-based servers (WIN32 3319 do esn't fork).3324 TRUE. This flag is only read by UNIX-based servers (WIN32-based servers 3325 do not fork). 3320 3326 </para></listitem> 3321 3327 </varlistentry> … … 3334 3340 <listitem><para> 3335 3341 A boolean value, which determines whether the server 3336 will operate sunder a UNIX INET daemon (inetd). Default is FALSE.3342 will operate under a UNIX INET daemon (inetd). Default is FALSE. 3337 3343 </para></listitem> 3338 3344 </varlistentry> … … 3399 3405 command line options have been parsed - but before the server 3400 3406 starts listening. 3401 For forked UNIX servers this handler is called in the mother3402 process; for threaded servers this handler is called in the3407 For forked UNIX servers, this handler is called in the mother 3408 process; for threaded servers, this handler is called in the 3403 3409 main thread. 3404 3410 The default value of this pointer is NULL in which case it 3405 3411 isn't invoked by the frontend server. 3406 When the server operates as an NT service this handler is called3412 When the server operates as an NT service, this handler is called 3407 3413 whenever the service is started. 3408 3414 </para></listitem> … … 3415 3421 has stopped listening for incoming connections. This function pointer 3416 3422 has a default value of NULL in which case it isn't called. 3417 When the server operates as an NT service this handler is called3423 When the server operates as an NT service, this handler is called 3418 3424 whenever the service is stopped. 3419 3425 </para></listitem> … … 3431 3437 The pointer returned by <literal>statserv_getcontrol</literal> points to 3432 3438 a static area. You are allowed to change the contents of the structure, 3433 but the changes will not take effect beforeyou call3439 but the changes will not take effect until you call 3434 3440 </para> 3435 3441 <synopsis> … … 3438 3444 <note> 3439 3445 <para> 3440 that you should generally update this structure before calling3446 You should generally update this structure before calling 3441 3447 <function>statserv_main()</function>. 3442 3448 </para> … … 3470 3476 Unlike previous versions of YAZ, the <function>bend_init</function> also 3471 3477 serves as a handler that defines the Z39.50 services that the backend 3472 wishto support. Pointers to <emphasis>all</emphasis> service handlers,3478 intends to support. Pointers to <emphasis>all</emphasis> service handlers, 3473 3479 including search - and fetch must be specified here in this handler. 3474 3480 </para> … … 3576 3582 <para> 3577 3583 The <literal>auth</literal> member holds the authentication information 3578 part of the Z39.50 Initialize Request. Interpret this if your serve s3584 part of the Z39.50 Initialize Request. Interpret this if your server 3579 3585 requires authentication. 3580 3586 </para> … … 3632 3638 <para> 3633 3639 The <function>bend_search</function> handler is a fairly close 3634 approximation of a protocol Z39.50 Search Request - and Response PDUs 3640 approximation of a protocol Z39.50 Search Request - and Response PDUs. 3635 3641 The <literal>setname</literal> is the resultSetName from the protocol. 3636 3642 You are required to establish a mapping between the set name and whatever … … 3803 3809 <title>Delete</title> 3804 3810 <para> 3805 For back-ends that supports delete of a result set only one handler3811 For back-ends that supports delete of a result set, only one handler 3806 3812 must be defined. 3807 3813 </para> … … 3870 3876 This backend server handles both Z39.50 scan 3871 3877 and SRU scan. In order for a handler to distinguish between SRU (CQL) scan 3872 Z39.50 Scan 3878 Z39.50 Scan, it must check for a non-NULL value of 3873 3879 <literal>scanClause</literal>. 3874 3880 </para> 3875 3881 <note> 3876 3882 <para> 3877 if designed today, it would be a choice using a union or similar,3883 If designed today, it would be a choice using a union or similar, 3878 3884 but that would break binary compatibility with existing servers. 3879 3885 </para> … … 3955 3961 </para> 3956 3962 <para> 3957 The above for the Apache 1.3 series.3963 The above is for the Apache 1.3 series. 3958 3964 </para> 3959 3965 </example> … … 3961 3967 <title>Running a server with local access only</title> 3962 3968 <para> 3963 Serversthat is only being accessed from the local host should listen3964 on UNIX file socket rather than a Internet socket. To listen on3969 A server that is only being accessed from the local host should listen 3970 on UNIX file socket rather than an Internet socket. To listen on 3965 3971 <filename>/tmp/mysocket</filename> start the server as follows: 3966 3972 <screen> … … 3992 3998 <para> 3993 3999 The &asn; module is located in sub directory <filename>z39.50</filename>. 3994 There you'll find C files that implement sencoders and decoders for the4000 There you'll find C files that implement encoders and decoders for the 3995 4001 Z39.50 types. You'll also find the protocol definitions: 3996 4002 <filename>z3950v3.asn</filename>, <filename>esupdate.asn</filename>, … … 4036 4042 <function>odr_malloc()</function>, you can release all of the 4037 4043 allocated data in a single operation, independent of any pointers and 4038 relations between the data. <function>odr_malloc()</function> is based on a4039 "nibble-memory"4044 relations between the data. The <function>odr_malloc()</function> function 4045 is based on a "nibble-memory" 4040 4046 scheme, in which large portions of memory are allocated, and then 4041 4047 gradually handed out with each call to <function>odr_malloc()</function>. … … 4079 4085 </synopsis> 4080 4086 <para> 4081 e g.:4087 e.g.: 4082 4088 </para> 4083 4089 <synopsis> … … 4168 4174 </para> 4169 4175 <para> 4170 Some servers return ASN.1 structured data values (e g. database4176 Some servers return ASN.1 structured data values (e.g. database 4171 4177 records) as BER-encoded records placed in the 4172 4178 <literal>octet-aligned</literal> branch of the EXTERNAL CHOICE. … … 4179 4185 </screen> 4180 4186 <para> 4181 Can be used to retrieve information about the known, external data4182 types. The function return a pointer to a static area, or NULL, if no4187 can be used to retrieve information about the known, external data 4188 types. The function returns a pointer to a static area, or NULL, if no 4183 4189 match for the given direct reference is found. The 4184 4190 <literal>Z_ext_typeent</literal> … … 4214 4220 <para> 4215 4221 If you want to <emphasis>send</emphasis> EXTERNALs containing 4216 ASN.1-structured values in the oc ctet-aligned branch of the CHOICE, this4222 ASN.1-structured values in the octet-aligned branch of the CHOICE, this 4217 4223 is possible too. However, on the encoding phase, it requires a somewhat 4218 4224 involved juggling around of the various buffers involved. … … 4938 4944 <para> 4939 4945 &yaz; uses a very simple implementation of 4940 <ulink url="&url.soap;">SOAP</ulink> that only ,4941 currenly,supports what is sufficient to offer SRU SOAP functionality.4946 <ulink url="&url.soap;">SOAP</ulink> that only 4947 (currently) supports what is sufficient to offer SRU SOAP functionality. 4942 4948 The implementation uses the 4943 4949 <ulink url="&url.libxml2.api.tree;">tree API</ulink> of … … 5018 5024 <para> 5019 5025 The <literal>fault</literal> and <literal>soap_error</literal> 5020 arms represent botha SOAP fault - struct5026 arms both represent a SOAP fault - struct 5021 5027 <literal>Z_SOAP_Fault</literal>. Any other generic 5022 5028 (valid) package is represented by <literal>Z_SOAP_Generic</literal>. … … 5048 5054 inspects the XML content 5049 5055 and tries to match one of the services namespaces of the 5050 supplied handlers. If there is a match a handler function5056 supplied handlers. If there is a match. a handler function 5051 5057 is invoked which decodes that particular SOAP package. 5052 5058 If successful, the returned <literal>Z_SOAP</literal> package will be 5053 5059 of type <literal>Z_SOAP_Generic</literal>. 5054 5060 Member <literal>no</literal> is 5055 set the offset of handler that matched; <literal>ns</literal>5056 is set to namespace of matching handler; the void pointer5061 set the offset of the handler that matched; <literal>ns</literal> 5062 is set to namespace of the matching handler; the void pointer 5057 5063 <literal>p</literal> is set to the C data structure assocatiated 5058 5064 with the handler. 5059 5065 </para> 5060 5066 <para> 5061 When a NULL namespace is met (member <literal>ns</literal> b wlow),5067 When a NULL namespace is met (member <literal>ns</literal> below), 5062 5068 that specifies end-of-list. 5063 5069 </para> … … 5071 5077 } Z_SOAP_Handler; 5072 5078 </synopsis> 5073 The <literal>ns</literal> is namespace ofservice associated with5074 handler <literal>f</literal>. <literal>client_data</literal>5075 is user-defined data which is passed to handler.5079 The <literal>ns</literal> is the namespace of the service associated with 5080 handler <literal>f</literal>. The <literal>client_data</literal> 5081 is user-defined data which is passed to the handler. 5076 5082 </para> 5077 5083 <para> … … 5086 5092 and is a pointer to the <literal>Body</literal> element 5087 5093 of the SOAP package. The <parameter>handler_data</parameter> 5088 is an opaque pointer to aC definitions associated with the5089 SOAP service. <parameter>client_data</parameter> is the pointer5094 is an opaque pointer to C definitions associated with the 5095 SOAP service. The <parameter>client_data</parameter> is the pointer 5090 5096 which was set as part of the <literal>Z_SOAP_handler</literal>. 5091 Finally, <parameter>ns</parameter> the service namespace.5097 Finally, <parameter>ns</parameter> is the service namespace. 5092 5098 </para> 5093 5099 </sect1> … … 5150 5156 as a char pointer (<literal>char *</literal>). A null pointer 5151 5157 means that the element is absent. 5152 Data of type xsd:integer is represent d as a pointer to5158 Data of type xsd:integer is represented as a pointer to 5153 5159 an int (<literal>int *</literal>). Again, a null pointer 5154 us used for absent elements.5160 is used for absent elements. 5155 5161 </para> 5156 5162 <para> … … 5171 5177 </synopsis> 5172 5178 The <literal>num_records</literal> and <literal>num_diagnostics</literal> 5173 is number of returned records and diagnostics respectively and also5179 is number of returned records and diagnostics respectively, and also 5174 5180 correspond to the "size of" arrays <literal>records</literal> 5175 5181 and <literal>diagnostics</literal>. … … 5204 5210 <para> 5205 5211 In support of the service API - primarily the ASN module, which 5206 provides the pro -grammatic interface to the Z39.50 APDUs, &yaz; contains5212 provides the programmatic interface to the Z39.50 APDUs, &yaz; contains 5207 5213 a collection of tools that support the development of applications. 5208 5214 </para> … … 5233 5239 <note> 5234 5240 <para> 5235 The PQF ha vebeen adopted by other parties developing Z39.505241 The PQF has been adopted by other parties developing Z39.50 5236 5242 software. It is often referred to as Prefix Query Notation 5237 5243 - PQN. … … 5240 5246 <para> 5241 5247 The PQF is defined by the pquery module in the YAZ library. 5242 There are two sets of function that have similar behavior. First5248 There are two sets of functions that have similar behavior. First 5243 5249 set operates on a PQF parser handle, second set doesn't. First set 5244 setof functions are more flexible than the second set. Second set5250 of functions are more flexible than the second set. Second set 5245 5251 is obsolete and is only provided to ensure backwards compatibility. 5246 5252 </para> … … 5266 5272 <function>yaz_pqf_create</function> and 5267 5273 <function>yaz_pqf_destroy</function> respectively. 5268 Function <function>yaz_pqf_parse</function> parses query given5274 Function <function>yaz_pqf_parse</function> parses the query given 5269 5275 by string <literal>qbuf</literal>. If parsing was successful, 5270 5276 a Z39.50 RPN Query is returned which is created using ODR stream … … 5280 5286 <function>yaz_pqf_error</function> which returns an error code and 5281 5287 modifies <literal>*msg</literal> to point to an error description, 5282 and modifies <literal>*off</literal> to the offset within last5283 query w ere parsing failed.5288 and modifies <literal>*off</literal> to the offset within the last 5289 query where parsing failed. 5284 5290 </para> 5285 5291 <para> … … 5370 5376 an attribute type, an equals sign, and an attribute value, like this: 5371 5377 <literal>@attr 1=1003</literal>. 5372 The type is always an integer but the value may be either an5378 The type is always an integer, but the value may be either an 5373 5379 integer or a string (if it doesn't start with a digit character). 5374 A string attribute-value is encoded as a Type-1 ``complex''5380 A string attribute-value is encoded as a Type-1 "complex" 5375 5381 attribute with the list of values containing the single string 5376 5382 specified, and including no semantic indicators. … … 5424 5430 @prox <replaceable>exclusion</replaceable> <replaceable>distance</replaceable> <replaceable>ordered</replaceable> <replaceable>relation</replaceable> <replaceable>which-code</replaceable> <replaceable>unit-code</replaceable> 5425 5431 </screen> 5426 in which the meanings of the parameters are as described in in5432 in which the meanings of the parameters are as described in 5427 5433 the standard, and they can take the following values: 5428 5434 <itemizedlist> … … 5471 5477 <literal>k</literal> 5472 5478 (the unit-code parameter is taken from the well-known list 5473 of alternatives described inbelow) or5479 of alternatives described below) or 5474 5480 <literal>private</literal> 5475 5481 or 5476 5482 <literal>p</literal> 5477 (the unit-code param ater has semantics specific to an5483 (the unit-code parameter has semantics specific to an 5478 5484 out-of-band agreement such as a profile). 5479 5485 </para> … … 5585 5591 <listitem> 5586 5592 <para> 5587 which-code is ``known'', so the standard unit-codes are used5593 which-code is "known", so the standard unit-codes are used 5588 5594 </para> 5589 5595 </listitem> … … 5596 5602 both occur in the record, in that order, differing in position 5597 5603 by three or fewer words (i.e. with two or fewer words between 5598 them.) The query would find ``Bob Dylan, aka. Robert5599 Zimmerman '', but not ``Bob Dylan, born as Robert Zimmerman''5604 them.) The query would find "Bob Dylan, aka. Robert 5605 Zimmerman", but not "Bob Dylan, born as Robert Zimmerman" 5600 5606 since the distance in this case is four. 5601 5607 </para> … … 5625 5631 2038 indicates West Bounding Coordinate and 5626 5632 2030 indicates East Bounding Coordinate, 5627 so the query is for areas extending from -114 degrees 5628 to no more than -109 degrees .5633 so the query is for areas extending from -114 degrees longitude 5634 to no more than -109 degrees longitude. 5629 5635 </para> 5630 5636 </example> … … 5645 5651 <para> 5646 5652 The CCL parser obeys the following grammar for the FIND argument. 5647 The syntax is annotated by in thelines prefixed by5653 The syntax is annotated using lines prefixed by 5648 5654 <literal>--</literal>. 5649 5655 </para> … … 5711 5717 </screen> 5712 5718 <para> 5713 Assuming that the qualifiers <literal>ti</literal> ,5714 <literal>au</literal>5715 and <literal>date</literal> are defined we may use:5719 Assuming that the qualifiers <literal>ti</literal> 5720 and <literal>au</literal> 5721 and <literal>date</literal> are defined, we may use: 5716 5722 </para> 5717 5723 <screen> … … 5757 5763 <para> 5758 5764 where <replaceable>qualifier-name</replaceable> is the name of the 5759 qualifier to be used (e g. <literal>ti</literal>),5765 qualifier to be used (e.g. <literal>ti</literal>), 5760 5766 <replaceable>type</replaceable> is attribute type in the attribute 5761 5767 set (Bib-1 is used if no attribute set is given) and 5762 5768 <replaceable>val</replaceable> is attribute value. 5763 5769 The <replaceable>type</replaceable> can be specified as an 5764 integer or as it be specified either as a single-letter:5770 integer, or as a single-letter: 5765 5771 <literal>u</literal> for use, 5766 <literal>r</literal> for relation, <literal>p</literal> for position,5767 <literal>s</literal> for structure,<literal>t</literal> for truncation 5772 <literal>r</literal> for relation, <literal>p</literal> for position, 5773 <literal>s</literal> for structure,<literal>t</literal> for truncation, 5768 5774 or <literal>c</literal> for completeness. 5769 5775 The attributes for the special qualifier name <literal>term</literal> … … 5786 5792 Use attribute (1). Common use attributes are 5787 5793 1 Personal-name, 4 Title, 7 ISBN, 8 ISSN, 30 Date, 5788 62 Subject, 1003 Author ), 1016 Any. Specify value5794 62 Subject, 1003 Author, 1016 Any. Specify value 5789 5795 as an integer. 5790 5796 </entry> … … 5819 5825 <entry> 5820 5826 Truncation attribute (5). Values: 1 right, 2 left, 5821 3 left &right, 100 none, 101 process #, 102 regular-1,5827 3 left and right, 100 none, 101 process #, 102 regular-1, 5822 5828 103 regular-2, 104 CCL. 5823 5829 </entry> … … 5864 5870 <entry><literal>s=al</literal></entry> 5865 5871 <entry> 5866 Each token in the term is ANDed .(and-list).5872 Each token in the term is ANDed (and-list). 5867 5873 This does not set the structure at all. 5868 5874 </entry> … … 5870 5876 <row><entry><literal>s=ol</literal></entry> 5871 5877 <entry> 5872 Each token in the term is ORed .(or-list).5878 Each token in the term is ORed (or-list). 5873 5879 This does not set the structure at all. 5874 5880 </entry> … … 5893 5899 <row><entry><literal>r=o</literal></entry> 5894 5900 <entry> 5895 Allows ranges and the operators great her-than, less-than, ...5901 Allows ranges and the operators greater-than, less-than, ... 5896 5902 equals. 5897 5903 This sets Bib-1 relation attribute accordingly (relation … … 5919 5925 <entry> 5920 5926 This will omit relation=equals (@attr 2=3) when r=o / r=r 5921 is used. This is useful for servers that somehow break s5927 is used. This is useful for servers that somehow break 5922 5928 when an explicit relation=equals is used. Omitting the 5923 5929 relation is usually safe because "equals" is the default … … 5947 5953 <row><entry><literal>t=b</literal></entry> 5948 5954 <entry> 5949 Allows term to be both left &right truncated.5955 Allows term to be both left-and-right truncated. 5950 5956 If term is of the form <literal>?x?</literal>, the 5951 5957 resulting term is <literal>x</literal> and trunctation is 5952 set to both left &right.5958 set to both left and right. 5953 5959 </entry> 5954 5960 </row> … … 5957 5963 Allows masking anywhere in a term, thus fully supporting 5958 5964 # (mask one character) and ? (zero or more of any). 5959 If masking is used, trunc tion is set to 102 (regexp-1 in term)5965 If masking is used, truncation is set to 102 (regexp-1 in term) 5960 5966 and the term is converted accordingly to a regular expression. 5961 5967 </entry> … … 5965 5971 Allows masking anywhere in a term, thus fully supporting 5966 5972 # (mask one character) and ? (zero or more of any). 5967 If masking is used, trunc tion is set to 104 (Z39.58 in term)5973 If masking is used, truncation is set to 104 (Z39.58 in term) 5968 5974 and the term is converted accordingly to Z39.58 masking term - 5969 5975 actually the same truncation as CCL itself. … … 5992 5998 sets the use-attribute to 4. <literal>au</literal> sets the 5993 5999 use-attribute to 1. 5994 When no qualifiers are used in the query the structure-attribute is6000 When no qualifiers are used in the query, the structure-attribute is 5995 6001 set to free-form-text (105) (rule for <literal>term</literal>). 5996 6002 The <literal>date</literal> sets the relation attribute to … … 6141 6147 which takes the CCL profile (<literal>bibset</literal>) and query 6142 6148 (<literal>str</literal>) as input. Upon successful completion the RPN 6143 tree is returned. If an error occur , such as a syntax error, the integer6149 tree is returned. If an error occurs, such as a syntax error, the integer 6144 6150 pointed to by <literal>error</literal> holds the error code and 6145 6151 <literal>pos</literal> holds the offset inside query string in which … … 6261 6267 </synopsis> 6262 6268 The functions <function>cql_parser_stream</function> and 6263 <function>cql_parser_stdio</function> parse sa CQL query6269 <function>cql_parser_stdio</function> parse a CQL query 6264 6270 - just like <function>cql_parser_string</function>. 6265 6271 The only difference is that the CQL query can be … … 6273 6279 <title>CQL tree</title> 6274 6280 <para> 6275 Thethe query string is valid, the CQL parser6281 If the query string is valid, the CQL parser 6276 6282 generates a tree representing the structure of the 6277 6283 CQL query. … … 6281 6287 struct cql_node *cql_parser_result(CQL_parser cp); 6282 6288 </synopsis> 6283 <function>cql_parser_result</function> returns the6289 <function>cql_parser_result</function> returns 6284 6290 a pointer to the root node of the resulting tree. 6285 6291 </para> … … 6439 6445 <literal>*addinfop</literal> to point to a string containing 6440 6446 additional information about the error that occurred: for 6441 example, if the error code is 15 ( ``Illegal or unsupported context6442 set ''), the additional information is the name of the requested6447 example, if the error code is 15 ("Illegal or unsupported context 6448 set"), the additional information is the name of the requested 6443 6449 context set that was not recognised. 6444 6450 </para> … … 6516 6522 </para> 6517 6523 <para> 6518 For terms not bound by an index the pattern6524 For terms not bound by an index, the pattern 6519 6525 <literal>index.cql.serverChoice</literal> is used. 6520 6526 Here, the prefix <literal>cql</literal> is defined as … … 6548 6554 <para> 6549 6555 This pattern specifies how a CQL relation is mapped to RPN. 6550 <replaceable>pattern</replaceable> is name of relation6556 The <replaceable>pattern</replaceable> is name of relation 6551 6557 operator. Since <literal>=</literal> is used as 6552 6558 separator between CQL pattern and RPN, CQL relations … … 6589 6595 <para> 6590 6596 This pattern specifies how a CQL structure is mapped to RPN. 6591 Note that this CQL pattern is somewhat tosimilar to6597 Note that this CQL pattern is somewhat similar to 6592 6598 CQL pattern <literal>relation</literal>. 6593 6599 The <replaceable>type</replaceable> is a CQL relation. … … 6748 6754 Conversion from CQL to XCQL is trivial and does not 6749 6755 require a mapping to be defined. 6750 There three functions to choose from depending on the6756 There are three functions to choose from depending on the 6751 6757 way you wish to store the resulting output (XML buffer 6752 6758 containing XCQL). … … 6759 6765 </synopsis> 6760 6766 Function <function>cql_to_xml_buf</function> converts 6761 to XCQL and stores result in a usersupplied buffer of a given6767 to XCQL and stores the result in a user-supplied buffer of a given 6762 6768 max size. 6763 6769 </para> 6764 6770 <para> 6765 6771 <function>cql_to_xml</function> writes the result in 6766 a user 6772 a user-defined output stream. 6767 6773 <function>cql_to_xml_stdio</function> writes to a 6768 6774 a file. … … 6805 6811 <para> 6806 6812 An OID can either be declared as a automatic variable or it can 6807 allocated using the memory utilities or ODR/NMEM. It's6813 be allocated using the memory utilities or ODR/NMEM. It's 6808 6814 guaranteed that an OID can fit in <literal>OID_SIZE</literal> integers. 6809 6815 </para> … … 6825 6831 <para> 6826 6832 And OID may also be filled from a string-based representation using 6827 dots (.). This is achieved by function6833 dots (.). This is achieved by the function 6828 6834 <screen> 6829 6835 int oid_dotstring_to_oid(const char *name, Odr_oid *oid); … … 6833 6839 <example id="tools.oid.bib1.2"><title>Using oid_oiddotstring_to_oid</title> 6834 6840 <para> 6835 We can fill the Bib-1 attribute set OID easierwith:6841 We can fill the Bib-1 attribute set OID more easily with: 6836 6842 <screen> 6837 6843 Odr_oid bib1[OID_SIZE]; … … 6841 6847 </example> 6842 6848 <para> 6843 We can also allocate an OID dynamically on a ODR stream with:6849 We can also allocate an OID dynamically on an ODR stream with: 6844 6850 <screen> 6845 6851 Odr_oid *odr_getoidbystr(ODR o, const char *str); 6846 6852 </screen> 6847 This creates an OID from string-based representation using dots.6853 This creates an OID from a string-based representation using dots. 6848 6854 This function take an &odr; stream as parameter. This stream is used to 6849 6855 allocate memory for the data elements, which is released on a … … 6853 6859 <title>Using odr_getoidbystr</title> 6854 6860 <para> 6855 We can create a OID for the Bib-1 attribute set with:6861 We can create an OID for the Bib-1 attribute set with: 6856 6862 <screen> 6857 6863 Odr_oid *bib1 = odr_getoidbystr(odr, "1.2.840.10003.3.1"); … … 6871 6877 <para> 6872 6878 OIDs can be copied with <function>oid_oidcpy</function> which takes 6873 two OID lists as arguments. Alternativ ly, an OID copy can be allocated6874 on a ODR stream with:6879 two OID lists as arguments. Alternatively, an OID copy can be allocated 6880 on an ODR stream with: 6875 6881 <screen> 6876 6882 Odr_oid *odr_oiddup(ODR odr, const Odr_oid *o); … … 6906 6912 <para> 6907 6913 A YAZ database handle is of type <literal>yaz_oid_db_t</literal>. 6908 Actually that's a pointer. You need not thinkdeal with that.6914 Actually that's a pointer. You need not deal with that. 6909 6915 YAZ has a built-in database which can be considered "constant" for 6910 6916 most purposes. 6911 We can get hold that by using function <function>yaz_oid_std</function>.6917 We can get hold of that by using function <function>yaz_oid_std</function>. 6912 6918 </para> 6913 6919 <para> … … 6940 6946 <para> 6941 6947 All the object identifers in the standard OID database as returned 6942 by <function>yaz_oid_std</function> can referenced directly in a6948 by <function>yaz_oid_std</function> can be referenced directly in a 6943 6949 program as a constant OID. 6944 6950 Each constant OID is prefixed with <literal>yaz_oid_</literal> - … … 6973 6979 memory-management system of the &odr; subsystem (see 6974 6980 <xref linkend="odr.use"/>). However, in some circumstances 6975 where you might otherwise benefit from using a simple nibble 6981 where you might otherwise benefit from using a simple nibble-memory 6976 6982 management system, it may be impractical to use 6977 6983 <function>odr_malloc()</function> and <function>odr_reset()</function>. … … 7005 7011 </para> 7006 7012 <para> 7007 The nibble 7013 The nibble-memory pool is shared amongst threads. POSIX 7008 7014 mutex'es and WIN32 Critical sections are introduced to keep the 7009 7015 module thread safe. Function <function>nmem_init()</function> 7010 initializes the nibble 7016 initializes the nibble-memory library and it is called automatically 7011 7017 the first time the <literal>YAZ.DLL</literal> is loaded. &yaz; uses 7012 7018 function <function>DllMain</function> to achieve this. You should … … 7029 7035 Due to name clash with syslog and some math utilities the logging 7030 7036 interface has been modified as of YAZ 2.0.29. The obsolete interface 7031 is still available i f in header file <filename>yaz/log.h</filename>.7037 is still available in header file <filename>yaz/log.h</filename>. 7032 7038 The key points of the interface are: 7033 7039 </para> … … 7079 7085 </para> 7080 7086 <para> 7081 Each module should check what log bits itshould be used, by calling7087 Each module should check what log bits should be used, by calling 7082 7088 <function>yaz_log_module_level</function> with a suitable name for the 7083 module. The name is cleared froma preceding path and an extension, if any,7089 module. The name is cleared of a preceding path and an extension, if any, 7084 7090 so it is quite possible to use <literal>__FILE__</literal> for it. If the 7085 7091 name has been passed to <function>yaz_log_mask_str</function>, the routine … … 7098 7104 debugging of yaz itself. 7099 7105 Of course, any program using yaz is welcome to define as many new 7100 ones ,as it needs.7106 ones as it needs. 7101 7107 </para> 7102 7108 <para> … … 7157 7163 YAZ provides a fast utility for working with MARC records. 7158 7164 Early versions of the MARC utility only allowed decoding of ISO2709. 7159 Today the utility may both encode - and decode to a vari ty of formats.7165 Today the utility may both encode - and decode to a variety of formats. 7160 7166 </para> 7161 7167 <synopsis><![CDATA[ … … 7209 7215 </para> 7210 7216 <para> 7211 All other function operate on a <literal>yaz_marc_t</literal> handle.7217 All other functions operate on a <literal>yaz_marc_t</literal> handle. 7212 7218 The output is specified by a call to <function>yaz_marc_xml</function>. 7213 7219 The <literal>xmlmode</literal> must be one of … … 7218 7224 <para> 7219 7225 A simple line-by-line format suitable for display but not 7220 recommend for further (machine) processing.7226 recommended for further (machine) processing. 7221 7227 </para> 7222 7228 </listitem> … … 7269 7275 <listitem> 7270 7276 <para> 7271 <ulink url="&url.marc_in_json;">MARC-in _JSON</ulink> format.7277 <ulink url="&url.marc_in_json;">MARC-in-JSON</ulink> format. 7272 7278 </para> 7273 7279 </listitem> … … 7279 7285 <function>yaz_marc_decode_buf</function> and 7280 7286 <function>yaz_marc_decode_wrbuf</function> which decodes and encodes 7281 a MARC record. The former function operates on simple buffers, the7287 a MARC record. The former function operates on simple buffers, and 7282 7288 stores the resulting record in a WRBUF handle (WRBUF is a simple string 7283 7289 type). … … 7313 7319 Applications like 7314 7320 Pazpar2 uses XSLT to convert an XML encoded MARC record to an internal 7315 representation. This conversion mostly check the tag of a MARC field7321 representation. This conversion mostly checks the tag of a MARC field 7316 7322 to determine the basic rules in the conversion. This check is 7317 costly when that istag is encoded as an attribute in MARCXML.7323 costly when that tag is encoded as an attribute in MARCXML. 7318 7324 By having the tag value as the element instead, makes processing 7319 7325 many times faster (at least for Libxslt). … … 7350 7356 with the tag value of the control field if the tag value 7351 7357 matches the regular expression <literal>[a-zA-Z0-9]*</literal>. 7352 If the tag value do not match the regular expression7358 If the tag value does not match the regular expression 7353 7359 <literal>[a-zA-Z0-9]*</literal> the control field is encoded 7354 7360 as element <literal>c</literal> and attribute <literal>code</literal> 7355 7361 will hold the tag value. 7356 This rule ensure that in the rare cases where a tag value might7357 result in a non-well formed XML YAZ encode it as a codedattribute7362 This rule ensures that in the rare cases where a tag value might 7363 result in a non-well-formed XML, then YAZ will encode it as a coded attribute 7358 7364 (as in MARCXML). 7359 7365 </para> 7360 7366 <para> 7361 The control field content is the t he text value of this element.7367 The control field content is the text value of this element. 7362 7368 Indicators are encoded as attribute names 7363 <literal>i1</literal>, <literal>i2</literal>, etc. .and7369 <literal>i1</literal>, <literal>i2</literal>, etc. and 7364 7370 corresponding values for each indicator. 7365 7371 </para> … … 7370 7376 with the tag value of the data field or using the attribute 7371 7377 <literal>code</literal> as described in the rules for control fields. 7372 The children of the data field element issubfield elements.7378 The children of the data field element are subfield elements. 7373 7379 Each subfield element is encoded as <literal>s</literal> 7374 7380 concatenated with the sub field code. 7375 7381 The text of the subfield element is the contents of the subfield. 7376 Indicators are encoded as attributes for the data field element similar7382 Indicators are encoded as attributes for the data field element, similar 7377 7383 to the encoding for control fields. 7378 7384 </para> … … 7425 7431 configuration is neither Z39.50 ZeeRex or SRU ZeeRex. But it 7426 7432 should be easy to generate both of them from the XML configuration. 7427 ( unfortunately the two versions7428 of ZeeRex differ substantially in this regard ).7433 (Unfortunately the two versions 7434 of ZeeRex differ substantially in this regard.) 7429 7435 </para> 7430 7436 <sect2 id="tools.retrieval.format"> … … 7458 7464 <para> 7459 7465 Defines the name of the retrieval format. This can be 7460 any string. For SRU, the value ,is equivalent to schema (short-hand);7466 any string. For SRU, the value is equivalent to schema (short-hand); 7461 7467 for Z39.50 it's equivalent to simple element set name. 7462 7468 For YAZ 3.0.24 and later this name may be specified as a glob … … 7470 7476 <para> 7471 7477 Defines the URI schema name of the retrieval format. This can be 7472 any string. For SRU, the value ,is equivalent to URI schema.7478 any string. For SRU, the value is equivalent to URI schema. 7473 7479 For Z39.50, there is no equivalent. 7474 7480 </para> … … 7486 7492 <para> 7487 7493 The attributes, <literal>name</literal> and <literal>syntax</literal> 7488 may be specified for the <literal>backend</literal> element. The se7494 may be specified for the <literal>backend</literal> element. The 7489 7495 semantics of these attributes is equivalent to those for the 7490 7496 <literal>retrieval</literal>. However, these values are passed to … … 7492 7498 </para> 7493 7499 <para> 7494 The <literal>backend</literal> element may include sone or more7500 The <literal>backend</literal> element may include one or more 7495 7501 conversion instructions (as children elements). The supported 7496 7502 conversions are: … … 7511 7517 <literal>marc</literal> (for ISO2709), <literal>xml</literal> 7512 7518 (MARCXML/MarcXchange) and <literal>json</literal> 7513 (<ulink url="&url.marc_in_json;">MARC-in _JSON</ulink>).7519 (<ulink url="&url.marc_in_json;">MARC-in-JSON</ulink>). 7514 7520 </para> 7515 7521 </listitem> … … 7525 7531 <literal>marcxhcange</literal> (for MarcXchange), 7526 7532 or <literal>json</literal> 7527 (<ulink url="&url.marc_in_json;">MARC-in _JSON </ulink>).7533 (<ulink url="&url.marc_in_json;">MARC-in-JSON </ulink>). 7528 7534 </para> 7529 7535 </listitem> … … 7669 7675 <title>MARCXML backend</title> 7670 7676 <para> 7671 SRW/SRU and Solr backends return srecords in XML.7677 SRW/SRU and Solr backends return records in XML. 7672 7678 If they return MARCXML or MarcXchange, the retrieval module 7673 7679 can convert those into ISO2709 formats, most commonly USMARC … … 7744 7750 <para> 7745 7751 In SRU/Solr, however, the model is different. Here, sorting is specified 7746 during the thesearch operation. Note, however, that SRU might7752 during the search operation. Note, however, that SRU might 7747 7753 perform sort as separate search, by referring to an existing result-set 7748 7754 in the query (result-set reference). … … 7751 7757 <title>Using the Z39.50 sort service</title> 7752 7758 <para> 7753 yaz-client and the ZOOM API support sthe Z39.50 sort facility. In any7759 yaz-client and the ZOOM API support the Z39.50 sort facility. In any 7754 7760 case the sort sequence or sort critiera is using a string notation. 7755 7761 This notation is a one-line notation suitable for being manually 7756 entered or generated and allows for easy logging (one liner).7762 entered or generated, and allows for easy logging (one liner). 7757 7763 For the ZOOM API, the sort is specified in the call to ZOOM_query_sortby 7758 7764 function. For yaz-client the sort is performed and specified using … … 7780 7786 </para> 7781 7787 <para> 7782 The sort is triggered by the presence of type 7 and the value of type 77788 The sort is triggered by the presence of type 7, and the value of type 7 7783 7789 specifies the 7784 7790 <ulink url="http://www.loc.gov/z3950/agency/asn1.html#SortKeySpec"> 7785 7791 sortRelation 7786 </ulink> 7792 </ulink>. 7787 7793 The value for type 7 is 1 for ascending and 2 for descending. 7788 7794 For the … … 7793 7799 sortField, then attribute type 1 is present and the value is 7794 7800 sortField (InternationalString). If generic sortKey is of type 7795 sortAttributes, then the attributes in list is used . generic sortKey7801 sortAttributes, then the attributes in the list are used. Generic sortKey 7796 7802 of type elementSpec is not supported. 7797 7803 </para> … … 7806 7812 <title>Facets</title> 7807 7813 <para> 7808 YAZ supports facets for inSolr, SRU 2.0 and Z39.50 protocols.7814 YAZ supports facets in the Solr, SRU 2.0 and Z39.50 protocols. 7809 7815 </para> 7810 7816 <para> … … 7814 7820 </para> 7815 7821 <para> 7816 For ZOOM C the facets are given by option "facets" 7817 For yaz-client it is used for the facetscommand.7822 For ZOOM C the facets are given by option "facets". 7823 For yaz-client it is used for the 'facets' command. 7818 7824 </para> 7819 7825 <para> … … 7828 7834 </literallayout> 7829 7835 The notation is inspired by PQF. The string following '@attr' 7830 m aynot include blanks and is of the form7836 must not include blanks and is of the form 7831 7837 <replaceable>type</replaceable><literal>=</literal><replaceable>value</replaceable>, 7832 7838 where <replaceable>type</replaceable> is an integer and … … 7851 7857 <entry>1</entry> 7852 7858 <entry> 7853 Field-name. This is often a string, e g"Author", "Year", etc.7859 Field-name. This is often a string, e.g. "Author", "Year", etc. 7854 7860 </entry> 7855 7861 </row> … … 7883 7889 <title>Introduction</title> 7884 7890 <para> 7885 &odr; is the BER-encoding/decoding subsystem of &yaz;. Care as been taken7891 &odr; is the BER-encoding/decoding subsystem of &yaz;. Care has been taken 7886 7892 to isolate &odr; from the rest of the package - specifically from the 7887 7893 transport interface. &odr; may be used in any context where basic … … 7994 8000 small bits of space, the system maintains a free-list of larger chunks 7995 8001 of memory, which are handed out in small bits. This scheme is 7996 generally known as a <emphasis>nibble 8002 generally known as a <emphasis>nibble-memory</emphasis> system. 7997 8003 It is very useful for maintaining short-lived constructions such 7998 8004 as protocol PDUs. … … 8207 8213 </synopsis> 8208 8214 before encoders or decoders are being invoked. 8209 It is also possible to direct the output to a buffer (o findeed8215 It is also possible to direct the output to a buffer (or indeed 8210 8216 another file), by using the more generic mechanism: 8211 8217 <synopsis> … … 8222 8228 if NULL for the function is provided, it will not be invoked. 8223 8229 The <replaceable>stream_write</replaceable> takes the ODR handle 8224 as parameter, the user 8230 as parameter, the user-defined handle, a type 8225 8231 <literal>ODR_OCTETSTRING</literal>, <literal>ODR_VISIBLESTRING</literal> 8226 which indicates the type of contents isbeing written.8232 which indicates the type of contents being written. 8227 8233 </para> 8228 8234 <para> … … 8234 8240 which returns a list of current elements that ODR deals with at the 8235 8241 moment. For the returned array, say <literal>ar</literal>, 8236 <literal>ar[0]</literal> is the top level element,8242 then <literal>ar[0]</literal> is the top level element, 8237 8243 <literal>ar[n]</literal> is the last. The last element has the 8238 8244 property that <literal>ar[n+1] == NULL</literal>. … … 8484 8490 that holds the octetstring. The <literal>len</literal> field holds the 8485 8491 actual length. 8486 The character array need not be null 8492 The character array need not be null-terminated. 8487 8493 </para> 8488 8494 <para> 8489 8495 To make things a little easier, an alternative is given for string 8490 types that are not expected to contain embedded NULL characters (e g.8496 types that are not expected to contain embedded NULL characters (e.g. 8491 8497 VisibleString): 8492 8498 </para> … … 8495 8501 </synopsis> 8496 8502 <para> 8497 Which encodedor decodes between OCTETSTRING representations and8498 null-terminate sC strings.8499 </para> 8500 <para> 8501 Functions are provided for the derived string types, e g:8503 which encodes or decodes between OCTETSTRING representations and 8504 null-terminated C strings. 8505 </para> 8506 <para> 8507 Functions are provided for the derived string types, e.g.: 8502 8508 </para> 8503 8509 <synopsis> … … 8514 8520 <para> 8515 8521 The opaque type <literal>Odr_bitmask</literal> is only suitable for 8516 holding relatively brief bit strings, e g. for options fields, etc.8522 holding relatively brief bit strings, e.g. for options fields, etc. 8517 8523 The constant <literal>ODR_BITMASK_SIZE</literal> multiplied by 8 8518 8524 gives the maximum possible number of bits. … … 8626 8632 the data stream. <literal>size</literal> bytes of memory are allocated, 8627 8633 and <literal>*p</literal> is set to point to this space. 8628 <function>odr_sequence_end()</function> is called at the end of the8634 The <function>odr_sequence_end()</function> is called at the end of the 8629 8635 complex function. Assume that a type is defined like this: 8630 8636 </para> … … 8752 8758 <para> 8753 8759 Assume that the IMPLICIT in the type definition above were replaced 8754 with EXPLICIT (or that the IMPLICIT keyword w eresimply deleted, which8760 with EXPLICIT (or that the IMPLICIT keyword was simply deleted, which 8755 8761 would be equivalent). The structure definition would look the same, 8756 8762 but the function would look like this: … … 8779 8785 simple: Explicitly tagged, constructed types are fairly rare in 8780 8786 the protocols that we care about, so the 8781 esthetic annoyance (not to mention the dangers of a cluttered8787 aesthetic annoyance (not to mention the dangers of a cluttered 8782 8788 interface) is less than the time that would be required to develop a 8783 8789 better interface. Nevertheless, it is far from satisfying, and it's a … … 8976 8982 </para> 8977 8983 <para> 8978 The ASN.1 specifications naturally require sthat each member of a8984 The ASN.1 specifications naturally require that each member of a 8979 8985 CHOICE have a distinct tag, so they can be told apart on decoding. 8980 8986 Sometimes it can be useful to define a CHOICE that has multiple types … … 8993 8999 provides this functionality. When called, it leaves a notice for the next 8994 9000 call to <function>odr_choice()</function> to be called on the decoding 8995 stream <literal>o</literal> that only the <literal>arm</literal> entry with9001 stream <literal>o</literal>, that only the <literal>arm</literal> entry with 8996 9002 a <literal>which</literal> field equal to <literal>what</literal> 8997 9003 should be tried. … … 9163 9169 The <function>cs_create</function> function returns a null-pointer 9164 9170 if a system error occurs. 9165 The <literal>blocking</literal> parameter should be oneif9166 you wish the association to operate in blocking mode, zerootherwise.9171 The <literal>blocking</literal> parameter should be '1' if 9172 you wish the association to operate in blocking mode, and '0' otherwise. 9167 9173 The <literal>protocol</literal> field should be 9168 9174 <literal>PROTO_Z3950</literal> or <literal>PROTO_HTTP</literal>. … … 9201 9207 and <literal>len</literal>, until the buffer has been transmitted. 9202 9208 When a full buffer has been sent, the function will return 0 for 9203 success. -1 indicates an error condition (see below).9209 success. The return value -1 indicates an error condition (see below). 9204 9210 </para> 9205 9211 <synopsis> … … 9217 9223 calling 9218 9224 <function>cs_get</function> 9219 for the fi st time, the buffer can be initialized to the null pointer,9220 and the length should also be set to 0 -cs_get will perform a9225 for the first time, the buffer can be initialized to the null pointer, 9226 and the length should also be set to 0 (cs_get will perform a 9221 9227 <function>malloc(2)</function> 9222 on the buffer for you . When a full buffer has been read, the size of9223 the package is returned (which will always be greater than 1). -19224 indicates an error condition.9228 on the buffer for you). When a full buffer has been read, the size of 9229 the package is returned (which will always be greater than 1). 9230 The return value -1 indicates an error condition. 9225 9231 </para> 9226 9232 <para> … … 9325 9331 </synopsis> 9326 9332 <para> 9327 Returns the file descriptor of the association. Use this when9333 returns the file descriptor of the association. Use this when 9328 9334 file-level operations on the endpoint are required 9329 9335 (<function>select(2)</function> operations, specifically). … … 9411 9417 <para> 9412 9418 You may need to use this function with some care if your 9413 name server service is slow or unreliable 9419 name server service is slow or unreliable. 9414 9420 </para> 9415 9421 </note> … … 9471 9477 is similar to that described for <function>cs_straddr</function> 9472 9478 but with a prefix denoting the &comstack; type. Prefixes supported 9473 are <literal>tcp:</literal> ,<literal>unix:</literal> and9474 <literal>ssl:</literal> for TCP/IP ,UNIX and SSL respectively.9479 are <literal>tcp:</literal> and <literal>unix:</literal> and 9480 <literal>ssl:</literal> for TCP/IP and UNIX and SSL respectively. 9475 9481 If no prefix is given, then TCP/IP is used. 9476 9482 The <parameter>blocking</parameter> is passed to … … 9489 9495 </synopsis> 9490 9496 Returns the SSL handle, <literal>SSL *</literal> for comstack. If comstack 9491 is not of type SSL, NULL is returned.9497 is not of type SSL, then NULL is returned. 9492 9498 </para> 9493 9499 <para> … … 9539 9545 <para> 9540 9546 You can the textual representation of the error code 9541 by using <function>cs_errmsg</function> -which9542 works like <function>strerror(3)</function> 9547 by using <function>cs_errmsg</function>, which 9548 works like <function>strerror(3)</function>. 9543 9549 </para> 9544 9550 <synopsis> … … 9546 9552 </synopsis> 9547 9553 <para> 9548 It is also possible to get straight to the textual represen ataion9549 without the error code by using9554 It is also possible to get straight to the textual representation 9555 without the error code, by using 9550 9556 <function>cs_strerror</function>. 9551 9557 </para> -
yaz/trunk/fuentes/doc/common/Makefile.in
r255 r265 172 172 EXEEXT = @EXEEXT@ 173 173 FGREP = @FGREP@ 174 GCRYPT_LIBS = @GCRYPT_LIBS@175 174 GREP = @GREP@ 176 175 HIREDIS_LIBS = @HIREDIS_LIBS@ … … 274 273 libdir = @libdir@ 275 274 libexecdir = @libexecdir@ 276 libgcrypt = @libgcrypt@277 275 localedir = @localedir@ 278 276 localstatedir = @localstatedir@ -
yaz/trunk/fuentes/doc/common/common.ent
r255 r265 143 143 <!ENTITY url.marcxml "http://www.loc.gov/standards/marcxml/"> 144 144 <!ENTITY url.marcxchange "http://www.loc.gov/standards/iso25577/"> 145 <!ENTITY url.ill "http://www.nlc-bnc.ca/iso/ill/ ">145 <!ENTITY url.ill "http://www.nlc-bnc.ca/iso/ill/standard.htm"> 146 146 <!ENTITY url.ber.over.tcpip "http://www.faqs.org/rfcs/rfc1729.html"> 147 147 <!ENTITY url.http "http://www.w3.org/Protocols/"> … … 163 163 <!ENTITY url.libxslt "http://xmlsoft.org/XSLT/"> 164 164 <!ENTITY url.libxml2.download.windows "http://ftp.indexdata.dk/pub/support/windows/"> 165 <!ENTITY url.indexdata.support "http://ftp.indexdata.dk/pub/support/"> 166 <!ENTITY url.indexdata.support.windows "http://ftp.indexdata.dk/pub/support/windows/"> 165 167 <!ENTITY url.expat "http://expat.sourceforge.net/"> 166 168 <!ENTITY url.autoconf "http://www.gnu.org/software/autoconf/"> -
yaz/trunk/fuentes/doc/comstack.addresses.html
r255 r265 41 41 is similar to that described for <code class="function">cs_straddr</code> 42 42 but with a prefix denoting the <acronym class="acronym">COMSTACK</acronym> type. Prefixes supported 43 are <code class="literal">tcp:</code> ,<code class="literal">unix:</code> and44 <code class="literal">ssl:</code> for TCP/IP ,UNIX and SSL respectively.43 are <code class="literal">tcp:</code> and <code class="literal">unix:</code> and 44 <code class="literal">ssl:</code> for TCP/IP and UNIX and SSL respectively. 45 45 If no prefix is given, then TCP/IP is used. 46 46 The <em class="parameter"><code>blocking</code></em> is passed to -
yaz/trunk/fuentes/doc/comstack.common.html
r255 r265 14 14 The <code class="function">cs_create</code> function returns a null-pointer 15 15 if a system error occurs. 16 The <code class="literal">blocking</code> parameter should be oneif17 you wish the association to operate in blocking mode, zerootherwise.16 The <code class="literal">blocking</code> parameter should be '1' if 17 you wish the association to operate in blocking mode, and '0' otherwise. 18 18 The <code class="literal">protocol</code> field should be 19 19 <code class="literal">PROTO_Z3950</code> or <code class="literal">PROTO_HTTP</code>. … … 42 42 and <code class="literal">len</code>, until the buffer has been transmitted. 43 43 When a full buffer has been sent, the function will return 0 for 44 success. -1 indicates an error condition (see below).44 success. The return value -1 indicates an error condition (see below). 45 45 </p><pre class="synopsis"> 46 46 int cs_get(COMSTACK handle, char **buf, int *size); … … 56 56 calling 57 57 <code class="function">cs_get</code> 58 for the fi st time, the buffer can be initialized to the null pointer,59 and the length should also be set to 0 -cs_get will perform a58 for the first time, the buffer can be initialized to the null pointer, 59 and the length should also be set to 0 (cs_get will perform a 60 60 <code class="function">malloc(2)</code> 61 on the buffer for you . When a full buffer has been read, the size of62 the package is returned (which will always be greater than 1). -163 indicates an error condition.61 on the buffer for you). When a full buffer has been read, the size of 62 the package is returned (which will always be greater than 1). 63 The return value -1 indicates an error condition. 64 64 </p><p> 65 65 See also the <code class="function">cs_more()</code> function below. … … 129 129 int cs_fileno(COMSTACK h); 130 130 </pre><p> 131 Returns the file descriptor of the association. Use this when131 returns the file descriptor of the association. Use this when 132 132 file-level operations on the endpoint are required 133 133 (<code class="function">select(2)</code> operations, specifically). -
yaz/trunk/fuentes/doc/comstack.diagnostics.html
r255 r265 15 15 </pre><p> 16 16 You can the textual representation of the error code 17 by using <code class="function">cs_errmsg</code> -which18 works like <code class="function">strerror(3)</code> 17 by using <code class="function">cs_errmsg</code>, which 18 works like <code class="function">strerror(3)</code>. 19 19 </p><pre class="synopsis"> 20 20 const char *cs_errmsg(int n); 21 21 </pre><p> 22 It is also possible to get straight to the textual represen ataion23 without the error code by using22 It is also possible to get straight to the textual representation 23 without the error code, by using 24 24 <code class="function">cs_strerror</code>. 25 25 </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-201 5">16 <!ENTITY copyright-year "1995-2016"> 17 17 <!ENTITY soversion "5"> -
yaz/trunk/fuentes/doc/facets.html
r255 r265 1 1 <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> 2 YAZ supports facets for inSolr, SRU 2.0 and Z39.50 protocols.2 YAZ supports facets in the Solr, SRU 2.0 and Z39.50 protocols. 3 3 </p><p> 4 4 Like Type-1/RPN, YAZ supports a string notation for specifying … … 6 6 <code class="function">yaz_pqf_parse_facet_list</code>. 7 7 </p><p> 8 For ZOOM C the facets are given by option "facets" 9 For yaz-client it is used for the facetscommand.8 For ZOOM C the facets are given by option "facets". 9 For yaz-client it is used for the 'facets' command. 10 10 </p><p> 11 11 The grammar of this specification is as follows: … … 19 19 </p></div><p> 20 20 The notation is inspired by PQF. The string following '@attr' 21 m aynot include blanks and is of the form21 must not include blanks and is of the form 22 22 <em class="replaceable"><code>type</code></em><code class="literal">=</code><em class="replaceable"><code>value</code></em>, 23 23 where <em class="replaceable"><code>type</code></em> is an integer and … … 26 26 The Facets specification is not Bib-1. The following types apply: 27 27 </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> 28 Field-name. This is often a string, e g"Author", "Year", etc.28 Field-name. This is often a string, e.g. "Author", "Year", etc. 29 29 </td></tr><tr><td>2</td><td> 30 30 Sort order. Value should be an integer. -
yaz/trunk/fuentes/doc/gfs-options.xml
r255 r265 35 35 <listitem><para> 36 36 Operate the server in threaded mode. The server creates a thread 37 for each connection rather than afork a process. Only available38 on UNIX systems that offer sPOSIX threads.37 for each connection rather than fork a process. Only available 38 on UNIX systems that offer POSIX threads. 39 39 </para></listitem> 40 40 </varlistentry> … … 100 100 <term><literal>-w </literal><replaceable>dir</replaceable></term> 101 101 <listitem><para> 102 The server changes to this directory duringbefore listening103 onincoming connections. This option is useful102 The server changes to this directory before listening 103 to incoming connections. This option is useful 104 104 when the server is operating from the <application>inetd</application> 105 105 daemon (see <literal>-i</literal>). … … 110 110 </term> 111 111 <listitem><para> 112 Specifies that the server should write its Process ID to 112 Specifies that the server should write its Process ID to the 113 113 file given by <replaceable>pidfile</replaceable>. 114 114 A typical location would be <filename>/var/run/yaz-ztest.pid</filename>. -
yaz/trunk/fuentes/doc/gfs-virtual.xml
r255 r265 23 23 <note> 24 24 <para> 25 Not all Z39.50 clients allow sthe VHOST information to be set.26 For those the selection of the backend must rely on the25 Not all Z39.50 clients allow the VHOST information to be set. 26 For those, the selection of the backend must rely on the 27 27 TCP/IP information alone (port and address). 28 28 </para> … … 56 56 <listitem> 57 57 <para> 58 identifier for this listener. This may be referred to from58 Identifier for this listener. This may be referred to from 59 59 server sections. 60 60 </para> … … 108 108 <para> 109 109 Specifies a working directory for this backend server. If 110 specifi d, the YAZ fronend changes current working directory110 specified, the YAZ frontend changes current working directory 111 111 to this directory whenever a backend of this type is 112 112 started (backend handler bend_start), stopped (backend handler hand_stop) … … 130 130 <para> 131 131 Specifies a filename that includes CQL to RPN conversion for this 132 backend server. See &reference-tools-cql-map; 132 backend server. See &reference-tools-cql-map;. 133 133 If given, the backend server will only "see" a Type-1/RPN query. 134 134 </para> … … 140 140 <para> 141 141 Specifies a filename that includes CCL to RPN conversion for this 142 backend server. See &reference-tools-ccl-qualifiers; 142 backend server. See &reference-tools-ccl-qualifiers;. 143 143 If given, the backend server will only "see" a Type-1/RPN query. 144 144 </para> … … 150 150 <para> 151 151 Specifies the stylesheet reference to be part of SRU HTTP responses 152 when the client does not specify one. If n either this is given, nor153 the client specifies one,no stylesheet reference is part of the152 when the client does not specify one. If none is given, then if 153 the client does not specify one, then no stylesheet reference is part of the 154 154 SRU HTTP response. 155 155 </para> … … 171 171 <para> 172 172 Specifies a path for local file access using HTTP. All URLs with 173 a leading prefix (/ ex luded) that matches the value of docpath173 a leading prefix (/ excluded) that matches the value of <literal>docpath</literal> 174 174 are used for file access. For example, if the server is to offer 175 175 access in directory <literal>xsl</literal>, the docpath would be 176 176 <literal>xsl</literal> and all URLs of the form 177 <literal>http://host/ exl</literal> will result in a local file access.177 <literal>http://host/xsl</literal> will result in a local file access. 178 178 </para> 179 179 </listitem> … … 185 185 Specifies SRW/SRU ZeeRex content for this server. Copied verbatim 186 186 to the client. As things are now, some of the Explain content 187 see em redundant because host information, etc. is also stored187 seem redundant because host information, etc. is also stored 188 188 elsewhere. 189 189 </para> … … 195 195 <para> 196 196 Specifies maximum record size/message size, in bytes. This 197 value also serve rs asmaximum size of <emphasis>incoming</emphasis>197 value also serves as the maximum size of <emphasis>incoming</emphasis> 198 198 packages (for Record Updates etc). It's the same value as that 199 199 given by the <literal>-k</literal> option. … … 205 205 <listitem> 206 206 <para> 207 Enables the retrieval facility supportingconversions and207 Enables the retrieval facility to support conversions and 208 208 specifications of record formats/types. 209 209 See <xref linkend="tools.retrieval"/> for … … 260 260 <literal>"server2"</literal> is reached by the two listeners specified. 261 261 In order to distinguish between the two, a virtual host has 262 been specified for each ofserver in the <literal>host</literal>262 been specified for each server in the <literal>host</literal> 263 263 elements. 264 264 </para> -
yaz/trunk/fuentes/doc/index.html
r255 r265 1 <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.1 4.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-2015Index Data</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>1 <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> 2 2 This document is the programmer's guide and reference to the YAZ 3 package version 5.1 4.3. YAZ is a compact toolkit that provides3 package version 5.15.2. YAZ is a compact toolkit that provides 4 4 access to the Z39.50 and SRU/Solr protocols, as well as a set of 5 5 higher-level tools for implementing the server and client … … 9 9 </p><p> 10 10 <span class="inlinemediaobject"><img src="common/id.png"></span> 11 </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#id p46954032">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"> — Z39.50/SRU client for implementors</span></dt><dt><span class="refentrytitle"><a href="yaz-ztest.html">yaz-ztest</a></span><span class="refpurpose"> — Z39.50/SRU Test Server</span></dt><dt><span class="refentrytitle"><a href="yaz-config.html">yaz-config</a></span><span class="refpurpose"> — Script to get information about YAZ.</span></dt><dt><span class="refentrytitle"><a href="yaz.html">yaz</a></span><span class="refpurpose"> — Z39.50 toolkit.</span></dt><dt><span class="refentrytitle"><a href="zoomsh.html">zoomsh</a></span><span class="refpurpose"> — ZOOM shell</span></dt><dt><span class="refentrytitle"><a href="yaz-asncomp.html">yaz-asncomp</a></span><span class="refpurpose"> — YAZ ASN.1 compiler</span></dt><dt><span class="refentrytitle"><a href="yaz-marcdump.html">yaz-marcdump</a></span><span class="refpurpose"> — MARC record dump utility</span></dt><dt><span class="refentrytitle"><a href="yaz-iconv.html">yaz-iconv</a></span><span class="refpurpose"> — YAZ Character set conversion utility</span></dt><dt><span class="refentrytitle"><a href="yaz-log.html">yaz-log</a></span><span class="refpurpose"> — 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"> — ILL client</span></dt><dt><span class="refentrytitle"><a href="yaz-icu.html">yaz-icu</a></span><span class="refpurpose"> — YAZ ICU utility</span></dt><dt><span class="refentrytitle"><a href="yaz-url.html">yaz-url</a></span><span class="refpurpose"> — YAZ URL fetch utility</span></dt><dt><span class="refentrytitle"><a href="bib1.html">Bib-1 Attribute Set</a></span><span class="refpurpose"> — Bib-1 Attribute Set</span></dt><dt><span class="refentrytitle"><a href="yaz-json-parse.html">yaz-json-parse</a></span><span class="refpurpose"> — 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>11 </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"> — Z39.50/SRU client for implementors</span></dt><dt><span class="refentrytitle"><a href="yaz-ztest.html">yaz-ztest</a></span><span class="refpurpose"> — Z39.50/SRU Test Server</span></dt><dt><span class="refentrytitle"><a href="yaz-config.html">yaz-config</a></span><span class="refpurpose"> — Script to get information about YAZ.</span></dt><dt><span class="refentrytitle"><a href="yaz.html">yaz</a></span><span class="refpurpose"> — Z39.50 toolkit.</span></dt><dt><span class="refentrytitle"><a href="zoomsh.html">zoomsh</a></span><span class="refpurpose"> — ZOOM shell</span></dt><dt><span class="refentrytitle"><a href="yaz-asncomp.html">yaz-asncomp</a></span><span class="refpurpose"> — YAZ ASN.1 compiler</span></dt><dt><span class="refentrytitle"><a href="yaz-marcdump.html">yaz-marcdump</a></span><span class="refpurpose"> — MARC record dump utility</span></dt><dt><span class="refentrytitle"><a href="yaz-iconv.html">yaz-iconv</a></span><span class="refpurpose"> — YAZ Character set conversion utility</span></dt><dt><span class="refentrytitle"><a href="yaz-log.html">yaz-log</a></span><span class="refpurpose"> — 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"> — ILL client</span></dt><dt><span class="refentrytitle"><a href="yaz-icu.html">yaz-icu</a></span><span class="refpurpose"> — YAZ ICU utility</span></dt><dt><span class="refentrytitle"><a href="yaz-url.html">yaz-url</a></span><span class="refpurpose"> — YAZ URL fetch utility</span></dt><dt><span class="refentrytitle"><a href="bib1.html">Bib-1 Attribute Set</a></span><span class="refpurpose"> — Bib-1 Attribute Set</span></dt><dt><span class="refentrytitle"><a href="yaz-json-parse.html">yaz-json-parse</a></span><span class="refpurpose"> — 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 14 14 <a class="ulink" href="http://www.freebsd.org/" target="_top">FreeBSD (i386)</a>, 15 15 <a class="ulink" href="http://www.apple.com/macosx/" target="_top">MAC OSX</a>, 16 <a class="ulink" href="http://www.oracle.com/solaris" target="_top">Solaris</a>, 17 Windows 7, Windows XP. 16 Windows 10. 18 17 </p><p> 19 Some versions have be known to work on HP/UX,18 Some versions have be known to work on Windows XP, Solaris, HP/UX, 20 19 DEC Unix, <a class="ulink" href="http://www.netbsd.org" target="_top">NetBSD</a>, 21 20 <a class="ulink" href="http://www.openbsd.org" target="_top">OpenBSD</a>, -
yaz/trunk/fuentes/doc/installation.unix.html
r255 r265 23 23 <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> 24 24 </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> 25 Note that if your system doesn't have a native ANSI C compiler, you may 26 have to acquire one separately. We recommend 27 <a class="ulink" href="http://gcc.gnu.org" target="_top">GCC</a>. 25 You can choose to compile YAZ from official tar releases from 26 <a class="ulink" href="http://ftp.indexdata.com/pub/yaz/" target="_top">http://ftp.indexdata.com/pub/yaz/</a> 27 or clone it via Github 28 <a class="ulink" href="https://github.com/indexdata/yaz.git" target="_top">https://github.com/indexdata/yaz.git</a>. 28 29 </p><p> 29 30 If you wish to use character set conversion facilities in YAZ or if you … … 52 53 <a class="ulink" href="http://www.gnu.org/software/libtool/" target="_top">Libtool</a> 53 54 are used to generate Makefiles and configure YAZ for the system. 54 You do <span class="emphasis"><em>not</em></span> these tools unless you're using the55 You do <span class="emphasis"><em>not</em></span> need these tools unless you're using the 55 56 Git version of YAZ. 56 57 </p><p> … … 62 63 written in <a class="ulink" href="http://www.tcl.tk/" target="_top">Tcl</a>. 63 64 But as for Bison you do not need it unless you're using Git 64 version of YAZ or you're using the compiler to buil town codecs65 version of YAZ or you're using the compiler to build your own codecs 65 66 for private ASN.1. 66 67 </p><p> 67 Generally it should be sufficient to run configure without options, 68 like this: 68 If you are checking out from Git, run: 69 </p><pre class="screen"> 70 ./buildconf.sh 71 </pre><p> 72 This will create the <code class="filename">configure</code> script and Makefiles. 73 </p><p> 74 The next step is always: 69 75 </p><pre class="screen"> 70 76 ./configure … … 121 127 search for iconv on the system. Use this option if it 122 128 doesn't find iconv. Alternatively, 123 <code class="literal">--without-iconv</code>, can be use tto force YAZ129 <code class="literal">--without-iconv</code>, can be used to force YAZ 124 130 not to use iconv. 125 131 </p></dd><dt><span class="term"> … … 130 136 Use this option if you want XSLT and XML support. 131 137 By default, configure will 132 search for libxslt on the system. Use this option if it138 search for libxslt on the system. Use this option if 133 139 libxslt is not found automatically. Alternatively, 134 140 <code class="literal">--without-xslt</code>, can be used to force YAZ … … 141 147 Use this option if you want YAZ to use XML and support SRU/Solr. 142 148 By default, configure will 143 search for libxml2 on the system. Use this option if it149 search for libxml2 on the system. Use this option if 144 150 libxml2 is not found automatically. Alternatively, 145 151 <code class="literal">--without-xml2</code>, can be used to force YAZ … … 161 167 <span class="application">icu-config</span> will be used if found. 162 168 </p></dd><dt><span class="term"> 163 <code class="literal">--with-libgcrypt</code>[=<em class="replaceable"><code>prefix</code></em>]164 </span></dt><dd><p>YAZ will be linked with165 <a class="ulink" href="http://www.gnu.org/software/libgcrypt/" target="_top">Libgcrypt</a> in the prefix if given.166 If prefix is not given, the libraries exposed by the script167 <span class="application">libgcrypt-config</span> will be used if found.168 </p></dd><dt><span class="term">169 169 <code class="literal">--with-memcached</code> 170 170 </span></dt><dd><p>YAZ will be linked with 171 171 <a class="ulink" href="http://libmemcached.org/" target="_top">libMemcached</a> to allow 172 172 for result-set caching for ZOOM. 173 The prefix can not be given. Note that YAZ will only search 174 for libMemcached if Libgcrypt is also enabled. 173 The prefix can not be given. 175 174 Note that 0.40 of libmemcached is required. 176 175 </p></dd><dt><span class="term"> … … 179 178 to allow for result-set caching for ZOOM on a 180 179 <a class="ulink" href="http://redis.io/" target="_top">redis</a> server. 181 The prefix can not be given. Note that YAZ will only search 182 for hiredis if Libgcrypt is also enabled. 180 The prefix can not be given. 183 181 </p></dd></dl></div><p> 184 182 </p><p> … … 253 251 applications using the YAZ toolkit. 254 252 If you're used to Makefiles this shouldn't be hard. As for 255 other libraries you have used before, you haveto set a proper include253 other libraries you have used before, you need to set a proper include 256 254 path for your C/C++ compiler and specify the location of 257 255 YAZ libraries. You can do it by hand, but generally we suggest -
yaz/trunk/fuentes/doc/installation.win32.html
r255 r265 1 1 <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 2 2 an installer from 3 <a class="ulink" href="http://ftp.indexdata.com/pub/yaz/win32/" target="_top">here</a>. 3 <a class="ulink" href="http://ftp.indexdata.com/pub/yaz/win32/" target="_top"> 4 Index Data's Windows support area 5 </a>. 4 6 The installer comes with source too - in case you wish to 5 7 compile YAZ with different compiler options, etc. … … 8 10 with <a class="ulink" href="http://www.visualstudio.com" target="_top"> 9 11 Microsoft Visual Studio</a>. It has been tested with 10 Microsoft Visual Studio 201 3.12 Microsoft Visual Studio 2015. 11 13 </p><p> 12 14 Start a command prompt and switch the sub directory … … 38 40 (<code class="filename">cql.y</code>). 39 41 </p><p> 40 A Windows version of GNU Bison is part of 41 <a class="ulink" href="http://msysgit.github.io/" target="_top">Git for Windows</a>. 42 A Windows version of GNU Bison can be fetched from here: 43 <a class="ulink" href="http://ftp.indexdata.dk/pub/support/windows/bison-2.4.1-setup.exe" target="_top"> 44 Index Data's Windows support area 45 </a>. 42 46 </p></dd><dt><span class="term"><code class="literal">HAVE_ICONV</code>, 43 47 <code class="literal">ICONV_DIR</code></span></dt><dd><p> … … 63 67 <a class="ulink" href="http://xmlsoft.org/XSLT/" target="_top">libxslt</a> source directory. 64 68 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 65 libxslt depends libxml2.69 libxslt depends on libxml2. 66 70 </p></div></dd><dt><span class="term"><code class="literal">HAVE_ICU</code>, 67 71 <code class="literal">ICU_DIR</code></span></dt><dd><p> … … 71 75 <code class="literal">ICU_DIR</code> to the 72 76 <a class="ulink" href="http://www.icu-project.org/" target="_top">ICU</a> source directory. 77 </p><p> 78 Pre-compiled ICU libraries for various versions of Visual Studio 79 can be found 80 <a class="ulink" href="http://www.npcglib.org/~stathis/blog/precompiled-icu/" target="_top"> 81 here 82 </a> or from Index Data's <a class="ulink" href="http://ftp.indexdata.dk/pub/support/windows/" target="_top">Windows support site</a>. 73 83 </p></dd></dl></div><p> 74 84 </p><p> … … 124 134 </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 125 135 is enabled for YAZ. Only if ICU is available this program is 126 buil d.136 built. 127 137 </p></dd><dt><span class="term"><code class="filename">bin/zoomsh.exe</code></span></dt><dd><p> 128 138 Simple console application implemented on top of the … … 132 142 </p></dd><dt><span class="term"><code class="filename">bin/zoomtst1.exe</code>, 133 143 <code class="filename">bin/zoomtst2.exe</code>, ..</span></dt><dd><p> 134 Several small applications that demonstrate sthe ZOOM API.144 Several small applications that demonstrate the ZOOM API. 135 145 </p></dd></dl></div><p> 136 146 </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 3 3 toolkit offers several different levels of access to the 4 4 <a class="ulink" href="http://www.loc.gov/z3950/agency/" target="_top">ISO23950/Z39.50</a>, 5 <a class="ulink" href="http://www.nlc-bnc.ca/iso/ill/ " target="_top">ILL</a> and5 <a class="ulink" href="http://www.nlc-bnc.ca/iso/ill/standard.htm" target="_top">ILL</a> and 6 6 <a class="ulink" href="http://www.loc.gov/standards/sru/" target="_top">SRU</a> 7 7 protocols. … … 21 21 level APIs of YAZ. 22 22 </p><p> 23 The YAZ toolkit modules isshown in figure <a class="xref" href="introduction.api.html#yaz.layer" title="Figure 1.1. YAZ layers">Figure 1.1, “YAZ layers”</a>.23 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, “YAZ layers”</a>. 24 24 </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> 25 25 There are four layers. … … 66 66 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 67 67 If you are using the premade definitions of the Z39.50 ASN.1 module, and you 68 are not adding new protocol of your own, the only parts of <acronym class="acronym">ODR</acronym> that you68 are not adding a new protocol of your own, the only parts of <acronym class="acronym">ODR</acronym> that you 69 69 need to worry about are documented in 70 70 <a class="xref" href="odr.use.html" title="2. Using ODR">Section 2, “Using ODR”</a>. -
yaz/trunk/fuentes/doc/introduction.html
r255 r265 14 14 </p></li><li class="listitem"><p> 15 15 Includes BER encoders/decoders for the 16 <a class="ulink" href="http://www.nlc-bnc.ca/iso/ill/ " target="_top">ISO ILL</a>16 <a class="ulink" href="http://www.nlc-bnc.ca/iso/ill/standard.htm" target="_top">ISO ILL</a> 17 17 protocol. 18 18 </p></li><li class="listitem"><p> 19 19 Supports 20 <a class="ulink" href="http://lucene.apache.org/solr/" target="_top"> Solr</a> Web Service version 1.4.x20 <a class="ulink" href="http://lucene.apache.org/solr/" target="_top">Apache Solr</a> Web Service version 1.4.x 21 21 (client side only) 22 22 </p></li><li class="listitem"><p> … … 51 51 </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> 52 52 Most implementors only need to read a fraction of the 53 material in thi emanual, so a quick walkthrough of the chapters53 material in this manual, so a quick walkthrough of the chapters 54 54 is in order. 55 55 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> 56 56 <a class="xref" href="installation.html" title="Chapter 2. Compilation and Installation">Chapter 2, <i>Compilation and Installation</i></a> contains installation 57 instructions for YAZ. You don't need readingthis57 instructions for YAZ. You don't need to read this 58 58 if you expect to download YAZ binaries. 59 59 However, the chapter contains information about how … … 62 62 </p></li><li class="listitem"><p> 63 63 <a class="xref" href="zoom.html" title="Chapter 3. ZOOM">Chapter 3, <i>ZOOM</i></a> describes the ZOOM API of YAZ. 64 This is definitely worth a readif you wish to develop a Z39.50/SRU64 This is definitely worth reading if you wish to develop a Z39.50/SRU 65 65 client. 66 66 </p></li><li class="listitem"><p> … … 70 70 </p></li><li class="listitem"><p> 71 71 <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 72 client. If you're developer and wish to test your server72 client. If you're a developer and wish to test your server 73 73 or a server from another party, you might find this chapter 74 74 useful. … … 91 91 ODR module which is the work horse that encodes and decodes 92 92 BER packages. Implementors using ZOOM only, do <span class="emphasis"><em>not</em></span> 93 need readingthis.93 need to read this. 94 94 Most other Z39.50 implementors only need to read the first two 95 95 sections (<a class="xref" href="odr.html#odr.introduction" title="1. Introduction">Section 1, “Introduction”</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-201 5Index 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 3 3 <refentryinfo> 4 4 <productname class="trade">YAZ</productname> 5 <productnumber>5.1 4.3</productnumber>6 < info><orgname>Index Data</orgname></info>5 <productnumber>5.15.2</productnumber> 6 <orgname>Index Data</orgname> 7 7 </refentryinfo> 8 8 … … 82 82 <listitem><para> 83 83 If specified, logging of protocol packages will be appended 84 file given. If <replaceable>filename</replaceable> is84 to the file given. If <replaceable>filename</replaceable> is 85 85 specified as <literal moreinfo="none">-</literal>, the output is written 86 86 to <literal moreinfo="none">stdout</literal>. … … 142 142 connect to a proxy on the address and port given. 143 143 The actual target will be specified as part of the InitRequest 144 to inform the proxy about actual target.144 to inform the proxy about the actual target. 145 145 </para></listitem> 146 146 </varlistentry> … … 248 248 <listitem> 249 249 <para>Sets the name(s) of the database(s) to search. One or more 250 databases may be specified separated by blanks. This commandsoverrides250 databases may be specified, separated by blanks. This command overrides 251 251 the database given in <replaceable>zurl</replaceable>. 252 252 </para> … … 261 261 position given by 262 262 <replaceable>start</replaceable> 263 a number of records given by <replaceable>number</replaceable>. If263 and a number of records given by <replaceable>number</replaceable>. If 264 264 <replaceable>start</replaceable> is not given, then the client 265 will fetch from position of the last retrieved record plus 1. If265 will fetch from the position of the last retrieved record plus 1. If 266 266 <replaceable>number</replaceable> is not given, then one record will 267 267 be fetched at a time. … … 305 305 <simpara> 306 306 Sets preferred position for scan. This value 307 is used in next scan. By defaultposition is 1.307 is used in the next scan. By default, position is 1. 308 308 </simpara> 309 309 </listitem> … … 324 324 <listitem> 325 325 <simpara> 326 Set step-size for scan. This value is used in next scan326 Set step-size for scan. This value is used in the next scan 327 327 sent to the target. By default step-size is 0. 328 328 </simpara> … … 368 368 </term> 369 369 <listitem> 370 <para>Sets up a authentication string if a server requires370 <para>Sets up an authentication string if a server requires 371 371 authentication (v2 OpenStyle). The authentication string is first 372 372 sent to the server when the … … 439 439 </term> 440 440 <listitem> 441 <para>Sets the number of records should be returned if the441 <para>Sets the number of records that should be returned if the 442 442 number of records in the result set is between the values of 443 443 <literal moreinfo="none">lslb</literal> and <literal moreinfo="none">ssub</literal>. … … 495 495 <listitem> 496 496 <para>Sets the element set name for the records. Many targets support 497 element sets areB (for brief) and F (for full).497 element sets B (for brief) and F (for full). 498 498 </para> 499 499 </listitem> … … 519 519 <literal moreinfo="none">cql</literal> for CQL (Type-104 search with CQL OID), 520 520 <literal moreinfo="none">ccl2rpn</literal> for 521 <link linkend="CCL">CCL</link> to RPN conversion (Type-1 Query) .521 <link linkend="CCL">CCL</link> to RPN conversion (Type-1 Query), 522 522 <literal moreinfo="none">cql2rpn</literal> for 523 523 CQL to RPN conversion (Type-1 Query). … … 570 570 "<", then the following characters are treated as a filename 571 571 with the records to be updated. Otherwise doc is treated as 572 a document itself. The doc may also be qu ited in double quotes.572 a document itself. The doc may also be quoted in double quotes. 573 573 If doc is omitted, the last received record (as part of present 574 574 response or piggybacked search response) is used for the update. … … 583 583 <listitem> 584 584 <para>Executes list of commands from 585 file <replaceable>filename</replaceable>, just like sourceon585 file <replaceable>filename</replaceable>, just like 'source' on 586 586 most UNIX shells. A single dot (<literal moreinfo="none">.</literal>) can be used 587 587 as an alternative. … … 632 632 </term> 633 633 <listitem> 634 <para>Specifies whether YAZ client automatically reconnect if634 <para>Specifies whether YAZ client automatically reconnects if the 635 635 target closes connection (Z39.50 only). 636 636 </para> … … 649 649 <para>Specifies whether YAZ client should wait for 650 650 response protocol packages after a request. 651 By default YAZ client waits ( on) for response packages immediately651 By default YAZ client waits (<literal moreinfo="none">on</literal>) for response packages immediately 652 652 after a command (find, show) has been issued. If <literal moreinfo="none">off</literal> 653 653 is used, YAZ client does not attempt to receive packages automatically. … … 715 715 </para> 716 716 <para> 717 If <replaceable>marc harset</replaceable> is given, it specifies name717 If <replaceable>marccharset</replaceable> is given, it specifies name 718 718 of the character set of retrieved MARC records from server. See 719 also <literal moreinfo="none">marc harset</literal> command.719 also <literal moreinfo="none">marccharset</literal> command. 720 720 </para> 721 721 <note> … … 828 828 name for the OID, <replaceable>class</replaceable> is the 829 829 class, and <replaceable>OID</replaceable> is the raw OID in 830 dot notation. Class is one <literal moreinfo="none">appctx</literal>,830 dot notation. Class is one of: <literal moreinfo="none">appctx</literal>, 831 831 <literal moreinfo="none">absyn</literal>, <literal moreinfo="none">attet</literal>, 832 832 <literal moreinfo="none">transyn</literal>, <literal moreinfo="none">diagset</literal>, … … 954 954 f "donald knuth" 955 955 </screen> 956 In those queries no attributes wasspecified.956 In those queries, no attributes were specified. 957 957 This leaves it up to the server what fields to search but 958 most servers will search in all fields. Some servers do esnot958 most servers will search in all fields. Some servers do not 959 959 support this feature though, and require that some attributes 960 960 are defined. To add one attribute you could do: … … 1004 1004 <refentryinfo> 1005 1005 <productname class="trade">YAZ</productname> 1006 <productnumber>5.1 4.3</productnumber>1007 < info><orgname>Index Data</orgname></info>1006 <productnumber>5.15.2</productnumber> 1007 <orgname>Index Data</orgname> 1008 1008 </refentryinfo> 1009 1009 … … 1076 1076 </para> 1077 1077 <para> 1078 For UNIX local socket the address is the filename of the local socket.1078 For UNIX local socket, the address is the filename of the local socket. 1079 1079 </para> 1080 1080 </refsect1> … … 1117 1117 <listitem><para> 1118 1118 Operate the server in threaded mode. The server creates a thread 1119 for each connection rather than afork a process. Only available1120 on UNIX systems that offer sPOSIX threads.1119 for each connection rather than fork a process. Only available 1120 on UNIX systems that offer POSIX threads. 1121 1121 </para></listitem> 1122 1122 </varlistentry> … … 1182 1182 <term><literal moreinfo="none">-w </literal><replaceable>dir</replaceable></term> 1183 1183 <listitem><para> 1184 The server changes to this directory duringbefore listening1185 onincoming connections. This option is useful1184 The server changes to this directory before listening 1185 to incoming connections. This option is useful 1186 1186 when the server is operating from the <application moreinfo="none">inetd</application> 1187 1187 daemon (see <literal moreinfo="none">-i</literal>). … … 1192 1192 </term> 1193 1193 <listitem><para> 1194 Specifies that the server should write its Process ID to 1194 Specifies that the server should write its Process ID to the 1195 1195 file given by <replaceable>pidfile</replaceable>. 1196 1196 A typical location would be <filename moreinfo="none">/var/run/yaz-ztest.pid</filename>. … … 1311 1311 to return any number of hits. <command moreinfo="none">yaz-ztest</command> includes 1312 1312 24 MARC records for testing. Hit counts exceeding 24 will make 1313 <command moreinfo="none">yaz-ztest</command> return the same record batch over and over. .1314 So record at position 1, 25, 49, etc .. are equivalent.1313 <command moreinfo="none">yaz-ztest</command> return the same record batch over and over. 1314 So record at position 1, 25, 49, etc. are equivalent. 1315 1315 </para> 1316 1316 <para> 1317 For XML if no element set is given or element has value "marcxml",1317 For XML, if no element set is given or element has value "marcxml", 1318 1318 MARCXML is returned (each of the 24 dummy records converted from 1319 ISO2709 to XML). For element set OP, OPAC XML is returned.1319 ISO2709 to XML). For element set OP, then OPAC XML is returned. 1320 1320 </para> 1321 1321 <para> 1322 1322 yaz-ztest may also return predefined XML records (for testing). 1323 1323 This is enabled if <literal moreinfo="none">YAZ_ZTEST_XML_FETCH</literal> environment 1324 variable is defined. A record is fetched f orm a file (one record per file).1324 variable is defined. A record is fetched from a file (one record per file). 1325 1325 The path for the filename is 1326 1326 <replaceable>F</replaceable><replaceable>E</replaceable><literal moreinfo="none">.</literal><replaceable>d</replaceable><literal moreinfo="none">.xml</literal> … … 1351 1351 value which specifies the delay in seconds. 1352 1352 Alternatively the value may be given as two floating point numbers 1353 separated by colon, which wil make <command moreinfo="none">yaz-ztest</command> perform1353 separated by colon, which will make <command moreinfo="none">yaz-ztest</command> perform 1354 1354 a random sleep between the first and second number. 1355 1355 </para> … … 1390 1390 <note> 1391 1391 <para> 1392 Not all Z39.50 clients allow sthe VHOST information to be set.1393 For those the selection of the backend must rely on the1392 Not all Z39.50 clients allow the VHOST information to be set. 1393 For those, the selection of the backend must rely on the 1394 1394 TCP/IP information alone (port and address). 1395 1395 </para> … … 1423 1423 <listitem> 1424 1424 <para> 1425 identifier for this listener. This may be referred to from1425 Identifier for this listener. This may be referred to from 1426 1426 server sections. 1427 1427 </para> … … 1475 1475 <para> 1476 1476 Specifies a working directory for this backend server. If 1477 specifi d, the YAZ fronend changes current working directory1477 specified, the YAZ frontend changes current working directory 1478 1478 to this directory whenever a backend of this type is 1479 1479 started (backend handler bend_start), stopped (backend handler hand_stop) … … 1497 1497 <para> 1498 1498 Specifies a filename that includes CQL to RPN conversion for this 1499 backend server. See <xref linkend="cql.to.rpn"/> 1499 backend server. See <xref linkend="cql.to.rpn"/>. 1500 1500 If given, the backend server will only "see" a Type-1/RPN query. 1501 1501 </para> … … 1507 1507 <para> 1508 1508 Specifies a filename that includes CCL to RPN conversion for this 1509 backend server. See <xref linkend="ccl.qualifiers"/> 1509 backend server. See <xref linkend="ccl.qualifiers"/>. 1510 1510 If given, the backend server will only "see" a Type-1/RPN query. 1511 1511 </para> … … 1517 1517 <para> 1518 1518 Specifies the stylesheet reference to be part of SRU HTTP responses 1519 when the client does not specify one. If n either this is given, nor1520 the client specifies one,no stylesheet reference is part of the1519 when the client does not specify one. If none is given, then if 1520 the client does not specify one, then no stylesheet reference is part of the 1521 1521 SRU HTTP response. 1522 1522 </para> … … 1538 1538 <para> 1539 1539 Specifies a path for local file access using HTTP. All URLs with 1540 a leading prefix (/ ex luded) that matches the value of docpath1540 a leading prefix (/ excluded) that matches the value of <literal moreinfo="none">docpath</literal> 1541 1541 are used for file access. For example, if the server is to offer 1542 1542 access in directory <literal moreinfo="none">xsl</literal>, the docpath would be 1543 1543 <literal moreinfo="none">xsl</literal> and all URLs of the form 1544 <literal moreinfo="none">http://host/ exl</literal> will result in a local file access.1544 <literal moreinfo="none">http://host/xsl</literal> will result in a local file access. 1545 1545 </para> 1546 1546 </listitem> … … 1552 1552 Specifies SRW/SRU ZeeRex content for this server. Copied verbatim 1553 1553 to the client. As things are now, some of the Explain content 1554 see em redundant because host information, etc. is also stored1554 seem redundant because host information, etc. is also stored 1555 1555 elsewhere. 1556 1556 </para> … … 1562 1562 <para> 1563 1563 Specifies maximum record size/message size, in bytes. This 1564 value also serve rs asmaximum size of <emphasis>incoming</emphasis>1564 value also serves as the maximum size of <emphasis>incoming</emphasis> 1565 1565 packages (for Record Updates etc). It's the same value as that 1566 1566 given by the <literal moreinfo="none">-k</literal> option. … … 1572 1572 <listitem> 1573 1573 <para> 1574 Enables the retrieval facility supportingconversions and1574 Enables the retrieval facility to support conversions and 1575 1575 specifications of record formats/types. 1576 1576 See <xref linkend="tools.retrieval"/> for … … 1627 1627 <literal moreinfo="none">"server2"</literal> is reached by the two listeners specified. 1628 1628 In order to distinguish between the two, a virtual host has 1629 been specified for each ofserver in the <literal moreinfo="none">host</literal>1629 been specified for each server in the <literal moreinfo="none">host</literal> 1630 1630 elements. 1631 1631 </para> … … 1673 1673 <refentryinfo> 1674 1674 <productname class="trade">YAZ</productname> 1675 <productnumber>5.1 4.3</productnumber>1676 < info><orgname>Index Data</orgname></info>1675 <productnumber>5.15.2</productnumber> 1676 <orgname>Index Data</orgname> 1677 1677 </refentryinfo> 1678 1678 … … 1780 1780 <term>-V</term> 1781 1781 <listitem><para> 1782 veturns YAZ SHA1 ID (from Git) and version.1782 Returns YAZ SHA1 ID (from Git) and version. 1783 1783 </para></listitem> 1784 1784 </varlistentry> … … 1811 1811 <refentryinfo> 1812 1812 <productname class="trade">YAZ</productname> 1813 <productnumber>5.1 4.3</productnumber>1814 < info><orgname>Index Data</orgname></info>1813 <productnumber>5.15.2</productnumber> 1814 <orgname>Index Data</orgname> 1815 1815 </refentryinfo> 1816 1816 … … 1839 1839 <refsect1><title>COPYRIGHT</title> 1840 1840 <para> 1841 Copyright © 1995-201 5Index Data.1841 Copyright © 1995-2016 Index Data. 1842 1842 </para> 1843 1843 <para> … … 1927 1927 <refentryinfo> 1928 1928 <productname class="trade">YAZ</productname> 1929 <productnumber>5.1 4.3</productnumber>1930 < info><orgname>Index Data</orgname></info>1929 <productnumber>5.15.2</productnumber> 1930 <orgname>Index Data</orgname> 1931 1931 </refentryinfo> 1932 1932 … … 2105 2105 <refentryinfo> 2106 2106 <productname class="trade">YAZ</productname> 2107 <productnumber>5.1 4.3</productnumber>2108 < info><orgname>Index Data</orgname></info>2107 <productnumber>5.15.2</productnumber> 2108 <orgname>Index Data</orgname> 2109 2109 </refentryinfo> 2110 2110 … … 2146 2146 <command moreinfo="none">yaz-asncomp</command> allows you to specify name of 2147 2147 resulting source via options. Alternatively, you can specify 2148 a DEFINI SIONS file, which provides customized output to2148 a DEFINITIONS file, which provides customized output to 2149 2149 many output files - if the ASN.1 specification file consists 2150 2150 of many modules. … … 2229 2229 traditional rules for Shell like configuration files. 2230 2230 That is # denotes the beginning of a comment. Definitions 2231 are line oriented. The definitions files usually consist sof2231 are line oriented. The definitions files usually consist of 2232 2232 a series of variable assignments of the form: 2233 2233 </para> … … 2315 2315 <replaceable>name</replaceable> in module 2316 2316 <replaceable>module</replaceable> to value. 2317 Value consists of t o or three tokens. The first token2317 Value consists of two or three tokens. The first token 2318 2318 is name of the integer in the <literal moreinfo="none">union</literal> that 2319 2319 is used as selector for the <literal moreinfo="none">union</literal> itself. … … 2349 2349 <refentryinfo> 2350 2350 <productname class="trade">YAZ</productname> 2351 <productnumber>5.1 4.3</productnumber>2352 < info><orgname>Index Data</orgname></info>2351 <productnumber>5.15.2</productnumber> 2352 <orgname>Index Data</orgname> 2353 2353 </refentryinfo> 2354 2354 … … 2448 2448 <term>-f <replaceable>from</replaceable></term> 2449 2449 <listitem><para> 2450 Specify the character set <replaceable>from</replaceable>2450 Specify the character set 2451 2451 of the input MARC record. 2452 2452 Should be used in conjunction with option <literal moreinfo="none">-t</literal>. … … 2458 2458 <term>-t <replaceable>to</replaceable></term> 2459 2459 <listitem><para> 2460 Specify the character set <replaceable>of</replaceable>2460 Specify the character set 2461 2461 of the output. 2462 2462 Should be used in conjunction with option <literal moreinfo="none">-f</literal>. … … 2482 2482 Writes a chunk of records to a separate file with prefix given, 2483 2483 i.e. splits a record batch into files with only at most 2484 "chunk" ISO2709 record per file. By default chunk is 1 (one record2484 "chunk" ISO2709 records per file. By default chunk is 1 (one record 2485 2485 per file). See option <literal moreinfo="none">-C</literal>. 2486 2486 </para></listitem> … … 2498 2498 <term>-p</term> 2499 2499 <listitem><para> 2500 Makes yaz-marcdump print srecord number and input file offset2500 Makes yaz-marcdump print record number and input file offset 2501 2501 of each record read. 2502 2502 </para></listitem> … … 2506 2506 <term>-n</term> 2507 2507 <listitem><para> 2508 MARC output is omitted so that MARC input is only checke cd.2508 MARC output is omitted so that MARC input is only checked. 2509 2509 </para></listitem> 2510 2510 </varlistentry> … … 2582 2582 <refentryinfo> 2583 2583 <productname class="trade">YAZ</productname> 2584 <productnumber>5.1 4.3</productnumber>2585 < info><orgname>Index Data</orgname></info>2584 <productnumber>5.15.2</productnumber> 2585 <orgname>Index Data</orgname> 2586 2586 </refentryinfo> 2587 2587 … … 2609 2609 <refsect1><title>DESCRIPTION</title> 2610 2610 <para> 2611 <command moreinfo="none">yaz-iconv</command> converts data in file incharacter2611 <command moreinfo="none">yaz-iconv</command> converts data in the character 2612 2612 set specified by <replaceable>from</replaceable> to output in 2613 character set as specified by <replaceable>to</replaceable>.2614 </para> 2615 <para> 2616 This <command moreinfo="none">yaz-iconv</command> utility similar to the2613 the character set as specified by <replaceable>to</replaceable>. 2614 </para> 2615 <para> 2616 This <command moreinfo="none">yaz-iconv</command> utility is similar to the 2617 2617 <command moreinfo="none">iconv</command> found on many POSIX systems (Glibc, Solaris, etc). 2618 2618 </para> … … 2659 2659 <filename moreinfo="none">yaz/yaz-iconv.h</filename> is a wrapper for the 2660 2660 library system call iconv. But YAZ' iconv utility also implements 2661 conversions on its own. The table below lists characters sets (or encodings) .2661 conversions on its own. The table below lists characters sets (or encodings) 2662 2662 that are supported by YAZ. Each character set is marked with either 2663 2663 <emphasis>encode</emphasis> or <emphasis>decode</emphasis>. If 2664 an encoding is encode-enabled YAZ may convert <emphasis>to</emphasis>2665 t o the designated encoding. If an encoding is decode-enabled, YAZ2664 an encoding is encode-enabled, YAZ may convert <emphasis>to</emphasis> 2665 the designated encoding. If an encoding is decode-enabled, YAZ 2666 2666 may convert <emphasis>from</emphasis> the designated encoding. 2667 2667 </para> … … 2680 2680 <listitem> 2681 2681 <para> 2682 Like MARC8 but withconversion prefers non-combined characters2682 Like MARC8 but conversion prefers non-combined characters 2683 2683 in the Latin-1 plane over combined characters. 2684 2684 </para> … …