-------------- Original message ---------------------- From: Dominic Maricic <[EMAIL PROTECTED]> > <snip> > Hi Bill, > > My question wasn't rhetorical. I've tried jpeg, gif, png and had issues with > all. I even had the exact same distortion when trying to add a tiff at 72 dpi. > So my question again is, when adding line art graphics via iText, what format > and dpi should I recommend to my users? >
When I developed a solution to the problem I had described earlier, i.e., "blurry logo" problem, I used a 300 dpi version of the logo. The logo was B&W, with finely spaced radial lines. 150 dpi was almost good enough. IMO, 300 dpi was adequate. Finer resolution, say 600 dpi, would have been better, at the cost of having an image that consumed 4X as much file size for the logo. > Bruno sent me an example with a logo I had at 450dpi jpg and it worked well, > at > 72dpi, the image needed to be converted to 110dpi which causes a size loss. So > I'm just trying to find out what's 'best' to use. > This is not an iText issue. iText does not change the resolution of an embedded image. That said (written), the adequacy of resolution of a raster image, when embedded in a PDF, is IMO dependent on the size to which you are scaling the image. About 10 years ago, before iText, he logo to which I referred above started out as a very high resolution PCX image, IIRC, about 24 inches square. I scaled it to about 3% of original size in an MSWord document and printed to PDF with Acrobat PDFWriter, with the downsampling set to 300 dpi. Also, IIRC, the default downsampling at the time for Acrobat PDFWriter was 72 dpi, which was part of the problem on the side of generation of the PDF. That was only half of the problem, IMO, as the previously mentioned blurring problem with Acrobat Reader rendering the PDF for screen resolution, 72 dpi (or was it 75 dpi?) at the time, still had to be solved. I put the above description here for historical context. Today, knowing what I now know about PDF and iText, I wouldn't solve the problem in the same way at all, but rather, would do everything (all of the scaling) with iText. In fact, there *is* a version of the NSSAR PDF application, the application that caused the problem 10 years ago, that is generated entirely with iText, completely eliminating the need to use Adobe Acrobat for PDF generation. Of course, Adobe Reader is still the "gold" standard for viewing and using the resulting PDF by applicants, as it is the only PDF viewer that supports the actions I had added to the AcroForm to make it submittable. Best regards, Bill Segraves ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions Do you like iText? Buy the iText book: http://www.1t3xt.com/docs/book.php Or leave a tip: https://tipit.to/itexttipjar
