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
Related to #34.
A typical nightmare due to Windows locale.
Tuw can show garbled strings if a child process does not use the default locale.
I should find a way to get locale for child processes or provide an option to set it by users.
I think there is nothing to do for unix-like systems because they use utf-8 basically.
The text was updated successfully, but these errors were encountered:
Supporting all locales would be hard to test, so I decided to support utf-8 only.
I'll add an option codepage.
{
"label": "UTF-8 output",
"command": "a command that outputs utf-8 strings",
"codepage": "utf-8",
"components": []
}
When utf-8 or utf8, tuw converts utf-8 strings to wstrings on Windows.
When default, tuw redirects output strings as it is.
Non-Windows platforms ignore the option.
Related to #34.
A typical nightmare due to Windows locale.
Tuw can show garbled strings if a child process does not use the default locale.
I should find a way to get locale for child processes or provide an option to set it by users.
I think there is nothing to do for unix-like systems because they use utf-8 basically.
The text was updated successfully, but these errors were encountered: