[libgda] Corrections to GdaBrowser's inline help to have 'make distcheck' work

[Vivien Malerba <vivien src gnome org>]

commit 58a5e217be389674c22bf2c72d87e75e01ad2e49
Author: Vivien Malerba <malerba gnome-db org>
Date:   Wed Mar 23 20:53:16 2011 +0100

    Corrections to GdaBrowser's inline help to have 'make distcheck' work

 tools/browser/help/C/data-manager-perspective.page |    4 ++--
 tools/browser/help/C/data-manager-xml-syntax.page  |   10 +++++-----
 tools/browser/help/C/declaredfk.page               |    4 ++--
 tools/browser/help/C/features.page                 |    8 ++++----
 .../help/C/query-execution-perspective.page        |    8 ++++----
 tools/browser/help/C/virtual-connections.page      |    4 ++--
 6 files changed, 19 insertions(+), 19 deletions(-)
---
diff --git a/tools/browser/help/C/data-manager-perspective.page b/tools/browser/help/C/data-manager-perspective.page
index 7c3d7c9..48e0949 100644
--- a/tools/browser/help/C/data-manager-perspective.page
+++ b/tools/browser/help/C/data-manager-perspective.page
@@ -40,7 +40,7 @@
   Also when the row selection of the 'customers' view changes, the whole contents of the 'orders' view
   is refreshed.
 </p>
-<section>
+<section id="data-manager-def-data-source">
   <title>Defining data sources</title>
   <p>
     The simplest data source
@@ -86,7 +86,7 @@
     <item><p><gui>Help</gui>: shows some help</p></item>
   </list>
 </section>
-<section>
+<section id="data-manager-exec-data-source">
   <title>Executing defined data sources</title>
   <p>
     To execute a defined set of data sources, simply switch to execute mode using
diff --git a/tools/browser/help/C/data-manager-xml-syntax.page b/tools/browser/help/C/data-manager-xml-syntax.page
index bcc3d2a..3895e49 100644
--- a/tools/browser/help/C/data-manager-xml-syntax.page
+++ b/tools/browser/help/C/data-manager-xml-syntax.page
@@ -20,7 +20,7 @@
   in the same data sources specifications.
 </p>
 
-<section>
+<section id="data-manager-exp-variables">
   <title>Exported variables</title>
   <p>
     Each data source exports some variables which can be reused by other data sources to introduce
@@ -33,7 +33,7 @@
     in case the variable is unset, the data source's execution result is an empty data set.
   </p>
 </section>
-<section>
+<section id="data-manager-query-tag">
   <title>The <code>&lt;query&gt;</code> tag</title>
   <p>
     Use the <code>&lt;query&gt;</code> tag to specify an SQL SELECT statement, as the contents of the tag.
@@ -69,7 +69,7 @@
     a customer, and one which displays all the attributes for the selected customer.
   </p>
 
-  <section>
+  <section id="data-manager-query-exp-variables">
     <title>Exported variables</title>
     <p>
       Each data source defined by a <code>&lt;query&gt;</code> tag exports the following variable for
@@ -84,7 +84,7 @@
 
 </section>
 
-<section>
+<section id="data-manager-table-tag">
   <title>The <code>&lt;table&gt;</code> tag</title>
   <p>
     Use the <code>&lt;table&gt;</code> tag to define a data source which will display the contents of a table.
@@ -150,7 +150,7 @@
 	has been specified for the <code>&lt;table&gt;</code> tags.</p></item>
   </list>
 
-  <section>
+  <section id="data-manager-table-exp-variables">
     <title>Exported variables</title>
     <p>
       Each data source defined by a <code>&lt;query&gt;</code> tag exports the following variable for
diff --git a/tools/browser/help/C/declaredfk.page b/tools/browser/help/C/declaredfk.page
index 2efdaac..4f5160d 100644
--- a/tools/browser/help/C/declaredfk.page
+++ b/tools/browser/help/C/declaredfk.page
@@ -38,7 +38,7 @@
 	UPDATE or DELETE situations, so the reported policy will always be "not enforced"</p></item>
   </list>
 
