Windows Metafile

Last updated

Windows Metafile (WMF) is an image file format originally designed for Microsoft Windows in the 1990s. The original Windows Metafile format was not device-independent (though could be made more so with placement headers) and may contain both vector graphics and bitmap components. It acts in a similar manner to SVG files. WMF files were later superseded by Enhanced Metafiles (EMF files) which did provide for device-independence. EMF files were then themselves enhanced via EMF+ files.

Contents

Essentially, a metafile stores a list of records consisting of drawing commands, property definitions and graphics objects to display an image on screen. [1] The drawing commands used are closely related to the commands of the Graphics Device Interface (GDI) API used for drawing in Microsoft Windows.

There are three major types of metafiles – a WMF is a 16-bit format introduced in Windows 3.0. It is the native vector format for Microsoft Office applications such as Word, PowerPoint, and Publisher. As of 2023, revision 17 of the Windows Metafile Format specification is available. [2] EMF files, which replaced WMF files, work on the same principle only it is a 32-bit file format that also allows for the embedding of private data within "comment" records. [3] EMF+ is an extension to EMF files and embedded in these comment records, allowing for images and text using commands, objects and properties that are similar to Windows GDI+. [4]

History

The original 16 bit WMF file format was fully specified in volume 4 of the 1992 Windows 3.1 SDK documentation [5] (at least if combined with the descriptions of the individual functions and structures in the other volumes), but that specification was vague about a few details. These manuals were published as printed books available in bookstores with no click through EULA or other unusual licensing restrictions (just a general warning that if purchased as part of a software bundle, the software would be subject to one).

Over time the existence of that historic specification was largely forgotten and some alternative implementations resorted to reverse engineering to figure out the file format from existing WMF files, which was difficult and error prone. [6] In September 2006, Microsoft again published the WMF file format specification in a more complete form [7] in the context of the Microsoft Open Specification Promise, promising to not assert patent rights to file format implementors. [8]

Microsoft later deprecated WMF files in favour of 32-bit EMF files as WMF files had real issues with device independence, despite the use of a "placeable" file header which provided basic device independence. Microsoft found that developers who use the format were "[embedding] application, location, or scaling comments in the metafiles... Others added headers to the metafile that provided various application-specific information", causing major compatibility issues. [9] Thus, in 1992 with Windows NT 3.1, Microsoft introduced the Enhanced Metafile format (EMF) [10] — a format which was based on the Win32 API and with which they built-in device independence. [11] [9] — these were also known as NT metafiles. [12] With the release of Windows XP and GDI+, the set of records had to be significantly increased and so Microsoft released EMF+ as an extension to the existing EMF file format. [10] [13]

Metafile structure

Comparison of Windows Metafiles - note that WMF files can include EMF+ records Microsoft Metafile comparisons.svg
Comparison of Windows Metafiles – note that WMF files can include EMF+ records

WMF, EMF and EMF+ files all consist of a series of records that are played back to produce graphical output. Some records define objects which can specify graphical objects used to determine how graphics should be drawn (e.g. pens specify the color and width of lines). Each of these objects are stored in metafiles and are placed into an object table, which tracks the usage of graphic objects while processing the metafile. The object table is an associative array of indexes to graphical object structures defined within the metafile.

WMF and EMF files handle object processing differently to EMF+ records in EMF files. As a WMF and EMF file is being processed, the records are read into an object table once an object is defined. If an object is deleted then the object is released from the table and the identifier can be reused. Notably an object will not be used until it is specifically selected during record playback. [14] [15] This differs for EMF+ files, which also use an associative array via a hashmap which records the object along with an object identifier. However, unlike WMF and EMF files which can delete an object, when a new object is created that has the same index as an existing object, the entry in the table is replaced with the new object. An EMF file also does not need to specifically select an object before it is used. [16]

WMF

Windows Metafile
Filename extension
.wmf
Internet media type
image/wmf [10]
Uniform Type Identifier (UTI) com.microsoft.wmf [10]
Type of format Vector graphics
Extended to EMF
Structures of original and placeable Windows metafiles WMF-structure.svg
Structures of original and placeable Windows metafiles

WMF files were not originally designed to be device independent, meaning that a file could not be played back on output devices that differed from the original device on which the file was recorded. A partial solution to this issue was invented by Aldus Corporation, who added an additional "placeable" header, called the "APM header", [18] which added a bounding rectangle, a metafile version, metafile size, number of objects in the metafile and the size of the largest single record in the metafile. [19] [20] This was later incorporated into the WMF format by Microsoft, starting in Windows 2000. [21]

WMF files are structured by a series of records, starting with a number of control records: the header record, [19] [22] the aforementioned optional placeable record, [23] and finished by an end of file record. [19] [24]

Encapsulated by the control records are the records that make up the image itself. These records work within what is known as the playback device context, which is the collection of properties and objects that make up a device's graphical environment as the metafile is being "played back" onto this output device. [25]

Records other than control records can be largely grouped into bitmap records, drawing records, object records, state records and escape records.

Bitmap records

Bitmap records manage and output bitmap images.

NameDescription
META_BITBLTSpecifies how to do a bit block transfer. These records can specify a bitmap to use as the source, or a region. [26]
META_DIBBITBLTSpecifies how to do a bit block transfer of a device-independent bitmap image. These records can specify a bitmap to use as the source, or a region. [27]
META_DIBSTRETCHBITBLTSpecifies how to do a bit block transfer of a device-independent bitmap image, but allows for expansion or contraction of the image. These records can specify a bitmap to use as the source, or a region. [28]
META_SETDIBTODEVSpecifies color to set a block of pixels in a device-independent bitmap image. These records can specify a bitmap to use as the source, or a region. [29]
META_STRETCHBLTSpecifies how to do a bit block transfer, but allows for expansion or contraction of the image. [30]
META_STRETCHDIBSpecifies how to do a bit block transfer of a device-independent bitmap image, but allows for expansion or contraction of the image. These records can specify a bitmap to use as the source, or a region. [31]

