This only forces the client which encoding to use to interpret and display the characters. But the actual problem is that you're already sending ’ (encoded
I have a new drop-shipping affiliate website, and receive an exported copy of the product catalog from the wholesaler. I format and import this into Prestashop 1.4.4. The front end of the website contains combinations of strange characters inside product text: Ã, Ã, ¢, â‚ etc.
In my xojo application, I retrieve the text from MSSQL server, and the apostrophe appears as ’. (In SQL manager the apostrophe appears normally). I later store the text in the above-mentioned field in MySQL, with the results as shown. It looks like your case.
