OpenType

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
OpenType
Filename extension .otf, .ttf, .ttc
Internet media type application/font-sfnt[1][2]
Type code OTTO
Uniform Type Identifier (UTI) public.opentype-font
Developed by Microsoft & Adobe Systems
Latest release
1.7[3]
(17 March 2015; 9 years ago (2015-03-17))
Type of format Font file
Extended from TrueType, PostScript fonts
Standard ISO/IEC 14496-22:2015[4]

OpenType is a format for scalable computer fonts. It was built on its predecessor TrueType, retaining TrueType's basic structure and adding many intricate data structures for prescribing typographic behavior. OpenType is a registered trademark of Microsoft Corporation.[5][6]

The specification germinated at Microsoft, with Adobe Systems also contributing by the time of the public announcement in 1996. The specification continues to be developed actively and is migrating to an open format.[clarification needed]

Because of wide availability and typographic flexibility, including provisions for handling the diverse behaviors of all the world's writing systems, OpenType fonts are used commonly today on the major computer platforms.

History

OpenType's origins date to Microsoft's attempt to license Apple's advanced typography technology GX Typography in the early 1990s. Those negotiations failed, motivating Microsoft to forge ahead with its own technology, dubbed "TrueType Open" in 1994.[7] Adobe joined Microsoft in those efforts in 1996, adding support for the glyph outline technology used in its Type 1 fonts.

These efforts were intended by Microsoft and Adobe to supersede both Apple's TrueType and Adobe's Type 1 ("PostScript") font formats. Needing a more expressive font format to handle fine typography and the complex behavior of many of the world's writing systems, the two companies combined the underlying technologies of both formats and added new extensions intended to address those formats' limitations. The name OpenType was chosen for the combined technologies, and the technology was announced later that year.

Open Font Format

Adobe and Microsoft continued to develop and refine OpenType over the next decade. Then, in late 2005, OpenType began migrating to an open standard under the International Organization for Standardization (ISO) within the MPEG group, which had previously (in 2003) adopted OpenType 1.4 by reference for MPEG-4.[6][8][9][10] Adoption of the new standard reached formal approval in March 2007 as ISO Standard ISO/IEC 14496-22 (MPEG-4 Part 22) called Open Font Format (OFF, not to be confused with Web Open Font Format).[11] It is also sometimes referred to as "Open Font Format Specification" (OFFS).[6] The standard is technically equivalent to OpenType 1.4 specification, with appropriate language changes for ISO.[12] The second edition of the Open Font Format was published in 2009 (ISO/IEC 14496-22:2009) and it is declared as "technically equivalent" to the "OpenType font format specification".[13][14] It is a free, publicly available standard.[15]

By 2001 hundreds of OpenType fonts were on the market. Adobe finished converting their entire font library to OpenType toward the end of 2002. As of early 2005, around 10,000 OpenType fonts had become available, with the Adobe library comprising about a third of the total. By 2006, every major font foundry and many minor ones were developing fonts in OpenType format.[citation needed]

Description

  • TrueType outlines use quadratic Bézier curves.

  • CFF outlines use cubic Bézier curves.

OpenType uses the general sfnt structure of a TrueType font, but it adds several smartfont options that enhance the font's typographic and language support capabilities.

The glyph outline data in an OpenType font may be in one of two formats: either TrueType format outlines in a 'glyf' table, or Compact Font Format (CFF) outlines in a 'CFF ' table. (The table name 'CFF ' is four characters long, ending in a space character.) CFF outline data is based on the PostScript language Type 2 font format. However, the OpenType specification does not support the use of PostScript outlines in a TrueType Collection font file.

For many purposes, such as layout, it doesn't matter what the outline data format is, but for some purposes, such as rasterisation, it is significant. The OpenType standard does not specify the outline data format: rather, it accommodates any of several existing standards. Sometimes terms like "OpenType (PostScript flavor)", "Type 1 OpenType", "OpenType CFF", or "OpenType (TrueType flavor)" are used to indicate which outline format a particular OpenType font file contains.

