207011 - Bullet characters not displaying correctly

Status: VERIFIED WORKSFORME

(Core :: Internationalization, defect)

Description

[foobarbaz99]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

On the http://www.nytimes.com, the bullet characters display  as "?" characters
on both win2k and linux builds of Mozilla. IE correctly shows bullet characters.
When I save the nytimes.com from IE, and then paste the bullet character (hex
95) into another webpage, Mozilla will show it correctly. When I save the
nytimes homepage from Mozilla and see what is being sent for the bullet
character, it's a weird mash of 3 characters (�, hex ef bf bd), but then when
I paste those 3 characters into a webapge, Mozilla shows those three characters,
not a bullet. I give up.

Anyway, I've been staring at the "?" characters on the nytimes.com homepage for
a long time using Mozilla (on both win2k and linux) and I finally decided to
report it.  Since I couldn't find any other report of this problem, I think
there's a 75% chance that I'm doing something wrong, but for the life of me I
can't figure out what it could be.

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.nytimes.com
2. See the broken bullet characters in the main headlines
3.

Actual Results:  
See a ? instead of the bullet character

Expected Results:  
Show a bullet character

Comment 1

[Hixie (not reading bugmail)]

This is worksforme on win2k 2003050908.

What character set do you have selected when you visit this page? (look under
Edit > Character Coding). The page doesn't specify one, Mozilla should guess
that it is Windows 1252. If it didn't, you may have changed your character
coding settings or something. (I have mine set to Universal autodetect, and it
picked the right encoding. Is our default wrong?)

Comment 2

[foobarbaz99]

Setting the character coding to Windows-1252 worked.

I've never messed around with changing the character coding so I'm not sure
how/why it wasn't set correctly in the first place. Previously, I was using
Mozilla1.3 which didn't have "Universal" as an option - so I'm not sure if/how
that effected Mozilla's ability to auto-detect the correct character coding for
nytimes.com.

If the lastest Mozilla more reliably detects the correct character coding, then
mark this "bug", as fixed or notabug.

Thanks,

Jeff

Comment 3

[Hixie (not reading bugmail)]

I don't think anything changed -- smontagu: any idea? Should this be WORKSFORMEd?

Comment 4

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

Encoding detection -> i18n, although it's really the site's fault in the end.

Comment 5

[Simon Montagu :smontagu]

Since universal autodetection currently identifies the page as Windows-1252 (per
comment 1 and my own testing) this is WORKSFORME as an encoding detection issue. 

Comment 6

[Yuying Long]

Mark as verified per previous comment.