> -----Original Message-----
>
> The "box"-ing you see is a side-effect of Markdown support
> (try setting MARKDOWN_SUPPORT=NO)

Excellent.  Thank-you.  That helped.  The documentation now looks like
what I envisioned, and the comment is placed back where I originally
wanted it to go.

Interestingly, \verbatim needed to immediately follow the preceeding
paragraph with no intervening blank lines.  With blank lines between
the preceeding paragraph and the \verbatim command, the verbatim
content seemed to be ignored (missing from the generated
documentation).

---
Kevin R. Bulgrien
New Product Development Engineer

This message and/or attachments may include information subject to GD Corporate 
Policy 07-105 and is intended to be accessed only by authorized personnel of 
General Dynamics and approved service providers.  Use, storage and transmission 
are governed by General Dynamics and its policies. Contractual restrictions 
apply to third parties.  Recipients should refer to the policies or contract to 
determine proper handling.  Unauthorized review, use, disclosure or 
distribution is prohibited.  If you are not an intended recipient, please 
contact the sender and destroy all copies of the original message.

------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users

Reply via email to