I'm also following this discussion, and it seems that you already mentioned the big things: color management support and more pixel formats, including high precision formats e.g. 16-bit or 32-bit float per channel. Everything else isn't that important.
One deficiency I can see in the Cairo API is that there's no way to store a path for later use, meaning that a truly efficient implementation of an OpenGL backend is not possible - you have to convert the path to polygons every time you want to display it. I'm not sure whether this can be solved at all within Cairo's current drawing model.
Regards, Krzysztof
2014/1/21 Tavmjong Bah <tavmjong@...8...>:
Hi,
There is a proposal before the ISO C++ standards group for a technical specification for 2D graphics based on the Cairo API.[1] It seems to have gained some traction. My question here is what is missing in the Cairo API that would be useful for rendering SVG?
Tav