datalogics_interface

An action can involve moving the reader to a new page in the file, for example. Also, with a PDF Viewer a PDF file can have an Action that runs automatically when a user opens the file, or reaches a specific page. Applications can support Actions in custom annotation types they add. Only GoTo and URI Actions are supported; you can only use an Action with the interface to move from one part of a file to another or open an external web page.

A go-to action includes a hyperlink that, when clicked, takes the reader to a different place within the same document. The action is linked to a bookmark within the document. A remote go-to action includes a hyperlink that takes the reader to a destination in a separate document.

A launch action launches an application or opens or prints a document.

The action associated with this object, when selected, opens a separate PDF file, or opens a web page in a browser window.

A Uniform Resource Identifier (URI) is a text string that identifies a resource on the Internet, typically a hyperlink to a web page. A URI Action within a PDF file allows a reader to click on a hyperlink and open a separate web page or another PDF or other kind of file accessed through a web link.

An annotation associates an object such as a note, sound, or movie with a location on a page of a PDF document, or provides a way to interact with the user by means of the mouse and keyboard.

The circle is inscribed within the annotation rectangle. Despite the circle name, the width and height of the annotation rectangle need not be equal. So the circle can actually be an ellipse.

An ordinary text annotation appears in a pop up window, and is attached to an icon; it represents a note added to a PDF file, and can be opened for viewing, or closed. But a free text annotation always appears open on the page. A free text annotation can be included anywhere in a PDF file by specifying the location and the CallOutLine points.

The annotated text is still readable on the PDF, but highlighted in yellow.

Ink annotations in a PDF file allow a user to work with a PDF document displayed on a screen just as if it were on paper, such as scribbling notes in the margins, or circling or underlining text. These types of annotations require a stylus or pen used on a tablet device.

When opened it displays a pop-up window containing the text of an associated note, placed at specific x/y coordinates for starting and ending points of the line.

A link annotation, which features an embedded hyperlink.

A polyline is also called a polygonal chain or piecewise linear curve. It represents a finite number of line segments where the first and last vertex are not connected. In this case, the polyline is added as an annotation to a PDF file.

In this case the polygon is created as an annotation added to a PDF file.

A redaction occludes some part of a document.

Text associated with the Square Annotation appears in a pop-up window. The size and shape of the rectangle is defined within the Rect entry.

Text markup annotations appear as highlights, underlines, or strikeouts when added to a PDF document in a PDF Viewer. When the edited PDF file is opened the markups appear in a pop-up window containing the text of the associated note.

Text markup annotations added to a PDF file appear as highlights, underlines, or strikeouts. The Underline Annotation appears PDF document as underlined text when the documnent is opened in a PDF Viewer.

An axial shading specifies a color blend that varies along a linear axis between two endpoints, and indefinitely perpendicular to that axis.

A tiling pattern consists of a repeating graphical figure that is replicated across an area to be filled in, or painted. A shading pattern provides smoothly varying gradients of color, to produce a transition between colors across an area.

A shading pattern consists of a smoothly varying gradient between two colors.

The Graphics State is an internal data structure in a PDF file that holds the parameters that describe graphics within that file. These parameters define how individual graphics are presented on the page, including layers and transparencies. The Extended Graphic State was introduced to expand the original Graphics State data structure, providing space to define and store more data objects within a PDF.

The graphics state holds the parameters that describe graphics within that file. These parameters define how individual graphics are presented on the page, including layers and transparencies.

Each bookmark has a title that appears on screen, and an action that specifies what happens when a user clicks on the bookmark. The typical action for a user-created bookmark is to move to another location in the current document, although any action (see Action) can be specified.

A destination describes a place in the PDF document where the user will be taken in response to clicking a hyperlink. The destination defines where a bookmark or hyperlink points to. The ViewDestination contains a reference to a page, a place (rectangle) on that page, and information specifying how to adjust the view to fit the window's size and shape.

A CalGray color space is a special case of a single-component CIE-based color space, known as a CIE-based A color space. This type of space is the one-dimensional (and usually achromatic) analog of CIE-based ABC spaces.

A CalRGB color space (Red, Green, Blue) is a CIE-based ABC color space with only one transformation stage instead of two. In this type of space, A, B, and C represent calibrated red, green, and blue color values. These three color components must be in the range 0.0 to 1.0; component values falling outside that range are adjusted to the nearest valid value without error indication.

The values that are offered range from 0 to 1.0 for red, green, and blue (RGB) or cyan, magenta, yellow, and black (CYMK).

