Solved it ... The major pieces that we all knew about were:
- decoding the database results via mysql_enable_utf8 - decoding the templates using ENCODING => 'utf8' - encoding the template output, using $Template::BINMODE = ':utf8' (easier than arguments to each and every process call) The two extra gotchas (or gotme anyway) that made for such strange symptoms were: - one module used by my main program was making its own connection to the database (for historical reasons). Apparently that changes the mysql_enable_utf8 setting on my main connection. I'm sure DBIC has a good reason for that which I ought to know, but it sure wasn't something I was expecting. Praise be to the debugger for finding that. - and of course changing encoding options for templates doesn't actually have any effect unless you actually subsequently edit the template, thanks to the wonders of TT's compilation cache. It was only because I updated the copyright message from 2013 to 2014 that I happened to fix that problem; just lucky it happened at this time of year, I guess. Cheers, and thanks again, Dave _______________________________________________ templates mailing list templates@template-toolkit.org http://mail.template-toolkit.org/mailman/listinfo/templates
