title: Combine OpenOffice/Libreoffice with Doxygen results for code documentation?
body: <h3>Problem</h3>
  <p>We currently want to migrate from manually to automated C-Code documentation, by re-using our previous OpenOffice results.</p>
  <h3>Background</h3>
  <p>In the last 10 years we manually generated a lot of OpenOffice (*.odt) files, including prosa like architecture, 'how it works', graphics and detailed API description. So we had a single document for each product (exported as *.pdf for our customers).</p>
  <p>We now changed our C-Code to use Doxygen compatible formats and keywords, resulting in well formatted documentation (HTML+CHM, no PDFs until now). But this of course includes detailed API only. The aim still is to generate a single result file including prosa &amp; graphics.</p>
  <p>Thinking about to combine the OpenOffice &amp; Doxygen result, we are wondering on how and in which direction to proceed:</p>
  <ol>
  <li>Convert *.odt =&gt; *.html and reference these in C-Code for Doxygen</li>
  <li>Convert *.odt =&gt; *.txt/png and reference these in C-Code for Doxygen</li>
  <li>Convert *.odt =&gt; *.html as a base and reference Doxygen-HTML-Results in these files</li>
  <li>Another common format available, to merge both results(?)</li>
  </ol>
  <h3>Question</h3>
  <p>What might be the most efficient way, to migrate from our old document style to an equivalent single documentation file - including Doxygen results?</p>