Internet Engineering Task Force (IETF)                         C. Lilley
Request for Comments: 8081                                           W3C
Category: Standards Track                                  February 2017
ISSN: 2070-1721
        
Internet Engineering Task Force (IETF)                         C. Lilley
Request for Comments: 8081                                           W3C
Category: Standards Track                                  February 2017
ISSN: 2070-1721
        

The "font" Top-Level Media Type

“字体”顶级媒体类型

Abstract

摘要

This memo serves to register and document the "font" top-level media type, under which subtypes for representation formats for fonts may be registered. This document also serves as a registration application for a set of intended subtypes, which are representative of some existing subtypes already in use, and currently registered under the "application" tree by their separate registrations.

此备忘录用于注册和记录“字体”顶级媒体类型,在此类型下可以注册字体表示格式的子类型。本文件还可作为一组预期子类型的注册申请,这些子类型代表已在使用的一些现有子类型,目前通过单独注册在“应用”树下注册。

Status of This Memo

关于下段备忘

This is an Internet Standards Track document.

这是一份互联网标准跟踪文件。

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.

本文件是互联网工程任务组(IETF)的产品。它代表了IETF社区的共识。它已经接受了公众审查,并已被互联网工程指导小组(IESG)批准出版。有关互联网标准的更多信息,请参见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/rfc8081.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息,请访问http://www.rfc-editor.org/info/rfc8081.

Copyright Notice

版权公告

Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.

版权所有(c)2017 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. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件,因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本,并提供简化BSD许可证中所述的无担保。

Table of Contents

目录

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Background and Justification  . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Definition and Encoding . . . . . . . . . . . . . . . . .   5
     4.2.  Fragment Identifiers for Font Collections . . . . . . . .   5
     4.3.  Registration Procedure  . . . . . . . . . . . . . . . . .   6
     4.4.  Subtype Registrations . . . . . . . . . . . . . . . . . .   6
       4.4.1.  Generic SFNT Font Type  . . . . . . . . . . . . . . .   6
       4.4.2.  TTF Font Type . . . . . . . . . . . . . . . . . . . .   9
       4.4.3.  OpenType Layout (OTF) Font Type . . . . . . . . . . .  10
       4.4.4.  Collection Font Type  . . . . . . . . . . . . . . . .  12
       4.4.5.  WOFF 1.0  . . . . . . . . . . . . . . . . . . . . . .  14
       4.4.6.  WOFF 2.0  . . . . . . . . . . . . . . . . . . . . . .  15
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     5.2.  Informative References  . . . . . . . . . . . . . . . . .  17
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  18
        
   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Background and Justification  . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Definition and Encoding . . . . . . . . . . . . . . . . .   5
     4.2.  Fragment Identifiers for Font Collections . . . . . . . .   5
     4.3.  Registration Procedure  . . . . . . . . . . . . . . . . .   6
     4.4.  Subtype Registrations . . . . . . . . . . . . . . . . . .   6
       4.4.1.  Generic SFNT Font Type  . . . . . . . . . . . . . . .   6
       4.4.2.  TTF Font Type . . . . . . . . . . . . . . . . . . . .   9
       4.4.3.  OpenType Layout (OTF) Font Type . . . . . . . . . . .  10
       4.4.4.  Collection Font Type  . . . . . . . . . . . . . . . .  12
       4.4.5.  WOFF 1.0  . . . . . . . . . . . . . . . . . . . . . .  14
       4.4.6.  WOFF 2.0  . . . . . . . . . . . . . . . . . . . . . .  15
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     5.2.  Informative References  . . . . . . . . . . . . . . . . .  17
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  18
        
1. Introduction
1. 介绍

The process of setting type in computer systems and other forms of text presentation systems uses fonts in order to provide visual representations of the glyphs. Just as with images, for example, there are a number of ways to represent the visual information of the glyphs. Early font formats often used bitmaps, as these could have been carefully tuned for maximum readability at a given size on low-resolution displays. More recently, scalable vector outline fonts have come into widespread use. In these fonts, the outlines of the glyphs are described, and the presentation system renders the outline in the desired position and size.

在计算机系统和其他形式的文本表示系统中设置类型的过程使用字体来提供字形的视觉表示。例如,与图像一样,有许多方法可以表示字形的视觉信息。早期的字体格式通常使用位图,因为在低分辨率显示器上,这些位图可以在给定大小下进行仔细调整,以获得最大的可读性。最近,可缩放矢量轮廓字体得到了广泛使用。在这些字体中,描述了字形的轮廓,表示系统以所需的位置和大小呈现轮廓。

Over time, a number of standard formats for recording font descriptions have evolved. Internet Media Types [RFC6838] are used to label content carried over Internet protocols. This document defines a new top-level type "font" according to Section 4.2.7 of [RFC6838]. This top-level type indicates that the content specifies font data. Under this top-level type, different representation formats of fonts may be registered.

随着时间的推移,许多记录字体描述的标准格式已经发展起来。Internet媒体类型[RFC6838]用于标记通过Internet协议传输的内容。本文件根据[RFC6838]第4.2.7节定义了一种新的顶级类型“字体”。此顶级类型表示内容指定字体数据。在此顶级类型下,可以注册不同的字体表示格式。

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。

2. Background and Justification
2. 背景和理由

Historically, there has not been a registration of formats for fonts. More recently, there have been several representation formats registered as media subtypes under the "application" top-level type (for example, "application/font-woff"). However, with the rapid adoption of web fonts (based on the data from HTTP Archive [HTTP-Archive-Trends] showing a huge increase in web font usage from 1% in the end of 2010 to 50% across all sites in the beginning of 2015), custom fonts on the web have become a core web resource. As the in-depth analysis [Font-Media-Type-Analysis] shows, the lack of the intuitive top-level font type is causing significant confusion among developers -- while currently defined font subtypes are severely under-utilized, there are many more sites that already use nonexistent (but highly intuitive) media types such as "font/woff", "font/ttf", and "font/truetype". At the same time, the majority of sites resort to using generic types such as "application/octet-stream", "text/plain", and "text/html", or use unregisterable types such as "application/x-font-ttf".

从历史上看,没有字体格式的注册。最近,在“application”顶级类型(例如,“application/font-woff”)下,有几种表示格式注册为媒体子类型。然而,随着web字体的迅速采用(根据HTTP Archive[HTTP Archive Trends]的数据显示,所有网站的web字体使用率从2010年底的1%大幅增加到2015年初的50%),web上的自定义字体已成为核心web资源。正如深入分析[Font Media Type analysis]所显示的,缺乏直观的顶级字体类型在开发人员中造成了严重的混乱——虽然目前定义的字体子类型严重不足,但还有更多的网站已经使用了不存在的(但非常直观的)媒体类型,如“Font/woff”、“Font/ttf”,和“字体/truetype”。同时,大多数网站求助于使用通用类型,如“应用程序/八位字节流”、“文本/普通”和“文本/html”,或使用未注册类型,如“应用程序/x-font-ttf”。

Contrary to the expectations of the W3C WebFonts WG, which developed Web Open Font Format (WOFF), the officially defined media types such as "application/font-woff" and "application/font-sfnt" see a very limited use -- their adoption rates trail far behind as the actual use of web fonts continues to increase. The members of the W3C WebFonts WG concluded that the use of the "application" top-level type is not ideal. First, the "application" sub-tree is treated (correctly) with great caution with respect to viruses and other active code. Secondly, the lack of a top-level type means that there is no opportunity to have a common set of optional parameters, such as are specified here. Third, fonts have a unique set of licensing and usage restrictions, which makes it worthwhile to identify this general category with a unique top-level type.

与开发Web开放字体格式(WOFF)的W3C WebFonts工作组的期望相反,官方定义的媒体类型,如“应用程序/字体WOFF”和“应用程序/字体sfnt”的使用非常有限——随着Web字体的实际使用持续增加,它们的采用率远远落后。W3CWebFonts工作组的成员得出结论,使用“应用程序”顶级类型并不理想。首先,对于病毒和其他活动代码,“应用程序”子树的处理(正确)非常谨慎。其次,缺少顶级类型意味着没有机会拥有一组通用的可选参数,如这里指定的。第三,字体有一套独特的许可和使用限制,这使得用一种独特的顶级类型来识别这个通用类别是值得的。

The W3C WebFonts WG decided [WG-tlt] that the situation can be significantly improved if a set of font media types is registered using "font" as a dedicated top-level type. Based on the data analysis presented above, we conclude that it is the presence of simple and highly intuitive media types for images that caused their widespread adoption, where the correct usage of existing media types reaches over 97% for all subtypes in the "image" tree. The WG considers that, keeping in mind a rapid adoption of fonts on the web, the registration of the top-level media type for fonts along with the intuitive set of subtypes that reflect popular and widely used data formats would further stimulate the adoption of web fonts, significantly simplify web server configuration process, and facilitate the proper use of media types for fonts.

W3C WebFonts工作组决定[WG tlt],如果使用“字体”作为专用顶级类型注册一组字体媒体类型,则可以显著改善这种情况。基于上述数据分析,我们得出结论,正是图像的简单和高度直观的媒体类型导致了它们的广泛采用,现有媒体类型的正确使用率达到了“图像”树中所有子类型的97%以上。工作组认为,考虑到网络上字体的快速采用,注册字体的顶级媒体类型以及反映流行和广泛使用的数据格式的直观子类型集将进一步刺激网络字体的采用,显著简化网络服务器配置过程,并促进字体的媒体类型的正确使用。

3. Security Considerations
3. 安全考虑

Fonts are interpreted data structures that represent collections of different tables containing data that represent different types of information, including glyph outlines in various formats, hinting instructions, metrics and layout information for multiple languages and writing systems, rules for glyph substitution and positioning, etc. In particular, the hinting instructions for TrueType glyphs represent executable code that has the potential to be maliciously constructed (for example, intended to hang the interpreter). There are many existing, already standardized font table tags and formats that allow an unspecified number of entries containing predefined data fields for storage of variable-length binary data. Many existing font formats (TrueType [truetype-wiki], OpenType and OFF [opentype-wiki], SIL Graphite, WOFF, etc.) are based on the table-based SFNT (scalable font) format, which is extremely flexible, highly extensible, and offers an opportunity to introduce additional table structures when needed, in an upward-compatible way that would not affect existing font rendering engines and text layout implementations. However, this very extensibility may present specific security concerns -- the flexibility and ease of adding new data structures makes it easy for any arbitrary data to be hidden inside a font file. There is a significant risk that the flexibility of font data structures may be exploited to hide malicious binary content disguised as a font data component.

字体是解释数据结构,表示不同表格的集合,其中包含表示不同类型信息的数据,包括各种格式的字形轮廓、暗示说明、多种语言和书写系统的度量和布局信息、字形替换和定位规则,特别是,TrueType标志符号的提示指令表示可能被恶意构造的可执行代码(例如,用于挂起解释器)。有许多现有的、已经标准化的字体表标记和格式,允许包含预定义数据字段的未指定数量的条目来存储可变长度的二进制数据。许多现有的字体格式(TrueType[TrueType wiki]、OpenType和OFF[OpenType wiki]、SIL Graphite、WOFF等)都基于基于表格的SFNT(可缩放字体)格式,这种格式非常灵活、高度可扩展,并提供了在需要时引入其他表格结构的机会,以向上兼容的方式,不会影响现有的字体呈现引擎和文本布局实现。然而,这种可扩展性可能会带来特定的安全问题——添加新数据结构的灵活性和易用性使得任何任意数据都很容易隐藏在字体文件中。字体数据结构的灵活性可能被利用来隐藏伪装成字体数据组件的恶意二进制内容,这是一个很大的风险。

Fonts may contain 'hints', which are programmatic instructions that are executed by the font engine for the alignment of graphical elements of glyph outlines with the target display pixel grid. Depending on the font technology utilized in the creation of a font, these hints may represent active code interpreted and executed by the font rasterizer. Even though hints operate within the confines of the glyph outline conversion system and have no access outside the font rendering engine, hint instructions can be quite complex, and a maliciously designed complex font could cause undue resource consumption (e.g., memory or CPU cycles) on a machine interpreting it. Indeed, fonts are sufficiently complex that most (if not all) interpreters cannot be completely protected from malicious fonts without undue performance penalties.

字体可能包含“提示”,这是字体引擎执行的编程指令,用于将字形轮廓的图形元素与目标显示像素网格对齐。根据创建字体时使用的字体技术,这些提示可能表示由字体光栅化器解释和执行的活动代码。即使提示在字形轮廓转换系统的范围内运行,并且在字体呈现引擎之外没有访问权限,提示指令也可能相当复杂,恶意设计的复杂字体可能会在解释它的机器上造成过度的资源消耗(例如,内存或CPU周期)。事实上,字体非常复杂,大多数(如果不是全部的话)解释器都无法在没有不当性能惩罚的情况下完全免受恶意字体的攻击。

