search

w3c / font-text-cg

GitHub Pages
https://w3c.github.io/font-text-cg/
Other
28 stars 5 forks source link

Meeting 6 schedule and agenda #35

Closed lianghai closed 3 years ago

lianghai commented 3 years ago

When and where

This meeting is open to all. Joining the meeting does not require you to first become a formal participant of the W3C FTCG.

See also agenda and minutes of Meeting 5.

IRC channel

To allow easier management, you are welcome but not required to join our IRC channel (see also #7) during the meeting.

Quickly join the channel right in your browser via Kiwi IRC: irc.w3.org/#font-text

IRC cheat sheet:

Draft agenda

Housekeeping

  1. Confirm scribes and record attendance.

    • We are using a Google Doc this time, to allow cooperation and offload the stress on a single skillful scribe: Meeting 6 scratchpad

  2. Attention to the code of conduct [#4]

  3. Self-introduction of new participants

  4. Review the last meeting’s minutes [link]

  5. Plan major agenda items for next meeting and tentatively schedule it

    • Question: “Is the day expected to stay the same in the future?” [Bobby de Vos @devosb, comment]

Proposals

  1. Actionable proposals [#36]

  2. Stalled proposals [#9] and other proposals in the issue tracker

FYIs and free discussions

  1. Experiments on the implementation of the OpenType JSTF table [@simoncozens]

  2. Informal liaison report from MPEG-OTSPEC [@vlevantovsky, list archives]

  3. COLRv1 changes [Laurence Penney @Lorp, comment]

  4. How about running a Discord place? [@lianghai, reference article]

  5. An interesting position at Microsoft: Senior Program Manager, Globalization and Typography Standards [link]

  6. DWrite Core, Duncan

xfq commented 3 years ago

We will use a Google Doc this time, to allow cooperation and offload the stress on a single skillful scribe: Meeting 6 scratchpad

Just FYI - it is possible to have more than one scribe using IRC: https://w3c.github.io/scribe2/scribedoc.html#multiple

(I don't object to Google Docs. As long as the participants are comfortable using it, it's fine.)

lianghai commented 3 years ago

@xfq, thanks. Yes, we are aware of that. The difficulty we’ve realized though, is that in an IRC channel you can’t see what the scribe (or other scribes) are typing in real time, and therefore it’s difficult for others to give a hand.

devosb commented 3 years ago

At first, these meetings were on Mondays (in North America). Recently they have been on Tuesdays. Is the day expected to stay the same in the future? If so, I might move another meeting so I don't have conflicts that I need to reschedule.

Lorp commented 3 years ago

Can we make sure the COLRv1 changes are on the agenda? These are significant, and the COLR transform implies how b/w glyph formats should develop too. Transforms in colour and b/w glyphs need to be in sync, long term. Also on transforms, note @BlackFoundryCom’s variable-components-spec. Synchronization is needed.

PeterCon commented 3 years ago

Just an FYI: If you're interested in HOI but haven't seen any good explanation of how it works, I had a chance to investigate and figure out why it works in the current formats, and wrote that up: Understanding Non-Linear Interpolation in OpenType Variable Fonts

duncanmacmichael commented 3 years ago

Hi everyone,

Thanks for listening today and for your interest in DWriteCore! Here are the right links to get you started:

Have fun exploring the sample app and exploring our initial prerelease! :)

Lorp commented 3 years ago

Thanks for listening to me describe the experimental ttf-cubic format, a format based on TrueType-flavour OpenType but containing cubic curves rather than quadratic. They can be produced quite easily with current tools. This document discusses what ttf-cubic fonts are, why they exist, how to make them, and where you can try them out.