no systematic render bug

[aurore]

For some curves imported from an .ai file, the rendering is very chaotic especially when you export it to .png .
Here is an exemple: some of the eyes are partially cutted but it depends of the zoom level for the screen rendering and of the pixel number for the .png rendering.

i'm not sure if it's the same bug but there is also a non systematic render bug: on a file created with Inkscape (not imported from another software), I have used many live path effects, mainly the skeletal one which applies a shape on a path and i have render bugs: when i export in .png, i have some full line area where everything is rendered except the path effect. I can walk around this bug by changing again and again the pixel number in the export to find one were the bug isn't present or with buggy area healable with copy/paste from another area in raster image editor like GIMP.

These bugs oppers on a stable version of Inkscape ( Inkscape 0.48.2 r9819) on Mac OS X 10.9.4 and Windows 7 (not tested with the Linux edition

[su_v (suv-lp)]

These are known glitches with the old renderer in current stable Inkscape - reported and tracked in various earlier reports, e.g.

- Bug #189214 “curve is exported badly (but displayed correctly)”
  <https://bugs.launchpad.net/inkscape/+bug/189214>

- Bug #428415 “Portions of path not drawn on screen or exported”
  <https://bugs.launchpad.net/inkscape/+bug/428415>

- Bug #588941 “Path is not rendered at different zoom levels”
  <https://bugs.launchpad.net/inkscape/+bug/588941>

and plenty of others. These glitches will be fixed by the new renderer for upcoming major release 0.91.

Proposing to link as duplicate to bug #189214.