I encounter this bug for too many years.
The workaround works to verify. But using the repair to an undamaged file, ads 
a "(invalid encoding)" to the file extension. I have not tried to repair 
damaged files with a "wrong name" yet.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/433260

Title:
  par2 cannot work with special characters

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/par2cmdline/+bug/433260/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to