UTF-8 all the things.

* Use a meta tag in the HTML to set a character set of UTF-8.
* Ensure your files are encoded with UTF-8.
* Avoid a byte order mark (BOM) in files as that may override other settings. * Ensure web servers serve text/html as UTF-8. A simple text file containing only HTML boilerplate with "©" or the classic "räksmörgås" should be sufficient to test.
* If you hit a database, ensure the connection uses UTF-8.

There's may be a couple of other places to check, too, but you get the idea.

--steve


On 7/4/17 at 2:05 PM, [email protected] ('Mathieu Dubois' via pylons-discuss) pronounced:

Dear all,

I'm far from being an expert on that so pardon my ignorance.

We have 2 servers (say prod and dev) running the same code (in some virtualenv). We recently upgraded to Ubuntu 16 (dev was updated from Ubuntu 14.04 and prod from Ubuntu 12.04 to Ubuntu 14.04 and then to Ubuntu 16.04). We use the version of pyramid provided by Ubuntu but we installed. The virutalenv were recreated from scratch for Ubuntu 16.04 and the same version of pyramid_jinja2 was installed there. The code is run with pserve (started by circus) and we use Apache as a reverse proxy to redirect to the internet (AFAIU the configuration is the same).

Our login page contains a '©'. This is served correctly from dev (the HTML code contains '©') but not from prod (the HTML code contains '©'). So somewhere there is something different but I have no idea where to look. it's not blocking but I would like to be sure that we don't miss something. Any advice ?

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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/r473Ps-10125i-D62620B42C544496A2C38276DF3CB76F%40Steves-iMac.local.
For more options, visit https://groups.google.com/d/optout.

Reply via email to