> Or just people stopped using broken tools. If the filename has Unicode > characters, so what, how does it make it broken? Quite the contrary, > it's an additional test to expose and let the broken tools be fixed.
I can see merit in this argument. Reminds me a bit of Linus's "tabs versus spaces" gate... :-) https://arstechnica.com/gadgets/2024/04/linus-torvalds-reiterates-his-tabs-versus-spaces-stance-with-a-kernel-trap/ I'm also curious as to what specific platforms/tools people have seen having problems with filenames such as "1986ве1т.cfg" and "к1879xб1я.cfg"? I just downloaded the latest xPack OpenOCD (https://xpack-dev-tools.github.io/openocd-xpack/docs/releases/) and extracted it using 7Zip and Windows Explorer ("File Manager") and neither had problems extracting all contents including 1986ве1т.cfg or к1879xб1я.cfg and I can use these files from the command line, editors etc. Personally, as things stand, I don't really see a compelling case for removing or renaming (to ASCII (or ANSI?) only) such files - or unilaterally removing content from them. Where somebody has a different opinion then maybe the best way to test it is via the patch/review process?