OpenType has several distinctive characteristics:

  • Accommodates the Unicode character encoding (as well as others), so that it can support any writing script (or multiple scripts at once).
  • Accommodates up to 65,536 glyphs.
  • Advanced typographic "layout" features which prescribe positioning and replacement of rendered glyphs. Replacement features include ligatures; positioning features include kerning, mark placement, and baseline specification.
  • Cross-platform font files, which can be used without modification on Mac OS, Windows and Unix systems.
  • If no additional glyphs or extensive typographic features are added, OpenType CFF fonts can be considerably smaller than their Type 1 counterparts.

Comparison to other formats

Lua error in package.lua at line 80: module 'strict' not found. Compared with Apple Computer’s "GX Typography"—now called Apple Advanced Typography (AAT)—and with the SIL’s Graphite technology, OpenType is less flexible in typographic options, but superior in language-related options and support.[clarification needed] Nevertheless, OpenType has been adopted much more widely than AAT and Graphite, despite AAT being the older technology.

The free software Graphite technology has been packaged with the desktop publishing and document editing software, LibreOffice (it is included in both the Windows and Linux distributions, but not with Mac, as AAT is already present).

From a font developer’s perspective, OpenType is, for many common situations, easier to develop for than AAT or Graphite. First, the simple declarative substitutions and positioning of OpenType are more readily understood than AAT’s more complex state tables or the Graphite description language that resembles C syntax. Second, Adobe’s strategy of licensing at no charge the source code developed for its own font development, AFDKO (Adobe Font Development Kit for OpenType), allowed third-party font editing applications such as FontLab and FontMaster to add support with relative ease. Although Adobe’s text-driven coding support is not as visual as Microsoft’s separate tool, VOLT (Visual OpenType Layout Tool), the integration with the tools being used to make the fonts has been well received.

Another difference is that an OpenType support framework (such as Microsoft’s Uniscribe) needs to provide a fair bit of knowledge about special language processing issues to handle (for example: Arabic). With AAT or Graphite, the font developer has to encapsulate all that expertise in the font. This means that AAT and Graphite can handle any arbitrary language, but that it requires more work and expertise from the font developers. On the other hand, OpenType fonts are easier to make, but can only support complex text layout if the application or operating system knows how to handle them.

Prior to supporting OpenType, Adobe promoted multiple master fonts and expert fonts for high-end typography. Multiple master fonts lacked the controls for alternate glyphs and languages provided by OpenType, but provided smooth transitions between styles within a type family. Expert fonts were intended as supplementary fonts, such that all the special characters that had no place in the Adobe Standard Encoding character set – ligatures, fractions, small capitals, etc. – were placed in the expert font instead. Usage in applications was tricky, with, for example, typing a Z causing the ffl ligature to be generated. In modern OpenType fonts all these glyphs are encoded with their Unicode indices and selection method (i.e. under what circumstances that glyph should be used).

OpenType support

Basic Roman support

OpenType support may be divided into several categories.[citation needed] Virtually all applications and most modern operating systems have basic Roman support and work with OpenType fonts just as well as other, older formats. What is of particular interest apart from basic Roman support is: extended language support through Unicode, support for complex writing scripts such as Arabic and the Indic languages, and advanced typographic support for Latin script languages such as English.

Amongst Microsoft's operating systems, OpenType TT fonts (.TTF) are backward compatible and therefore supported by all Windows versions starting with Windows 3.1. OpenType PS fonts (.OTF) are supported in all Windows versions starting with Windows 2000; Adobe Type Manager is required to be installed on Windows 95/98/NT/Me for basic Roman support (only) of OpenType PS fonts.

Extended language support

Extended language support via Unicode for both OpenType and TrueType is present in most Windows applications (including Microsoft Office Publisher, most Adobe applications, and Microsoft Office 2003, though not Word 2002), CorelDRAW X3 and newer, and many Mac OS X applications, including Apple's own such as TextEdit, Pages and Keynote. It is also widely supported in free operating systems, such as Linux (e.g. in multiplatform applications like AbiWord, Gnumeric, Calligra Suite, Scribus, OpenOffice.org 3.2 and later versions,[16] etc.).

