-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Problem with PNG Compression in Adobe Acrobat #862
Comments
CC @buenjybar |
Hi, what is the timeframe for this issue? Edit: getPredictorFromCompression = function getPredictorFromCompression(compression) {
var predictor;
switch (compression) {
case jsPDFAPI.image_compression.FAST:
predictor = 11;
break;
case jsPDFAPI.image_compression.MEDIUM:
predictor = 13;
break;
case jsPDFAPI.image_compression.SLOW:
predictor = 14;
break;
default:
predictor = 12;
break;
}
return predictor;
}, |
Is this fixed? I am having a similar issue with adobe acrobat reader dc version 2015.017.20053 with the attached file. Thanks. |
@nnylip Can you send me the image you have embedded? I'll write up a test case! |
I've created a test case, it renders fine in Firefox and Chrome, but not Acrobat DC https://github.com/MrRio/jsPDF/blob/bugfix/png/tests/readers/reference/broken-png-2.pdf Steps to reproduce: npm run local-test # run this once
rm ./tests/readers/reference/broken-png-2.pdf
./node_modules/.bin/karma run -- --grep="render transparent PNG"
open -a Adobe\ Acrobat\ Reader\ DC ./tests/readers/reference/broken-png-2.pdf |
The test program that created pdf is attached (image is changed as client might object), it uses On 10/10/2016 05:00 PM, James Hall wrote:
|
Hey @diegocr @jamesbrobb any idea what the issue here might be? Renders ok in Chrome. |
Anything happening with this? |
Currently looking into it! |
This issue started happening to me after updating from version 1.2.61 to 1.3.2. PDF is opened in Chrome but not in Adobe Acrobat Reader, gives 110 error. Rolled back to version 1.2.61 solved it for now. |
So how can I get this fixed? I am having the same problem @ido172 ? |
@edisonramaa i'm also waiting for a fix. i just Installed version 1.2.61 instead of 1.3.2. The error doesn't appear to exist there |
@MrRio should make a new release to fix the problem |
@MrRio we're waiting for release, can we help you with this? |
Thank you @Pe46dro! |
i have overwriten the dist folder of the npm files in node_modules with the ones from https://github.com/MrRio/jsPDF/archive/master.zip And this is how it should look(like it does with adobe reader opening the file on chrome or firefox). |
@stefanaerts This might be an issue from Safari PDF Reader. |
it's ok,safari works fine. |
Hi All, I am facing the similar issue. I have created a Plunkr to demonstrate this issue. I have tried with both the version 1.2.61 and 1.3.2, but both version showing some different behavior. @buenjybar any suggestions. |
Thank you @Pe46dro !! Waiting for release. |
any update on this issue? |
@codeReadyy @robpolak
|
Hey still getting the same issue with he latest download of jspdf, looks like that code has been implemented but still receiving error 101 on acrobat reader :( |
@Ant248 The current release is missing the default in the switch statement. Use the solution I posted above to fix until the release is updated |
Thanks! Odd i have this in my release: getPredictorFromCompression = function getPredictorFromCompression(compression) {
Seems to be what you have posted? |
@Ant248 The current release (1.3.3) still have this issue! I just follow @AshKetchumza instructions with previous version (1.3.2) and it works perfectly! |
The 110 error comes when you add PNG image on the document |
Note: version 1.3.4 doesn't have this PNG compression issue. |
Indeed, version 1.3.4 seems to not have this issue. |
Then it is officially fixed. :) |
See #852 (comment)
The text was updated successfully, but these errors were encountered: