Hello, I have the same problem when trying to save records with cyrillic, Japanese, or other characters. The only way I've found to fix this is to click on the "..." next to the 000 Leader field and on "9 - Character coding scheme" select "a - UCS/Unicode" from the dropdown menu. This allows me to save the record. I wanted to hide this field from our users in our custom framework, but if I do they won't be able to save records containing certain characters. Does someone know how to make it always be UCS/Unicode for all records? Thanks, Melisa 2009/8/3 BWS Johnson <mhelman@illinoisalumni.org>
Salvete!
More specifically, what *encoding* of the characters have you tried? Combining characters or composed?
Users are typically confused to realize there are multiple encodings for various characters, so it is probably worth your time to check by hex value or unicode number. In my experience, combining characters are less reliably interpreted by Koha and Zebra than composed ones. Then trying to use multiple combining characters *always* failed for me.
Is this a problem with a solution? It seems like a problem with a difficult solution and not an unsolvable problem. It seems like a good one to address slowly but surely, cause if we do it well, I can only imagine that a lot of people would be happier for it.
Cheers, Brooke
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha