You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 7854 Reporter: turpin Assigned to:@nojb Status: resolved (set by @nojb on 2018-12-02T15:10:44Z) Resolution: fixed Priority: normal Severity: minor Platform: Windows MSVC OS: Windows MSVC OS Version: Windows 10 Fixed in version: 4.08.0+dev/beta1/beta2 Category: platform support (windows, cross-compilation, etc)
Bug description
I believe that, for the intended backward-compatibility purpose, CP_ACP is more appropriate than CP_THREAD_ACP. The former (System active code page) is the one used by the ANSI version of the Windows API functions. I think the latter is more related to user language settings.
Steps to reproduce
Difference between CP_THREAD_ACP and CP_ACP was observed on a japanese Windows 10 host (shift_js) with french as use language setting.
The text was updated successfully, but these errors were encountered:
Original bug ID: 7854
Reporter: turpin
Assigned to: @nojb
Status: resolved (set by @nojb on 2018-12-02T15:10:44Z)
Resolution: fixed
Priority: normal
Severity: minor
Platform: Windows MSVC
OS: Windows MSVC
OS Version: Windows 10
Fixed in version: 4.08.0+dev/beta1/beta2
Category: platform support (windows, cross-compilation, etc)
Bug description
I believe that, for the intended backward-compatibility purpose, CP_ACP is more appropriate than CP_THREAD_ACP. The former (System active code page) is the one used by the ANSI version of the Windows API functions. I think the latter is more related to user language settings.
Steps to reproduce
Difference between CP_THREAD_ACP and CP_ACP was observed on a japanese Windows 10 host (shift_js) with french as use language setting.
The text was updated successfully, but these errors were encountered: