[Catalyst] Catalyst Unicode woes ...

[Matt S Trout]

On Thu, Aug 09, 2007 at 04:42:53PM +0200, Tobias Kremer wrote:
> > View::TT
> >     ENCODING: UTF-8
> >
> > Template provider will see you are running a modern Perl (UNICODE flag
> > in provider) and then look for a Byte Order Mark.  If not found it
> > will then decode your content based on the ENCODING setting.
> >
> > No, you don't need Template::Provider::Encoding if you only have one
> > encoding in your templates.
> >
> > Yes you need Unicode (or the older Unicode::Encoding) plugin so that
> > input params are decoded and output is encoded back to utf8.
> 
> Yes, it all starts to make sense :) Thanks for all the great clarifications.
> MyApp is working fine now with C::P::Unicode and the ENCODING setting. By the
> way, does anybody know why the ENCODING option is undocumented? IMHO, it really
> should be mentioned in the Catalyst::Manual alongside some best-practice for
> Unicode. Use C::P::Unicode and ENCODING: UTF-8 should be enough for most people
> ...

Because (1) we don't control the TT docs, (2) you haven't written the doc
patch for the Catalyst docs yet. I agree that you should patch the main manual
as well as View::TT docs though :)

-- 
      Matt S Trout       Need help with your Catalyst or DBIx::Class project?
   Technical Director    Want a managed development or deployment platform?
 Shadowcat Systems Ltd.  Contact mst (at) shadowcatsystems.co.uk for a quote
http://chainsawblues.vox.com/                    http://www.shadowcat.co.uk/