Drawing records

Drawing records produce graphics output.

NameDescription
META_ARCDraws an elliptical arc. [32]
META_CHORDDraws a chord. [33]
META_ELLIPSEDraws an elliptical arc. [34]
META_EXTFLOODFILLFills an area with a brush. [35]
META_EXTTEXTOUTDraw text with font, background color and text color of the playback device context. [36]
META_FILLREGIONFills a region with a specified brush. [37]
META_FLOODFILLFills an area with a brush. [38]
META_FRAMEREGIONDraws a border around a region of the page with a brush. [39]
META_INVERTREGIONPaints a region of the graphic with inverted colors. [40]
META_LINETODraws a half-open line from the drawing position defined in the playback device context to a specified point. [41]
META_PAINTREGIONPaint a region with the current brush specified in the playback device context. [42]
META_PATBLTPaint a region with the current brush specified in the playback device context and then combine the brush color and surface color(s) using a raster operation. [43]
META_PIEDraw a pie-shaped wedge bounded by the intersection of an ellipse and two radials — the line is set via the pen set via the playback device context, and the area bounded by the pie shape is filled in by the current brush of the playback device context. [44]
META_POLYLINEDraws a series of line segnments by connecting the points in a specified array. [45]
META_POLYGONPaints a polygon consisting of two or more vertices connected by straight lines. The polygon is outlined by using the pen and filled by using the brush and polygon fill mode that are defined in the playback device context. [46]
META_POLYPOLYGONPaints a series of closed polygons, which may overlap. Each polygon is outlined by using the pen and filled by using the brush and polygon fill mode that are defined in the playback device context. [47]
META_RECTANGLEPaints a rectangle, which is outlined by using the pen and filled by using the brush and is filled by using the brush that is defined in the playback device context. [48]
META_ROUNDRECTPaints a rectangle with rounded corners. The rectangle is outlined by using the pen and filled by using the brush and is filled by using the brush that is defined in the playback device context. [49]
META_SETPIXELSets the pixel at the specified coordinates to the specified color. [50]
META_TEXTOUTOutputs a character string at the specified location by using the font, background color, and text color that are defined in the playback device context. [51]

Object records

Object records create and manage graphics objects. In WMF files there are two broad categories of objects – graphics objects and structure objects. Structure objects are not explicitly created or deleted in a WMF, they are instead of complex structures. For example, the BitmapCoreHeader contains information about the dimensions and color format of a device-independent bitmap, [52] which is itself part of a DeviceIndependentBitmap object. [53] A graphics object, however, specifies parameters for graphics output and during playback of the WMF it sets up the playback device context. [54]

Graphics objects can be brushes (defines the style, color and pattern of a brush which defines how to paint an area of the graphic), fonts (defines properties that affect how text is displayed), palettes (specifies colors as device-independent values, defined by an application), pens (specifies the graphical attributes of a line), and regions (which specify line and curve segments that define a shape). [54]

NameDescription
META_CREATEBRUSHINDIRECTCreates a brush object from a LogBrush (logical brush) object. [55]
META_CREATEFONTINDIRECTCreates a brush object from a font object. [56]
META_CREATEPALETTECreates a palette object.
META_CREATEPATTERNBRUSH [57] Creates a brush object from a LogBrush (logical brush) object. [58]
META_CREATEPENINDIRECTCreates a pen object. [59]
META_CREATEREGIONCreates a region object. [60]
META_DELETEOBJECTDelete an object. [61]
META_CREATEBRUSHINDIRECTCreates a brush object from a LogBrush (logical brush) object. [62]
META_DIBCREATEPATTERNBRUSHCreates a brush object from a device-independent bitmap. [63]
META_SELECTCLIPREGIONSpecifies the region object that will be the current clipping region. [64]
META_SELECTOBJECTSelects the object that will be the current object for the playback device context, which works on all graphics objects except palette objects, which must be set with META_SELECTPALETTE. [65]
META_SELECTPLAETTESelects the logical palette for the playback device context. [66]

State records

State records manage the graphics properties of the playback device context. [67]

NameDescription
META_ANIMATEPALETTERedefines entries in the logical palette that is defined in the playback device context with a specified Palette Object. [68]
META_EXCLUDECLIPRECTSets the clipping region that is defined in the playback device context to the existing clipping region minus a specified rectangle. [69]
META_INTERSECTCLIPRECTSets the clipping region that is defined in the playback device context to the intersection of the existing clipping region and a specified rectangle. [70]
META_MOVETOSets the output position in the playback device context to a specified point. [71]
META_OFFSETCLIPRGNMoves the clipping region that is defined in the playback device context by specified offsets. [72]
META_OFFSETVIEWPORTORGMoves the viewport origin in the playback device context by specified horizontal and vertical offsets. [73]
META_OFFSETWINDOWORGMoves the output window origin in the playback device context by specified horizontal and vertical offsets. [74]
META_REALIZEPALETTEMaps entries from the logical palette that is defined in the playback device context to the system palette. [75]
META_RESIZEPALETTERedefines the size of the logical palette that is defined in the playback device context. [76]
META_RESTOREDCRestores the playback device context from a previously saved device context. [77]
META_SAVEDCSaves the playback device context for later retrieval. [78]
META_SCALEVIEWPORTEXTScales the horizontal and vertical extents of the viewport that is defined in the playback device context using the ratios formed by specified multiplicands and divisors. [79]
META_SCALEWINDOWEXTScales the horizontal and vertical extents of the output window that is defined in the playback device context using the ratios formed by specified multiplicands and divisors. [80]
META_SETBKCOLORSets the background color in the playback device context to a specified color. [81]
META_SETBKMODESets the background mix mode in the playback device context. [82]
META_SETLAYOUTDefines the layout orientation in the playback device context. [83]
META_SETMAPMODEDefines the mapping mode in the playback device context. [84]
META_SETMAPPERFLAGSDefines the algorithm that the font mapper uses when it maps logical fonts to physical fonts. [85]
META_SETPALENTRIESDefines RGB color values in a range of entries in the logical palette that is defined in the playback device context. [86]
META_SETPOLYFILLMODEDefines polygon fill mode in the playback device context for graphics operations that fill polygons. [87]
META_SETRELABSUnused record. [88]
META_SETROP2Defines the foreground raster operation mixing mode in the playback device context. [89]
META_SETSTRETCHBLTMODEDefines the bitmap stretching mode in the playback device context. [90]
META_SETTEXTALIGNDefines text-alignment values in the playback device context. [91]
META_SETTEXTCHAREXTRADefines inter-character spacing for text justification in the playback device context. [92]
META_SETTEXTCOLORDefines the text foreground color in the playback device context. [93]
META_SETTEXTJUSTIFICATIONDefines the amount of space to add to break characters in a string of justified text. [94]
META_SETVIEWPORTEXTDefines the horizontal and vertical extents of the viewport in the playback device context. [95]
META_SETVIEWPORTORGDefines the viewport origin in the playback device context. [96]
META_SETWINDOWEXTDefines the horizontal and vertical extents of the output window in the playback device context. [97]
META_SETWINDOWORGDefines the output window origin in the playback device context. [98]

Escape records

WMF generic escape record WMF Escape Record.svg
WMF generic escape record

Escape records are a means to extend metafile functionality via records that are not otherwise defined as a WMF record type. Each escape record contains a record function, an escape function and potentially escape data.

The following escape records make up a WMF file.

NameDescription
ABORTDOCStops processing the current document. [99]
BEGIN_PATHOpens a path. [100]
CHECK_JPEGFORMATDetermines whether it can handle the given JPEG image. [101]
CHECK_PNGFORMATDetermines whether it can handle the given PNG image. [102]
CLIP_TO_PATHApplies a function to the current PostScript clipping path. [103]
CLOSE_CHANNELSame as ENDDOC. [104]
DOWNLOAD_FACESets the font face name on the output device. [105]
DOWNLOAD_HEADERDownloads sets of PostScript procedures. [106]
DRAW_PATTERNRECTDraws a rectangle with a defined pattern. [107]
ENCAPSULATED_POSTSCRIPTSends arbitrary encapsulated PostScript (EPS) data directly to the printer driver. [108]
END_PATHEnds a path. [109]
ENDDOCNotifies the printer driver that a new print job is ending. [110]
EPS_PRINTINGIndicates the start and end of EPS printing. [111]
EXTTEXTOUTDraws text using the currently selected font, background color, and text color. [112]
GET_COLORTABLEGets color table values from the printer driver. [113]
GET_DEVICEUNITSGets the device units currently configured on the output device. [114]
GET_EXTENDED_TEXTMETRICSGets the extended text metrics that are currently configured on the printer driver. [115]
GET_FACENAMEGets the font face name currently configured on the output device. [116]
GET_PAIRKERNTABLEGets the font kern table currently defined on the output device. [117]
GET_PHYSPAGESIZERetrieves the physical page size currently selected on the output device. [118]
GET_PRINTINGOFFSETRetrieves the offset from the upper-left corner of the physical page where the actual printing or drawing begins. [119]
GET_PS_FEATURESETTINGQueries the printer driver for information about PostScript features supported on the output device. [120]
GET_SCALINGFACTORRetrieves the scaling factors for the x-axis and the y-axis of a printer. [121]
META_ESCAPE_ENHANCED_METAFILEUsed to embed an EMF metafile within a WMF metafile. [122]
METAFILE_DRIVERQueries the printer driver about its support for metafiles on the output device. [123]
NEWFRAMENotifies the printer driver that the application has finished writing to a page. [124]
NEXTBANDNotifies the printer driver that the application has finished writing to a band. [125]
PASSTHROUGHPasses through arbitrary data to the printer driver. [126]
POSTSCRIPT_DATASends arbitrary PostScript data to the output device. [127]
POSTSCRIPT_IDENTIFYSets the printer driver to either PostScript-centric or GDI-centric mode. [128]
POSTSCRIPT_IGNORENotifies the output device to ignore PostScript data. [129]
POSTSCRIPT_INJECTIONInserts a block of raw data into a PostScript stream. [130]
POSTSCRIPT_PASSTHROUGHSends arbitrary data directly to a printer driver, which is expected to process this data only when in PostScript mode. [131]
OPEN_CHANNELActs the same as STARTDOC, with a NULL document and output filename, and data in raw mode. [132]
QUERY_DIBSUPPORTQueries the printer driver about its support for DIBs on the output device. [133]
QUERY_ESCSUPPORTQueries the printer driver to determine whether a specific WMF escape function is supported on the output device. [134]
SET_COLORTABLESets color table values. [135]
SET_COPYCOUNTSets the number of copies. [136]
SET_LINECAPSpecifies the line-ending mode to use in drawing to the output device. [137]
SET_LINEJOINSpecifies the line-joining mode to use in drawing to the output device. [138]
SET_MITERLIMITSets the limit for the length of miter joins to use in drawing to the output device. [139]
SPCLPASSTHROUGH2Enables documents to include private procedures and other arbitrary data in documents. [140]
STARTDOCNotifies the printer driver that a new print job is starting. [141]

There was a major vulnerability found in escape records around the Abort escape record, which stores the abort procedure code within the record itself. This affected Windows systems (see CVE - 2005-4560) and the Wine project (see CVE - 2006-0106). According to Secunia, "The vulnerability is caused due to an error in the handling of Windows Metafile files ('.wmf') containing specially crafted SETABORTPROC 'Escape' records. Such records allow arbitrary user-defined function to be executed when the rendering of a WMF file fails." [142] According to the Windows 3.1 SDK documentation, the SETABORTPROC escape was obsoleted and replaced by the function of the same name in Windows 3.1, long before the WMF vulnerability was discovered. [143] However the obsoleted escape code was retained for compatibility with 16 bit programs written for (or at least backwards compatible with) Windows 3.0. This change happened at approximately the same time as Microsoft was creating the 32 bit reimplementation of GDI for Windows NT, and it is likely that the vulnerability occurred during this effort.

After Steve Gibson accused Microsoft of deliberately implementing a backdoor into their code, [144] [145] Mark Russinovich provided a rebuttal, and stated that:

...things were different when the format was architected. In the Windows 3.1 “large” memory model code is inherently location-independent and Windows was never patched, so both Windows and an application could simply copy an application function into the WMF file and assume it would work when played back by the same application in a later run session. In any case, its not clear that the developers envisioned applications creating on-disk metafiles with abort procedures. Also, as Microsoft’s Stephen Toulouse pointed out in Microsoft’s rebuttal to Steve’s claims, the security landscape in the early 1990s was very different than today and all code, including that stored in a WMF file, was inherently trusted. [146]

Peter Ferrie of Symantec Security Response, USA also disagreed with Gibson, noting that:

Gibson claimed that a thread is created to run the SetAbortProc handler. In fact, no thread is created to run the handler – it is a callback, which is called by the parser, and the parser has to wait until the callback returns, otherwise the whole point of the function (to abort the printing) is lost. By his own admission, Gibson did not read the documentation (in fact, he claimed that he couldn’t find it, although it is freely available on Microsoft’s Web site), and he claimed that the device context is not available to the function handler. Of course the device context is available to the function handler — it is one of the two parameters that is passed to it (see above), and it is required in order to abort the printing. Finally, Gibson claimed that the control flow could not return to Windows. It is simply a matter of the function returning and discarding the parameters that were passed on the stack. If the record is well formed, Windows will continue to parse the file, as before. ... Gibson admits that he was guessing about a number of things. Unfortunately, he guessed poorly. I guess we know better now. [147]

EMF

Enhanced Metafile
Filename extension
.emf
Internet media type
image/emf [10]
Uniform Type Identifier (UTI) com.microsoft.emf [10]
Type of format Vector graphics
Extended from WMF
Extended to EMF+
Windows Enhanced Metafile headers EMF headers.svg
Windows Enhanced Metafile headers

EMF files have three possible versions of headers. The original headers is just a container for images, the second and third version encapsulates the original header and contains a pixel format record and support for OpenGL records, and the third version encapsulates the second header extension and increases EMF accuracy and scalability of EMFs as it adds the ability to measure distances of device surfaces using the metric system. [148]

Each EMF header starts with an EMR_HEADER record, and records the relevant properties of the device on which the metafile image was recorded. The original EMF header has an 80 byte header and an optional variable length description string. [149] Other metafiles contain extension fields, which encapsulate the original header. EmfMetafileHeaderExtension1 is a record that is inserted directly after the original EMF header, specifies whether there is a pixel format descriptor and the offset to the descriptor object within the header, as well as a field that specifies if OpenGL records exist in the metafile. [150] The pixel format descriptor specifies the capabilities of the drawing surface and whether a pixel is encoded in RGBA or is an index into a color table. [151] EmfMetafileHeaderExtension2 is a record that is inserted directly after the EmfMetafileHeaderExtension1 record, and it contains two fields with the X and Y values to measure the device surface in micrometers. [152]

Like WMF files, records can be classified by function, however there are more record types in EMF files than there are in WMF files. Records can be classified as control, bitmap, clipping, comment, drawing, escape, object creation, object manipulation, OpenGL, path bracket, state and transform records.

EMF+

With the release of Windows XP, the Enhanced Metafile Format Plus Extensions (EMF+) format was introduced. EMF+ provides a way to serialize calls to the GDI+ API in the same way that WMF/EMF stores calls to GDI.

There are also compressed versions of Windows Metafiles known as Compressed Windows Metafile (WMZ) and Compressed Windows Enhanced Metafile (EMZ), [153] which are basically gzip compressed WMF and EMF files correspondingly.

Implementations

The WMF format was designed to be executed by the Windows GDI layer in order to restore the image, but as the WMF binary files contain the definition of the GDI graphic primitives that constitute this image, it is possible to design alternative libraries that render WMF binary files or convert them into other graphic formats.

See also

Related Research Articles

<span class="mw-page-title-main">Dia (software)</span> Diagramming software

Dia is free and open source general-purpose diagramming software, developed originally by Alexander Larsson. It uses a controlled single document interface (SDI) similar to GIMP and Inkscape.

The Rich Text Format is a proprietary document file format with published specification developed by Microsoft Corporation from 1987 until 2008 for cross-platform document interchange with Microsoft products. Prior to 2008, Microsoft published updated specifications for RTF with major revisions of Microsoft Word and Office versions.

The Portable Executable (PE) format is a file format for executables, object code, DLLs and others used in 32-bit and 64-bit versions of Windows operating systems, and in UEFI environments. The PE format is a data structure that encapsulates the information necessary for the Windows OS loader to manage the wrapped executable code. This includes dynamic library references for linking, API export and import tables, resource management data and thread-local storage (TLS) data. On NT operating systems, the PE format is used for EXE, DLL, SYS, MUI and other file types. The Unified Extensible Firmware Interface (UEFI) specification states that PE is the standard executable format in EFI environments.

<span class="mw-page-title-main">Graphics Device Interface</span> Microsoft Windows API

The Graphics Device Interface (GDI) is a legacy component of Microsoft Windows responsible for representing graphical objects and transmitting them to output devices such as monitors and printers. It was superseded by DirectDraw API and later Direct2D API. Windows apps use Windows API to interact with GDI, for such tasks as drawing lines and curves, rendering fonts, and handling palettes. The Windows USER subsystem uses GDI to render such UI elements as window frames and menus. Other systems have components that are similar to GDI; for example: Mac OS has QuickDraw, and Linux and Unix have X Window System core protocol.

