Assuming I had one of my classes documented with the following XML doc comment:

  /// <summary>Timer for games that advances time in fixed steps</summary>
  /// <remarks>
  ///   <para>
  ///     Frame rate independent movement can be implemented in two ways: either via
  ///     time scaling or via time stepping. Time scaling will scale the movements of all
  ///     objects in a game by the amount of time passed since the last frame. Time stepping
  ///     advances time in fixed steps, multiple times if more time has passed than the length
  ///     of a single step.
  ///   </para>
  ///   <para>
  ///     This timer is intended for the stepped approach. The advantages are simpler updating,
  ///     improved stability of physics simulations (most physics engines go haywire if time
  ///     jumps by a large amount) and the guarantee for identical rounding errors for all
  ///     players in a multi-player game.
  ///   </para>
  ///   <example>
  ///     <code>
  ///       steppedTimer.Reset();
  ///       while(!this->quitRequested) {
  ///         GameTime timeStep;
  ///         while(steppedTimer.TryAdvance(timeStep)) {
  ///           UpdateAll(timeStep);
  ///         }
  ///
  ///         GameTime frameTime = steppedTimer.GetFrameTimeAndReset()
  ///         DrawAll(frameTime);
  ///
  ///         RunMessagePump();
  ///       }
  ///     </code>
  ///   </example>
  class Stepped Timer { /* ... */ };

This will end up as three lines of code, everything being concatenated together until a blank line is encountered.

Microsoft's guide for XML documentation comments (which might or might not apply when using Doxygen) has this precise constellation of tags as an example: http://msdn.microsoft.com/en-us/library/9w4cf933.aspx

It would be great if Doxygen could preserve line breaks the same way other XML doc comment processors (eg. Visual Studio, Sandcastle) do.

Ideally, it would scan for the least indented line within the code tags and adjust indentation according to that, then putting everything in a <pre /> section for HTML output.