13:51:45 RRSAgent has joined #adapt 13:51:50 logging to https://www.w3.org/2026/07/21-adapt-irc 13:51:51 RRSAgent, make logs Public 13:51:52 please title this meeting ("meeting: ..."), janina 13:52:16 Meeting: WAI-Adapt Teleconference 13:52:36 Date 21 Jul 2026 13:52:44 Chair: Janina 13:59:02 matatk has joined #adapt 13:59:06 present+ 14:01:10 Russell has joined #adapt 14:01:36 present+ 14:03:13 Abhinav has joined #adapt 14:03:18 present+ 14:10:30 agenda? 14:10:38 topic: Administrivia 14:10:42 present+ 14:12:54 *Nobody away for the next few weeks.* 14:13:47 topic: Symbols 14:18:32 *Russell shows demo with text decorated with Mulberry symbols, with and a Mulberry font keyed on Bliss code points. Including zero-width joiners as well as single code points.* 14:21:35 Russell: Authoring experience is a little complicated; need to use OS method for input. 14:21:43 Russell: Have created a font with ~500 symbols. 14:22:29 Russell: *shows page with the rendered font representation, and gloss side-by-side* 14:22:47 s/and gloss side/and English gloss side/ 14:24:29 Russell: *Shows HTML source view* 14:25:46 Russell: *Changes the font used via CSS (a one-line change) and shows the glossary page now rendered with Bliss symbols instead.* 14:27:16 Russell: I wasn't concerned about implications of having lots of characters (Chinese has thousands of characters) but was concerned about whether having potentially thousands of zero-width joiners, as they're stored in a table within the font. Initial research indicates this won't be a problem. 14:27:44 Russell: This is ready to go. It was all about finding that tool - the nano emoji tool - I knew it ought to exist, but wasn't sure if I'd find an open source one - it's a great thing! 14:30:41 matatk: This is awesome; well done. See the styling issues re we can sort this with an extension. I have ideas for how the extension can simulate the UA providing this feature, so we can demo it. 14:31:29 matatk: Concerns around the authoring experience not _quite_ being able to edit via plain text (technically is, but slightly awkward). However, this solution (from the perspective of simplifying my existing code, to the experience of rendering these things) seems to fit at the right level in the ecosystem we have. 14:31:47 Russell: It's actually very neat because, by going via Bliss, we can support all the other symbol sets. 14:32:51 Russell: I'm not able to size the s independently here, just due to the example. There is a bit of an inconsistency between the Bliss and the Mulberry font size. The Mulberry symbols are quite consistent with each other. The Bliss ones seem a bit small. 14:33:00 Russell: I had to play round with the positioning. 14:33:01 q+ 14:33:16 Russell: It doesn't seem to naturally pick the right spots. We need someone with some CSS expertise to work on that. 14:35:47 matatk: We need to be careful with guidance about how to make the fonts - is there something that we should suggest to people generating the fonts, how things can be tuned so that they come out with similar proportions, and the UA (which will have only one style sheet) will render different symbol sets well? 14:35:56 Abhinav has joined #adapt 14:36:33 Russell: I noticed Hannes has put an option into his system relating to this. In Bliss, where the symbols are located within the 'viewbox' (in SVG terms) indicates something in relation to the meaning. Need to look into it. The Bliss symbols are consistent between themselves, but we have to define a standard about how the SVGs are prepared so 14:36:33 they're all consistent. 14:38:13 matatk: Could we make some sort of 'template' font that indicates allowed aspect ratios or sizes of things? 14:39:16 Russell: SVG is a language and you can generate the same image in several ways (strokes vs a pointillist approach, for example). Nano emoji doesn't like certain approaches. Sizing needs to be absolutes rather than percentages, for example. Understanding that well and providing the spec on what's required is important. 14:40:32 topic: DDs 14:40:37 rrsagent, make minutes 14:40:39 I have made the request to generate https://www.w3.org/2026/07/21-adapt-minutes.html matatk 14:41:33 Abhinav's PR - now merged! https://github.com/w3c/adapt/pull/337 14:43:21 matatk: Great work! We can do further edits to DRY between Explainer and (intended) Note. 14:43:24 Abhinav: Happy to take care of linking between docs, where content is removed from one. 14:44:47 matatk: (noted in the PR, but...) The TAG intends to talk about the gap between well-known URIs and more organic service discovery at its upcoming face-to-face meeting - here are some pointers to what we'll be discussing: https://github.com/w3ctag/design-reviews/issues/1243 14:53:18 topic: TPAC 2026 14:53:25 Registration info: https://www.w3.org/news-events/tpac/2026/registration/ 14:53:39 Travel funding application: https://www.surveymonkey.com/r/W3C-Apply 14:53:42 Deadline is the 31st! 14:59:41 zakim, end meeting 14:59:41 As of this point the attendees have been matatk, Russell, Abhinav, janina 14:59:43 RRSAgent, please draft minutes 14:59:44 I have made the request to generate https://www.w3.org/2026/07/21-adapt-minutes.html Zakim 14:59:50 I am happy to have been of service, matatk; please remember to excuse RRSAgent. Goodbye 14:59:51 Zakim has left #adapt 15:01:08 zakim, end meeting 15:01:22 janina has left #adapt