Bill, 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. http://search.cpan.org/~miyagawa/Template-Provider-Encoding-0.03/
On 1/25/06, Bill Moseley <[EMAIL PROTECTED]> wrote: > Just trying to get my head wrapped around the utf8 issues. > > I've got utf8 content in Postgresql and generating utf8 output. > That's all working fine. > > I have other cases where content is pulled from disk. I understand > that if the content has a BOM then it will be correctly read by TT. > I'm just passing an open file handle to process(), so I'm not reading > in the content before passing off to TT. > > I'm seeing some content that's cp1252, though. So, I'm wondering: how > I can still pass in a file handle, but have the content decoded > correctly? > > -- > Bill "utf8-challenged" Moseley > [EMAIL PROTECTED] > > > _______________________________________________ > templates mailing list > [email protected] > http://lists.template-toolkit.org/mailman/listinfo/templates > -- Tatsuhiko Miyagawa _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
