-
Bug
-
Resolution: Fixed
-
P3
-
17, 18
-
b22
-
generic
-
windows
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8293085 | 17.0.6-oracle | Yoshiki Sato | P3 | Resolved | Fixed | b01 |
JDK-8290120 | 17.0.5 | Christoph Langer | P3 | Resolved | Fixed | b01 |
JDK-8293084 | 11.0.18-oracle | Yoshiki Sato | P3 | Resolved | Fixed | b01 |
JDK-8290869 | 11.0.17 | Christoph Langer | P3 | Resolved | Fixed | b01 |
----
When we turned on "Use Unicode UTF-8 for worldwide language support"(something like https://stackoverflow.com/questions/56419639/what-does-beta-use-unicode-utf-8-for-worldwide-language-support-actually-do) option, java default launcher can not parse arguments that containing Chinese characters:
java Foo 你好世界
String[]args are actually garbled Chinese characters.
- backported by
-
JDK-8290120 Java launcher can not parse Chinese character when system locale is set to UTF-8
- Resolved
-
JDK-8290869 Java launcher can not parse Chinese character when system locale is set to UTF-8
- Resolved
-
JDK-8293084 Java launcher can not parse Chinese character when system locale is set to UTF-8
- Resolved
-
JDK-8293085 Java launcher can not parse Chinese character when system locale is set to UTF-8
- Resolved
- relates to
-
JDK-8124977 cmdline encoding challenges on Windows
- Open
-
JDK-8266774 System property values for stdout/err on Windows UTF-8
- Resolved
-
JDK-6584897 Cannot invoke class from command line with args containing non-ASCII characters
- Closed
-
JDK-8260265 UTF-8 by Default
- Resolved
- links to
-
Commit openjdk/jdk11u-dev/1a66d5a5
-
Commit openjdk/jdk17u-dev/011b96c3
-
Commit openjdk/jdk/22934485
-
Review openjdk/jdk11u-dev/1228
-
Review openjdk/jdk11u-dev/1234
-
Review openjdk/jdk17u-dev/522
-
Review openjdk/jdk17u-dev/530
-
Review openjdk/jdk/8434