Thanks for the examples! Actually I managed to get my own custom setup done in about an hour after reading through the docs and playing around a bit. Now though I need to dig in an learn more about the xsl stylesheets so that they correctly transform the docbook html form elements into html form elements. That is proving to be a bit more of a learning curve.
> * If we had plans to really support extended DocBook DTDs we would > choose MathML, SVG and EBNF and certainly not HTML Forms, because we > simply do not understand the use of this extended DTD. > > * Next version of XXE (V2.8p1) will fully support HTML tables in DocBook > 4.3 (though we don't understand the purpose of adding HTML tables to an > already *extremely* complex DTD). But currently, this is not the case: > we don't yet support HTML tables in DocBook. > Well from a practical perspective, and maybe from just not knowing what I don't know.. I can see a use for html forms in docbook. We are using docbook for all of our documentation, and we need form elements in the html output. I'm guessing from your statement that there is a more correct way to obtain that result? The other method I found that works is some xsl code that sticks arbitrary bits of html into the output using processing instructions. Chris >
