Closed Bug 9128 Opened 27 years ago Closed 26 years ago

DETECTCH.EXE (zhcnpsm, cjkpsm) does not detect Big5 on this page

Categories

(Core :: Internationalization, defect, P2)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: teruko, Assigned: ftang)

References

()

Details

The detecator, zhcnpsm, zhtwpsm, and cjkpsm does 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 zhcnpsm 1024 3. Type index.html | DETECTCH zhtwpwm 1024 4. Type index.html | DETECTCH cjkpsm 1024 Actual result step #2 Did not detect any charsets step #3 Did not detect any charsets step #4 Did not detect any charsets Expected result all of 3 detectors detect this page as BIG5. Tested 6-29-09 Win32 build under Winnt4.0J.
Priority: P3 → P2
Target Milestone: M9
This file is 2219 bytes long. Only the very last line has any Big5 characters. I assume the 2nd argument is the # bytes to check, so retry this Type index.html | DETECTCH ??cnpsm 2219 and see if it detects it.
I tried the following. 1. Type index.html | DETECTCH zhcnpsm 2219 2. Type index.html | DETECTCH zhtwpwm 2219 3. Type index.html | DETECTCH cjkpsm 2219 Actual result #1 Detect as windows-1252 #2 Did not detect any charsets #3 Did not detect any charsets
Status: NEW → ASSIGNED
zhcnpsm won't detect Big5 at all. Please ignore zhcnpsm in the previous comment.
Summary: DETECTCH.EXE does not detect charset on this page → DETECTCH.EXE (zhcnpsm, cjkpsm) does not detect Big5 on this page
Target Milestone: M9 → M12
change summary to "DETECTCH.EXE (zhcnpsm, cjkpsm) does not detect Big5 on this page" Mark this as M12, I won't fix zhcnpsm, cjkpsm bug untill M12
Target Milestone: M12 → M13
Target Milestone: M13 → M14
Target Milestone: M14 → M15
add yueheng.xu@intel.com to the CC list
Target Milestone: M15 → M20
change to M20
I think I fix this before 5/16
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
I verified this in 2000-06-19-08 Win32 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.