JDK-4631430 : JNI spec lacks character encoding spec for many functions
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2002-01-31
  • Updated: 2014-03-03
  • Resolved: 2014-03-03
Related Reports
Relates :  
Relates :  
Description

Name: nl37777			Date: 01/31/2002

The JNI specification, in particular the page
http://java.sun.com/j2se/1.4/docs/guide/jni/spec/functions.doc.html
lacks the specification of the character encoding used for many of
the functions that accept char* parameters. For each function
accepting such parameters, the character encoding must be clearly
specified - as UTF-8 (meaning the real one specified by the Unicode
Consortium), Java-modified UTF-8, the default platform encoding, or
whatever is appropriate.

The lack of this specification has been contributing to bugs such
as 4258198.
======================================================================

Comments
RT Triage Team: We have no plans to change this behavior. Any improvement to this area should be addressed through a JEP and we'd be happy to address through additional requirements.
03-03-2014