石庭豐 (Seak, Teng-Fong) Reporter
	Description • 22 years ago

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20020930
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20020930

I can see that Bugzilla doesn't specify encoding for its pages:
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
Please do so.

Actually, if Bugzilla database could handle Unicode, please use UTF-8.

Reproducible: Always

Steps to Reproduce:

	Tobias Burnus
	Comment 1 • 22 years ago

I believe the first is a duplicate of bug 126266. Reopen if you disagree.

Note that mySQL uses by default he ISO-8859-1 (Latin 1) encoding, but I think it
also supports UTF-8.

The additional problem with UTF-8 is that many browsers only support ISO-8859-1
so one probably needed some convertation routine [ISO-8891-1]=>[UTF-8] for this
purpose.

Note further that <META HTTP-EQUIV="Content-Type"> is bad since it causes a
second rendering, sendingt the Content-Type in the real HTML header is better.
Sending email properly is even more difficult. One usually uses two methodes
depending whether UTF-8 or e.g. ISO-8859-1 is used. (I don't have the bug number
for the email support at hand.)

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

	石庭豐 (Seak, Teng-Fong) Reporter
	Comment 2 • 22 years ago

Yeah, this is a dup of that bug.  That bug's summary (Allow administrator to set
charset .....) is so difficult to guess, that's why I opened a new bug.

Replying your second part of comment about HTTP header:
normally a browser would send its agent string to the server.  So, IMO, if the
browser is identified as Mozilla, then there's no problem sending the
content-type in both HTTP header AND HTML header.  If the browser is N4, then
only send HTTP header.  Isn't this a better solution?