Export (0) Print
Expand All

5 Appendix A: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs:

  • Windows NT 3.1 operating system

  • Windows NT 3.5 operating system

  • Windows NT 3.51 operating system

  • Windows NT 4.0 operating system

  • Microsoft Windows 98 operating system

  • Windows Millennium Edition operating system

  • Windows 2000 operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system

  • Windows Server 2008 operating system

  • Windows 7 operating system

  • Windows Server 2008 R2 operating system

  • Windows 8 operating system

  • Windows Server 2012 operating system

  • Windows 8.1 operating system

  • Windows Server 2012 R2 operating system

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.

<1> Section 1.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition do not support WCS color management.

<2> Section 1.3.1: EMF metafiles have changed over the years with the evolution of Windows operating systems. They were introduced with 32-bit Windows and replaced the 16-bit WMFmetafile[MS-WMF] as the Windows standard.

<3> Section 1.3.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows NT 4.0, Windows 98, and Windows Millennium Edition: This form of EMFmetafile is not supported.

<4> Section 1.3.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows NT 4.0, Windows 98, Windows Millennium Edition, Windows 2000: This form of EMFmetafile is not supported.

<5> Section 1.4: The EMF format supersedes WMF format, which was used in 16-bit Windows versions.

<6> Section 1.4: Windows applications that use the Graphics Device Interface, Extended (GDI)+ API can create EMFmetafiles that contain EMF+ records. See [MSDN-GDI+] for more information.

<7> Section 1.6: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition: EMF extension 1 is not supported.

<8> Section 1.6: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, Windows Millennium Edition, Windows NT 4.0, and Windows 2000: EMF extension 2 is not supported.

<9> Section 2.1.1: Only Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 support EMR_SETMAPPERFLAGS.

<10> Section 2.1.1: Windows GDI emulates EMR_EXTTEXTOUTA with an EMR_EXTTEXTOUTW record.

<11> Section 2.1.1: Windows NT 3.1 is the only Windows version in which GDI uses EMR_POLYTEXTOUTA records for text output. All other versions emulate EMR_POLYTEXTOUTA with EMR_EXTTEXTOUTW records.

<12> Section 2.1.1: Windows NT 3.1 is the only Windows version in which GDI uses EMR_POLYTEXTOUTW records for text output. All other versions emulate EMR_POLYTEXTOUTW with EMR_EXTTEXTOUTW records.

<13> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_SETICMMODE.

<14> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_CREATECOLORSPACE.

<15> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_SETCOLORSPACE.

<16> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_DELETECOLORSPACE.

<17> Section 2.1.1: Windows uses an EMR_DELETEOBJECT record to delete a logical color space object.

<18> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_GLSRECORD.

<19> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_GLSBOUNDEDRECORD.

<20> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_PIXELFORMAT.

<21> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_COLORCORRECTPALETTE.

<22> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_SETICMPROFILEA.

<23> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_SETICMPROFILEW.

<24> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_ALPHABLEND.

<25> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_SETLAYOUT.

<26> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_TRANSPARENTBLT.

<27> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_GRADIENTFILL.

<28> Section 2.1.1: Windows GDI uses an EMR_EXTTEXTOUTW record (section 2.3.5.8) to perform this function.

<29> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_COLORMATCHTOTARGETW.

<30> Section 2.1.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_CREATECOLORSPACEW.

<31> Section 2.1.11: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition: Do not support the ETO_GLYPH_INDEX flag used for bitmap and vector fonts—in addition to TrueType fonts—to indicate that no further language processing is necessary and that GDI should process the string directly. See [MSDN-GDI+] for more information.

<32> Section 2.1.11: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition: Do not support the ETO_RTLREADING flag used to indicate right-to-left reading order.

<33> Section 2.1.11: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition: Do not support the ETO_NUMERICSLOCAL flag used to indicate the display of numeric digits appropriate to the locale.

<34> Section 2.1.11: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition: Do not support the ETO_NUMERICSLATIN flag used to indicate the display of numeric digits appropriate to Europe.

<35> Section 2.1.11: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition: Do not support the ETO_IGNORELANGUAGE flag used to indicate that international scripting support is not used, which may cause no text to be output.

<36> Section 2.1.11: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, Windows Millennium Edition, Windows NT 4.0, and Windows 2000: Do not support the ETO_PDY flag used to indicate that that both horizontal and vertical character displacement values SHOULD be provided.

<37> Section 2.1.11: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, Windows Millennium Edition, Windows NT 4.0, and Windows 2000: Do not support the ETO_REVERSE_INDEX_MAP flag.

<38> Section 2.1.16: GM_COMPATIBLE graphics mode is used for compatibility between both 16-bit and 32-bit systems.

