On Fri, 4 Apr 2014 17:27:48 +0200 John Smith <lbalbalba@...155...> wrote:
On Fri, Apr 4, 2014 at 4:36 PM, Steve Litt <slitt@...2357...> wrote:
I bet if you tell us *why* you want to build an SVG from baby SVGs from the command line, somebody will come up with a much better way of doing it.
Allright, here we go.
I want to create svg files in an automated unattended manner (with unix shell scripts, command line tools, etc.) The output must be a single SVG file, so I can open the resulting files in MS Visio and/or LibreOffice.
The resulting single file should be an SVG that shows (part of) an IT infrastructure. The input is an ascii texty file containing things like hostname, location, etc. The text file has enough content and detail for me to create the picture.
I have no knowledge at all of the svg format or xml in general. So the easiest way to achieve the goal seemed to be to create 'baby svgs' in a WYSIWG GUI application, and then use a commandline program to paste the baby's onto the big canvas. I figured that doing it this way, I could just treat everything as a 'picture' (no matter if its jpg or svg or bmp or whatever) and use a commandline program to cut n paste, and I wouldnt have to learn the internals of SVG or XML.
(I attached an zipped svg file that sort of looks like what I want the end result to be, but im not sure if the mailing list lets me add attachments.)
Yes, but you haven't answered the question: Why not just use Inkscape itself to make your grand SVG? How could making a bunch of babies, without simultaneously seeing the first ones, be easier than just building layers in Inkscape, and making them visible/invisible as necessary?
SteveT
Steve Litt * http://www.troubleshooters.com/ Troubleshooting Training * Human Performance