Closed Bug 285242 Opened 20 years ago Closed 20 years ago

UTF-8 in title bar not displayed correctly

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: csh, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

UTF-8 in title bar not displayed correctly, and, in fact, incorrect characters
spill into the body.  This page DOES display correctly when it is a local file.

Reproducible: Always

Steps to Reproduce:
1.go to www.prototypos.com
Actual Results:  
displays "Ï€ Ï Î¿ Ï„ ÏŒ Ï„ Ï… Ï€ ο Ï‚" in the title bar and "" on the page 

Expected Results:  
should display "π ρ ο τ ό τ υ π ο ς" in the title bar
It seems like the character encoding automatically switches to UTF-8 for the
local file but not for the non-local file?  Note that the automatic switching to
UTF-8 works in IE.
Your server is sending:

Content-Type: text/html; charset=ISO-8859-1
I thought that if the line:

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

is included in the <head/> element, the browser would be forced to honor UTF-8.
See:
http://www.w3.org/TR/html401/charset.html#h-5.2.2

"To sum up, conforming user agents must observe the following priorities when
determining a document's character encoding (from highest priority to lowest):

   1. An HTTP "charset" parameter in a "Content-Type" field.
   2. A META declaration with "http-equiv" set to "Content-Type" and a value set
for "charset".
   3. The charset attribute set on an element that designates an external resource."

The HTTP Content-Type header is a higher priority than the meta http-equiv
element. Since your page has both, the header "wins".
Marking bug as INVALID (forgot to do that first time around).
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.