brokaddr - 3:14 pm on Sep 15, 2012 (gmt 0)
You need to include a line in both places that explicitly sets the encoding.
Forgive me for being daft, but how would I do that, exactly?
Also check to make sure it behaves the same locally and online. Sometimes your ftp-or-equivalent turns out to be the culprit. (Voice Of Experience.)
I save the file as UTF-8, in my client (WinSCP), the "Server Environment" is set to UTF-8 encoding for filenames = Auto
Anything else I'd need to check?
I would convert everything to UTF-8, this is really the simplest solution, but you need to do the conversion carefully.
Change the database tables from latin1_swedish_ci to UTF-8, correct? Would utf8_unicode_ci be the best option? I primarily use A-Z alphabet, but deal with a lot of foreign accents and characters from time to time.
Your problem is going to get worse as you might be contaminating your database with having a mix of iso-latin and utf-8 in it, something that you only can clean up if you know which fields have been contaminated.
Does the entire database need to be changed, or just the fields that are acting up? I don't have a lot of experience with this, I didn't even realize there was a difference in database storage until this happened. I've actually had it set to latin1_swedish_ci since 2005 or so, never had any issues until recently.