110 September 2005 XMP Specification Embedding XMP Metadata in Application Files PostScript and EPS 5 Traditional PDF Metadata and XMP The discussion here is primarily about explicitly embedding XMP in PostScript and EPS to provide metadata. However, when Distiller is used the document-level metadata in the PDF file can contain information that comes from other sources than the XMP embedded in the PostScript. This is metadata that traditionally went into the PDF document information dictionary, and with the advent of XMP is replicated in the PDF’s document-level XMP. There are two other methods for putting metadata in a PostScript file so Distiller will put it in the PDF document info dictionary and also create and embed an XMP packet for that data in the PDF document. You can use: ● DSC (Document Structuring Conventions) comments. The DSC comments are processed only if DSC parsing is enabled, that is, only if the job file contains the following line: /ParseDSCCommentsForDocInfo true ● DOCINFO pdfmark command. Information on pdfmark is available from the Distiller application Help menu, under “pdfmark Guide.” If more than one of the three possible sources of metadata for the PDF file are present, then a property value in the document-level XMP is taken from the first of these sources in the PostScript used to create the PDF that contains the property: ● Explicit document-level XMP. ● Explicit document info dictionary. ● DSC comments. Because the pdfmark command is more reliable than DSC comments, many applications use it to set DocInfo properties for a PDF document. The following is an example of PostScript code, created by FrameMaker, which illustrates the use of the DOCINFO pdfmark operator: /Creator (FrameMaker 6.0) /CreationDate (D:20020214144924) /ModDate (D:20020215142701) /Author(John Doe) /Title (Processing XMP Data in EPS Files) /Subject (XMP) /Keywords (XMP, pdfmark) /DOCINFO pdfmark Distiller will place these seven properties – plus “Producer” – into the resulting PDF file in two places: the document information dictionary and document-level Metadata as an XML Packet. The Producer is the product name, e.g. “Acrobat Distiller 5.0 (Windows).” It is possible to add other Key/Value pairs to PDF DocInfo, but they are not added to the document- level Metadata in Distiller 5.0. Care must be taken if the file might be sent to a PostScript interpreter instead of to Distiller. Some PostScript interpreters may not recognize the pdfmark command, e.g. those in older printers. One way to avoid problems is to conditionally define the pdfmark operator to the “cleartomark” operator. This is shown in the earlier examples.