Widespread use of fonts as necessary components of visual content presentation warrants that careful attention should be given to security considerations whenever a font is either embedded into an electronic document or transmitted alongside media content as a linked resource. While many existing font formats provide certain levels of protection of data integrity (such mechanisms include, e.g., checksums and digital signatures), font data formats provide

字体作为视觉内容呈现的必要组成部分的广泛使用,保证了在将字体嵌入电子文档或作为链接资源与媒体内容一起传输时,应仔细考虑安全问题。虽然许多现有字体格式提供了一定程度的数据完整性保护(此类机制包括校验和和数字签名等),但字体数据格式提供

neither privacy nor confidentiality protection internally; if needed, such protection should be provided externally.

内部既没有隐私保护,也没有保密保护;如果需要,应在外部提供此类保护。

4. IANA Considerations
4. IANA考虑

This specification registers a new top-level type, "font", in the standards tree, adds it as an alternative value of "Type Name" in the media types registration form [Media-Type-Registration], and registers several subtypes for it.

本规范在标准树中注册了一个新的顶级类型“字体”,将其作为“类型名称”的备选值添加到媒体类型注册表[媒体类型注册],并为其注册了多个子类型。

4.1. Definition and Encoding
4.1. 定义和编码

The "font" as the primary media content type indicates that the content identified by it requires a certain graphic subsystem such as a font rendering engine (and, in some cases, a text layout and a shaping engine) to process it as font data, which in turn may require a certain level of hardware capabilities such as certain levels of CPU performance and available memory. The "font" media type does not provide any specific information about the underlying data format and how the font information should be interpreted -- the subtypes defined within a "font" tree name the specific font formats. Unrecognized subtypes of "font" should be treated as "application/ octet-stream". Implementations may pass unrecognized subtypes to a common font-handling system, if such a system is available.

作为主要媒体内容类型的“字体”表示由其标识的内容需要特定的图形子系统,如字体呈现引擎(在某些情况下,还有文本布局和成形引擎)将其作为字体数据进行处理,这反过来可能需要一定级别的硬件功能,例如一定级别的CPU性能和可用内存。“字体”媒体类型不提供任何有关基础数据格式以及如何解释字体信息的特定信息——“字体”树中定义的子类型将指定字体格式。无法识别的“字体”子类型应视为“应用程序/八位字节流”。如果通用字体处理系统可用,实现可能会将无法识别的子类型传递给该系统。

4.2. Fragment Identifiers for Font Collections
4.2. 字体集合的片段标识符

Fragment identifiers for font collections identify one font in the collection by the PostScript name (name ID=6) [ISO.14496-22.2015]. This is a string, no longer than 63 characters and restricted to the printable ASCII subset, codes 33 ? 126, except for the 10 characters '[', ']', '(', ')', '{', '}', '<', '>', '/', '%', which are forbidden by [ISO.14496-22.2015].

字体集合的片段标识符通过PostScript名称(名称ID=6)标识集合中的一种字体[ISO.14496-22.2015]。这是一个字符串,长度不超过63个字符,仅限于可打印的ASCII子集,代码33?126,但[ISO.14496-22.2015]禁止的10个字符“[”、“]'、“(”、“)”、“{”、“}'、“<”、“>”、“/”、“%”除外。

