|
|
PDF Generator ES converts native file formats by invoking the application associated with the file format and then interacting with the application to print the document using the default printer. The default printer must have been set up as the Adobe PDF printer.This illustration shows the components and drivers involved with native application support. It also mentions the XML grammars that influence the interactions. These grammars are described in The following table lists the type of information used in printing native file formats..This document uses the term native application to indicate the application used to produce a native file format, such as Microsoft Word or Visio.AppMon is an enterprise component that interacts with a native application in the same way a user would navigate through the dialog boxes presented by that application. For example, the XML grammars used by AppMon to instruct an application such as Microsoft Word to open and print a file would involve the following sequential tasks:
Information type Modifying/creating entries related to native files Administrative settings Includes PDF settings, security settings, and file type settings.File type settings associate file name extensions with the corresponding native applications. File type settings also specify native application settings used to print native files. To change settings for an already supported native application, the system administrator sets the File Type Settings in the LiveCycle Administration Console.To add support for a new native file format, you must manually edit the file as described in Adding or modifying support for a native file format. Specifies interactions between PDF Generator ES and a native application. Such interactions usually direct the application to print a file to the Adobe PDF driver.The script contains discrete instructions that direct the native application to open specific dialog boxes and that supply specific responses to fields and buttons in those dialog boxes. PDF Generator ES includes script files for all supported native applications. You can modify these files using an XML editing application.To add support for a new native application, you must create a new script file, as described in Creating or modifying an additional dialog box XML file for a native application. Generic dialog box instructions Specifies how to respond to dialog boxes that are common to multiple applications. Such dialog boxes are generated by operating systems, helper applications (such as PDFMaker), and drivers.The file that contains this information is appmon.global.en_US.xml. Application-
specific dialog box instructions Specifies how to respond to application-specific dialog boxes.The file that contains this information is appmon.[appname].dialog.[locale].xml
(for example, appmon.word.en_US.xml). To add dialog box instructions for a new native application, create an appmon.[appname].addition.[locale]
.xml file for it (see below). Additional application-
specific dialog box instructions Specifies overrides and additions to application-specific dialog box instructions. The section presents an example of such information.The file that contains this information is appmon.[appname].addition.[locale]
.xml (for example, appmon.addition.en_
US.xml). Files of this type can be created and modified using an XML editing application, as described in Creating or modifying an additional dialog box XML file for a native application.Important: You must create additional application-specific dialog box instructions for each native application your server will support.
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/generatePdfPDFG_DG_AppMon.65.2.html