diff --git a/doc/gramps-manual/C/gramps-manual-C.omf b/doc/gramps-manual/C/gramps-manual-C.omf index d3e6959d9..c673b2cab 100644 --- a/doc/gramps-manual/C/gramps-manual-C.omf +++ b/doc/gramps-manual/C/gramps-manual-C.omf @@ -3,8 +3,8 @@ Alex Roitman shura@alex.neuro.umn.edu GRAMPS Manual - 2003-03-25 - + 2003-05-30 + User Manual for GRAMPS. User Manual diff --git a/doc/gramps-manual/C/gramps-manual.xml b/doc/gramps-manual/C/gramps-manual.xml index 2fc74ace6..5484f7862 100644 --- a/doc/gramps-manual/C/gramps-manual.xml +++ b/doc/gramps-manual/C/gramps-manual.xml @@ -3,7 +3,7 @@ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [ - + GRAMPS">
- &app; Getting Started Window + &app; Getting Started Window: Researcher Information - Shows Getting Started Window. + Shows Researcher Information Window.
+ Enter your personal information in the corresponding + text entry fields. Although &app; requests information about you, + this information is used only so that &app; can create valid GEDCOM + output files. A valid GEDCOM file requires information about the file's + creator. If you choose, you may leave the information empty, however + all the GEDCOM files you export will not be valid. + + + This information can be entered at any time in the + Preferences dialog, under the + Usage category. + + @@ -787,20 +813,28 @@ - - Importing GEDCOM Data - Importing GEDCOM data allows you to incorporate the data created in - other genealogical programs into your currently open &app; database. - &app; can import GEDCOM data files from a - number of software packages, as long as they comply with GEDCOM - standards. To import a GEDCOM file, choose File - ImportImport from - GEDCOM. You will then be prompted with the - Open File dialog asking you to specify the GEDCOM file - name. + + Importing Data + Importing allows you to incorporate the data from other + databases into your currently open &app; database. Currently, + &app; can import data from three different + formats: GEDCOM, &app; database, and &app; package. All of these are + available as items of File + Import submenu. - Upon starting the import, &app; will - display the following GEDCOM import dialog with the summary of the + Note that the difference between opening &app; database and + importing from &app; database is that importing incorporates all the + data into your currently open database, if any. + + After choosing an import format, you will be prompted with the + Open File dialog asking you to specify the + file name from which to import. For GEDCOM and + &app; package, select an appropriate file. + For &app; database, select a directory which stores + the database and all media files (if any). + + Upon starting the GEDCOM import, &app; + will display the following GEDCOM import dialog with the summary of the information about the data. The information is updated as the import progresses. @@ -813,18 +847,70 @@ Shows GEDCOM Import Window. - - - - Exporting GEDCOM Data - Exporting GEDCOM data allows you to share any portion of your - &app; database with other researchers - by way of standard GEDCOM files. To export into a GEDCOM file, - choose File - Export - Export to GEDCOM. The following - Export GEDCOM file dialog will appear. + Upon starting the &app; database or &app; package import, + &app; will display the progress in the + progress bar of its main window. + + If a media file is not found during import, the following dialog + will prompt you for the possible actions: + + +
+ Missing Media dialog + + + Shows Missing Media dialog. +
+ + + + + To remove the object corresponding to the missing file as well as + all the references to that object from various database records, click + Remove Object button. This will alter your + database so that it will be in a consistent state, but all the + references to the missing file will be gone. Use this option if the + file is irrevocably lost and there is no possibility of ever replacing + it. + + + + To keep the reference to the object corresponding to the missing + file, click Keep Reference button. + This will leave things as is, i.e. in an inconsistent state. + You could supply the missing file later, in which case you will have + to copy it into your database directory. Choose this option if the + replacement is possible, but not available right now. + + + To supply the missing file during import, click + Select File button. This will copy the file you + select in place of the missing file. No references will be altered + in the database, and it will be in the consistent state. Use this option + if the replacement is readily available. + + + + + + + + + Exporting Data + + Exporting allows you to share any portion of your &app; database + with other researchers as well as to make your database completely + portable to another computer. Currently, &app; + can export data to three different formats: GEDCOM, &app; package, + and CD. All of these are available as items of + File + Export submenu. + + Exporting to GEDCOM will create a GEDCOM file, according to the + settings set in the following dialog: +
Export GEDCOM File dialog @@ -863,43 +949,67 @@ Shows Export GEDCOM progress dialog.
- - - - Importing and Exporting &app; Packages - &app; provides a way to make your - &app; database completely portable. This might - prove useful, for instance, when you need to move your database to - another machine or to share it with somebody, while retaining all the - features provided by &app;. To accomplish - this, choose File - Export - Export to GRAMPS Package. The - GRAMPS Package Export window will appear. Type - the desired package name into the text entry area or click - Browse... to select the file using the - Save File dialog. The resulting package is a - gzip-compressed tar archive (also known as tarball) which contains - gramps database, all local media objects, and copies of all external - media objects. + Exporting to &app; package will create a gzip-compressed tar + archive (also known as tarball) which contains gramps database, all + local media objects, and copies of all external media objects. This is a + useful format for moving your database to another machine or for sharing + it with somebody, while retaining all the features provided + by &app;. + - To import data from such a package into your &app; database, choose - FileImport - Import from GRAMPS package, - then select a package to be imported from the Import from - GRAMPS package dialog. + Exporting to CD will prepare you database directory with all its + contents to be recorded to the CD. This is done through + burn:/// location in Nautilus. After exporting to + CD, go to burn:/// location by + selecting Go + CD Creator in Nautilus menu. Your + database directory will show up. To record it onto the CD, click the CD + icon on the Nautilus toolbar, or select File + Write to CD in Nautilus menu. + - To import data from existing &app; database into your currently - open &app; database, choose File - ImportImport from GRAMPS - database, then select a directory which - contains the database to be imported from the Import from - GRAMPS database dialog. + If a media file is not found during export, the following dialog + will prompt you for the possible actions: - Note that the difference between opening &app; database and - importing from &app; database is that importing incorporates all the - data into your currently open database, if any. + +
+ Missing Media dialog + + + Shows Missing Media dialog. +
+ + + + + To remove the object corresponding to the missing file as well as + all the references to that object from various database records, click + Remove Object button. This will alter your + database so that it will be in a consistent state, but all the + references to the missing file will be gone. Use this option if the + file is irrevocably lost and there is no possibility of ever replacing + it. + + + + To keep the reference to the object corresponding to the missing + file, click Keep Reference button. + This will leave things as is, i.e. in an inconsistent state. + You could supply the missing file later, in which case you will have + to copy it into your database directory. Choose this option if the + replacement is possible, but not available right now. + + + To supply the missing file during export, click + Select File button. This will copy the file you + select in place of the missing file. No references will be altered + in the database, and it will be in the consistent state. Use this option + if the replacement is readily available. + + + @@ -2262,13 +2372,14 @@ Person from the database - If the person's data are stored in a database, click Person - is in the database box. Then ... - -[ FIXME: Need Don to decide which way this will eventually be implemented. ] - - - + If the person's data are stored in a database, check Person + is in the database box. Then enter GRAMPS ID into + ID text entry field. If the ID you entered is + found in the database, the Person field will + display the name of that person. Note: even though the + person's name might be displayed in the Person + field, it is not available for direct editing. + @@ -2916,8 +3027,8 @@ Researcher information Enter your personal information in the corresponding - text entry fields. Although GRAMPS requests information about you, - this information is used only so that it can create valid GEDCOM + text entry fields. Although &app; requests information about you, + this information is used only so that &app; can create valid GEDCOM output files. A valid GEDCOM file requires information about the file's creator. If you choose, you may leave the information empty, however all the GEDCOM files you export will not be valid.