-
Bug
-
Resolution: Fixed
-
P3
-
5.0u7, 6
-
b03
-
generic, x86
-
windows, windows_xp
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2141404 | 6u2 | Martin Buchholz | P3 | Resolved | Fixed | b01 |
JDK-2141403 | 5.0u11 | Yumin Qi | P2 | Resolved | Fixed | b02 |
As specified in the Microsoft documentation,
http://windowssdk.msdn.microsoft.com/en-us/library/ms682009.aspx
"All strings in the environment block must be sorted alphabetically by name. The sort is case-insensitive, Unicode order, without regard to locale"
Unfortunately, this specification does not make it clear whether a character between
the lower-case range and the upper-case range, such as "_", should sort
before or after the alphabetic characters. An empirical test shows that it
Windows (actually cmd.exe's "set" command) sorts it after, while Java's
implementation sorts it before.
http://windowssdk.msdn.microsoft.com/en-us/library/ms682009.aspx
"All strings in the environment block must be sorted alphabetically by name. The sort is case-insensitive, Unicode order, without regard to locale"
Unfortunately, this specification does not make it clear whether a character between
the lower-case range and the upper-case range, such as "_", should sort
before or after the alphabetic characters. An empirical test shows that it
Windows (actually cmd.exe's "set" command) sorts it after, while Java's
implementation sorts it before.
- backported by
-
JDK-2141403 (process) subprocess environment sort order differs from Windows native sort order
- Resolved
-
JDK-2141404 (process) subprocess environment sort order differs from Windows native sort order
- Resolved
- relates to
-
JDK-6464222 (str) String.CaseInsensitiveComparator small code improvement
- Closed