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.
- relates to
-
JDK-4904545 JDK tools fail to work with non-latin characters in the install path
- Closed
-
JDK-6475368 Jar file doesnt execute if the path to it contains cyrilic letters
- Resolved
-
JDK-8029584 Allow \uxxxx unicode-escaping on the jvm command-line arguments
- Open