bulia byak lamentò:
So, it looks like due to this stupid byte-order issue, cairo for us is practically an all-or-nothing proposition - and much more hassle than I expected. I'm not saying it's impossible but it is quite a major project that cannot be done gradually.
Unless, of course, cairo gets so in love with Inkscape as to provide us with a new image surface with system-dependent byte order...
It should be possible to write a custom image surface which does this in the inkscape codebase without putting it in the cairo library, thus allowing the gradual shift to cairo.
In the worst case we can copy the image backend changing the byte order of the surfaces and use this until the transition is completed, then switching to the official image backend.