Fellow Brethren,

Most of my CGI scripts follow a common workflow:

  1. Fetch CGI GET and POST params
  2. Decode them into perls internal format
  3. Do some computations, and fill out a template
  4. Encode the template as utf8, and send it to the browser

My question is: how can I automate step 2, decode the return value of param().

The charset methods seems to affect only the generated header:

!/usr/bin/perl use strict; use warnings; use CGI; use utf8; my $q = new CGI; $q->charset('utf8'); my $str = $q->param('foo'); print utf8::is_utf8($str) ? 1 : 0, "\n"; print $CGI::VERSION, "\n"; __END__ $ perl foo.pl foo=bää 0 3.15

Currently my only idea is to subclass CGI, but somehow I think there should be a better solution. But what is it?

I've read Understanding CGI.pm and UTF-8 handling but it didn't enlighten me.


In reply to CGI.pm: automatically decode param() by moritz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.