avih

What's the downside of the wrapper? I'd guess embedding it in the binary? (and building it in the first place?)

> * then: `mt.exe -manifest utf8.manifest -outputresource:busybox.exe;#1` which will attach this manifest to the busybox.exe binary. (`mt.exe` is from the windows SDK... So, few things: `mt.exe` is closed source and...

> If the strings are kept internally in variables as UTF-8... The fact is that it's both a very useful feature, and also a feature which was not yet implemented...

I can confirm error 40: ```sh $ ./busybox wget https://files.catbox.moe/hkoctg.apk Connecting to files.catbox.moe (108.181.20.35:443) ssl_client: TLS error from peer (alert code 40): handshake failure wget: error getting response ``` in...

Hmmm... that's unfortunate. Thanks for the analysis.

For reference, in glibc `wcwidth(0xad)` appears to be 1. Judging by this discussion: https://sourceware.org/bugzilla/show_bug.cgi?id=22073 which concluded that it should be 1. That discussion took place in 2017 - after the...

For what it's worth, the musl-libc maintainer, @richfelker said on IRC that he thinks it should be 1 because historically it was 1 (in most/all implementations?), and, quoting, "(dalias) unless...

> if the most popular terminal emulators measure it as width of 1 then I’d like to match Right. I would guess that terminals measure its width according to the...

> I would guess that terminals measure its width according to the `wcwidth` implementation which they use? And I would also guess that typically that would be whatever libc provides?...

> At which case, the test should be dual... So, I tested it in the following terminals on Alpine linux 3.19.1, and all the tested terminal emulators treat it either...