Bug 792122 - XHTML pages are broken several ways

The Markdown processing was done after the normal tag processing and splitting the comment in brief, doc, inline. This resulted in that sectioning parts (i.e. e.g. ==== conversion to <h1> ) remained in the brief description whilst similar constructs with HTML commands landed in the doc (details) description. By performing the markdown on the entire comment block this problem has been overcome.

commentscan.l
- change moment of calling markdown processing
- skip start spaces and subsequent empty lines in markdown processed code
- small debug correction

markdown.cpp
- don't convert the dashes in <!--  and --> (HTML type comment)
- small debug correction

054 test
- update of example for compatibility and adding part about none code result.

doxygen.cpp
- small textual comment correction

1 files changed, 91 insertions, 1 deletions

diff --git a/testing/054/054__parblock_8cpp.xml b/testing/054/054__parblock_8cpp.xml
index ae6e462..5567908 100644
--- a/testing/054/054__parblock_8cpp.xml
+++ b/testing/054/054__parblock_8cpp.xml
@@ -80,6 +80,96 @@
                 <parameterdescription>
                   <para>
                     <parblock>
+                      <para>First paragraph of the param description.</para>
+                      <para>Second paragraph of the param description. </para>
+                    </parblock>
+                  </para>
+                </parameterdescription>
+              </parameteritem>
+            </parameterlist>
+          </para>
+        </detaileddescription>
+        <inbodydescription>
+        </inbodydescription>
+        <location file="054_parblock.cpp" line="33" column="1"/>
+      </memberdef>
+      <memberdef kind="function" id="054__parblock_8cpp_1a5cded03ec9e6fd626da35ab05f624f39" prot="public" static="no" const="no" explicit="no" inline="no" virt="non-virtual">
+        <type>void</type>
+        <definition>void function_2</definition>
+        <argsstring>(int client, int *resource, int parblock, int *test, int p)</argsstring>
+        <name>function_2</name>
+        <param>
+          <type>int</type>
+          <declname>client</declname>
+        </param>
+        <param>
+          <type>int *</type>
+          <declname>resource</declname>
+        </param>
+        <param>
+          <type>int</type>
+          <declname>parblock</declname>
+        </param>
+        <param>
+          <type>int *</type>
+          <declname>test</declname>
+        </param>
+        <param>
+          <type>int</type>
+          <declname>p</declname>
+        </param>
+        <briefdescription>
+        </briefdescription>
+        <detaileddescription>
+          <para>call by target-specific code to manage resources required by the client.</para>
+          <para>
+            <parameterlist kind="param">
+              <parameteritem>
+                <parameternamelist>
+                  <parametername direction="in">client</parametername>
+                </parameternamelist>
+                <parameterdescription>
+                  <para>ID of client requesting resource. </para>
+                </parameterdescription>
+              </parameteritem>
+              <parameteritem>
+                <parameternamelist>
+                  <parametername direction="out">resource</parametername>
+                </parameternamelist>
+                <parameterdescription>
+                  <para>Requested resource </para>
+                </parameterdescription>
+              </parameteritem>
+              <parameteritem>
+                <parameternamelist>
+                  <parametername direction="in">parblock</parametername>
+                </parameternamelist>
+                <parameterdescription>
+                  <para>
+                    <parblock>
+                      <para>This is a test for the @parblock command.</para>
+                      <para>A list if values for the parblock param:<itemizedlist><listitem><para>Item 1. This is short one-line description.</para></listitem><listitem><para>Item 2. This is a long bullet item; sometimes they wrap on multiple lines like this one.</para></listitem></itemizedlist>
+</para>
+                      <para>This is the second paragraph description for the @parblock parameter. Always end the text inside the @parblock command with an @endparblock command. </para>
+                    </parblock>
+                  </para>
+                </parameterdescription>
+              </parameteritem>
+              <parameteritem>
+                <parameternamelist>
+                  <parametername direction="out">test</parametername>
+                </parameternamelist>
+                <parameterdescription>
+                  <para>This is a test parameter for this function to see if it is included in the parameter table </para>
+                </parameterdescription>
+              </parameteritem>
+              <parameteritem>
+                <parameternamelist>
+                  <parametername direction="in">p</parametername>
+                </parameternamelist>
+                <parameterdescription>
+                  <para>
+                    <parblock>
                       <para>First paragraph of the param description. <verbatim>                  Second paragraph of the param description.
 </verbatim> </para>
                     </parblock>
@@ -91,7 +181,7 @@
         </detaileddescription>
         <inbodydescription>
         </inbodydescription>
-        <location file="054_parblock.cpp" line="32" column="1"/>
+        <location file="054_parblock.cpp" line="60" column="1"/>
       </memberdef>
     </sectiondef>
     <briefdescription>