From trvalentine at gmail.com Tue Mar 21 22:53:03 2017 From: trvalentine at gmail.com (T. R. Valentine) Date: Tue, 21 Mar 2017 17:53:03 -0500 Subject: [thelist] character encoding nightmare In-Reply-To: <562662A8-3948-40E8-8D36-572798C199BD@mcn.org> References: <8242061D-40AE-49C5-A2DE-809DD09DF1FE@mcn.org> <6DE90835-C53C-4B57-9495-F7C51244BA01@mcn.org> <562662A8-3948-40E8-8D36-572798C199BD@mcn.org> Message-ID: On 16 March 2017 at 20:48, Garth Hagerman wrote: >>If you can provide an example of a raw string, and the different results of your encoding and conversions in addition to what the final text looks like when pulled back out of the DB, we might be able to recognize the hiccup via the changes being made. > The results are easy to see and compare: > Site 1 - > Site 2 - My 2¢ — although both sites html show "charset=iso-8859-1", Site 1 is being presented to my web browser as iso-885901, but Site 2 is being presented as Unicode. If I manually change the display to iso-8859-1 on Site 2, the ugly characters disappear. Methinks the server for Site 2 is serving up pages in Unicode regardless of what the markup contains. -- T. R. Valentine A rich heart may be under a poor coat.