UniConvertor is a derivative from sK1 vector graphics editor. The idea to
create converter was inspired by Libre Graphics Meeting 2007. We have
reported on this conference about successful CDR format (CorelDRAW) reverse
engineering and many people have been interested in our results sharing.
sK1 is a classic vector graphics editor based on Model-View-Controller
pattern. UniConvertor contains only sK1 model component and import/export
filters. Therefore sK1 document model is a "central data structure". Unlike
VectorSection our converter is monolanguage tool and all import/export
filters are written on Python.
Concerning common issues: the most interested part is a DWG adn DXF reverse
engineering. Although there are public specifications for the formats, real
AutoCAD files doesn't correspond on 100% to published specifications.
Similar issues we have found for CorelDRAW CMX specification. Public
document doesn't describe all required chunks and only manual reverse
engineering resolved such problems.
On Tue, Oct 21, 2008 at 9:14 AM, Eric Wilhelm <ewilh...@vectorsection.org>wrote:
> # from Igor Novikov
> # on Monday 20 October 2008:
> >I hope we can collaborate with you especially in DXF/DWG format.
> >Although our UniConvertor (http://sk1project.org) is oriented
> >on prepress related formats I think can be common issues for the
> Hi Igor,
> That's very interesting. This is essentially where things were going
> with the Chromista hub (thus far only .svg, .xar, and a bit with .pdf),
> which is quite different from .dxf/.dwg/.dgn (the Rhizopod hub) in that
> the prepress formats don't include 3D and tend to focus more on fill
> properties (e.g. .svg has a much wider variety of gradient and such
> data than .dxf entities.)
> Aside: the names "rhizopod" and "chromista" are going to be replaced
> with "vectorsection drawing" (.vxd) and "vectorsection printing" (.vxp)
> rather soon. They originated several years ago and I don't feel like
> researching more micro-organisms just to name another hub ;-)
> A bridge between .vxp and .vxd is going to be key to integrating between
> the printing and drawing worlds. The basic idea is to gather all of
> the down-conversion and associated options into the bridge (i.e.
> vxd2vxp and vxp2vxd.) The vxd structure is likely to flux a bit as I
> get deeper into the dxf entities, but the tricky parts are probably in
> the text properties and curve conversion -- at least until you get to
> 3D, when the options have to be about projections vs slices, etc.
> Does UniConvertor have anything like a central data structure which is
> shared between the supported formats? If so, an example dump of that,
> it would be interesting to see.