Base class for all color spaces.

DeviceN color spaces were designed to represent color spaces containing multiple color components that correspond to the colorants of some target device. They provide greater flexibility than is possible with standard device color spaces such as DeviceCMYK or with individual Separation color spaces. For example, it is possible to create a DeviceN color space consisting of only the cyan, magenta, and yellow color components, with the black component excluded.

The International Color Consortium (ICC) developed the ICC color space in 1993 to serve as a universal standard for for printing or presenting content with digital devices, and across all operating systems and platforms. The ICC color standard applies regardless the hardware or software involved, and is used to make sure that color images and text appear properly on a wide variety of platforms.

Indexed color spaces are used when a limited number of colors are needed. Commonly, an image with an indexed color space can be one third the size of the same image with a standard color space, because the indexed image uses a smaller palette of colors.

In this type of space, A, B, and C represent the L*, a*, and b* components of a CIE 1976 L*a*b* space. The range of the first (L*) component is always 0 to 100; the ranges of the second and third (a* and b*) components are defined by the Range.

Class used to define the color space in use.

Colorants in a separation color space are also sometimes referred to as spot colorants. The device displaying or printing the PDF document will supply an appropriate color based on the colorant included in the separation color space.

The clipping path clips out part of the design. A clip can also be used with text. The clipping path defines an area within a page (text or graphic) that will be highlighted or removed. For example, a clipping path could be used to remove the background in a photograph, to highlight a person or object in front, or to super-impose text over an image. Only part of the image appears through a shape created with the clipping path. The Clip class is made up of a list of path and text elements. Any element can have a clip associated with it, and clip objects can hold arbitrary levels of nested container and group objects. If a group object is inside a clip object, and the clip object also contains at least one text object and no path objects, the group object has a special meaning. All text objects contained in a group object like this are considered to be part of the same BT/ET block. This means that the union of these text objects makes up a single clipping path. The text objects do not intersect.

In the PDF file, every container has a set of Marked Content tags, starting with Begin Marked Content (BMC or BDC) and ending with End Marked Content (EMC), so each container has a BMC/EMC or BDC/EMC pair of tags. These tags can be used to define the beginning and end of metadata around objects, providing information about the text and shapes within a PDF file. Containers can be nested within other containers.

A content object represents a collection of elements that make up a page in a PDF file. A content object is more convenient to use than directly parsing or working with a page content stream. This is because a page can include a large collection of individual stream objects. Working with a content object, you can avoid focusing on this level of detail. The content converts individual stream items to a structured form, making it unnecessary to parse the individual syntax for each one. A content object can be associated with a large amount of unmanaged memory in APDFL and should be deleted when the object is no longer in use. The index associated with Content is 0-based, so 0 is the first element.

An element is a building block; everything in a PDF file is an element. An element object can be associated with a large amount of unmanaged memory in APDFL and should be deleted when the object is no longer in use.

This is not to be confused with a PDF fillable form; a Form XObject is an object outside the page content stream. A form XObject is a way to group a number of PDF objects together, into a single container. A Form XObject can hold both text and images, and can be defined once within a PDF file and then reused multiple times in the same PDF, and across multiple pages.

A Group represents objects in a content object, but it resides in memory. Therefore the group has no state and is not represented in any way in a PDF content stream. When used in a Clip, a group is used to associate Text objects into a single clipping object.

A path is a series of commands that define the boundary of a vector shape. The ClosePath command draws a line from the current location back to its starting point, effectively closing a box or parabolic shape on a page.

The curved segment is appended to a path. The curveto operator calculates the curve between two endpoints, the current (beginning) point and the final (end) point, and in relation to two matching control points. The control points define the nature of the curve between the two endpoints. These values are represented by a series of x and y coordinates.

The current point is the beginning point in the curve. The name CurveToV is drawn from the "V" path construction operator.

Here the new current point is the end point in the curve. The name CurveToY is drawn from the "Y" path construction operator.

A lineto operator creates a line path element. It draws a straight line from the current position (MoveTo) to a new position-a new set of (x,y) coordinates: MoveTo{x:0 y:50} LineTo{x:100 y:100}

A LineTo operator creates an addition to a path element by moving to the (x,y) coordinates specified in the MoveTo statement. The MoveTo coordinates serve as the new current position, and from here a new path element can start. For example, the MoveTo coordinates can define the starting position for a LineTo operator. The LineTo operator draws a straight line from the current position (MoveTo) to a new position, the set of (x,y) coordinates defined with the LineTo operator: MoveTo{x:0 y:50} LineTo{x:100 y:100}

