Updated help files to reflect the database type options.

git-svn-id: svn+ssh://garage/var/lib/gforge/svnroot/maemo-mapper/trunk@245 6c538b50-5814-0410-93ad-8bdf4c0149d1

diff --git a/data/help/en_US/maemomapper.xml b/data/help/en_US/maemomapper.xml
index 3c15c132350133d792929031e8bd0555ebc89cdc..6882a99900c361b1080734ac265298c005b07f2d 100644 (file)
--- a/data/help/en_US/maemomapper.xml
+++ b/data/help/en_US/maemomapper.xml
@@ -844,7 +844,8 @@
           selected repository.
         </listitem>
         <listitem>
-          <display_text>New...</display_text> - Adds a new repository.
+          <display_text>New...</display_text> - Adds a new repository.  See
+          <ref refid="help_maemomapper_newrepo" refdoc="New Repositories"/>.
         </listitem>
         <listitem>
           <display_text>Reset...</display_text> - Resets your repository
@@ -872,6 +873,34 @@
         use of a particular repository.
       </note>
     </topic>
+    <topic>
+      <topictitle>Repository Types</topictitle>
+      <context contextUID="help_maemomapper_newrepo"/>
+      <para>
+        Over the years, Maemo Mapper has used several different types of
+        backing databases to store downloaded maps.  Currently, Maemo Mapper
+        supports two different types of backing map databases.
+      </para>
+      <list>
+        <listitem>
+          <display_text>SQLite 3 (default)</display_text> - The new default
+          backing database format since Maemo Mapper v2.6, SQLite 3 provides
+         better reliability. It also scales somewhat better than GDBM and is
+         not subject to file size limitations, making it the only choice for
+         large map databases.  This is the preferred format, and should
+         generally be used for all new databases.
+        </listitem>
+        <listitem>
+          <display_text>GDBM (legacy)</display_text> - The database format
+          of versions of Maemo Mapper prior to v2.6.  It is slightly less
+          reliable than SQLite, and GDBM files are limited to 2 gigabytes.
+          These limitations, however, allow it to perform slightly faster
+         than SQLite for small map databases.  If you are unsatisfied with
+         SQLite's performance in Maemo Mapper, you can take your chances with
+         GDBM.
+        </listitem>
+      </list>
+    </topic>
     <topic>
       <topictitle>Managing Maps</topictitle>
       <context contextUID="help_maemomapper_mapman"/>
@@ -1598,7 +1627,7 @@
       <topictitle>About Maemo Mapper</topictitle>
       <context contextUID="help_maemomapper_about"/>
       <para>
-        Current Version: 2.5.3
+        Current Version: 2.6
       </para>
       <para>
         Maemo Mapper was created and developed by John Costigan (aka

diff --git a/data/help/en_US/maemomapper.xml.in b/data/help/en_US/maemomapper.xml.in
index 8b9d87d19e430337e2f0673ccd000765d354aa18..edca102cfa10b7a20e11a42a437a2a4ec185a6bd 100644 (file)
--- a/data/help/en_US/maemomapper.xml.in
+++ b/data/help/en_US/maemomapper.xml.in
@@ -844,7 +844,8 @@
           selected repository.
         </listitem>
         <listitem>
-          <display_text>New...</display_text> - Adds a new repository.
+          <display_text>New...</display_text> - Adds a new repository.  See
+          <ref refid="help_maemomapper_newrepo" refdoc="New Repositories"/>.
         </listitem>
         <listitem>
           <display_text>Reset...</display_text> - Resets your repository
@@ -872,6 +873,34 @@
         use of a particular repository.
       </note>
     </topic>
+    <topic>
+      <topictitle>Repository Types</topictitle>
+      <context contextUID="help_maemomapper_newrepo"/>
+      <para>
+        Over the years, Maemo Mapper has used several different types of
+        backing databases to store downloaded maps.  Currently, Maemo Mapper
+        supports two different types of backing map databases.
+      </para>
+      <list>
+        <listitem>
+          <display_text>SQLite 3 (default)</display_text> - The new default
+          backing database format since Maemo Mapper v2.6, SQLite 3 provides
+         better reliability. It also scales somewhat better than GDBM and is
+         not subject to file size limitations, making it the only choice for
+         large map databases.  This is the preferred format, and should
+         generally be used for all new databases.
+        </listitem>
+        <listitem>
+          <display_text>GDBM (legacy)</display_text> - The database format
+          of versions of Maemo Mapper prior to v2.6.  It is slightly less
+          reliable than SQLite, and GDBM files are limited to 2 gigabytes.
+          These limitations, however, allow it to perform slightly faster
+         than SQLite for small map databases.  If you are unsatisfied with
+         SQLite's performance in Maemo Mapper, you can take your chances with
+         GDBM.
+        </listitem>
+      </list>
+    </topic>
     <topic>
       <topictitle>Managing Maps</topictitle>
       <context contextUID="help_maemomapper_mapman"/>

diff --git a/data/help/fi_FI/maemomapper.xml b/data/help/fi_FI/maemomapper.xml
index b04bf3bbbe8ae8a12f69091a0f460d3dff7880e9..e3dbbb6c6231c0317cc88edae158d059125788b4 100644 (file)
--- a/data/help/fi_FI/maemomapper.xml
+++ b/data/help/fi_FI/maemomapper.xml
@@ -1625,7 +1625,7 @@
       <topictitle>Tietoja ohjelmasta Maemo Mapper</topictitle>
       <context contextUID="help_maemomapper_about"/>
       <para>
-        Asennettu versio: 2.5.3
+        Asennettu versio: 2.6
       </para>
       <para>
         Maemo Mapperin on suunnitellut ja luonut John Costigan (aka