It is a Unicode issue and it needs to be fixed. Tonight after downloading 4.8Gigs of files I found I cannot use par2cmdline to fix them.
Running the following, I get errors because the file cannot be found.
$ par2 r La\ Bête.par2
par2cmdline version 0.4, Copyright (C) 2003 Peter Brian Clements.
par2cmdline comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it and/or modify
it under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version. See COPYING for details.
Loading "La Bête.vol061+29.PAR2".
Loaded 235 new packets including 29 recovery blocks
There are 102 recoverable files and 0 other files.
The block size used was 1724140 bytes.
There are a total of 2950 data blocks.
The total size of the data files is 5084948804 bytes.
Verifying source files:
Target: "LaB�te.part001.rar" - missing.
Target: "LaB�te.part002.rar" - missing.
Target: "LaB�te.part003.rar" - missing.
…
Scanning extra files:
Repair is required.
102 file(s) are missing.
You have 0 out of 2950 data blocks available.
You have 29 recovery blocks available.
Repair is not possible.
You need 2921 more recovery blocks to be able to repair.
================================
From the one bug report, I tried to fix a single damaged file but it wouldn't fix as the rest of the 102 files are still missing.
"Unicode issue" as in: "par2 clients don't support the optional unicode parts of the par2 specs
and stupidly write 8-bit characters to the ascii (7-bit) 'name of the file' field of the File Description packet"?
Fixing that file set is easy. for ex: par2 r La\ Bête.par2 La*.rar
The resulting rar files might or might not have an "ê" in the filename,
depending on the fact if you and the creator of the par2 set use the same character encoding…
If clients had adhered to the specs and hadn't stored non-ascii characters in what should have been an ascii-only field, the clients
would probably have had no other choice but to implement the optional unicode stuff to store non-ascii filenames years ago… :(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does anyone know how to make par2repair recognize non-locale character encoding, specifically ISO 8859-1 German characters?
Are you talking about the chars in filenames?
While understanding the code, I saw that it removes (escapes) a lot of chars from filenames.
could this be your problem?
in my opinion this is not neccessary at all...
but I am not sure about this
JPT
It is a Unicode issue and it needs to be fixed. Tonight after downloading 4.8Gigs of files I found I cannot use par2cmdline to fix them.
Running the following, I get errors because the file cannot be found.
$ par2 r La\ Bête.par2
par2cmdline version 0.4, Copyright (C) 2003 Peter Brian Clements.
par2cmdline comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it and/or modify
it under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version. See COPYING for details.
Loading "La Bête.vol061+29.PAR2".
Loaded 235 new packets including 29 recovery blocks
There are 102 recoverable files and 0 other files.
The block size used was 1724140 bytes.
There are a total of 2950 data blocks.
The total size of the data files is 5084948804 bytes.
Verifying source files:
Target: "LaB�te.part001.rar" - missing.
Target: "LaB�te.part002.rar" - missing.
Target: "LaB�te.part003.rar" - missing.
…
Scanning extra files:
Repair is required.
102 file(s) are missing.
You have 0 out of 2950 data blocks available.
You have 29 recovery blocks available.
Repair is not possible.
You need 2921 more recovery blocks to be able to repair.
================================
From the one bug report, I tried to fix a single damaged file but it wouldn't fix as the rest of the 102 files are still missing.
Files were downloaded from a.b.sleazemovies
https://sourceforge.net/tracker/index.php?func=detail&aid=839542&group_id=30568&atid=399698
"Unicode issue" as in: "par2 clients don't support the optional unicode parts of the par2 specs
and stupidly write 8-bit characters to the ascii (7-bit) 'name of the file' field of the File Description packet"?
Fixing that file set is easy. for ex: par2 r La\ Bête.par2 La*.rar
The resulting rar files might or might not have an "ê" in the filename,
depending on the fact if you and the creator of the par2 set use the same character encoding…
If clients had adhered to the specs and hadn't stored non-ascii characters in what should have been an ascii-only field, the clients
would probably have had no other choice but to implement the optional unicode stuff to store non-ascii filenames years ago… :(
Thank you macrovanloon. It seems to have worked. I am running it now and par2 is doing the repairs and passed.
This is something that should be added to the help file, at least until the unicode issue is fixed.
- par2 r {filename.par2} {unicode files*.rar}
- eg. par2 r La\ Bête.par2 La*.rar
I hope it helps someone else.