Encapsulated PostScript (EPS) is a Document Structuring Convention (DSC) conforming PostScript document format usable as a graphics file format. The format was developed as early as 1987 by John Warnock and Chuck Geschke, the founders of Adobe, together with Aldus. The basis of early versions of the Adobe Illustrator Artwork file format is formed by EPS together with the DSC Open Structuring Conventions.

The BMP file format or bitmap, is a raster graphics image file format used to store bitmap digital images, independently of the display device, especially on Microsoft Windows and OS/2 operating systems.

A container format or metafile is a file format that allows multiple data streams to be embedded into a single file, usually along with metadata for identifying and further detailing those streams. Notable examples of container formats include archive files and formats used for multimedia playback. Among the earliest cross-platform container formats were Distinguished Encoding Rules and the 1985 Interchange File Format.

<span class="mw-page-title-main">Microsoft PhotoDraw</span> Vector/raster graphics editing software

Microsoft PhotoDraw was a vector graphics and raster image editing software developed by Microsoft. It was released in 1999 as part of the Microsoft Office 2000 family of products and was specifically designed for creating and editing graphics, illustrations, and photo compositions.

<span class="mw-page-title-main">GUID Partition Table</span> Computer disk partitioning standard

The GUID Partition Table (GPT) is a standard for the layout of partition tables of a physical computer storage device, such as a hard disk drive or solid-state drive, using universally unique identifiers (UUIDs), which are also known as globally unique identifiers (GUIDs). Forming a part of the Unified Extensible Firmware Interface (UEFI) standard, it is nevertheless also used for some BIOSs, because of the limitations of master boot record (MBR) partition tables, which use 32 bits for logical block addressing (LBA) of traditional 512-byte disk sectors.

An image file format is a file format for a digital image. There are many formats that can be used, such as JPEG, PNG, and GIF. Most formats up until 2022 were for storing 2D images, not 3D ones. The data stored in an image file format may be compressed or uncompressed. If the data is compressed, it may be done so using lossy compression or lossless compression. For graphic design applications, vector formats are often used. Some image file formats support transparency.

Open XML Paper Specification is an open specification for a page description language and a fixed-document format. Microsoft developed it as the XML Paper Specification (XPS). In June 2009, Ecma International adopted it as international standard ECMA-388.

The Windows Metafile vulnerability—also called the Metafile Image Code Execution and abbreviated MICE—is a security vulnerability in the way some versions of the Microsoft Windows operating system handled images in the Windows Metafile format. It permits arbitrary code to be executed on affected computers without the permission of their users. It was discovered on December 27, 2005, and the first reports of affected computers were announced within 24 hours. Microsoft released a high-priority update to eliminate this vulnerability via Windows Update on January 5, 2006. Attacks using this vulnerability are known as WMF exploits.

<span class="mw-page-title-main">Apache Batik</span>

Batik is a pure-Java library that can be used to render, generate, and manipulate SVG graphics. IBM supported the project and then donated the code to the Apache Software Foundation, where other companies and teams decided to join efforts. Batik provides a set of core modules that provide functionality to:

The SNP file format was used by Microsoft Access to store Report Snapshots in a single file which can be viewed and printed by the Microsoft Snapshot Viewer, a Windows program available free of charge from Microsoft that allows report output to be viewed without requiring Access. Support for the format was discontinued in Access 2010 and later versions; Access reports can be exported in PDF/XPS and Excel formats viewable on many platforms.

The Object Module Format (OMF) is an object file format used primarily for software intended to run on Intel 80x86 microprocessors. It was originally developed by Intel around 1975–1977 for ISIS-II, targeting the 8-bit 8080/8085 processors. This variant later became known as OMF-80. As OMF-86 it was adapted to the 16-bit 8086 processor in 1978.

In computing, a bitmap graphic is an image formed from rows of different colored pixels. A GIF is an example of a graphics image file that uses a bitmap.

The Microsoft Open Specification Promise is a promise by Microsoft, published in September 2006, to not assert its patents, in certain conditions, against implementations of a certain list of specifications.

<span class="mw-page-title-main">STDU Viewer</span> Document viewer

STDU Viewer is computer software, a compact viewer for many computer file formats: Portable Document Format (PDF), World Wide Fund for Nature (WWF), DjVu, comic book archive, FB2, ePUB, XML Paper Specification (XPS), Text Compression for Reader (TCR), Mobipocket (MOBI), AZW, multi-page TIFF, text file (TXT), PalmDoc (PDB), Windows Metafile (EMF), Windows Metafile (WMF), bitmap (BMP), Graphics Interchange Format (GIF), JPEG-JPG, Portable Network Graphics (PNG), Photoshop Document (PSD), PiCture eXchange (PCX-DCX). It works under Microsoft Windows, and is free for non-commercial use.

<span class="mw-page-title-main">Microsoft Expression Design</span> Vector and raster graphics editor

Microsoft Expression Design was Microsoft's commercial professional illustration vector and raster graphic design tool for web images based on Creature House Expression, which was acquired by Microsoft in 2003. It is available free of charge from Microsoft and is a component of the discontinued Microsoft Expression Studio suite. Expression Design is more oriented towards editing XAML and web graphics rather than print graphics and does not incorporate all of the raster image editing features of the original Creature House Expression.

