Graphviz should be able to output its dot language source code as part of SVG documentation. Although simply commenting it with XML comments “< ! - -” and “- - >” would run into trouble with “- -” content, you could use a combination of CDATA and defs instead at the end of the SVG file like this: <!…

Do you have a use case for this?

Just today I was providing a SVG image of a PV power diagram to someone and I wanted to include the source with the SVG so he could modify it if he wanted to without having to keep track of the source file for which SVG he’s looking at. Actually it would be cool if it could recognize its own source …

It would also be nice to be able to find the source to old SVG files when they get separated.

Seemingly you can do this now, using the comment attribute: f=ranksep00.gv;T=svg;F=$(basename $f .gv); /usr/bin/dot -G"comment=$(cat $f)" -T$T $f >$F.$T But if you want it as a default, create an issue here: Issues · graphviz / graphviz · GitLab

well sort of - but it tries to put it into a regular XML comment, and to avoid the double dash problem, all dashes are replaced with entity - which doesn’t lend itself to easily copying the source code back from a comment. That’s why CDATA was suggested. Thanks for the link to the issues database.

[image] Include graphviz source in SVG file (#2121) · Issues · graphviz / graphviz ·... Steps to reproduce Use dot to create SVG output, and examine it.

Maybe this is a silly question, but if your recipient is modifying the source then they also have Graphviz installed, so why not just email around DOT files instead of SVGs? You can both view them as SVGs (or anything else) on your respective sides.

I don’t know for a fact when I send it whether he has graphviz installed or not. I do know he’s an engineer who can install it. Also for archival, I’ll see the thumbnails of SVGs and be able to find them, not dot files.

If this isn’t approved, then perhaps using an image database will help you on managing source and output files easier

related idea: [image] Adding metadata to the output Dev From What is image metadata? - Definition from WhatIs.com , there are 3 types of metadata: Technical metadata: aperture, shutter speed, ISO number, focal depth, dots per inch, etc Descriptive metadata: name of the im…

Include graphviz source code in SVG output

Dev

Ooker March 13, 2022, 7:31pm 11

related idea:

Topic		Replies	Views
Obtaining dot commands from SVG Help	4	1404	September 7, 2021
Rendering of Graphviz graphs directly in your posts is now available (again) Announcements	0	497	January 14, 2024
How to Edit a graph somewhere else in the file Help	2	425	November 15, 2022
Basic HTML embedding Help	6	1521	July 24, 2024
SVGs are broken in subtle ways (spacing issues) Help	19	668	March 21, 2025

Include graphviz source code in SVG output

Related topics