-
Enhancement
-
Resolution: Unresolved
-
P3
-
7u6, 15, 16
Enhancement request from a customer.
When launching a Java Application under Windows using the Tanuki Wrapper, it
is impossible to properly send Unicode Characters to the command-line,
perhaps at all, perhaps without tightly restricting the System Encoding
configuration. It would really help, if we could Unicode-escape \uXXXX
characters on the command-line and then add a JVM argument to indicate this
was done. This would allow passing any Unicode character, even if only ASCII
is available on the command-line.
It appears that the Tanuki codebase uses the proper Win32 Unicode magic.
It appears that the JVM command-line arguments under Windows are parsed in
hotspot.src.os.windows.launcher.java_md.c and that it would be simple to
pre-parse the command-line to handle Unicode in this way.
The IBM JVM has this feature. See
http://publib.boulder.ibm.com/infocenter/javasdk/v5r0/index.jsp?topic=%2Fcom.ibm.java.doc.user.aix64.50%2Fuser%2Fglobalization.html
for Example.
When launching a Java Application under Windows using the Tanuki Wrapper, it
is impossible to properly send Unicode Characters to the command-line,
perhaps at all, perhaps without tightly restricting the System Encoding
configuration. It would really help, if we could Unicode-escape \uXXXX
characters on the command-line and then add a JVM argument to indicate this
was done. This would allow passing any Unicode character, even if only ASCII
is available on the command-line.
It appears that the Tanuki codebase uses the proper Win32 Unicode magic.
It appears that the JVM command-line arguments under Windows are parsed in
hotspot.src.os.windows.launcher.java_md.c and that it would be simple to
pre-parse the command-line to handle Unicode in this way.
The IBM JVM has this feature. See
http://publib.boulder.ibm.com/infocenter/javasdk/v5r0/index.jsp?topic=%2Fcom.ibm.java.doc.user.aix64.50%2Fuser%2Fglobalization.html
for Example.
- blocks
-
JDK-8205991 Cannot start application (WinLauncher) if path contains non-ascii character
- Open
- duplicates
-
JDK-8221508 Cannot run java.exe from folder if path contains non-ASCII character
- Closed
- relates to
-
JDK-8124977 cmdline encoding challenges on Windows
- Open
-
JDK-4858889 JNI Invocation API strings not UTF-8
- Closed
-
JDK-8221508 Cannot run java.exe from folder if path contains non-ASCII character
- Closed