Meeting minutes
Introduction, logistics, updates as needed
Lionel_Wolberger: Our next call on the 17th will be the last of 2024
Lionel_Wolberger: We resume 7 January
janina: Notes F2F is still on for May 5-6
matatk: I have room booked; will followup with geo data, e.g. hotels
matatk: Don't expect a problem
matatk: Hotels will be cheaper near Samsung, it's near LHR, and accessible to London
Lionel_Wolberger: We intend to use the WBS form, just as we do at TPAC, to check if any potential attendees need particular accommodations
Email from COGA
<gb> Issue 329 Broken links to w3c/personalization-semantics (by shawnthompson)
matatk: Explainers do not go TR
matatk: Correct approach is to file a github issue
Lionel_Wolberger: We do want good links from their docs
matatk: Problem is there isn't a single doc any longer.
matatk: In some cases we don't yet know what they should link to
janina: They're also behind on Content Usable v 2
matatk: Maybe best to wait; for now point to overall Adapt Explainer
matatk: Will check TR for any errata we need to introduce
Well Known Destinations
Symbols (Issue 240)
Russell: Have been designing fonts ...
Russell: A few symbols from 3 different AAC
Russell: Have been working on a written explanation
Russell: Believe proposers of unicode are seeing AAC as ligatures
Russell: ligatures different from combining chars
Russell: each symbol having one or more ligatures
Russell: unicode has multiple mechanisms for creating ligatures
Russell: e.g. Old English "ash" symbole
Russell: process: attach to a base symbol and add another symbol
Russell: 0-width joiners
Russell: -- outlines the process for display --
Russell: Would indeed work
Russell: There are long term issues
Russell: Notes unicode also has a shaping engine for langs with complex character graphics
Russell: e.g. Arabic
<Zakim> matatk, you wanted to ask about pigeon holes
matatk: expresses appreciation for all Russell's work on this!
matatk: Seems no code written and no standards updated to render in this way? Yes?
matatk: understand the ligature maps from individual char rendering many to one
Lionel_Wolberger: Ensuring these concepts get into the minutes, review:
Russell: It's robust and well tested because of emojis
Russell: also looked at multiple ruby
Russell: Zero Width Joiner (ZWJ) sequences can specify different glyphs, or emojis, and the rendering engine will combine them if a combination is known
… Example 1: Family (Woman, Woman, Girl, Boy)
Russell: Believe it's OK for ruby
… with ZWJ will render as a single emoji, 👩👩👧👦
… (separate symbols): 👩, 👩, 👧, 👦
… Rendering: 👩👩👧👦
… ligature is another way to join glyphs
… the shaping engine is the technology that joins them