> The problem is that UTF-X may or may not be well-formed UTF-8 , it could
> also be UTF-EBCDIC, but you have to understand that you are trying to output > Perl's internal encoding and *not* UTF-8. > Current behavior is desirable, if you wish to change this you need to convince > p5p as it's beyond the scope for an extension module. I understand why this is desirable, I am just trying to understand how to fix my application that previously worked, even if it only worked accidentally. I don't think there's any change available to me at the application level that will solve this. My application doesn't use FCGI directly. It creates a CGI::Fast object and passes that to HTML::Mason::CGIHandler::handle_cgi_object. As far as I can tell, neither CGI::Fast nor Mason has any special handling for Unicode. Mason just passes strings to the print method of the STDOUT stream. Most Mason applications are deployed using mod_perl. I am not using mod_perl, but I assume that those applications are current working with Unicode. What is the change required to enable Mason to work with FastCGI with Unicode strings? Do I need to re-implement or create a subclass of CGI::Fast that doesn't use FCGI directly but uses a wrapper object that does the Perl string to raw bytes conversion itself? ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
