On 2/11/10 12:33, Tavmjong Bah wrote:
On Mon, 2010-11-01 at 03:45 +0100, ~suv wrote:
> This has turned into a FAQ - related questions come up weekly if
> daily somewhere in a user forum, in #inkscape or in the 'Answers'
> sections of launchpad: how to save a bitmap in Inkscape with a
> transparent background, or why filter effects or patterns are not
> visible or incorrect in exported PNG files. Yesterday it was filed as
> bug too:
> Bug #669267 “Saving file in PNG format creates incorrect file.”:
> Any chance this can be addresses for 0.48.1? "Cairo PNG" should not be
> listed as file format in the 'Save/Save as/Save a copy' dialog in
> release versions.
I agree this change should be made. It should be as simple as commenting
Internal::CairoRendererOutput::init(); (line 157 in init.cpp).
If nobody objects, I will do this.
I just did a quick test, because I was curious about a possible
side-effect for bug #404826:
from a comment in bug #669267:
The internal output extension 'org.inkscape.output.png.cairo' seems to
get used (instead of 'sp_export_png_file()'?) when pasting the clipboard
contents from Inkscape into e.g. a raster image editor like GIMP: the
pasted images always have a white solid background and show the same
rendering errors (e.g. with patterns) or missing filter effects as when
saving an SVG drawing as "Cairo PNG".
Bug #404826 “copy an object from inkscape to system clipboard doesn't
... and indeed, at least with Inkscape 0.48+devel r9870 on OS X 10.5.8,
using X11/Xquartz 2.4.0 and GIMP 2.6.11, after above edit (disabling
CairoRendererOutput) copy&paste from Inkscape to GIMP as raster image is
pasted without solid white background, and with correctly rendered
patterns and filter effects.
Definitely cool :)
Can others confirm that disabling "Cairo PNG" does fix bug #404826?