OpenType support for complex written scripts has so far mainly appeared in Microsoft applications in Microsoft Office, such as Microsoft Word and Microsoft Publisher. Adobe InDesign provides extensive OpenType capability in Japanese but does not directly support Middle Eastern or Indic scripts— though a separate version of InDesign is available that supports Middle Eastern scripts such as Arabic and Hebrew. Undocumented functionality in many Adobe Creative Suite 4 applications, including InDesign, Photoshop and Illustrator, enables Middle Eastern, Indic and other languages, but is not officially supported by Adobe, and requires third-party plug-ins to provide a user interface for the features.

Advanced typography

Advanced typographic support for Latin script languages first appeared in Adobe applications such as Adobe InDesign, Adobe Photoshop and Adobe Illustrator. QuarkXPress 6.5 and below were not Unicode compliant. Hence text in these versions of QuarkXPress that contains anything other than WinANSI/MacRoman characters will not display correctly in an OpenType font (nor in other Unicode font formats, for that matter). However, in QuarkXPress 7, Quark offered support similar to Adobe's. Corel's CorelDRAW introduced support for OpenType typographic features in version X6. Mellel, a Mac OS X-only word processor from Redlers, claims parity in typographic features with InDesign, but also extends the support to right-to-left scripts; so does the Classical Text Editor, a specialized word processor developed at the Austrian Academy of Sciences.

As of 2009, popular Windows word processors did not support advanced OpenType typography features. Advanced typography features are implemented only in high-end desktop publishing software. The text engine from Windows Presentation Foundation, which is a managed code implementation of OpenType, is the first Windows API to expose OpenType features to software developers, supporting both OpenType TrueType, and OpenType CFF (Compact Font Format) fonts. It supports advanced typographic features such as ligatures, old-style numerals, swash variants, fractions, superscript and subscript, small capitalization, glyph substitution, multiple baselines, contextual and stylistic alternate character forms, kerning, line-level justification, ruby characters etc. WPF applications automatically gain support for advanced typography features. OpenType ligatures are accessible in Microsoft Office Word 2010.[17]

Windows 7 introduced DirectWrite, a hardware accelerated native DirectX API for text rendering with support for multi-format text, resolution-independent outline fonts, ClearType, advanced OpenType typography features, full Unicode text, layout and language support and low-level glyph rendering APIs.[18]

On Mac OS X, AAT-supporting applications running on Mac OS X 10.4 and later, including TextEdit and Keynote, get considerable OpenType support. Apple's support for OpenType in Mac OS X 10.4 included most advanced typographic features necessary for Latin script languages, such as small caps, oldstyle figures, and various sorts of ligatures, but it did not yet support contextual alternates, positional forms, nor glyph reordering as handled by Microsoft's Uniscribe library on Windows. Thus, Mac OS X 10.4 did not offer support for Arabic or Indic scripts via OpenType (though such scripts are fully supported by existing AAT fonts). Mac OS X 10.5 has improved support for OpenType and supports Arabic OpenType fonts. Gradually, the OpenType typography support has improved on newer Mac OS X versions (e.g. Mac OS X 10.10 can handle much better long contextual glyph substitutions).

Bitstream Panorama, a line layout and text composition engine from Bitstream Inc., provides complete OpenType support for compact and standard Asian fonts, Arabic, Hebrew, Indic, Thai and over 50 other worldwide languages. The application supports key OpenType tables required for line layout, such as BASE, glyph definition (GDEF), glyph positioning (GPOS), and glyph substitution (GSUB). Panorama also offers complete support for advanced typography features, such as ligatures, swashes, small caps, ornaments, ordinals, superiors, old style, kerning, fractions, etc.

In free software environments such as Linux, OpenType rendering is provided by the FreeType project, included in free implementations of the X Window System such as X.org. Complex text handling is provided either by pango (calling HarfBuzz) or Qt. The XeTeX and LuaTeX systems allow TeX documents to use OpenType fonts, along with most of their typographic features. Linux version of LibreOffice v. 4.1 (and newer) supports many OpenType typography features, because it began to use more sophisticated HarfBuzz text shaping library.[19]

OpenType Feature File (.fea)

OpenType features are tedious to define using a GUI.[20] Consequently, Adobe standardized[21] a text specification format for feature files, which typically have a name ending in a .fea extension. These files can be compiled into the binary font container (.ttf or .otf) using Adobe FDK (AFDKO), FontLab or FontForge. The latter program implements a few features that are documented in the Adobe standard but are not implemented by AFDKO.[22]

Layout tags

OpenType Layout tags are 4-byte character strings that identify the scripts, language systems, features and baselines in an OpenType Layout font. Microsoft's Layout tag registry establishes conventions for naming and using these tags. OpenType features are created by using the tags in creating feature scripts that describe how characters are to be manipulated to make the desired feature. These feature scripts can be created and incorporated into OpenType fonts by advanced font editors such as FontLab Studio, AsiaFont Studio, and FontForge.

Operating system and application support for layout tags varies widely.

Script tags

Script tags identify the scripts (writing systems) represented in an OpenType typeface. Each tag corresponds to contiguous character code ranges in Unicode. A script tag can consist of 4 or fewer lowercase letters, such as arab for the Arabic alphabet, cyrl for the Cyrillic script and latn for the Latin alphabet. The math script tag, added by Microsoft for Cambria Math, has been added to the specification.[23][24]

Language system tags

Language system tags identify the language systems supported in an OpenType typeface. Examples include ARA for Arabic, ESP for Spanish, HYE for Armenian, etc. In general, the codes are not the same as ISO 639-2 codes.

Feature tags

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: OpenType feature tag list

A list of OpenType features with expanded descriptions is given list of typographic features.

Baseline tags

Baseline tags have a specific meaning when used in the horizontal writing direction (used in the 'BASE' table's HorizAxis table), vertical writing direction (used in the 'BASE' table's VertAxis table), or both.

Baseline Tag HorizAxis VertAxis
'hang' horizontal line from which the syllabograms seem to hang in the Tibetan script The same line in Tibetan vertical writing mode.
'icfb' Ideographic character face bottom edge baseline. Ideographic character face left edge baseline.
'icft' Ideographic character face top edge baseline. Ideographic character face right edge baseline.
'ideo' Ideographic em-box bottom edge baseline. Ideographic em-box left edge baseline.
'idtp' Ideographic em-box top edge baseline. Ideographic em-box right edge baseline.
'math' The baseline about which mathematical characters are centered. The baseline about which mathematical characters are centered in vertical writing mode.
'romn' The baseline used by simple alphabetic scripts such as Latin, Cyrillic and Greek. The alphabetic baseline for characters rotated 90 degrees clockwise for vertical writing mode.

Math

A set of tables that mirrors TeX math font metrics relatively closely was added by Microsoft initially to Cambria Math for supporting their new math editing and rendering engine in Office 2007 and later.[25][26] This extension was added to the ISO standard (ISO/IEC CD 14496-22 3rd edition) in April 2014.[27] Additional (usage) details are available in the Unicode technical report 25[28] and technical note 28.[29] Some of the new technical features (not present in TeX), such as "cut-ins" (which allows kerning of subscripts and subscripts relative to their bases[30]) and stretch stacks[31] have been patented by Microsoft.[32][33][34] Windows 8 supports OpenType math outside MS Office applications via the RichEdit 8.0 component.[35]

Besides Microsoft products, XeTeX and LuaTeX also have some level of support for these tables; support is more limited in XeTeX because it uses the traditional TeX math rendering engine (thus is cannot fully use some of the new features in OpenType math that extend TeX), while LuaTeX takes a more flexible approach by changing some of the internals of TeX's math rendering; in the words of Ulrik Vieth (2009): "More precisely, while XeTeX only provides access to the OpenType parameters as additional \fontdimens, LuaTeX uses an internal data structure based on the combined set of OpenType and TeX parameters, making it possible to supply missing values which are not supported in either OpenType math fonts or traditional TeX math fonts."[31] In 2013, XeTeX also gained support for cut-ins.[36]

The Gecko rendering engine used by the Firefox web browser also supports some OpenType math features in its MathML implementation.[37][38]

As of 2010, the set of fonts that supported OpenType math was fairly limited. Besides Cambria Math, three free fonts were available: Asana-Math, Neo Euler, and XITS.[39] More recently the Latin Modern and TeX Gyre fonts (a "LM-ization" of the standard PostScript fonts[40]) have also gained support for OpenType math.[41][42][43][44] As of 2014 the number of OpenType math fonts is still fairly limited.[45] A more up-to-date list is maintained on Mozilla's web site.[46]

Color

Apple added a color extension in Mac OS X Lion (and also to iOS 4+) for the purpose of implementing colored Emoji fonts. The codepoints for these come from Unicode 6.0. In Apple's implementation, the fonts were extended with colored PNG images using the AAT-specific ’sbix’ table.[47][48][49] Google has made a similar proposal but using a pair of CBDT/CBLC tables.[50] The Google version is implemented in FreeType 2.5.[51]

In Windows 8.1 Microsoft also added color support to fonts, first implemented in the Segoe UI Emoji font.[48][52][53][54] Microsoft's implementation however relies entirely on vector graphics:[48][55] two new OpenType tables were added in Microsoft's implementation: the COLR table allows layered glyphs and the CPAL (“Color Palette”) actually defines the colors for the layers. The multi-layer approach allows a backwards compatible implementation as well as varying the rendering depending on the color context surrounding the glyphs.[48] Microsoft has announced their intention to submit their color extension for standardization thorough ISO/IEC 14496-22.[56] According to Adam Twardoch: "At TypeCon [2013], Greg Hitchcock clarified the envisioned roles of the palettes: first palette is used by default for “dark on light” color situations while second palette is intended for use in “light on dark” situations. Additional palettes should be selectable by the user."[51]

Mozilla and Adobe have proposed adding full SVG support (including color but also animations) to OpenType fonts. Support is present since Firefox 26.[50] Two new OpenType tables are proposed for this purpose: one called SVG and one called CPAL.[57]

SING gaiji solution

In 2005, Adobe shipped a new technology in their Creative Suite applications bundle that offers a solution for "gaiji" (外字, Japanese for "outside character"). Ideographic writing scripts such as Chinese and Japanese do not have fixed collections of characters. They use thousands of glyphs commonly and tens of thousands less commonly. Not all glyphs ever invented and used in Far Eastern literature have even been catalogued. A typical font might contain 8,000 to 15,000 of the most commonly used glyphs. From time to time, though, an author needs a glyph not present in the font of choice. Such missing characters are known in Japan as gaiji, and they often disrupt work.

Another aspect of the gaiji problem is that of variant glyphs for certain characters. Often certain characters have been written differently over periods of time. It is not unusual for place names or personal family names to use a historical form of a character. Thus it is possible for an end user using standard fonts to be left unable to spell correctly either their own name or the name of the place where they live.

Several ways to deal with gaiji have been devised. Solutions that treat them as characters usually assign arbitrary Unicode values to them in the Private Use Areas (PUA). Such characters cannot be used outside the environment in which the association of the private Unicode to the glyph shape is known. Documents based on them are not portable. Other installations treat gaiji as graphics. This can be cumbersome because text layout and composition cannot apply to graphics. They cannot be searched for. Often their rendering looks different from surrounding characters because the machinery for rendering graphics usually is different from the machinery for rendering glyphs from fonts.

The SING (Smart INdependent Glyphlets)[58][59] technology that made its debut with Adobe's Creative Suite 2 allows for the creation of glyphs, each packaged as a standalone font, after a fashion. Such a packaged glyph is called a glyphlet. The format, which Adobe has made public, is based on OpenType. The package consists of the glyph outline in TrueType or CFF (PostScript style outlines) form; standard OpenType tables declaring the glyph's metrics and behavior in composition; and metadata, extra information included for identifying the glyphlet, its ownership, and perhaps pronunciation or linguistic categorization. SING glyphlets can be created using Fontlab's SigMaker3 application.

The SING specification states that glyphlets are to travel with the document they are used in. That way documents are portable, leaving no danger of characters in the document that cannot be displayed. Because glyphlets are essentially OpenType fonts, standard font machinery can render them. The SING specification also describes an XML format that includes all the data necessary for reconstituting the glyphlet in binary form. A typical glyphlet might require one to two kilobytes to represent.

