Opened 12 years ago
Last modified 12 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: |
Description
Some browsers screw up without that. I use the HTML5 meta line here. It works in all browsers I've tested.
Subtickets
Attachments (1)
Change History (8)
Changed 12 years ago by
Attachment: | charset_utf8.patch added |
---|
comment:1 Changed 12 years ago by
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 Changed 12 years ago by
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 Changed 12 years ago by
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:6 Changed 12 years ago by
Owner: | set to Odin Hørthe Omdal |
---|---|
Status: | New → Closed |
Again, forgot to close ;)
comment:7 Changed 11 years ago by
The original url for this bug was http://bugs.foocorp.net/issues/450 .
Note: See
TracTickets for help on using
tickets.
charset_utf8.patch