Event |
The category of conversion events
See ConversionEvent for more information on conversion events.public enum EventCategory
Member name | Value | Description |
---|---|---|
VisualDifferences | 1 | The conversion resulted in visual differences to the document. The conversion is optimized to preserve the visual appearance of documents. However, under some circumstances visual differences cannot be avoided. This is typically the case for low quality and erroneous input documents. Examples:
Suggested severity: Warning It is not possible for the SDK to gauge the effect of the visual differences on the document's content. Therefore, it is recommended to let a user assess, whether or not the conversion result is acceptable. If a manual review is not feasible, events of this category should be classified as an Error. |
RepairedCorruption | 2 | Repaired a corrupt document. Corrupt documents are repaired automatically. Since the specification does not define how corrupt documents should be repaired, each viewer has its own heuristics for doing so. Therefore, the repaired document might have visual differences to the input document in your viewer. For that reason, an event is generated such that the repaired document can be reviewed, similarly to VisualDifferences. Examples for documents that must be repaired:
Suggested severity: Warning |
ManagedColors | 4 | Managed colors of input document. Purely informational messages related to color management. Examples:
Suggested severity: Information |
ChangedColorant | 8 | Resolved ambiguous or conflicting descriptions of colorants (spot colors). Colorants are special inks used in addition to the process colors (e.g. red, green, and blue in the RGB color space or cyan, magenta, yellow and black in the CMYK color space). Popular colorants are PANTONE colors typically used in printing; or also metallic or fluorescent inks. Colorants in PDF documents contain a description that is required to paint a good approximation of the intended color in case the colorant is unavailable. Within the same document all descriptions for the same colorant should be equal. This warning is generated if conflicting descriptions must be harmonized, for example during PDF/A conversion. This has no effect on output devices where the colorant is available, e.g. on certain printers. For other output devices this warning may indicate visual differences. However, for well-formed documents (i.e. not maliciously created documents), the visual differences are not noticeable. Suggested severity: Information |
RemovedExternalContent | 16 | Removed references to external content. Examples:
Suggested severity: Information |
ConvertedFont | 32 | Converted fonts of input document. Purely informational messages related to font management. Examples:
Suggested severity: Information |
SubstitutedFont | 64 | Substituted a font for a similar one. If a required font is not embedded and not available in the installed fonts, a similar font must be chosen and used. This is a commonly performed when viewing or printing a PDF document. While this may lead to minor visual differences, all text is preserved. It is important that the installed fonts contain all fonts that are not embedded in the input documents. See the product's installation documentation for a list of fonts that are recommended to install. Examples:
Suggested severity: Information |
RemovedTransparency | 128 | Converted transparent object to opaque. Because transparency is not allowed in PDF/A-1, transparent objects have to be converted to opaque when converting a document to PDF/A-1. This can lead to visual differences. Even though the conversion has been optimized to reduce visual differences, they might be noticeable. Therefore, it is highly recommended to convert documents to PDF/A-2 or higher. These versions of the standard allow transparency, which results in a higher conversion quality. This conversion event should be handled similarly to VisualDifferences. Suggested severity: Warning |
RemovedAnnotation | 256 | Removed prohibited annotation type. Removing annotations does not lead to visual differences, but merely removes the interactivity of the elements. Examples:
Suggested severity: Information |
RemovedMultimedia | 512 | Removed multimedia content (sound, movie). Suggested severity: Information |
RemovedAction | 1,024 | Removed prohibited action type. Removing actions does not lead to visual differences. Examples:
Suggested severity: Information |
RemovedMetadata | 2,048 | Removed parts of the XMP metadata that could not be repaired. This event indicates that metadata properties have been removed during conversion. This includes any kind of metadata like e.g. the XMP metadata of a PDF document. Examples:
Suggested severity: Information |
RemovedStructure | 4,096 | Removed logical structure (tagging) information. The logical structure of the document is a description of the content of its pages. This description has to be provided by the creator of the document. It consists of a fine granular hierarchical tagging that distinguishes between the actual content and artifacts (such as page numbers, layout artifacts, etc.). The tagging provides a meaningful description, for example "This is a header", "This color image shows a small sailing boat at sunset", etc. This information can be used e.g. to read the document to the visually impaired. The SDK has been optimized to preserve tagging information. Typically, tagging information only has to be removed if it is invalid or corrupt. Suggested severity: Information |
RemovedOptionalContent | 8,192 | Removed optional content groups (layers). Because optional content is not allowed in PDF/A-1, it has to be removed when converting a document to PDF/A-1. Removing layers does not change the initial appearance of pages. However, the visibility of content cannot be changed anymore. Therefore, it is highly recommended to convert documents to PDF/A-2 or higher. These versions of the standard allow optional content, which results in a higher conversion quality. Suggested severity: Warning |
ConvertedEmbeddedFile | 16,384 | Converted embedded file. Purely informational messages related to the conversion of embedded files. Examples:
Suggested severity: Information |
RemovedEmbeddedFile | 32,768 | Removed embedded files. Whether embedded files have to be removed depends on the conformance:
Suggested severity: Warning |
RemovedSignature | 65,536 | Removed signatures of signed input file. Converting a signed document invalidates its signatures. For that reason, the cryptographic parts of the signatures are removed while their visual appearances are preserved. Note that we generally recommend to sign PDF/A documents only for two reasons. First, this ensures that the file is not corrupt and its visual appearance is well defined, such than it can be reproduced flawlessly and authentically in any environment. Second, PDF/A conformance is typically required if the file is to be archived, e.g. by the recipient. Because signed files cannot be converted to PDF/A without breaking the signature, the signature must be removed before the file can be archived. By converting files to PDF/A before applying the signature, this dilemma can be avoided. Suggested severity: Information |