dsh-console-utf8

When running bash commands through dsh on Windows, output from Windows-native child processes such as powershell, git, and cmd frequently arrives as mojibake. The root cause is not a decoding bug: the console defaults to an OEM code page (936 on Chinese systems, 932 on Japanese, 437 on US-English), while the dsh subprocess layer decodes child stdout as UTF-8. The mismatch irrevocably destroys every non-ASCII character in that output.

dsh-console-utf8 does one thing well: it makes the console speak UTF-8. It switches the host console to code page 65001 via chcp, reads the page back to confirm the change actually took effect, and maintains a BASH_ENV hook script so every non-interactive bash -c invocation re-applies the code page within its own process group. This covers the case where the shell executor spawns a fresh console that would otherwise revert to the system default. The plugin writes exactly two files (the hook script and a bounded lifecycle log), never rewrites commands, never touches PATH, and never patches the shell stack.

Best suited for developers who use dsh with bash on Windows and whose child-process output contains Chinese, Japanese, or other non-ASCII text. If you see garbled output from git log, chcp, or powershell in your TUI session, the issue resolves after a single /restart. On a pure US-English locale the benefit is minimal since code page 437 and UTF-8 share most printable ASCII characters.