Changeset 265


Ignore:
Timestamp:
Feb 2, 2016, 6:13:30 PM (3 years ago)
Author:
mabarracus
Message:

Add new source code 5.15.2

Location:
yaz/trunk
Files:
1 added
3 deleted
158 edited

Legend:

Unmodified
Added
Removed
  • yaz/trunk/fuentes/ChangeLog

    r255 r265  
     1commit 738b345708b245e67cded6d917393a80b5bd4eca
     2Author: Adam Dickmeiss <adam@indexdata.dk>
     3Date:   Mon Jan 11 13:06:41 2016 +0000
     4
     5    Version 5.15.2
     6
     7commit f43944a7ffc80bfcf8ec6a5ec1935c354d4bcac2
     8Author: Adam Dickmeiss <adam@indexdata.dk>
     9Date:   Mon Jan 11 11:04:38 2016 +0100
     10
     11    Happy new year
     12
     13commit d35bb455afe361c1f8ed360cce55e8fb75c6eec7
     14Author: Adam Dickmeiss <adam@indexdata.dk>
     15Date:   Mon Jan 11 11:04:11 2016 +0100
     16
     17    Mention configure as a script
     18
     19commit 2eb6e27fe677e40f53327f5af456d39df5b24edf
     20Author: Adam Dickmeiss <adam@indexdata.dk>
     21Date:   Mon Jan 11 11:01:00 2016 +0100
     22
     23    Mention Github + buildconf.sh
     24
     25commit ccfd0bb7d8af350d358e70a3b4bedb289e2be042
     26Author: Adam Dickmeiss <adam@indexdata.dk>
     27Date:   Mon Jan 11 11:00:15 2016 +0100
     28
     29    Update list of Debian packages for buildconf.sh
     30
     31commit 4c57a37b6ff798585433440641d9c86a25c9092c
     32Author: Adam Dickmeiss <adam@indexdata.dk>
     33Date:   Wed Jan 6 11:26:26 2016 +0100
     34
     35    Use submodules from Github
     36
     37commit 7b112287740b44d1dd939cea0ecca217356affd5
     38Author: Adam Dickmeiss <adam@indexdata.dk>
     39Date:   Thu Nov 26 10:06:18 2015 +0100
     40
     41    No more manifest files
     42
     43commit d4514445a1caea19faff82c3541a716ddfdc2b0f
     44Author: Adam Dickmeiss <adam@indexdata.dk>
     45Date:   Tue Nov 24 14:14:20 2015 +0100
     46
     47    Include links to pre-compiled ICU binaries
     48
     49commit b687939804570b289122ca78f25b5f255ed36326
     50Author: Adam Dickmeiss <adam@indexdata.dk>
     51Date:   Tue Nov 24 14:14:11 2015 +0100
     52
     53    Update list of supported platforms
     54
     55commit 05f7afcaa053728864a9b1b6d7bd1a6a48701f2c
     56Author: Adam Dickmeiss <adam@indexdata.dk>
     57Date:   Tue Nov 24 14:13:35 2015 +0100
     58
     59    Update doc/common
     60
     61commit ebfa76b327665398553785b6a00e69d119ba9297
     62Merge: b1a5a64 4e71d4a
     63Author: Adam Dickmeiss <adam@indexdata.dk>
     64Date:   Tue Nov 24 13:54:30 2015 +0100
     65
     66    Merge branch 'master' of ssh://git.indexdata.com:222/home/git/pub/yaz
     67
     68commit b1a5a6402e767afee10073381d842642d3a640d0
     69Author: Adam Dickmeiss <adam@indexdata.dk>
     70Date:   Tue Nov 24 13:52:36 2015 +0100
     71
     72    Win32/64 split. Use ICU compiled with VS2015
     73
     74commit 4e71d4a715bca8fc6a9a1010ffa00def8c63ab1b
     75Author: Adam Dickmeiss <adam@indexdata.dk>
     76Date:   Tue Nov 17 15:14:06 2015 +0100
     77
     78    Remove <info> from ref entry header
     79
     80commit 81358822816ed75a14af31a0656550de1329c33a
     81Author: Adam Dickmeiss <adam@indexdata.dk>
     82Date:   Mon Nov 16 16:01:50 2015 +0100
     83
     84    README.md
     85
     86commit 319ea8d6f518d08c1f50d8ec80899e1bc6ca7923
     87Author: Adam Dickmeiss <adam@indexdata.dk>
     88Date:   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
     94commit 02b4f0ab937b62d892d3e0918439da770fe720c2
     95Author: Adam Dickmeiss <adam@indexdata.dk>
     96Date:   Thu Nov 12 08:54:19 2015 +0000
     97
     98    Version 5.15.1
     99
     100commit 2bfb0b990bbbe0f9c5ef9e78b094a2063bc45f33
     101Author: Adam Dickmeiss <adam@indexdata.dk>
     102Date:   Thu Nov 12 09:48:02 2015 +0100
     103
     104    Add test case for YAZ-861 YAZ-865
     105
     106commit 8484857deb143d2a71498d3b8b7a345328dac969
     107Author: Adam Dickmeiss <adam@indexdata.dk>
     108Date:   Wed Nov 11 21:52:15 2015 +0100
     109
     110    sha1: Work around older VS compilers
     111
     112commit 92e9ead954f1292391afde93235f0fd25891da8e
     113Author: Adam Dickmeiss <adam@indexdata.dk>
     114Date:   Wed Nov 11 21:51:05 2015 +0100
     115
     116    Current YAZ are made with VS 2015
     117
     118commit a6b61b9f8b6576e8159a4e7e6aee88bba7e5d07d
     119Author: Adam Dickmeiss <adam@indexdata.dk>
     120Date:   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
     126commit 4eb90d87b9374b30b8ea4f9d5e70d509a11d9a58
     127Author: Adam Dickmeiss <adam@indexdata.dk>
     128Date:   Wed Nov 11 14:50:27 2015 +0100
     129
     130    Fix rpn2cql fails for Bib-1 set in qry+conf YAZ-865
     131
     132commit 94a0aa1a3d45b41484ac4bf81b85f90dca7f7181
     133Author: Adam Dickmeiss <adam@indexdata.dk>
     134Date:   Wed Nov 11 14:13:31 2015 +0100
     135
     136    Bundle sha1 rather than use libgcrypt/nettle
     137
     138commit 1b29294f1ba913fb798c3556e3fda09bfc46bb67
     139Author: Adam Dickmeiss <adam@indexdata.dk>
     140Date:   Wed Nov 11 09:04:25 2015 +0000
     141
     142    Version 5.15.0
     143
     144commit 71e94b6a27e3dd1dcd8a781254a4c329de020f34
     145Author: Adam Dickmeiss <adam@indexdata.dk>
     146Date:   Wed Nov 11 09:03:41 2015 +0000
     147
     148    Add Ubuntu Wily Werewolf
     149
     150commit 240156e69d3a6390699644756e367fffd42891d1
     151Author: Adam Dickmeiss <adam@indexdata.dk>
     152Date:   Tue Nov 10 13:47:18 2015 +0100
     153
     154    CCL: fix other inherited attributes
     155
     156commit 31596bdcae098f8acea695d44c44ee5f646b4c1f
     157Author: Adam Dickmeiss <adam@indexdata.dk>
     158Date:   Tue Nov 10 13:26:00 2015 +0100
     159
     160    CCL: fix r=o, r=r WRT inherited attributes YAZ-864
     161
     162commit 13da404f1294cb29e30100e71b76c4b44e06cf89
     163Author: Adam Dickmeiss <adam@indexdata.dk>
     164Date:   Mon Nov 9 12:48:24 2015 +0000
     165
     166    Version 5.14.12
     167
     168commit 8b9999744362603b448a74f779ff7a2b4d76c89d
     169Author: Adam Dickmeiss <adam@indexdata.dk>
     170Date:   Mon Nov 9 13:47:46 2015 +0100
     171
     172    Set VS_REDIST_EXE for all architectures
     173
     174commit dae688b0b3ebe96d6b65385b2fa0e627ab6ce451
     175Author: Adam Dickmeiss <adam@indexdata.dk>
     176Date:   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
     182commit 84153486e91926be04dd28d4f2bda6c6ade0e005
     183Author: Adam Dickmeiss <adam@indexdata.dk>
     184Date:   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
     197commit 2487937ef218d16b41294bf7d1845d164e17bfe2
     198Author: Adam Dickmeiss <adam@indexdata.dk>
     199Date:   Mon Nov 9 11:55:39 2015 +0000
     200
     201    Build with nettle on Debian/Ubuntu
     202
     203commit 60f0955d87a511503ce48de0e99f697e112ff3d0
     204Author: Adam Dickmeiss <adam@indexdata.dk>
     205Date:   Mon Nov 9 12:45:04 2015 +0100
     206
     207    Allow use of Nettle as an alternative to gcrypt
     208
     209commit 756129c2a4eaa8a0cc4e0acbc8b401083024c1e2
     210Author: Adam Dickmeiss <adam@indexdata.dk>
     211Date:   Mon Nov 9 12:00:14 2015 +0100
     212
     213    yaz_deinit_globals closes FILE log
     214
     215commit eec02e3b60802638aa3a105f3037814cf32af3b6
     216Author: Adam Dickmeiss <adam@indexdata.dk>
     217Date:   Thu Nov 5 12:50:26 2015 +0100
     218
     219    cs_get_host_args: allow unix:path:args notation
     220
     221commit 7207680c8f685c9ed33536bfd4a4878cb2616d99
     222Author: Adam Dickmeiss <adam@indexdata.dk>
     223Date:   Wed Oct 28 11:08:40 2015 +0100
     224
     225    Build with VS 2015 (2014 runtime)
     226
     227commit 70ce06b6fcbe3a53e94111ecedf0312848647c1b
     228Author: Adam Dickmeiss <adam@indexdata.dk>
     229Date:   Wed Oct 28 11:08:01 2015 +0100
     230
     231    Fix registry keys for VC runtime
     232
     233commit a4a4e9d375bfbcc823e8b3820ffb23272e919004
     234Author: Adam Dickmeiss <adam@indexdata.dk>
     235Date:   Tue Oct 27 15:40:03 2015 +0100
     236
     237    Prepare to bundle VC 2015 Runtime 14.0.23026
     238
     239commit 917d2c4a288a19c0da7fa98ad514288d0e045413
     240Author: Adam Dickmeiss <adam@indexdata.dk>
     241Date:   Tue Oct 27 15:39:38 2015 +0100
     242
     243    make64 does not build yaz4j
     244
     245commit d438b90ac17fbae25ba2554dd76f4e156f420437
     246Author: Adam Dickmeiss <adam@indexdata.dk>
     247Date:   Thu Oct 22 16:31:26 2015 +0200
     248
     249    Cleanup de-init function YAZ-863
     250   
     251    New function yaz_deinit_globals
     252
     253commit 7cf33bcd4c625c2197101ebffd38513e44271be6
     254Author: Adam Dickmeiss <adam@indexdata.dk>
     255Date:   Fri Oct 9 15:09:34 2015 +0000
     256
     257    Version 5.14.11
     258
     259commit 59830038599648515b34784fbab8f5befa63e185
     260Author: Adam Dickmeiss <adam@indexdata.dk>
     261Date:   Fri Oct 9 15:09:17 2015 +0000
     262
     263    Remove Ubuntu utopic
     264
     265commit e8001c3381e00a846e96fab5a1c6f7ca00df4f55
     266Author: Adam Dickmeiss <adam@indexdata.dk>
     267Date:   Fri Oct 9 16:15:42 2015 +0200
     268
     269    Fix RPN to CQL rejects local Bib-1 attribute set YAZ-861
     270
     271commit 39671a069c30f6cc508de7692f49a01f413a5a16
     272Author: Adam Dickmeiss <adam@indexdata.dk>
     273Date:   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
     279commit ab99e2d94176eef3b1b23ef3f0f180c6d5077ea6
     280Author: Adam Dickmeiss <adam@indexdata.dk>
     281Date:   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
     289commit 38f746ee0f3da5e620bbf3b60eb2ccc1bc647d19
     290Author: Adam Dickmeiss <adam@indexdata.dk>
     291Date:   Wed Oct 7 11:29:21 2015 +0200
     292
     293    Update doc/common
     294
     295commit 323805b6779bcf1befdc7cdd7f10c23b06885e0d
     296Author: David Crossley <dcrossley@indexgeo.com.au>
     297Date:   Wed Oct 7 12:57:33 2015 +1100
     298
     299    Various minor text tweaks.
     300
     301commit 0ec12c344e05f3637af9f48e6aa28a54d99f8343
     302Author: David Crossley <dcrossley@indexgeo.com.au>
     303Date:   Mon Oct 5 15:22:20 2015 +1100
     304
     305    Various minor text tweaks.
     306
     307commit 2a624ff1daa841601aebca86c0196039da6978b3
     308Author: Adam Dickmeiss <adam@indexdata.dk>
     309Date:   Wed Sep 16 14:21:04 2015 +0200
     310
     311    Fix windows uninstall does not remove start menu shortcuts YAZ-860
     312
     313commit 3cdd02c11b85c98430021bbc6413fcceda754354
     314Author: Adam Dickmeiss <adam@indexdata.dk>
     315Date:   Wed Sep 16 09:10:07 2015 +0000
     316
     317    Version 5.14.10
     318
     319commit 4db60a9b1f537de4c0f04587b44be32d0701a64f
     320Author: Adam Dickmeiss <adam@indexdata.dk>
     321Date:   Tue Sep 15 19:43:54 2015 +0200
     322
     323    prevent huge expansions in CCL s=sl YAZ-859
     324
     325commit ba19dacdfe290bee024a23673a6e75f451e2c013
     326Author: Adam Dickmeiss <adam@indexdata.dk>
     327Date:   Tue Sep 15 09:02:49 2015 +0000
     328
     329    Version 5.14.9
     330
     331commit 1426a3da9b0390bb0d928a6ee56ebf5fa0ceb0ef
     332Author: Adam Dickmeiss <adam@indexdata.dk>
     333Date:   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
     342commit 7c6b3363478950a3a5c7f448e5bfa6f4ea19fbab
     343Author: Adam Dickmeiss <adam@indexdata.dk>
     344Date:   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
     351commit 30af0a1ebbea75c3e757eb03d3f988c61fce8511
     352Author: Adam Dickmeiss <adam@indexdata.dk>
     353Date:   Mon Sep 14 13:53:34 2015 +0000
     354
     355    Version 5.14.8
     356
     357commit c5b92d32f5619eae0b99c4bfb39374e8ef675e34
     358Author: Adam Dickmeiss <adam@indexdata.dk>
     359Date:   Mon Sep 14 15:49:47 2015 +0200
     360
     361    Remove ununsed function ccl_rpn_dup
     362
     363commit 4f3f16d519137001a916178e28ad1dff8b986a7d
     364Author: Adam Dickmeiss <adam@indexdata.dk>
     365Date:   Mon Sep 14 15:48:43 2015 +0200
     366
     367    Fix SEGV for s=sl for 3 terms and syntax error YAZ-857
     368
     369commit de94629a46584eafe114f740ed3000b26dd42ffb
     370Author: Adam Dickmeiss <adam@indexdata.dk>
     371Date:   Sun Sep 13 19:31:45 2015 +0000
     372
     373    Version 5.14.7
     374
     375commit fcb40f9ed16ce6a8ef86997890057af0f7692377
     376Author: Adam Dickmeiss <adam@indexdata.dk>
     377Date:   Sun Sep 13 21:12:40 2015 +0200
     378
     379    backtrace: add \n in error msg
     380
     381commit 7cda3530b0d64128462118433a9f69645f49a39b
     382Author: Adam Dickmeiss <adam@indexdata.dk>
     383Date:   Sun Sep 13 21:08:30 2015 +0200
     384
     385    Fix possible deadlock in backtrace YAZ-856
     386
     387commit b0afe9a4eb412d5d605450ea715dcd033f45b878
     388Merge: e94e943 a7261ce
     389Author: Wolfram Schneider <wosch@indexdata.dk>
     390Date:   Tue Sep 8 12:21:49 2015 +0000
     391
     392    Merge branch 'master' of ssh://git.indexdata.com:222/home/git/pub/yaz
     393
     394commit e94e943c08f4f9265c2ff211d74984166b289841
     395Author: Wolfram Schneider <wosch@indexdata.dk>
     396Date:   Tue Sep 8 11:45:37 2015 +0000
     397
     398    documentation: libreadline5-dev is retired, recommend to install libreadline-gplv2-dev
     399
     400commit 44c26c79fddc6d28b4da0a0fd5788eca526b390e
     401Author: Wolfram Schneider <wosch@indexdata.dk>
     402Date:   Tue Sep 8 11:42:23 2015 +0000
     403
     404    update documentation / help text
     405
     406commit a7261ce1171ca8e90561b2055e6198e15208bcd6
     407Author: Adam Dickmeiss <adam@indexdata.dk>
     408Date:   Tue Sep 8 09:02:05 2015 +0200
     409
     410    Fix docpath example
     411
     412commit a996c33edb96a3273c81d799189b33437ad6ae18
     413Author: David Crossley <dcrossley@indexgeo.com.au>
     414Date:   Tue Sep 8 14:10:10 2015 +1000
     415
     416    Various minor text tweaks.
     417
     418commit 086d0dd7b180c786daf78359e1a7b94c656dd855
     419Author: Adam Dickmeiss <adam@indexdata.dk>
     420Date:   Mon Sep 7 17:26:20 2015 +0200
     421
     422    yaz-ztest: set named_result_sets flag
     423
     424commit d802116821b20c1dac70011b1ff36edfc4a3119b
     425Author: David Crossley <dcrossley@indexgeo.com.au>
     426Date:   Thu Sep 3 15:53:19 2015 +1000
     427
     428    Various minor text tweaks.
     429
     430commit f332be40c2edee783d37633597b4f7ac3b22fc3e
     431Author: David Crossley <dcrossley@indexgeo.com.au>
     432Date:   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
     436commit 3b046fa5df64b76cc6a28f562c135c06d7a428a7
     437Author: David Crossley <dcrossley@indexgeo.com.au>
     438Date:   Wed Sep 2 12:19:38 2015 +1000
     439
     440    Various minor text tweaks.
     441
     442commit 02ef0ddc8ff17fa5053089af7d5d93ea1f2182ea
     443Author: David Crossley <dcrossley@indexgeo.com.au>
     444Date:   Wed Sep 2 12:18:15 2015 +1000
     445
     446    Various minor text tweaks.
     447
     448commit 87faebe8ef5cab8f6df86f387e8b919b7b9897a8
     449Author: Adam Dickmeiss <adam@indexdata.dk>
     450Date:   Mon Aug 17 12:41:33 2015 +0000
     451
     452    Version 5.14.6
     453
     454commit 473f3071b86a40479e38e3fe4d434c0d2bf03379
     455Author: Adam Dickmeiss <adam@indexdata.dk>
     456Date:   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
     462commit 686414b0ac6446cd55610d5203d61a32672e2203
     463Author: Adam Dickmeiss <adam@indexdata.dk>
     464Date:   Thu Aug 6 10:23:41 2015 +0000
     465
     466    Version 5.14.5
     467
     468commit 7673cf27f5be351a18a5d3ea1baf6c4aee06eb3b
     469Author: Adam Dickmeiss <adam@indexdata.dk>
     470Date:   Wed Aug 5 13:43:22 2015 +0000
     471
     472    Remove Debian squeeze (compat 8)
     473
     474commit 8e27c4a44da61c8d639187f2b914ef7d432baed5
     475Author: Adam Dickmeiss <adam@indexdata.dk>
     476Date:   Wed Aug 5 15:29:19 2015 +0200
     477
     478    debian compat 9 YAZ-854
     479
     480commit d7909431b9e73132e227463279bc8fe614c49184
     481Author: Adam Dickmeiss <adam@indexdata.dk>
     482Date:   Wed Aug 5 13:23:29 2015 +0200
     483
     484    rpn2cql diagnostics: provide use attribute addinfo YAZ-853
     485
     486commit 5ae31048f134f9f9db937db6847edef583123a90
     487Author: Adam Dickmeiss <adam@indexdata.dk>
     488Date:   Tue Aug 4 12:19:09 2015 +0000
     489
     490    deb: deprecated substitution ${Source-Version} YAZ-852
     491
     492commit 5be87e7a04c7219b31cefc0a3bd02fe5a255430c
     493Author: Adam Dickmeiss <adam@indexdata.dk>
     494Date:   Wed Jul 29 15:36:51 2015 +0200
     495
     496    Fix yaz-client: semicolon terminates arguments YAZ-851
     497
     498commit f575db041e99b9c7455e5251fe677d145c98f6f0
     499Author: Adam Dickmeiss <adam@indexdata.dk>
     500Date:   Wed Jul 29 08:54:34 2015 +0000
     501
     502    Version 5.14.4
     503
     504commit eb556013557ef8c9e76c52614f88c059ec443c95
     505Author: Adam Dickmeiss <adam@indexdata.dk>
     506Date:   Tue Jul 28 13:04:55 2015 +0200
     507
     508    Solr >= 5.1 / content type text/xml YAZ-850
     509
    1510commit 74168354bcd4a020093adb4a1c0981e35ed340db
    2511Author: Adam Dickmeiss <adam@indexdata.dk>
  • yaz/trunk/fuentes/IDMETA

    r255 r265  
    1 DEBIAN_DIST="jessie wheezy squeeze"
    2 UBUNTU_DIST="vivid utopic trusty precise"
     1DEBIAN_DIST="jessie wheezy"
     2UBUNTU_DIST="wily vivid trusty precise"
    33CENTOS_DIST="centos5 centos6 centos7"
    4 VERSION=5.14.3
     4VERSION=5.15.2
  • yaz/trunk/fuentes/LICENSE

    r255 r265  
    1 Copyright (c) 1995-2015, Index Data
     1Copyright (c) 1995-2016, Index Data
    22All rights reserved.
    33Redistribution and use in source and binary forms, with or without
  • yaz/trunk/fuentes/Makefile.am

    r255 r265  
    1717
    1818SPEC_FILE=$(PACKAGE).spec
    19 EXTRA_DIST=$(SPEC_FILE) IDMETA README LICENSE NEWS m4/id-config.sh \
     19EXTRA_DIST=$(SPEC_FILE) IDMETA README.md LICENSE NEWS m4/id-config.sh \
    2020        yaz-config.in yaz.pc.in m4/yaz.m4 m4/yaz_libxml2.m4 buildconf.sh \
    2121        Doxyfile.in m4/acx_pthread.m4 m4/ac_check_icu.m4
  • yaz/trunk/fuentes/Makefile.in

    r255 r265  
    8484        $(srcdir)/yaz-config.in $(srcdir)/yaz.pc.in \
    8585        $(srcdir)/Doxyfile.in $(top_srcdir)/win/version.nsi.in \
    86         ChangeLog NEWS README config/compile config/config.guess \
     86        ChangeLog NEWS config/compile config/config.guess \
    8787        config/config.sub config/depcomp config/install-sh \
    8888        config/missing config/ylwrap config/ltmain.sh \
     
    261261EXEEXT = @EXEEXT@
    262262FGREP = @FGREP@
    263 GCRYPT_LIBS = @GCRYPT_LIBS@
    264263GREP = @GREP@
    265264HIREDIS_LIBS = @HIREDIS_LIBS@
     
    363362libdir = @libdir@
    364363libexecdir = @libexecdir@
    365 libgcrypt = @libgcrypt@
    366364localedir = @localedir@
    367365localstatedir = @localstatedir@
     
    390388pkgconfig_DATA = yaz.pc
    391389SPEC_FILE = $(PACKAGE).spec
    392 EXTRA_DIST = $(SPEC_FILE) IDMETA README LICENSE NEWS m4/id-config.sh \
     390EXTRA_DIST = $(SPEC_FILE) IDMETA README.md LICENSE NEWS m4/id-config.sh \
    393391        yaz-config.in yaz.pc.in m4/yaz.m4 m4/yaz_libxml2.m4 buildconf.sh \
    394392        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
     3Re-organize Windows build. Use ICU compiled with VS 2015 to use
     4same runtime as rest of components (YAZ, Libxml2, etc).
     5
     6Move YAZ and many other software components to GitHub.
     7
     8--- 5.15.1 2015/11/12
     9
     10Bundle sha1 rather than use libgcrypt/nettle. This means that
     11configure no longer accepts --with-gcrypt and --with-nettle.
     12
     13Fix rpn2cql fails for Bib-1 set in qry+conf YAZ-865
     14
     15--- 5.15.0 2015/11/11
     16
     17CCL: fix r=o, r=r WRT inherited attributes YAZ-864
     18
     19--- 5.14.12 2015/11/09
     20
     21Build with nettle on Debian/Ubuntu
     22
     23test system calls yaz_deinit_globals for better memory leak detection
     24
     25cs_get_host_args: allow unix:path:args notation
     26
     27Windows: build YAZ with VC 2015 and bundle it with runtime
     28version 14.0.23026.
     29
     30--- 5.14.11 2015/10/09
     31
     32Fix RPN to CQL rejects local Bib-1 attribute set YAZ-861
     33
     34ZOOM C: tweak when connection failed is returned
     35For cases with multiple socket addresses for some hostname, eg
     36localhost IPV4+IPV6, the code now properly returns "connection
     37failed" rather than "connection lost".
     38
     39Various minor documenation tweaks from David Crossley. Thanks.
     40
     41Fix windows uninstall does not remove start menu shortcuts YAZ-860
     42
     43--- 5.14.10 2015/09/16
     44
     45Prevent huge expansions in CCL s=sl YAZ-859
     46
     47--- 5.14.9 2015/09/15
     48
     49Fix segv in ZOOM_connection_fire_event_socket YAZ-858
     50The odr_in memory taken by handle_srw_response, and, thus if result
     51set is destructed before we expect the HTTP response (hres) it may
     52be come invalid. Therefore we inspect hres before the call to
     53ZOOM_handle_sru.
     54
     55Fix possible deadlock in backtrace (2nd attempt) YAZ-856
     56An alarm is set up so that backtrace is terminated if it hangs.
     57Even if backtrace the handler also attempts to spawn gdb.
     58
     59--- 5.14.8 2015/09/14
     60
     61Fix SEGV for s=sl for 3 terms and syntax error YAZ-857
     62
     63--- 5.14.7 2015/09/13
     64
     65Fix possible deadlock in backtrace YAZ-856
     66
     67Various minor text tweaks in documentation
     68
     69--- 5.14.6 2015/08/17
     70
     71Fix yaz-client command args parsing broken YAZ-855
     72Bug introduced in 5be87e7a04c7219b31cefc0a3 - version 5.14.5
     73
     74--- 5.14.5 2015/08/06
     75
     76Stop building packages for obsolete Debian squeeze and use DH
     77version 9. YAZ-854
     78
     79rpn2cql diagnostics: provide use attribute addinfo YAZ-853
     80
     81deb: deprecated substitution ${Source-Version} YAZ-852
     82
     83Fix yaz-client: semicolon terminates arguments YAZ-851
     84
     85--- 5.14.4 2015/07/29
     86
     87Windows: Bundle VC runtime exe YAZ-848
     88
     89Omit Content-Type for HTTP requests to Solr YAZ-850
     90
    191--- 5.14.3 2015/06/29
    292
  • yaz/trunk/fuentes/buildconf.sh

    r255 r265  
    3535
    3636When building from Git, you need these Debian packages:
    37   autoconf automake libtool gcc bison tcl8.4
     37  autoconf automake libtool gcc bison tclsh
    3838  xsltproc docbook docbook-xml docbook-xsl
    39   libxslt1-dev libgnutls-dev libreadline5-dev libwrap0-dev
    40   pkg-config libicu-dev
     39  libxslt1-dev libgnutls-dev libreadline--dev libwrap0-dev
     40  pkg-config libicu-dev make
    4141
    4242And if you want to make a Debian package: dpkg-dev fakeroot debhelper
  • yaz/trunk/fuentes/client/Makefile.in

    r255 r265  
    200200EXEEXT = @EXEEXT@
    201201FGREP = @FGREP@
    202 GCRYPT_LIBS = @GCRYPT_LIBS@
    203202GREP = @GREP@
    204203HIREDIS_LIBS = @HIREDIS_LIBS@
     
    302301libdir = @libdir@
    303302libexecdir = @libexecdir@
    304 libgcrypt = @libgcrypt@
    305303localedir = @localedir@
    306304localstatedir = @localstatedir@
  • yaz/trunk/fuentes/client/client.c

    r255 r265  
    51855185{
    51865186    int i, res;
    5187     char word[32], arg[10240];
     5187    char word[32], *arg;
     5188    int no_read = 0;
    51885189
    51895190#if HAVE_GETTIMEOFDAY
     
    51915192#endif
    51925193
    5193     if ((res = sscanf(line, "%31s %10239[^;]", word, arg)) <= 0)
     5194    sscanf(line, "%31s%n", word, &no_read);
     5195    if (no_read == 0)
    51945196    {
    51955197        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;
    52005202    strcpy(last_cmd, word);
    52015203
    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)
    52085212        {
    52095213            if (!yaz_isspace(*p))
     
    52895293    else
    52905294    {
    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)
    52945298        {
    52955299            rl_attempted_completion_over = 1;
  • yaz/trunk/fuentes/configure

    r255 r265  
    11#! /bin/sh
    22# Guess values for system-dependent variables and create Makefiles.
    3 # Generated by GNU Autoconf 2.69 for yaz 5.14.3.
     3# Generated by GNU Autoconf 2.69 for yaz 5.15.2.
    44#
    55# Report bugs to <yaz-help@indexdata.dk>.
     
    591591PACKAGE_NAME='yaz'
    592592PACKAGE_TARNAME='yaz'
    593 PACKAGE_VERSION='5.14.3'
    594 PACKAGE_STRING='yaz 5.14.3'
     593PACKAGE_VERSION='5.15.2'
     594PACKAGE_STRING='yaz 5.15.2'
    595595PACKAGE_BUGREPORT='yaz-help@indexdata.dk'
    596596PACKAGE_URL=''
     
    656656MEMCACHED_LIBS
    657657HIREDIS_LIBS
    658 libgcrypt
    659 GCRYPT_LIBS
    660658XSL_DIR
    661659DSSSL_DIR
     
    798796with_docbook_dsssl
    799797with_docbook_xsl
    800 with_libgcrypt
    801798with_redis
    802799with_memcached
     
    13591356  # This message is too long to be a string in the A/UX 3.1 sh.
    13601357  cat <<_ACEOF
    1361 \`configure' configures yaz 5.14.3 to adapt to many kinds of systems.
     1358\`configure' configures yaz 5.15.2 to adapt to many kinds of systems.
    13621359
    13631360Usage: $0 [OPTION]... [VAR=VALUE]...
     
    14291426if test -n "$ac_init_help"; then
    14301427  case $ac_init_help in
    1431      short | recursive ) echo "Configuration of yaz 5.14.3:";;
     1428     short | recursive ) echo "Configuration of yaz 5.15.2:";;
    14321429   esac
    14331430  cat <<\_ACEOF
     
    14621459  --with-docbook-dsssl=DIR use Docbook DSSSL in DIR/{html,print}/docbook.dsl
    14631460  --with-docbook-xsl=DIR  use Docbook XSL in DIR/{htmlhelp,xhtml}
    1464   --with-libgcrypt=DIR    use libgcrypt-config in DIR
    14651461  --with-redis            hiredis library
    14661462  --with-memcached        Memcached library
     
    15481544if $ac_init_version; then
    15491545  cat <<\_ACEOF
    1550 yaz configure 5.14.3
     1546yaz configure 5.15.2
    15511547generated by GNU Autoconf 2.69
    15521548
     
    19711967running configure, to aid debugging if configure makes a mistake.
    19721968
    1973 It was created by yaz $as_me 5.14.3, which was
     1969It was created by yaz $as_me 5.15.2, which was
    19741970generated by GNU Autoconf 2.69.  Invocation command line was
    19751971
     
    28372833# Define the identity of the package.
    28382834 PACKAGE='yaz'
    2839  VERSION='5.14.3'
     2835 VERSION='5.15.2'
    28402836
    28412837
     
    1181411810
    1181511811
     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; }
     11814if ${ac_cv_c_bigendian+:} false; then :
     11815  $as_echo_n "(cached) " >&6
     11816else
     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
     11827if 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
     11850fi
     11851rm -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
     11859int
     11860main ()
     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
     11872if 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
     11879int
     11880main ()
     11881{
     11882#if BYTE_ORDER != BIG_ENDIAN
     11883                 not big endian
     11884                #endif
     11885
     11886  ;
     11887  return 0;
     11888}
     11889_ACEOF
     11890if ac_fn_c_try_compile "$LINENO"; then :
     11891  ac_cv_c_bigendian=yes
     11892else
     11893  ac_cv_c_bigendian=no
     11894fi
     11895rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
     11896fi
     11897rm -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
     11905int
     11906main ()
     11907{
     11908#if ! (defined _LITTLE_ENDIAN || defined _BIG_ENDIAN)
     11909              bogus endian macros
     11910             #endif
     11911
     11912  ;
     11913  return 0;
     11914}
     11915_ACEOF
     11916if 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
     11922int
     11923main ()
     11924{
     11925#ifndef _BIG_ENDIAN
     11926                 not big endian
     11927                #endif
     11928
     11929  ;
     11930  return 0;
     11931}
     11932_ACEOF
     11933if ac_fn_c_try_compile "$LINENO"; then :
     11934  ac_cv_c_bigendian=yes
     11935else
     11936  ac_cv_c_bigendian=no
     11937fi
     11938rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
     11939fi
     11940rm -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.  */
     11948short 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
     11964int
     11965main ()
     11966{
     11967return use_ascii (foo) == use_ebcdic (foo);
     11968  ;
     11969  return 0;
     11970}
     11971_ACEOF
     11972if 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
     11984fi
     11985rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
     11986else
     11987  cat confdefs.h - <<_ACEOF >conftest.$ac_ext
     11988/* end confdefs.h.  */
     11989$ac_includes_default
     11990int
     11991main ()
     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
     12007if ac_fn_c_try_run "$LINENO"; then :
     12008  ac_cv_c_bigendian=no
     12009else
     12010  ac_cv_c_bigendian=yes
     12011fi
     12012rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \
     12013  conftest.$ac_objext conftest.beam conftest.$ac_ext
     12014fi
     12015
     12016    fi
     12017fi
     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
    1181612036for 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
    1181712037do :
     
    1207512295fi
    1207612296
    12077 
    12078 libgcryptpath=NONE
    12079 
    12080 # Check whether --with-libgcrypt was given.
    12081 if test "${with_libgcrypt+set}" = set; then :
    12082   withval=$with_libgcrypt; libgcryptpath=$withval
    12083 fi
    12084 
    12085 if test "$libgcryptpath" != "no"; then
    12086     if test "$libgcryptpath" = "NONE"; then
    12087         # Extract the first word of "libgcrypt-config", so it can be a program name with args.
    12088 set dummy libgcrypt-config; ac_word=$2
    12089 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
    12090 $as_echo_n "checking for $ac_word... " >&6; }
    12091 if ${ac_cv_path_libgcrypt+:} false; then :
    12092   $as_echo_n "(cached) " >&6
    12093 else
    12094   case $libgcrypt in
    12095   [\\/]* | ?:[\\/]*)
    12096   ac_cv_path_libgcrypt="$libgcrypt" # Let the user override the test with a path.
    12097   ;;
    12098   *)
    12099   as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
    12100 for as_dir in $PATH
    12101 do
    12102   IFS=$as_save_IFS
    12103   test -z "$as_dir" && as_dir=.
    12104     for ac_exec_ext in '' $ac_executable_extensions; do
    12105   if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
    12106     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" >&5
    12108     break 2
    12109   fi
    12110 done
    12111   done
    12112 IFS=$as_save_IFS
    12113 
    12114   test -z "$ac_cv_path_libgcrypt" && ac_cv_path_libgcrypt="NONE"
    12115   ;;
    12116 esac
    12117 fi
    12118 libgcrypt=$ac_cv_path_libgcrypt
    12119 if test -n "$libgcrypt"; then
    12120   { $as_echo "$as_me:${as_lineno-$LINENO}: result: $libgcrypt" >&5
    12121 $as_echo "$libgcrypt" >&6; }
    12122 else
    12123   { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
    12124 $as_echo "no" >&6; }
    12125 fi
    12126 
    12127 
    12128     elif test -x $libgcryptpath/libgcrypt-config; then
    12129         libgcrypt=$libgcryptpath/libgcrypt-config
    12130     else
    12131         libgcrypt=$libgcryptpath
    12132     fi
    12133     { $as_echo "$as_me:${as_lineno-$LINENO}: checking for libgcrypt" >&5
    12134 $as_echo_n "checking for libgcrypt... " >&6; }
    12135     if "$libgcrypt" --version >/dev/null 2>&1; then
    12136         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" >&5
    12139 $as_echo "$libgcryptversion" >&6; }
    12140         if test $libgcryptversion2 -ge 1002; then
    12141             GCRYPT_LIBS="`$libgcrypt --libs`"
    12142             CFLAGS="$CFLAGS `$libgcrypt --cflags`"
    12143 
    12144 $as_echo "#define HAVE_GCRYPT_H 1" >>confdefs.h
    12145 
    12146         else
    12147             if test "$libgcryptpath" = "NONE"; then
    12148                 { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: Only libgcrypt version 1.2 and later supported" >&5
    12149 $as_echo "$as_me: WARNING: Only libgcrypt version 1.2 and later supported" >&2;}
    12150             else
    12151                 as_fn_error $? "Only libgcrypt version 1.2 and later supported" "$LINENO" 5
    12152             fi
    12153             libgcryptversion=""
    12154         fi
    12155     else
    12156         { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
    12157 $as_echo "no" >&6; }
    12158     fi
    12159 fi
    1216012297hiredis=default
    1216112298
     
    1216612303fi
    1216712304
    12168 if test "$hiredis" != "no" -a "$pkgconfigpath" != "NONE" -a "$libgcryptversion"; then
     12305if test "$hiredis" != "no" -a "$pkgconfigpath" != "NONE"; then
    1216912306    { $as_echo "$as_me:${as_lineno-$LINENO}: checking for redisCommandArgv in -lhiredis" >&5
    1217012307$as_echo_n "checking for redisCommandArgv in -lhiredis... " >&6; }
     
    1224812385fi
    1224912386
    12250 if test "$memcached" != "no" -a -n "$libgcryptversion" -a "$pkgconfigpath" != "NONE"; then
     12387if test "$memcached" != "no" -a "$pkgconfigpath" != "NONE"; then
    1225112388    { $as_echo "$as_me:${as_lineno-$LINENO}: checking for libmemcached" >&5
    1225212389$as_echo_n "checking for libmemcached... " >&6; }
     
    1377613913fi
    1377713914
     13915
    1377813916: "${CONFIG_STATUS=./config.status}"
    1377913917ac_write_fail=0
     
    1417214310# values after options handling.
    1417314311ac_log="
    14174 This file was extended by yaz $as_me 5.14.3, which was
     14312This file was extended by yaz $as_me 5.15.2, which was
    1417514313generated by GNU Autoconf 2.69.  Invocation command line was
    1417614314
     
    1423814376ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
    1423914377ac_cs_version="\\
    14240 yaz config.status 5.14.3
     14378yaz config.status 5.15.2
    1424114379configured by $0, generated by GNU Autoconf 2.69,
    1424214380  with options \\"\$ac_cs_config\\"
  • yaz/trunk/fuentes/configure.ac

    r255 r265  
    2828dnl
    2929dnl
     30AC_C_BIGENDIAN
    3031AC_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],[],[],[])
    3132AC_CHECK_HEADERS([net/if.h netinet/in.h netinet/if_ether.h],[],[],[
     
    6263fi
    6364AC_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
     65dnl
    9766dnl ------ redis
    9867hiredis=default
    9968AC_SUBST([HIREDIS_LIBS])
    10069AC_ARG_WITH([redis], [  --with-redis            hiredis library], [hiredis=$withval])
    101 if test "$hiredis" != "no" -a "$pkgconfigpath" != "NONE" -a "$libgcryptversion"; then
     70if test "$hiredis" != "no" -a "$pkgconfigpath" != "NONE"; then
    10271    AC_CHECK_LIB([hiredis],[redisCommandArgv],[HIREDIS_LIBS=-lhiredis])
    10372    AC_MSG_CHECKING([for redis])
     
    13099AC_SUBST([MEMCACHED_LIBS])
    131100AC_ARG_WITH([memcached], [  --with-memcached        Memcached library], [memcached=$withval])
    132 if test "$memcached" != "no" -a -n "$libgcryptversion" -a "$pkgconfigpath" != "NONE"; then
     101if test "$memcached" != "no" -a "$pkgconfigpath" != "NONE"; then
    133102    AC_MSG_CHECKING([for libmemcached])
    134103    if $pkgconfigpath --cflags libmemcached >/dev/null 2>&1 ; then
     
    151120    fi
    152121fi
     122dnl
     123dnl
     124dnl
    153125dnl ------ GNU TLS
    154126AC_SUBST([SSL_CFLAGS])
  • yaz/trunk/fuentes/debian/.gitignore

    r255 r265  
    1313*.postinst.debhelper
    1414*.postrm.debhelper
     15copyright
     16files
     17libyaz5
     18libyaz5-dbg
     19libyaz5-dev
     20yaz-icu
     21yaz-illclient
     22tmp
     23yaz
     24yaz-doc
     25*.debhelper.log
     26*.substvars
     27*.postinst.debhelper
     28*.postrm.debhelper
  • yaz/trunk/fuentes/debian/changelog

    r256 r265  
     1yaz (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
    17yaz (5.14.3-1.indexdata+lliurex3) xenial; urgency=medium
    28
  • yaz/trunk/fuentes/debian/compat

    r255 r265  
     19
    127
  • yaz/trunk/fuentes/debian/control

    r255 r265  
     1Source: yaz
     2Section: devel
     3Standards-Version: 3.6.2
     4Maintainer: Adam Dickmeiss <adam@indexdata.dk>
     5Priority: extra
     6Build-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
     16Package: libyaz5
     17Section: libs
     18Architecture: any
     19Depends: ${shlibs:Depends}
     20Conflicts: idzebra (<= 1.3.4-2), php4-yaz (<= 4.1.2-5)
     21Description: 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
     27Package: libyaz5-dbg
     28Section: debug
     29Architecture: any
     30Depends: libyaz5 (= ${binary:Version}), ${misc:Depends}
     31Description: 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
     37Package: yaz
     38Section: utils
     39Architecture: any
     40Depends: ${shlibs:Depends}
     41Conflicts: yaz-runtime, yaz-ssl
     42Description: 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
     48Package: yaz-doc
     49Section: doc
     50Architecture: all
     51Description: 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
     57Package: libyaz5-dev
     58Depends: libyaz5 (= ${source:Version}),
     59        libxslt1-dev,
     60        libicu-dev,
     61        tclsh
     62Provides: libyaz-dev
     63Replaces: libyaz-dev
     64Conflicts: libyaz2-dev, libyaz3-dev, libyaz-dev
     65Section: libdevel
     66Architecture: any
     67Suggests: yaz-doc
     68Description: 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
     74Package: yaz-illclient
     75Section: utils
     76Depends: ${shlibs:Depends}
     77Architecture: any
     78Description: 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
     85Package: yaz-icu
     86Section: utils
     87Depends: ${shlibs:Depends}
     88Architecture: any
     89Description: 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
    196Source: yaz
    297Section: devel
  • yaz/trunk/fuentes/debian/libyaz5-dev.install

    r255 r265  
     1debian/tmp/usr/include/yaz
     2debian/tmp/usr/lib/*/pkgconfig/yaz.pc
     3debian/tmp/usr/lib/*/libyaz*.a
     4debian/tmp/usr/lib/*/libyaz*.so
     5debian/tmp/usr/bin/yaz-config
     6debian/tmp/usr/bin/yaz-asncomp
     7debian/tmp/usr/share/aclocal/yaz.m4
     8debian/tmp/usr/share/yaz
    19debian/tmp/usr/include/yaz
    210debian/tmp/usr/lib/pkgconfig/yaz.pc
  • yaz/trunk/fuentes/debian/libyaz5-dev.manpages

    r255 r265  
    22debian/tmp/usr/share/man/man7/yaz.7
    33debian/tmp/usr/share/man/man1/yaz-config.1
     4debian/tmp/usr/share/man/man1/yaz-asncomp.1
     5debian/tmp/usr/share/man/man7/yaz.7
     6debian/tmp/usr/share/man/man1/yaz-config.1
  • yaz/trunk/fuentes/debian/libyaz5.install

    r255 r265  
     1debian/tmp/usr/lib/*/lib*.so.*
    12debian/tmp/usr/lib/lib*.so.*
  • yaz/trunk/fuentes/debian/rules

    r255 r265  
     1#!/usr/bin/make -f
     2export DH_VERBOSE=1
     3
     4%:
     5        dh $@ --without python-support
     6
     7override_dh_auto_configure:
     8        dh_auto_configure -- \
     9                --enable-tcpd --with-xslt --with-gnutls --with-icu \
     10                --with-memcached --with-redis
     11
     12override_dh_strip:
     13        dh_strip --dbg-package=libyaz5-dbg
     14
     15override_dh_auto_install:
     16        dh_auto_install
     17        mv debian/tmp/usr/share/doc/yaz debian/tmp/usr/share/doc/yaz-doc
     18
     19override_dh_makeshlibs:
     20        dh_makeshlibs -V 'libyaz5 (>= 5.13.0)'
     21
     22override_dh_installchangelogs:
     23        dh_installchangelogs NEWS
     24
     25override_dh_installdocs:
     26        cp LICENSE debian/copyright
     27        dh_installdocs -A README.md
    128#!/usr/bin/make -f
    229export DH_VERBOSE=1
  • yaz/trunk/fuentes/debian/yaz-doc.install

    r255 r265  
    11debian/tmp/usr/share/doc/yaz-doc
    22debian/tmp/usr/share/doc/yaz-doc/common
     3debian/tmp/usr/share/doc/yaz-doc
     4debian/tmp/usr/share/doc/yaz-doc/common
  • yaz/trunk/fuentes/debian/yaz-icu.install

    r255 r265  
    11debian/tmp/usr/bin/yaz-icu
     2debian/tmp/usr/bin/yaz-icu
  • yaz/trunk/fuentes/debian/yaz-icu.manpages

    r255 r265  
    11debian/tmp/usr/share/man/man1/yaz-icu.1
     2debian/tmp/usr/share/man/man1/yaz-icu.1
  • yaz/trunk/fuentes/debian/yaz-illclient.install

    r255 r265  
    11debian/tmp/usr/bin/yaz-illclient
     2debian/tmp/usr/bin/yaz-illclient
  • yaz/trunk/fuentes/debian/yaz-illclient.manpages

    r255 r265  
    11debian/tmp/usr/share/man/man1/yaz-illclient.1
     2debian/tmp/usr/share/man/man1/yaz-illclient.1
  • yaz/trunk/fuentes/debian/yaz.install

    r255 r265  
    66debian/tmp/usr/bin/yaz-json-parse
    77debian/tmp/usr/bin/yaz-url
     8debian/tmp/usr/bin/yaz-client
     9debian/tmp/usr/bin/yaz-ztest
     10debian/tmp/usr/bin/zoomsh
     11debian/tmp/usr/bin/yaz-marcdump
     12debian/tmp/usr/bin/yaz-iconv
     13debian/tmp/usr/bin/yaz-json-parse
     14debian/tmp/usr/bin/yaz-url
  • yaz/trunk/fuentes/debian/yaz.manpages

    r255 r265  
    88debian/tmp/usr/share/man/man1/yaz-json-parse.1
    99debian/tmp/usr/share/man/man1/yaz-url.1
     10debian/tmp/usr/share/man/man1/yaz-client.1
     11debian/tmp/usr/share/man/man8/yaz-ztest.8
     12debian/tmp/usr/share/man/man1/zoomsh.1
     13debian/tmp/usr/share/man/man1/yaz-marcdump.1
     14debian/tmp/usr/share/man/man1/yaz-iconv.1
     15debian/tmp/usr/share/man/man7/yaz-log.7
     16debian/tmp/usr/share/man/man7/bib1-attr.7
     17debian/tmp/usr/share/man/man1/yaz-json-parse.1
     18debian/tmp/usr/share/man/man1/yaz-url.1
  • yaz/trunk/fuentes/doc/Makefile.in

    r255 r265  
    238238EXEEXT = @EXEEXT@
    239239FGREP = @FGREP@
    240 GCRYPT_LIBS = @GCRYPT_LIBS@
    241240GREP = @GREP@
    242241HIREDIS_LIBS = @HIREDIS_LIBS@
     
    340339libdir = @libdir@
    341340libexecdir = @libexecdir@
    342 libgcrypt = @libgcrypt@
    343341localedir = @localedir@
    344342localstatedir = @localstatedir@
  • yaz/trunk/fuentes/doc/asn.external.html

    r255 r265  
    5959    <code class="literal">octet_aligned</code> arm of the union.
    6060   </p><p>
    61     Some servers return ASN.1 structured data values (eg. database
     61    Some servers return ASN.1 structured data values (e.g. database
    6262    records) as BER-encoded records placed in the
    6363    <code class="literal">octet-aligned</code> branch of the EXTERNAL CHOICE.
     
    6868   Z_ext_typeent *z_ext_gettypebyref(const oid *oid);
    6969   </pre><p>
    70     Can be used to retrieve information about the known, external data
    71     types. The function return a pointer to a static area, or NULL, if no
     70    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
    7272    match for the given direct reference is found. The
    7373    <code class="literal">Z_ext_typeent</code>
     
    9999   </p><p>
    100100    If you want to <span class="emphasis"><em>send</em></span> EXTERNALs containing
    101     ASN.1-structured values in the occtet-aligned branch of the CHOICE, this
     101    ASN.1-structured values in the octet-aligned branch of the CHOICE, this
    102102    is possible too. However, on the encoding phase, it requires a somewhat
    103103    involved juggling around of the various buffers involved.
  • yaz/trunk/fuentes/doc/asn.html

    r255 r265  
    1111   </p><p>
    1212    The Z39.50 ASN.1 module is located in sub directory <code class="filename">z39.50</code>.
    13     There you'll find C files that implements encoders and decoders for the
     13    There you'll find C files that implement encoders and decoders for the
    1414    Z39.50 types. You'll also find the protocol definitions:
    1515    <code class="filename">z3950v3.asn</code>, <code class="filename">esupdate.asn</code>,
  • yaz/trunk/fuentes/doc/asn.preparing.html

    r255 r265  
    3131    <code class="function">odr_malloc()</code>, you can release all of the
    3232    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 a
    34     "nibble-memory"
     33    relations between the data. The <code class="function">odr_malloc()</code> function
     34    is based on a "nibble-memory"
    3535    scheme, in which large portions of memory are allocated, and then
    3636    gradually handed out with each call to <code class="function">odr_malloc()</code>.
     
    6969    Z_&lt;type&gt; *zget_&lt;type&gt;(ODR o);
    7070   </pre><p>
    71     eg.:
     71    e.g.:
    7272   </p><pre class="synopsis">
    7373    Z_InitRequest *zget_InitRequest(ODR o);
  • yaz/trunk/fuentes/doc/bib1-attr-man.xml

    r255 r265  
    1313  <productname>YAZ</productname>
    1414  <productnumber>&version;</productnumber>
    15   <info><orgname>Index Data</orgname></info>
     15  <orgname>Index Data</orgname>
    1616 </refentryinfo>
    1717
     
    3535 <refsect1><title>TYPES</title>
    3636  <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).
    3939  </para>
    4040 </refsect1>
     
    219219 </refsect1>
    220220
    221  <refsect1><title>COMPLETENSS (6)</title>
     221 <refsect1><title>COMPLETENESS (6)</title>
    222222  <para>
    223223   <screen>
  • yaz/trunk/fuentes/doc/bib1-attr.7

    r255 r265  
    33.\"    Author: Index Data
    44.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
    5 .\"      Date: 06/29/2015
     5.\"      Date: 01/11/2016
    66.\"    Manual: Conventions and miscellaneous
    7 .\"    Source: YAZ 5.14.3
     7.\"    Source: YAZ 5.15.2
    88.\"  Language: English
    99.\"
    10 .TH "BIB\-1 ATTRIBUTE SET" "7" "06/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"
    1111.\" -----------------------------------------------------------------
    1212.\" * Define some portability stuff
     
    3535.SH "TYPES"
    3636.PP
    37 The Bib\-1 attribute defines six attribute types: Use (1), Relation (2), Position (3), Structure (4), Truncation (5) and completeness (6)\&.
     37The Bib\-1 attribute set defines six attribute types: Use (1), Relation (2), Position (3), Structure (4), Truncation (5) and Completeness (6)\&.
    3838.SH "USE (1)"
    3939.PP
     
    246246.\}
    247247.sp
    248 .SH "COMPLETENSS (6)"
     248.SH "COMPLETENESS (6)"
    249249.PP
    250250.if n \{\
     
    281281.PP
    282282\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
    283286.SH "NOTES"
    284287.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 &#8212; Bib-1 Attribute Set</p></div><div class="refsect1"><a name="idp48545008"></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 &#8212; Bib-1 Attribute Set</p></div><div class="refsect1"><a name="idm46170480248784"></a><h2>DESCRIPTION</h2><p>
    22   This reference entry lists the Bib-1 attribute set types and values.
    3   </p></div><div class="refsect1"><a name="idp48546160"></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="idp48547376"></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>
    77   </p><pre class="screen">
    88    1     Personal-name
     
    106106    1036  Author-Title-Subject
    107107   </pre><p>
    108   </p></div><div class="refsect1"><a name="idp48554048"></a><h2>RELATION (2)</h2><p>
     108  </p></div><div class="refsect1"><a name="idm46170480239744"></a><h2>RELATION (2)</h2><p>
    109109   </p><pre class="screen">
    110110    1 Less than
     
    119119    103 AlwaysMatches
    120120   </pre><p>
    121   </p></div><div class="refsect1"><a name="idp48555968"></a><h2>POSITION (3)</h2><p>
     121  </p></div><div class="refsect1"><a name="idm46170480237824"></a><h2>POSITION (3)</h2><p>
    122122   </p><pre class="screen">
    123123    1 First in field
     
    125125    3 Any position in field
    126126   </pre><p>
    127   </p></div><div class="refsect1"><a name="idp48557776"></a><h2>STRUCTURE (4)</h2><p>
     127  </p></div><div class="refsect1"><a name="idm46170480236016"></a><h2>STRUCTURE (4)</h2><p>
    128128   </p><pre class="screen">
    129129    1 Phrase
     
    144144    109 Numeric-string
    145145   </pre><p>
    146   </p></div><div class="refsect1"><a name="idp48559808"></a><h2>TRUNCATION (5)</h2><p>
     146  </p></div><div class="refsect1"><a name="idm46170480233984"></a><h2>TRUNCATION (5)</h2><p>
    147147   </p><pre class="screen">
    148148    1 Right truncation
     
    162162    106 Process * ! regular: *=.*, !=.
    163163   </pre><p>
    164   </p></div><div class="refsect1"><a name="idp48563056"></a><h2>COMPLETENSS (6)</h2><p>
     164  </p></div><div class="refsect1"><a name="idm46170480230736"></a><h2>COMPLETENESS (6)</h2><p>
    165165   </p><pre class="screen">
    166166    1 Incomplete subfield
     
    168168    3 Complete field
    169169   </pre><p>
    170   </p></div><div class="refsect1"><a name="idp48564864"></a><h2>SORTING (7)</h2><p>
     170  </p></div><div class="refsect1"><a name="idm46170480228928"></a><h2>SORTING (7)</h2><p>
    171171   </p><pre class="screen">
    172172    1 ascending
     
    176176    Type 7 is an Index Data extension to RPN queries that allows
    177177    embedding a sort critieria into a query.
    178   </p></div><div class="refsect1"><a name="idp48567184"></a><h2>SEE ALSO</h2><p>
     178  </p></div><div class="refsect1"><a name="idm46170480226608"></a><h2>SEE ALSO</h2><p>
    179179   <a class="ulink" href="http://www.loc.gov/z3950/agency/defns/bib1.html" target="_top">Bib-1 Attribute Set</a>
    180180  </p><p>
  • yaz/trunk/fuentes/doc/book.xml

    r255 r265  
    7979     <para>
    8080      Supports
    81       <ulink url="&url.solr;">Solr</ulink> Web Service version 1.4.x
     81      <ulink url="&url.solr;">Apache Solr</ulink> Web Service version 1.4.x
    8282      (client side only)
    8383     </para>
     
    139139   <para>
    140140    Most implementors only need to read a fraction of the
    141     material in thie manual, so a quick walkthrough of the chapters
     141    material in this manual, so a quick walkthrough of the chapters
    142142    is in order.
    143143   </para>
     
    146146     <para>
    147147      <xref linkend="installation"/> contains installation
    148       instructions for &yaz;. You don't need reading this
     148      instructions for &yaz;. You don't need to read this
    149149      if you expect to download &yaz; binaries.
    150150      However, the chapter contains information about how
     
    156156     <para>
    157157      <xref linkend="zoom"/> describes the ZOOM API of &yaz;.
    158       This is definitely worth a read if you wish to develop a Z39.50/SRU
     158      This is definitely worth reading if you wish to develop a Z39.50/SRU
    159159      client.
    160160     </para>
     
    170170     <para>
    171171      <xref linkend="yaz-client"/> describes how to use the &yaz; Z39.50
    172       client. If you're developer and wish to test your server
     172      client. If you're a developer and wish to test your server
    173173      or a server from another party, you might find this chapter
    174174      useful.
     
    203203      ODR module which is the work horse that encodes and decodes
    204204      BER packages. Implementors using ZOOM only, do <emphasis>not</emphasis>
    205       need reading this.
     205      need to read this.
    206206      Most other Z39.50 implementors only need to read the first two
    207207      sections (<xref linkend="odr.introduction"/> and
     
    245245   </para>
    246246   <para>
    247     The YAZ toolkit modules is shown in figure <xref linkend="yaz.layer"/>.
     247    The YAZ toolkit modules are shown in figure <xref linkend="yaz.layer"/>.
    248248   </para>
    249249   <figure id="yaz.layer">
     
    326326    <para>
    327327     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 you
     328     are not adding a new protocol of your own, the only parts of &odr; that you
    329329     need to worry about are documented in
    330330     <xref linkend="odr.use"/>.
     
    384384    <ulink url="&url.freebsd;">FreeBSD (i386)</ulink>,
    385385    <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,
    391390    DEC Unix, <ulink url="&url.netbsd;">NetBSD</ulink>,
    392391    <ulink url="&url.openbsd;">OpenBSD</ulink>,
     
    464463    <title>Compiling from source on Unix</title>
    465464    <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"/>.
    469469    </para>
    470470    <para>
     
    497497     <ulink url="&url.libtool;">Libtool</ulink>
    498498     are used to generate Makefiles and configure &yaz; for the system.
    499      You do <emphasis>not</emphasis> these tools unless you're using the
     499     You do <emphasis>not</emphasis> need these tools unless you're using the
    500500     Git version of &yaz;.
    501501    </para>
     
    509509     written in <ulink url="&url.tcl;">Tcl</ulink>.
    510510     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 built own codecs
     511     version of &yaz; or you're using the compiler to build your own codecs
    512512     for private ASN.1.
    513513    </para>
    514514    <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:
    517523    </para>
    518524    <screen>
     
    613619        search for iconv on the system. Use this option if it
    614620        doesn't find iconv. Alternatively,
    615         <literal>--without-iconv</literal>, can be uset to force &yaz;
     621        <literal>--without-iconv</literal>, can be used to force &yaz;
    616622        not to use iconv.
    617623        </para>
     
    628634        Use this option if you want XSLT and XML support.
    629635        By default, configure will
    630         search for libxslt on the system. Use this option if it
     636        search for libxslt on the system. Use this option if
    631637        libxslt is not found automatically. Alternatively,
    632638        <literal>--without-xslt</literal>, can be used to force &yaz;
     
    645651        Use this option if you want &yaz; to use XML and support SRU/Solr.
    646652        By default, configure will
    647         search for libxml2 on the system. Use this option if it
     653        search for libxml2 on the system. Use this option if
    648654        libxml2 is not found automatically. Alternatively,
    649655        <literal>--without-xml2</literal>, can be used to force &yaz;
     
    683689      <varlistentry>
    684690       <term>
    685         <literal>--with-libgcrypt</literal>[=<replaceable>prefix</replaceable>]
    686        </term>
    687        <listitem>
    688         <para>&yaz; will be linked with
    689         <ulink url="&url.libgcrypt;">Libgcrypt</ulink> in the prefix if given.
    690         If prefix is not given, the libraries exposed by the script
    691         <application>libgcrypt-config</application> will be used if found.
    692         </para>
    693        </listitem>
    694       </varlistentry>
    695       <varlistentry>
    696        <term>
    697691        <literal>--with-memcached</literal>
    698692       </term>
     
    701695        <ulink url="&url.libmemcached;">libMemcached</ulink> to allow
    702696        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.
    705698        Note that 0.40 of libmemcached is required.
    706699       </para>
     
    715708        to allow for result-set caching for ZOOM on a
    716709        <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.
    719711       </para>
    720712       </listitem>
     
    858850     applications using the &yaz; toolkit.
    859851     If you're used to Makefiles this shouldn't be hard. As for
    860      other libraries you have used before, you have to set a proper include
     852     other libraries you have used before, you need to set a proper include
    861853     path for your C/C++ compiler and specify the location of
    862854     &yaz; libraries. You can do it by hand, but generally we suggest
     
    929921   <para>The easiest way to install YAZ on Windows is by downloading
    930922   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>.
    932926   The installer comes with source too - in case you wish to
    933927   compile YAZ with different compiler options, etc.
     
    940934     with <ulink url="&url.vstudio;">
    941935     Microsoft Visual Studio</ulink>. It has been tested with
    942      Microsoft Visual Studio 2013.
     936     Microsoft Visual Studio 2015.
    943937    </para>
    944938    <para>
     
    984978       </para>
    985979       <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>.
    988985       </para></listitem>
    989986      </varlistentry>
     
    10271024        <note>
    10281025         <para>
    1029           libxslt depends libxml2.
     1026          libxslt depends on libxml2.
    10301027         </para>
    10311028        </note>
     
    10421039         <literal>ICU_DIR</literal> to the
    10431040         <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>.
    10441049        </para>
    10451050       </listitem>
     
    11391144       <listitem><para>This program exposes the ICU wrapper library if that
    11401145       is enabled for YAZ. Only if ICU is available this program is
    1141        build.
     1146       built.
    11421147      </para></listitem>
    11431148      </varlistentry>
     
    11551160       <filename>bin/zoomtst2.exe</filename>, ..</term>
    11561161       <listitem><para>
    1157         Several small applications that demonstrates the ZOOM API.
     1162        Several small applications that demonstrate the ZOOM API.
    11581163      </para></listitem>
    11591164      </varlistentry>
     
    12981303   became available,
    12991304   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
    13011307   chapter describes the &zoom; C binding. Before going further, please
    13021308   reconsider whether C is the right programming language for the job.
     
    13171323   such as C++, Java, etc. For example, you'll have to manually,
    13181324   destroy all objects you create, even though you may think of them as
    1319    temporary. Most objects has a <literal>_create</literal> - and a
     1325   temporary. Most objects have a <literal>_create</literal> - and a
    13201326   <literal>_destroy</literal> variant.
    13211327   All objects are in fact pointers to internal stuff, but you don't see
     
    13621368    default scheme is <literal>tcp</literal> (Z39.50 protocol).
    13631369    The scheme <literal>http</literal> selects SRU/get over HTTP by default,
    1364     but can overridded to use SRU/post, SRW and the Solr protocol.
     1370    but can overridden to use SRU/post, SRW, and the Solr protocol.
    13651371   </para>
    13661372   <para>
     
    14501456       encoded in the otherInfo area of a Z39.50 PDU with OID
    14511457       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.
    14531459      </entry><entry>none</entry></row>
    14541460      <row><entry>
     
    14891495      <row><entry>
    14901496       databaseName</entry><entry>One or more database names
    1491        separated by character plus (<literal>+</literal>), which to
     1497       separated by character plus (<literal>+</literal>), which is to
    14921498       be used by subsequent search requests on this Connection.
    14931499      </entry><entry>Default</entry></row>
     
    15061512      <row><entry>
    15071513       mediumSetPresentNumber</entry><entry>This value represents
    1508        the number of records to be returned as part of a search when when
     1514       the number of records to be returned as part of a search when
    15091515       hits is less than or equal to large set lower bound and if hits
    15101516       is greater than small set upper bound.
     
    15161522      <row><entry>
    15171523       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.
    15191525      </entry><entry>none</entry></row>
    15201526      <row><entry>
     
    15331539       sru_version</entry><entry>
    15341540       SRU/SRW version. Should be <literal>1.1</literal>, or
    1535        <literal>1.2</literal>. This is , prior to connect, the version
     1541       <literal>1.2</literal>. This is, prior to connect, the version
    15361542       to offer (highest version). And following connect (in fact
    15371543       first operation), holds the negotiated version with the server
     
    15451551      <row id="zoom.facets.option"><entry>
    15461552       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.
    15481554       The value of this setting is described in <xref linkend="facets"/>
    15491555       For inspection of the facets returned, refer to the functions
     
    16051611       option is supplied for an earlier version of YAZ, it is
    16061612       <emphasis>ignored</emphasis>.
    1607        The value of this option is a set options, similar to that
     1613       The value of this option is a set of options, similar to that
    16081614       of the memcached setting. At this stage only --server=host[:port]
    1609        and --expire=seconds is supported.
     1615       and --expire=seconds are supported.
    16101616      </entry><entry>none</entry></row>
    16111617     </tbody>
     
    16411647     <function>ZOOM_connection_connect</function> establishes a TCP/IP
    16421648     connection and sends an Initialize Request to the target if
    1643      possible. In addition, the calls waits for an Initialize Response
     1649     possible. In addition, the calls wait for an Initialize Response
    16441650     from the target and the result is inspected (OK or rejected).
    16451651    </para>
     
    16771683    <title>SRU/Solr Protocol behavior</title>
    16781684    <para>
    1679      The HTTP based protocols (SRU, SRW, Solr) doesn't feature an
     1685     The HTTP based protocols (SRU, SRW, Solr) do not feature an
    16801686     Inititialize Request, so  the connection phase merely establishes a
    16811687     TCP/IP connection with the HTTP server.
     
    17431749    <function>ZOOM_query_sortby</function> but allows a strategy for
    17441750    sorting. The reason for the strategy parameter is that some
    1745     protocols offers multiple ways of performing sorting.
     1751    protocols offer multiple ways of performing sorting.
    17461752    For example, Z39.50 has the standard sort, which is performed after
    17471753    search on an existing result set.
     
    17991805   <para>
    18001806    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.
    18021808    Destroy a result set by calling
    18031809    <function>ZOOM_resultset_destroy</function>.
    1804     Simple clients may using PQF only may use function
     1810    Simple clients using PQF only, may use the function
    18051811    <function>ZOOM_connection_search_pqf</function> in which case
    18061812    creating query objects is not necessary.
     
    18211827   </para>
    18221828   <para>
    1823     The number of hits also called result-count is returned by
     1829    The number of hits, also called result-count, is returned by
    18241830    function <function>ZOOM_resultset_size</function>.
    18251831   </para>
     
    19191925       <entry>searchresult.size</entry>
    19201926       <entry>
    1921         number of search result entries. This option is-nonexistant
     1927        number of search result entries. This option is non-existent
    19221928        if no entries are returned by the server.
    19231929       </entry>
     
    19621968     <function>ZOOM_resultset_sort</function> and
    19631969     <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".
    19651971     The sort_spec is same notation as ZOOM_query_sortby and identical
    19661972     to that offered by yaz-client's
     
    20052011     the result set with a given start offset. When you use this mode
    20062012     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.
    20082014     Even if the target returns fewer records as part of a present response
    20092015     because of a record size limit, etc. the client will repeat sending
     
    20312037     Current version of &yaz; does not take advantage of a result set id
    20322038     returned by the SRU server. Future versions might do, however.
    2033      Since, the ZOOM driver does not save result set IDs any
     2039     Since the ZOOM driver does not save result set IDs, any
    20342040     present (retrieval) is transformed to a SRU SearchRetrieveRequest
    20352041     with same query but, possibly, different offsets.
     
    20592065    </para>
    20602066    <para>
    2061      Solr queries has to be done in Solr query format.
    2062     </para>
    2063     <para>
    2064      Unfortunately, SRU or Solr does not 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,
    20652071     <literal>databaseName</literal> is unsupported and ignored.
    20662072     However, the path part in host parameter for functions
     
    21202126    a number of records from a result set. Parameter <literal>start</literal>
    21212127    and <literal>count</literal> specifies the range of records to
    2122     be returned. Upon completion array
     2128    be returned. Upon completion, the array
    21232129    <literal>recs[0], ..recs[count-1]</literal>
    21242130    holds record objects for the records. The array of records
    21252131     <literal>recs</literal> should be allocated prior the call
    21262132    <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,
    21282134    <literal>recs[ ..]</literal> is set to <literal>NULL</literal>.
    21292135   </para>
     
    21862192    <variablelist>
    21872193     <varlistentry><term><literal>database</literal></term>
    2188       <listitem><para>Database of record is returned
     2194      <listitem><para>The Database of the record is returned
    21892195        as a C null-terminated string. Return type
    21902196        <literal>const char *</literal>.
     
    22072213     <varlistentry><term><literal>render</literal></term>
    22082214      <listitem><para>The record is returned in a display friendly
    2209         format. Upon completion buffer is returned
     2215        format. Upon completion, buffer is returned
    22102216        (type <literal>const char *</literal>) and length is stored in
    22112217        <literal>*len</literal>.
     
    22862292     The functions may block (and perform network I/O)  - even though option
    22872293     <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!)
    22892295     </para>
    22902296    <para>
     
    23572363    <function>ZOOM_resultset_facets</function>. The length of the array is
    23582364    given by <function>ZOOM_resultset_facets_size</function>. The array is
    2359     zero-based and last entry will be at
     2365    zero-based and the last entry will be at
    23602366    <function>ZOOM_resultset_facets_size(result_set)</function>-1.
    23612367   </para>
     
    23632369    It is possible to interate over facets by name, by calling
    23642370    <function>ZOOM_resultset_facets_names</function>.
    2365     This will return an const array of char * where each string can be used
     2371    This will return a const array of char * where each string can be used
    23662372    as parameter for <function>ZOOM_resultset_get_facet_field</function>.
    23672373   </para>
     
    24222428    If the operation was successful, the size of the scan set can be
    24232429    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.
    24252431    To obtain information about a particular scan term, call function
    24262432    <function>ZOOM_scanset_term</function>. This function takes
     
    25422548   </itemizedlist>
    25432549   <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>
    25452551    must be created. The operation is a five step operation. The
    25462552    package is created, package is configured by means of options,
    2547     the package is send, result is inspected (by means of options),
     2553    the package is sent, result is inspected (by means of options),
    25482554    the package is destroyed.
    25492555   </para>
     
    26242630       <entry>package-name</entry>
    26252631       <entry>Extended Service Request package name. Must be specified
    2626        as part of a request</entry>
     2632       as part of a request.</entry>
    26272633       <entry>none</entry>
    26282634      </row>
    26292635      <row>
    26302636       <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>
    26322638       <entry>none</entry>
    26332639      </row>
     
    28692875          to record - and <literal>record</literal> option (above) is
    28702876          ignored if recordOpaque is set. This option is only available in
    2871           YAZ 3.0.35 and later and is meant to facilitate Updates with
     2877          YAZ 3.0.35 and later, and is meant to facilitate Updates with
    28722878          servers from OCLC.
    28732879        </entry>
     
    29963002    <note>
    29973003     <para>
    2998       The database create, drop and commit services are privately defined
     3004      The database create, drop, and commit services are privately defined
    29993005      operations.
    30003006      Refer to <filename>esadmin.asn</filename> in YAZ for the ASN.1
     
    30083014   <para>
    30093015    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 like
     3016    From an implementation point of view, a set of options is just like
    30113017    an associative array / hash.
    30123018   </para>
     
    30483054    <function>ZOOM_query_cql2rpn</function> translates the CQL string,
    30493055    client-side, into RPN which may be passed to the server.
    3050     This is useful for server's that don't themselves
     3056    This is useful for servers that don't themselves
    30513057    support CQL, for which <function>ZOOM_query_cql</function> is useless.
    3052     `conn' is used  only as a place to stash diagnostics if compilation
     3058    'conn' is used  only as a place to stash diagnostics if compilation
    30533059    fails; if this information is not needed, a null pointer may be used.
    30543060    The CQL conversion is driven by option <literal>cqlfile</literal> from
    3055     connection conn. This specifies a conversion file (eg pqf.properties)
     3061    connection conn. This specifies a conversion file (e.g. pqf.properties)
    30563062    which <emphasis>must</emphasis> be present.
    30573063   </para>
     
    30613067    The conversion is driven by the specification given by
    30623068    <literal>config</literal>. Upon completion 0 is returned on success; -1
    3063     is returned on on failure. Om failure <literal>error_string</literal> and
    3064     <literal>error_pos</literal> holds error message and position of
     3069    is returned on failure. On failure <literal>error_string</literal> and
     3070    <literal>error_pos</literal> hold the error message and position of
    30653071    first error in original CCL string.
    30663072   </para>
     
    30793085    <literal>no</literal> and an array of connections in
    30803086    <literal>cs</literal> (<literal>cs[0] ... cs[no-1]</literal>).
    3081     A pending event could be a sending a search, receiving a response,
     3087    A pending event could be sending a search, receiving a response,
    30823088    etc.
    30833089    When an event has occurred for one of the connections, this function
     
    30863092    When no events are pending for the connections, a value of zero is
    30873093    returned.
    3088     To ensure that all outstanding requests are performed call this function
     3094    To ensure that all outstanding requests are performed, call this function
    30893095    repeatedly until zero is returned.
    30903096   </para>
    30913097   <para>
    3092     If <function>ZOOM_event</function> returns and returns non-zero, the
     3098    If <function>ZOOM_event</function> returns, and returns non-zero, the
    30933099    last event that occurred can be expected.
    30943100   </para>
     
    31273133      <row>
    31283134       <entry>ZOOM_EVENT_RECV_DATA</entry>
    3129        <entry>Data has been received)</entry>
     3135       <entry>Data has been received</entry>
    31303136      </row>
    31313137      <row>
     
    31513157      <row>
    31523158       <entry>ZOOM_EVENT_RECV_SEARCH</entry>
    3153        <entry>A search result been received</entry>
     3159       <entry>A search result has been received</entry>
    31543160      </row>
    31553161     </tbody>
     
    31713177   <para>
    31723178    If you have a database system that you would like to make available by
    3173     means of Z39.50 or SRU, &yaz; basically offers your two options. You
     3179    means of Z39.50 or SRU, &yaz; basically offers two options. You
    31743180    can use the APIs provided by the &asn;, &odr;, and &comstack;
    31753181    modules to
     
    33163322       A boolean value, which determines whether the server
    33173323       will fork on each incoming request (TRUE), or not (FALSE). Default is
    3318        TRUE. This flag is only read by UNIX-based servers (WIN32 based servers
    3319        doesn't fork).
     3324       TRUE. This flag is only read by UNIX-based servers (WIN32-based servers
     3325       do not fork).
    33203326     </para></listitem>
    33213327     </varlistentry>
     
    33343340      <listitem><para>
    33353341       A boolean value, which determines whether the server
    3336        will operates under a UNIX INET daemon (inetd). Default is FALSE.
     3342       will operate under a UNIX INET daemon (inetd). Default is FALSE.
    33373343     </para></listitem>
    33383344     </varlistentry>
     
    33993405      command line options have been parsed - but before the server
    34003406      starts listening.
    3401       For forked UNIX servers this handler is called in the mother
    3402       process; for threaded servers this handler is called in the
     3407      For forked UNIX servers, this handler is called in the mother
     3408      process; for threaded servers, this handler is called in the
    34033409      main thread.
    34043410      The default value of this pointer is NULL in which case it
    34053411      isn't invoked by the frontend server.
    3406       When the server operates as an NT service this handler is called
     3412      When the server operates as an NT service, this handler is called
    34073413      whenever the service is started.
    34083414      </para></listitem>
     
    34153421      has stopped listening for incoming connections. This function pointer
    34163422      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 called
     3423      When the server operates as an NT service, this handler is called
    34183424      whenever the service is stopped.
    34193425      </para></listitem>
     
    34313437    The pointer returned by <literal>statserv_getcontrol</literal> points to
    34323438    a static area. You are allowed to change the contents of the structure,
    3433     but the changes will not take effect before you call
     3439    but the changes will not take effect until you call
    34343440   </para>
    34353441   <synopsis>
     
    34383444   <note>
    34393445    <para>
    3440      that you should generally update this structure before calling
     3446     You should generally update this structure before calling
    34413447     <function>statserv_main()</function>.
    34423448    </para>
     
    34703476     Unlike previous versions of YAZ, the <function>bend_init</function> also
    34713477     serves as a handler that defines the Z39.50 services that the backend
    3472      wish to support. Pointers to <emphasis>all</emphasis> service handlers,
     3478     intends to support. Pointers to <emphasis>all</emphasis> service handlers,
    34733479     including search - and fetch must be specified here in this handler.
    34743480    </para>
     
    35763582    <para>
    35773583     The <literal>auth</literal> member holds the authentication information
    3578      part of the Z39.50 Initialize Request. Interpret this if your serves
     3584     part of the Z39.50 Initialize Request. Interpret this if your server
    35793585     requires authentication.
    35803586    </para>
     
    36323638    <para>
    36333639     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.
    36353641     The <literal>setname</literal> is the resultSetName from the protocol.
    36363642     You are required to establish a mapping between the set name and whatever
     
    38033809    <title>Delete</title>
    38043810    <para>
    3805      For back-ends that supports delete of a result set only one handler
     3811     For back-ends that supports delete of a result set, only one handler
    38063812     must be defined.
    38073813    </para>
     
    38703876    This backend server handles both Z39.50 scan
    38713877    and SRU scan. In order for a handler to distinguish between SRU (CQL) scan
    3872     Z39.50 Scan , it must check for a non-NULL value of
     3878    Z39.50 Scan, it must check for a non-NULL value of
    38733879    <literal>scanClause</literal>.
    38743880   </para>
    38753881   <note>
    38763882    <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,
    38783884     but that would break binary compatibility with existing servers.
    38793885    </para>
     
    39553961    </para>
    39563962    <para>
    3957      The above for the Apache 1.3 series.
     3963     The above is for the Apache 1.3 series.
    39583964    </para>
    39593965   </example>
     
    39613967    <title>Running a server with local access only</title>
    39623968    <para>
    3963      Servers that is only being accessed from the local host should listen
    3964      on UNIX file socket rather than a Internet socket. To listen on
     3969     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
    39653971     <filename>/tmp/mysocket</filename> start the server as follows:
    39663972     <screen>
     
    39923998   <para>
    39933999    The &asn; module is located in sub directory <filename>z39.50</filename>.
    3994     There you'll find C files that implements encoders and decoders for the
     4000    There you'll find C files that implement encoders and decoders for the
    39954001    Z39.50 types. You'll also find the protocol definitions:
    39964002    <filename>z3950v3.asn</filename>, <filename>esupdate.asn</filename>,
     
    40364042    <function>odr_malloc()</function>, you can release all of the
    40374043    allocated data in a single operation, independent of any pointers and
    4038     relations between the data. <function>odr_malloc()</function> is based on a
    4039     &quot;nibble-memory&quot;
     4044    relations between the data. The <function>odr_malloc()</function> function
     4045    is based on a &quot;nibble-memory&quot;
    40404046    scheme, in which large portions of memory are allocated, and then
    40414047    gradually handed out with each call to <function>odr_malloc()</function>.
     
    40794085   </synopsis>
    40804086   <para>
    4081     eg.:
     4087    e.g.:
    40824088   </para>
    40834089   <synopsis>
     
    41684174   </para>
    41694175   <para>
    4170     Some servers return ASN.1 structured data values (eg. database
     4176    Some servers return ASN.1 structured data values (e.g. database
    41714177    records) as BER-encoded records placed in the
    41724178    <literal>octet-aligned</literal> branch of the EXTERNAL CHOICE.
     
    41794185   </screen>
    41804186   <para>
    4181     Can be used to retrieve information about the known, external data
    4182     types. The function return a pointer to a static area, or NULL, if no
     4187    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
    41834189    match for the given direct reference is found. The
    41844190    <literal>Z_ext_typeent</literal>
     
    42144220   <para>
    42154221    If you want to <emphasis>send</emphasis> EXTERNALs containing
    4216     ASN.1-structured values in the occtet-aligned branch of the CHOICE, this
     4222    ASN.1-structured values in the octet-aligned branch of the CHOICE, this
    42174223    is possible too. However, on the encoding phase, it requires a somewhat
    42184224    involved juggling around of the various buffers involved.
     
    49384944   <para>
    49394945    &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.
    49424948    The implementation uses the
    49434949    <ulink url="&url.libxml2.api.tree;">tree API</ulink> of
     
    50185024   <para>
    50195025    The <literal>fault</literal> and <literal>soap_error</literal>
    5020     arms represent both a SOAP fault - struct
     5026    arms both represent a SOAP fault - struct
    50215027    <literal>Z_SOAP_Fault</literal>. Any other generic
    50225028    (valid) package is represented by <literal>Z_SOAP_Generic</literal>.
     
    50485054    inspects the XML content
    50495055    and tries to match one of the services namespaces of the
    5050     supplied handlers. If there is a match a handler function
     5056    supplied handlers. If there is a match. a handler function
    50515057    is invoked which decodes that particular SOAP package.
    50525058    If successful, the returned <literal>Z_SOAP</literal> package will be
    50535059    of type <literal>Z_SOAP_Generic</literal>.
    50545060    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 pointer
     5061    set the offset of the handler that matched; <literal>ns</literal>
     5062    is set to namespace of the matching handler; the void pointer
    50575063    <literal>p</literal> is set to the C data structure assocatiated
    50585064    with the handler.
    50595065   </para>
    50605066   <para>
    5061     When a NULL namespace is met (member <literal>ns</literal> bwlow),
     5067    When a NULL namespace is met (member <literal>ns</literal> below),
    50625068    that specifies end-of-list.
    50635069   </para>
     
    50715077} Z_SOAP_Handler;
    50725078    </synopsis>
    5073     The <literal>ns</literal> is namespace of service associated with
    5074     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.
    50765082   </para>
    50775083   <para>
     
    50865092    and is a pointer to the <literal>Body</literal> element
    50875093    of the SOAP package. The <parameter>handler_data</parameter>
    5088     is an opaque pointer to a C definitions associated with the
    5089     SOAP service. <parameter>client_data</parameter> is the pointer
     5094    is an opaque pointer to C definitions associated with the
     5095    SOAP service. The <parameter>client_data</parameter> is the pointer
    50905096    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.
    50925098   </para>
    50935099  </sect1>
     
    51505156    as a char pointer (<literal>char *</literal>). A null pointer
    51515157    means that the element is absent.
    5152     Data of type xsd:integer is representd as a pointer to
     5158    Data of type xsd:integer is represented as a pointer to
    51535159    an int (<literal>int *</literal>). Again, a null pointer
    5154     us used for absent elements.
     5160    is used for absent elements.
    51555161   </para>
    51565162   <para>
     
    51715177    </synopsis>
    51725178    The <literal>num_records</literal> and <literal>num_diagnostics</literal>
    5173     is number of returned records and diagnostics respectively and also
     5179    is number of returned records and diagnostics respectively, and also
    51745180    correspond to the "size of" arrays <literal>records</literal>
    51755181    and <literal>diagnostics</literal>.
     
    52045210  <para>
    52055211   In support of the service API - primarily the ASN module, which
    5206    provides the pro-grammatic interface to the Z39.50 APDUs, &yaz; contains
     5212   provides the programmatic interface to the Z39.50 APDUs, &yaz; contains
    52075213   a collection of tools that support the development of applications.
    52085214  </para>
     
    52335239    <note>
    52345240     <para>
    5235       The PQF have been adopted by other parties developing Z39.50
     5241      The PQF has been adopted by other parties developing Z39.50
    52365242      software. It is often referred to as Prefix Query Notation
    52375243      - PQN.
     
    52405246    <para>
    52415247     The PQF is defined by the pquery module in the YAZ library.
    5242      There are two sets of function that have similar behavior. First
     5248     There are two sets of functions that have similar behavior. First
    52435249     set operates on a PQF parser handle, second set doesn't. First set
    5244      set of functions are more flexible than the second set. Second set
     5250     of functions are more flexible than the second set. Second set
    52455251     is obsolete and is only provided to ensure backwards compatibility.
    52465252    </para>
     
    52665272     <function>yaz_pqf_create</function> and
    52675273     <function>yaz_pqf_destroy</function> respectively.
    5268      Function <function>yaz_pqf_parse</function> parses query given
     5274     Function <function>yaz_pqf_parse</function> parses the query given
    52695275     by string <literal>qbuf</literal>. If parsing was successful,
    52705276     a Z39.50 RPN Query is returned which is created using ODR stream
     
    52805286     <function>yaz_pqf_error</function> which returns an error code and
    52815287     modifies <literal>*msg</literal> to point to an error description,
    5282      and modifies <literal>*off</literal> to the offset within last
    5283      query were parsing failed.
     5288     and modifies <literal>*off</literal> to the offset within the last
     5289     query where parsing failed.
    52845290    </para>
    52855291    <para>
     
    53705376     an attribute type, an equals sign, and an attribute value, like this:
    53715377     <literal>@attr 1=1003</literal>.
    5372      The type is always an integer but the value may be either an
     5378     The type is always an integer, but the value may be either an
    53735379     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"
    53755381     attribute with the list of values containing the single string
    53765382     specified, and including no semantic indicators.
     
    54245430       @prox <replaceable>exclusion</replaceable> <replaceable>distance</replaceable> <replaceable>ordered</replaceable> <replaceable>relation</replaceable> <replaceable>which-code</replaceable> <replaceable>unit-code</replaceable>
    54255431      </screen>
    5426       in which the meanings of the parameters are as described in in
     5432      in which the meanings of the parameters are as described in
    54275433      the standard, and they can take the following values:
    54285434      <itemizedlist>
     
    54715477        <literal>k</literal>
    54725478        (the unit-code parameter is taken from the well-known list
    5473         of alternatives described in below) or
     5479        of alternatives described below) or
    54745480        <literal>private</literal>
    54755481        or
    54765482        <literal>p</literal>
    5477         (the unit-code paramater has semantics specific to an
     5483        (the unit-code parameter has semantics specific to an
    54785484        out-of-band agreement such as a profile).
    54795485       </para>
     
    55855591        <listitem>
    55865592         <para>
    5587           which-code is ``known'', so the standard unit-codes are used
     5593          which-code is "known", so the standard unit-codes are used
    55885594         </para>
    55895595        </listitem>
     
    55965602       both occur in the record, in that order, differing in position
    55975603       by three or fewer words (i.e. with two or fewer words between
    5598        them.)  The query would find ``Bob Dylan, aka. Robert
    5599        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"
    56005606       since the distance in this case is four.
    56015607      </para>
     
    56255631       2038 indicates West Bounding Coordinate and
    56265632       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.
    56295635      </para>
    56305636     </example>
     
    56455651     <para>
    56465652      The CCL parser obeys the following grammar for the FIND argument.
    5647       The syntax is annotated by in the lines prefixed by
     5653      The syntax is annotated using lines prefixed by
    56485654      <literal>--</literal>.
    56495655     </para>
     
    57115717      </screen>
    57125718      <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:
    57165722      </para>
    57175723      <screen>
     
    57575763      <para>
    57585764       where <replaceable>qualifier-name</replaceable> is the name of the
    5759        qualifier to be used (eg. <literal>ti</literal>),
     5765       qualifier to be used (e.g. <literal>ti</literal>),
    57605766       <replaceable>type</replaceable> is attribute type in the attribute
    57615767       set (Bib-1 is used if no attribute set is given) and
    57625768       <replaceable>val</replaceable> is attribute value.
    57635769       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:
    57655771       <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,
    57685774       or <literal>c</literal> for completeness.
    57695775       The attributes for the special qualifier name <literal>term</literal>
     
    57865792            Use attribute (1). Common use attributes are
    57875793            1 Personal-name, 4 Title, 7 ISBN, 8 ISSN, 30 Date,
    5788             62 Subject, 1003 Author), 1016 Any. Specify value
     5794            62 Subject, 1003 Author, 1016 Any. Specify value
    57895795            as an integer.
    57905796           </entry>
     
    58195825           <entry>
    58205826            Truncation attribute (5). Values: 1 right, 2 left,
    5821             3 left&amp; right, 100 none, 101 process #, 102 regular-1,
     5827            3 left and right, 100 none, 101 process #, 102 regular-1,
    58225828            103 regular-2, 104 CCL.
    58235829           </entry>
     
    58645870           <entry><literal>s=al</literal></entry>
    58655871           <entry>
    5866             Each token in the term is ANDed. (and-list).
     5872            Each token in the term is ANDed (and-list).
    58675873            This does not set the structure at all.
    58685874           </entry>
     
    58705876          <row><entry><literal>s=ol</literal></entry>
    58715877          <entry>
    5872            Each token in the term is ORed. (or-list).
     5878           Each token in the term is ORed (or-list).
    58735879           This does not set the structure at all.
    58745880          </entry>
     
    58935899          <row><entry><literal>r=o</literal></entry>
    58945900          <entry>
    5895            Allows ranges and the operators greather-than, less-than, ...
     5901           Allows ranges and the operators greater-than, less-than, ...
    58965902           equals.
    58975903           This sets Bib-1 relation attribute accordingly (relation
     
    59195925          <entry>
    59205926           This will omit relation=equals (@attr 2=3) when r=o / r=r
    5921            is used. This is useful for servers that somehow breaks
     5927           is used. This is useful for servers that somehow break
    59225928           when an explicit relation=equals is used. Omitting the
    59235929           relation is usually safe because "equals" is the default
     
    59475953          <row><entry><literal>t=b</literal></entry>
    59485954          <entry>
    5949            Allows term to be both left&amp;right truncated.
     5955           Allows term to be both left-and-right truncated.
    59505956           If term is of the form <literal>?x?</literal>, the
    59515957           resulting term is <literal>x</literal> and trunctation is
    5952            set to both left&amp;right.
     5958           set to both left and right.
    59535959          </entry>
    59545960          </row>
     
    59575963           Allows masking anywhere in a term, thus fully supporting
    59585964           # (mask one character) and ? (zero or more of any).
    5959            If masking is used, trunction is set to 102 (regexp-1 in term)
     5965           If masking is used, truncation is set to 102 (regexp-1 in term)
    59605966           and the term is converted accordingly to a regular expression.
    59615967          </entry>
     
    59655971           Allows masking anywhere in a term, thus fully supporting
    59665972           # (mask one character) and ? (zero or more of any).
    5967            If masking is used, trunction is set to 104 (Z39.58 in term)
     5973           If masking is used, truncation is set to 104 (Z39.58 in term)
    59685974           and the term is converted accordingly to Z39.58 masking term -
    59695975           actually the same truncation as CCL itself.
     
    59925998        sets the use-attribute to 4. <literal>au</literal> sets the
    59935999        use-attribute to 1.
    5994         When no qualifiers are used in the query the structure-attribute is
     6000        When no qualifiers are used in the query, the structure-attribute is
    59956001        set to free-form-text (105) (rule for <literal>term</literal>).
    59966002        The <literal>date</literal> sets the relation attribute to
     
    61416147      which takes the CCL profile (<literal>bibset</literal>) and query
    61426148      (<literal>str</literal>) as input. Upon successful completion the RPN
    6143       tree is returned. If an error occur, such as a syntax error, the integer
     6149      tree is returned. If an error occurs, such as a syntax error, the integer
    61446150      pointed to by <literal>error</literal> holds the error code and
    61456151      <literal>pos</literal> holds the offset inside query string in which
     
    62616267      </synopsis>
    62626268      The functions <function>cql_parser_stream</function> and
    6263       <function>cql_parser_stdio</function> parses a CQL query
     6269      <function>cql_parser_stdio</function> parse a CQL query
    62646270      - just like <function>cql_parser_string</function>.
    62656271      The only difference is that the CQL query can be
     
    62736279     <title>CQL tree</title>
    62746280     <para>
    6275       The the query string is valid, the CQL parser
     6281      If the query string is valid, the CQL parser
    62766282      generates a tree representing the structure of the
    62776283      CQL query.
     
    62816287struct cql_node *cql_parser_result(CQL_parser cp);
    62826288      </synopsis>
    6283       <function>cql_parser_result</function> returns the
     6289      <function>cql_parser_result</function> returns
    62846290      a pointer to the root node of the resulting tree.
    62856291     </para>
     
    64396445      <literal>*addinfop</literal> to point to a string containing
    64406446      additional information about the error that occurred: for
    6441       example, if the error code is 15 (``Illegal or unsupported context
    6442       set''), the additional information is the name of the requested
     6447      example, if the error code is 15 ("Illegal or unsupported context
     6448      set"), the additional information is the name of the requested
    64436449      context set that was not recognised.
    64446450     </para>
     
    65166522         </para>
    65176523         <para>
    6518           For terms not bound by an index the pattern
     6524          For terms not bound by an index, the pattern
    65196525          <literal>index.cql.serverChoice</literal> is used.
    65206526          Here, the prefix <literal>cql</literal> is defined as
     
    65486554         <para>
    65496555          This pattern specifies how a CQL relation is mapped to RPN.
    6550           <replaceable>pattern</replaceable> is name of relation
     6556          The <replaceable>pattern</replaceable> is name of relation
    65516557          operator. Since <literal>=</literal> is used as
    65526558          separator between CQL pattern and RPN, CQL relations
     
    65896595         <para>
    65906596          This pattern specifies how a CQL structure is mapped to RPN.
    6591           Note that this CQL pattern is somewhat to similar to
     6597          Note that this CQL pattern is somewhat similar to
    65926598          CQL pattern <literal>relation</literal>.
    65936599          The <replaceable>type</replaceable> is a CQL relation.
     
    67486754      Conversion from CQL to XCQL is trivial and does not
    67496755      require a mapping to be defined.
    6750       There three functions to choose from depending on the
     6756      There are three functions to choose from depending on the
    67516757      way you wish to store the resulting output (XML buffer
    67526758      containing XCQL).
     
    67596765      </synopsis>
    67606766      Function <function>cql_to_xml_buf</function> converts
    6761       to XCQL and stores result in a user supplied buffer of a given
     6767      to XCQL and stores the result in a user-supplied buffer of a given
    67626768      max size.
    67636769     </para>
    67646770     <para>
    67656771      <function>cql_to_xml</function> writes the result in
    6766       a user defined output stream.
     6772      a user-defined output stream.
    67676773      <function>cql_to_xml_stdio</function> writes to a
    67686774      a file.
     
    68056811   <para>
    68066812    An OID can either be declared as a automatic variable or it can
    6807     allocated using the memory utilities or ODR/NMEM. It's
     6813    be allocated using the memory utilities or ODR/NMEM. It's
    68086814    guaranteed that an OID can fit in <literal>OID_SIZE</literal> integers.
    68096815   </para>
     
    68256831   <para>
    68266832    And OID may also be filled from a string-based representation using
    6827     dots (.). This is achieved by function
     6833    dots (.). This is achieved by the function
    68286834    <screen>
    68296835     int oid_dotstring_to_oid(const char *name, Odr_oid *oid);
     
    68336839   <example id="tools.oid.bib1.2"><title>Using oid_oiddotstring_to_oid</title>
    68346840    <para>
    6835      We can fill the Bib-1 attribute set OID easier with:
     6841     We can fill the Bib-1 attribute set OID more easily with:
    68366842     <screen>
    68376843      Odr_oid bib1[OID_SIZE];
     
    68416847   </example>
    68426848   <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:
    68446850    <screen>
    68456851    Odr_oid *odr_getoidbystr(ODR o, const char *str);
    68466852    </screen>
    6847     This creates an OID from string-based representation using dots.
     6853    This creates an OID from a string-based representation using dots.
    68486854    This function take an &odr; stream as parameter. This stream is used to
    68496855    allocate memory for the data elements, which is released on a
     
    68536859    <title>Using odr_getoidbystr</title>
    68546860    <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:
    68566862     <screen>
    68576863      Odr_oid *bib1 = odr_getoidbystr(odr, "1.2.840.10003.3.1");
     
    68716877   <para>
    68726878    OIDs can be copied with <function>oid_oidcpy</function> which takes
    6873     two OID lists as arguments. Alternativly, an OID copy can be allocated
    6874     on a ODR stream with:
     6879    two OID lists as arguments. Alternatively, an OID copy can be allocated
     6880    on an ODR stream with:
    68756881    <screen>
    68766882     Odr_oid *odr_oiddup(ODR odr, const Odr_oid *o);
     
    69066912    <para>
    69076913     A YAZ database handle is of type <literal>yaz_oid_db_t</literal>.
    6908      Actually that's a pointer. You need not think deal with that.
     6914     Actually that's a pointer. You need not deal with that.
    69096915     YAZ has a built-in database which can be considered "constant" for
    69106916     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>.
    69126918    </para>
    69136919    <para>
     
    69406946    <para>
    69416947     All the object identifers in the standard OID database as returned
    6942      by <function>yaz_oid_std</function> can referenced directly in a
     6948     by <function>yaz_oid_std</function> can be referenced directly in a
    69436949     program as a constant OID.
    69446950     Each constant OID is prefixed with <literal>yaz_oid_</literal> -
     
    69736979    memory-management system of the &odr; subsystem (see
    69746980    <xref linkend="odr.use"/>). However, in some circumstances
    6975     where you might otherwise benefit from using a simple nibble memory
     6981    where you might otherwise benefit from using a simple nibble-memory
    69766982    management system, it may be impractical to use
    69776983    <function>odr_malloc()</function> and <function>odr_reset()</function>.
     
    70057011   </para>
    70067012   <para>
    7007     The nibble memory pool is shared amongst threads. POSIX
     7013    The nibble-memory pool is shared amongst threads. POSIX
    70087014    mutex'es and WIN32 Critical sections are introduced to keep the
    70097015    module thread safe. Function <function>nmem_init()</function>
    7010     initializes the nibble memory library and it is called automatically
     7016    initializes the nibble-memory library and it is called automatically
    70117017    the first time the <literal>YAZ.DLL</literal> is loaded. &yaz; uses
    70127018    function <function>DllMain</function> to achieve this. You should
     
    70297035    Due to name clash with syslog and some math utilities the logging
    70307036    interface has been modified as of YAZ 2.0.29. The obsolete interface
    7031     is still available if in header file <filename>yaz/log.h</filename>.
     7037    is still available in header file <filename>yaz/log.h</filename>.
    70327038    The key points of the interface are:
    70337039   </para>
     
    70797085   </para>
    70807086   <para>
    7081     Each module should check what log bits it should be used, by calling
     7087    Each module should check what log bits should be used, by calling
    70827088    <function>yaz_log_module_level</function> with a suitable name for the
    7083     module. The name is cleared from a preceding path and an extension, if any,
     7089    module. The name is cleared of a preceding path and an extension, if any,
    70847090    so it is quite possible to use <literal>__FILE__</literal> for it. If the
    70857091    name has been passed to <function>yaz_log_mask_str</function>, the routine
     
    70987104    debugging of yaz itself.
    70997105    Of course, any program using yaz is welcome to define as many new
    7100     ones, as it needs.
     7106    ones as it needs.
    71017107   </para>
    71027108   <para>
     
    71577163    YAZ provides a fast utility for working with MARC records.
    71587164    Early versions of the MARC utility only allowed decoding of ISO2709.
    7159     Today the utility may both encode - and decode to a varity of formats.
     7165    Today the utility may both encode - and decode to a variety of formats.
    71607166   </para>
    71617167   <synopsis><![CDATA[
     
    72097215   </para>
    72107216   <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.
    72127218    The output is specified by a call to <function>yaz_marc_xml</function>.
    72137219    The <literal>xmlmode</literal> must be one of
     
    72187224       <para>
    72197225        A simple line-by-line format suitable for display but not
    7220         recommend for further (machine) processing.
     7226        recommended for further (machine) processing.
    72217227       </para>
    72227228      </listitem>
     
    72697275      <listitem>
    72707276       <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.
    72727278       </para>
    72737279      </listitem>
     
    72797285    <function>yaz_marc_decode_buf</function> and
    72807286    <function>yaz_marc_decode_wrbuf</function> which decodes and encodes
    7281     a MARC record. The former function operates on simple buffers, the
     7287    a MARC record. The former function operates on simple buffers, and
    72827288    stores the resulting record in a WRBUF handle (WRBUF is a simple string
    72837289    type).
     
    73137319     Applications like
    73147320     Pazpar2 uses XSLT to convert an XML encoded MARC record to an internal
    7315      representation. This conversion mostly check the tag of a MARC field
     7321     representation. This conversion mostly checks the tag of a MARC field
    73167322     to determine the basic rules in the conversion. This check is
    7317      costly when that is tag is encoded as an attribute in MARCXML.
     7323     costly when that tag is encoded as an attribute in MARCXML.
    73187324     By having the tag value as the element instead, makes processing
    73197325     many times faster (at least for Libxslt).
     
    73507356        with the tag value of the control field if the tag value
    73517357        matches the regular expression <literal>[a-zA-Z0-9]*</literal>.
    7352         If the tag value do not match the regular expression
     7358        If the tag value does not match the regular expression
    73537359        <literal>[a-zA-Z0-9]*</literal> the control field is encoded
    73547360        as element <literal>c</literal> and attribute <literal>code</literal>
    73557361        will hold the tag value.
    7356         This rule ensure that in the rare cases where a tag value might
    7357         result in a non-wellformed XML YAZ encode it as a coded attribute
     7362        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
    73587364        (as in MARCXML).
    73597365       </para>
    73607366       <para>
    7361         The control field content is the the text value of this element.
     7367        The control field content is the text value of this element.
    73627368        Indicators are encoded as attribute names
    7363         <literal>i1</literal>, <literal>i2</literal>, etc.. and
     7369        <literal>i1</literal>, <literal>i2</literal>, etc. and
    73647370        corresponding values for each indicator.
    73657371       </para>
     
    73707376        with the tag value of the data field or using the attribute
    73717377        <literal>code</literal> as described in the rules for control fields.
    7372         The children of the data field element is subfield elements.
     7378        The children of the data field element are subfield elements.
    73737379        Each subfield element is encoded as <literal>s</literal>
    73747380        concatenated with the sub field code.
    73757381        The text of the subfield element is the contents of the subfield.
    7376         Indicators are encoded as attributes for the data field element similar
     7382        Indicators are encoded as attributes for the data field element, similar
    73777383        to the encoding for control fields.
    73787384      </para>
     
    74257431    configuration is neither Z39.50 ZeeRex or SRU ZeeRex. But it
    74267432    should be easy to generate both of them from the XML configuration.
    7427     (unfortunately the two versions
    7428     of ZeeRex differ substantially in this regard).
     7433    (Unfortunately the two versions
     7434    of ZeeRex differ substantially in this regard.)
    74297435   </para>
    74307436   <sect2 id="tools.retrieval.format">
     
    74587464        <para>
    74597465         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);
    74617467         for Z39.50 it's equivalent to simple element set name.
    74627468         For YAZ 3.0.24 and later this name may be specified as a glob
     
    74707476        <para>
    74717477         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.
    74737479         For Z39.50, there is no equivalent.
    74747480        </para>
     
    74867492    <para>
    74877493     The attributes, <literal>name</literal> and <literal>syntax</literal>
    7488      may be specified for the <literal>backend</literal> element. These
     7494     may be specified for the <literal>backend</literal> element. The
    74897495     semantics of these attributes is equivalent to those for the
    74907496     <literal>retrieval</literal>. However, these values are passed to
     
    74927498    </para>
    74937499    <para>
    7494      The <literal>backend</literal> element may includes one or more
     7500     The <literal>backend</literal> element may include one or more
    74957501     conversion instructions (as children elements). The supported
    74967502     conversions are:
     
    75117517             <literal>marc</literal> (for ISO2709), <literal>xml</literal>
    75127518             (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>).
    75147520            </para>
    75157521           </listitem>
     
    75257531             <literal>marcxhcange</literal> (for MarcXchange),
    75267532             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>).
    75287534            </para>
    75297535           </listitem>
     
    76697675     <title>MARCXML backend</title>
    76707676     <para>
    7671       SRW/SRU and Solr backends returns records in XML.
     7677      SRW/SRU and Solr backends return records in XML.
    76727678      If they return MARCXML or MarcXchange, the retrieval module
    76737679      can convert those into ISO2709 formats, most commonly USMARC
     
    77447750   <para>
    77457751    In SRU/Solr, however, the model is different. Here, sorting is specified
    7746     during the the search operation. Note, however, that SRU might
     7752    during the search operation. Note, however, that SRU might
    77477753    perform sort as separate search, by referring to an existing result-set
    77487754    in the query (result-set reference).
     
    77517757    <title>Using the Z39.50 sort service</title>
    77527758    <para>
    7753      yaz-client and the ZOOM API supports the Z39.50 sort facility. In any
     7759     yaz-client and the ZOOM API support the Z39.50 sort facility. In any
    77547760     case the sort sequence or sort critiera is using a string notation.
    77557761     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).
    77577763     For the ZOOM API, the sort is specified in the call to ZOOM_query_sortby
    77587764     function. For yaz-client the sort is performed and specified using
     
    77807786    </para>
    77817787    <para>
    7782      The sort is triggered by the presence of type 7 and the value of type 7
     7788     The sort is triggered by the presence of type 7, and the value of type 7
    77837789     specifies the
    77847790     <ulink url="http://www.loc.gov/z3950/agency/asn1.html#SortKeySpec">
    77857791      sortRelation
    7786      </ulink>
     7792     </ulink>.
    77877793     The value for type 7 is 1 for ascending and 2 for descending.
    77887794     For the
     
    77937799     sortField, then attribute type 1 is present and the value is
    77947800     sortField (InternationalString). If generic sortKey is of type
    7795      sortAttributes, then the attributes in list is used . generic sortKey
     7801     sortAttributes, then the attributes in the list are used. Generic sortKey
    77967802     of type elementSpec is not supported.
    77977803    </para>
     
    78067812   <title>Facets</title>
    78077813   <para>
    7808     YAZ supports facets for in Solr, SRU 2.0 and Z39.50 protocols.
     7814    YAZ supports facets in the Solr, SRU 2.0 and Z39.50 protocols.
    78097815   </para>
    78107816   <para>
     
    78147820   </para>
    78157821   <para>
    7816     For ZOOM C the facets are given by option "facets"
    7817     For yaz-client it is used for the facets command.
     7822    For ZOOM C the facets are given by option "facets".
     7823    For yaz-client it is used for the 'facets' command.
    78187824   </para>
    78197825   <para>
     
    78287834    </literallayout>
    78297835    The notation is inspired by PQF. The string following '@attr'
    7830     may not include blanks and is of the form
     7836    must not include blanks and is of the form
    78317837    <replaceable>type</replaceable><literal>=</literal><replaceable>value</replaceable>,
    78327838    where <replaceable>type</replaceable> is an integer and
     
    78517857       <entry>1</entry>
    78527858       <entry>
    7853         Field-name. This is often a string, eg "Author", "Year", etc.
     7859        Field-name. This is often a string, e.g. "Author", "Year", etc.
    78547860       </entry>
    78557861      </row>
     
    78837889   <title>Introduction</title>
    78847890   <para>
    7885     &odr; is the BER-encoding/decoding subsystem of &yaz;. Care as been taken
     7891    &odr; is the BER-encoding/decoding subsystem of &yaz;. Care has been taken
    78867892    to isolate &odr; from the rest of the package - specifically from the
    78877893    transport interface. &odr; may be used in any context where basic
     
    79948000     small bits of space, the system maintains a free-list of larger chunks
    79958001     of memory, which are handed out in small bits. This scheme is
    7996      generally known as a <emphasis>nibble memory</emphasis> system.
     8002     generally known as a <emphasis>nibble-memory</emphasis> system.
    79978003     It is very useful for maintaining short-lived constructions such
    79988004     as protocol PDUs.
     
    82078213     </synopsis>
    82088214     before encoders or decoders are being invoked.
    8209      It is also possible to direct the output to a buffer (of indeed
     8215     It is also possible to direct the output to a buffer (or indeed
    82108216     another file), by using the more generic mechanism:
    82118217     <synopsis>
     
    82228228     if NULL for the function is provided, it will not be invoked.
    82238229     The <replaceable>stream_write</replaceable> takes the ODR handle
    8224      as parameter, the user defined handle, a type
     8230     as parameter, the user-defined handle, a type
    82258231     <literal>ODR_OCTETSTRING</literal>, <literal>ODR_VISIBLESTRING</literal>
    8226      which indicates the type of contents is being written.
     8232     which indicates the type of contents being written.
    82278233    </para>
    82288234    <para>
     
    82348240     which returns a list of current elements that ODR deals with at the
    82358241     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,
    82378243     <literal>ar[n]</literal> is the last. The last element has the
    82388244     property that <literal>ar[n+1] == NULL</literal>.
     
    84848490      that holds the octetstring. The <literal>len</literal> field holds the
    84858491      actual length.
    8486       The character array need not be null terminated.
     8492      The character array need not be null-terminated.
    84878493     </para>
    84888494     <para>
    84898495      To make things a little easier, an alternative is given for string
    8490       types that are not expected to contain embedded NULL characters (eg.
     8496      types that are not expected to contain embedded NULL characters (e.g.
    84918497      VisibleString):
    84928498     </para>
     
    84958501     </synopsis>
    84968502     <para>
    8497       Which encoded or decodes between OCTETSTRING representations and
    8498       null-terminates C strings.
    8499      </para>
    8500      <para>
    8501       Functions are provided for the derived string types, eg:
     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.:
    85028508     </para>
    85038509     <synopsis>
     
    85148520     <para>
    85158521      The opaque type <literal>Odr_bitmask</literal> is only suitable for
    8516       holding relatively brief bit strings, eg. for options fields, etc.
     8522      holding relatively brief bit strings, e.g. for options fields, etc.
    85178523      The constant <literal>ODR_BITMASK_SIZE</literal> multiplied by 8
    85188524      gives the maximum possible number of bits.
     
    86268632     the data stream. <literal>size</literal> bytes of memory are allocated,
    86278633     and <literal>*p</literal> is set to point to this space.
    8628      <function>odr_sequence_end()</function> is called at the end of the
     8634     The <function>odr_sequence_end()</function> is called at the end of the
    86298635     complex function. Assume that a type is defined like this:
    86308636    </para>
     
    87528758     <para>
    87538759      Assume that the IMPLICIT in the type definition above were replaced
    8754       with EXPLICIT (or that the IMPLICIT keyword were simply deleted, which
     8760      with EXPLICIT (or that the IMPLICIT keyword was simply deleted, which
    87558761      would be equivalent). The structure definition would look the same,
    87568762      but the function would look like this:
     
    87798785      simple: Explicitly tagged, constructed types are fairly rare in
    87808786      the protocols that we care about, so the
    8781       esthetic annoyance (not to mention the dangers of a cluttered
     8787      aesthetic annoyance (not to mention the dangers of a cluttered
    87828788      interface) is less than the time that would be required to develop a
    87838789      better interface. Nevertheless, it is far from satisfying, and it's a
     
    89768982    </para>
    89778983    <para>
    8978      The ASN.1 specifications naturally requires that each member of a
     8984     The ASN.1 specifications naturally require that each member of a
    89798985     CHOICE have a distinct tag, so they can be told apart on decoding.
    89808986     Sometimes it can be useful to define a CHOICE that has multiple types
     
    89938999     provides this functionality. When called, it leaves a notice for the next
    89949000     call to <function>odr_choice()</function> to be called on the decoding
    8995      stream <literal>o</literal> that only the <literal>arm</literal> entry with
     9001     stream <literal>o</literal>, that only the <literal>arm</literal> entry with
    89969002     a <literal>which</literal> field equal to <literal>what</literal>
    89979003     should be tried.
     
    91639169     The <function>cs_create</function> function returns a null-pointer
    91649170     if a system error occurs.
    9165      The <literal>blocking</literal> parameter should be one if
    9166      you wish the association to operate in blocking mode, zero otherwise.
     9171     The <literal>blocking</literal> parameter should be '1' if
     9172     you wish the association to operate in blocking mode, and '0' otherwise.
    91679173     The <literal>protocol</literal> field should be
    91689174     <literal>PROTO_Z3950</literal> or <literal>PROTO_HTTP</literal>.
     
    92019207     and <literal>len</literal>, until the buffer has been transmitted.
    92029208     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).
    92049210    </para>
    92059211    <synopsis>
     
    92179223     calling
    92189224     <function>cs_get</function>
    9219      for the fist time, the buffer can be initialized to the null pointer,
    9220      and the length should also be set to 0 - cs_get will perform a
     9225     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
    92219227     <function>malloc(2)</function>
    9222      on the buffer for you. When a full buffer has been read, the size of
    9223      the package is returned (which will always be greater than 1). -1
    9224      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.
    92259231    </para>
    92269232    <para>
     
    93259331    </synopsis>
    93269332    <para>
    9327      Returns the file descriptor of the association. Use this when
     9333     returns the file descriptor of the association. Use this when
    93289334     file-level operations on the endpoint are required
    93299335     (<function>select(2)</function> operations, specifically).
     
    94119417    <para>
    94129418     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.
    94149420    </para>
    94159421   </note>
     
    94719477    is similar to that described for <function>cs_straddr</function>
    94729478    but with a prefix denoting the &comstack; type. Prefixes supported
    9473     are <literal>tcp:</literal>, <literal>unix:</literal> and
    9474     <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.
    94759481    If no prefix is given, then TCP/IP is used.
    94769482    The <parameter>blocking</parameter> is passed to
     
    94899495    </synopsis>
    94909496    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.
    94929498   </para>
    94939499   <para>
     
    95399545   <para>
    95409546    You can the textual representation of the error code
    9541     by using <function>cs_errmsg</function> - which
    9542     works like <function>strerror(3)</function>
     9547    by using <function>cs_errmsg</function>, which
     9548    works like <function>strerror(3)</function>.
    95439549   </para>
    95449550   <synopsis>
     
    95469552   </synopsis>
    95479553   <para>
    9548     It is also possible to get straight to the textual represenataion
    9549     without the error code by using
     9554    It is also possible to get straight to the textual representation
     9555    without the error code, by using
    95509556    <function>cs_strerror</function>.
    95519557   </para>
  • yaz/trunk/fuentes/doc/common/Makefile.in

    r255 r265  
    172172EXEEXT = @EXEEXT@
    173173FGREP = @FGREP@
    174 GCRYPT_LIBS = @GCRYPT_LIBS@
    175174GREP = @GREP@
    176175HIREDIS_LIBS = @HIREDIS_LIBS@
     
    274273libdir = @libdir@
    275274libexecdir = @libexecdir@
    276 libgcrypt = @libgcrypt@
    277275localedir = @localedir@
    278276localstatedir = @localstatedir@
  • yaz/trunk/fuentes/doc/common/common.ent

    r255 r265  
    143143<!ENTITY url.marcxml "http://www.loc.gov/standards/marcxml/">
    144144<!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">
    146146<!ENTITY url.ber.over.tcpip "http://www.faqs.org/rfcs/rfc1729.html">
    147147<!ENTITY url.http "http://www.w3.org/Protocols/">
     
    163163<!ENTITY url.libxslt "http://xmlsoft.org/XSLT/">
    164164<!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/">
    165167<!ENTITY url.expat "http://expat.sourceforge.net/">
    166168<!ENTITY url.autoconf "http://www.gnu.org/software/autoconf/">
  • yaz/trunk/fuentes/doc/comstack.addresses.html

    r255 r265  
    4141    is similar to that described for <code class="function">cs_straddr</code>
    4242    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> and
    44     <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.
    4545    If no prefix is given, then TCP/IP is used.
    4646    The <em class="parameter"><code>blocking</code></em> is passed to
  • yaz/trunk/fuentes/doc/comstack.common.html

    r255 r265  
    1414     The <code class="function">cs_create</code> function returns a null-pointer
    1515     if a system error occurs.
    16      The <code class="literal">blocking</code> parameter should be one if
    17      you wish the association to operate in blocking mode, zero otherwise.
     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.
    1818     The <code class="literal">protocol</code> field should be
    1919     <code class="literal">PROTO_Z3950</code> or <code class="literal">PROTO_HTTP</code>.
     
    4242     and <code class="literal">len</code>, until the buffer has been transmitted.
    4343     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).
    4545    </p><pre class="synopsis">
    4646     int cs_get(COMSTACK handle, char **buf, int *size);
     
    5656     calling
    5757     <code class="function">cs_get</code>
    58      for the fist 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
     58     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
    6060     <code class="function">malloc(2)</code>
    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). -1
    63      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.
    6464    </p><p>
    6565     See also the <code class="function">cs_more()</code> function below.
     
    129129     int cs_fileno(COMSTACK h);
    130130    </pre><p>
    131      Returns the file descriptor of the association. Use this when
     131     returns the file descriptor of the association. Use this when
    132132     file-level operations on the endpoint are required
    133133     (<code class="function">select(2)</code> operations, specifically).
  • yaz/trunk/fuentes/doc/comstack.diagnostics.html

    r255 r265  
    1515   </pre><p>
    1616    You can the textual representation of the error code
    17     by using <code class="function">cs_errmsg</code> - which
    18     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>.
    1919   </p><pre class="synopsis">
    2020    const char *cs_errmsg(int n);
    2121   </pre><p>
    22     It is also possible to get straight to the textual represenataion
    23     without the error code by using
     22    It is also possible to get straight to the textual representation
     23    without the error code, by using
    2424    <code class="function">cs_strerror</code>.
    2525   </p><pre class="synopsis">
  • yaz/trunk/fuentes/doc/comstack.server.html

    r255 r265  
    4141   </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    4242     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.
    4444    </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  
    44    </pre><p>
    55    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.
    77   </p><p>
    88    </p><pre class="synopsis">
  • yaz/trunk/fuentes/doc/entities.ent

    r255 r265  
    1414<!ENTITY reference-tools-cql-map "<xref linkend='cql.to.rpn'/>">
    1515<!ENTITY reference-tools-ccl-qualifiers "<xref linkend='ccl.qualifiers'/>">
    16 <!ENTITY copyright-year "1995-2015">
     16<!ENTITY copyright-year "1995-2016">
    1717<!ENTITY soversion "5">
  • yaz/trunk/fuentes/doc/facets.html

    r255 r265  
    11<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 in Solr, SRU 2.0 and Z39.50 protocols.
     2    YAZ supports facets in the Solr, SRU 2.0 and Z39.50 protocols.
    33   </p><p>
    44    Like Type-1/RPN, YAZ supports a string notation for specifying
     
    66    <code class="function">yaz_pqf_parse_facet_list</code>.
    77   </p><p>
    8     For ZOOM C the facets are given by option "facets"
    9     For yaz-client it is used for the facets command.
     8    For ZOOM C the facets are given by option "facets".
     9    For yaz-client it is used for the 'facets' command.
    1010   </p><p>
    1111    The grammar of this specification is as follows:
     
    1919    </p></div><p>
    2020    The notation is inspired by PQF. The string following '@attr'
    21     may not include blanks and is of the form
     21    must not include blanks and is of the form
    2222    <em class="replaceable"><code>type</code></em><code class="literal">=</code><em class="replaceable"><code>value</code></em>,
    2323    where <em class="replaceable"><code>type</code></em> is an integer and
     
    2626    The Facets specification is not Bib-1. The following types apply:
    2727   </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, eg "Author", "Year", etc.
     28        Field-name. This is often a string, e.g. "Author", "Year", etc.
    2929       </td></tr><tr><td>2</td><td>
    3030        Sort order. Value should be an integer.
  • yaz/trunk/fuentes/doc/gfs-options.xml

    r255 r265  
    3535  <listitem><para>
    3636   Operate the server in threaded mode. The server creates a thread
    37    for each connection rather than a fork a process. Only available
    38    on UNIX systems that offers POSIX threads.
     37   for each connection rather than fork a process. Only available
     38   on UNIX systems that offer POSIX threads.
    3939  </para></listitem>
    4040 </varlistentry>
     
    100100  <term><literal>-w </literal><replaceable>dir</replaceable></term>
    101101  <listitem><para>
    102    The server changes to this directory during before listening
    103    on incoming connections. This option is useful
     102   The server changes to this directory before listening
     103   to incoming connections. This option is useful
    104104   when the server is operating from the <application>inetd</application>
    105105   daemon (see <literal>-i</literal>).
     
    110110 </term>
    111111 <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
    113113  file given by <replaceable>pidfile</replaceable>.
    114114  A typical location would be <filename>/var/run/yaz-ztest.pid</filename>.
  • yaz/trunk/fuentes/doc/gfs-virtual.xml

    r255 r265  
    2323<note>
    2424 <para>
    25   Not all Z39.50 clients allows the VHOST information to be set.
    26   For those the selection of the backend must rely on the
     25  Not all Z39.50 clients allow the VHOST information to be set.
     26  For those, the selection of the backend must rely on the
    2727  TCP/IP information alone (port and address).
    2828 </para>
     
    5656    <listitem>
    5757     <para>
    58       identifier for this listener. This may be referred to from
     58      Identifier for this listener. This may be referred to from
    5959      server sections.
    6060     </para>
     
    108108    <para>
    109109     Specifies a working directory for this backend server. If
    110      specifid, the YAZ fronend changes current working directory
     110     specified, the YAZ frontend changes current working directory
    111111     to this directory whenever a backend of this type is
    112112     started (backend handler bend_start), stopped (backend handler hand_stop)
     
    130130    <para>
    131131     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;.
    133133     If given, the backend server will only "see" a Type-1/RPN query.
    134134    </para>
     
    140140    <para>
    141141     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;.
    143143     If given, the backend server will only "see" a Type-1/RPN query.
    144144    </para>
     
    150150    <para>
    151151     Specifies the stylesheet reference to be part of SRU HTTP responses
    152      when the client does not specify one. If neither this is given, nor
    153      the client specifies one, no stylesheet reference is part of the
     152     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
    154154     SRU HTTP response.
    155155    </para>
     
    171171    <para>
    172172     Specifies a path for local file access using HTTP. All URLs with
    173      a leading prefix (/ exluded) that matches the value of docpath
     173     a leading prefix (/ excluded) that matches the value of <literal>docpath</literal>
    174174     are used for file access. For example, if the server is to offer
    175175     access in directory <literal>xsl</literal>, the docpath would be
    176176     <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.
    178178    </para>
    179179   </listitem>
     
    185185     Specifies SRW/SRU ZeeRex content for this server. Copied verbatim
    186186     to the client. As things are now, some of the Explain content
    187      seeem redundant because host information, etc. is also stored
     187     seem redundant because host information, etc. is also stored
    188188     elsewhere.
    189189    </para>
     
    195195    <para>
    196196     Specifies maximum record size/message size, in bytes. This
    197      value also servers as maximum size of <emphasis>incoming</emphasis>
     197     value also serves as the maximum size of <emphasis>incoming</emphasis>
    198198     packages (for Record Updates etc). It's the same value as that
    199199     given by the <literal>-k</literal> option.
     
    205205   <listitem>
    206206    <para>
    207      Enables the retrieval facility supporting conversions and
     207     Enables the retrieval facility to support conversions and
    208208     specifications of record formats/types.
    209209     See <xref linkend="tools.retrieval"/> for
     
    260260 <literal>"server2"</literal> is reached by the two listeners specified.
    261261 In order to distinguish between the two, a virtual host has
    262  been specified for each of server in the <literal>host</literal>
     262 been specified for each server in the <literal>host</literal>
    263263 elements.
    264264</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.14.3. YAZ is a compact toolkit that provides access to the Z39.50 and SRU/Solr protocols, as well as a set of higher-level tools for implementing the server and client roles, respectively. The documentation can be used on its own, or as a reference when looking at the example applications provided with the package. "><link rel="home" href="index.html" title="YAZ User's Guide and Reference"><link rel="next" href="introduction.html" title="Chapter 1. Introduction"></head><body><link rel="stylesheet" type="text/css" href="common/style1.css"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">YAZ User's Guide and Reference</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="introduction.html">Next</a></td></tr></table><hr></div><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idp43484400"></a>YAZ User's Guide and Reference</h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Sebastian</span> <span class="surname">Hammer</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Adam</span> <span class="surname">Dickmeiss</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Mike</span> <span class="surname">Taylor</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Heikki</span> <span class="surname">Levanto</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Dennis</span> <span class="surname">Schafroth</span></h3></div></div></div><div><p class="releaseinfo">5.14.3</p></div><div><p class="copyright">Copyright © 1995-2015 Index Data</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
     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>
    22    This document is the programmer's guide and reference to the YAZ
    3     package version 5.14.3. YAZ is a compact toolkit that provides
     3    package version 5.15.2. YAZ is a compact toolkit that provides
    44    access to the Z39.50 and SRU/Solr protocols, as well as a set of
    55    higher-level tools for implementing the server and client
     
    99   </p><p>
    1010    <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#idp46954032">7.1. Using the Z39.50 sort service</a></span></dt><dt><span class="sect2"><a href="sorting.html#idp46957856">7.2. Type-7 sort</a></span></dt></dl></dd><dt><span class="sect1"><a href="facets.html">8. Facets</a></span></dt></dl></dd><dt><span class="chapter"><a href="odr.html">8. The ODR Module</a></span></dt><dd><dl><dt><span class="sect1"><a href="odr.html#odr.introduction">1. Introduction</a></span></dt><dt><span class="sect1"><a href="odr.use.html">2. Using ODR</a></span></dt><dd><dl><dt><span class="sect2"><a href="odr.use.html#odr.streams">2.1. ODR Streams</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.memory.management">2.2. Memory Management</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.encoding.and.decoding">2.3. Encoding and Decoding Data</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.printing">2.4. Printing</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.diagnostics">2.5. Diagnostics</a></span></dt><dt><span class="sect2"><a href="odr.use.html#odr.summary.and.synopsis">2.6. Summary and Synopsis</a></span></dt></dl></dd><dt><span class="sect1"><a href="odr.programming.html">3. Programming with ODR</a></span></dt><dd><dl><dt><span class="sect2"><a href="odr.programming.html#odr.primitive.asn1.types">3.1. The Primitive ASN.1 Types</a></span></dt><dd><dl><dt><span class="sect3"><a href="odr.programming.html#odr.integer">3.1.1. INTEGER</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.boolean">3.1.2. BOOLEAN</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.real">3.1.3. REAL</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.null">3.1.4. NULL</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.octet.string">3.1.5. OCTET STRING</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.bit.string">3.1.6. BIT STRING</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.object.identifier">3.1.7. OBJECT IDENTIFIER</a></span></dt></dl></dd><dt><span class="sect2"><a href="odr.programming.html#odr.tagging.primitive.types">3.2. Tagging Primitive Types</a></span></dt><dt><span class="sect2"><a href="odr.programming.html#odr.constructed.types">3.3. Constructed Types</a></span></dt><dt><span class="sect2"><a href="odr.programming.html#odr.tagging.constructed.types">3.4. Tagging Constructed Types</a></span></dt><dd><dl><dt><span class="sect3"><a href="odr.programming.html#odr.implicit.tagging">3.4.1. Implicit Tagging</a></span></dt><dt><span class="sect3"><a href="odr.programming.html#odr.explicit.tagging">3.4.2. Explicit Tagging</a></span></dt></dl></dd><dt><span class="sect2"><a href="odr.programming.html#odr.sequence.of">3.5. SEQUENCE OF</a></span></dt><dt><span class="sect2"><a href="odr.programming.html#odr.choice.types">3.6. CHOICE Types</a></span></dt></dl></dd><dt><span class="sect1"><a href="odr.debugging.html">4. Debugging</a></span></dt></dl></dd><dt><span class="chapter"><a href="comstack.html">9. The COMSTACK Module</a></span></dt><dd><dl><dt><span class="sect1"><a href="comstack.html#comstack.synopsis">1. Synopsis (blocking mode)</a></span></dt><dt><span class="sect1"><a href="comstack.introduction.html">2. Introduction</a></span></dt><dt><span class="sect1"><a href="comstack.common.html">3. Common Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="comstack.common.html#comstack.managing.endpoints">3.1. Managing Endpoints</a></span></dt><dt><span class="sect2"><a href="comstack.common.html#comstack.data.exchange">3.2. Data Exchange</a></span></dt></dl></dd><dt><span class="sect1"><a href="comstack.client.html">4. Client Side</a></span></dt><dt><span class="sect1"><a href="comstack.server.html">5. Server Side</a></span></dt><dt><span class="sect1"><a href="comstack.addresses.html">6. Addresses</a></span></dt><dt><span class="sect1"><a href="comstack.ssl.html">7. SSL</a></span></dt><dt><span class="sect1"><a href="comstack.diagnostics.html">8. Diagnostics</a></span></dt><dt><span class="sect1"><a href="comstack.summary.html">9. Summary and Synopsis</a></span></dt></dl></dd><dt><span class="chapter"><a href="future.html">10. Future Directions</a></span></dt><dt><span class="reference"><a href="reference.html">I. Reference</a></span></dt><dd><dl><dt><span class="refentrytitle"><a href="yaz-client.html">yaz-client</a></span><span class="refpurpose"> &#8212; Z39.50/SRU client for implementors</span></dt><dt><span class="refentrytitle"><a href="yaz-ztest.html">yaz-ztest</a></span><span class="refpurpose"> &#8212; Z39.50/SRU Test Server</span></dt><dt><span class="refentrytitle"><a href="yaz-config.html">yaz-config</a></span><span class="refpurpose"> &#8212; Script to get information about YAZ.</span></dt><dt><span class="refentrytitle"><a href="yaz.html">yaz</a></span><span class="refpurpose"> &#8212; Z39.50 toolkit.</span></dt><dt><span class="refentrytitle"><a href="zoomsh.html">zoomsh</a></span><span class="refpurpose"> &#8212; ZOOM shell</span></dt><dt><span class="refentrytitle"><a href="yaz-asncomp.html">yaz-asncomp</a></span><span class="refpurpose"> &#8212; YAZ ASN.1 compiler</span></dt><dt><span class="refentrytitle"><a href="yaz-marcdump.html">yaz-marcdump</a></span><span class="refpurpose"> &#8212; MARC record dump utility</span></dt><dt><span class="refentrytitle"><a href="yaz-iconv.html">yaz-iconv</a></span><span class="refpurpose"> &#8212; YAZ Character set conversion utility</span></dt><dt><span class="refentrytitle"><a href="yaz-log.html">yaz-log</a></span><span class="refpurpose"> &#8212; Log handling in all yaz-based programs</span></dt><dt><span class="refentrytitle"><a href="yaz-illclient.html">yaz-illclient</a></span><span class="refpurpose"> &#8212; ILL client</span></dt><dt><span class="refentrytitle"><a href="yaz-icu.html">yaz-icu</a></span><span class="refpurpose"> &#8212; YAZ ICU utility</span></dt><dt><span class="refentrytitle"><a href="yaz-url.html">yaz-url</a></span><span class="refpurpose"> &#8212; YAZ URL fetch utility</span></dt><dt><span class="refentrytitle"><a href="bib1.html">Bib-1 Attribute Set</a></span><span class="refpurpose"> &#8212; Bib-1 Attribute Set</span></dt><dt><span class="refentrytitle"><a href="yaz-json-parse.html">yaz-json-parse</a></span><span class="refpurpose"> &#8212; YAZ JSON parser</span></dt></dl></dd><dt><span class="appendix"><a href="list-oids.html">A. List of Object Identifiers</a></span></dt><dt><span class="appendix"><a href="bib1-diagnostics.html">B. Bib-1 diagnostics</a></span></dt><dt><span class="appendix"><a href="sru-diagnostics.html">C. SRU diagnostics</a></span></dt><dt><span class="appendix"><a href="license.html">D. License</a></span></dt><dd><dl><dt><span class="sect1"><a href="license.html#license.indexdata">1. Index Data Copyright</a></span></dt></dl></dd><dt><span class="appendix"><a href="indexdata.html">E. About Index Data</a></span></dt><dt><span class="appendix"><a href="credits.html">F. Credits</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>1.1. <a href="introduction.api.html#yaz.layer">YAZ layers</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>3.1. <a href="zoom.html#zoom-connection-options">ZOOM Connection Options</a></dt><dt>3.2. <a href="zoom.query.html#zoom-sort-strategy">ZOOM sort strategy</a></dt><dt>3.3. <a href="zoom.resultsets.html#zoom.resultset.options">ZOOM Result set Options</a></dt><dt>3.4. <a href="zoom.resultsets.html#zoom.search.info.report.options">Search Info Report Options</a></dt><dt>3.5. <a href="zoom.scan.html#zoom.scanset.options">ZOOM Scan Set Options</a></dt><dt>3.6. <a href="zoom.extendedservices.html#zoom.extendedservices.type">Extended Service Type</a></dt><dt>3.7. <a href="zoom.extendedservices.html#zoom.extendedservices.options">Extended Service Common Options</a></dt><dt>3.8. <a href="zoom.extendedservices.html#zoom.item.order.options">Item Order Options</a></dt><dt>3.9. <a href="zoom.extendedservices.html#zoom.illrequest.options">ILL Request Options</a></dt><dt>3.10. <a href="zoom.extendedservices.html#zoom.record.update.options">Record Update Options</a></dt><dt>3.11. <a href="zoom.extendedservices.html#zoom.database.create.options">Database Create Options</a></dt><dt>3.12. <a href="zoom.extendedservices.html#zoom.database.drop.options">Database Drop Options</a></dt><dt>3.13. <a href="zoom.events.html#zoom.event.ids">ZOOM Event IDs</a></dt><dt>5.1. <a href="asn.pdu.html#asn.default.initialize.request">Default settings for PDU Initialize Request</a></dt><dt>5.2. <a href="asn.pdu.html#asn.default.initialize.response">Default settings for PDU Initialize Response</a></dt><dt>5.3. <a href="asn.pdu.html#asn.default.search.request">Default settings for PDU Search Request</a></dt><dt>5.4. <a href="asn.pdu.html#asn.default.search.response">Default settings for PDU Search Response</a></dt><dt>5.5. <a href="asn.pdu.html#asn.default.present.request">Default settings for PDU Present Request</a></dt><dt>5.6. <a href="asn.pdu.html#asn.default.present.response">Default settings for PDU Present Response</a></dt><dt>5.7. <a href="asn.pdu.html#asn.default.delete.result.set.request">Default settings for Delete Result Set Request</a></dt><dt>5.8. <a href="asn.pdu.html#asn.default.delete.result.set.response">Default settings for Delete Result Set Response</a></dt><dt>5.9. <a href="asn.pdu.html#asn.default.scan.request">Default settings for Scan Request</a></dt><dt>5.10. <a href="asn.pdu.html#asn.default.scan.response">Default settings for Scan Response</a></dt><dt>5.11. <a href="asn.pdu.html#asn.default.trigger.resource.control.request">Default settings for Trigger Resource Control Request</a></dt><dt>5.12. <a href="asn.pdu.html#asn.default.resource.control.request">Default settings for Resource Control Request</a></dt><dt>5.13. <a href="asn.pdu.html#asn.default.resource.control.response">Default settings for Resource Control Response</a></dt><dt>5.14. <a href="asn.pdu.html#asn.default.access.control.request">Default settings for Access Control Request</a></dt><dt>5.15. <a href="asn.pdu.html#asn.default.access.control.response">Default settings for Access Control Response</a></dt><dt>5.16. <a href="asn.pdu.html#asn.default.segment">Default settings for Segment</a></dt><dt>5.17. <a href="asn.pdu.html#asn.default.close">Default settings for Close</a></dt><dt>7.1. <a href="tools.html#ccl.common.bib1.attributes">Common Bib-1 attributes</a></dt><dt>7.2. <a href="tools.html#ccl.special.attribute.combos">Special attribute combos</a></dt><dt>7.3. <a href="tools.html#ccl.directives.table">CCL directives</a></dt><dt>7.4. <a href="facets.html#facet.attributes">Facet attributes</a></dt><dt>8.1. <a href="odr.use.html#odr.error.codes">ODR Error codes</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>4.1. <a href="server.invocation.html#server.example.running.unix">Running the GFS on Unix</a></dt><dt>4.2. <a href="server.invocation.html#server.example.apache.sru">Setting up Apache as SRU Frontend</a></dt><dt>4.3. <a href="server.invocation.html#server.example.local.access">Running a server with local access only</a></dt><dt>7.1. <a href="tools.html#example.pqf.simple.terms">PQF queries using simple terms</a></dt><dt>7.2. <a href="tools.html#pqf.example.pqf.boolean.operators">PQF boolean operators</a></dt><dt>7.3. <a href="tools.html#example.pqf.result.sets">PQF references to result sets</a></dt><dt>7.4. <a href="tools.html#example.pqf.attributes">Attributes for terms</a></dt><dt>7.5. <a href="tools.html#example.pqf.proximity">PQF Proximity queries</a></dt><dt>7.6. <a href="tools.html#example.pqf.search.term.type">PQF specification of search term type</a></dt><dt>7.7. <a href="tools.html#example.pqf.mixed.queries">PQF mixed queries</a></dt><dt>7.8. <a href="tools.html#example.ccl.queries">CCL queries</a></dt><dt>7.9. <a href="tools.html#example.ccl.profile">CCL profile</a></dt><dt>7.10. <a href="tools.html#example.cql.to.rpn.mapping">CQL to RPN mapping file</a></dt><dt>7.11. <a href="tools.html#example.cql.to.rpn.string">CQL to RPN string attributes</a></dt><dt>7.12. <a href="tools.html#example.cql.to.rpn.bathprofile">CQL to RPN using Bath Profile</a></dt><dt>7.13. <a href="tools.oid.html#tools.oid.bib1.1">Create OID on stack</a></dt><dt>7.14. <a href="tools.oid.html#tools.oid.bib1.2">Using oid_oiddotstring_to_oid</a></dt><dt>7.15. <a href="tools.oid.html#tools.oid.bib1.3">Using odr_getoidbystr</a></dt><dt>7.16. <a href="tools.oid.html#tools.oid.bib1.4">Create OID with YAZ DB</a></dt><dt>7.17. <a href="tools.oid.html#tools.oid.bib1.5">Use a built-in OID</a></dt><dt>7.18. <a href="marc.html#example.marc.display">Display of MARC record</a></dt><dt>7.19. <a href="tools.retrieval.html#tools.retrieval.marc21">MARC21 backend</a></dt><dt>7.20. <a href="tools.retrieval.html#tools.retrieval.marcxml">MARCXML backend</a></dt><dt>8.1. <a href="odr.use.html#example.odr.encoding.and.decoding.functions">Encoding and decoding functions</a></dt><dt>8.2. <a href="odr.use.html#example.odr.encoding.of.integer">Encoding and decoding of an integer</a></dt><dt>8.3. <a href="odr.use.html#example.odr.element.path.record">Element Path for record</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="introduction.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. Introduction</td></tr></table></div></body></html>
     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"> &#8212; Z39.50/SRU client for implementors</span></dt><dt><span class="refentrytitle"><a href="yaz-ztest.html">yaz-ztest</a></span><span class="refpurpose"> &#8212; Z39.50/SRU Test Server</span></dt><dt><span class="refentrytitle"><a href="yaz-config.html">yaz-config</a></span><span class="refpurpose"> &#8212; Script to get information about YAZ.</span></dt><dt><span class="refentrytitle"><a href="yaz.html">yaz</a></span><span class="refpurpose"> &#8212; Z39.50 toolkit.</span></dt><dt><span class="refentrytitle"><a href="zoomsh.html">zoomsh</a></span><span class="refpurpose"> &#8212; ZOOM shell</span></dt><dt><span class="refentrytitle"><a href="yaz-asncomp.html">yaz-asncomp</a></span><span class="refpurpose"> &#8212; YAZ ASN.1 compiler</span></dt><dt><span class="refentrytitle"><a href="yaz-marcdump.html">yaz-marcdump</a></span><span class="refpurpose"> &#8212; MARC record dump utility</span></dt><dt><span class="refentrytitle"><a href="yaz-iconv.html">yaz-iconv</a></span><span class="refpurpose"> &#8212; YAZ Character set conversion utility</span></dt><dt><span class="refentrytitle"><a href="yaz-log.html">yaz-log</a></span><span class="refpurpose"> &#8212; Log handling in all yaz-based programs</span></dt><dt><span class="refentrytitle"><a href="yaz-illclient.html">yaz-illclient</a></span><span class="refpurpose"> &#8212; ILL client</span></dt><dt><span class="refentrytitle"><a href="yaz-icu.html">yaz-icu</a></span><span class="refpurpose"> &#8212; YAZ ICU utility</span></dt><dt><span class="refentrytitle"><a href="yaz-url.html">yaz-url</a></span><span class="refpurpose"> &#8212; YAZ URL fetch utility</span></dt><dt><span class="refentrytitle"><a href="bib1.html">Bib-1 Attribute Set</a></span><span class="refpurpose"> &#8212; Bib-1 Attribute Set</span></dt><dt><span class="refentrytitle"><a href="yaz-json-parse.html">yaz-json-parse</a></span><span class="refpurpose"> &#8212; YAZ JSON parser</span></dt></dl></dd><dt><span class="appendix"><a href="list-oids.html">A. List of Object Identifiers</a></span></dt><dt><span class="appendix"><a href="bib1-diagnostics.html">B. Bib-1 diagnostics</a></span></dt><dt><span class="appendix"><a href="sru-diagnostics.html">C. SRU diagnostics</a></span></dt><dt><span class="appendix"><a href="license.html">D. License</a></span></dt><dd><dl><dt><span class="sect1"><a href="license.html#license.indexdata">1. Index Data Copyright</a></span></dt></dl></dd><dt><span class="appendix"><a href="indexdata.html">E. About Index Data</a></span></dt><dt><span class="appendix"><a href="credits.html">F. Credits</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>1.1. <a href="introduction.api.html#yaz.layer">YAZ layers</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>3.1. <a href="zoom.html#zoom-connection-options">ZOOM Connection Options</a></dt><dt>3.2. <a href="zoom.query.html#zoom-sort-strategy">ZOOM sort strategy</a></dt><dt>3.3. <a href="zoom.resultsets.html#zoom.resultset.options">ZOOM Result set Options</a></dt><dt>3.4. <a href="zoom.resultsets.html#zoom.search.info.report.options">Search Info Report Options</a></dt><dt>3.5. <a href="zoom.scan.html#zoom.scanset.options">ZOOM Scan Set Options</a></dt><dt>3.6. <a href="zoom.extendedservices.html#zoom.extendedservices.type">Extended Service Type</a></dt><dt>3.7. <a href="zoom.extendedservices.html#zoom.extendedservices.options">Extended Service Common Options</a></dt><dt>3.8. <a href="zoom.extendedservices.html#zoom.item.order.options">Item Order Options</a></dt><dt>3.9. <a href="zoom.extendedservices.html#zoom.illrequest.options">ILL Request Options</a></dt><dt>3.10. <a href="zoom.extendedservices.html#zoom.record.update.options">Record Update Options</a></dt><dt>3.11. <a href="zoom.extendedservices.html#zoom.database.create.options">Database Create Options</a></dt><dt>3.12. <a href="zoom.extendedservices.html#zoom.database.drop.options">Database Drop Options</a></dt><dt>3.13. <a href="zoom.events.html#zoom.event.ids">ZOOM Event IDs</a></dt><dt>5.1. <a href="asn.pdu.html#asn.default.initialize.request">Default settings for PDU Initialize Request</a></dt><dt>5.2. <a href="asn.pdu.html#asn.default.initialize.response">Default settings for PDU Initialize Response</a></dt><dt>5.3. <a href="asn.pdu.html#asn.default.search.request">Default settings for PDU Search Request</a></dt><dt>5.4. <a href="asn.pdu.html#asn.default.search.response">Default settings for PDU Search Response</a></dt><dt>5.5. <a href="asn.pdu.html#asn.default.present.request">Default settings for PDU Present Request</a></dt><dt>5.6. <a href="asn.pdu.html#asn.default.present.response">Default settings for PDU Present Response</a></dt><dt>5.7. <a href="asn.pdu.html#asn.default.delete.result.set.request">Default settings for Delete Result Set Request</a></dt><dt>5.8. <a href="asn.pdu.html#asn.default.delete.result.set.response">Default settings for Delete Result Set Response</a></dt><dt>5.9. <a href="asn.pdu.html#asn.default.scan.request">Default settings for Scan Request</a></dt><dt>5.10. <a href="asn.pdu.html#asn.default.scan.response">Default settings for Scan Response</a></dt><dt>5.11. <a href="asn.pdu.html#asn.default.trigger.resource.control.request">Default settings for Trigger Resource Control Request</a></dt><dt>5.12. <a href="asn.pdu.html#asn.default.resource.control.request">Default settings for Resource Control Request</a></dt><dt>5.13. <a href="asn.pdu.html#asn.default.resource.control.response">Default settings for Resource Control Response</a></dt><dt>5.14. <a href="asn.pdu.html#asn.default.access.control.request">Default settings for Access Control Request</a></dt><dt>5.15. <a href="asn.pdu.html#asn.default.access.control.response">Default settings for Access Control Response</a></dt><dt>5.16. <a href="asn.pdu.html#asn.default.segment">Default settings for Segment</a></dt><dt>5.17. <a href="asn.pdu.html#asn.default.close">Default settings for Close</a></dt><dt>7.1. <a href="tools.html#ccl.common.bib1.attributes">Common Bib-1 attributes</a></dt><dt>7.2. <a href="tools.html#ccl.special.attribute.combos">Special attribute combos</a></dt><dt>7.3. <a href="tools.html#ccl.directives.table">CCL directives</a></dt><dt>7.4. <a href="facets.html#facet.attributes">Facet attributes</a></dt><dt>8.1. <a href="odr.use.html#odr.error.codes">ODR Error codes</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>4.1. <a href="server.invocation.html#server.example.running.unix">Running the GFS on Unix</a></dt><dt>4.2. <a href="server.invocation.html#server.example.apache.sru">Setting up Apache as SRU Frontend</a></dt><dt>4.3. <a href="server.invocation.html#server.example.local.access">Running a server with local access only</a></dt><dt>7.1. <a href="tools.html#example.pqf.simple.terms">PQF queries using simple terms</a></dt><dt>7.2. <a href="tools.html#pqf.example.pqf.boolean.operators">PQF boolean operators</a></dt><dt>7.3. <a href="tools.html#example.pqf.result.sets">PQF references to result sets</a></dt><dt>7.4. <a href="tools.html#example.pqf.attributes">Attributes for terms</a></dt><dt>7.5. <a href="tools.html#example.pqf.proximity">PQF Proximity queries</a></dt><dt>7.6. <a href="tools.html#example.pqf.search.term.type">PQF specification of search term type</a></dt><dt>7.7. <a href="tools.html#example.pqf.mixed.queries">PQF mixed queries</a></dt><dt>7.8. <a href="tools.html#example.ccl.queries">CCL queries</a></dt><dt>7.9. <a href="tools.html#example.ccl.profile">CCL profile</a></dt><dt>7.10. <a href="tools.html#example.cql.to.rpn.mapping">CQL to RPN mapping file</a></dt><dt>7.11. <a href="tools.html#example.cql.to.rpn.string">CQL to RPN string attributes</a></dt><dt>7.12. <a href="tools.html#example.cql.to.rpn.bathprofile">CQL to RPN using Bath Profile</a></dt><dt>7.13. <a href="tools.oid.html#tools.oid.bib1.1">Create OID on stack</a></dt><dt>7.14. <a href="tools.oid.html#tools.oid.bib1.2">Using oid_oiddotstring_to_oid</a></dt><dt>7.15. <a href="tools.oid.html#tools.oid.bib1.3">Using odr_getoidbystr</a></dt><dt>7.16. <a href="tools.oid.html#tools.oid.bib1.4">Create OID with YAZ DB</a></dt><dt>7.17. <a href="tools.oid.html#tools.oid.bib1.5">Use a built-in OID</a></dt><dt>7.18. <a href="marc.html#example.marc.display">Display of MARC record</a></dt><dt>7.19. <a href="tools.retrieval.html#tools.retrieval.marc21">MARC21 backend</a></dt><dt>7.20. <a href="tools.retrieval.html#tools.retrieval.marcxml">MARCXML backend</a></dt><dt>8.1. <a href="odr.use.html#example.odr.encoding.and.decoding.functions">Encoding and decoding functions</a></dt><dt>8.2. <a href="odr.use.html#example.odr.encoding.of.integer">Encoding and decoding of an integer</a></dt><dt>8.3. <a href="odr.use.html#example.odr.element.path.record">Element Path for record</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="introduction.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. Introduction</td></tr></table></div></body></html>
  • yaz/trunk/fuentes/doc/installation.html

    r255 r265  
    1414    <a class="ulink" href="http://www.freebsd.org/" target="_top">FreeBSD (i386)</a>,
    1515    <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.
    1817   </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,
    2019    DEC Unix, <a class="ulink" href="http://www.netbsd.org" target="_top">NetBSD</a>,
    2120    <a class="ulink" href="http://www.openbsd.org" target="_top">OpenBSD</a>,
  • yaz/trunk/fuentes/doc/installation.unix.html

    r255 r265  
    2323      <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>
    2424     </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>.
    2829    </p><p>
    2930     If you wish to use character set conversion facilities in YAZ or if you
     
    5253     <a class="ulink" href="http://www.gnu.org/software/libtool/" target="_top">Libtool</a>
    5354     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 the
     55     You do <span class="emphasis"><em>not</em></span> need these tools unless you're using the
    5556     Git version of YAZ.
    5657    </p><p>
     
    6263     written in <a class="ulink" href="http://www.tcl.tk/" target="_top">Tcl</a>.
    6364     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 built own codecs
     65     version of YAZ or you're using the compiler to build your own codecs
    6566     for private ASN.1.
    6667    </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:
    6975    </p><pre class="screen">
    7076     ./configure
     
    121127        search for iconv on the system. Use this option if it
    122128        doesn't find iconv. Alternatively,
    123         <code class="literal">--without-iconv</code>, can be uset to force YAZ
     129        <code class="literal">--without-iconv</code>, can be used to force YAZ
    124130        not to use iconv.
    125131        </p></dd><dt><span class="term">
     
    130136        Use this option if you want XSLT and XML support.
    131137        By default, configure will
    132         search for libxslt on the system. Use this option if it
     138        search for libxslt on the system. Use this option if
    133139        libxslt is not found automatically. Alternatively,
    134140        <code class="literal">--without-xslt</code>, can be used to force YAZ
     
    141147        Use this option if you want YAZ to use XML and support SRU/Solr.
    142148        By default, configure will
    143         search for libxml2 on the system. Use this option if it
     149        search for libxml2 on the system. Use this option if
    144150        libxml2 is not found automatically. Alternatively,
    145151        <code class="literal">--without-xml2</code>, can be used to force YAZ
     
    161167        <span class="application">icu-config</span> will be used if found.
    162168        </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 with
    165         <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 script
    167         <span class="application">libgcrypt-config</span> will be used if found.
    168         </p></dd><dt><span class="term">
    169169        <code class="literal">--with-memcached</code>
    170170       </span></dt><dd><p>YAZ will be linked with
    171171        <a class="ulink" href="http://libmemcached.org/" target="_top">libMemcached</a> to allow
    172172        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.
    175174        Note that 0.40 of libmemcached is required.
    176175       </p></dd><dt><span class="term">
     
    179178        to allow for result-set caching for ZOOM on a
    180179        <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.
    183181       </p></dd></dl></div><p>
    184182    </p><p>
     
    253251     applications using the YAZ toolkit.
    254252     If you're used to Makefiles this shouldn't be hard. As for
    255      other libraries you have used before, you have to set a proper include
     253     other libraries you have used before, you need to set a proper include
    256254     path for your C/C++ compiler and specify the location of
    257255     YAZ libraries. You can do it by hand, but generally we suggest
  • yaz/trunk/fuentes/doc/installation.win32.html

    r255 r265  
    11<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
    22   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>.
    46   The installer comes with source too - in case you wish to
    57   compile YAZ with different compiler options, etc.
     
    810     with <a class="ulink" href="http://www.visualstudio.com" target="_top">
    911     Microsoft Visual Studio</a>. It has been tested with
    10      Microsoft Visual Studio 2013.
     12     Microsoft Visual Studio 2015.
    1113    </p><p>
    1214     Start a command prompt and switch the sub directory
     
    3840        (<code class="filename">cql.y</code>).
    3941       </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>.
    4246       </p></dd><dt><span class="term"><code class="literal">HAVE_ICONV</code>,
    4347       <code class="literal">ICONV_DIR</code></span></dt><dd><p>
     
    6367         <a class="ulink" href="http://xmlsoft.org/XSLT/" target="_top">libxslt</a> source directory.
    6468        </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.
    6670         </p></div></dd><dt><span class="term"><code class="literal">HAVE_ICU</code>,
    6771       <code class="literal">ICU_DIR</code></span></dt><dd><p>
     
    7175         <code class="literal">ICU_DIR</code> to the
    7276         <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>.
    7383        </p></dd></dl></div><p>
    7484    </p><p>
     
    124134      </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
    125135       is enabled for YAZ. Only if ICU is available this program is
    126        build.
     136       built.
    127137      </p></dd><dt><span class="term"><code class="filename">bin/zoomsh.exe</code></span></dt><dd><p>
    128138        Simple console application implemented on top of the
     
    132142      </p></dd><dt><span class="term"><code class="filename">bin/zoomtst1.exe</code>,
    133143       <code class="filename">bin/zoomtst2.exe</code>, ..</span></dt><dd><p>
    134         Several small applications that demonstrates the ZOOM API.
     144        Several small applications that demonstrate the ZOOM API.
    135145      </p></dd></dl></div><p>
    136146    </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  
    33    toolkit offers several different levels of access to the
    44    <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> and
     5    <a class="ulink" href="http://www.nlc-bnc.ca/iso/ill/standard.htm" target="_top">ILL</a> and
    66    <a class="ulink" href="http://www.loc.gov/standards/sru/" target="_top">SRU</a>
    77    protocols.
     
    2121    level APIs of YAZ.
    2222   </p><p>
    23     The YAZ toolkit modules is shown in figure <a class="xref" href="introduction.api.html#yaz.layer" title="Figure 1.1. YAZ layers">Figure 1.1, &#8220;YAZ layers&#8221;</a>.
     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, &#8220;YAZ layers&#8221;</a>.
    2424   </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>
    2525    There are four layers.
     
    6666   </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    6767     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 you
     68     are not adding a new protocol of your own, the only parts of <acronym class="acronym">ODR</acronym> that you
    6969     need to worry about are documented in
    7070     <a class="xref" href="odr.use.html" title="2. Using ODR">Section 2, &#8220;Using ODR&#8221;</a>.
  • yaz/trunk/fuentes/doc/introduction.html

    r255 r265  
    1414    </p></li><li class="listitem"><p>
    1515      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>
    1717      protocol.
    1818    </p></li><li class="listitem"><p>
    1919      Supports
    20       <a class="ulink" href="http://lucene.apache.org/solr/" target="_top">Solr</a> Web Service version 1.4.x
     20      <a class="ulink" href="http://lucene.apache.org/solr/" target="_top">Apache Solr</a> Web Service version 1.4.x
    2121      (client side only)
    2222     </p></li><li class="listitem"><p>
     
    5151  </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>
    5252    Most implementors only need to read a fraction of the
    53     material in thie manual, so a quick walkthrough of the chapters
     53    material in this manual, so a quick walkthrough of the chapters
    5454    is in order.
    5555   </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
    5656      <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 reading this
     57      instructions for YAZ. You don't need to read this
    5858      if you expect to download YAZ binaries.
    5959      However, the chapter contains information about how
     
    6262     </p></li><li class="listitem"><p>
    6363      <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 read if you wish to develop a Z39.50/SRU
     64      This is definitely worth reading if you wish to develop a Z39.50/SRU
    6565      client.
    6666     </p></li><li class="listitem"><p>
     
    7070    </p></li><li class="listitem"><p>
    7171      <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 server
     72      client. If you're a developer and wish to test your server
    7373      or a server from another party, you might find this chapter
    7474      useful.
     
    9191      ODR module which is the work horse that encodes and decodes
    9292      BER packages. Implementors using ZOOM only, do <span class="emphasis"><em>not</em></span>
    93       need reading this.
     93      need to read this.
    9494      Most other Z39.50 implementors only need to read the first two
    9595      sections (<a class="xref" href="odr.html#odr.introduction" title="1. Introduction">Section 1, &#8220;Introduction&#8221;</a> and
  • yaz/trunk/fuentes/doc/license.html

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

    r255 r265  
    1 <!ENTITY version "5.14.3">
     1<!ENTITY version "5.15.2">
  • yaz/trunk/fuentes/doc/manref.xml

    r255 r265  
    33 <refentryinfo>
    44  <productname class="trade">YAZ</productname>
    5   <productnumber>5.14.3</productnumber>
    6   <info><orgname>Index Data</orgname></info>
     5  <productnumber>5.15.2</productnumber>
     6  <orgname>Index Data</orgname>
    77 </refentryinfo>
    88
     
    8282     <listitem><para>
    8383       If specified, logging of protocol packages will be appended
    84        file given. If <replaceable>filename</replaceable> is
     84       to the file given. If <replaceable>filename</replaceable> is
    8585       specified as <literal moreinfo="none">-</literal>, the output is written
    8686       to <literal moreinfo="none">stdout</literal>.
     
    142142       connect to a proxy on the address and port given.
    143143       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.
    145145      </para></listitem>
    146146    </varlistentry>
     
    248248    <listitem>
    249249     <para>Sets the name(s) of the database(s) to search. One or more
    250       databases may be specified separated by blanks. This commands overrides
     250      databases may be specified, separated by blanks. This command overrides
    251251      the database given in <replaceable>zurl</replaceable>.
    252252     </para>
     
    261261      position given by
    262262      <replaceable>start</replaceable>
    263       a number of records given by <replaceable>number</replaceable>. If
     263      and a number of records given by <replaceable>number</replaceable>. If
    264264      <replaceable>start</replaceable> is not given, then the client
    265       will fetch from position of the last retrieved record plus 1. If
     265      will fetch from the position of the last retrieved record plus 1. If
    266266      <replaceable>number</replaceable> is not given, then one record will
    267267      be fetched at a time.
     
    305305     <simpara>
    306306      Sets preferred position for scan. This value
    307       is used in next scan. By default position is 1.
     307      is used in the next scan. By default, position is 1.
    308308     </simpara>
    309309    </listitem>
     
    324324    <listitem>
    325325     <simpara>
    326       Set step-size for scan. This value is used in next scan
     326      Set step-size for scan. This value is used in the next scan
    327327      sent to the target. By default step-size is 0.
    328328     </simpara>
     
    368368    </term>
    369369    <listitem>
    370      <para>Sets up a authentication string if a server requires
     370     <para>Sets up an authentication string if a server requires
    371371      authentication (v2 OpenStyle). The authentication string is first
    372372      sent to the server when the
     
    439439    </term>
    440440    <listitem>
    441      <para>Sets the number of records should be returned if the
     441     <para>Sets the number of records that should be returned if the
    442442      number of records in the result set is between the values of
    443443      <literal moreinfo="none">lslb</literal> and <literal moreinfo="none">ssub</literal>.
     
    495495    <listitem>
    496496     <para>Sets the element set name for the records. Many targets support
    497       element sets are B (for brief) and F (for full).
     497      element sets B (for brief) and F (for full).
    498498     </para>
    499499    </listitem>
     
    519519      <literal moreinfo="none">cql</literal> for CQL (Type-104 search with CQL OID),
    520520      <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),
    522522      <literal moreinfo="none">cql2rpn</literal> for
    523523      CQL to RPN conversion (Type-1 Query).
     
    570570      "&lt;", then the following characters are treated as a filename
    571571      with the records to be updated. Otherwise doc is treated as
    572       a document itself. The doc may also be quited in double quotes.
     572      a document itself. The doc may also be quoted in double quotes.
    573573      If doc is omitted, the last received record (as part of present
    574574      response or piggybacked search response) is used for the update.
     
    583583    <listitem>
    584584     <para>Executes list of commands from
    585       file <replaceable>filename</replaceable>, just like source on
     585      file <replaceable>filename</replaceable>, just like 'source' on
    586586      most UNIX shells. A single dot (<literal moreinfo="none">.</literal>) can be used
    587587      as an alternative.
     
    632632    </term>
    633633    <listitem>
    634      <para>Specifies whether YAZ client automatically reconnect if
     634     <para>Specifies whether YAZ client automatically reconnects if the
    635635      target closes connection (Z39.50 only).
    636636     </para>
     
    649649     <para>Specifies whether YAZ client should wait for
    650650      response protocol packages after a request.
    651       By default YAZ client waits (on) for response packages immediately
     651      By default YAZ client waits (<literal moreinfo="none">on</literal>) for response packages immediately
    652652      after a command (find, show) has been issued. If <literal moreinfo="none">off</literal>
    653653      is used, YAZ client does not attempt to receive packages automatically.
     
    715715     </para>
    716716     <para>
    717       If <replaceable>marcharset</replaceable> is given, it specifies name
     717      If <replaceable>marccharset</replaceable> is given, it specifies name
    718718      of the character set of retrieved MARC records from server. See
    719       also <literal moreinfo="none">marcharset</literal> command.
     719      also <literal moreinfo="none">marccharset</literal> command.
    720720     </para>
    721721     <note>
     
    828828      name for the OID, <replaceable>class</replaceable> is the
    829829      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>,
    831831      <literal moreinfo="none">absyn</literal>, <literal moreinfo="none">attet</literal>,
    832832      <literal moreinfo="none">transyn</literal>, <literal moreinfo="none">diagset</literal>,
     
    954954    f "donald knuth"
    955955   </screen>
    956    In those queries no attributes was specified.
     956   In those queries, no attributes were specified.
    957957   This leaves it up to the server what fields to search but
    958    most servers will search in all fields. Some servers does not
     958   most servers will search in all fields. Some servers do not
    959959   support this feature though, and require that some attributes
    960960   are defined. To add one attribute you could do:
     
    10041004 <refentryinfo>
    10051005  <productname class="trade">YAZ</productname>
    1006   <productnumber>5.14.3</productnumber>
    1007   <info><orgname>Index Data</orgname></info>
     1006  <productnumber>5.15.2</productnumber>
     1007  <orgname>Index Data</orgname>
    10081008 </refentryinfo>
    10091009
     
    10761076  </para>
    10771077  <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.
    10791079  </para>
    10801080 </refsect1>
     
    11171117  <listitem><para>
    11181118   Operate the server in threaded mode. The server creates a thread
    1119    for each connection rather than a fork a process. Only available
    1120    on UNIX systems that offers POSIX threads.
     1119   for each connection rather than fork a process. Only available
     1120   on UNIX systems that offer POSIX threads.
    11211121  </para></listitem>
    11221122 </varlistentry>
     
    11821182  <term><literal moreinfo="none">-w </literal><replaceable>dir</replaceable></term>
    11831183  <listitem><para>
    1184    The server changes to this directory during before listening
    1185    on incoming connections. This option is useful
     1184   The server changes to this directory before listening
     1185   to incoming connections. This option is useful
    11861186   when the server is operating from the <application moreinfo="none">inetd</application>
    11871187   daemon (see <literal moreinfo="none">-i</literal>).
     
    11921192 </term>
    11931193 <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
    11951195  file given by <replaceable>pidfile</replaceable>.
    11961196  A typical location would be <filename moreinfo="none">/var/run/yaz-ztest.pid</filename>.
     
    13111311    to return any number of hits. <command moreinfo="none">yaz-ztest</command> includes
    13121312    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.
    13151315   </para>
    13161316   <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",
    13181318    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.
    13201320   </para>
    13211321   <para>
    13221322    yaz-ztest may also return predefined XML records (for testing).
    13231323    This is enabled if <literal moreinfo="none">YAZ_ZTEST_XML_FETCH</literal> environment
    1324     variable is defined. A record is fetched form a file (one record per file).
     1324    variable is defined. A record is fetched from a file (one record per file).
    13251325    The path for the filename is
    13261326    <replaceable>F</replaceable><replaceable>E</replaceable><literal moreinfo="none">.</literal><replaceable>d</replaceable><literal moreinfo="none">.xml</literal>
     
    13511351     value which specifies the delay in seconds.
    13521352     Alternatively the value may be given as two floating point numbers
    1353      separated by colon, which wil make <command moreinfo="none">yaz-ztest</command> perform
     1353     separated by colon, which will make <command moreinfo="none">yaz-ztest</command> perform
    13541354     a random sleep between the first and second number.
    13551355   </para>
     
    13901390<note>
    13911391 <para>
    1392   Not all Z39.50 clients allows the VHOST information to be set.
    1393   For those the selection of the backend must rely on the
     1392  Not all Z39.50 clients allow the VHOST information to be set.
     1393  For those, the selection of the backend must rely on the
    13941394  TCP/IP information alone (port and address).
    13951395 </para>
     
    14231423    <listitem>
    14241424     <para>
    1425       identifier for this listener. This may be referred to from
     1425      Identifier for this listener. This may be referred to from
    14261426      server sections.
    14271427     </para>
     
    14751475    <para>
    14761476     Specifies a working directory for this backend server. If
    1477      specifid, the YAZ fronend changes current working directory
     1477     specified, the YAZ frontend changes current working directory
    14781478     to this directory whenever a backend of this type is
    14791479     started (backend handler bend_start), stopped (backend handler hand_stop)
     
    14971497    <para>
    14981498     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"/>.
    15001500     If given, the backend server will only "see" a Type-1/RPN query.
    15011501    </para>
     
    15071507    <para>
    15081508     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"/>.
    15101510     If given, the backend server will only "see" a Type-1/RPN query.
    15111511    </para>
     
    15171517    <para>
    15181518     Specifies the stylesheet reference to be part of SRU HTTP responses
    1519      when the client does not specify one. If neither this is given, nor
    1520      the client specifies one, no stylesheet reference is part of the
     1519     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
    15211521     SRU HTTP response.
    15221522    </para>
     
    15381538    <para>
    15391539     Specifies a path for local file access using HTTP. All URLs with
    1540      a leading prefix (/ exluded) that matches the value of docpath
     1540     a leading prefix (/ excluded) that matches the value of <literal moreinfo="none">docpath</literal>
    15411541     are used for file access. For example, if the server is to offer
    15421542     access in directory <literal moreinfo="none">xsl</literal>, the docpath would be
    15431543     <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.
    15451545    </para>
    15461546   </listitem>
     
    15521552     Specifies SRW/SRU ZeeRex content for this server. Copied verbatim
    15531553     to the client. As things are now, some of the Explain content
    1554      seeem redundant because host information, etc. is also stored
     1554     seem redundant because host information, etc. is also stored
    15551555     elsewhere.
    15561556    </para>
     
    15621562    <para>
    15631563     Specifies maximum record size/message size, in bytes. This
    1564      value also servers as maximum size of <emphasis>incoming</emphasis>
     1564     value also serves as the maximum size of <emphasis>incoming</emphasis>
    15651565     packages (for Record Updates etc). It's the same value as that
    15661566     given by the <literal moreinfo="none">-k</literal> option.
     
    15721572   <listitem>
    15731573    <para>
    1574      Enables the retrieval facility supporting conversions and
     1574     Enables the retrieval facility to support conversions and
    15751575     specifications of record formats/types.
    15761576     See <xref linkend="tools.retrieval"/> for
     
    16271627 <literal moreinfo="none">"server2"</literal> is reached by the two listeners specified.
    16281628 In order to distinguish between the two, a virtual host has
    1629  been specified for each of server in the <literal moreinfo="none">host</literal>
     1629 been specified for each server in the <literal moreinfo="none">host</literal>
    16301630 elements.
    16311631</para>
     
    16731673 <refentryinfo>
    16741674  <productname class="trade">YAZ</productname>
    1675   <productnumber>5.14.3</productnumber>
    1676   <info><orgname>Index Data</orgname></info>
     1675  <productnumber>5.15.2</productnumber>
     1676  <orgname>Index Data</orgname>
    16771677 </refentryinfo>
    16781678
     
    17801780    <term>-V</term>
    17811781    <listitem><para>
    1782       veturns YAZ SHA1 ID (from Git) and version.
     1782      Returns YAZ SHA1 ID (from Git) and version.
    17831783     </para></listitem>
    17841784   </varlistentry>
     
    18111811 <refentryinfo>
    18121812  <productname class="trade">YAZ</productname>
    1813   <productnumber>5.14.3</productnumber>
    1814   <info><orgname>Index Data</orgname></info>
     1813  <productnumber>5.15.2</productnumber>
     1814  <orgname>Index Data</orgname>
    18151815 </refentryinfo>
    18161816
     
    18391839 <refsect1><title>COPYRIGHT</title>
    18401840  <para>
    1841    Copyright © 1995-2015 Index Data.
     1841   Copyright © 1995-2016 Index Data.
    18421842  </para>
    18431843  <para>
     
    19271927 <refentryinfo>
    19281928  <productname class="trade">YAZ</productname>
    1929   <productnumber>5.14.3</productnumber>
    1930   <info><orgname>Index Data</orgname></info>
     1929  <productnumber>5.15.2</productnumber>
     1930  <orgname>Index Data</orgname>
    19311931 </refentryinfo>
    19321932
     
    21052105 <refentryinfo>
    21062106  <productname class="trade">YAZ</productname>
    2107   <productnumber>5.14.3</productnumber>
    2108   <info><orgname>Index Data</orgname></info>
     2107  <productnumber>5.15.2</productnumber>
     2108  <orgname>Index Data</orgname>
    21092109 </refentryinfo>
    21102110
     
    21462146   <command moreinfo="none">yaz-asncomp</command> allows you to specify name of
    21472147   resulting source via options. Alternatively, you can specify
    2148    a DEFINISIONS file, which provides customized output to
     2148   a DEFINITIONS file, which provides customized output to
    21492149   many output files - if the ASN.1 specification file consists
    21502150   of many modules.
     
    22292229   traditional rules for Shell like configuration files.
    22302230   That is # denotes the beginning of a comment. Definitions
    2231    are line oriented. The definitions files usually consists of
     2231   are line oriented. The definitions files usually consist of
    22322232   a series of variable assignments of the form:
    22332233  </para>
     
    23152315       <replaceable>name</replaceable> in module
    23162316       <replaceable>module</replaceable> to value.
    2317        Value consists of to or three tokens. The first token
     2317       Value consists of two or three tokens. The first token
    23182318       is name of the integer in the <literal moreinfo="none">union</literal> that
    23192319       is used as selector for the <literal moreinfo="none">union</literal> itself.
     
    23492349 <refentryinfo>
    23502350  <productname class="trade">YAZ</productname>
    2351   <productnumber>5.14.3</productnumber>
    2352   <info><orgname>Index Data</orgname></info>
     2351  <productnumber>5.15.2</productnumber>
     2352  <orgname>Index Data</orgname>
    23532353 </refentryinfo>
    23542354
     
    24482448    <term>-f <replaceable>from</replaceable></term>
    24492449    <listitem><para>
    2450       Specify the character set <replaceable>from</replaceable>
     2450      Specify the character set
    24512451      of the input MARC record.
    24522452      Should be used in conjunction with option <literal moreinfo="none">-t</literal>.
     
    24582458    <term>-t <replaceable>to</replaceable></term>
    24592459    <listitem><para>
    2460       Specify the character set <replaceable>of</replaceable>
     2460      Specify the character set
    24612461      of the output.
    24622462      Should be used in conjunction with option <literal moreinfo="none">-f</literal>.
     
    24822482      Writes a chunk of records to a separate file with prefix given,
    24832483      i.e. splits a record batch into files with only at most
    2484       "chunk" ISO2709 record per file. By default chunk is 1 (one record
     2484      "chunk" ISO2709 records per file. By default chunk is 1 (one record
    24852485      per file). See option <literal moreinfo="none">-C</literal>.
    24862486     </para></listitem>
     
    24982498    <term>-p</term>
    24992499    <listitem><para>
    2500       Makes yaz-marcdump prints record number and input file offset
     2500      Makes yaz-marcdump print record number and input file offset
    25012501      of each record read.
    25022502     </para></listitem>
     
    25062506    <term>-n</term>
    25072507    <listitem><para>
    2508       MARC output is omitted so that MARC input is only checkecd.
     2508      MARC output is omitted so that MARC input is only checked.
    25092509     </para></listitem>
    25102510   </varlistentry>
     
    25822582 <refentryinfo>
    25832583  <productname class="trade">YAZ</productname>
    2584   <productnumber>5.14.3</productnumber>
    2585   <info><orgname>Index Data</orgname></info>
     2584  <productnumber>5.15.2</productnumber>
     2585  <orgname>Index Data</orgname>
    25862586 </refentryinfo>
    25872587
     
    26092609 <refsect1><title>DESCRIPTION</title>
    26102610  <para>
    2611    <command moreinfo="none">yaz-iconv</command> converts data in file in character
     2611   <command moreinfo="none">yaz-iconv</command> converts data in the character
    26122612   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 the
     2613   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
    26172617   <command moreinfo="none">iconv</command> found on many POSIX systems (Glibc, Solaris, etc).
    26182618  </para>
     
    26592659   <filename moreinfo="none">yaz/yaz-iconv.h</filename> is a wrapper for the
    26602660   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)
    26622662   that are supported by YAZ. Each character set is marked with either
    26632663   <emphasis>encode</emphasis> or <emphasis>decode</emphasis>. If
    2664    an encoding is encode-enabled YAZ may convert <emphasis>to</emphasis>
    2665    to the designated encoding. If an encoding is decode-enabled, YAZ
     2664   an encoding is encode-enabled, YAZ may convert <emphasis>to</emphasis>
     2665   the designated encoding. If an encoding is decode-enabled, YAZ
    26662666   may convert <emphasis>from</emphasis> the designated encoding.
    26672667  </para>
     
    26802680    <listitem>
    26812681     <para>
    2682       Like MARC8 but with conversion prefers non-combined characters
     2682      Like MARC8 but conversion prefers non-combined characters
    26832683      in the Latin-1 plane over combined characters.
    26842684     </para>