comment on

DocBook is not what I'm looking for. It uses SGML markup, and that's just as "bad", if not moreso, than writing in HTML. I don't see any provisions for generating the master tables and index and such, too.

However, I'm wondering if a two-stage approach might work. I can write a simple Perl tool to take an easily-typed markup and convert to formal XML, and that's all it does. I can bang on that to extend when needed, as I need more features. Anything that doesn't fit the mold can be written directly in XML.

Then, another tool reads the XML document and produces the set of HTML pages, including the index and stuff.

—John

In reply to Re: Re: HTML documentation system - design and planning by John M. Dlugosz
in thread HTML documentation system - design and planning by John M. Dlugosz

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks