[Koha-bugs] [Bug 6554] Broken encoding in members home/search page

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Fri Mar 22 16:07:13 CET 2013


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6554

Dobrica Pavlinusic <dpavlin at rot13.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #16780|0                           |1
        is obsolete|                            |

--- Comment #36 from Dobrica Pavlinusic <dpavlin at rot13.org> ---
Created attachment 16797
  -->
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=16797&action=edit
Bug 6554 - make Koha internally utf-8 clean

In current implementation (mostly commented out in this patch)
uses heuristic to guess which strings need decoding from utf-8
to binary representation and doesn't support utf-8 characters
in templates and has problems with utf-8 data from database.

With this changes, Koha perl code always uses utf-8 encoding
correctly. All incomming data from database is allready
correctly marked as utf-8, and decoding of utf8 is required
only from Zebra and XSLT transfers which don't set utf-8 flag
correctly.

For output, standard perl :encoding(utf8) handler is used
so it also removes various "wide character" warnings as side-effect.

Test scenario:
1. make sure that you have utf-8 characters in your biblio
   records, patrons, categories etc.
2. try to search records on intranet and opac which contain
   utf-8 characters
3. install language which has utf-8 characters, e.g. uk-UA
   dpavlin at koha-dev:/srv/koha/misc/translator(bug_6554) $
   PERL5LIB=/srv/koha/ perl translate install uk-UA
4. switch language to uk-UA and verify that templates
   display correctly
5. test search and Z39.50 search and verify that caracters
   are correct

This version uses more strict :encoding(utf8) and removes
unneeded decode of XSLT which comes back as correctly encoded
strings.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are watching all bug changes.


More information about the Koha-bugs mailing list