UniConverter is currently used for input: ccx, cdr, cdt, cgm, cmx, plt, sk1, wmf output: plt, sk1, wmf
Oh, I thought wmf was internal. That's why I used it on my example on my previous post.
I just checked the UniConverter website - they have a link to their bug tracker on launchpad which could make it easier to link Inkscape export bug reports to https://bugs.launchpad.net/uniconvertor/. However the launchpad UniConverter project doesn't seem to be used at all. There's still the 'sK1 Project - Support Forum: UniConvertor bugreports' at http://sk1project.org/forum/viewforum.php?forum_id=6 which has more recent activity. Should we mark uniconvertor bugs as 'Invalid' and refer to the sK1 website?
~suv
I would drop a letter to UniConvertor developers suggesting them to use the bug tracker at Launchpad more (best solution) or inviting them to take a look at the 'uniconvertor' tag in our Launchpad's section now and then. The forum they're using would force us to get an account and forums are not the best way to manage bugs anyway (no duplicates, status, patches, attachments...)
The first step is to tag bugs with 'uniconvertor' and see how many of them there are. At first I'm going to tag them without removing any previous tag.Then will write a letter to UniConvertor authors exposing them the situation. But that will be in some hours, I've yet to take my bike from the repairman (who hadn't good news...)
Regards.