2009-10-17 15:00:03 UTC
"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... :(
