Closed Bug 93586 Opened 24 years ago Closed 23 years ago

Character coding can't be applied to the ALL frame of the homepage.

Categories

(Core :: Internationalization, defect)

defect
Not set
minor

Tracking

()

CLOSED FIXED
Future

People

(Reporter: l_chicken, Assigned: shanjian)

References

()

Details

(Keywords: intl)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.3) Gecko/20010801 BuildID: 2001080110 The chararcter coding of this homepage should be set to the Traditional Chinese(HK-SCS) in order to display it properly. However, the character coding setting can't be applied to all the frame of the homepage. As a result, I can't read the words in the windows with frame. Moreover, when I click of a link on a webpage that I had already set the Traditional Chinese(HK-SCS) coding, this setting will not inherit to the next page? Can't is be inherited? I don't want to set it again and again....thx Reproducible: Always Steps to Reproduce: 1.load the page 2.set Character coding to Traditional Chinese(HK-SCS) Actual Results: no font change to the right bottom frame Expected Results: The font of the frame should be changed to Traditional Chinese(HK-SCS) (Compare this with opening that frame in a single window with character coding set.) Open that frame in a new window with character coding set will show the correct screen.
->i18n
Assignee: asa → yokoyama
Component: Browser-General → Internationalization
QA Contact: doronr → andreasb
andreas: please confirm. === cc'ing shanjian.
I don't really understand what means by "Confirm". I can say that the my problem DO exsist. Should I provide any other information?
Switching qa contact to ylong. Yuying, can you take a look?
Keywords: intl
QA Contact: andreasb → ylong
l_chicken@yahoo.com: "Confirm" simply means to get our QA personal to look at this bug and change the bug status from UNCONFIRMED TO NEW. Sorry for confusion.
I checked this here: 1. Frames encoding are Big5. 2. The unreadable characters are those Japanese characters that encoding in this Big5 charset page even you manually select Big5 or Big5-HKSCS. I can always view the Chinese characters correctly in any case. 3. You have to open the frame pages by open a new window, and set charset to Big5-HKSCS every time in order to view those Japanese characters correctly. I'm not quite sure how we should handle Japanese characters that in Big5 charset page like such case, but I'm going to confirm this bug. Please change the status if there is a non-issue. It happens on All platforms, change OS to ALL.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows ME → All
Hardware: PC → All
Yuying's observation is correct. The subframe html page has meta charset specified incorrectly. Instead of "Big5-HKSCS", "big5" is used. Since child frame can only inherit one charset (parent charset) from its parent, so we always trust meta charset before parent charset.
shanjian: so is this a bug or is working as designed?
Status: NEW → ASSIGNED
This is working as designed, at least for know. Subframe or link will not inherit charset of its parent/previous page if it has meta charset specified. Reporter, you might want to notify the webmaster to correct the problem. To be specific, when a page has following line: <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=big5"> It should be replaced by <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=big5-hkscs">
give this bug to shanjian
Assignee: yokoyama → shanjian
Status: ASSIGNED → NEW
We planned to do something to children frame charset handling. This bug is most like a dup of some other bug. Leave it for future.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
This problem should have been fixed. The mentioned website does not exist any more, so I can no longer verify this.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Mark as verified, it's more likely the web page problem.
Status: RESOLVED → VERIFIED
It's ok now. Very nice.
Status: VERIFIED → CLOSED
You need to log in before you can comment on or make changes to this bug.