SVG import / export status ?

[GerryI]

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

[Korab]

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

[Korab]

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

[GerryI]

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

[Korab]

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.

[Korab]

My path ~/.local/bin was added to local path (~/.bashrc). On terminal conversion works fine, on Xara import not working. Why ?

[Odat]

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.

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!

[stuseven]

Gerry - This is excellent ! That SVG-to-*.xar import/conversion
works great for me, even on slightly older releases (as far back as
three days ago :-)

Since you are familiar with this command line function, perhaps
you can suggest a similar command line sequence for EXPORTING
SVG from a finished *.xar file ?
(note - I tried many variations of the command you had suggested for
import, trying to export the SVG - but all without success) - here are
a few I tried which failed:
xarasvgfilter -e file.svg < file.xar
xarasvgfilter -e file.xar > -x file.svg
...note, again, these aren't documented syntax, just guessing... I dont
see any documentation for those binaries.

Also, Gerry, or anyone in the know... what difference is there
between the two binaries xarasvgfilter /and/ xarasvgfilterui ?
It occurred to me, since xarasvgfilter worked for importing, the
other might be for export ? If so, still lacking syntax for an actual
command line export.

much thanks / stuseven

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

[Korab]

Usage: xarasvgfilter [-h] [-v] [-g] [-p] [-e] [-c] [-i] [-z] [-f <str>] [-x <str>]
-h, --help show this help message
-v, --verbose be verbose
-g, --progress give progress
-p, --prepareexport prepare export
-e, --export do export
-c, --canimport can import
-i, --import do import
-z, --compress (de)compress (output) input file
-f, --file=<str> input/output file
-x, --xmlfile=<str> xml configuration file

I suppose export not ready yet.

xarasvgfilter -e -f inputfile.xar -x outputfile.svg

[Korab]

but remember it call xarasvgfilterui