_WinAPI_AnsiToOem + _WinAPI_OemToAnsi

[Zedna]

Here is proposition for new UDF to WinApi include also with examples:

; Name...........: _WinAPI_AnsiToOem
; Description ...: Translates a string into the OEM-defined character set
; Syntax.........: _WinAPI_AnsiToOem($sText)

#cs
non english (accented) letters written to AU3 script from Scite (GUI)
must be converted to be correct in commandline output (CUI)
#ce

; Name...........: _WinAPI_OemToAnsi
; Description ...: Translates a string from the OEM-defined character set into either an ANSI or a wide-character string
; Syntax.........: _WinAPI_OemToAnsi($sText)

#cs
non english (accented) letters in output from CUI commandline tools (like PING, NET VIEW, ...)
must be converted to be correct in Windows GUI output (MsgBox)
#ce

[Jpm]

Those functions already exist using _WinAPI_WideCharToMultiByte() and _WinAPI_MultiByteToWideChar() with $iCodePage = 1
I am just wondering if we should add this code to
ConsoleWrite($text [, $iCodePage = 0])

[Jpm]

I update the functions _WinAPI_WideCharToMultiByte() and _WinAPI_MultiByteToWideChar() to support "string" or struct as input and a new optional can force the return in a "string"

[Jpm]

Added in version: 3.3.1.2