On Fri, 15 Jun 2012 18:38:08 -0500
"David C. Rankin" <drankinatty@...> wrote:

> but it doesn't explain the go.svg issue as E pointed out.

And that issue has just become a little murkier again.

I just took the time to have a look at the original SVG, as posted
at http://www.3111skyline.com/dl/dt/tde/img/tdeaccessibility/go.svg ,
and there's no artefact.  I tried both 3.5.10 Konqueror and the
corresponding version of Karbon14, and I can tell that it's not 
my revised SVG because I thickened up the T somewhat as Darrell 
requested at one point.

Several possibilities suggest themselves:
1. Konqueror and Karbon use a different renderer than the dialogs.
2. The artefact is a regression introduced between 3.5.10 and
	current GIT, in which case We Have A Real Bug and
	need to find out which patch introduced it.
3. The artefact is due to something else on Darrell's system, possibly 
	a video driver bug, and is not Trinity's fault at all.
4. This isn't the original file after all.

So the immediate questions are, Darrell, is this the faulty file, and does 
the artefact show up for you in Konqueror/Karbon, or is it only visible 
in the shutdown dialog?

The diff between the two files isn't very enlightening either. Boilerplate 
in mine suggests that I saved as Inkscape SVG (since there were no 
text elements, that shouldn't make a difference), and I can see how 
David's file was grouped and tell which XML element corresponds to 
what shape, but there's nothing obviously *wrong*--the two documents
are basically similar and everything appears to be well-formed XML, 
although I haven't yet checked to see if it's valid. [1]

[1] "Well-formed", with respect to XML, means that the document 
follows the general syntax of XML as outlined in the XML standard.  
"Valid" means that the document is well-formed *and* the elements 
and attributes match what's in the DTD(s) or schema(s) that define 
the document type, in this case SVG.  $DEITY, I haven't thought
about this stuff in years.