Jump to content

User:Chris.sherlock/sandbox

From Wikipedia, the free encyclopedia
Chris.sherlock/sandbox
Filename extension
.wmf, .emf, .wmz, .emz
Internet media type
image/wmf, image/emf
Magic number01 00 09 00 00 03 (WMF hex signature)
01 00 00 00 (EMF/EMF+ hex signature)
Developed byMicrosoft
Initial release1990; 34 years ago (1990)
Latest release
15
12 September 2018; 6 years ago (2018-09-12)[1]
Type of formatImage file formats
Container forBitmaps, EPS data, among others
Extended toEMF and EMF+
Free format?Microsoft OSP

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.[2] 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 2017 revision 14 of the Windows Metafile Format specification is available for online reading or download as PDF.[1] 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

[edit]

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

[edit]
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

[edit]
Structures of original and placeable Windows metafiles[17]

WMF files were not originally designed to be device independent, meaning that you could not playback the file 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 rectable, 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

[edit]

Bitmap records manage and output bitmap images.

Name Description
META_BITBLT Specifies how to do a bit block transfer. These records can specify a bitmap to use as the source, or a region.[26]
META_DIBBITBLT Specifies 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_DIBSTRETCHBITBLT Specifies 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_SETDIBTODEV Specifies 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_STRETCHBLT Specifies how to do a bit block transfer, but allows for expansion or contraction of the image.[30]
META_STRETCHDIB Specifies 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

[edit]

Drawing records produce graphics output.

Name Description
META_ARC Draws an elliptical arc.[32]
META_CHORD Draws a chord.[33]
META_ELLIPSE Draws an elliptical arc.[34]
META_EXTFLOODFILL Fills an area with a brush.[35]
META_EXTTEXTOUT Draw text with font, background color and text color of the playback device context.[36]
META_FILLREGION Fills a region with a specified brush.[37]
META_FLOODFILL Fills an area with a brush.[38]
META_FRAMEREGION Draws a border around a region of the page with a brush.[39]
META_INVERTREGION Paints a region of the graphic with inverted colors.[40]
META_LINETO Draws a half-open line from the drawing position defined in the playback device context to a specified point.[41]
META_PAINTREGION Paint a region with the current brush specified in the playback device context.[42]
META_PATBLT Paint 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_PIE Draw 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_POLYLINE Draws a series of line segnments by connecting the points in a specified array.[45]
META_POLYGON Paints 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_POLYPOLYGON Paints 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_RECTANGLE Paints 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_ROUNDRECT Paints 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_SETPIXEL Sets the pixel at the specified coordinates to the specified color.[50]
META_TEXTOUT Outputs 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

[edit]

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]

Name Description
META_CREATEBRUSHINDIRECT Creates a brush object from a LogBrush (logical brush) object.[55]
META_CREATEFONTINDIRECT Creates a brush object from a font object.[56]
META_CREATEPALETTE Creates a palette object.
META_CREATEPATTERNBRUSH[57] Creates a brush object from a LogBrush (logical brush) object.[58]
META_CREATEPENINDIRECT Creates a pen object.[59]
META_CREATEREGION Creates a region object.[60]
META_DELETEOBJECT Delete a object.[61]
META_CREATEBRUSHINDIRECT Creates a brush object from a LogBrush (logical brush) object.[62]
META_DIBCREATEPATTERNBRUSH Creates a brush object from a device-independent bitmap.[63]
META_SELECTCLIPREGION Specifies the region object that will be the current clipping region.[64]
META_SELECTOBJECT Selects 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_SELECTPLAETTE Selects the logical palette for the playback device context.[66]

State records

[edit]

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

Name Description
META_ANIMATEPALETTE Redefines entries in the logical palette that is defined in the playback device context with a specified Palette Object.[68]
META_EXCLUDECLIPRECT Sets the clipping region that is defined in the playback device context to the existing clipping region minus a specified rectangle.[69]
META_INTERSECTCLIPRECT Sets 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_MOVETO Sets the output position in the playback device context to a specified point.[71]
META_OFFSETCLIPRGN Moves the clipping region that is defined in the playback device context by specified offsets.[72]
META_OFFSETVIEWPORTORG Moves the viewport origin in the playback device context by specified horizontal and vertical offsets.[73]
META_OFFSETWINDOWORG Moves the output window origin in the playback device context by specified horizontal and vertical offsets.[74]
META_REALIZEPALETTE Maps entries from the logical palette that is defined in the playback device context to the system palette.[75]
META_RESIZEPALETTE Redefines the size of the logical palette that is defined in the playback device context.[76]
META_RESTOREDC Restores the playback device context from a previously saved device context.[77]
META_SAVEDC Saves the playback device context for later retrieval.[78]
META_SCALEVIEWPORTEXT Scales 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_SCALEWINDOWEXT Scales 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_SETBKCOLOR Sets the background color in the playback device context to a specified color.[81]
META_SETBKMODE Sets the background mix mode in the playback device context.[82]
META_SETLAYOUT Defines the layout orientation in the playback device context.[83]
META_SETMAPMODE Defines the mapping mode in the playback device context.[84]
META_SETMAPPERFLAGS Defines the algorithm that the font mapper uses when it maps logical fonts to physical fonts.[85]
META_SETPALENTRIES Defines RGB color values in a range of entries in the logical palette that is defined in the playback device context.[86]
META_SETPOLYFILLMODE Defines polygon fill mode in the playback device context for graphics operations that fill polygons.[87]
META_SETRELABS Unused record.[88]
META_SETROP2 Defines the foreground raster operation mixing mode in the playback device context.[89]
META_SETSTRETCHBLTMODE Defines the bitmap stretching mode in the playback device context.[90]
META_SETTEXTALIGN Defines text-alignment values in the playback device context.[91]
META_SETTEXTCHAREXTRA Defines inter-character spacing for text justification in the playback device context.[92]
META_SETTEXTCOLOR Defines the text foreground color in the playback device context.[93]
META_SETTEXTJUSTIFICATION Defines the amount of space to add to break characters in a string of justified text.[94]
META_SETVIEWPORTEXT Defines the horizontal and vertical extents of the viewport in the playback device context.[95]
META_SETVIEWPORTORG Defines the viewport origin in the playback device context.[96]
META_SETWINDOWEXT Defines the horizontal and vertical extents of the output window in the playback device context.[97]
META_SETWINDOWORG Defines the output window origin in the playback device context.[98]

Escape records

[edit]
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.

Name Description
ABORTDOC Stops processing the current document. [99]
BEGIN_PATH Opens a path.[100]
CHECK_JPEGFORMAT Determines whether it can handle the given JPEG image.[101]
CHECK_PNGFORMAT Determines whether it can handle the given PNG image.[102]
CLIP_TO_PATH Applies a function to the current PostScript clipping path.[103]
CLOSE_CHANNEL Same as ENDDOC.[104]
DOWNLOAD_FACE Sets the font face name on the output device.[105]
DOWNLOAD_HEADER Downloads sets of PostScript procedures.[106]
DRAW_PATTERNRECT Draws a rectangle with a defined pattern.[107]
ENCAPSULATED_POSTSCRIPT Sends arbitrary encapsulated PostScript (EPS) data directly to the printer driver.[108]
END_PATH Ends a path.[109]
ENDDOC Notifies the printer driver that a new print job is ending.[110]
EPS_PRINTING Indicates the start and end of EPS printing.[111]
EXTTEXTOUT Draws text using the currently selected font, background color, and text color.[112]
GET_COLORTABLE Gets color table values from the printer driver.[113]
GET_DEVICEUNITS Gets the device units currently configured on the output device.[114]
GET_EXTENDED_TEXTMETRICS Gets the extended text metrics that are currently configured on the printer driver.[115]
GET_FACENAME Gets the font face name currently configured on the output device.[116]
GET_PAIRKERNTABLE Gets the font kern table currently defined on the output device.[117]
GET_PHYSPAGESIZE Retrieves the physical page size currently selected on the output device.[118]
GET_PRINTINGOFFSET Retrieves the offset from the upper-left corner of the physical page where the actual printing or drawing begins.[119]
GET_PS_FEATURESETTING Queries the printer driver for information about PostScript features supported on the output device.[120]
GET_SCALINGFACTOR Retrieves the scaling factors for the x-axis and the y-axis of a printer.[121]
META_ESCAPE_ENHANCED_METAFILE Used to embed an EMF metafile within a WMF metafile.[122]
METAFILE_DRIVER Queries the printer driver about its support for metafiles on the output device.[123]
NEWFRAME Notifies the printer driver that the application has finished writing to a page.[124]
NEXTBAND Notifies the printer driver that the application has finished writing to a band.[125]
PASSTHROUGH Passes through arbitrary data to the printer driver.[126]
POSTSCRIPT_DATA Sends arbitrary PostScript data to the output device.[127]
POSTSCRIPT_IDENTIFY Sets the printer driver to either PostScript-centric or GDI-centric mode.[128]
POSTSCRIPT_IGNORE Notifies the output device to ignore PostScript data.[129]
POSTSCRIPT_INJECTION Inserts a block of raw data into a PostScript stream.[130]
POSTSCRIPT_PASSTHROUGH Sends arbitrary data directly to a printer driver, which is expected to process this data only when in PostScript mode.[131]
OPEN_CHANNEL Acts the same as STARTDOC, with a NULL document and output filename, and data in raw mode.[132]
QUERY_DIBSUPPORT Queries the printer driver about its support for DIBs on the output device.[133]
QUERY_ESCSUPPORT Queries the printer driver to determine whether a specific WMF escape function is supported on the output device.[134]
SET_COLORTABLE Sets color table values.[135]
SET_COPYCOUNT Sets the number of copies.[136]
SET_LINECAP Specifies the line-ending mode to use in drawing to the output device.[137]
SET_LINEJOIN Specifies the line-joining mode to use in drawing to the output device.[138]
SET_MITERLIMIT Sets the limit for the length of miter joins to use in drawing to the output device.[139]
SPCLPASSTHROUGH2 Enables documents to include private procedures and other arbitrary data in documents.[140]
STARTDOC Notifies 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 from Gibson Research Corporation 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 1990’s 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

[edit]

Like WMF files, EMF files use a series of records to draw images that are rendered onto a playback device context. However, EMF files are device-independent, which is accomplished via a header that can define the pixel format and allow accurate measurement of distances on device surfaces. Furthermore, EMF files use coordinate spaces and transformations to stretch, rotate, squeeze, rotate, shear, reflect and translate graphics output on a Cartesian plane.

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.

Coordinate systems

[edit]

Working in coordinate spaces allows EMF files to map to the four Windows GDI spaces, which are defined as world space, page space, device space, and physical device space.[148] In practice, graphical objects are either first mapped from the world space if set (which must first specify a two-dimensional linear transformation between world space and page space for the specified device context)[149] or page space if not.[150] For a graphical object to be painted, it must be processed through a coordinate transformation pipeline:

  1. If the world space has been set, then the graphics will exist in a world coordinate system. The world space is 232 units high and 232 units wide.[150]
  2. A graphical object will be next transformed into the page space if the world space is set, otherwise the coordinate system starts from the page space. This space uses a logical (device-independent) coordinate system.[151] Graphical objects use a world space to page space transformation to support scaling, translation, rotation, shearing, and reflection.[152]
  3. Graphics in page spaces are mapped to a device space. The page space is commonly referred to as the window and the device space is referred to as the viewport. The window and viewport each have an origin and an extent consisting of the width and height. Each unit of the page space maps to a unit in the device space via one of six predefined mapping modes (MM_HIENGLISH[a], MM_LOENGLISH[b], MM_HIMETRIC[c], MM_LOMETRIC[d], MM_TEXT[e], and MM_TWIPS[f]) or by one of two user-defined mapping modes (MM_ISOTROPIC[g] and MM_ANISOTROPIC[h]). Using the origin and extents of the window and viewports, a translation is performed to convert the graphical object from page space to device space.[153]
  4. The final step is to convert to the physical device space, or the client area of the physical output device. Examples of this are the area of a computer window that is displaying, the desktop, or the physical dimensions of a page of paper that is being printed on.[150]

Control records

[edit]
Windows Enhanced Metafile structure, showing the three types of headers

Control records consist of and one of three EMF headers and an end of file marker (EMR_EOF) followed by an optional palette.[154]

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.[155]

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.[156] 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.[157] 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.[158] 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.[159]

Clipping records

[edit]

EMF files have a class of record that deal with clipping. The following record types perform clipping operations:

Name Description
EMR_EXCLUDECLIPRECT Remove a rectangular region from the current clipping region[160]
EMR_EXTSELECTCLIPRGN Combine a region with the current clipping region[161]
EMR_INTERSECTCLIPRECT Create a clipping region from the intersection of a region from the current clipping region[162]
EMR_OFFSETCLIPRGN Setup a new clipping region from the current clipping region, only moved by a specified offset[163]
EMR_SELECTCLIPPATH Specify a clipping region as the currently region plus the current path bracket[164]
EMR_SETMETARGN Intersect the currently metaregion with the current clipping region if the current metaregion is not null. If the metaregion is null, then set the metaregion to the current clipping region. After the metaregion is set then set the current clipping region to null.[165]

