On 1/25/06, Bill Moseley <[EMAIL PROTECTED]> wrote: > > This is not a direct answer to your question, but my > > Template::Provider::Encoding module will help your situation. When you > > use it with Stash::ForceUTF8, you don't have to care about UTF-8 > > auto-upgrading problem. > > Thanks. I like this idea as it forces the encoding to be defined in > the templates. Might be nice to specify something other than utf8 as > the default encoding if not encoding is specified in the template, > though.
There's a very similar module on CPAN to do that: http://search.cpan.org/dist/Template-Provider-Encode/ > Since Template::Provider::Encoding calls Template::Provider::_load > should it not check for the utf8 flag before trying to decode it? > If a template had a BOM then returned data would already be decoded. Good point. This should be fixed in a next release. Personally I never use BOM in the templates. -- Tatsuhiko Miyagawa _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