<39> Section 2.1.16: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, Windows Millennium Edition, Windows NT 4.0, and Windows 2000: GM_ADVANCED is not supported.

<40> Section 2.1.18: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition: Do not support ICM_OFF.

<41> Section 2.1.18: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition: Do not support ICM_ON.

<42> Section 2.1.18: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition: Do not support ICM_QUERY.

<43> Section 2.1.18: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition: Do not support ICM_DONE_OUTSIDEDC.

<44> Section 2.1.31: In Windows implementations, BS_HOLLOW was added as a duplicate symbolic name for BS_NULL because BS_NULL was too easily mistaken for a null pointer.

BS_HOLLOW is used by an application when GDI requires a non-null brush parameter, but the application requires that no brush be used. See [MSDN-GDI+] for more information.

<45> Section 2.1.31: On Windows, this is the "Courier" font.

<46> Section 2.1.31: On Windows, this is the "MS Sans Serif" font.

<47> Section 2.1.31: On Windows, this is the font used to draw menu text and dialog box controls.

Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows NT 4.0, Windows 98, and Windows Millennium Edition: The system font is "MS Sans Serif".

Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2: The system font is "Tahoma".

<48> Section 2.1.31: Windows 98 and Windows Millennium Edition: This value is not supported.

Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2: This value is considered equivalent to SYSTEM_FONT for the purposes of screen display of metafiles.

<49> Section 2.1.31: On Windows, this palette consists of the static colors in the system palette.

<50> Section 2.1.31: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows NT 4.0, Windows 98, and Windows Millennium Edition: The default user interface font is "MS Sans Serif".

Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2: The default user-interface font is "Tahoma".

<51> Section 2.1.31: Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2: The default brush is WHITE_BRUSH.

<52> Section 2.1.31: Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2: The default pen is BLACK_PEN.

<53> Section 2.1.32: Windows also uses the following symbolic names for the StretchMode enumeration; their meanings are exactly the same as the members with the same values.

#define BLACKONWHITE                 1
#define WHITEONBLACK                 2
#define COLORONCOLOR                 3
#define HALFTONE                     4

<54> Section 2.2.2: Windows 98 and Windows Millennium Edition do not support the ColorAdjustment object.

<55> Section 2.2.2: Windows can generate ColorAdjustment objects with values outside their valid ranges. Such objects are ignored.

<56> Section 2.2.5: In Windows implementations, this is the clipping and/or opaquing rectangle that is passed to GDI methods ExtTextOutA and ExtTextOutW.

<57> Section 2.2.6: Windows does not parse the PostScript data in an EpsData object; the data is handed off to the graphics printer driver if the driver supports PostScript printing.

<58> Section 2.2.9: Windows does not check this value.

<59> Section 2.2.12: In Windows implementations, BS_HOLLOW was added as a duplicate symbolic name for BS_NULL because BS_NULL was too easily mistaken for a null pointer.

BS_HOLLOW is used by an application when GDI requires a non-null brush parameter, but the application requires that no brush be used. See [MSDN-GDI+] for more information.

<60> Section 2.2.13: In Windows implementations, the aspect ratio of the device is matched against the digitization aspect ratios of the available fonts to find the closest match, determined by the absolute value of the difference.

<61> Section 2.2.13: Windows uses a weight value of 400 by default.

Value

Weight

Thin

100

Extra Light (Ultra Light)

200

Light

300

Normal (Regular)

400

Medium

500

Semi-Bold (Demi-Bold)

600

Bold

700

Extra Bold (Ultra Bold)

800

Heavy (Black)

900

<62> Section 2.2.20: In Windows implementations, BS_HOLLOW was added as a duplicate symbolic name for BS_NULL because BS_NULL was too easily mistaken for a null pointer.

BS_HOLLOW is used by an application when GDI requires a non-null brush parameter, but the application requires that no brush be used. See [MSDN-GDI+] for more information.

<63> Section 2.2.22: Windows implementations do not support this flag.

<64> Section 2.2.22: Windows can use this flag to indicate that the pixel format specified by this structure is supported by GDI. See [MSDN-GDI+] for more information.

Windows can also use this flag to specify single-buffering for the pixel buffer.

<65> Section 2.2.22: Windows uses this flag to indicate that the pixel pixel format is supported by GDI.

<66> Section 2.2.22: Windows uses this with OpenGL drawing only.

Windows NT 3.1, Windows NT 3.51, Windows NT 4.0, Windows 98, Windows 2000, Windows Millennium Edition, Windows XP, and Windows Server 2003 do not support this flag.

<67> Section 2.2.22: Windows does not support alpha bitplanes.

<68> Section 2.2.22: Windows does not support alpha bitplanes.

