Re^2: How do I convince my Perl script that UTF-8 from an HTML form really is UTF-8?

As of today, static pages can declare their own encoding in a meta element, e.g. <meta charset="utf-8">

This is what I mean when I said I declared the charset in the HTML

If you write UTF-8 in the response CGI script, you ought to print "Content-type: text/plain; charset=utf-8\n\n":

The server had already added the UTF-8 content type in the HTTP headers

binmode STDOUT, ":encoding(UTF-8)";

I had done this but forgot to include it in the code snippet. It still didn't work.

Comment on Re^2: How do I convince my Perl script that UTF-8 from an HTML form really is UTF-8? Select or Download Code

Replies are listed 'Best First'.

Re^3: How do I convince my Perl script that UTF-8 from an HTML form really is UTF-8?
by haj (Vicar) on Mar 11, 2020 at 21:24 UTC

The server had already added the UTF-8 content type in the HTTP headers

Could you please elaborate which server you are using, and how you configure it to modify the content type of a CGI script? You could also verify in your browser which encoding it uses for your text/plain response.

I also had a look at the source of CGI::Simple and found out:

The module will decode parameters for you only if you set the global variable $CGI::Simple::PARAM_UTF8 to a true value. That's sort of difficult to guess, since it isn't documented. Of course, you can decode yourself, but it looks like you didn't.
The module will add ; charset=utf-8 to the content type header only if you print it as print $q->header(-type => 'text/plain');, but not if you just print "Content-type: text/plain\n\n";.

just works

use strict;
use warnings;
use CGI::Simple;
$CGI::Simple::PARAM_UTF8 = 1;

my $q = CGI::Simple->new();
$q->charset('utf-8');

binmode STDOUT,':encoding(UTF-8)';
print $q->header(-type => 'text/plain');
print $q->param('text'),"\n";
[download]

[reply]
[d/l]


"be consistent"
	PerlMonks