diff --git a/doc/geany.html b/doc/geany.html
index c7154f2..9955307 100644
--- a/doc/geany.html
+++ b/doc/geany.html
@@ -3,10 +3,10 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
+<meta name="generator" content="Docutils 0.7: http://docutils.sourceforge.net/" />
 <title>Geany</title>
 <meta name="authors" content="Enrico Tr��ger  Nick Treleaven  Frank Lanitz" />
-<meta name="date" content="2010-10-26" />
+<meta name="date" content="$Date$" />
 <style type="text/css">
 
 /*
@@ -139,7 +139,7 @@ Stylesheet for Geany's documentation based on a version of John Gabriele.
 <br />Nick Treleaven
 <br />Frank Lanitz</td></tr>
 <tr><th class="docinfo-name">Date:</th>
-<td>2010-10-26</td></tr>
+<td>$Date$</td></tr>
 <tr><th class="docinfo-name">Version:</th>
 <td>0.20</td></tr>
 </tbody>
@@ -149,352 +149,353 @@ Stylesheet for Geany's documentation based on a version of John Gabriele.
 License as published by the Free Software Foundation; either version 2
 of the License, or (at your option) any later version. A copy of this
 license can be found in the file COPYING included with the source code
-of this program, and also in the chapter <a class="reference" href="#gnu-general-public-license">GNU General Public License</a>.</p>
-<div class="contents topic">
-<p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
+of this program, and also in the chapter <a class="reference internal" href="#gnu-general-public-license">GNU General Public License</a>.</p>
+<div class="contents topic" id="contents">
+<p class="topic-title first">Contents</p>
 <ul class="simple">
-<li><a class="reference" href="#introduction" id="id8" name="id8">Introduction</a><ul>
-<li><a class="reference" href="#about-geany" id="id9" name="id9">About Geany</a></li>
-<li><a class="reference" href="#where-to-get-it" id="id10" name="id10">Where to get it</a></li>
-<li><a class="reference" href="#license" id="id11" name="id11">License</a></li>
-<li><a class="reference" href="#about-this-document" id="id12" name="id12">About this document</a></li>
+<li><a class="reference internal" href="#introduction" id="id8">Introduction</a><ul>
+<li><a class="reference internal" href="#about-geany" id="id9">About Geany</a></li>
+<li><a class="reference internal" href="#where-to-get-it" id="id10">Where to get it</a></li>
+<li><a class="reference internal" href="#license" id="id11">License</a></li>
+<li><a class="reference internal" href="#about-this-document" id="id12">About this document</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#installation" id="id13" name="id13">Installation</a><ul>
-<li><a class="reference" href="#requirements" id="id14" name="id14">Requirements</a></li>
-<li><a class="reference" href="#binary-packages" id="id15" name="id15">Binary packages</a></li>
-<li><a class="reference" href="#source-compilation" id="id16" name="id16">Source compilation</a><ul>
-<li><a class="reference" href="#autotools-based-build-system" id="id17" name="id17">Autotools based build system</a></li>
-<li><a class="reference" href="#waf-based-build-system" id="id18" name="id18">Waf based build system</a><ul>
-<li><a class="reference" href="#waf-cache" id="id19" name="id19">Waf Cache</a><ul>
-<li><a class="reference" href="#cleaning-the-cache" id="id20" name="id20">Cleaning the Cache</a></li>
+<li><a class="reference internal" href="#installation" id="id13">Installation</a><ul>
+<li><a class="reference internal" href="#requirements" id="id14">Requirements</a></li>
+<li><a class="reference internal" href="#binary-packages" id="id15">Binary packages</a></li>
+<li><a class="reference internal" href="#source-compilation" id="id16">Source compilation</a><ul>
+<li><a class="reference internal" href="#autotools-based-build-system" id="id17">Autotools based build system</a></li>
+<li><a class="reference internal" href="#waf-based-build-system" id="id18">Waf based build system</a><ul>
+<li><a class="reference internal" href="#waf-cache" id="id19">Waf Cache</a><ul>
+<li><a class="reference internal" href="#cleaning-the-cache" id="id20">Cleaning the Cache</a></li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a class="reference" href="#custom-installation" id="id21" name="id21">Custom installation</a></li>
-<li><a class="reference" href="#dynamic-linking-loader-support-and-vte" id="id22" name="id22">Dynamic linking loader support and VTE</a></li>
-<li><a class="reference" href="#build-problems" id="id23" name="id23">Build problems</a></li>
+<li><a class="reference internal" href="#custom-installation" id="id21">Custom installation</a></li>
+<li><a class="reference internal" href="#dynamic-linking-loader-support-and-vte" id="id22">Dynamic linking loader support and VTE</a></li>
+<li><a class="reference internal" href="#build-problems" id="id23">Build problems</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#installation-prefix" id="id24" name="id24">Installation prefix</a></li>
+<li><a class="reference internal" href="#installation-prefix" id="id24">Installation prefix</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#usage" id="id25" name="id25">Usage</a><ul>
-<li><a class="reference" href="#getting-started" id="id26" name="id26">Getting started</a></li>
-<li><a class="reference" href="#the-geany-workspace" id="id27" name="id27">The Geany workspace</a></li>
-<li><a class="reference" href="#command-line-options" id="id28" name="id28">Command line options</a></li>
-<li><a class="reference" href="#general" id="id29" name="id29">General</a><ul>
-<li><a class="reference" href="#startup" id="id30" name="id30">Startup</a></li>
-<li><a class="reference" href="#opening-files-from-the-command-line-in-a-running-instance" id="id31" name="id31">Opening files from the command-line in a running instance</a></li>
-<li><a class="reference" href="#virtual-terminal-emulator-widget-vte" id="id32" name="id32">Virtual terminal emulator widget (VTE)</a></li>
-<li><a class="reference" href="#defining-own-widget-styles-using-gtkrc-2-0" id="id33" name="id33">Defining own widget styles using .gtkrc-2.0</a></li>
+<li><a class="reference internal" href="#usage" id="id25">Usage</a><ul>
+<li><a class="reference internal" href="#getting-started" id="id26">Getting started</a></li>
+<li><a class="reference internal" href="#the-geany-workspace" id="id27">The Geany workspace</a></li>
+<li><a class="reference internal" href="#command-line-options" id="id28">Command line options</a></li>
+<li><a class="reference internal" href="#general" id="id29">General</a><ul>
+<li><a class="reference internal" href="#startup" id="id30">Startup</a></li>
+<li><a class="reference internal" href="#opening-files-from-the-command-line-in-a-running-instance" id="id31">Opening files from the command-line in a running instance</a></li>
+<li><a class="reference internal" href="#virtual-terminal-emulator-widget-vte" id="id32">Virtual terminal emulator widget (VTE)</a></li>
+<li><a class="reference internal" href="#defining-own-widget-styles-using-gtkrc-2-0" id="id33">Defining own widget styles using .gtkrc-2.0</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#documents" id="id34" name="id34">Documents</a><ul>
-<li><a class="reference" href="#switching-between-documents" id="id35" name="id35">Switching between documents</a></li>
+<li><a class="reference internal" href="#documents" id="id34">Documents</a><ul>
+<li><a class="reference internal" href="#switching-between-documents" id="id35">Switching between documents</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#character-sets-and-unicode-byte-order-mark-bom" id="id36" name="id36">Character sets and Unicode Byte-Order-Mark (BOM)</a><ul>
-<li><a class="reference" href="#using-character-sets" id="id37" name="id37">Using character sets</a></li>
-<li><a class="reference" href="#in-file-encoding-specification" id="id38" name="id38">In-file encoding specification</a></li>
-<li><a class="reference" href="#special-encoding-none" id="id39" name="id39">Special encoding &quot;None&quot;</a></li>
-<li><a class="reference" href="#unicode-byte-order-mark-bom" id="id40" name="id40">Unicode Byte-Order-Mark (BOM)</a></li>
+<li><a class="reference internal" href="#character-sets-and-unicode-byte-order-mark-bom" id="id36">Character sets and Unicode Byte-Order-Mark (BOM)</a><ul>
+<li><a class="reference internal" href="#using-character-sets" id="id37">Using character sets</a></li>
+<li><a class="reference internal" href="#in-file-encoding-specification" id="id38">In-file encoding specification</a></li>
+<li><a class="reference internal" href="#special-encoding-none" id="id39">Special encoding &quot;None&quot;</a></li>
+<li><a class="reference internal" href="#unicode-byte-order-mark-bom" id="id40">Unicode Byte-Order-Mark (BOM)</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#editing" id="id41" name="id41">Editing</a><ul>
-<li><a class="reference" href="#folding" id="id42" name="id42">Folding</a></li>
-<li><a class="reference" href="#column-mode-editing-rectangular-selections" id="id43" name="id43">Column mode editing (rectangular selections)</a></li>
-<li><a class="reference" href="#drag-and-drop-of-text" id="id44" name="id44">Drag and drop of text</a></li>
-<li><a class="reference" href="#indentation" id="id45" name="id45">Indentation</a></li>
-<li><a class="reference" href="#auto-indentation" id="id46" name="id46">Auto-indentation</a></li>
-<li><a class="reference" href="#bookmarks" id="id47" name="id47">Bookmarks</a></li>
-<li><a class="reference" href="#code-navigation-history" id="id48" name="id48">Code navigation history</a></li>
-<li><a class="reference" href="#sending-text-through-custom-commands" id="id49" name="id49">Sending text through custom commands</a></li>
-<li><a class="reference" href="#context-actions" id="id50" name="id50">Context actions</a></li>
-<li><a class="reference" href="#autocompletion" id="id51" name="id51">Autocompletion</a><ul>
-<li><a class="reference" href="#word-part-completion" id="id52" name="id52">Word part completion</a></li>
-<li><a class="reference" href="#scope-autocompletion" id="id53" name="id53">Scope autocompletion</a></li>
+<li><a class="reference internal" href="#editing" id="id41">Editing</a><ul>
+<li><a class="reference internal" href="#folding" id="id42">Folding</a></li>
+<li><a class="reference internal" href="#column-mode-editing-rectangular-selections" id="id43">Column mode editing (rectangular selections)</a></li>
+<li><a class="reference internal" href="#drag-and-drop-of-text" id="id44">Drag and drop of text</a></li>
+<li><a class="reference internal" href="#indentation" id="id45">Indentation</a></li>
+<li><a class="reference internal" href="#auto-indentation" id="id46">Auto-indentation</a></li>
+<li><a class="reference internal" href="#bookmarks" id="id47">Bookmarks</a></li>
+<li><a class="reference internal" href="#code-navigation-history" id="id48">Code navigation history</a></li>
+<li><a class="reference internal" href="#sending-text-through-custom-commands" id="id49">Sending text through custom commands</a></li>
+<li><a class="reference internal" href="#context-actions" id="id50">Context actions</a></li>
+<li><a class="reference internal" href="#autocompletion" id="id51">Autocompletion</a><ul>
+<li><a class="reference internal" href="#word-part-completion" id="id52">Word part completion</a></li>
+<li><a class="reference internal" href="#scope-autocompletion" id="id53">Scope autocompletion</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#user-definable-snippets" id="id54" name="id54">User-definable snippets</a><ul>
-<li><a class="reference" href="#snippet-keybindings" id="id55" name="id55">Snippet keybindings</a></li>
+<li><a class="reference internal" href="#user-definable-snippets" id="id54">User-definable snippets</a><ul>
+<li><a class="reference internal" href="#snippet-keybindings" id="id55">Snippet keybindings</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#inserting-unicode-characters" id="id56" name="id56">Inserting Unicode characters</a></li>
+<li><a class="reference internal" href="#inserting-unicode-characters" id="id56">Inserting Unicode characters</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#search-replace-and-go-to" id="id57" name="id57">Search, replace and go to</a><ul>
-<li><a class="reference" href="#toolbar-entries" id="id58" name="id58">Toolbar entries</a><ul>
-<li><a class="reference" href="#search-bar" id="id59" name="id59">Search bar</a></li>
+<li><a class="reference internal" href="#search-replace-and-go-to" id="id57">Search, replace and go to</a><ul>
+<li><a class="reference internal" href="#toolbar-entries" id="id58">Toolbar entries</a><ul>
+<li><a class="reference internal" href="#search-bar" id="id59">Search bar</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#find" id="id60" name="id60">Find</a><ul>
-<li><a class="reference" href="#matching-options" id="id61" name="id61">Matching options</a></li>
-<li><a class="reference" href="#find-all" id="id62" name="id62">Find all</a></li>
-<li><a class="reference" href="#change-font-in-search-dialog-text-fields" id="id63" name="id63">Change font in search dialog text fields</a></li>
+<li><a class="reference internal" href="#find" id="id60">Find</a><ul>
+<li><a class="reference internal" href="#matching-options" id="id61">Matching options</a></li>
+<li><a class="reference internal" href="#find-all" id="id62">Find all</a></li>
+<li><a class="reference internal" href="#change-font-in-search-dialog-text-fields" id="id63">Change font in search dialog text fields</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#find-selection" id="id64" name="id64">Find selection</a></li>
-<li><a class="reference" href="#find-usage" id="id65" name="id65">Find usage</a></li>
-<li><a class="reference" href="#find-in-files" id="id66" name="id66">Find in files</a><ul>
-<li><a class="reference" href="#filtering-out-version-control-files" id="id67" name="id67">Filtering out version control files</a></li>
+<li><a class="reference internal" href="#find-selection" id="id64">Find selection</a></li>
+<li><a class="reference internal" href="#find-usage" id="id65">Find usage</a></li>
+<li><a class="reference internal" href="#find-in-files" id="id66">Find in files</a><ul>
+<li><a class="reference internal" href="#filtering-out-version-control-files" id="id67">Filtering out version control files</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#replace" id="id68" name="id68">Replace</a><ul>
-<li><a class="reference" href="#replace-all" id="id69" name="id69">Replace all</a></li>
+<li><a class="reference internal" href="#replace" id="id68">Replace</a><ul>
+<li><a class="reference internal" href="#replace-all" id="id69">Replace all</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#go-to-tag-definition" id="id70" name="id70">Go to tag definition</a></li>
-<li><a class="reference" href="#go-to-tag-declaration" id="id71" name="id71">Go to tag declaration</a></li>
-<li><a class="reference" href="#go-to-line" id="id72" name="id72">Go to line</a></li>
-<li><a class="reference" href="#regular-expressions" id="id73" name="id73">Regular expressions</a></li>
+<li><a class="reference internal" href="#go-to-tag-definition" id="id70">Go to tag definition</a></li>
+<li><a class="reference internal" href="#go-to-tag-declaration" id="id71">Go to tag declaration</a></li>
+<li><a class="reference internal" href="#go-to-line" id="id72">Go to line</a></li>
+<li><a class="reference internal" href="#regular-expressions" id="id73">Regular expressions</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#tags" id="id74" name="id74">Tags</a><ul>
-<li><a class="reference" href="#workspace-tags" id="id75" name="id75">Workspace tags</a></li>
-<li><a class="reference" href="#global-tags" id="id76" name="id76">Global tags</a><ul>
-<li><a class="reference" href="#default-global-tags-files" id="id77" name="id77">Default global tags files</a></li>
-<li><a class="reference" href="#global-tags-file-format" id="id78" name="id78">Global tags file format</a></li>
-<li><a class="reference" href="#generating-a-global-tags-file" id="id79" name="id79">Generating a global tags file</a></li>
+<li><a class="reference internal" href="#tags" id="id74">Tags</a><ul>
+<li><a class="reference internal" href="#workspace-tags" id="id75">Workspace tags</a></li>
+<li><a class="reference internal" href="#global-tags" id="id76">Global tags</a><ul>
+<li><a class="reference internal" href="#default-global-tags-files" id="id77">Default global tags files</a></li>
+<li><a class="reference internal" href="#global-tags-file-format" id="id78">Global tags file format</a></li>
+<li><a class="reference internal" href="#generating-a-global-tags-file" id="id79">Generating a global tags file</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#ignore-tags" id="id80" name="id80">Ignore tags</a></li>
+<li><a class="reference internal" href="#ignore-tags" id="id80">Ignore tags</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#preferences" id="id81" name="id81">Preferences</a><ul>
-<li><a class="reference" href="#general-startup-preferences" id="id82" name="id82">General Startup preferences</a><ul>
-<li><a class="reference" href="#id1" id="id83" name="id83">Startup</a></li>
-<li><a class="reference" href="#shutdown" id="id84" name="id84">Shutdown</a></li>
-<li><a class="reference" href="#paths" id="id85" name="id85">Paths</a></li>
+<li><a class="reference internal" href="#preferences" id="id81">Preferences</a><ul>
+<li><a class="reference internal" href="#general-startup-preferences" id="id82">General Startup preferences</a><ul>
+<li><a class="reference internal" href="#id1" id="id83">Startup</a></li>
+<li><a class="reference internal" href="#shutdown" id="id84">Shutdown</a></li>
+<li><a class="reference internal" href="#paths" id="id85">Paths</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#general-miscellaneous-preferences" id="id86" name="id86">General Miscellaneous preferences</a><ul>
-<li><a class="reference" href="#miscellaneous" id="id87" name="id87">Miscellaneous</a></li>
-<li><a class="reference" href="#search" id="id88" name="id88">Search</a></li>
-<li><a class="reference" href="#projects" id="id89" name="id89">Projects</a></li>
+<li><a class="reference internal" href="#general-miscellaneous-preferences" id="id86">General Miscellaneous preferences</a><ul>
+<li><a class="reference internal" href="#miscellaneous" id="id87">Miscellaneous</a></li>
+<li><a class="reference internal" href="#search" id="id88">Search</a></li>
+<li><a class="reference internal" href="#projects" id="id89">Projects</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#interface-preferences" id="id90" name="id90">Interface preferences</a><ul>
-<li><a class="reference" href="#sidebar" id="id91" name="id91">Sidebar</a></li>
-<li><a class="reference" href="#fonts" id="id92" name="id92">Fonts</a></li>
-<li><a class="reference" href="#editor-tabs" id="id93" name="id93">Editor tabs</a></li>
-<li><a class="reference" href="#tab-positions" id="id94" name="id94">Tab positions</a></li>
-<li><a class="reference" href="#id2" id="id95" name="id95">Miscellaneous</a></li>
+<li><a class="reference internal" href="#interface-preferences" id="id90">Interface preferences</a><ul>
+<li><a class="reference internal" href="#sidebar" id="id91">Sidebar</a></li>
+<li><a class="reference internal" href="#fonts" id="id92">Fonts</a></li>
+<li><a class="reference internal" href="#editor-tabs" id="id93">Editor tabs</a></li>
+<li><a class="reference internal" href="#tab-positions" id="id94">Tab positions</a></li>
+<li><a class="reference internal" href="#id2" id="id95">Miscellaneous</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#toolbar-preferences" id="id96" name="id96">Toolbar preferences</a><ul>
-<li><a class="reference" href="#toolbar" id="id97" name="id97">Toolbar</a></li>
-<li><a class="reference" href="#appearance" id="id98" name="id98">Appearance</a></li>
+<li><a class="reference internal" href="#toolbar-preferences" id="id96">Toolbar preferences</a><ul>
+<li><a class="reference internal" href="#toolbar" id="id97">Toolbar</a></li>
+<li><a class="reference internal" href="#appearance" id="id98">Appearance</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#editor-features-preferences" id="id99" name="id99">Editor Features preferences</a><ul>
-<li><a class="reference" href="#features" id="id100" name="id100">Features</a></li>
+<li><a class="reference internal" href="#editor-features-preferences" id="id99">Editor Features preferences</a><ul>
+<li><a class="reference internal" href="#features" id="id100">Features</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#editor-indentation-preferences" id="id101" name="id101">Editor Indentation preferences</a><ul>
-<li><a class="reference" href="#indentation-group" id="id102" name="id102">Indentation group</a></li>
+<li><a class="reference internal" href="#editor-indentation-preferences" id="id101">Editor Indentation preferences</a><ul>
+<li><a class="reference internal" href="#indentation-group" id="id102">Indentation group</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#editor-completions-preferences" id="id103" name="id103">Editor Completions preferences</a><ul>
-<li><a class="reference" href="#completions" id="id104" name="id104">Completions</a></li>
-<li><a class="reference" href="#auto-close-quotes-and-brackets" id="id105" name="id105">Auto-close quotes and brackets</a></li>
+<li><a class="reference internal" href="#editor-completions-preferences" id="id103">Editor Completions preferences</a><ul>
+<li><a class="reference internal" href="#completions" id="id104">Completions</a></li>
+<li><a class="reference internal" href="#auto-close-quotes-and-brackets" id="id105">Auto-close quotes and brackets</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#editor-display-preferences" id="id106" name="id106">Editor Display preferences</a><ul>
-<li><a class="reference" href="#display" id="id107" name="id107">Display</a></li>
-<li><a class="reference" href="#long-line-marker" id="id108" name="id108">Long line marker</a></li>
-<li><a class="reference" href="#virtual-spaces" id="id109" name="id109">Virtual spaces</a></li>
+<li><a class="reference internal" href="#editor-display-preferences" id="id106">Editor Display preferences</a><ul>
+<li><a class="reference internal" href="#display" id="id107">Display</a></li>
+<li><a class="reference internal" href="#long-line-marker" id="id108">Long line marker</a></li>
+<li><a class="reference internal" href="#virtual-spaces" id="id109">Virtual spaces</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#files-preferences" id="id110" name="id110">Files preferences</a><ul>
-<li><a class="reference" href="#new-files" id="id111" name="id111">New files</a></li>
-<li><a class="reference" href="#saving-files" id="id112" name="id112">Saving files</a></li>
-<li><a class="reference" href="#id3" id="id113" name="id113">Miscellaneous</a></li>
+<li><a class="reference internal" href="#files-preferences" id="id110">Files preferences</a><ul>
+<li><a class="reference internal" href="#new-files" id="id111">New files</a></li>
+<li><a class="reference internal" href="#saving-files" id="id112">Saving files</a></li>
+<li><a class="reference internal" href="#id3" id="id113">Miscellaneous</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#tools-preferences" id="id114" name="id114">Tools preferences</a><ul>
-<li><a class="reference" href="#tool-paths" id="id115" name="id115">Tool paths</a></li>
-<li><a class="reference" href="#commands" id="id116" name="id116">Commands</a></li>
+<li><a class="reference internal" href="#tools-preferences" id="id114">Tools preferences</a><ul>
+<li><a class="reference internal" href="#tool-paths" id="id115">Tool paths</a></li>
+<li><a class="reference internal" href="#commands" id="id116">Commands</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#template-preferences" id="id117" name="id117">Template preferences</a><ul>
-<li><a class="reference" href="#template-data" id="id118" name="id118">Template data</a></li>
+<li><a class="reference internal" href="#template-preferences" id="id117">Template preferences</a><ul>
+<li><a class="reference internal" href="#template-data" id="id118">Template data</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#keybinding-preferences" id="id119" name="id119">Keybinding preferences</a></li>
-<li><a class="reference" href="#printing-preferences" id="id120" name="id120">Printing preferences</a></li>
-<li><a class="reference" href="#terminal-vte-preferences" id="id121" name="id121">Terminal (VTE) preferences</a><ul>
-<li><a class="reference" href="#terminal-widget" id="id122" name="id122">Terminal widget</a></li>
+<li><a class="reference internal" href="#keybinding-preferences" id="id119">Keybinding preferences</a></li>
+<li><a class="reference internal" href="#printing-preferences" id="id120">Printing preferences</a></li>
+<li><a class="reference internal" href="#terminal-vte-preferences" id="id121">Terminal (VTE) preferences</a><ul>
+<li><a class="reference internal" href="#terminal-widget" id="id122">Terminal widget</a></li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a class="reference" href="#project-management" id="id123" name="id123">Project Management</a><ul>
-<li><a class="reference" href="#new-project" id="id124" name="id124">New Project</a></li>
-<li><a class="reference" href="#project-properties" id="id125" name="id125">Project Properties</a></li>
-<li><a class="reference" href="#open-project" id="id126" name="id126">Open Project</a></li>
-<li><a class="reference" href="#close-project" id="id127" name="id127">Close Project</a></li>
+<li><a class="reference internal" href="#project-management" id="id123">Project Management</a><ul>
+<li><a class="reference internal" href="#new-project" id="id124">New Project</a></li>
+<li><a class="reference internal" href="#project-properties" id="id125">Project Properties</a></li>
+<li><a class="reference internal" href="#open-project" id="id126">Open Project</a></li>
+<li><a class="reference internal" href="#close-project" id="id127">Close Project</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#build-menu" id="id128" name="id128">Build Menu</a><ul>
-<li><a class="reference" href="#indicators" id="id129" name="id129">Indicators</a></li>
-<li><a class="reference" href="#default-build-menu-items" id="id130" name="id130">Default Build Menu Items</a><ul>
-<li><a class="reference" href="#compile" id="id131" name="id131">Compile</a></li>
-<li><a class="reference" href="#build" id="id132" name="id132">Build</a></li>
-<li><a class="reference" href="#make" id="id133" name="id133">Make</a></li>
-<li><a class="reference" href="#make-custom-target" id="id134" name="id134">Make custom target</a></li>
-<li><a class="reference" href="#make-object" id="id135" name="id135">Make object</a></li>
-<li><a class="reference" href="#next-error" id="id136" name="id136">Next Error</a></li>
-<li><a class="reference" href="#previous-error" id="id137" name="id137">Previous Error</a></li>
-<li><a class="reference" href="#execute" id="id138" name="id138">Execute</a></li>
-<li><a class="reference" href="#stopping-running-processes" id="id139" name="id139">Stopping running processes</a><ul>
-<li><a class="reference" href="#terminal-emulators" id="id140" name="id140">Terminal emulators</a></li>
+<li><a class="reference internal" href="#build-menu" id="id128">Build Menu</a><ul>
+<li><a class="reference internal" href="#indicators" id="id129">Indicators</a></li>
+<li><a class="reference internal" href="#default-build-menu-items" id="id130">Default Build Menu Items</a><ul>
+<li><a class="reference internal" href="#compile" id="id131">Compile</a></li>
+<li><a class="reference internal" href="#build" id="id132">Build</a></li>
+<li><a class="reference internal" href="#make" id="id133">Make</a></li>
+<li><a class="reference internal" href="#make-custom-target" id="id134">Make custom target</a></li>
+<li><a class="reference internal" href="#make-object" id="id135">Make object</a></li>
+<li><a class="reference internal" href="#next-error" id="id136">Next Error</a></li>
+<li><a class="reference internal" href="#previous-error" id="id137">Previous Error</a></li>
+<li><a class="reference internal" href="#execute" id="id138">Execute</a></li>
+<li><a class="reference internal" href="#stopping-running-processes" id="id139">Stopping running processes</a><ul>
+<li><a class="reference internal" href="#terminal-emulators" id="id140">Terminal emulators</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#set-build-commands" id="id141" name="id141">Set Build Commands</a></li>
+<li><a class="reference internal" href="#set-build-commands" id="id141">Set Build Commands</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#build-menu-configuration" id="id142" name="id142">Build Menu Configuration</a></li>
-<li><a class="reference" href="#build-menu-commands-dialog" id="id143" name="id143">Build Menu Commands Dialog</a><ul>
-<li><a class="reference" href="#substitutions-in-commands-and-working-directories" id="id144" name="id144">Substitutions in Commands and Working Directories</a></li>
-<li><a class="reference" href="#build-menu-keyboard-shortcuts" id="id145" name="id145">Build Menu Keyboard Shortcuts</a></li>
-<li><a class="reference" href="#configuration-files" id="id146" name="id146">Configuration Files</a></li>
+<li><a class="reference internal" href="#build-menu-configuration" id="id142">Build Menu Configuration</a></li>
+<li><a class="reference internal" href="#build-menu-commands-dialog" id="id143">Build Menu Commands Dialog</a><ul>
+<li><a class="reference internal" href="#substitutions-in-commands-and-working-directories" id="id144">Substitutions in Commands and Working Directories</a></li>
+<li><a class="reference internal" href="#build-menu-keyboard-shortcuts" id="id145">Build Menu Keyboard Shortcuts</a></li>
+<li><a class="reference internal" href="#configuration-files" id="id146">Configuration Files</a></li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a class="reference" href="#printing-support" id="id147" name="id147">Printing support</a></li>
-<li><a class="reference" href="#plugins" id="id148" name="id148">Plugins</a></li>
-<li><a class="reference" href="#keybindings" id="id149" name="id149">Keybindings</a><ul>
-<li><a class="reference" href="#switching-documents" id="id150" name="id150">Switching documents</a></li>
-<li><a class="reference" href="#configurable-keybindings" id="id151" name="id151">Configurable keybindings</a><ul>
-<li><a class="reference" href="#file-keybindings" id="id152" name="id152">File keybindings</a></li>
-<li><a class="reference" href="#editor-keybindings" id="id153" name="id153">Editor keybindings</a></li>
-<li><a class="reference" href="#clipboard-keybindings" id="id154" name="id154">Clipboard keybindings</a></li>
-<li><a class="reference" href="#select-keybindings" id="id155" name="id155">Select keybindings</a></li>
-<li><a class="reference" href="#insert-keybindings" id="id156" name="id156">Insert keybindings</a></li>
-<li><a class="reference" href="#format-keybindings" id="id157" name="id157">Format keybindings</a></li>
-<li><a class="reference" href="#settings-keybindings" id="id158" name="id158">Settings keybindings</a></li>
-<li><a class="reference" href="#search-keybindings" id="id159" name="id159">Search keybindings</a></li>
-<li><a class="reference" href="#go-to-keybindings" id="id160" name="id160">Go to keybindings</a></li>
-<li><a class="reference" href="#view-keybindings" id="id161" name="id161">View keybindings</a></li>
-<li><a class="reference" href="#focus-keybindings" id="id162" name="id162">Focus keybindings</a></li>
-<li><a class="reference" href="#notebook-tab-keybindings" id="id163" name="id163">Notebook tab keybindings</a></li>
-<li><a class="reference" href="#document-keybindings" id="id164" name="id164">Document keybindings</a></li>
-<li><a class="reference" href="#build-keybindings" id="id165" name="id165">Build keybindings</a></li>
-<li><a class="reference" href="#tools-keybindings" id="id166" name="id166">Tools keybindings</a></li>
-<li><a class="reference" href="#help-keybindings" id="id167" name="id167">Help keybindings</a></li>
+<li><a class="reference internal" href="#printing-support" id="id147">Printing support</a></li>
+<li><a class="reference internal" href="#plugins" id="id148">Plugins</a></li>
+<li><a class="reference internal" href="#keybindings" id="id149">Keybindings</a><ul>
+<li><a class="reference internal" href="#switching-documents" id="id150">Switching documents</a></li>
+<li><a class="reference internal" href="#configurable-keybindings" id="id151">Configurable keybindings</a><ul>
+<li><a class="reference internal" href="#file-keybindings" id="id152">File keybindings</a></li>
+<li><a class="reference internal" href="#editor-keybindings" id="id153">Editor keybindings</a></li>
+<li><a class="reference internal" href="#clipboard-keybindings" id="id154">Clipboard keybindings</a></li>
+<li><a class="reference internal" href="#select-keybindings" id="id155">Select keybindings</a></li>
+<li><a class="reference internal" href="#insert-keybindings" id="id156">Insert keybindings</a></li>
+<li><a class="reference internal" href="#format-keybindings" id="id157">Format keybindings</a></li>
+<li><a class="reference internal" href="#settings-keybindings" id="id158">Settings keybindings</a></li>
+<li><a class="reference internal" href="#search-keybindings" id="id159">Search keybindings</a></li>
+<li><a class="reference internal" href="#go-to-keybindings" id="id160">Go to keybindings</a></li>
+<li><a class="reference internal" href="#view-keybindings" id="id161">View keybindings</a></li>
+<li><a class="reference internal" href="#focus-keybindings" id="id162">Focus keybindings</a></li>
+<li><a class="reference internal" href="#notebook-tab-keybindings" id="id163">Notebook tab keybindings</a></li>
+<li><a class="reference internal" href="#document-keybindings" id="id164">Document keybindings</a></li>
+<li><a class="reference internal" href="#build-keybindings" id="id165">Build keybindings</a></li>
+<li><a class="reference internal" href="#tools-keybindings" id="id166">Tools keybindings</a></li>
+<li><a class="reference internal" href="#help-keybindings" id="id167">Help keybindings</a></li>
 </ul>
 </li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a class="reference" href="#id4" id="id168" name="id168">Configuration files</a><ul>
-<li><a class="reference" href="#tools-menu-items" id="id169" name="id169">Tools menu items</a></li>
-<li><a class="reference" href="#global-configuration-file" id="id170" name="id170">Global configuration file</a></li>
-<li><a class="reference" href="#filetype-definition-files" id="id171" name="id171">Filetype definition files</a><ul>
-<li><a class="reference" href="#custom-filetypes" id="id172" name="id172">Custom filetypes</a></li>
-<li><a class="reference" href="#system-files" id="id173" name="id173">System files</a></li>
-<li><a class="reference" href="#user-files" id="id174" name="id174">User files</a></li>
-<li><a class="reference" href="#format" id="id175" name="id175">Format</a><ul>
-<li><a class="reference" href="#styling-section" id="id176" name="id176">[styling] Section</a><ul>
-<li><a class="reference" href="#using-a-named-style" id="id177" name="id177">Using a named style</a></li>
+<li><a class="reference internal" href="#id4" id="id168">Configuration files</a><ul>
+<li><a class="reference internal" href="#tools-menu-items" id="id169">Tools menu items</a></li>
+<li><a class="reference internal" href="#global-configuration-file" id="id170">Global configuration file</a></li>
+<li><a class="reference internal" href="#filetype-definition-files" id="id171">Filetype definition files</a><ul>
+<li><a class="reference internal" href="#custom-filetypes" id="id172">Custom filetypes</a></li>
+<li><a class="reference internal" href="#system-files" id="id173">System files</a></li>
+<li><a class="reference internal" href="#user-files" id="id174">User files</a></li>
+<li><a class="reference internal" href="#format" id="id175">Format</a><ul>
+<li><a class="reference internal" href="#styling-section" id="id176">[styling] Section</a><ul>
+<li><a class="reference internal" href="#using-a-named-style" id="id177">Using a named style</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#keywords-section" id="id178" name="id178">[keywords] Section</a></li>
-<li><a class="reference" href="#lexer-properties-section" id="id179" name="id179">[lexer_properties] Section</a></li>
-<li><a class="reference" href="#settings-section" id="id180" name="id180">[settings] Section</a></li>
-<li><a class="reference" href="#build-settings-section" id="id181" name="id181">[build_settings] Section</a></li>
+<li><a class="reference internal" href="#keywords-section" id="id178">[keywords] Section</a></li>
+<li><a class="reference internal" href="#lexer-properties-section" id="id179">[lexer_properties] Section</a></li>
+<li><a class="reference internal" href="#settings-section" id="id180">[settings] Section</a></li>
+<li><a class="reference internal" href="#build-settings-section" id="id181">[build_settings] Section</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#special-file-filetypes-common" id="id182" name="id182">Special file filetypes.common</a><ul>
-<li><a class="reference" href="#named-styles-section" id="id183" name="id183">[named_styles] Section</a></li>
-<li><a class="reference" href="#id5" id="id184" name="id184">[styling] Section</a></li>
-<li><a class="reference" href="#id6" id="id185" name="id185">[settings] Section</a></li>
+<li><a class="reference internal" href="#special-file-filetypes-common" id="id182">Special file filetypes.common</a><ul>
+<li><a class="reference internal" href="#named-styles-section" id="id183">[named_styles] Section</a></li>
+<li><a class="reference internal" href="#id5" id="id184">[styling] Section</a></li>
+<li><a class="reference internal" href="#id6" id="id185">[settings] Section</a></li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a class="reference" href="#filetype-extensions" id="id186" name="id186">Filetype extensions</a></li>
-<li><a class="reference" href="#preferences-file-format" id="id187" name="id187">Preferences File Format</a><ul>
-<li><a class="reference" href="#hidden-preferences" id="id188" name="id188">Hidden preferences</a></li>
-<li><a class="reference" href="#build-menu-section" id="id189" name="id189">[build-menu] Section</a></li>
+<li><a class="reference internal" href="#filetype-extensions" id="id186">Filetype extensions</a></li>
+<li><a class="reference internal" href="#preferences-file-format" id="id187">Preferences File Format</a><ul>
+<li><a class="reference internal" href="#hidden-preferences" id="id188">Hidden preferences</a></li>
+<li><a class="reference internal" href="#build-menu-section" id="id189">[build-menu] Section</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#project-file-format" id="id190" name="id190">Project File Format</a><ul>
-<li><a class="reference" href="#build-menu-additions" id="id191" name="id191">[build-menu] Additions</a></li>
+<li><a class="reference internal" href="#project-file-format" id="id190">Project File Format</a><ul>
+<li><a class="reference internal" href="#build-menu-additions" id="id191">[build-menu] Additions</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#templates" id="id192" name="id192">Templates</a><ul>
-<li><a class="reference" href="#template-meta-data" id="id193" name="id193">Template meta data</a></li>
-<li><a class="reference" href="#file-templates" id="id194" name="id194">File templates</a><ul>
-<li><a class="reference" href="#custom-file-templates" id="id195" name="id195">Custom file templates</a></li>
-<li><a class="reference" href="#filetype-templates" id="id196" name="id196">Filetype templates</a></li>
+<li><a class="reference internal" href="#templates" id="id192">Templates</a><ul>
+<li><a class="reference internal" href="#template-meta-data" id="id193">Template meta data</a></li>
+<li><a class="reference internal" href="#file-templates" id="id194">File templates</a><ul>
+<li><a class="reference internal" href="#custom-file-templates" id="id195">Custom file templates</a></li>
+<li><a class="reference internal" href="#filetype-templates" id="id196">Filetype templates</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#customizing-templates" id="id197" name="id197">Customizing templates</a><ul>
-<li><a class="reference" href="#template-wildcards" id="id198" name="id198">Template wildcards</a><ul>
-<li><a class="reference" href="#special-command-wildcard" id="id199" name="id199">Special {command:} wildcard</a></li>
+<li><a class="reference internal" href="#customizing-templates" id="id197">Customizing templates</a><ul>
+<li><a class="reference internal" href="#template-wildcards" id="id198">Template wildcards</a><ul>
+<li><a class="reference internal" href="#special-command-wildcard" id="id199">Special {command:} wildcard</a></li>
 </ul>
 </li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a class="reference" href="#customizing-the-toolbar" id="id200" name="id200">Customizing the toolbar</a><ul>
-<li><a class="reference" href="#manually-editing-of-the-toolbar-layout" id="id201" name="id201">Manually editing of the toolbar layout</a></li>
-<li><a class="reference" href="#available-toolbar-elements" id="id202" name="id202">Available toolbar elements</a></li>
+<li><a class="reference internal" href="#customizing-the-toolbar" id="id200">Customizing the toolbar</a><ul>
+<li><a class="reference internal" href="#manually-editing-of-the-toolbar-layout" id="id201">Manually editing of the toolbar layout</a></li>
+<li><a class="reference internal" href="#available-toolbar-elements" id="id202">Available toolbar elements</a></li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a class="reference" href="#plugin-documentation" id="id203" name="id203">Plugin documentation</a><ul>
-<li><a class="reference" href="#htmlchars" id="id204" name="id204">HTMLChars</a><ul>
-<li><a class="reference" href="#insert-entity-dialog" id="id205" name="id205">Insert entity dialog</a></li>
-<li><a class="reference" href="#replace-special-chars-by-its-entity" id="id206" name="id206">Replace special chars by its entity</a><ul>
-<li><a class="reference" href="#at-typing-time" id="id207" name="id207">At typing time</a></li>
-<li><a class="reference" href="#bulk-replacement" id="id208" name="id208">Bulk replacement</a></li>
+<li><a class="reference internal" href="#plugin-documentation" id="id203">Plugin documentation</a><ul>
+<li><a class="reference internal" href="#htmlchars" id="id204">HTMLChars</a><ul>
+<li><a class="reference internal" href="#insert-entity-dialog" id="id205">Insert entity dialog</a></li>
+<li><a class="reference internal" href="#replace-special-chars-by-its-entity" id="id206">Replace special chars by its entity</a><ul>
+<li><a class="reference internal" href="#at-typing-time" id="id207">At typing time</a></li>
+<li><a class="reference internal" href="#bulk-replacement" id="id208">Bulk replacement</a></li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a class="reference" href="#save-actions" id="id209" name="id209">Save Actions</a><ul>
-<li><a class="reference" href="#instant-save" id="id210" name="id210">Instant Save</a></li>
-<li><a class="reference" href="#backup-copy" id="id211" name="id211">Backup Copy</a></li>
+<li><a class="reference internal" href="#save-actions" id="id209">Save Actions</a><ul>
+<li><a class="reference internal" href="#instant-save" id="id210">Instant Save</a></li>
+<li><a class="reference internal" href="#backup-copy" id="id211">Backup Copy</a></li>
 </ul>
 </li>
+<li><a class="reference internal" href="#xml-snippets" id="id212">XML Snippets</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#contributing-to-this-document" id="id212" name="id212">Contributing to this document</a></li>
-<li><a class="reference" href="#scintilla-keyboard-commands" id="id213" name="id213">Scintilla keyboard commands</a><ul>
-<li><a class="reference" href="#keyboard-commands" id="id214" name="id214">Keyboard commands</a></li>
+<li><a class="reference internal" href="#contributing-to-this-document" id="id213">Contributing to this document</a></li>
+<li><a class="reference internal" href="#scintilla-keyboard-commands" id="id214">Scintilla keyboard commands</a><ul>
+<li><a class="reference internal" href="#keyboard-commands" id="id215">Keyboard commands</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#tips-and-tricks" id="id215" name="id215">Tips and tricks</a><ul>
-<li><a class="reference" href="#document-notebook" id="id216" name="id216">Document notebook</a></li>
-<li><a class="reference" href="#editor" id="id217" name="id217">Editor</a></li>
-<li><a class="reference" href="#interface" id="id218" name="id218">Interface</a></li>
-<li><a class="reference" href="#gtk-related" id="id219" name="id219">GTK-related</a></li>
+<li><a class="reference internal" href="#tips-and-tricks" id="id216">Tips and tricks</a><ul>
+<li><a class="reference internal" href="#document-notebook" id="id217">Document notebook</a></li>
+<li><a class="reference internal" href="#editor" id="id218">Editor</a></li>
+<li><a class="reference internal" href="#interface" id="id219">Interface</a></li>
+<li><a class="reference internal" href="#gtk-related" id="id220">GTK-related</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#compile-time-options" id="id220" name="id220">Compile-time options</a><ul>
-<li><a class="reference" href="#src-geany-h" id="id221" name="id221">src/geany.h</a></li>
-<li><a class="reference" href="#project-h" id="id222" name="id222">project.h</a></li>
-<li><a class="reference" href="#editor-h" id="id223" name="id223">editor.h</a></li>
-<li><a class="reference" href="#keyfile-c" id="id224" name="id224">keyfile.c</a></li>
-<li><a class="reference" href="#build-c" id="id225" name="id225">build.c</a></li>
+<li><a class="reference internal" href="#compile-time-options" id="id221">Compile-time options</a><ul>
+<li><a class="reference internal" href="#src-geany-h" id="id222">src/geany.h</a></li>
+<li><a class="reference internal" href="#project-h" id="id223">project.h</a></li>
+<li><a class="reference internal" href="#editor-h" id="id224">editor.h</a></li>
+<li><a class="reference internal" href="#keyfile-c" id="id225">keyfile.c</a></li>
+<li><a class="reference internal" href="#build-c" id="id226">build.c</a></li>
 </ul>
 </li>
-<li><a class="reference" href="#gnu-general-public-license" id="id226" name="id226">GNU General Public License</a></li>
-<li><a class="reference" href="#license-for-scintilla-and-scite" id="id227" name="id227">License for Scintilla and SciTE</a></li>
+<li><a class="reference internal" href="#gnu-general-public-license" id="id227">GNU General Public License</a></li>
+<li><a class="reference internal" href="#license-for-scintilla-and-scite" id="id228">License for Scintilla and SciTE</a></li>
 </ul>
 </div>
-<div class="section">
-<h1><a class="toc-backref" href="#id8" id="introduction" name="introduction">Introduction</a></h1>
-<div class="section">
-<h2><a class="toc-backref" href="#id9" id="about-geany" name="about-geany">About Geany</a></h2>
+<div class="section" id="introduction">
+<h1><a class="toc-backref" href="#id8">Introduction</a></h1>
+<div class="section" id="about-geany">
+<h2><a class="toc-backref" href="#id9">About Geany</a></h2>
 <p>Geany is a small and lightweight Integrated Development Environment. It
 was developed to provide a small and fast IDE, which has only a few
 dependencies on other packages. Another goal was to be as independent
@@ -517,56 +518,56 @@ Pascal, and others</li>
 <li>Plugin interface</li>
 </ul>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id10" id="where-to-get-it" name="where-to-get-it">Where to get it</a></h2>
-<p>You can obtain Geany from <a class="reference" href="http://www.geany.org/">http://www.geany.org/</a> or perhaps also from
+<div class="section" id="where-to-get-it">
+<h2><a class="toc-backref" href="#id10">Where to get it</a></h2>
+<p>You can obtain Geany from <a class="reference external" href="http://www.geany.org/">http://www.geany.org/</a> or perhaps also from
 your distribution. For a list of available packages, please see
-<a class="reference" href="http://www.geany.org/Download/ThirdPartyPackages">http://www.geany.org/Download/ThirdPartyPackages</a>.</p>
+<a class="reference external" href="http://www.geany.org/Download/ThirdPartyPackages">http://www.geany.org/Download/ThirdPartyPackages</a>.</p>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id11" id="license" name="license">License</a></h2>
+<div class="section" id="license">
+<h2><a class="toc-backref" href="#id11">License</a></h2>
 <p>Geany is distributed under the terms of the GNU General Public License
 as published by the Free Software Foundation; either version 2 of
 the License, or (at your option) any later version. A copy of this
 license can be found in the file COPYING included with the source
-code of this program and in the chapter, <a class="reference" href="#gnu-general-public-license">GNU General Public License</a>.</p>
+code of this program and in the chapter, <a class="reference internal" href="#gnu-general-public-license">GNU General Public License</a>.</p>
 <p>The included Scintilla library (found in the subdirectory
-<tt class="docutils literal"><span class="pre">scintilla/</span></tt>) has its own license, which can be found in the chapter,
-<a class="reference" href="#license-for-scintilla-and-scite">License for Scintilla and SciTE</a>.</p>
+<tt class="docutils literal">scintilla/</tt>) has its own license, which can be found in the chapter,
+<a class="reference internal" href="#license-for-scintilla-and-scite">License for Scintilla and SciTE</a>.</p>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id12" id="about-this-document" name="about-this-document">About this document</a></h2>
+<div class="section" id="about-this-document">
+<h2><a class="toc-backref" href="#id12">About this document</a></h2>
 <p>This documentation is available in HTML and text formats.
-The latest version can always be found at <a class="reference" href="http://www.geany.org/">http://www.geany.org/</a>.</p>
-<p>If you want to contribute to it, see <a class="reference" href="#contributing-to-this-document">Contributing to this document</a>.</p>
+The latest version can always be found at <a class="reference external" href="http://www.geany.org/">http://www.geany.org/</a>.</p>
+<p>If you want to contribute to it, see <a class="reference internal" href="#contributing-to-this-document">Contributing to this document</a>.</p>
 </div>
 </div>
-<div class="section">
-<h1><a class="toc-backref" href="#id13" id="installation" name="installation">Installation</a></h1>
-<div class="section">
-<h2><a class="toc-backref" href="#id14" id="requirements" name="requirements">Requirements</a></h2>
+<div class="section" id="installation">
+<h1><a class="toc-backref" href="#id13">Installation</a></h1>
+<div class="section" id="requirements">
+<h2><a class="toc-backref" href="#id14">Requirements</a></h2>
 <p>You will need the GTK (&gt;= 2.8.0) libraries and their dependencies
 (Pango, GLib and ATK). Your distro should provide packages for these,
 usually installed by default. For Windows, you can download an installer
 from the website which bundles these libraries.</p>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id15" id="binary-packages" name="binary-packages">Binary packages</a></h2>
+<div class="section" id="binary-packages">
+<h2><a class="toc-backref" href="#id15">Binary packages</a></h2>
 <p>There are many binary packages available. For an up-to-date but maybe
-incomplete list see <a class="reference" href="http://www.geany.org/Download/ThirdPartyPackages">http://www.geany.org/Download/ThirdPartyPackages</a>.</p>
+incomplete list see <a class="reference external" href="http://www.geany.org/Download/ThirdPartyPackages">http://www.geany.org/Download/ThirdPartyPackages</a>.</p>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id16" id="source-compilation" name="source-compilation">Source compilation</a></h2>
+<div class="section" id="source-compilation">
+<h2><a class="toc-backref" href="#id16">Source compilation</a></h2>
 <p>Compiling Geany is quite easy.
 To do so, you need the GTK (&gt;= 2.8.0) libraries and header files.
 You also need the Pango, GLib and ATK libraries and header files.
-All these files are available at <a class="reference" href="http://www.gtk.org">http://www.gtk.org</a>, but very often
+All these files are available at <a class="reference external" href="http://www.gtk.org">http://www.gtk.org</a>, but very often
 your distro will provide development packages to save the trouble of
 building these yourself.</p>
 <p>Furthermore you need, of course, a C and C++ compiler. The GNU versions
 of these tools are recommended.</p>
-<div class="section">
-<h3><a class="toc-backref" href="#id17" id="autotools-based-build-system" name="autotools-based-build-system">Autotools based build system</a></h3>
+<div class="section" id="autotools-based-build-system">
+<h3><a class="toc-backref" href="#id17">Autotools based build system</a></h3>
 <p>The Autotools based build system is very mature and has been well tested.
 To use it, you just need the Make tool, preferably GNU Make.</p>
 <p>Then run the following commands:</p>
@@ -579,8 +580,8 @@ $ make
 % make install
 </pre>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id18" id="waf-based-build-system" name="waf-based-build-system">Waf based build system</a></h3>
+<div class="section" id="waf-based-build-system">
+<h3><a class="toc-backref" href="#id18">Waf based build system</a></h3>
 <p>The Waf build system is still quite young and under heavy development but already in a
 usable state. In contrast to the Autotools system, Waf needs Python. So before using Waf, you need
 to install Python on your system.
@@ -588,7 +589,7 @@ The advantage of the Waf build system over the Autotools based build system is t
 build process might be a bit faster. Especially when you use the Waf
 cache feature for repetitive builds (e.g. when changing only a few source files
 to test something) will become much faster since Waf will cache and re-use the
-unchanged built files and only compile the changed code again. See <a class="reference" href="#waf-cache">Waf Cache</a> for details.
+unchanged built files and only compile the changed code again. See <a class="reference internal" href="#waf-cache">Waf Cache</a> for details.
 To build Geany with Waf as run:</p>
 <pre class="literal-block">
 $ ./waf configure
@@ -598,13 +599,13 @@ $ ./waf build
 <pre class="literal-block">
 % ./waf install
 </pre>
-<div class="section">
-<h4><a class="toc-backref" href="#id19" id="waf-cache" name="waf-cache">Waf Cache</a></h4>
+<div class="section" id="waf-cache">
+<h4><a class="toc-backref" href="#id19">Waf Cache</a></h4>
 <p>The Waf build system has a nice and interesting feature which can help  to avoid
 a lot of unnecessary rebuilding of unchanged code. This often happens when developing new features
 or trying to debug something in Geany.
 Waf is able to store and retrieve the object files from a cache. This cache is declared
-using the environment variable <tt class="docutils literal"><span class="pre">WAFCACHE</span></tt>.
+using the environment variable <tt class="docutils literal">WAFCACHE</tt>.
 A possible location of the cache directory could be <tt class="docutils literal"><span class="pre">~/.cache/waf</span></tt>. In order to make use of
 this, you first need to create this directory:</p>
 <pre class="literal-block">
@@ -615,11 +616,11 @@ Bash and should be adjusted to your used shell):</p>
 <pre class="literal-block">
 export WAFCACHE=/home/username/.cache/waf
 </pre>
-<p>Remember to replace <tt class="docutils literal"><span class="pre">username</span></tt> with your actual username.</p>
+<p>Remember to replace <tt class="docutils literal">username</tt> with your actual username.</p>
 <p>More information about the Waf cache feature are available at
-<a class="reference" href="http://code.google.com/p/waf/wiki/CacheObjectFiles">http://code.google.com/p/waf/wiki/CacheObjectFiles</a>.</p>
-<div class="section">
-<h5><a class="toc-backref" href="#id20" id="cleaning-the-cache" name="cleaning-the-cache">Cleaning the Cache</a></h5>
+<a class="reference external" href="http://code.google.com/p/waf/wiki/CacheObjectFiles">http://code.google.com/p/waf/wiki/CacheObjectFiles</a>.</p>
+<div class="section" id="cleaning-the-cache">
+<h5><a class="toc-backref" href="#id20">Cleaning the Cache</a></h5>
 <p>You should be careful about the size of the cache directory as it may
 grow rapidly over time.
 Waf doesn't do any cleaning or other house-keeping of the cache yet, so you need to keep it
@@ -630,12 +631,12 @@ cached files:</p>
 $ find /home/username/.cache/waf -mtime +14 -exec rm {} \;
 </pre>
 <p>This will delete all files in the cache directory which are older than 14 days.</p>
-<p>For details about the <tt class="docutils literal"><span class="pre">find</span></tt> command and its options, check its manual page.</p>
+<p>For details about the <tt class="docutils literal">find</tt> command and its options, check its manual page.</p>
 </div>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id21" id="custom-installation" name="custom-installation">Custom installation</a></h3>
+<div class="section" id="custom-installation">
+<h3><a class="toc-backref" href="#id21">Custom installation</a></h3>
 <p>The configure script supports several common options, for a detailed
 list, type:</p>
 <pre class="literal-block">
@@ -649,40 +650,40 @@ $ ./configure --help
 <p>You may also want to read the INSTALL file for advanced installation
 options.</p>
 <ul class="simple">
-<li>See also <a class="reference" href="#compile-time-options">Compile-time options</a>.</li>
+<li>See also <a class="reference internal" href="#compile-time-options">Compile-time options</a>.</li>
 </ul>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id22" id="dynamic-linking-loader-support-and-vte" name="dynamic-linking-loader-support-and-vte">Dynamic linking loader support and VTE</a></h3>
+<div class="section" id="dynamic-linking-loader-support-and-vte">
+<h3><a class="toc-backref" href="#id22">Dynamic linking loader support and VTE</a></h3>
 <p>In the case that your system lacks dynamic linking loader support, you
-probably want to pass the option <tt class="docutils literal"><span class="pre">--disable-vte</span></tt> to the <tt class="docutils literal"><span class="pre">configure</span></tt>
+probably want to pass the option <tt class="docutils literal"><span class="pre">--disable-vte</span></tt> to the <tt class="docutils literal">configure</tt>
 script. This prevents compiling Geany with dynamic linking loader
-support for automatically loading <tt class="docutils literal"><span class="pre">libvte.so.4</span></tt> if available.</p>
+support for automatically loading <tt class="docutils literal">libvte.so.4</tt> if available.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id23" id="build-problems" name="build-problems">Build problems</a></h3>
+<div class="section" id="build-problems">
+<h3><a class="toc-backref" href="#id23">Build problems</a></h3>
 <p>If there are any errors during compilation, check your build
 environment and try to find the error, otherwise contact the mailing
 list or one the authors. Sometimes you might need to ask for specific
 help from your distribution.</p>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id24" id="installation-prefix" name="installation-prefix">Installation prefix</a></h2>
+<div class="section" id="installation-prefix">
+<h2><a class="toc-backref" href="#id24">Installation prefix</a></h2>
 <p>If you want to edit any of Geany's system configuration files after
 installation you will need to know the installation prefix.  Usually this
 is not necessary as you can just use per user configuration files and
 you will not need root permissions.</p>
-<p>Use the <tt class="docutils literal"><span class="pre">--print-prefix</span></tt> option to Geany to check - see <a class="reference" href="#command-line-options">Command line
+<p>Use the <tt class="docutils literal"><span class="pre">--print-prefix</span></tt> option to Geany to check - see <a class="reference internal" href="#command-line-options">Command line
 options</a>. The first path is the prefix.</p>
-<p>This is commonly <tt class="docutils literal"><span class="pre">/usr</span></tt> if you installed from a binary package, or
-<tt class="docutils literal"><span class="pre">/usr/local</span></tt> if you build from source.</p>
+<p>This is commonly <tt class="docutils literal">/usr</tt> if you installed from a binary package, or
+<tt class="docutils literal">/usr/local</tt> if you build from source.</p>
 </div>
 </div>
-<div class="section">
-<h1><a class="toc-backref" href="#id25" id="usage" name="usage">Usage</a></h1>
-<div class="section">
-<h2><a class="toc-backref" href="#id26" id="getting-started" name="getting-started">Getting started</a></h2>
+<div class="section" id="usage">
+<h1><a class="toc-backref" href="#id25">Usage</a></h1>
+<div class="section" id="getting-started">
+<h2><a class="toc-backref" href="#id26">Getting started</a></h2>
 <p>You can start Geany in the following ways:</p>
 <ul>
 <li><p class="first">From the Desktop Environment menu:</p>
@@ -698,8 +699,8 @@ Return:</p>
 </li>
 </ul>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id27" id="the-geany-workspace" name="the-geany-workspace">The Geany workspace</a></h2>
+<div class="section" id="the-geany-workspace">
+<h2><a class="toc-backref" href="#id27">The Geany workspace</a></h2>
 <p>The Geany window is shown in the following figure:</p>
 <img alt="./images/main_window.png" src="./images/main_window.png" />
 <p>The workspace has the following parts:</p>
@@ -727,8 +728,8 @@ Return:</p>
 <p>The sizes of the sidebar and message window can be adjusted by
 dragging the dividers.</p>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id28" id="command-line-options" name="command-line-options">Command line options</a></h2>
+<div class="section" id="command-line-options">
+<h2><a class="toc-backref" href="#id28">Command line options</a></h2>
 <table border="1" class="docutils">
 <colgroup>
 <col width="9%" />
@@ -757,7 +758,7 @@ file foo.bar and place the cursor in line 7.</td>
 <td>--config=directory_name</td>
 <td>Use an alternate configuration directory. The default
 configuration directory is <tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt> and that
-is where <tt class="docutils literal"><span class="pre">geany.conf</span></tt> and other configuration files
+is where <tt class="docutils literal">geany.conf</tt> and other configuration files
 reside.</td>
 </tr>
 <tr><td><em>none</em></td>
@@ -768,7 +769,7 @@ for snippets configuration).</td>
 <tr><td>-g</td>
 <td>--generate-tags</td>
 <td>Generate a global tags file (see
-<a class="reference" href="#generating-a-global-tags-file">Generating a global tags file</a>).</td>
+<a class="reference internal" href="#generating-a-global-tags-file">Generating a global tags file</a>).</td>
 </tr>
 <tr><td>-P</td>
 <td>--no-preprocessing</td>
@@ -824,7 +825,7 @@ authors to detect installation paths.</td>
 <td>--no-terminal</td>
 <td>Do not load terminal support. Use this option if you do
 not want to load the virtual terminal emulator widget
-at startup. If you do not have <tt class="docutils literal"><span class="pre">libvte.so.4</span></tt> installed,
+at startup. If you do not have <tt class="docutils literal">libvte.so.4</tt> installed,
 then terminal-support is automatically disabled. Only
 available if Geany was compiled with support for VTE.</td>
 </tr>
@@ -842,7 +843,7 @@ geany --socket-file=/tmp/geany-sock-$(xprop -root _NET_CURRENT_DESKTOP | awk '{p
 <td>--vte-lib</td>
 <td>Specify explicitly the path including filename or only
 the filename to the VTE library, e.g.
-<tt class="docutils literal"><span class="pre">/usr/lib/libvte.so</span></tt> or <tt class="docutils literal"><span class="pre">libvte.so</span></tt>. This option is
+<tt class="docutils literal">/usr/lib/libvte.so</tt> or <tt class="docutils literal">libvte.so</tt>. This option is
 only needed when the auto-detection does not work. Only
 available if Geany was compiled with support for VTE.</td>
 </tr>
@@ -881,13 +882,13 @@ geany some_file.foo:55:4
 <p>Geany supports all generic GTK options, a list is available on the
 help screen.</p>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id29" id="general" name="general">General</a></h2>
-<div class="section">
-<h3><a class="toc-backref" href="#id30" id="startup" name="startup">Startup</a></h3>
+<div class="section" id="general">
+<h2><a class="toc-backref" href="#id29">General</a></h2>
+<div class="section" id="startup">
+<h3><a class="toc-backref" href="#id30">Startup</a></h3>
 <p>At startup, Geany loads all files from the last time Geany was
 launched. You can disable this feature in the preferences dialog
-(see <a class="reference" href="#general-startup-preferences">General Startup preferences</a>). If you specify some
+(see <a class="reference internal" href="#general-startup-preferences">General Startup preferences</a>). If you specify some
 files on the command line, only these files will be opened, but you
 can find the files from the last session in the file menu under the
 &quot;Recent files&quot; item. By default this contains the last 10 recently
@@ -898,8 +899,8 @@ load files from the last session. To run a second instance of Geany,
 do not specify any filenames on the command-line, or disable opening
 files in a running instance using the appropriate command line option.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id31" id="opening-files-from-the-command-line-in-a-running-instance" name="opening-files-from-the-command-line-in-a-running-instance">Opening files from the command-line in a running instance</a></h3>
+<div class="section" id="opening-files-from-the-command-line-in-a-running-instance">
+<h3><a class="toc-backref" href="#id31">Opening files from the command-line in a running instance</a></h3>
 <p>Geany detects if there is an an instance of itself already running and opens files
 from the command-line in that instance. So, Geany can
 be used to view and edit files by opening them from other programs
@@ -908,22 +909,22 @@ such as a file manager.</p>
 <pre class="literal-block">
 geany some_file.foo:55:4
 </pre>
-<p>This would open the file <tt class="docutils literal"><span class="pre">some_file.foo</span></tt> with the cursor on line 55,
+<p>This would open the file <tt class="docutils literal">some_file.foo</tt> with the cursor on line 55,
 column 4.</p>
 <p>If you do not like this for some reason, you can disable using the first
 instance by using the appropriate command line option -- see the section
-called <a class="reference" href="#command-line-options">Command line options</a>.</p>
+called <a class="reference internal" href="#command-line-options">Command line options</a>.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id32" id="virtual-terminal-emulator-widget-vte" name="virtual-terminal-emulator-widget-vte">Virtual terminal emulator widget (VTE)</a></h3>
-<p>If you have installed <tt class="docutils literal"><span class="pre">libvte.so</span></tt> on your system, it is loaded
+<div class="section" id="virtual-terminal-emulator-widget-vte">
+<h3><a class="toc-backref" href="#id32">Virtual terminal emulator widget (VTE)</a></h3>
+<p>If you have installed <tt class="docutils literal">libvte.so</tt> on your system, it is loaded
 automatically by Geany, and you will have a terminal widget in the
 notebook at the bottom.</p>
-<p>If Geany cannot find any <tt class="docutils literal"><span class="pre">libvte.so</span></tt> at startup, the terminal widget
+<p>If Geany cannot find any <tt class="docutils literal">libvte.so</tt> at startup, the terminal widget
 will not be loaded. So there is no need to install the package containing
 this file in order to run Geany. Additionally, you can disable the use
 of the terminal widget by command line option, for more information
-see the section called <a class="reference" href="#command-line-options">Command line options</a>.</p>
+see the section called <a class="reference internal" href="#command-line-options">Command line options</a>.</p>
 <p>You can use this terminal (from now on called VTE) much as you would
 a terminal program like xterm. There is basic clipboard support. You
 can paste the contents of the clipboard by pressing the right mouse
@@ -940,26 +941,26 @@ should be found in the manual page of the shell. For zsh and bash
 you can use the argument <tt class="docutils literal"><span class="pre">--login</span></tt>.</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
-<p class="last">Geany tries to load <tt class="docutils literal"><span class="pre">libvte.so</span></tt>. If this fails, it tries to load
+<p class="last">Geany tries to load <tt class="docutils literal">libvte.so</tt>. If this fails, it tries to load
 some other filenames. If this fails too, you should check whether you
 installed libvte correctly. Again note, Geany will run without this
 library.</p>
 </div>
 <p>It could be, that the library is called something else than
-<tt class="docutils literal"><span class="pre">libvte.so</span></tt> (e.g. on FreeBSD 6.0 it is called <tt class="docutils literal"><span class="pre">libvte.so.8</span></tt>). If so
+<tt class="docutils literal">libvte.so</tt> (e.g. on FreeBSD 6.0 it is called <tt class="docutils literal">libvte.so.8</tt>). If so
 please set a link to the correct file (as root):</p>
 <pre class="literal-block">
 # ln -s /usr/lib/libvte.so.X /usr/lib/libvte.so
 </pre>
 <p>Obviously, you have to adjust the paths and set X to the number of your
-<tt class="docutils literal"><span class="pre">libvte.so</span></tt>.</p>
+<tt class="docutils literal">libvte.so</tt>.</p>
 <p>You can also specify the filename of the VTE library to use on the command
-line (see the section called <a class="reference" href="#command-line-options">Command line options</a>) or at compile time
+line (see the section called <a class="reference internal" href="#command-line-options">Command line options</a>) or at compile time
 by specifying the command line option <tt class="docutils literal"><span class="pre">--with-vte-module-path</span></tt> to
 ./configure.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id33" id="defining-own-widget-styles-using-gtkrc-2-0" name="defining-own-widget-styles-using-gtkrc-2-0">Defining own widget styles using .gtkrc-2.0</a></h3>
+<div class="section" id="defining-own-widget-styles-using-gtkrc-2-0">
+<h3><a class="toc-backref" href="#id33">Defining own widget styles using .gtkrc-2.0</a></h3>
 <p>You can define your widget style for many of Geany's GUI parts. To
 do this, just edit your <tt class="docutils literal"><span class="pre">.gtkrc-2.0</span></tt> (usually found in your home
 directory on UNIX-like systems and in the etc subdirectory of your
@@ -999,10 +1000,10 @@ widget &quot;GeanyPrefsDialog&quot; style &quot;geanyStyle&quot;
 </pre>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id34" id="documents" name="documents">Documents</a></h2>
-<div class="section">
-<h3><a class="toc-backref" href="#id35" id="switching-between-documents" name="switching-between-documents">Switching between documents</a></h3>
+<div class="section" id="documents">
+<h2><a class="toc-backref" href="#id34">Documents</a></h2>
+<div class="section" id="switching-between-documents">
+<h3><a class="toc-backref" href="#id35">Switching between documents</a></h3>
 <p>The documents list and the editor tabs are two different ways
 to switch between documents using the mouse. When you hit the key
 combination to move between tabs, the order is determined by the tab
@@ -1010,14 +1011,14 @@ order. Its is not alphabetical as shown in the documents list
 (regardless of whether or not editor tabs are visible).</p>
 <p>The tabs can be positioned at the top, bottom, left, or right of the
 main editing window, by a selection in the interface preferences.</p>
-<p>See the <a class="reference" href="#notebook-tab-keybindings">Notebook tab keybindings</a> section for useful
+<p>See the <a class="reference internal" href="#notebook-tab-keybindings">Notebook tab keybindings</a> section for useful
 shortcuts including for Most-Recently-Used document switching.</p>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id36" id="character-sets-and-unicode-byte-order-mark-bom" name="character-sets-and-unicode-byte-order-mark-bom">Character sets and Unicode Byte-Order-Mark (BOM)</a></h2>
-<div class="section">
-<h3><a class="toc-backref" href="#id37" id="using-character-sets" name="using-character-sets">Using character sets</a></h3>
+<div class="section" id="character-sets-and-unicode-byte-order-mark-bom">
+<h2><a class="toc-backref" href="#id36">Character sets and Unicode Byte-Order-Mark (BOM)</a></h2>
+<div class="section" id="using-character-sets">
+<h3><a class="toc-backref" href="#id37">Using character sets</a></h3>
 <p>Geany provides support for detecting and converting character sets. So
 you can open and save files in different character sets, and even
 convert a file from one character set to another. To do this,
@@ -1063,8 +1064,8 @@ encoding when opening the file.</p>
 </li>
 </ul>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id38" id="in-file-encoding-specification" name="in-file-encoding-specification">In-file encoding specification</a></h3>
+<div class="section" id="in-file-encoding-specification">
+<h3><a class="toc-backref" href="#id38">In-file encoding specification</a></h3>
 <p>Geany detects meta tags of HTML files which contain charset information
 like:</p>
 <pre class="literal-block">
@@ -1091,7 +1092,7 @@ Then you simply add such a line to the file and Geany will open it
 correctly the next time.</p>
 <p>Since Geany 0.15 you can also use lines which match the
 regular expression used to find the encoding string:
-<tt class="docutils literal"><span class="pre">coding[\t</span> <span class="pre">]*[:=][\t</span> <span class="pre">]*([a-z0-9-]+)[\t</span> <span class="pre">]*</span></tt></p>
+<tt class="docutils literal"><span class="pre">coding[\t</span> <span class="pre">]*[:=][\t</span> <span class="pre">]*([a-z0-9-]+)[\t</span> ]*</tt></p>
 <div class="note">
 <p class="first admonition-title">Note</p>
 <p class="last">These specifications must be in the first 512 bytes of the file.
@@ -1106,8 +1107,8 @@ Anything after the first 512 bytes will not be recognized.</p>
 # coding: ISO-8859-15
 </pre>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id39" id="special-encoding-none" name="special-encoding-none">Special encoding &quot;None&quot;</a></h3>
+<div class="section" id="special-encoding-none">
+<h3><a class="toc-backref" href="#id39">Special encoding &quot;None&quot;</a></h3>
 <p>There is a special encoding &quot;None&quot; which uses no
 encoding. It is useful when you know that Geany cannot auto-detect
 the encoding of a file and it is not displayed correctly. Especially
@@ -1116,10 +1117,10 @@ detection and open the file properly at least until the occurrence
 of the first NULL-byte. Using this encoding opens the file as it is
 without any character conversion.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id40" id="unicode-byte-order-mark-bom" name="unicode-byte-order-mark-bom">Unicode Byte-Order-Mark (BOM)</a></h3>
+<div class="section" id="unicode-byte-order-mark-bom">
+<h3><a class="toc-backref" href="#id40">Unicode Byte-Order-Mark (BOM)</a></h3>
 <p>Furthermore, Geany detects a Unicode Byte Order Mark (see
-<a class="reference" href="http://en.wikipedia.org/wiki/Byte_Order_Mark">http://en.wikipedia.org/wiki/Byte_Order_Mark</a> for details). Of course,
+<a class="reference external" href="http://en.wikipedia.org/wiki/Byte_Order_Mark">http://en.wikipedia.org/wiki/Byte_Order_Mark</a> for details). Of course,
 this feature is only available if the opened file is in a Unicode
 encoding. The Byte Order Mark helps to detect the encoding of a file,
 e.g. whether it is UTF-16LE or UTF-16BE and so on. On Unix-like systems
@@ -1139,10 +1140,10 @@ safely ignore it.</p>
 </div>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id41" id="editing" name="editing">Editing</a></h2>
-<div class="section">
-<h3><a class="toc-backref" href="#id42" id="folding" name="folding">Folding</a></h3>
+<div class="section" id="editing">
+<h2><a class="toc-backref" href="#id41">Editing</a></h2>
+<div class="section" id="folding">
+<h3><a class="toc-backref" href="#id42">Folding</a></h3>
 <p>Geany provides basic code folding support. Folding means the ability to
 show and hide parts of the text in the current file. You can hide
 unimportant code sections and concentrate on the parts you are working on
@@ -1156,7 +1157,7 @@ fold points.</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
 <p class="last">You can customize the folding icon and line styles - see the
-filetypes.common <a class="reference" href="#folding-settings">Folding Settings</a>.</p>
+filetypes.common <a class="reference internal" href="#folding-settings">Folding Settings</a>.</p>
 </div>
 <p>If you don't like it or don't need it at all, you can simply disable
 folding support completely in the preferences dialog.</p>
@@ -1171,8 +1172,8 @@ key while clicking on a fold symbol. That means, if the &quot;Fold/Unfold all
 children of a fold point&quot; option is enabled, pressing Shift will disable
 it for this click and vice versa.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id43" id="column-mode-editing-rectangular-selections" name="column-mode-editing-rectangular-selections">Column mode editing (rectangular selections)</a></h3>
+<div class="section" id="column-mode-editing-rectangular-selections">
+<h3><a class="toc-backref" href="#id43">Column mode editing (rectangular selections)</a></h3>
 <p>There is basic support for column mode editing. To use it, create a
 rectangular selection by holding down the Control and Shift keys
 (or Control and Alt if it doesn't work) while
@@ -1181,18 +1182,18 @@ Once a rectangular selection exists you can start editing the text within
 this selection and the modifications will be done for every line in the
 selection.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id44" id="drag-and-drop-of-text" name="drag-and-drop-of-text">Drag and drop of text</a></h3>
+<div class="section" id="drag-and-drop-of-text">
+<h3><a class="toc-backref" href="#id44">Drag and drop of text</a></h3>
 <p>If you drag selected text in the editor widget of Geany the text is
 moved to the position where the mouse pointer is when releasing the
 mouse button. Holding Control when releasing the mouse button will
 copy the text instead. This behaviour was changed in Geany 0.11 -
 before the selected text was copied to the new position.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id45" id="indentation" name="indentation">Indentation</a></h3>
+<div class="section" id="indentation">
+<h3><a class="toc-backref" href="#id45">Indentation</a></h3>
 <p>Geany allows each document to indent either with a tab character or
-multiple spaces. The default indent mode is set in the <a class="reference" href="#editor-features-preferences">Editor Features
+multiple spaces. The default indent mode is set in the <a class="reference internal" href="#editor-features-preferences">Editor Features
 preferences</a> (see the link for more information). But
 this can be overridden using either the <em>Document-&gt;Indent Type</em> menu,
 or by using the <em>Detect from file</em> indentation preference. When enabled,
@@ -1210,8 +1211,8 @@ as follows:</p>
 on a line.</dd>
 </dl>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id46" id="auto-indentation" name="auto-indentation">Auto-indentation</a></h3>
+<div class="section" id="auto-indentation">
+<h3><a class="toc-backref" href="#id46">Auto-indentation</a></h3>
 <p>When enabled, auto-indentation happens when pressing <em>Enter</em> in the
 Editor. It adds a certain amount of indentation to the new line so the
 user doesn't always have to indent each line manually.</p>
@@ -1231,8 +1232,8 @@ previous line.</dd>
 match the indentation of the line with the opening brace.</dd>
 </dl>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id47" id="bookmarks" name="bookmarks">Bookmarks</a></h3>
+<div class="section" id="bookmarks">
+<h3><a class="toc-backref" href="#id47">Bookmarks</a></h3>
 <p>Geany provides a handy bookmarking feature that lets you mark one
 or more lines in a document, and return the cursor to them using a
 key combination.</p>
@@ -1249,14 +1250,14 @@ together with the commands to switch from one editor tab to another
 (Ctrl-PgUp/PgDn and Ctrl-Tab) provides a particularly fast way to
 navigate around multiple files.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id48" id="code-navigation-history" name="code-navigation-history">Code navigation history</a></h3>
+<div class="section" id="code-navigation-history">
+<h3><a class="toc-backref" href="#id48">Code navigation history</a></h3>
 <p>To ease navigation in source files and especially between
 different files, Geany lets you jump between different navigation
 points. Currently, this works for the following:</p>
 <ul class="simple">
-<li><a class="reference" href="#go-to-tag-declaration">Go to tag declaration</a></li>
-<li><a class="reference" href="#go-to-tag-definition">Go to tag definition</a></li>
+<li><a class="reference internal" href="#go-to-tag-declaration">Go to tag declaration</a></li>
+<li><a class="reference internal" href="#go-to-tag-definition">Go to tag definition</a></li>
 <li>Symbol list items</li>
 <li>Build errors</li>
 <li>Message items</li>
@@ -1268,8 +1269,8 @@ get back to the new position again, just use &quot;Navigate forward a
 location&quot;. This makes it easier to navigate in e.g.  foreign code
 and between different files.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id49" id="sending-text-through-custom-commands" name="sending-text-through-custom-commands">Sending text through custom commands</a></h3>
+<div class="section" id="sending-text-through-custom-commands">
+<h3><a class="toc-backref" href="#id49">Sending text through custom commands</a></h3>
 <p>You can define several custom commands in Geany and send the current
 selection to one of these commands using the <em>Edit-&gt;Format-&gt;Send
 Selection to</em> menu or keybindings. The output of the command will be
@@ -1288,22 +1289,22 @@ delete a command, just clear the text entry and press OK. It will be
 deleted automatically.</p>
 <p>Normal shell quoting is supported, so you can do things like:</p>
 <ul class="simple">
-<li><tt class="docutils literal"><span class="pre">sed</span> <span class="pre">'s/\./(dot)/g'</span></tt></li>
+<li><tt class="docutils literal">sed <span class="pre">'s/\./(dot)/g'</span></tt></li>
 </ul>
-<p>The above example would normally be done with the <a class="reference" href="#replace-all">Replace all</a>
+<p>The above example would normally be done with the <a class="reference internal" href="#replace-all">Replace all</a>
 function, but it can be handy to have common commands already set up.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id50" id="context-actions" name="context-actions">Context actions</a></h3>
+<div class="section" id="context-actions">
+<h3><a class="toc-backref" href="#id50">Context actions</a></h3>
 <p>You can execute the context action command on the current word at the
 cursor position or the available selection.  This word or selection
 can be used as an argument to the command.
 The context action is invoked by a menu entry in the popup menu of the
 editor and also a keyboard shortcut (see the section called
-<a class="reference" href="#keybindings">Keybindings</a>).</p>
+<a class="reference internal" href="#keybindings">Keybindings</a>).</p>
 <p>The command can be specified in the preferences dialog and also for
 each filetype (see &quot;context_action_cmd&quot; in the section called
-<a class="reference" href="#format">Format</a>). When the context action is invoked, the filetype
+<a class="reference internal" href="#format">Format</a>). When the context action is invoked, the filetype
 specific command is used if available, otherwise the command
 specified in the preferences dialog is executed.</p>
 <p>The current word or selection can be referred with the wildcard &quot;%s&quot;
@@ -1318,19 +1319,19 @@ firefox &quot;http://www.php.net/%s&quot;
 <p>when executing the command, the %s is substituted by the word near
 the cursor position or by the current selection. If the cursor is at
 the word &quot;echo&quot;, a browser window will open(assumed your browser is
-called firefox) and it will open the address: <a class="reference" href="http://www.php.net/echo">http://www.php.net/echo</a>.</p>
+called firefox) and it will open the address: <a class="reference external" href="http://www.php.net/echo">http://www.php.net/echo</a>.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id51" id="autocompletion" name="autocompletion">Autocompletion</a></h3>
+<div class="section" id="autocompletion">
+<h3><a class="toc-backref" href="#id51">Autocompletion</a></h3>
 <p>Geany can offer a list of possible completions for symbols defined in the
 tags and for all words in a document.</p>
 <p>The autocompletion list for symbols is presented when the first few
-characters of the symbol are typed (configurable, see <a class="reference" href="#editor-completions-preferences">Editor Completions
+characters of the symbol are typed (configurable, see <a class="reference internal" href="#editor-completions-preferences">Editor Completions
 preferences</a>, default 4) or when the <em>Complete word</em>
-keybinding is pressed (configurable, see <a class="reference" href="#editor-keybindings">Editor keybindings</a>,
+keybinding is pressed (configurable, see <a class="reference internal" href="#editor-keybindings">Editor keybindings</a>,
 default Ctrl-Space).</p>
 <p>When the defined keybinding is typed and the <em>Autocomplete all words in
-document</em> preference (in <a class="reference" href="#editor-completions-preferences">Editor Completions preferences</a>)
+document</em> preference (in <a class="reference internal" href="#editor-completions-preferences">Editor Completions preferences</a>)
 is selected then the autocompletion list will show all matching words
 in the document, if there are no matching symbols.</p>
 <p>If you don't want to use autocompletion it can be dismissed until
@@ -1342,13 +1343,13 @@ the autocompletion window is closed.</p>
 item on the autocompletion list can be chosen from the list by pressing
 Enter/Return. You can also double-click to select an item. The sequence
 will be completed to match the chosen item, and if the <em>Drop rest of
-word on completion</em> preference is set (in <a class="reference" href="#editor-completions-preferences">Editor Completions
+word on completion</em> preference is set (in <a class="reference internal" href="#editor-completions-preferences">Editor Completions
 preferences</a>) then any characters after the cursor that match
 a symbol or word are deleted.</p>
-<div class="section">
-<h4><a class="toc-backref" href="#id52" id="word-part-completion" name="word-part-completion">Word part completion</a></h4>
+<div class="section" id="word-part-completion">
+<h4><a class="toc-backref" href="#id52">Word part completion</a></h4>
 <p>By default, pressing Tab will complete the selected item by word part;
-useful e.g. for adding the prefix <tt class="docutils literal"><span class="pre">gtk_combo_box_entry_</span></tt> without typing it
+useful e.g. for adding the prefix <tt class="docutils literal">gtk_combo_box_entry_</tt> without typing it
 manually:</p>
 <ul class="simple">
 <li>gtk_com&lt;TAB&gt;</li>
@@ -1357,12 +1358,12 @@ manually:</p>
 <li>gtk_combo_box_entry_&lt;s&gt;&lt;ENTER&gt;</li>
 <li>gtk_combo_box_entry_set_text_column</li>
 </ul>
-<p>The key combination can be changed from Tab - See <a class="reference" href="#editor-keybindings">Editor keybindings</a>.
+<p>The key combination can be changed from Tab - See <a class="reference internal" href="#editor-keybindings">Editor keybindings</a>.
 If you clear/change the key combination for word part completion, Tab
 will complete the whole word instead, like Enter.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id53" id="scope-autocompletion" name="scope-autocompletion">Scope autocompletion</a></h4>
+<div class="section" id="scope-autocompletion">
+<h4><a class="toc-backref" href="#id53">Scope autocompletion</a></h4>
 <p>E.g.:</p>
 <pre class="literal-block">
 struct
@@ -1371,7 +1372,7 @@ struct
     char c;
 } foo;
 </pre>
-<p>When you type <tt class="docutils literal"><span class="pre">foo.</span></tt> it will show an autocompletion list with 'i' and
+<p>When you type <tt class="docutils literal">foo.</tt> it will show an autocompletion list with 'i' and
 'c' symbols.</p>
 <p>It only works for languages that set parent scope names for e.g. struct
 members. Currently this means C-like languages. The C tag parser only
@@ -1379,28 +1380,28 @@ parses global scopes, so this won't work for structs or objects declared
 in local scope.</p>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id54" id="user-definable-snippets" name="user-definable-snippets">User-definable snippets</a></h3>
+<div class="section" id="user-definable-snippets">
+<h3><a class="toc-backref" href="#id54">User-definable snippets</a></h3>
 <p>Snippets are small strings or code constructs which can be replaced or
 completed to a more complex string. So you can save a lot of time when
 typing common strings and letting Geany do the work for you.
 To know what to complete or replace Geany reads a configuration file
-called <tt class="docutils literal"><span class="pre">snippets.conf</span></tt> at startup.</p>
+called <tt class="docutils literal">snippets.conf</tt> at startup.</p>
 <p>Maybe you need to often type your name, so define a snippet like this:</p>
 <pre class="literal-block">
 [Default]
 myname=Enrico Tr��ger
 </pre>
-<p>Every time you write <tt class="docutils literal"><span class="pre">myname</span></tt> &lt;TAB&gt; in Geany, it will replace &quot;myname&quot;
+<p>Every time you write <tt class="docutils literal">myname</tt> &lt;TAB&gt; in Geany, it will replace &quot;myname&quot;
 with &quot;Enrico Tr��ger&quot;. The key to start autocompletion can be changed
 in the preferences dialog, by default it is TAB. The corresponding keybinding
-is called <tt class="docutils literal"><span class="pre">Complete</span> <span class="pre">snippet</span></tt>.</p>
+is called <tt class="docutils literal">Complete snippet</tt>.</p>
 <p><strong>Paths</strong></p>
 <p>The system-wide configuration file can be found in
-<tt class="docutils literal"><span class="pre">$prefix/share/geany</span></tt>, where <tt class="docutils literal"><span class="pre">$prefix</span></tt> is the path where Geany is
-installed (see <a class="reference" href="#installation-prefix">Installation prefix</a>). It is not recommended to edit the
+<tt class="docutils literal">$prefix/share/geany</tt>, where <tt class="docutils literal">$prefix</tt> is the path where Geany is
+installed (see <a class="reference internal" href="#installation-prefix">Installation prefix</a>). It is not recommended to edit the
 system-wide file, because it will be overridden when Geany is updated.</p>
-<p>To change the settings, copy the file from <tt class="docutils literal"><span class="pre">$prefix/share/geany</span></tt>
+<p>To change the settings, copy the file from <tt class="docutils literal">$prefix/share/geany</tt>
 in your configuration directory (usually <tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt>).</p>
 <p>For example:</p>
 <pre class="literal-block">
@@ -1411,16 +1412,16 @@ after an update of Geany because the file resides in your
 configuration directory. Alternatively, you can create a file
 <tt class="docutils literal"><span class="pre">~/.config/geany/snippets.conf</span></tt> and add only these settings you want
 to change. All missing settings will be read from the global snippets
-file in <tt class="docutils literal"><span class="pre">$prefix/share/geany</span></tt>.</p>
+file in <tt class="docutils literal">$prefix/share/geany</tt>.</p>
 <p><strong>Snippet groups</strong></p>
-<p>The file <tt class="docutils literal"><span class="pre">snippets.conf</span></tt> contains sections defining snippets that
+<p>The file <tt class="docutils literal">snippets.conf</tt> contains sections defining snippets that
 are available for particular filetypes and in general.</p>
 <p>The two sections &quot;Default&quot; and &quot;Special&quot; apply to all filetypes.
 &quot;Default&quot; contains all snippets which are available for every
 filetype and &quot;Special&quot; contains snippets which can only be used in
 other snippets. So you can define often used parts of snippets and
 just use the special snippet as a placeholder (see the
-<tt class="docutils literal"><span class="pre">snippets.conf</span></tt> for details).</p>
+<tt class="docutils literal">snippets.conf</tt> for details).</p>
 <p>You can define sections with the name of a filetype eg &quot;C++&quot;.  The
 snippets in that section are only available for use in files with that
 filetype.  Snippets in filetype sections will hide snippets with the
@@ -1450,7 +1451,7 @@ to the current document's indent mode.</td>
 <tr><td>%cursor%</td>
 <td>Place the cursor at this position after completion has
 been done. You can define multiple %cursor% wildcards
-and use the keybinding <tt class="docutils literal"><span class="pre">Move</span> <span class="pre">cursor</span> <span class="pre">in</span> <span class="pre">snippet</span></tt> to jump
+and use the keybinding <tt class="docutils literal">Move cursor in snippet</tt> to jump
 to the next defined cursor position in the completed
 snippet.</td>
 </tr>
@@ -1464,19 +1465,19 @@ section you can use %brace_open% in any other snippet.</td>
 <p>Snippet names must not contain spaces otherwise they won't
 work correctly. But beside that you can define almost any
 string as a snippet and use it later in Geany. It is not limited
-to existing contructs of certain programming languages(like <tt class="docutils literal"><span class="pre">if</span></tt>,
-<tt class="docutils literal"><span class="pre">for</span></tt>, <tt class="docutils literal"><span class="pre">switch</span></tt>). Define whatever you need.</p>
+to existing contructs of certain programming languages(like <tt class="docutils literal">if</tt>,
+<tt class="docutils literal">for</tt>, <tt class="docutils literal">switch</tt>). Define whatever you need.</p>
 <p><strong>Template wildcards</strong></p>
 <p>Since Geany 0.15 you can also use most of the available templates wildcards
-listed in <a class="reference" href="#template-wildcards">Template wildcards</a>. All wildcards which are listed as
+listed in <a class="reference internal" href="#template-wildcards">Template wildcards</a>. All wildcards which are listed as
 <cite>available in snippets</cite> can be used. For instance to improve the above example:</p>
 <pre class="literal-block">
 [Default]
 myname=My name is {developer}
 mysystem=My system: {command:uname -a}
 </pre>
-<p>this will replace <tt class="docutils literal"><span class="pre">myname</span></tt> with &quot;My name is &quot; and the value of the template
-preference <tt class="docutils literal"><span class="pre">developer</span></tt>.</p>
+<p>this will replace <tt class="docutils literal">myname</tt> with &quot;My name is &quot; and the value of the template
+preference <tt class="docutils literal">developer</tt>.</p>
 <p><strong>Word characters</strong></p>
 <p>You can change the way Geany recognizes the word to complete,
 that is how the start and end of a word is recognised when the
@@ -1485,11 +1486,11 @@ contain a key &quot;wordchars&quot; which lists all characters a string may cont
 to be recognized as a word for completion. Leave it commented to use
 default characters or define it to add or remove characters to fit your
 needs.</p>
-<div class="section">
-<h4><a class="toc-backref" href="#id55" id="snippet-keybindings" name="snippet-keybindings">Snippet keybindings</a></h4>
+<div class="section" id="snippet-keybindings">
+<h4><a class="toc-backref" href="#id55">Snippet keybindings</a></h4>
 <p>Normally you would type the snippet name and press Tab. However, you
 can define keybindings for snippets under the <em>Keybindings</em> group in
-<tt class="docutils literal"><span class="pre">snippets.conf</span></tt>:</p>
+<tt class="docutils literal">snippets.conf</tt>:</p>
 <pre class="literal-block">
 [Keybindings]
 for=&lt;Ctrl&gt;7
@@ -1502,8 +1503,8 @@ keybindings.</p>
 </div>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id56" id="inserting-unicode-characters" name="inserting-unicode-characters">Inserting Unicode characters</a></h3>
+<div class="section" id="inserting-unicode-characters">
+<h3><a class="toc-backref" href="#id56">Inserting Unicode characters</a></h3>
 <p>With GTK 2.10 and above, you can insert Unicode code points by hitting
 Ctrl-Shift-u, then still holding Ctrl-Shift, type some hex digits representing
 the code point for the character you want and hit Enter or Return (still
@@ -1512,7 +1513,7 @@ holding Ctrl-Shift). If you release Ctrl-Shift before hitting Enter or Return
 character is also entered.  In the case of Enter/Return, it is a newline, as
 you might expect.</p>
 <p>In some earlier versions of Geany, you might need to first unbind Ctrl-Shift-u
-in the <a class="reference" href="#keybinding-preferences">keybinding preferences</a>, then select <em>Tools-&gt;Reload Configuration</em>
+in the <a class="reference internal" href="#keybinding-preferences">keybinding preferences</a>, then select <em>Tools-&gt;Reload Configuration</em>
 or restart Geany. Note that it works slightly differently from other GTK
 applications, in that you'll need to continue to hold down the Ctrl and Shift
 keys while typing the code point hex digits (and the Enter or Return to finish the code point).</p>
@@ -1521,8 +1522,8 @@ is not necessary. One problem is that you may find the alphabetic
 keys conflict with other Geany keybindings.</p>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id57" id="search-replace-and-go-to" name="search-replace-and-go-to">Search, replace and go to</a></h2>
+<div class="section" id="search-replace-and-go-to">
+<h2><a class="toc-backref" href="#id57">Search, replace and go to</a></h2>
 <p>This section describes search-related commands from the Search menu
 and the editor window's popup menu:</p>
 <ul class="simple">
@@ -1535,30 +1536,30 @@ and the editor window's popup menu:</p>
 <li>Go to tag declaration</li>
 <li>Go to line</li>
 </ul>
-<div class="section">
-<h3><a class="toc-backref" href="#id58" id="toolbar-entries" name="toolbar-entries">Toolbar entries</a></h3>
+<div class="section" id="toolbar-entries">
+<h3><a class="toc-backref" href="#id58">Toolbar entries</a></h3>
 <p>There are also two toolbar entries:</p>
 <ul class="simple">
 <li>Search bar</li>
 <li>Go to line entry</li>
 </ul>
-<p>There are keybindings to focus each of these - see <a class="reference" href="#focus-keybindings">Focus
+<p>There are keybindings to focus each of these - see <a class="reference internal" href="#focus-keybindings">Focus
 keybindings</a>. Pressing Escape will then focus the editor.</p>
-<div class="section">
-<h4><a class="toc-backref" href="#id59" id="search-bar" name="search-bar">Search bar</a></h4>
+<div class="section" id="search-bar">
+<h4><a class="toc-backref" href="#id59">Search bar</a></h4>
 <p>The quickest way to find some text is to use the search bar entry in
 the toolbar. This performs a case-insensitive search in the current
 document whilst you type. Pressing Enter will search again.</p>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id60" id="find" name="find">Find</a></h3>
+<div class="section" id="find">
+<h3><a class="toc-backref" href="#id60">Find</a></h3>
 <p>The Find dialog is used for finding text in one or more open documents.</p>
 <img alt="./images/find_dialog.png" src="./images/find_dialog.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id61" id="matching-options" name="matching-options">Matching options</a></h4>
+<div class="section" id="matching-options">
+<h4><a class="toc-backref" href="#id61">Matching options</a></h4>
 <p>The syntax for the <em>Use regular expressions</em> option is shown in
-<a class="reference" href="#regular-expressions">Regular expressions</a>.</p>
+<a class="reference internal" href="#regular-expressions">Regular expressions</a>.</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
 <p class="last"><em>Use escape sequences</em> is implied for regular expressions.</p>
@@ -1568,8 +1569,8 @@ into their UTF-8 equivalent. For example, \t will be transformed into
 a tab character. Other recognized symbols are: \\, \n, \r, \uXXXX
 (Unicode characters).</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id62" id="find-all" name="find-all">Find all</a></h4>
+<div class="section" id="find-all">
+<h4><a class="toc-backref" href="#id62">Find all</a></h4>
 <p>To find all matches, click on the Find All expander. This will reveal
 several options:</p>
 <ul class="simple">
@@ -1584,8 +1585,8 @@ In Session</em> does the same for all open documents.</p>
 colored box. These markers can be removed by selecting the
 Remove Markers command from the Document menu.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id63" id="change-font-in-search-dialog-text-fields" name="change-font-in-search-dialog-text-fields">Change font in search dialog text fields</a></h4>
+<div class="section" id="change-font-in-search-dialog-text-fields">
+<h4><a class="toc-backref" href="#id63">Change font in search dialog text fields</a></h4>
 <p>All search related dialogs use a Monospace for the text input fields to
 increase the readability of input text. This is useful when you are
 typing input such as regular expressions with spaces, periods and commas which
@@ -1606,12 +1607,12 @@ of this style to the highest available. Otherwise, the style is ignored
 for the search dialogs.</p>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id64" id="find-selection" name="find-selection">Find selection</a></h3>
+<div class="section" id="find-selection">
+<h3><a class="toc-backref" href="#id64">Find selection</a></h3>
 <p>The <em>Find Next/Previous Selection</em> commands perform a search for the
 current selected text. If nothing is selected, by default the current
 word is used instead. This can be customized by the
-<em>find_selection_type</em> hidden pref - see <a class="reference" href="#hidden-preferences">Hidden preferences</a>.</p>
+<em>find_selection_type</em> hidden pref - see <a class="reference internal" href="#hidden-preferences">Hidden preferences</a>.</p>
 <table border="1" class="docutils">
 <colgroup>
 <col width="10%" />
@@ -1635,8 +1636,8 @@ word is used instead. This can be customized by the
 </tbody>
 </table>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id65" id="find-usage" name="find-usage">Find usage</a></h3>
+<div class="section" id="find-usage">
+<h3><a class="toc-backref" href="#id65">Find usage</a></h3>
 <p>Find usage searches all open files. It is similar to the Find All In
 Session option in the Find dialog.</p>
 <p>If there is a selection, then it is used as the search text; otherwise
@@ -1645,8 +1646,8 @@ word nearest the edit cursor, or the word underneath the popup menu
 click position when the popup menu is used. The search results are
 shown in the Messages tab of the Message Window.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id66" id="find-in-files" name="find-in-files">Find in files</a></h3>
+<div class="section" id="find-in-files">
+<h3><a class="toc-backref" href="#id66">Find in files</a></h3>
 <p>Find in files is a more powerful version of Find usage that searches
 all files in a certain directory using the Grep tool. The Grep tool
 must be correctly set in Preferences to the path of the system's Grep
@@ -1654,7 +1655,7 @@ utility. GNU Grep is recommended (see note below).</p>
 <img alt="./images/find_in_files_dialog.png" src="./images/find_in_files_dialog.png" />
 <p>The <em>Files</em> field optionally searches only files matching the
 patterns listed. Patterns are basic and shell-like, separated by a
-space. To search all <tt class="docutils literal"><span class="pre">.c</span></tt> and <tt class="docutils literal"><span class="pre">.h</span></tt> files, use: <tt class="docutils literal"><span class="pre">*.c</span> <span class="pre">*.h</span></tt>.</p>
+space. To search all <tt class="docutils literal">.c</tt> and <tt class="docutils literal">.h</tt> files, use: <tt class="docutils literal">*.c *.h</tt>.</p>
 <p>The <em>Encoding</em> field can be used to define the encoding of the files
 to be searched. The entered search text is converted to the chosen encoding
 and the search results are converted back to UTF-8.</p>
@@ -1666,13 +1667,13 @@ the grep tool.</p>
 uses <tt class="docutils literal"><span class="pre">-r</span></tt>; both are GNU Grep options and may not work with other
 Grep implementations.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id67" id="filtering-out-version-control-files" name="filtering-out-version-control-files">Filtering out version control files</a></h4>
+<div class="section" id="filtering-out-version-control-files">
+<h4><a class="toc-backref" href="#id67">Filtering out version control files</a></h4>
 <p>When using the <em>Recurse in subfolders</em> option with a directory that's
 under version control, you can set the <em>Extra options</em> field to filter
 out version control files.</p>
 <p>If you have GNU Grep &gt;= 2.5.2 you can use the <tt class="docutils literal"><span class="pre">--exclude-dir</span></tt>
-argument to filter out CVS and hidden directories like <tt class="docutils literal"><span class="pre">.svn</span></tt>.</p>
+argument to filter out CVS and hidden directories like <tt class="docutils literal">.svn</tt>.</p>
 <p>Example: <tt class="docutils literal"><span class="pre">--exclude-dir=.svn</span> <span class="pre">--exclude-dir=CVS</span></tt></p>
 <p>If you have an older Grep, you can try using the <tt class="docutils literal"><span class="pre">--exclude</span></tt> flag
 to filter out filenames.</p>
@@ -1680,18 +1681,18 @@ to filter out filenames.</p>
 <p>The --exclude argument only matches the file name part, not the path.</p>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id68" id="replace" name="replace">Replace</a></h3>
+<div class="section" id="replace">
+<h3><a class="toc-backref" href="#id68">Replace</a></h3>
 <p>The Replace dialog is used for replacing text in one or more open
 documents.</p>
 <img alt="./images/replace_dialog.png" src="./images/replace_dialog.png" />
 <p>The Replace dialog has the same options for matching text as the Find
-dialog. See the section <a class="reference" href="#matching-options">Matching options</a>.</p>
+dialog. See the section <a class="reference internal" href="#matching-options">Matching options</a>.</p>
 <p>The <em>Use regular expressions</em> option allows regular expressions to
 be used in the search string and back references in the replacement
-text -- see the entry for '\n' in <a class="reference" href="#regular-expressions">Regular expressions</a>.</p>
-<div class="section">
-<h4><a class="toc-backref" href="#id69" id="replace-all" name="replace-all">Replace all</a></h4>
+text -- see the entry for '\n' in <a class="reference internal" href="#regular-expressions">Regular expressions</a>.</p>
+<div class="section" id="replace-all">
+<h4><a class="toc-backref" href="#id69">Replace all</a></h4>
 <p>To replace several matches, click on the <em>Replace All</em> expander. This
 will reveal several options:</p>
 <ul class="simple">
@@ -1705,8 +1706,8 @@ documents. <em>Replace All In Selection</em> will replace all matching text
 in the current selection of the current document.</p>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id70" id="go-to-tag-definition" name="go-to-tag-definition">Go to tag definition</a></h3>
+<div class="section" id="go-to-tag-definition">
+<h3><a class="toc-backref" href="#id70">Go to tag definition</a></h3>
 <p>If the current word is the name of a tag definition (like a function
 body) and the file containing the tag definition is open, this command
 will switch to that file and go to the corresponding line number. The
@@ -1714,20 +1715,20 @@ current word is either the word nearest the edit cursor,
 or the word underneath the popup menu click position when the popup
 menu is used.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id71" id="go-to-tag-declaration" name="go-to-tag-declaration">Go to tag declaration</a></h3>
+<div class="section" id="go-to-tag-declaration">
+<h3><a class="toc-backref" href="#id71">Go to tag declaration</a></h3>
 <p>Like Go to tag definition, but for a forward declaration such as a
-C function prototype or <tt class="docutils literal"><span class="pre">extern</span></tt> declaration instead of a function
+C function prototype or <tt class="docutils literal">extern</tt> declaration instead of a function
 body.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id72" id="go-to-line" name="go-to-line">Go to line</a></h3>
+<div class="section" id="go-to-line">
+<h3><a class="toc-backref" href="#id72">Go to line</a></h3>
 <p>Go to a particular line number in the current file.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id73" id="regular-expressions" name="regular-expressions">Regular expressions</a></h3>
+<div class="section" id="regular-expressions">
+<h3><a class="toc-backref" href="#id73">Regular expressions</a></h3>
 <p>You can use regular expressions in the Find and Replace dialogs
-by selecting the <em>Use regular expressions</em> check box (see <a class="reference" href="#matching-options">Matching
+by selecting the <em>Use regular expressions</em> check box (see <a class="reference internal" href="#matching-options">Matching
 options</a>). The syntax is POSIX compatible, as described in the table
 below.</p>
 <div class="note">
@@ -1834,32 +1835,32 @@ Saam, Saaam and so on.</td>
 <div class="note">
 <p class="first admonition-title">Note</p>
 <p class="last">This table is adapted from Scintilla and SciTE documentation,
-distributed under the <a class="reference" href="#license-for-scintilla-and-scite">License for Scintilla and SciTE</a>.</p>
+distributed under the <a class="reference internal" href="#license-for-scintilla-and-scite">License for Scintilla and SciTE</a>.</p>
 </div>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id74" id="tags" name="tags">Tags</a></h2>
+<div class="section" id="tags">
+<h2><a class="toc-backref" href="#id74">Tags</a></h2>
 <p>Tags are information that relates symbols in a program with the
 source file location of the declaration and definition.</p>
 <p>Geany has built-in functionality for generating tag information (aka
 &quot;workspace tags&quot;) for supported filetypes when you open a file.  You
 can also have Geany automatically load external tag files (aka &quot;global
 tags files&quot;) upon startup, or manually using <em>Tools --&gt; Load Tags</em>.</p>
-<p>Geany uses its own tag file format, similar to what <tt class="docutils literal"><span class="pre">ctags</span></tt> uses
+<p>Geany uses its own tag file format, similar to what <tt class="docutils literal">ctags</tt> uses
 (but is incompatible with ctags). You use Geany to generate global
 tags files, as described below.</p>
-<div class="section">
-<h3><a class="toc-backref" href="#id75" id="workspace-tags" name="workspace-tags">Workspace tags</a></h3>
+<div class="section" id="workspace-tags">
+<h3><a class="toc-backref" href="#id75">Workspace tags</a></h3>
 <p>Tags for each document are parsed whenever a file is loaded or
 saved. These are shown in the Symbol list in the Sidebar. These tags
 are also used for autocompletion of symbols and calltips for all documents
 open in the current session that have the same filetype.</p>
 <p>The <em>Go to Tag</em> commands can be used with all workspace tags. See
-<a class="reference" href="#go-to-tag-definition">Go to tag definition</a>.</p>
+<a class="reference internal" href="#go-to-tag-definition">Go to tag definition</a>.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id76" id="global-tags" name="global-tags">Global tags</a></h3>
+<div class="section" id="global-tags">
+<h3><a class="toc-backref" href="#id76">Global tags</a></h3>
 <p>Global tags are used to provide autocompletion of symbols and calltips
 without having to open the corresponding source files. This is intended
 for library APIs, as the tags file only has to be updated when you upgrade
@@ -1869,9 +1870,9 @@ the library.</p>
 <li>Using the <em>Load Tags</em> command in the Tools menu.</li>
 <li>By creating a directory <tt class="docutils literal"><span class="pre">~/.config/geany/tags</span></tt>, and moving or symlinking
 the tags files there before starting Geany.</li>
-<li>By creating a directory <tt class="docutils literal"><span class="pre">$prefix/share/geany/tags</span></tt>, and moving
+<li>By creating a directory <tt class="docutils literal">$prefix/share/geany/tags</tt>, and moving
 or symlinking the tags files there before starting Geany.
-<tt class="docutils literal"><span class="pre">$prefix</span></tt> is the installation prefix (see <a class="reference" href="#installation-prefix">Installation prefix</a>).</li>
+<tt class="docutils literal">$prefix</tt> is the installation prefix (see <a class="reference internal" href="#installation-prefix">Installation prefix</a>).</li>
 </ul>
 <p>You can either download these files or generate your own. They have
 the format:</p>
@@ -1879,10 +1880,10 @@ the format:</p>
 name.lang_ext.tags
 </pre>
 <p><em>lang_ext</em> is one of the extensions set for the filetype associated
-with the tags. See the section called <a class="reference" href="#filetype-extensions">Filetype extensions</a> for
+with the tags. See the section called <a class="reference internal" href="#filetype-extensions">Filetype extensions</a> for
 more information.</p>
-<div class="section">
-<h4><a class="toc-backref" href="#id77" id="default-global-tags-files" name="default-global-tags-files">Default global tags files</a></h4>
+<div class="section" id="default-global-tags-files">
+<h4><a class="toc-backref" href="#id77">Default global tags files</a></h4>
 <p>For some languages, a list of global tags is loaded when the
 corresponding filetype is first used. Currently these are for:</p>
 <ul class="simple">
@@ -1894,27 +1895,27 @@ corresponding filetype is first used. Currently these are for:</p>
 <li>Python</li>
 </ul>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id78" id="global-tags-file-format" name="global-tags-file-format">Global tags file format</a></h4>
+<div class="section" id="global-tags-file-format">
+<h4><a class="toc-backref" href="#id78">Global tags file format</a></h4>
 <p>Global tags files can have two different formats:</p>
 <ul class="simple">
 <li>Tagmanager format</li>
 <li>Pipe-separated format</li>
 </ul>
 <p>The first line of global tags files should be a comment, introduced
-by <tt class="docutils literal"><span class="pre">#</span></tt> followed by a space and a string like <tt class="docutils literal"><span class="pre">format=pipe</span></tt>
-or <tt class="docutils literal"><span class="pre">format=tagmanager</span></tt> respectively, these are case-sensitive.
+by <tt class="docutils literal">#</tt> followed by a space and a string like <tt class="docutils literal">format=pipe</tt>
+or <tt class="docutils literal">format=tagmanager</tt> respectively, these are case-sensitive.
 This helps Geany to read the file properly. If this line
 is missing, Geany tries to auto-detect the used format but this
 might fail.</p>
 <p>The Tagmanager format is a bit more complex and is used for files
-created by the <tt class="docutils literal"><span class="pre">geany</span> <span class="pre">-g</span></tt> command. There is one tag per line.
+created by the <tt class="docutils literal">geany <span class="pre">-g</span></tt> command. There is one tag per line.
 Different tag attributes like the return value or the argument list
 are separated with different characters indicating the type of the
 following argument.</p>
 <p>The Pipe-separated format is easier to read and write.
 There is one tag per line and different tag attributes are separated
-by the pipe character (<tt class="docutils literal"><span class="pre">|</span></tt>). A line looks like:</p>
+by the pipe character (<tt class="docutils literal">|</tt>). A line looks like:</p>
 <pre class="literal-block">
 basename|string|(string path [, string suffix])|
 </pre>
@@ -1929,10 +1930,10 @@ currently unused and should be left empty.</div>
 empty but the pipe separator must appear for them.</p>
 <p>You can easily write your own global tag files using this format.
 Just save them in your tags directory, as described earlier in the
-section <a class="reference" href="#global-tags">Global tags</a>.</p>
+section <a class="reference internal" href="#global-tags">Global tags</a>.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id79" id="generating-a-global-tags-file" name="generating-a-global-tags-file">Generating a global tags file</a></h4>
+<div class="section" id="generating-a-global-tags-file">
+<h4><a class="toc-backref" href="#id79">Generating a global tags file</a></h4>
 <p>You can generate your own global tags files by parsing a list of
 source files. The command is:</p>
 <pre class="literal-block">
@@ -1940,12 +1941,12 @@ geany -g [-P] &lt;Tag File&gt; &lt;File list&gt;
 </pre>
 <ul class="simple">
 <li>Tag File filename should be in the format described earlier --
-see the section called <a class="reference" href="#global-tags">Global tags</a>.</li>
+see the section called <a class="reference internal" href="#global-tags">Global tags</a>.</li>
 <li>File list is a list of filenames, each with a full path (unless
 you are generating C/C++ tags and have set the CFLAGS environment
 variable appropriately).</li>
 <li><tt class="docutils literal"><span class="pre">-P</span></tt> or <tt class="docutils literal"><span class="pre">--no-preprocessing</span></tt> disables using the C pre-processor
-to process <tt class="docutils literal"><span class="pre">#include</span></tt> directives for C/C++ source files. Use this
+to process <tt class="docutils literal">#include</tt> directives for C/C++ source files. Use this
 option if you want to specify each source file on the command-line
 instead of using a 'master' header file. Also can be useful if you
 don't want to specify the CFLAGS environment variable.</li>
@@ -1976,8 +1977,8 @@ copy of the generated tags file because it will get overwritten when
 upgrading Geany.</p>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id80" id="ignore-tags" name="ignore-tags">Ignore tags</a></h3>
+<div class="section" id="ignore-tags">
+<h3><a class="toc-backref" href="#id80">Ignore tags</a></h3>
 <p>You can also ignore certain tags if they would lead to wrong parsing of
 the code. Simply create a file called &quot;ignore.tags&quot; in your Geany
 configuration directory (usually <tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt>). Then list all tags
@@ -2000,8 +2001,8 @@ identifiers is replaced by the second identifiers for parsing purposes.
 Exuberant Ctags.</p>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id81" id="preferences" name="preferences">Preferences</a></h2>
+<div class="section" id="preferences">
+<h2><a class="toc-backref" href="#id81">Preferences</a></h2>
 <p>You may adjust Geany's settings using the Edit --&gt; Preferences
 dialog. Any changes you make there can be applied by hitting either
 the Apply or the OK button. These settings will persist between Geany
@@ -2012,17 +2013,17 @@ on it.</p>
 persist between Geany sessions. The settings under the Document menu,
 however, are only for the current document and revert to defaults
 when restarting Geany.</p>
-<p>There are also some rarer <a class="reference" href="#hidden-preferences">Hidden preferences</a>.</p>
+<p>There are also some rarer <a class="reference internal" href="#hidden-preferences">Hidden preferences</a>.</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
 <p class="last">In the paragraphs that follow, the text describing a dialog tab
 comes after the screenshot of that tab.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id82" id="general-startup-preferences" name="general-startup-preferences">General Startup preferences</a></h3>
+<div class="section" id="general-startup-preferences">
+<h3><a class="toc-backref" href="#id82">General Startup preferences</a></h3>
 <img alt="./images/pref_dialog_gen_startup.png" src="./images/pref_dialog_gen_startup.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id83" id="id1" name="id1">Startup</a></h4>
+<div class="section" id="id1">
+<h4><a class="toc-backref" href="#id83">Startup</a></h4>
 <dl class="docutils">
 <dt>Load files from the last session</dt>
 <dd>On startup, load the same files you had open the last time you
@@ -2033,8 +2034,8 @@ used Geany.</dd>
 <dd>Allow plugins to be used in Geany.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id84" id="shutdown" name="shutdown">Shutdown</a></h4>
+<div class="section" id="shutdown">
+<h4><a class="toc-backref" href="#id84">Shutdown</a></h4>
 <dl class="docutils">
 <dt>Save window position and geometry</dt>
 <dd>Save the current position and size of the main window so next time
@@ -2043,8 +2044,8 @@ you open Geany it's in the same location.</dd>
 <dd>Have a dialog pop up to confirm that you really want to quit Geany.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id85" id="paths" name="paths">Paths</a></h4>
+<div class="section" id="paths">
+<h4><a class="toc-backref" href="#id85">Paths</a></h4>
 <dl class="docutils">
 <dt>Startup path</dt>
 <dd>Path to start in when opening or saving files.
@@ -2062,11 +2063,11 @@ Leave blank to not set an additional lookup path.</dd>
 </dl>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id86" id="general-miscellaneous-preferences" name="general-miscellaneous-preferences">General Miscellaneous preferences</a></h3>
+<div class="section" id="general-miscellaneous-preferences">
+<h3><a class="toc-backref" href="#id86">General Miscellaneous preferences</a></h3>
 <img alt="./images/pref_dialog_gen_misc.png" src="./images/pref_dialog_gen_misc.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id87" id="miscellaneous" name="miscellaneous">Miscellaneous</a></h4>
+<div class="section" id="miscellaneous">
+<h4><a class="toc-backref" href="#id87">Miscellaneous</a></h4>
 <dl class="docutils">
 <dt>Beep on errors when compilation has finished</dt>
 <dd>Have the computer make a beeping sound when compilation of your program
@@ -2077,10 +2078,10 @@ once a new status message arrives.</dd>
 <dt>Suppress status messages in the status bar</dt>
 <dd><p class="first">Remove all messages from the status bar. The messages are still displayed
 in the status messages window.</p>
-<div class="last tip">
+<div class="tip last">
 <p class="first admonition-title">Tip</p>
 <p class="last">Another option is to use the <em>Switch to Editor</em> keybinding - it
-reshows the document statistics on the status bar. See <a class="reference" href="#focus-keybindings">Focus
+reshows the document statistics on the status bar. See <a class="reference internal" href="#focus-keybindings">Focus
 keybindings</a>.</p>
 </div>
 </dd>
@@ -2093,8 +2094,8 @@ This works for the main editor widget, the scribble, the toolbar search field
 goto line fields and the VTE.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id88" id="search" name="search">Search</a></h4>
+<div class="section" id="search">
+<h4><a class="toc-backref" href="#id88">Search</a></h4>
 <dl class="docutils">
 <dt>Always wrap search and hide the Find dialog</dt>
 <dd>Always wrap search around the document and hide the Find dialog after clicking
@@ -2109,8 +2110,8 @@ active file. When this option is disabled, the directory of the last use of the
 dialog is used.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id89" id="projects" name="projects">Projects</a></h4>
+<div class="section" id="projects">
+<h4><a class="toc-backref" href="#id89">Projects</a></h4>
 <dl class="docutils">
 <dt>Use project-based session files</dt>
 <dd>Save your current session when closing projects. You will be able to
@@ -2126,11 +2127,11 @@ defaults automatically for convenience.</dd>
 </dl>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id90" id="interface-preferences" name="interface-preferences">Interface preferences</a></h3>
+<div class="section" id="interface-preferences">
+<h3><a class="toc-backref" href="#id90">Interface preferences</a></h3>
 <img alt="./images/pref_dialog_interface.png" src="./images/pref_dialog_interface.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id91" id="sidebar" name="sidebar">Sidebar</a></h4>
+<div class="section" id="sidebar">
+<h4><a class="toc-backref" href="#id91">Sidebar</a></h4>
 <dl class="docutils">
 <dt>Show sidebar</dt>
 <dd>Whether to show the sidebar at all.</dd>
@@ -2139,14 +2140,14 @@ defaults automatically for convenience.</dd>
 current document you are editing.</dd>
 <dt>Show documents list</dt>
 <dd>Show all the documents you have open currently. This can be used to
-change between documents (see <a class="reference" href="#switching-between-documents">Switching between documents</a>) and
+change between documents (see <a class="reference internal" href="#switching-between-documents">Switching between documents</a>) and
 to perform some common operations such as saving, closing and reloading.</dd>
 <dt>Position</dt>
 <dd>Whether to place the sidebar on the left or right of the editor window.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id92" id="fonts" name="fonts">Fonts</a></h4>
+<div class="section" id="fonts">
+<h4><a class="toc-backref" href="#id92">Fonts</a></h4>
 <dl class="docutils">
 <dt>Editor</dt>
 <dd>Change the font used to display documents.</dd>
@@ -2156,8 +2157,8 @@ to perform some common operations such as saving, closing and reloading.</dd>
 <dd>Change the font used for the message window area.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id93" id="editor-tabs" name="editor-tabs">Editor tabs</a></h4>
+<div class="section" id="editor-tabs">
+<h4><a class="toc-backref" href="#id93">Editor tabs</a></h4>
 <dl class="docutils">
 <dt>Show editor tabs</dt>
 <dd>Show a notebook tab for all documents so you can switch between them
@@ -2176,8 +2177,8 @@ rather than at the edges of the notebook.</dd>
 when double-clicking on a notebook tab.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id94" id="tab-positions" name="tab-positions">Tab positions</a></h4>
+<div class="section" id="tab-positions">
+<h4><a class="toc-backref" href="#id94">Tab positions</a></h4>
 <dl class="docutils">
 <dt>Editor</dt>
 <dd>Set the positioning of the editor's notebook tabs to the right,
@@ -2190,8 +2191,8 @@ left, top, or bottom of the sidebar window.</dd>
 right, left, top, or bottom of the message window.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id95" id="id2" name="id2">Miscellaneous</a></h4>
+<div class="section" id="id2">
+<h4><a class="toc-backref" href="#id95">Miscellaneous</a></h4>
 <dl class="docutils">
 <dt>Show status bar</dt>
 <dd>Show the status bar at the bottom of the main window. It gives information about
@@ -2200,12 +2201,12 @@ modifications were done, the file encoding, the filetype and other information.<
 </dl>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id96" id="toolbar-preferences" name="toolbar-preferences">Toolbar preferences</a></h3>
+<div class="section" id="toolbar-preferences">
+<h3><a class="toc-backref" href="#id96">Toolbar preferences</a></h3>
 <p>Affects the main toolbar underneath the menu bar.</p>
 <img alt="./images/pref_dialog_toolbar.png" src="./images/pref_dialog_toolbar.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id97" id="toolbar" name="toolbar">Toolbar</a></h4>
+<div class="section" id="toolbar">
+<h4><a class="toc-backref" href="#id97">Toolbar</a></h4>
 <dl class="docutils">
 <dt>Show Toolbar</dt>
 <dd>Whether to show the toolbar.</dd>
@@ -2213,11 +2214,11 @@ modifications were done, the file encoding, the filetype and other information.<
 <dd>Allows to append the toolbar to the main menu bar instead of placing it below.
 This is useful to save vertical space.</dd>
 <dt>Customize Toolbar</dt>
-<dd>See <a class="reference" href="#customizing-the-toolbar">Customizing the toolbar</a>.</dd>
+<dd>See <a class="reference internal" href="#customizing-the-toolbar">Customizing the toolbar</a>.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id98" id="appearance" name="appearance">Appearance</a></h4>
+<div class="section" id="appearance">
+<h4><a class="toc-backref" href="#id98">Appearance</a></h4>
 <dl class="docutils">
 <dt>Icon Style</dt>
 <dd>Select the toolbar icon style to use - either icons and text, just
@@ -2229,11 +2230,11 @@ The choice System default uses whatever icon size is set by GTK.</dd>
 </dl>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id99" id="editor-features-preferences" name="editor-features-preferences">Editor Features preferences</a></h3>
+<div class="section" id="editor-features-preferences">
+<h3><a class="toc-backref" href="#id99">Editor Features preferences</a></h3>
 <img alt="./images/pref_dialog_edit_features.png" src="./images/pref_dialog_edit_features.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id100" id="features" name="features">Features</a></h4>
+<div class="section" id="features">
+<h4><a class="toc-backref" href="#id100">Features</a></h4>
 <dl class="docutils">
 <dt>Line wrapping</dt>
 <dd>Show long lines wrapped around to new display lines.</dd>
@@ -2264,12 +2265,12 @@ It is used to mark the comment as toggled.</dd>
 </dl>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id101" id="editor-indentation-preferences" name="editor-indentation-preferences">Editor Indentation preferences</a></h3>
+<div class="section" id="editor-indentation-preferences">
+<h3><a class="toc-backref" href="#id101">Editor Indentation preferences</a></h3>
 <img alt="./images/pref_dialog_edit_indentation.png" src="./images/pref_dialog_edit_indentation.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id102" id="indentation-group" name="indentation-group">Indentation group</a></h4>
-<p>See <a class="reference" href="#indentation">Indentation</a> for more information.</p>
+<div class="section" id="indentation-group">
+<h4><a class="toc-backref" href="#id102">Indentation group</a></h4>
+<p>See <a class="reference internal" href="#indentation">Indentation</a> for more information.</p>
 <dl class="docutils">
 <dt>Type</dt>
 <dd><p class="first">When Geany inserts indentation, whether to use:</p>
@@ -2295,10 +2296,10 @@ if any.</p>
 <dd>Just add the indentation of the previous line.</dd>
 <dt>Current chars</dt>
 <dd>Add indentation based on the current filetype and any characters at
-the end of the line such as <tt class="docutils literal"><span class="pre">{</span></tt>, <tt class="docutils literal"><span class="pre">}</span></tt> for C, <tt class="docutils literal"><span class="pre">:</span></tt> for Python.</dd>
+the end of the line such as <tt class="docutils literal">{</tt>, <tt class="docutils literal">}</tt> for C, <tt class="docutils literal">:</tt> for Python.</dd>
 <dt>Match braces</dt>
 <dd>Like <em>Current chars</em> but for C-like languages, make a closing
-<tt class="docutils literal"><span class="pre">}</span></tt> brace line up with the matching opening brace.</dd>
+<tt class="docutils literal">}</tt> brace line up with the matching opening brace.</dd>
 </dl>
 </dd>
 <dt>Tab key indents</dt>
@@ -2306,7 +2307,7 @@ the end of the line such as <tt class="docutils literal"><span class="pre">{</sp
 unindent when pressing Shift-tab. Otherwise, the tab key will
 insert a tab character into the document (which can be different
 from indentation, depending on the indent type).</p>
-<div class="last note">
+<div class="note last">
 <p class="first admonition-title">Note</p>
 <p class="last">There are also separate configurable keybindings for indent &amp;
 unindent, but this preference allows the tab key to have different
@@ -2316,22 +2317,22 @@ meanings in different contexts - e.g. for snippet completion.</p>
 </dl>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id103" id="editor-completions-preferences" name="editor-completions-preferences">Editor Completions preferences</a></h3>
+<div class="section" id="editor-completions-preferences">
+<h3><a class="toc-backref" href="#id103">Editor Completions preferences</a></h3>
 <img alt="./images/pref_dialog_edit_completions.png" src="./images/pref_dialog_edit_completions.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id104" id="completions" name="completions">Completions</a></h4>
+<div class="section" id="completions">
+<h4><a class="toc-backref" href="#id104">Completions</a></h4>
 <dl class="docutils">
 <dt>Snippet Completion</dt>
 <dd>Whether to replace special keywords after typing Tab into a
 pre-defined text snippet.
-See <a class="reference" href="#user-definable-snippets">User-definable snippets</a>.</dd>
+See <a class="reference internal" href="#user-definable-snippets">User-definable snippets</a>.</dd>
 <dt>XML/HTML tag autocompletion</dt>
 <dd>When you open an XML tag automatically generate its completion tag.</dd>
 <dt>Automatic continuation multi-line comments</dt>
 <dd><p class="first">Continue automatically multi-line comments in languages like C, C++
 and Java when a new line is entered inside such a comment.
-With this option enabled, Geany will insert a <tt class="docutils literal"><span class="pre">*</span></tt> on every new line
+With this option enabled, Geany will insert a <tt class="docutils literal">*</tt> on every new line
 inside a multi-line comment, for example when you press return in the
 following C code:</p>
 <pre class="literal-block">
@@ -2343,7 +2344,7 @@ following C code:</p>
 *
 </pre>
 <p class="last">on the next line with the correct indentation based on the previous line,
-as long as the multi-line is not closed by <tt class="docutils literal"><span class="pre">*/</span></tt>.</p>
+as long as the multi-line is not closed by <tt class="docutils literal">*/</tt>.</p>
 </dd>
 <dt>Autocomplete symbols</dt>
 <dd>When you start to type a symbol name, look for the full string to