-  <section>
+  <section id="declare-new-fk">
     <title>Declaring a new foreign key</title>
     <p>
       A new foreign key can be declared from the
@@ -66,7 +66,7 @@
     </figure>
   </section>
   
-  <section>
+  <section id="remove-fk">
     <title>Remove a declared foreign key</title>
     <p>
       A declared foreign key can be removed by clicking on the <guiseq><gui>(Remove)</gui></guiseq> link
diff --git a/tools/browser/help/C/features.page b/tools/browser/help/C/features.page
index 8799fed..915058f 100644
--- a/tools/browser/help/C/features.page
+++ b/tools/browser/help/C/features.page
@@ -9,7 +9,7 @@
   <p>
     <app>gda-browser</app>'s current features are:
   </p>
-  <section>
+  <section id="features-gen-ui">
     <title>General user interface</title>
     <list>	
       <item><p>multi threaded: each connection is handled in it own thread, meaning that no single
@@ -18,7 +18,7 @@
       <item><p>full screen mode accessible to maximize the screen space usage</p></item>
     </list>
   </section>
-  <section>
+  <section id="features-cnc-mgmt">
     <title>Connection management</title>
     <list>
       <item><p>multiple simultaneous connections can be opened at once</p></item>
@@ -27,7 +27,7 @@
       connection can lock the application</p></item>
     </list>
   </section>
-  <section>
+  <section id="features-activities">
     <title>Activities</title>
     <p>
       The activities are grouped by theme around the notion of <link type="topic" xref="general-ui">perspectives</link>, the following are currently implemented:
@@ -44,7 +44,7 @@
       See also the section about <link xref="actions">actions</link>
     </p>
   </section>
-  <section>
+  <section id="features-open">
     <title>Openness</title>
     <list>
       <item><p>CSV and other text files can be imported and used in conjunction with <link type="topic" xref="virtual-connections">connection binding</link></p></item>
diff --git a/tools/browser/help/C/query-execution-perspective.page b/tools/browser/help/C/query-execution-perspective.page
index 55d53ac..e1eb327 100644
--- a/tools/browser/help/C/query-execution-perspective.page
+++ b/tools/browser/help/C/query-execution-perspective.page
@@ -48,7 +48,7 @@
   <item><p>execution results in the lower right part</p></item>
 </list>
 
-<section>
+<section id="query-exec-sql">
   <title>SQL area</title>
   <p>
     The SQL area is an SQL editor. The SQL can be any SQL understood by the database, with the exception
@@ -66,7 +66,7 @@
   </list>
 </section>
 
-<section>
+<section id="query-exec-command-buttons">
   <title>Command buttons</title>
   <p>
     The commands available through the command buttons are:
@@ -84,7 +84,7 @@
   </list>
 </section>
 
-<section>
+<section id="query-exec-history">
   <title>Execution history</title>
   <p>
     The execution history part contains a list of the past executed statements, ordered by execution date
@@ -100,7 +100,7 @@
   </p>
 </section>
 
-<section>
+<section id="query-exec-results">
   <title>Execution results</title>
   <p>
     The Execution results part displays the execution result of the currently selected execution
diff --git a/tools/browser/help/C/virtual-connections.page b/tools/browser/help/C/virtual-connections.page
index 383cc8f..c0ec791 100644
--- a/tools/browser/help/C/virtual-connections.page
+++ b/tools/browser/help/C/virtual-connections.page
@@ -36,7 +36,7 @@
     <item><p>bind a data set to import data from a text file as a single table: use the <guiseq><gui>Bind a data set</gui></guiseq> option. See section below for more information.</p></item>
   </list>
 
-  <section>
+  <section id="vcnc-use-case">
     <title>Use case for virtual connections</title>
     <p>
       To illustrate virtual connection usage, let's define a simple use case and see how it's usefull. Suppose you have
@@ -96,7 +96,7 @@ WHERE "Error code"=0
   </section>
 
 
-  <section>
+  <section id="vcnc-import-dataset">
     <title>Importing a data set into a virtual connection</title>
     <p>
       To import a data set into a table in the virtual connection (for example to import the "problems.csv" file