@aerique @b0rk A tool that consumes roff will (I believe) never be good. (We could change roff but no.) We want a tool that reads something better and can fall back to roff. We can't convert roff-to-gooddoc.

Texinfo was meant to be that, but (I would say) failed. A subset of HTML could replace it. (And Texinfo can compile to HTML.) You'd then want a tool that know how to find the html for a given command/name.

It's "easy" except for the xkcd 927 problem. Sorry, this is not constructive.

@b0rk Ugggggh if you find a good answer, please repost it with a bright red light. I think the biggest issue is that the roff format is too bankrupt, and we need better linking primitives, but… I might just be jaded.