Serbian cyrillic solution

Specific Russian (top) and proper Serbian/Macedonian (bottom) letters.

Serbian/Macedonian cyrillic uses some language specific glyphs. In Unicode these are encoded in a single code point. OpenType allows showing these language-specific glyphs.

See also

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ 6.0 6.1 6.2 Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Suitcase Type Foundry Information Guide Archived November 18, 2006 at the Wayback Machine
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Christopher Slye – OpenType feature files, ATypI 2006 slides
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found. (consent to non-chargeable online licence agreement required to download specification)
  25. ↑ http://blogs.msdn.com/b/murrays/archive/2006/11/15/lineservices.aspx
  26. ↑ http://ultrasparky.org/school/pdf/DanielRhatigan_Dissertation.pdf
  27. ↑ http://blogs.msdn.com/b/murrays/archive/2014/04/27/opentype-math-tables.aspx
  28. ↑ http://www.unicode.org/reports/tr25/
  29. ↑ http://www.unicode.org/notes/tn28/
  30. ↑ http://blogs.msdn.com/b/murrays/archive/2010/01/12/special-capabilities-of-a-math-font.aspx
  31. ↑ 31.0 31.1 https://www.tug.org/TUGboat/tb30-1/tb94vieth.pdf also at http://www.ntg.nl/maps/38/03.pdf
  32. ↑ http://www.google.com/patents/US7492366
  33. ↑ http://www.google.com/patents/US7242404
  34. ↑ http://www.google.com/patents/US7453463
  35. ↑ http://blogs.msdn.com/b/murrays/archive/2012/03/03/richedit-8-0-preview.aspx
  36. ↑ http://www.preining.info/blog/2013/06/tex-live-2013-released/
  37. ↑ http://fred-wang.github.io/MathUI2014/demos/4-mathml-fonts.html
  38. ↑ https://wiki.mozilla.org/MathML:Open_Type_MATH_Table
  39. ↑ http://www.tug.org/~vieth/papers/context2010/context-paper.pdf
  40. ↑ https://www.tug.org/TUGboat/tb27-2/tb87hagen-gyre.pdf
  41. ↑ http://www.gust.org.pl/projects/e-foundry/lm-math
  42. ↑ http://www.ctan.org/pkg/lm-math
  43. ↑ http://vimeo.com/51944975
  44. ↑ http://www.ctan.org/tex-archive/fonts/tex-gyre-math
  45. ↑ http://www.gust.org.pl/bachotex/2014-pl/presentations/tgm-final03web.pdf
  46. ↑ https://developer.mozilla.org/en-US/docs/Mozilla/MathML_Project/Fonts#MATH_fonts
  47. ↑ http://typographica.org/typeface-reviews/apple-color-emoji/
  48. ↑ 48.0 48.1 48.2 48.3 http://opentype.info/blog/2013/07/03/color-emoji-in-windows-8-1-the-future-of-color-fonts/
  49. ↑ https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6sbix.html
  50. ↑ 50.0 50.1 http://pixelambacht.nl/2014/multicolor-fonts/
  51. ↑ 51.0 51.1 http://blog.fontlab.com/font-tech/color-fonts/color-font-format-proposals/
  52. ↑ http://msdn.microsoft.com/en-us/goglobal/bb688099.aspx#W8.1
  53. ↑ http://www.charlespetzold.com/blog/2013/06/Multicolor-Font-Characters-in-Windows-8-1.html
  54. ↑ http://channel9.msdn.com/Events/Build/2013/3-191
  55. ↑ http://www.hanselman.com/blog/HowToEnterAndUseEmojiOnWindows81.aspx
  56. ↑ http://lwn.net/Articles/564944/
  57. ↑ http://www.w3.org/2013/10/SVG_in_OpenType/
  58. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ DeLaHunt, Jim. "SING: Adobe's New Gaiji Architecture". 26th Internationalization and Unicode Conference, September 2004. Retrieved 16 July 2009.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=OpenType&oldid=138080"