DynaPDF Manual - Page 703

Previous Page 702   Index   Next Page 704

Function Reference
Page 703 of 770
Flag
Description
mfNoClippingRgn
If set, clipping regions will be ignored.
mfNoFontEmbedding
If set, fonts used by an EMF file are not embedded.
mfNoImages
If set, image records are ignored.
mfNoStdPatterns
If set, standard hatch patterns are not applied.
mfNoBmpPatterns
If set, bitmap patterns are ignored.
mfNoText
If set, text records are ignored.
mfUseUnicode
If set, the character set within CreateFont() records will be ignored and
all strings are printed in Unicode mode (EMF files contain Unicode
strings only). This flag can be used to avoid the conversion of strings
to the Ansi character set if Ansi_CHARSET was used in the
CreateFont() record. The character set is often wrongly defined in EMF
files so that characters outside of the Ansi_CHARSET are replaced by
question marks due to the default conversion to Ansi if the character
set Ansi_CHARSET is used.
mfUseTextScaling
If set, strings are scaled instead of applying kerning space to get the
correct string width. Text scaling produces often better results due to
limited precision of the integer values of the intercharacter spacing
array. However, text scaling cannot always be used because characters
can be placed individually on the x-axis by applying kerning space. In
the latter case, strings can overlap or single characters appear on a
wrong x-coordinate; do not set this flag in this case.
mfNoUnicode
If set, all strings are converted to the code page 1252 and no Unicode
font will be embedded in the PDF file during EMF conversion. This
flag should be set if PDF-1.2 compatibility is recommended because
PDF-1.2 does not support Unicode fonts. However, note that you get
invalid results if the EMF file contains characters outside the code
page 1252.
mfFullScale
If set, all coordinates are scaled to the output window size. Set this
flag if the EMF file uses 32 bit coordinates, e.g. large CAD drawings.
Full scaling avoids floating point overflows in PDF viewer
applications because all coordinate transformations are already
applied. The resulting file size is also smaller due to the smaller
coordinate values which must be stored in the PDF file.
 

Previous topic: SetMaxFieldLen, SetMetaConvFlags

Next topic: SetMetadata