Prepare to add U+32FF (new Japanese era character)

[jungshik]

See http://blog.unicode.org/2018/09/new-japanese-era.html about a new Japanese era expected to take effect in May 2019.

U+32FF was reserved in the Unicode for a new era character (a new character combining the two characters used in a new era name).

Noto CJK need to prepare for adding the glyph for U+32FF as soon as it's announced.

[kenlunde]

An issue isn't necessary for this, as the 2018-08-08 CJK Type Blog article covers this in more than enough detail. This was also discussed during the 2018-08-06 Adobe/Google meeting (see agenda item 6).

In any case, the Source Han Sans / Noto Sans CJK Version 2.000 update will include two placeholder (blank) glyphs for U+32FF ㋿, uni32FF and uni32FF-V, so that the dot-release next Spring will be a smooth and quick experience. Because this is completely on the radar, and already in the Version 2.000 glyph set, I recommend that this issue be closed.

[epico]

BTW, when will the Noto CJK Serif fonts be updated for new Japanese era?

[kenlunde]

The high priority was to update Noto Sans CJK (and Source Han Sans). The Version 2.000 update for Noto Serif CJK (and Source Han Serif) is quite involved, and the release is likely to be late next year. The glyphs for U+32FF ㋿, uni32FF-JP and uni32FF-JP-V, will be added as part of that update.

While it is certainly nice to have support for U+32FF, it is not an absolute requirement for all Japanese fonts, because the primary way in which the Reiwa era name is expressed is as two separate kanji, 令 and 和, which are universally available in typical Japanese fonts. Good examples of Japanese fonts that do not support Japan era name ligatures include Ten Mincho (貂明朝) and Ten Mincho Text (貂明朝テキスト), which are very successful commercial fonts.

[epico]

Thanks very much for the information!