JDK-4858889 : JNI Invocation API strings not UTF-8
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.1_02
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: other
  • CPU: unknown
  • Submitted: 2003-05-06
  • Updated: 2014-03-18
  • Resolved: 2014-02-20
Related Reports
Relates :  
JDK-4904545 - JDK tools fail to work with non-latin characters in the install path
Relates :  
JDK-8029584 - Allow \uxxxx unicode-escaping on the jvm command-line arguments
Relates :  
JDK-6475368 - Jar file doesnt execute if the path to it contains cyrilic letters
Description
In struct JavaVMOption, char *optionString is obviously not expected by the Invocation API to be encoded with Java's modified UTF-8, but rather with a "platform" encoding somehow derived from the OS environment.  This makes it impossible for a client of the Invocation API to reliably pass in any Unicode optionStrings.  Also, the documentation of the Invocation API lacks a description of how those strings should be encoded.
Comments
We don't intend to change the type of JavaVMOption to support UTF-8, closing as WNF
20-02-2014