-# Some of this Pod-using code may be useful.
-#
-#$pod->option(elementSetName => "b");
-#$pod->callback(ZOOM::Event::RECV_SEARCH, \&completed_search);
-#$pod->callback(ZOOM::Event::RECV_RECORD, \&got_record);
-##$pod->callback(exception => \&exception_thrown);
-#$pod->search_pqf("the");
-#my $err = $pod->wait();
-#die "$pod->wait() failed with error $err" if $err;
-#
-#sub completed_search {
-# my($conn, $state, $rs, $event) = @_;
-# print $conn->option("host"), ": found ", $rs->size(), " records\n";
-# $state->{next_to_fetch} = 0;
-# $state->{next_to_show} = 0;
-# request_records($conn, $rs, $state, 2);
-# return 0;
-#}
-#
-#sub got_record {
-# my($conn, $state, $rs, $event) = @_;
-#
-# {
-# # Sanity-checking assertions. These should be impossible
-# my $ns = $state->{next_to_show};
-# my $nf = $state->{next_to_fetch};
-# if ($ns > $nf) {
-# die "next_to_show > next_to_fetch ($ns > $nf)";
-# } elsif ($ns == $nf) {
-# die "next_to_show == next_to_fetch ($ns)";
-# }
-# }
-#
-# my $i = $state->{next_to_show}++;
-# my $rec = $rs->record($i);
-# print $conn->option("host"), ": record $i is ", render_record($rec), "\n";
-# request_records($conn, $rs, $state, 3)
-# if $i == $state->{next_to_fetch}-1;
-#
-# return 0;
-#}
-#
-#sub exception_thrown {
-# my($conn, $state, $rs, $exception) = @_;
-# print "Uh-oh! $exception\n";
-# return 0;
-#}
-#
-#sub request_records {
-# my($conn, $rs, $state, $count) = @_;
-#
-# my $i = $state->{next_to_fetch};
-# ZOOM::Log::log("irspy", "requesting $count records from $i");
-# $rs->records($i, $count, 0);
-# $state->{next_to_fetch} += $count;
-#}
-#
-#sub render_record {
-# my($rec) = @_;
-#
-# return "undefined" if !defined $rec;
-# return "'" . $rec->render() . "'";
-#}
+ # There doesn't seem to be a reliable way to tell what
+ # character set the server uses for these. At least one
+ # server (z3950.bcl.jcyl.es:210/AbsysCCFL) returns an ISO
+ # 8859-1 string containing an o-acute, which breaks the
+ # XML parser if we just insert it naively. It seems
+ # reasonable, though, to guess that the great majority of
+ # servers will use ASCII, Latin-1 or Unicode. The first
+ # of these is a subset of the second, so that brings it to
+ # down to two. The strategy is simply this: assume it's
+ # ASCII-Latin-1, and try to convert to UTF-8. If that
+ # conversion works, fine; if not, assume it's because the
+ # string was already UTF-8, so use it as is.
+ Text::Iconv->raise_error(1);
+ my $maybe;
+ eval {
+ $maybe = $conv->convert($val);
+ }; if (!$@ && $maybe ne $val) {
+ $conn->log("irspy", "converted '$val' from Latin-1 to UTF-8");
+ $val = $maybe;
+ }
+ $conn->record()->store_result($opt, value => $val);
+ }
+ }
+
+
+ return $ok ? ZOOM::IRSpy::Status::TEST_GOOD :
+ ZOOM::IRSpy::Status::TEST_BAD;
+}