What you mean: isn't text.

The text you typed into your browser is transformed by it as follows:

1. It is encoded using the proper character encoding.
2. Some of it is encoded using percent encoding.
3. The resulting string is joined to others to form a application/x-www-urlencoded document.

That leaves you something that's no longer your text. The proper inverse of that is:

1. Split the form data into its components.
2. Remove any percent encoding.
3. Remove the character encoding.

You're adding an additional step:

1. Remove the character encoding. (XXX)
2. Split the form data into its components.
3. Remove any percent encoding.
4. Remove the character encoding.

The fourth step notices something is odd and throws an error.

And how then transfer the text and make perl to understand it is UTF-8 encoded?

That's what the «-utf8» in «use CGI qw(:all -utf8);» does. "This makes CGI.pm treat all parameters as UTF-8 strings" by passing them to decode.

That's what the «-utf8» in «use CGI qw(:all -utf8);» does.

And without "-utf8" i can't use CGI properly because then are UTF-8 encoded GET-paramaters treated wrong? I mean, STDIN i can fix with "use open ..."

I'm gonna finally get to somewhere... Thank you!

Nõnda, WK

Huh, at least i found the difference between working production code and script here: in production i initialize CGI-object (inside BEGIN-block) before asking use open to decode STDIN. Seems, it is the significant difference. Still i hope, you could explain, why input from STDIN is not text.

The CGI object only reads from STDIN during initialisation. Anything you do to STDIN later won't affect the CGI object.