If you put a protected / secured PDF in the /source/ folder, the project will not open and an error message such as "Unable to read project file! -- java.lang.NoClassDefFoundError: org/bouncycastle/jce/provider/BouncyCastleProvider -- OK" will show up. Same happens if you try to reload the project after putting the file in /source/.
Right now the user is left with the error message but can't really do anything. After clicking OK, the project gets closed and the cursor becomes an hourglass (although you can still go to the menu and continue opening a new project, for instance). It would be much better if the error message was more informative and the project could open (or keep open) nevertheless.
Password-protected PDFs are not currently supported, but the way the error is (not) handled at the moment is problematic.
I have fixed it so we handle this the same way we handle other format errors: The file is skipped and the project continues loading as usual. At the moment there is no good way to propagate the error up to the user as a dialog, so I have added a log message instead.
Thanks, Aaron. As a side note, the issue occurred even with non-password protected PDF's, namely those that prevent you from selecting and/or copying text, but don't require any password to open them. I thought it was relevant to your troubleshooting.
Please try a nightly build and report back with a sample file if the issue
still occurs.
Fixed in the released version 4.1 of OmegaT.
Didier