[androidgirl]

I use inkscape at work in part of a large-ish application.

We chose to use inkscape for part of an image generation toolkit because of the great command line options and the easy to modify source files.

As for the UI, ever since .91 they have fixed my biggest concern, and I'm really happy for the team. Rarely feel the pain and need to reach for illustrator on a windows machine!

[dylan604]

We have recently been playing with a laser cutter for protyping, and have been using different applications to get SVGs to the cutter. Illustrator has actually been a pain for this. Illustrator's SVG format does not retain the dimensions correctly. After trial and error, it turns out that the Illustrator SVG must be scaled 133%. SVGs coming out of Inkscape do not suffer from this problem.

At this point, I have not used Inkscape as someone else has been using it (not a power user). However, hearing about its command line options makes me want to investigate that immediately. I have been suggesting a CLI approach would be much better for us with all of the automation we are looking to implement. Thanks!

[rbalsdon]

I was just told that Illustrator assumes 96 dpi and Glowforge assumes 76 dpi. If you change the Illustrator doc settings to the lower dpi, dimensions will work right. Same problem with Sketch. I haven’t tried the solution out yet to confirm.

[mdorazio]

Just as a counterpoint, I had the exact opposite problem on my laser cutter. Inkscape SVGs were always the wrong size, while Illustrator ones were perfect. It ended up being a difference in the assumed resolution of SVGs in the control board firmware. Also, if you forget to save from Inkscape as a vanilla SVG, you end up with inkscape-specific tags that cause laser software to freak out.

[ris]

> because of the great command line options and the easy to modify source files.

Some of my projects have only the icon svgs checked into the source repo and the build tool renders them to PNGs through inkscape. Works really well.