[Koha] Z39.50 encoding problem (tested on 2 koha servers)

Tajoli Zeno z.tajoli at cineca.it
Thu Jul 6 20:11:56 NZST 2017


Hi Jose',

Il 05/07/2017 15:14, anjoze ha scritto:
> I've looked at tables with Workbench and all tables have Collation set
> utf8_unicode_ci
> Then I've added to my mysql conf:
> /[client]
> default-character-set=utf8
> 
> [mysql]
> default-character-set=utf8
> 
> [mysqld]
> collation-server = utf8_unicode_ci
> init-connect='SET NAMES utf8'
> character-set-server = utf8/
> 
> Then:
> mysql> SHOW VARIABLES LIKE '%char%';
> +--------------------------+----------------------------+
> | Variable_name            | Value                      |
> +--------------------------+----------------------------+
> | character_set_client     | utf8                       |
> | character_set_connection | utf8                       |
> | character_set_database   | utf8                       |
> | character_set_filesystem | binary                     |
> | character_set_results    | utf8                       |
> | character_set_server     | utf8                       |
> | character_set_system     | utf8                       |
> | character_sets_dir       | /usr/share/mysql/charsets/ |
> +--------------------------+----------------------------+
> 
> Still have the same problem with Z39.50 characters.

last try:
close apache, plack and zebra.
On linux command line go to the correct dir and with the koha user do:
./cleanup_database.pl --verbose --z3950

Then retest z39.50 searches.

Bye
Zeno Tajoli


-- 
Zeno Tajoli
/SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche
Email: z.tajoli at cineca.it Fax: 051/6132198
*CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)


More information about the Koha mailing list