@@ -2364,11 +2365,11 @@ displayed.</dd>
 <dd>The maximum number of items in the autocompletion list.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id105" id="auto-close-quotes-and-brackets" name="auto-close-quotes-and-brackets">Auto-close quotes and brackets</a></h4>
+<div class="section" id="auto-close-quotes-and-brackets">
+<h4><a class="toc-backref" href="#id105">Auto-close quotes and brackets</a></h4>
 <p>Geany can automatically insert a closing bracket and quote characters when
-you open them. For instance, you type a <tt class="docutils literal"><span class="pre">(</span></tt> and Geany will automatically
-insert <tt class="docutils literal"><span class="pre">)</span></tt>. With the following options, you can define for which
+you open them. For instance, you type a <tt class="docutils literal">(</tt> and Geany will automatically
+insert <tt class="docutils literal">)</tt>. With the following options, you can define for which
 characters this should work.</p>
 <dl class="docutils">
 <dt>Parenthesis ( )</dt>
@@ -2384,12 +2385,12 @@ characters this should work.</p>
 </dl>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id106" id="editor-display-preferences" name="editor-display-preferences">Editor Display preferences</a></h3>
+<div class="section" id="editor-display-preferences">
+<h3><a class="toc-backref" href="#id106">Editor Display preferences</a></h3>
 <p>This is for visual elements displayed in the editor window.</p>
 <img alt="./images/pref_dialog_edit_display.png" src="./images/pref_dialog_edit_display.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id107" id="display" name="display">Display</a></h4>