Paths in PDF files are used to draw lines, define filled areas, and define boundaries for clipping graphics. A path is composed of straight and curved line segments.

RectSegment represents a single path, or line, within a rectangle, with coordinates xy, xy for the beginning and end of the line.

Represents a segment, or a single line, within a path.

The class illustrates how to process a collection's schema. It also describes sorting of a portfolio.

Provides for adding/removing/retrieving schema fields in a collection.

Parameters that are part of a schema's field may be set.

Collections are aslo known as portfolios.

Class that defines color conversion actions for an object described by certain attributes.

Holds parameters to be passed to a color convert method. This includes the actions to take in case of a match. Each object is compared against the selection criteria for each of the actions, in order, until a matching action is found.

This class contains methods used to convert sets of values from one Colorspace to another.

A class used to extract words from a document using a regular expression.

A phrase matching a regular expression, with location information.

Bounding box quad information for a character match, including page number.

Use document objects to perform most of the functions related to pages in a PDF file, such as deleting pages, inserting blank pages, copying watermarks, creating bookmarks and thumbnails, and so on. Threading: single-thread use. A <code>Document</code> is bound to the <code>Library</code> active on the thread where it was constructed. Do not share <code>Document</code> instances across threads. See <code>datalogics_interface.hpp</code> for the full threading model.

A class representing a Rolled back instance of a PDF document that was previously saved Incrementally.

This is used for rendering PDF pages to images, such as PNG or JPG files, to export to separate files or to send to a printer.

Encoding is the process that transforms a set of Unicode characters into a series of bytes. With PDF files, Unicode values are used to represent individual character within a font set. Unicode assigns a symbolic value to represent every single character in a wide variety of fonts, scripts, and languages. For example, the Unicode value "U+0041" refers to the capital letter "A" in a Latin script. The EncodingInfo Class is used to provide basic information about an encoding. For example, EncodingInfo could be used to provide just the code name and description for a Unicode standard font or language encoding, like this: IBM860 (Portuguese, DOS) ibm861 (Icelandic, DOS) DOS-862 (Hebrew, DOS) IBM863 (French Canadian, DOS) IBM864 (Arabic, 864) iso-8859-9 (Turkish, ISO) iso-8859-13 (Estonian, ISO) (c)2007 Datalogics Inc. Datalogics is a registered trademark of Datalogics Incorporated. Other company and brand, product and service names are for identification purposes only and may be trademarks or registered trademarks of their respective holders. Data is subject to change without notice.

The Font class represents a font installed on the system.

For an Exponential Function, the curve between the two values is determined by the exponent N.

A function takes input values and manipulates them to create output values.

A function represented as a stream containing code written in a small subset of the PostScript language.

The class allows to create attachment and manipulate by its content.

The PDF file system is known more commonly as the file path name. The reference can be either absolute, as in a complete path name, or relative to the current place in a directory structure.

Class that represents control parameters for flattening transparencies within a PDF file. PDF files can hold objects that are stacked, and that are partially or fully transparent. This means that these objects can blend in various ways with objects behind them. With a stacked set of transparent graphics or images in a PDF file, each one contributing to the final result that appears on the page. One or more graphics images presented together in a stack is referred to as a transparency group. With a stack of transparent images, the final colors shown are the result of blending the colors of all of the overlapping objects. Flatten Transparency merges a stack of transparent objects or graphics into a single image on the PDF page. Flattening images in a PDF file is generally necessary before you can send the document to a printer. The flattening process simplifies the PDF file and may make it smaller as well.

An Image Xobject is stored separately from the graphics content stream in a PDF, and so can be used multiple times in the document, even across pages. The image is described in the /Xobject entry in the resources dictionary on the PDF page. Image size and resoultion: For images that are imported from raster image files, the design width and height are stored in the Image object's Matrix, in the A (width) and D (depth) Matrix members, when the image is imported. These are stored in PDF units. To derive the effective resolution of an image imported from a raster image file: Horizontal resolution: divide the Image Width by the Image's Matrix A member and multiply by 72 to scale to DPI (dots per inch). Vertical resolution: divide the Image Height by the Image's Matrix D member and multiply by 72 to scale to DPI (dots per inch).

The full set of images in the collection can be saved to a single image file, but only as a .tif image file. For any other file type (JPG, PNG, and so on), the collection can only be saved as one image object per file.

