In exactly 10 days, Japan is expected to reveal the name of its next era that will begin on 2019-05-01.
This article will cover several important standards or events that are related to the two-kanji square ligature forms of the current era name, the previous three, and the forthcoming one.
This is a brief article to draw readers’ attention to my latest test font, which is a 12-font 65,535-glyph OpenType/CFF Collection that is intended to test how well an app or other font-consuming environment supports language tagging for East Asian text, to include the handling of localized strings, such as those for menu names in the 'name' table, and for named Stylistic Set 'GSUB' features.
The Variable Font Collection test fonts that were made available at the beginning of this month serve this purpose to some extent, but they also require an environment that supports not only Variable Fonts (aka OpenType/CFF2 fonts), but also Variable Font Collections (aka OpenType/CFF2 Collections). The main intent of this OpenType/CFF Collection is to remove the Variable Font baggage from the testing requirement. It also includes support for Macao SAR as a third form of Traditional Chinese, which was described in the previous article.
Please visit the open source Source LOCL Test project for more details, or to download the pre-built OpenType/CFF Collection binary from the Latest Release page.
This is a short article that is simply meant to draw developers’ attention to three OpenType/CFF2 Collections (aka Variable Font Collections) that I built this week, which are now available in the open source Variable Font Collection Test project. As stated in the project, the purpose of these Variable Font Collections is to simulate the Source Han and Noto CJK fonts deployed as Variable Fonts, to help make sure that the infrastructure—OSes, apps, layout engines, libraries, and so on—will support them. Remember that it took several years for Microsoft to support OpenType/CFF Collections (OTCs), which finally happened on 2016-08-02. In other words, this is not trivial.
“Everything that has a beginning, has an end. I see the end coming.” — The Oracle
To first provide some background, I started to work at Adobe right before we invented CID-keyed fonts. The first desktop (aka non-printer) deployment of CID-keyed fonts was in the form of “Naked-CID fonts” in 1993 or so, which required ATM (Adobe Type Manager) to be installed. While such fonts were available for Macintosh and Windows OSes, Naked-CID fonts for the latter OS were incredibly short-lived and therefore rare, and were subsequently replaced with OpenType/CFF fonts in the late 1990s. Naked-CID fonts for the former OS were replaced by “sfnt-wrapped CIDFonts” (aka “sfnt-CID fonts”) in the mid-1990s, and also required that ATM be installed. Adobe Tech Note #5180, entitled “CID-Keyed sfnt Font File Format for the Macintosh,” details the sfnt-wrapped CIDFont format, which is specific to Macintosh due to its use of a resource fork.
With that stated, fonts are among the most perpetual and resilient of digital resources, meaning that discontinuing support for legacy font formats cannot be done quickly, and many years must pass before it can be realistically considered.
日本語 (Japanese) はこちら
(Everything that is stated in this article applies to the corresponding Google-branded Pan-CJK typeface family, Noto Sans CJK. Likewise, any reference to Source Han Serif also applies to Noto Serif CJK.)
The last time that a new version of the Source Han Sans family, along with the Google-branded version, Noto Sans CJK, was released was in June of 2015 in the form of Version 1.004. I know from personal experience that a lot of planning, preparation, and work took place during the three years that followed, and the end result is Version 2.000 of both Pan-CJK typeface families.
If you’re interested in learning more details about some of the changes, enhancements, and additions that Version 2.000 offers, please continue reading this article.
日本語 (Japanese) はこちら
Flashback to almost exactly a year ago.
We released Ten Mincho (貂明朝) Version 1.000 during MAX Japan 2017, and I published this marten-laced article that provided technical details about its fonts. Now, a year later, and during MAX Japan 2018, we have released Version 2.003 of this cute and mischievous typeface family. Please continue to read if you have interest in details about the new and updated fonts that are included as part of this Japanese typeface family.
English (英語) here
（翻訳：Adobe Type チーム 山本太郎、西村美苗）
貂明朝のバージョン 1.000 をリリースしたのは、昨年の MAX Japan 2017 開催中のことだった。そのフォントの技術的な詳細に関しては、この記事を書いて、おまけに、貂の写真を何枚も貼り付けておいた。さて 1 年後の今、同じく MAX Japan 2018 の開催期間中に、この妖しくも可愛い書体ファミリーのバージョン 2.003 をリリースした。この日本語書体ファミリーに新たに追加されたフォントやその他の改善点について、技術的詳細を知りたい方はこの記事を参照されたい。
English (英語) here
（翻訳：Adobe Type チーム 山本太郎、西村美苗）
（この記事中の事項はすべて、Google の Pan-CJK 書体ファミリー、Noto Sans CJK にもあてはまる。源ノ明朝に言及している場合には Google の Noto Serif CJK にもあてはまる。）
源ノ角ゴシックファミリーを、Google により製品化されたバージョンである Noto Sans CJK ファミリーも含めて、バージョン 1.004 にアップデートしたのは、2015 年 6 月だった。以来、さまざまな計画を立案し、また膨大な量の準備と作業を積み重ねてきた。その結果、Pan-CJK フォントファミリー：源ノ角ゴシックと Noto Sans CJK のバージョン 2.000 が誕生した。
バージョン 2.000 での変更・改良点の詳細について関心があれば、以下を参照されたい。
Something extraordinary happened today.
This extraordinary event provided to me an opportunity to revisit the open source LOCL Test OpenType/CFF test font that I introduced over two years ago. I improved the language declarations in the 'locl' (Localized Forms) GSUB feature definition, and also made other minor tweaks, two of which can be seen in the image above.
The version of Adobe InDesign CC that was released today during Adobe MAX, Version 14.0, now supports language-tagging for a fifth East Asian language: Traditional Chinese for Hong Kong. This new language-tagging option appears as “Chinese: Hong Kong” in the Character Styles and Paragraph Styles panels, and as the same in the Character panel.
For those who were not aware, OpenType has supported language-tagging for Hong Kong, a flavor of Traditional Chinese, for over 10 years via the three-letter language tag ZHH, which was introduced in Version 1.5 (May 2008) of the OpenType Specification. ZHS is the language tag for Simplified Chinese, and ZHT is the one for Traditional Chinese, but for Taiwan. For Japanese and Korean, JAN and KOR are their language tags, respectively. I am very pleased that Adobe InDesign finally supports all five of these OpenType language tags.
The timing couldn’t have been better…
(After realizing that the retargeting of Adobe-Japan1-7 to include only two glyphs, and with a fairly predictable release date range, exhibited characteristics of a pregnancy, I became inspired to write the text for the Adobe-Japan1-6 is Expecting! article while flying from SJC to ORD on the morning of 2018-07-20. I also prepared the article’s images while in-flight. The passenger sitting next to me was justifiably giving me funny looks. My flight to MSN, which was the final destination to attend my 35th high school class reunion in greater-metropolitan Mount Horeb, was delayed three hours, and this gave me an opportunity to publish the article while still on the ground at ORD.)
What do we know about Japan’s new era name? First and foremost, its announcement is unlikely to occur before 2019-02-25, because doing so would divert attention away from the 30th anniversary of the enthronement, 2019-02-24, but it may occur as late as 2019-05-01, which is the date on which the new era begins. That’s effectively a two-month window of uncertainty.
Interestingly, the date 2019-05-01 takes place not only during UTC #159, which will be hosted by me at Adobe, but also during Japan’s Golden Week (ゴールデンウィーク), which may begin early to prepare for the imperial transition.
English (영어) here
2017년 6월 23일 제가 서울에 위치한 산돌의 사무실을 방문했을 때, 마지막 업데이트로부터 근 20년이 다 되어가는 Adobe-Korea1-2 (링크를 클릭하면 PDF가 다운로드됨)를 대체할 만한 새로운 한국어 글리프 세트를 개발하는 것에 대한 논의가 시작되었습니다. 그리고 이는 새로운 Adobe-KR-9 캐릭터 컬렉션의 첫 번째 공개 릴리스로 완결되었습니다. 본 글리프 세트는 네 번의 초안을 거쳐 완성되었습니다. 첫 번째 초안은 2017년 10월 1일, 두 번째 초안은 2017년 12월 19일, 세 번째 초안은 2018년 1월 8일, 그리고 2018년 3월 2일의 네 번째 초안을 거쳐 2018년 5월 15일 베타 릴리스가 공개되었습니다. 여기에는 전체 데이터 파일 세트, 대표적인 글리프들의 완전한 세트, 오픈타입/CFF 폰트의 모든 기능이 포함된 두 가지 예제, 그리고 기타 보조 자료가 포함되어 있습니다.
본 글리프 세트에 대한 아이디어가 탄생한 이래로 1년이 조금 넘게 지난 오늘, 첫 번째 공개 릴리스를 발표하게 된 것을 기쁘게 생각합니다. 베타 릴리스와 첫 번째 공개 릴리스 사이에 변경된 사항이 궁금하신 분들은 스펙의 이전 버전 변경사항 섹션을 참조하십시오. 첫 번째 공개 릴리스에 해당하는 Adobe-KR-9 CMap 리소스는 이제 CMap 리소스 프로젝트에서 사용이 가능합니다. 이 프로젝트를 방문하는 동안, 최신 출시 버전에서 1,990페이지의 UTF-32.pdf 파일을 다운로드하여 책갈피를 확인하시기 바랍니다. 이 버전은 UTF-32 CMap 리소스를 위한 글리프 테이블을 제공합니다.
한국어는 (Korean) 여기
What began on 2017-06-23 when I visited Sandoll‘s office in Seoul, which included discussions about developing a new Korean glyph set to replace Adobe-Korea1-2 (if you click the link, the PDF will download) that was last updated nearly 20 years ago, has culminated in the First Public Release of the new Adobe-KR-9 Character Collection. This glyph set went through four drafts—First Draft on 2017-10-01, Second Draft on 2017-12-19, Third Draft on 2018-01-18, and Fourth Draft on 2018-03-02—followed by a Beta Release on 2018-05-15 that included a complete set of data files, a complete set of representative glyphs, two fully-functional example OpenType/CFF fonts, and other collateral materials.
After a little over a year since the idea for this glyph set was born, I am pleased to announce that the First Public Release was issued today. For those who are curious about what changed between the Beta Release and the First Public Release, please reference the Changes Since Earlier Versions section of the specification. The Adobe-KR-9 CMap resources that correspond to the First Public Release are now available in the CMap Resources project. While visiting that project, be sure to download the bookmarked 1,990-page UTF-32.pdf file from the latest release that provides glyph tables for all UTF-32 CMap resources.
This is a brief article to report that the 16 SVSes (Standardized Variation Sequences) for eight full-width punctuation characters—U+3001 、 IDEOGRAPHIC COMMA, U+3002 。 IDEOGRAPHIC FULL STOP, U+FF01 ！ FULLWIDTH EXCLAMATION MARK, U+FF0C ， FULLWIDTH COMMA, U+FF0C ， FULLWIDTH COMMA, U+FF1A ： FULLWIDTH COLON, U+FF1B ； FULLWIDTH SEMICOLON & U+FF1F ？ FULLWIDTH QUESTION MARK—that I proposed in L2/17-436 were accepted for Unicode Version 12.0 during UTC #154 this week. After reading the Script Ad Hoc group’s comments, I prepared a revised version (L2/17-436R) that provided additional information as a response to the two comments, which included the table that is shown above, and this served as the basis for the discussions.
This all began with a proposal that I submitted four years ago, L2/14-006, which was resurrected as L2/17-056, and finally discussed during UTC #153 during which I received constructive feedback. This prompted me to split the proposal into two parts. The first part proposed the less-controversial SVSes, which are the ones that were accepted. The second part, L2/18-013, proposes the more controversial ones. I am fully expecting to revise the second part before it is discussed during UTC #155, which begins on 2018-04-30.
I would like to use this opportunity to solicit comments and feedback for L2/18-013, which would be taken into account when I revise it. (I also hope to receive feedback from the Script Ad Hoc group prior to UTC #155, which would also be taken into account.)
In closing, the 16 new SVSes should soon appear in The Pipeline.
Today’s article provides useful details for our relatively small number of customers who author documents with our flagship Creative Cloud apps and make use of CID-keyed OpenType SVG fonts. A rather broadly-deployed CID-keyed OpenType SVG typeface is the open source Source Han Code JP family, whose development details are described in the very first section of this article.
While it is fully possible to build OpenType fonts—CID-keyed or otherwise—that include an 'SVG ' (Scalable Vector Graphics) table, the infrastructure to support them in apps is still maturing. That is the purpose of this article, so please continue reading if the details interest or otherwise affect you.
Per a suggestion by a friend named Leroy, I recently renamed the multiple-style and multiple-family OTCs (OpenType Collections) in this open source repository which includes such OTCs that are based on the Adobe-branded Source Han and Google-branded Noto CJK families. These multiple-style and multiple-family OpenType Collections were described in this article from April of this year. The purpose of this particular article is to introduce better names for them besides Super OTC.
First, some background about Super OTCs…
Shortly after Source Han Sans and Noto Sans CJK were released, I came up with the idea of creating a single OpenType Collection that includes all languages and all weights, and the name Super OTC was coined. This was included in the Version 1.001 update (2014-09-12) as a fourth deployment format for both families, and each one included 28 fonts. These were expanded to 36 fonts when the HW (half-width, ASCII-only) fonts, which covered only the Regular and Bold weights, were added as part of the Version 1.002 update (2015-04-20). Source Han Serif and Noto Serif CJK included a Super OTC in their Version 1.000 release (2017-04-03).
One of my hobbies is apparently to explore various ways to stress-test Adobe products, and the target of today’s article happens to be recent adventures with Adobe InDesign and our Source Han families.
The background is that I produced Unicode-based glyph synopses as part of the Source Han Sans and Source Han Serif releases, but those PDFs show only up to 256 code points per page, and it takes several hundred pages to show their complete Unicode coverage. I also produced single-page PDFs that show all 65,535 glyphs. A Source Han Sans one is available here, and a Source Han Serif one is available here. However, they are not Unicode-based.
At seemingly every opportunity, whether via this blog or during public speaking engagements, I have made it abundantly clear that the Adobe-branded Source Han families share the same glyph set as the corresponding Google-branded Noto CJK families. That is simply because it is true. What requires a bit of explanation, however, is how the two typeface designs—Source Han Sans and Source Han Serif—differ. That is what this particular article is about.
As the Project Architect of these Pan-CJK typeface families, I have my fingers on all of the data that was used during their development, and for preparing each release. I can therefore impart some useful tidbits of information that cannot be found elsewhere.
To take the previous article further—and because I tend to have an urge to stress-test environments—I added two more Super OTCs to the Source Han Super OTC open source project this morning.
The release of Source Han Serif earlier this month, on 2017-04-03, gave me an opportunity to build yet another resource for stress-testing environments, particularly those that consume OpenType/CFF Collections. (This also continues to simplify file management by combining three Super OTCs into a much larger one.)
Early last August, I celebrated the release of Microsoft’s Windows 10 Anniversary Update (Version 1607, and also known as Redstone 1 or RS1), mainly because it represented the very first version of Windows OS to support OpenType/CFF Collections (aka OTCs). Alas, my favorite Source Han Sans—and now Source Han Serif—deployment format, the Super OTC that packs all of the fonts into a single and easy-to-manage font resource, could not be installed.