[Koha-patches] [PATCH] Bug 3226 - Extended characters inconsistantly displayed - NoZebra

2009-07-23 Thread Frédéric Demians
Fix errors introduced by previous patch on NoZebra installation. Thanks Lupin. --- C4/Search.pm | 25 + 1 files changed, 13 insertions(+), 12 deletions(-) diff --git a/C4/Search.pm b/C4/Search.pm index 4b113c1..f2f738d 100644 --- a/C4/Search.pm +++ b/C4/Search.pm @@

Re: [Koha-patches] [PATCH] Bug 3226 - Extended characters inconsistantly displayed

2009-07-14 Thread Galen Charlton
Hi, I ended up having to revert this - it had the effect of causing the facets in the OPAC and staff catalog search to disappear. Regards, Galen 2009/7/4 Frédéric Demians f.demi...@tamil.fr: When displayed on result page, some UNIMARC biblio records are marc8 to utf8 converted for whatever

[Koha-patches] [PATCH] Bug 3226 - Extended characters inconsistantly displayed

2009-07-03 Thread Frédéric Demians
When displayed on result page, some UNIMARC biblio records are marc8 to utf8 converted for whatever reason! It appears that iso2709 records in Zebra can't always properly by used to construct MARC::Record. This patch ask Zebra to return xml record rather than iso2709 and use it to create

Re: [Koha-patches] [PATCH] Bug 3226 - Extended characters inconsistantly displayed

2009-06-22 Thread LAURENT Henri-Damien
hi Why not use preferredRecordSyntax=XML ? rather than hardcoding get('xml') I have never had this problem. But it seems to me that adding a preference to connection would be safer than hardcoding a get param. -- Henri-Damien LAURENT Frédéric Demians a écrit : When displayed on result page,

Re: [Koha-patches] [PATCH] Bug 3226 - Extended characters inconsistantly displayed

2009-06-22 Thread Frédéric DEMIANS
Why not use preferredRecordSyntax=XML ? rather than hardcoding get('xml') No specific reason. I can add that in Context::_new_Zconn function. I have never had this problem. I get this issues on result page on all Koha installations using stable or development version, with UNIMARC DB and