http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13239 Bug ID: 13239 Summary: MySQL Character encoding utf8 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt@gmail.com Reporter: martin.renvoize@ptfs-europe.com QA Contact: testopia@bugs.koha-community.org CC: abl@biblos.pk.edu.pl, benjamin.rokseth@kul.oslo.kommune.no, bgkriegel@gmail.com, boutrosboutrosboutros@gmail.com, dpavlin@rot13.org, hbraum@nekls.org, jonathan.druart@biblibre.com, josef.moravec@gmail.com, katrin.fischer@bsz-bw.de, m.de.rooy@rijksmuseum.nl, magnus@enger.priv.no, martin.renvoize@ptfs-europe.com, paola.rossi@cineca.it, tomascohen@gmail.com, z.tajoli@cineca.it Depends on: 11248, 11906, 11944 Blocks: 7380, 10855, 11844, 12176, 12637, 12832 As discussed in bug 11944 we should use utf8_mb4 as default mysql encoding where the mysql version allows for it. This would allow for the entire utf8 character range rather than an arbitrarily truncated set as chosen by mysql during their first attempt at utf8 compatibility. As promised, I've opened this followup bug to track this issue. -- You are receiving this mail because: You are watching all bug changes.