Closed Bug 63460 Opened 25 years ago Closed 25 years ago

When open an exist file contains other than ISO-88591 charset characters, those characters doesn't show correctly.

Categories

(Core :: Internationalization, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: amyy, Assigned: nhottanscp)

Details

(Keywords: intl, regression)

When open an exist file(not the first create time) contains other than ISO-88591 charset characters, those characters doesn't show correctly. Tested 12-19 Mtrunk build with WinME, Mac and Linux. Steps to reproduce: 1. Launch the Netscape 6 > Composer. 2. View > Character Coding > Choose some charset like shift-jis or EUC-jp. 3. Type some Japanese words, check the HTML source, make sure the charset in meta-tag is match to the setting in step 2, and the Japanese characters are correct then save the file. 4. Close the Composer, and re-open it, then open the file that was created above. Result: You will see the Japanese characters are wrong, and if you go to HTML source page, charset in meta-tag still shows correctly, however the Japanese characters are wrong. And if you load to browser, the characters doesn't shows correct too, you have to change the character coding to like s-jis in order to see them. Note: You won't see the problem while you create them, it happens after you save the file and re-open it.
Change QA contact and add the keywords.
Keywords: intl, nsbeta1
QA Contact: teruko → ylong
Summary: When open an exist file contains other than ISO-88591 charset characters, those characters doesn't show correctly. → When open an exist file contains other than ISO-88591 charset characters, those characters doesn't show correctly.
Keywords: regression
Actually, it happens when you type Japanese words at the very beginning of page.
ylong, please test this again with the latest trunk build, I think this is related to the META charset bug which has been fixed.
Yes, it has been fixed in latest(01-02) Mtrunk build.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Mark it as verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.