Just put it through:
It depends on material in the next skia-python, 117b3:
I think the current plan is for about a dozen beta releases until about skia-python m130 b16 , in the next year and half. (Skia has new release every 4 to 6 weeks...) If things go well, there might be a non-beta release by then.
This is probably the easiest way of coping with some *cough* google *cough* OT-SVG fonts, given rsvg and Adobe Native can't cope. Skia-python comes with a bundled skia, so you don't have to build it yourself.
The plan is to release skia-python m117 b3, whatever state it is, when upstream m118 appears (in about two weeks' time...), etc, until about m130 b16, at least.
Hi, it has been a while with any traffic on the create list.
I have had some fun recently with downloading and building skia with ~80MB nework traffic and ~300MB disk space usage, without compromising on functionality:
Thought it is probably useful for other projects like libreoffice, etc. Potentially that means Skia is package'able as a shared library for wider use.
Quite surprised that Google Fonts make SVG's in their OT-SVG fonts that some of the most common SVG editors/viewers cannot read correctly:
What other SVG editors/viewers are out there? (besides Skia and Webkit, that is - those two work okay). I haven't given batik a go yet.
The context is that I have a few different options of enabling OT-SVG support on any freetype-based application, with an operational but still ugly (code-wise) addition for COLRv1.