Hi Kevin,
@verbatim indeed preserves the //! comments
(to allow these to appear in the output, I use them in the manual for instance).
The "box"-ing you see is a side-effect of Markdown support (try setting
MARKDOWN_SUPPORT=NO)
In general I recommend to use C-style comments for page documentation, i.e.
/*!
@page Com Windows COM
@section ComRegistry Registry Example
COM depends on registration of COM servers in the Windows Registry...
@verbatim
__uuidof(NetFwMgr) == {304CE942-6E39-40D8-943A-B913C40C9CD4}...
@endverbatim
*/
this doesn't have the issues you encountered.
Regards,
Dimitri
On Sep 6, 2013, at 23:02 , "Bulgrien, Kevin" <[email protected]>
wrote:
> Moving the \page, \section, and \verbatim outside the function body comes
> close to doing what I want BUT any text between @section and @verbatim is
> placed in its own "box" as though it was bounded by \verbatim and
> \endverbatim.
>
> //! @page Com Windows COM
> //! @section ComRegistry Registry Example
> //!
> //! COM depends on registration of COM servers in the Windows Registry...
> //!
> //! @verbatim
> //! __uuidof(NetFwMgr) == {304CE942-6E39-40D8-943A-B913C40C9CD4}...
> //!
> //! @endverbatim
>
> To restate, on the Com page, the text beginning "COM depends" appears
> inside a separate, but similar, box that \verbatim ... \endverbatim
> text appears in. It looks as though styling is being applied to a
> container rather than to a sub-container holding the verbatim text.
>
> Actually, the generated HTML source says:
>
> <h1><a class="anchor" id="ComRegistry"></a>
> Registry Example</h1>
> <pre class="fragment">COM depends...
> </pre><pre class="fragment">//! __uuidof(NetFwMgr) ==
> {304CE942-6E39-40D8-943A-B913C40C9CD4}...
> </pre> </div></div><!-- contents -->
>
> Based on the source HTML of other \page \section text, I would have
> expected more along the lines of:
>
> <h1><a class="anchor" id="ComRegistry"></a>
> Registry Example</h1>
> <p>COM depends...</p>
> <pre class="fragment">//! __uuidof(NetFwMgr) ==
> {304CE942-6E39-40D8-943A-B913C40C9CD4}...
> </pre> </div></div><!-- contents -->
>
> It has the appearance that I need to avoid use of \verbatim to avoid
> repercussions in the generated documentation. There must be a fair
> number of undocumented conditions when use of \verbatim is unwise.
>
> ---
> Kevin R. Bulgrien
> New Product Development Engineer
>
> The author is not under control of what appears below this point...
>
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/doxygen-users
