Simon Cozens

> also the start_step/end_step methods, aren't those already covered by the context-manager behaviour of Timers (i.e. with timer(...): ...) ? No, because the context-manager behaviour is currently designed to track...

> so this is basically to prettify the log messages with indentation, in a way that works across library boundaries Right. > > the context-manager behaviour is currently designed to...

> You'd have to change fontmake and all the dependant libraries that use timers to instead use this new GlobalTimer singleton (instead of instantiating their own) I think you're overestimating...

Good point. I've started working on some code which translates between a TTFont (i.e. the on-disk representation), fontTool's feaLib AST (and from there to feature file format), and this proposed...

I haven't added much to this recently, but I have been working on it, and the fontFeatures library is now able to ingest different OpenType Layout formats into a simple...

Yep, I'm there, which is why this issue is suddenly live again. :-)

I thought XML was part of the deal with UFO...

Returning to the topic, after some experience with fontFeatures I think I know what a platform-independent OTL representation should look like; and serialising/deserialising is not really a relevant concern as...

> I would say that there is a conflict there: what type designers need in their workflow (a place to write features in a syntax most know well and are...

The more I think about mini-specifications the less enthusiastic I am. It’s a deliberate fragmenting of the file format. With mini-specifications providing several options of representation, a font editor needing...