View Single Post
Old 11-21-2015, 06:10 PM   #24
PHC
Member
PHC is as sexy as a twisted cruller doughtnut.PHC is as sexy as a twisted cruller doughtnut.PHC is as sexy as a twisted cruller doughtnut.PHC is as sexy as a twisted cruller doughtnut.PHC is as sexy as a twisted cruller doughtnut.PHC is as sexy as a twisted cruller doughtnut.PHC is as sexy as a twisted cruller doughtnut.PHC is as sexy as a twisted cruller doughtnut.PHC is as sexy as a twisted cruller doughtnut.PHC is as sexy as a twisted cruller doughtnut.PHC is as sexy as a twisted cruller doughtnut.
 
Posts: 21
Karma: 15000
Join Date: Feb 2014
Device: iPhone, iPad, Macbook Pro, Mac Pro
Quote:
Originally Posted by willus View Post
You are correct. What I discovered doing more experimentation is that if the source PDF has lossless bitmap encodings (e.g. LZW/Flate, as I had in my example), then the ghostscript output with "pdfwrite" is a lossless replica. But if the source PDF has bitmaps with lossy encodings, this is not the case--the ghostscript output will be different. Since k2pdfopt defaults to writing LZW/Flate bitmaps, this method has always worked fine on k2pdfopt output, but it is not as effective for PDFs with lossy encodings. (Also, ghostscript does not support writing PDFs with JBIG2/JPX encodings, which you had in your source PDF, due to patent issues, so it had to change these encodings to something else entirely.)
That is very interesting. So it treats even different LOSSY encodings differently apparently. Where is it stated that this particular encoding has a patent issue? Is there documentation that states which codecs are supported?
PHC is offline   Reply With Quote