<69> Section 2.2.22: Windows does not support alpha bitplanes.

<70> Section 2.2.27: In this case, Windows uses the logical font that is currently selected in the playback device context.

<71> Section 2.3.1: Windows does not support rotation or shear transforms.

<72> Section 2.3.1.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_ALPHABLEND.

<73> Section 2.3.1.3: Windows might set this to a non-zero value.

<74> Section 2.3.1.8: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_TRANSPARENTBLT.

<75> Section 2.3.1.8: Windows uses the EMR_ALPHABLEND record (section 2.3.1.1) to specify a block transfer of a 32 bits-per-pixel bitmap with alpha transparency.

<76> Section 2.3.3.1: Windows NT 3.1, Windows NT 3.51, and Windows NT 4.0 ignore EMR_COMMENT records.

<77> Section 2.3.3.4.3: On playback, the first graphics format recognized by Windows is used to render the image.

<78> Section 2.3.4.2: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition create EMFmetafiles with an EmfMetafileHeader header record (section 2.3.4.2.1).

<79> Section 2.3.4.2: Windows NT 4.0 creates EMFmetafiles with an EmfMetafileHeaderExtension1 header record (section 2.3.4.2.2).

<80> Section 2.3.4.2: Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2 create EMFmetafiles with an EmfMetafileHeaderExtension2 header record (section 2.3.4.2.3).

<81> Section 2.3.4.2.2: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition do not support this type of EMFmetafile header.

<82> Section 2.3.4.2.3: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows NT 4.0, Windows 98, and Windows Millennium Edition do not support this type of EMFmetafile header.

<83> Section 2.3.5.7: Windows GDI emulates EMR_EXTTEXTOUTA with an EMR_EXTTEXTOUTW record.

<84> Section 2.3.5.12: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_GRADIENTFILL.

<85> Section 2.3.5.12: Windows uses true colors in 24-bits-per-pixel (bpp) and 32-bpp formats, and dithering in 4-bpp, 8-bpp, and 16-bpp formats.

<86> Section 2.3.5.32: Windows NT 3.1 is the only Windows version in which GDI uses EMR_POLYTEXTOUTA records for text output. All other versions emulate EMR_POLYTEXTOUTA with EMR_EXTTEXTOUTW records.

<87> Section 2.3.5.33: Windows NT 3.1 is the only Windows version in which GDI uses EMR_POLYTEXTOUTW records for text output. All other versions emulate EMR_POLYTEXTOUTW with EMR_EXTTEXTOUTW records.

<88> Section 2.3.7.2: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_CREATECOLORSPACE.

<89> Section 2.3.7.3: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_CREATECOLORSPACEW.

<90> Section 2.3.7.8: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 metafiles contain a LogFont object in this field.

<91> Section 2.3.8.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_COLORCORRECTPALETTE.

<92> Section 2.3.8.2: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_DELETECOLORSPACE.

<93> Section 2.3.8.2: Windows uses an EMR_DELETEOBJECT record to delete a logical color space object.

<94> Section 2.3.8.4: Windows GDI does not perform parameter validation on this value, which can lead to the generation of EMFmetafiles that contain invalid EMR_RESIZEPALETTE records. Windows ignores such invalid records when processing metafiles.

<95> Section 2.3.8.7: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_SETCOLORSPACE.

<96> Section 2.3.9: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows 98, and Windows Millennium Edition: OpenGL records are not supported.

<97> Section 2.3.9.1: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_GLSBOUNDEDRECORD.

<98> Section 2.3.9.2: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_GLSRECORD.

<99> Section 2.3.11.1: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_COLORMATCHTOTARGETW.

<100> Section 2.3.11.1: On Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2, before applying the current color transform, WCS is enabled in the playback device context.

<101> Section 2.3.11.5: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_PIXELFORMAT.

<102> Section 2.3.11.14: Windows NT 3.1, Windows NT 3.5, and Windows NT 3.51 do not support EMR_SETICMMODE.

<103> Section 2.3.11.15: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_SETICMPROFILEA.

<104> Section 2.3.11.16: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_SETICMPROFILEW.

<105> Section 2.3.11.17: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 do not support EMR_SETLAYOUT.

<106> Section 2.3.11.20: Only Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 support EMR_SETMAPPERFLAGS.

<107> Section 2.3.11.21: Windows GDI accepts a floating-point value for the corresponding miter length limit value,

<108> Section 2.3.11.27: Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, Windows NT 4.0, Windows 98, and Windows Millennium Edition do not support EMR_SETTEXTJUSTIFICATION.

<109> Section 2.3.11.27: Windows GDI uses an EMR_EXTTEXTOUTW record (section 2.3.5.8) to perform this function.

 
Show:
© 2014 Microsoft