Unified Font Object

From HandWiki
Short description: XML-based source file format for digital fonts
Unified Font Object (UFO)
Filename extension.ufo, .ufoz
Developed byTal Leming, Just van Rossum, Erik van Blokland, Ben Kiel, Frederik Berlaen
Initial releaseUFO 1
Latest release
UFO 3
Type of formatmacOS Package, XML, Property List
Open format?Yes
Websitehttp://unifiedfontobject.org

The Unified Font Object (UFO) is an XML-based source file format for digital fonts. It was created by Tal Leming, Just van Rossum and Erik van Blokland.[1] Contributors to the format also include Ben Kiel and Frederik Berlaen.[1] According to its creators, the UFO is a "future proof" open format that is designed to be "application independent", "human readable and human editable".[2]

History

The first version of the UFO format was created in 2003.[3] The most recent version, UFO 3, was released in 2012.[2]

RoboFog (1996–2003)

The idea for the Unified Font Object originated with a customized version of the font editor Fontographer 3.5.[4] Petr van Blokland, together with Just van Rossum and Erik van Blokland, and with assistance from David Berlow and Steven Paul of the Font Bureau, created and distributed on a subscription basis a customized version of Fontographer called RoboFog in 1996.[4][5] RoboFog allowed users to script in Python, a language Just's brother Guido van Rossum invented two years prior in 1994.[4][5][6] The tool became very popular among type designers because of the ability to automate tasks.[5]

In 1998, FontLab, rival font editor developer to Fontographer (then owned by Macromedia) added Python to version 2.0 of their application, partially due to the popularity of RoboFog.[4] On March 24, 2001, Apple released Mac OS X 10.0, a major rewrite of the Mac operating system.[7] Fontographer was by then too old to be ported to Mac OS X, so the RoboFog developers turned their attention to FontLab.[5]

RoboFab and the creation of UFO (2003–2009)

In February, 2003, at the TypoTechnica conference in Heidelberg, van Rossum, van Blokland and Baltimore-based type designer Tal Leming combined their existing FontLab API scripts into a Python module called RoboFab.[6][3] The group started going by the name "The RoboFab Consortium".[6] With RoboFab came a need for an interchange file format for transferring font data between RoboFog and FontLab.[4] In April, 2003, van Rossum started work on an XML-based file format for glyph data called the Glyph Interchange Format (GLIF).[3] In July, 2003, the group started work on the first UFO file format (later known as "UFO 1"), which used "GLIF for glyph information and Apple's .plist (also XML based and entirely cross platform) for any other data as listings, indices, etc."[3] The group intended to present it at the 2003 RoboThon conference, but its launch was delayed until March 14, 2004.[6][3]

The group introduced the UFO with the following manifesto:[4]

  1. The data must be human readable and human editable.
  2. The data should be application independent.
  3. Data duplication should be avoided unless absolutely necessary.

In the consortium's view, font data should be independent of font editors to avoid issues like Software rot, which the field of type design is particularly prone to, due to the long period of time that fonts take to develop and the relative lack of variety in font editing applications.[6]

Decentralization (2009–Present)

In 2009, UFO version 2 was announced at RoboThon 2009, bringing minor changes to the format.[8] A variety of applications outside of FontLab using the UFO format started to be written at around this time, such as Leming's kerning application MetricsMachine, van Blokland's interpolation application, Superpolator, and Frederik Berlaen's parametric design application, KalliCulator.[4][9]

At the request of David Berlow and Petr van Blokland, Frederik Berlaen started work in 2009 on a font editor that used the UFO as a native format.[4] Because of the network of apps now being used in the "UFO workflow", "the dependency of FontLab as a central drawing environment had created a bottleneck", in their view.[10] Berlaen presented his font editor RoboFont at ATypI 2011 in Reykjavík,[10] and gave it the tagline, "The missing UFO font editor".[11]

At RoboThon 2012, UFO 3 was announced, and Tal Leming was named “Benevolent Dictator for life” of the UFO format.[11] Major changes to the UFO include a reworking of how the format organizes design layers, and an introduction of a ZIP-compressed "UFOZ" format.[12]

Shortly thereafter, other font editing programs, such as Glyphs,[11][13] FontLab[14] and FontForge[15] started supporting the UFO as an interchange format.

The fourth version of the format, "UFO 4", is currently in the concept phase.[16]

Technical format

The UFO is a package; a file system directory that presents as a single file on MacOS. On Windows and other operating systems without support for packages, it appears as a normal file system directory with the extension ".ufo".[17]

UFOs are organized with XML-based Property List files in the main UFO file system directory, describing font-wide metadata, like font name and weight, as well as interactions between glyphs, like glyph groups and kerning.[17]

