-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
black stain issue #28
Comments
This is fixed by PR #24 |
I am still seeing this issue using: |
Because 1.3.0 is from 2015. If you want to test the change, then you'd have to build from the repository. |
Thanks, that's what I planned on doing. I was thinking Jugen meant that the issue was fixed in a release. |
THKausherr, |
You need to make sure that the new jar is part of your classpath, and also that the old jar isn't. And this must also be at runtime. |
Maybe I am building the J2000 jar incorrectly. **I realize I shouldn't need to add the libs folder to source but have been trying everything to get this to work EDIT: built jar using Run As>Maven Install and now it works. Using the maven reference now instead of adding external jar. Just wasn't thinking I guess. Thanks for the help, the black stains are now gone. |
My built jai-imageio-jpeg2000-1.3.1-SNAPSHOT.jar has a size of 456KB. Another trick to see whether the file is in your classpath would be to access a class from there, e.g. com.github.jaiimageio.jpeg2000.J2KImageReadParam . |
built jar using Run As>Maven Install and now it works. Using the maven reference now instead of adding external jar. Just wasn't thinking I guess. Thanks for the help, the black stains are now gone. |
Ink blot problem now fixed, thanks. But the second PR mentioned at the beginning of this issue ( faceless2@94e047e ) wasn't committed, that one prevents garbled images in rare cases. |
There is an issue with "black stains" or "ink blots" etc appearing in some images.
See here for more info:
https://issues.apache.org/jira/browse/PDFBOX-1752
https://issues.apache.org/jira/browse/PDFBOX-1819
can be fixed by applying:
faceless2@b203429
faceless2@94e047e
The text was updated successfully, but these errors were encountered: