diff --git a/gramps2/doc/gramps-manual/C/usage.xml b/gramps2/doc/gramps-manual/C/usage.xml
index f89aa36e9..62e4b2ef1 100644
--- a/gramps2/doc/gramps-manual/C/usage.xml
+++ b/gramps2/doc/gramps-manual/C/usage.xml
@@ -37,13 +37,9 @@
To start a new database, choose
+ FileNew
+ .You will then be asked to give the new database a name.
-
- File
- New
- .
-
- You will then be asked to give the new database a name.
@@ -65,29 +61,23 @@
Opening a Database
- To open a database, either choose
-
-
- File
- Open
-
-
- or click the Open button on the Toolbar.
- The Open database dialog will appear and
- you'll see a list of files. If you don't see the file you're
- looking for, make sure the All files filter is selected. (This
- dialog has a "filetype" filter, meaning it may only be
+ To open a database, either choose
+ File
+ Open or click the
+ Open button on the Toolbar. The
+ Open database dialog will appear and you'll
+ see a list of files. If you don't see the file you're looking
+ for, make sure the All files filter is selected. (This dialog
+ has a "filetype" filter, meaning it may only be
showing files that have a certain extension.)
-
-
+
To open a recently accessed database, choose
- File Open Recent
+ FileOpen Recent
and select the filename from the list.
-
-
+
If you do not have "write permissions" for the selected database,
it will be opened in a Read Only mode. In this mode, the data
@@ -97,12 +87,12 @@
- GRAMPS allows you to open certain databases that have not been
- saved in GRAMPS' own file format. These include XML and GEDCOM
- databases. But you should be aware that if the XML or GEDCOM
- database is relatively large, you may encounter some performance
- problems. These can be avoided by creating a new GRAMPS database
- and importing your XML/GEDCOM data into it.
+ GRAMPS allows you to open certain databases that have not been
+ saved in GRAMPS' own file format. These include XML and GEDCOM
+ databases. But you should be aware that if the XML or GEDCOM
+ database is relatively large, you may encounter some performance
+ problems. These can be avoided by creating a new GRAMPS database
+ and importing your XML/GEDCOM data into it.
@@ -144,23 +134,23 @@
"save" command (although there is a "save
as" command that we'll discuss below.)
-
+
-
You can undo changes you've made by selecting
Edit
Undo . If you select
this command repeatedly, your most recent changes will be undone
- one at a time.
+ one at a time.
+
+
If you have made changes to your data, and would like to return
your database to the way it was when you opened it, select
FileAbandon changes
and quit. This just like quitting
without saving in other programs.
-
-
+
If you would like to save your database under a different name,
you can do so by choosing File
@@ -180,9 +170,10 @@
Importing Data
- Importing allows you to bring data from other
- genealogy programs into a &app; database Currently,
- &app; can import data from the following formats:
+ Importing allows you to bring data from other genealogy programs
+ into a &app; database Currently, &app; can import data from the
+ following formats:
+
@@ -207,25 +198,25 @@
- Importing vs. opening
-
- Please recognize that importing a database is different from
- opening a database. When you import, you are actually bringing
- data from one database into a GRAMPS database. When you open a
- file, you editing your original file.
-
+ Importing vs. opening
+
+ Please recognize that importing a database is different from
+ opening a database. When you import, you are actually bringing
+ data from one database into a GRAMPS database. When you open a
+ file, you editing your original file.
+
- To import data, select File
- Import . The
- Import database dialog will open, asking you
- to specify the file you wish to import.
+ To import data, select File
+ Import. The Import
+ database dialog will open, asking you to specify the
+ file you wish to import.
-
+
Data loss with some formats
It is important to note that the importing process is not
@@ -233,8 +224,7 @@
that some of the data in these databases will not be imported
into &app;.
-
-
+
The &app; database (grdb), &app; XML, and &app; package are all
@@ -254,51 +244,51 @@
but not generally portable across computers with
different binary architecture (e.g. i386 vs alpha).
-
+
-
- &app; XML
-
-
- The &app; XML file was the default format for the
- previous stable version of &app;. Unlike the grdb
- format, it is architecture independent and
- human-readable. The database may also have references to
- non-local (external) media objects, therefore it is not
- guaranteed to be completely portable. The &app; XML
- database is created by saving (
+
+ &app; XML
+
+
+
+ The &app; XML file was the default format for the
+ previous stable version of &app;. Unlike the grdb
+ format, it is architecture independent and
+ human-readable. The database may also have references to
+ non-local (external) media objects, therefore it is not
+ guaranteed to be completely portable. The &app; XML
+ database is created by saving (
File
Save As...
-
+
) or exporting (
File
Export...
) data in that format
-
-
-
-
- &app; package
-
-
- The package is a compressed archive containing the &app;
- XML file and all media objects (images, sound files,
- etc.) to which the database refers. The &app; package is
- created by exporting (
-
- File
- Export...
-
- ) data in that format.
-
-
-
-
-
+
+
+
+
+ &app; package
+
+
+ The package is a compressed archive containing the &app;
+ XML file and all media objects (images, sound files,
+ etc.) to which the database refers. The &app; package is
+ created by exporting (
+
+ File
+ Export...
+
+ ) data in that format.
+
+
+
+