Hi Norman, Some help conceptualising the best way to structure the FVWM documentation would be most appreciated.
My fundamental problem at the moment is that I can't work out how to generate manpage and _decent_ HTML output from the same XML source. I can generate a refentry document that outputs an appropriate man page. However, I'm having difficulty getting the refentry document to output in a HTML format that I'm happy with. Obviously "xsltproc html/docbook.xsl refentry.xsl" will output the document in HTML format, but it doesn't make full use of the features of HTML. There are 2 requirements that I'm particularly keen for the HTML document to have: 1. It can be split up into multiple pages. ie. chunked. Ideally I could have a HTML page that describes, say, the FVWM "Read" command, & another HTML page that descibes the FVWM "PipeRead" command. Also, I could have a HTML page for "Shell Commands" & it would have the contents of both the "Read" & "PipeRead" commands. 2. I'd like the HTML output to be massively cross-referenced. So, eg, every occurance of the FVWM "Read" command would be a link to the HTML page that describes the "Read" syntax. Alternatively, I can generate an article or book document that has all the HTML characteristics that I desire, but then I don't seem to be able to generate a man page from it. "xsltproc manpages/docbook.xsl article.xml" gives me an "No refentry elements!" error message. I'd be happy to have lots of small individual XML files describing, say, the syntax of the FVWM "Read" command & then XInclude'ing them into 2 separate documents: 1) a refentry doc for manpage output & 2) an article for HTML output. I've been experimenting with this in fact, but at some level, they differ in which elements they expect. ie. An article would be expecting <section> in read.xml whilst a refentry expects <refsect1>. Any help/pointers muchly appreciated. Scott. :)
