> On 24 Sep 2024, at 17:41, Tommy Murphy <tommy_mur...@hotmail.com> wrote: > > 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.
I'm glad it works (thank you for testing, Tommy!) In the xPack distribution, the Windows archive is created with Linux `zip`, which, I guess, is pretty portable. > 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. I agree. According to my tests, I never had problems unpacking the archives, so, as long as keeping the non-ASCII names is not harmful in any way, I see no compelling reasons for removing them. However, personally I think that avoiding non-ASCII names is a matter of courtesy, allowing users to enter the names on any common keyboard. Regards, Liviu --- **[tickets:#435] Broken file** **Status:** new **Milestone:** 0.10.0 **Created:** Mon Sep 23, 2024 06:14 PM UTC by Paul **Last Updated:** Tue Sep 24, 2024 01:52 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.
