The key idea is to provide a way to avoid writing decode/encode stuff every time we read a param from CGI.
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.
This is not needed, as we patched all cgi files to have 'use CGI qw (-utf8)' instead. *** This bug has been marked as a duplicate of bug 11944 ***