On Wed, Feb 01, 2006 at 12:00:15PM +0000, Andy Wardley wrote: > Tom Insam wrote: > > will encode the output to utf-8 before writing. Andy - as regards your > > reply, I think it would be a bad idea to assume the same input and > > output template character sets. But that's just me. > > Having looked it over, I agree. > > It's a more complex issue than I first thought. I've changed ENCODING > to only specify the default encoding for input templates. It doesn't > have any effect on the output encoding - you still have to do that > via the fourth process() argument.
I first started with "DEFAULT_ENCODING" and then changed to "TEMPLATE_ENCODING", but, it's really "DEFAULT_TEMPLATE_ENCODING" because it's after the BOM check. But, I figured that big option name would force too many people to have to move all their "=>" over in their nice, neat, lined-up config option lists. -- Bill Moseley [EMAIL PROTECTED] _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
