Buy Image to PDF Desktop Application Online!

WMF/EMF Control Tab

Note: Move the mouse over the screenshot below and click on an item of interest.

WMF and EMF image files are vector (or meta) image formats (which can also include bitmap images within them) that consist of a number of Windows Graphics Device Interface (GDI) drawing commands.

Many applications are able to create or export WMF and EMF files and these are a common file interchange format.

There are two ways to convert WMF and EMF files into PDF:

1. Use Windows to replay the file into an image - this reproduces the image with 100% compatibility but creates a non-scalable bitmap image (with a larger file size).
2. Convert the Windows GDI commands into their native PDF equivalent - this is faster and produces scalable output (with a much smaller file size) but cannot accurately convert all GDI elements.

	Metafile To Rendered Bitmap
Purpose:	Uses Windows to replay the meta file into an image bitmap.
Notes:	This is 100% compatible. Produces much larger file sizes and takes longer to convert than the native option. The image quality is not necessarily as good as native conversion. We recommend that native conversion is used unless you absolutely must have 100% re-production. Any text in the meta file is rendered by Windows into pixels, so the PDF is not text searchable. If you zoom in on the page - you will start to see blocky pixels - this depends on the maximum megapixel size that you have specified.

	Metafile To Rendered Bitmap: Image Max Megapixel Size
Purpose:	Specifies the meta image maximum rendering size.
Notes:	Valid values are 0.1 to 20.0 Meta image files can often be authored at very high resolutions (sometimes in excess of 10,000 units for both the width and height) and this would lead to very large converted image sizes. To combat this it is possible to set the maximum total area of the rendered image as a value in megapixels (similar to the way that digital cameras have their resolutions quoted). If a meta image file's width x height is greater than the specified number of mega pixels then it is re-sized to be within this value. It is important to note that this "re-size" is actually a meta image file rendering transformation and not a "re-size" in the strictest sense (see the Image Scaling option below). Here is a list of common mega pixel sizes and an example of an image size that just fits within this limit:    1.3    1300 x 1000 2.2 1800 x 1200 3.1 2000 x 1600 4.3 2400 x 1800 5.3 2700 x 2000 6.1 2900 x 2200 8.2 3400 x 2500 10.0 3700 x 2800

	Metafile To Rendered Bitmap: Image Scaling
Purpose:	Specifies the meta image scaling factor.
Notes:	Valid values are 1.0 (1% original size) to 100.0 (full size). In some circumstances rendering a meta image file at a lower resolution by using a lower value for the Image Max Megapixel Size can result in images whose lines and text look "jagged". In these cases you could try using a higher resolution Image Max Megapixel Size and then re-sizing (or scaling) the resultant image with this option. This will have the effect of smoothing (or anti-aliasing) these "jagged" items.

	Metafile To Rendered Bitmap: Image Stamp Max Megapixel Size
Purpose:	Specifies the meta image maximum rendering size for an image stamp.
Notes:	Valid values are 0.1 to 20.0 Here is a list of common mega pixel sizes and an example of an image size that just fits within this limit:    1.3    1300 x 1000 2.2 1800 x 1200 3.1 2000 x 1600 4.3 2400 x 1800 5.3 2700 x 2000 6.1 2900 x 2200 8.2 3400 x 2500 10.0 3700 x 2800

	Metafile To Rendered Bitmap: Image Stamp Scaling
Purpose:	Specifies the meta image stamp scaling factor.
Notes:	Valid values are 1.0 (1% original size) to 100.0 (full size). In some circumstances rendering a meta image file at a lower resolution by using a lower value for the Image Stamp Max Megapixel Size can result in images whose lines and text look "jagged". In these cases you could try using a higher resolution Image Stamp Max Megapixel Size and then re-sizing (or scaling) the resultant image with this option. This will have the effect of smoothing (or anti-aliasing) these "jagged" items.

	Metafile To Rendered Bitmap: Vertical Render Scale
Purpose:	Specifies the meta image vertical scaling factor during rendering.
Notes:	Valid values are 0.01 to 10.0, a value of 1.0 is equivalent to no scaling. In some circumstances rendering a meta image file may exhibit stretched text, to combat this you can set the vertical scaling to a value less than 1.0 - try 0.5 to start with.

	Metafile To Rendered Bitmap: Font Quality
Purpose:	Controls the font quality when rendering the meta image file into an image.
Notes:	Available options are:    Default Draft Proof Non Anti-Aliased Anti-Aliased Clear Type There are instances where the font records stored in a meta image file may specify either a default setting which is dependent on the PC being used or a setting that is not desired. This option allows the font quality to be set to a known value. Depending on your requirements you may want to use Non Anti-Aliased (when you want to ensure that the text pixels are either on or off only and not an interpolated color), Anti-Aliased (to make the text look smoother without adding any non-font color) or Clear Type (which creates better looking text but does add colored pixels in - note that this may not always be available on a PC - it depends on which version of Windows is being used and how it may have been configured).

	Metafile To Native PDF
