Take a survey

Developing Applications Using APIs > Assembling PDF Documents > Assembling and Disassembling PDF Documents > Understanding PDF packages > Combining a PDF package into a single PDF

Combining a PDF package into a single PDF
To convert a package to a single PDF, specify a NoPackage element. For example, suppose pkg1 contains single1a and single1b as package files, pkg2 contains single2a and single2b as Package files, and the aggregated package specification produces the package files sorted into this order: [single1a, single2a, single1b, single2b]. The pages in the resulting "newSingle" would be comprised of the cover sheets from pkg1 and pkg2, followed by pages from single1a, single2a, single1b, and single2b. The file attachments would be any document level file attachments contained in single1a, single1b, single2a, and single2b, other package files that would not assemble (they become document level file attachments), and all page-level file attachments from all six files. Note that encrypted PDF documents, dynamic XFA forms, and non-PDF documents will not assemble. The following example shows the usage of the NoPackage element in this case:
Example: Converting a package to a single PDF
<PDF result="newSingle">
	<NoPackage/>
	<PDF source="pkg1"/>
	<PDF source="pkg2"/>
</PDF>
You can also use the NoPackage element to assemble a single PDF from PDF documents. In this case, the <Package/> child of a <PDF> source element will promote a single PDF into a PDF package (the pages become the cover sheet and the document-level file attachments become package files):
Example: Assembling a single PDF from two PDF documents
<PDF result="newSingle">
	<NoPackage/>
	<PDF source="doc1">
		<Package/>
	</PDF>
	<PDF source="doc2">
		<Package/>
	</PDF>
</PDF>
 
 

 

Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/sdkHelp/assemblePDFAssembling.96.14.html