comment on

Actually, I've used (regular) T_EX for documentation long ago. I'm aware at how powerful a separate formatting pass, as opposed to WYSIWYG, can be. The obverse side of WYSIWYG is What You See Is All You Got.

I got a LaTeX book once, but didn't care for it.

Once upon a time, I decided I'd rather have copious documentation rather than beautiful documentation, and used Word for the project. It's just so much easier to create and edit, esp. if inserting illustrations and such.

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.


laziness, impatience, and hubris
	PerlMonks