3 ms·
Sure, if you can, file an Issue on Github! Did you try manually creating parity for that file (using par2cmdline)?
by brnt 6y ago
Sure, if you can, file an Issue on Github!
Did you try manually creating parity for that file (using par2cmdline)?
- solstice 6y agoI almost did but I tried something else and found the likely reason: the file name contained an "ä". Par2deep also fails when there's a CJK character in the filename. After removing these non-ascii characters it works. But this bug is going to cause problems for many people. Edit: filed a bug report
- brnt 6y agoThe joys of pre-UTF8 software :) You're right to point it out, however, the speed at which par2cmdline accepts PRs (~0/yr), consider it unfixable. I'm looking into https://github.com/akalin/gopar https://github.com/akalin/gopar and this may solve this.