<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Documentation on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/documentation/</link><description>Recent content in Documentation on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 26 Nov 2012 07:45:00 +0100</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>Github Project Wiki: separate page filename from page title</title><link>http://blog.marko-apfel.de/posts/github-project-wiki-separate-page-filename-from-page-title/</link><pubDate>Mon, 26 Nov 2012 07:45:00 +0100</pubDate><guid>http://blog.marko-apfel.de/posts/github-project-wiki-separate-page-filename-from-page-title/</guid><description>&lt;h2 id="starting-point"&gt;Starting Point&lt;/h2&gt;
&lt;p&gt;In a former version of a project wiki on Github was a separation between the page filename and page title. So we build up our Wiki in a manner, that some well defined prefixes in the filename describe the overall context of the particular page.&lt;/p&gt;</description></item><item><title>Converting Creole to HTML, PDF, DOCX, ..</title><link>http://blog.marko-apfel.de/posts/converting-creole-to-html-pdf-docx/</link><pubDate>Fri, 24 Aug 2012 13:14:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/converting-creole-to-html-pdf-docx/</guid><description>&lt;h2 id="challenge"&gt;Challenge&lt;/h2&gt;
&lt;p&gt;We documented a project on Github with the Wiki there. For most articles we used Creole as markup language. Now we have to deliver a lot of the content to our client in an usual format like PDF or DOCX.&lt;/p&gt;</description></item><item><title>StyleCop throws documentation warning SA1600 for private elements</title><link>http://blog.marko-apfel.de/posts/stylecop-throws-documentation-warning-sa1600-for-private-elements/</link><pubDate>Thu, 12 Nov 2009 06:24:00 +0100</pubDate><guid>http://blog.marko-apfel.de/posts/stylecop-throws-documentation-warning-sa1600-for-private-elements/</guid><description>&lt;p&gt;if you see the following warnings in your code:&lt;/p&gt;
&lt;p&gt;&lt;figure&gt;
 &lt;img src="http://blog.marko-apfel.de/posts/stylecop-throws-documentation-warning-sa1600-for-private-elements/StyleCop.Warning.SA1600.png" alt="Screenshot for StyleCop throws documentation warning SA1600 for private elements" loading="lazy" decoding="async"&gt;&lt;/figure&gt;&lt;/p&gt;
&lt;p&gt;You have two choices:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;deactivate the rule
but this disables this rule for all documentations – also the wanted&lt;/li&gt;
&lt;li&gt;tune the detail settings
In the settings editor you see additional options if you select the “Documentation Rules” root node&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;figure&gt;
 &lt;img src="http://blog.marko-apfel.de/posts/stylecop-throws-documentation-warning-sa1600-for-private-elements/StyleCop.Settings.01.png" alt="Screenshot for StyleCop throws documentation warning SA1600 for private elements" loading="lazy" decoding="async"&gt;&lt;/figure&gt;&lt;/p&gt;</description></item><item><title>Building a Help-TOC by hand</title><link>http://blog.marko-apfel.de/posts/building-a-help-toc-by-hand/</link><pubDate>Fri, 25 Sep 2009 09:24:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/building-a-help-toc-by-hand/</guid><description>&lt;p&gt;If you build a TOC for a CHM-help by hand it is important the for an entry the &lt;code&gt;&amp;lt;object&amp;gt;&lt;/code&gt;-tag directly follows the &lt;code&gt;&amp;lt;li&amp;gt;&lt;/code&gt;-tag.&lt;/p&gt;
&lt;p&gt;So this format works:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-xml" data-lang="xml"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nt"&gt;&amp;lt;LI&amp;gt;&amp;lt;OBJECT&lt;/span&gt; &lt;span class="na"&gt;type=&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;text/sitemap&amp;#34;&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;and this format lets show nothing:&lt;/p&gt;</description></item><item><title>Sandcastle Help File Builder: Content Editor opens without functionality</title><link>http://blog.marko-apfel.de/posts/sandcastle-help-file-builder-content-editor-opens-without-functionality/</link><pubDate>Thu, 16 Apr 2009 10:52:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/sandcastle-help-file-builder-content-editor-opens-without-functionality/</guid><description>&lt;p&gt;If the content editor of &lt;em&gt;SHFB&lt;/em&gt; opens without any functionality then the configuration file is corrupt.&lt;/p&gt;
&lt;p&gt;This is repairable through deleting the config-files under &lt;code&gt;C:\Documents and Settings\[YOUR\_USER\_ID]\Local Settings\Application Data\Eric\_Woodruff\...&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Sometimes an error occurred during opening content editor next time. In this case you must study the message. Often you have created a not XML-wellformed content file. Open your last used files with an other XML-editor and look for the place which is described in the message.
After fixing the prob you must close &lt;em&gt;SHFB&lt;/em&gt;, delete the config-file again and reopen your &lt;em&gt;SHFB&lt;/em&gt;-project.&lt;/p&gt;</description></item><item><title>HTML Help Compiler Error HHC3004</title><link>http://blog.marko-apfel.de/posts/html-help-compiler-error-hhc3004/</link><pubDate>Wed, 11 Mar 2009 11:28:00 +0100</pubDate><guid>http://blog.marko-apfel.de/posts/html-help-compiler-error-hhc3004/</guid><description>&lt;p&gt;Today i had an error by building my sandcastle documentation project.&lt;/p&gt;
&lt;p&gt;After compiling during opening the output instead my chm-file in the help viewer the internet explorer pops up with an error message that the destination could not be found.
So i took a look in the log of the compile process and there was some warnings of the following type listed:&lt;/p&gt;</description></item></channel></rss>