We recently released alternate versions of two Heisei (平成) fonts, specifically Heisei Mincho StdN W3 (平成明朝 StdN W3) and Heisei Kaku Gothic StdN W5 (平成角ゴシック StdN W5). As the “StdN” designator suggests, JIS2004 glyphs are the default for these two fonts (the Heisei “Std” fonts use JIS90 glyphs by default).
These two fonts also differ from the Heisei “Std” fonts in that they include significantly more glyphs. The Heisei fonts were developed by a consortium of companies, and Adobe is one of the member companies. Interestingly, JIS X 0213:2004 glyph data was developed only for Heisei Mincho W3 and Heisei Kaku Gothic W5, and JIS X 0212-1990 glyph data was developed only for the former font. So, one of my projects last year was to map as many of these glyphs as possible to Adobe-Japan1-6 CIDs.
As I wrote nearly a year ago, the Adobe-Identity-0 ROS is useful for building special-purpose fonts, especially CJK ones whose glyph coverage does not match one of our public ROSes. Our latest Adobe-Identity-0 ROS font is the open-source Adobe Blank, whose purposes and implementation details are described on our sister blog, Typblography.
Sequences are important in the context of Unicode, and UAX #34 (Unicode Named Character Sequences) is a good reference for Unicode sequences. The first type of sequence that typically comes to mind in the context of Japanese are Ideographic Variation Sequences (IVSes), which are registered and maintained by The Unicode Consortium via the Ideographic Variation Database (IVD). There are also Standardized Variation Sequences that are much more closely bound to the standard.
I will close this particular topic by detailing how to support these proposed standardized variants in OpenType/CFF fonts.
For fonts that are currently IVS-enabled, such as those that include Format 14 ‘cmap’ subtables with Adobe-Japan1 or Hanyo-Denshi IVSes, it is important to note that the proposed standardized variants can co-exist with them, at least in terms of being specified in the font. For the former, I created an Adobe-Japan1_sequences.txt file that includes all registered Adobe-Japan1 IVSes, along with 89 of the 1,002 proposed standardized variants. The 89 standardized variants are at the end of the file. AFDKO tools, such as makeotf and spot, already support these standardized variants. When building OpenType/CFF fonts using the makeotf tool, this file is specified as the argument of the “-ci” command-line option.
To continue from the December 26, 2012 article, I should first point out that there is a relationship between these 1,002 proposed standardized variants and IVSes (Ideographic Variation Sequences). Standardized variants are standardized, hence their name. IVSes, on the other hand, are registered via a process that is described in UTS #37 and administered by the IVD Registrar (which happens to me at the moment).
One problem that has been plaguing CJK Compatibility Ideographs is the fact that they are adversely affected by normalization. Regardless of which of the four normalization forms is applied—NFC, NFD, NFKC, or NFKD—they are converted to their canonical equivalents, which are CJK Unified Ideographs. This is a problem, particularly for Japan, because 75 kanji in JIS X 0213:2004 kanji map to CJK Compatibility Ideograph code points. Furthermore, 57 of these 75 kanji correspond to Jinmei-yō Kanji (人名用漢字), meaning that they are used for personal names. The bottom-line problem with CJK Compatibility Ideographs is that any application of normalization, by any process, will permanently remove any distinctions between a CJK Compatibility Ideograph and its canonical equivalent. Not all processes are under one’s direct control, meaning that it is impossible to guarantee that normalization will not be applied. My opinion is that it is prudent to assume that normalization will be applied, and that preemption is the best solution.
In the December 4, 2012 Old Hangul article I mentioned that the ‘ccmp’ GSUB feature that is referenced in Microsoft’s Developing OpenType Fonts for Korean Hangul Script document is not necessary. Jaemin Chung kindly pointed out to me that environments that do not yet support Unicode Version 5.2 still require the ‘ccmp‘ (Glyph Composition/Decomposition) GSUB feature to be present, otherwise proper shaping will not happen.
The main purpose of this short article is to provide a revised Perl script, named mkoldhangul-ccmp.pl, that adds a complete ‘ccmp’ GSUB feature definition for environments that do not yet support Unicode Version 5.2 (or greater). The sample glyph-map.txt datafile that maps the Unicode-based glyph names to CIDs is unchanged.
Okay. It is time to put some “K” into CJK…
Seriously, much of the content of this blog has been focused on Chinese and Japanese issues. This article will provide some much-deserved Korean content.
I spent the last few days coming to grips with Old Hangul (옛한글 yethangeul), specifically how to implement proper shaping using the three registered OpenType GSUB features, ‘ljmo‘ (Leading Jamo Forms), ‘vjmo‘ (Vowel Jamo Forms), and ‘tjmo‘ (Trailing Jamo Forms).
I like ASCII. Do I like ASCII because of all the wonderful things one can do with its extraordinarily large repertoire of 94 printable characters? Actually, yes. Before I defend that answer, I’d like to point out that ASCII has three important strengths: simplicity, robustness, and ubiquity. In other words, ASCII is simple in that it has a relatively small number of characters; it forms a subset of virtually every encoding, Unicode or otherwise; and is supported everywhere. In fact, ASCII can be used to represent Unicode through the use of notations. Richard Ishida‘s excellent Unicode Code Converter is an excellent way to explore the various notations that are currently in use.
10月10日水曜日、香港で開催されたATypI Hong Kong 2012にてAFDKOワークショプをおこないました。とても専門的な内容にもかかわらず、多くの方にご参加いただきありがとうございました。
３時間のワークショプの前半２時間は、Ken Lundeによる「Manipulating CID-Keyed Fonts Using AFDKO Tools」が行われ、後半１時間「Turning CID-Keyed Fonts Into OpenType Fonts Using AFDKO」を私が担当しました。
For those who make use of the extract-cids.pl, extract-gids.pl, or extract-names.pl tools, all of which are AFDKO tx tool filters and are included in AFDKO, and whose purpose is to list the glyphs in the specified font resource, I’d like to introduce a new tool, named glyph-list.pl, which combines their functionality, thus making font development simpler.
I had the opportunity this morning to present at ATypI Hong Kong 2012 about Kazuraki, specifically the details about its OpenType implementation. Hence, the title of the presentation is Kazuraki: Under The Hood. The purpose of this article is simply to make the presentation available.
Yesterday—meaning Wednesday, October 10th, 2012, Hong Kong Time (UTC+8)—I had the honor and privilege to present the first two hours of a three-hour ATypI Hong Kong 2012 workshop entitled Manipulating CID-Keyed Fonts Using AFDKO Tools. When I did a rough count, there were nearly 30 people in attendance. I’d like to use this opportunity to thank those who were able to attend, which meant that they made the effort to travel to this conference, and also chose to attend this workshop in lieu of attending presentations from the Typography & Reading and Typography & Culture tracks, or other concurrent workshops. I’d also like to provide to those who attended, and to those who were not able to attend, the presentation that I used to drive these two hours, which includes material that can be studied and referenced.
In addition to installing the latest-and-greatest version of AFDKO, the workshop attendees were also provide with the actual sample font data that I used to demonstrate the various workflows and techniques.
My hope is that these materials are useful to those who attended this workshop, and to those who were not able to do so. Enjoy!
Speaking of enjoy, that is what I plan to do for the remaining four days of this five-day conference. ☺
ATypI Hong Kong 2012 takes place next week, starting on Wednesday, October 10th, and ending on Sunday, October 14th. I will be there for all five days, and very much look forward to meeting many people face-to-face, some for the first time.
I will be speaking twice. The first time will be on the afternoon of October 10th, for the first two hours of the three-hour Manipulating CID-keyed Fonts Using AFDKO Tools workshop. My colleague, Masataka HATTORI (服部正貴), will be speaking for the last hour of the workshop.
The second time will be on the morning of October 11th as a twenty-minute presentation entitled Kazuraki: Under The Hood that immediately follows another twenty-minute presentation by two colleagues from our Tokyo office, Taro YAMAMOTO (山本太郎) and Ryoko NISHIZUKA (西塚涼子), entitled Kazuraki: Its Art & Design.
I declared my presentations final this morning, and the materials for the workshop have been prepared and were provided to those who registered.
I am excited…
One of the most useful bits of feedback that I received from my portion of the June 25, 2012 AFDKO Workshop was that I include workflow diagrams that visually explain how various tools and control files work together. While preparing to present the same material at ATypI Hong Kong 2012 on the afternoon of October 10, 2012, I spent last Friday and this week creating additional presentation slides that include such workflow diagrams.
The first set of ideographs to be encoded in Unicode (Version 1.1), which are referred to as CJK Unified Ideographs, are also referred to as the URO, which is an abbreviation for Unified Repertoire and Ordering. None of the other extensions are given this label. Extensions A through D have been standardized, and Extension E will soon be standardized. Only Extension A is in the BMP (Basic Multilingual Plane). Extension B and beyond are in Plane 2, which is called the SIP (Supplementary Ideographic Plane). What makes the URO special or unique?
As I wrote earlier today on our sibling blog, Typblography, a new version of AFDKO was release earlier this month. I want to use this opportunity to point out some of the changes and enhancements that affect font developers who work with CID-keyed fonts. The details are buried in the detailed Release Notes that Read Roberts prepared.
As described in the August 24, 2012 article, I am currently updating most of our OpenType Japanese fonts. One aspect of the update is to include the 32 additional IVSes, based on the March 2, 2012 version of the IVD (Ideographic Variation Database), which means that all of the kanji in Adobe-Japan1-6 now have a “plain text” representation. Another aspect of this particular update is to use the latest UTF-32 CMap resources, which include three additional mappings, one of which is U+9FCC that was appended to the URO (Unified Repertoire & Ordering) in Unicode Version 6.1. But, the topic of this article is about fixing a small number of glyphs, and the techniques that I used to do so.
Founded in 1987 by Yuan Ho and Seth Schneider, IMUG (International Multilingual User Group) has become Silicon Valley’s best user group for all matters related to internationalization, localization, and globalization. Meeting once a month, usually the third Thursday, IMUG meetings include a presentation by a distinguished member of the internationalization, localization, or globalization community. Adobe began hosting IMUG meetings in 2010 for odd-numbered months, and its Globalization Engineering Council serves as the official host. Even-numbered months are hosted by Google.
Regardless of whether you reside in the San Francisco Bay Area, I encourage you to attend IMUG meetings. Those that are hosted by Adobe are broadcasted via Adobe Connect, meaning that attendees need not be on site.
It seems that I have presented for IMUG six times, in 1995 (Adobe Systems’ CID-Keyed Fonts For Large Character Sets), 1999 (Adventures in Multilingual Publishing), 2005 (The Adobe-Japan1-6 Character Collection), 2008 (Ideographic Variation Sequences: Implementation Details), 2010 (Kazuraki: Adobe Systems’ Groundbreaking New Japanese Typeface), and 2011 (The Power of “Plain Text” & the Importance of Meaningful Content).
The next IMUG meeting, which will be hosted at Adobe, will include an intriguing presentation by Microsoft’s Michael Kaplan, which will be about new internationalization features in Windows 8, scheduled to be released on October 26, 2012, which is, by the way, approximately two months before our world ends. Please plan to attend, either in person or via Adobe Connect.
I spent part of this week staging the data for some minor glyph corrections for our Kozuka Mincho and Kozuka Gothic fonts—and those that are derived from them—and was reminded that the techniques I described in the February 27, 2012 article are incredibly useful and indeed time-saving. These same techniques were also conveyed during the AM session of the June 25, 2012 AFDKO Workshop, as shown is the presentation slide below: