Closed
Bug 92632
Opened 24 years ago
Closed 24 years ago
Japanese page source appears garbage when using a page that in Composer
Categories
(Core :: Internationalization, defect)
Core
Internationalization
Tracking
()
VERIFIED
INVALID
People
(Reporter: amyy, Assigned: nhottanscp)
Details
(Keywords: intl, regression)
Build: Last respin N6.1 RTM build on all platforms:
Win32 07-27-00 0.9.2 on WinME-Ja
Mac 07-26-21 0.9.2 on Mac9.0-Ja
Linux 07-26-23 0.9.2 on ReadHat6.2-Ja
Not reproduce on: 07-25 Branch on all platforms.
Japanese page source appears garbage when the page was created in Composer.
This is happenes when setting charset to Shift-JIS and EUC-JP, but not
ISO-2022-JP though.
This most likely regression by check in of bug 90288 because I can not reproduce
it on 07-25 branch build.
Steps to reproduce:
1. Launch browser and open Composer.
2. Create a page that contains Japanese characters.
3. File | Save As Charset, save the page as Japanese charset page:
a. Shift-JIS.
b. EUC-JP.
c. ISO-8859-1
4. Browse the page, and check View | Page Source.
Result:
Japanese characters are display as garbage on step 3 case a nad b, but not case c.
Note: I haven't check this with other non-Ascii charset(e.g. Chinese or Korean
...etc) yet at this point.
Reporter | ||
Updated•24 years ago
|
Keywords: intl,
regression
Summary: Japanese page source appears garbage when using a page that in Composer → Japanese page source appears garbage when using a page that in Composer
Assignee | ||
Comment 1•24 years ago
|
||
>4. Browse the page, and check View | Page Source.
Was this done by "Brows" button in Composer, or File Open in Browser?
Reporter | ||
Comment 2•24 years ago
|
||
> Was this done by "Brows" button in Composer, or File Open in Browser?
---Both
Please wait:
I found the auto-detect set to either Korean or Chinese when I saw this problem.
Updated•24 years ago
|
QA Contact: andreasb → ylong
Reporter | ||
Comment 3•24 years ago
|
||
OK, It was seems before I did this I turn on Auto-detect Korean and Chinese with
today's build, then cause this happened.
If I turn off auto-detect or change to auto-detect ALL, then won't see the proble.
I'm marking it as invalid.
Status: NEW → RESOLVED
Closed: 24 years ago
QA Contact: ylong → andreasb
Resolution: --- → FIXED
Comment 4•24 years ago
|
||
Marking as invalid accordingly to Yuyings comment.
Status: RESOLVED → REOPENED
QA Contact: andreasb → ylong
Resolution: FIXED → ---
Comment 5•24 years ago
|
||
.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•