Closed Bug 66130 Opened 24 years ago Closed 24 years ago

Can't control the character coding within frameset

Categories

(Core :: Internationalization, defect, P4)

Product:
Core
Component:
Internationalization
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 43529

People

(Reporter: chip, Assigned: shanjian)

References

(
URL
)

Details

(Keywords: intl)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010119 BuildID: 2001011904 Currently the only way to set the coding of a page is through view -> character coding. However, such setting is lost when the page is composed within frames. Frames inside without meta tag saying 'charset=big5' will not set to use big-5 charset, even i set it in the view->character coding->traditional chinese. The workaround is to open that frame to set the properly language is to right click the frame -> open frame in a new window, then set to the charset i wish. Reproducible: Always Steps to Reproduce: clear all caches -> close all existing browser windows -> start mozilla browser to http://www.citibank.com.hk -> click (chinese version) (???) on the right top -> click (investment, or ??) on top navigator bar -> set language coding to traditional chinese (big 5) Actual Results: the biggest frame filled with garabe characters Expected Results: stuffs in the biggest frame should be converted to readable traditional chinese characters, if appropriate language support has been installed. my computer config: windows 2000 sp 1, with traditional chinese language support (added during installation, however, can be added through control panel -> regional setting)
Reassign to cata, not a dup but related to bug 63054.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reassign to cata cc to bstell, not a dup but related to bug 63054.
Assignee: nhotta → cata
this bug seems to be requesting: charset override force the charset into all frames in the page If so, should we change the summary to refelect this intent?
move all cata's bug to ftang
Assignee: cata → ftang
P4 all
Status: NEW → ASSIGNED
OS: Windows 2000 → All
Priority: -- → P4
Hardware: PC → All
shanjian- can you take a look at this?
Assignee: ftang → shanjian
Status: ASSIGNED → NEW
Looks like a duplicate of bug 43529 to me
Changed QA contact to ylong@netscape.com.
QA Contact: teruko → ylong
*** Bug 69661 has been marked as a duplicate of this bug. ***
patch proposed in 43529 should be able to resolve this problem.
Status: NEW → ASSIGNED
Depends on: 43529
Is this the logic here?: By moving the "inherit charset from parent" to higher priority than "use charset from cache" then changing the parent's charset and reloading will override the (old/wrong) charset. This seems reasonable to me. Can anyone think of other (undesireable) consequences of this change? This of course is not the same as being able to individually control a frame's charset. However, in general I would expect a frame set to use related encodings.
Yes, that's the logic. We do not have a way to set a frame's charset directly. In future when it is implemented, it will just use a higher priority source, ie "user forced charset".
*** Bug 74152 has been marked as a duplicate of this bug. ***
This sounds like a duplicate. Please mark it as so . . . so we can reduce triage and bug lists.
Keywords: intl
Most likely this is duplicate of 43529. But please verify this after 43529 has been checked in. *** This bug has been marked as a duplicate of 43529 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
With this page: http://www.citibank.com.hk/cgi-bin/bv.cgi/chinese/index.jsp No matter how I change the charset(e.g. Shift-JIS or EUC-KR....) it just display Chinese OK. I don't know if it the same problem with bug 72299 though.
for those inside the netscape firewall (sorry to those outside): try using http://warp.mcom.com/employees/erik/view/ to see the http headers
Verified as dup.
Status: RESOLVED → VERIFIED
qa=marina
QA Contact: ylong → marina
You need to log in before you can comment on or make changes to this bug.