Posts in Category "Unicode"

Source Han Sans Version 2.000 Technical Tidbits

Posted on November 19, 2018 by Dr. Ken Lunde | Comments (11)

日本語 (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.
Continue reading…

Ten Mincho Redux: SVG & Text

Posted on November 19, 2018 by Dr. Ken Lunde | Comments (0)

日本語 (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.
Continue reading…

帰ってきた「貂明朝」：SVG と「テキスト」

Posted on November 10, 2018 by Dr. Ken Lunde | Comments (0)

English (英語) here

（翻訳：Adobe Type チーム 山本太郎、西村美苗）

あれからほぼ一年たった。

貂明朝のバージョン 1.000 をリリースしたのは、昨年の MAX Japan 2017 開催中のことだった。そのフォントの技術的な詳細に関しては、この記事を書いて、おまけに、貂の写真を何枚も貼り付けておいた。さて 1 年後の今、同じく MAX Japan 2018 の開催期間中に、この妖しくも可愛い書体ファミリーのバージョン 2.003 をリリースした。この日本語書体ファミリーに新たに追加されたフォントやその他の改善点について、技術的詳細を知りたい方はこの記事を参照されたい。
Continue reading…

「源ノ角ゴシック」バージョン 2.000 の技術的な特長について

Posted on November 10, 2018 by Dr. Ken Lunde | Comments (3)

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 での変更・改良点の詳細について関心があれば、以下を参照されたい。
Continue reading…

Revisiting “LOCL Test”

Posted on October 15, 2018 by Dr. Ken Lunde | Comments (0)

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…

🐡

2018 Unicode Bulldog Award

Posted on September 17, 2018 by Dr. Ken Lunde | Comments (1)

“Out of the blue.”

I was sitting near the back of a crowded room, filled with many familiar faces, when the two-day conference proper of IUC42 (42nd Unicode & Internationalization Conference) began promptly at 9AM on September 11, 2018, with Mark Davis, President of Unicode, making the opening statements. When Mark announced the recipient of this year’s Unicode Bulldog Award, it took me by complete surprise when I heard my name called. Wow. What an absolute honor. In fact, I would claim that this is one of the biggest honors of my life, especially given that Unicode now transcends so many aspects of our society. Looking back at the 27 prior recipients of this award, almost all of whom I consider to be friends, I am definitely in good company.

Luckily for this blog’s readership, Rick McGowan managed to capture all of my embarrassing moments in a three-minute video. You can also see the tweets that were published by @unicode and @AdobeType.

For better or worse, the proverbial bar has been raised, in terms of others’ expectations of me. I shall therefore endeavor not to disappoint. #MaximumEffort

🐡

“Strange Things Are Afoot at the Circle K” → U+327F ㉿

Posted on September 5, 2018 by Dr. Ken Lunde | Comments (3)

This week once again proved that one is never too old to learn something new.

My friends at Sandoll Communications (산돌커뮤니케이션) kindly informed me earlier this week that the offical Korean Standards Association (한국표준협회/韓國標準協會) logo, U+327F ㉿ KOREAN STANDARD SYMBOL, which has been encoded in Unicode from the very beginning (Version 1.1), is generic, both in terms of typeface design and weight, and that there is an actual specification for its design. This character is included in Unicode because it was also included in the KS X 1001 (정보 교환용 부호(한글 및 한자)) standard at position 02-62. The very bottom of the specification page on the KSA website includes a link to a ZIP file that contains the image for the KSA logo in two forms: a 592×840-pixel JPEG image and an Adobe Illustrator vector image file.
Continue reading…

About Adobe-Japan1-7 Font Names

Posted on September 2, 2018 by Dr. Ken Lunde | Comments (0)

日本語 (Japanese) はこちら

The feedback that we received from the previous article on this subject has been extraordinarily valuable. Our proposal to leave the names of Adobe-Japan1-7 subset fonts unchanged met with virtually unanimous agreement, but given the relatively minor nature of the Adobe-Japan1-7 additions, to the tune of only two glyphs, the same naming policy seems to benefit Adobe-Japan1-6 fonts as well.

In other words, fonts that currently support Adobe-Japan1-6 in its entirety can be updated to Adobe-Japan1-7 without changing their names. Of course, the advertised Supplement value as recorded in the 'CFF ' table should reflect 7. The following is a revised version of the table from the previous article on this subject:

Supplement Designator JIS2004-Savvy Designator /CIDFontName & Menu Name Examples
3 Std StdN KozMinStd-Regular, 小塚明朝 Std R
KozMinStdN-Regular, 小塚明朝 StdN R
4 Pro ProN KozMinPro-Regular, 小塚明朝 Pro R
KozMinProN-Regular, 小塚明朝 ProN R
5 Pr5 Pr5N KozMinPr5-Regular, 小塚明朝 Pr5 R
KozMinPr5N-Regular, 小塚明朝 Pr5N R
6 Pr6 Pr6N KozMinPr6-Regular, 小塚明朝 Pr6 R
KozMinPr6N-Regular, 小塚明朝 Pr6N R
7 Pr6 Pr6N KozMinPr6-Regular, 小塚明朝 Pr6 R
KozMinPr6N-Regular, 小塚明朝 Pr6N R

Of course, we still welcome any and all feedback about this font-naming issue.

🐡

Adobe-Japan1-7 のフォント名について

Posted on September 2, 2018 by Dr. Ken Lunde | Comments (0)

English (英語) here

先のブログ記事について、既にいくつか貴重なフィードバックを受け取っている。Adobe-Japan1-7 のサブセットとなるフォントの名前を変えずにそのままにしておくという提案については、ほぼ大方の賛同を得ることができたが、Adobe-Japan1-7 での追加が二つのグリフだけに限定されるため、Adobe-Japan1-6 対応のフォントについても、名前を変えない方が良いという意見があった。

言い換えれば、現時点で Adobe-Japan1-6 に対応しているフォントは、名前を変更せずに Adobe-Japan1-7 にアップデートできるということだ。もちろん、CFF テーブルに記録されるべき Supplement の値は「7」に設定しておく必要がある。この考えに沿って、前回の記事の表を以下のように修正した。

Supplement Designator JIS2004-Savvy Designator /CIDFontName & Menu Name Examples
3 Std StdN KozMinStd-Regular, 小塚明朝 Std R
KozMinStdN-Regular, 小塚明朝 StdN R
4 Pro ProN KozMinPro-Regular, 小塚明朝 Pro R
KozMinProN-Regular, 小塚明朝 ProN R
5 Pr5 Pr5N KozMinPr5-Regular, 小塚明朝 Pr5 R
KozMinPr5N-Regular, 小塚明朝 Pr5N R
6 Pr6 Pr6N KozMinPr6-Regular, 小塚明朝 Pr6 R
KozMinPr6N-Regular, 小塚明朝 Pr6N R
7 Pr6 Pr6N KozMinPr6-Regular, 小塚明朝 Pr6 R
KozMinPr6N-Regular, 小塚明朝 Pr6N R

もちろん、このフォント名の問題についてすべてのフィードバックを歓迎する。

🐡

IICore 2020 🤔

Posted on August 28, 2018 by Dr. Ken Lunde | Comments (0)

Page 697 of the Unicode Version 11.0 Core Specification includes an IICore subsection that states the following about its 9,810 ideographs: This coverage is of particular use on devices such as cell phones or PDAs, which have relatively stringent resource limitations. Various iterations of L2/18-066 attempted to tweak the existing IICore set based on my recent five-part analysis. I was even given a UTC #156 Action Item to update L2/18-066 once again.

However, after realizing that the “resource limitations” from about 15 years ago, which was when the current IICore set was established, no longer apply to today’s devices, I opted to propose a completely new version of IICore that would be tagged with its year of vintage, 2020, which is also the year in which the earliest version of Unicode that includes it would be released. While I intend to reveal more details later, what I plan to propose will include a little over 20K ideographs, and will be discussed during UTC #157 and IRG #51 later this year.

Edited To Add: The proposal was posted to the UTC document register on 2018-09-04 as L2/18-279, and is also available in the IRG #51 document register as IRG N2334. If anyone has any formal feedback for the UTC to consider during UTC #157, please use Unicode’s Contact Form.

🐡