- From: Garret Rieger <grieger@google.com>
- Date: Fri, 30 Aug 2024 17:44:26 -0600
- To: "w3c-webfonts-wg (public-webfonts-wg@w3.org)" <public-webfonts-wg@w3.org>
- Message-ID: <CAM=OCWbRdphWaAdgxGx-5CMgKuN5=e-COSQ7MpqY5hnGG8_OZA@mail.gmail.com>
I've started to collect up topics for our upcoming fonts WG meeting at
TPAC. Here's a list of things that I have so far:
High Level Discussions
-
Specification overview and feedback. We'll likely have some additional
participants that aren't on our regular WG calls. This would be a good
opportunity to get them up to speed on all of the changes since last TPAC,
including the current IFT draft and gather feedback.
-
I'm planning to put together a short deck/presentation that gives an
overview of how IFT works in the current draft.
-
Detailed specification review. Let's take some time to review the
current state of the specification. Focus is to identify any remaining
areas that need improvement or changes and develop a plan for any remaining
work that is needed. For example:
-
Any high level reorg/structural changes needed?
-
Sections/information that’s missing?
-
Sections that are unclear or ambigous?
-
Inconsistencies and/or missing normative requirements?
-
Encoder discussions: this wouldn’t be specific to the specification but
rather a discussion on how to develop a high quality encoder implementation.
*Specific Topics*
Discuss any of the open issues as needed, some that might warrant
discussion:
- All other codepoint mechanism (https://github.com/w3c/IFT/issues/192)
- On by default feature list (https://github.com/w3c/IFT/issues/206)
- Dessicated initial font file (https://github.com/w3c/IFT/issues/201)
- Planning for client conformance tests.
- Discussions on font licensing and IFT (we've covered this in previous
calls so not sure if there's more discussion needed here or not).
I'm also looking for input from the group, so please let me know if you
have any additional topics that you think should be on the agenda.
Received on Friday, 30 August 2024 23:44:50 UTC