Last modified: 2008-10-14 04:47:37 UTC
Some SVG containing arrows are not correctly rendered :
between the rotating belt)
The Van de Graaff generator has been drawn using Inkscape 0.43 (Linux).
Just wanted to add that the problem seems to be related to an Inkscape property :
inkscape:stockid="Arrow2Lend" <--------- this is probably ignored
Just a note to say that I have redo a version of
http://commons.wikimedia.org/wiki/Image:Aikido_ikkyo.svg with manula arrows
head. So, in order to look at the problem, either use
http://commons.wikimedia.org/wiki/Image:Van_de_graaf_generator.svg or an older
version of ''Aikido_ikkyo.svg''.
(In reply to comment #1)
I'm not sure it has anything to do with that property, it's more likely caused
by librsvg ignoring the "overflow:visible" style. Inkscape's default markers are
defined outside their bounding box and therefore rely on the overflow to be
visible in order to look correct. Librsvg, hovewer, ignores this overflow
I guess this is a duplicate of http://bugzilla.wikimedia.org/show_bug.cgi?id=5163.
*** Bug 5514 has been marked as a duplicate of this bug. ***
Don't know if this is the same bug:
http://en.wikipedia.org/wiki/Image:BJT_symbol_NPN.svg looks fine on the full-
size image page, but the thumbnail on http://en.wikipedia.org/w/index.php?
title=NPN&oldid=46322776 is missing the emitter arrow.
I think this is a duplicate of bug 5163...
Indeed, I can't get MediaWiki to render SVG line terminators at all...
This image should have arrows and dots, neither of which appear.
On this image (http://commons.wikimedia.org/wiki/Image:Compression_JPEG.svg) I
have as a problem with arrow they are really small, in Firefox
or in Inkscape the arrows will be really bigger !!!
Is it the same bug, is there a work around ?
This bug has been fixed upstream.
Upgrading to librsvg >= 2.18 would solve this.
*** Bug 12722 has been marked as a duplicate of this bug. ***
Looks OK now that we have librsvg 2.22.0. The arrows in the first test case point the wrong way, but the rest of the test cases seem to be correct so I'll assume that the first one is an author issue.