Re: Re: Catalyst, utf8 in form element type text - Solved

7 msg	Configuration of $c->log with Catalyst::Log:...
8 msg	Invalid session ids being generated
4 msg	Catalyst / dbix-class / mysql / REST job
2 msg	Strange UTF16 warning
1 msg	Wikipedia article improvement?
5 msg	FastCGI: incomplete headers (0 bytes) received ...
5 msg	Basic CRUD Tutorial
2 msg	How to display a single HTML::Widget form field...
7 msg	Let's port Twitter to Perl

Catalyst, utf8 in form element type text
\ Marius Kjeldahl (4 May 2008)
. \ Aristotle Pagaltzis (5 May 2008)
. . \ Marius Kjeldahl (5 May 2008)
. . . \ Bill Moseley (5 May 2008)
. . . . \ Marius Kjeldahl (5 May 2008)
. . . . . \ Bill Moseley (5 May 2008)
. . . . \ Aristotle Pagaltzis (6 May 2008)
. . . . . \ Bill Moseley (6 May 2008)

17 msg	Anybody who fancies some LWP poking ...
54 msg	RFC: Catalyst::Controller::REST::DBIC
1 msg	Kill the book thread please
2 msg	More Catalyst Template Toolkit examples?
6 msg	Fw: high school reunion (no subject)
2 msg	(no subject)
6 msg	Using URIs for my app in another program
4 msg	Tutorial
11 msg	$row->copy causing exit from controller(!)
14 msg	How to print/display some data in an end action

Subject:	Re: Re: Catalyst, utf8 in form element type text - Solved
Group:	Catalyst
From:	Bill Moseley
Date:	6 May 2008

On Tue, May 06, 2008 at 09:04:38AM +0200, Aristotle Pagaltzis wrote:
> * Bill Moseley <moseley> [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 general.

Yes, IE will use the HTTP Content-Type header over accpet-charset in
the <form> tag (and over any <meta> tag as well).

Firefox 2 will use accept-charset (even if its different from the
HTTP charset). So, it's good to have an accept-charset and make sure
it matches the page's Content-Type charset.

At least, that's how I remember it.

> other screwy things. Overall this is an area of much hatefulness.
> For best results, <http://search.cpan.org/perldoc?Encode::HEBCI>
> is the way to go. But most of the time it’s overkill, since once
> you get your pages to be served as UTF-8 properly, you can pretty
> much forget the issue.

That's what I do -- I set the Content-Type, meta http-equiv,
and accept-charset on the form all to utf-8. Any browser that screws
that up likely isn't supported in other ways, too.

--
Bill Moseley
moseley

_______________________________________________
List: Catalyst
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst/
Dev site: http://dev.catalyst.perl.org/