Meeting minutes
review of CTS updates
https://
Garret: updates on the conformance test suite. DuringTPAC we discussed the approach to testing the client side. That discussion was recorded in the above google doc. Since then I've transcribed that discussion to markdown on the client test repository (link above). That document explains the approach we plan to take in developing the client tests.
Garret: Scott has been working on client test implementations. Main focus has been developing the framework that the tests will use, plus a few initial client tests to demonstrate the approach.
Vlad: Scott what is the availability for working on the client tests?
Scott: looking like 10-20 hours a week starting next week.
Vlad: looking for help with the client test suites. Client test suites are needed to advance the spec.
Jason: can't help with test suites, but can help trying out the tech.
Garret: what could be useful is to help me develop a better demo to showcase the tech.
Dileep: I can potentially help out on the tests, will get back on the commitment.
<jpamental> (again)
<jpamental> Here's the book example I was talking about to use as the foundation of a test implementation: https://
Vlad: tests are to test specific aspects of the tech in relation to spec conformance statements. For example you could have a simple font with a pass and fail glyph that displays a pass when the implementation does the right thing.
<streude> w3c/
IFT encoder updates.
Garret: I've been working on the encoder since TPAC to develop a complex condition detector which can find conditions for glyphs that the regular analysis fails on. It doesn't find the true conditions, but approximations of them that are super sets.
Garret: overall it's working really good so far, main focus now is to improve performance. Hoping to have something ready in a week or two.
Garret: additional I did an analysis over the Google Fonts open source collection to see how prevalent complex conditions are that can be found here: https://
next steps for CTS development.
Scott: starting next week will be identifying tests to start working on.
Vlad: as you go through different steps would be useful if you periodically send email updates with the current status.
Scott: roughly thinking of cutting a branch for ~4 tests, and then can update the mailing list.