13:53:43 RRSAgent has joined #adapt 13:53:48 logging to https://www.w3.org/2026/06/16-adapt-irc 13:53:48 RRSAgent, make logs Public 13:53:49 please title this meeting ("meeting: ..."), janina 13:54:02 Meeting: WAI-Adapt Teleconference 13:54:10 Date: 16 Jun 2026 13:54:14 Chair: Janina 13:56:23 Russell has joined #adapt 13:56:59 present+ 13:57:02 scribe+ 14:13:40 matatk has joined #adapt 14:14:18 agenda? 14:14:39 rrsagent, make minutes 14:14:41 I have made the request to generate https://www.w3.org/2026/06/16-adapt-minutes.html matatk 14:14:48 topic: Symbols 14:14:48 scribe+ 14:14:48 present+ 14:14:52 Russell has joined #adapt 14:14:57 present+ 14:15:06 [discussion of timeline and reqs for TPAC] 14:15:29 matatk: If we have a couple of fonts ready for TPAC (Bliss and maybe ARASAAC) then I can take out 95% of the code for the extension and authoring tool I wrote, and we can make it a 'real' demo. (Except for using the PUA.) 14:15:36 Russell: Hannes and I had the same thought last week! 14:16:39 Russell: Knowing that we want to use SVG glyphs, I looked at Global Symbols, Mulberry popped out to me (SVG, CC licenced). 14:16:51 Russell: The mapping needs to be done. 14:17:27 Russell: I had a quick look; they have 3,200 to 3,400 symbols. Some duplicates. I did some matching and curating, and came up with 498 symbols. 14:18:19 Russell: Hannes is as we speak working on those two fonts. I think he understands the need for the ligatures. We'll work together on it. 14:18:31 Russell: I'm sure we can get this done by October. 14:19:32 Russell: Note though that this is a very large number of ligatures, my research indicated this ought to be feasible, but we'll see in practice. 14:19:37 matatk: I can start stripping away code. 14:20:02 janina: We should be aware that surprises will happen. Any project without surprises would be unheard of. 14:20:09 janina: We need to declare our intent to meet at TPAC by tomorrow. 14:21:00 matatk: If it's not practical, then we can demonstrate _that_ 14:21:37 Russell: In theory it's doable, but maybe assumptions in systems' implementation mean that it isn't in practice - it's reasonable that it should work, though, and we ought to be able to do it by then. 14:21:48 janina: Eager that we not lose momentum. This sounds really good. 14:21:58 matatk: +1! Thanks Russell and Hannes 14:25:21 matatk: Asks whether we could have a placeholder font soon in order to practice mappings 14:25:34 s/soon/soonest/ 14:26:00 matatk: Is it relatively easy -- a glyph per word or such? 14:26:50 matatk: Suggests variety of representatioh for testing -- double line below, one red, one green, etc 14:27:37 Russell: there are triditional ligatures that have both separate codepoints and the individual glyph 14:28:23 Russell: how it's accessed in a sequence of codepoints -- code is always checking it's codepoints for a sequence of text 14:28:36 Russell: So, we can do that, but it won't work that way once developed 14:29:20 matatk: We need to work out the steps so the AAC devs can follow the guide to create the fonts 14:29:25 Russell: not by tpac 14:29:29 matatk: of course! 14:29:46 matatk: The kernel of how it goes would be good to have though 14:29:50 Russell: agree 14:30:24 Russell: still wondergin whether ligatures work in privade Unicode space 14:30:47 Russell: any font should work for testing font interchange 14:31:13 Russell: obviously for a demo you want AAC, but for dev work any font should do 14:31:24 matatk: Also want to demo authoring 14:32:11 matatk: Important we document anything that doesn't work as expected 14:32:47 matatk: Would like to understand better 14:33:03 matatk: Now we're mapping from a codepoint to a glyph 14:33:09 matatk: We need the list ... 14:33:18 Russell: I have it. Got it from Michael 14:33:57 s/Got it from Michael/Got it from Michael's public draft document./ 14:35:21 matatk: We may not want to pub Registry with private use references; but we'll need it for our work 14:35:48 matatk: Trying to see the data struct of the Registry 14:36:53 matatk: we need all these things to match up 14:37:20 matatk: all based on valid codepoints that make up the Registry 14:37:53 matatk: Wondering how to help? How to marry up with glosses? 14:38:23 Russell: I map BCI IDs, have it in spread sheet, not codepoints but easily matched 14:38:56 matatk: we can use internally though 14:39:17 s/we can use internally though/we can use internally though?/ 14:41:34 Russell: On an aside -- Doug Crawford, inventor of json, very into Bliss 14:45:33 Russell: he came up with his own version and was doing things with itmaSo, canonical needn't be json, but it's useful to us at this point to use json 14:48:16 matatk: our goal is interoperable font, but we're not quite there. However, we want to dev efficiently so that we don't unnecessarily repeat processes as we work this out 14:49:48 Russell: bliss string would be the key 14:50:12 Russell: gloss, id, codepoint string 14:51:14 Russell: I basically have this, as does Hannes; we can put it together as is useful 14:51:37 matatk: I propose to create a schema we can test against some json; perhaps for next week? 14:52:17 Russell: I'm currently mostly spread sheet, Libreoffice Calc 14:52:50 Russell: Google SS useful for scrolling to see the symbols 14:53:46 matatk: it's imp[ortant we can roundtrip among these various formats 14:54:34 matatk: want to be ready when the font is ready 14:56:37 Russell: So from me a small set using codepoints? 14:56:45 matatk: maybe not yet 14:56:58 matatk: a pointer to the source of truth for the bcp 14:57:10 Russell: on BCI web 14:57:25 Russell: will send link and one to the Google Sheets version 14:57:45 matatk: sounds great 14:58:21 matatk: json so it has everything we build everything else from 15:18:25 zakim, end meeting 15:18:25 As of this point the attendees have been janina, matatk, Russell 15:18:26 RRSAgent, please draft minutes 15:18:27 I have made the request to generate https://www.w3.org/2026/06/16-adapt-minutes.html Zakim 15:18:33 I am happy to have been of service, janina; please remember to excuse RRSAgent. Goodbye 15:18:34 Zakim has left #adapt