I'm part of a team starting to implement Jinja2 templates, and seeing our first UnicodeDecodeErrors from data being in strings with non- ascii characters passed in the context to the templates.
Most of the objects of the application are not unicode, but strings. Data retrieved from the db, and so on. I don't think we're going to change that to be slinging unicode around before using templates. Is it a common approach to use a common function to convert any string variables to unicode when building the context dict being sent to the template? Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pocoo-libs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pocoo-libs?hl=en -~----------~----~----~----~------~----~------~--~---
