[Sorry for not posting to the more appropriate thread, but I had to resubscribe to the Unicode mailing list.] > Now, I'd always wondered when “when the sequences listed here are stable” > would be—but I was not expecting that it would be as soon as this year that > BabelStone's untimely passing, not long before the CAAPH collection was > registered, would sadly settle that question.
I had just added support for the new CAAPH collection (IVD 2025) in the CJK Variations utility of my Unicopedia Sinica <https://codeberg.org/tonton-pixel/unicopedia-sinica> application, when I got that terribly sad and so shocking news of Andrew's passing away... The latest beta release of the BabelStone Han font <https://github.com/babelstone/babelstonehan-ufo> is very recent (2025-07-08) and the associated BSH_IVS_BETA.html <https://www.babelstone.co.uk/Fonts/BSH_IVS_BETA.html> page and BSH_IVS_BETA.TXT <https://www.babelstone.co.uk/Fonts/BSH_IVS_BETA.TXT> data file appear to be in sync with it, except for a few issues that I was able to spot and correct. FWIW, I created an "Issue" documenting those issues in my app's repository: BabelStone Han Variation Sequences (v17.0.0 BETA) - Corrigendum <https://codeberg.org/tonton-pixel/unicopedia-sinica/issues/5>, and I also updated support in my app for the *unregistered* BabelStone IVD collection accordingly, for Unicode 16.0 though. I may be wrong, but I've got the feeling that Andrew was specifically waiting for the CAAPH collection to get registered and was almost ready to officially release the current font for Unicode 17.0 in September, and possibly apply for registration of his own BabelStone collection. [Andrew C. West (魏安), 1960-2025 RIP (安息吧).] --Michel Mariani