+<div class="section" id="display">
+<h4><a class="toc-backref" href="#id107">Display</a></h4>
 <dl class="docutils">
 <dt>Invert syntax highlighting colors</dt>
 <dd>Invert all colors, by default this makes white text on a black
@@ -2413,8 +2414,8 @@ to mark lines.</dd>
 Otherwise you can scroll one more page even if there are no real lines.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id108" id="long-line-marker" name="long-line-marker">Long line marker</a></h4>
+<div class="section" id="long-line-marker">
+<h4><a class="toc-backref" href="#id108">Long line marker</a></h4>
 <p>The long line marker helps to indicate overly-long lines, or as a hint
 to the user for when to break the line.</p>
 <dl class="docutils">
@@ -2438,8 +2439,8 @@ where it should appear.</dd>
 <dd>Set the color of the long line marker.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id109" id="virtual-spaces" name="virtual-spaces">Virtual spaces</a></h4>
+<div class="section" id="virtual-spaces">
+<h4><a class="toc-backref" href="#id109">Virtual spaces</a></h4>
 <p>Virtual space is space beyond the end of each line.
 The cursor may be moved into virtual space but no real space will be
 added to the document until there is some text typed or some other
@@ -2454,11 +2455,11 @@ text insertion command is used.</p>
 </dl>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id110" id="files-preferences" name="files-preferences">Files preferences</a></h3>
