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 --- **[tickets:#435] Broken file** **Status:** new **Milestone:** 0.10.0 **Created:** Mon Sep 23, 2024 06:14 PM UTC by Paul **Last Updated:** Mon Sep 23, 2024 06:14 PM UTC **Owner:** nobody Hi maintainers and contributors, Please remove https://github.com/openocd-org/openocd/blob/ad216136180e0cd482f414eb072c9dd25dd1c559/tcl/target/1986%D0%B2%D0%B51%D1%82.cfg or https://sourceforge.net/p/openocd/code/ci/master/tree/tcl/target/1986%D0%B2%D0%B51%D1%82.cfg from the repository. Many tools can't cope with these special chars in it. Which results in extraction errors if someone tries to extract a zip with this file and OpenOCD in it. Also some file system tools don't like them and fail to display the file name correctly. (This is not the reason for the ticket but it would be reason enough: it's Russian and contains a link to a Russian {.ru} web site. If you don't support the war against the Ukrain I it would be nice to remove any links {and in the same act support for special products from them} to them from your software) And here is some example on a Windows system how an error of a library which failed to extract the zip look like: `scripts\target\1986??1?.cfg` as you can see the special chars broke the path. --- Sent from sourceforge.net because openocd-devel@lists.sourceforge.net is subscribed to https://sourceforge.net/p/openocd/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
