On 20-Aug-2013 16:44, Krzysztof Kosiński wrote:
2013/8/20 mathog <mathog@...1176...>:
Branch lp988601 has working EMF (and WMF) import and export on Linux and I believe OS X, although I do not have a Mac to test that on. It uses libUEMF, which I wrote for this purpose.
What are the differences between this library and libEMF?
Many. I initially started with libEMF, found that there were a lot of things it could not do, and then decided to write my own from scratch. The most important difference is that the Inkscape input/output code for EMF and WMF are already written for libUEMF.
If you want this in trunk then lp988601 will need to be merged into trunk. Which it probably should be at this point. There is only one outstanding bug that I know of: in some EMF files written by Illustrator on OSX image objects render with the sign of y reversed, even though the rest of the diagram renders correctly.
Sounds like most of the work is already done :)
Is this code a suitable replacement for the native EMF extension we have on Windows?
Try importing the test EMF and WMF files from libUEMF into the Windows version of trunk, then do the same with lp988601. The latter works much better. There are also output options in lp988601 to work around EMF import glitches in PowerPoint, which is the most common target. If you have access to a Windows machine there is an lp988601 binary here:
http://saf.bio.caltech.edu/pub/software/windows/inkscape_r11738_lp988601.zip
Also, apparently the version of the GPL used by libUEMF is somehow incompatible with that required by Inkscape. Since libUEMF is my code I can change the GPL version to whatever is needed.
Inkscape seems to be GPLv2, but most files do not actually specify the version of the GPL. There is some GPLv3+-only code pulled from GIMP, which strictly speaking should be removed or rewritten, because v2 is incompatible with v3. We also have some dual licensed code (MPL + LGPL, MPL + GPL) and some "public domain" code, mainly from Sodipodi.
libUEMF's GPL is "Version 2, June 1991". That seems to be the same on in the top layer of my Inkscape Windows build. I will have to dig back through my email to find the message somebody sent me about this issue.
Regards,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech