Closed
Bug 92856
Opened 24 years ago
Closed 24 years ago
With auto-detector turned on CJK, Netcenter France page is marked as window-1252 page
Categories
(Core :: Internationalization, defect)
Tracking
()
People
(Reporter: ji, Assigned: shanjian)
References
()
Details
(Keywords: intl, regression)
Attachments
(1 file)
26.77 KB,
text/html
|
Details |
Build: 07/27 branch build (win32), 07/26 branch build (linux, mac)
With the latest branch build, when the auto-detector is turned on any
double-byte languages, like Japanese, Chinese or Korean, Netcenter France page
is not recognized as ISO-8859-1 page, instead windows-1252 is marked on the
charset menu.
Steps to reproduce
1. Launch browser with a new profile or clear cache wiht a old profile.
2. Turn on auto-detector on Japanese/Chinese/Korean
3. Go to http://home.netscape.com/fr
4. Select View | Character Coding, you'll see Western (Windows-1252) has dot
marked on the left.
5. View page source on this page, the charset set meta tag is set to iso-8859-1.
So far above URL is the only page that has this problem, I don't see this on
Netcenter Germany page.
It doesn't happen on 07/24, 07/25 branch build.
It seems a regression.
Summary: With auto-detector turned on CJK, Netcenter France page is marked as window-1252 page → With auto-detector turned on CJK, Netcenter France page is marked as window-1252 page
Please note that the fix for bug 90288 has been checked-in on 07/26 branch build.
Keywords: intl,
regression
Comment 3•24 years ago
|
||
On my win2k-cn, when I set Auto-detect to All, the charset marked as
windows-1252 as well.
I checked it on 07-25 win32 branch build on same machine, got same result as
build 07-27 branch build.
Updated•24 years ago
|
QA Contact: andreasb → ylong
On 07/24, 07/25 branch build, I don't see this problem with the first try, but
on the second try (clear cache, go to the page again), the problem appears.
Comment 5•24 years ago
|
||
assigning to shanjian. he knows the code best.
Assignee: yokoyama → shanjian
Comment 7•24 years ago
|
||
I saw same problem on WinME-Ja / 07-25 branch build, but WinME doesn't has
auto-detect All problem.
For Win2k-cn, if I using a new profile, then auto-detect All won't get problem,
but if I use a old profile and clear the cache, then auto-detect All and CJK,
Esat Asian will have this problem. This is same case on 07-25 and 07-27 branch
build. I guess it might not related with the check-in of bug 90288.
On linux, with a 07/26 build + Japanese lang pack, I saw this page recognized as
a EUC-JP page, so accented chars are displayed as question marks.
Comment 10•24 years ago
|
||
cc jbetak
Assignee | ||
Comment 11•24 years ago
|
||
In netscape french page, meta charset is specified in the middle of the
document. Meta charset sniffing does not work for this page, and CJK charset
detector return win1252 as detecting result, which is perfectly fine. The
problem is, when meta charset is met later, reload/update does not happen
correctly in certain situation. I trace the problem several times, and some time
I can see the problem. However, I still need more time to find out what is the
problem.
Status: NEW → ASSIGNED
Assignee | ||
Comment 12•24 years ago
|
||
After I simplified the testcase, I found out that this is a dup of 78229, which
has a fix already. Marked as so.
*** This bug has been marked as a duplicate of 78229 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 13•24 years ago
|
||
I need to reopen this bug. It doesn't seem to be the case.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Assignee | ||
Comment 14•24 years ago
|
||
After some investigation, I need mark this one as dup of 78229 once again.
Unfortunately, the proposed fix in 78229 does not work in this case, so a right
patch need to be worked out.
*** This bug has been marked as a duplicate of 78229 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
Comment 15•24 years ago
|
||
Mark it as verified per Shanjian's comments.
After bug 78229 fixed checked in, if still see same problem, then re-open it.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•