Hey Tommy, I want to echo your statements and probably add a bit more clarification.
I was the one who added some non-ASCII file names and I still think it was a good idea. All the other targets are using their official names, so why make an exception for those having non-Latin letters? Single-byte encodings are the memories from the past by now, so what else would be a solid technical reason for that? On Tue, Sep 24, 2024 at 07:28:26AM +0000, Tommy Murphy wrote: > I remember a few such filenames in the OpenOCD > source base years ago but then the files in question were either renamed or > were > removed along the way. 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. > Similarly, I'm not sure if there's any stated policy on > stuff like removing from files content such as links/URLs of a specific > geographical/national nature, but I suspect that anything suggestive of > censorship might be potentially controversial? There's no policy indeed. And removing actual information and code "just because" is indeed controversial. If the chip was only good for military purposes it might have made some sense, but "banning" a generic Cortex-M MCU for the crimes of its country is just silly I think. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com
