Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v3]

2025-04-05 Thread Alan Bateman
On Thu, 27 Mar 2025 16:03:08 GMT, Naoto Sato wrote: >> Those system property values on Windows were derived from Windows' >> `GetConsoleCP()` call, but they should have been taken from >> `GetConsoleOutputCP()`. Replacing the incorrect call with the correct one >> won't change any behavior, as

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v3]

2025-03-28 Thread Naoto Sato
On Thu, 27 Mar 2025 16:03:08 GMT, Naoto Sato wrote: >> Those system property values on Windows were derived from Windows' >> `GetConsoleCP()` call, but they should have been taken from >> `GetConsoleOutputCP()`. Replacing the incorrect call with the correct one >> won't change any behavior, as

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v3]

2025-03-27 Thread Brian Burkhalter
On Thu, 27 Mar 2025 16:03:08 GMT, Naoto Sato wrote: >> Those system property values on Windows were derived from Windows' >> `GetConsoleCP()` call, but they should have been taken from >> `GetConsoleOutputCP()`. Replacing the incorrect call with the correct one >> won't change any behavior, as

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v2]

2025-03-27 Thread Alan Bateman
On Thu, 27 Mar 2025 15:59:24 GMT, Naoto Sato wrote: >> src/java.base/windows/native/libjava/java_props_md.c line 142: >> >>> 140: cp = GetConsoleOutputCP(); >>> 141: } else { >>> 142: cp = GetConsoleCP(); >> >> Just a reminder that we should handle the case where GetConsoleX

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v2]

2025-03-27 Thread Naoto Sato
On Thu, 27 Mar 2025 16:12:24 GMT, Alan Bateman wrote: >> Ah, you mentioned it before which I forgot! Handled the error case too. > > How is NULL handled in the callers? Those system properties will be substituted with `native.encoding` https://github.com/openjdk/jdk/blob/dc5c4148c70ca43d0a69c326

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v3]

2025-03-27 Thread Naoto Sato
On Thu, 27 Mar 2025 16:11:47 GMT, Alan Bateman wrote: >> Naoto Sato has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Handled the error case > > src/java.base/windows/native/libjava/java_props_md.c line 131: > >> 129: } >> 130: >> 131: s

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v3]

2025-03-27 Thread Alan Bateman
On Thu, 27 Mar 2025 16:03:08 GMT, Naoto Sato wrote: >> Those system property values on Windows were derived from Windows' >> `GetConsoleCP()` call, but they should have been taken from >> `GetConsoleOutputCP()`. Replacing the incorrect call with the correct one >> won't change any behavior, as

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v2]

2025-03-27 Thread Naoto Sato
On Thu, 27 Mar 2025 07:36:07 GMT, Alan Bateman wrote: >> Naoto Sato has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Reflects the review comment > > src/java.base/windows/native/libjava/java_props_md.c line 142: > >> 140: cp = Ge

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v3]

2025-03-27 Thread Naoto Sato
> Those system property values on Windows were derived from Windows' > `GetConsoleCP()` call, but they should have been taken from > `GetConsoleOutputCP()`. Replacing the incorrect call with the correct one > won't change any behavior, as both calls return the same value by default > (`GetOEMCP

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v2]

2025-03-27 Thread Alan Bateman
On Wed, 26 Mar 2025 20:57:47 GMT, Naoto Sato wrote: >> Those system property values on Windows were derived from Windows' >> `GetConsoleCP()` call, but they should have been taken from >> `GetConsoleOutputCP()`. Replacing the incorrect call with the correct one >> won't change any behavior, as

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v2]

2025-03-26 Thread Naoto Sato
> Those system property values on Windows were derived from Windows' > `GetConsoleCP()` call, but they should have been taken from > `GetConsoleOutputCP()`. Replacing the incorrect call with the correct one > won't change any behavior, as both calls return the same value by default > (`GetOEMCP

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v2]

2025-03-26 Thread Brian Burkhalter
On Wed, 26 Mar 2025 20:57:47 GMT, Naoto Sato wrote: >> Those system property values on Windows were derived from Windows' >> `GetConsoleCP()` call, but they should have been taken from >> `GetConsoleOutputCP()`. Replacing the incorrect call with the correct one >> won't change any behavior, as

RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call

2025-03-26 Thread Naoto Sato
Those system property values on Windows were derived from Windows' `GetConsoleCP()` call, but they should have been taken from `GetConsoleOutputCP()`. Replacing the incorrect call with the correct one won't change any behavior, as both calls return the same value by default (`GetOEMCP()`). Howe

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call [v2]

2025-03-26 Thread Naoto Sato
On Wed, 26 Mar 2025 19:19:03 GMT, Alan Bateman wrote: >> Naoto Sato has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Reflects the review comment > > src/java.base/windows/native/libjava/java_props_md.c line 131: > >> 129: } >> 130: >> 1

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call

2025-03-26 Thread Alan Bateman
On Wed, 26 Mar 2025 18:57:37 GMT, Naoto Sato wrote: > Those system property values on Windows were derived from Windows' > `GetConsoleCP()` call, but they should have been taken from > `GetConsoleOutputCP()`. Replacing the incorrect call with the correct one > won't change any behavior, as bot

Re: RFR: 8352906: stdout/err.encoding on Windows set by incorrect Win32 call

2025-03-26 Thread Brian Burkhalter
On Wed, 26 Mar 2025 18:57:37 GMT, Naoto Sato wrote: > Those system property values on Windows were derived from Windows' > `GetConsoleCP()` call, but they should have been taken from > `GetConsoleOutputCP()`. Replacing the incorrect call with the correct one > won't change any behavior, as bot