Closed Bug 10230 Opened 25 years ago Closed 25 years ago

Detectch (japsm) does not detect any charsets

Categories

(Core :: Internationalization, defect, P2)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: teruko, Assigned: ftang)

References

()

Details

Attachments

(1 file)

Tested 7-20-12-M9 Win32 build.

Step of reproduce
1. Save above file in the same directory as apprunner is located.
2. type index.html | DetectCh japsm 1024

Expected result EUC
Actual result   No charset is detected

I did the same thing in http://home.netscape.com/ja   page
Detectch did not detect any charsets.
Priority: P3 → P2
Target Milestone: M9
Status: NEW → ASSIGNED
Z:\mozilla\dist\WIN32_D.OBJ\bin>perl -MLWP::Simple -e "getprint 'http://home.net
scape.com/ja/index.html'"|DetectCharset japsm 1024
It's NOT windows-1252- byte 0(0)
It's NOT UTF-8- byte 0(0)
It's NOT Shift_JIS- byte 0(0)
It's NOT ISO-2022-JP- byte 31(1f)
It's NOT ISO-10646-UCS-2- byte 233(e9)
Done
Done 2
This mean we have some problem with the new ISO-10646-UCS-2-LE verifier which it
does not go into error state as we expect.
*** Bug 10340 has been marked as a duplicate of this bug. ***
Find the bug on the 1.3 of mozilla/intl/chardet/src/nsPkgInt.h All the PRUint16
in the #define should be PRUint32. Wait till people give me ok from hook to
check in.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
fix.
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.

Attachment

General

Created:
Updated:
Size: