diff options
| author | xmo-odoo <xmo-odoo@users.noreply.github.com> | 2016-03-15 11:25:16 +0100 |
|---|---|---|
| committer | xmo-odoo <xmo-odoo@users.noreply.github.com> | 2016-03-15 11:25:16 +0100 |
| commit | c824e50b3f2e752e324a3ec56224d8c464950287 (patch) | |
| tree | 051b1df1d0b520f386db3052bd9945c34d09c905 /addons/web/static/src/js/framework/pyeval.js | |
| parent | d377ffd5bf290d1e61e9bf18bafac87ac441e104 (diff) | |
[FIX] scaffold: correctly decode utf8 templates
As its documentation notes[0], Jinja2 only processes unicode template
data (or pure ASCII, which will implicitly decode to unicode).
The scaffolding system would read raw scaffolding data in memory (both
templates and passthrough non-templates), but fail to decode templates
before handing them to Jinja, blowing rendering up if templates
contained non-ascii.
Fix #11331 by always decoding templates from UTF8 before handing them
to jinja. This is backwards-compatible, ascii templates work as they
used to, non-ascii UTF8 templates now work correctly, non-ascii
non-UTF8 templates what are you doing?
[0] http://jinja.pocoo.org/docs/dev/api/#unicode
Diffstat (limited to 'addons/web/static/src/js/framework/pyeval.js')
0 files changed, 0 insertions, 0 deletions
