Closed Bug 144090 Opened 23 years ago Closed 23 years ago

display content in gb18030 charset if CJK charset detection is on

Categories

(Core :: Internationalization, defect)

Product:
Core
Component:
Internationalization
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED DUPLICATE of bug 132006

People

(Reporter: cslsy96, Assigned: tetsuroy)

References

(
URL
)

Details

(Keywords: intl)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; zh-TW; rv:1.0rc2) Gecko/20020510 BuildID: 2002051006 When loading a page not in cache, it displays content in gb18030 charset if CJK charset detection is on, even the pages are specified in utf-8. When re-visiting the page, it shows the content correctly. Reproducible: Always Steps to Reproduce: 1.open http://www.geocities.com/omnibussun/music/beyond_chung_yau_oi.html (if it is in cache, clear all caches) 2. 3. Actual Results: show the content in GB18030 Expected Results: detect the content charset is UTF-8
-> i18n
Assignee: attinasi → yokoyama
Component: Layout → Internationalization
QA Contact: petersen → ruixu
I'm using a bit old code (20020426). It uses UTF-8 even auto-detect is on. Need to verify. cc shanjian. He may know something might have changed since then.
I could not see any problem with latest trunk build and branch build either.
reporter: I'm going to mark as WFM. Please reopen if you disagree and provide us with a test case or steps. Thanks
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Keywords: intl
QA Contact: ruixu → ylong
Actually on 05-10 PR1 build / WinXP-JA and 05-12 PR1 build / Win2k-SC: When auto-detect Chinese or SimpChinese, the charset menu is marked as gb18030, but display fine. If you reload, then will be marked as UTF-8. If manually select gb18030, it will diplay garbled. So, looks like auto-detect works fine but mark memu item wrong. Re-open.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Confirm.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Can not reproduce this on latest TRUNK build even can see it on branch build, so seems like another dup of bug 132006.
*** This bug has been marked as a duplicate of 132006 ***
Status: NEW → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
Mark as verified cause can not reproduce in on latest trunk build. Please re-open if you can still see it on latest build after bug 132006 checked into branch.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.