+<div class="section" id="files-preferences">
+<h3><a class="toc-backref" href="#id110">Files preferences</a></h3>
 <img alt="./images/pref_dialog_files.png" src="./images/pref_dialog_files.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id111" id="new-files" name="new-files">New files</a></h4>
+<div class="section" id="new-files">
+<h4><a class="toc-backref" href="#id111">New files</a></h4>
 <dl class="docutils">
 <dt>Open new documents from the command-line</dt>
 <dd>Whether to create new documents when passing filenames that don't
@@ -2477,8 +2478,8 @@ characters to mark line breaks.
 On Unix-like systems, LF is default and CR is used on MAC systems.</dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id112" id="saving-files" name="saving-files">Saving files</a></h4>
+<div class="section" id="saving-files">
+<h4><a class="toc-backref" href="#id112">Saving files</a></h4>
 <p>Perform formatting operations when a document is saved. These
 can each be undone with the Undo command.</p>
 <dl class="docutils">
@@ -2491,16 +2492,16 @@ saving, avoiding mixed line endings in the same file.</dd>
 <dd>Remove the trailing spaces on each line of the document.</dd>
 <dt>Replace tabs by space</dt>
 <dd><p class="first">Replace all tabs in the document with the equivalent number of spaces.</p>
-<div class="last note">
+<div class="note last">
 <p class="first admonition-title">Note</p>
 <p class="last">It is better to use spaces to indent than use this preference - see