Purpose:	Converts a meta image file into a native PDF representation by converting the GDI commands directly into equivalent PDF functions.
Notes:	This ensures that any text that was in the meta image file is text in the PDF and is therefore searchable. This may not be a perfect representation as there are features of meta image files that just cannot be duplicated using the native PDF facilities. However the PDF files produced are much smaller in filesize and usually of higher quality too. If fonts are used within a meta image then they must be TrueType fonts which have a Unicode CMAP font resource (which defines the names of the glyphs available) within their font definition. If a font does not have this then a default font is substituted. It is not possible to convert all Unicode characters that may be used, but the ones in the following Unicode codepages are mostly supported: CP874 (Thai), CP1250 (Latin2), CP1251 (Cyrillic), CP1252 (Latin1), CP1253 (Greek), CP1254 (Turkish), CP1255 (Hebrew), CP1256 (Arabic), CP127 (Baltic). Additionally, Arabic contextual forms (initial, medial, final and isolated) are supported through the use of the "Arabic Contextual Forms" option.

	Metafile To Native PDF: Center On Page
Purpose:	Adjusts the rendering of the meta image so that it is centered on the page.
Notes:	Rather than using a manual combination of Meta Margins and Border options to try and get a native rendered page to have the contents centered on the page, this option will do this automatically based on the content of the meta image that is actually rendered into the PDF.

	Metafile To Native PDF: Fit Text Within Bounds
Purpose:	Forces all text output to remain within the declared text bounding rectangle for that text.
Notes:	If text in a meta image file is larger than the defined bounding rectangle this option will progressively reduce the font size until it can fit the text within the defined bounding area. Depending on the composition of your meta image file it is sometimes better (with the text being more legible) if the text is allowed to extend outside the defined bounding rectangle (as long as there is nothing immediately next to it of course).

	Metafile To Native PDF: Embed Fonts
Purpose:	Embeds the actual fonts used within the PDF document to ensure that the text can be displayed in the correct font even on systems which do not have that font installed.
Notes:	If a document is converted which uses an unusual font that is not likely to be installed on a target system then this option will ensure that all of the font details are embedded within the PDF so that the target system that a PDF may be viewed on does not require the font in order to display the text within the PDF correctly. It should be noted that this will increase the file size of the produced PDF - but that may be a small price to pay to ensure that all users can view the PDF correctly.

	Metafile To Native PDF: Arabic Contextual Forms
Purpose:	Enables the analysis of surrounding text in order to change the Arabic glyph into one of the contextual Arabic alternatives (known as initial, medial, final and isolated forms).
Notes:	By default, when Arabic Unicode text is used (codepage CP1256) the Arabic glyphs do not take into account the context and relationship with other Arabic and non-Arabic text around them. It should be noted that not all available Arabic supporting fonts have all of the required Arabic contextual form characters, and therefore the output may feature non-available glyphs (normally shown as an outlined rectangular shape).

	Metafile To Native PDF: Default Font X Scaling
Purpose:	Enable scaling of the default font to better approximate the size and shape characteristics of the original font.
Notes:	Valid values are 0.01 to 100.0 If a default font is used because the original font cannot be matched then it may be necessary to use this option to scale the font width.

	Metafile To Native PDF: Default Font
Purpose:	Specifies the font name of one of the standard PDF fonts (which are also known as base14 fonts) used when the original font is either not a TrueType font or it is missing the required CMAP font resource.
Notes:	Available options are:    Automatic Courier Courier Bold Courier Bold Oblique Courier Oblique Helvetica Helvetica Bold Helvetica Bold Oblique Helvetica Oblique Times Roman Times Bold Times Italic Times Bold Italic The Automatic option ensures that the Helvetica font is used if the original font was determined as being of a proportional type or it uses Courier if it was determined as being of a mono-spaced type.

	Use EMF Device Size
Purpose:	Use a page size based on the declared device pixel size instead of the declared bounding rectangle.
Notes:	By default the dimensions (ie size) of an EMF image is determined by using the declared bounding rectangle which is stored as part of the meta file. Sometimes (and this depends on the application that created it) this can lead to a distorted (ie incorrectly sized) image. If this appears to be the case then try using this option which ignores the declared bounding rectangle and uses the declared reference device pixel size (again some applications may not set this correctly - although one would hope that at least one of these two settings has been correctly set!).

	Meta Margins
Purpose:	Forces the page size to include the meta image declared margin sizing.
Notes:	By default a meta image file is rendered on a page that is just large enough to enclose it. This option overrides this behaviour for those situations where you want to preserve the margins around the image (no matter how large they might be).

Buy Image to PDF Desktop Application Online!