NEW: UniConvertor in Windows bundle
I tried to use CDR import on Windows with UniConvertor and found out that:
- you can only install UniConvertor into a separate installed Python, not into Inkscape's own Python,
- even if you do that, it won't work because Inkscape insists on using its own Python, even to the point of prepending it to the system PATH, so it is simply impossible to run the separate Python unless you know exactly where it is.
For these reasons, I decided that the best strategy would be to include a copy of UniConvertor to our Inkscape Python in devlibs, which I did. I think supporting CorelDraw formats out of the box is an important enough feature to justify a few extra megabytes to the distribution.
P.S. Inkscape on Windows compiles and runs fine, except for the missing icons.
bulia byak wrote:
I decided that the best strategy would be to include a copy of UniConvertor to our Inkscape Python in devlibs, which I did. I think supporting CorelDraw formats out of the box is an important enough feature to justify a few extra megabytes to the distribution.
Ages ago I put up a uniconvertor bundle on launchpad that could be dropped into the inkscape python folder, but at the time some people (don't remember who, and it doesn't matter) were worried about Inkscape's file size.
I agree a couple of Mb is a good tradeoff for the functionality, especially since knowing that the extra functionality can be added with a module isn't at all obvious, unless the documentation were made very clear on this.
Thanks!
https://bugs.launchpad.net/inkscape/+bug/197617
Already marked as fix committed, so no need to update.
Just noticed that uniconvertor also does CGM and SK/SK1 (Skencil) formats, but they don't show up in the open or import dialogues. Would this be useful? I think we might as well make use of all uniconvertor's formats unless some other importer (Ghostscript etc) does it better. I think this would be similar to the changes in the following;
https://bugs.launchpad.net/inkscape/+bug/197617
https://bugs.launchpad.net/inkscape/+bug/227449
I'm also noticing that the open or import dialogues are not coming to the front, as was happening in LP # 227449 - I have to select open (or import), then click on the main Inkscape window, and when I've clicked on the main window the dialogue jumps to the top. See https://bugs.launchpad.net/inkscape/+bug/227449/comments/20
rygle wrote:
Just noticed that uniconvertor also does CGM and SK/SK1 (Skencil) formats, but they don't show up in the open or import dialogues.
.cgm and .sk1 are both supported in the File | Open and File | Import dialogues, Win32 build 20711
Strange, both my builds of 20711 and 20804 don't offer that option, even after making sure both have the latest uniconvertor files installed in the python directory. The uniconvertor stuff is obviously working, as I am offered cdr files as an option.
Here's a shot from my 20711 build; http://www.nabble.com/file/p22282156/20711.jpg
Here's a shot from my 20804 build; http://www.nabble.com/file/p22282156/20804.jpg
For both instances I have navigated to the site-packages folder of the python folder of that build to show that I have indeed got uniconvertor installed. 20804 it up directly from the dev-libs and 20711 I copied across the whole python directory from the 20804 build.
Seems there's some other inconsistency happening here.
Alvin Penner wrote:
.cgm and .sk1 are both supported in the File | Open and File | Import dialogues, Win32 build 20711
Scratch what I said about the dialogues not coming to the front - seems to be working fine after quitting Inkscape and going back in.
rygle wrote:
I'm also noticing that the open or import dialogues are not coming to the front, as was happening in LP # 227449 - I have to select open (or import), then click on the main Inkscape window, and when I've clicked on the main window the dialogue jumps to the top. See https://bugs.launchpad.net/inkscape/+bug/227449/comments/20
in the file cdr_input.inx, a dependency was recently removed, as in rev 20292 <!-- the uniconv or uniconvertor dependency will be tested by uniconv-ext.py --> this change, if necessary, should be applied to all the files that use uniconv, which normally have <dependency type="executable" location="path">uniconv</dependency>
in any event, on a Windows system, the name uniconv is probably not a meaningful dependency to use, it would probably be better to use uniconv.cmd, the full file name, or nothing at all.
On Mon, Mar 2, 2009 at 1:00 PM, Alvin Penner <penner@...1856...> wrote:
in any event, on a Windows system, the name uniconv is probably not a meaningful dependency to use, it would probably be better to use uniconv.cmd, the full file name, or nothing at all.
You're right, on Windows we now don't use uniconv script at all, so I removed it from other inx files as well.
Thanks Alvin. Now have about 5 more file formats in build 20806. Great work!
good to hear, I sort of misspoke myself. I was suggesting that the .inx files need to be fixed, in fact all that is needed is the file uniconv.cmd in the path. (and the affected formats are : ccx, cdt, cgm, cmx, sk1, wmf)
participants (3)
-
Alvin Penner -
bulia byak -
rygle