Stefano Cappellini

It's a matter of charset encoding. Their server doesn't specify any charset encoding within the Content-Type header. The browser start searching for the meta tag - that's simply not there,...

I've just set up a small demo: - With content-type charset: [http://tests.codingwh.com/md-page-accent/](http://tests.codingwh.com/md-page-accent/) - Without: [http://tests.codingwh.com/md-page-accent/without](http://tests.codingwh.com/md-page-accent/without) - With BOM: [http://tests.codingwh.com/md-page-accent/bom/](http://tests.codingwh.com/md-page-accent/bom/) It happens, obviously, only if the default charset of the browser...