https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22715
--- Comment #8 from Katrin Fischer <katrin.fisc...@bsz-bw.de> --- (In reply to Kyle M Hall from comment #7) > (In reply to Katrin Fischer from comment #5) > > This works as described, my only concern would be that we should handle > > these kinds of characters in a more global approach - this only fixes one > > field. > > This entire script needs to be re-engineered to output json using the JSON > module at the end of the script instead of using a template to generate > json. This will solve all these encoding problems. Makes sense. My thinking here was that as we have another patch right now making HTML available for this field it might be worth catching some of the possible problems that would break search immediately. We also have similar problems in item search - we have a publisher with a backslash that breaks the item search regularly. We might want to take a closer look at the places where we work with JSON. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
