Thanks for the lively discussion. I totally agree to Leonard's comment, I have to, better must, archive the final (absolutly the same file as the print provider got used) version of the single PDF, so there is no way to produce or dispart on modules like text and font.
On the other side, the generating, mean validate the jasperreport fields and rendering the PDF happens for a data collection of more then 10-15.000 records, should work as fast as possible. So the process loads the data from the DB, validate, render the PDF, creates the file (huge PDF) and sends to the print provider. This should work as fast as possible. Later, after finishing all letter production, the splitting process starting and have enough time to finish the job (archive the single documents into the DB, referencing each record loaded before). The end-user can load the single document(invoice, letter, etc.) in a fast way and be sure seeing the final version. This is fine and is running stable since few years. Times have changed - we are using exotic fonts, given as ttf, so we need to embed them -- requirement from the print provider. Further we won't explode the DB. Don't misunderstood me pls, won't teach you or repeat myself, but the system and the process is given, running stable. So we are searching for the "best complement solution", without extremly burden the budget. Zoltan > My only comment would be that in most cases, there are laws/regulations > that require that the "exact document" that was presented/distributed is > what goes into the archive. In such a case, it wouldn't be possible to > archive "parts"... > > Leonard > > -----Original Message----- > From: Mike Marchywka [mailto:[email protected]] > Sent: Thursday, January 07, 2010 12:44 PM > To: [email protected] > Subject: Re: [iText-questions] Embedding subset of fonts > > > > > > > > > > ________________________________ >> Date: Thu, 7 Jan 2010 17:38:05 +0100 >> From: [email protected] >> To: [email protected] >> Subject: Re: [iText-questions] Embedding subset of fonts >> >> >> >> >> >> >> >> >> >> Hi, >> >> >> >> I can't agree that. >> >> Just to show you the difference between huge single PDF and broken down >> single PDF-s, have a look pls at the following table: >> >> >> >> embedded subset Huge PDF(kB) Pages Single PDF (averaged in >> kB) >> >> ------------------------------------------------------------------------ >> >> yes 130 61 >> 27 >> >> yes 2147 1184 >> 29 >> >> >> >> no 633 253 >> 6 >> >> no 14202 7577 >> 4 >> >> >> >> The single PDF is a lot of bigger, a factor of 5-6 of multiplication. >> >> Producing ca. 4 million pages per year and archiving this (this is only >> the beginning), the diference would be more then 100GB more space, data >> transfer and so on. > > > At the risk of antagonizing Leonard and Bruno again re the resource > requirements, > I guess I'd ask why you archive PDF files and not just the pieces that go > into making > them which presumably are smaller, and then recreate on the fly when > needed? You wouldn't archive page images > unless you value rendering speed over size. It is easier to store a font > and input string and have a "decompression" algorithm that happens to > convert > this into a human readable image. You wouldn't have many quams about > archiving a zip file, > why not "decompose" your pdf file into input pieces (text and fonts) that > probably are much smaller and for that > matter would probably allow better indexing with your DB facilities. > Then, you > can "decompress" using itext when needed. Creating a PDF file is a great > way to "decompress" > a concise representation of anything ( just to provoke a response from Leo > LOL). > > > > > >> >> >> >> Regards, >> >> Zoltan >> >> >> >> 1T3XT info schrieb: >> >> >> Zoltan Kakucs wrote: >> >> >> >> >> Thanks again. >> Do you mean with subset fonts embedding the ttf-s or using the metrik >> files (afm) together with the postscript (pfb)? >> We are using also fonts given only as ttf. >> It's a bit shadowy for me, how the final version looks like. >> >> >> >> >> If you embed Type1 fonts (afm or pfm + pfb), iText will embed >> the complete font. (But most Type1 fonts aren't that big.) >> If you embed True Type or Open Type fonts with True Type oulines >> (ttf files), iText will automatically subset the font. >> >> Now if you create the large document with the fonts embedded, >> chances are the separate files won't be that large, because you're >> basically using an alphabet of 26 letters (times 2 for caps) and >> some interpunction. >> >> If you have a capital Z in one page, the description of this glyph >> will also be in the subsetted font of documents that don't contain >> the capital Z, but that's not a technical problem. The file will be >> a little bit bigger because of the unused Z, but is that a problem? >> >> >> >> > > _________________________________________________________________ > Hotmail: Powerful Free email with security by Microsoft. > http://clk.atdmt.com/GBL/go/196390710/direct/01/ > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > iText-questions mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/itext-questions > > Buy the iText book: http://www.1t3xt.com/docs/book.php > Check the site with examples before you ask questions: > http://www.1t3xt.info/examples/ > You can also search the keywords list: > http://1t3xt.info/tutorials/keywords/ > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > iText-questions mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/itext-questions > > Buy the iText book: http://www.1t3xt.com/docs/book.php > Check the site with examples before you ask questions: > http://www.1t3xt.info/examples/ > You can also search the keywords list: > http://1t3xt.info/tutorials/keywords/ > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.1t3xt.com/docs/book.php Check the site with examples before you ask questions: http://www.1t3xt.info/examples/ You can also search the keywords list: http://1t3xt.info/tutorials/keywords/
