On Tue, May 06, 2008 at 09:04:38AM +0200, Aristotle Pagaltzis wrote:
* Bill Moseley [EMAIL PROTECTED] [2008-05-05 21:40]:
form tags should have accept-charset
Browsers tend to ignore that and send the form data in the same
encoding as the page that the form was on.
Browsers is a bit
Problem solved. In my View class, like:
package MyApp::View::TT;
use strict; use warnings;
use base 'Catalyst::View::TT';
replace the last line with:
use base 'Catalyst::View::TT::ForceUTF8';
and everything works fine. I guess there was some confusion between
Template Toolkit and non-utf8
On Mon, May 05, 2008 at 04:12:53PM +0200, Marius Kjeldahl wrote:
Problem solved. In my View class, like:
package MyApp::View::TT;
use strict; use warnings;
use base 'Catalyst::View::TT';
replace the last line with:
use base 'Catalyst::View::TT::ForceUTF8';
That seems like the wrong
Bill Moseley wrote:
use base 'Catalyst::View::TT::ForceUTF8';
That seems like the wrong approach.
Data should be decoded on input from the outside and encoded on
output. I'm not sure when it would be advisable to force utf8 flag
on items in the stash, but I have not looked at that module in
On Mon, May 05, 2008 at 09:22:19PM +0200, Marius Kjeldahl wrote:
form tags should have accept-charset
I tried this but couldn't get it working correctly, which may be
entirely my fault of course.
What does couldn't get it working mean? You couldn't get an
accept-charset on your form tags?