A class representing the decompressed Image Data.

The parameters include the file type (such as PNG or JPG), compression, image quality, and gray scale.

The Page Image Parameters are a set of parameters used to control converting a PDF page to an image, such as a PNG, JPG, or BMP. The parameters include pixel height & width, color space, resolution, so on.

The ink object represents the color in the color space, CYMK or RGB.

A Library object can be used to create a new instance of a library or change the properties of an existing library. Threading: per-thread. Each thread that touches the SDK must construct its own <code>Library</code> before creating any <code>Document</code>, <code>Page</code>, or <code>PDFObject</code>, and that <code>Library</code> must outlive every object it backs. Do not share a <code>Library</code> instance across threads. See <code>datalogics_interface.hpp</code> for the full threading model.

The messages include the date and time, the source of the error, and the error type: debug, info, warning, error, or fatal. This class also defines the log file name and path.

A name tree is a type of dictionary that can store many more pairs of matched records than a standard object dictionary. A name tree uses keys that are character strings to map to data objects. The strings can use a standard coding format, such as Unicode, are sorted in order in the data structure, and can be associated with any type of object.

The number tree is a type of dictionary that can store many more pairs of matched records than a standard object dictionary. A number tree uses keys that are integers to map to data objects, sorted in ascending numerical order.

Represents an OCR Engine and its configuration. Create an OCREngine object once, and reuse it to convert multiple images to Form objects to avoid repeating the sometimes expensive initialization of the engine. The configuration of the engine can't be changed after it's created; if you need to do that, create another OCREngine object.

Parameters for configuring the OCR engine. OCRParams controls settings such as the engine to use, the resolution of the input images, the language(s) to recognize, performance tuning, page segmentation mode, candidate font names for placing text, and image preprocessing options.

Thrown when a user-supplied progress callback returns false to cancel a long-running operation. Distinct from WebConvertError so that non-coupling catch handlers can quietly handle cancellation without also being aware of the web-conversion subsystem.

Use the PDFOptimizer object to accumulate options for the Optimization, and to Optimize documents.

The Optional Content Configuration Structure is used to maintain a set of visibility states and other optional values related to layers, or Optional Content Groups, within a PDF file. These configuration values are stored for future use. The default configuration for a PDF document is stored in the D entry in the Optional Content Properties dictionary. An Optional Content Group, or layer, is a set of graphic images that can be made visible or invisible within a PDF file, and the Optional Content Configuration Structure is typically used to set the initial value for these images-On or Off, visible or invisible.

An Optional Content Context is a status object that defines the context for optional content within a document. The context tracks the On/Off status for Optional Content Groups (layers) within a document. It contains flags that control whether to display content that is marked as optional.

An Optional Content Group is a dictionary that represents a set of graphics images that users can turn on or off in a PDF document, making them visible or invisible. In a PDF Viewer, Optional Content Groups are referred to as "Layers."

Form, container, and annotation objects can be associated with one or more optional content groups. By associating them with an optional content group, they become part of that 'layer', and the user can control the visibility of the content. Note that by placing other element objects in a container, they can also be associated with an optional content group. An OptionalContentMembershipDict connects content to the OptionalContentGroup; it contains a list of OptionalContentGroups, and rules for determining visibility when the OptionalContentGroups have conflicting on/off states in the active OptionalContentContext. An OptionalContentMembershipDict cannot be changed once created; you must create a new OptionalContentMembershipDict and change the objects to point to it.

Items in the Order array can be arranged into a tree structure; subarrays within the parent array form 'branches' of the tree. Each OptionalContentOrderArray may contain OptionalContentOrderLeafs or OptionalContentOrderArrays in a specific order; this order determines how they will appear in the 'Layers' control of the viewer. By placing OptionalContentOrderArrays into a higher-level array, branches can be added to the tree. The 'Title' property is a string that will appear next to the expand/collapse branch control in a PDF Viewer 'Layers' panel.

Items in the Order array can be arranged into a tree structure. Each 'leaf' on this tree would be an OptionalContentOrderLeaf that contains a reference to an OptionalContentGroup in this document.

Items in the OptionalContentConfig's Order array are either OptionalContentOrderLeaf or OptionalContentOrderArray. This is the base class for both; you cannot instantiate an OptionalContentOrderNode, only one of its child classes.

The page is the basic object used for organizing content in a PDF document. Threading: single-thread use. A <code>Page</code> is bound to its owning <code>Document</code>'s thread; do not share it across threads. See <code>datalogics_interface.hpp</code> for the full threading model. Lifetime: a <code>Page</code> must not outlive the <code>Document</code> that produced it.

