I think you need to go into the manager and edit the charset in the site configuration panel to match what you have in the template.
Also...you should put the <base> before the css and javascript links to avoid issues with IE.
-
☆ A M B ☆
- 24,524 Posts
That’s why I recommend putting [(modx_charset)] to replace the actual character set in your template so that it will always match whatever your configuration is set to.
http://www.sottwell.com/how-templates-work.html
One item of especial note in our template is how the site variable tag [(modx_charset)] is used to define the charset in the content-type meta tag. This uses the site configuration setting. When MODx generates the HTTP headers for the page it will use the character set specified in the site configuration. By using this MODx tag in your template you make sure that the HTTP header character set matches the meta tag’s charset. This will, among other things, avoid the character encoding mismatch warning from the W3C validator.