Revision: 1416
http://geany-plugins.svn.sourceforge.net/geany-plugins/?rev=1416&view=rev
Author: funto66
Date: 2010-05-31 10:28:38 +0000 (Mon, 31 May 2010)
Log Message:
-----------
CodeNav: Oops, a debug macro was defined and shouldn't have been...
Modified Paths:
--------------
trunk/geany-plugins/codenav/src/codenavigation.h
Modified: trunk/geany-plugins/codenav/src/codenavigation.h
===================================================================
--- trunk/geany-plugins/codenav/src/codenavigation.h 2010-05-30 18:13:47 UTC (rev 1415)
+++ trunk/geany-plugins/codenav/src/codenavigation.h 2010-05-31 10:28:38 UTC (rev 1416)
@@ -46,7 +46,8 @@
#include "geanyfunctions.h" /* this wraps geany_functions function pointers */
/* Debug flag */
-#define CODE_NAVIGATION_DEBUG
+/*#define CODE_NAVIGATION_DEBUG
+*/
#define CODE_NAVIGATION_VERSION "0.1"
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 1412
http://geany-plugins.svn.sourceforge.net/geany-plugins/?rev=1412&view=rev
Author: colombanw
Date: 2010-05-29 09:05:27 +0000 (Sat, 29 May 2010)
Log Message:
-----------
GeanyGenDoc: Fix build for r1411 (oops)
Modified Paths:
--------------
trunk/geany-plugins/build/geanygendoc.m4
Modified: trunk/geany-plugins/build/geanygendoc.m4
===================================================================
--- trunk/geany-plugins/build/geanygendoc.m4 2010-05-27 15:16:40 UTC (rev 1411)
+++ trunk/geany-plugins/build/geanygendoc.m4 2010-05-29 09:05:27 UTC (rev 1412)
@@ -56,6 +56,5 @@
geanygendoc/data/Makefile
geanygendoc/data/filetypes/Makefile
geanygendoc/docs/Makefile
- geanygendoc/docs/help/Makefile
])
])
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 1411
http://geany-plugins.svn.sourceforge.net/geany-plugins/?rev=1411&view=rev
Author: colombanw
Date: 2010-05-27 15:16:40 +0000 (Thu, 27 May 2010)
Log Message:
-----------
GeanyGenDoc: Move manual to docs/ and install HTML in DOCDIR/html
Move the manual sources from docs/help to docs since the sub-directory
is useless and led to some confusion.
Install the HTML version of the manual in DOCDIR/html rather than
DOCDIR.
Modified Paths:
--------------
trunk/geany-plugins/geanygendoc/docs/Makefile.am
trunk/geany-plugins/geanygendoc/src/ggd-plugin.c
trunk/geany-plugins/wscript
Added Paths:
-----------
trunk/geany-plugins/geanygendoc/docs/html4css1.css
trunk/geany-plugins/geanygendoc/docs/manual.css
trunk/geany-plugins/geanygendoc/docs/manual.html
trunk/geany-plugins/geanygendoc/docs/manual.rst
Removed Paths:
-------------
trunk/geany-plugins/geanygendoc/docs/help/Makefile.am
trunk/geany-plugins/geanygendoc/docs/help/html4css1.css
trunk/geany-plugins/geanygendoc/docs/help/manual.css
trunk/geany-plugins/geanygendoc/docs/help/manual.html
trunk/geany-plugins/geanygendoc/docs/help/manual.rst
Modified: trunk/geany-plugins/geanygendoc/docs/Makefile.am
===================================================================
--- trunk/geany-plugins/geanygendoc/docs/Makefile.am 2010-05-26 17:43:39 UTC (rev 1410)
+++ trunk/geany-plugins/geanygendoc/docs/Makefile.am 2010-05-27 15:16:40 UTC (rev 1411)
@@ -1 +1,20 @@
-SUBDIRS = help
+if ENABLE_GEANYGENDOC
+include $(top_srcdir)/build/vars.docs.mk
+plugin = geanygendoc
+pluginhtmldocdir = $(plugindocdir)/html
+endif ENABLE_GEANYGENDOC
+
+EXTRA_DIST = manual.rst \
+ manual.css \
+ html4css1.css \
+ manual.html
+
+if ENABLE_GEANYGENDOC
+plugindoc_DATA = manual.rst
+pluginhtmldoc_DATA = manual.html
+
+if BUILD_RST
+manual.html: manual.rst manual.css
+ $(AM_V_GEN) $(RST2HTML) -d --strict --stylesheet-path manual.css $< $@
+endif BUILD_RST
+endif ENABLE_GEANYGENDOC
Deleted: trunk/geany-plugins/geanygendoc/docs/help/Makefile.am
===================================================================
--- trunk/geany-plugins/geanygendoc/docs/help/Makefile.am 2010-05-26 17:43:39 UTC (rev 1410)
+++ trunk/geany-plugins/geanygendoc/docs/help/Makefile.am 2010-05-27 15:16:40 UTC (rev 1411)
@@ -1,19 +0,0 @@
-if ENABLE_GEANYGENDOC
-include $(top_srcdir)/build/vars.docs.mk
-plugin = geanygendoc
-endif ENABLE_GEANYGENDOC
-
-EXTRA_DIST = manual.rst \
- manual.css \
- html4css1.css \
- manual.html
-
-if ENABLE_GEANYGENDOC
-plugindoc_DATA = manual.rst \
- manual.html
-
-if BUILD_RST
-manual.html: manual.rst manual.css
- $(AM_V_GEN) $(RST2HTML) -d --strict --stylesheet-path manual.css $< $@
-endif BUILD_RST
-endif ENABLE_GEANYGENDOC
Deleted: trunk/geany-plugins/geanygendoc/docs/help/html4css1.css
===================================================================
--- trunk/geany-plugins/geanygendoc/docs/help/html4css1.css 2010-05-26 17:43:39 UTC (rev 1410)
+++ trunk/geany-plugins/geanygendoc/docs/help/html4css1.css 2010-05-27 15:16:40 UTC (rev 1411)
@@ -1,293 +0,0 @@
-/*
-:Author: David Goodger (goodger(a)python.org)
-:Id: $Id: html4css1.css 5951 2009-05-18 18:03:10Z milde $
-:Copyright: This stylesheet has been placed in the public domain.
-
-Default cascading style sheet for the HTML output of Docutils.
-
-See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
-customize this style sheet.
-*/
-
-/* used to remove borders from tables and images */
-.borderless, table.borderless td, table.borderless th {
- border: 0 }
-
-table.borderless td, table.borderless th {
- /* Override padding for "table.docutils td" with "! important".
- The right padding separates the table cells. */
- padding: 0 0.5em 0 0 ! important }
-
-.first {
- /* Override more specific margin styles with "! important". */
- margin-top: 0 ! important }
-
-.last, .with-subtitle {
- margin-bottom: 0 ! important }
-
-.hidden {
- display: none }
-
-a.toc-backref {
- text-decoration: none ;
- color: black }
-
-blockquote.epigraph {
- margin: 2em 5em ; }
-
-dl.docutils dd {
- margin-bottom: 0.5em }
-
-/* Uncomment (and remove this text!) to get bold-faced definition list terms
-dl.docutils dt {
- font-weight: bold }
-*/
-
-div.abstract {
- margin: 2em 5em }
-
-div.abstract p.topic-title {
- font-weight: bold ;
- text-align: center }
-
-div.admonition, div.attention, div.caution, div.danger, div.error,
-div.hint, div.important, div.note, div.tip, div.warning {
- margin: 2em ;
- border: medium outset ;
- padding: 1em }
-
-div.admonition p.admonition-title, div.hint p.admonition-title,
-div.important p.admonition-title, div.note p.admonition-title,
-div.tip p.admonition-title {
- font-weight: bold ;
- font-family: sans-serif }
-
-div.attention p.admonition-title, div.caution p.admonition-title,
-div.danger p.admonition-title, div.error p.admonition-title,
-div.warning p.admonition-title {
- color: red ;
- font-weight: bold ;
- font-family: sans-serif }
-
-/* Uncomment (and remove this text!) to get reduced vertical space in
- compound paragraphs.
-div.compound .compound-first, div.compound .compound-middle {
- margin-bottom: 0.5em }
-
-div.compound .compound-last, div.compound .compound-middle {
- margin-top: 0.5em }
-*/
-
-div.dedication {
- margin: 2em 5em ;
- text-align: center ;
- font-style: italic }
-
-div.dedication p.topic-title {
- font-weight: bold ;
- font-style: normal }
-
-div.figure {
- margin-left: 2em ;
- margin-right: 2em }
-
-div.footer, div.header {
- clear: both;
- font-size: smaller }
-
-div.line-block {
- display: block ;
- margin-top: 1em ;
- margin-bottom: 1em }
-
-div.line-block div.line-block {
- margin-top: 0 ;
- margin-bottom: 0 ;
- margin-left: 1.5em }
-
-div.sidebar {
- margin: 0 0 0.5em 1em ;
- border: medium outset ;
- padding: 1em ;
- background-color: #ffffee ;
- width: 40% ;
- float: right ;
- clear: right }
-
-div.sidebar p.rubric {
- font-family: sans-serif ;
- font-size: medium }
-
-div.system-messages {
- margin: 5em }
-
-div.system-messages h1 {
- color: red }
-
-div.system-message {
- border: medium outset ;
- padding: 1em }
-
-div.system-message p.system-message-title {
- color: red ;
- font-weight: bold }
-
-div.topic {
- margin: 2em }
-
-h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
-h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
- margin-top: 0.4em }
-
-h1.title {
- text-align: center }
-
-h2.subtitle {
- text-align: center }
-
-hr.docutils {
- width: 75% }
-
-img.align-left, .figure.align-left{
- clear: left ;
- float: left ;
- margin-right: 1em }
-
-img.align-right, .figure.align-right {
- clear: right ;
- float: right ;
- margin-left: 1em }
-
-.align-left {
- text-align: left }
-
-.align-center {
- clear: both ;
- text-align: center }
-
-.align-right {
- text-align: right }
-
-/* reset inner alignment in figures */
-div.align-right {
- text-align: left }
-
-/* div.align-center * { */
-/* text-align: left } */
-
-ol.simple, ul.simple {
- margin-bottom: 1em }
-
-ol.arabic {
- list-style: decimal }
-
-ol.loweralpha {
- list-style: lower-alpha }
-
-ol.upperalpha {
- list-style: upper-alpha }
-
-ol.lowerroman {
- list-style: lower-roman }
-
-ol.upperroman {
- list-style: upper-roman }
-
-p.attribution {
- text-align: right ;
- margin-left: 50% }
-
-p.caption {
- font-style: italic }
-
-p.credits {
- font-style: italic ;
- font-size: smaller }
-
-p.label {
- white-space: nowrap }
-
-p.rubric {
- font-weight: bold ;
- font-size: larger ;
- color: maroon ;
- text-align: center }
-
-p.sidebar-title {
- font-family: sans-serif ;
- font-weight: bold ;
- font-size: larger }
-
-p.sidebar-subtitle {
- font-family: sans-serif ;
- font-weight: bold }
-
-p.topic-title {
- font-weight: bold }
-
-pre.address {
- margin-bottom: 0 ;
- margin-top: 0 ;
- font: inherit }
-
-pre.literal-block, pre.doctest-block {
- margin-left: 2em ;
- margin-right: 2em }
-
-span.classifier {
- font-family: sans-serif ;
- font-style: oblique }
-
-span.classifier-delimiter {
- font-family: sans-serif ;
- font-weight: bold }
-
-span.interpreted {
- font-family: sans-serif }
-
-span.option {
- white-space: nowrap }
-
-span.pre {
- white-space: pre }
-
-span.problematic {
- color: red }
-
-span.section-subtitle {
- /* font-size relative to parent (h1..h6 element) */
- font-size: 80% }
-
-table.citation {
- border-left: solid 1px gray;
- margin-left: 1px }
-
-table.docinfo {
- margin: 2em 4em }
-
-table.docutils {
- margin-top: 0.5em ;
- margin-bottom: 0.5em }
-
-table.footnote {
- border-left: solid 1px black;
- margin-left: 1px }
-
-table.docutils td, table.docutils th,
-table.docinfo td, table.docinfo th {
- padding-left: 0.5em ;
- padding-right: 0.5em ;
- vertical-align: top }
-
-table.docutils th.field-name, table.docinfo th.docinfo-name {
- font-weight: bold ;
- text-align: left ;
- white-space: nowrap ;
- padding-left: 0 }
-
-h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
-h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
- font-size: 100% }
-
-ul.auto-toc {
- list-style-type: none }
Deleted: trunk/geany-plugins/geanygendoc/docs/help/manual.css
===================================================================
--- trunk/geany-plugins/geanygendoc/docs/help/manual.css 2010-05-26 17:43:39 UTC (rev 1410)
+++ trunk/geany-plugins/geanygendoc/docs/help/manual.css 2010-05-27 15:16:40 UTC (rev 1411)
@@ -1,68 +0,0 @@
-/*
-:Author: Colomban Wendling
-:Contact: ban(a)herbesfolles.org
-:Copyright: This stylesheet has been placed in the public domain.
-
-Stylesheet for use with Docutils.
-*/
-
-@import url(html4css1.css);
-
-html {
- background-color: #eeeeec;
- color: #2e3436;
- font-family: bitstream vera sans, sans-serif;
- margin: 0 1em;
-}
-
-
-h1, h2, h3, h4, h5, h6, p.topic-title {
- font-family: georgia, times new roman, times, serif;
-}
-
-h2.subtitle {
- font-style: italic;
- font-weight: normal;
-}
-
-p, dd {
- text-align: justify;
-}
-
-.literal-block,
-.literal {
- background: #fff;
-}
-.literal-block {
- border: 1px solid #babdb6;
- padding: 1px 2px;
-}
-h1 .literal, h2 .literal, h3 .literal, h4 .literal, h5 .literal, h6 .literal
-p.topic-title .literal {
- background: inherit;
- text-align: left;
-}
-
-
-.footnote-reference {
- vertical-align: super;
- font-size: 75%;
-}
-
-
-a { text-decoration: none; }
-a:hover { text-decoration: underline }
-a:link { color: #204a87; }
-a:visited { color: #5c3566; }
-
-h1 a, h1 a:hover, h1 a:link, h1 a:visited,
-h2 a, h2 a:hover, h2 a:link, h2 a:visited,
-h3 a, h3 a:hover, h3 a:link, h3 a:visited,
-h4 a, h4 a:hover, h4 a:link, h4 a:visited,
-h5 a, h5 a:hover, h5 a:link, h5 a:visited,
-h6 a, h6 a:hover, h6 a:link, h6 a:visited,
-p.topic-title a, p.topic-title a:hover, p.topic-title a:link, p.topic-title a:visited
-{
- text-decoration: none;
- color: inherit;
-}
Deleted: trunk/geany-plugins/geanygendoc/docs/help/manual.html
===================================================================
--- trunk/geany-plugins/geanygendoc/docs/help/manual.html 2010-05-26 17:43:39 UTC (rev 1410)
+++ trunk/geany-plugins/geanygendoc/docs/help/manual.html 2010-05-27 15:16:40 UTC (rev 1411)
@@ -1,602 +0,0 @@
-<?xml version="1.0" encoding="utf-8" ?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<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.6: http://docutils.sourceforge.net/" />
-<title>GeanyGenDoc User Manual</title>
-<style type="text/css">
-
-/*
-:Author: Colomban Wendling
-:Contact: ban(a)herbesfolles.org
-:Copyright: This stylesheet has been placed in the public domain.
-
-Stylesheet for use with Docutils.
-*/
-
-@import url(html4css1.css);
-
-html {
- background-color: #eeeeec;
- color: #2e3436;
- font-family: bitstream vera sans, sans-serif;
- margin: 0 1em;
-}
-
-
-h1, h2, h3, h4, h5, h6, p.topic-title {
- font-family: georgia, times new roman, times, serif;
-}
-
-h2.subtitle {
- font-style: italic;
- font-weight: normal;
-}
-
-p, dd {
- text-align: justify;
-}
-
-.literal-block,
-.literal {
- background: #fff;
-}
-.literal-block {
- border: 1px solid #babdb6;
- padding: 1px 2px;
-}
-h1 .literal, h2 .literal, h3 .literal, h4 .literal, h5 .literal, h6 .literal
-p.topic-title .literal {
- background: inherit;
- text-align: left;
-}
-
-
-.footnote-reference {
- vertical-align: super;
- font-size: 75%;
-}
-
-
-a { text-decoration: none; }
-a:hover { text-decoration: underline }
-a:link { color: #204a87; }
-a:visited { color: #5c3566; }
-
-h1 a, h1 a:hover, h1 a:link, h1 a:visited,
-h2 a, h2 a:hover, h2 a:link, h2 a:visited,
-h3 a, h3 a:hover, h3 a:link, h3 a:visited,
-h4 a, h4 a:hover, h4 a:link, h4 a:visited,
-h5 a, h5 a:hover, h5 a:link, h5 a:visited,
-h6 a, h6 a:hover, h6 a:link, h6 a:visited,
-p.topic-title a, p.topic-title a:hover, p.topic-title a:link, p.topic-title a:visited
-{
- text-decoration: none;
- color: inherit;
-}
-
-</style>
-</head>
-<body>
-<div class="document" id="geanygendoc-user-manual">
-<h1 class="title">GeanyGenDoc User Manual</h1>
-<h2 class="subtitle" id="a-handy-hand-guide-for-the-lazy-documenter-in-you">A handy hand guide for the lazy documenter in you</h2>
-
-<div class="section" id="introduction">
-<h1><a class="toc-backref" href="#id4">Introduction</a></h1>
-<p>First of all, welcome to this manual. Then, what is GeanyGenDoc? It is a
-plug-in for Geany as you might have noticed; but what is it meant to do?
-Basically, it generates and inserts text chunks, particularly from document's
-symbols. Its goal is to ease writing documentation for the good.</p>
-<div class="contents topic" id="contents">
-<p class="topic-title first">Contents</p>
-<ul class="simple">
-<li><a class="reference internal" href="#introduction" id="id4">Introduction</a></li>
-<li><a class="reference internal" href="#design" id="id5">Design</a></li>
-<li><a class="reference internal" href="#syntax" id="id6">Syntax</a><ul>
-<li><a class="reference internal" href="#key-value-pairs" id="id7">Key-Value pairs</a></li>
-<li><a class="reference internal" href="#naming" id="id8">Naming</a></li>
-<li><a class="reference internal" href="#comments" id="id9">Comments</a></li>
-<li><a class="reference internal" href="#value-types" id="id10">Value types</a></li>
-</ul>
-</li>
-<li><a class="reference internal" href="#file-types" id="id11">File types</a><ul>
-<li><a class="reference internal" href="#the-settings-group" id="id12">The <tt class="docutils literal">settings</tt> group</a></li>
-<li><a class="reference internal" href="#the-doctypes-group" id="id13">The <tt class="docutils literal">doctypes</tt> group</a></li>
-</ul>
-</li>
-<li><a class="reference internal" href="#documentation-types" id="id14">Documentation types</a><ul>
-<li><a class="reference internal" href="#short-example" id="id15">Short example</a></li>
-</ul>
-</li>
-<li><a class="reference internal" href="#rules-the-cool-thing" id="id16">Rules: the cool thing</a><ul>
-<li><a class="reference internal" href="#type-hierarchy" id="id17">Type hierarchy</a><ul>
-<li><a class="reference internal" href="#known-types" id="id18">Known types</a></li>
-</ul>
-</li>
-<li><a class="reference internal" href="#rule-settings" id="id19">Rule settings</a></li>
-</ul>
-</li>
-<li><a class="reference internal" href="#user-interface-in-geany" id="id20">User interface in Geany</a><ul>
-<li><a class="reference internal" href="#menus" id="id21">Menus</a><ul>
-<li><a class="reference internal" href="#editor-s-pop-up-menu" id="id22">Editor's pop-up menu</a></li>
-<li><a class="reference internal" href="#tools-menu" id="id23">Tools menu</a></li>
-</ul>
-</li>
-<li><a class="reference internal" href="#preferences-dialog" id="id24">Preferences dialog</a></li>
-</ul>
-</li>
-<li><a class="reference internal" href="#miscellaneous" id="id25">Miscellaneous</a><ul>
-<li><a class="reference internal" href="#configuration-directories" id="id26">Configuration directories</a></li>
-</ul>
-</li>
-<li><a class="reference internal" href="#appendix" id="id27">Appendix</a><ul>
-<li><a class="reference internal" href="#configuration-syntax-summary" id="id28">Configuration syntax summary</a></li>
-</ul>
-</li>
-</ul>
-</div>
-</div>
-<div class="section" id="design">
-<h1><a class="toc-backref" href="#id5">Design</a></h1>
-<p>GeanyGenDoc has an extensible design based on three points: file type,
-documentation type and rules.</p>
-<dl class="docutils">
-<dt><a class="reference internal" href="#file-types">File type</a></dt>
-<dd>The file type determines which configuration applies to which document. For
-example, the "c" file type corresponds to C source, and so on.</dd>
-<dt><a class="reference internal" href="#documentation-types">Documentation type</a></dt>
-<dd>A documentation type is an arbitrary name for a set of rules. The goal of
-documentation types is to allow different set of rules to be defined for each
-file type.
-One might want to have separate rules to generate for example <a class="reference external" href="http://www.doxygen.org">Doxygen</a>
-and <a class="reference external" href="http://www.gtk.org/gtk-doc/">Gtk-Doc</a> documentation from C sources. She should then create two
-documentation types in the C <a class="reference internal" href="#file-types">file type configuration file</a>, such as
-"doxygen" and "gtkdoc".</dd>
-<dt><a class="reference internal" href="#rules-the-cool-thing">Rule</a></dt>
-<dd>A rule is a group of settings controlling how a documentation comment is
-generated. For example, it can define a template, describe how to handle
-particular imbrications and so on.</dd>
-</dl>
-</div>
-<div class="section" id="syntax">
-<h1><a class="toc-backref" href="#id6">Syntax</a></h1>
-<div class="section" id="key-value-pairs">
-<h2><a class="toc-backref" href="#id7">Key-Value pairs</a></h2>
-<p>The syntax used by the configuration files is an extended key-value tree
-definition based on common concepts (trees, string literals, semicolon-ended
-values, etc.).</p>
-<p>The key-value syntax is as follows:</p>
-<pre class="literal-block">
-key = value
-</pre>
-<p>where value is either a semicolon-ended single value:</p>
-<pre class="literal-block">
-value;
-</pre>
-<p>or a brace-surrounded list of key-value pairs that use the same syntax again:</p>
-<pre class="literal-block">
-{
- key1 = value1
- key2 = value2
-}
-</pre>
-<p>Here a little example of the <em>syntax</em> (not any actual configuration example):</p>
-<pre class="literal-block">
-key1 = value1;
-key2 = {
- sub-key1 = sub-value1;
- sub-key2 = {
- sub-sub-key1 = sub-sub-value1;
- }
-}
-</pre>
-</div>
-<div class="section" id="naming">
-<h2><a class="toc-backref" href="#id8">Naming</a></h2>
-<p>Key-value pairs are often referred as <em>group</em> when they are meant to have
-multiple values and as <em>setting</em> when they have a single value.</p>
-</div>
-<div class="section" id="comments">
-<h2><a class="toc-backref" href="#id9">Comments</a></h2>
-<p>Is considered as comment (and therefore ignored) everything between a number
-sign (<tt class="docutils literal">#</tt>) and the following end of line, unless the <tt class="docutils literal">#</tt> occurs as part of
-another syntactic element (such as a string literal).</p>
-<p>A short example:</p>
-<pre class="literal-block">
-# This is a comment
-key = value; # This is also a comment
-string = "A string. # This isn't a comment but a string";
-</pre>
-</div>
-<div class="section" id="value-types">
-<h2><a class="toc-backref" href="#id10">Value types</a></h2>
-<dl class="docutils">
-<dt>string</dt>
-<dd><p class="first">A string literal. String literals are surrounded by either single (<tt class="docutils literal">'</tt>) or
-double (<tt class="docutils literal">"</tt>) quotes.</p>
-<p>Some special characters can be inserted in a string with an escape sequence:</p>
-<dl class="docutils">
-<dt><tt class="docutils literal">\t</tt></dt>
-<dd>A tabulation.</dd>
-<dt><tt class="docutils literal">\n</tt></dt>
-<dd>A new line.</dd>
-<dt><tt class="docutils literal">\r</tt></dt>
-<dd>A carriage return.</dd>
-<dt><tt class="docutils literal">\\</tt></dt>
-<dd>A backslash.</dd>
-<dt><tt class="docutils literal">\'</tt></dt>
-<dd>A single quote (escaping only needed in single-quotes surrounded strings).</dd>
-<dt><tt class="docutils literal">\"</tt></dt>
-<dd>A double quote (escaping only needed in double-quotes surrounded strings).</dd>
-</dl>
-<p>Note that backslashes are used as the escaping character, which means that it
-must be escaped to be treated as a simple backslash character.</p>
-<p>A simple example:</p>
-<pre class="last literal-block">
-"This is a string with \"special\" characters.\nThis is another line!"
-</pre>
-</dd>
-<dt>boolean</dt>
-<dd>A boolean. It can take one of the two symbolic values <tt class="docutils literal">True</tt> and <tt class="docutils literal">False</tt>.</dd>
-<dt>enumeration</dt>
-<dd>An enumeration. It consists of a named constant, generally in capital letters.
-The possible values depend on the setting that use this type.</dd>
-<dt>flags</dt>
-<dd><p class="first">A logical OR of named constants. This is like enumerations but can combine
-different values.</p>
-<p class="last">The syntax is common for such types and uses the pipe (<tt class="docutils literal">|</tt>) as
-combination character. Considering the <tt class="docutils literal">A</tt>, <tt class="docutils literal">B</tt> and <tt class="docutils literal">C</tt> constants, a
-valid value could be <tt class="docutils literal">A | C</tt>, which represents both <tt class="docutils literal">A</tt> and <tt class="docutils literal">C</tt> but
-not <tt class="docutils literal">B</tt>.</p>
-</dd>
-<dt>list</dt>
-<dd>A list of values (often referred as array).</dd>
-</dl>
-</div>
-</div>
-<div class="section" id="file-types">
-<h1><a class="toc-backref" href="#id11">File types</a></h1>
-<p>The file type determines which configuration applies to which document.
-<em>File type identifiers</em> are the lowercased name of the Geany's file type, for
-example "c" or "python".</p>
-<p>Configuration for a particular file type goes in a file named
-<tt class="docutils literal"><span class="pre">file-type-identifier.conf</span></tt> in the <tt class="docutils literal">filetypes</tt> sub-directory of a
-<a class="reference internal" href="#configuration-directories">configuration directory</a>.</p>
-<p>A file type configuration can contain two type of things: file-type-wide
-settings and any number of <a class="reference internal" href="#documentation-types">documentation types</a>.</p>
-<div class="section" id="the-settings-group">
-<h2><a class="toc-backref" href="#id12">The <tt class="docutils literal">settings</tt> group</a></h2>
-<p>This group contains the file-type-wide settings.</p>
-<dl class="docutils">
-<dt><tt class="docutils literal">match_function_arguments</tt> (string)</dt>
-<dd>A regular expression used to extract arguments from a function-style argument
-list (functions, methods, macros, etc.). This regular expression should match
-one argument at a time and capture only the argument's name.
-This setting is a little odd but currently needed to extract argument list
-from function definitions.</dd>
-<dt><tt class="docutils literal">global_environment</tt> (string)</dt>
-<dd>A description of a <a class="reference external" href="http://ctpl.tuxfamily.org/">CTPL</a> environment to add when parsing <a class="reference internal" href="#rules-the-cool-thing">rule</a>'s templates.</dd>
-</dl>
-</div>
-<div class="section" id="the-doctypes-group">
-<h2><a class="toc-backref" href="#id13">The <tt class="docutils literal">doctypes</tt> group</a></h2>
-<p>This group contains a list of <a class="reference internal" href="#documentation-types">documentation types</a>.</p>
-</div>
-</div>
-<div class="section" id="documentation-types">
-<h1><a class="toc-backref" href="#id14">Documentation types</a></h1>
-<p>A documentation type is a named set of <a class="reference internal" href="#rules-the-cool-thing">rules</a> for a <a class="reference internal" href="#file-types">file type</a>, describing how
-to generate a particular type of documentation (i.e. <a class="reference external" href="http://www.doxygen.org">Doxygen</a>, <a class="reference external" href="http://www.gtk.org/gtk-doc/">Gtk-Doc</a>,
-<a class="reference external" href="http://www.valadoc.org/">Valadoc</a> or whatever).</p>
-<p>A documentation type is identified by its name and must therefore be unique
-in a file type. But of course, different file types can define the same
-documentation type. It is even recommended for a better consistency to use the
-same identifier in different file types when they generate the same type of
-documentation (even though it is completely up to you).</p>
-<div class="section" id="short-example">
-<h2><a class="toc-backref" href="#id15">Short example</a></h2>
-<pre class="literal-block">
-doxygen = {
- struct.member = {
- template = " /**< {cursor} */";
- position = AFTER;
- }
- struct.template = "/**\n * @brief: {cursor}\n * \n * \n */\n";
-}
-</pre>
-</div>
-</div>
-<div class="section" id="rules-the-cool-thing">
-<h1><a class="toc-backref" href="#id16">Rules: the cool thing</a></h1>
-<p>Rules are the actual definition of how documentation is generated. A rule
-applies to a symbol type and hierarchy, allowing fine control over which and
-how symbols are documented.</p>
-<p>A rule is represented as a group of <a class="reference internal" href="#rule-settings">settings</a> in a <a class="reference internal" href="#documentation-types">documentation type</a>.
-The name of this group is the <a class="reference internal" href="#type-hierarchy">type hierarchy</a> to which the settings applies.</p>
-<div class="section" id="type-hierarchy">
-<h2><a class="toc-backref" href="#id17">Type hierarchy</a></h2>
-<p>A type hierarchy is a hierarchy of the types that a symbol must have to match
-this rule.</p>
-<p>In the symbol side, the type hierarchy is the types of the symbol's parents,
-terminated by the symbol's own type. For example, a method in a class would
-have a hierarchy like <tt class="docutils literal">class <span class="pre">-></span> method</tt>; and if the class is itself in a
-namespace, the hierarchy would the look like <tt class="docutils literal">namespace <span class="pre">-></span> class <span class="pre">-></span> method</tt>,
-and so on.</p>
-<p>For a rule to apply, its type hierarchy must match <em>the end</em> of the symbol
-type hierarchy. For example a rule with the type hierarchy <tt class="docutils literal">class</tt> will match
-a symbol with the type hierarchy <tt class="docutils literal">namespace <span class="pre">-></span> class</tt> but not one with
-<tt class="docutils literal">class <span class="pre">-></span> method</tt>.</p>
-<p>A type hierarchy uses dots (<tt class="docutils literal">.</tt>) to separate types and build the hierarchy.
-For example, the type hierarchy representing <tt class="docutils literal">namespace <span class="pre">-></span> class</tt> would be
-written <tt class="docutils literal">namespace.class</tt>.</p>
-<div class="section" id="known-types">
-<h3><a class="toc-backref" href="#id18">Known types</a></h3>
-<dl class="docutils">
-<dt><tt class="docutils literal">class</tt></dt>
-<dd>A class.</dd>
-<dt><tt class="docutils literal">enum</tt></dt>
-<dd>An enumeration.</dd>
-<dt><tt class="docutils literal">enumval</tt></dt>
-<dd>An enumeration value.</dd>
-<dt><tt class="docutils literal">field</tt></dt>
-<dd>A field (of a class for example).</dd>
-<dt><tt class="docutils literal">function</tt></dt>
-<dd>A function.</dd>
-<dt><tt class="docutils literal">interface</tt></dt>
-<dd>An interface.</dd>
-<dt><tt class="docutils literal">member</tt></dt>
-<dd>A member (of a structure for example).</dd>
-<dt><tt class="docutils literal">method</tt></dt>
-<dd>A method.</dd>
-<dt><tt class="docutils literal">namespace</tt></dt>
-<dd>A namespace.</dd>
-<dt><tt class="docutils literal">package</tt></dt>
-<dd>A package.</dd>
-<dt><tt class="docutils literal">prototype</tt></dt>
-<dd>A prototype.</dd>
-<dt><tt class="docutils literal">struct</tt></dt>
-<dd>A structure.</dd>
-<dt><tt class="docutils literal">typedef</tt></dt>
-<dd>A type alias definition (<em>typedef</em> in C).</dd>
-<dt><tt class="docutils literal">union</tt></dt>
-<dd>An union.</dd>
-<dt><tt class="docutils literal">variable</tt></dt>
-<dd>A variable.</dd>
-<dt><tt class="docutils literal">extern</tt></dt>
-<dd><cite>???</cite></dd>
-<dt><tt class="docutils literal">define</tt></dt>
-<dd>A definition (like the <em>define</em> C preprocessor macro).</dd>
-<dt><tt class="docutils literal">macro</tt></dt>
-<dd>A macro.</dd>
-<dt><tt class="docutils literal">file</tt></dt>
-<dd>A file (will never match).</dd>
-</dl>
-</div>
-</div>
-<div class="section" id="rule-settings">
-<h2><a class="toc-backref" href="#id19">Rule settings</a></h2>
-<dl class="docutils">
-<dt><tt class="docutils literal">template</tt> (string)</dt>
-<dd><p class="first">A <a class="reference external" href="http://ctpl.tuxfamily.org/">CTPL</a> template that can include references to the following predefined
-variables in addition to the file-type-wide and the global environment:</p>
-<dl class="docutils">
-<dt><tt class="docutils literal">argument_list</tt> (string list)</dt>
-<dd>A list of the arguments of the currently documented symbol.</dd>
-<dt><tt class="docutils literal">returns</tt> (boolean)</dt>
-<dd>Indicates whether the currently documented symbol returns a value
-(makes sense only for symbols that may return a value).</dd>
-<dt><tt class="docutils literal">children</tt> (string list)</dt>
-<dd>A list of the current symbol's first-level children. This is only set if
-the rule's setting <tt class="docutils literal">children</tt> is set to <tt class="docutils literal">MERGE</tt>.</dd>
-</dl>
-<p><strong>[...]</strong></p>
-<dl class="last docutils">
-<dt><tt class="docutils literal">cursor</tt> (special, described below)</dt>
-<dd>This can be used to mark in the template the position where the editor's
-cursor should be moved to after comment insertion.
-This mark will be removed from the generated documentation.
-Note that even if this mark may occur as many times as you want in a
-template, only the first will be actually honored, the latter being
-only removed.</dd>
-</dl>
-</dd>
-<dt><tt class="docutils literal">position</tt> (enumeration)</dt>
-<dd><p class="first">The position where the documentation should be inserted. Possible values are:</p>
-<dl class="last docutils">
-<dt><tt class="docutils literal">BEFORE</tt> <a class="citation-reference" href="#default" id="id1">[default]</a></dt>
-<dd>Inserts the documentation just before the symbol.</dd>
-<dt><tt class="docutils literal">AFTER</tt></dt>
-<dd>Inserts the documentation just after the symbol (currently quite limited, it
-inserts the documentation at the end of the symbol's first line).</dd>
-<dt><tt class="docutils literal">CURSOR</tt></dt>
-<dd>Inserts the documentation at the current cursor position.</dd>
-</dl>
-</dd>
-<dt><tt class="docutils literal">policy</tt> (enumeration)</dt>
-<dd><p class="first">How the symbol is documented. Possible values are:</p>
-<dl class="last docutils">
-<dt><tt class="docutils literal">KEEP</tt> <a class="citation-reference" href="#default" id="id2">[default]</a></dt>
-<dd>The symbol documents itself.</dd>
-<dt><tt class="docutils literal">FORWARD</tt></dt>
-<dd>Forward the documentation request to the parent. This is useful for symbols
-that are documented by their parent, such as <a class="reference external" href="http://www.gtk.org/gtk-doc/">Gtk-Doc</a>'s enumerations.</dd>
-</dl>
-</dd>
-<dt><tt class="docutils literal">children</tt> (enumeration)</dt>
-<dd><p class="first">How the symbol's children can be used in the template. Possible values are:</p>
-<dl class="last docutils">
-<dt><tt class="docutils literal">SPLIT</tt> <a class="citation-reference" href="#default" id="id3">[default]</a></dt>
-<dd>The symbol's children are provided as per-type lists.</dd>
-<dt><tt class="docutils literal">MERGE</tt></dt>
-<dd>The symbol's children are provided as a single list named <tt class="docutils literal">children</tt>.</dd>
-</dl>
-</dd>
-<dt><tt class="docutils literal">matches</tt> (flags)</dt>
-<dd>List of the children types that should be provided. Only useful if the
-<tt class="docutils literal">children</tt> setting is set to <tt class="docutils literal">MERGE</tt>.
-Defaults to all.
-<strong>FIXME: check the exactitude of this description</strong></dd>
-<dt><tt class="docutils literal">auto_doc_children</tt> (boolean)</dt>
-<dd>Whether to also document symbol's children (according to their own rules).</dd>
-</dl>
-</div>
-</div>
-<div class="section" id="user-interface-in-geany">
-<h1><a class="toc-backref" href="#id20">User interface in Geany</a></h1>
-<div class="section" id="menus">
-<h2><a class="toc-backref" href="#id21">Menus</a></h2>
-<p>GeanyGenDoc adds an item named <cite>Insert Documentation Comment</cite> in the editor's
-pop-up under the <cite>Insert Comments</cite> sub-menu; and a menu named
-<cite>Documentation Generator</cite> into the <cite>Tools</cite> menu.</p>
-<div class="section" id="editor-s-pop-up-menu">
-<h3><a class="toc-backref" href="#id22">Editor's pop-up menu</a></h3>
-<p>The item <cite>Editor's pop-up → Insert Comments → Insert Documentation Comment</cite>
-generates documentation for the current symbol. It has a keyboard shortcut
-that can be configured through Geany's keybinding configuration system, under
-<cite>GeanyGenDoc → Insert Documentation Comment</cite>.</p>
-</div>
-<div class="section" id="tools-menu">
-<h3><a class="toc-backref" href="#id23">Tools menu</a></h3>
-<p>The <cite>Documentation Generator</cite> menu under <cite>Tools</cite> contains the following items:</p>
-<dl class="docutils">
-<dt><cite>Document Current Symbol</cite></dt>
-<dd>This generates documentation for the current symbol. It is equivalent to the
-item <cite>Insert Documentation Comment</cite> that can be found in the editor's pop-up
-menu.</dd>
-<dt><cite>Document All Symbols</cite></dt>
-<dd>This generates documentation for all symbols in the document. This is
-equivalent to manually requesting documentation generation for each symbol in
-the document.</dd>
-<dt><cite>Reload Configuration Files</cite></dt>
-<dd>This force reloading of all the <a class="reference internal" href="#file-types">file type</a> configuration files. It is
-useful when a file type configuration file was modified, in order to the new
-configuration to be used without reloading the plugin.</dd>
-<dt><cite>Edit Current Language Configuration</cite></dt>
-<dd>This opens the configuration file that applies to the current document for
-editing. The opened configuration file has write permissions: if it was a
-system configuration file it is copied under your personal <a class="reference internal" href="#configuration-directories">configuration
-directory</a> transparently.</dd>
-<dt><cite>Open Manual</cite></dt>
-<dd>Opens this manual in a browser.</dd>
-</dl>
-</div>
-</div>
-<div class="section" id="preferences-dialog">
-<h2><a class="toc-backref" href="#id24">Preferences dialog</a></h2>
-<p>The preferences dialog, than can either be opened through <cite>Edit →
-Plugin Preferences</cite> or with the <cite>Preferences</cite> button in the plugin manager,
-allows to modify the following preferences:</p>
-<dl class="docutils">
-<dt><cite>General</cite></dt>
-<dd><dl class="first last docutils">
-<dt><cite>Save file before generating documentation</cite></dt>
-<dd>Choose whether the current document should be saved to disc before
-generating the documentation. This is a technical detail, but it is
-currently needed to have an up-to-date tag list. If you disable this option
-and ask for documentation generation on a modified document, the behavior
-may be surprising since the comment will be generated for the last saved
-state of the document and not the current one.</dd>
-<dt><cite>Indent inserted documentation</cite></dt>
-<dd>Chooses whether the inserted documentation should be indented to fit the
-indentation at the insertion position.</dd>
-</dl>
-</dd>
-<dt><cite>Documentation type</cite></dt>
-<dd>This list allows you to choose the documentation type to use with each file
-type. The special language <cite>All</cite> on top of the list is used to choose the
-default documentation type, used for all languages that haven't one set.</dd>
-<dt><cite>Global environment</cite></dt>
-<dd>Global environment overrides and additions. This is an environment that will
-be merged with the <a class="reference internal" href="#file-types">file type</a>-specific ones, possibly overriding some parts.
-It can be used to define some values for all the file types, such as whether
-to write the common <cite>Since</cite> tag, define the <a class="reference external" href="http://www.doxygen.org">Doxygen</a> prefix an so on.
-Its most use case is not to need to change a file type's environment to change
-the value of one of its elements.</dd>
-</dl>
-</div>
-</div>
-<div class="section" id="miscellaneous">
-<h1><a class="toc-backref" href="#id25">Miscellaneous</a></h1>
-<div class="section" id="configuration-directories">
-<h2><a class="toc-backref" href="#id26">Configuration directories</a></h2>
-<p>Configuration directories hold GeanyGenDoc's configuration. They are the
-following:</p>
-<ul class="simple">
-<li>The user-specific configuration directory, containing the user-defined
-settings is <tt class="docutils literal">$GEANY_USER_CONFIG/plugins/geanygendoc/</tt>.
-<tt class="docutils literal">$GEANY_USER_CONFIG</tt> is generally <tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt> on UNIX systems.</li>
-<li>The system-wide configuration directory containing the default and
-pre-installed configuration is <tt class="docutils literal">$GEANY_SYS_CONFIG/plugins/geanygendoc/</tt>.
-<tt class="docutils literal">$GEANY_SYS_CONFIG</tt> is generally <tt class="docutils literal">/usr/share/geany/</tt> or
-<tt class="docutils literal">/usr/local/share/geany</tt> on UNIX systems.</li>
-</ul>
-<p>When searching for configuration, GeanyGenDoc will first look in the
-user's configuration directory, and if it wasn't successful, in the system
-configuration directory. If both failed, it assumes that there is no
-configuration at all.</p>
-</div>
-</div>
-<div class="section" id="appendix">
-<h1><a class="toc-backref" href="#id27">Appendix</a></h1>
-<div class="section" id="configuration-syntax-summary">
-<h2><a class="toc-backref" href="#id28">Configuration syntax summary</a></h2>
-<pre class="literal-block">
-string ::= ( """ .* """ | "'" .* "'" )
-constant ::= [_A-Z][_A-Z0-9]+
-integer ::= [0-9]+
-boolean ::= ( "True" | "False" )
-setting_value ::= ( string | constant | integer )
-setting ::= "setting-name" "=" setting_value ";"
-setting_list ::= ( "{" setting* "}" | setting )
-setting_section ::= "settings" "=" setting_list
-
-position ::= ( "BEFORE" | "AFTER" | "CURSOR" )
-policy ::= ( "KEEP" | "FORWARD" )
-children ::= ( "SPLIT" | "MERGE" )
-type ::= ( "class" | "enum" | "enumval" | "field" |
- "function" | "interface" | "member" | "method" |
- "namespace" | "package" | "prototype" | "struct" |
- "typedef" | "union" | "variable" | "extern" |
- "define" | "macro" | "file" )
-matches ::= type ( "|" type )*
-doctype_subsetting ::= ( "template" "=" string |
- "position" "=" position |
- "policy" "=" policy |
- "children" "=" children |
- "matches" "=" matches |
- "auto_doc_children" "=" boolean ) ";"
-match ::= type ( "." type )*
-doctype_setting ::= ( match "=" "{" doctype_subsetting* "}" |
- match "." doctype_subsetting )
-doctype_setting_list ::= ( "{" doctype_setting* "}" | doctype_setting )
-doctype ::= "doctype-name" "=" doctype_setting_list
-doctype_list ::= ( "{" doctype* "}" | doctype )
-doctype_section ::= "doctypes" "=" doctype_list
-
-document ::= ( setting_section? doctype_section? |
- doctype_section? setting_section? )
-</pre>
-<!-- Content end, begin references -->
-<!-- External links -->
-<!-- -->
-<!-- Internal links -->
-<!-- -->
-<hr class="docutils" />
-<table class="docutils citation" frame="void" id="default" rules="none">
-<colgroup><col class="label" /><col /></colgroup>
-<tbody valign="top">
-<tr><td class="label">[default]</td><td><em>(<a class="fn-backref" href="#id1">1</a>, <a class="fn-backref" href="#id2">2</a>, <a class="fn-backref" href="#id3">3</a>)</em> This is the default value of the setting</td></tr>
-</tbody>
-</table>
-</div>
-</div>
-</div>
-<div class="footer">
-<hr class="footer" />
-Generated on: 2010-05-22.
-
-</div>
-</body>
-</html>
Deleted: trunk/geany-plugins/geanygendoc/docs/help/manual.rst
===================================================================
--- trunk/geany-plugins/geanygendoc/docs/help/manual.rst 2010-05-26 17:43:39 UTC (rev 1410)
+++ trunk/geany-plugins/geanygendoc/docs/help/manual.rst 2010-05-27 15:16:40 UTC (rev 1411)
@@ -1,535 +0,0 @@
-=======================
-GeanyGenDoc User Manual
-=======================
--------------------------------------------------
-A handy hand guide for the lazy documenter in you
--------------------------------------------------
-
-
-Introduction
-============
-
-First of all, welcome to this manual. Then, what is GeanyGenDoc? It is a
-plug-in for Geany as you might have noticed; but what is it meant to do?
-Basically, it generates and inserts text chunks, particularly from document's
-symbols. Its goal is to ease writing documentation for the good.
-
-
-.. contents::
-
-
-Design
-======
-
-GeanyGenDoc has an extensible design based on three points: file type,
-documentation type and rules.
-
-`File type`_
- The file type determines which configuration applies to which document. For
- example, the "c" file type corresponds to C source, and so on.
-
-`Documentation type`_
- A documentation type is an arbitrary name for a set of rules. The goal of
- documentation types is to allow different set of rules to be defined for each
- file type.
- One might want to have separate rules to generate for example `Doxygen`_
- and `Gtk-Doc`_ documentation from C sources. She should then create two
- documentation types in the C `file type configuration file`_, such as
- "doxygen" and "gtkdoc".
-
-`Rule`_
- A rule is a group of settings controlling how a documentation comment is
- generated. For example, it can define a template, describe how to handle
- particular imbrications and so on.
-
-
-Syntax
-======
-
-Key-Value pairs
----------------
-
-The syntax used by the configuration files is an extended key-value tree
-definition based on common concepts (trees, string literals, semicolon-ended
-values, etc.).
-
-The key-value syntax is as follows::
-
- key = value
-
-where value is either a semicolon-ended single value::
-
- value;
-
-or a brace-surrounded list of key-value pairs that use the same syntax again::
-
- {
- key1 = value1
- key2 = value2
- }
-
-Here a little example of the *syntax* (not any actual configuration example)::
-
- key1 = value1;
- key2 = {
- sub-key1 = sub-value1;
- sub-key2 = {
- sub-sub-key1 = sub-sub-value1;
- }
- }
-
-
-Naming
-------
-
-Key-value pairs are often referred as *group* when they are meant to have
-multiple values and as *setting* when they have a single value.
-
-
-Comments
---------
-
-Is considered as comment (and therefore ignored) everything between a number
-sign (``#``) and the following end of line, unless the ``#`` occurs as part of
-another syntactic element (such as a string literal).
-
-A short example::
-
- # This is a comment
- key = value; # This is also a comment
- string = "A string. # This isn't a comment but a string";
-
-
-Value types
------------
-
-string
- A string literal. String literals are surrounded by either single (``'``) or
- double (``"``) quotes.
-
- Some special characters can be inserted in a string with an escape sequence:
-
- ``\t``
- A tabulation.
- ``\n``
- A new line.
- ``\r``
- A carriage return.
- ``\\``
- A backslash.
- ``\'``
- A single quote (escaping only needed in single-quotes surrounded strings).
- ``\"``
- A double quote (escaping only needed in double-quotes surrounded strings).
-
- Note that backslashes are used as the escaping character, which means that it
- must be escaped to be treated as a simple backslash character.
-
- A simple example::
-
- "This is a string with \"special\" characters.\nThis is another line!"
-
-boolean
- A boolean. It can take one of the two symbolic values ``True`` and ``False``.
-
-enumeration
- An enumeration. It consists of a named constant, generally in capital letters.
- The possible values depend on the setting that use this type.
-
-flags
- A logical OR of named constants. This is like enumerations but can combine
- different values.
-
- The syntax is common for such types and uses the pipe (``|``) as
- combination character. Considering the ``A``, ``B`` and ``C`` constants, a
- valid value could be ``A | C``, which represents both ``A`` and ``C`` but
- not ``B``.
-
-list
- A list of values (often referred as array).
-
-
-File types
-==========
-
-The file type determines which configuration applies to which document.
-*File type identifiers* are the lowercased name of the Geany's file type, for
-example "c" or "python".
-
-Configuration for a particular file type goes in a file named
-``file-type-identifier.conf`` in the ``filetypes`` sub-directory of a
-`configuration directory`_.
-
-A file type configuration can contain two type of things: file-type-wide
-settings and any number of `documentation types`_.
-
-
-The ``settings`` group
-----------------------
-
-This group contains the file-type-wide settings.
-
-``match_function_arguments`` (string)
- A regular expression used to extract arguments from a function-style argument
- list (functions, methods, macros, etc.). This regular expression should match
- one argument at a time and capture only the argument's name.
- This setting is a little odd but currently needed to extract argument list
- from function definitions.
-
-``global_environment`` (string)
- A description of a CTPL_ environment to add when parsing rule_'s templates.
-
-
-The ``doctypes`` group
-----------------------
-
-This group contains a list of `documentation types`_.
-
-
-Documentation types
-===================
-
-A documentation type is a named set of rules_ for a `file type`_, describing how
-to generate a particular type of documentation (i.e. Doxygen_, `Gtk-Doc`_,
-Valadoc_ or whatever).
-
-A documentation type is identified by its name and must therefore be unique
-in a file type. But of course, different file types can define the same
-documentation type. It is even recommended for a better consistency to use the
-same identifier in different file types when they generate the same type of
-documentation (even though it is completely up to you).
-
-
-Short example
--------------
-
-::
-
- doxygen = {
- struct.member = {
- template = " /**< {cursor} */";
- position = AFTER;
- }
- struct.template = "/**\n * @brief: {cursor}\n * \n * \n */\n";
- }
-
-
-Rules: the cool thing
-=====================
-
-Rules are the actual definition of how documentation is generated. A rule
-applies to a symbol type and hierarchy, allowing fine control over which and
-how symbols are documented.
-
-A rule is represented as a group of `settings`_ in a `documentation type`_.
-The name of this group is the `type hierarchy`_ to which the settings applies.
-
-
-Type hierarchy
---------------
-
-A type hierarchy is a hierarchy of the types that a symbol must have to match
-this rule.
-
-In the symbol side, the type hierarchy is the types of the symbol's parents,
-terminated by the symbol's own type. For example, a method in a class would
-have a hierarchy like ``class -> method``; and if the class is itself in a
-namespace, the hierarchy would the look like ``namespace -> class -> method``,
-and so on.
-
-For a rule to apply, its type hierarchy must match *the end* of the symbol
-type hierarchy. For example a rule with the type hierarchy ``class`` will match
-a symbol with the type hierarchy ``namespace -> class`` but not one with
-``class -> method``.
-
-A type hierarchy uses dots (``.``) to separate types and build the hierarchy.
-For example, the type hierarchy representing ``namespace -> class`` would be
-written ``namespace.class``.
-
-
-Known types
-~~~~~~~~~~~
-
-``class``
- A class.
-``enum``
- An enumeration.
-``enumval``
- An enumeration value.
-``field``
- A field (of a class for example).
-``function``
- A function.
-``interface``
- An interface.
-``member``
- A member (of a structure for example).
-``method``
- A method.
-``namespace``
- A namespace.
-``package``
- A package.
-``prototype``
- A prototype.
-``struct``
- A structure.
-``typedef``
- A type alias definition (*typedef* in C).
-``union``
- An union.
-``variable``
- A variable.
-``extern``
- `???`
-``define``
- A definition (like the *define* C preprocessor macro).
-``macro``
- A macro.
-``file``
- A file (will never match).
-
-
-Rule settings
--------------
-
-``template`` (string)
- A CTPL_ template that can include references to the following predefined
- variables in addition to the file-type-wide and the global environment:
-
- ``argument_list`` (string list)
- A list of the arguments of the currently documented symbol.
-
- ``returns`` (boolean)
- Indicates whether the currently documented symbol returns a value
- (makes sense only for symbols that may return a value).
-
- ``children`` (string list)
- A list of the current symbol's first-level children. This is only set if
- the rule's setting ``children`` is set to ``MERGE``.
-
- **[...]**
-
- ``cursor`` (special, described below)
- This can be used to mark in the template the position where the editor's
- cursor should be moved to after comment insertion.
- This mark will be removed from the generated documentation.
- Note that even if this mark may occur as many times as you want in a
- template, only the first will be actually honored, the latter being
- only removed.
-
-``position`` (enumeration)
- The position where the documentation should be inserted. Possible values are:
-
- ``BEFORE`` [default]_
- Inserts the documentation just before the symbol.
-
- ``AFTER``
- Inserts the documentation just after the symbol (currently quite limited, it
- inserts the documentation at the end of the symbol's first line).
-
- ``CURSOR``
- Inserts the documentation at the current cursor position.
-
-``policy`` (enumeration)
- How the symbol is documented. Possible values are:
-
- ``KEEP`` [default]_
- The symbol documents itself.
-
- ``FORWARD``
- Forward the documentation request to the parent. This is useful for symbols
- that are documented by their parent, such as `Gtk-Doc`_'s enumerations.
-
-``children`` (enumeration)
- How the symbol's children can be used in the template. Possible values are:
-
- ``SPLIT`` [default]_
- The symbol's children are provided as per-type lists.
-
- ``MERGE``
- The symbol's children are provided as a single list named ``children``.
-
-``matches`` (flags)
- List of the children types that should be provided. Only useful if the
- ``children`` setting is set to ``MERGE``.
- Defaults to all.
- **FIXME: check the exactitude of this description**
-
-``auto_doc_children`` (boolean)
- Whether to also document symbol's children (according to their own rules).
-
-
-User interface in Geany
-=======================
-
-Menus
------
-
-GeanyGenDoc adds an item named `Insert Documentation Comment` in the editor's
-pop-up under the `Insert Comments` sub-menu; and a menu named
-`Documentation Generator` into the `Tools` menu.
-
-Editor's pop-up menu
-~~~~~~~~~~~~~~~~~~~~
-
-The item `Editor's pop-up → Insert Comments → Insert Documentation Comment`
-generates documentation for the current symbol. It has a keyboard shortcut
-that can be configured through Geany's keybinding configuration system, under
-`GeanyGenDoc → Insert Documentation Comment`.
-
-Tools menu
-~~~~~~~~~~
-
-The `Documentation Generator` menu under `Tools` contains the following items:
-
-`Document Current Symbol`
- This generates documentation for the current symbol. It is equivalent to the
- item `Insert Documentation Comment` that can be found in the editor's pop-up
- menu.
-
-`Document All Symbols`
- This generates documentation for all symbols in the document. This is
- equivalent to manually requesting documentation generation for each symbol in
- the document.
-
-`Reload Configuration Files`
- This force reloading of all the `file type`_ configuration files. It is
- useful when a file type configuration file was modified, in order to the new
- configuration to be used without reloading the plugin.
-
-`Edit Current Language Configuration`
- This opens the configuration file that applies to the current document for
- editing. The opened configuration file has write permissions: if it was a
- system configuration file it is copied under your personal `configuration
- directory`_ transparently.
-
-`Open Manual`
- Opens this manual in a browser.
-
-
-Preferences dialog
-------------------
-
-The preferences dialog, than can either be opened through `Edit →
-Plugin Preferences` or with the `Preferences` button in the plugin manager,
-allows to modify the following preferences:
-
-`General`
- `Save file before generating documentation`
- Choose whether the current document should be saved to disc before
- generating the documentation. This is a technical detail, but it is
- currently needed to have an up-to-date tag list. If you disable this option
- and ask for documentation generation on a modified document, the behavior
- may be surprising since the comment will be generated for the last saved
- state of the document and not the current one.
-
- `Indent inserted documentation`
- Chooses whether the inserted documentation should be indented to fit the
- indentation at the insertion position.
-
-`Documentation type`
- This list allows you to choose the documentation type to use with each file
- type. The special language `All` on top of the list is used to choose the
- default documentation type, used for all languages that haven't one set.
-
-`Global environment`
- Global environment overrides and additions. This is an environment that will
- be merged with the `file type`_-specific ones, possibly overriding some parts.
- It can be used to define some values for all the file types, such as whether
- to write the common `Since` tag, define the `Doxygen`_ prefix an so on.
- Its most use case is not to need to change a file type's environment to change
- the value of one of its elements.
-
-
-Miscellaneous
-=============
-
-Configuration directories
--------------------------
-
-Configuration directories hold GeanyGenDoc's configuration. They are the
-following:
-
-*
- The user-specific configuration directory, containing the user-defined
- settings is ``$GEANY_USER_CONFIG/plugins/geanygendoc/``.
- ``$GEANY_USER_CONFIG`` is generally ``~/.config/geany/`` on UNIX systems.
-*
- The system-wide configuration directory containing the default and
- pre-installed configuration is ``$GEANY_SYS_CONFIG/plugins/geanygendoc/``.
- ``$GEANY_SYS_CONFIG`` is generally ``/usr/share/geany/`` or
- ``/usr/local/share/geany`` on UNIX systems.
-
-When searching for configuration, GeanyGenDoc will first look in the
-user's configuration directory, and if it wasn't successful, in the system
-configuration directory. If both failed, it assumes that there is no
-configuration at all.
-
-
-Appendix
-========
-
-Configuration syntax summary
-----------------------------
-
-::
-
- string ::= ( """ .* """ | "'" .* "'" )
- constant ::= [_A-Z][_A-Z0-9]+
- integer ::= [0-9]+
- boolean ::= ( "True" | "False" )
- setting_value ::= ( string | constant | integer )
- setting ::= "setting-name" "=" setting_value ";"
- setting_list ::= ( "{" setting* "}" | setting )
- setting_section ::= "settings" "=" setting_list
-
- position ::= ( "BEFORE" | "AFTER" | "CURSOR" )
- policy ::= ( "KEEP" | "FORWARD" )
- children ::= ( "SPLIT" | "MERGE" )
- type ::= ( "class" | "enum" | "enumval" | "field" |
- "function" | "interface" | "member" | "method" |
- "namespace" | "package" | "prototype" | "struct" |
- "typedef" | "union" | "variable" | "extern" |
- "define" | "macro" | "file" )
- matches ::= type ( "|" type )*
- doctype_subsetting ::= ( "template" "=" string |
- "position" "=" position |
- "policy" "=" policy |
- "children" "=" children |
- "matches" "=" matches |
- "auto_doc_children" "=" boolean ) ";"
- match ::= type ( "." type )*
- doctype_setting ::= ( match "=" "{" doctype_subsetting* "}" |
- match "." doctype_subsetting )
- doctype_setting_list ::= ( "{" doctype_setting* "}" | doctype_setting )
- doctype ::= "doctype-name" "=" doctype_setting_list
- doctype_list ::= ( "{" doctype* "}" | doctype )
- doctype_section ::= "doctypes" "=" doctype_list
-
- document ::= ( setting_section? doctype_section? |
- doctype_section? setting_section? )
-
-
-.. Content end, begin references
-
-.. External links
-..
-.. _Doxygen: http://www.doxygen.org
-.. _Gtk-Doc: http://www.gtk.org/gtk-doc/
-.. _Valadoc: http://www.valadoc.org/
-.. _CTPL: http://ctpl.tuxfamily.org/
-
-.. Internal links
-..
-.. _file type: `File types`_
-.. _file type configuration file: `File types`_
-.. _documentation type: `Documentation types`_
-.. _rule: `Rules: the cool thing`_
-.. _rules: `Rules: the cool thing`_
-.. _settings: `Rule settings`_
-.. _configuration directory: `Configuration directories`_
-
--------------------
-
-.. [default] This is the default value of the setting
Copied: trunk/geany-plugins/geanygendoc/docs/html4css1.css (from rev 1409, trunk/geany-plugins/geanygendoc/docs/help/html4css1.css)
===================================================================
--- trunk/geany-plugins/geanygendoc/docs/html4css1.css (rev 0)
+++ trunk/geany-plugins/geanygendoc/docs/html4css1.css 2010-05-27 15:16:40 UTC (rev 1411)
@@ -0,0 +1,293 @@
+/*
+:Author: David Goodger (goodger(a)python.org)
+:Id: $Id: html4css1.css 5951 2009-05-18 18:03:10Z milde $
+:Copyright: This stylesheet has been placed in the public domain.
+
+Default cascading style sheet for the HTML output of Docutils.
+
+See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
+customize this style sheet.
+*/
+
+/* used to remove borders from tables and images */
+.borderless, table.borderless td, table.borderless th {
+ border: 0 }
+
+table.borderless td, table.borderless th {
+ /* Override padding for "table.docutils td" with "! important".
+ The right padding separates the table cells. */
+ padding: 0 0.5em 0 0 ! important }
+
+.first {
+ /* Override more specific margin styles with "! important". */
+ margin-top: 0 ! important }
+
+.last, .with-subtitle {
+ margin-bottom: 0 ! important }
+
+.hidden {
+ display: none }
+
+a.toc-backref {
+ text-decoration: none ;
+ color: black }
+
+blockquote.epigraph {
+ margin: 2em 5em ; }
+
+dl.docutils dd {
+ margin-bottom: 0.5em }
+
+/* Uncomment (and remove this text!) to get bold-faced definition list terms
+dl.docutils dt {
+ font-weight: bold }
+*/
+
+div.abstract {
+ margin: 2em 5em }
+
+div.abstract p.topic-title {
+ font-weight: bold ;
+ text-align: center }
+
+div.admonition, div.attention, div.caution, div.danger, div.error,
+div.hint, div.important, div.note, div.tip, div.warning {
+ margin: 2em ;
+ border: medium outset ;
+ padding: 1em }
+
+div.admonition p.admonition-title, div.hint p.admonition-title,
+div.important p.admonition-title, div.note p.admonition-title,
+div.tip p.admonition-title {
+ font-weight: bold ;
+ font-family: sans-serif }
+
+div.attention p.admonition-title, div.caution p.admonition-title,
+div.danger p.admonition-title, div.error p.admonition-title,
+div.warning p.admonition-title {
+ color: red ;
+ font-weight: bold ;
+ font-family: sans-serif }
+
+/* Uncomment (and remove this text!) to get reduced vertical space in
+ compound paragraphs.
+div.compound .compound-first, div.compound .compound-middle {
+ margin-bottom: 0.5em }
+
+div.compound .compound-last, div.compound .compound-middle {
+ margin-top: 0.5em }
+*/
+
+div.dedication {
+ margin: 2em 5em ;
+ text-align: center ;
+ font-style: italic }
+
+div.dedication p.topic-title {
+ font-weight: bold ;
+ font-style: normal }
+
+div.figure {
+ margin-left: 2em ;
+ margin-right: 2em }
+
+div.footer, div.header {
+ clear: both;
+ font-size: smaller }
+
+div.line-block {
+ display: block ;
+ margin-top: 1em ;
+ margin-bottom: 1em }
+
+div.line-block div.line-block {
+ margin-top: 0 ;
+ margin-bottom: 0 ;
+ margin-left: 1.5em }
+
+div.sidebar {
+ margin: 0 0 0.5em 1em ;
+ border: medium outset ;
+ padding: 1em ;
+ background-color: #ffffee ;
+ width: 40% ;
+ float: right ;
+ clear: right }
+
+div.sidebar p.rubric {
+ font-family: sans-serif ;
+ font-size: medium }
+
+div.system-messages {
+ margin: 5em }
+
+div.system-messages h1 {
+ color: red }
+
+div.system-message {
+ border: medium outset ;
+ padding: 1em }
+
+div.system-message p.system-message-title {
+ color: red ;
+ font-weight: bold }
+
+div.topic {
+ margin: 2em }
+
+h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
+h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
+ margin-top: 0.4em }
+
+h1.title {
+ text-align: center }
+
+h2.subtitle {
+ text-align: center }
+
+hr.docutils {
+ width: 75% }
+
+img.align-left, .figure.align-left{
+ clear: left ;
+ float: left ;
+ margin-right: 1em }
+
+img.align-right, .figure.align-right {
+ clear: right ;
+ float: right ;
+ margin-left: 1em }
+
+.align-left {
+ text-align: left }
+
+.align-center {
+ clear: both ;
+ text-align: center }
+
+.align-right {
+ text-align: right }
+
+/* reset inner alignment in figures */
+div.align-right {
+ text-align: left }
+
+/* div.align-center * { */
+/* text-align: left } */
+
+ol.simple, ul.simple {
+ margin-bottom: 1em }
+
+ol.arabic {
+ list-style: decimal }
+
+ol.loweralpha {
+ list-style: lower-alpha }
+
+ol.upperalpha {
+ list-style: upper-alpha }
+
+ol.lowerroman {
+ list-style: lower-roman }
+
+ol.upperroman {
+ list-style: upper-roman }
+
+p.attribution {
+ text-align: right ;
+ margin-left: 50% }
+
+p.caption {
+ font-style: italic }
+
+p.credits {
+ font-style: italic ;
+ font-size: smaller }
+
+p.label {
+ white-space: nowrap }
+
+p.rubric {
+ font-weight: bold ;
+ font-size: larger ;
+ color: maroon ;
+ text-align: center }
+
+p.sidebar-title {
+ font-family: sans-serif ;
+ font-weight: bold ;
+ font-size: larger }
+
+p.sidebar-subtitle {
+ font-family: sans-serif ;
+ font-weight: bold }
+
+p.topic-title {
+ font-weight: bold }
+
+pre.address {
+ margin-bottom: 0 ;
+ margin-top: 0 ;
+ font: inherit }
+
+pre.literal-block, pre.doctest-block {
+ margin-left: 2em ;
+ margin-right: 2em }
+
+span.classifier {
+ font-family: sans-serif ;
+ font-style: oblique }
+
+span.classifier-delimiter {
+ font-family: sans-serif ;
+ font-weight: bold }
+
+span.interpreted {
+ font-family: sans-serif }
+
+span.option {
+ white-space: nowrap }
+
+span.pre {
+ white-space: pre }
+
+span.problematic {
+ color: red }
+
+span.section-subtitle {
+ /* font-size relative to parent (h1..h6 element) */
+ font-size: 80% }
+
+table.citation {
+ border-left: solid 1px gray;
+ margin-left: 1px }
+
+table.docinfo {
+ margin: 2em 4em }
+
+table.docutils {
+ margin-top: 0.5em ;
+ margin-bottom: 0.5em }
+
+table.footnote {
+ border-left: solid 1px black;
+ margin-left: 1px }
+
+table.docutils td, table.docutils th,
+table.docinfo td, table.docinfo th {
+ padding-left: 0.5em ;
+ padding-right: 0.5em ;
+ vertical-align: top }
+
+table.docutils th.field-name, table.docinfo th.docinfo-name {
+ font-weight: bold ;
+ text-align: left ;
+ white-space: nowrap ;
+ padding-left: 0 }
+
+h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
+h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
+ font-size: 100% }
+
+ul.auto-toc {
+ list-style-type: none }
Copied: trunk/geany-plugins/geanygendoc/docs/manual.css (from rev 1409, trunk/geany-plugins/geanygendoc/docs/help/manual.css)
===================================================================
--- trunk/geany-plugins/geanygendoc/docs/manual.css (rev 0)
+++ trunk/geany-plugins/geanygendoc/docs/manual.css 2010-05-27 15:16:40 UTC (rev 1411)
@@ -0,0 +1,68 @@
+/*
+:Author: Colomban Wendling
+:Contact: ban(a)herbesfolles.org
+:Copyright: This stylesheet has been placed in the public domain.
+
+Stylesheet for use with Docutils.
+*/
+
+@import url(html4css1.css);
+
+html {
+ background-color: #eeeeec;
+ color: #2e3436;
+ font-family: bitstream vera sans, sans-serif;
+ margin: 0 1em;
+}
+
+
+h1, h2, h3, h4, h5, h6, p.topic-title {
+ font-family: georgia, times new roman, times, serif;
+}
+
+h2.subtitle {
+ font-style: italic;
+ font-weight: normal;
+}
+
+p, dd {
+ text-align: justify;
+}
+
+.literal-block,
+.literal {
+ background: #fff;
+}
+.literal-block {
+ border: 1px solid #babdb6;
+ padding: 1px 2px;
+}
+h1 .literal, h2 .literal, h3 .literal, h4 .literal, h5 .literal, h6 .literal
+p.topic-title .literal {
+ background: inherit;
+ text-align: left;
+}
+
+
+.footnote-reference {
+ vertical-align: super;
+ font-size: 75%;
+}
+
+
+a { text-decoration: none; }
+a:hover { text-decoration: underline }
+a:link { color: #204a87; }
+a:visited { color: #5c3566; }
+
+h1 a, h1 a:hover, h1 a:link, h1 a:visited,
+h2 a, h2 a:hover, h2 a:link, h2 a:visited,
+h3 a, h3 a:hover, h3 a:link, h3 a:visited,
+h4 a, h4 a:hover, h4 a:link, h4 a:visited,
+h5 a, h5 a:hover, h5 a:link, h5 a:visited,
+h6 a, h6 a:hover, h6 a:link, h6 a:visited,
+p.topic-title a, p.topic-title a:hover, p.topic-title a:link, p.topic-title a:visited
+{
+ text-decoration: none;
+ color: inherit;
+}
Copied: trunk/geany-plugins/geanygendoc/docs/manual.html (from rev 1409, trunk/geany-plugins/geanygendoc/docs/help/manual.html)
===================================================================
--- trunk/geany-plugins/geanygendoc/docs/manual.html (rev 0)
+++ trunk/geany-plugins/geanygendoc/docs/manual.html 2010-05-27 15:16:40 UTC (rev 1411)
@@ -0,0 +1,602 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<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.6: http://docutils.sourceforge.net/" />
+<title>GeanyGenDoc User Manual</title>
+<style type="text/css">
+
+/*
+:Author: Colomban Wendling
+:Contact: ban(a)herbesfolles.org
+:Copyright: This stylesheet has been placed in the public domain.
+
+Stylesheet for use with Docutils.
+*/
+
+@import url(html4css1.css);
+
+html {
+ background-color: #eeeeec;
+ color: #2e3436;
+ font-family: bitstream vera sans, sans-serif;
+ margin: 0 1em;
+}
+
+
+h1, h2, h3, h4, h5, h6, p.topic-title {
+ font-family: georgia, times new roman, times, serif;
+}
+
+h2.subtitle {
+ font-style: italic;
+ font-weight: normal;
+}
+
+p, dd {
+ text-align: justify;
+}
+
+.literal-block,
+.literal {
+ background: #fff;
+}
+.literal-block {
+ border: 1px solid #babdb6;
+ padding: 1px 2px;
+}
+h1 .literal, h2 .literal, h3 .literal, h4 .literal, h5 .literal, h6 .literal
+p.topic-title .literal {
+ background: inherit;
+ text-align: left;
+}
+
+
+.footnote-reference {
+ vertical-align: super;
+ font-size: 75%;
+}
+
+
+a { text-decoration: none; }
+a:hover { text-decoration: underline }
+a:link { color: #204a87; }
+a:visited { color: #5c3566; }
+
+h1 a, h1 a:hover, h1 a:link, h1 a:visited,
+h2 a, h2 a:hover, h2 a:link, h2 a:visited,
+h3 a, h3 a:hover, h3 a:link, h3 a:visited,
+h4 a, h4 a:hover, h4 a:link, h4 a:visited,
+h5 a, h5 a:hover, h5 a:link, h5 a:visited,
+h6 a, h6 a:hover, h6 a:link, h6 a:visited,
+p.topic-title a, p.topic-title a:hover, p.topic-title a:link, p.topic-title a:visited
+{
+ text-decoration: none;
+ color: inherit;
+}
+
+</style>
+</head>
+<body>
+<div class="document" id="geanygendoc-user-manual">
+<h1 class="title">GeanyGenDoc User Manual</h1>
+<h2 class="subtitle" id="a-handy-hand-guide-for-the-lazy-documenter-in-you">A handy hand guide for the lazy documenter in you</h2>
+
+<div class="section" id="introduction">
+<h1><a class="toc-backref" href="#id4">Introduction</a></h1>
+<p>First of all, welcome to this manual. Then, what is GeanyGenDoc? It is a
+plug-in for Geany as you might have noticed; but what is it meant to do?
+Basically, it generates and inserts text chunks, particularly from document's
+symbols. Its goal is to ease writing documentation for the good.</p>
+<div class="contents topic" id="contents">
+<p class="topic-title first">Contents</p>
+<ul class="simple">
+<li><a class="reference internal" href="#introduction" id="id4">Introduction</a></li>
+<li><a class="reference internal" href="#design" id="id5">Design</a></li>
+<li><a class="reference internal" href="#syntax" id="id6">Syntax</a><ul>
+<li><a class="reference internal" href="#key-value-pairs" id="id7">Key-Value pairs</a></li>
+<li><a class="reference internal" href="#naming" id="id8">Naming</a></li>
+<li><a class="reference internal" href="#comments" id="id9">Comments</a></li>
+<li><a class="reference internal" href="#value-types" id="id10">Value types</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#file-types" id="id11">File types</a><ul>
+<li><a class="reference internal" href="#the-settings-group" id="id12">The <tt class="docutils literal">settings</tt> group</a></li>
+<li><a class="reference internal" href="#the-doctypes-group" id="id13">The <tt class="docutils literal">doctypes</tt> group</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#documentation-types" id="id14">Documentation types</a><ul>
+<li><a class="reference internal" href="#short-example" id="id15">Short example</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#rules-the-cool-thing" id="id16">Rules: the cool thing</a><ul>
+<li><a class="reference internal" href="#type-hierarchy" id="id17">Type hierarchy</a><ul>
+<li><a class="reference internal" href="#known-types" id="id18">Known types</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#rule-settings" id="id19">Rule settings</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#user-interface-in-geany" id="id20">User interface in Geany</a><ul>
+<li><a class="reference internal" href="#menus" id="id21">Menus</a><ul>
+<li><a class="reference internal" href="#editor-s-pop-up-menu" id="id22">Editor's pop-up menu</a></li>
+<li><a class="reference internal" href="#tools-menu" id="id23">Tools menu</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#preferences-dialog" id="id24">Preferences dialog</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#miscellaneous" id="id25">Miscellaneous</a><ul>
+<li><a class="reference internal" href="#configuration-directories" id="id26">Configuration directories</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#appendix" id="id27">Appendix</a><ul>
+<li><a class="reference internal" href="#configuration-syntax-summary" id="id28">Configuration syntax summary</a></li>
+</ul>
+</li>
+</ul>
+</div>
+</div>
+<div class="section" id="design">
+<h1><a class="toc-backref" href="#id5">Design</a></h1>
+<p>GeanyGenDoc has an extensible design based on three points: file type,
+documentation type and rules.</p>
+<dl class="docutils">
+<dt><a class="reference internal" href="#file-types">File type</a></dt>
+<dd>The file type determines which configuration applies to which document. For
+example, the "c" file type corresponds to C source, and so on.</dd>
+<dt><a class="reference internal" href="#documentation-types">Documentation type</a></dt>
+<dd>A documentation type is an arbitrary name for a set of rules. The goal of
+documentation types is to allow different set of rules to be defined for each
+file type.
+One might want to have separate rules to generate for example <a class="reference external" href="http://www.doxygen.org">Doxygen</a>
+and <a class="reference external" href="http://www.gtk.org/gtk-doc/">Gtk-Doc</a> documentation from C sources. She should then create two
+documentation types in the C <a class="reference internal" href="#file-types">file type configuration file</a>, such as
+"doxygen" and "gtkdoc".</dd>
+<dt><a class="reference internal" href="#rules-the-cool-thing">Rule</a></dt>
+<dd>A rule is a group of settings controlling how a documentation comment is
+generated. For example, it can define a template, describe how to handle
+particular imbrications and so on.</dd>
+</dl>
+</div>
+<div class="section" id="syntax">
+<h1><a class="toc-backref" href="#id6">Syntax</a></h1>
+<div class="section" id="key-value-pairs">
+<h2><a class="toc-backref" href="#id7">Key-Value pairs</a></h2>
+<p>The syntax used by the configuration files is an extended key-value tree
+definition based on common concepts (trees, string literals, semicolon-ended
+values, etc.).</p>
+<p>The key-value syntax is as follows:</p>
+<pre class="literal-block">
+key = value
+</pre>
+<p>where value is either a semicolon-ended single value:</p>
+<pre class="literal-block">
+value;
+</pre>
+<p>or a brace-surrounded list of key-value pairs that use the same syntax again:</p>
+<pre class="literal-block">
+{
+ key1 = value1
+ key2 = value2
+}
+</pre>
+<p>Here a little example of the <em>syntax</em> (not any actual configuration example):</p>
+<pre class="literal-block">
+key1 = value1;
+key2 = {
+ sub-key1 = sub-value1;
+ sub-key2 = {
+ sub-sub-key1 = sub-sub-value1;
+ }
+}
+</pre>
+</div>
+<div class="section" id="naming">
+<h2><a class="toc-backref" href="#id8">Naming</a></h2>
+<p>Key-value pairs are often referred as <em>group</em> when they are meant to have
+multiple values and as <em>setting</em> when they have a single value.</p>
+</div>
+<div class="section" id="comments">
+<h2><a class="toc-backref" href="#id9">Comments</a></h2>
+<p>Is considered as comment (and therefore ignored) everything between a number
+sign (<tt class="docutils literal">#</tt>) and the following end of line, unless the <tt class="docutils literal">#</tt> occurs as part of
+another syntactic element (such as a string literal).</p>
+<p>A short example:</p>
+<pre class="literal-block">
+# This is a comment
+key = value; # This is also a comment
+string = "A string. # This isn't a comment but a string";
+</pre>
+</div>
+<div class="section" id="value-types">
+<h2><a class="toc-backref" href="#id10">Value types</a></h2>
+<dl class="docutils">
+<dt>string</dt>
+<dd><p class="first">A string literal. String literals are surrounded by either single (<tt class="docutils literal">'</tt>) or
+double (<tt class="docutils literal">"</tt>) quotes.</p>
+<p>Some special characters can be inserted in a string with an escape sequence:</p>
+<dl class="docutils">
+<dt><tt class="docutils literal">\t</tt></dt>
+<dd>A tabulation.</dd>
+<dt><tt class="docutils literal">\n</tt></dt>
+<dd>A new line.</dd>
+<dt><tt class="docutils literal">\r</tt></dt>
+<dd>A carriage return.</dd>
+<dt><tt class="docutils literal">\\</tt></dt>
+<dd>A backslash.</dd>
+<dt><tt class="docutils literal">\'</tt></dt>
+<dd>A single quote (escaping only needed in single-quotes surrounded strings).</dd>
+<dt><tt class="docutils literal">\"</tt></dt>
+<dd>A double quote (escaping only needed in double-quotes surrounded strings).</dd>
+</dl>
+<p>Note that backslashes are used as the escaping character, which means that it
+must be escaped to be treated as a simple backslash character.</p>
+<p>A simple example:</p>
+<pre class="last literal-block">
+"This is a string with \"special\" characters.\nThis is another line!"
+</pre>
+</dd>
+<dt>boolean</dt>
+<dd>A boolean. It can take one of the two symbolic values <tt class="docutils literal">True</tt> and <tt class="docutils literal">False</tt>.</dd>
+<dt>enumeration</dt>
+<dd>An enumeration. It consists of a named constant, generally in capital letters.
+The possible values depend on the setting that use this type.</dd>
+<dt>flags</dt>
+<dd><p class="first">A logical OR of named constants. This is like enumerations but can combine
+different values.</p>
+<p class="last">The syntax is common for such types and uses the pipe (<tt class="docutils literal">|</tt>) as
+combination character. Considering the <tt class="docutils literal">A</tt>, <tt class="docutils literal">B</tt> and <tt class="docutils literal">C</tt> constants, a
+valid value could be <tt class="docutils literal">A | C</tt>, which represents both <tt class="docutils literal">A</tt> and <tt class="docutils literal">C</tt> but
+not <tt class="docutils literal">B</tt>.</p>
+</dd>
+<dt>list</dt>
+<dd>A list of values (often referred as array).</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="file-types">
+<h1><a class="toc-backref" href="#id11">File types</a></h1>
+<p>The file type determines which configuration applies to which document.
+<em>File type identifiers</em> are the lowercased name of the Geany's file type, for
+example "c" or "python".</p>
+<p>Configuration for a particular file type goes in a file named
+<tt class="docutils literal"><span class="pre">file-type-identifier.conf</span></tt> in the <tt class="docutils literal">filetypes</tt> sub-directory of a
+<a class="reference internal" href="#configuration-directories">configuration directory</a>.</p>
+<p>A file type configuration can contain two type of things: file-type-wide
+settings and any number of <a class="reference internal" href="#documentation-types">documentation types</a>.</p>
+<div class="section" id="the-settings-group">
+<h2><a class="toc-backref" href="#id12">The <tt class="docutils literal">settings</tt> group</a></h2>
+<p>This group contains the file-type-wide settings.</p>
+<dl class="docutils">
+<dt><tt class="docutils literal">match_function_arguments</tt> (string)</dt>
+<dd>A regular expression used to extract arguments from a function-style argument
+list (functions, methods, macros, etc.). This regular expression should match
+one argument at a time and capture only the argument's name.
+This setting is a little odd but currently needed to extract argument list
+from function definitions.</dd>
+<dt><tt class="docutils literal">global_environment</tt> (string)</dt>
+<dd>A description of a <a class="reference external" href="http://ctpl.tuxfamily.org/">CTPL</a> environment to add when parsing <a class="reference internal" href="#rules-the-cool-thing">rule</a>'s templates.</dd>
+</dl>
+</div>
+<div class="section" id="the-doctypes-group">
+<h2><a class="toc-backref" href="#id13">The <tt class="docutils literal">doctypes</tt> group</a></h2>
+<p>This group contains a list of <a class="reference internal" href="#documentation-types">documentation types</a>.</p>
+</div>
+</div>
+<div class="section" id="documentation-types">
+<h1><a class="toc-backref" href="#id14">Documentation types</a></h1>
+<p>A documentation type is a named set of <a class="reference internal" href="#rules-the-cool-thing">rules</a> for a <a class="reference internal" href="#file-types">file type</a>, describing how
+to generate a particular type of documentation (i.e. <a class="reference external" href="http://www.doxygen.org">Doxygen</a>, <a class="reference external" href="http://www.gtk.org/gtk-doc/">Gtk-Doc</a>,
+<a class="reference external" href="http://www.valadoc.org/">Valadoc</a> or whatever).</p>
+<p>A documentation type is identified by its name and must therefore be unique
+in a file type. But of course, different file types can define the same
+documentation type. It is even recommended for a better consistency to use the
+same identifier in different file types when they generate the same type of
+documentation (even though it is completely up to you).</p>
+<div class="section" id="short-example">
+<h2><a class="toc-backref" href="#id15">Short example</a></h2>
+<pre class="literal-block">
+doxygen = {
+ struct.member = {
+ template = " /**< {cursor} */";
+ position = AFTER;
+ }
+ struct.template = "/**\n * @brief: {cursor}\n * \n * \n */\n";
+}
+</pre>
+</div>
+</div>
+<div class="section" id="rules-the-cool-thing">
+<h1><a class="toc-backref" href="#id16">Rules: the cool thing</a></h1>
+<p>Rules are the actual definition of how documentation is generated. A rule
+applies to a symbol type and hierarchy, allowing fine control over which and
+how symbols are documented.</p>
+<p>A rule is represented as a group of <a class="reference internal" href="#rule-settings">settings</a> in a <a class="reference internal" href="#documentation-types">documentation type</a>.
+The name of this group is the <a class="reference internal" href="#type-hierarchy">type hierarchy</a> to which the settings applies.</p>
+<div class="section" id="type-hierarchy">
+<h2><a class="toc-backref" href="#id17">Type hierarchy</a></h2>
+<p>A type hierarchy is a hierarchy of the types that a symbol must have to match
+this rule.</p>
+<p>In the symbol side, the type hierarchy is the types of the symbol's parents,
+terminated by the symbol's own type. For example, a method in a class would
+have a hierarchy like <tt class="docutils literal">class <span class="pre">-></span> method</tt>; and if the class is itself in a
+namespace, the hierarchy would the look like <tt class="docutils literal">namespace <span class="pre">-></span> class <span class="pre">-></span> method</tt>,
+and so on.</p>
+<p>For a rule to apply, its type hierarchy must match <em>the end</em> of the symbol
+type hierarchy. For example a rule with the type hierarchy <tt class="docutils literal">class</tt> will match
+a symbol with the type hierarchy <tt class="docutils literal">namespace <span class="pre">-></span> class</tt> but not one with
+<tt class="docutils literal">class <span class="pre">-></span> method</tt>.</p>
+<p>A type hierarchy uses dots (<tt class="docutils literal">.</tt>) to separate types and build the hierarchy.
+For example, the type hierarchy representing <tt class="docutils literal">namespace <span class="pre">-></span> class</tt> would be
+written <tt class="docutils literal">namespace.class</tt>.</p>
+<div class="section" id="known-types">
+<h3><a class="toc-backref" href="#id18">Known types</a></h3>
+<dl class="docutils">
+<dt><tt class="docutils literal">class</tt></dt>
+<dd>A class.</dd>
+<dt><tt class="docutils literal">enum</tt></dt>
+<dd>An enumeration.</dd>
+<dt><tt class="docutils literal">enumval</tt></dt>
+<dd>An enumeration value.</dd>
+<dt><tt class="docutils literal">field</tt></dt>
+<dd>A field (of a class for example).</dd>
+<dt><tt class="docutils literal">function</tt></dt>
+<dd>A function.</dd>
+<dt><tt class="docutils literal">interface</tt></dt>
+<dd>An interface.</dd>
+<dt><tt class="docutils literal">member</tt></dt>
+<dd>A member (of a structure for example).</dd>
+<dt><tt class="docutils literal">method</tt></dt>
+<dd>A method.</dd>
+<dt><tt class="docutils literal">namespace</tt></dt>
+<dd>A namespace.</dd>
+<dt><tt class="docutils literal">package</tt></dt>
+<dd>A package.</dd>
+<dt><tt class="docutils literal">prototype</tt></dt>
+<dd>A prototype.</dd>
+<dt><tt class="docutils literal">struct</tt></dt>
+<dd>A structure.</dd>
+<dt><tt class="docutils literal">typedef</tt></dt>
+<dd>A type alias definition (<em>typedef</em> in C).</dd>
+<dt><tt class="docutils literal">union</tt></dt>
+<dd>An union.</dd>
+<dt><tt class="docutils literal">variable</tt></dt>
+<dd>A variable.</dd>
+<dt><tt class="docutils literal">extern</tt></dt>
+<dd><cite>???</cite></dd>
+<dt><tt class="docutils literal">define</tt></dt>
+<dd>A definition (like the <em>define</em> C preprocessor macro).</dd>
+<dt><tt class="docutils literal">macro</tt></dt>
+<dd>A macro.</dd>
+<dt><tt class="docutils literal">file</tt></dt>
+<dd>A file (will never match).</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="rule-settings">
+<h2><a class="toc-backref" href="#id19">Rule settings</a></h2>
+<dl class="docutils">
+<dt><tt class="docutils literal">template</tt> (string)</dt>
+<dd><p class="first">A <a class="reference external" href="http://ctpl.tuxfamily.org/">CTPL</a> template that can include references to the following predefined
+variables in addition to the file-type-wide and the global environment:</p>
+<dl class="docutils">
+<dt><tt class="docutils literal">argument_list</tt> (string list)</dt>
+<dd>A list of the arguments of the currently documented symbol.</dd>
+<dt><tt class="docutils literal">returns</tt> (boolean)</dt>
+<dd>Indicates whether the currently documented symbol returns a value
+(makes sense only for symbols that may return a value).</dd>
+<dt><tt class="docutils literal">children</tt> (string list)</dt>
+<dd>A list of the current symbol's first-level children. This is only set if
+the rule's setting <tt class="docutils literal">children</tt> is set to <tt class="docutils literal">MERGE</tt>.</dd>
+</dl>
+<p><strong>[...]</strong></p>
+<dl class="last docutils">
+<dt><tt class="docutils literal">cursor</tt> (special, described below)</dt>
+<dd>This can be used to mark in the template the position where the editor's
+cursor should be moved to after comment insertion.
+This mark will be removed from the generated documentation.
+Note that even if this mark may occur as many times as you want in a
+template, only the first will be actually honored, the latter being
+only removed.</dd>
+</dl>
+</dd>
+<dt><tt class="docutils literal">position</tt> (enumeration)</dt>
+<dd><p class="first">The position where the documentation should be inserted. Possible values are:</p>
+<dl class="last docutils">
+<dt><tt class="docutils literal">BEFORE</tt> <a class="citation-reference" href="#default" id="id1">[default]</a></dt>
+<dd>Inserts the documentation just before the symbol.</dd>
+<dt><tt class="docutils literal">AFTER</tt></dt>
+<dd>Inserts the documentation just after the symbol (currently quite limited, it
+inserts the documentation at the end of the symbol's first line).</dd>
+<dt><tt class="docutils literal">CURSOR</tt></dt>
+<dd>Inserts the documentation at the current cursor position.</dd>
+</dl>
+</dd>
+<dt><tt class="docutils literal">policy</tt> (enumeration)</dt>
+<dd><p class="first">How the symbol is documented. Possible values are:</p>
+<dl class="last docutils">
+<dt><tt class="docutils literal">KEEP</tt> <a class="citation-reference" href="#default" id="id2">[default]</a></dt>
+<dd>The symbol documents itself.</dd>
+<dt><tt class="docutils literal">FORWARD</tt></dt>
+<dd>Forward the documentation request to the parent. This is useful for symbols
+that are documented by their parent, such as <a class="reference external" href="http://www.gtk.org/gtk-doc/">Gtk-Doc</a>'s enumerations.</dd>
+</dl>
+</dd>
+<dt><tt class="docutils literal">children</tt> (enumeration)</dt>
+<dd><p class="first">How the symbol's children can be used in the template. Possible values are:</p>
+<dl class="last docutils">
+<dt><tt class="docutils literal">SPLIT</tt> <a class="citation-reference" href="#default" id="id3">[default]</a></dt>
+<dd>The symbol's children are provided as per-type lists.</dd>
+<dt><tt class="docutils literal">MERGE</tt></dt>
+<dd>The symbol's children are provided as a single list named <tt class="docutils literal">children</tt>.</dd>
+</dl>
+</dd>
+<dt><tt class="docutils literal">matches</tt> (flags)</dt>
+<dd>List of the children types that should be provided. Only useful if the
+<tt class="docutils literal">children</tt> setting is set to <tt class="docutils literal">MERGE</tt>.
+Defaults to all.
+<strong>FIXME: check the exactitude of this description</strong></dd>
+<dt><tt class="docutils literal">auto_doc_children</tt> (boolean)</dt>
+<dd>Whether to also document symbol's children (according to their own rules).</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="user-interface-in-geany">
+<h1><a class="toc-backref" href="#id20">User interface in Geany</a></h1>
+<div class="section" id="menus">
+<h2><a class="toc-backref" href="#id21">Menus</a></h2>
+<p>GeanyGenDoc adds an item named <cite>Insert Documentation Comment</cite> in the editor's
+pop-up under the <cite>Insert Comments</cite> sub-menu; and a menu named
+<cite>Documentation Generator</cite> into the <cite>Tools</cite> menu.</p>
+<div class="section" id="editor-s-pop-up-menu">
+<h3><a class="toc-backref" href="#id22">Editor's pop-up menu</a></h3>
+<p>The item <cite>Editor's pop-up → Insert Comments → Insert Documentation Comment</cite>
+generates documentation for the current symbol. It has a keyboard shortcut
+that can be configured through Geany's keybinding configuration system, under
+<cite>GeanyGenDoc → Insert Documentation Comment</cite>.</p>
+</div>
+<div class="section" id="tools-menu">
+<h3><a class="toc-backref" href="#id23">Tools menu</a></h3>
+<p>The <cite>Documentation Generator</cite> menu under <cite>Tools</cite> contains the following items:</p>
+<dl class="docutils">
+<dt><cite>Document Current Symbol</cite></dt>
+<dd>This generates documentation for the current symbol. It is equivalent to the
+item <cite>Insert Documentation Comment</cite> that can be found in the editor's pop-up
+menu.</dd>
+<dt><cite>Document All Symbols</cite></dt>
+<dd>This generates documentation for all symbols in the document. This is
+equivalent to manually requesting documentation generation for each symbol in
+the document.</dd>
+<dt><cite>Reload Configuration Files</cite></dt>
+<dd>This force reloading of all the <a class="reference internal" href="#file-types">file type</a> configuration files. It is
+useful when a file type configuration file was modified, in order to the new
+configuration to be used without reloading the plugin.</dd>
+<dt><cite>Edit Current Language Configuration</cite></dt>
+<dd>This opens the configuration file that applies to the current document for
+editing. The opened configuration file has write permissions: if it was a
+system configuration file it is copied under your personal <a class="reference internal" href="#configuration-directories">configuration
+directory</a> transparently.</dd>
+<dt><cite>Open Manual</cite></dt>
+<dd>Opens this manual in a browser.</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="preferences-dialog">
+<h2><a class="toc-backref" href="#id24">Preferences dialog</a></h2>
+<p>The preferences dialog, than can either be opened through <cite>Edit →
+Plugin Preferences</cite> or with the <cite>Preferences</cite> button in the plugin manager,
+allows to modify the following preferences:</p>
+<dl class="docutils">
+<dt><cite>General</cite></dt>
+<dd><dl class="first last docutils">
+<dt><cite>Save file before generating documentation</cite></dt>
+<dd>Choose whether the current document should be saved to disc before
+generating the documentation. This is a technical detail, but it is
+currently needed to have an up-to-date tag list. If you disable this option
+and ask for documentation generation on a modified document, the behavior
+may be surprising since the comment will be generated for the last saved
+state of the document and not the current one.</dd>
+<dt><cite>Indent inserted documentation</cite></dt>
+<dd>Chooses whether the inserted documentation should be indented to fit the
+indentation at the insertion position.</dd>
+</dl>
+</dd>
+<dt><cite>Documentation type</cite></dt>
+<dd>This list allows you to choose the documentation type to use with each file
+type. The special language <cite>All</cite> on top of the list is used to choose the
+default documentation type, used for all languages that haven't one set.</dd>
+<dt><cite>Global environment</cite></dt>
+<dd>Global environment overrides and additions. This is an environment that will
+be merged with the <a class="reference internal" href="#file-types">file type</a>-specific ones, possibly overriding some parts.
+It can be used to define some values for all the file types, such as whether
+to write the common <cite>Since</cite> tag, define the <a class="reference external" href="http://www.doxygen.org">Doxygen</a> prefix an so on.
+Its most use case is not to need to change a file type's environment to change
+the value of one of its elements.</dd>
+</dl>
+</div>
+</div>
+<div class="section" id="miscellaneous">
+<h1><a class="toc-backref" href="#id25">Miscellaneous</a></h1>
+<div class="section" id="configuration-directories">
+<h2><a class="toc-backref" href="#id26">Configuration directories</a></h2>
+<p>Configuration directories hold GeanyGenDoc's configuration. They are the
+following:</p>
+<ul class="simple">
+<li>The user-specific configuration directory, containing the user-defined
+settings is <tt class="docutils literal">$GEANY_USER_CONFIG/plugins/geanygendoc/</tt>.
+<tt class="docutils literal">$GEANY_USER_CONFIG</tt> is generally <tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt> on UNIX systems.</li>
+<li>The system-wide configuration directory containing the default and
+pre-installed configuration is <tt class="docutils literal">$GEANY_SYS_CONFIG/plugins/geanygendoc/</tt>.
+<tt class="docutils literal">$GEANY_SYS_CONFIG</tt> is generally <tt class="docutils literal">/usr/share/geany/</tt> or
+<tt class="docutils literal">/usr/local/share/geany</tt> on UNIX systems.</li>
+</ul>
+<p>When searching for configuration, GeanyGenDoc will first look in the
+user's configuration directory, and if it wasn't successful, in the system
+configuration directory. If both failed, it assumes that there is no
+configuration at all.</p>
+</div>
+</div>
+<div class="section" id="appendix">
+<h1><a class="toc-backref" href="#id27">Appendix</a></h1>
+<div class="section" id="configuration-syntax-summary">
+<h2><a class="toc-backref" href="#id28">Configuration syntax summary</a></h2>
+<pre class="literal-block">
+string ::= ( """ .* """ | "'" .* "'" )
+constant ::= [_A-Z][_A-Z0-9]+
+integer ::= [0-9]+
+boolean ::= ( "True" | "False" )
+setting_value ::= ( string | constant | integer )
+setting ::= "setting-name" "=" setting_value ";"
+setting_list ::= ( "{" setting* "}" | setting )
+setting_section ::= "settings" "=" setting_list
+
+position ::= ( "BEFORE" | "AFTER" | "CURSOR" )
+policy ::= ( "KEEP" | "FORWARD" )
+children ::= ( "SPLIT" | "MERGE" )
+type ::= ( "class" | "enum" | "enumval" | "field" |
+ "function" | "interface" | "member" | "method" |
+ "namespace" | "package" | "prototype" | "struct" |
+ "typedef" | "union" | "variable" | "extern" |
+ "define" | "macro" | "file" )
+matches ::= type ( "|" type )*
+doctype_subsetting ::= ( "template" "=" string |
+ "position" "=" position |
+ "policy" "=" policy |
+ "children" "=" children |
+ "matches" "=" matches |
+ "auto_doc_children" "=" boolean ) ";"
+match ::= type ( "." type )*
+doctype_setting ::= ( match "=" "{" doctype_subsetting* "}" |
+ match "." doctype_subsetting )
+doctype_setting_list ::= ( "{" doctype_setting* "}" | doctype_setting )
+doctype ::= "doctype-name" "=" doctype_setting_list
+doctype_list ::= ( "{" doctype* "}" | doctype )
+doctype_section ::= "doctypes" "=" doctype_list
+
+document ::= ( setting_section? doctype_section? |
+ doctype_section? setting_section? )
+</pre>
+<!-- Content end, begin references -->
+<!-- External links -->
+<!-- -->
+<!-- Internal links -->
+<!-- -->
+<hr class="docutils" />
+<table class="docutils citation" frame="void" id="default" rules="none">
+<colgroup><col class="label" /><col /></colgroup>
+<tbody valign="top">
+<tr><td class="label">[default]</td><td><em>(<a class="fn-backref" href="#id1">1</a>, <a class="fn-backref" href="#id2">2</a>, <a class="fn-backref" href="#id3">3</a>)</em> This is the default value of the setting</td></tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+<div class="footer">
+<hr class="footer" />
+Generated on: 2010-05-22.
+
+</div>
+</body>
+</html>
Copied: trunk/geany-plugins/geanygendoc/docs/manual.rst (from rev 1409, trunk/geany-plugins/geanygendoc/docs/help/manual.rst)
===================================================================
--- trunk/geany-plugins/geanygendoc/docs/manual.rst (rev 0)
+++ trunk/geany-plugins/geanygendoc/docs/manual.rst 2010-05-27 15:16:40 UTC (rev 1411)
@@ -0,0 +1,535 @@
+=======================
+GeanyGenDoc User Manual
+=======================
+-------------------------------------------------
+A handy hand guide for the lazy documenter in you
+-------------------------------------------------
+
+
+Introduction
+============
+
+First of all, welcome to this manual. Then, what is GeanyGenDoc? It is a
+plug-in for Geany as you might have noticed; but what is it meant to do?
+Basically, it generates and inserts text chunks, particularly from document's
+symbols. Its goal is to ease writing documentation for the good.
+
+
+.. contents::
+
+
+Design
+======
+
+GeanyGenDoc has an extensible design based on three points: file type,
+documentation type and rules.
+
+`File type`_
+ The file type determines which configuration applies to which document. For
+ example, the "c" file type corresponds to C source, and so on.
+
+`Documentation type`_
+ A documentation type is an arbitrary name for a set of rules. The goal of
+ documentation types is to allow different set of rules to be defined for each
+ file type.
+ One might want to have separate rules to generate for example `Doxygen`_
+ and `Gtk-Doc`_ documentation from C sources. She should then create two
+ documentation types in the C `file type configuration file`_, such as
+ "doxygen" and "gtkdoc".
+
+`Rule`_
+ A rule is a group of settings controlling how a documentation comment is
+ generated. For example, it can define a template, describe how to handle
+ particular imbrications and so on.
+
+
+Syntax
+======
+
+Key-Value pairs
+---------------
+
+The syntax used by the configuration files is an extended key-value tree
+definition based on common concepts (trees, string literals, semicolon-ended
+values, etc.).
+
+The key-value syntax is as follows::
+
+ key = value
+
+where value is either a semicolon-ended single value::
+
+ value;
+
+or a brace-surrounded list of key-value pairs that use the same syntax again::
+
+ {
+ key1 = value1
+ key2 = value2
+ }
+
+Here a little example of the *syntax* (not any actual configuration example)::
+
+ key1 = value1;
+ key2 = {
+ sub-key1 = sub-value1;
+ sub-key2 = {
+ sub-sub-key1 = sub-sub-value1;
+ }
+ }
+
+
+Naming
+------
+
+Key-value pairs are often referred as *group* when they are meant to have
+multiple values and as *setting* when they have a single value.
+
+
+Comments
+--------
+
+Is considered as comment (and therefore ignored) everything between a number
+sign (``#``) and the following end of line, unless the ``#`` occurs as part of
+another syntactic element (such as a string literal).
+
+A short example::
+
+ # This is a comment
+ key = value; # This is also a comment
+ string = "A string. # This isn't a comment but a string";
+
+
+Value types
+-----------
+
+string
+ A string literal. String literals are surrounded by either single (``'``) or
+ double (``"``) quotes.
+
+ Some special characters can be inserted in a string with an escape sequence:
+
+ ``\t``
+ A tabulation.
+ ``\n``
+ A new line.
+ ``\r``
+ A carriage return.
+ ``\\``
+ A backslash.
+ ``\'``
+ A single quote (escaping only needed in single-quotes surrounded strings).
+ ``\"``
+ A double quote (escaping only needed in double-quotes surrounded strings).
+
@@ Diff output truncated at 100000 characters. @@
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 1410
http://geany-plugins.svn.sourceforge.net/geany-plugins/?rev=1410&view=rev
Author: frlan
Date: 2010-05-26 17:43:39 +0000 (Wed, 26 May 2010)
Log Message:
-----------
Minor update of German translation. Still some work missing
Modified Paths:
--------------
trunk/geany-plugins/po/ChangeLog
trunk/geany-plugins/po/de.po
Modified: trunk/geany-plugins/po/ChangeLog
===================================================================
--- trunk/geany-plugins/po/ChangeLog 2010-05-26 14:58:04 UTC (rev 1409)
+++ trunk/geany-plugins/po/ChangeLog 2010-05-26 17:43:39 UTC (rev 1410)
@@ -1,3 +1,8 @@
+2010-05-26 Frank Lanitz <frank(a)frank.uvena.de>
+
+ * de.po: Update of german translation.
+
+
2010-05-23 Frank Lanitz <frank(a)frank.uvena.de>
* *.po, geany-plugins.pot:
Modified: trunk/geany-plugins/po/de.po
===================================================================
--- trunk/geany-plugins/po/de.po 2010-05-26 14:58:04 UTC (rev 1409)
+++ trunk/geany-plugins/po/de.po 2010-05-26 17:43:39 UTC (rev 1410)
@@ -10,17 +10,19 @@
msgstr ""
"Project-Id-Version: geany-plugins 0.19\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2010-05-23 20:24+0200\n"
-"PO-Revision-Date: 2009-12-13 22:20+0100\n"
-"Last-Translator: Dominic Hopf <dmaphy(a)googlemail.com>\n"
+"POT-Creation-Date: 2010-05-24 21:26+0200\n"
+"PO-Revision-Date: 2010-05-26 19:41+0100\n"
+"Last-Translator: Frank Lanitz <frank(a)frank.uvena.de>\n"
"Language-Team: German <geany-i18n(a)uvena.de>\n"
+"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. complete update
-#: ../addons/src/ao_tasks.c:368 ../geanyvc/src/geanyvc.c:2246
+#: ../addons/src/ao_tasks.c:368
+#: ../geanyvc/src/geanyvc.c:2246
msgid "_Update"
msgstr "_Aktualisieren"
@@ -36,7 +38,8 @@
msgid "Line"
msgstr "Zeile"
-#: ../addons/src/ao_tasks.c:429 ../geanylatex/src/bibtexlabels.c:65
+#: ../addons/src/ao_tasks.c:429
+#: ../geanylatex/src/bibtexlabels.c:65
msgid "Type"
msgstr "Typ"
@@ -50,9 +53,8 @@
# Ironischerweise finde ich den Kontext für diesen String nicht --Dominic
#: ../addons/src/ao_tasks.c:536
-#, fuzzy
msgid "Context:"
-msgstr "Konsole:"
+msgstr "Kontext:"
#: ../addons/src/ao_openuri.c:162
msgid "Open URI"
@@ -84,21 +86,21 @@
#: ../addons/src/addons.c:270
msgid "Run XML tagging"
-msgstr ""
+msgstr "XML-Tagging durchführen"
-#: ../addons/src/addons.c:346 ../geanylatex/src/geanylatex.c:202
+#: ../addons/src/addons.c:346
+#: ../geanylatex/src/geanylatex.c:202
#: ../geanysendmail/src/geanysendmail.c:150
-#: ../geanysendmail/src/geanysendmail.c:314 ../geanyvc/src/geanyvc.c:1776
-#: ../spellcheck/src/scplugin.c:134 ../treebrowser/src/treebrowser.c:1435
+#: ../geanysendmail/src/geanysendmail.c:314
+#: ../geanyvc/src/geanyvc.c:1776
+#: ../spellcheck/src/scplugin.c:134
+#: ../treebrowser/src/treebrowser.c:1435
msgid "Plugin configuration directory could not be created."
-msgstr ""
-"Das Konfigurationsverzeichnis für das Plugin konnte nicht erstellt werden."
+msgstr "Das Konfigurationsverzeichnis für das Plugin konnte nicht erstellt werden."
#: ../addons/src/addons.c:371
msgid "Show toolbar item to show a list of currently open documents"
-msgstr ""
-"Symbol in die Werkzeugleiste hinzufügen um eine Liste mit aktuell geöffneten "
-"Dateien zu zeigen."
+msgstr "Symbol in die Werkzeugleiste hinzufügen um eine Liste mit aktuell geöffneten Dateien zu zeigen."
#. TODO fix the string
#: ../addons/src/addons.c:378
@@ -111,13 +113,11 @@
#: ../addons/src/addons.c:390
msgid "Show tasks of all documents"
-msgstr ""
+msgstr "Sämtliche Aufgaben aller Dokumente anzeigen"
#: ../addons/src/addons.c:394
-msgid ""
-"Whether to show the tasks of all open documents in the list or only those of "
-"the current document."
-msgstr ""
+msgid "Whether to show the tasks of all open documents in the list or only those of the current document."
+msgstr "Bestimmt, ob alle Aufgaben der aktuell geöffneten Dokumente angezeigt werden sollen oder nur des derzeit aktiven Dokumentes."
#: ../addons/src/addons.c:401
msgid "Specify a semicolon separated list of search tokens."
@@ -141,11 +141,11 @@
#: ../addons/src/addons.c:438
msgid "Strip trailing blank lines"
-msgstr ""
+msgstr "Leere Zeilen am Ende entfrnen"
#: ../addons/src/addons.c:444
msgid "XML tagging for selection"
-msgstr ""
+msgstr "XML-Tagging für eine Auswahl"
#: ../addons/src/ao_doclist.c:179
msgid "Close Ot_her Documents"
@@ -162,7 +162,7 @@
# what the heck? :D
#: ../addons/src/ao_bookmarklist.c:179
msgid "(Empty Line)"
-msgstr ""
+msgstr "(Leere Zeile)"
#: ../addons/src/ao_bookmarklist.c:301
msgid "_Remove Bookmark"
@@ -176,17 +176,18 @@
msgid "Contents"
msgstr "Inhalt"
-#: ../addons/src/ao_bookmarklist.c:368 ../treebrowser/src/treebrowser.c:390
+#: ../addons/src/ao_bookmarklist.c:368
+#: ../treebrowser/src/treebrowser.c:390
msgid "Bookmarks"
msgstr "Lesezeichen"
#: ../addons/src/ao_xmltagging.c:51
msgid "XML tagging"
-msgstr ""
+msgstr "XML-Tagging"
#: ../addons/src/ao_xmltagging.c:62
msgid "Tag name to be inserted:"
-msgstr ""
+msgstr "Tag zum Einfügen:"
#. All plugins must set name, description, version and author.
#: ../codenav/src/codenavigation.c:46
@@ -200,10 +201,8 @@
"- switching between a .cpp file and the corresponding .h file\n"
"- [opening a file by typing its name -> TODO]"
msgstr ""
-"Dieses Plugin hilft dabei, zwischen verschiedenen Quelltext-Dateien zu "
-"navigieren.\n"
-"Im Moment unterstützt es:- Umschalten zwischen einer .cpp-Datei und der dazu "
-"passenden .H-Datei\n"
+"Dieses Plugin hilft dabei, zwischen verschiedenen Quelltext-Dateien zu navigieren.\n"
+"Im Moment unterstützt es:- Umschalten zwischen einer .cpp-Datei und der dazu passenden .H-Datei\n"
"- [Eine Datei über Ihren Namen öffnen -> TODO]"
#: ../codenav/src/codenavigation.c:50
@@ -211,10 +210,10 @@
msgstr "Lionel Fuentes"
#. Add the menu item, sensitive only when a document is opened
-#: ../codenav/src/goto_file.c:50 ../codenav/src/goto_file.c:64
-#, fuzzy
+#: ../codenav/src/goto_file.c:50
+#: ../codenav/src/goto_file.c:64
msgid "Goto file"
-msgstr "Gehe zu Datei..."
+msgstr "Gehe zu Datei:"
#: ../codenav/src/goto_file.c:63
#, fuzzy
@@ -229,7 +228,8 @@
# Diese Übersetzung existiert drei mal.
#. Add the menu item and make it sensitive only when a document is opened
#. Frame, which is the returned widget
-#: ../codenav/src/switch_head_impl.c:75 ../codenav/src/switch_head_impl.c:89
+#: ../codenav/src/switch_head_impl.c:75
+#: ../codenav/src/switch_head_impl.c:89
#: ../codenav/src/switch_head_impl.c:449
msgid "Switch header/implementation"
msgstr "Umschalten zwischen Deklaration und Implementierung"
@@ -258,7 +258,8 @@
msgstr "Implementierungserweiterungen"
#. All plugins must set name, description, version and author.
-#: ../geanydoc/src/geanydoc.c:50 ../geanydoc/src/geanydoc.c:347
+#: ../geanydoc/src/geanydoc.c:50
+#: ../geanydoc/src/geanydoc.c:347
msgid "Doc"
msgstr "Doc"
@@ -270,7 +271,8 @@
msgid "Yura Siamshka <yurand2(a)gmail.com>"
msgstr "Yura Siamshka <yurand2(a)gmail.com>"
-#: ../geanydoc/src/geanydoc.c:170 ../geanyvc/src/geanyvc.c:399
+#: ../geanydoc/src/geanydoc.c:170
+#: ../geanyvc/src/geanyvc.c:399
msgid "Could not parse the output of command"
msgstr "Kann die Ausgabe des Befehls nicht verarbeiten."
@@ -320,8 +322,7 @@
#: ../geanygdb/src/gdb-io-break.c:178
#, fuzzy, c-format
msgid "Added read/write watchpoint #%s for %s\n"
-msgstr ""
-"Beobachtungspunkt #%s für Lese- und Schreibzugriff auf %s hinzugefügt\n"
+msgstr "Beobachtungspunkt #%s für Lese- und Schreibzugriff auf %s hinzugefügt\n"
# Beobachtungspunkt oder Haltepunkt?
# Watchpoint = Beobachtungspunkt, Breakpoint=Haltepunkt, das war meine Intention --Dominic
@@ -364,17 +365,14 @@
#: ../geanygdb/src/gdb-io-frame.c:500
msgid "Field list too long, not all items can be displayed.\n"
-msgstr ""
-"Die Liste ist zu lang, so dass nicht alle Einträge angezeigt werden können.\n"
+msgstr "Die Liste ist zu lang, so dass nicht alle Einträge angezeigt werden können.\n"
#: ../geanygdb/src/gdb-io-read.c:240
msgid "Error starting target process!\n"
msgstr "Fehler beim Starten des Zielprozess!\n"
#: ../geanygdb/src/gdb-io-read.c:285
-msgid ""
-"This executable does not appear to contain the required debugging "
-"information."
+msgid "This executable does not appear to contain the required debugging information."
msgstr "Die ausführbare Datei scheint keine Debug-Informationen zu enthalten."
# Bitte die Erklärung noch mit hinzufügen: %s's have following meaning (in this order):
@@ -459,7 +457,8 @@
msgid "reason:"
msgstr "Grund:"
-#: ../geanygdb/src/gdb-io-run.c:552 ../geanygdb/src/gdb-io-run.c:617
+#: ../geanygdb/src/gdb-io-run.c:552
+#: ../geanygdb/src/gdb-io-run.c:617
#, c-format
msgid "Directory %s not found!\n"
msgstr "Verzeichnis »%s« nicht gefunden!\n"
@@ -617,11 +616,13 @@
"\n"
"Suchpfad für ausführbare Dateien:"
-#: ../geanygdb/src/gdb-ui-envir.c:162 ../geanylua/gsdlg.c:226
+#: ../geanygdb/src/gdb-ui-envir.c:162
+#: ../geanylua/gsdlg.c:226
msgid "Select Font"
msgstr "Schriftart auswählen"
-#: ../geanygdb/src/gdb-ui-envir.c:184 ../geanyprj/src/menu.c:412
+#: ../geanygdb/src/gdb-ui-envir.c:184
+#: ../geanyprj/src/menu.c:412
#: ../geanyprj/src/sidebar.c:214
msgid "Preferences"
msgstr "Einstellungen"
@@ -667,7 +668,8 @@
msgid "Return to previous dialog."
msgstr "Zum vorherigen Dialog zurückkehren"
-#: ../geanygdb/src/gdb-ui-frame.c:307 ../geanygdb/src/gdb-ui-frame.c:381
+#: ../geanygdb/src/gdb-ui-frame.c:307
+#: ../geanygdb/src/gdb-ui-frame.c:381
msgid "Display additional information about the selected item."
msgstr "Zusätzliche Information zum ausgewählten Eintrag anzeigen"
@@ -700,9 +702,8 @@
msgstr "Zurück zum Stapel."
#: ../geanygdb/src/gdb-ui-frame.c:588
-#, fuzzy
msgid "Stack trace"
-msgstr "Aufrufliste:"
+msgstr "Aufrufliste"
#: ../geanygdb/src/gdb-ui-frame.c:605
#, fuzzy
@@ -801,7 +802,7 @@
#: ../geanygdb/src/gdb-ui-main.c:848
msgid ": "
-msgstr ""
+msgstr ": "
#: ../geanygdb/src/gdb-ui-main.c:915
msgid "no program"
@@ -824,8 +825,7 @@
"Don't pause execution when target gets a SIGPIPE signal.\n"
"(Useful for certain networking applications.)"
msgstr ""
-"Die Ausführung des Programms nicht unterbrechen wenn das Signal SIGPIPE "
-"empfangen wird.\n"
+"Die Ausführung des Programms nicht unterbrechen wenn das Signal SIGPIPE empfangen wird.\n"
"(Nützlich bei einigen Netzwerkanwendungen)"
#: ../geanygdb/src/gdb-ui-main.c:984
@@ -878,12 +878,11 @@
#: ../geanygendoc/src/ggd.c:79
#, c-format
msgid "Failed to resize memory output stream"
-msgstr ""
+msgstr "Größe des Speicherausgabestroms konnte nicht geändert werden"
#: ../geanygendoc/src/ggd.c:107
#, c-format
-msgid ""
-"Argument parsing regular expression did not match (argument list was: \"%s\")"
+msgid "Argument parsing regular expression did not match (argument list was: \"%s\")"
msgstr ""
#: ../geanygendoc/src/ggd.c:241
@@ -913,7 +912,7 @@
#: ../geanygendoc/src/ggd-file-type-loader.c:112
msgid "boolean value"
-msgstr ""
+msgstr "Boolescher Wert"
#: ../geanygendoc/src/ggd-file-type-loader.c:125
#, c-format
@@ -953,7 +952,6 @@
msgstr ""
#: ../geanygendoc/src/ggd-file-type-loader.c:254
-#, fuzzy
msgid "type"
msgstr "Typ"
@@ -1038,22 +1036,22 @@
#: ../geanygendoc/src/ggd-file-type-loader.c:897
#, c-format
msgid "input is empty"
-msgstr ""
+msgstr "Die Eingabe ist leer"
#: ../geanygendoc/src/ggd-file-type-loader.c:859
#, c-format
msgid "Parser warning: %s:%u:%u: %s"
-msgstr ""
+msgstr "Warnung bei der Auswrtung: %s:%u:%u: %s"
#: ../geanygendoc/src/ggd-file-type-loader.c:862
#, c-format
msgid "Parser error: %s:%u:%u: %s"
-msgstr ""
+msgstr "Fehler bei der Auswertung: %s:%u:%u: %s"
#: ../geanygendoc/src/ggd-file-type-loader.c:866
#, c-format
msgid "%s:%u:%u: %s"
-msgstr ""
+msgstr "%s:%u:%u: %s"
#: ../geanygendoc/src/ggd-file-type-manager.c:175
#, c-format
@@ -1071,9 +1069,7 @@
msgstr "Unbekanntes Signal"
#: ../geanygendoc/src/ggd-options.c:335
-msgid ""
-"Invalid option or proxy: either the proxy's property or the option type is "
-"incompatible."
+msgid "Invalid option or proxy: either the proxy's property or the option type is incompatible."
msgstr ""
#: ../geanygendoc/src/ggd-options.c:512
@@ -1095,155 +1091,142 @@
msgid "Generates documentation basis from source code"
msgstr ""
-#: ../geanygendoc/src/ggd-plugin.c:207
+#: ../geanygendoc/src/ggd-plugin.c:213
#, fuzzy, c-format
msgid "Failed to load configuration: %s"
msgstr "Skriptkonfiguration"
-#: ../geanygendoc/src/ggd-plugin.c:228
+#: ../geanygendoc/src/ggd-plugin.c:234
#, fuzzy, c-format
msgid "Failed to save configuration: %s"
msgstr "Skriptkonfiguration"
-#: ../geanygendoc/src/ggd-plugin.c:299
+#: ../geanygendoc/src/ggd-plugin.c:305
#, c-format
msgid "Failed to find configuration file for file type \"%s\": %s"
msgstr ""
-#: ../geanygendoc/src/ggd-plugin.c:360 ../geanygendoc/src/ggd-plugin.c:371
+#: ../geanygendoc/src/ggd-plugin.c:366
+#: ../geanygendoc/src/ggd-plugin.c:377
#, fuzzy
msgid "Insert Documentation Comment"
msgstr "Umgebung einfügen"
-#: ../geanygendoc/src/ggd-plugin.c:425
+#: ../geanygendoc/src/ggd-plugin.c:431
#, fuzzy
msgid "_Document Current Symbol"
msgstr "Dokumentation für aktuelles Wort öffnen"
-#: ../geanygendoc/src/ggd-plugin.c:426
+#: ../geanygendoc/src/ggd-plugin.c:432
#, fuzzy
msgid "Generate documentation for the current symbol"
msgstr "Dokumentation für das aktuelle Wort anzeigen."
-#: ../geanygendoc/src/ggd-plugin.c:432
+#: ../geanygendoc/src/ggd-plugin.c:438
msgid "Document _All Symbols"
msgstr ""
-#: ../geanygendoc/src/ggd-plugin.c:433
+#: ../geanygendoc/src/ggd-plugin.c:439
msgid "Generate documentation for all symbols in the current document"
msgstr ""
-#: ../geanygendoc/src/ggd-plugin.c:443
+#: ../geanygendoc/src/ggd-plugin.c:449
msgid "_Reload Configuration Files"
-msgstr ""
+msgstr "_Konfigurationsdateien neu laden"
-#: ../geanygendoc/src/ggd-plugin.c:444
+#: ../geanygendoc/src/ggd-plugin.c:450
#, fuzzy
msgid "Force reloading of the configuration files"
msgstr "Zeigt die Versionshistorie der aktuellen Datei an."
-#: ../geanygendoc/src/ggd-plugin.c:449
+#: ../geanygendoc/src/ggd-plugin.c:455
msgid "_Edit Current Language Configuration"
msgstr ""
-#: ../geanygendoc/src/ggd-plugin.c:450
+#: ../geanygendoc/src/ggd-plugin.c:456
msgid "Open the current language configuration file for editing"
msgstr ""
-#: ../geanygendoc/src/ggd-plugin.c:460
-#, fuzzy
+#: ../geanygendoc/src/ggd-plugin.c:466
msgid "Open _Manual"
-msgstr "Handbuch"
+msgstr "_Anleitung öffnen"
-#: ../geanygendoc/src/ggd-plugin.c:461
+#: ../geanygendoc/src/ggd-plugin.c:467
msgid "Open the manual in a browser"
-msgstr ""
+msgstr "Anleitung im Browser öfnen"
#. build tools menu item
-#: ../geanygendoc/src/ggd-plugin.c:465
+#: ../geanygendoc/src/ggd-plugin.c:471
#, fuzzy
msgid "_Documentation Generator"
msgstr "Nach Dokumentationswerkzeug für aktuelles Wort fragen"
#. General
-#: ../geanygendoc/src/ggd-plugin.c:562
-#, fuzzy
+#: ../geanygendoc/src/ggd-plugin.c:568
msgid "General"
-msgstr "GeanySendMail"
+msgstr "Allgemein"
#. auto-save
-#: ../geanygendoc/src/ggd-plugin.c:567
+#: ../geanygendoc/src/ggd-plugin.c:573
msgid "_Save file before generating documentation"
msgstr ""
-#: ../geanygendoc/src/ggd-plugin.c:570
-msgid ""
-"Whether the current document should be saved to disc before generating the "
-"documentation. This is a technical detail, but it is currently needed to "
-"have an up-to-date tag list. If you disable this option and ask for "
-"documentation generation on a modified document, the behavior may be "
-"surprising since the comment will be generated for the last saved state of "
-"this document and not the current one."
+#: ../geanygendoc/src/ggd-plugin.c:576
+msgid "Whether the current document should be saved to disc before generating the documentation. This is a technical detail, but it is currently needed to have an up-to-date tag list. If you disable this option and ask for documentation generation on a modified document, the behavior may be surprising since the comment will be generated for the last saved state of this document and not the current one."
msgstr ""
#. indent
-#: ../geanygendoc/src/ggd-plugin.c:580
+#: ../geanygendoc/src/ggd-plugin.c:586
msgid "_Indent inserted documentation"
msgstr ""
-#: ../geanygendoc/src/ggd-plugin.c:582
-msgid ""
-"Whether the inserted documentation should be indented to fit the indentation "
-"at the insertion position."
+#: ../geanygendoc/src/ggd-plugin.c:588
+msgid "Whether the inserted documentation should be indented to fit the indentation at the insertion position."
msgstr ""
#. Documentation type
-#: ../geanygendoc/src/ggd-plugin.c:589
+#: ../geanygendoc/src/ggd-plugin.c:595
#: ../geanygendoc/src/ggd-widget-doctype-selector.c:121
#, fuzzy
msgid "Documentation type"
msgstr "Nach Dokumentationswerkzeug für aktuelles Wort fragen"
-#: ../geanygendoc/src/ggd-plugin.c:599
-msgid ""
-"Choose the documentation type to use with each file type. The special "
-"language \"All\" on top of the list is used to choose the default "
-"documentation type, used for all languages that haven't one set."
+#: ../geanygendoc/src/ggd-plugin.c:605
+msgid "Choose the documentation type to use with each file type. The special language \"All\" on top of the list is used to choose the default documentation type, used for all languages that haven't one set."
msgstr ""
#. Environ editor
-#: ../geanygendoc/src/ggd-plugin.c:605
+#: ../geanygendoc/src/ggd-plugin.c:611
#, fuzzy
msgid "Global environment"
msgstr "Umgebungen"
-#: ../geanygendoc/src/ggd-plugin.c:607
-msgid ""
-"Global environment overrides and additions. This environment will be merged "
-"with the file-type-specific ones."
+#: ../geanygendoc/src/ggd-plugin.c:613
+msgid "Global environment overrides and additions. This environment will be merged with the file-type-specific ones."
msgstr ""
#: ../geanygendoc/src/ggd-tag-utils.c:389
msgid "Invalid tag"
-msgstr ""
+msgstr "Ungültige Markierung"
-#: ../geanygendoc/src/ggd-utils.c:166 ../geanygendoc/src/ggd-utils.c:177
+#: ../geanygendoc/src/ggd-utils.c:163
+#: ../geanygendoc/src/ggd-utils.c:174
#, c-format
msgid "File \"%s\" exists but is not a regular file"
msgstr ""
-#: ../geanygendoc/src/ggd-utils.c:186
+#: ../geanygendoc/src/ggd-utils.c:183
#, c-format
msgid "%s: no such file or directory"
-msgstr ""
+msgstr "Die Datei oder das Verzeichnis »%s« gibt es nicht."
#: ../geanygendoc/src/ggd-widget-doctype-selector.c:112
msgid "Language"
-msgstr ""
+msgstr "Sprache"
#: ../geanygendoc/src/ggd-widget-doctype-selector.c:143
msgid "All"
-msgstr ""
+msgstr "Alle"
#: ../geanygendoc/src/ggd-widget-doctype-selector.c:144
msgid "Default documentation type for languages that does not have one set"
@@ -1289,11 +1272,13 @@
msgid "Could not determine where to insert package: %s"
msgstr ""
-#: ../geanylatex/src/bibtexlabels.c:26 ../geanylatex/src/geanylatex.c:1638
+#: ../geanylatex/src/bibtexlabels.c:26
+#: ../geanylatex/src/geanylatex.c:1638
msgid "Article"
msgstr "Artikel"
-#: ../geanylatex/src/bibtexlabels.c:27 ../geanylatex/src/geanylatex.c:1636
+#: ../geanylatex/src/bibtexlabels.c:27
+#: ../geanylatex/src/geanylatex.c:1636
msgid "Book"
msgstr "Buch"
@@ -1327,7 +1312,8 @@
msgid "Mastersthesis"
msgstr "Masterarbeit"
-#: ../geanylatex/src/bibtexlabels.c:35 ../geanylatex/src/letters.c:41
+#: ../geanylatex/src/bibtexlabels.c:35
+#: ../geanylatex/src/letters.c:41
msgid "Misc"
msgstr "Sonstiges"
@@ -1458,9 +1444,7 @@
#: ../geanylatex/src/bibtexlabels.c:102
msgid "Name(s) of the author(s), separated by 'and' if more than one"
-msgstr ""
-"Name(n) der Autoren, getrennt mit einem »and« sollten mehrere Autoren am Werk "
-"mitgearbeitet werden."
+msgstr "Name(n) der Autoren, getrennt mit einem »and« sollten mehrere Autoren am Werk mitgearbeitet werden."
#: ../geanylatex/src/bibtexlabels.c:103
msgid "Title of the book, if only part of it is being cited"
@@ -1501,17 +1485,12 @@
msgstr "Journal oder Magazin, in dem die Arbeit veröffentlicht wurde"
#: ../geanylatex/src/bibtexlabels.c:112
-msgid ""
-"Hidden field used for specifying or overriding the alphabetical order of "
-"entries"
-msgstr ""
-"Verstecktes Feld, welches zur Festlegung oder zum Überschreiben der "
-"alphabetischen Reihenfolge von Einträgen benutzt wird"
+msgid "Hidden field used for specifying or overriding the alphabetical order of entries"
+msgstr "Verstecktes Feld, welches zur Festlegung oder zum Überschreiben der alphabetischen Reihenfolge von Einträgen benutzt wird"
#: ../geanylatex/src/bibtexlabels.c:113
msgid "Month of publication or creation if unpublished"
-msgstr ""
-"Monat der Publikation bzw. der Erstellung bei unveröffentlichten Werken"
+msgstr "Monat der Publikation bzw. der Erstellung bei unveröffentlichten Werken"
#: ../geanylatex/src/bibtexlabels.c:114
msgid "Miscellaneous extra information"
@@ -1559,21 +1538,17 @@
#: ../geanylatex/src/bibtexlabels.c:125
msgid "Year of publication or creation if unpublished"
-msgstr ""
-"Jahr der Publikation oder der Erstellung, wenn das Werk noch nicht "
-"veröffentlicht ist."
+msgstr "Jahr der Publikation oder der Erstellung, wenn das Werk noch nicht veröffentlicht ist."
#: ../geanylatex/src/geanylatex.c:33
-#, fuzzy
msgid "GeanyLaTeX"
-msgstr "LaTeX"
+msgstr "GeanyLaTeX"
#: ../geanylatex/src/geanylatex.c:33
msgid "Plugin to provide better LaTeX support"
msgstr "GeanyLaTeX bietet LaTeX-Support für Geany"
#: ../geanylatex/src/geanylatex.c:98
-#, fuzzy
msgid "Runs LaTeX wizard"
msgstr "LaTeX-Assistent starten"
@@ -1589,15 +1564,18 @@
msgid "Underlines selected text"
msgstr "Auswahl unterstreichen"
-#: ../geanylatex/src/geanylatex.c:102 ../geanylatex/src/formatpatterns.c:45
+#: ../geanylatex/src/geanylatex.c:102
+#: ../geanylatex/src/formatpatterns.c:45
msgid "Centered"
msgstr "Zentriert"
-#: ../geanylatex/src/geanylatex.c:103 ../geanylatex/src/formatpatterns.c:46
+#: ../geanylatex/src/geanylatex.c:103
+#: ../geanylatex/src/formatpatterns.c:46
msgid "Left side oriented"
msgstr "Linksbündig"
-#: ../geanylatex/src/geanylatex.c:104 ../geanylatex/src/formatpatterns.c:47
+#: ../geanylatex/src/geanylatex.c:104
+#: ../geanylatex/src/formatpatterns.c:47
msgid "Right side oriented"
msgstr "Rechtsbündig"
@@ -1611,15 +1589,15 @@
#: ../geanylatex/src/geanylatex.c:253
msgid "Don't care about this inside plugin"
-msgstr ""
+msgstr "Führe keine Autovervollständigung durch"
#: ../geanylatex/src/geanylatex.c:255
msgid "Always perform autocompletion on LaTeX"
-msgstr ""
+msgstr "Autovervollständigung in LaTeX durchführen"
#: ../geanylatex/src/geanylatex.c:267
msgid "Modus of autocompletion"
-msgstr ""
+msgstr "Typ der Autovervollständigung"
#: ../geanylatex/src/geanylatex.c:726
msgid "Insert Label"
@@ -1666,7 +1644,7 @@
#: ../geanylatex/src/geanylatex.c:1149
msgid "Add additional package"
-msgstr ""
+msgstr "Paket inzufügen"
#: ../geanylatex/src/geanylatex.c:1162
#, fuzzy
@@ -1675,7 +1653,7 @@
#: ../geanylatex/src/geanylatex.c:1165
msgid "Package options:"
-msgstr ""
+msgstr "Paket Optionen:"
#: ../geanylatex/src/geanylatex.c:1556
msgid "Dear Sir or Madame"
@@ -1687,7 +1665,7 @@
#: ../geanylatex/src/geanylatex.c:1565
msgid "No template assigned. Aborting"
-msgstr ""
+msgstr "Keine Vorlage zugewiesen. Abbruch."
#. Building the wizard-dialog and showing it
#: ../geanylatex/src/geanylatex.c:1592
@@ -1699,16 +1677,15 @@
#. * adds default one
#: ../geanylatex/src/geanylatex.c:1607
msgid "Template:"
-msgstr ""
+msgstr "Vorlage:"
#: ../geanylatex/src/geanylatex.c:1611
msgid "Set the template which should be used for creating the new document"
-msgstr ""
+msgstr "Bestimmt, welche Vorlage zum Erstellen des neuen Dokumentes genutzt werden soll."
#: ../geanylatex/src/geanylatex.c:1620
-#, fuzzy
msgid "Default"
-msgstr "Vorgabe (%s)"
+msgstr "Vorgabe"
#. Documentclass
#: ../geanylatex/src/geanylatex.c:1631
@@ -1755,11 +1732,8 @@
msgstr "Autor:"
#: ../geanylatex/src/geanylatex.c:1695
-msgid ""
-"Sets the value of the \\author command. In most cases this should be your "
-"name"
-msgstr ""
-"Setzt den Eintrag für den \\author Befehl. Meist sollte hier Ihr Name stehen."
+msgid "Sets the value of the \\author command. In most cases this should be your name"
+msgstr "Setzt den Eintrag für den \\author Befehl. Meist sollte hier Ihr Name stehen."
#. Date
#: ../geanylatex/src/geanylatex.c:1709
@@ -1768,13 +1742,8 @@
#: ../geanylatex/src/geanylatex.c:1712
#, fuzzy
-msgid ""
-"Sets the value of the \\date command inside header of your new created LaTeX-"
-"document. Keeping it at \\today is a good decision if you don't need any "
-"fixed date."
-msgstr ""
-"Setzt den Eintrag für den \\date Befehl im Kopf des neuen Dokumentes. In den "
-"meisten Fällen sollte \\today eine gute Wahl sein."
+msgid "Sets the value of the \\date command inside header of your new created LaTeX-document. Keeping it at \\today is a good decision if you don't need any fixed date."
+msgstr "Setzt den Eintrag für den \\date Befehl im Kopf des neuen Dokumentes. In den meisten Fällen sollte \\today eine gute Wahl sein."
#. Title of the new document
#: ../geanylatex/src/geanylatex.c:1724
@@ -1792,22 +1761,17 @@
#: ../geanylatex/src/geanylatex.c:1739
msgid "Choose the paper format for the newly created document"
-msgstr ""
-"Setzt das Papierformat als Argument der Dokumentenklasse für das neue "
-"Dokument"
+msgstr "Setzt das Papierformat als Argument der Dokumentenklasse für das neue Dokument"
#. Paper direction
#: ../geanylatex/src/geanylatex.c:1752
-#, fuzzy
msgid "Paper Orientation:"
-msgstr "Präsentation"
+msgstr "Seitenausrichtung:"
#: ../geanylatex/src/geanylatex.c:1755
#, fuzzy
msgid "Choose the paper orientation for the newly created document"
-msgstr ""
-"Setzt das Papierformat als Argument der Dokumentenklasse für das neue "
-"Dokument"
+msgstr "Setzt das Papierformat als Argument der Dokumentenklasse für das neue Dokument"
#: ../geanylatex/src/geanylatex.c:1776
msgid "Use KOMA-script classes if possible"
@@ -1817,23 +1781,16 @@
#, fuzzy
msgid ""
"Uses the KOMA-script classes by Markus Kohm.\n"
-"Keep in mind: To compile your document these classes have to be installed "
-"before."
-msgstr ""
-"Wenn diese Option aktiviert ist, werden die KOMA-Skript-Klassen von Markus "
-"Kohm genutzt. Sie müssen natürlich dafür installiert sein."
+"Keep in mind: To compile your document these classes have to be installed before."
+msgstr "Wenn diese Option aktiviert ist, werden die KOMA-Skript-Klassen von Markus Kohm genutzt. Sie müssen natürlich dafür installiert sein."
#: ../geanylatex/src/geanylatex.c:1785
msgid "Use draft mode"
msgstr "Entwurfsmodus benutzen"
#: ../geanylatex/src/geanylatex.c:1787
-msgid ""
-"Set the draft flag inside new created documents to get documents with a "
-"number of debugging helpers"
-msgstr ""
-"Setzt die Option draft für die Dokumentenklasse um das neue Dokument mit "
-"einer Nummer von kleinen Korrekturhinweisen zu versehen."
+msgid "Set the draft flag inside new created documents to get documents with a number of debugging helpers"
+msgstr "Setzt die Option draft für die Dokumentenklasse um das neue Dokument mit einer Nummer von kleinen Korrekturhinweisen zu versehen."
#: ../geanylatex/src/geanylatex.c:1801
msgid "Run LaTeX-Wizard"
@@ -1852,9 +1809,8 @@
msgstr "Zeilenumbruch einfügen (\\\\)"
#: ../geanylatex/src/geanylatex.c:1810
-#, fuzzy
msgid "Insert command"
-msgstr "Umgebung einfügen"
+msgstr "Kommando eingeben"
#: ../geanylatex/src/geanylatex.c:1812
msgid "Turn input replacement on/off"
@@ -1893,13 +1849,12 @@
msgstr "Auswahl linksbündig formatieren"
#: ../geanylatex/src/geanylatex.c:1833
-#, fuzzy
msgid "Format selection right-aligned"
msgstr "Auswahl rechtsbündig formatieren"
#: ../geanylatex/src/geanylatex.c:1836
msgid "Insert description list"
-msgstr ""
+msgstr "Description-Umgebung einfügen"
#: ../geanylatex/src/geanylatex.c:1839
#, fuzzy
@@ -1936,18 +1891,18 @@
"Alle Fehler bitte an einen der Entwickler weitermelden."
#: ../geanylatex/src/geanylatex.c:1894
-msgid ""
-"glatex_set_autocompletion_contextsize has been initialized with an invalid "
-"value. Default value taken. Please check your configuration file"
+msgid "glatex_set_autocompletion_contextsize has been initialized with an invalid value. Default value taken. Please check your configuration file"
msgstr ""
-#: ../geanylatex/src/geanylatex.c:1906 ../geanylatex/src/geanylatex.c:1913
+#: ../geanylatex/src/geanylatex.c:1906
+#: ../geanylatex/src/geanylatex.c:1913
msgid "page \\pageref{{{reference}}}"
-msgstr ""
+msgstr "Seite \\pageref{{{reference}}}"
-#: ../geanylatex/src/geanylatex.c:1910 ../geanylatex/src/geanylatex.c:1917
+#: ../geanylatex/src/geanylatex.c:1910
+#: ../geanylatex/src/geanylatex.c:1917
msgid "\\ref{{{reference}}}, page \\pageref{{{reference}}}"
-msgstr ""
+msgstr "\\ref{{{reference}}}, Seite \\pageref{{{reference}}}"
#: ../geanylatex/src/geanylatex.c:1934
msgid "_LaTeX"
@@ -1962,7 +1917,6 @@
msgstr "Öffnet einen Assistenten, um einfache LaTeX-Dokumente zu erstellen."
#: ../geanylatex/src/geanylatex.c:1948
-#, fuzzy
msgid "I_nsert Special Character"
msgstr "_Sonderzeichen einfügen"
@@ -2001,7 +1955,7 @@
#: ../geanylatex/src/geanylatex.c:1985
msgid "A small dialog to insert \\usepackage{} into header of current file"
-msgstr ""
+msgstr "Eine kleine Hilfe, um \\usepackage{} in den Kopf des Dokumentes ein zufügen. "
#: ../geanylatex/src/geanylatex.c:1990
msgid "_BibTeX"
@@ -2013,9 +1967,8 @@
#. Add font size menu
#: ../geanylatex/src/geanylatex.c:2023
-#, fuzzy
msgid "F_ont size"
-msgstr "Schriftgröße:"
+msgstr "Sc_hriftgröße:"
#: ../geanylatex/src/geanylatex.c:2041
msgid "_Special Character Replacement"
@@ -2094,11 +2047,11 @@
#: ../geanylatex/src/formatpatterns.c:64
msgid "tiny"
-msgstr ""
+msgstr "tiny"
#: ../geanylatex/src/formatpatterns.c:65
msgid "scriptsize"
-msgstr ""
+msgstr "scriptsize"
#: ../geanylatex/src/formatpatterns.c:66
#, fuzzy
@@ -2107,33 +2060,31 @@
#: ../geanylatex/src/formatpatterns.c:67
msgid "small"
-msgstr ""
+msgstr "small"
#: ../geanylatex/src/formatpatterns.c:68
msgid "normalsize"
-msgstr ""
+msgstr "normalsize"
#: ../geanylatex/src/formatpatterns.c:69
-#, fuzzy
msgid "large"
-msgstr "Seiten"
+msgstr "large"
#: ../geanylatex/src/formatpatterns.c:70
-#, fuzzy
msgid "Large"
-msgstr "LaTeX"
+msgstr "Large"
#: ../geanylatex/src/formatpatterns.c:71
msgid "LARGE"
-msgstr ""
+msgstr "LARGE"
#: ../geanylatex/src/formatpatterns.c:72
msgid "huge"
-msgstr ""
+msgstr "huge"
#: ../geanylatex/src/formatpatterns.c:73
msgid "Huge"
-msgstr ""
+msgstr "Huge"
#: ../geanylatex/src/latexencodings.c:37
msgid "UTF-8"
@@ -2181,12 +2132,11 @@
#: ../geanylatex/src/latexencodings.c:57
msgid "Don't set any encoding"
-msgstr ""
+msgstr "Keine Zeichenkodierung explizit festlegen"
#: ../geanylipsum/src/geanylipsum.c:35
-#, fuzzy
msgid "GeanyLipsum"
-msgstr "Lipsum"
+msgstr "GeanyLipsum"
#: ../geanylipsum/src/geanylipsum.c:35
msgid "Creating dummy text with Geany"
@@ -2218,12 +2168,8 @@
msgstr "GeanySendMail"
#: ../geanysendmail/src/geanysendmail.c:40
-msgid ""
-"A little plugin to send the current file as attachment by user's favorite "
-"mailer"
-msgstr ""
-"Ein Plugin zum Senden einer Datei als Anhang unter Verwendung eines E-Mail-"
-"Programms."
+msgid "A little plugin to send the current file as attachment by user's favorite mailer"
+msgstr "Ein Plugin zum Senden einer Datei als Anhang unter Verwendung eines E-Mail-Programms."
#: ../geanysendmail/src/geanysendmail.c:105
msgid "Recipient's Address"
@@ -2235,23 +2181,15 @@
#: ../geanysendmail/src/geanysendmail.c:165
msgid "Filename placeholder not found. The executed command might have failed."
-msgstr ""
-"Konnte den Platzhalter für den Dateinamen (\\%s) nicht finden. Das "
-"angegebene Kommando könnte nicht korrekt ausgeführt worden sein."
+msgstr "Konnte den Platzhalter für den Dateinamen (\\%s) nicht finden. Das angegebene Kommando könnte nicht korrekt ausgeführt worden sein."
#: ../geanysendmail/src/geanysendmail.c:171
-msgid ""
-"Recipient address placeholder not found. The executed command might have "
-"failed."
-msgstr ""
-"Konnte den Platzhalter für den E-Mail-Empfänger nicht finden. Das angegebene "
-"Kommando könnte nicht korrekt ausgeführt worden sein."
+msgid "Recipient address placeholder not found. The executed command might have failed."
+msgstr "Konnte den Platzhalter für den E-Mail-Empfänger nicht finden. Das angegebene Kommando könnte nicht korrekt ausgeführt worden sein."
#: ../geanysendmail/src/geanysendmail.c:183
msgid "Could not execute mailer. Please check your configuration."
-msgstr ""
-"Konnte das E-Mail-Programm nicht aufrufen. Bitte überprüfen Sie Ihre "
-"Einstellungen"
+msgstr "Konnte das E-Mail-Programm nicht aufrufen. Bitte überprüfen Sie Ihre Einstellungen"
#: ../geanysendmail/src/geanysendmail.c:198
msgid "Please define a mail client first."
@@ -2298,15 +2236,11 @@
#: ../geanysendmail/src/geanysendmail.c:355
msgid "Shows a icon in the toolbar to send file more easy."
-msgstr ""
-"Zeigt ein Symbol in der Werkzeugleiste an, sodass eine Datei einfacher "
-"versendet werden kann."
+msgstr "Zeigt ein Symbol in der Werkzeugleiste an, sodass eine Datei einfacher versendet werden kann."
#: ../geanysendmail/src/geanysendmail.c:361
msgid "Using dialog for entering email address of recipients"
-msgstr ""
-"Zeigt einen Dialog zum Eingeben der E-Mail-Adresse des Empfängers der zu "
-"sendenden Datei"
+msgstr "Zeigt einen Dialog zum Eingeben der E-Mail-Adresse des Empfängers der zu sendenden Datei"
#: ../geanysendmail/src/geanysendmail.c:386
msgid "Send file by mail"
@@ -2318,16 +2252,12 @@
msgstr "_Dokument versenden"
#: ../geanysendmail/src/geanysendmail.c:416
-msgid ""
-"Sends the opened file as unzipped attachment by any mailer from your $PATH"
-msgstr ""
-"Sendet ein geöffnetes Dokument als ungepackten Anhang unter Verwendung eines "
-"E-Mail-Programms."
+msgid "Sends the opened file as unzipped attachment by any mailer from your $PATH"
+msgstr "Sendet ein geöffnetes Dokument als ungepackten Anhang unter Verwendung eines E-Mail-Programms."
#: ../geanyvc/src/geanyvc.c:49
-#, fuzzy
msgid "GeanyVC"
-msgstr "GeanyGDB"
+msgstr "GeanyVC"
#: ../geanyvc/src/geanyvc.c:49
msgid "Interface to different Version Control systems."
@@ -2337,20 +2267,21 @@
msgid ""
"Yura Siamashka <yurand2(a)gmail.com>,\n"
"Frank Lanitz <frank(a)frank.uvena.de>"
-msgstr ""
-"Yura Siamashka <yurand2(a)gmail.com>, Frank Lanitz <frank(a)frank.uvena.de>"
+msgstr "Yura Siamashka <yurand2(a)gmail.com>, Frank Lanitz <frank(a)frank.uvena.de>"
#: ../geanyvc/src/geanyvc.c:458
#, c-format
msgid "geanyvc: s_spawn_sync error: %s"
msgstr "geanyvc: s_spawn_sync error: %s"
-#: ../geanyvc/src/geanyvc.c:592 ../geanyvc/src/geanyvc.c:603
+#: ../geanyvc/src/geanyvc.c:592
+#: ../geanyvc/src/geanyvc.c:603
#, c-format
msgid "geanyvc: vcdiff_file_activated: Unable to rename '%s' to '%s'"
msgstr "geanyvc: vcdiff_file_activated: Kann »%s« nicht in »%s« umbenennen."
-#: ../geanyvc/src/geanyvc.c:629 ../geanyvc/src/geanyvc.c:679
+#: ../geanyvc/src/geanyvc.c:629
+#: ../geanyvc/src/geanyvc.c:679
msgid "No changes were made."
msgstr "Es wurden keine Änderungen vorgenommen."
@@ -2358,7 +2289,8 @@
msgid "No history avaible"
msgstr "Keine Historie verfügbar"
-#: ../geanyvc/src/geanyvc.c:898 ../geanyvc/src/geanyvc.c:906
+#: ../geanyvc/src/geanyvc.c:898
+#: ../geanyvc/src/geanyvc.c:906
#, c-format
msgid "Do you really want to revert: %s?"
msgstr "Möchten Sie wirklich »%s« zurücksetzen?"
@@ -2402,7 +2334,8 @@
msgstr "<b>Commitnachricht:</b>"
#. Commit all changes
-#: ../geanyvc/src/geanyvc.c:1408 ../geanyvc/src/geanyvc.c:2253
+#: ../geanyvc/src/geanyvc.c:1408
+#: ../geanyvc/src/geanyvc.c:2253
msgid "_Commit"
msgstr "Über_tragen"
@@ -2417,27 +2350,16 @@
#: ../geanyvc/src/geanyvc.c:1540
#, c-format
-msgid ""
-"Error while setting up language for spellchecking. Please check "
-"configuration. Error message was: %s"
-msgstr ""
-"Fehler beim Auswählen der Sprache für die Rechtschreibprüfung. Bitte "
-"überprüfen Sie Ihre Konfiguration. Fehlermeldung: %s"
+msgid "Error while setting up language for spellchecking. Please check configuration. Error message was: %s"
+msgstr "Fehler beim Auswählen der Sprache für die Rechtschreibprüfung. Bitte überprüfen Sie Ihre Konfiguration. Fehlermeldung: %s"
#: ../geanyvc/src/geanyvc.c:1812
msgid "Set Changed-flag for document tabs created by the plugin"
msgstr "Markiere vom Plugin erstellte Dokumente als geändert"
#: ../geanyvc/src/geanyvc.c:1815
-msgid ""
-"If this option is activated, every new by the VC-plugin created document tab "
-"will be marked as changed. Even this option is useful in some cases, it "
-"could cause a big number of annoying \"Do you want to save\"-dialogs."
-msgstr ""
-"Wenn diese Option aktiviert ist, werden alle Dokumente die durch das Plugin "
-"erzeugt werden als geändert markiert, sodass z.B. beim Schließen der Datei "
-"der Speichern Dialog geöffnet wird. Auch wenn diese Option von Zeit zu Zeit "
-"sehr nützlich sein kann, kann Sie ab und an einfach nur stören."
+msgid "If this option is activated, every new by the VC-plugin created document tab will be marked as changed. Even this option is useful in some cases, it could cause a big number of annoying \"Do you want to save\"-dialogs."
+msgstr "Wenn diese Option aktiviert ist, werden alle Dokumente die durch das Plugin erzeugt werden als geändert markiert, sodass z.B. beim Schließen der Datei der Speichern Dialog geöffnet wird. Auch wenn diese Option von Zeit zu Zeit sehr nützlich sein kann, kann Sie ab und an einfach nur stören."
#: ../geanyvc/src/geanyvc.c:1823
msgid "Confirm adding new files to a VCS"
@@ -2445,9 +2367,7 @@
#: ../geanyvc/src/geanyvc.c:1826
msgid "Shows a confirmation dialog on adding a new (created) file to VCS."
-msgstr ""
-"Zeigt einen Bestätigungsdialog wenn Dateien zu einem "
-"Versionsverwaltungssystem hinzugefügt werden sollen."
+msgstr "Zeigt einen Bestätigungsdialog wenn Dateien zu einem Versionsverwaltungssystem hinzugefügt werden sollen."
#: ../geanyvc/src/geanyvc.c:1832
msgid "Maximize commit dialog"
@@ -2512,7 +2432,8 @@
#. Diff of current file
#. Diff of the current dir
#. Complete diff of base directory
-#: ../geanyvc/src/geanyvc.c:1980 ../geanyvc/src/geanyvc.c:2057
+#: ../geanyvc/src/geanyvc.c:1980
+#: ../geanyvc/src/geanyvc.c:2057
#: ../geanyvc/src/geanyvc.c:2097
msgid "_Diff"
msgstr "_Unterschiede anzeigen"
@@ -2524,16 +2445,15 @@
#. Revert current file
#. Revert current dir
#. Revert everything
-#: ../geanyvc/src/geanyvc.c:1988 ../geanyvc/src/geanyvc.c:2066
+#: ../geanyvc/src/geanyvc.c:1988
+#: ../geanyvc/src/geanyvc.c:2066
#: ../geanyvc/src/geanyvc.c:2105
msgid "_Revert"
msgstr "_Zurücksetzen"
#: ../geanyvc/src/geanyvc.c:1991
msgid "Restore pristine working copy file (undo local edits)."
-msgstr ""
-"Stellt den ursprünglichen Zustand der Datei wieder her (verwirft lokale "
-"Änderungen)."
+msgstr "Stellt den ursprünglichen Zustand der Datei wieder her (verwirft lokale Änderungen)."
#. Blame for current file
#: ../geanyvc/src/geanyvc.c:2000
@@ -2547,7 +2467,8 @@
#. History/log of current file
#. History/log of the current dir
#. Complete History/Log of base directory
-#: ../geanyvc/src/geanyvc.c:2010 ../geanyvc/src/geanyvc.c:2076
+#: ../geanyvc/src/geanyvc.c:2010
+#: ../geanyvc/src/geanyvc.c:2076
#: ../geanyvc/src/geanyvc.c:2117
msgid "_History (log)"
msgstr "_Versionsgeschichte (log)"
@@ -2593,9 +2514,7 @@
#: ../geanyvc/src/geanyvc.c:2069
msgid "Restore original files in the current folder (undo local edits)."
-msgstr ""
-"Stellt den ursprünglichen Zustand der Datei wieder her (verwirft lokale "
-"Änderungen)."
+msgstr "Stellt den ursprünglichen Zustand der Datei wieder her (verwirft lokale Änderungen)."
#: ../geanyvc/src/geanyvc.c:2079
msgid "Shows the log of the current directory"
@@ -2671,7 +2590,6 @@
msgstr "Zeigt den Status der Arbeitskopie."
#: ../geanyvc/src/geanyvc.c:2248
-#, fuzzy
msgid "Update from remote repository."
msgstr "Aus dem Repository aktualisieren"
@@ -2708,9 +2626,7 @@
#: ../spellcheck/src/speller.c:222
msgid "unknown error (maybe the chosen language is not available)"
-msgstr ""
-"unbekannter Fehler (möglicherweise ist die ausgewählte Sprache nicht "
-"verfügbar)."
+msgstr "unbekannter Fehler (möglicherweise ist die ausgewählte Sprache nicht verfügbar)."
#: ../spellcheck/src/scplugin.c:40
msgid "Spell Check"
@@ -2743,9 +2659,7 @@
#: ../spellcheck/src/scplugin.c:251
msgid "Show toolbar item to toggle spell checking"
-msgstr ""
-"Zeige Symbol in der Werkzeugleiste um 'Rechtschreibung beim Tippen "
-"überprüfen' ein- und auszuschalten"
+msgstr "Zeige Symbol in der Werkzeugleiste um 'Rechtschreibung beim Tippen überprüfen' ein- und auszuschalten"
#: ../spellcheck/src/scplugin.c:256
msgid "Show editor menu item to show spelling suggestions"
@@ -2764,12 +2678,8 @@
msgstr "_Verzeichnis mit Übersetzungsdateien:"
#: ../spellcheck/src/scplugin.c:288
-msgid ""
-"Read additional dictionary files from this directory. For now, this only "
-"works with myspell dictionaries."
-msgstr ""
-"Lese zusätzliche Wörterbücher aus diesem Verzeichnis. (Funktioniert zur Zeit "
-"nur mit myspell-Wörterbüchern)."
+msgid "Read additional dictionary files from this directory. For now, this only works with myspell dictionaries."
+msgstr "Lese zusätzliche Wörterbücher aus diesem Verzeichnis. (Funktioniert zur Zeit nur mit myspell-Wörterbüchern)."
#: ../spellcheck/src/gui.c:56
msgid "Spell checking while typing is now enabled"
@@ -2814,16 +2724,15 @@
msgid "Default (%s)"
msgstr "Vorgabe (%s)"
-#: ../spellcheck/src/gui.c:464 ../spellcheck/src/gui.c:475
+#: ../spellcheck/src/gui.c:464
+#: ../spellcheck/src/gui.c:475
msgid "unknown"
msgstr "Unbekannt"
#: ../spellcheck/src/gui.c:474
#, c-format
msgid "Toggle spell check while typing (current language: %s)"
-msgstr ""
-"'Rechtschreibung beim Tippen überprüfen' ein-/ausschalten (Aktuelle Sprache: "
-"%s)"
+msgstr "'Rechtschreibung beim Tippen überprüfen' ein-/ausschalten (Aktuelle Sprache: %s)"
#: ../spellcheck/src/gui.c:529
msgid "Spelling Suggestions"
@@ -2837,15 +2746,18 @@
msgid "Shift a selection left and right"
msgstr "Verschiebt eine Auswahl nach Links oder Rechts"
-#: ../shiftcolumn/src/shiftcolumn.c:374 ../shiftcolumn/src/shiftcolumn.c:394
+#: ../shiftcolumn/src/shiftcolumn.c:374
+#: ../shiftcolumn/src/shiftcolumn.c:394
msgid "Shift Left"
msgstr "Auswahl nach Links verschieben"
-#: ../shiftcolumn/src/shiftcolumn.c:381 ../shiftcolumn/src/shiftcolumn.c:396
+#: ../shiftcolumn/src/shiftcolumn.c:381
+#: ../shiftcolumn/src/shiftcolumn.c:396
msgid "Shift Right"
msgstr "Auswahl nach Rechts verschieben"
-#: ../geanylua/gsdlg_lua.c:95 ../geanylua/glspi_kfile.c:54
+#: ../geanylua/gsdlg_lua.c:95
+#: ../geanylua/glspi_kfile.c:54
#: ../geanylua/glspi.h:96
#, c-format
msgid ""
@@ -2855,7 +2767,8 @@
"Fehler in Modul »%s« in Funktion %s():\n"
"Erwarte Typ »%s« als Argument #%d\n"
-#: ../geanylua/gsdlg_lua.c:108 ../geanylua/glspi.h:124
+#: ../geanylua/gsdlg_lua.c:108
+#: ../geanylua/glspi.h:124
#, fuzzy, c-format
msgid ""
"Error in module \"%s\" at function %s():\n"
@@ -2887,9 +2800,7 @@
"\"%s\"\n"
"\n"
"to add your own custom configuration dialog."
-msgstr ""
-"Sie können das Script »%s« erstellen, um einen benutzerdefinierten "
-"Konfigurationsdialog hinzuzufügen."
+msgstr "Sie können das Script »%s« erstellen, um einen benutzerdefinierten Konfigurationsdialog hinzuzufügen."
#: ../geanylua/glspi_sci.c:427
#, c-format
@@ -2918,7 +2829,8 @@
"Fehler in Modul »%s« in Funktion %s():\n"
"Nicht genügend Argumente für den Befehl »%s«.\n"
-#: ../geanylua/glspi_sci.c:651 ../geanylua/glspi_app.c:397
+#: ../geanylua/glspi_sci.c:651
+#: ../geanylua/glspi_app.c:397
#, c-format
msgid ""
"Error in module \"%s\" at function %s():\n"
@@ -2942,7 +2854,8 @@
msgid "<too large to display>"
msgstr "<zu groß zum Anzeigen>"
-#: ../geanylua/gsdlg.c:103 ../geanylua/glspi_dlg.c:422
+#: ../geanylua/gsdlg.c:103
+#: ../geanylua/glspi_dlg.c:422
msgid "Open file"
msgstr "Datei öffnen"
@@ -3019,9 +2932,7 @@
#: ../geanylua/glspi_ver.h:9
msgid "Write and run Lua scripts for custom commands."
-msgstr ""
-"Lua Scripts schreiben und als benutzerdefinierte Funktionen in Geany "
-"ausführen."
+msgstr "Lua Scripts schreiben und als benutzerdefinierte Funktionen in Geany ausführen."
#: ../geanylua/glspi_ver.h:19
msgid "Lua Script Plugin"
@@ -3087,7 +2998,8 @@
"Fehler in Modul \"%s\" in Funktion %s():\n"
"Erwartete »open« oder »save« als 1. Argument.\n"
-#: ../geanylua/glspi_run.c:112 ../geanylua/glspi_run.c:119
+#: ../geanylua/glspi_run.c:112
+#: ../geanylua/glspi_run.c:119
msgid "Lua script error:"
msgstr "Lua Script Fehler:"
@@ -3127,7 +3039,8 @@
msgid "Unknown error while loading script file."
msgstr "Unbekannter Fehler beim Laden des Scripts."
-#: ../geanyprj/src/geanyprj.c:33 ../geanyprj/src/sidebar.c:449
+#: ../geanyprj/src/geanyprj.c:33
+#: ../geanyprj/src/sidebar.c:449
msgid "Project"
msgstr "Projekt"
@@ -3143,7 +3056,8 @@
msgid "Project Preferences"
msgstr "Projekteigenschaften"
-#: ../geanyprj/src/menu.c:99 ../geanyprj/src/menu.c:381
+#: ../geanyprj/src/menu.c:99
+#: ../geanyprj/src/menu.c:381
#: ../geanyprj/src/sidebar.c:170
msgid "New Project"
msgstr "Neues Projekt"
@@ -3169,15 +3083,8 @@
msgstr "Basisverzeichnis:"
#: ../geanyprj/src/menu.c:158
-msgid ""
-"Base directory of all files that make up the project. This can be a new "
-"path, or an existing directory tree. You can use paths relative to the "
-"project filename."
-msgstr ""
-"Basisverzeichnis aller Dateien, die zu einem Projekt gehören. Es kann sowohl "
-"ein bereits existierender, als auch ein neu zu erstellendes Verzeichnis "
-"sein. Weiterhin kann es sowohl in relativer als auch absoluter Form "
-"eingegeben werden."
+msgid "Base directory of all files that make up the project. This can be a new path, or an existing directory tree. You can use paths relative to the project filename."
+msgstr "Basisverzeichnis aller Dateien, die zu einem Projekt gehören. Es kann sowohl ein bereits existierender, als auch ein neu zu erstellendes Verzeichnis sein. Weiterhin kann es sowohl in relativer als auch absoluter Form eingegeben werden."
#: ../geanyprj/src/menu.c:161
msgid "Choose Project Base Path"
@@ -3188,14 +3095,8 @@
msgstr "Dateiliste beim Laden erzeugen"
#: ../geanyprj/src/menu.c:170
-msgid ""
-"Automatically add files that match project type on project load automaticly. "
-"You can't manually add/remove files if you checked this option, since your "
-"modification will be lost on on next project load"
-msgstr ""
-"Fügt Dateien, die dem Projekt-Typ entsprechen, automatisch beim Laden hinzu "
-"dem Projekte hinzu. Manuelles Hinzufügen oder Löschen von Dateien ist dann "
-"nicht möglich, Änderungen würden beim nächsten Laden überschrieben werden."
+msgid "Automatically add files that match project type on project load automaticly. You can't manually add/remove files if you checked this option, since your modification will be lost on on next project load"
+msgstr "Fügt Dateien, die dem Projekt-Typ entsprechen, automatisch beim Laden hinzu dem Projekte hinzu. Manuelles Hinzufügen oder Löschen von Dateien ist dann nicht möglich, Änderungen würden beim nächsten Laden überschrieben werden."
#: ../geanyprj/src/menu.c:178
msgid "Type:"
@@ -3210,15 +3111,18 @@
msgid "_Project"
msgstr "_Projekt"
-#: ../geanyprj/src/menu.c:390 ../geanyprj/src/sidebar.c:179
+#: ../geanyprj/src/menu.c:390
+#: ../geanyprj/src/sidebar.c:179
msgid "Delete Project"
msgstr "Projekt löschen"
-#: ../geanyprj/src/menu.c:401 ../geanyprj/src/sidebar.c:192
+#: ../geanyprj/src/menu.c:401
+#: ../geanyprj/src/sidebar.c:192
msgid "Add File"
msgstr "Datei hinzufügen"
-#: ../geanyprj/src/menu.c:423 ../geanyprj/src/sidebar.c:227
+#: ../geanyprj/src/menu.c:423
+#: ../geanyprj/src/sidebar.c:227
msgid "Find in Project"
msgstr "Im Projekt suchen"
@@ -3235,7 +3139,8 @@
msgid "Project \"%s\" opened."
msgstr "Projekt »%s« geöffnet."
-#: ../geanyinsertnum/src/insertnum.c:33 ../geanyinsertnum/src/insertnum.c:373
+#: ../geanyinsertnum/src/insertnum.c:33
+#: ../geanyinsertnum/src/insertnum.c:373
#: ../geanyinsertnum/src/insertnum.c:501
#, fuzzy
msgid "Insert Numbers"
@@ -3252,7 +3157,7 @@
#: ../geanyinsertnum/src/insertnum.c:198
msgid "Preparing..."
-msgstr ""
+msgstr "Vorbereitung läuft..."
#: ../geanyinsertnum/src/insertnum.c:204
#, fuzzy
@@ -3279,9 +3184,8 @@
msgstr "_Anhalten"
#: ../geanyinsertnum/src/insertnum.c:406
-#, fuzzy
msgid "Letters:"
-msgstr "Brief"
+msgstr "Buchstaben:"
#: ../geanyinsertnum/src/insertnum.c:409
#, fuzzy
@@ -3310,14 +3214,15 @@
#: ../geanyinsertnum/src/insertnum.c:427
msgid "_Zero"
-msgstr ""
+msgstr "_Null"
#: ../geanyinsertnum/src/insertnum.c:494
#, fuzzy
msgid "Insert _Numbers"
msgstr "_Lesezeichen einfügen"
-#: ../treebrowser/src/treebrowser.c:89 ../treebrowser/src/treebrowser.c:1315
+#: ../treebrowser/src/treebrowser.c:89
+#: ../treebrowser/src/treebrowser.c:1315
msgid "Tree Browser"
msgstr ""
@@ -3330,9 +3235,10 @@
msgid "Directory '%s' not exists."
msgstr "Verzeichnis »%s« nicht gefunden!\n"
-#: ../treebrowser/src/treebrowser.c:334 ../treebrowser/src/treebrowser.c:432
+#: ../treebrowser/src/treebrowser.c:334
+#: ../treebrowser/src/treebrowser.c:432
msgid "Empty"
-msgstr ""
+msgstr "Leer"
#: ../treebrowser/src/treebrowser.c:614
#, c-format
@@ -3345,7 +3251,6 @@
msgstr "_Verzeichnis"
#: ../treebrowser/src/treebrowser.c:677
-#, fuzzy
msgid "NewFile"
msgstr "Datei"
@@ -3354,11 +3259,13 @@
msgid "Do you really want to delete '%s' ?"
msgstr "Möchten Sie wirklich »%s« zurücksetzen?"
-#: ../treebrowser/src/treebrowser.c:835 ../treebrowser/src/treebrowser.c:1248
+#: ../treebrowser/src/treebrowser.c:835
+#: ../treebrowser/src/treebrowser.c:1248
msgid "Go up"
msgstr ""
-#: ../treebrowser/src/treebrowser.c:839 ../treebrowser/src/treebrowser.c:1263
+#: ../treebrowser/src/treebrowser.c:839
+#: ../treebrowser/src/treebrowser.c:1263
#, fuzzy
msgid "Set path from document"
msgstr "Zeichensatz für das neue Dokument"
@@ -3368,7 +3275,6 @@
msgstr ""
#: ../treebrowser/src/treebrowser.c:848
-#, fuzzy
msgid "Open Terminal"
msgstr "In Terminal ausführen"
@@ -3387,56 +3293,54 @@
msgstr "Datei aktualisieren"
#: ../treebrowser/src/treebrowser.c:868
-#, fuzzy
msgid "Rename"
-msgstr "Dateiname: "
+msgstr "Umbenennen"
#: ../treebrowser/src/treebrowser.c:873
-#, fuzzy
msgid "Delete"
-msgstr "Projekt löschen"
+msgstr "Löschen"
-#: ../treebrowser/src/treebrowser.c:881 ../treebrowser/src/treebrowser.c:1253
-#, fuzzy
+#: ../treebrowser/src/treebrowser.c:881
+#: ../treebrowser/src/treebrowser.c:1253
msgid "Refresh"
-msgstr "Reihe"
+msgstr "Auffrischen"
#: ../treebrowser/src/treebrowser.c:889
msgid "Expand all"
msgstr ""
#: ../treebrowser/src/treebrowser.c:893
-#, fuzzy
msgid "Collapse all"
-msgstr "_Alle schließen"
+msgstr "Alle einklappen"
#: ../treebrowser/src/treebrowser.c:900
-#, fuzzy, c-format
+#, c-format
msgid "Close: %s"
-msgstr "_Alle schließen"
+msgstr "%s: Schließen"
#: ../treebrowser/src/treebrowser.c:905
#, c-format
msgid "Copy full path"
msgstr ""
-#: ../treebrowser/src/treebrowser.c:913 ../treebrowser/src/treebrowser.c:1531
-#, fuzzy
+#: ../treebrowser/src/treebrowser.c:913
+#: ../treebrowser/src/treebrowser.c:1531
msgid "Show bookmarks"
-msgstr "Lesezeichen"
+msgstr "Lesezeichen anzeigen"
-#: ../treebrowser/src/treebrowser.c:918 ../treebrowser/src/treebrowser.c:1480
+#: ../treebrowser/src/treebrowser.c:918
+#: ../treebrowser/src/treebrowser.c:1480
#, fuzzy
msgid "Show hidden files"
msgstr "Diff von der aktuellen Datei"
-#: ../treebrowser/src/treebrowser.c:923 ../treebrowser/src/treebrowser.c:1470
+#: ../treebrowser/src/treebrowser.c:923
+#: ../treebrowser/src/treebrowser.c:1470
#, fuzzy
msgid "Show bars"
msgstr "Status der Arbeitskopie anzeigen"
#: ../treebrowser/src/treebrowser.c:1258
-#, fuzzy
msgid "Home"
msgstr "Ausgabe"
@@ -3451,9 +3355,7 @@
msgstr "Seitenleiste _verstecken"
#: ../treebrowser/src/treebrowser.c:1283
-msgid ""
-"Filter (*.c;*.h;*.cpp), and if you want temporary filter using the '!' "
-"reverse try for example this '!;*.c;*.h;*.cpp'"
+msgid "Filter (*.c;*.h;*.cpp), and if you want temporary filter using the '!' reverse try for example this '!;*.c;*.h;*.cpp'"
msgstr ""
#: ../treebrowser/src/treebrowser.c:1291
@@ -3467,11 +3369,9 @@
#: ../treebrowser/src/treebrowser.c:1452
#, c-format
msgid ""
-"The command to execute when using \"Open with\". You can use %f and %d "
-"wildcards.\n"
+"The command to execute when using \"Open with\". You can use %f and %d wildcards.\n"
"%f will be replaced with the filename including full path\n"
-"%d will be replaced with the path name of the selected file without the "
-"filename"
+"%d will be replaced with the path name of the selected file without the filename"
msgstr ""
#: ../treebrowser/src/treebrowser.c:1460
@@ -3496,15 +3396,12 @@
msgstr "Datei auswählen"
#: ../treebrowser/src/treebrowser.c:1492
-msgid ""
-"Don't show generated object files in the file browser, this includes *.o, *."
-"obj. *.so, *.dll, *.a, *.lib"
+msgid "Don't show generated object files in the file browser, this includes *.o, *.obj. *.so, *.dll, *.a, *.lib"
msgstr ""
#: ../treebrowser/src/treebrowser.c:1494
-#, fuzzy
msgid "Reverse filter"
-msgstr "Datei zurücksetzen"
+msgstr "Filter zurücksetzen"
#: ../treebrowser/src/treebrowser.c:1499
msgid "Follow current document"
@@ -3534,9 +3431,8 @@
msgstr "Kurzhilfen anzeigen"
#: ../geanyextrasel/src/extrasel.c:30
-#, fuzzy
msgid "Extra Selection"
-msgstr "Schriftart auswählen"
+msgstr "Extra Selection"
#: ../geanyextrasel/src/extrasel.c:30
msgid "Column mode, select to line / matching brace."
@@ -3548,21 +3444,19 @@
#: ../geanyextrasel/src/extrasel.c:271
msgid "_Column mode"
-msgstr ""
+msgstr "_Spaltenmodus"
#: ../geanyextrasel/src/extrasel.c:275
msgid "Column mode"
-msgstr ""
+msgstr "Spaltenmodus"
#: ../geanyextrasel/src/extrasel.c:277
-#, fuzzy
msgid "Select to _Line"
-msgstr "Schriftart auswählen"
+msgstr "Zeile _auswählen"
#: ../geanyextrasel/src/extrasel.c:281
-#, fuzzy
msgid "Select to line"
-msgstr "Schriftart auswählen"
+msgstr "Zeile auswählen"
#: ../geanyextrasel/src/extrasel.c:283
msgid "Select to Matching _Brace"
@@ -3574,34 +3468,24 @@
#~ msgid "_Load"
#~ msgstr "_Laden"
-
#~ msgid "Load target program into debugger."
#~ msgstr "Zielprogramm in den Debugger laden."
-
#~ msgid "_Unload"
#~ msgstr "_Entladen"
-
#~ msgid "Kill the target program AND the debugger."
#~ msgstr "Das Programm UND den Debugger beenden (töten)."
-
#~ msgid "_Run"
#~ msgstr "_Ausführen"
-
#~ msgid "Execute target program in debugger."
#~ msgstr "Zieprogramm im Debugger ausführen."
-
#~ msgid "_Kill"
#~ msgstr "_Töten"
-
#~ msgid "Kill the target program with SIGKILL."
#~ msgstr "Das Zielprogramm mit SIGKILL töten."
-
#~ msgid "Pause the target program with SIGINT."
#~ msgstr "Das Zielprogramm mit SIGINT pausieren."
-
#~ msgid "Continue executing target program."
#~ msgstr "Des Zielprgramme weiter ausführen"
-
#~ msgid "Step to the next line or function call."
#~ msgstr ""
#~ "Halte bei der Ausführung der nächsten Zeile bzw. des nächsten "
@@ -3611,10 +3495,8 @@
#, fuzzy
#~ msgid "Step _in"
#~ msgstr "%s bei Schritt »%s..%s«"
-
#~ msgid "Execute the next machine instruction or function call."
#~ msgstr "Den nächsten Befehl oder Funktionsaufruf ausführen."
-
#~ msgid "Step to the next line."
#~ msgstr "Zur nächsten Zeile springen"
@@ -3622,138 +3504,99 @@
#, fuzzy
#~ msgid "Ne_xt in"
#~ msgstr "_Weitersuchen"
-
#~ msgid "Execute the next machine instruction."
#~ msgstr "Den nächsten Befehl ausführen."
-
#~ msgid "Run _to"
#~ msgstr "Springe zu"
-
#~ msgid "Run to specified source line."
#~ msgstr "Bis zur ausgewählten Quellcodezeile ausführen"
-
#~ msgid "Stac_k"
#~ msgstr "_Stapel"
-
#~ msgid "Display a backtrace of the current call stack."
#~ msgstr "Eine Ablaufverfolgung des momentanen Stapels anzeigen."
-
#~ msgid "Add or remove breakpoints."
#~ msgstr "Haltepunkte hinzufügen oder entfernen."
-
#~ msgid "Add or remove watchpoints."
#~ msgstr "Beobachtungspunkte hinzufügen oder entfernen."
-
#~ msgid "_Finish"
#~ msgstr "_Beenden"
#, fuzzy
#~ msgid "Complete the currently executing function."
#~ msgstr "Die momentan ausgeführte Funktion fertig stellen."
-
#~ msgid "_Return"
#~ msgstr "_Zurück"
#, fuzzy
#~ msgid "Return immediately from the current function."
#~ msgstr "Unverzüglich von der momentanen Funktion zurückkehren."
-
#~ msgid "En_viron"
#~ msgstr "_Umgebungen"
-
#~ msgid "Set target environment and command line options."
#~ msgstr "Die Zielumgebung und Kommandozeilenoptionen einstellen."
-
#~ msgid "_Options"
#~ msgstr "_Optionen"
-
#~ msgid "Set user interface options."
#~ msgstr "Setze Optionen für die Benutzerschnittstelle"
-
#~ msgid "VC"
#~ msgstr "VC"
-
#~ msgid "Code Navigation plug-in configuration"
#~ msgstr "Quellcode-Navigation Plugin Konfiguration"
# Diese Übersetzung existiert drei mal.
#~ msgid "Switch header / implementation"
#~ msgstr "Umschalten zwischen Deklaration und Implementierung"
-
#, fuzzy
#~ msgid "_History (Log)"
#~ msgstr "_Versionsgeschichte"
-
#~ msgid "_Spell Check"
#~ msgstr "_Rechtschreibprüfung"
-
#~ msgid "Frank Lanitz <frank(a)frank.uvena.de>"
#~ msgstr "Frank Lanitz <frank(a)frank.uvena.de>"
-
#~ msgid "Current _File"
#~ msgstr "_Aktuelle Datei"
-
#~ msgid "Diff From Current File"
#~ msgstr "Diff von der aktuellen Datei"
-
#~ msgid "Diff From Current Directory"
#~ msgstr "Diff vom aktuellen Verzeichnis"
-
#~ msgid "Diff From Base Directory"
#~ msgstr "Diff vom Grundverzeichnis"
-
#~ msgid "Blame From Current File"
#~ msgstr "Blame von aktueller Datei"
-
#~ msgid "Diff From Current Project"
#~ msgstr "Diff vom aktuellen Projekt"
-
#~ msgid "Make a diff from the current project's base path"
#~ msgstr "Erstellt ein Diff für das aktuell geöffnete Projekt."
-
#~ msgid "Log Of Current Project"
#~ msgstr "Historie vom aktuellen Projekt"
-
#~ msgid "Shows the log of the current project"
#~ msgstr "Zeigt die Versionshistorie vom aktuellen Projekt."
#, fuzzy
#~ msgid "External Debugger"
#~ msgstr "Führe externes Debuggingwerkzeug aus"
-
#~ msgid "Run external debugger."
#~ msgstr "Führe externes Debuggingwerkzeug aus"
-
#~ msgid "Launch external debugger"
#~ msgstr "Starte externes Debuggingwerkzeug"
-
#~ msgid "DBG"
#~ msgstr "DBG"
-
#~ msgid "Insert label"
#~ msgstr "Lesezeichen einfügen"
-
#~ msgid "Insert reference"
#~ msgstr "Verweis einfügen"
-
#~ msgid "Replacement of special characters"
#~ msgstr "Sonderzeichen ersetzen"
-
#~ msgid "_Mail"
#~ msgstr "_Mail"
-
#~ msgid "Note: \\%f will be replaced by your filename."
#~ msgstr "Anmerkung: \\%f wird durch den Dateinamen ersetzt."
-
#~ msgid "Project \"%s\" closed."
#~ msgstr "Projekt »%s« geschlossen."
-
#~ msgid "Load Mini-Script File"
#~ msgstr "Mini-Skript laden"
-
#~ msgid "Save Mini-Script File"
#~ msgstr "Mini-Skript speichern"
-
#~ msgid ""
#~ "<b>GMS : Geany Mini-Script filter Plugin</b>\n"
#~ "This plugin is a tools to apply a script filter on :\n"
@@ -3802,54 +3645,38 @@
#~ "General Public License as published by the Free \n"
#~ "Software Foundation; either version 2 of the License, \n"
#~ "or (at your option) any later version."
-
#~ msgid "Mini-Script Filter"
#~ msgstr "Mini-Skript Filter"
-
#~ msgid "Clear the mini-script window"
#~ msgstr "Leert das Skript-Fenster"
-
#~ msgid "Load a mini-script into this window"
#~ msgstr "Lädt eine Datei in das Skript-Fenster"
-
#~ msgid "Save the mini-script into a file"
#~ msgstr "Speichert das Skript ab"
-
#~ msgid "Display a information about the mini-script plugin"
#~ msgstr "Zeigt Informationen über das Plugin"
-
#~ msgid "select the mini-script type"
#~ msgstr "Wählen Sie den Skript-Typ aus"
-
#~ msgid "filter input"
#~ msgstr "Eingabedaten für den Filter"
-
#~ msgid "select the input of mini-script filter"
#~ msgstr "Wählen Sie die Eingabedaten des Filters aus"
-
#~ msgid "session"
#~ msgstr "Sitzung"
-
#~ msgid "filter output"
#~ msgstr "Filterausgabe"
-
#~ msgid "select the output of mini-script filter"
#~ msgstr "Wählen Sie die Ausgabe des Filters aus"
-
#~ msgid "Current Doc."
#~ msgstr "Aktuelles Dokument"
-
#~ msgid "New Doc."
#~ msgstr "Neues Dokument"
-
#~ msgid "geany mini-script"
#~ msgstr "Geany Mini-Skript"
-
#~ msgid "GMS (Geany Mini-Script filter plugin)"
#~ msgstr "GMS (Geany Mini-Skript-Filter)"
-
#~ msgid "Pascal BURLOT, a Geany user"
#~ msgstr "Pascal BURLOT, ein Geany-Benutzer"
-
#~ msgid "_Mini-Script"
#~ msgstr "_Mini-Skript"
+
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 1408
http://geany-plugins.svn.sourceforge.net/geany-plugins/?rev=1408&view=rev
Author: eht16
Date: 2010-05-25 20:04:45 +0000 (Tue, 25 May 2010)
Log Message:
-----------
Save dictionary directory only if it is set (patch by Colomban Wendling, thanks).
Modified Paths:
--------------
trunk/geany-plugins/spellcheck/ChangeLog
trunk/geany-plugins/spellcheck/src/scplugin.c
Modified: trunk/geany-plugins/spellcheck/ChangeLog
===================================================================
--- trunk/geany-plugins/spellcheck/ChangeLog 2010-05-25 20:01:45 UTC (rev 1407)
+++ trunk/geany-plugins/spellcheck/ChangeLog 2010-05-25 20:04:45 UTC (rev 1408)
@@ -2,6 +2,9 @@
* src/speller.c:
Fix broken checks when the selected text is only on one line.
+ * src/scplugin.c:
+ Save dictionary directory only if it is set
+ (patch by Colomban Wendling, thanks).
2010-01-01 Enrico Tröger <enrico(dot)troeger(at)uvena(dot)de>
Modified: trunk/geany-plugins/spellcheck/src/scplugin.c
===================================================================
--- trunk/geany-plugins/spellcheck/src/scplugin.c 2010-05-25 20:01:45 UTC (rev 1407)
+++ trunk/geany-plugins/spellcheck/src/scplugin.c 2010-05-25 20:04:45 UTC (rev 1408)
@@ -122,7 +122,9 @@
sc_info->show_toolbar_item);
g_key_file_set_boolean(config, "spellcheck", "show_editor_menu_item",
sc_info->show_editor_menu_item);
- g_key_file_set_string(config, "spellcheck", "dictionary_dir", sc_info->dictionary_dir);
+ if (sc_info->dictionary_dir != NULL)
+ g_key_file_set_string(config, "spellcheck", "dictionary_dir",
+ sc_info->dictionary_dir);
sc_gui_update_toolbar();
sc_gui_update_menu();
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.