-<a class="reference" href="#indentation">Indentation</a>.</p>
+<a class="reference internal" href="#indentation">Indentation</a>.</p>
 </div>
 </dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id113" id="id3" name="id3">Miscellaneous</a></h4>
+<div class="section" id="id3">
+<h4><a class="toc-backref" href="#id113">Miscellaneous</a></h4>
 <dl class="docutils">
 <dt>Recent files list length</dt>
 <dd>The number of files to remember in the recently used files list.</dd>
@@ -2508,7 +2509,7 @@ saving, avoiding mixed line endings in the same file.</dd>
 <dd><p class="first">The number of seconds to periodically check the current document's
 file on disk in case it has changed. Setting it to 0 will disable
 this feature.</p>
-<div class="last note">
+<div class="note last">
 <p class="first admonition-title">Note</p>
 <p class="last">These checks are only performed on local files. Remote files are
 not checked for changes due to performance issues
@@ -2518,11 +2519,11 @@ not checked for changes due to performance issues
 </dl>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id114" id="tools-preferences" name="tools-preferences">Tools preferences</a></h3>
+<div class="section" id="tools-preferences">
+<h3><a class="toc-backref" href="#id114">Tools preferences</a></h3>
 <img alt="./images/pref_dialog_tools.png" src="./images/pref_dialog_tools.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id115" id="tool-paths" name="tool-paths">Tool paths</a></h4>
+<div class="section" id="tool-paths">
+<h4><a class="toc-backref" href="#id115">Tool paths</a></h4>
 <dl class="docutils">
 <dt>Terminal</dt>
 <dd>The location of your terminal executable.</dd>
@@ -2535,12 +2536,12 @@ not checked for changes due to performance issues
 <p class="first admonition-title">Note</p>
 <p class="last">For Windows users: at the time of writing it is recommended to use
 the grep.exe from the UnxUtils project
-(<a class="reference" href="http://sourceforge.net/projects/unxutils">http://sourceforge.net/projects/unxutils</a>). The grep.exe from the
+(<a class="reference external" href="http://sourceforge.net/projects/unxutils">http://sourceforge.net/projects/unxutils</a>). The grep.exe from the
 Mingw project for instance might not work with Geany at the moment.</p>
 </div>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id116" id="commands" name="commands">Commands</a></h4>
+<div class="section" id="commands">
+<h4><a class="toc-backref" href="#id116">Commands</a></h4>
 <dl class="docutils">
 <dt>Context action</dt>
 <dd>Set this to a command to execute on the current word.
@@ -2549,8 +2550,8 @@ to the specified command.</dd>
 </dl>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id117" id="template-preferences" name="template-preferences">Template preferences</a></h3>
+<div class="section" id="template-preferences">
+<h3><a class="toc-backref" href="#id117">Template preferences</a></h3>
 <p>This data is used as meta data for various template text to insert into
 a document, such as the file header. You only need to set fields that
 you want to use in your template files.</p>
@@ -2560,8 +2561,8 @@ you want to use in your template files.</p>
 <em>Tools-&gt;Reload Configuration</em> or restart Geany.</p>
 </div>
 <img alt="./images/pref_dialog_templ.png" src="./images/pref_dialog_templ.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id118" id="template-data" name="template-data">Template data</a></h4>
+<div class="section" id="template-data">
+<h4><a class="toc-backref" href="#id118">Template data</a></h4>
 <dl class="docutils">
 <dt>Developer</dt>
 <dd>The name of the developer who will be creating files.</dd>
@@ -2569,9 +2570,9 @@ you want to use in your template files.</p>
 <dd>The initials of the developer.</dd>
 <dt>Mail address</dt>
 <dd><p class="first">The email address of the developer.</p>
-<div class="last note">
+<div class="note last">
 <p class="first admonition-title">Note</p>
-<p class="last">You may wish to add anti-spam markup, e.g. <tt class="docutils literal"><span class="pre">name&lt;at&gt;site&lt;dot&gt;ext</span></tt>.</p>
+<p class="last">You may wish to add anti-spam markup, e.g. <tt class="docutils literal">name&lt;at&gt;site&lt;dot&gt;ext</tt>.</p>
 </div>
 </dd>
 <dt>Company</dt>
@@ -2581,30 +2582,30 @@ you want to use in your template files.</p>
 <dt>Year</dt>
 <dd>Specify a format for the the {year} wildcard. You can use any conversion specifiers
 which can be used with the ANSI C strftime function.  For details please see
-<a class="reference" href="http://man.cx/strftime">http://man.cx/strftime</a>.</dd>
+<a class="reference external" href="http://man.cx/strftime">http://man.cx/strftime</a>.</dd>
 <dt>Date</dt>
 <dd>Specify a format for the the {date} wildcard. You can use any conversion specifiers
 which can be used with the ANSI C strftime function.  For details please see
-<a class="reference" href="http://man.cx/strftime">http://man.cx/strftime</a>.</dd>
+<a class="reference external" href="http://man.cx/strftime">http://man.cx/strftime</a>.</dd>
 <dt>Date &amp; Time</dt>
 <dd>Specify a format for the the {datetime} wildcard. You can use any conversion specifiers
 which can be used with the ANSI C strftime function.  For details please see
-<a class="reference" href="http://man.cx/strftime">http://man.cx/strftime</a>.</dd>
+<a class="reference external" href="http://man.cx/strftime">http://man.cx/strftime</a>.</dd>
 </dl>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id119" id="keybinding-preferences" name="keybinding-preferences">Keybinding preferences</a></h3>
+<div class="section" id="keybinding-preferences">
+<h3><a class="toc-backref" href="#id119">Keybinding preferences</a></h3>
 <img alt="./images/pref_dialog_keys.png" src="./images/pref_dialog_keys.png" />
 <p>There are some commands listed in the keybinding dialog that are not, by default,
 bound to a key combination, and may not be available as a menu item.</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
-<p class="last">For more information see the section <a class="reference" href="#keybindings">Keybindings</a>.</p>
+<p class="last">For more information see the section <a class="reference internal" href="#keybindings">Keybindings</a>.</p>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id120" id="printing-preferences" name="printing-preferences">Printing preferences</a></h3>
+<div class="section" id="printing-preferences">
+<h3><a class="toc-backref" href="#id120">Printing preferences</a></h3>
 <img alt="./images/pref_dialog_printing.png" src="./images/pref_dialog_printing.png" />
 <dl class="docutils">
 <dt>Use external command for printing</dt>
@@ -2622,15 +2623,15 @@ bound to a key combination, and may not be available as a menu item.</p>
 <dt>Date format</dt>
 <dd>How the date should be printed. You can use the same format
 specifiers as in the ANSI C function strftime(). For details please
-see <a class="reference" href="http://man.cx/strftime">http://man.cx/strftime</a>.</dd>
+see <a class="reference external" href="http://man.cx/strftime">http://man.cx/strftime</a>.</dd>
 </dl>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id121" id="terminal-vte-preferences" name="terminal-vte-preferences">Terminal (VTE) preferences</a></h3>
-<p>See also: <a class="reference" href="#virtual-terminal-emulator-widget-vte">Virtual terminal emulator widget (VTE)</a>.</p>
+<div class="section" id="terminal-vte-preferences">
+<h3><a class="toc-backref" href="#id121">Terminal (VTE) preferences</a></h3>
+<p>See also: <a class="reference internal" href="#virtual-terminal-emulator-widget-vte">Virtual terminal emulator widget (VTE)</a>.</p>
 <img alt="./images/pref_dialog_vte.png" src="./images/pref_dialog_vte.png" />
-<div class="section">
-<h4><a class="toc-backref" href="#id122" id="terminal-widget" name="terminal-widget">Terminal widget</a></h4>
+<div class="section" id="terminal-widget">
+<h4><a class="toc-backref" href="#id122">Terminal widget</a></h4>
 <dl class="docutils">
 <dt>Terminal font</dt>
 <dd>Select the font that will be used in the terminal emulation control.</dd>
@@ -2668,8 +2669,8 @@ like a Python console (e.g. ipython). Use this with care.</dd>
 </div>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id123" id="project-management" name="project-management">Project Management</a></h2>
+<div class="section" id="project-management">
+<h2><a class="toc-backref" href="#id123">Project Management</a></h2>
 <p>Project Management is optional in Geany. Currently it can be used for:</p>
 <ul class="simple">
 <li>Storing and opening session files on a project basis.</li>
@@ -2677,49 +2678,49 @@ like a Python console (e.g. ipython). Use this with care.</dd>
 </ul>
 <p>A list of session files can be stored and opened with the project
 when the <em>Use project-based session files</em> preference is enabled,
-in the <em>Project</em> group of the <a class="reference" href="#preferences">Preferences</a> dialog.</p>
+in the <em>Project</em> group of the <a class="reference internal" href="#preferences">Preferences</a> dialog.</p>
 <p>As long as a project is open, the Build menu will use
 the items defined in project's settings, instead of the defaults.
-See <a class="reference" href="#build-menu-configuration">Build Menu Configuration</a> for information on configuring the menu.</p>
+See <a class="reference internal" href="#build-menu-configuration">Build Menu Configuration</a> for information on configuring the menu.</p>
 <p>The current project's settings are saved when it is closed, or when
 Geany is shutdown. When restarting Geany, the previously opened project
 file that was in use at the end of the last session will be reopened.</p>
 <p>The project menu items are detailed below.</p>
-<div class="section">
-<h3><a class="toc-backref" href="#id124" id="new-project" name="new-project">New Project</a></h3>
+<div class="section" id="new-project">
+<h3><a class="toc-backref" href="#id124">New Project</a></h3>
 <p>To create a new project, fill in the <em>Name</em> field. By default this
-will setup a new project file <tt class="docutils literal"><span class="pre">~/projects/name.geany</span></tt>. Usually it's
+will setup a new project file <tt class="docutils literal">~/projects/name.geany</tt>. Usually it's
 best to store all your project files in the same directory (they are
 independent of any source directory trees).</p>
-<p>The Base path text field is setup to use <tt class="docutils literal"><span class="pre">~/projects/name</span></tt>. This
+<p>The Base path text field is setup to use <tt class="docutils literal">~/projects/name</tt>. This
 can safely be set to any existing path -- it will not touch the file
 structure contained in it.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id125" id="project-properties" name="project-properties">Project Properties</a></h3>
+<div class="section" id="project-properties">
+<h3><a class="toc-backref" href="#id125">Project Properties</a></h3>
 <p>You can set an optional description for the project, but it is not
 used elsewhere by Geany.</p>
 <p>The <em>Base path</em> field is used as the directory to run the Build menu commands.
 The specified path can be an absolute path or it is considered to be
 relative to the project's file name.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id126" id="open-project" name="open-project">Open Project</a></h3>
+<div class="section" id="open-project">
+<h3><a class="toc-backref" href="#id126">Open Project</a></h3>
 <p>The Open command displays a standard file chooser, starting in
-<tt class="docutils literal"><span class="pre">~/projects</span></tt>. Choose a project file named with the <tt class="docutils literal"><span class="pre">.geany</span></tt>
+<tt class="docutils literal">~/projects</tt>. Choose a project file named with the <tt class="docutils literal">.geany</tt>
 extension.</p>
 <p>When project session support is enabled, Geany will close the currently
 open files and open the session files associated with the project.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id127" id="close-project" name="close-project">Close Project</a></h3>
+<div class="section" id="close-project">
+<h3><a class="toc-backref" href="#id127">Close Project</a></h3>
 <p>Project file settings are saved when the project is closed.</p>
 <p>When project session support is enabled, Geany will close the project
 session files and open any previously closed default session files.</p>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id128" id="build-menu" name="build-menu">Build Menu</a></h2>
+<div class="section" id="build-menu">
+<h2><a class="toc-backref" href="#id128">Build Menu</a></h2>
 <p>After editing code with Geany, the next step is to compile, link, build,
 interpret, run etc.  As Geany supports many languages each with a different
 approach to such operations, and as there are also many language independent
@@ -2738,24 +2739,24 @@ warnings or errors.</li>
 <p>Warnings and errors that can be parsed for line numbers will be shown in
 red in the Compiler tab and you can click on them to switch to the relevant
 source file (or open it) and mark the line number.  Also lines with
-warnings or errors are marked in the source, see <a class="reference" href="#indicators">Indicators</a> below.</p>
+warnings or errors are marked in the source, see <a class="reference internal" href="#indicators">Indicators</a> below.</p>
 <div class="tip">
 <p class="first admonition-title">Tip</p>
 <p class="last">If Geany's default error message parsing does not parse errors for
 the tool you're using, you can set a custom regex in the Build Commands
-Dialog, see <a class="reference" href="#build-menu-configuration">Build Menu Configuration</a>.</p>
+Dialog, see <a class="reference internal" href="#build-menu-configuration">Build Menu Configuration</a>.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id129" id="indicators" name="indicators">Indicators</a></h3>
+<div class="section" id="indicators">
+<h3><a class="toc-backref" href="#id129">Indicators</a></h3>
 <p>Indicators are red squiggly underlines which are used to highlight
 errors which occurred while compiling the current file. So you can
 easily see where your code failed to compile. You can remove them by
 selecting <em>Remove Error Indicators</em> in the Document menu.</p>
-<p>If you do not like this feature, you can disable it - see <a class="reference" href="#editor-features-preferences">Editor Features
+<p>If you do not like this feature, you can disable it - see <a class="reference internal" href="#editor-features-preferences">Editor Features
 preferences</a>.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id130" id="default-build-menu-items" name="default-build-menu-items">Default Build Menu Items</a></h3>
+<div class="section" id="default-build-menu-items">
+<h3><a class="toc-backref" href="#id130">Default Build Menu Items</a></h3>
 <p>Depending on the current file's filetype, the default Build menu will contain
 the following items:</p>
 <ul class="simple">
@@ -2769,8 +2770,8 @@ the following items:</p>
 <li>Execute</li>
 <li>Set Build Menu Commands</li>
 </ul>
-<div class="section">
-<h4><a class="toc-backref" href="#id131" id="compile" name="compile">Compile</a></h4>
+<div class="section" id="compile">
+<h4><a class="toc-backref" href="#id131">Compile</a></h4>
 <p>The Compile command has different uses for different kinds of files.</p>
 <p>For compilable languages such as C and C++, the Compile command is
 set up to compile the current source file into a binary object file.</p>
@@ -2779,8 +2780,8 @@ set up to compile the current source file into a binary object file.</p>
 bytecode if the language supports it, or will run a syntax check,
 or if that is not available will run the file in its language interpreter.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id132" id="build" name="build">Build</a></h4>
+<div class="section" id="build">
+<h4><a class="toc-backref" href="#id132">Build</a></h4>
 <p>For compilable languages such as C and C++, the Build command will link
 the current source file's equivalent object file into an executable. If
 the object file does not exist, the source will be compiled and linked
@@ -2794,40 +2795,40 @@ commands is recommended; this will also make it easier for users to
 build your software.</p>
 </div>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id133" id="make" name="make">Make</a></h4>
+<div class="section" id="make">
+<h4><a class="toc-backref" href="#id133">Make</a></h4>
 <p>This runs &quot;make&quot; in the same directory as the
 current file.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id134" id="make-custom-target" name="make-custom-target">Make custom target</a></h4>
+<div class="section" id="make-custom-target">
+<h4><a class="toc-backref" href="#id134">Make custom target</a></h4>
 <p>This is similar to running 'Make' but you will be prompted for
 the make target name to be passed to the Make tool. For example,
 typing 'clean' in the dialog prompt will run &quot;make clean&quot;.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id135" id="make-object" name="make-object">Make object</a></h4>
+<div class="section" id="make-object">
+<h4><a class="toc-backref" href="#id135">Make object</a></h4>
 <p>Make object will run &quot;make current_file.o&quot; in the same directory as
 the current file, using the filename for 'current_file'. It is useful
 for building just the current file without building the whole project.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id136" id="next-error" name="next-error">Next Error</a></h4>
+<div class="section" id="next-error">
+<h4><a class="toc-backref" href="#id136">Next Error</a></h4>
 <p>The next error item will move to the next detected error in the file.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id137" id="previous-error" name="previous-error">Previous Error</a></h4>
+<div class="section" id="previous-error">
+<h4><a class="toc-backref" href="#id137">Previous Error</a></h4>
 <p>The previous error item will move to the previous detected error in the file.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id138" id="execute" name="execute">Execute</a></h4>
+<div class="section" id="execute">
+<h4><a class="toc-backref" href="#id138">Execute</a></h4>
 <p>Execute will run the corresponding executable file, shell script or
 interpreted script in a terminal window. Note that the Terminal tool
 path must be correctly set in the Tools tab of the Preferences dialog -
 you can use any terminal program that runs a Bourne compatible shell
 and accept the &quot;-e&quot; command line argument to start a command or can be
 selected to use the built-in VTE if it is available - see
-<a class="reference" href="#virtual-terminal-emulator-widget-vte">Virtual terminal emulator widget (VTE)</a>.</p>
+<a class="reference internal" href="#virtual-terminal-emulator-widget-vte">Virtual terminal emulator widget (VTE)</a>.</p>
 <p>After your program or script has finished executing, you will be
 prompted to press the return key. This allows you to review any text
 output from the program before the terminal window is closed.</p>
@@ -2836,8 +2837,8 @@ output from the program before the terminal window is closed.</p>
 <p class="last">The execute command output is not parsed for errors.</p>
 </div>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id139" id="stopping-running-processes" name="stopping-running-processes">Stopping running processes</a></h4>
+<div class="section" id="stopping-running-processes">
+<h4><a class="toc-backref" href="#id139">Stopping running processes</a></h4>
 <p>When there is a running program, the Execute menu item in the menu and
 the Run button in the toolbar
 each become a stop button so you can stop the current running program (and
@@ -2845,8 +2846,8 @@ any child processes). This works by sending the SIGQUIT signal to the process.</
 <p>Depending on the process you started it is possible that the process
 cannot be stopped. For example this can happen when the process creates
 more than one child process.</p>
-<div class="section">
-<h5><a class="toc-backref" href="#id140" id="terminal-emulators" name="terminal-emulators">Terminal emulators</a></h5>
+<div class="section" id="terminal-emulators">
+<h5><a class="toc-backref" href="#id140">Terminal emulators</a></h5>
 <p>Xterm is known to work properly. If you are using &quot;Terminal&quot;
 (the terminal program of Xfce), you should add the command line
 option <tt class="docutils literal"><span class="pre">--disable-server</span></tt> otherwise the started process cannot be
@@ -2854,8 +2855,8 @@ stopped. Just add this option in the preferences dialog on the Tools
 tab in the terminal field.</p>
 </div>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id141" id="set-build-commands" name="set-build-commands">Set Build Commands</a></h4>
+<div class="section" id="set-build-commands">
+<h4><a class="toc-backref" href="#id141">Set Build Commands</a></h4>
 <p>By default the Compile and Build commands invoke the GCC compiler and
 linker with only the basic arguments needed by all programs. Using
 <em>Set Build Commands</em> you can add any include paths and compile
@@ -2863,8 +2864,8 @@ flags for the compiler, any library names and paths for the linker,
 and any arguments you want to use when running Execute.</p>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id142" id="build-menu-configuration" name="build-menu-configuration">Build Menu Configuration</a></h3>
+<div class="section" id="build-menu-configuration">
+<h3><a class="toc-backref" href="#id142">Build Menu Configuration</a></h3>
 <p>The build menu has considerable flexibility and configurability, allowing
 both menu labels the commands they execute and the directory they execute
 in to be configured.</p>
@@ -2898,7 +2899,7 @@ and is directed to the terminal selected in preferences.</p>
 </li>
 </ul>
 <p>The maximum numbers of items in each of the configurable groups can be
-configured when Geany starts using hidden settings (see <a class="reference" href="#preferences-file-format">Preferences File Format</a>).
+configured when Geany starts using hidden settings (see <a class="reference internal" href="#preferences-file-format">Preferences File Format</a>).
 Even though the maximum number of items may have been increased, only
 those menu items that have values configured are shown in the menu.</p>
 <p>The groups of menu items obtain their configuration from four potential
@@ -3023,11 +3024,11 @@ non-filetype commands in a filetype file, this provides the ability to
 define filetype dependent default menu items.</li>
 <li>(Execute, Project File) and (Execute, Preferences) - the project filetype based execute
 configuration and preferences non-filetype based execute can only be set by hand editing the
-appropriate file, see <a class="reference" href="#preferences-file-format">Preferences File Format</a> and <a class="reference" href="#project-file-format">Project File Format</a>.</li>
+appropriate file, see <a class="reference internal" href="#preferences-file-format">Preferences File Format</a> and <a class="reference internal" href="#project-file-format">Project File Format</a>.</li>
 </ul>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id143" id="build-menu-commands-dialog" name="build-menu-commands-dialog">Build Menu Commands Dialog</a></h3>
+<div class="section" id="build-menu-commands-dialog">
+<h3><a class="toc-backref" href="#id143">Build Menu Commands Dialog</a></h3>
 <p>Most of the configuration of the build menu is done through the Build Menu
 Commands Dialog.  You edit the configuration sourced from preferences in the
 dialog opened from the Build-&gt;Build Menu Commands item and you edit the
@@ -3059,8 +3060,8 @@ with the project source but can with the preferences source dialog.</p>
 When you do this the command from the next lower priority source will be shown.
 To hide lower priority menu items without having anything show in the menu
 configure with a nothing in the label but at least one character in the command.</p>
-<div class="section">
-<h4><a class="toc-backref" href="#id144" id="substitutions-in-commands-and-working-directories" name="substitutions-in-commands-and-working-directories">Substitutions in Commands and Working Directories</a></h4>
+<div class="section" id="substitutions-in-commands-and-working-directories">
+<h4><a class="toc-backref" href="#id144">Substitutions in Commands and Working Directories</a></h4>
 <p>The first occurence of each of the following character sequences in each of the
 command and working directory fields is substituted by the items specified below
 before the command is run.</p>
@@ -3080,20 +3081,20 @@ and even checked into and out of version control without having to re-configure
 build menu.</p>
 </div>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id145" id="build-menu-keyboard-shortcuts" name="build-menu-keyboard-shortcuts">Build Menu Keyboard Shortcuts</a></h4>
+<div class="section" id="build-menu-keyboard-shortcuts">
+<h4><a class="toc-backref" href="#id145">Build Menu Keyboard Shortcuts</a></h4>
 <p>Keyboard shortcuts can be defined for the first two filetype menu items, the first three
 non-filetype menu items, the first two execute menu items and the fixed menu items.
-In the keybindings configuration dialog (see <a class="reference" href="#keybinding-preferences">Keybinding preferences</a>)
-these items are identified by the default labels shown in the <a class="reference" href="#build-menu">Build Menu</a> section above.</p>
+In the keybindings configuration dialog (see <a class="reference internal" href="#keybinding-preferences">Keybinding preferences</a>)
+these items are identified by the default labels shown in the <a class="reference internal" href="#build-menu">Build Menu</a> section above.</p>
 <p>It is currently not possible to bind keyboard shortcuts to more than these menu items.</p>
 <p>You can also use underlines in the labels to set mnemonic characters.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id146" id="configuration-files" name="configuration-files">Configuration Files</a></h4>
+<div class="section" id="configuration-files">
+<h4><a class="toc-backref" href="#id146">Configuration Files</a></h4>
 <p>The configurable Build Menu capability was introduced in Geany 0.19 and
 required a new section to be added to the configuration files (See
-<a class="reference" href="#preferences-file-format">Preferences File Format</a>).  Geany will still load older format project,
+<a class="reference internal" href="#preferences-file-format">Preferences File Format</a>).  Geany will still load older format project,
 preferences and filetype file settings and will attempt to map them into the new
 configuration format.  There is not a simple clean mapping between the formats.
 The mapping used produces the most sensible results for the majority of cases.
@@ -3105,8 +3106,8 @@ older format configuration files.</p>
 </div>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id147" id="printing-support" name="printing-support">Printing support</a></h2>
+<div class="section" id="printing-support">
+<h2><a class="toc-backref" href="#id147">Printing support</a></h2>
 <p>Since Geany 0.13 there has been printing support using GTK's printing API.
 The printed page(s) will look nearly the same as on your screen in Geany.
 Additionally, there are some options to modify the printed page(s).</p>
@@ -3128,7 +3129,7 @@ same as the ones which can be used with the ANSI C strftime function.</p>
 <p>All of these settings can also be changed in the print dialog just before
 actual printing is done.
 On Unix-like systems the provided print dialog offers a print preview. The
-preview file is opened with a PDF viewer and by default GTK uses <tt class="docutils literal"><span class="pre">evince</span></tt>
+preview file is opened with a PDF viewer and by default GTK uses <tt class="docutils literal">evince</tt>
 for print preview. If you have not installed evince or just want to use
 another PDF viewer, you can change the program to use in the file
 <tt class="docutils literal"><span class="pre">.gtkrc-2.0</span></tt> (usually found in your home directory). Simply add a line
@@ -3148,7 +3149,7 @@ passed in the preferences dialog. The default command is:</p>
 <pre class="literal-block">
 % lpr %f
 </pre>
-<p><tt class="docutils literal"><span class="pre">%f</span></tt> will be substituted by the filename of the current file. Geany
+<p><tt class="docutils literal">%f</tt> will be substituted by the filename of the current file. Geany
 will not show errors from the command itself, so you should make
 sure that it works before(e.g. by trying to execute it from the
 command line).</p>
@@ -3159,14 +3160,14 @@ command line).</p>
 <p>But this depends on a2ps and xfprint4. As a replacement for xfprint4,
 gtklp or similar programs can be used.</p>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id148" id="plugins" name="plugins">Plugins</a></h2>