References

  1. ↑ Windows Metafile Format (PDF), Microsoft, p. 16
  2. ↑ "[MS-WMF]: Windows Metafile Format". MSDN. 2021-04-26. Retrieved 2023-09-13.
  3. ↑ [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 17
  4. ↑ [MS-EMFPLUS]: Enhanced Metafile Format Plus Extensions (PDF), Microsoft, p. 19
  5. ↑ Microsoft Windows 3.1 Programmers Reference, Volume 4 Resources, Microsoft Press 1992, ISBN   1-55615-494-1, chapter 3 pp. 21-45
  6. ↑ Caolan McNamara. "Window Metafile (wmf) Reference" . Retrieved 2008-06-01. These opcodes are unimplemented, for the reason that i dont know what they are, no known documentation
  7. ↑ "[MS-WMF]: Windows Metafile Format Specification" . Retrieved 2008-06-01.
  8. ↑ "Microsoft Open Specification Promise". Microsoft . Retrieved 2008-06-01.
  9. 1 2 Enhanced Metafiles in Win32, Microsoft Developer Network Technology Group, June 10, 1993
  10. 1 2 3 4 5 6 Leonard, Sean (September 2016). "Windows Metafiles". Windows Image Media Types. IETF. p. 1. doi: 10.17487/RFC7903 . ISSN   2070-1721. RFC 7903 . Retrieved February 8, 2020.
  11. ↑ "EMF", FileFormat, Aspose Pty Ltd, 11 October 2019, retrieved 2020-01-20
  12. ↑ Petzold, Charles (October 11, 1994), "NT Metafiles and GDI Objects", PC Magazine , pp. 343–347
  13. ↑ Polyakov, Alex; Brusentsev, Vitaly (2005). Graphics Programming with GDI+ & DirectX. A-List Publishing. p. 68. ISBN   1-931769-39-7.
  14. ↑ "3.1.4.1 WMF Object Table", [MS-WMF]: Enhanced Metafile Format (PDF), Microsoft, p. 187
  15. ↑ "3.1.1.1 EMF Object Table", [MS-EMF]: Windows Metafile Format Specification (PDF), Microsoft, pp. 212–214
  16. ↑ [MS-EMFPLUS]: Enhanced Metafile Format Plus Extensions (PDF), Microsoft, pp. 204–205
  17. ↑ "Figure 1: Structures of original and placeable Windows metafiles", Windows Metafile Format (PDF), Microsoft, p. 17
  18. ↑ Q66949: INFO: Windows Metafile Functions & Aldus Placeable Metafiles, Microsoft – via KnowledgeBase Archive: An Archive of Early Microsoft KnowledgeBase
  19. 1 2 3 "1.3.1 Metafile Structure", Windows Metafile Format (PDF), Microsoft, p. 17
  20. ↑ "2.3.2.3 META_PLACEABLE Record", Windows Metafile Format (PDF), Microsoft, p. 115
  21. ↑ Windows Metafile Format (PDF), Microsoft, p. 55, <55> Section 2.3.2.3: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows 95: This feature is not supported.
  22. ↑ "2.3.2.2 MTF_HEADERRECORD Record", Windows Metafile Format (PDF), Microsoft, p. 114
  23. ↑ "2.3.2.2 MTF_HEADERRECORD Record", Windows Metafile Format (PDF), Microsoft, p. 114
  24. ↑ "2.3.2.1 MTF_EOF Record", Windows Metafile Format (PDF), Microsoft, p. 114
  25. ↑ "1.1 Glossary", [MS-WMF]: Windows Metafile Format Specification (PDF), Microsoft, p. 13, retrieved 2020-01-24
  26. ↑ "2.3.1.1 META_BITBLT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 101–103, retrieved 2020-01-24
  27. ↑ "2.3.1.2 META_DIBBITBLT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), Microsoft, pp. 103–106, retrieved 2020-01-24
  28. ↑ "2.3.1.3 META_DIBSTRETCHBITBLT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), Microsoft, pp. 106–108, retrieved 2020-01-24
  29. ↑ "2.3.1.4 META_SETDIBTODEV Record", [MS-WMF]: Windows Metafile Format Specification (PDF), Microsoft, pp. 108–109, retrieved 2020-01-24
  30. ↑ "2.3.1.5 META_STRETCHBLT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), Microsoft, pp. 109–110, retrieved 2020-01-24
  31. ↑ "2.3.1.6 META_STRETCHDIB Record", [MS-WMF]: Windows Metafile Format Specification (PDF), Microsoft, pp. 103–106, retrieved 2020-01-24
  32. ↑ "2.3.3.1 META_ARC Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 101–103, retrieved 2020-01-24
  33. ↑ "2.3.3.2 META_CHORD Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 117–118, retrieved 2020-01-24
  34. ↑ "2.3.3.3 META_ELLIPSE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 119, retrieved 2020-01-24
  35. ↑ "2.3.3.4 META_EXTFLOODFILL Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 119–120, retrieved 2020-01-24
  36. ↑ "2.3.3.5 META_EXTTEXTOUT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 119–120, retrieved 2020-01-24
  37. ↑ "2.3.3.6 META_FILLREGION Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 121, retrieved 2020-01-24
  38. ↑ "2.3.3.7 META_FLOODFILL Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 119–120, retrieved 2020-01-24
  39. ↑ "2.3.3.8 META_FRAMEREGION Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 122–123, retrieved 2020-01-24
  40. ↑ "2.3.3.9 META_INVERTREGION Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 123, retrieved 2020-01-24
  41. ↑ "2.3.3.10 META_LINETO Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 123–124, retrieved 2020-01-24
  42. ↑ "2.3.3.11 META_PAINTREGION Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 124, retrieved 2020-01-24
  43. ↑ "2.3.3.12 META_PATBLT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 124–125, retrieved 2020-01-24
  44. ↑ "2.3.3.13 META_PIE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 125–126, retrieved 2020-01-24
  45. ↑ "2.3.3.14 META_POLYLINE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 126, retrieved 2020-01-24
  46. ↑ "2.3.3.15 META_POLYGON Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 127, retrieved 2020-01-24
  47. ↑ "2.3.3.16 META_POLYPOLYGON Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 127–128, retrieved 2020-01-24
  48. ↑ "2.3.3.17 META_RECTANGLE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 127–128, retrieved 2020-01-24
  49. ↑ "2.3.3.18 META_ROUNDRECT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 128–129, retrieved 2020-01-24
  50. ↑ "2.3.3.19 META_SETPIXEL Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 129–130, retrieved 2020-01-24
  51. ↑ "2.3.3.20 META_TEXTOUT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 130, retrieved 2020-01-24
  52. ↑ "2.2.2.2. BitmapCoreHeader Object", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 85, retrieved 2020-01-25
  53. ↑ "2.2.2.9. DeviceIndependentBitmap Object", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 91, retrieved 2020-01-25
  54. 1 2 "2.2.1. Graphics Objects", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 79, retrieved 2020-01-25
  55. ↑ "2.3.4.1 META_CREATEBRUSHINDIRECT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 131–132, retrieved 2020-01-25
  56. ↑ "2.3.4.2 META_CREATEFONTINDIRECT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 132, retrieved 2020-01-25
  57. ↑ "2.3.4.4 META_CREATEPATTERNBRUSH Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 133–135, retrieved 2020-01-25
  58. ↑ "2.3.4.3 META_CREATEPALETTE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 132–133, retrieved 2020-01-25
  59. ↑ "2.3.4.5 META_CREATEPENINDIRECT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 134–135, retrieved 2020-01-25
  60. ↑ "2.3.4.6 META_CREATEREGION Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 135, retrieved 2020-01-25
  61. ↑ "2.3.4.7 META_DELETEOBJECT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 135, retrieved 2020-01-25
  62. ↑ "2.3.4.8 META_CREATEBRUSHINDIRECT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 135–136, retrieved 2020-01-25
  63. ↑ "2.3.4.9 META_DIBCREATEPATTERNBRUSH Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 136–137, retrieved 2020-01-25
  64. ↑ "2.3.4.10 META_SELECTCLIPREGION Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 137, retrieved 2020-01-25
  65. ↑ "2.3.4.11 META_SELECTOBJECT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 137–138, retrieved 2020-01-25
  66. ↑ "2.3.4.11 META_SELECTPLAETTE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 139, retrieved 2020-01-25
  67. ↑ "2.3.5 State Record Types", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 138, retrieved 2020-01-28
  68. ↑ "2.3.5.1 META_ANIMATEPALETTE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 140, retrieved 2020-01-28
  69. ↑ "2.3.5.2 META_EXCLUDECLIPRECT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 140–141, retrieved 2020-01-28
  70. ↑ "2.3.5.3 META_INTERSECTCLIPRECT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 141–142, retrieved 2020-01-28
  71. ↑ "2.3.5.1 META_MOVETO Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 142, retrieved 2020-01-28
  72. ↑ "2.3.5.4 META_OFFSETCLIPRGN Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 142–143, retrieved 2020-01-28
  73. ↑ "2.3.5.5 META_OFFSETVIEWPORTORG Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 143, retrieved 2020-01-28
  74. ↑ "2.3.5.6 META_OFFSETWINDOWORG Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 131–132, retrieved 2020-01-28
  75. ↑ "2.3.5.7 META_REALIZEPALETTE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 143–144, retrieved 2020-01-28
  76. ↑ "2.3.5.8 META_RESIZEPALETTE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 144, retrieved 2020-01-28
  77. ↑ "2.3.5.9 META_RESTOREDC Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 145, retrieved 2020-01-28
  78. ↑ "2.3.5.10 META_SAVEDC Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 145, retrieved 2020-01-28
  79. ↑ "2.3.5.11 META_SCALEVIEWPORTEXT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 145–146, retrieved 2020-01-28
  80. ↑ "2.3.5.12 META_SCALEWINDOWEXT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 146–147, retrieved 2020-01-28
  81. ↑ "2.3.5.13 META_SETBKCOLOR Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 147, retrieved 2020-01-28
  82. ↑ "2.3.5.14 META_SETBKMODE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 147–148, retrieved 2020-01-28
  83. ↑ "2.3.5.15 META_SETLAYOUT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 148, retrieved 2020-01-28
  84. ↑ "2.3.5.16 META_SETMAPMODE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 148–149, retrieved 2020-01-28
  85. ↑ "2.3.5.17 META_SETMAPPERFLAGS Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 131–132, retrieved 2020-01-28
  86. ↑ "2.3.5.18 META_ANIMATEPALETTE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 149, retrieved 2020-01-28
  87. ↑ "2.3.5.19 META_SETPALENTRIES Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 149–150, retrieved 2020-01-28
  88. ↑ "2.3.5.20 META_SETRELABS Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 150, retrieved 2020-01-28
  89. ↑ "2.3.5.21 META_SETROP2 Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 151, retrieved 2020-01-28
  90. ↑ "2.3.5.1 META_SETSTRETCHBLTMODE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 151–152, retrieved 2020-01-28
  91. ↑ "2.3.5.22 META_SETTEXTALIGN Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 152, retrieved 2020-01-28
  92. ↑ "2.3.5.1 META_SETTEXTCHAREXTRA Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 152–153, retrieved 2020-01-28
  93. ↑ "2.3.5.23 META_SETTEXTCOLOR Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 153, retrieved 2020-01-28
  94. ↑ "2.3.5.24 META_SETTEXTJUSTIFICATION Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 153–154, retrieved 2020-01-28
  95. ↑ "2.3.5.25 META_SETVIEWPORTEXT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 154, retrieved 2020-01-28
  96. ↑ "2.3.5.26 META_SETVIEWPORTORG Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 154–155, retrieved 2020-01-28
  97. ↑ "2.3.5.27 META_SETWINDOWEXT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 155, retrieved 2020-01-28
  98. ↑ "2.3.5.28 META_SETWINDOWORG Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 155, retrieved 2020-01-28
  99. ↑ "2.3.6.2. ABORTDOC Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 158–159, retrieved 2020-01-28
  100. ↑ "2.3.6.3. BEGIN_PATH Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 159, retrieved 2020-01-28
  101. ↑ "2.3.6.4. CHECK_JPEGFORMAT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 159–160, retrieved 2020-01-28
  102. ↑ "2.3.6.5. CHECK_PNGFORMAT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 160, retrieved 2020-01-28
  103. ↑ "2.3.6.6. CLIP_TO_PATH Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 160, retrieved 2020-01-28
  104. ↑ "2.3.6.7. CLOSE_CHANNEL Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 162, retrieved 2020-01-28
  105. ↑ "2.3.6.8. DOWNLOAD_FACE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 162–163, retrieved 2020-01-28
  106. ↑ "2.3.6.9. DOWNLOAD_HEADER Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 158–159, retrieved 2020-01-28
  107. ↑ "2.3.6.10. DRAW_PATTERNRECT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 163–164, retrieved 2020-01-28
  108. ↑ "2.3.6.11. ENCAPSULATED_POSTSCRIPT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 164, retrieved 2020-01-28
  109. ↑ "2.3.6.12. END_PATH Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 164–165, retrieved 2020-01-28
  110. ↑ "2.3.6.13. ENDDOC Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 165, retrieved 2020-01-28
  111. ↑ "2.3.6.14. EPS_PRINTING Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 165–166, retrieved 2020-01-28
  112. ↑ "2.3.6.15. EXTTEXTOUT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 166–167, retrieved 2020-01-28
  113. ↑ "2.3.6.16. GET_COLORTABLE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 167–168, retrieved 2020-01-28
  114. ↑ "2.3.6.17. GET_DEVICEUNITS Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 168, retrieved 2020-01-28
  115. ↑ "2.3.6.18. GET_EXTENDED_TEXTMETRICS Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 168–169, retrieved 2020-01-28
  116. ↑ "2.3.6.19. GET_FACENAME Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 169, retrieved 2020-01-28
  117. ↑ "2.3.6.20. GET_PAIRKERNTABLE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 169–170, retrieved 2020-01-28
  118. ↑ "2.3.6.21. GET_PHYSPAGESIZE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 170, retrieved 2020-01-28
  119. ↑ "2.3.6.22. GET_PRINTINGOFFSET Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 170–171, retrieved 2020-01-28
  120. ↑ "2.3.6.23. GET_PS_FEATURESETTING Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 171, retrieved 2020-01-28
  121. ↑ "2.3.6.24. GET_SCALINGFACTOR Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 171–172, retrieved 2020-01-28
  122. ↑ "2.3.6.25. META_ESCAPE_ENHANCED_METAFILE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 172–173, retrieved 2020-01-28
  123. ↑ "2.3.6.26. METAFILE_DRIVER Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 173–174, retrieved 2020-01-28
  124. ↑ "2.3.6.27. NEWFRAME Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 174–175, retrieved 2020-01-28
  125. ↑ "2.3.6.28. NEXTBAND Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 174–175, retrieved 2020-01-28
  126. ↑ "2.3.6.29. PASSTHROUGH Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 175, retrieved 2020-01-28
  127. ↑ "2.3.6.30. POSTSCRIPT_DATA Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 176, retrieved 2020-01-28
  128. ↑ "2.3.6.31. POSTSCRIPT_IDENTIFY Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 176–177, retrieved 2020-01-28
  129. ↑ "2.3.6.32. POSTSCRIPT_IGNORE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 177, retrieved 2020-01-28
  130. ↑ "2.3.6.33. POSTSCRIPT_INJECTION Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 177–178, retrieved 2020-01-28
  131. ↑ "2.3.6.34. POSTSCRIPT_PASSTHROUGH Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 178, retrieved 2020-01-28
  132. ↑ "2.3.6.35. OPEN_CHANNEL Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 179, retrieved 2020-01-28
  133. ↑ "2.3.6.36. QUERY_DIBSUPPORT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 179–180, retrieved 2020-01-28
  134. ↑ "2.3.6.37. QUERY_ESCSUPPORT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 180, retrieved 2020-01-28
  135. ↑ "2.3.6.38. SET_COLORTABLE Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 180–181, retrieved 2020-01-28
  136. ↑ "2.3.6.39. SET_COPYCOUNT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 181, retrieved 2020-01-28
  137. ↑ "2.3.6.40. SET_LINECAP Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 181–182, retrieved 2020-01-28
  138. ↑ "2.3.6.41. SET_LINEJOIN Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 182–183, retrieved 2020-01-28
  139. ↑ "2.3.6.42. SET_MITERLIMIT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 183, retrieved 2020-01-28
  140. ↑ "2.3.6.43. SPCLPASSTHROUGH2 Record", [MS-WMF]: Windows Metafile Format Specification (PDF), pp. 183–184, retrieved 2020-01-28
  141. ↑ "2.3.6.44. STARTDOC Record", [MS-WMF]: Windows Metafile Format Specification (PDF), p. 184, retrieved 2020-01-28
  142. ↑ "Microsoft Windows WMF "SETABORTPROC" Arbitrary Code Execution". Secunia. Secunia Advisory: SA18255. Archived from the original on January 2, 2006.
  143. ↑ Pscript-Supported Escapes, Microsoft, retrieved 2020-01-28
  144. ↑ "The Windows MetaFile Backdoor?". GRC Security Now! (Podcast). Gibson Research Corporation. January 12, 2006. Retrieved 2020-01-28.
  145. ↑ Gibson, Steve (January 12, 2006), "Re: You won't want to miss tonight's Security Now!, #22", grc.news.feedback, retrieved 2020-01-28
  146. ↑ Russinovich, Mark (January 18, 2006), "Inside the WMF Backdoor", TechNet, Microsoft – via Microsoft Tech Community
  147. ↑ Ferrie, Peter (February 2, 2006), Inside the Windows Meta File Format (PDF), Virus Bulletin , retrieved 2020-01-24– via Symantec
  148. ↑ "1.3.1. Metafile Structure", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 17–18
  149. ↑ "2.3.4.2.1 EmfMetafileHeader Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 120
  150. ↑ "2.2.10 HeaderExtension1 Object", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 57–58
  151. ↑ "2.2.22 PixelFormatDescriptor Object", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 68–71
  152. ↑ "2.3.4.2.3 EmfMetafileHeaderExtension2 Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 122–124
  153. ↑ "You receive a "This file is an unsupported graphic format" error message when you try to insert a picture into a PowerPoint for Mac presentation". Microsoft. Archived from the original on 2014-04-19. Retrieved 2014-04-19.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.