-
SVG import / export status ?
+ In the past week of daily releases for Linux, the
XaraLX package has included "xarasvgfilter" and "xarasvgfilterui",
which, according to the author, may be used as command line
conversion tools with XaraLX...
...and, in other discussion, we see that SVG import should now
be possible, via the import menu... but, for me, none of these
features have worked - this, again, in any of the four or five
newest releases I've downloaded.
Is SVG import/export still a work in progress, or is there some
way to do this already, before it appears in the menus ?
Thanks to anyone who may know !
-
Re: SVG import / export status ?
Quote:
Originally Posted by stuseven
+ In the past week of daily releases for Linux, the
XaraLX package has included "xarasvgfilter" and "xarasvgfilterui",
which, according to the author, may be used as command line
conversion tools with XaraLX...
...and, in other discussion, we see that SVG import should now
be possible, via the import menu... but, for me, none of these
features have worked - this, again, in any of the four or five
newest releases I've downloaded.
Is SVG import/export still a work in progress, or is there some
way to do this already, before it appears in the menus ?
Thanks to anyone who may know !
It's still a work-in-progress in the sense that it needs fully integrating. I don't think anyone has tested it on the command line, but very recent builds should do SVG import (I think). Whether autopackage is installing the SVG filter right right is another matter: we've done a lot of fiddling there (not helped by renaming the binaries). What's the most recent build you've tried?
The recommended 0.7 version (when released) should have functional SVG import.
Alex
-
Re: SVG import / export status ?
+ Alex - Thanks for your reply.
As I said, I've been downloading the daily builds... so... yesterday's
will have been the latest I'd installed - however, that version did not
include menu items for either SVG import or export (and I was unable to
get the svgfile binaries to produce anything useable).
I have downloaded, but not yet installed, today's XaraLX release, (version 0.7 Revision 1680 Built 08-Aug-06 12:00)... I'm still not at my
Linux machine, and haven't tried it yet. Hopefully, this newest one will
do it ! If not, I'm happy to wait... it should be a great new feature
when it's ready.
Quote:
Originally Posted by abligh
It's still a work-in-progress in the sense that it needs fully integrating. I don't think anyone has tested it on the command line, but very recent builds should do SVG import (I think). Whether autopackage is installing the SVG filter right right is another matter: we've done a lot of fiddling there (not helped by renaming the binaries). What's the most recent build you've tried?
The recommended 0.7 version (when released) should have functional SVG import.
Alex
-
Re: SVG import / export status ?
Its not working here either.
With revision 1680 SVG does not appear as an option under either the import or export menu. Furthermore, trying to import a rather simple SVG produces: "That file is not recognized by any of the installed filters."
Cheers,
--
Jed
-
Re: SVG import / export status ?
SVG import (r1680) can't handle any of the Open Clipart Library files. Only the simplest of drawing can be imported, from Inkscape, and offset to the upper-right of the screen, off the page.
frank
-
Re: SVG import / export status ?
Please can those people reporting that SVG import isn't available after Autopackage install please answer the following questions.
- Are you installing the autopackage with default options (so files get installed under /usr)?
- Can you see all the following files are installed:-
/usr/bin/xarasvgfilter
/usr/bin/xarasvgfilterui
/usr/share/xaralx/filters/svgfilter.xml
/usr/share/xaralx/filters/svgfilterc.xml
Please try using revision 1680 or higher.
Once installed, you should see that SVG is included as one of the many import file types. Do File, Import. Go to the file type list near the bottom of the dialog (it will show *.XAR by default). You should see SVG included in the list of types in that list.
After choosing a file (choose a simple one for now as this is work in progress) you should find the data has been imported into your current design. Usually it appears above and to the right of your current view (bug), so zoom out to see it.
Thanks
Neil
-
Re: SVG import / export status ?
Yes, to all your questions, Neil, I see them all in their correct places.
I have the import filter SVG file type in the menu. I can import simple SVG drawings, after zooming out to get them.
I used autopackage to install Xara LX r1680.
frank
-
Re: SVG import / export status ?
Ok now this is interesting. I have r1680 installed both here at work and also at home (home runs Slack 10.1 and work Slack 10.2).
At home, SVG import works for all of the (2 or 3) files I've tried from openclipart.org. As has been mentioned, the files import rather huge and away from the open page, but big whoop, that's no show stopper.
At work however, the SVG import doesn't work at all, not even for the files that work at home for the same revision. Although SVG is in the import dialog, when I try to import the document I get two dialog boxes; One with the "This file may not work with this filter" message, and then another one that says "Plugin filter reported an error but didn't provide a message".
I presume that I'm running the package with default options, since I'm not specifying any. However, I'm installing them as my own user rather than root, so they get installed to $(HOME)/.local/ instead of /usr. The files mentioned are in the appropriate location under that path, both at home (where this works) at here at work (where it doesn't).
I even used ldd to make sure that I'm not missing a library, and tried to run the executes manually, and things check out that way.
-
Re: SVG import / export status ?
Thanks.
Stuseven - can you try again please. You don't actually say whether you were using the autopackage or not. Please try the latest autopackage. We know that there is a problem with using the tar archive. If you install using the tar archive you won't be able to see the SVG import filter currently.
Thanks
Neil
-
Re: SVG import / export status ?
Oops I forgot to mention that I am using the tar archive. It looks like that is already a known issue.
--
Jed
-
Re: SVG import / export status ?
Hi Neil - OK then, looks like I'll have to wait... I have never
been able to use the autopackaged releases... perhaps just
something I need to install, but it has never worked on my
Linux... the bzip'd version is what I can use presently.
Good to know about the tar archive problem.
Here's hoping it isn't too much longer !
stuseven
Quote:
Originally Posted by NeilH
Thanks.
Stuseven - can you try again please. You don't actually say whether you were using the autopackage or not. Please try the latest autopackage. We know that there is a problem with using the tar archive. If you install using the tar archive you won't be able to see the SVG import filter currently.
Thanks
Neil
-
Re: SVG import / export status ?
Quote:
Originally Posted by stuseven
Hi Neil - OK then, looks like I'll have to wait... I have never
been able to use the autopackaged releases... perhaps just
something I need to install, but it has never worked on my
Linux... the bzip'd version is what I can use presently.
Good to know about the tar archive problem.
Here's hoping it isn't too much longer !
stuseven
Just so we have this clear, is ANYONE seeing problems where the svgfilter does not appear on the import type menus (we are not concerned right now about the offset problems, import failures etc.) who is using the AUTOPACKAGE version?
Also, is there anyone for whom the above works, using the TARBALL version?
Alex
-
Re: SVG import / export status ?
Quote:
Originally Posted by fjgaude
SVG import (r1680) can't handle any of the Open Clipart Library files. Only the simplest of drawing can be imported, from Inkscape, and offset to the upper-right of the screen, off the page.
frank
That's a different problem to it not being installed (indeed it shows it is installed). I 'm hoping most of that's fixed in r1687 (certainly the offset bug).
We are aware that the SVGFilter is not yet complete.
Alex
-
Re: SVG import / export status ?
Hi Alex,
I use the autopackage and the SVG import works using a simple svg image I created with inkscape. Simple Circle and rectangle with solid colour fills.
-
Re: SVG import / export status ?
Quote:
Originally Posted by abligh
That's a different problem to it not being installed (indeed it shows it is installed). I 'm hoping most of that's fixed in r1687 (certainly the offset bug).
We are aware that the SVGFilter is not yet complete.
Alex
In FC5, using autopackage r1691, all works for importing simple SVG drawings, even the centering of it on the page. Good work, guys.
frank
-
Re: SVG import / export status ?
I think r1691 should also fix the "mysterious missing SVGFilter" issue when using the tar.bz2 version.
-
Re: SVG import / export status ?
Quote:
Originally Posted by abligh
Also, is there anyone for whom the above works, using the TARBALL version?
Using the TARBALL version of rev. 1691 SVG shows up in the import menu but the import fails complaining that the file is not suitable for the chosen filter (SVG). SVG files are not recognized when trying to import using "All files"
--
Jed
-
Re: SVG import / export status ?
Jed are you using a simple drawing in SVG format or one of the Open Clipart Library files?
-
Re: SVG import / export status ?
Quote:
Originally Posted by Soquili
Jed are you using a simple drawing in SVG format or one of the Open Clipart Library files?
A filled circle created in Inkscape and saved as "Plain SVG." Although, I did try a couple of other files just for fun. I don't know if I can get much simpler. :)
-
Re: SVG import / export status ?
There are some comments on the developer mailing list, that Inkscape uses arcs to create circles/ellipses and the current svg import filter doesn't interprete arcs, right now.
It seems, the current implementation of the svg import filter supports only lines, rectangles, polylines and paths with flat fills.
Regards,
Remi
-
Re: SVG import / export status ?
Quote:
Originally Posted by jedfrechette
Using the TARBALL version of rev. 1691 SVG shows up in the import menu but the import fails complaining that the file is not suitable for the chosen filter (SVG). SVG files are not recognized when trying to import using "All files"
--
Jed
You might try deleting your preferences (this is the equivalent of the "reinstall windows" helpine suggestion I know, but there is a specific reason why it's useful here).
Alex
-
Re: SVG import / export status ?
Quote:
Originally Posted by jedfrechette
Using the TARBALL version of rev. 1691 SVG shows up in the import menu but the import fails complaining that the file is not suitable for the chosen filter (SVG). SVG files are not recognized when trying to import using "All files"
--
Jed
I'm using the autopackage version and seeing the same thing. The weird thing is that on my machine at home running the same revision, the same files that this machine says it can't import, the other can.
Tried dumping the preferences, but that didn't fix the problem.
-
Re: SVG import / export status ?
Quote:
Originally Posted by Odat
I'm using the autopackage version and seeing the same thing. The weird thing is that on my machine at home running the same revision, the same files that this machine says it can't import, the other can.
Tried dumping the preferences, but that didn't fix the problem.
Which autopackage version?
Alex
-
Re: SVG import / export status ?
Quote:
Originally Posted by abligh
You might try deleting your preferences
I've already tried this, unfortunately, with no luck. The SVG entries and new templates still appear in the menus but importing (or exporting) doesn't work. Both fail with "Plugin filter reported an error but didn't provide a message." I thought I might be having problems because I also had the Debian package of xaralx installed but purging the package didn't help.
Quote:
Originally Posted by remi
It seems, the current implementation of the svg import filter supports only lines, rectangles, polylines and paths with flat fills.
I've also tried files containing single instances of these shapes with no luck. That being said I wouldn't be ready to rule out the possibility that my SVG is bad.
I see that the subversion server has a number of test SVG files. I don't have the time to do it at the moment but I will take a look at these and try to narrow down what is going on as soon as I have a chance.
-
Re: SVG import / export status ?
Quote:
Originally Posted by abligh
Which autopackage version?
Alex
r1691, downloaded earlier today. I also get the dialog saying "The plugin reported an error but not a message" (or whatever the text is).
On my other machine the same revision works just fine, using the same sample files.
-
Re: SVG import / export status ?
In Inkscape 0,43 - I save simple rectangle. When try import to Xara rev. 1685[autopackage] (selected type files on SVG) Xara reply "This file may not be suitable for this filter - are you sure you wish to continue ?", when selected "Import" reply is "Plugin filter reported an error but didn't provide a message"
-
Re: SVG import / export status ?
Xara 1692 downloaded and tested with resuts above (rectangle saving on Inkscape no filled)
-
Re: SVG import / export status ?
Hello,
Can you try running the filter from the command line, e.g.
xarasvgfilter -i -f inputfile.svg > outputfile.xar
...should convert the svg file to a xar file which you should be able to load into XaraLX.
xarasvgfilter -c -f inputfile.svg
...should print a number between 0 and 10 (0 if it isn't an SVG file and 10 if it is).
Cheers,
Gerry
-
Re: SVG import / export status ?
Quote:
Originally Posted by
Korab
When try import to Xara rev. 1685[autopackage] (selected type files on SVG) Xara reply "This file may not be suitable for this filter - are you sure you wish to continue ?", when selected "Import" reply is "Plugin filter reported an error but didn't provide a message"
I got such a result when installing as user with tar.bz2. There the problem was that xarasvgfilter was not in the path (I called ./xaralx/bin/xaralx).
If you have an unusual location for the installation (i.e. not /usr/ with /usr/bin/xaralx) this could also be your problem.
Does which xarasvgfilter work (shows where that executable is installed)?
Tobias
-
Re: SVG import / export status ?
Right gentelman :) I can't load xarasvgfilter
Xara was instaled with privilege regular user from package into home directory.
Where I can set right path to xarasvgfilter (myHome/.local/bin)
-
Re: SVG import / export status ?
Quote:
Originally Posted by
GerryI
Hello,
Can you try running the filter from the command line, e.g.
xarasvgfilter -i -f inputfile.svg > outputfile.xar
Gerry
Done (with full path) reply :
Segmentation fault
-
Re: SVG import / export status ?
OK works, (but I can't use polish letters in name of directory)
Polish letters = Segmentation fault on reply
Size rectangle not same (154,61/115,90 mm on Inkscape, and 192,5/144,1 mm on Xara
-
Re: SVG import / export status ?
Does the -c version of the command also seg fault with Polish filenames?
It sounds like we have a general problem in the handling of unicode filenames. I'll try to find out why...
Gerry
-
Re: SVG import / export status ?
Quote:
Originally Posted by
tobias
If you have an unusual location for the installation (i.e. not /usr/ with /usr/bin/xaralx) this could also be your problem.
Ah, this was my problem. I added symbolic links to xarasvgfilter and xarasvgfilterui in $HOME/bin (which is on my $PATH) and everything works nicely.
I was under the, apparently mistaken, assumption that binreloc would take care of finding the executables in xaralx/bin/ as well as the resources in xaralx/share/.
In any case, I'm glad to have this working. Thanks to all for your help.
-
Re: SVG import / export status ?
Quote:
Originally Posted by
jedfrechette
Ah, this was my problem. I added symbolic links to xarasvgfilter and xarasvgfilterui in $HOME/bin (which is on my $PATH) and everything works nicely.
I was under the, apparently mistaken, assumption that binreloc would take care of finding the executables in xaralx/bin/ as well as the resources in xaralx/share/.
In any case, I'm glad to have this working. Thanks to all for your help.
Not entirely mistaken, because that's where I have my xaralx installed, and it works fine on this computer without my having to create any links. On my work computer however, it doesn't work for beans. When I get in today I'll see if these suggestions fix anything.
-
Re: SVG import / export status ?
Quote:
Originally Posted by
GerryI
It sounds like we have a general problem in the handling of unicode filenames. I'll try to find out why...
Gerry
No, filenames works fine, directory names (with polish letters utf-8) not.
-
Re: SVG import / export status ?
My path ~/.local/bin was added to local path (~/.bashrc). On terminal conversion works fine, on Xara import not working. Why ?
-
Re: SVG import / export status ?
I may have a possible explanation for why this sometimes works and sometimes doesn't.
I have installed the same autopackage revision r1690 both here and at home, and while SVG import works just fine from home, at work it doesn't at all (tells me the file may not be SVG, and then reports that the filter reported an error with no message).
Doing some testing, I indeed discovered that if I symlinked the svg filter binaries to a directory on the path, the filter worked.
I happened to notice that at home, $(HOME)/.local/bin was a part of my path, but I wasn't the one that added it. So I checked and discovered that autopackage crammed a line into the end of my .bashrc for me.
I then checked at work, and lo and behold, $(HOME)/.local/bin is in the path as well, for the same reason. And yet, I have to symlink the binaries into a different directory on the path in order to get it to work.
So that's when the penny dropped. You can probably guess what's coming. A quick check of the uptime on my work computer shows that I've been running the same login session since the first time I installed autopackage. This isn't the case at home, as I had to reboot recently during a kernel upgrade.
Here at work my window manager hasn't been restarted in so long that as far as it's concerned, $(HOME)/.local/bin isn't in the path, so anything that it launches also doesn't know. If I launch xaralx from a terminal, it works just fine.
So, I shut down the window manager, did a ". ~/.bashrc" and restarted it, and now things work just dandy. :o
I'd say that anyone that installed the autopackage as their own user that has problems with SVG import should first try launching the binary from a terminal (if that's not how you're already doing it) and see if that fixes the problem. If so, you may be experiencing the same problem. Nothing a logout-then-login can't cure!
-
Re: SVG import / export status ?
Quote:
Originally Posted by
jedfrechette
I was under the, apparently mistaken, assumption that binreloc would take care of finding the executables in xaralx/bin/ as well as the resources in xaralx/share/.
It should do this. I'm interested to know why it doesn't work (assuming deleting preferences didn't help). What it was doing before r1692 was "corrupting" the preferences by sticking a path in there all the time, so if you installed a new version it wouldn't work.
It should not need to be on the path. If it does need to be on the path, that's a bug we need to fix. In fact I'd go further: it shouldn't use the path at all, and if that fixes it, there's something else broken.
Alex
-
Re: SVG import / export status ?
Quote:
Originally Posted by
Odat
I may have a possible explanation for why this sometimes works and sometimes doesn't.
I then checked at work, and lo and behold, $(HOME)/.local/bin is in the path as well, for the same reason. And yet, I have to symlink the binaries into a different directory on the path in order to get it to work.
The only thing I can think is happening here is that something had the old stuff's inode cached (i.e. the bash shell had the inodes of the directories on the path cached on the version that didn't work). You said it (somehow) had got onto the path on both machines. This would imply the difference is actually the version of LX you were running. So you thought you were running r1692 (having installed it) but actually you weren't. This would have the additional amusing consequence of breaking the preferences every time you run it.
The only other explanation for this making a difference is binreloc failing (assuming it's not the preferences bug). It should not matter one jot whether LX is on the path provided you can run it (and adding things to your path is precisely why I hate things like autopackage). That's because what binreloc does is (effectively) take the path to the binary (from /proc/self), remove the "/bin/xaralx" and add "/share". So provided it's passed a path ending "/bin/xaralx" it should work fine.
Alex