Ron Yorston

Thank you for the very detailed report. The point at issue here is a difference in the way command line arguments are handled in Unix shells and Windows cmd and...

I think that fixing this requires the use of Windows' wide character filename APIs. du uses opendir/readdir/closedir to handle directory traversal. mingw has non-standard wide character versions of these that...

I've made a couple of changes that should improve support for non-ASCII characters in ls and vi.

I know almost nothing about Windows codepages but I thought there might be problems. I'd like to get this sorted, though: cyrillic support is important to us at the company...

I've attempted to intercept I/O operations to the console and convert characters. I definitely haven't caught all I/O and nor have I tested it very thoroughly, but the latest binary...

A [patch](http://lists.busybox.net/pipermail/busybox/2020-February/087799.html) adding ```-b``` was submitted to the upstream mailing list last month.

Sufficiently interested to have kept this issue open for nearly seven years as a reminder. Make of that what you will. Observations: - BusyBox ```vi``` doesn't support UTF-8, only single-byte...

Yes, I'm sure. I fired up an Ubuntu 18.04 virtual machine to check, but no, it's just as borken as on Fedora. The utf8demo.txt file has no trailing white space...

@avih, thanks for the update. I think it's important that the standard binary of busybox-w32 should Just Work on any version of Windows and without any configuration by the user.

busybox-w32 has a very limited understanding of Windows users. When it reports the user is root it indicates you're running with elevated privileges ('as administrator'). Is that what's happening here?