Closed Bug 9129 Opened 25 years ago Closed 25 years ago

DETECTCH.EXE (japsm,cjkpsm) does not detect SJIS charset on this page correctly

Categories

(Core :: Internationalization, defect, P3)

Product:
Core
Component:
Internationalization
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: teruko, Assigned: ftang)

References

(
URL
)

Details

(Whiteboard: have fix in local tree. Wait after M8 branch to check in.)

The detecator, japsm and cjkpsm do not detect charset on this page. step of reproduce 1. Copy this page to the directory as DETECTCH.EXE is located. 2. Type index.html | DETECTCH japsm 1024 3. Type index.html | DETECTCH cjkpsm 1024 Actual result step #2 Detect charset is Windows-1251 step #3 Detect charset is Windows-1251 Expected result all of 2 detectors detect this page as Shift-JIS. Tested 6-29-09 Win32 build under Winnt4.0J.
Target Milestone: M9
This looks like an EUC-JP page to me.
URL: http://www.fresheye.com/index → http://www.fresheye.com/index.html
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
1. It think teruko refer to http://www.fresheye.com/index.html , but not http://www.fresheye.com/index - I change the URL to http://www.fresheye.com/index.html 2. The page have invalid SJIS sequence 0x82 0xa0 in the HTML comment, which cause the detection fail. Therefore, I mark this bug invalid.
Status: RESOLVED → REOPENED
Status: REOPENED → ASSIGNED
sorry, I am wrong 0x82 0xA0 are legal Shift_JIS. (Thanks naoki). I reopen this bug.
Resolution: INVALID → ---
Whiteboard: have fix in local tree. Wait after M8 branch to check in.
have fix in local tree. Wait after M8 branch to check in.
Summary: DETECTCH.EXE does not detect charset on this page correctly → DETECTCH.EXE (japsm,cjkpsm) does not detect SJIS charset on this page correctly
change summary
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
fix check into M9 tree, not M8
Status: RESOLVED → VERIFIED
I verified this in 7-28-13-M9 Win32 build.
You need to log in before you can comment on or make changes to this bug.