Why are "plugins" like unflatten, gvpack or gvpr not in the official documentation?

They are documented elsewhere, but I don’t see where they are mentioned in https://graphviz.org/doc/. Why is that?



if you search here: Documentation | Graphviz you will find these programs documented.

I see. Why are they all in PDF?

I don’t know why, but why not?
What would you prefer and why?

My 2c: It would be nice to make these PDF manuals available as HTML so that they’re searchable within the site, so we can link to headings, and so they’re consistent with the rest of the site, and so they’re more easily editable.

1 Like

I would like us to make them available as HTML one day. The only reason it hasn’t happened yet is the usual: lack of volunteer time.

1 Like

AFAIK the PDFs are generated from man page sources. So we could also compile the man pages to HTML if useful.


is there a guide on how to help?

This is a great question. We need to write a contributor guide that explains steps for making contributions to code or the website beyond “edit this page”.

1 Like

The use of manpages and PDF dates the developers. As @smattr notes, the PDF are just generated from the manages. There seem to be good tools to convert manpages to HTML, so it would just be a matter of tweaking the makefiles. But then you get into the issue raised by @mark as to finding people with the time to do the editing.

On a related note, the info in manpages is reasonably sufficient for simple filters like unflatten and gvpack, but gvpr is complex enough that it could use a real manual/tutorial like the ones under User’s Guides.