PageLabel describes how to construct a label string for a range of pages. It contains information on number style, any prefixes, and a starting position within the document. Note that a single PageLabel describes the label string for several pages all pages up until the first page covered by the next PageLabel, or the end of the document. Also note that if a Document has any PageLabels, there must be one that starts at page index 0. This will be automatically created if the user does not supply one.

These parameters control how a Document is converted to the PDF/A standard. RemoveAllAnnotations if true, will remove all Annotations and Actions from the output IgnoreFontErrors if true, will try to rasterize the page when fonts cannot be embedded AbortIfXFAIsPresent if true, will abort conversion process if XFA form entry is detected NoValidationErrors if true, will ignore validation errors RasterizationResolution rasterization resolution; if 0, use 72 DPI ValidateImplementationLimitsOfDocument Validate PDF Implementation Limits of the Document. PDF/A is an ISO-standard version the PDF format. It is designed to be used with PDF files that need to be archived and stored for long periods. For example, the fonts in a PDF/A file are embedded in the file itself, rather than accessed through a link to a font directory on a local server.

All objects in a PDF document are built from a collection of simpler objects that represent fundamental datatypes like numbers, strings and arrays. PDFObject and its subclasses allow direct access and manipulation of these simple objects. Some subclasses represent single data elements. For example, PDFInteger represents a single integer value. Others represent a collection of PDFObjects, like PDFArray, an indexed array of data elements. A PDFArray is a heterogenous collection object that gathers other PDFObjects (including other PDFArrays) into an indexed list.

All objects in a PDF document are built from a collection of simpler objects that represent fundamental datatypes like numbers, strings and arrays. PDFObject and its subclasses allow direct access and manipulation of these simple objects. Some subclasses represent single data elements. For example, PDFBoolean represents a single boolean value. Others represent a collection of PDFObjects, such as PDFArray, an indexed array of data elements. A PDFBoolean represents a single boolean value, and may be inserted into any collection object.

All objects in a PDF document are built from a collection of simpler objects that represent fundamental datatypes like numbers, strings and arrays. PDFObject and its subclasses allow direct access and manipulation of these simple objects. Some subclasses represent single data elements, such as PDFInteger, which represents a single integer value. Other subclasses represent a collection of PDFObjects, like PDFArray, an indexed array of data elements. A PDFDict is a heterogenous collection object that maps other PDFObjects (including other PDFDicts) to PDFName objects.

All objects in a PDF document are built from a collection of simpler objects that represent fundamental datatypes like numbers, strings and arrays. PDFObject and its subclasses allow direct access and manipulation of these simple objects. Some subclasses represent single data elements. For example, PDFInteger represents a single integer value. Others represent a collection of PDFObjects, such as PDFArray, an indexed array of data elements. A PDFInteger represents a single integer value, and may be inserted into any collection object.

All objects in a PDF document are built from a collection of simpler objects that represent fundamental datatypes like numbers, strings and arrays. PDFObject and its subclasses allow direct access and manipulation of these simple objects. Some subclasses represent single data elements. For example, PDFName represents a single name value. Others represent a collection of PDFObjects, such as PDFArray, an indexed array of data elements. A PDFName represents a single indivisible name token, and may be inserted into any collection object. It may also be used as a key in a PDFDictionary.

All objects in a PDF document are built from a collection of simpler objects that represent fundamental datatypes like numbers, strings and arrays. PDFObject and its subclasses allow direct access and manipulation of these simple objects. Some subclasses represent single data elements. For example, PDFInteger represents a single integer value. Others represent a collection of PDFObjects, such as PDFArray, an indexed array of data elements. PDFObject is the superclass of these simple objects. A PDFObject cannot be directly instantiated, but any of its subclasses may. Any PDFObject may be either direct or indirect. A direct object exists within its collection object (such as a PDFArray) and can be referenced only within that collection object. An indirect object exists outside of any collection object and can be referenced by many collection objects. Threading: single-thread use. A <code>PDFObject</code> (and every subclass: <code>PDFDict</code>, <code>PDFArray</code>, <code>PDFStream</code>, <code>PDFString</code>, <code>PDFName</code>, <code>PDFInteger</code>, <code>PDFReal</code>, <code>PDFBoolean</code>) is bound to its owning <code>Document</code>'s thread. Do not share instances across threads. See <code>datalogics_interface.hpp</code> for the full threading model.

