Hi Charles,
My apology for the late response. I was on vacation the past week and
did not have full email
access.
As Sean pointed out, this is triggered by the change we just put in
recently for 8008386, in which
tried to address a strong request that asked for case like 'fe' '40' to
be tre
What incantation is required to get Sherman to offer his perspective? :-)
I accept that it may be after Thanksgiving, but I need to know the
situation since we have tests for JRuby that depended on this
character being valid Shift-JIS.
- Charlie
On Mon, Nov 25, 2013 at 4:08 AM, Seán Coffey wrot
Sherman can answer this best. The 8008386 fix for 8 differs from earlier
updates since alot of the code was rewritten in this area. The initial
report was identified as a regression in JDK6. Back in 2005, the 6227339
fix changed behaviour which meant that invalid single byte characters
were tre
On 22/11/2013 11:02, Charles Oliver Nutter wrote:
Apologies if this is not the correct place to post this, bit i18n
seemed more focused on languages and localization than the mechanics
of transcoding.
I have noticed a behavioral difference in JDK8 decoding a two-byte
Shift-JIS sequence. Specific
Apologies if this is not the correct place to post this, bit i18n
seemed more focused on languages and localization than the mechanics
of transcoding.
I have noticed a behavioral difference in JDK8 decoding a two-byte
Shift-JIS sequence. Specifically, JDK8 appears to report malformed
input for wha
