Hi Jose',
Il 28/06/2017 17:10, anjoze ha scritto:
Locale is the same on both servers:
LANG=pt_PT.UTF-8
LANGUAGE=pt:pt_BR:en
LC_CTYPE="pt_PT.UTF-8"
LC_NUMERIC=pt_PT
LC_TIME=pt_PT
LC_COLLATE="pt_PT.UTF-8"
LC_MONETARY=pt_PT
LC_MESSAGES="pt_PT.UTF-8"
LC_PAPER=pt_PT
LC_NAME=pt_PT
LC_ADDRESS=pt_PT
LC_TELEPHONE=pt_PT
LC_MEASUREMENT=pt_PT
LC_IDENTIFICATION=pt_PT
LC_ALL=
Ok, but do a better setup.
Insert "pt_PT.UTF-8" in all variables.
But "LANGUAGE=pt:pt_BR:en" is good.
*SERVER1*:
+--------------------------+----------------------------+
| Variable_name | Value |
+--------------------------+----------------------------+
| character_set_client | utf8mb4 |
| character_set_connection | utf8mb4 |
| character_set_database | utf8mb4 |
| character_set_filesystem | binary |
| character_set_results | utf8mb4 |
| character_set_server | utf8mb4 |
| character_set_system | utf8 |
| character_sets_dir | /usr/share/mysql/charsets/ |
+--------------------------+----------------------------+
*SERVER2:*
+--------------------------+----------------------------+
| Variable_name | Value |
+--------------------------+----------------------------+
| character_set_client | utf8 |
| character_set_connection | utf8 |
| character_set_database | latin1 |
| character_set_filesystem | binary |
| character_set_results | utf8 |
| character_set_server | latin1 |
| character_set_system | utf8 |
| character_sets_dir | /usr/share/mysql/charsets/ |
+--------------------------+----------------------------+
Server2 is clearly wrong, you need to fix /etc/mysql/my.conf
Server1 could be OK, but 'utf8mb4' is not Mysql standard on Ubuntu as I
know, check all conf files in /etc/mysql and into subdirs.
Shouldn't be Z39.50 independent of Mysql schema?
This is not MySQL schema, it is MySQL setup.
Z39.50 is not indipendent from MySQL setup.
When you see data in z39.50 derivate cataloguing, those data are not
coming directly from z39.50 server. They are saved on a Mysql table and
AFTER are showing in the browser.
As you see here:
https://lists.katipo.co.nz/pipermail/koha/2017-June/048353.html
if you use yaz-client [a direct view of z39.50 data] no problems on encoding
And the same is for staged records.
If I have undestand well, Server2 is a test server, correct ?
If so, you could fix locale and MySQL setup and after try to use z39.50
from it.
If all ok, you can start to think about production changes.
To do similar changes on a production server with data IS DIFFICULT and
RISKY
You need to find a good MySQL DBA, follow his/her advice.
--
Zeno Tajoli
/SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche
Email: z.taj...@cineca.it Fax: 051/6132198
*CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)
_______________________________________________
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