All objects in a PDF document are built from a collection of simpler objects that represent fundamental datatypes like numbers, strings and arrays. PDFObject and its subclasses allow direct access and manipulation of these simple objects. Some subclasses represent single data elements. For example, PDFReal represents a single floating point value. Others represent a collection of PDFObjects, such as PDFArray, an indexed array of data elements. A PDFReal represents a single floating point value, and may be inserted into any collection object.

All objects in a PDF document are built from a collection of simpler objects that represent fundamental datatypes like numbers, strings and arrays. PDFObject and its subclasses allow direct access and manipulation of these simple objects. Some subclasses represent single data elements (e.g. PDFInteger represents a single integer value); other subclasses represent a collection of PDFObjects (e.g. PDFArray is an indexed array of data elements). A PDFStream represents a stream of unsigned bytes, and may be inserted into any collection object. It includes a dictionary that describes how the data in the stream is encoded and other useful information about the stream. A PDFStream is always an indirect object. PDFStreams can be encoded using built-in filters. These filters include compression schemes for most popular image formats, and text encoding translators to permit safe transmission of the document over the Internet. The data in a PDFStream will be automatically encoded when it is created; the user can read either the encoded (raw) or decoded (filtered) data. PDFStreams can be used for any large collection of data that need not be read into memory all at once, including image data, multimedia data or XML markup.

A PDFString is a single data element that represents an array of unsigned bytes. It may be inserted into any collection object. PDFString may be a string of human readable text, but this is not required, and it may be stored either as characters or as hex values.

These parameters control how a Document is converted to the PDF/X standard. PDF/X is a subset of the PDF ISO standard. The purpose of PDF/X is to facilitate graphics exchange, and it therefore has a series of printing related requirements. For example, in PDF/X-1a all fonts need to be embedded and all images need to be CMYK or spot colors. PDF/X-3 accepts calibrated RGB and CIELAB colors, while retaining most of the other restrictions of PDF/X-1a.

A PostScript XObject is an XObject stream with the subtype entry of PostScript. The XObject contains a fragment of code expressed in the PostScript language. PostScript External Objects are not recommended.

Two structures provide settings for setting parameters for print jobs, PrintUserParams and PrintParams. PrintUserParams was created first, and then PrintParams was created as an extension of PrintUserParams, to provide more settings to account for changing technology. When the system seeks to print a document it will pass the content and the print parameters, such as the page size, paper tray, and landscape v. portrait, to the print API in APDFL. If the setting is in PrintParams it will pass the document and parameters to PrintParams and then to PrintUserParams and from there to the print API to complete the printing process. The print logic may take different code paths depending on whether or not the print content is being sent to a printer or to a file, or if the printing uses PostScript or not. When you see a print setting that appears in both PrintUserParams and PrintParams, such as "ShrinktoFit," set the appropriate value in both of these classes. Also, PrintParams offers a variety of settings related to PostScript, but the use of PrintParams is not limited to PostScript.

This class intentionally uses inline storage rather than the pimpl pattern because it is a trivial 3-member value type with no internal APDFL object to wrap.

Used to control how the QR code is created.

A RemoteDestination is not the same as a ViewDestination; the two objects are not interchangeable.

Holds parameters for making color separations. Used with PostScript.

Represents a plate for making print separations. Used with PostScript.

Use the SignDoc object to digitally sign a document

Owns a non-owning reference to its CDocument. Exposes type (/S) access, the backing dict (for arbitrary attribute reads/writes), child creation, and marked-content reference insertion. Threading: single-thread use. A <code>StructElement</code> is bound to its owning <code>Document</code>'s thread; do not share it across threads. See <code>datalogics_interface.hpp</code> for the full threading model. Lifetime: a <code>StructElement</code> must not outlive the <code>Document</code> that produced it.

Owns a non-owning reference to its CDocument. The underlying PDF structure tree is owned by the document; this wrapper provides C++ access to catalog- level struct tree operations (add children, access the backing dict). Root of the PDF logical structure tree. Obtained exclusively via Document::create_struct_tree_root() or Document::get_struct_tree_root(). Threading: single-thread use. A <code>StructTreeRoot</code> is bound to its owning <code>Document</code>'s thread; do not share it across threads. See <code>datalogics_interface.hpp</code> for the full threading model. Lifetime: a <code>StructTreeRoot</code> must not outlive the <code>Document</code> that produced it.

Provides access to data about fonts, font sizes, and colors used in a word.

