Charset issue: SeaMonkey and Minefield display differently word "Apple’s"

NEW
Unassigned

Status

()

11 years ago
11 years ago

People

(Reporter: BijuMailList, Unassigned)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(2 attachments)

(Reporter)

Description

11 years ago
Created attachment 270990 [details]
fontissue.png

Font issue: SeaMonkey and Minefield display differently 
word "Apple’s" in paragraph starting with
"This is because Apple’s iPhone battery replacement..."
at http://www.business-standard.com/common/storypage.php?autono=290126&leftnm=8&subLeft=0&chkFlg=

see attached screenshot fontissue.png
and test case attachment app.html

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/2007061701 SeaMonkey/2.0a1pre

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7pre) Gecko/2007070404 Minefield/3.0a7pre
(Reporter)

Comment 1

11 years ago
Created attachment 270991 [details]
app.html

test case

Comment 2

11 years ago
looks like different character encodings.  don't think this belongs in gfx.
The page at http://www.business-standard.com/ doesn't specify a character encoding, so this is probably caused by different settings for the default encoding (intl.charset.default). The test case in attachment 270991 [details] doesn't show the same behaviour, because it is served as UTF-8 by bugzilla.

In the screen shot, the encoding used seems to be IBM-850.

Updated

11 years ago
Component: GFX: Thebes → General
QA Contact: thebes → general
Summary: Font issue: SeaMonkey and Minefield display differently word "Apple’s" → Charset issue: SeaMonkey and Minefield display differently word "Apple’s"
(Reporter)

Comment 4

11 years ago
(In reply to comment #3)
> encoding, so this is probably caused by different settings for the default
> encoding (intl.charset.default).

Tested and found that is the reason...

> The page at http://www.business-standard.com/ doesn't specify a character

that is a problem... 
In that case Firefox/SeaMonkey should give user some indication on status bar (or somewhere) that it defaulted to an encoding.

My default firefox encoding may have changed because, I may have adjusted it to make Malayalam pages better, with out realizing it may affect other pages.
You need to log in before you can comment on or make changes to this bug.