Default theme misses UTF-8 charset declaration

[Odin Hørthe Omdal]

Some browsers screw up without that.

I use the HTML5 meta line here. It works in all browsers I've
tested.

[Odin Hørthe Omdal]

charset_utf8.patch

[joar]

Since we set up using paste; Would it not be possible to globally
set Content-type: ...; charset=UTF-8?

It would in my opinion be the more intuitive way of telling the
browser about our charset since it would also tell the browser
about CSS files, JavaScript files and other plain files.

[Odin Hørthe Omdal]

Yes, although one doesn't exclude the other.

Thing is; if you ever save this, and **not** get it from the
server, you will miss the Content-Type header. Also, some bad
caching might forget it as well.

If we can do both, I think we should.

[Odin Hørthe Omdal]

It already does set ``Content-Type: text/html; charset=UTF-8``.

I've been saving the files and comparing/looking at them to find an
unclosed div-bug, and that's when I got UTF-8 errors.

[Christopher Allan Webber]

Ah okay, that clarification helps.

[Christopher Allan Webber]

Merged! Thanks!

[Christopher Allan Webber]

Again, forgot to close ;)

[Will Kahn-Greene]

The original url for this bug was ​http://bugs.foocorp.net/issues/450 .