Comments records

[edit]

Comment records allow private data to be included in EMF files.[166] When EMF files are read, comments records are skipped by applications that cannot read them.[167] Whilst you can include arbitrary private data,[168] the most notable usage of comment records are EMF+ files, which are actually records contained in an EMF comment and such files can be considered EMF+ only or EMF+ dual format — the former means that you can just use EMF+ records to draw the image fully, the later means the file contains both EMF and EMF+ records; you must only one type to draw the image.[169] However, Microsoft also takes advantage of comment records to also produce EMFSPOOL files, which store portable definitions of print jobs that output graphical images.[170]

Another type of comment record in an EMF is called a public comment record. Public records can group drawing records via an EMF_COMMENT_BEGINGROUP[171] and EMF_COMMENT_ENDGROUP records.[172] Public comments can also contain images in multiple graphics formats. [173][174] This includes EPS data[175] and interestingly can also contain embedded EMF images within the EMF image itself.[175] WMF files can also be embedded in EMF files via a non-multiformat comment type named the EMR_COMMENT_WINDOW_METAFILE comment record.[168]

Name Description
EMR_COMMENT Arbitrary data[176]
EMR_COMMENT_EMFPLUS EMF+ records [177]
EMR_COMMENT_EMFSPOOL Embedded EMFSPOOL records
EMR_COMMENT_EMFPLUS EMF+ records[178]
EMR_COMMENT_PUBLIC Extensions for EMF processing[179]

Drawing records

[edit]

Bitmap records

[edit]

Object creation records

[edit]

Object manipulation records

[edit]

OpenGL records

[edit]

Path bracket records

[edit]

State records

[edit]

Transform records

[edit]

Escape records

[edit]

EMF+

[edit]

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),[180] which are basically gzip compressed WMF and EMF files correspondingly.

Clipping records

[edit]

EMF files have a class of record that deal with clipping. The following record types perform clipping operations:

Name Description
EmfPlusOffsetClip Apply a translation tranformation on the current clipping region.[181]
EmfPlusResetClip Resets the the current clipping region - the clipping region will take up the entire region.[182]
EmfPlusSetClipPath Combine the current clipping region with a graphics path.[183]
EmfPlusSetClipRect Combine the current clipping region with a rectangle.[184]
EmfPlusSetClipRegion Combine the current clipping region with a region.[185]

See also

[edit]

Notes

[edit]
  1. ^ Each unit in page space is mapped to 0.001 inch in device space.
  2. ^ Each unit in page space is mapped to 0.01 inch in device space.
  3. ^ Each unit in page space is mapped to 0.01 millimeter in device space.
  4. ^ Each unit in page space is mapped to 0.1 millimeter in device space.
  5. ^ Each unit in page space is mapped to one pixel, in other words no scaling is performed
  6. ^ Each unit in page space is mapped to one twentieth of a printer's point (1/1440 inch).
  7. ^ Each unit in page space is mapped to an application-specified unit in device space, with an axis equally scaled and the an application defined axis orientation
  8. ^ Each unit in page space is mapped to an application-specified unit in device space, where the axis may or may not be equally scaled and the orientation of the axis is specified by the application

References

[edit]
  1. ^ a b "[MS-WMF]: Windows Metafile Format". MSDN. 2015-06-30. Retrieved 2015-07-26.
  2. ^ Windows Metafile Format (PDF), Microsoft, p. 16
  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. ^ a b Enhanced Metafiles in Win32, Microsoft Developer Network Technology Group, June 10, 1993
  10. ^ a b 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, 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, p. 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. ^ a b c "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, p. 103-106, retrieved 2020-01-24
  28. ^ "2.3.1.3 META_DIBSTRETCHBITBLT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), Microsoft, p. 106-108, retrieved 2020-01-24
  29. ^ "2.3.1.4 META_SETDIBTODEV Record", [MS-WMF]: Windows Metafile Format Specification (PDF), Microsoft, p. 108-109, retrieved 2020-01-24
  30. ^ "2.3.1.5 META_STRETCHBLT Record", [MS-WMF]: Windows Metafile Format Specification (PDF), Microsoft, p. 109-110, retrieved 2020-01-24
  31. ^ "2.3.1.6 META_STRETCHDIB Record", [MS-WMF]: Windows Metafile Format Specification (PDF), Microsoft, p. 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. ^ a b "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, 2008. {{cite web}}: |archive-date= / |archive-url= timestamp mismatch; January 2, 2006 suggested (help)
  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. ^ "Coordinate Spaces and Transformations", Windows GDI, Microsoft Corporation, May 31, 2018, retrieved 2020-02-10
  149. ^ "Windows GDI", SetWorldTransform function, Microsoft Corporation, May 31, 2018, retrieved 2020-02-10
  150. ^ a b c "Transformation of Coordinate Spaces", Windows GDI, Microsoft Corporation, May 31, 2018, retrieved 2020-02-10
  151. ^ "1.1 Glossary", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 10–16
  152. ^ "World-Space to Page-Space Transformations", Windows GDI, Microsoft Corporation, May 31, 2018, retrieved 2020-02-10
  153. ^ "Mapping Modes and Translations", Windows GDI, Microsoft Corporation, May 31, 2018, retrieved 2020-02-10
  154. ^ "1.3.1. Metafile Structure", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 17–18
  155. ^ "2.3.4.1 EMR_EOF Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 116–117
  156. ^ "2.3.4.2.1 EmfMetafileHeader Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 120
  157. ^ "2.2.10 HeaderExtension1 Object", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 57–58
  158. ^ "2.2.22 PixelFormatDescriptor Object", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 68–71
  159. ^ "2.3.4.2.3 EmfMetafileHeaderExtension2 Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 122–124
  160. ^ "2.3.2.1 EMR_EXCLUDECLIPRECT Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 104–105
  161. ^ "2.3.2.2 EMR_EXTSELECTCLIPRGN Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 105
  162. ^ "2.3.2.3 EMR_INTERSECTCLIPRECT Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 106–107
  163. ^ "2.3.2.4 EMR_OFFSETCLIPRGN Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 106
  164. ^ "2.3.2.5 EMR_SELECTCLIPPATH Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 106–107
  165. ^ "2.3.2 Clipping Record Types", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 103
  166. ^ "2.3.3 Comment Record Types", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 107–114
  167. ^ Chand, Manesh (2004), "Advanced Imaging, 8.2.3 Enhanced Metafiles", GDI+ Programming with C#, MSDN (unsourced): Addison-Wesley, p. 366, ISBN 0-321-16077-0
  168. ^ a b "2.3.3.1 EMR_COMMENT Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 108-109 Cite error: The named reference "wmfinemf" was defined multiple times with different content (see the help page).
  169. ^ Leonard, Sean (September 2016). "Enhanced Metafile Media Type Registration Application". Windows Image Media Types. IETF. p. 6. doi:10.17487/RFC7903. ISSN 2070-1721. RFC 7903. Retrieved February 8, 2020.
  170. ^ "1. Introduction", [MS-EMFSPOOL]: Enhanced Metafile Spool Format (PDF), Microsoft, p. 7
  171. ^ "2.3.3.4.1 EMR_COMMENT_BEGINGROUP Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 111–112
  172. ^ "2.3.3.4.2 EMR_COMMENT_ENDGROUP Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 112–113
  173. ^ "2.1.14 FormatSignature Enumeration", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 34
  174. ^ "2.1.14 FormatSignature Enumeration", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 34
  175. ^ a b "2.3.3.4.3 EMR_COMMENT_MULTIFORMATS Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 113-114
  176. ^ "2.3.3.1 EMR_COMMENT Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 108–109
  177. ^ "2.3.3.2 EMR_COMMENT_EMFPLUS Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 109
  178. ^ "2.3.3.3 EMR_COMMENT_EMFPLUS Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 109–110
  179. ^ "2.3.3.4 EMR_COMMENT_PUBLIC Record", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 110–115
  180. ^ "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.
  181. ^ "2.3.1.1 EmfPlusOffsetClip", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 133
  182. ^ "2.3.1.2 EmfPlusOffsetClip", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, p. 133
  183. ^ "2.3.1.3 EmfPlusSetClipPath", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 134–135
  184. ^ "2.3.1.4 EmfPlusSetClipRectangle", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 134–135
  185. ^ "2.3.1.4 EmfPlusSetClipRegion", [MS-EMF]: Enhanced Metafile Format (PDF), Microsoft, pp. 136–137
[edit]

Category:Graphics file formats Category:Vector graphics Category:Microsoft Windows multimedia technology

Retrieved from "https://en.wikipedia.org/w/index.php?title=User:Chris.sherlock/sandbox&oldid=1091350178"