Auto-Update wiki pages

The-VDR-Plugin-System.md

@@ -1837,7 +1837,7 @@ osd->DrawText(x, y, s, Theme.Color(clrButtonRedFg), Theme.Color(clrButtonRedB
 
 By default this will use the colors that have been defined in the respective
 <tt>THEME_CLR()</tt> line, but may be overwritten through user supplied theme
-files (see <tt>man vdr(5)</tt> for information about the format of a theme file).
+files (see <tt>man [vdr(5)](VDR-file-formats-and-conventions)</tt> for information about the format of a theme file).
 
 <hr><h2>Devices</h2>
 

VDR-command-reference.md

@@ -126,7 +126,7 @@
 <dd><p>Activate the watchdog timer with a timeout of <em>sec</em> seconds. A value of <strong>0</strong> (default) disables the watchdog.</p>
 </dd>
 </dl>
-<p>If started without any options, vdr tries to read command line options from files named '*.conf' in the directory /etc/vdr/conf.d. Files are read in alphabetical order. See vdr(5) for details.</p>
+<p>If started without any options, vdr tries to read command line options from files named '*.conf' in the directory /etc/vdr/conf.d. Files are read in alphabetical order. See [vdr(5)](VDR-file-formats-and-conventions) for details.</p>
 <h1>SIGNALS</h1>
 <dl>
 <dt><h3><strong>SIGINT, SIGTERM</strong></h3></dt>
@@ -197,7 +197,7 @@
 </dd>
 </dl>
 <h1>SEE ALSO</h1>
-<p><strong>vdr</strong>(5),<strong>svdrpsend</strong>(1)</p>
+<p>[vdr(5)](VDR-file-formats-and-conventions),[svdrpsend(1)](svdrpsend-command-reference)</p>
 <h1>AUTHOR</h1>
 <p>Written by Klaus Schmidinger, with contributions from many others. See the file <em>CONTRIBUTORS</em> in the <strong>vdr</strong> source distribution.</p>
 <h1>REPORTING BUGS</h1>

VDR-file-formats-and-conventions.md

@@ -846,7 +846,7 @@ The '?' at the end of the "Check for new mail?" entry will prompt the user wheth
 --longarg=123</code></pre>
 <p>Any lines that begin with '#' as the first non-whitespace character are considered comments and are ignored. A command line option file consists of one or more sections, indicated by '[name]', where 'name' is either the fixed word 'vdr' (if this section contains options for the main VDR program) or the name of the plugin this section applies to. Each option must be written on a separate line, including the leading '-' (for a short option) or '--' (for a long option). If the option has additional arguments, they have to be written on the same line as the option itself, separated from the option with a blank (short option) or equal sign (long option).</p>
 <h1>SEE ALSO</h1>
-<p><strong>vdr</strong>(1)</p>
+<p>[vdr(1)](VDR-command-reference)</p>
 <h1>AUTHOR</h1>
 <p>Written by Klaus Schmidinger.</p>
 <h1>REPORTING BUGS</h1>

VDR-manual.md

@@ -1311,20 +1311,20 @@ timer, making "TITLE - EPISODE" and "TITLE: EPISODE" the same.
 ## Executing system commands
 
   The "VDR" menu option "Commands" allows you to execute any system commands
-  defined in the configuration file 'commands.conf' (see vdr(5) for details).
+  defined in the configuration file '[commands.conf](VDR-file-formats-and-conventions#commands)' (see [vdr(5)](VDR-file-formats-and-conventions) for details).
   The "Commands" option will only be present in the "VDR" menu if a valid
-  'commands.conf' file containing at least one command definition has been
+  '[commands.conf](VDR-file-formats-and-conventions#commands)' file containing at least one command definition has been
   found at program start.
 
   This feature can be used to do virtually anything, like checking for new
   mail, displaying the CPU temperature - you name it! All you need to do is
-  enter the necessary command definition into 'commands.conf' and implement
+  enter the necessary command definition into '[commands.conf](VDR-file-formats-and-conventions#commands)' and implement
   the actual command that will be called. Such a command can typically be a
   shell script or a Perl program. Anything that command writes to stdout will
   be displayed on a result screen after executing the command. This screen will
   use a 'fixed' font so that you can generate formatted output. In order to
   avoid error messages going to stderr, command definitions should redirect
-  stderr to stdout (see vdr(5)).
+  stderr to stdout (see [vdr(5)](VDR-file-formats-and-conventions)).
 
     WARNING: THE COMMANDS DEFINED IN 'commands.conf' WILL BE EXECUTED UNDER THE
     =======  SAME USER ID THAT VDR IS RUNNING WITH. BE VERY CAREFUL WHEN

svdrpsend-command-reference.md

@@ -26,5 +26,5 @@
 <p>Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 any later version published by the Free Software Foundation.</p>
 <p>On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.</p>
 <h1>SEE ALSO</h1>
-<p>vdr(1), vdr(5)</p>
+<p>[vdr(1)](VDR-command-reference), [vdr(5)](VDR-file-formats-and-conventions)</p>