In addition, the following 6 characters could occur in the PostScript name but are forbidden in fragments by [RFC3986], and thus must be escaped: '"', '#', '\', '^', '`', '|'.

此外,以下6个字符可能出现在PostScript名称中,但[RFC3986]禁止出现在片段中,因此必须对其进行转义:“'”、“#'、“\”、“^'、“'、”、“|”。

If (following un-escaping) this string matches one of the PostScript names in the name table, that font is selected. For example, "#Foo-Bold" refers to the font with PostScript name "Foo-Bold" and "#Caret%5Estick" refers to the font with PostScript name "Caret^stick". If the name does not match, or if a fragment is not specified, the first font in the collection is matched. Note that the order of fonts in collections may change as the font is revised, so relying on a particular font in a collection always being first is unwise.

如果(在取消转义之后)此字符串与名称表中的一个PostScript名称匹配,则选中该字体。例如,“#Foo Bold”表示PostScript名称为“Foo Bold”的字体,“#插入符号%5Estick”表示PostScript名称为“插入符号^stick”的字体。如果名称不匹配,或者未指定片段,则集合中的第一个字体匹配。请注意,集合中字体的顺序可能会随着字体的修改而改变,因此依赖集合中的特定字体始终处于第一位是不明智的。

4.3. Registration Procedure
4.3. 登记程序

New font formats should be registered using the online form [Media-Type-Registration]. [RFC6838] should be consulted on registration procedures. In particular, the font specification should preferably be freely available. If the font format can contain multiple fonts, a fragment identifier syntax should also be defined.

应使用在线表格[媒体类型注册]注册新字体格式。注册程序应咨询[RFC6838]。特别是,字体规范最好是免费提供的。如果字体格式可以包含多个字体,则还应定义片段标识符语法。

Note that new parameter sub-values may be defined in the future. If an implementation does not recognize a sub-value in the comma-separated list, it should ignore the sub-value and continue processing the other sub-values in the list.

请注意,将来可能会定义新的参数子值。如果实现无法识别逗号分隔列表中的子值,则应忽略该子值并继续处理列表中的其他子值。

4.4. Subtype Registrations
4.4. 子类型注册

In this section, the initial entries under the top-level 'font' media type are specified. They also serve as examples for future registrations.

在本节中,将指定顶级“字体”媒体类型下的初始条目。它们也可作为今后注册的范例。

For each subtype, an @font-face format identifier is listed. This is for use with the @font-face src descriptor, defined by the Cascading Style Sheets Level 3 (CSS3) Fonts specification [W3C.CR-css-fonts-3-20131003]. That specification is normative; the identifiers here are informative.

对于每个子类型,都会列出@font-face格式标识符。这用于@font-face src描述符,由级联样式表级别3(CSS3)字体规范[W3C.CR-css-Fonts-3-20131003]定义。该规范是规范性的;这里的标识符是信息性的。

4.4.1. Generic SFNT Font Type
4.4.1. 通用SFNT字体类型

Type name: font

类型名称:字体

Subtype name: sfnt

子类型名称:sfnt

Required parameters: None

所需参数:无

Optional parameters:

可选参数:

1) Name: outlines

1) 名称:大纲

Values: a comma-separated subset of True Type Font (TTF), Compact Font Format (CFF), and SVG

值:以逗号分隔的True Type字体(TTF)、紧凑字体格式(CFF)和SVG子集

This parameter can be used to specify the type of outlines provided by the font. The value "TTF" shall be used when a font resource contains glyph outlines in TrueType format, the value "CFF" shall be used to identify fonts containing PostScript/CFF outlines [cff-wiki], and the value SVG [svg-wiki] shall be used to identify fonts that include SVG outlines. TTF, CFF, or SVG outlines can be present in various

此参数可用于指定字体提供的轮廓类型。当字体资源包含TrueType格式的字形轮廓时,应使用值“TTF”,值“CFF”用于标识包含PostScript/CFF轮廓的字体[CFF wiki],值SVG[SVG wiki]用于标识包含SVG轮廓的字体。TTF、CFF或SVG大纲可以以多种形式呈现

combinations in the same font file; therefore, this optional parameter is a list containing one or more items, separated by commas. Order in the list is not significant.

同一字体文件中的组合;因此,此可选参数是包含一个或多个项目的列表,用逗号分隔。列表中的顺序并不重要。

2) Name: layout

2) 名称:布局

Values: a comma-separated subset of OTL, Apple Advanced Typography (AAT), and SIL

值:OTL、Apple高级排版(AAT)和SIL的逗号分隔子集

This parameter identifies the type of implemented support for advanced text layout features. The predefined values "OTL", "AAT", and "SIL", respectively, indicate support for OpenType text layout, Apple Advanced Typography, or Graphite SIL. More than one shaping and layout mechanism may be provided by the same font file; therefore, this optional parameter is a list containing one or more items, separated by commas. Order in the list is not significant.

此参数标识实现的对高级文本布局功能的支持类型。预定义值“OTL”、“AAT”和“SIL”分别表示支持OpenType文本布局、Apple Advanced排版或Graphite SIL。同一字体文件可以提供多个整形和布局机制;因此,此可选参数是包含一个或多个项目的列表,用逗号分隔。列表中的顺序并不重要。

Encoding considerations: Binary

编码注意事项:二进制

Interoperability considerations: As it was noted in the first paragraph of the Security Considerations section, a single font file can contain encoding of the same glyphs using several different representations, e.g., both TrueType and PostScript (CFF) outlines. Existing font rendering engines may not be able to process some of the particular outline formats, and downloading a font resource that contains only an unsupported glyph data format would be futile. Therefore, it is useful to clearly identify the format of the glyph outline data within a font using an optional parameter, and allow applications to make decisions about downloading a particular font resource sooner. Similarly, another optional parameter identifies the type of text shaping and layout mechanism that is provided by a font.

互操作性注意事项:正如安全注意事项部分的第一段所述,单个字体文件可以包含使用几种不同表示法的相同字形编码,例如TrueType和PostScript(CFF)轮廓。现有字体呈现引擎可能无法处理某些特定的大纲格式,下载仅包含不受支持的字形数据格式的字体资源将是徒劳的。因此,使用可选参数清楚地标识字体内字形轮廓数据的格式非常有用,并允许应用程序更快地决定下载特定字体资源。类似地,另一个可选参数标识字体提供的文本成形和布局机制的类型。

Published specification: ISO/IEC 14496-22 "Open Font Format" (OFF) specification [ISO.14496-22.2015] being developed by ISO/IEC SC29/ WG11.

发布规范:ISO/IEC SC29/WG11正在制定ISO/IEC 14496-22“开放式字体格式”(OFF)规范[ISO.14496-22.2015]。

Applications that use this media type: All applications that are able to create, edit, or display textual media content.

使用此媒体类型的应用程序:所有能够创建、编辑或显示文本媒体内容的应用程序。

Note that "font/sfnt" is an abstract type from which the (widely used in practice) "font/ttf" and "font/otf" types are conceptually derived. Use of "font/sfnt" is likely to be rare in practice, and might be confined to:

请注意,“font/sfnt”是一种抽象类型,(在实践中广泛使用)“font/ttf”和“font/otf”类型是从概念上派生出来的。“字体/sfnt”的使用在实践中可能很少,可能仅限于:

Uncommon combinations such as "font/sfnt; layout=sil" that do not have a shorter type

不常见的组合,如“font/sfnt;layout=sil”,没有较短的类型

Cases where a new parameter value is registered

注册新参数值的情况

Test cases, experimentation, etc.

测试用例、实验等。

Additional information:

其他信息:

Magic number(s): The TrueType fonts and OFF / OpenType fonts containing TrueType outlines should use 0x00010000 as the 'sfnt' version number.

幻数:包含TrueType轮廓的TrueType字体和OFF/OpenType字体应使用0x00010000作为“sfnt”版本号。

The OFF / OpenType fonts containing CFF data should use the tag 'OTTO' as the 'sfnt' version number.

包含CFF数据的OFF/OpenType字体应使用标记“OTTO”作为“sfnt”版本号。

      File extension(s):  Font file extensions used for OFF / OpenType
         fonts: .ttf and .otf
        
      File extension(s):  Font file extensions used for OFF / OpenType
         fonts: .ttf and .otf
        

Typically, the .ttf extension is only used for fonts containing TrueType outlines, whereas the .otf extension can be used for any OpenType/OFF font, and either can be used with the TrueType or CFF outlines.

通常,.ttf扩展名仅用于包含TrueType轮廓的字体,而.otf扩展名可用于任何OpenType/OFF字体,并且可以与TrueType或CFF轮廓一起使用。

Macintosh file type code(s): (no code specified)

Macintosh文件类型代码:(未指定代码)

Macintosh Universal Type Identifier code: "public.font"

Macintosh通用类型标识符代码:“public.font”

@font-face Format: None

@字体格式:无

Fragment Identifiers: None

片段标识符:无

Deprecated Alias: The existing registration "application/font-sfnt" is deprecated in favor of "font/sfnt".

已弃用别名:现有注册“application/font-sfnt”已弃用,取而代之的是“font/sfnt”。

Person & email address to contact for further information: Vladimir Levantovsky (vladimir.levantovsky@monotype.com).

联系人和电子邮件地址,以获取更多信息:Vladimir Levantovsky(Vladimir。levantovsky@monotype.com).

Intended usage: COMMON

预期用途:普通

Restrictions on usage: None

使用限制:无

Author: The ISO/IEC 14496-22 "Open Font Format" specification is a product of the ISO/IEC JTC1 SC29/WG11.

作者:ISO/IEC 14496-22“开放式字体格式”规范是ISO/IEC JTC1 SC29/WG11的产品。

Change controller: The ISO/IEC has change control over this specification.

变更控制器:ISO/IEC对本规范具有变更控制权。

4.4.2. TTF Font Type
4.4.2. TTF字体类型

Type name: font

类型名称:字体

Subtype name: ttf

子类型名称:ttf

Required parameters: None

所需参数:无

Optional parameters:

可选参数:

Name: layout

名称:布局

Values: a comma-separated subset of OTL, AAT, and SIL

值:OTL、AAT和SIL的逗号分隔子集

This parameter identifies the type of support mechanism for advanced text layout features. The predefined values "OTL", "AAT", and "SIL" respectively indicate support for OpenType text layout, Apple Advanced Typography, or Graphite SIL. More than one shaping and layout mechanism may be provided by the same font file; therefore, this optional parameter is a list containing one or more items, separated by commas. Order in the list is not significant.

此参数标识高级文本布局功能的支持机制类型。预定义值“OTL”、“AAT”和“SIL”分别表示支持OpenType文本布局、Apple Advanced排版或Graphite SIL。同一字体文件可以提供多个整形和布局机制;因此,此可选参数是包含一个或多个项目的列表,用逗号分隔。列表中的顺序并不重要。

Encoding considerations: Binary

编码注意事项:二进制

Interoperability considerations: As it was noted in the first paragraph of Section 3, a single font file can contain encoding of the same glyphs using several different representations, e.g., both TrueType and PostScript (CFF) outlines. Existing font rendering engines may not be able to process some of the particular outline formats, and downloading a font resource that contains only an unsupported glyph data format would be futile. Therefore, it is useful to clearly identify the format of the glyph outline data within a font using an optional parameter, and allow applications to make decisions about downloading a particular font resource sooner. Similarly, another optional parameter identifies the type of text shaping and layout mechanism that is provided by a font.

互操作性注意事项:如第3节第一段所述,单个字体文件可以包含使用几种不同表示法的相同字形编码,例如TrueType和PostScript(CFF)轮廓。现有字体呈现引擎可能无法处理某些特定的大纲格式,下载仅包含不受支持的字形数据格式的字体资源将是徒劳的。因此,使用可选参数清楚地标识字体内字形轮廓数据的格式非常有用,并允许应用程序更快地决定下载特定字体资源。类似地,另一个可选参数标识字体提供的文本成形和布局机制的类型。

Published specification: ISO/IEC 14496-22 "Open Font Format" (OFF) specification [ISO.14496-22.2015] being developed by ISO/IEC SC29/ WG11.

发布规范:ISO/IEC SC29/WG11正在制定ISO/IEC 14496-22“开放式字体格式”(OFF)规范[ISO.14496-22.2015]。

Applications that use this media type: All applications that are able to create, edit, or display textual media content.

使用此媒体类型的应用程序:所有能够创建、编辑或显示文本媒体内容的应用程序。

Additional information:

其他信息:

Magic number(s): The TrueType fonts and OFF / OpenType fonts containing TrueType outlines should use 0x00010000 as the 'sfnt' version number.

幻数:包含TrueType轮廓的TrueType字体和OFF/OpenType字体应使用0x00010000作为“sfnt”版本号。

      File extension(s):  Font file extensions used for TrueType / OFF /
         OpenType fonts: .ttf and .otf
        
      File extension(s):  Font file extensions used for TrueType / OFF /
         OpenType fonts: .ttf and .otf
        

Typically, the .ttf extension is only used for fonts containing TrueType outlines, while the .otf extension may be used for any OpenType/OFF font, either with TrueType or CFF outlines.

通常,.ttf扩展名仅用于包含TrueType轮廓的字体,而.otf扩展名可用于任何OpenType/OFF字体,包括TrueType或CFF轮廓。

Macintosh file type code(s): (no code specified)

Macintosh文件类型代码:(未指定代码)

Macintosh Universal Type Identifier code: "public.truetype-font"

Macintosh通用类型标识符代码:“public.truetype字体”

@font-face Format: truetype

@字体面格式:truetype

Fragment Identifiers: None

片段标识符:无

Person & email address to contact for further information: Vladimir Levantovsky (vladimir.levantovsky@monotype.com).

联系人和电子邮件地址,以获取更多信息:Vladimir Levantovsky(Vladimir。levantovsky@monotype.com).

Intended usage: COMMON

预期用途:普通

Restrictions on usage: None

使用限制:无

Author: The ISO/IEC 14496-22 "Open Font Format" specification is a product of the ISO/IEC JTC1 SC29/WG11.

作者:ISO/IEC 14496-22“开放式字体格式”规范是ISO/IEC JTC1 SC29/WG11的产品。

Change controller: The ISO/IEC has change control over this specification.

变更控制器:ISO/IEC对本规范具有变更控制权。

4.4.3. OpenType Layout (OTF) Font Type
4.4.3. OpenType版面(OTF)字体类型

Type name: font

类型名称:字体

Subtype name: otf

子类型名称:otf

Required parameters: None

所需参数:无

Optional parameters

可选参数

Name: outlines

名称:大纲

Values: a comma-separated subset of TTF, CFF, and SVG

值:TTF、CFF和SVG的逗号分隔子集

This parameter can be used to specify the type of outlines provided by the font. The value "TTF" shall be used when a font resource contains glyph outlines in TrueType format, the value "CFF" shall be used to identify fonts containing PostScript/CFF outlines, and the value SVG shall be used to identify fonts that include SVG outlines. TTF, CFF, or SVG outlines can be present in various combinations in the same font file; therefore, this optional parameter is a list containing one or more items, separated by commas. Order in the list is not significant.

此参数可用于指定字体提供的轮廓类型。当字体资源包含TrueType格式的字形轮廓时,应使用值“TTF”,值“CFF”应用于识别包含PostScript/CFF轮廓的字体,值SVG应用于识别包含SVG轮廓的字体。TTF、CFF或SVG轮廓可以在同一字体文件中以各种组合呈现;因此,此可选参数是包含一个或多个项目的列表,用逗号分隔。列表中的顺序并不重要。

Encoding considerations: Binary

编码注意事项:二进制

Interoperability considerations: As it was noted in the first paragraph of the Security Considerations section, a single font file can contain encoding of the same glyphs using several different representations, e.g., both TrueType and PostScript (CFF) outlines. Existing font rendering engines may not be able to process some of the particular outline formats, and downloading a font resource that contains only unsupported glyph data format would be futile. Therefore, it is useful to clearly identify the format of the glyph outline data within a font using an optional parameter, and allow applications to make decisions about downloading a particular font resource sooner. Similarly, another optional parameter identifies the type of text shaping and layout mechanism that is provided by a font.

互操作性注意事项:正如安全注意事项部分的第一段所述,单个字体文件可以包含使用几种不同表示法的相同字形编码,例如TrueType和PostScript(CFF)轮廓。现有字体呈现引擎可能无法处理某些特定的大纲格式,下载仅包含不支持的字形数据格式的字体资源将是徒劳的。因此,使用可选参数清楚地标识字体内字形轮廓数据的格式非常有用,并允许应用程序更快地决定下载特定字体资源。类似地,另一个可选参数标识字体提供的文本成形和布局机制的类型。

Published specification: ISO/IEC 14496-22 "Open Font Format" (OFF) specification [ISO.14496-22.2015] being developed by ISO/IEC SC29/ WG11.

发布规范:ISO/IEC SC29/WG11正在制定ISO/IEC 14496-22“开放式字体格式”(OFF)规范[ISO.14496-22.2015]。

Applications that use this media type: All applications that are able to create, edit, or display textual media content.

使用此媒体类型的应用程序:所有能够创建、编辑或显示文本媒体内容的应用程序。

Additional information:

其他信息:

Magic number(s): The TrueType fonts and OFF / OpenType fonts containing TrueType outlines should use 0x00010000 as the 'sfnt' version number.

幻数:包含TrueType轮廓的TrueType字体和OFF/OpenType字体应使用0x00010000作为“sfnt”版本号。

The OFF / OpenType fonts containing CFF outlines should use the tag 'OTTO' as the 'sfnt' version number. There is no magic number for SVG outlines; these are always accompanied by either TrueType or CFF outlines, and thus use the corresponding magic number.

包含CFF轮廓的OFF/OpenType字体应使用标记“OTTO”作为“sfnt”版本号。SVG轮廓没有神奇的数字;这些总是伴随着TrueType或CFF轮廓,因此使用相应的幻数。

      File extension(s):  Font file extensions used for OFF / OpenType
         fonts: .ttf and .otf
        
      File extension(s):  Font file extensions used for OFF / OpenType
         fonts: .ttf and .otf
        

Typically, the .ttf extension is only used for fonts containing TrueType outlines, while the .otf extension can be used for any OpenType/OFF font, either with TrueType, CFF, or SVG outlines.

通常,.ttf扩展名仅用于包含TrueType轮廓的字体,而.otf扩展名可用于任何OpenType/OFF字体,包括TrueType、CFF或SVG轮廓。

Macintosh file type code(s): (no code specified)

Macintosh文件类型代码:(未指定代码)

Macintosh Universal Type Identifier code: "public.opentype-font"

Macintosh通用类型标识符代码:“public.opentype字体”

@font-face Format: opentype

@字体面格式:opentype

Fragment Identifiers: None

片段标识符:无

Person & email address to contact for further information: Vladimir Levantovsky (vladimir.levantovsky@monotype.com).

联系人和电子邮件地址,以获取更多信息:Vladimir Levantovsky(Vladimir。levantovsky@monotype.com).

Intended usage: COMMON

预期用途:普通

Restrictions on usage: None

使用限制:无

Author: The ISO/IEC 14496-22 "Open Font Format" specification is a product of the ISO/IEC JTC1 SC29/WG11.

作者:ISO/IEC 14496-22“开放式字体格式”规范是ISO/IEC JTC1 SC29/WG11的产品。

Change controller: The ISO/IEC has change control over this specification.

变更控制器:ISO/IEC对本规范具有变更控制权。

4.4.4. Collection Font Type
4.4.4. 集合字体类型

Type name: font

类型名称:字体

Subtype name: collection

子类型名称:集合

Required parameters: None

所需参数:无

Optional parameters

可选参数

Name: outlines

名称:大纲

Values: a comma-separated subset of TTF, CFF, and SVG

值:TTF、CFF和SVG的逗号分隔子集

This parameter can be used to specify the type of outlines provided by the font. The value "TTF" shall be used when a font resource contains glyph outlines in TrueType format, the value "CFF" shall be used to identify fonts containing PostScript/CFF outlines, and the value SVG shall be used to identify fonts that include SVG outlines. TTF, CFF, or SVG

此参数可用于指定字体提供的轮廓类型。当字体资源包含TrueType格式的字形轮廓时,应使用值“TTF”,值“CFF”应用于识别包含PostScript/CFF轮廓的字体,值SVG应用于识别包含SVG轮廓的字体。TTF、CFF或SVG

outlines can be present in various combinations in the same font file; therefore, this optional parameter is a list containing one or more items, separated by commas. Order in the list is not significant.

轮廓可以在同一字体文件中以各种组合呈现;因此,此可选参数是包含一个或多个项目的列表,用逗号分隔。列表中的顺序并不重要。

Encoding considerations: Binary

编码注意事项:二进制

Interoperability considerations: As it was noted in the first paragraph of the Security Considerations section, a single font file can contain encoding of the same glyphs using several different representations, e.g., both TrueType and PostScript (CFF) outlines. Existing font rendering engines may not be able to process some of the particular outline formats, and downloading a font resource that contains only unsupported glyph data format would be futile. Therefore, it is useful to clearly identify the format of the glyph outline data within a font using an optional parameter, and allow applications to make decisions about downloading a particular font resource sooner. Similarly, another optional parameter identifies the type of text shaping and layout mechanism that is provided by a font.

互操作性注意事项:正如安全注意事项部分的第一段所述,单个字体文件可以包含使用几种不同表示法的相同字形编码,例如TrueType和PostScript(CFF)轮廓。现有字体呈现引擎可能无法处理某些特定的大纲格式,下载仅包含不支持的字形数据格式的字体资源将是徒劳的。因此,使用可选参数清楚地标识字体内字形轮廓数据的格式非常有用,并允许应用程序更快地决定下载特定字体资源。类似地,另一个可选参数标识字体提供的文本成形和布局机制的类型。

Published specification: ISO/IEC 14496-22 "Open Font Format" (OFF) specification [ISO.14496-22.2015] being developed by ISO/IEC SC29/ WG11.

发布规范:ISO/IEC SC29/WG11正在制定ISO/IEC 14496-22“开放式字体格式”(OFF)规范[ISO.14496-22.2015]。

Applications that use this media type: All applications that are able to create, edit, or display textual media content.

使用此媒体类型的应用程序:所有能够创建、编辑或显示文本媒体内容的应用程序。

Additional information:

其他信息:

Magic number(s): The TrueType fonts and OFF / OpenType fonts containing TrueType outlines should use 0x00010000 as the 'sfnt' version number.

幻数:包含TrueType轮廓的TrueType字体和OFF/OpenType字体应使用0x00010000作为“sfnt”版本号。

The OFF / OpenType fonts containing CFF outlines should use the tag 'OTTO' as the 'sfnt' version number. There is no magic number for SVG outlines; these are always accompanied by either TrueType or CFF outlines, and thus use the corresponding magic number.

包含CFF轮廓的OFF/OpenType字体应使用标记“OTTO”作为“sfnt”版本号。SVG轮廓没有神奇的数字;这些总是伴随着TrueType或CFF轮廓,因此使用相应的幻数。

      File extension(s):  Font file extensions used for OFF / TrueType
         and OpenType fonts: .ttc
        
      File extension(s):  Font file extensions used for OFF / TrueType
         and OpenType fonts: .ttc
        

Macintosh file type code(s): (no code specified)

Macintosh文件类型代码:(未指定代码)

Macintosh Universal Type Identifier code: "public.truetype-collection-font"

Macintosh通用类型标识符代码:“public.truetype集合字体”

@font-face Format: collection

@字体格式:集合

Fragment Identifiers: See Section 4.2.

片段标识符:见第4.2节。

Person & email address to contact for further information: Vladimir Levantovsky (vladimir.levantovsky@monotype.com).

联系人和电子邮件地址,以获取更多信息:Vladimir Levantovsky(Vladimir。levantovsky@monotype.com).

Intended usage: COMMON

预期用途:普通

Restrictions on usage: None

使用限制:无

Author: The ISO/IEC 14496-22 "Open Font Format" specification is a product of the ISO/IEC JTC1 SC29/WG11.

作者:ISO/IEC 14496-22“开放式字体格式”规范是ISO/IEC JTC1 SC29/WG11的产品。

Change controller: The ISO/IEC has change control over this specification.

变更控制器:ISO/IEC对本规范具有变更控制权。

4.4.5. WOFF 1.0
4.4.5. WOFF 1.0

Type name: font

类型名称:字体

Subtype name: woff

子类型名称:woff

Required parameters: None

所需参数:无

Optional parameters: None

可选参数:无

Encoding considerations: Binary

编码注意事项:二进制

Interoperability considerations: None

互操作性注意事项:无

Published specification: This media type registration updates the WOFF specification [W3C.REC-WOFF-20121213] at W3C.

已发布规范:此媒体类型注册更新W3C上的WOFF规范[W3C.REC-WOFF-20121213]。

Applications that use this media type: WOFF is used by web browsers, often in conjunction with HTML and CSS.

使用这种媒体类型的应用程序:WOFF由web浏览器使用,通常与HTML和CSS结合使用。

Additional information:

其他信息:

Magic number(s): The signature field in the WOFF header MUST contain the "magic number" 0x774F4646 ('wOFF')

幻数:WOFF头中的签名字段必须包含“幻数”0x774F4646(“WOFF”)

File extension(s): woff

文件扩展名:woff

Macintosh file type code(s): (no code specified)

Macintosh文件类型代码:(未指定代码)

Macintosh Universal Type Identifier code: "org.w3.woff"

Macintosh通用类型标识符代码:“org.w3.woff”

@font-face Format: woff

@字体格式:woff

Fragment Identifiers: None

片段标识符:无

Deprecated Alias: The existing registration "application/font-woff" is deprecated in favor of "font/woff".

不推荐使用的别名:现有注册“application/font-woff”已不推荐使用,取而代之的是“font/woff”。

Person & email address to contact for further information: Chris Lilley (www-font@w3.org).

联系人和电子邮件地址,以获取更多信息:Chris Lilley(www-font@w3.org).

Intended usage: COMMON

预期用途:普通

Restrictions on usage: None

使用限制:无

Author: The WOFF specification is a work product of the World Wide Web Consortium's WebFonts working group.

作者:WOFF规范是万维网联盟WebFonts工作组的工作成果。

Change controller: The W3C has change control over this specification.

变更控制器:W3C对该规范具有变更控制权。

4.4.6. WOFF 2.0
4.4.6. 沃夫2.0

Type name: font

类型名称:字体

Subtype name: woff2

子类型名称:woff2

Required parameters: None

所需参数:无

Optional parameters: None

可选参数:无

Encoding considerations: Binary

编码注意事项:二进制

Interoperability considerations: WOFF 2.0 is an improvement on WOFF 1.0. The two formats have different Internet Media Types and different @font-face formats, and they may be used in parallel.

互操作性注意事项:WOFF2.0是对WOFF1.0的改进。这两种格式具有不同的互联网媒体类型和不同的@font-face格式,可以并行使用。

Published specification: This media type registration is extracted from the WOFF 2.0 specification [W3C.CR-WOFF2-20150414] at W3C.

已发布规范:此媒体类型注册摘自W3C的WOFF 2.0规范[W3C.CR-WOFF2-20150414]。

Applications that use this media type: WOFF 2.0 is used by web browsers, often in conjunction with HTML and CSS.

使用这种媒体类型的应用程序:WOFF 2.0由web浏览器使用,通常与HTML和CSS结合使用。

Additional information:

其他信息:

Magic number(s): The signature field in the WOFF header MUST contain the "magic number" 0x774F4632 ('wOF2')

幻数:WOFF头中的签名字段必须包含“幻数”0x774F4632(“wOF2”)

File extension(s): woff2

文件扩展名:woff2

Macintosh file type code(s): (no code specified)

Macintosh文件类型代码:(未指定代码)

Macintosh Universal Type Identifier code: "org.w3.woff2"

Macintosh通用类型标识符代码:“org.w3.woff2”

@font-face Format: woff2

@字体面格式:woff2

Fragment Identifiers: See Section 4.2.

片段标识符:见第4.2节。

Person & email address to contact for further information: Chris Lilley (www-font@w3.org).

联系人和电子邮件地址,以获取更多信息:Chris Lilley(www-font@w3.org).

Intended usage: COMMON

预期用途:普通

Restrictions on usage: None

使用限制:无

Author: The WOFF2 specification is a work product of the World Wide Web Consortium's WebFonts working group.

作者:WOFF2规范是万维网联盟WebFonts工作组的工作成果。

Change controller: The W3C has change control over this specification.

变更控制器:W3C对该规范具有变更控制权。

5. References
5. 工具书类
5.1. Normative References
5.1. 规范性引用文件

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.

[RFC2119]Bradner,S.,“RFC中用于表示需求水平的关键词”,BCP 14,RFC 2119,DOI 10.17487/RFC2119,1997年3月<http://www.rfc-editor.org/info/rfc2119>.

[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, <http://www.rfc-editor.org/info/rfc3986>.

[RFC3986]Berners Lee,T.,Fielding,R.,和L.Masinter,“统一资源标识符(URI):通用语法”,STD 66,RFC 3986,DOI 10.17487/RFC3986,2005年1月<http://www.rfc-editor.org/info/rfc3986>.

[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, DOI 10.17487/RFC6838, January 2013, <http://www.rfc-editor.org/info/rfc6838>.

[RFC6838]Freed,N.,Klensin,J.和T.Hansen,“介质类型规范和注册程序”,BCP 13,RFC 6838,DOI 10.17487/RFC6838,2013年1月<http://www.rfc-editor.org/info/rfc6838>.

[W3C.CR-css-fonts-3-20131003] Daggett, J., "CSS Fonts Module Level 3", World Wide Web Consortium CR CR-css-fonts-3-20131003, October 2013, <http://www.w3.org/TR/2013/CR-css-fonts-3-20131003>.

[W3C.CR-css-fonts-3-20131003]Daggett,J.,“css字体模块3级”,万维网联盟CR-css-fonts-3-20131003,2013年10月<http://www.w3.org/TR/2013/CR-css-fonts-3-20131003>.

[ISO.14496-22.2015] International Organization for Standardization, "Coding of audio-visual objects Part 22: Open Font Format", ISO Standard 14496-22, 10 2015, <http://standards.iso.org/ittf/PubliclyAvailableStandards/ c066391_ISO_IEC_14496-22_2015.zip>.

[ISO.14496-22.2015]国际标准化组织,“视听对象编码第22部分:开放式字体格式”,ISO标准14496-22,2015年10月<http://standards.iso.org/ittf/PubliclyAvailableStandards/ c066391_ISO_IEC_14496-22_2015.zip>。

[W3C.REC-WOFF-20121213] Kew, J., Leming, T., and E. Blokland, "WOFF File Format 1.0", World Wide Web Consortium Recommendation REC-WOFF-20121213, December 2012, <http://www.w3.org/TR/2012/REC-WOFF-20121213>.

[W3C.REC-WOFF-20121213]Kew,J.,Leming,T.,和E.Blokland,“WOFF文件格式1.0”,万维网联盟建议REC-WOFF-20121213,2012年12月<http://www.w3.org/TR/2012/REC-WOFF-20121213>.

[W3C.CR-WOFF2-20150414] Levantovsky, V. and R. Levien, "WOFF File Format 2.0", World Wide Web Consortium WD CR-WOFF2-20150414, March 2016, <https://www.w3.org/TR/2016/CR-WOFF2-20160315/>.

[W3C.CR-WOFF2-20150414]Levantovsky,V.和R.Levien,“WOFF文件格式2.0”,万维网联盟WD CR-WOFF2-20150414,2016年3月<https://www.w3.org/TR/2016/CR-WOFF2-20160315/>.

5.2. Informative References
5.2. 资料性引用

[cff-wiki] Wikipedia, "Compact Font Format", November 2016, <https://en.wikipedia.org/w/ index.php?title=PostScript_fonts&oldid=747740863>.

[cff wiki]维基百科,“紧凑字体格式”,2016年11月<https://en.wikipedia.org/w/ index.php?title=PostScript\u font&oldid=747740863>。

[opentype-wiki] Wikipedia, "OpenType", February 2017, <https://en.wikipedia.org/w/ index.php?title=OpenType&oldid=763528773>.

[opentype wiki]维基百科,“opentype”,2017年2月<https://en.wikipedia.org/w/ index.php?title=OpenType&oldid=763528773>。

[truetype-wiki] Wikipedia, "TrueType", January 2017, <https://en.wikipedia.org/w/ index.php?title=TrueType&oldid=759367886>.

[truetype wiki]维基百科,“truetype”,2017年1月<https://en.wikipedia.org/w/ index.php?title=TrueType&oldid=759367886>。

[svg-wiki] Wikipedia, "Scalable Vector Graphics", February 2017, <https://en.wikipedia.org/w/ index.php?title=Scalable_Vector_Graphics&oldid=763136508>.

[svg wiki]维基百科,“可缩放矢量图形”,2017年2月<https://en.wikipedia.org/w/ index.php?title=Scalable\u Vector\u Graphics&oldid=763136508>。

[HTTP-Archive-Trends] Kuetell, D., "HTTP Archive trend analysis", March 2015, <http://httparchive.org/trends.php?s=All&minlabel=Nov+15+2 010&maxlabel=Feb+15+2015#perFonts>.

[HTTP归档趋势]Kuetell,D.,“HTTP归档趋势分析”,2015年3月<http://httparchive.org/trends.php?s=All&minlabel=Nov+2010年2月15日&maxlabel=2015年2月15日#性能>。

[Font-Media-Type-Analysis] Kuetell, D., "Web Font Media Type (mime type) Analysis 2015", 2015, <http://goo.gl/zbDhUN>.

[字体媒体类型分析]Kuetell,D.,“2015年网络字体媒体类型(mime类型)分析”,2015年<http://goo.gl/zbDhUN>.

[WG-tlt] W3C, "ACTION-164: Bring widely used top-level type to w3c-ietf liaison", 2015, <https://www.w3.org/Fonts/WG/track/actions/164>.

[WG tlt]W3C,“行动-164:将广泛使用的顶级类型引入W3C ietf联络”,2015年<https://www.w3.org/Fonts/WG/track/actions/164>.

[Media-Type-Registration] IANA, "Application for a Media Type", <http://www.iana.org/form/media-types>.

[媒体类型注册]IANA,“媒体类型应用程序”<http://www.iana.org/form/media-types>.

Author's Address

作者地址

Chris Lilley W3C 2004 Route des Lucioles Sophia Antipolis 06902 France

Chris Lilley W3C 2004法国路索菲亚-安提波利斯06902

   Email: chris@w3.org
        
   Email: chris@w3.org