JDK-4976235 : iso-2022-jp: provide support for NEC-Row-13 characters
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.nio.charsets
  • Affected Version: 1.4.2
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_8
  • CPU: sparc
  • Submitted: 2004-01-09
  • Updated: 2005-10-25
  • Resolved: 2005-10-25
Related Reports
Duplicate :  
Relates :  
Description
Escalation: 549119 (NICP - Portal Products, Sun ONE Portal Server)
Escalation Bug Id: 4945426
Customer: Bank of Tokyo Mitsubishi

The customer, Bank of Tokyo Mitsubishi - one of the largest banks in Japan, is requesting support for MS932 characters, i.e. circled digits (NEC-ROW-13) characters, in the iso-2022-jp charset.

Problem:
User composes a message in Sun ONE Messaging Server's Messenger Express.  The message contains MS932 characters in the subject and the charset encoding is iso-2022-jp
  
Messenger Express displays the characters correctly.  It uses ICU libraries for conversion.

The Sun ONE Portal Server Mail channel does not display the characters correctly.  It uses Java for conversion.

The customer is experiencing the problem with JDK 1.3.1_06, but will need the fix for JDK 1.4.2


>From an engineer on the J2SE I18N team.
> .......
>
> These characters are  so called NEC-Row-13 characters, which are NOT
> part of
> jis-x-208 but supported by different vendors in their "user
> defined/vender defined"
> area for "compability" reason on different platforms. But they are not
> supported by
> iso-2022-jp, which is supposed to only include characters defined in
> jis-x-0208
> and jis-x-0201, ascii.

Comments
EVALUATION NEW-ROW-13 hs now supported in several newly added Windows iso-2022-jp variants, see 6173388.
25-10-2005

EVALUATION The IANA registered ISO-2022-JP is based upon RFC 1468 and there is an extension of ISO-2022-JP defined in RFC 1554 (ISO-2022-JP-2 multilingual extension of ISO-2022-JP). Standards based implementations of ISO-2022-JP and its known variants use JIS X 0212 and JIS X 0208 without additional vendor added character mappings. Where customers or solution providers need to build upon, redefine or extend custom charsets for particular solutions (eg, to overcome transcoding issues from roundtrip and content aggregation in portal applications) it might be more appropriate for the middleware products or solution providers to make use of the java.nio.charset API/SPI to provide custom pluggable charsets rather than have j2se provide overloaded variant charsets as part of the standard bundling of supported charsets. So it is not immediately evident that by adding NEC ROW 13 mapping support into either the existing ISO-2022-JP j2se provided NIO charset implementation (probably would break standards compliance) or adding a ISO-2022-JP-vendor-extended variant to the standard bundling of j2se supported charsets (possibly better handled by being provided outside of standard j2se bundled set). ###@###.### 2004-01-13 ###@###.### 2005-07-21 00:16:04 GMT
13-01-2004