Summary: | Extend CGI to provide a param_utf8_decode method | ||
---|---|---|---|
Product: | Koha | Reporter: | Tomás Cohen Arazi (tcohen) <tomascohen> |
Component: | Architecture, internals, and plumbing | Assignee: | Galen Charlton <gmcharlt> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | jonathan.druart, ketan, m.de.rooy |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11944 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Attachments: | Bug 10075 - Extend CGI and overload the param method to one that decodes utf8 by default |
Description
Tomás Cohen Arazi (tcohen)
2013-04-18 16:30:26 UTC
Created attachment 17658 [details] [review] Bug 10075 - Extend CGI and overload the param method to one that decodes utf8 by default The key idea is to provide a way to avoid writing decode stuff every time we read a param from CGI. Adds a method for explicitly not decoding input (for images, iso data, etc). Regards To+ Sponsored-by: Universidad Nacional de Córdoba I do not oppose to this idea, but have some questions: Why not use -utf8 on CGI? Should you really add a no_decode parameter? It is a rather complicated way of using CGI without this wrapper. I am working on a related bug - 6554. utf decoding needs to be done in a few places. Would be great if people submit more ideas/preferences here. Ketan (In reply to M. de Rooy from comment #2) > I do not oppose to this idea, but have some questions: > Why not use -utf8 on CGI? > Should you really add a no_decode parameter? It is a rather complicated way > of using CGI without this wrapper. With 11944, this will certainly become invalid. |