This conversation raises some basic questions: * Will we ever be able to use karbon14 as a basic tool for supporting our own svg(z) images? We're talking basics and not exotic or professional needs. * Your reference to konqueror actually is a reference to the embedded svg viewer. As you mentioned svg specifications, do you feel comfortable looking at that code to provide a report of sorts whether the TDE embedded svg viewer is up to snuff with those specifications and what needs to be done to update the code? * In an effort to help us support our own svg(z) images, do you feel comfortable writing a basic how-to at our wiki outlining the basics of svg support? The app used is not as important as the fundamentals of what needs to be done to avoid problems and errors. For example, you mentioned different Save As options that would alleviate the problem reported by David, but my guess is you are the only person on this list who knew those distinctions. :-) I'm willing to help if writing is something you dislike. Darrell

I believe the user interface is shared among all koffice apps. I think karbon and chalk (nee krita) share some interface components too. I doubt we can remedy the interface issues any time soon, so we would focus on documentation, tool tips, etc. As karbon, and koffice in general, was long ago neglected and shoved aside, we do the best we can with what we inherited. As long as we remember our project goal of maintaining koffice as a light-weight office suite, I think we can tweak karbon. Great. You're already way ahead of me. :-) Editing and proofreading would happen naturally when the text is transformed to docbook, which is needed to create the help handbook. I'm pretty good at "dumbing down" technical information --- been doing that for many years. :-) Just write whatever you want. We'll handle the editing and refining later. I'll learn much about karbon by helping with editing and docbook transformation because I'll actually have to test what we write. :-) Thank you for helping. If we get something crafted for R14 then great, but let's not let the R14.0.0 release dictate this particular project. We can always push a new karbon handbook in R14.1.0 or R14.2.0. Darrell

On Fri, 15 Jun 2012 18:38:08 -0500 "David C. Rankin" <drankinatty(a)suddenlinkmail.com> wrote: 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.