Inkscape

Saving as XCF

Asked by Syllie

Hi there,

WinXP / Inkscape 0.47
It seems that the save as .xcf format as described in tav's manual is not available for win32. Is this correct?

Ubuntu 9.10 / Inkscape 0.47+devel r, built Jan 13 2010
When I try to save a single layer Inkscape SVG to .xcf I run into error messages, not sure if they are bugs and if this functionality is running properly as it is a developers version. I could not find bug reports on this issue, but do not wanna lodge ones that aren't bugs either - so it would be great if someone can point me in the right direction:

------------------------
Traceback (most recent call last):
  File "/usr/share/inkscape-devel/extensions/gimp_xcf.py", line 185, in <module>
    e.affect()
  File "/usr/share/inkscape-devel/extensions/inkex.py", line 208, in affect
    self.effect()
  File "/usr/share/inkscape-devel/extensions/gimp_xcf.py", line 179, in effect
    x = open(xcf, 'r')
IOError: [Errno 2] No such file or directory: '/tmp/tmpb3XEEo/paisley_test.xcf'

------------------
Observations:
The directory exists but file is not created.
At specified output location (desktop) a 0 byte file with the specified name is created.
The filename in Inkscape changes to <filename>.xcf but it is not actually saved in that format (nor does saving again result in a non 0 bytes file).

Is this a bug or am I missing something?

Cheers,
Syllie

Question information

Language:
English Edit question
Status:
Solved
For:
Inkscape Edit question
Assignee:
No assignee Edit question
Solved by:
Syllie
Solved:
Last query:
Last reply:
Revision history for this message
jazzynico (jazzynico) said : 		#1

Hi,

I can't reproduce this issue on Ubuntu 9.10, Inkscape 0.47+devel r9113, but 0.47pre4 had that kind of error messages.
Could you please create a new bug report and attach the SVG which generates the error?
Thanks!

Revision history for this message
Syllie (eurosyl1) said : 		#2

Will do.

That was just a partial answer tho :)

Is the save to XCF unavailable for win32 users?

Cheers, Syllie

Revision history for this message
su_v (suv-lp) said : 		#3

The export extension "GIMP XCF maintaining layers (*.xcf)" uses and depends on 'gimp' being found in $PATH - which is not likely on win32 platforms (but I don't know for sure)?

gimp_xcf.inx:
  <dependency type="executable" location="path">gimp</dependency>

gimp_xcf.py:
  f = os.popen('gimp -i --batch-interpreter plug-in-script-fu-eval -b - > %s 2>&1' % junk,'w')

Revision history for this message
Syllie (eurosyl1) said : 		#4

hmm... making it a documented requirement to add GIMP to an environment variable should not be a problem.

I do find it a problem that it is documented as an export feature that is not available (at least not to the win users). Reason for exploring this path was to see if saving as XCF resulted in better quality than letting GIMP rasterize SVG (which might have been ambitiously anyways).

Thanks for the answers.

Cheers,
Syllie