A Text object is container that represents both a series of TextRun elements and a series of text characters. Operations can be performed on individual TextRuns within a Text or on individual characters within a Text by specifying the index of the individual TextRun or character. All indices start at 0.

@structure PDEGraphicState @structure PDETextState @structure PDETextItem All the characters contained within a text run have the same style, color, font, and size.

These parameters include character and word spacing, font, font size, and horizontal scale.

Watermark settings control the appearance of a watermark in a PDF.

Watermark settings to control the appearance of text in a text-based watermark.

Thrown by web-to-PDF conversion when the underlying plugin reports a non-cancellation failure. Carries the C-layer result code and textual detail in addition to the human-readable what() string.

Metadata about a successful web/HTML conversion. Result metadata for a completed web-to-PDF conversion: page count, conversion time, document title, and resolved source URL. Populate() reads the plugin's last-conversion record on supported platforms and is a no-op (returning false) on the stub path; the page count is then overridden by the curator bridge with the authoritative count from the opened PDF. Header has no plugin-typed surface; all conversions live in the .cpp.

Parameters controlling Document::from_web_url and Document::from_html_file. Plain value type. Safe to construct and pass by reference. On supported platforms, owns a WebToPDFParamsRec and bridges it to a pair of CWebProgressProc/CWebLogProc functors that the static C trampolines installed into the params dispatch through. On platforms where the WebToPDF plugin is not supported, the same class compiles with a stub state that mirrors the public set/get surface using primitive fields. The stub never throws from the constructor or any setter failures only surface from the Document::from_web_url / from_html_file entry points (in CDocument.cpp). This keeps configuration code platform-portable. Public signatures use plain int where the underlying plugin enum would otherwise leak through; numeric values match the plugin enums and the public api WebViewportPreset / WebPageSize / ... 1:1, so callers cast freely at either boundary.

Each word contains a sequence of characters in one or more styles (see Style).

A class used to extract words from a document.

Wraps the key fields from PDWordFinderConfigRec to configure word extraction.

The XML Paper Specification (XPS) is a standard document format that Microsoft created in 2006 as an alternative to the PDF format. The XPS format is intended to be a simple but secure file format, without embedded images or video clips, and easy to share and print. NOTE: This class is only available on Windows or Linux.

AcroForm Data Export types.

AcroForm Data Import types.

Flags that control how annotations are handled when adding a page to a Content object.

Represents the relationship between the component of the PDF document that refers to this attachment and the file denoted by the attachment

Bitfield flags controlling the display and behavior of annotations.

Specifies horizontal alignment (quadding) for text layout.

Line-ending shape for annotations whose appearance includes line endings (line, polyline, polygon, free-text callouts).

The blend mode used for painting objects.

The line cap style specifies the shape to be used at the ends of open subpaths (and dashes, if any) when they are stroked.

The line join style specifies the shape to be used at the corners of paths that are stroked. Join styles are significant only at points where consecutive segments of a path connect at an angle; segments that meet or intersect fortuitously receive no special treatment.

Constants that specify a standard ICC rendering intent for a device color profile. The rendering intent specifies the color translation method for colors that are outside the gamut of the color profile.

Flags describing the visual style of a bookmark's title text.

Runtime element type tag returned by Element::get_element_type().

Controls how the navigator and preview panes are arranged when displaying a PDF collection.

Specifies the type of navigator view used to display a PDF collection (portfolio).

Constants specifying the action to take when a color conversion match occurs.

Bit field constants specifying object attributes used for matching in color conversion actions.

Constants specifying color space types used for matching in color conversion actions.

Constants identifying standard ICC color profiles for use in color conversion.

Compression values for generating graphics files from PDF pages. A compression value must be provided for JPG or GIF images.

