JDK-8008386 : (cs) Unmappable leading should be decoded to replacement.
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.nio.charsets
  • Affected Version: 7,8
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-02-18
  • Updated: 2016-07-19
  • Resolved: 2013-10-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7 JDK 8
6u51Fixed 7u80Fixed 8 b115Fixed
Related Reports
Duplicate :  
Duplicate :  
Duplicate :  
Relates :  
Relates :  
Relates :  
Description
SHORT SUMMARY:
Unmappable single byte characters are incorrectly handled in multi-byte 
encodings
INDICATORS:
Incorrect decoding performed on multi-byte encoding for cases
where un-defined single-bytecode points are encountered

COUNTER INDICATORS:
TRIGGERS:
Issue in JDK 6 (and later) since 6227339 was fixed (6 GA)
KNOWN WORKAROUND: N/A
PRESENT SINCE: JDK 6 FCS
HOW TO VERIFY:
Testcase attached
NOTES FOR SE:
Suggestion as per Dev engineer comments : 
The problem of our implementation is that currently if it is not a "valid" 
single-byte,
it assumes it's a double-byte, and if it's a double-byte, and if it can't be 
mapped to
anything, treat it as a "un-mappable" double-byte., this is a wrong 
assumption for
this kind of "undefined" code point. The bottom line is that we should skip 
2, for
un-mappable double-byte character, but skip only 1, for un-defined 
single-byte
code point.

REGRESSION: Yes.


Comments
No issues with the fix in the 7u85 nightly test run. SQE OK to take it in PSU15_02
18-02-2015

This bug fix should address JDK-8025896 for jdk8 also.
16-10-2013

Chatting with Sherman - he's probably best to handle jdk8.
15-10-2013

If this is a regression - why are we not fixing in 7u40? Can we really push this regression to 7u60? I need some clarification before I can approve.
25-06-2013

SQE is OK with deferral request
24-06-2013

7u40-defer-request : This is a recent fix that's being implemented in jdk6u source for a Cu escalation at the moment. I'm planning to push this to 7u-dev (7u60) in coming weeks and no urgency for a 7u40 fix exists.
21-06-2013

Testcase demonstrates that the orignal output and the converted output (JIS) differ. Test output should be equal.
18-02-2013

Fix needed for jdk6 and later.
18-02-2013