So now you have two working files that are aligned with each other. You now just go into paths, right click, import path and load that same svg again and your paths should be right where you wanted them. No worries, this step was just to get your gimp document sized to match your inkscape document.
Perhaps if you save the inkscape svg without the background gimp image in it? Don't know. Here's another problem, once you select to load the svg as layers, you get a nice box to adjust coordinates (which you don't want to do), and a little check box that says "Import paths". This usually gives me larger layers than the canvas but it should be centered around the same image.
I load my xcf that I am working on and do a File->Open as layers on the svg. The reason for centering the gimp image is so you can make the paths on top of the image where you want them to be and then load them into gimp and not have to move them around. Once I have my paths, I save the file as svg. Then I will put that image on a layer where I can hide it and what not while I work on the paths that I ultimately want to become gimp selected areas. I flatten my working copy in gimp and save as an image, then import into my inkscape document and center it. I make an Inkscape document with dimension large enough to contain the gimp image I am working on. The solution I found is not slick, but it works. Converting all to curves has fixed that, but then you cannot reasonably scale the paths. But getting the paths into Gimp has been a problem for me. Inkscape is just so much better for editing paths. This forces Inkscape to rewrite the path data in a way that seems to be better handled by GIMP's SVG import library (librsvg). Note: this is not the same as converting cusp nodes into smooth nodes: in the node tool, select all (Ctrl+A) and use the 12th button on the controls bar ("Make selected segments curves") - this keeps the shape as is, but adds handles to each node even for straight line segments (in this case collinear with the segments). I haven't specifically tested SVG import into GIMP of Inkscape files created after changing the SVG output options in the Inkscape preferences to 1) not Allow relative coordinates and 2) Force repeat commands, but it might be worth a try whether it helps to solve your issue. QtSvgRenderer (Gwenview of KDE), Blender). The underlying cause for these issues might be the optimized path data Inkscape 0.47 uses and which is known to cause issues in other SVG renderers (e.g. Testing your file with Inkscape 0.47 and GIMP 2.6.8 (on OS X 10.5.8, but this shouldn't make a difference) - I noticed that import in GIMP as paths worked well when I converted all path segments to curves in Inkscape before importing the SVG into GIMP. (…) I am working with GIMP version 2.6.8 and Inkscape 0.47. I lose the path information, connectivity as well as the 'beziered' attributes. Morpheus wrote:When I 'path import' this into gimp, all I get it is the bunch of points. I am working with GIMP version 2.6.8 and Inkscape 0.47.
When I 'path import' this into gimp, all I get it is the bunch of points. I make a graphic (a closed path consisting of straight lines and bezier'ed to contain some curves) in inkscape and save it as an svg. But not the Mac.Īlways proofread carefully to see if you any words out.I am encountering the same problem. Note: I was successful in installing the X11 package on my iMac running Tiger and GIMP works fine on that machine.
Gimp for mac 10.5.8 update#
I've tried doing an update to the X11 application but it states that I don't need this application. Reason: Incompatible library version: libgtk-x11-2.0.0.dylib requires version 3.0.0 or later, but libXdamage.1.dylib provides version 2.0.0 Referenced from: /tmp/skl/Gimp.app/Contents/Resources/lib/libgtk-x11-2.0.0.dylib Library not loaded: /usr/X11/lib/libXdamage.1.dylib Path: /tmp/skl/Gimp.app/Contents/Resources/bin/gimp-2.6 Now, the error continually tells me GIMP application quit unexpectedly and the option to ignore, report, or re-launch. Having a problem getting GIMP to run on my macbook.
0 kommentar(er)