Files containing glyph outline data are contained in a directory one level down, one file per glyph.[17] These files end in ".glif", and are in an XML-based format called "Glyph Interchange Format (GLIF)".[18] GLIF files can describe glyph Bézier curves in cubic or quadratic formats.[19]

OpenType features in AFDKO feature syntax are stored in a plain text file in the main UFO file system directory, with the filename extension ".fea".[20]

Criticism

A common criticism of the format is that its structure (of sometimes hundreds of GLIF files) does not work well with online file hosting services like Dropbox.[21] This criticism led to the proposal and adoption of the "UFOZ" format, which is a UFO (version 3 and up) compressed into a ZIP archive.[12]

Another criticism of the UFO is that there is no normalized form, as the order of elements in its files and indent standards are left up to the editor.[17] This led to the creation of a few "UFO Normalizers", like the "psfnormalize" command in SIL International's "pysilfont" project,[17] and the "ufonormalizer" project by Tal Leming.[22]

Use in applications

The following are some applications that support the UFO format either natively or as an officially-supported interchange format.

Application Name Kind of Application Platform License
Area51 UFO Viewer, feature editor macOS Retail [4][11]
FontCreator Multipurpose font editor Windows Retail [23]
FontForge Multipurpose font editor Linux, Windows, macOS (through X11) Mix of GNU General Public License v3 and BSD license [15][24][25]
FontLab Multipurpose font editor Windows, macOS Retail [17][14]
Glyphs Multipurpose font editor macOS Retail [13][17]
KalliCulator Parametric font editor macOS Retail [9]
Metapolator Parametric font editor Online GNU General Public License [26]
MetricsMachine Kerning editor macOS Retail [4][11]
Prepolator Interpolation compatibility manager macOS Retail [4]
RoboFont Multipurpose font editor macOS Retail [17][27]
RoundingUFO Font outline rounding and inktrap tool macOS Retail [11]
Superpolator Multidimensional interpolation manager macOS Retail [4][11]
TruFont Multipurpose font editor macOS GNU General Public License [17][28]
UFOStretch Linear Interpolation App macOS Retail [4]

Use in open source font projects

The UFO format is a popular choice among open source font projects because the XML-based, multiple file format is compatible with collaborative version control systems like Git.[29] SIL International recommends UFO as the format for new font projects.[17]

  • Source Sans Pro and Source Code Pro by Adobe Originals[29][17]
  • Cooper Hewitt (typeface) by Chester Jenkins for Cooper Hewitt, Smithsonian Design Museum[30]
  • Nokyung, a font for the Tai Lue script and Andika Mtihani, both by SIL International.[17]
  • Parts of the Noto fonts project are available in the UFO format.[31]
  • Open Baskerville, an open source revival of Fry's Baskerville.[32]

Use in programming

The UFO file format translates easily to object-based representation[33] in code. In addition to RoboFab, the project that originated the UFO format, many closed and open source projects read and write UFOs, for instance the Adobe Font Development Kit for OpenType.[17]

See also

References

  1. ↑ 1.0 1.1 "Contributors". https://unifiedfontobject.org/contributors/. 
  2. ↑ 2.0 2.1 "Overview". http://unifiedfontobject.org/. 
  3. ↑ 3.0 3.1 3.2 3.3 3.4 "RoboFab Release History". 2008-10-04. http://www.robofab.org/history.html. 
  4. ↑ 4.00 4.01 4.02 4.03 4.04 4.05 4.06 4.07 4.08 4.09 4.10 4.11 4.12 Arista, Roberto (Autumn 2016). "RoboTools: L'influenza dell'open source sugli strumenti di produzione del carattere tipografico" (in it, en). Progetto Grafico 30 (AIAP Edizioni): 33–39. https://archive.org/details/arista-roberto-robotools-progetto-grafico-30/. 
  5. ↑ 5.0 5.1 5.2 5.3 Middendorp, Jan (2004). Dutch type. Rotterdam: 010 Publishers. pp. 187. ISBN 90-6450-460-1. OCLC 54880333. https://www.worldcat.org/oclc/54880333. 
  6. ↑ 6.0 6.1 6.2 6.3 6.4 Kiel, Ben (May 4, 2005). "An Introduction to RoboFab". https://typographica.org/on-typography/an-introduction-to-robofab/. 
  7. ↑ Siracusa, John (2001-04-02). "Mac OS X 10.0". https://arstechnica.com/apple/reviews/2001/04/macos-x.ars. 
  8. ↑ "UFO 2". https://unifiedfontobject.org/versions/ufo2/index.html. 
  9. ↑ 9.0 9.1 Typeface as program : applied research and development in typography = Le caractère typographique comme programme : recherche appliquée et développement en typographie. Peter Bilak, François Rappo, Pierre Keller, École cantonale d'art de Lausanne. Lausanne, Switzerland: École cantonale d'art de Lausanne. 2010. ISBN 978-3-03764-072-2. OCLC 630189661. https://www.worldcat.org/oclc/630189661. 
  10. ↑ 10.0 10.1 RoboFont. "The history of RoboFont". https://robofont.com/documentation/topics/robofont-history/. 
  11. ↑ 11.0 11.1 11.2 11.3 11.4 11.5 11.6 "Robothon 2012, RoboHint, and the Gerrit Noordzij Prize" (in en-US). https://typographica.org/on-typography/robothon-2012-robohint-and-the-gerrit-noordzij-prize/. 
  12. ↑ 12.0 12.1 "UFO 3". https://unifiedfontobject.org/versions/ufo3/index.html#storage-formats. 
  13. ↑ 13.0 13.1 "Working with UFO | Glyphs". https://glyphsapp.com/tutorials/working-with-ufo. 
  14. ↑ 14.0 14.1 "Font Formats". https://help.fontlab.com/fontlab/7/manual/Font-Formats/. 
  15. ↑ 15.0 15.1 "Technical Bulletin: UFO 3 Export". https://fontforge.org/en-US/bulletins/ufo3_2018_1/. 
  16. ↑ "UFO 4". https://unifiedfontobject.org/versions/ufo4/. 
  17. ↑ 17.00 17.01 17.02 17.03 17.04 17.05 17.06 17.07 17.08 17.09 17.10 17.11 17.12 "Font Development Best Practices: UFO". https://silnrsi.github.io/FDBP/en-US/UFO.html. 
  18. ↑ "Glyph Interchange Format". https://unifiedfontobject.org/versions/ufo3/glyphs/glif/. 
  19. ↑ "UFO: Unified Font Object". http://luc.devroye.org/fonts-43145.html. 
  20. ↑ "features.fea". https://unifiedfontobject.org/versions/ufo3/features.fea/. 
  21. ↑ Simonson, Mark (2014-06-12). "I didn't quite realize until recently: .ufo + Dropbox kind of sucks." (in en). https://twitter.com/marksimonson/status/477277781726736384. 
  22. ↑ Leming, Tal, ufonormalizer: Script to normalize the XML and other data inside of a UFO., https://github.com/unified-font-object/ufoNormalizer, retrieved 2022-02-22 
  23. ↑ "FontCreator features and benefits". https://www.high-logic.com/font-editor/fontcreator/features-and-benefits. 
  24. ↑ Willis, Nathan (2014-12-08). "A quick look at the new FontForge release [LWN.net"]. https://lwn.net/Articles/624623/. 
  25. ↑ Willis, Nathan. "Font and type development at LGM 2014". https://lwn.net/Articles/592959/. 
  26. ↑ "Metapolator – Free Font Editor for Designing Typeface Families" (in en). http://metapolator.com/home. 
  27. ↑ RoboFont. "Welcome to RoboFont!". https://robofont.com/documentation/topics/welcome-to-robofont/. 
  28. ↑ Willis, Nathan (April 27, 2016). "Introducing TruFont [LWN.net"]. https://lwn.net/Articles/684970/. 
  29. ↑ 29.0 29.1 "LWN.net Weekly Edition for August 29, 2013 [LWN.net"]. https://lwn.net/Articles/564371/. 
  30. ↑ "Cooper Hewitt: the typeface by Chester Jenkins | Cooper Hewitt, Smithsonian Design Museum" (in en-US). 2014-06-13. https://www.cooperhewitt.org/open-source-at-cooper-hewitt/cooper-hewitt-the-typeface-by-chester-jenkins/. 
  31. ↑ Liputan6.com (2020-11-25). "Inisiatif Google Melestarikan Bahasa Terancam Punah Lewat Noto Font" (in id). https://www.liputan6.com/tekno/read/4416403/inisiatif-google-melestarikan-bahasa-terancam-punah-lewat-noto-font. 
  32. ↑ "Open Baskerville". http://klepas.org/openbaskerville/. 
  33. ↑ Beckmann, Tom (2019) (in en). The font engineering platform collaborative font creation in a self-supporting programming environment. Justus Hildebrand, Corinna Jaschek, Eva Krebs, Alexander Löser, Marcel Taeumel, Tobias Pape. Potsdam. pp. 72. ISBN 978-3-86956-464-7. OCLC 1169672607. https://www.worldcat.org/oclc/1169672607. 

External links



Retrieved from "https://handwiki.org/wiki/index.php?title=Unified_Font_Object&oldid=3360601"