+<div class="section" id="plugins">
+<h2><a class="toc-backref" href="#id148">Plugins</a></h2>
 <p>Plugins are loaded at startup, if the <em>Enable plugin support</em>
 general preference is set. There is also a command-line option,
 <tt class="docutils literal"><span class="pre">-p</span></tt>, which prevents plugins being loaded. Plugins are scanned in
 the following directories:</p>
 <ul class="simple">
-<li><tt class="docutils literal"><span class="pre">$prefix/lib/geany</span></tt> (see <a class="reference" href="#installation-prefix">Installation prefix</a>)</li>
+<li><tt class="docutils literal">$prefix/lib/geany</tt> (see <a class="reference internal" href="#installation-prefix">Installation prefix</a>)</li>
 <li><tt class="docutils literal"><span class="pre">~/.config/geany/plugins</span></tt></li>
 </ul>
 <p>Most plugins add menu items to the <em>Tools</em> menu when they are loaded.</p>
@@ -3177,17 +3178,17 @@ in the dialog, it is loaded or unloaded according to its previous state.
 By default, no plugins are loaded at startup until you select some.
 You can also configure some plugin specific options when the plugin
 provides some.</p>
-<p>See also <a class="reference" href="#plugin-documentation">Plugin documentation</a> for information about single plugins
+<p>See also <a class="reference internal" href="#plugin-documentation">Plugin documentation</a> for information about single plugins
 which are included in Geany.</p>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id149" id="keybindings" name="keybindings">Keybindings</a></h2>
+<div class="section" id="keybindings">
+<h2><a class="toc-backref" href="#id149">Keybindings</a></h2>
 <p>Geany supports the default keyboard shortcuts for the Scintilla
-editing widget. For a list of these commands, see <a class="reference" href="#scintilla-keyboard-commands">Scintilla
+editing widget. For a list of these commands, see <a class="reference internal" href="#scintilla-keyboard-commands">Scintilla
 keyboard commands</a>. The Scintilla keyboard shortcuts will be overridden
 by any custom keybindings with the same keyboard shortcut.</p>
-<div class="section">
-<h3><a class="toc-backref" href="#id150" id="switching-documents" name="switching-documents">Switching documents</a></h3>
+<div class="section" id="switching-documents">
+<h3><a class="toc-backref" href="#id150">Switching documents</a></h3>
 <p>There are a few non-configurable bindings to switch between documents,
 listed below. These can also be overridden by custom keybindings.</p>
 <table border="1" class="docutils">
@@ -3216,8 +3217,8 @@ listed below. These can also be overridden by custom keybindings.</p>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id151" id="configurable-keybindings" name="configurable-keybindings">Configurable keybindings</a></h3>
+<div class="section" id="configurable-keybindings">
+<h3><a class="toc-backref" href="#id151">Configurable keybindings</a></h3>
 <p>For all actions listed below you can define your own keybindings. Open
 the Preferences dialog, select the desired action and click on
 change. In the resulting dialog you can press the key combination you
@@ -3234,8 +3235,8 @@ either <em>Ctrl-O</em> or <em>Alt-O</em>.</p>
 <p>The following tables list all customizable keyboard shortcuts, those
 which are common to many applications are marked with (C) after the
 shortcut.</p>
-<div class="section">
-<h4><a class="toc-backref" href="#id152" id="file-keybindings" name="file-keybindings">File keybindings</a></h4>
+<div class="section" id="file-keybindings">
+<h4><a class="toc-backref" href="#id152">File keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -3297,8 +3298,8 @@ will be lost.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id153" id="editor-keybindings" name="editor-keybindings">Editor keybindings</a></h4>
+<div class="section" id="editor-keybindings">
+<h4><a class="toc-backref" href="#id153">Editor keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -3391,7 +3392,7 @@ insert a space.</td>
 <td>&nbsp;</td>
 <td>Executes a command and passes the current word
 (near the cursor position) or selection as an
-argument. See the section called <a class="reference" href="#context-actions">Context
+argument. See the section called <a class="reference internal" href="#context-actions">Context
 actions</a>.</td>
 </tr>
 <tr><td>Move cursor in snippet</td>
@@ -3419,8 +3420,8 @@ one line.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id154" id="clipboard-keybindings" name="clipboard-keybindings">Clipboard keybindings</a></h4>
+<div class="section" id="clipboard-keybindings">
+<h4><a class="toc-backref" href="#id154">Clipboard keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -3459,8 +3460,8 @@ selection) to the clipboard.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id155" id="select-keybindings" name="select-keybindings">Select keybindings</a></h4>
+<div class="section" id="select-keybindings">
+<h4><a class="toc-backref" href="#id155">Select keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -3504,8 +3505,8 @@ partially selected lines).</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id156" id="insert-keybindings" name="insert-keybindings">Insert keybindings</a></h4>
+<div class="section" id="insert-keybindings">
+<h4><a class="toc-backref" href="#id156">Insert keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -3541,8 +3542,8 @@ tabs should be used for indentation.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id157" id="format-keybindings" name="format-keybindings">Format keybindings</a></h4>
+<div class="section" id="format-keybindings">
+<h4><a class="toc-backref" href="#id157">Format keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -3609,7 +3610,7 @@ with the same indentation as the previous line.</td>
 <td>Passes the current selection to a configured
 external command (available for the first
 three configured commands, see
-<a class="reference" href="#sending-text-through-custom-commands">Sending text through custom commands</a> for
+<a class="reference internal" href="#sending-text-through-custom-commands">Sending text through custom commands</a> for
 details).</td>
 </tr>
 <tr><td>Send Selection to Terminal</td>
@@ -3629,8 +3630,8 @@ enabled for the current document.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id158" id="settings-keybindings" name="settings-keybindings">Settings keybindings</a></h4>
+<div class="section" id="settings-keybindings">
+<h4><a class="toc-backref" href="#id158">Settings keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -3655,8 +3656,8 @@ enabled for the current document.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id159" id="search-keybindings" name="search-keybindings">Search keybindings</a></h4>
+<div class="section" id="search-keybindings">
+<h4><a class="toc-backref" href="#id159">Search keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -3732,8 +3733,8 @@ find, highlighted matches will be cleared.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id160" id="go-to-keybindings" name="go-to-keybindings">Go to keybindings</a></h4>
+<div class="section" id="go-to-keybindings">
+<h4><a class="toc-backref" href="#id160">Go to keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -3750,14 +3751,14 @@ find, highlighted matches will be cleared.</td>
 <tr><td>Navigate forward a location</td>
 <td>&nbsp;</td>
 <td>Switches to the next location in the navigation
-history. See the section called <a class="reference" href="#code-navigation-history">Code Navigation
+history. See the section called <a class="reference internal" href="#code-navigation-history">Code Navigation
 History</a>.</td>
 </tr>
 <tr><td>Navigate back a location</td>
 <td>&nbsp;</td>
 <td>Switches to the previous location in the
 navigation history. See the section called
-<a class="reference" href="#code-navigation-history">Code navigation history</a>.</td>
+<a class="reference internal" href="#code-navigation-history">Code navigation history</a>.</td>
 </tr>
 <tr><td>Go to line</td>
 <td>Ctrl-L</td>
@@ -3790,7 +3791,7 @@ marker if there already is one.</td>
 the keyboard cursor). If the definition cannot be
 found (e.g. the relevant file is not open) Geany
 will beep and do nothing. See the section called
-<a class="reference" href="#go-to-tag-definition">Go to tag definition</a>.</td>
+<a class="reference internal" href="#go-to-tag-definition">Go to tag definition</a>.</td>
 </tr>
 <tr><td>Go to tag declaration</td>
 <td>&nbsp;</td>
@@ -3798,7 +3799,7 @@ will beep and do nothing. See the section called
 the keyboard cursor). If the declaration cannot be
 found (e.g. the relevant file is not open) Geany
 will beep and do nothing. See the section called
-<a class="reference" href="#go-to-tag-declaration">Go to tag declaration</a>.</td>
+<a class="reference internal" href="#go-to-tag-declaration">Go to tag declaration</a>.</td>
 </tr>
 <tr><td>Go to Start of Line</td>
 <td>Home</td>
@@ -3830,8 +3831,8 @@ If the line is not wrapped, it behaves like
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id161" id="view-keybindings" name="view-keybindings">View keybindings</a></h4>
+<div class="section" id="view-keybindings">
+<h4><a class="toc-backref" href="#id161">View keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -3879,8 +3880,8 @@ and the status bar.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id162" id="focus-keybindings" name="focus-keybindings">Focus keybindings</a></h4>
+<div class="section" id="focus-keybindings">
+<h4><a class="toc-backref" href="#id162">Focus keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="30%" />
@@ -3942,8 +3943,8 @@ visible).</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id163" id="notebook-tab-keybindings" name="notebook-tab-keybindings">Notebook tab keybindings</a></h4>
+<div class="section" id="notebook-tab-keybindings">
+<h4><a class="toc-backref" href="#id163">Notebook tab keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="28%" />
@@ -3996,8 +3997,8 @@ one.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id164" id="document-keybindings" name="document-keybindings">Document keybindings</a></h4>
+<div class="section" id="document-keybindings">
+<h4><a class="toc-backref" href="#id164">Document keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -4058,8 +4059,8 @@ current document.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id165" id="build-keybindings" name="build-keybindings">Build keybindings</a></h4>
+<div class="section" id="build-keybindings">
+<h4><a class="toc-backref" href="#id165">Build keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -4116,8 +4117,8 @@ the last build process.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id166" id="tools-keybindings" name="tools-keybindings">Tools keybindings</a></h4>
+<div class="section" id="tools-keybindings">
+<h4><a class="toc-backref" href="#id166">Tools keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -4138,8 +4139,8 @@ the last build process.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id167" id="help-keybindings" name="help-keybindings">Help keybindings</a></h4>
+<div class="section" id="help-keybindings">
+<h4><a class="toc-backref" href="#id167">Help keybindings</a></h4>
 <table border="1" class="docutils">
 <colgroup>
 <col width="29%" />
@@ -4163,14 +4164,14 @@ the last build process.</td>
 </div>
 </div>
 </div>
-<div class="section">
-<h1><a class="toc-backref" href="#id168" id="id4" name="id4">Configuration files</a></h1>
+<div class="section" id="id4">
+<h1><a class="toc-backref" href="#id168">Configuration files</a></h1>
 <div class="warning">
 <p class="first admonition-title">Warning</p>
 <p class="last">You must use UTF-8 encoding <em>without BOM</em> for configuration files.</p>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id169" id="tools-menu-items" name="tools-menu-items">Tools menu items</a></h2>
+<div class="section" id="tools-menu-items">
+<h2><a class="toc-backref" href="#id169">Tools menu items</a></h2>
 <p>There's a <em>Configuration files</em> submenu in the <em>Tools</em> menu that
 contains items for some of the available user configuration files.
 Clicking on one opens it in the editor for you to update. Geany will
@@ -4192,15 +4193,15 @@ saving filetypes.common as this can possibly take a significant
 amount of time.</p>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id170" id="global-configuration-file" name="global-configuration-file">Global configuration file</a></h2>
+<div class="section" id="global-configuration-file">
+<h2><a class="toc-backref" href="#id170">Global configuration file</a></h2>
 <p>There is a global configuration file for Geany which will be used for
 any settings not defined in the users local configuration file.
 Settings present in the local configuration file override those in the global
 file.</p>
 <p>The global configuration file is read from
-<tt class="docutils literal"><span class="pre">$prefix/share/geany/geany.conf</span></tt> (where <tt class="docutils literal"><span class="pre">$prefix</span></tt> is the path where
-Geany is installed, see <a class="reference" href="#installation-prefix">Installation prefix</a>) when starting Geany and
+<tt class="docutils literal">$prefix/share/geany/geany.conf</tt> (where <tt class="docutils literal">$prefix</tt> is the path where
+Geany is installed, see <a class="reference internal" href="#installation-prefix">Installation prefix</a>) when starting Geany and
 an user configuration file does not exist. It can contain any settings
 which are found in the usual configuration file created by Geany but
 does not have to contain all settings.</p>
@@ -4212,28 +4213,28 @@ set some sane default values for this environment. Usually users won't
 need to do that.</p>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id171" id="filetype-definition-files" name="filetype-definition-files">Filetype definition files</a></h2>
+<div class="section" id="filetype-definition-files">
+<h2><a class="toc-backref" href="#id171">Filetype definition files</a></h2>
 <p>All color definitions and other filetype specific settings are
 stored in the filetype definition files. Those settings are colors
 for syntax highlighting, general settings like comment characters or
 word delimiter characters as well as compiler and linker settings.</p>
-<div class="section">
-<h3><a class="toc-backref" href="#id172" id="custom-filetypes" name="custom-filetypes">Custom filetypes</a></h3>
+<div class="section" id="custom-filetypes">
+<h3><a class="toc-backref" href="#id172">Custom filetypes</a></h3>
 <p>At startup Geany looks for <tt class="docutils literal"><span class="pre">filetypes.*.conf</span></tt> files in the system and
 user filetype paths, adding any filetypes found with the name matching
-the '<tt class="docutils literal"><span class="pre">*</span></tt>' wildcard.</p>
+the '<tt class="docutils literal">*</tt>' wildcard.</p>
 <p>Custom filetypes are not as powerful as built-in filetypes, but the following
 have been implemented:</p>
 <ul>
 <li><p class="first">Recognizing and setting the filetype (after the user has manually edited
-<tt class="docutils literal"><span class="pre">filetype_extensions.conf</span></tt>).</p>
+<tt class="docutils literal">filetype_extensions.conf</tt>).</p>
 </li>
 <li><dl class="first docutils">
-<dt>Filetype settings in the [settings] section (see <a class="reference" href="#format">Format</a>).</dt>
+<dt>Filetype settings in the [settings] section (see <a class="reference internal" href="#format">Format</a>).</dt>
 <dd><ul class="first last simple">
-<li>Using existing tag parsing (<tt class="docutils literal"><span class="pre">tag_parser</span></tt> key).</li>
-<li>Using existing syntax highlighting (<tt class="docutils literal"><span class="pre">lexer_filetype</span></tt> key).</li>
+<li>Using existing tag parsing (<tt class="docutils literal">tag_parser</tt> key).</li>
+<li>Using existing syntax highlighting (<tt class="docutils literal">lexer_filetype</tt> key).</li>
 </ul>
 </dd>
 </dl>
@@ -4245,14 +4246,14 @@ type).</p>
 </li>
 </ul>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id173" id="system-files" name="system-files">System files</a></h3>
+<div class="section" id="system-files">
+<h3><a class="toc-backref" href="#id173">System files</a></h3>
 <p>The system-wide configuration files can be found in
-<tt class="docutils literal"><span class="pre">$prefix/share/geany</span></tt> and are called <tt class="docutils literal"><span class="pre">filetypes.$ext</span></tt>,
-where <tt class="docutils literal"><span class="pre">$prefix</span></tt> is the path where Geany is installed (see
-<a class="reference" href="#installation-prefix">Installation prefix</a>) and $ext is the name of the filetype. For every
+<tt class="docutils literal">$prefix/share/geany</tt> and are called <tt class="docutils literal"><span class="pre">filetypes.$ext</span></tt>,
+where <tt class="docutils literal">$prefix</tt> is the path where Geany is installed (see
+<a class="reference internal" href="#installation-prefix">Installation prefix</a>) and $ext is the name of the filetype. For every
 filetype there is a corresponding definition file. There is one
-exception: <tt class="docutils literal"><span class="pre">filetypes.common</span></tt> -- this file is for general settings,
+exception: <tt class="docutils literal">filetypes.common</tt> -- this file is for general settings,
 which are not specific to a certain filetype.</p>
 <div class="warning">
 <p class="first admonition-title">Warning</p>
@@ -4260,9 +4261,9 @@ which are not specific to a certain filetype.</p>
 because they will be overridden when Geany is updated.</p>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id174" id="user-files" name="user-files">User files</a></h3>
-<p>To change the settings, copy a file from <tt class="docutils literal"><span class="pre">$prefix/share/geany</span></tt> to
+<div class="section" id="user-files">
+<h3><a class="toc-backref" href="#id174">User files</a></h3>
+<p>To change the settings, copy a file from <tt class="docutils literal">$prefix/share/geany</tt> to
 the subdirectory filedefs in your configuration directory (usually
 <tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt>).</p>
 <p>For example:</p>
@@ -4274,49 +4275,49 @@ available after an update of Geany because they reside in your
 configuration directory. Alternatively, you can create a file
 <tt class="docutils literal"><span class="pre">~/.config/geany/filedefs/filetypes.X</span></tt> and add only these settings you want
 to change. All missing settings will be read from the corresponding
-global definition file in <tt class="docutils literal"><span class="pre">$prefix/share/geany</span></tt>.</p>
+global definition file in <tt class="docutils literal">$prefix/share/geany</tt>.</p>
 <p>As well as the sections listed below, each filetype file can contain
-a [build-menu] section as described in <a class="reference" href="#build-menu-section">[build-menu] Section</a>.</p>
+a [build-menu] section as described in <a class="reference internal" href="#build-menu-section">[build-menu] Section</a>.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id175" id="format" name="format">Format</a></h3>
-<div class="section">
-<h4><a class="toc-backref" href="#id176" id="styling-section" name="styling-section">[styling] Section</a></h4>
+<div class="section" id="format">
+<h3><a class="toc-backref" href="#id175">Format</a></h3>
+<div class="section" id="styling-section">
+<h4><a class="toc-backref" href="#id176">[styling] Section</a></h4>
 <p>In this section the colors for syntax highlighting are defined. The
 manual format is:</p>
 <ul class="simple">
-<li><tt class="docutils literal"><span class="pre">key=foreground_color;background_color;bold_flag;italic_flag</span></tt></li>
+<li><tt class="docutils literal">key=foreground_color;background_color;bold_flag;italic_flag</tt></li>
 </ul>
 <p>Colors have to be specified as RGB hex values prefixed by
 0x. For example red is 0xff0000, blue is 0x0000ff. The values are
 case-insensitive, but it is a good idea to use small letters. Bold
 and italic are flags and should only be &quot;true&quot; or &quot;false&quot;. If their
 value is something other than &quot;true&quot; or &quot;false&quot;, &quot;false&quot; is assumed.</p>
-<p>You can omit fields to use the values from the style named <tt class="docutils literal"><span class="pre">&quot;default&quot;</span></tt>.</p>
+<p>You can omit fields to use the values from the style named <tt class="docutils literal">&quot;default&quot;</tt>.</p>
 <p>E.g. <tt class="docutils literal"><span class="pre">key=0xff0000;;true</span></tt></p>
 <p>This makes the key style have red foreground text, default background
 color text and bold emphasis.</p>
-<div class="section">
-<h5><a class="toc-backref" href="#id177" id="using-a-named-style" name="using-a-named-style">Using a named style</a></h5>
+<div class="section" id="using-a-named-style">
+<h5><a class="toc-backref" href="#id177">Using a named style</a></h5>
 <p>The second format uses a <em>named style</em> name to reference a style
 defined in filetypes.common.</p>
 <ul class="simple">
-<li><tt class="docutils literal"><span class="pre">key=named_style</span></tt></li>
-<li><tt class="docutils literal"><span class="pre">key2=named_style2,bold,italic</span></tt></li>
+<li><tt class="docutils literal">key=named_style</tt></li>
+<li><tt class="docutils literal">key2=named_style2,bold,italic</tt></li>
 </ul>
 <p>The bold and italic parts are optional, and if present are used to
 toggle the bold or italic flags to the opposite of the named style's
 flags. In contrast to style definition booleans, they are a literal
 &quot;,bold,italic&quot; and commas are used instead of semi-colons.</p>
-<p>E.g. <tt class="docutils literal"><span class="pre">key=comment,italic</span></tt></p>
-<p>This makes the key style match the <tt class="docutils literal"><span class="pre">&quot;comment&quot;</span></tt> named style, but with
+<p>E.g. <tt class="docutils literal">key=comment,italic</tt></p>
+<p>This makes the key style match the <tt class="docutils literal">&quot;comment&quot;</tt> named style, but with
 italic emphasis.</p>
-<p>To define named styles, see the filetypes.common <a class="reference" href="#named-styles-section">[named_styles]
+<p>To define named styles, see the filetypes.common <a class="reference internal" href="#named-styles-section">[named_styles]
 Section</a>.</p>
 </div>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id178" id="keywords-section" name="keywords-section">[keywords] Section</a></h4>
+<div class="section" id="keywords-section">
+<h4><a class="toc-backref" href="#id178">[keywords] Section</a></h4>
 <p>This section contains keys for different keyword lists specific to
 the filetype. Some filetypes do not support keywords, so adding a
 new key will not work. You can only add or remove keywords to/from
@@ -4326,26 +4327,26 @@ an existing list.</p>
 <p class="last">The keywords list must be in one line without line ending characters.</p>
 </div>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id179" id="lexer-properties-section" name="lexer-properties-section">[lexer_properties] Section</a></h4>
+<div class="section" id="lexer-properties-section">
+<h4><a class="toc-backref" href="#id179">[lexer_properties] Section</a></h4>
 <p>Here any special properties for the Scintilla lexer can be set in the
-format <tt class="docutils literal"><span class="pre">key.name.field=some.value</span></tt>.</p>
+format <tt class="docutils literal">key.name.field=some.value</tt>.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id180" id="settings-section" name="settings-section">[settings] Section</a></h4>
+<div class="section" id="settings-section">
+<h4><a class="toc-backref" href="#id180">[settings] Section</a></h4>
 <dl class="docutils">
 <dt>extension</dt>
 <dd><p class="first">This is the default file extension used when saving files, not
-including the period character (<tt class="docutils literal"><span class="pre">.</span></tt>). The extension used should
+including the period character (<tt class="docutils literal">.</tt>). The extension used should
 match one of the patterns associated with that filetype (see
-<a class="reference" href="#filetype-extensions">Filetype extensions</a>).</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">extension=cxx</span></tt></p>
+<a class="reference internal" href="#filetype-extensions">Filetype extensions</a>).</p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">extension=cxx</tt></p>
 </dd>
 <dt>wordchars</dt>
 <dd><p class="first">These characters define word boundaries when making selections
 and searching using word matching options.</p>
 <p><em>Example:</em> (look at system filetypes.* files)</p>
-<div class="last note">
+<div class="note last">
 <p class="first admonition-title">Note</p>
 <p class="last">This can be overridden by the <em>whitespace_chars</em>
 filetypes.common setting.</p>
@@ -4367,19 +4368,19 @@ close the comment.</p>
 column 0 of a line. If set to true it uses any indentation of the
 line.</p>
 <p>Note: Comment indentation</p>
-<p><tt class="docutils literal"><span class="pre">comment_use_indent=true</span></tt> would generate this if a line is
+<p><tt class="docutils literal">comment_use_indent=true</tt> would generate this if a line is
 commented (e.g. with Ctrl-D):</p>
 <pre class="literal-block">
 #command_example();
 </pre>
