Hi all,

As an UniConvertor author I would recommend to install UniConvertor 1.1.5 which is installed as a stand-alone application under Windows platform and has no dll clash issues:

http://sk1project.org/modules.php?name=Products&product=uniconvertor&...

to integrate UniConvertor wit Inkscape just run Inkscape patch vbs script from windows Start menu. Details: http://www.libregraphicsworld.org/articles.php?article_id=20

Regards,

Igor Novikov, sK1 Project http://sk1project.org

On Mon, Jul 5, 2010 at 4:33 PM, Nicolas Dufour <nicoduf@...48...> wrote:

Hi,

...

De : "Lewis, Simon" <Simon.Lewis@...2371...> Applies toInscape 0.48pre1(OS:Windows XP) Following error shown in dialogue boxwhen saving as wmf: UniConvertor failed:

Confirmed on Windows XP, Inkscape revision 9535. This is due to the fact that Inkscape now uses Python 2.6 with a Python 2.5 version of Uniconvertor 1.1.3.

Replacing the Uniconvertor 1.1.3 devlibs with Uniconvertor 1.1.4 (downloaded from http://sk1project.org/downloads/uniconvertor/v1.1.4/uniconvertor-1.1.4.win32...) seems to work well.

Krzysztof, could you please update the devlibs with this version? Thanks! -- Nicolas

---

This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Hi Simon!

But actually external installation of UniConvertor is the best pattern (like under Linux) because we are going to accelerate UniConvertor development and provide short life cycles for versions (2-3 months). Now we are receiving bug reports from Inkscape win32 users about 1.1.3 version and therefore we have prepared external variant with integration patch to resolve issues. So external installation will allow users easy upgrade UniConvertor and keep up to date it. Also from 1.1.5 version internal UniConvertor structure has a lot of native dependencies so built-in variant will not be easy way for maintenance.

Regards,

Igor Novikov sK1 Project http://sk1project.org

On Tue, Jul 6, 2010 at 11:45 AM, Lewis, Simon <Simon.Lewis@...2371...> wrote:

Hi Igor

Many thanks for the tip - UniConvertor 1.1.5 installed perfectly on my German Windows XP and the vbs script worked as well.

The save as wmf from Inkscape now works perfectly too.

Based on this experience, I strongly recommend including UniConvertor 1.1.5 in the finale 0.48 release of Inskape.

Best regards, Simon

*From:* Igor Novikov [mailto:igor.e.novikov@...400...] *Sent:* Monday, July 05, 2010 4:23 PM *To:* Nicolas Dufour *Cc:* Lewis, Simon; inkscape-devel@lists.sourceforge.net *Subject:* Re: [Inkscape-devel] Re : Inskape 0.48pre1 - Error message when saving as wmf

Hi all,

As an UniConvertor author I would recommend to install UniConvertor 1.1.5 which is installed as a stand-alone application under Windows platform and has no dll clash issues:

http://sk1project.org/modules.php?name=Products&product=uniconvertor&...

to integrate UniConvertor wit Inkscape just run Inkscape patch vbs script from windows Start menu. Details: http://www.libregraphicsworld.org/articles.php?article_id=20

Regards,

Igor Novikov, sK1 Project http://sk1project.org

---

Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Krauss-Maffei Wegmann GmbH & Co. KG Sitz der Gesellschaft ist München Registergericht: Amtsgericht München, HRA 72 460

Persönlich haftende Gesellschafterin: Krauss-Maffei Wegmann Verwaltungs GmbH Sitz der Gesellschaft ist München Registergericht: Amtsgericht München, HRB 118952 Geschäftsführer: Dipl.-Ing. Frank Haun (Vorsitzender), Dipl.-Kfm. Stefan Krischik, Dipl.-Ing. Jürgen Weber Vorsitzender des Aufsichtsrates: Johannes Schmidt

Nevertheless .Net applications have such dependencies (for example Paint.NET) and some times users get info message like "You need installing .Net xxx version to run this program". The simplest way is include UniConvertor MSI package "as is" into Inkscape installer and install it by default running MSI. But users should have ability to skip UniConvertor installation if they already installed it. Also MSI package has unique UID so user will get warning about possible installation clash. Similar pattern is used in Sun Java JDK installer which has JRE installer inside. Thus we could simplify win32 version of Inkscape skipping UniConvertor code maintenance and provide more flexible solution for end users.

Regards,

Igor Novikov

On Tue, Jul 6, 2010 at 1:24 PM, Lewis, Simon <Simon.Lewis@...2371...> wrote:

Hi Igor

As a „seasoned“ Linux user (8 years openSUSE – 3 years Fedora) I agree this would be the best pattern, especially as the RPMs automatically install any dependencies like UniConvertor (when specified as „Requires:“ in the rpm spec file) and UniConvertor would be kept up-to-date through the package manager.

But Windows users don’t think like this and don’t understand when separate programs need to be installed for full functionality. Perhaps the Inscape windows installer needs to be more intelligent and look for an existing UniConvertor installation before installing static libraries?

Best regards, Simon

*From:* Igor Novikov [mailto:igor.e.novikov@...400...] *Sent:* Tuesday, July 06, 2010 11:28 AM *To:* Lewis, Simon *Cc:* Nicolas Dufour; inkscape-devel@lists.sourceforge.net *Subject:* Re: Inskape 0.48pre1 - Error message when saving as wmf

Hi Simon!

But actually external installation of UniConvertor is the best pattern (like under Linux) because we are going to accelerate UniConvertor development and provide short life cycles for versions (2-3 months). Now we are receiving bug reports from Inkscape win32 users about 1.1.3 version and therefore we have prepared external variant with integration patch to resolve issues. So external installation will allow users easy upgrade UniConvertor and keep up to date it. Also from 1.1.5 version internal UniConvertor structure has a lot of native dependencies so built-in variant will not be easy way for maintenance.

Regards,

Igor Novikov sK1 Project http://sk1project.org

Krauss-Maffei Wegmann GmbH & Co. KG Sitz der Gesellschaft ist München Registergericht: Amtsgericht München, HRA 72 460

Persönlich haftende Gesellschafterin: Krauss-Maffei Wegmann Verwaltungs GmbH Sitz der Gesellschaft ist München Registergericht: Amtsgericht München, HRB 118952 Geschäftsführer: Dipl.-Ing. Frank Haun (Vorsitzender), Dipl.-Kfm. Stefan Krischik, Dipl.-Ing. Jürgen Weber Vorsitzender des Aufsichtsrates: Johannes Schmidt

Hi,

De : Krzysztof Kosiński <tweenk.pl@...400...> 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

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

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...).

I think that will be perceived as a regression. Lots of formats that used to work will suddenly stop working. We had a lot of pain with displaying messages like this - most people simply perceive any such message as an error and complain or give up without reading. Those who read it and act on it will be a minority.

What's such a big problem with including a new UC into devlibs?