Independent Submission S. Leonard
Request for Comments: 7903 Penango, Inc.
Category: Informational September 2016
ISSN: 2070-1721
Independent Submission S. Leonard
Request for Comments: 7903 Penango, Inc.
Category: Informational September 2016
ISSN: 2070-1721
Windows Image Media Types
Windows映像媒体类型
Abstract
摘要
This document registers media types for certain image formats promulgated in Microsoft Windows, namely image/wmf, image/x-wmf, image/emf, image/x-emf, and image/bmp for use with Windows Metafile, Enhanced Metafile, and Windows Bitmap formats. Originally designed for Microsoft Windows 2.0 and 3.0, these image files are intended to be portable between applications and devices, and they may contain both vector and raster graphics.
本文档为Microsoft Windows中发布的某些图像格式注册媒体类型，即image/wmf、image/x-wmf、image/emf、image/x-emf和image/bmp，用于Windows图元文件、增强图元文件和Windows位图格式。这些图像文件最初是为Microsoft Windows 2.0和3.0设计的，旨在在应用程序和设备之间进行移植，它们可能包含矢量和光栅图形。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document at its discretion and makes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor are not a candidate for any level of Internet Standard; see Section 2 of RFC 7841.
这是对RFC系列的贡献，独立于任何其他RFC流。RFC编辑器已选择自行发布此文档，并且未声明其对实现或部署的价值。RFC编辑批准发布的文件不适用于任何级别的互联网标准；见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7903.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7903.
Copyright Notice
版权公告
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2016 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Windows Metafiles ..........................................2
1.2. Windows Bitmaps ............................................3
2. Windows Metafile Media Type Registration Application ............4
3. Enhanced Metafile Media Type Registration Application ...........6
4. Windows Bitmap Media Type Registration Application ..............9
5. IANA Considerations ............................................11
6. Security Considerations ........................................11
7. References .....................................................11
7.1. Normative References ......................................11
7.2. Informative References ....................................11
Author's Address ..................................................12
1. Introduction ....................................................2
1.1. Windows Metafiles ..........................................2
1.2. Windows Bitmaps ............................................3
2. Windows Metafile Media Type Registration Application ............4
3. Enhanced Metafile Media Type Registration Application ...........6
4. Windows Bitmap Media Type Registration Application ..............9
5. IANA Considerations ............................................11
6. Security Considerations ........................................11
7. References .....................................................11
7.1. Normative References ......................................11
7.2. Informative References ....................................11
Author's Address ..................................................12
Long before the invention of Scalable Vector Graphics, Microsoft Corporation recognized the value of recording images in a format that its applications and operating systems could easily render irrespective of the output device. With the release of Windows 3.0, Microsoft released its Windows Metafile (WMF) format, which can contain vector and raster graphics in one package. As a binary format that needed to work on 16-bit machines, WMF is comprised of a sequence of record structures. Each record contains drawing commands, object definitions, and configuration settings. When a metafile is processed, the image can be rendered on a display, output to a printer or plotter, stored in memory, or saved to some persistent storage. Reflecting the relationship to the Windows Graphics Device Interface (GDI) API, WMF data is "played" to a playback device context in the same manner that PostScript content is treated as an executable program that results in the output of the original document.
早在可伸缩矢量图形发明之前，微软公司就认识到以其应用程序和操作系统可以轻松呈现的格式记录图像的价值，而不管输出设备如何。随着Windows 3.0的发布，Microsoft发布了其Windows图元文件（WMF）格式，该格式可以在一个软件包中包含矢量和光栅图形。作为一种需要在16位机器上工作的二进制格式，WMF由一系列记录结构组成。每个记录都包含图形命令、对象定义和配置设置。处理图元文件时，图像可以在显示器上渲染、输出到打印机或绘图仪、存储在内存中或保存到某个永久性存储器中。反映与Windows图形设备接口（GDI）API的关系，WMF数据以与PostScript内容被视为可执行程序的方式“播放”到播放设备上下文，从而导致原始文档的输出。
As Microsoft's first 32-bit operating system, Windows NT 3.1 introduced an overhaul to the Windows API ("Win32") and the in-memory formats upon which those APIs relied. The Enhanced Metafile (EMF) format was created at this time, using 32-bit values instead of WMF's 16-bit values. In Windows XP, Microsoft extended EMF with "EMF+", adding support for Windows GDI+.
作为微软的第一个32位操作系统，WindowsNT3.1对WindowsAPI（“Win32”）以及这些API所依赖的内存格式进行了彻底的修改。此时创建了增强型图元文件（EMF）格式，使用32位值而不是WMF的16位值。在Windows XP中，Microsoft使用“EMF+”扩展了EMF，增加了对Windows GDI+的支持。
Many implementations of WMF and EMF were created because of Windows' commercial success in the 1990s. A large body of free and commercially available clip art and other artwork exists in this format. Furthermore, WMF content appears non-normatively in certain
许多WMF和EMF的实现都是由于Windows在20世纪90年代的商业成功而创建的。大量免费和商用的剪贴画和其他艺术品以这种格式存在。此外，在某些情况下，WMF含量表现出非规范性
standards (e.g., [OOXML]); the usage is common enough that an implementer would almost certainly need to support it for basic interoperability.
标准（例如，[OOXML]）；这种用法非常普遍，实现者几乎肯定需要支持它以实现基本的互操作性。
Microsoft publicly documented the WMF format as early as the 1992 Windows 3.1 SDK. Since 2007, Microsoft has released the format specifications [MS-WMF], [MS-EMF], and [MS-EMF+] under its Open Specification Promise [MS-OSP].
早在1992年Windows 3.1 SDK中，Microsoft就公开记录了WMF格式。自2007年以来，微软在其开放规范承诺[MS-OSP]下发布了格式规范[MS-WMF]、[MS-EMF]和[MS-EMF+]。
Long before the invention of Portable Network Graphics (PNG), Microsoft Corporation and IBM Corporation needed to record images in a format that their applications and operating systems could easily render on low-end machines (Intel 80286). The resulting "BMP" format contains a single raster graphic with basic header fields that can be easily mapped (or "blitted") to locations in memory. As computing moved from 16-bit to 32-bit, BMP evolved to contain 32-bit structures. As the '90s wore on, the venerable BMP got boosts with support for additional color spaces, color profiles, and compression formats. The same basic format can be used to convey 2-bit black-and-white bitmaps with a 1-bit alpha mask from the '80s, and full-color Ultra HD images on leading-edge displays. BMP is a building block of other formats, including Windows Metafiles, Windows Icons, and Windows Cursors.
早在便携式网络图形（PNG）发明之前，微软公司和IBM公司就需要以其应用程序和操作系统可以在低端机器（英特尔80286）上轻松呈现的格式记录图像。生成的“BMP”格式包含一个带有基本标题字段的光栅图形，这些字段可以轻松映射（或“Blit”）到内存中的位置。随着计算从16位移动到32位，BMP演变为包含32位结构。随着90年代的发展，久负盛名的BMP获得了支持额外颜色空间、颜色配置文件和压缩格式的提升。同样的基本格式也可以用于传输20世纪80年代的2位黑白位图（带有1位alpha遮罩）和前沿显示器上的全彩超高清图像。BMP是其他格式的构建块，包括Windows图元文件、Windows图标和Windows光标。
Many implementations of BMP were created because of Windows' commercial success in the 1990s. Usage of the format for interchange has declined since the advent of PNG (for lossless raster graphics) and JPEG (for lossy raster graphics); however, a large body of free and commercially available BMP artwork exists. Since Windows Icons are a building block of "favicon.ico" web technology, an implementer would almost certainly need to support this format for basic interoperability.
许多BMP的实现都是由于Windows在20世纪90年代的商业成功而产生的。自从PNG（用于无损光栅图形）和JPEG（用于有损光栅图形）问世以来，交换格式的使用有所下降；然而，存在大量免费和商用BMP艺术品。由于Windows图标是“favicon.ico”web技术的组成部分，实现者几乎肯定需要支持这种格式以实现基本的互操作性。
Microsoft publicly documented the BMP format as early as the 1992 Windows 3.1 SDK (in the Windows Metafile documentation). Since 2007 Microsoft has released the format specification [MS-WMF], which includes most components of the Windows Bitmap format, under its Open Specification Promise [MS-OSP]. See Section 2.2.2.9 of [MS-WMF] (DeviceIndependentBitmap Object). BMP data begins with a BITMAPFILEHEADER and is followed by one of the bitmap headers (BITMAPINFOHEADER, BITMAPV4HEADER, or BITMAPV5HEADER), optional color table data, bitmap data, and optional profile data, in that order [BMPSTOR].
早在1992年Windows 3.1 SDK（在Windows图元文件文档中）时，Microsoft就公开记录了BMP格式。自2007年以来，微软根据其开放规范承诺[MS-OSP]，发布了格式规范[MS-WMF]，其中包括Windows位图格式的大部分组件。参见[MS-WMF]（设备独立位图对象）的第2.2.2.9节。BMP数据以BITMAPFILEHEADER开头，然后依次为位图头（BitMapInfo头、BITMAPV4HEADER或BITMAPV5HEADER）、可选颜色表数据、位图数据和可选配置文件数据[BMPSTOR]。
Implementers need to be aware of the [MICE] vulnerability, and to guard against it. Some details are included in the completed registration template.
实现者需要意识到[MICE]漏洞，并加以防范。已完成的注册模板中包含一些详细信息。
Type name: image
类型名称：图像
Subtype name: wmf
子类型名称：wmf
Required parameters: None.
所需参数：无。
Optional parameters:
可选参数：
DEFAULT_CHARSET: The character set intended when the CharacterSet enumeration (see the WMF specification) specifies DEFAULT_CHARSET. The value of this parameter is a charset from the IANA "Character Sets" registry <http://www.iana.org/assignments/character-sets>. When this parameter is not specified, DEFAULT_CHARSET has the following meaning in the WMF specification: "a character set based on the current system locale; for example, when the system locale is United States English, the default character set is ANSI_CHARSET" (which is Windows-1252, more or less). That is, when not specified, the default character set is system dependent. This optional parameter is new to this registration and may not enjoy widespread support for some time. Therefore, EMF instead of WMF (or if necessary under the circumstances, embedded EMF within WMF) is a more sensible choice when text is present.
DEFAULT_字符集：字符集枚举（请参阅WMF规范）指定DEFAULT_字符集时使用的字符集。此参数的值是IANA“字符集”注册表中的字符集<http://www.iana.org/assignments/character-sets>. 未指定此参数时，默认字符集在WMF规范中具有以下含义：“基于当前系统区域设置的字符集；例如，当系统区域设置为美国英语时，默认字符集为ANSI_字符集”（或多或少为Windows-1252）。也就是说，未指定时，默认字符集取决于系统。此可选参数是此注册的新参数，可能在一段时间内不会得到广泛支持。因此，当文本存在时，EMF而不是WMF（或者在必要的情况下，WMF中嵌入EMF）是更明智的选择。
Encoding considerations: Binary.
编码注意事项：二进制。
Security considerations:
安全考虑：
The Windows Metafile format's security history is punctuated in 2005-2006 with the disclosure of the Metafile Image Code Execution ("MICE") vulnerability. MICE won the 2007 Pwnie Award for "Mass 0wnage" and "Breaking the Internet". The official Microsoft security bulletin describes that the flaw occurs because Windows Metafiles can set the SETABORTPROC value of the MetafileEscapes enumeration (accessible via the META_ESCAPE record), allowing for arbitrary code execution, i.e., "active content".
2005-2006年，随着元文件图像代码执行（“MICE”）漏洞的披露，Windows元文件格式的安全历史被打断。MICE凭借“海量下载”和“打破互联网”获得2007年Pwnie奖。官方Microsoft安全公告描述，出现该漏洞的原因是Windows元文件可以设置MetaFileEscape枚举的SETABORTPROC值（可通过META_ESCAPE记录访问），从而允许执行任意代码，即“活动内容”。
Windows Metafiles can contain Enhanced Metafiles using the META_ESCAPE_ENHANCED_METAFILE record; thus, the security considerations of EMF apply to WMF.
Windows图元文件可以包含使用META_ESCAPE_Enhanced_图元文件记录的增强图元文件；因此，EMF的安全考虑适用于WMF。
Windows Metafiles are historically very buggy. As the original intent was to replicate Windows GDI calls, flaws in GDI, or in a display or printer driver implementing the backend to GDI, could be exploitable. WMF implementations not backed by Windows GDI have different risks: namely, while a malicious WMF author may not consider the non-Windows GDI implementation as a primary target, WMF has many "corner case" records for which an implementation's processing may not have received the same level of scrutiny as the Windows implementation. "Fuzzing" the implementation is appropriate.
Windows图元文件在历史上是非常有缺陷的。由于最初的意图是复制Windows GDI调用，GDI中的缺陷，或者实现GDI后端的显示器或打印机驱动程序中的缺陷，都可能被利用。不支持Windows GDI的WMF实现具有不同的风险：即，恶意WMF作者可能不考虑非Windows GDI实现作为主要目标，WMF具有许多“角落情况”记录，其中实现的处理可能没有接收到与Windows实现相同的审查级别。“模糊化”的实现是适当的。
As a "basic" image format, the image/wmf media type does not employ executable content and provides no facilities for privacy or integrity.
作为“基本”图像格式，图像/wmf媒体类型不采用可执行内容，也不提供隐私或完整性设施。
Interoperability considerations:
互操作性注意事项：
Windows Metafile is the original 16-bit metafile format; it was released in 1990 at what some computer historians might consider the "zenith" of the desktop publishing revolution. Accordingly, there is a large body of free and commercially available clip art that is still in use, either independently or embedded in productivity documents (word processing documents, desktop publishing documents, slideshows, presentations, spreadsheets, and workbooks). For example, references to WMF content appear (non-normatively) in Office Open XML. To say that support for this format is necessary for interoperability would not be an understatement.
Windows图元文件是原始的16位图元文件格式；它在1990发布，一些计算机历史学家可能会认为桌面出版革命的“顶峰”。因此，大量免费和商用的剪贴画仍在使用中，可以独立使用，也可以嵌入生产力文档（文字处理文档、桌面发布文档、幻灯片、演示、电子表格和工作簿）。例如，对WMF内容的引用（非规范地）出现在Office Open XML中。要说对这种格式的支持对于互操作性是必要的，这并不轻描淡写。
Accommodations for comments or arbitrary data storage in Windows Metafiles are virtually non-existent. However, Windows Metafiles can contain Enhanced Metafiles using the META_ESCAPE_ENHANCED_METAFILE record, so an implementation that handles Windows Metafiles is also expected to handle enhanced metafile content. Windows Metafiles can store and output text strings (see META_TEXTOUT and META_EXTTEXTOUT records), but the encodings of the strings may be ambiguous. Unicode encodings are not possible without the DEFAULT_CHARSET parameter defined in this registration.
在Windows图元文件中几乎不存在对注释或任意数据存储的调节。但是，Windows图元文件可以包含使用META_ESCAPE_Enhanced_图元文件记录的增强图元文件，因此处理Windows图元文件的实现也需要处理增强图元文件内容。Windows图元文件可以存储和输出文本字符串（请参见META_TEXTOUT和META_EXTTEXTOUT记录），但字符串的编码可能不明确。如果没有在此注册中定义的默认_字符集参数，则无法进行Unicode编码。
The previously unregistered type image/x-wmf is also in wide use. Accordingly, it is registered as a deprecated alias.
以前未注册的image/x-wmf类型也在广泛使用。因此，它被注册为不推荐使用的别名。
Published specification:
已发布的规范：
WMF: Microsoft Corporation, "[MS-WMF]: Windows Metafile Format", v20160714 (Rev 13.1), July 2016, <http://msdn.microsoft.com/library/cc250370>.
WMF:Microsoft Corporation，“[MS-WMF]：Windows图元文件格式”，v20160714（版本13.1），2016年7月<http://msdn.microsoft.com/library/cc250370>.
Applications that use this media type:
使用此媒体类型的应用程序：
Office productivity applications; clip art applications; desktop publishing applications; some web browsers (e.g., Internet Explorer).
办公室生产力应用；剪贴画应用；桌面出版应用程序；一些web浏览器（如Internet Explorer）。
Fragment identifier considerations: None.
片段标识符注意事项：无。
Additional information:
其他信息：
Deprecated alias names for this type: image/x-wmf
此类型的不推荐别名：image/x-wmf
Magic number(s): D7 CD C6 9A (little-endian DWORD 0x9AC6CDD7)
幻数：D7 CD C6 9A（小端DWORD 0x9AC6CDD7）
File extension(s): .wmf
文件扩展名：.wmf
Macintosh file type code(s): None. A uniform type identifier (UTI) of "com.microsoft.wmf" is suggested.
Macintosh文件类型代码：无。建议使用“com.microsoft.wmf”的统一类型标识符（UTI）。
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Sean Leonard <dev+ietf@seantek.com>
Sean Leonard <dev+ietf@seantek.com>
Restrictions on usage: None.
使用限制：无。
Author/Change controller: Sean Leonard <dev+ietf@seantek.com>
Author/Change controller: Sean Leonard <dev+ietf@seantek.com>
Intended usage: COMMON
预期用途：普通
Provisional registration? No
临时登记？不
Type name: image
类型名称：图像
Subtype name: emf
子类型名称：emf
Required parameters: None.
所需参数：无。
Optional parameters: None.
可选参数：无。
Encoding considerations: Binary.
编码注意事项：二进制。
Security considerations:
安全考虑：
Enhanced Metafiles are not afflicted with the Metafile Image Code Execution ("MICE") vulnerability. There has been no public disclosure of vulnerabilities specific to EMF or EMF+ to date. Neither EMF nor EMF+ are designed to contain "active content". Nonetheless, Enhanced Metafiles can contain Encapsulated PostScript (EPS) data; thus, the security considerations of PostScript processing may also apply to EMF.
增强型图元文件不会受到图元文件映像代码执行（“MICE”）漏洞的影响。迄今为止，尚未公开披露EMF或EMF+特有的漏洞。EMF和EMF+都不是为包含“活动内容”而设计的。尽管如此，增强的图元文件可以包含封装的PostScript（EPS）数据；因此，PostScript处理的安全考虑也可能适用于EMF。
As the original intent was to replicate Windows GDI calls, flaws in GDI, or in a display or printer driver implementing the backend to GDI, could be exploitable with maliciously crafted EMF content. EMF implementations not backed by Windows GDI have different risks: namely, while a malicious EMF author may not consider the non-Windows GDI implementation as a primary target, EMF has many "corner case" records for which an implementation's processing may not have received the same level of scrutiny as the Windows implementation. "Fuzzing" the implementation is appropriate. It is also possible that EMF+ data is "safe" while EMF data contains an exploit (or vice versa); the EMF+-aware implementation (such as an application designed for GDI+ on Windows XP or above) would skip the "unsafe" data while another implementation would fall prey to the exploit.
由于最初的意图是复制Windows GDI调用，GDI中的缺陷，或者实现GDI后端的显示器或打印机驱动程序中的缺陷，可能会被恶意制作的EMF内容所利用。不支持Windows GDI的EMF实现具有不同的风险：即，尽管恶意EMF作者可能不认为非Windows GDI实现为主要目标，EMF具有许多“角落情况”记录，其中实现的处理可能没有接收到与Windows实现相同的审查级别。“模糊化”的实现是适当的。当EMF数据包含漏洞时，EMF+数据也可能是“安全的”（反之亦然）；EMF+感知的实现（例如在Windows XP或更高版本上为GDI+设计的应用程序）将跳过“不安全”数据，而另一个实现将成为该漏洞的牺牲品。
As a "basic" image format, the image/emf media type does not employ executable content and provides no facilities for privacy or integrity.
作为一种“基本”图像格式，image/emf媒体类型不使用可执行内容，也不提供隐私或完整性方面的便利。
Interoperability considerations:
互操作性注意事项：
Enhanced Metafile is the 32-bit metafile format; it was released in 1992 along with Windows NT 3.1. There is a large body of free and commercially available clip art that is still in use, either independently or embedded in productivity documents (word processing documents, desktop publishing documents, slideshows, presentations, spreadsheets, and workbooks). To say that support for this format is necessary for interoperability would not be an understatement.
增强型图元文件是32位图元文件格式；它与WindowsNT3.1一起于1992年发布。大量免费和商用的剪贴画仍在使用中，可以独立使用，也可以嵌入生产力文档（文字处理文档、桌面出版文档、幻灯片、演示、电子表格和工作簿）。要说对这种格式的支持对于互操作性是必要的，这并不轻描淡写。
Enhanced Metafiles have extensive accommodations for comments and arbitrary data storage. Enhanced Metafiles can store and output text strings. Mercifully, the encodings of these strings are well-defined. Record examples include EMR_EXTTEXTOUTA (US-ASCII), EMR_EXTTEXTOUTW (UTF16-LE), EMR_POLYTEXTOUTA (US-ASCII), EMR_POLYTEXTOUTW (UTF16-LE), and EMR_SMALLTEXTOUT (UTF16-LE or the low-order 8 bits of UTF16-LE -- effectively ISO-8859-1 -- depending on ETO_SMALL_CHARS).
增强型图元文件可广泛容纳注释和任意数据存储。增强型图元文件可以存储和输出文本字符串。幸运的是，这些字符串的编码定义良好。记录示例包括EMR_EXTTEXTOUTA（US-ASCII）、EMR_EXTTEXTOUTA（UTF16-LE）、EMR_POLYTEXTOUTA（US-ASCII）、EMR_polytextoutu（UTF16-LE）和EMR_SMALLTEXTOUT（UTF16-LE或UTF16-LE的低阶8位——实际上是ISO-8859-1——取决于ETO_SMALL_字符）。
Enhanced Metafiles can contain Encapsulated PostScript (EPS) data in the EpsData object. The FormatSignature EPS_SIGNATURE (0x46535045, in little-endian) is used instead of ENHMETA_SIGNAUTRE (0x464D4520, in little-endian) in such a case.
增强型图元文件可以在EpsData对象中包含封装的PostScript（EPS）数据。在这种情况下，将使用FormatSignature EPS_签名（0x46535045，小写）代替ENHMETA_签名（0x464D4520，小写）。
Windows XP introduced the GDI+ API, along with EMF+. EMF+ is actually an embedded format in which GDI+ commands are stored as EMF comment records (EMR_COMMENT_EMFPLUS record type). Content containing EMF+ data can be identified as "EMF+ Only" (only EMF+; the EMF records are not sufficient to reconstitute the drawing) or "EMF+ Dual" (both EMF records alone or EMF+ records alone, when played back, are sufficient to reconstitute the drawing). Support for EMF+ records may not be as extensive as support for the original EMF records.
WindowsXP引入了GDI+API和EMF+。EMF+实际上是一种嵌入式格式，其中GDI+命令存储为EMF注释记录（EMR_comment_EMFPLUS记录类型）。包含EMF+数据的内容可以标识为“仅EMF+”（仅EMF+；EMF记录不足以重建图形）或“EMF+双”（播放时，仅EMF记录或仅EMF+记录就足以重建图形）。对EMF+记录的支持可能不如对原始EMF记录的支持那么广泛。
The previously unregistered type image/x-emf is also in wide use. Accordingly, it is registered as a deprecated alias.
以前未注册的image/x-emf类型也被广泛使用。因此，它被注册为不推荐使用的别名。
Published specification:
已发布的规范：
EMF: Microsoft Corporation, "[MS-EMF]: Enhanced Metafile Format", v20160714 (Rev 12.0), July 2016, <http://msdn.microsoft.com/library/cc230514>.
EMF:Microsoft Corporation，“[MS-EMF]：增强型图元文件格式”，v20160714（12.0版），2016年7月<http://msdn.microsoft.com/library/cc230514>.
EMF+: Microsoft Corporation, "[MS-EMFPLUS]: Enhanced Metafile Format Plus Extensions", v20160714 (Rev 14.1), July 2016, <http://msdn.microsoft.com/library/cc230724>.
EMF+：微软公司，“[MS-EMFPLUS]：增强型图元文件格式加扩展”，v20160714（14.1版），2016年7月<http://msdn.microsoft.com/library/cc230724>.
Applications that use this media type:
使用此媒体类型的应用程序：
Office productivity applications; clip art applications; desktop publishing applications; some web browsers (e.g., Internet Explorer).
办公室生产力应用；剪贴画应用；桌面出版应用程序；一些web浏览器（如Internet Explorer）。
Fragment identifier considerations: None.
片段标识符注意事项：无。
Additional information:
其他信息：
Deprecated alias names for this type: image/x-emf
此类型的不推荐别名：image/x-emf
Magic number(s): 01 00 00 00 (little-endian DWORD 0x00000001), corresponding to the EMR_HEADER Type field. The next field (EMR_HEADER Size) should be at least 88 (little-endian DWORD 0x00000050).
幻数：01 00（小尾端DWORD 0x00000001），对应于EMR_头类型字段。下一个字段（EMR_头大小）应至少为88（小尾端DWORD 0x00000050）。
File extension(s): .emf (for both EMF and EMF+ content)
File extension(s): .emf (for both EMF and EMF+ content)
Macintosh file type code(s): None. A uniform type identifier (UTI) of "com.microsoft.emf" is suggested.
Macintosh文件类型代码：无。建议使用“com.microsoft.emf”的统一类型标识符（UTI）。
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Sean Leonard <dev+ietf@seantek.com>
Sean Leonard <dev+ietf@seantek.com>
Restrictions on usage: None.
使用限制：无。
Author/Change controller: Sean Leonard <dev+ietf@seantek.com>
Author/Change controller: Sean Leonard <dev+ietf@seantek.com>
Intended usage: COMMON
预期用途：普通
Provisional registration? No
临时登记？不
Type name: image
类型名称：图像
Subtype name: bmp
子类型名称：bmp
Required parameters: None.
所需参数：无。
Optional parameters: None.
可选参数：无。
Encoding considerations: Binary.
编码注意事项：二进制。
Security considerations:
安全考虑：
Bitmaps have a mostly unremarkable security history.
位图的安全性历史记录通常不显著。
Because BMP data can encapsulate JPEG or PNG data (BI_JPEG, BI_PNG values of the Compression enumeration in Section 2.1.1.7 of the WMF specification), the security considerations of JPEG and PNG processing may also apply to BMP.
由于BMP数据可以封装JPEG或PNG数据（WMF规范第2.1.1.7节中压缩枚举的BI_JPEG、BI_PNG值），JPEG和PNG处理的安全注意事项也可能适用于BMP。
As a "basic" image format, the image/bmp media type does not employ executable content and provides no facilities for privacy or integrity.
作为一种“基本”图像格式，图像/bmp媒体类型不采用可执行内容，也不提供隐私或完整性方面的便利。
Interoperability considerations:
互操作性注意事项：
Uncompressed Windows Bitmaps can be rather large. If there is a need to compress an image, modern applications should consider emitting JPEG or PNG data instead of embedding them in BMP payloads.
未压缩的Windows位图可能相当大。如果需要压缩图像，现代应用程序应该考虑发射JPEG或PNG数据，而不是将它们嵌入到BMP有效载荷中。
Published specification:
已发布的规范：
WMF: Microsoft Corporation, "[MS-WMF]: Windows Metafile Format", v20160714 (Rev 13.1), July 2016, <http://msdn.microsoft.com/library/cc250370>.
WMF:Microsoft Corporation，“[MS-WMF]：Windows图元文件格式”，v20160714（版本13.1），2016年7月<http://msdn.microsoft.com/library/cc250370>.
BMP: Microsoft Corporation, "Bitmap Storage", MSDN ID dd183391, <http://msdn.microsoft.com/library/dd183391>.
BMP:Microsoft Corporation，“位图存储”，MSDN ID dd183391<http://msdn.microsoft.com/library/dd183391>.
Applications that use this media type:
使用此媒体类型的应用程序：
Office productivity applications; clip art applications; desktop publishing applications; web browsers; graphics processing applications.
办公室生产力应用；剪贴画应用；桌面出版应用程序；网络浏览器；图形处理应用程序。
Fragment identifier considerations: None.
片段标识符注意事项：无。
Additional information:
其他信息：
Magic number(s): 42 4D ("BM"), meaning "bitmap". The next field (BITMAPFILEHEADER bfSize) is a little-endian DWORD indicating the size of the bitmap content in bytes.
幻数：424D（“BM”），意思是“位图”。下一个字段（BITMAPFILEHEADER bfSize）是一个小的endian DWORD，表示位图内容的大小（以字节为单位）。
File extension(s): .bmp, .dib
文件扩展名：.bmp、.dib
Macintosh file type code(s): "BMP ", "BMPf", or "BMPp". Apple has promulgated a uniform type identifier (UTI) of "com.microsoft.bmp".
Macintosh文件类型代码：“BMP”、“BMPf”或“BMPp”。苹果公司发布了一个统一类型标识符（UTI）“com.microsoft.bmp”。
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Sean Leonard <dev+ietf@seantek.com>
Sean Leonard <dev+ietf@seantek.com>
Restrictions on usage: None.
使用限制：无。
Author/Change controller: Sean Leonard <dev+ietf@seantek.com>
Author/Change controller: Sean Leonard <dev+ietf@seantek.com>
Intended usage: COMMON
预期用途：普通
Provisional registration? No
临时登记？不
IANA has registered the media types image/wmf, image/x-wmf, image/emf, image/x-emf, and image/bmp in the standards tree using the applications provided in Sections 2, 3, and 4 of this document.
IANA已使用本文档第2、3和4节中提供的应用程序在标准树中注册了媒体类型image/wmf、image/x-wmf、image/emf、image/x-emf和image/bmp。
See the registration templates for their respective security considerations.
有关各自的安全注意事项，请参见注册模板。
The Metafile Image Code Execution (MICE) vulnerability won the 2007 Pwnie Award for "Mass 0wnage" and "Breaking the Internet" [PWNIES07].
元文件图像代码执行（MICE）漏洞因“海量下载”和“破坏互联网”而获得2007年Pwnie奖[PWNIES07]。
[BMPSTOR] Microsoft Corporation, "Bitmap Storage", MSDN ID dd183391, <http://msdn.microsoft.com/library/dd183391>.
[BMPSTOR]微软公司，“位图存储”，MSDN ID dd183391<http://msdn.microsoft.com/library/dd183391>.
[MS-EMF] Microsoft Corporation, "[MS-EMF]: Enhanced Metafile Format", v20160714 (Rev 12.0), July 2016, <http://msdn.microsoft.com/library/cc230514>.
[MS-EMF]微软公司，“[MS-EMF]：增强型图元文件格式”，v20160714（12.0版），2016年7月<http://msdn.microsoft.com/library/cc230514>.
[MS-EMF+] Microsoft Corporation, "[MS-EMFPLUS]: Enhanced Metafile Format Plus Extensions", v20160714 (Rev 14.1), July 2016, <http://msdn.microsoft.com/library/cc230724>.
[MS-EMF+]微软公司，“[MS-EMFPLUS]：增强型图元文件格式加扩展名”，v20160714（14.1版），2016年7月<http://msdn.microsoft.com/library/cc230724>.
[MS-WMF] Microsoft Corporation, "[MS-WMF]: Windows Metafile Format", v20160714 (Rev 13.1), July 2016, <http://msdn.microsoft.com/library/cc250370>.
[MS-WMF]微软公司，“[MS-WMF]：Windows图元文件格式”，v20160714（版本13.1），2016年7月<http://msdn.microsoft.com/library/cc250370>.
[MICE] Microsoft Corporation, "Vulnerability in Graphics Rendering Engine Could Allow Remote Code Execution (912919)", MS06-001, V1.0, January 2006, <https://technet.microsoft.com/library/security/ms06-001>.
[MICE]微软公司，“图形呈现引擎中的漏洞可能允许远程代码执行（912919）”，MS06-001，V1.0，2006年1月<https://technet.microsoft.com/library/security/ms06-001>.
[MS-OSP] Microsoft Corporation, "Open Specification Promise", February 2007, <https://msdn.microsoft.com/ en-us/openspecifications/dn646765>.
[MS-OSP]微软公司，“开放规范承诺”，2007年2月<https://msdn.microsoft.com/ en us/openspecifications/dn646765>。
[OOXML] Ecma International, "Office Open XML File Formats", Standard ECMA-376, Fourth Edition, ISO/IEC 29500, December 2012, <http://www.ecma-international.org/publications/ standards/Ecma-376.htm>.
[OOXML]Ecma国际，“办公室开放XML文件格式”，标准Ecma-376，第四版，ISO/IEC 29500，2012年12月<http://www.ecma-international.org/publications/ 标准/Ecma-376.htm>。
[PWNIES07] Pwnie Awards LLC, "Winners of Pwnie Awards 2007", 2007, <http://pwnies.com/archive/2007/winners/>.
[PWNIES07]Pwnie Awards LLC，“2007年Pwnie Awards获奖者”，2007年<http://pwnies.com/archive/2007/winners/>.
Author's Address
作者地址
Sean Leonard Penango, Inc. 5900 Wilshire Boulevard 21st Floor Los Angeles, CA 90036 United States of America
Sean Leonard Penango，Inc.美国加利福尼亚州洛杉矶威尔希尔大道21楼5900号，邮编90036
Email: dev+ietf@seantek.com
URI: http://www.penango.com/
Email: dev+ietf@seantek.com
URI: http://www.penango.com/