On Sun, 10 Jun 2012 18:43:47 -0700 (PDT) Darrell Anderson <humanreadable@...> wrote: > > 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. > > Yay! No white block. Nice and clean. > > Although what you described about strokes went over my head. :-) Any shape in a piece of vector artwork can consist of a fill--a solid inside--and a stroke--an outline. What I did was convert the T from a pair of lines with a really thick outline to a pair of solid rounded rectangles with no outline. > I'll push to GIT. > > > 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. > > I have koffice running on my 3.5.10 setup as well as Trinity. Strangely, karbon (both 3.5.10 >and TDE) does not render the T in the new svgz. Only the gear. Gwenview and squirrel open >the svgz fine. Hmmm. Sounds like karbon may not fully implement the svg standard (Inkscape does, except for a quirk with the handling of multiline text--it's why they forked from Sodipodi in the first place). Either that, or it has some kind of weird problem with overlapping shapes. > > If there's no manual, someone should try to create at least the rudiments > > of one, no? > > Sounds like something for our to do list after R14. :-) I wonder whether the Calligra version has any >kind of manual that we can use as a basis. Would be nice if karbon could do some very basic work for >us --- to somewhat eat our own dog food. Fishing through the Calligra/KDE git indicates that they have no more docs than we do. I get the impression that, since the KOffice-Calligra fork, they haven't added significantly to their documentation, just maintained what they already have. Maybe we can sweeten the relationship between Trinity and the KDE family of projects here by contributing something back. Anyway, Karbon did install for me, so I'll try to find some time to poke at it and see what it can (and can't) do. If I can squeeze out a couple of lines of description each tool or setting and a few illustrative screen shots, that'll be more than we have, and if I can't, we'll be no worse off.