It is theoretically possible to merge font subsets, sometimes. It's just Very Hard, which is why iText doesn't do it.
Merging subsets with custom encodings can involve altering the content streams using those fonts... not impossible, just Very Hard. --Mark Storer Senior Software Engineer Cardiff.com #include <disclaimer> typedef std::Disclaimer<Cardiff> DisCard; > -----Original Message----- > From: Paulo Soares [mailto:[email protected]] > Sent: Wednesday, October 07, 2009 2:37 AM > To: Post all your questions about iText here > Subject: Re: [iText-questions] PdfSmartCopy not reusing a > font resource > > > I suspect that the fonts are subset and in that case can't be reused. > > Paulo > > > -----Original Message----- > > From: Jeff Mericle [mailto:[email protected]] > > Sent: Tuesday, October 06, 2009 6:35 PM > > To: [email protected] > > Subject: [iText-questions] PdfSmartCopy not reusing a font resource > > > > Hi, > > > > I am using version 2.1.7 to concatenate many source documents > > into one. I use PdfStamper to reduce each source page, as > > well as applying a header image and a running page count. I > > copy the results from each PdfStampter operation to the final > > document. When I first began adding images, the file size > > grew large, which I presumed was due to the image being > > inserted once per page. I switched to PdfSmartCopy and the > > file size was reduced considerably. However, once I added > > page numbering, the file size began growing larger than > > expected. Examining the file, I saw that my true type font > > was being embedded once per source document, which indicates > > to me that PdfSmartCopy is not reusing this font resource as > > implied in the JavaDoc. My goal is to have the true type > > font embedded, but only once, since I learned from iText in > > Action that it is best to embed true type fonts. Should > > PdfSmartCopy only include one entry for the font in the final > > document? > > > > Thanks for your help, > > > > Jeff > > > > > > 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. > > > > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ 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/
