Click or drag to resize
Pdftools logo

EventCategory Enumeration

The category of conversion events

See ConversionEvent for more information on conversion events.

Namespace: PdfTools.PdfA.Conversion
Assembly: PdfTools (in PdfTools.dll) Version: 1.6.0+e1db8f4bf6125495a2d29513486ea3e61205c81b
Syntax
C#
public enum EventCategory
Members
Member nameValueDescription
VisualDifferences1

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:

  • The visual appearance of a proprietary annotation type could not be generated.
  • Numbers that exceed the allowed value range have been clipped.
  • Text of an invalid font is unclear because its mapping to glyphs is ambiguous.

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.

RepairedCorruption2

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:

  • The document has been damaged, e.g. during an incomplete file upload.
  • The document has been created by an erroneous application.

Suggested severity: Warning

ManagedColors4

Managed colors of input document.

Purely informational messages related to color management.

Examples:

  • Copied PDF/A output intent from input file.
  • Embedded ICC color profile.

Suggested severity: Information

ChangedColorant8

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

RemovedExternalContent16

Removed references to external content.

Examples:

  • Removed references to external files containing stream data used in the document.

Suggested severity: Information

ConvertedFont32

Converted fonts of input document.

Purely informational messages related to font management.

Examples:

  • Embedded a font.

Suggested severity: Information

SubstitutedFont64

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:

  • Substituted font 'GothicBBB-Medium' with 'MS-Gothic'.

Suggested severity: Information

RemovedTransparency128

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

RemovedAnnotation256

Removed prohibited annotation type.

Removing annotations does not lead to visual differences, but merely removes the interactivity of the elements.

Examples:

  • Removed proprietary annotation types.
  • Removed forbidden annotation types, e.g. 3D.

Suggested severity: Information

RemovedMultimedia512

Removed multimedia content (sound, movie).

Suggested severity: Information

RemovedAction1,024

Removed prohibited action type.

Removing actions does not lead to visual differences.

Examples:

  • Removed JavaScript actions in interactive form fields.

Suggested severity: Information

RemovedMetadata2,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:

  • Parts of the XMP metadata of a PDF did not conform to the PDF/A standard and had to be removed.

Suggested severity: Information

RemovedStructure4,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

RemovedOptionalContent8,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

ConvertedEmbeddedFile16,384

Converted embedded file.

Purely informational messages related to the conversion of embedded files.

Examples:

  • Copied an embedded file.
  • Embedded a file that has successfully been converted to PDF/A.

Suggested severity: Information

RemovedEmbeddedFile32,768

Removed embedded files.

Whether embedded files have to be removed depends on the conformance:

  • PDF/A-1: Embedded files are not allowed.

    All embedded files have to be removed.

  • PDF/A-2: Only embedded files are allowed, that conform to PDF/A.

    All embedded PDF documents are converted to PDF/A. All other files have to be removed.

    The Conversion Service can be used to convert PDF documents with other types of embedded files, e.g. Microsoft Office documents, images, and mails, to PDF/A-2.

  • PDF/A-3: All types of embedded files are allowed and copied as-is.

    The Conversion Service can be used, if a more fine-grained control over the conversion and copying of embedded files is required.

Suggested severity: Warning

RemovedSignature65,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

See Also