-<p><tt class="docutils literal"><span class="pre">comment_use_indent=false</span></tt> would generate this if a line is
+<p><tt class="docutils literal">comment_use_indent=false</tt> would generate this if a line is
 commented (e.g. with Ctrl-D):</p>
 <pre class="literal-block">
 #   command_example();
 </pre>
 <p>Note: This setting only works for single line comments (like '//',
 '#' or ';').</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">comment_use_indent=true</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">comment_use_indent=true</tt></p>
 </dd>
 <dt>context_action_cmd</dt>
 <dd><p class="first">A command which can be executed on the current word or the current
@@ -4394,8 +4395,8 @@ it is recommended to specify the full path to the command. The
 wildcard %s will be replaced by the current word at the cursor
 position or by the current selection.</p>
 <p>Hint: for PHP files the following could be quite useful:
-context_action_cmd=firefox &quot;<a class="reference" href="http://www.php.net/%s">http://www.php.net/%s</a>&quot;</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">context_action_cmd=devhelp</span> <span class="pre">-s</span> <span class="pre">&quot;%s&quot;</span></tt></p>
+context_action_cmd=firefox &quot;<a class="reference external" href="http://www.php.net/%s">http://www.php.net/%s</a>&quot;</p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">context_action_cmd=devhelp <span class="pre">-s</span> &quot;%s&quot;</tt></p>
 </dd>
 <dt>tag_parser</dt>
 <dd>The TagManager language name, e.g. &quot;C&quot;.</dd>
@@ -4427,9 +4428,9 @@ doesn't use the lexer_filetype key itself.</dd>
 </dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id181" id="build-settings-section" name="build-settings-section">[build_settings] Section</a></h4>
-<p>As of Geany 0.19 this section is supplemented by the <a class="reference" href="#build-menu-section">[build-menu] Section</a>.
+<div class="section" id="build-settings-section">
+<h4><a class="toc-backref" href="#id181">[build_settings] Section</a></h4>
+<p>As of Geany 0.19 this section is supplemented by the <a class="reference internal" href="#build-menu-section">[build-menu] Section</a>.
 Values that are set in the [build-menu] section will override those in this section.</p>
 <dl class="docutils">
 <dt>error_regex</dt>
@@ -4441,7 +4442,7 @@ a match that is purely digits, and use this for the line number. The
 remaining match will be used as the filename.</p>
 <p><em>Example:</em> <tt class="docutils literal"><span class="pre">error_regex=(.+):([0-9]+):[0-9]+</span></tt></p>
 <p class="last">This will parse a message such as:
-<tt class="docutils literal"><span class="pre">test.py:7:24:</span> <span class="pre">E202</span> <span class="pre">whitespace</span> <span class="pre">before</span> <span class="pre">']'</span></tt></p>
+<tt class="docutils literal">test.py:7:24: E202 whitespace before ']'</tt></p>
 </dd>
 </dl>
 <p><strong>Build commands</strong></p>
@@ -4461,14 +4462,14 @@ spaces. The following wildcards for filenames are available:</p>
 <li>%f -- complete filename without path</li>
 <li>%e -- filename without path and without extension</li>
 </ul>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">compiler=gcc</span> <span class="pre">-Wall</span> <span class="pre">-c</span> <span class="pre">&quot;%f&quot;</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">compiler=gcc <span class="pre">-Wall</span> <span class="pre">-c</span> &quot;%f&quot;</tt></p>
 </dd>
 <dt>linker</dt>
 <dd><p class="first">This item specifies the command to link the file. If the file is not
 already compiled, it will be compiled while linking. The -o option
 is automatically added by Geany. This item works well with GNU gcc,
 but may be problematic with other compilers (esp. with the linker).</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">linker=gcc</span> <span class="pre">-Wall</span> <span class="pre">&quot;%f&quot;</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">linker=gcc <span class="pre">-Wall</span> &quot;%f&quot;</tt></p>
 </dd>
 <dt>run_cmd</dt>
 <dd><p class="first">Use this item to execute your file. It has to have been built
@@ -4480,14 +4481,14 @@ complete filename, e.g. for shell scripts.</p>
 </dl>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id182" id="special-file-filetypes-common" name="special-file-filetypes-common">Special file filetypes.common</a></h3>
+<div class="section" id="special-file-filetypes-common">
+<h3><a class="toc-backref" href="#id182">Special file filetypes.common</a></h3>
 <p>There is a special filetype definition file called
 filetypes.common. This file defines some general non-filetype-specific
 settings.</p>
-<p>See the <a class="reference" href="#format">Format</a> section for how to define styles.</p>
-<div class="section">
-<h4><a class="toc-backref" href="#id183" id="named-styles-section" name="named-styles-section">[named_styles] Section</a></h4>
+<p>See the <a class="reference internal" href="#format">Format</a> section for how to define styles.</p>
+<div class="section" id="named-styles-section">
+<h4><a class="toc-backref" href="#id183">[named_styles] Section</a></h4>
 <p>Named styles declared here can be used in the [styling] section of any
 filetypes.* file.</p>
 <p>For example:</p>
@@ -4506,18 +4507,18 @@ comment=foo
 different files.</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
-<p class="last">You can define aliases for named styles, as shown with the <tt class="docutils literal"><span class="pre">bar</span></tt>
+<p class="last">You can define aliases for named styles, as shown with the <tt class="docutils literal">bar</tt>
 entry in the above example, but they must be declared after the
 original style.</p>
 </div>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id184" id="id5" name="id5">[styling] Section</a></h4>
+<div class="section" id="id5">
+<h4><a class="toc-backref" href="#id184">[styling] Section</a></h4>
 <dl class="docutils">
 <dt>default</dt>
 <dd><p class="first">This is the default style. It is used for styling files without a
 filetype set.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">default=0x000000;0xffffff;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">default=0x000000;0xffffff;false;false</tt></p>
 </dd>
 <dt>selection</dt>
 <dd><p class="first">The style for coloring selected text. The format is:</p>
@@ -4530,28 +4531,28 @@ filetype set.</p>
 <p>The colors are only set if the 3rd or 4th argument is true. When
 the colors are not overridden, the default is a dark grey
 background with syntax highlighted foreground text.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">selection=0xc0c0c0;0x00007F;true;true</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">selection=0xc0c0c0;0x00007F;true;true</tt></p>
 </dd>
 <dt>brace_good</dt>
 <dd><p class="first">The style for brace highlighting when a matching brace was found.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">brace_good=0xff0000;0xFFFFFF;true;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">brace_good=0xff0000;0xFFFFFF;true;false</tt></p>
 </dd>
 <dt>brace_bad</dt>
 <dd><p class="first">The style for brace highlighting when no matching brace was found.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">brace_bad=0x0000ff;0xFFFFFF;true;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">brace_bad=0x0000ff;0xFFFFFF;true;false</tt></p>
 </dd>
 <dt>caret</dt>
 <dd><p class="first">The style for coloring the caret(the blinking cursor). Only first
 and third argument is interpreted.
 Set the third argument to true to change the caret into a block caret.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">caret=0x000000;0x0;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">caret=0x000000;0x0;false;false</tt></p>
 </dd>
 <dt>caret_width</dt>
 <dd><p class="first">The width for the caret(the blinking cursor). Only the first
 argument is interpreted. The width is specified in pixels with
 a maximum of three pixel. Use the width 0 to make the caret
 invisible.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">caret=1;0;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">caret=1;0;false;false</tt></p>
 </dd>
 <dt>current_line</dt>
 <dd><p class="first">The style for coloring the background of the current line. Only
@@ -4559,12 +4560,12 @@ the second and third arguments are interpreted. The second argument
 is the background color. Use the third argument to enable or
 disable background highlighting for the current line (has to be
 true/false).</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">current_line=0x0;0xe5e5e5;true;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">current_line=0x0;0xe5e5e5;true;false</tt></p>
 </dd>
 <dt>indent_guide</dt>
 <dd><p class="first">The style for coloring the indentation guides. Only the first and
 second arguments are interpreted.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">indent_guide=0xc0c0c0;0xffffff;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">indent_guide=0xc0c0c0;0xffffff;false;false</tt></p>
 </dd>
 <dt>white_space</dt>
 <dd><p class="first">The style for coloring the white space if it is shown. The first
@@ -4572,7 +4573,7 @@ both arguments define the foreground and background colors, the
 third argument sets whether to use the defined foreground color
 or to use the color defined by each filetype for the white space.
 The fourth argument defines whether to use the background color.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">white_space=0xc0c0c0;0xffffff;true;true</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">white_space=0xc0c0c0;0xffffff;true;true</tt></p>
 </dd>
 <dt>margin_linenumber</dt>
 <dd>Line number margin foreground and background colors.</dd>
@@ -4598,8 +4599,8 @@ used.</p>
 <li>1 -- for straight lines</li>
 <li>2 -- for curved lines</li>
 </ul>
-<p><em>Default:</em> <tt class="docutils literal"><span class="pre">folding_style=1;1;</span></tt></p>
-<p class="last"><em>Arrows:</em> <tt class="docutils literal"><span class="pre">folding_style=3;0;</span></tt></p>
+<p><em>Default:</em> <tt class="docutils literal">folding_style=1;1;</tt></p>
+<p class="last"><em>Arrows:</em> <tt class="docutils literal">folding_style=3;0;</tt></p>
 </dd>
 <dt>folding_horiz_line</dt>
 <dd><p class="first">Draw a thin horizontal line at the line where text is folded. Only
@@ -4610,7 +4611,7 @@ first argument is used.</p>
 <li>1 -- draw the line above folded text</li>
 <li>2 -- draw the line below folded text</li>
 </ul>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">folding_horiz_line=0;0;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">folding_horiz_line=0;0;false;false</tt></p>
 </dd>
 <dt>line_wrap_visuals</dt>
 <dd><p class="first">First argument: drawing of visual flags to indicate a line is wrapped.
@@ -4629,11 +4630,11 @@ are drawn near the border or near the text. This is a bitmask of the values:</p>
 <li>2 -- Visual flag at begin of subline drawn near text</li>
 </ul>
 <p>Only first and second argument is interpreted.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">line_wrap_visuals=3;0;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">line_wrap_visuals=3;0;false;false</tt></p>
 </dd>
 <dt>line_wrap_indent</dt>
 <dd><p class="first">First argument: sets the size of indentation of sublines for wrapped lines
-in terms of the width of a space, only used when the second argument is <tt class="docutils literal"><span class="pre">0</span></tt>.</p>
+in terms of the width of a space, only used when the second argument is <tt class="docutils literal">0</tt>.</p>
 <p>Second argument: wrapped sublines can be indented to the position of their
 first subline or one more indent level. Possible values:</p>
 <ul class="simple">
@@ -4642,7 +4643,7 @@ first subline or one more indent level. Possible values:</p>
 <li>2 - Wrapped sublines are aligned to first subline indent plus one more level of indentation</li>
 </ul>
 <p>Only first and second argument is interpreted.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">line_wrap_indent=0;1;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">line_wrap_indent=0;1;false;false</tt></p>
 </dd>
 <dt>translucency</dt>
 <dd><p class="first">Translucency for the current line (first argument) and the selection
@@ -4650,27 +4651,27 @@ first subline or one more indent level. Possible values:</p>
 <p>Note for Windows 95, 98 and ME users:
 keep this value at 256 to disable translucency otherwise Geany might crash.</p>
 <p>Only the first and second argument is interpreted.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">translucency=256;256;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">translucency=256;256;false;false</tt></p>
 </dd>
 <dt>marker_line</dt>
 <dd><p class="first">The style for a highlighted line (e.g when using Goto line or goto tag).
 The foreground color (first argument) is only used when the Markers margin
 is enabled (see View menu).</p>
 <p>Only the first and second argument is interpreted.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">marker_line=0x000000;0xffff00;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">marker_line=0x000000;0xffff00;false;false</tt></p>
 </dd>
 <dt>marker_search</dt>
 <dd><p class="first">The style for a marked search results (when using &quot;Mark&quot; in Search dialogs).
 The second argument sets the background colour for the drawn rectangle.</p>
 <p>Only the second argument is interpreted.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">marker_search=0x000000;0xb8f4b8;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">marker_search=0x000000;0xb8f4b8;false;false</tt></p>
 </dd>
 <dt>marker_mark</dt>
 <dd><p class="first">The style for a marked line (e.g when using the &quot;Toggle Marker&quot; keybinding
 (Ctrl-M)). The foreground color (first argument) is only used
 when the Markers margin is enabled (see View menu).</p>
 <p>Only the first and second argument is interpreted.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">marker_mark=0x000000;0xb8f4b8;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">marker_mark=0x000000;0xb8f4b8;false;false</tt></p>
 </dd>
 <dt>marker_translucency</dt>
 <dd><p class="first">Translucency for the line marker (first argument) and the search marker
@@ -4678,30 +4679,30 @@ when the Markers margin is enabled (see View menu).</p>
 <p>Note for Windows 95, 98 and ME users:
 keep this value at 256 to disable translucency otherwise Geany might crash.</p>
 <p>Only the first and second argument is interpreted.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">marker_translucency=256;256;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">marker_translucency=256;256;false;false</tt></p>
 </dd>
 <dt>line_height</dt>
 <dd><p class="first">Amount of space to be drawn above and below the line's baseline.
 The first argument defines the amount of space to be drawn above the line, the second
 argument defines the amount of space to be drawn below.</p>
 <p>Only the first and second argument is interpreted.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">line_height=0;0;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">line_height=0;0;false;false</tt></p>
 </dd>
 <dt>calltips</dt>
 <dd><p class="first">The style for coloring the calltips. The first two arguments
 define the foreground and background colors, the third and fourth
 arguments set whether to use the defined colors.</p>
-<p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">calltips=0xc0c0c0;0xffffff;false;false</span></tt></p>
+<p class="last"><em>Example:</em> <tt class="docutils literal">calltips=0xc0c0c0;0xffffff;false;false</tt></p>
 </dd>
 </dl>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id185" id="id6" name="id6">[settings] Section</a></h4>
+<div class="section" id="id6">
+<h4><a class="toc-backref" href="#id185">[settings] Section</a></h4>
 <dl class="docutils">
 <dt>whitespace_chars</dt>
 <dd><p class="first">Characters to treat as whitespace. These characters are ignored
 when moving, selecting and deleting across word boundaries
-(see <a class="reference" href="#scintilla-keyboard-commands">Scintilla keyboard commands</a>).</p>
+(see <a class="reference internal" href="#scintilla-keyboard-commands">Scintilla keyboard commands</a>).</p>
 <p>This should include space (\s) and tab (\t).</p>
 <p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">whitespace_chars=\s\t!\&quot;#$%&amp;'()*+,-./:;&lt;=&gt;?&#64;[\\]^`{|}~</span></tt></p>
 </dd>
@@ -4709,23 +4710,23 @@ when moving, selecting and deleting across word boundaries
 </div>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id186" id="filetype-extensions" name="filetype-extensions">Filetype extensions</a></h2>
+<div class="section" id="filetype-extensions">
+<h2><a class="toc-backref" href="#id186">Filetype extensions</a></h2>
 <p>To change the default filetype extension used when saving a new file,
-see <a class="reference" href="#filetype-definition-files">Filetype definition files</a>.</p>
+see <a class="reference internal" href="#filetype-definition-files">Filetype definition files</a>.</p>
 <p>You can override the list of file extensions that Geany uses for each
-filetype using the <tt class="docutils literal"><span class="pre">filetype_extensions.conf</span></tt> file.</p>
+filetype using the <tt class="docutils literal">filetype_extensions.conf</tt> file.</p>
 <p>To override the system-wide configuration file, copy it from
-<tt class="docutils literal"><span class="pre">$prefix/share/geany</span></tt> to your configuration directory, usually
-<tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt>. <tt class="docutils literal"><span class="pre">$prefix</span></tt> is the path where Geany is installed
-(see <a class="reference" href="#installation-prefix">Installation prefix</a>).</p>
+<tt class="docutils literal">$prefix/share/geany</tt> to your configuration directory, usually
+<tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt>. <tt class="docutils literal">$prefix</tt> is the path where Geany is installed
+(see <a class="reference internal" href="#installation-prefix">Installation prefix</a>).</p>
 <p>For example:</p>
 <pre class="literal-block">
 % cp /usr/local/share/geany/filetype_extensions.conf /home/username/.config/geany/
 </pre>
 <p>Then edit it and remove all the lines for filetype extensions that
 you do not want to override. The remaining lines can be edited after
-the <tt class="docutils literal"><span class="pre">=</span></tt> sign, using a semi-colon separated list of patterns which
+the <tt class="docutils literal">=</tt> sign, using a semi-colon separated list of patterns which
 should be matched for that filetype.</p>
 <p>For example, to set the filetype extensions for Make, the
 <tt class="docutils literal"><span class="pre">/home/username/.config/geany/filetype_extensions.conf</span></tt> file should
@@ -4735,19 +4736,19 @@ look like:</p>
 Make=Makefile*;*.mk;Buildfile;
 </pre>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id187" id="preferences-file-format" name="preferences-file-format">Preferences File Format</a></h2>
+<div class="section" id="preferences-file-format">
+<h2><a class="toc-backref" href="#id187">Preferences File Format</a></h2>
 <p>The preferences file <tt class="docutils literal"><span class="pre">~/.config/geany/geany.conf</span></tt> holds settings for all the items configured
 in the preferences dialog. This file should not be edited while Geany is running
 as the file will be overwritten when the preferences in Geany are changed or Geany
 is quitted.</p>
-<div class="section">
-<h3><a class="toc-backref" href="#id188" id="hidden-preferences" name="hidden-preferences">Hidden preferences</a></h3>
+<div class="section" id="hidden-preferences">
+<h3><a class="toc-backref" href="#id188">Hidden preferences</a></h3>
 <p>There are some rarely used preferences that are not shown in the Preferences
 dialog. These can be set by editing the preferences file, then
 restarting Geany. Search for the key name, then edit the value. Example:</p>
 <blockquote>
-<tt class="docutils literal"><span class="pre">brace_match_ltgt=true</span></tt></blockquote>
+<tt class="docutils literal">brace_match_ltgt=true</tt></blockquote>
 <div class="note">
 <p class="first admonition-title">Note</p>
 <p class="last">If you just installed or updated Geany, you should restart it
@@ -4780,7 +4781,7 @@ configuration file.</p>
 <tr><td>use_gtk_word_boundaries</td>
 <td>Whether to look for the end of a word when
 using word-boundary related Scintilla
-commands (see <a class="reference" href="#scintilla-keyboard-commands">Scintilla keyboard
+commands (see <a class="reference internal" href="#scintilla-keyboard-commands">Scintilla keyboard
 commands</a>).</td>
 <td>true</td>
 </tr>
@@ -4789,8 +4790,8 @@ commands</a>).</td>
 when editing an existing line (i.e. there
 is some text after the current cursor
 position on the line). Only used when the
-keybinding <tt class="docutils literal"><span class="pre">Complete</span> <span class="pre">snippet</span></tt> is set to
-<tt class="docutils literal"><span class="pre">Space</span></tt>.</td>
+keybinding <tt class="docutils literal">Complete snippet</tt> is set to
+<tt class="docutils literal">Space</tt>.</td>
 <td>false</td>
 </tr>
 <tr><td>show_editor_scrollbars</td>
@@ -4859,8 +4860,8 @@ Messages Window</td>
 </table>
 <p>By default, statusbar_template is empty. This tells Geany to use its
 internal default, which is currently:</p>
-<p><tt class="docutils literal"><span class="pre">line:</span> <span class="pre">%l</span> <span class="pre">/</span> <span class="pre">%L\t</span> <span class="pre">col:</span> <span class="pre">%c\t</span> <span class="pre">sel:</span> <span class="pre">%s\t</span> <span class="pre">%w</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span class="pre">%t</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span class="pre">%mmode:</span> <span class="pre">%M</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span class="pre">encoding:</span> <span class="pre">%e</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span class="pre">filetype:</span> <span class="pre">%f</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span class="pre">scope:</span> <span class="pre">%S</span></tt></p>
-<p>Note that <tt class="docutils literal"><span class="pre">\t</span></tt> = tab.</p>
+<p><tt class="docutils literal">line: %l / %L\t col: %c\t sel: %s\t %w&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; %t&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; %mmode: %M&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; encoding: %e&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; filetype: %f&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; scope: %S</tt></p>
+<p>Note that <tt class="docutils literal">\t</tt> = tab.</p>
 <table border="1" class="docutils">
 <colgroup>
 <col width="34%" />
@@ -4881,7 +4882,7 @@ internal default, which is currently:</p>
 <tr><td>emulation</td>
 <td>Terminal emulation mode. Only change this
 if you have VTE termcap files other than
-<tt class="docutils literal"><span class="pre">vte/termcap/xterm</span></tt>.</td>
+<tt class="docutils literal">vte/termcap/xterm</tt>.</td>
 <td>xterm</td>
 </tr>
 <tr><td>send_selection_unsafe</td>
@@ -4924,7 +4925,7 @@ disk won't run out of free space.</td>
 <td>&nbsp;</td>
 </tr>
 <tr><td>find_selection_type</td>
-<td>See <a class="reference" href="#find-selection">Find selection</a>.</td>
+<td>See <a class="reference internal" href="#find-selection">Find selection</a>.</td>
 <td>0</td>
 </tr>
 <tr><td><strong>Build Menu related</strong></td>
@@ -4949,19 +4950,19 @@ execute section of the Build menu.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id189" id="build-menu-section" name="build-menu-section">[build-menu] Section</a></h3>
+<div class="section" id="build-menu-section">
+<h3><a class="toc-backref" href="#id189">[build-menu] Section</a></h3>
 <p>The [build-menu] section contains the configuration of the build menu.
 This section can occur in filetype, preferences and project files and
 always has the format described here.  Different menu items are loaded
-from different files, see the table in the <a class="reference" href="#build-menu-configuration">Build Menu Configuration</a>
+from different files, see the table in the <a class="reference internal" href="#build-menu-configuration">Build Menu Configuration</a>
 section for details.  All the settings can be configured from the dialogs
 except the execute command in filetype files and filetype definitions in
 the project file, so these are the only ones which need hand editing.</p>
 <p>The build-menu section stores one entry for each setting for each menu item that
 is configured.  The keys for these settings have the format:</p>
 <blockquote>
-<tt class="docutils literal"><span class="pre">GG_NN_FF</span></tt></blockquote>
+<tt class="docutils literal">GG_NN_FF</tt></blockquote>
 <p>where:</p>
 <ul class="simple">
 <li>GG - is the menu item group,<ul>
@@ -4981,28 +4982,28 @@ starting at 00</li>
 </ul>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id190" id="project-file-format" name="project-file-format">Project File Format</a></h2>
+<div class="section" id="project-file-format">
+<h2><a class="toc-backref" href="#id190">Project File Format</a></h2>
 <p>The project file contains project related settings and possibly a
 record of the current session files.</p>
-<div class="section">
-<h3><a class="toc-backref" href="#id191" id="build-menu-additions" name="build-menu-additions">[build-menu] Additions</a></h3>
+<div class="section" id="build-menu-additions">
+<h3><a class="toc-backref" href="#id191">[build-menu] Additions</a></h3>
 <p>The project file also can have extra fields in the [build-menu] section
-in addition to those listed in <a class="reference" href="#build-menu-section">[build-menu] Section</a> above.</p>
+in addition to those listed in <a class="reference internal" href="#build-menu-section">[build-menu] Section</a> above.</p>
 <p>When filetype menu items are configured for the project they are stored
 in the project file.</p>
-<p>The <tt class="docutils literal"><span class="pre">filetypes</span></tt> entry is a list of the filetypes which exist in the
+<p>The <tt class="docutils literal">filetypes</tt> entry is a list of the filetypes which exist in the
 project file.</p>
 <p>For each filetype the entries for that filetype have the format defined in
-<a class="reference" href="#build-menu-section">[build-menu] Section</a> but the key is prefixed by the name of the filetype
-as it appears in the <tt class="docutils literal"><span class="pre">filetypes</span></tt> entry, eg the entry for the label of
+<a class="reference internal" href="#build-menu-section">[build-menu] Section</a> but the key is prefixed by the name of the filetype
+as it appears in the <tt class="docutils literal">filetypes</tt> entry, eg the entry for the label of
 filetype menu item 0 for the C filetype would be</p>
 <blockquote>
-<tt class="docutils literal"><span class="pre">CFT_00_LB=Label</span></tt></blockquote>
+<tt class="docutils literal">CFT_00_LB=Label</tt></blockquote>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id192" id="templates" name="templates">Templates</a></h2>
+<div class="section" id="templates">
+<h2><a class="toc-backref" href="#id192">Templates</a></h2>
 <p>Geany supports the following templates:</p>
 <ul class="simple">
 <li>ChangeLog entry</li>
@@ -5030,17 +5031,17 @@ instead.</p>
 save a file in the user's template configuration directory. You can
 also force this by selecting <em>Tools-&gt;Reload Configuration</em>.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id193" id="template-meta-data" name="template-meta-data">Template meta data</a></h3>
+<div class="section" id="template-meta-data">
+<h3><a class="toc-backref" href="#id193">Template meta data</a></h3>
 <p>Meta data can be used with all templates, but by default user set
 meta data is only used for the ChangeLog and File header templates.</p>
 <p>In the configuration dialog you can find a tab &quot;Templates&quot; (see
-<a class="reference" href="#template-preferences">Template preferences</a>). You can define the default values
+<a class="reference internal" href="#template-preferences">Template preferences</a>). You can define the default values
 which will be inserted in the templates. You should select
 <em>Tools-&gt;Reload Configuration</em> or restart Geany after making changes.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id194" id="file-templates" name="file-templates">File templates</a></h3>
+<div class="section" id="file-templates">
+<h3><a class="toc-backref" href="#id194">File templates</a></h3>
 <p>File templates are templates used as the basis of a new file. To
 use them, choose the <em>New (with Template)</em> menu item from the <em>File</em>
 menu.</p>
@@ -5048,25 +5049,25 @@ menu.</p>
 file templates can be added by creating the appropriate template file. You can
 also edit the default file templates.</p>
 <p>The file's contents are just the text to place in the document, with
-optional template wildcards like <tt class="docutils literal"><span class="pre">{fileheader}</span></tt>. The fileheader
+optional template wildcards like <tt class="docutils literal">{fileheader}</tt>. The fileheader
 wildcard can be placed anywhere, but it's usually put on the first
 line of the file, followed by a blank line.</p>
-<div class="section">
-<h4><a class="toc-backref" href="#id195" id="custom-file-templates" name="custom-file-templates">Custom file templates</a></h4>
+<div class="section" id="custom-file-templates">
+<h4><a class="toc-backref" href="#id195">Custom file templates</a></h4>
 <p>These are read from the following directories:</p>
 <ul class="simple">
-<li><tt class="docutils literal"><span class="pre">$prefix/share/geany/templates/files</span></tt> (see <a class="reference" href="#installation-prefix">Installation prefix</a>)</li>
+<li><tt class="docutils literal">$prefix/share/geany/templates/files</tt> (see <a class="reference internal" href="#installation-prefix">Installation prefix</a>)</li>
 <li><tt class="docutils literal"><span class="pre">~/.config/geany/templates/files</span></tt> (created the first time
 Geany is started).</li>
 </ul>
 <p>The filetype to use is detected from the template file's extension, if
-any. For example, creating a file <tt class="docutils literal"><span class="pre">module.c</span></tt> would add a menu item
+any. For example, creating a file <tt class="docutils literal">module.c</tt> would add a menu item
 which created a new document with the filetype set to 'C'.</p>
 <p>The template file is read from disk when the corresponding menu item is
 clicked.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id196" id="filetype-templates" name="filetype-templates">Filetype templates</a></h4>
+<div class="section" id="filetype-templates">
+<h4><a class="toc-backref" href="#id196">Filetype templates</a></h4>
 <div class="note">
 <p class="first admonition-title">Note</p>
 <p class="last">It's recommended to use custom file templates instead.</p>
@@ -5076,21 +5077,21 @@ directory, and are named &quot;filetype.&quot; followed by the filetype
 name, e.g. &quot;filetype.python&quot;, &quot;filetype.sh&quot;, etc. If you are
 unsure about the filetype name extensions, they are the same as
 the filetype configuration file extensions, commonly installed in
-<tt class="docutils literal"><span class="pre">/usr/share/geany</span></tt>, with the prefix &quot;filetypes.&quot;.</p>
-<p>There is also a template file <tt class="docutils literal"><span class="pre">filetype.none</span></tt> which is used when
+<tt class="docutils literal">/usr/share/geany</tt>, with the prefix &quot;filetypes.&quot;.</p>
+<p>There is also a template file <tt class="docutils literal">filetype.none</tt> which is used when
 the New command is used without a filetype. This is empty by default.</p>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id197" id="customizing-templates" name="customizing-templates">Customizing templates</a></h3>
+<div class="section" id="customizing-templates">
+<h3><a class="toc-backref" href="#id197">Customizing templates</a></h3>
 <p>Each template can be customized to your needs. The templates are
 stored in the <tt class="docutils literal"><span class="pre">~/.config/geany/templates/</span></tt> directory (see the section called
-<a class="reference" href="#command-line-options">Command line options</a> for further information about the configuration
+<a class="reference internal" href="#command-line-options">Command line options</a> for further information about the configuration
 directory). Just open the desired template with an editor (ideally,
 Geany ;-) ) and edit the template to your needs. There are some
 wildcards which will be automatically replaced by Geany at startup.</p>
