I would suspect one of your Apache's not setting the character
set to UTF-8, but something less robust or not at all. You'd
have to compare versions of Apache installed as well as all the
configuration files. Check for AddDefaultCharset:
https://httpd.apache.org/docs/current/mod/core.html#adddefaultcharset
--steve
On 7/6/17 at 1:11 AM, pylons-discuss@googlegroups.com ('Mathieu
Dubois' via pylons-discuss) pronounced:
Dear all,
Thanks for the answers. First of all I solved the problem by
adding <meta charset="utf-8">.
But what puzzled me is the difference between the 2 machines
that are fairly similar: same OS version (although not exact
same history), deployment in virtualenv, same code source (the
jinja files are UTF8), same locale, etc. So I was suspecting a
subtle pyramid or python or apache configuration issue...
Mathieu
------------------------
Steve Piercy, Soquel, CA
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/pylons-discuss/r473Ps-10125i-F22E460DAFB945A2A6B4413FF1D4A10D%40Steves-iMac.local.
For more options, visit https://groups.google.com/d/optout.
