Google Developers Blog: web fonts
COLLECTED BY
Organization:
Internet Archive
The Internet Archive discovers and captures web pages through many different web crawls.
At any given time several distinct crawls are running, some for months, and some every day or longer.
View the web archive through the
Wayback Machine .
Wide17 was seeded with the "Total Domains" list of 256,796,456 URLs provided by Domains Index on June 26th, and crawled with max-hops set to "3" and de-duplication set "on".
The Wayback Machine - https://web.archive.org/web/20190427140538/https://developers.googleblog.com/search/label/web%20fonts
Posted by Xiangye Xiao and Jungshik Shin, Internationalization Engineering team
Today, in collaboration with Adobe, we are responding to the call for Serif! We
are pleased to announce Noto Serif CJK, the long-awaited companion to Noto
Sans CJK released in 2014 . Like Noto Sans CJK, Noto Serif CJK supports
Simplified Chinese, Traditional Chinese, Japanese, and Korean, all in one font.
A serif-style CJK font goes by many names: Song (宋体) in Mainland China,
Ming (明體) in Hong Kong, Macao and Taiwan, Minchō (明朝) in
Japan, and Myeongjo (명조) or Batang (바탕) in Korea. The names
and writing styles originated during the Song and Ming dynasties in China, when
China's wood-block printing technique became popular. Characters were carved
along the grain of the wood block. Horizontal strokes were easy to carve and
vertical strokes were difficult; this resulted in thinner horizontal strokes and
wider vertical ones. In addition, subtle triangular ornaments were added to the
end of horizontal strokes to simulate Chinese Kai (楷体) calligraphy. This style
continues today and has become a popular typeface style.
Serif fonts, which are considered more traditional with calligraphic aesthetics,
are often used for long paragraphs of text such as body text of web pages or
ebooks. Sans-serif fonts are often used for user interfaces of websites/apps and
headings because of their simplicity and modern feeling.
Design of '永' ('eternity') in Noto Serif and Sans CJK. This ideograph is famous for having the most important elements of calligraphic strokes. It is often used to evaluate calligraphy or typeface design.
The Noto Serif CJK package offers the same features as Noto Sans CJK:
It has comprehensive character coverage for the four languages. This
includes the full coverage of CJK Ideographs with variation support for four
regions, Kangxi radicals, Japanese Kana, Korean Hangul and other CJK symbols and
letters in the Unicode Basic Multilingual Plane of Unicode. It also provides a
limited coverage of CJK Ideographs in Plane 2 of Unicode, as necessary to
support standards from China and Japan.
Simplified Chinese
Supports GB 18030 and China’s latest standard Table of General Chinese Characters (通用规范汉字表) published in 2013.
Traditional Chinese
Supports BIG5, and Traditional Chinese glyphs are compliant to glyph standard of Taiwan Ministry of Education (教育部國字標準字體) .
Japanese
Supports all of the kanji in JIS X 0208, JIS X 0213, and JIS X 0212 to include all kanji in Adobe-Japan1-6.
Korean
Supports over 1.5 million archaic Hangul syllables and 11,172 modern syllables as well as all CJK ideographs in KS X 1001 and KS X 1002
Noto Serif CJK’s support of character and glyph set standards for the four languages
It respects diversity of regional writing conventions for the same
character. The example below shows the four glyphs of '述' (describe) in four
languages that have subtle differences.
From left to right are glyphs of '述' in S. Chinese, T. Chinese, Japanese and Korean. This character means "describe".
It is offered in seven weights: ExtraLight, Light, Regular, Medium,
SemiBold, Bold, and Black. Noto Serif CJK supports 43,027 encoded characters and
includes 65,535 glyphs (the maximum number of glyphs that can be included in a
single font). The seven weights, when put together, have almost a half-million
glyphs. The weights are compatible with Google's Material Design standard fonts, Roboto , Noto Sans and Noto Serif
(Latin-Greek-Cyrillic fonts in the Noto family).
Seven weights of Noto Serif CJK
It supports vertical text layout and is compliant with the Unicode vertical text layout
standard . The shape, orientation, and position of particular characters
(e.g., brackets and kana letters) are changed when the writing direction of
the text is vertical.
The sheer size of this project also required regional expertise! Glyph design
would not have been possible without leading East Asian type foundries Changzhou
SinoType Technology, Iwata
Corporation , and Sandoll Communications .
Noto Serif CJK is open source under the SIL Open
Font License, Version 1.1 . We invite individual users to install and use
these fonts in their favorite authoring apps; developers to bundle these fonts
with your apps, and OEMs to embed them into their devices. The fonts are free
for everyone to use!
Noto Serif CJK font download:
https://www.google.com/get/noto
Noto Serif CJK on GitHub:
https://github.com/googlei18n/noto-cjk
Adobe's landing page for this release: http://adobe.ly/SourceHanSerif
Source Han Serif on GitHub: https://github.com/adobe-fonts/source-han-serif/tree/release/
By Raph Levien, Engineer, Google Web Fonts One of Google’s core principles is that "fast is better than slow", and the Web Fonts team takes that to heart. We’re always looking for ways to make web fonts load faster, and that’s doubtless a key factor in our rapid user adoption . Today, we are announcing a new way to make web fonts smaller and faster, in collaboration with the Monotype Imaging Fonts.com Web Fonts team. Google Web Fonts now implements Monotype Imaging’s MicroType Express compression format, which yields an approximate 15% savings in file size over using gzip alone. This change will automatically speed up Google Web Fonts for Internet Explorer browsers (version 6 and up). We’re also actively working to offer improved compression with other modern browsers, including Google Chrome. We’ve kept the interface simple, so designers don’t need to update their integrations in any way — we’ll automatically upgrade the CSS snippet and font files so that site designers and visitors get their fonts faster. We’ve done this for previous speed optimizations as well, such as automatically stripping the hints (metadata used for improving rendering quality on Windows) when serving fonts to Mac, iOS, and Android clients. We expect that most future optimizations will also be automatic and transparent. Monotype Imaging has agreed to make MicroType Express available to the public at no cost; the license can be found at monotypeimaging.com/aboutus/mtx-license . We believe it’s friendly to both open source and proprietary implementations. Today, we are also releasing an implementation of MicroType Express compression as part of the Embedded OpenType converter in the open-source sfntly library, adding to the existing WOFF compression. The sfntly library, developed by the Google Internationalization Engineering team, serves as the core conversion engine in Google Web Fonts for subsetting, hint stripping, and related functions of our dynamic serving path. We hope that all web font services, as well as people hosting their own web fonts, will use sfntly to optimize font serving across the web. We are proud to be working with Monotype Imaging, and we look forward to learning more from designers, users, sites and other partners to advance the state of web fonts together!Raph Levien is an expert on fonts and graphics technologies. Raph designed Inconsolata , one of the fonts available on the Web Font API. Raph enjoys photography and spending time with his family. Posted by Scott Knaster , Editor
By Stuart Gill, sfntly Architect Today we’re releasing the sfntly font programming library as open source. Created by the Google Internationalization Engineering team, the sfntly Java and C++ library makes it easy for programmers to build high performance font manipulation applications and services. sfntly is really, really fast: Raph Levien, Google Web Fonts Engineer, says, "Using sfntly we can subset a large font in a millisecond. It’s faster than gzip'ing the result." Starting today, both Java and C++ programmers can use sfntly to quickly and easily develop code to read, edit, and subset OpenType and TrueType fonts. The Google Web Fonts team uses the Java version to dynamically subset fonts, and the Chrome/Chromium browser uses the C++ version to subset fonts for PDF printing. sfntly (\s-’font-lē\) was built from the ground up to provide high performance, an easy to use API, and both high-level and low-level access to font data. Font objects are both thread safe and high performance while still providing access for editing. After about a year of internal development sfntly is stable enough to move it into open source and share with others. Currently, sfntly has editing support for most core TrueType and OpenType tables, with support for more tables being added. Using sfntly’s basic sfnt table read and write capability, programmers can do basic manipulation of any of the many font formats that use the sfnt container, including TrueType, OpenType, AAT/GX, and Graphite. Tables that aren’t specifically supported can still be handled and round-tripped by the library without risk of corruption. sfntly is already capable of allowing many really exciting things to be done with fonts, but there is much more planned: expanding support for the rest of the OpenType spec and other sfnt-container font formats, other serialization forms, better higher level abstractions, and more. I encourage you to you join us on our journey as a user or a contributor.Stuart Gill is a Software Engineer in the Internationalization Engineering team at Google where he focuses on fonts and text. When not doing that he is playing the blues on his guitar, studying Japanese, or puttering about the house and garage. Posted by Scott Knaster , Editor
By Jeremie Lenfant-Engelmann, Google Web Fonts Engineer We’ve received lots of requests from developers for a dynamic feed of the most recent web fonts offered via Google Web Fonts . Such a feed would ensure that you can incorporate Google Web Fonts into applications and menus dynamically, without the need to hardcode any URLs. The benefits of this approach are clear. As Google Web Fonts continues to add fonts, these fonts can become immediately available within your applications and sites. To address this need, we’ve built the Google Web Fonts Developer API , which provides a list of fonts offered via Google Web Fonts. Results can be sorted by alpha, date added, popularity, number of styles available, and trending (which is a measure of fonts growing rapidly in usage). Check out the documentation to get started. Some developers have helped us test this new API over the last few months, and the results are already public. Take a look at TypeDNA’s photoshop plugin as well as Faviconist , an app that makes generating favicons as simple as can be, and Google Web Fonts Families , a list of Google Web Fonts that have more than one style. We look forward to seeing what you come up with!Jeremie Lenfant-Engelmann is a Software Engineer on the Google Web Fonts team. Posted by Scott Knaster , Editor
By Raph Levien, Engineer, Google Web Fonts Last week, the Google Web Fonts team announced a new feature on the Google Web Fonts Blog. Since we’re discussing this feature today at Google I/O , we’d like to share this news with Google Code Blog readers as well. Oftentimes, when you want to use a web font on your website or application, you know in advance which letters you’ll need. This often occurs when you’re using a web font in a logo or heading. That’s why we’re introducing a new beta feature to the Google Web Fonts API. The feature is called “text=”, and allows you to specify which characters you’ll need. To use it, simply add “text=” to your Google Web Fonts API requests. Here’s an example:<link href='http://fonts.googleapis.com/css?family=Special+Elite &text=MyText' rel='stylesheet' type='text/css'> Google will optimize the web font served based on the contents of this parameter. For example, if you only require a few letters for a logo, such as “MyText”, Google will return a font file that is optimized to those letters. Typically, that means Google will return a font file that contains only the letters you requested. Other times, Google might return a more complete font file, especially when that will lead to better caching performance. The “text=” parameter has the potential to dramatically cut down web font file size. In some preliminary studies, web fonts can be cut from 35k down to just 5k (or even smaller), if only short strings of text are required. If you have a longer string, you can shorten the request by removing duplicate characters, as the order of characters in the string doesn’t matter. Of course, the font you get back is optimized even if there are duplicate character in the request. The effect of this feature is even more pronounced on mobile devices, where connection speeds are limited. Using the text= parameter, you can ensure your users will have a great, quick loading experience. We’re happy to say that the feature also works for international fonts. There’s no need to also specify the subset= parameter, as text= has access to all the characters in the original font. To access Unicode characters, use standard technique of url-encoding the UTF-8 representation of the string. Therefore, ¡Hola! is represented as: text=%c2%a1Hola! . We hope you enjoy this new feature.Raph Levien is an expert on fonts and graphics technologies. Raph designed Inconsolata , one of the fonts available on the Web Font API. Raph enjoys photography and spending time with his family. Posted by Scott Knaster , Editor