On 8/9/07, Tobias Kremer <[EMAIL PROTECTED]> 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 > ...
IIRC, ENCODING options was added right after I released Template::Provider::Encoding. No idea why it's still undocumented (consult the template-toolkit mailing list :), but yeah, if it's a single encoding you use in your templates, there's no need to use T::P::Encoding. -- Tatsuhiko Miyagawa _______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
