319343 - bugzilla HTML pages should specify charset

Status: VERIFIED DUPLICATE of bug 126266

(Bugzilla :: Bugzilla-General, defect)

Description

[Eyal Rozenberg]

all Bugzilla HTML pages should have a

<meta http-equiv="Content-Type" content="text/html;charset=whatever">

in their header. They currently do not.

Comment 1

[timeless]

possibly bug 304550. this is already reported and bmo isn't changing until its internal data is fixed. standard bugzilla *can* specify utf8 if it wants to.

Comment 2

[Eyal Rozenberg]

Regardless of whether the DB charset is set, the pages should have a charset specified; if nothing else, IMHO it should be some default value (e.g. iso-8859-1).

Comment 3

[Marc Schumann [:Wurblzap]]

We don't need to do this if we specify the character set encoding in the HTTP header, right? That's bug 126266, so I'd say this bug is a duplicate of bug 126266.

If this is about having the character set encoding handy in saved files, then I'd rather vote for a <?xml version="1.0" encoding="UTF-8"?> line.

Comment 4

[Eyal Rozenberg]

*** This bug has been marked as a duplicate of 126266 ***

Comment 5

[Marc Schumann [:Wurblzap]]

Answering your question of bug 126266, comment 273: adding such a tag is not broken as far as I know. You can add it to your local installation easily, if you want, by modifying template/en/default/global/header.html.tmpl. If you want to provide for correct HTTP headers, you may want to apply the modification of http://www.bugzilla.org/docs/2.20/html/security-bugzilla.html to your installation.

Installations with the utf8 parameter switched on don't need this because the HTTP header specifies the character set encoding.
The utf8 parameter appeared first in version 2.21.1.

All other installations are currently considered to be using mixed character set encodings so that both such a meta tag or a HTTP header giving a character set encoding may be wrong. The reason is, ironically, because Bugzilla didn't specify a character set encoding all the time -- incoming data may be encoded in many different encodings. (That's the case for https://bugzilla.mozilla.org/, for example.) Until bug 280633 is fixed, the character set encoding of a given Bugzilla page is indeterminate.