Well, we could downgrade its version to XX.0.0-alpha.
That would permit us to continue shipping it while acknowledging that
it's problematic.
Let's keep that in mind. We need to let users know that karbon is not
production-ready, even for graphics bozos like me. :-)
If we find some improvements in newer versions of karbon that we can backport, then
perhaps we avoid the version downgrade. Likewise if we find documentation that helps learn
some methods to the madness.
Bug 1064: "Karbon functionality and UI
improvements needed"
filed, listing the deficiencies that I'm aware of at this time. I'll look
at building an interface mockup when I have more time (might be QT4, but it'll be
enough to get the idea across).
I'm pretty sure the outside border of that particular image
is a single line with a dash style applied, not a series of shorter lines.
Extracting a single dash-bit in Inkscape would require two non-obvious actions (Object
>
Stroke to Path, Object > Break Apart), neither of which Karbon appears to
support. (I don't consider that a deficiency in Karbon per se, as those are
more advanced functions which aren't strictly necessary for a basic editor.)
Bug report 1064 looks like a good start. I added some notes to the report.
Darrell