Misplaced Pages

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.

Essentially, a metafile stores a list of records consisting of drawing commands, property definitions and graphics objects to display an image on screen. 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. 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. 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+.

History

The original 16 bit WMF file format was fully specified in volume 4 of the 1992 Windows 3.1 SDK documentation (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. In September 2006, Microsoft again published the WMF file format specification in a more complete form in the context of the Microsoft Open Specification Promise, promising to not assert patent rights to file format implementors.

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 " application, location, or scaling comments in the metafiles... Others added headers to the metafile that provided various application-specific information", causing major compatibility issues. Thus, in 1992 with Windows NT 3.1, Microsoft introduced the Enhanced Metafile format (EMF) — a format which was based on the Win32 API and with which they built-in device independence. — these were also known as NT metafiles. 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.

Metafile structure

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. 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.

WMF

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", 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. This was later incorporated into the WMF format by Microsoft, starting in Windows 2000.

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

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.

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.

Drawing records

Drawing records produce graphics output.

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, which is itself part of a DeviceIndependentBitmap object. A graphics object, however, specifies parameters for graphics output and during playback of the WMF it sets up the playback device context.

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).

State records

State records manage the graphics properties of the playback device context.

Escape records

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.

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." 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. 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, 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.

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.

EMF

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.

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. 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. 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. 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.

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), 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

• PostScript
• Vector Markup Language (VML)
• Scalable Vector Graphics (SVG)

References

1. Windows Metafile Format (PDF), Microsoft, p. 16
2. ": Windows Metafile Format". MSDN. 2021-04-26. Retrieved 2023-09-13.
3. : Enhanced Metafile Format (PDF), Microsoft, p. 17
4. : 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. ": Windows Metafile Format Specification". Retrieved 2008-06-01.
8. "Microsoft Open Specification Promise". Microsoft. Retrieved 2008-06-01.
9. ^ Enhanced Metafiles in Win32, Microsoft Developer Network Technology Group, June 10, 1993
10. ^ 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", : Enhanced Metafile Format (PDF), Microsoft, p. 187
15. "3.1.1.1 EMF Object Table", : Windows Metafile Format Specification (PDF), Microsoft, pp. 212–214
16. : 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.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", : Windows Metafile Format Specification (PDF), Microsoft, p. 13, retrieved 2020-01-24
26. "2.3.1.1 META_BITBLT Record", : Windows Metafile Format Specification (PDF), pp. 101–103, retrieved 2020-01-24
27. "2.3.1.2 META_DIBBITBLT Record", : Windows Metafile Format Specification (PDF), Microsoft, pp. 103–106, retrieved 2020-01-24
28. "2.3.1.3 META_DIBSTRETCHBITBLT Record", : Windows Metafile Format Specification (PDF), Microsoft, pp. 106–108, retrieved 2020-01-24
29. "2.3.1.4 META_SETDIBTODEV Record", : Windows Metafile Format Specification (PDF), Microsoft, pp. 108–109, retrieved 2020-01-24
30. "2.3.1.5 META_STRETCHBLT Record", : Windows Metafile Format Specification (PDF), Microsoft, pp. 109–110, retrieved 2020-01-24
31. "2.3.1.6 META_STRETCHDIB Record", : Windows Metafile Format Specification (PDF), Microsoft, pp. 103–106, retrieved 2020-01-24
32. "2.3.3.1 META_ARC Record", : Windows Metafile Format Specification (PDF), pp. 101–103, retrieved 2020-01-24
33. "2.3.3.2 META_CHORD Record", : Windows Metafile Format Specification (PDF), pp. 117–118, retrieved 2020-01-24
34. "2.3.3.3 META_ELLIPSE Record", : Windows Metafile Format Specification (PDF), p. 119, retrieved 2020-01-24
35. "2.3.3.4 META_EXTFLOODFILL Record", : Windows Metafile Format Specification (PDF), pp. 119–120, retrieved 2020-01-24
36. "2.3.3.5 META_EXTTEXTOUT Record", : Windows Metafile Format Specification (PDF), pp. 119–120, retrieved 2020-01-24
37. "2.3.3.6 META_FILLREGION Record", : Windows Metafile Format Specification (PDF), p. 121, retrieved 2020-01-24
38. "2.3.3.7 META_FLOODFILL Record", : Windows Metafile Format Specification (PDF), pp. 119–120, retrieved 2020-01-24
39. "2.3.3.8 META_FRAMEREGION Record", : Windows Metafile Format Specification (PDF), pp. 122–123, retrieved 2020-01-24
40. "2.3.3.9 META_INVERTREGION Record", : Windows Metafile Format Specification (PDF), p. 123, retrieved 2020-01-24
41. "2.3.3.10 META_LINETO Record", : Windows Metafile Format Specification (PDF), pp. 123–124, retrieved 2020-01-24
42. "2.3.3.11 META_PAINTREGION Record", : Windows Metafile Format Specification (PDF), p. 124, retrieved 2020-01-24
43. "2.3.3.12 META_PATBLT Record", : Windows Metafile Format Specification (PDF), pp. 124–125, retrieved 2020-01-24
44. "2.3.3.13 META_PIE Record", : Windows Metafile Format Specification (PDF), pp. 125–126, retrieved 2020-01-24
45. "2.3.3.14 META_POLYLINE Record", : Windows Metafile Format Specification (PDF), p. 126, retrieved 2020-01-24
46. "2.3.3.15 META_POLYGON Record", : Windows Metafile Format Specification (PDF), p. 127, retrieved 2020-01-24
47. "2.3.3.16 META_POLYPOLYGON Record", : Windows Metafile Format Specification (PDF), pp. 127–128, retrieved 2020-01-24
48. "2.3.3.17 META_RECTANGLE Record", : Windows Metafile Format Specification (PDF), pp. 127–128, retrieved 2020-01-24
49. "2.3.3.18 META_ROUNDRECT Record", : Windows Metafile Format Specification (PDF), pp. 128–129, retrieved 2020-01-24
50. "2.3.3.19 META_SETPIXEL Record", : Windows Metafile Format Specification (PDF), pp. 129–130, retrieved 2020-01-24
51. "2.3.3.20 META_TEXTOUT Record", : Windows Metafile Format Specification (PDF), p. 130, retrieved 2020-01-24
52. "2.2.2.2. BitmapCoreHeader Object", : Windows Metafile Format Specification (PDF), p. 85, retrieved 2020-01-25
53. "2.2.2.9. DeviceIndependentBitmap Object", : Windows Metafile Format Specification (PDF), p. 91, retrieved 2020-01-25
54. ^ "2.2.1. Graphics Objects", : Windows Metafile Format Specification (PDF), p. 79, retrieved 2020-01-25
55. "2.3.4.1 META_CREATEBRUSHINDIRECT Record", : Windows Metafile Format Specification (PDF), pp. 131–132, retrieved 2020-01-25
56. "2.3.4.2 META_CREATEFONTINDIRECT Record", : Windows Metafile Format Specification (PDF), p. 132, retrieved 2020-01-25
57. "2.3.4.4 META_CREATEPATTERNBRUSH Record", : Windows Metafile Format Specification (PDF), pp. 133–135, retrieved 2020-01-25
58. "2.3.4.3 META_CREATEPALETTE Record", : Windows Metafile Format Specification (PDF), pp. 132–133, retrieved 2020-01-25
59. "2.3.4.5 META_CREATEPENINDIRECT Record", : Windows Metafile Format Specification (PDF), pp. 134–135, retrieved 2020-01-25
60. "2.3.4.6 META_CREATEREGION Record", : Windows Metafile Format Specification (PDF), p. 135, retrieved 2020-01-25
61. "2.3.4.7 META_DELETEOBJECT Record", : Windows Metafile Format Specification (PDF), p. 135, retrieved 2020-01-25
62. "2.3.4.8 META_CREATEBRUSHINDIRECT Record", : Windows Metafile Format Specification (PDF), pp. 135–136, retrieved 2020-01-25
63. "2.3.4.9 META_DIBCREATEPATTERNBRUSH Record", : Windows Metafile Format Specification (PDF), pp. 136–137, retrieved 2020-01-25
64. "2.3.4.10 META_SELECTCLIPREGION Record", : Windows Metafile Format Specification (PDF), p. 137, retrieved 2020-01-25
65. "2.3.4.11 META_SELECTOBJECT Record", : Windows Metafile Format Specification (PDF), pp. 137–138, retrieved 2020-01-25
66. "2.3.4.11 META_SELECTPALETTE Record", : Windows Metafile Format Specification (PDF), p. 139, retrieved 2020-01-25
67. "2.3.5 State Record Types", : Windows Metafile Format Specification (PDF), p. 138, retrieved 2020-01-28
68. "2.3.5.1 META_ANIMATEPALETTE Record", : Windows Metafile Format Specification (PDF), p. 140, retrieved 2020-01-28
69. "2.3.5.2 META_EXCLUDECLIPRECT Record", : Windows Metafile Format Specification (PDF), pp. 140–141, retrieved 2020-01-28
70. "2.3.5.3 META_INTERSECTCLIPRECT Record", : Windows Metafile Format Specification (PDF), pp. 141–142, retrieved 2020-01-28
71. "2.3.5.1 META_MOVETO Record", : Windows Metafile Format Specification (PDF), p. 142, retrieved 2020-01-28
72. "2.3.5.4 META_OFFSETCLIPRGN Record", : Windows Metafile Format Specification (PDF), pp. 142–143, retrieved 2020-01-28
73. "2.3.5.5 META_OFFSETVIEWPORTORG Record", : Windows Metafile Format Specification (PDF), p. 143, retrieved 2020-01-28
74. "2.3.5.6 META_OFFSETWINDOWORG Record", : Windows Metafile Format Specification (PDF), pp. 131–132, retrieved 2020-01-28
75. "2.3.5.7 META_REALIZEPALETTE Record", : Windows Metafile Format Specification (PDF), pp. 143–144, retrieved 2020-01-28
76. "2.3.5.8 META_RESIZEPALETTE Record", : Windows Metafile Format Specification (PDF), p. 144, retrieved 2020-01-28
77. "2.3.5.9 META_RESTOREDC Record", : Windows Metafile Format Specification (PDF), p. 145, retrieved 2020-01-28
78. "2.3.5.10 META_SAVEDC Record", : Windows Metafile Format Specification (PDF), p. 145, retrieved 2020-01-28
79. "2.3.5.11 META_SCALEVIEWPORTEXT Record", : Windows Metafile Format Specification (PDF), pp. 145–146, retrieved 2020-01-28
80. "2.3.5.12 META_SCALEWINDOWEXT Record", : Windows Metafile Format Specification (PDF), pp. 146–147, retrieved 2020-01-28
81. "2.3.5.13 META_SETBKCOLOR Record", : Windows Metafile Format Specification (PDF), p. 147, retrieved 2020-01-28
82. "2.3.5.14 META_SETBKMODE Record", : Windows Metafile Format Specification (PDF), pp. 147–148, retrieved 2020-01-28
83. "2.3.5.15 META_SETLAYOUT Record", : Windows Metafile Format Specification (PDF), p. 148, retrieved 2020-01-28
84. "2.3.5.16 META_SETMAPMODE Record", : Windows Metafile Format Specification (PDF), pp. 148–149, retrieved 2020-01-28
85. "2.3.5.17 META_SETMAPPERFLAGS Record", : Windows Metafile Format Specification (PDF), pp. 131–132, retrieved 2020-01-28
86. "2.3.5.18 META_ANIMATEPALETTE Record", : Windows Metafile Format Specification (PDF), p. 149, retrieved 2020-01-28
87. "2.3.5.19 META_SETPALENTRIES Record", : Windows Metafile Format Specification (PDF), pp. 149–150, retrieved 2020-01-28
88. "2.3.5.20 META_SETRELABS Record", : Windows Metafile Format Specification (PDF), p. 150, retrieved 2020-01-28
89. "2.3.5.21 META_SETROP2 Record", : Windows Metafile Format Specification (PDF), p. 151, retrieved 2020-01-28
90. "2.3.5.1 META_SETSTRETCHBLTMODE Record", : Windows Metafile Format Specification (PDF), pp. 151–152, retrieved 2020-01-28
91. "2.3.5.22 META_SETTEXTALIGN Record", : Windows Metafile Format Specification (PDF), p. 152, retrieved 2020-01-28
92. "2.3.5.1 META_SETTEXTCHAREXTRA Record", : Windows Metafile Format Specification (PDF), pp. 152–153, retrieved 2020-01-28
93. "2.3.5.23 META_SETTEXTCOLOR Record", : Windows Metafile Format Specification (PDF), p. 153, retrieved 2020-01-28
94. "2.3.5.24 META_SETTEXTJUSTIFICATION Record", : Windows Metafile Format Specification (PDF), pp. 153–154, retrieved 2020-01-28
95. "2.3.5.25 META_SETVIEWPORTEXT Record", : Windows Metafile Format Specification (PDF), p. 154, retrieved 2020-01-28
96. "2.3.5.26 META_SETVIEWPORTORG Record", : Windows Metafile Format Specification (PDF), pp. 154–155, retrieved 2020-01-28
97. "2.3.5.27 META_SETWINDOWEXT Record", : Windows Metafile Format Specification (PDF), p. 155, retrieved 2020-01-28
98. "2.3.5.28 META_SETWINDOWORG Record", : Windows Metafile Format Specification (PDF), p. 155, retrieved 2020-01-28
99. "2.3.6.2. ABORTDOC Record", : Windows Metafile Format Specification (PDF), pp. 158–159, retrieved 2020-01-28
100. "2.3.6.3. BEGIN_PATH Record", : Windows Metafile Format Specification (PDF), p. 159, retrieved 2020-01-28
101. "2.3.6.4. CHECK_JPEGFORMAT Record", : Windows Metafile Format Specification (PDF), pp. 159–160, retrieved 2020-01-28
102. "2.3.6.5. CHECK_PNGFORMAT Record", : Windows Metafile Format Specification (PDF), p. 160, retrieved 2020-01-28
103. "2.3.6.6. CLIP_TO_PATH Record", : Windows Metafile Format Specification (PDF), p. 160, retrieved 2020-01-28
104. "2.3.6.7. CLOSE_CHANNEL Record", : Windows Metafile Format Specification (PDF), p. 162, retrieved 2020-01-28
105. "2.3.6.8. DOWNLOAD_FACE Record", : Windows Metafile Format Specification (PDF), pp. 162–163, retrieved 2020-01-28
106. "2.3.6.9. DOWNLOAD_HEADER Record", : Windows Metafile Format Specification (PDF), pp. 158–159, retrieved 2020-01-28
107. "2.3.6.10. DRAW_PATTERNRECT Record", : Windows Metafile Format Specification (PDF), pp. 163–164, retrieved 2020-01-28
108. "2.3.6.11. ENCAPSULATED_POSTSCRIPT Record", : Windows Metafile Format Specification (PDF), p. 164, retrieved 2020-01-28
109. "2.3.6.12. END_PATH Record", : Windows Metafile Format Specification (PDF), pp. 164–165, retrieved 2020-01-28
110. "2.3.6.13. ENDDOC Record", : Windows Metafile Format Specification (PDF), p. 165, retrieved 2020-01-28
111. "2.3.6.14. EPS_PRINTING Record", : Windows Metafile Format Specification (PDF), pp. 165–166, retrieved 2020-01-28
112. "2.3.6.15. EXTTEXTOUT Record", : Windows Metafile Format Specification (PDF), pp. 166–167, retrieved 2020-01-28
113. "2.3.6.16. GET_COLORTABLE Record", : Windows Metafile Format Specification (PDF), pp. 167–168, retrieved 2020-01-28
114. "2.3.6.17. GET_DEVICEUNITS Record", : Windows Metafile Format Specification (PDF), p. 168, retrieved 2020-01-28
115. "2.3.6.18. GET_EXTENDED_TEXTMETRICS Record", : Windows Metafile Format Specification (PDF), pp. 168–169, retrieved 2020-01-28
116. "2.3.6.19. GET_FACENAME Record", : Windows Metafile Format Specification (PDF), p. 169, retrieved 2020-01-28
117. "2.3.6.20. GET_PAIRKERNTABLE Record", : Windows Metafile Format Specification (PDF), pp. 169–170, retrieved 2020-01-28
118. "2.3.6.21. GET_PHYSPAGESIZE Record", : Windows Metafile Format Specification (PDF), p. 170, retrieved 2020-01-28
119. "2.3.6.22. GET_PRINTINGOFFSET Record", : Windows Metafile Format Specification (PDF), pp. 170–171, retrieved 2020-01-28
120. "2.3.6.23. GET_PS_FEATURESETTING Record", : Windows Metafile Format Specification (PDF), p. 171, retrieved 2020-01-28
121. "2.3.6.24. GET_SCALINGFACTOR Record", : Windows Metafile Format Specification (PDF), pp. 171–172, retrieved 2020-01-28
122. "2.3.6.25. META_ESCAPE_ENHANCED_METAFILE Record", : Windows Metafile Format Specification (PDF), pp. 172–173, retrieved 2020-01-28
123. "2.3.6.26. METAFILE_DRIVER Record", : Windows Metafile Format Specification (PDF), pp. 173–174, retrieved 2020-01-28
124. "2.3.6.27. NEWFRAME Record", : Windows Metafile Format Specification (PDF), pp. 174–175, retrieved 2020-01-28
125. "2.3.6.28. NEXTBAND Record", : Windows Metafile Format Specification (PDF), pp. 174–175, retrieved 2020-01-28
126. "2.3.6.29. PASSTHROUGH Record", : Windows Metafile Format Specification (PDF), p. 175, retrieved 2020-01-28
127. "2.3.6.30. POSTSCRIPT_DATA Record", : Windows Metafile Format Specification (PDF), p. 176, retrieved 2020-01-28
128. "2.3.6.31. POSTSCRIPT_IDENTIFY Record", : Windows Metafile Format Specification (PDF), pp. 176–177, retrieved 2020-01-28
129. "2.3.6.32. POSTSCRIPT_IGNORE Record", : Windows Metafile Format Specification (PDF), p. 177, retrieved 2020-01-28
130. "2.3.6.33. POSTSCRIPT_INJECTION Record", : Windows Metafile Format Specification (PDF), pp. 177–178, retrieved 2020-01-28
131. "2.3.6.34. POSTSCRIPT_PASSTHROUGH Record", : Windows Metafile Format Specification (PDF), p. 178, retrieved 2020-01-28
132. "2.3.6.35. OPEN_CHANNEL Record", : Windows Metafile Format Specification (PDF), p. 179, retrieved 2020-01-28
133. "2.3.6.36. QUERY_DIBSUPPORT Record", : Windows Metafile Format Specification (PDF), pp. 179–180, retrieved 2020-01-28
134. "2.3.6.37. QUERY_ESCSUPPORT Record", : Windows Metafile Format Specification (PDF), p. 180, retrieved 2020-01-28
135. "2.3.6.38. SET_COLORTABLE Record", : Windows Metafile Format Specification (PDF), pp. 180–181, retrieved 2020-01-28
136. "2.3.6.39. SET_COPYCOUNT Record", : Windows Metafile Format Specification (PDF), p. 181, retrieved 2020-01-28
137. "2.3.6.40. SET_LINECAP Record", : Windows Metafile Format Specification (PDF), pp. 181–182, retrieved 2020-01-28
138. "2.3.6.41. SET_LINEJOIN Record", : Windows Metafile Format Specification (PDF), pp. 182–183, retrieved 2020-01-28
139. "2.3.6.42. SET_MITERLIMIT Record", : Windows Metafile Format Specification (PDF), p. 183, retrieved 2020-01-28
140. "2.3.6.43. SPCLPASSTHROUGH2 Record", : Windows Metafile Format Specification (PDF), pp. 183–184, retrieved 2020-01-28
141. "2.3.6.44. STARTDOC Record", : 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, archived from the original (PDF) on May 16, 2008, retrieved 2020-01-24 – via Symantec
148. "1.3.1. Metafile Structure", : Enhanced Metafile Format (PDF), Microsoft, pp. 17–18
149. "2.3.4.2.1 EmfMetafileHeader Record", : Enhanced Metafile Format (PDF), Microsoft, p. 120
150. "2.2.10 HeaderExtension1 Object", : Enhanced Metafile Format (PDF), Microsoft, pp. 57–58
151. "2.2.22 PixelFormatDescriptor Object", : Enhanced Metafile Format (PDF), Microsoft, pp. 68–71
152. "2.3.4.2.3 EmfMetafileHeaderExtension2 Record", : 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.

External links

• Windows Metafile Format Specification from Microsoft
• Metafiles – Windows applications
• File Format Summary at fileformat.info
• Windows Metafile FAQ

• Graphics file formats
• Vector graphics
• Microsoft Windows multimedia technology