Encapsulates an image which can be set either by value (and serialized in place) or reference a dictionary item and serialized by reference.

Class with the only purpose in life - serialize images.

Holds a serializable name/value collection. Each name/value is serialized as: name:type:value where type can be one of: i - int s - string (strings are base64'ed) f - float d - double ? what else?

Class used to persist page settings without printer settings. The following page settings are persisted: color, landscape, margins, paper size and name.

Provides serialization for a collection of PointF items

Serializer for PointF (can serialize as an attribute). The sequence is x,y

Serializer for RectangleF (can serialize as an attribute). The sequence is x,y,width,height

Holds float values for four sides. Also serializes as an attribute. Note that the implied sequence is top-right-bottom-left.

Contains addititional information about metafile created by the C1PrintDocument. This information are stored in the GdiComment record. Format of the record describes by the C1.C1Pdf.EMR_C1_METAFILE_INFO structure.

C1 text renderer.

Represents the line of text, each line contains several C1TextLineRange objects.

Represents the part of formatted text within line.

The array of C1TextLine objects.

Class used to persist page settings without printer settings. The following page settings are persisted: color, landscape, margins, paper size and name.

Class allowing access to Win32 GetDeviceCaps API call.

Class with no instance props or methods, providing static image handling utilities.

Class describes one entry in the document outline. Used to create outline tree nodes in the outline control. Instances of this class contain level, and thus can be stored in a flat array.

The .NET PreviewPrintController creates metafiles with gdi+ commands. This is bad for us because the format of such emf records is not documented, and so we can not e.g. search for text. But, if we just use .NET PrintController, the page generation process slows down by a factor of 2 (at least). The only way to avoid this is to inherit from PreviewPrintController but provide our own graphics, based on emf-only metafiles. Another caveat is which base methods to call and which not. Invoking base.OnStartPrint/base.OnEndPrint is necessary because if we do not do that performance is the same as with the regular PrintController (i.e. bad). OTOH, invoking base.OnStartPage/ base.OnEndPage looks like wasting time (as we can not use the provided graphics anyway) and what is more, for big documents at some point seems to drain resources and causes our creation of metailes to fail. So what is below seems to be the only combination that works. Still, the whole printing stuff in .NET is a mess. --dima.

Auxiliary class that provides an unified StringFormat content.

Base for a simple type converter to/from strings

Contains an information about text of range.

Represents an information about hyperlink in object.

This interface must be implemented by any class using (hosting) the C1Text

Describes the format of text range in C1Text.

Describes the list of text formats.

Describes variaous text directions in the C1Text object, which are depend of TextAngle. TopToBottom - TextAngle is about 0 BottomToTop - TextAngle is about 180 LeftToRight - TextAngle is about 90 RightToLeft - TextAngle is about 270