-
Bug
-
Resolution: Fixed
-
P4
-
6
-
b43
-
x86
-
windows_2000
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8018763 | 7u45 | Xueming Shen | P4 | Closed | Fixed | b01 |
| JDK-8007265 | 7u40 | Xueming Shen | P4 | Closed | Fixed | b14 |
Some 538 UDC wrongly mapped and some 412 non-UDC characters missing in Java's MS936 converter.
For example, 0xA7A0 is supposed to be mapped to 0xE765 in Unicode (0xEE9DA5), whereas Java's MS936 maps it to 0xE79F in Unicode.
A comparison of MS936 to GBK mappings indicates that the Microsoft code page 936 is slightly different from GBK in terms of UDC mapping. However, Java's implementation of MS936 appears to be same as GBK.
A list of the incorrect mappings and missing characters is being provided to Sun separately.
The list is attached to this CR.
###@###.### 10/22/04 21:36 GMT
###@###.### 10/22/04 21:42 GMT
For example, 0xA7A0 is supposed to be mapped to 0xE765 in Unicode (0xEE9DA5), whereas Java's MS936 maps it to 0xE79F in Unicode.
A comparison of MS936 to GBK mappings indicates that the Microsoft code page 936 is slightly different from GBK in terms of UDC mapping. However, Java's implementation of MS936 appears to be same as GBK.
A list of the incorrect mappings and missing characters is being provided to Sun separately.
The list is attached to this CR.
###@###.### 10/22/04 21:36 GMT
###@###.### 10/22/04 21:42 GMT
- backported by
-
JDK-8007265 Many eudc characters are incorrectly mapped in MS936 and GBK converter
-
- Closed
-
-
-
- Closed
-