#97 Fix for invalid file names

[laf]

Anyone who uses thunar typically also uses Xarchiver. However if Xarchiver handles a file with an invalid file name nothing happens; no error message, no extraction nothing. A common character for valid windows file names that are invalid in linux is the appostrophe '

So there's a number of fixes possible:
Where the invalid character is an appostrophe, rename file without appostrophe then extract; this would be great.
Could also execute script to search for invalid characters in file name and remove such character then extract; this would be excellent addition to Xarchiver.
Where the invalid character is not an appostrophe or where the file name is invalid, create error message and detail the linux file name requirements and acceptable characters; this is the bare minimum.

The defacto in linux is if a command it entered and nothing happens then it worked and there is no problem. Hence why the aforementioned is a bug because extraction fails without notice and this is contrary to linux and computing standards.

[Giuseppe Torelli]

Hello,

Thank you for your email but Xarchiver is definitely abandoned as there are
better archivers out there.

Kind regards
Giuseppe

On Mon, 9 Mar 2020, 15:48 laf, neonred@users.sourceforge.net wrote:

---

[bugs:#97] Fix for invalid file names

Status: open
Group: v1.0 (example)
Created: Mon Mar 09, 2020 03:48 PM UTC by laf
Last Updated: Mon Mar 09, 2020 03:48 PM UTC
Owner: nobody

Anyone who uses thunar typically also uses Xarchiver. However if
Xarchiver handles a file with an invalid file name nothing happens; no
error message, no extraction nothing. A common character for valid windows
file names that are invalid in linux is the appostrophe '

So there's a number of fixes possible:
Where the invalid character is an appostrophe, rename file without
appostrophe then extract; this would be great.
Could also execute script to search for invalid characters in file name
and remove such character then extract; this would be excellent addition to
Xarchiver.
Where the invalid character is not an appostrophe or where the file name
is invalid, create error message and detail the linux file name
requirements and acceptable characters; this is the bare minimum.

The defacto in linux is if a command it entered and nothing happens then
it worked and there is no problem. Hence why the aforementioned is a bug
because extraction fails without notice and this is contrary to linux and
computing standards.

---

Sent from sourceforge.net because you indicated interest in <
https://sourceforge.net/p/xarchiver/bugs/97/>

To unsubscribe from further messages, please visit <
https://sourceforge.net/auth/subscriptions/>

[Martin Mokrejs]

On a similar note, it would be nice if I can change the charset used to decode filenames stored in the archive. Often I receive archives from MS Win computer in cp1252 encoding but provided my locale is set to cs_CZ.utf8 the filenames are broken and replaced by question marks. It would be nice if I could select inside the Xarchiver GUI source charset encoding and output encoding. An example of such archive is here: https://portal.cenia.cz/eiasea/download/RUlBX09MSzkyN19vem5hbWVuaURPQ18yMDkyODIwMDY3MzE0MDc2NTMxLnppcA/OLK927_oznameni.zip . There is an option to right-click over a filename and to rename it. It would be handy if one could change input charset locale to test which one to use per file and somewhere in Menu to apply the settings over a whole archive, which would be re-parsed again as a whole.

@gt67 Which are the better archivers on Linux. unzip and 7z have similar issues with supposedly badly tagged ZIP files packed with invalid encoding?