-<div class="section">
-<h4><a class="toc-backref" href="#id198" id="template-wildcards" name="template-wildcards">Template wildcards</a></h4>
+<div class="section" id="template-wildcards">
+<h4><a class="toc-backref" href="#id198">Template wildcards</a></h4>
 <p>All wildcards must be enclosed by &quot;{&quot; and &quot;}&quot;, e.g. {date}.</p>
 <p><strong>Wildcards for character escaping</strong></p>
 <table border="1" class="docutils">
@@ -5123,7 +5124,7 @@ snippets).</td>
 </tbody>
 </table>
 <p><strong>Global wildcards</strong></p>
-<p>These are configurable, see <a class="reference" href="#template-preferences">Template preferences</a>.</p>
+<p>These are configurable, see <a class="reference internal" href="#template-preferences">Template preferences</a>.</p>
 <table border="1" class="docutils">
 <colgroup>
 <col width="14%" />
@@ -5172,9 +5173,9 @@ bsd, gpl, snippets.</td>
 </table>
 <p><strong>Date &amp; time wildcards</strong></p>
 <p>The format for these wildcards can be changed in the preferences
-dialog, see <a class="reference" href="#template-preferences">Template preferences</a>. You can use any conversion
+dialog, see <a class="reference internal" href="#template-preferences">Template preferences</a>. You can use any conversion
 specifiers which can be used with the ANSI C strftime function.
-For details please see <a class="reference" href="http://man.cx/strftime">http://man.cx/strftime</a>.</p>
+For details please see <a class="reference external" href="http://man.cx/strftime">http://man.cx/strftime</a>.</p>
 <table border="1" class="docutils">
 <colgroup>
 <col width="14%" />
@@ -5265,7 +5266,7 @@ template.</td>
 <tr><td>command:path</td>
 <td>Executes the specified command and replace
 the wildcard with the command's standard
-output. See <a class="reference" href="#special-command-wildcard">Special {command:} wildcard</a>
+output. See <a class="reference internal" href="#special-command-wildcard">Special {command:} wildcard</a>
 for details.</td>
 <td>file templates, file header,
 function description, ChangeLog entry,
@@ -5303,8 +5304,8 @@ templates.</td>
 </tr>
 </tbody>
 </table>
-<div class="section">
-<h5><a class="toc-backref" href="#id199" id="special-command-wildcard" name="special-command-wildcard">Special {command:} wildcard</a></h5>
+<div class="section" id="special-command-wildcard">
+<h5><a class="toc-backref" href="#id199">Special {command:} wildcard</a></h5>
 <p>The {command:} wildcard is a special one because it can execute
 a specified command and put the command's output (stdout) into
 the template.</p>
@@ -5319,10 +5320,10 @@ Linux localhost 2.6.9-023stab046.2-smp #1 SMP Mon Dec 10 15:04:55 MSK 2007 x86_6
 <p>Using this wildcard you can insert nearly any arbitrary text into the
 template.</p>
 <p>In the environment of the executed command the variables
-<tt class="docutils literal"><span class="pre">GEANY_FILENAME</span></tt>, <tt class="docutils literal"><span class="pre">GEANY_FILETYPE</span></tt> and <tt class="docutils literal"><span class="pre">GEANY_FUNCNAME</span></tt> are set.
+<tt class="docutils literal">GEANY_FILENAME</tt>, <tt class="docutils literal">GEANY_FILETYPE</tt> and <tt class="docutils literal">GEANY_FUNCNAME</tt> are set.
 The value of these variables is filled in only if Geany knows about it.
-For example, <tt class="docutils literal"><span class="pre">GEANY_FUNCNAME</span></tt> is only filled within the function
-description template. However, these variables are <tt class="docutils literal"><span class="pre">always</span></tt> set,
+For example, <tt class="docutils literal">GEANY_FUNCNAME</tt> is only filled within the function
+description template. However, these variables are <tt class="docutils literal">always</tt> set,
 just maybe with an empty value.
 You can easily access them e.g. within an executed shell script using:</p>
 <pre class="literal-block">
@@ -5338,18 +5339,18 @@ standard error and in the Help-&gt;Debug Messages dialog.</p>
 </div>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id200" id="customizing-the-toolbar" name="customizing-the-toolbar">Customizing the toolbar</a></h2>
+<div class="section" id="customizing-the-toolbar">
+<h2><a class="toc-backref" href="#id200">Customizing the toolbar</a></h2>
 <p>You can add, remove and reorder the elements in the toolbar by using the toolbar editor
-by manually editing the file <tt class="docutils literal"><span class="pre">ui_toolbar.xml</span></tt>.</p>
+by manually editing the file <tt class="docutils literal">ui_toolbar.xml</tt>.</p>
 <p>The toolbar editor can be opened from the preferences editor on the Toolbar tab or
 by right-clicking on the toolbar itself and choosing it from the menu.</p>
-<div class="section">
-<h3><a class="toc-backref" href="#id201" id="manually-editing-of-the-toolbar-layout" name="manually-editing-of-the-toolbar-layout">Manually editing of the toolbar layout</a></h3>
+<div class="section" id="manually-editing-of-the-toolbar-layout">
+<h3><a class="toc-backref" href="#id201">Manually editing of the toolbar layout</a></h3>
 <p>To override the system-wide configuration file, copy it from
-<tt class="docutils literal"><span class="pre">$prefix/share/geany</span></tt> to your configuration directory, usually
-<tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt>. <tt class="docutils literal"><span class="pre">$prefix</span></tt> is the path where Geany is installed
-(see <a class="reference" href="#installation-prefix">Installation prefix</a>).</p>
+<tt class="docutils literal">$prefix/share/geany</tt> to your configuration directory, usually
+<tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt>. <tt class="docutils literal">$prefix</tt> is the path where Geany is installed
+(see <a class="reference internal" href="#installation-prefix">Installation prefix</a>).</p>
 <p>For example:</p>
 <pre class="literal-block">
 % cp /usr/local/share/geany/ui_toolbar.xml /home/username/.config/geany/
@@ -5368,8 +5369,8 @@ will be used instead.</p>
 </ol>
 </div>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id202" id="available-toolbar-elements" name="available-toolbar-elements">Available toolbar elements</a></h3>
+<div class="section" id="available-toolbar-elements">
+<h3><a class="toc-backref" href="#id202">Available toolbar elements</a></h3>
 <table border="1" class="docutils">
 <colgroup>
 <col width="19%" />
@@ -5482,14 +5483,14 @@ use 'SearchEntry')</td>
 </div>
 </div>
 </div>
-<div class="section">
-<h1><a class="toc-backref" href="#id203" id="plugin-documentation" name="plugin-documentation">Plugin documentation</a></h1>
-<div class="section">
-<h2><a class="toc-backref" href="#id204" id="htmlchars" name="htmlchars">HTMLChars</a></h2>
+<div class="section" id="plugin-documentation">
+<h1><a class="toc-backref" href="#id203">Plugin documentation</a></h1>
+<div class="section" id="htmlchars">
+<h2><a class="toc-backref" href="#id204">HTMLChars</a></h2>
 <p>The HTMLChars plugin helps when working with special characters in
 XML/HTML, e.g. German Umlauts �� and ��.</p>
-<div class="section">
-<h3><a class="toc-backref" href="#id205" id="insert-entity-dialog" name="insert-entity-dialog">Insert entity dialog</a></h3>
+<div class="section" id="insert-entity-dialog">
+<h3><a class="toc-backref" href="#id205">Insert entity dialog</a></h3>
 <p>When the plugin is enabled, you can insert special character
 entities using <em>Tools-&gt;Insert Special HTML Characters</em>.</p>
 <p>This opens up a dialog where you can find a huge amount of special
@@ -5500,8 +5501,8 @@ desired character click on it and choose &quot;Insert&quot;. This will insert
 the entity for the character at the current cursor position. You
 might also like to double click the chosen entity instead.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id206" id="replace-special-chars-by-its-entity" name="replace-special-chars-by-its-entity">Replace special chars by its entity</a></h3>
+<div class="section" id="replace-special-chars-by-its-entity">
+<h3><a class="toc-backref" href="#id206">Replace special chars by its entity</a></h3>
 <p>To help make a XML/HTML document valid the plugin supports
 replacement of special chars known by the plugin. Both bulk
 replacement and immediate replacement during typing are supported.</p>
@@ -5516,8 +5517,8 @@ replacement and immediate replacement during typing are supported.</p>
 </ul>
 </dd>
 </dl>
-<div class="section">
-<h4><a class="toc-backref" href="#id207" id="at-typing-time" name="at-typing-time">At typing time</a></h4>
+<div class="section" id="at-typing-time">
+<h4><a class="toc-backref" href="#id207">At typing time</a></h4>
 <p>You can activate/deactivate this feature using the <em>Tools-&gt;HTML
 Replacement-&gt;Auto-replace Special Characters</em> menu item. If it's
 activated, all special characters (beside the given exceptions from
@@ -5525,8 +5526,8 @@ above) known by the plugin will be replaced by their entities.</p>
 <p>You could also set a keybinding for the plugin to toggle the status
 of this feature.</p>
 </div>
-<div class="section">
-<h4><a class="toc-backref" href="#id208" id="bulk-replacement" name="bulk-replacement">Bulk replacement</a></h4>
+<div class="section" id="bulk-replacement">
+<h4><a class="toc-backref" href="#id208">Bulk replacement</a></h4>
 <p>After inserting a huge amount of text, e.g. by using copy &amp; paste, the
 plugin allows bulk replacement of all known characters (beside the
 mentioned exceptions). You can find the function under the same
@@ -5535,10 +5536,10 @@ configure a keybinding for the plugin.</p>
 </div>
 </div>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id209" id="save-actions" name="save-actions">Save Actions</a></h2>
-<div class="section">
-<h3><a class="toc-backref" href="#id210" id="instant-save" name="instant-save">Instant Save</a></h3>
+<div class="section" id="save-actions">
+<h2><a class="toc-backref" href="#id209">Save Actions</a></h2>
+<div class="section" id="instant-save">
+<h3><a class="toc-backref" href="#id210">Instant Save</a></h3>
 <p>This plugin sets on every new file (<em>File-&gt;New</em> or <em>File-&gt;New (with template)</em>)
 a randomly chosen filename and set its filetype appropriate to the used template
 or when no template was used, to a configurable default filetype.
@@ -5547,8 +5548,8 @@ need to give it an explicit filename using the Save As dialog. This might be
 useful when you often create new files just for testing some code or something
 similar.</p>
 </div>
-<div class="section">
-<h3><a class="toc-backref" href="#id211" id="backup-copy" name="backup-copy">Backup Copy</a></h3>
+<div class="section" id="backup-copy">
+<h3><a class="toc-backref" href="#id211">Backup Copy</a></h3>
 <p>This plugin creates a backup copy of the current file in Geany when it is
 saved. You can specify the directory where the backup copy is saved and
 you can configure the automatically added extension in the configure dialog
@@ -5557,17 +5558,46 @@ in Geany's plugin manager.</p>
 copied into the configured backup directory when the file is saved in Geany.</p>
 </div>
 </div>
+<div class="section" id="xml-snippets">
+<h2><a class="toc-backref" href="#id212">XML Snippets</a></h2>
+<p>This plugin extends XML/HTML tag autocompletion provided by Geany (see
+<a class="reference internal" href="#completions">Completions</a>).  It automatically inserts a matching snippet (see
+<a class="reference internal" href="#user-definable-snippets">User-definable snippets</a>) after you type an opening tag.  For example, using
+this plugin to automatically insert a table template is as easy as turning on
+the plugin and adding the following snippet to the <tt class="docutils literal">[HTML]</tt> section in your
+<tt class="docutils literal">snippets.conf</tt>:</p>
+<pre class="literal-block">
+&lt;table&gt;=\n\t&lt;tr&gt;\n\t\t&lt;td&gt;%cursor%&lt;/td&gt;\n\t&lt;/tr&gt;\n&lt;/table&gt;
+</pre>
+<p>This functionality was present in previous versions of Geany, but, in contrast
+to the plugin, it did not allow the template to be customized.</p>
+<dl class="docutils">
+<dt>Notes:</dt>
+<dd><ul class="first last simple">
+<li>the plugin requires snippet names to contain brackets.  It allows you to
+define snippets, which need not to be automatically inserted, without any
+name clashes.</li>
+<li>the snippet itself should contain only the part that follows an opening
+tag.  It allows for autocompletion in case you typed some attributes in the
+opening tag.</li>
+</ul>
+</dd>
+</dl>
+<p>You can use this plugin together with built-in tag autocompletion.  Tags, for
+which you defined snippets, will be completed by the plugin; Geany will deal
+with other tags.</p>
+</div>
 </div>
-<div class="section">
-<h1><a class="toc-backref" href="#id212" id="contributing-to-this-document" name="contributing-to-this-document">Contributing to this document</a></h1>
-<p>This document (<tt class="docutils literal"><span class="pre">geany.txt</span></tt>) is written in <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a>
-(or &quot;reST&quot;). The source file for it is located in Geany's <tt class="docutils literal"><span class="pre">doc</span></tt>
+<div class="section" id="contributing-to-this-document">
+<h1><a class="toc-backref" href="#id213">Contributing to this document</a></h1>
+<p>This document (<tt class="docutils literal">geany.txt</tt>) is written in <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a>
+(or &quot;reST&quot;). The source file for it is located in Geany's <tt class="docutils literal">doc</tt>
 subdirectory.  If you intend on making changes, you should grab the
 source right from SVN to make sure you've got the newest version. After
 editing the file, to build the HTML document to see how your changes
-look, run &quot;<tt class="docutils literal"><span class="pre">make</span> <span class="pre">doc</span></tt>&quot; in the subdirectory <tt class="docutils literal"><span class="pre">doc</span></tt> of Geany's source
-directory. This regenerates the <tt class="docutils literal"><span class="pre">geany.html</span></tt> file. To generate a PDF
-file, use the command &quot;<tt class="docutils literal"><span class="pre">make</span> <span class="pre">pdf</span></tt>&quot; which should generate a file called
+look, run &quot;<tt class="docutils literal">make doc</tt>&quot; in the subdirectory <tt class="docutils literal">doc</tt> of Geany's source
+directory. This regenerates the <tt class="docutils literal">geany.html</tt> file. To generate a PDF
+file, use the command &quot;<tt class="docutils literal">make pdf</tt>&quot; which should generate a file called
 geany-0.20.pdf.</p>
 <p>After you are happy with your changes, create a patch:</p>
 <pre class="literal-block">
@@ -5578,17 +5608,17 @@ geany-0.20.pdf.</p>
 to build the docs. The package is named <tt class="docutils literal"><span class="pre">python-docutils</span></tt> on Debian
 and Fedora systems.</p>
 </div>
-<div class="section">
-<h1><a class="toc-backref" href="#id213" id="scintilla-keyboard-commands" name="scintilla-keyboard-commands">Scintilla keyboard commands</a></h1>
+<div class="section" id="scintilla-keyboard-commands">
+<h1><a class="toc-backref" href="#id214">Scintilla keyboard commands</a></h1>
 <p>Copyright �� 1998, 2006 Neil Hodgson &lt;neilh(at)scintilla(dot)org&gt;</p>
 <p>This appendix is distributed under the terms of the License for
 Scintilla and SciTE. A copy of this license can be found in the file
-<tt class="docutils literal"><span class="pre">scintilla/License.txt</span></tt> included with the source code of this
-program and in the appendix of this document. See <a class="reference" href="#license-for-scintilla-and-scite">License for
+<tt class="docutils literal">scintilla/License.txt</tt> included with the source code of this
+program and in the appendix of this document. See <a class="reference internal" href="#license-for-scintilla-and-scite">License for
 Scintilla and SciTE</a>.</p>
 <p>20 June 2006</p>
-<div class="section">
-<h2><a class="toc-backref" href="#id214" id="keyboard-commands" name="keyboard-commands">Keyboard commands</a></h2>
+<div class="section" id="keyboard-commands">
+<h2><a class="toc-backref" href="#id215">Keyboard commands</a></h2>
 <p>Keyboard commands for Scintilla mostly follow common Windows and GTK+
 conventions. All move keys (arrows, page up/down, home and end)
 allows to extend or reduce the stream selection when holding the
@@ -5669,10 +5699,10 @@ menus. Some less common commands with no menu equivalent are:</p>
 </table>
 </div>
 </div>
-<div class="section">
-<h1><a class="toc-backref" href="#id215" id="tips-and-tricks" name="tips-and-tricks">Tips and tricks</a></h1>
-<div class="section">
-<h2><a class="toc-backref" href="#id216" id="document-notebook" name="document-notebook">Document notebook</a></h2>
+<div class="section" id="tips-and-tricks">
+<h1><a class="toc-backref" href="#id216">Tips and tricks</a></h1>
+<div class="section" id="document-notebook">
+<h2><a class="toc-backref" href="#id217">Document notebook</a></h2>
 <ul class="simple">
 <li>Double-click on empty space in the notebook tab bar to open a
 new document.</li>
@@ -5684,8 +5714,8 @@ widgets (to show them again use the View menu or the keyboard
 shortcut). The interface pref must be enabled for this to work.</li>
 </ul>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id217" id="editor" name="editor">Editor</a></h2>
+<div class="section" id="editor">
+<h2><a class="toc-backref" href="#id218">Editor</a></h2>
 <ul class="simple">
 <li>Alt-scroll wheel moves up/down a page.</li>
 <li>Ctrl-scroll wheel zooms in/out.</li>
@@ -5694,14 +5724,14 @@ shortcut). The interface pref must be enabled for this to work.</li>
 <li>Ctrl-click on a bracket/brace to perform <em>Go to Matching Brace</em>.</li>
 </ul>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id218" id="interface" name="interface">Interface</a></h2>
+<div class="section" id="interface">
+<h2><a class="toc-backref" href="#id219">Interface</a></h2>
 <ul class="simple">
 <li>Double-click on a symbol-list group to expand or compact it.</li>
 </ul>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id219" id="gtk-related" name="gtk-related">GTK-related</a></h2>
+<div class="section" id="gtk-related">
+<h2><a class="toc-backref" href="#id220">GTK-related</a></h2>
 <ul class="simple">
 <li>Scrolling the mouse wheel over a notebook tab bar will switch
 notebook pages.</li>
@@ -5715,20 +5745,20 @@ position without having to drag it.</li>
 </ul>
 </div>
 </div>
-<div class="section">
-<h1><a class="toc-backref" href="#id220" id="compile-time-options" name="compile-time-options">Compile-time options</a></h1>
+<div class="section" id="compile-time-options">
+<h1><a class="toc-backref" href="#id221">Compile-time options</a></h1>
 <p>There are some options which can only be changed at compile time,
 and some options which are used as the default for configurable
 options. To change these options, edit the appropriate source file
-in the <tt class="docutils literal"><span class="pre">src</span></tt> subdirectory. Look for a block of lines starting with
-<tt class="docutils literal"><span class="pre">#define</span> <span class="pre">GEANY_*</span></tt>. Any definitions which are not listed here should
+in the <tt class="docutils literal">src</tt> subdirectory. Look for a block of lines starting with
+<tt class="docutils literal">#define GEANY_*</tt>. Any definitions which are not listed here should
 not be changed.</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
 <p class="last">Most users should not need to change these options.</p>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id221" id="src-geany-h" name="src-geany-h">src/geany.h</a></h2>
+<div class="section" id="src-geany-h">
+<h2><a class="toc-backref" href="#id222">src/geany.h</a></h2>
 <table border="1" class="docutils">
 <colgroup>
 <col width="33%" />
@@ -5784,8 +5814,8 @@ when building on a non-Win32 system.</em></td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id222" id="project-h" name="project-h">project.h</a></h2>
+<div class="section" id="project-h">
+<h2><a class="toc-backref" href="#id223">project.h</a></h2>
 <table border="1" class="docutils">
 <colgroup>
 <col width="33%" />
@@ -5809,8 +5839,8 @@ open dialog.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id223" id="editor-h" name="editor-h">editor.h</a></h2>
+<div class="section" id="editor-h">
+<h2><a class="toc-backref" href="#id224">editor.h</a></h2>
 <table border="1" class="docutils">
 <colgroup>
 <col width="33%" />
@@ -5835,9 +5865,9 @@ underscore.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id224" id="keyfile-c" name="keyfile-c">keyfile.c</a></h2>
-<p>These are default settings that can be overridden in the <a class="reference" href="#preferences">Preferences</a> dialog.</p>
+<div class="section" id="keyfile-c">
+<h2><a class="toc-backref" href="#id225">keyfile.c</a></h2>
+<p>These are default settings that can be overridden in the <a class="reference internal" href="#preferences">Preferences</a> dialog.</p>
 <table border="1" class="docutils">
 <colgroup>
 <col width="33%" />
@@ -5916,8 +5946,8 @@ Geany provide.</td>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h2><a class="toc-backref" href="#id225" id="build-c" name="build-c">build.c</a></h2>
+<div class="section" id="build-c">
+<h2><a class="toc-backref" href="#id226">build.c</a></h2>
 <table border="1" class="docutils">
 <colgroup>
 <col width="33%" />
@@ -5949,7 +5979,7 @@ and unaffected by this value.</td>
 <td>Every time a build menu item priority
 calculation is run, print the state of the
 menu item table in the form of the table
-in <a class="reference" href="#build-menu-configuration">Build Menu Configuration</a>.  May be
+in <a class="reference internal" href="#build-menu-configuration">Build Menu Configuration</a>.  May be
 useful to debug configuration file
 overloading.  Warning produces a lot of
 output.  Can also be enabled/disabled by the
@@ -5961,8 +5991,8 @@ overriding the compile setting.</td>
 </table>
 </div>
 </div>
-<div class="section">
-<h1><a class="toc-backref" href="#id226" id="gnu-general-public-license" name="gnu-general-public-license">GNU General Public License</a></h1>
+<div class="section" id="gnu-general-public-license">
+<h1><a class="toc-backref" href="#id227">GNU General Public License</a></h1>
 <pre class="literal-block">
             GNU GENERAL PUBLIC LICENSE
                Version 2, June 1991
@@ -6306,8 +6336,8 @@ library.  If this is what you want to do, use the GNU Library General
 Public License instead of this License.
 </pre>
 </div>
-<div class="section">
-<h1><a class="toc-backref" href="#id227" id="license-for-scintilla-and-scite" name="license-for-scintilla-and-scite">License for Scintilla and SciTE</a></h1>
+<div class="section" id="license-for-scintilla-and-scite">
+<h1><a class="toc-backref" href="#id228">License for Scintilla and SciTE</a></h1>
 <p>Copyright 1998-2003 by Neil Hodgson &lt;neilh(at)scintilla(dot)org&gt;</p>
 <p>All Rights Reserved</p>
 <p>Permission to use, copy, modify, and distribute this software and
@@ -6326,9 +6356,9 @@ USE OR PERFORMANCE OF THIS SOFTWARE.</p>
 </div>
 <div class="footer">
 <hr class="footer" />
-<a class="reference" href="geany.txt">View document source</a>.
-Generated on: 2010-11-07 18:52 UTC.
-Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
+<a class="reference external" href="geany.txt">View document source</a>.
+Generated on: 2010-11-08 09:04 UTC.
+Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
 
 </div>
 </body>
diff --git a/doc/geany.txt b/doc/geany.txt
index e839e04..22b21cf 100644
--- a/doc/geany.txt
+++ b/doc/geany.txt
@@ -4673,6 +4673,34 @@ After the plugin was loaded in Geany's plugin manager, every file is
 copied into the configured backup directory when the file is saved in Geany.
 
 
+XML Snippets
+------------
+
+This plugin extends XML/HTML tag autocompletion provided by Geany (see
+`Completions`_).  It automatically inserts a matching snippet (see
+`User-definable snippets`_) after you type an opening tag.  For example, using
+this plugin to automatically insert a table template is as easy as turning on
+the plugin and adding the following snippet to the ``[HTML]`` section in your
+``snippets.conf``::
+
+  <table>=\n\t<tr>\n\t\t<td>%cursor%</td>\n\t</tr>\n</table>
+
+This functionality was present in previous versions of Geany, but, in contrast
+to the plugin, it did not allow the template to be customized.
+
+Notes:
+  * the plugin requires snippet names to contain brackets.  It allows you to
+    define snippets, which need not to be automatically inserted, without any
+    name clashes.
+  * the snippet itself should contain only the part that follows an opening
+    tag.  It allows for autocompletion in case you typed some attributes in the
+    opening tag.
+
+You can use this plugin together with built-in tag autocompletion.  Tags, for
+which you defined snippets, will be completed by the plugin; Geany will deal
+with other tags.
+
+
 
 Contributing to this document
 =============================
diff --git a/plugins/Makefile.am b/plugins/Makefile.am
index 9c5b488..d7c9dab 100644
--- a/plugins/Makefile.am
+++ b/plugins/Makefile.am
@@ -25,6 +25,7 @@ export_la_LDFLAGS        = -module -avoid-version
 saveactions_la_LDFLAGS   = -module -avoid-version
 filebrowser_la_LDFLAGS   = -module -avoid-version
 splitwindow_la_LDFLAGS   = -module -avoid-version
+xmlsnippets_la_LDFLAGS   = -module -avoid-version
 
 if PLUGINS
 
@@ -50,7 +51,8 @@ all-local: \
 	htmlchars.dll \
 	export.dll \
 	saveactions.dll \
-	filebrowser.dll
+	filebrowser.dll \
+	xmlsnippets.dll
 # Split Window is broken on Windows
 #	splitwindow.dll
 
@@ -70,7 +72,8 @@ plugin_LTLIBRARIES = \
 	export.la \
 	saveactions.la \
 	filebrowser.la \
-	splitwindow.la
+	splitwindow.la \
+	xmlsnippets.la
 
 # Plugins not to be installed
 noinst_LTLIBRARIES = \
@@ -83,6 +86,7 @@ export_la_SOURCES        = export.c
 saveactions_la_SOURCES   = saveactions.c
 filebrowser_la_SOURCES   = filebrowser.c
 splitwindow_la_SOURCES   = splitwindow.c
+xmlsnippets_la_SOURCES   = xmlsnippets.c
 
 demoplugin_la_CFLAGS    = -DG_LOG_DOMAIN=\""Demoplugin"\"
 classbuilder_la_CFLAGS  = -DG_LOG_DOMAIN=\""Classbuilder"\"
@@ -91,6 +95,7 @@ export_la_CFLAGS        = -DG_LOG_DOMAIN=\""Export"\"
 saveactions_la_CFLAGS   = -DG_LOG_DOMAIN=\""SaveActions"\"
 filebrowser_la_CFLAGS   = -DG_LOG_DOMAIN=\""FileBrowser"\"
 splitwindow_la_CFLAGS   = -DG_LOG_DOMAIN=\""SplitWindow"\"
+xmlsnippets_la_CFLAGS   = -DG_LOG_DOMAIN=\""XMLSnippets"\"
 
 demoplugin_la_LIBADD    = $(GTK_LIBS)
 classbuilder_la_LIBADD  = $(GTK_LIBS)
@@ -99,6 +104,7 @@ export_la_LIBADD        = $(GTK_LIBS)
 saveactions_la_LIBADD   = $(GTK_LIBS)
 filebrowser_la_LIBADD   = $(GTK_LIBS)
 splitwindow_la_LIBADD   = $(GTK_LIBS)
+xmlsnippets_la_LIBADD   = $(GTK_LIBS)
 
 endif # MINGW
 endif # PLUGINS
diff --git a/plugins/makefile.win32 b/plugins/makefile.win32
index e66a572..fb59a70 100644
--- a/plugins/makefile.win32
+++ b/plugins/makefile.win32
@@ -56,7 +56,8 @@ plugins: \
 		classbuilder.dll \
 		export.dll \
 		saveactions.dll \
-		filebrowser.dll
+		filebrowser.dll \
+		xmlsnippets.dll
 
 # Split Window is broken on Windows
 #		splitwindow.dll
diff --git a/po/POTFILES.in b/po/POTFILES.in
index 975bc31..808ccbb 100644
--- a/po/POTFILES.in
+++ b/po/POTFILES.in
@@ -45,3 +45,4 @@ plugins/export.c
 plugins/filebrowser.c
 plugins/saveactions.c
 plugins/splitwindow.c
+plugins/xmlsnippets.c
\ No newline at end of file
diff --git a/po/ru.po b/po/ru.po
index 3b6bccc..e333dbf 100644
--- a/po/ru.po
+++ b/po/ru.po
@@ -1,5 +1,5 @@
-# Translation Geany to Russian. 
-# Copyright (C) Geany development team. 
+# Translation Geany to Russian.
+# Copyright (C) Geany development team.
 # This file is distributed under the same license as the Geany package.
 # John Wehin <john.wehin@gmail.com>, 2008-2009.
 # Denis Koryavov <dkoryavov@yandex.ru>, 2010.
@@ -5345,6 +5345,14 @@ msgstr "������������������ ���� ����������������������"
 msgid "Split Vertically"
 msgstr "������������������ ���� ������������������"
 
+#: ../plugins/xmlsnippets.c:37
+msgid "XML Snippets"
+msgstr "XML ����������������"
+
+#: ../plugins/xmlsnippets.c:37
+msgid "Autocompletes XML/HTML tags using snippets."
+msgstr "������������������ XML/HTML �������� �� ���������������������������� ������������������"
+
 #~ msgid "Fixed s_trings"
 #~ msgstr "_�������������������������� ������������"
 
diff --git a/wscript b/wscript
index 3e134e8..3ca5155 100644
--- a/wscript
+++ b/wscript
@@ -413,6 +413,7 @@ def build(bld):
 		build_plugin('htmlchars')
 		build_plugin('saveactions')
 		build_plugin('splitwindow', not is_win32)
+		build_plugin('xmlsnippets')
 
 	# Translations
 	if bld.env['INTLTOOL']:
