> The old template was set to a charset of "ISO-8859-1" while the new
> template is set to a charset of "UTF-8". The server is still reading
> the encoding as: "ISO-8859-1" even though the pages have been saved
> using UTF-8.
Saving as UTF-8 doesn't mean browsers can guess that you did*. You
should always declare explicitly--ideally in the Content-Type
header--the encoding of the file.
Browsers do try to guess, but it's frequently an error-prone process.
Here's what most browsers currently do:
*If you include the UTF-8 BOM browsers can guess, but BOMs can cause
problems in CGI scripts, notably PHP.