I am not 100% sure when I merge these PDF(s) together that the resulting output 
will be of the correct format (i.e. the fonts are required for the proper 
presentation - barcode fonts).

This is useful information: can I assume that the size of the barcode font 
isn't that big?

I haven't tried it yet but is it possible to remove the fonts from the 
individual PDF(s) during the copy phase and attach them at the new document 
level during the PDFSmartCopy processing.

Removing the fonts from the individual PDFs could work, but it shouldn't be 
your first choice.

Are you adding the content that requires barcode fonts with iText?
If so, you've noticed that iText will subset the font by default.
You can change this default with bf.setSubset(false); where bf is a BaseFont 
instance.

The print vendor requires that we fully embed all fonts - the barcode font is 
not big and we are embedding 9 fonts in total - all through iText

Now the files that we are concatenating together are pretty close 1GB in total 
size - and when we concatenate them together using PDFSmartCopy the resulting 
file is around 13Mb - so we are seeing a dramatic decrease in size of the 
resultant file (as expected). However, and yes I am not a PDF expert here, the 
way the fonts streams are being referenced are causing the software by the 
print vendor to believe they are unique references and not shared

This will cause the individual files to be bigger (for fonts such as Arial, 
your files will be bloated), but the composed file (the one you're creating 
with PdfSmartCopy) will be much smaller because you won't have all these small 
different subsets to deal with.

This is what I meant with: you need to give us more context if you want actual 
help.

Steve Whatmore, MBA, MCP, .NET
Software Development Manager / Architect
416.598.1241 x245
-------------------------------------------------
PureFacts Financial Solutions
372 Bay Street, Suite 1400
Toronto, Ontario M5H 2W9
416.598.1241 main
888.596.9338 toll free
416.598.9226 fax
www.purefacts.com
Please consider the environment before printing this e-mail.
This e-mail may be privileged and/or confidential, and the sender does not 
waive any related rights and obligations. Any distribution, use or copying of 
this e-mail or the information it contains by other than an intended recipient 
is unauthorized. If you received this e-mail in error, please advise me (by 
return e-mail or otherwise) immediately.
Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce 
pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation 
ou copie de ce message ou des renseignements qu'il contient par une personne 
autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce 
courrier électronique par erreur, veuillez m'en aviser immédiatement, par 
retour de courrier électronique ou par un autre moyen.



From: 1T3XT BVBA [mailto:i...@1t3xt.info]
Sent: June-09-13 6:06 AM
To: Post all your questions about iText here
Subject: Re: [iText-questions] FW: PDFSmartCopy and embedded fonts

On 8/06/2013 18:51, Steven Whatmore wrote:
I would highly prefer not to have to render the PDF twice (one with embedded 
fonts and one without) strictly for this print vendor. Even if I do render 
without the embedded fonts -

That's a bad idea in general.


I am not 100% sure when I merge these PDF(s) together that the resulting output 
will be of the correct format (i.e. the fonts are required for the proper 
presentation - barcode fonts).

This is useful information: can I assume that the size of the barcode font 
isn't that big?


I haven't tried it yet but is it possible to remove the fonts from the 
individual PDF(s) during the copy phase and attach them at the new document 
level during the PDFSmartCopy processing.

Removing the fonts from the individual PDFs could work, but it shouldn't be 
your first choice.

Are you adding the content that requires barcode fonts with iText?
If so, you've noticed that iText will subset the font by default.
You can change this default with bf.setSubset(false); where bf is a BaseFont 
instance.

This will cause the individual files to be bigger (for fonts such as Arial, 
your files will be bloated), but the composed file (the one you're creating 
with PdfSmartCopy) will be much smaller because you won't have all these small 
different subsets to deal with.

This is what I meant with: you need to give us more context if you want actual 
help.
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
iText-questions mailing list
iText-questions@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/itext-questions

iText(R) is a registered trademark of 1T3XT BVBA.
Many questions posted to this list can (and will) be answered with a reference 
to the iText book: http://www.itextpdf.com/book/
Please check the keywords list before you ask for examples: 
http://itextpdf.com/themes/keywords.php

Reply via email to