The Unicode community is greatly saddened and affected by the
recent and sudden loss of John H. Jenkins, a long-time colleague and friend.
John was most recently the Vice-Chair of the
Unicode CJK & Unihan
Group. The vast majority of characters in the Unicode Standard are Chinese,
Japanese, and Korean (aka Han) ideographs, which are historically used with a
broader range of languages. These have been challenging characters to deal with
in script encoding, because of significant regional drift over hundreds of
years. As an expert in Han ideographs, John contributed a non-trivial amount of
work and effort, sometimes needing to make difficult character encoding
decisions for the benefit of the large user community.
Many people have worked with John and appreciated his substantial
contributions. Here are some reflections from two people who worked with him
most closely.
From Lee Collins:
I met John when he joined our team at Apple in 1991. He came from
an internship in Apple's Advanced Technology Group (ATG), having graduated in
math and ancient Greek at UC Berkeley. In addition to his technical skills, he
could read, write and speak Cantonese. All in all, he was a perfect addition to
the team, since one of our main tasks was completion of the first version of the
Unicode standard, in particular the Unified Han character set. A key component
was the database we had built to track all the different Han character
encodings, beginning with Xerox, later adding Mac OS version of JIS, GB, Big5,
and KSC, then the unified simplified and traditional mappings provided by Mr
Zhang Zhoucai of China. The database was a Hypercard stack that ran on a version
of Mac OS I cobbled together to allow Chinese, Japanese and Korean text to be
edited and displayed simultaneously. John took over management of that system
and database and began to learn the arcane art of Chinese character encoding. He
also found time to write a Risk-like game based on the classical world. I don't
remember the name of that game, but it was a nice diversion from work.
I had been the primary Unicode representative at the first meetings
of international experts to refine what became the ISO 10646 Unified Repertoire
and Ordering / Unicode V1.0. The group, initially known as the CJK-JRG (Chinese
Japanese, Korean Joint Research Group) later became the current IRG. Hoping he
would take over my work, I invited John to join one of the early meetings in
Hong Kong, November 1991, and he later became the primary representative. John
continued to contribute to the IRG and the Unihan database for the rest of his
career.
We both joined the ill-fated Taligent effort, where we developed
the internationalization classes that later became the foundation for ICU. Those
designs were probably one of the few things of value that came out of Taligent.
I left Taligent and went back to Apple. John came back sometime later after IBM
took it over completely. I was manager of the team charged with developing
Apple's first Unicode-based text library, which we called ATSUI (Apple Type
Services for Unicode Imaging). It was largely based on the model of text layout
developed for Quickdraw GX. John was the engineer charged with developing the
library. That role was not a good fit for John's talents, so he moved to the
Typography group where he was responsible for the font tools Apple used to
develop our Truetype fonts. My team also developed support for complex scripts
like Hindi and Thai, so I often used John's tools to create fonts with the
required layout tables.
I moved on to other areas of Apple, ceased to work directly with
John, and eventually left Apple. But, since 2015 or so, I again became involved
in the IRG as the representative for Vietnam. That allowed me to work with John
once more in his various capacities on the Unicode Technical Committee,
especially his responsibility for the Unihan database and participation in the
IRG. I enjoyed being able to work with him again. Knowing the size and
complexity of the work he did for Unicode, he will not be easily replaced.
While we had our differences on technical and work issues at times,
he was always a kind and thoughtful person. The world is a lesser place without
him.
John was much more familiar with Cantonese than Mandarin due to his
missionary work in Hong Kong. I think John’s characters, 井作恆, satisfied two
criteria: they are close to his name phonetically (zeng2 zok3 hang4) and look
like an actual Chinese name. Purely phonetic transcriptions often use a limited
set of characters that look obviously foreign. These don't.
From Ken Lunde:
Nothing brought more joy to John than attending IRG (
Ideographic
Research Group) meetings, particularly when they took place in
Chinese-speaking regions, especially Hong Kong, which held a special place in
John’s heart. For those who are unaware, the IRG is responsible for reviewing
and preparing the thousands of characters in the growing number of CJK Unified
Ideographs blocks, which comprise approximately one-third of the total number of
characters in the Unicode Standard.
Fun fact: John and I had an unwritten and informal agreement that
he would attend these one-week IRG meetings when they took place in
Chinese-speaking regions, and I would attend those hosted elsewhere, in a quasi
yin and yang relationship. This would completely explain why I have never
attended an IRG meeting in a Chinese-speaking region. This relationship was also
evident in John’s focus on all things Chinese and my focus on all things
Japanese, though both of us performed sufficiently dangerous dabbling in the
other language.
John and I began working much more closely together as a result of
COVID-19, which necessitated the formation of the Unicode CJK & Unihan Group,
with me serving as the Chair, and John serving as the Vice-Chair. This group,
which was formed in early 2020, pre-digests proposals and public feedback,
interacts with the IRG, and provides its recommendations to the UTC.
Please visit John’s obituary to read more about his extraordinary life, or
to express condolences to John’s family:
https://www.larkinmortuary.com/obituary/view/john-howard-jenkins/
![[image]](https://www.unicode.org/announcements/cldr40-alpha-annc.png)
CLDR provides key building blocks for software to support the world's languages
(dates, times, numbers, sort-order, etc.). For example, all major browsers and
all modern mobile phones use CLDR for language support. (See
Who uses CLDR?)
![[badge]](https://www.unicode.org/announcements/ynh-pink-heart.png)
![[Photo of Ken Lunde and John Jenkins, October 2022]](https://www.unicode.org/announcements/Lunde-Jenkins-Oct-2022.jpg "Photo of Ken Lunde and John Jenkins, October 2022")
![[Silver badge]](https://www.unicode.org/announcements/silver-4E95-jenkins.png)
Posts
