Opened 13 years ago

Last modified 13 years ago

#160 closed defect (FIXED)

Default theme misses UTF-8 charset declaration

Reported by: Odin Hørthe Omdal Owned by: Odin Hørthe Omdal
Priority: minor Milestone: 0.0.4
Component: programming Keywords:
Cc: Parent Tickets:


Some browsers screw up without that.

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

Attachments (1)

charset_utf8.patch (491 bytes ) - added by Odin Hørthe Omdal 13 years ago.

Download all attachments as: .zip

Change History (8)

by Odin Hørthe Omdal, 13 years ago

Attachment: charset_utf8.patch added


comment:1 by joar, 13 years ago

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.

comment:2 by Odin Hørthe Omdal, 13 years ago

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.

comment:3 by Odin Hørthe Omdal, 13 years ago

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.

comment:4 by Christopher Allan Webber, 13 years ago

Ah okay, that clarification helps.

comment:5 by Christopher Allan Webber, 13 years ago

Component: Programming
Milestone: 0.0.4
Merged! Thanks!

comment:6 by Christopher Allan Webber, 13 years ago

Owner: set to Odin Hørthe Omdal
Status: NewClosed
Again, forgot to close ;)

comment:7 by Will Kahn-Greene, 12 years ago

The original url for this bug was .

Note: See TracTickets for help on using tickets.