Yeah, I'm crafting one now....but an answer to the question would tell me if my 
test "followed suit".  Memory isn't an issue on my hardware...so I'd sacrifice 
it for speed/resulting file size....and in the end, a repeatable and well 
understood process trumps everything.

 

Jason

 

________________________________

From: Paulo Soares [mailto:[email protected]] 
Sent: Monday, March 22, 2010 1:55 PM
To: Post all your questions about iText here
Subject: Re: [iText-questions] design pattern

 

In PdfsmartCopy if the images are the same only one instance will be used but 
subset fonts won't be merged and you'll end up with an instance per file 
inserted. It will also use a lot of memory for the generation. iText does a lot 
of things but it's not particulary efficient memorywise and will always lose 
for a custom app written in C. The best way to evaluate this is to create test 
PDFs, do the process and see the result.

 

Paulo

         

        
________________________________


        From: Jason Berk [mailto:[email protected]] 
        Sent: Monday, March 22, 2010 5:30 PM
        To: Post all your questions about iText here
        Subject: Re: [iText-questions] design pattern

        I understand....in the meantime, could you answer this question:

         

        if I create one PDF and add 100,000 pages, what will it's file size be 
relative to creating 100,000 PDFs and using PdfSmartCopy to concat them 
together?  If the difference is a few KB/MB I'll go that route.  If it's 10s or 
100s of MB, I'll explore other solutions.

        I'm curious....

         

        jason

         

        
________________________________


        From: Leonard Rosenthol [mailto:[email protected]] 
        Sent: Sunday, March 21, 2010 5:15 PM
        To: Post all your questions about iText here
        Subject: Re: [iText-questions] design pattern

         

        If you're doing that type of volume - I would strongly recommend that 
you invest in commercial-grade solutions for document merging, many of which 
also support PDF optimization options.

         

        iText is a great product, but there are some things it simply doesn't 
do well - large volume document assembly is one of them (see the archives of 
the mailing list for discussions on this in the past).

         

        Leonard

         

        From: Jason Berk [mailto:[email protected]] 
        Sent: Sunday, March 21, 2010 5:06 PM
        To: Post all your questions about iText here; Post all your questions 
about iText here
        Subject: Re: [iText-questions] design pattern

         

        I think you misunderstood.  The images are TIF or PNG files.  The pages 
are NOT images.
        
        I need to create 60,000 PDFs and concatenate 30,000 of them together 
into a single "print" file.
        
        priority 1 is to avoid creating the pdf content for a given account 
twice.
        priority 2 is to create the smallest possible print file (size wise)
        
        if I create one PDF and add 100,000 pages, what will it's file size be 
relative to creating 100,000 PDFs and using PdfSmartCopy to concat them 
together?  If the difference is a few KB/MB I'll go that route.  If it's 10s or 
100s of MB, I'll explore other solutions.
        
        Thanks,
        
        Jason
        
        
        -----Original Message-----
        From: Leonard Rosenthol [mailto:[email protected]]
        Sent: Sun 3/21/2010 1:05 PM
        To: Post all your questions about iText here
        Subject: Re: [iText-questions] design pattern
        
        Why are the pages images and not real text and vector objects?  If you 
want small files, DON'T use raster images!
        
        From: Jason Berk [mailto:[email protected]]
        Sent: Sunday, March 21, 2010 12:47 PM
        To: [email protected]
        Subject: [iText-questions] design pattern
        
        
        hello all.
        
        looking for advice...
        
        my credit union has 60K members.  I need to produce a single PDF for 
each member that uses low res images (96 DPI).  This is know as the 
"E-Statement".  For about half of the members, I also need to produce a "print 
statement" version which uses 300 DPI images.  The print statement needs to be 
just one single PDF (with thousands of pages).  I would like this print file to 
be as small as possible.
        
        it is possible to
        
        1) create a statement with a button as an image place holder
        2) save that statement as a singular PDF after adding low res images to 
the buttons
        3) concat that statement to an open PDF stream after adding high res 
images to the buttons (so the pdf specific stuff isn't repeated with each 
statement)
        
        I've read this: http://1t3xt.info/examples/browse/?page=example&id=347 
which shows how to set button images and I've read about using PdfSmartCopy to 
concat PDFs, but from what I read, the PDF innards will still be repeated in my 
resulting file, eating up file size (please correct me if this is not the case)
        
        I've also thought about creating two different processes...once to 
create e versions and one to create the print file, but that seems inefficient 
as I'd be creating the (hopefully) same statement twice for basically half of 
my accounts and could potentially result in the statement looking slightly 
different between e and print versions.
        
        The end goal is for a member to get his print statement in the mail, 
and print the estatement from online banking and (basically) not be able to 
tell which is which.
        
        how would you all handle this with iText / Java?
        
        (FYI: this is a server side java process...no web container)
        
        Thanks for any opinions / help.
        
        Jason

         

________________________________

Aviso Legal:
Esta mensagem é destinada exclusivamente ao destinatário. Pode conter 
informação confidencial ou legalmente protegida. A incorrecta transmissão desta 
mensagem não significa a perca de confidencialidade. Se esta mensagem for 
recebida por engano, por favor envie-a de volta para o remetente e apague-a do 
seu sistema de imediato. É proibido a qualquer pessoa que não o destinatário de 
usar, revelar ou distribuir qualquer parte desta mensagem. 

Disclaimer:
This message is destined exclusively to the intended receiver. It may contain 
confidential or legally protected information. The incorrect transmission of 
this message does not mean the loss of its confidentiality. If this message is 
received by mistake, please send it back to the sender and delete it from your 
system immediately. It is forbidden to any person who is not the intended 
receiver to use, distribute or copy any part of this message.



***This is a transmission from Purdue Employees Federal Credit
Union (PEFCU) and is intended solely for its authorized
recipient(s), and may contain information that is confidential
and or legally privileged.  If you are not an addressee, or the
employee or agent responsible for delivering it to an addressee,
you are hereby notified that any use, dissemination,
distribution, publication or copying of the information 
contained
in this email is strictly prohibited. If you have received this
transmission in error, please notify us by telephoning (765)
497-3328 or returning the email. You are then instructed to
delete the information from your computer.  Thank you for your
cooperation.***

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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/

Reply via email to