http://qs321.pair.com?node_id=764506


in reply to CGI.pm and URL parameters

Your script still depends on what input encoding the browser is sending the form values in. You will need to trace the whole path between what the browser sends and what it tells you the encoding is, through how you process that data, to the output. Possibly, you have to add the encoding not only to a header but also as a META tag in the generated page.

Replies are listed 'Best First'.
Re^2: CGI.pm and URL parameters
by ambs (Pilgrim) on May 17, 2009 at 13:07 UTC
    Unfortunately that doesn't change a thing. If I just remembered what changed in the machine...

    Alberto Simões

      Have you done this as the first communication to the browser?

      print "Content-type: text/html; charset=utf-8\n\n";

      IE requires this. Firefox will respect the <meta> tag directions, but IE needs to hear of UTF in the content headers.

      Blessings,

      ~Polyglot~

        You know, that line is what the CGI header function produces when called with -charset => utf-8.

        Alberto Simões

      What do you mean by "that"? Did you need to trace the whole path?