Inkscape to OpenSCAD converter v6
by dnewman, published
___This is version 6 of Thing #24808___
___At github as github.com/l0b0/paths2openscad .___
Libre Graphics World has a nice write up by Alexandre Prokoudine of this extension at libregraphicsworld.org/blog/entry/inkscape-gets-openscad-converter
This Thing is an Inkscape extension to export Inkscape paths to OpenSCAD. There has been at least one prior Thing attempting this, Thing #9376. However, it only handled a small subset of SVG. This extension handles SVG arcs, clones, circles, ellipses, groups, lines, paths, polygons, polylines, rects, and splines. It also follows document transforms as well as viewports. Either an entire document or just the selected portions of a document are processed.
SVG text must first be converted to a path within Inkscape using Inkscape's "Path > Object to Path" menu item.
Note that another approach to importing SVG into OpenSCAD is to save the SVG to DXF from within Inkscape. Then use OpenSCAD's import() function to import the DXF. [Older versions of OpenSCAD used import_dxf().]
Much of the core code in this extension is derived from work done by myself and others while developing the Inkscape driver for the Eggbot.
___15 June 2012:___ Added support for a single level of polygon nesting. I.e., subtract from a polygon the polygons contained within it AND from the same Inkscape path. This works well for most fonts. You can tell Inkscape to combine multiple polygons into a single path by selecting the polygons and then using "Path > Combine". (You do not need to do this for text converted to a path: Inkscape already does the proper combining.)
___15 June 2012:___ Corrected Windows issue with handling of Unix-style file paths.
___21 June 2012:___ Correct a typo in the extension. Would not affect content generated by Inkscape but might have affected SVG content generated elsewhere and loaded into Inkscape.
___9 May 2013:___ Modified the code to remove non alphanumeric characters from the strings used to generate the OpenSCAD module names. Some SVG paths had non alphanumeric characters in their path ids and those ids were being used to generate OpenSCAD module names. OpenSCAD doesn't allow that.
___29 May 2013:___ Corrected an issue whereby the converted could exit with an error when attempting to warn about images embedded in the SVG file or Inkscape drawing. Images are not allowed and the converter cannot convert them. However, it should gracefully warn about the issue and exit normally.
___30 May 2013:___ Fixed a bug in the v4 version.
___16 Aug 2013:___ Possible workaround to Inkscape bug experienced by some users, "terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct null not valid"
Recent Commentsview all
Whatever software you used to create the SVG must have decided to use 72 units / inch. It should have, using standardized SVG, specified that it was using units of printer's points, pt, which are 72 pt to 1 inch. Looks as though it didn't, or there's a bug in the openscad converter which isn't handling the unit specification correctly.
I'll look into the SVG. Do you have thoughts on why I would end up with 72 units / inch being the correct scale instead of 90?
You need to fix your SVG to have units or correct units. SVG files should specify the units used (cm, ft, in, m, mm, pc, or pt) and if no units are specified then user units are assumed as per the SVG specification. Moreover 1 user unit is defined to be 1px. Further, the conversion from px to mm is 90px to 25.4 mm. (More precisely, 90px is defined to be 1inch.) So, if things are scaled improperly, the issue is likely with your SVG and you need to correct the usage of units in your SVG file.
P.S. Technically, if no units are specified then the measurement defaults to "user" units. But 1px is defined to be 1 user unit so you can use them interchangeably.
Liked Byview all
Give a Shout Out
MAC 10.7 or later users, see the second note in the Notes section! This means Lion, Mt. Lion, and beyond.
Download the paths2openscad-2.zip file from this page. After unzipping that archive, you should have two files: paths2openscad.py and paths2openscad.inx .
Once you have downloaded paths2openscad.zip, open the zip file and place its contents in your local Inkscape extension folder,
on Linux and OS X. On Windows systems, you can place them directly into the Inkscape extension directory. For example, if Inkscape is installed in C:/Program Files/Inkscape then the extension directory will be C:/Program Files/Inkscape/share/extensions.
Once you have placed the two files in the proper directory, exit and then restart Inkscape. The extension should appear under the "Extensions > Generate from Path" menu as "Paths to OpenSCAD".
To use the extension,
0. You may find it helpful to set your document units to millimeters and the document dimension to millimeters as well as a reasonable document size (e.g., 100 x 100 mm). Do this with the "File > Document Properties" menu item. The document units is in the upper part of the dialog box while the document dimensions are near the bottom of that same box.
1. To see what the extension sees, set Inkscape's display mode to "outline". This is done with the "Display Mode" item of the "View" menu.
2. Next ensure that within Inkscape, the desired objects have been converted to paths. Use the "Path > Object to Path" menu item to convert objects such as text to paths.
3. Select the desired objects to generate an OpenSCAD program for. If you wish to generate a program for the entire document, then select nothing (i.e., "Edit > Deselect").
4. From the "Extensions" menu, select "Generate from Path > Paths to OpenSCAD".
5. In the dialog window which appears, enter the name of the output file to generate. (Windows users: the "~" notation indicates that the file goes into your "Document and Settings" folder.) You can also enter a extrusion height and a smoothing parameter. For most purposes, a smoothing parameter of 0.2 is sufficient. If your paths have lots of tight, twisty curves which are described using arcs, circles, ellipses, or other SVG elements which aren't collections of straight line segments, then you may want to use a smaller value.
6. Click the "Apply" button. A pop-up window will appear while the extension is running and will then disappear when it is done running. After the extension is done running, you can click the "Close" button to dismiss the extension's dialog window. If an error occurs, you will see an error window appear when the extension is running.
7. From OpenSCAD, open the output file you generated with the extension and render it.
If you wish to build solids involving subtracting one polygon from another, be sure to combine the two polygons into a single path: select the polygons and then combine them with "Path > Combine". Only a single level of nesting is handled at present. You do not need to do this for text converted to a path: Inkscape already does the proper combining.
I have seen a few complex, but legitimate polygons, compile and render with F5 but not with F6 in OpenSCAD. They instead trigger some internal error detection code in OpenSCAD.
1. The sample .svg, .stl, and .scad files serve as examples: you do not need to download them to use this Inkscape extension. You only need the .zip file.
2. OS X Lion (10.7) and Mt. Lion (10.8) users need a "patch" to allow Inkscape extensions to work correctly. This is a general Inkscape issue and not specific to this extension. At issue is the lack of a Python package, lxml, which Inkscape extensions use to read (parse) SVG files. Install the patch from code.google.com/p/eggbotcode/downloads/detail?name=EggBot2.2.2.r2.mpkg.zip . This will also give you Eggbot extensions, many of which I wrote. (An Eggbot is a cool pen plotter for plotting on Eggs.)
You must be logged in to post a comment.