Enumeration to specify credential encoding format as either Non-PFX (PEM/DER) or PFX (PKCS#12).

Enumeration to specify credential is required to be retrieved from disk (OnDisk) or is cached in memory (InMemory).

Enumeration to specify cryptographic hash functions that generate variable- length message digests required for digital signature creation.

Enumeration to specify fields to display as part of signature appearance.

Used by Page.Rotation to get or set the display and print rotation of a page.

These flags can be OR'd together to control various rendering behaviors.

These flags can be OR'd together to control text, line art, and image smoothing behavior during page rendering.

Flags that control how an Element is cloned.

Flags for creating fonts.

Font descriptor flags.

Encryption types for securing a PDF document.

Enumeration for setting the compression scheme for the Flattened Color images.

Enumeration for setting the compression scheme for the Flattened Grayscale images.

Enumeration for setting the compression scheme for the Flattened Monochrome images.

Enumeration for setting the Quality setting for the JPEG or JPEG2000 images.

Specifies the visual effect used when a link annotation is activated (clicked).

Specifies the format of the raster image file to import or export.

Specifies the ink type used for trapping purposes.

Flags for initializing the library. Unless you require fine-grain control of the intialization process of the library there is no need to use LibraryFlags or you can specify the value of NoFlags.

Multiple flags can be combined using bitwise OR to send log output to more than one destination simultaneously.

Options for mirroring output in the PostScript stream.

Specifies the numbering style for page labels in a document.

The policy for drawing optional content within the document.

Languages which may be selected for OCR recognition. Languages which may be selected. To find if a language is available, call IsLanguageAvailable() on the OCREngine.

The behavior to use if a suitable Font can't be found to represent recognized text. The behavior to use if a suitable Font can't be found to represent the recognized Text.

How the OCR engine views the page and detects text segments. Specify how the OCR engine will view the page, and how it detects text segments.

Performance mode for the OCR engine, balancing speed vs accuracy. Specify the performance of the OCR engine in an abstract way. In Tesseract, for instance, this changes the OCREngineMode.

Enumerator used to select type of compression used when images are recompressed. For color or grayscale images: Flate, JPEG or JPEG2000 may be selected. For black and white images: Flate, JBIG2, CCITTG3, or CCITTG4 may be selected.

Establish the compression quality to be used in compression schemas that allow variable quality. (JPEG, JPEG2000, JBIG2). Unset should be selected for compression schemes that are inherently lossless (Flate, CCITTG3, or CCITTG4). JBIG2 may select any value. JPEG and JPEG2000 can select any value between Minimum and Maximum, but should not select Unset or Lossless.

Enumerator to allow the selection of image type to Set the values for resampling and recompression.

Enumerator to allow the selection of object compression type to Set the values for object compression type.

Select the optimization option to be set or obtained.

These values determine the default ON/OFF state applied to optional content groups when an OptionalContentConfig is used to initialize an OptionalContentContext.

A code specifying whether a color component value of 0 in a DeviceCMYK color space should erase that component or leave it unchanged when overprinting.

An enumerated data type used to describe the page view mode of a Document.

Insertion flags used by InsertPages().

Bit flags indicating which page marks are emitted for color separations.

Specifies which pages a watermark targets.

These flags control whether a path is stroked, filled, or both, and which fill rule is used.

Each value corresponds to a specific PDF/A standard (1a, 1b, 2a, 2b, 2u, 3a, 3b, 3u, 4, 4e, 4f) combined with a target color space (RGB or CMYK).

The underlying PDF data type of a PDFObject. Use with PDFObject::get_type() for switch-style dispatch instead of chained dynamic_cast.

Specifies the PDF/X standard version to convert a document to.

Permissions mask, for Save.

An enumerated data type used to describe the target operation of a permissions request.

The Error Correction Level of the QR Code.

Flags for saving documents.

The data type of a collection schema field.

Options controlling how fonts are emitted in separation output.

Specifies how a colorant is handled during a separation preview.

Digital signature field options.

Enumeration to specify fields to display as part of signature appearance.

Discriminator for the three shapes of kid entries that can live in a struct element's /K array: another struct element, a marked-content reference (inline MCID or MCR dict), or an object reference (OBJR).

Controls whether temporary files are stored on disk or in memory.

Flags that control how text operations address text within a Text object.

Rendering mode for text, corresponding to the Tr operator in a PDF content stream.

TIFF Byte Order values describing the byte order used within a file.

Specification of vertical alignment options.

Determines how content visibility is resolved when an OptionalContentMembershipDict references multiple OptionalContentGroups with conflicting on/off states.

Controls whether the watermark is rendered as an annotation or as a form XObject within the page content stream. The "Try" variants attempt the specified method but may fall back if it is not possible.

Downsampling resolution for raster images. The plugin supports only this discrete set; arbitrary DPI values are not accepted. Numeric values match the underlying <code>WebToPDFDownsamplingDPI</code> enum so a <code>static_cast</code> suffices at the bridge.

This refers to versions of the WordFinder algorithm. WordFinder extracts words from a PDF file and enumerates the words on a single page or on all of the pages in the document.

Flags returned by Word::GetAttributes.

Writing direction for text.

XFA Form Data Export types.