Personally I'm preferring 1 option because we have planned next UniConvertor release on September.
Also it would be great to resolve "black console" issue under Windows. During import/export operation
users observe cmd console. Such behavior is considered as a bad programming style under Windows.
Can you switching for pythonw command usage vs conventional python?

Also from our side we can providing progress bar dialog to notify user about operation progress.
It would be great improvement because some files require a lot of time for translation.
This is possible as for win platform and for Linux - uniconvw script is based on pyGtk, so Inkscape
UI integrity will be good. If this option is interested we can preparing minor release with required
fixes.

Regards,

Igor Novikov
sK1 Project
http://sk1project.org

2010/7/8 Nicolas Dufour <nicoduf@...48...>
Hi,



> De : Krzysztof Kosiński <tweenk.pl@gmail.com>
> So, how do we proceed? Should I remove the UniConvertor Python library
> from devlibs and include an UniConvertor installer?

IMHO including the whole UniConvertor installer is not a good idea (at least for 0.48).

I see two (tested) options:
1. Removing the Uniconvertor scripts from the devlibs. UniConvertor import or export scripts warn users to install UniConvertor manually (and give the site address) when the libs are missing. (Note to self: fix the gettext import bug in uniconv_output.py...).
2. Replacing the old files in C:\devlibs\python\Lib\site-packages (uniconvertor/ and UniConvertor-1.1.3-py2.5.egg-info) with the new ones (uniconvertor/ and UniConvertor-1.1.4-py2.6.egg-info) in C:\devlibs\python\Lib\site-packages.

Option 2 doesn't seem to work with UniConvertor-1.1.5, thus option 1 may be a better long term solution.

Regards,
--
Nicolas