Hi all,

OCLC made updates to its z39.50 service on Sunday, and since then,
it's been sending badly encoded characters like nobody's business.
I've been able to find out how to get uncorrupted characters in
yaz-client, but I don't know how to get Evergreen to do the extra
utf-8-setting step detailed below.

Example one: just regular old searching (doesn't work)

$ yaz-client zcat.oclc.org:210/OLUCWorldCat
Z> authentication user/pass
Z> init
Z> find 9786070131356
Z> show 1
<snip />
100 1  $a Plans, Juan Jose&#x301;, $e compiler.
245 10 $a Los mejores relatos de terror llevados al cine / $c
seleccio&#x301;n, pro&#x301;logo y notas de Juan Jose&#x301; Plans.
250    $a Segunda edicio&#x301;n
264  1 $a Me&#x301;xico, D. F. : $b loqueleo, $c 2016.
<snip />

Example two: specifying utf-8 (which does work)

$ yaz-client zcat.oclc.org:210/OLUCWorldCat
Z> charset utf-8
Z> authentication user/pass
Z> init
Z> find 9786070131356
Z> show 1
<snip />
100 1  $a Plans, Juan José, $e compiler.
245 10 $a Los mejores relatos de terror llevados al cine / $c
selección, prólogo y notas de Juan José Plans.
250    $a Segunda edición
264  1 $a México, D. F. : $b loqueleo, $c 2016.
<snip />

Is there an Evergreen setting somewhere that would specify a charset
and fix this problem?

Thanks!

  -Jane

-- 
Jane Sandberg
Electronic Resources Librarian
Linn-Benton Community College
sand...@linnbenton.edu / 541-917-4655
Pronouns: she/her/hers or they/them/theirs

Reply via email to