On Sun, 10 Jun 2012 14:40:26 -0700 (PDT)
Darrell Anderson <humanreadable@...> wrote:
> > If the go.svg icon still shows the artifact, then I
> > can try joining the strokes to see if that helps. There must be something
> > strange in the way tde is rendering the svg images (perhaps old svg code - dunno). I
> > used inkscape and saves as a "plain svg" filetype -- so it doesn't get any
> > more basic than that. The tde svg-render engine is probably 8-10 years old now, I
> > don't know if the svg standard has been updated in the interim, but it is a
> > distinct possibility.
>
> David,
>
> The problem is not TDE, per se. I copied the image to 3.5.10 and the same thing happened. The image looks fine in gwenview and karbon14 but displays the white block in the menu icon or session exit dialog. If there is a weird corner case with displaying svgz images, then TDE seems to have inherited the problem from KDE3.
>
> Would you send me another copy with everything ungrouped? I then can tinker with bringing objects forward in the layers and see what might help. I'm a proverbial fish out of water with this stuff but I will tinker in karbon14 somewhat with whatever you send. I'm no artist and I can't figure out anything in karbon14. We inherited an app with no help handbook. Slackware does not come with inkscape and for me to build the package means building about a dozen dependencies --- lots of time. Even if I built, I have no idea how to work with these kinds of apps --- so more time trying to learn some basics.
>
> Possibly the problem is the way the file is compressed with gzip. I created the svgz file like this:
>
> gzip go.svg --suffix z
>
> Does inkscape have the ability to save as svgz rather than svg? If so, we can try that too.
Inkscape does have the option of saving as .svgz . The attached .svgz is ungrouped
and has the strokes forming the T converted to filled shapes, although I don't know
whether or not that will help.
I'll also see if I can get karbon to install (I'm still running KDE3, so there may
be libpng or other failures), and play with it a bit if I can. If there's no
manual, someone should try to create at least the rudiments of one, no?
Attachments: