https://metacpan.org/dist/CGI/view/lib/CGI.pod#Creating-a-standard-http-header
"The -charset parameter can be used to control the character set sent to the browser. If not provided, defaults to ISO-8859-1."
So you'll need to tell CGI.pm explicitly to use utf8 via $cgi->header(-charset => 'utf-8') AND make sure the content is correctly encoded.
That being said, I would not use plain CGI.pm but look into Plack/PSGI instead (which has a CGI compat mode).
]]>I know that this is a bit more complex in e.g. Switzerland than in e.g. Austria, but it is so much easier for especially new speakers to speak in their native language.
]]>P.S.: As it seems that the ironman perl blog aggregator is down, I (ab)use blogs.perl.org to alert you of my new posts..
]]>P.S. As http://ironman.enlightenedperl.org/ seems to be down, I'm back to using blogs.perl.org for syndication...
]]>We are currently moving from logging to syslog to logging to/via graylog, and having structured log messages would be a huge win.
]]>I do hope for the first option. But I fear that in fact nobody wants to gain endless glory by organising our yearly conference.
So here's again the Call for Venue for the Perl Conference in Europe 2018 (formerly know as YAPC::Europe). And please do consider submitting a proposal, or it might be a very sad summer in 2018...
More information is available at the YEF website.
Generally, when working with micro/no-frameworks, I think it makes most sense to implement as little as possible on your own, and do the rest in Plack/PSGI...
]]>$ENV{DBIC_TRACE_PROFILE}=console
?
ok, DBIC_TRACE_PROFILE also won't work with plain DBI (I guess)..
]]>