Cyclone-Team/gramps
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Initial revision

Browse Source 
svn: r5226
This commit is contained in:
Don Allingham
2005-09-24 23:26:05 +00:00
parent 38e189191f
commit 483c215735
298 changed files with 32190 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
manual/.cvsignore Normal file
View File

@@ -0,0 +1,2 @@
Makefile.in
Makefile

4
manual/C/.cvsignore Normal file
View File

@@ -0,0 +1,4 @@
Makefile
Makefile.in
omf_timestamp
*.omf.out

18
manual/C/Makefile.am Normal file
View File

@@ -0,0 +1,18 @@
figdir = figures
docname = gramps-manual
lang = C
omffile = gramps-manual-C.omf
entities = legal.xml\
getstart.xml\
preface.xml\
mainwin.xml\
usage.xml\
custom.xml\
faq.xml\
keybind.xml\
filtref.xml\
cmdline.xml\
bugs.xml\
authors.xml
include $(top_srcdir)/doc/xmldocs.make
dist-hook: app-dist-hook

105
manual/C/authors.xml Normal file
View File

@@ -0,0 +1,105 @@
<appendix id="gramps-about">
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003-2005 Alexander Roitman
This document is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-->
<!-- $Id$ -->
<title>About GRAMPS</title>
<para> &app; was written by Donald N. Allingham
(<email>don@gramps-project.org</email>).</para>
<para>
The somewhat incomplete list of contributors includes (in alphabetical order):
<itemizedlist>
<listitem><para>Larry Allingham</para></listitem>
<listitem><para>Jens Arvidsson</para></listitem>
<listitem><para>Marcos Bedinelli</para></listitem>
<listitem><para>Douglas S. Blank</para></listitem>
<listitem><para>Radu Bogdan Mare</para></listitem>
<listitem><para>Alexander Bogdashevsky</para></listitem>
<listitem><para>Richard Bos</para></listitem>
<listitem><para>Nathan Bullock</para></listitem>
<listitem><para>Lorenzo Cappelletti</para></listitem>
<listitem><para>Pier Luigi Cinquantini</para></listitem>
<listitem><para>Bruce J. DeGrasse</para></listitem>
<listitem><para>Alexandre Duret-Lutz</para></listitem>
<listitem><para>Billy C. Earney</para></listitem>
<listitem><para>Baruch Even</para></listitem>
<listitem><para>Bernd Felsche</para></listitem>
<listitem><para>Egyeki Gergely</para></listitem>
<listitem><para>Michel Guitel</para></listitem>
<listitem><para>Steve Hall</para></listitem>
<listitem><para>David R. Hampton</para></listitem>
<listitem><para>Martin Hawlisch</para></listitem>
<listitem><para>Anton Huber</para></listitem>
<listitem><para>Frode Jemtland</para></listitem>
<listitem><para>Greg Kuperberg</para></listitem>
<listitem><para>Arkadiusz Lipiec</para></listitem>
<listitem><para>Lars Kr. Lundin</para></listitem>
<listitem><para>Radek Malcic</para></listitem>
<listitem><para>Leonid Mamtchenkov</para></listitem>
<listitem><para>Tino Meinen</para></listitem>
<listitem><para>Frederick Noronha</para></listitem>
<listitem><para>Jeffrey C. Ollie</para></listitem>
<listitem><para>Donald A. Peterson</para></listitem>
<listitem><para>Guillaume Pratte</para></listitem>
<listitem><para>Laurent Protois</para></listitem>
<listitem><para>Matthieu Pupat</para></listitem>
<listitem><para>Trevor Rhodes</para></listitem>
<listitem><para>Alexander Roitman</para></listitem>
<listitem><para>Jason Salaz</para></listitem>
<listitem><para>Julio Sanchez</para></listitem>
<listitem><para>Bernd Schandl</para></listitem>
<listitem><para>Martin Senftleben</para></listitem>
<listitem><para>Gary Shao</para></listitem>
<listitem><para>Jim Smart</para></listitem>
<listitem><para>Steve Swales</para></listitem>
<listitem><para>Eero Tamminen</para></listitem>
<listitem><para>Samuel Tardieu</para></listitem>
<listitem><para>Richard Taylor</para></listitem>
<listitem><para>James Treacy</para></listitem>
<listitem><para>Sebastian Voecking</para></listitem>
<listitem><para>Xing Wang</para></listitem>
<listitem><para>Tim Waugh</para></listitem>
<listitem><para>Jesper Zedlitz</para></listitem>
</itemizedlist>
If you know of somebody else who should be listed here, please let us know.
</para>
<para>
To find more information about &app;, please visit the
<ulink url="http://gramps.sourceforge.net" type="http">GRAMPS Project
Web page</ulink>. </para>
<para>
To report a bug or make a suggestion regarding this application or
this manual, use the help menu in &app;, or follow the directions
on <ulink url="http://gramps.sourceforce.net/contact.html" type="http">this site.</ulink>
</para>
<para> This program is distributed under the terms of the GNU
General Public license as published by the Free Software
Foundation; either version 2 of the License, or (at your option)
any later version. A copy of this license can be found at this
<ulink url="ghelp:gpl" type="help">link</ulink>, or in the file
COPYING included with the source code of this program. </para>
</appendix>

36
manual/C/bugs.xml Normal file
View File

@@ -0,0 +1,36 @@
<appendix id="mayapp-bugs">
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003-2005 Alexander Roitman
This document is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-->
<!-- $Id$ -->
<title>Known Bugs and Limitations</title>
<para>The known limitations include the BSDDB performance issues related
to caching and the memory size. As long as the BSDDB cache fits completely
into the available memory on the system, the performance should be
adequate. When the cache size exceeds that of the free memory and
portions of database cache start to be swapped onto the disk, the performance
degrades appreciably. This can be solved by adjusting the BSDDB cache
size for the large databases.
</para>
</appendix >

503
manual/C/cmdline.xml Normal file
View File

@@ -0,0 +1,503 @@
<appendix id="append-cmdline">
<!--
User Manual for GRAMPS - a GTK+/GNOME based genealogy program
Copyright (C) 2003-2005 Alexander Roitman
This document is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-->
<!-- $Id$ -->
<!-- =============== Appendices Subsection ================ -->
<title>Command line reference</title>
<para>This appendix provides the reference to the command line
capabilities available when launching &app; from the terminal. </para>
<note><para>&app; was designed to be an interactive
program. Therefore it uses graphical display and cannot run from the
true non-graphical console. It would take an enormous amount of effort
to enable it to run in a text-only terminal. This is why the set of
command line options does not aim to completely get rid of dependency
on the graphical display. Rather, it merely makes certain (typical) tasks
more convenient. It also allows one to execute these tasks from the scripts.
However, the graphical display must be accessible at all times!
</para></note>
<tip><para>To summarize, the use of the command line options provides
non-interactive behavior, but does not get rid of graphical display
dependency. Take it or leave it!
</para></tip>
<sect1 id="cmdline-options">
<title>Available options</title>
<para>This section provides the reference list of all command line
options available in &app;. If you want to know more than just
a list of options, see next sections: <xref linkend="cmdline-operation"/>
and <xref linkend="cmdline-examples"/>.
</para>
<sect2 id="cmdline-opt-format"><title>Format options</title>
<para> The format of any file destined for opening, importing,
or exporting can be specified with the
<command>-f <replaceable>format</replaceable></command>
option. The acceptable <replaceable>format</replaceable> values
are listed below.</para>
<variablelist>
<varlistentry><term>grdb</term>
<listitem><para> &app; database. This format is available
for opening, import, and export. When not specified, it can be
guessed if the filename ends with .grdb
</para></listitem></varlistentry>
<varlistentry><term>gramps-xml</term>
<listitem><para> &app; XML database. This format is available
for opening, import, and export. When not specified, it can be
guessed if the filename ends with .gramps
</para></listitem></varlistentry>
<varlistentry><term>gedcom</term>
<listitem><para> GEDCOM file. This format is available
for opening, import, and export. When not specified, it can be
guessed if the filename ends with .ged
</para></listitem></varlistentry>
<varlistentry><term>gramps-pkg</term>
<listitem><para> &app; package. This format is available
for import and export. When not specified, it can be
guessed if the filename ends with .gpkg
</para></listitem></varlistentry>
<varlistentry><term>geneweb</term>
<listitem><para> GeneWen file This format is available
for import and export. When not specified, it can be
guessed if the filename ends with .gw
</para></listitem></varlistentry>
<varlistentry><term>wft</term>
<listitem><para> Web Family Tree. This format is available
for export only. When not specified, it can be guessed
if the filename ends with .wft
</para></listitem></varlistentry>
<varlistentry><term>iso</term>
<listitem><para> CD image. This format is available
for export only. It must always be specified explicitly.
</para></listitem></varlistentry>
</variablelist>
</sect2>
<sect2 id="cmdline-opt-open"><title>Opening options</title>
<para>There are two ways to give &app; the name of the file to
be opened: </para>
<itemizedlist>
<listitem><para>supply bare file name</para></listitem>
<listitem><para>use the
<command>-O <filename>filename</filename></command> or
<command>-open=<filename>filename</filename></command> option
</para></listitem>
</itemizedlist>
<para>If the filename is given without any option flag, the attempt
to open the file will be made, and then the interactive &app; session
will be launched.
</para>
<tip><para>If no option is given, just the file name, &app; will
ignore the rest of the command line arguments. Use the -O flag
to open the file and do something with the data.
</para></tip>
<para>The format can be specified with the
<command>-f <replaceable>format</replaceable></command> or
<command>--format=<replaceable>format</replaceable></command>
option, immediately following the <filename>filename</filename>.
If not specified, the guess will be attempted based on
the <filename>filename</filename>.
</para>
<tip><para>Only grdb, gramps-xml,
and gedcom formats can be opened directly.
For other formats, you will need to use the import option
which will set up the empty database and then import data into it.
</para></tip>
<tip><para>Only a single file can be opened. If you need to combine
data from several sources, you will need to use
the import option.</para></tip>
</sect2>
<sect2 id="cmdline-opt-import"><title>Import options</title>
<para> The files destined for import can be specified with the
<command>-i <filename>filename</filename></command>
or <command>--import=<filename>filename</filename></command>
option. The format can be specified with the
<command>-f <replaceable>format</replaceable></command> or
<command>--format=<replaceable>format</replaceable></command>
option, immediately following the <filename>filename</filename>.
If not specified, the guess will be attempted based on
the <filename>filename</filename>.
</para>
<tip><para>More than one file can be imported in one command.
If this is the case, &app; will incorporate the data from
the next file into the database available at the moment.
</para></tip>
<para>When more than one input file is given, each has to be preceded
by <command>-i</command> flag. The files are imported in the
specified order, i.e. <command>
-i <filename>file1</filename>
-i <filename>file2</filename>
</command> and <command>
-i <filename>file2</filename>
-i <filename>file1</filename>
</command>
might produce different GRAMPS IDs in the resulting database.
</para></sect2>
<sect2 id="cmdline-opt-export"><title>Export options</title>
<para> The files destined for export can be specified with the
<command>-o <filename>filename</filename></command> or
<command>--output=<filename>filename</filename></command>
option. The format can be specified with the <command>-f</command>
option immediately following the <filename>filename</filename>.
If not specified, the guess will be attempted based on
the <filename>filename</filename>. For iso format,
the <filename>filename</filename>
is actually the name of directory the &app; database will be written
into. For grdb, gramps-xml, gedcom, wft, geneweb,
and gramps-pkg, the <filename>filename</filename>
is the name of the resulting file.
</para>
<tip><para>More than one file can be exported in one command.
If this is the case, &app; will attempt to write several files
using the data from the database available at the moment.
</para></tip>
<para> When more than one output file is given, each has to be
preceded by <command>-o</command> flag. The files are written one
by one, in the specified order.
</para></sect2>
<sect2 id="cmdline-opt-action"><title>Action options</title>
<para> The action to perform on the imported data can be
specified with the
<command>-a <replaceable>action</replaceable></command> or
<command>--action=<replaceable>action</replaceable></command>
option. This is done after all imports are successfully completed.
</para>
<para>Currently available actions are:</para>
<variablelist>
<varlistentry><term>summary</term>
<listitem><para>This action is the same as
<menuchoice><guimenu>Reports</guimenu><guisubmenu>View</guisubmenu>
<guimenuitem>Summary</guimenuitem></menuchoice>
</para></listitem></varlistentry>
<varlistentry><term>check</term>
<listitem><para>This action is the same as
<menuchoice><guimenu>Tools</guimenu>
<guisubmenu>Database Processing</guisubmenu>
<guimenuitem>Check and Repair</guimenuitem></menuchoice>.
</para> </listitem> </varlistentry>
<varlistentry><term>report</term>
<listitem><para>This action allows producing reports
from the command line. As reports generally have many options
of their own, this action should be followed by the report option
string. The string is given using the
<command>-p <replaceable>option_string</replaceable></command> or
<command>--options=<replaceable>option_string</replaceable></command>
option.
</para>
<tip><para>
The report option string should satisfy the following conditions:
</para>
<itemizedlist>
<listitem><para>It must not contain any spaces. If some arguments
need to include spaces, the string should be enclosed with
quotation marks.
</para></listitem>
<listitem><para>Option string must list pairs of option names
and values.
</para></listitem>
<listitem><para>Within a pair, option name and value must be
separated by the equal sign.
</para></listitem>
<listitem><para>Different pairs must be separated by commas.
</para></listitem>
</itemizedlist>
</tip>
<para>Most of the report options are specific for every report.
However, there some common options.
</para>
<variablelist>
<varlistentry><term>name=report_name</term>
<listitem> <para>
This mandatory option determines which report will be
generated. If the supplied report_name does not correspond
to any available report, the error message will be printed
followed by the list of available reports.
</para>
</listitem> </varlistentry>
<varlistentry><term>show=all</term>
<listitem> <para>
This will produce the list of names for all options available for
a given report.
</para>
</listitem> </varlistentry>
<varlistentry><term>show=option_name</term>
<listitem> <para>
This will print the description of the functionality supplied
by the option_name, as well as what are the acceptable types
and values for this option.
</para>
</listitem> </varlistentry>
</variablelist>
<para>
Use the above options to find out everything about a given report.
</para>
<tip><para>
If an option is not supplied, the last used value will be used.
If this report has never been generated before, then the
value from last generated report will be used when applicable.
Otherwise, the default value will be used.
</para></tip>
</listitem> </varlistentry>
</variablelist>
<para>When more than one output action is given, each has to be
preceded by <command>-a</command> flag. The actions are performed
one by one, in the specified order.
</para></sect2>
</sect1>
<sect1 id="cmdline-operation">
<title>Operation</title>
<itemizedlist>
<listitem>
<para>If the first argument on the command line does not start
with dash (i.e. no flag), &app; will attempt to open the file
with the name given by the first argument and start interactive
session, ignoring the rest of the command line arguments.
</para></listitem>
<listitem>
<para>If the <command>-O</command> flag is given, then &app; will
try opening the
supplied file name and then work with that data, as instructed by
the further command line parameters.
</para>
<note><para>Only one file can be opened in a single invocation
of &app;. If you need to get data from multiple sources, use
the importing options by using <command>-i</command> flag.
</para></note>
</listitem>
<listitem>
<para>With or without the <command>-O</command> flag, there could
be multiple imports, exports, and actions specified further on
the command line by using <command>-i</command>,
<command>-o</command>, and <command>-a</command> flags.
</para></listitem>
<listitem>
<para>The order of <command>-i</command>, <command>-o</command>,
or <command>-a</command> options with respect to each does not matter.
The actual execution order always is: all imports (if any) -> all
exports (if any) -> all actions (if any).</para>
<note><para>But opening must always be first!</para></note>
</listitem>
<listitem>
<para>If no <command>-O</command> or <command>-i</command>
option is given, &app; will launch
its main window and start the usual interactive session with the empty
database, since there is no data to process, anyway.
</para></listitem>
<listitem>
<para>If no <command>-o</command> or <command>-a</command> options
are given, &app; will launch its main window and start the usual
interactive session with the database resulted from opening
and all imports (if any). This database resides in the
<filename>import_db.grdb</filename> file under the
<filename>~/.gramps/import/</filename> directory.
</para></listitem>
<listitem>
<para>Any errors encountered during import, export, or action, will
be either dumped to stdout (if these are exceptions handled by &app;)
or or to stderr (if these are not handled). Use usual shell redirections
of stdout and stderr to save messages and errors in files.
</para></listitem>
</itemizedlist>
</sect1>
<sect1 id="cmdline-examples">
<title>Examples</title>
<variablelist>
<varlistentry>
<term>To import four databases (whose formats can be determined from
their names) and then check the resulting database for errors, one may
type:</term>
<listitem>
<para><command>gramps
-i<filename>file1.ged</filename>
-i <filename>file2.gpkg</filename>
-i <filename>~/db3.gramps</filename>
-i <filename>file4.wft</filename>
-a <filename>check</filename></command>
</para> </listitem></varlistentry>
<varlistentry>
<term>To explicitly specify the formats in the above example, append
filenames with appropriate <command>-f</command> options:</term>
<listitem>
<para><command>gramps
-i <filename>file1.ged</filename>
-f <replaceable>gedcom</replaceable>
-i <filename>file2.gpkg</filename>
-f <replaceable>gramps-pkg</replaceable>
-i <filename>~/db3.gramps</filename>
-f <replaceable>gramps-xml</replaceable>
-i <filename>file4.wft</filename>
-f <replaceable>wft</replaceable>
-a <replaceable>check</replaceable></command>
</para></listitem>
</varlistentry>
<varlistentry>
<term>To record the database resulting from all imports, supply
<command>-o</command> flag (use <command>-f</command>
if the filename does not allow &app; to guess the format):</term>
<listitem>
<para><command>gramps
-i <filename>file1.ged</filename>
-i <filename>file2.gpkg</filename>
-o <filename>~/new-package</filename>
-f <replaceable>gramps-pkg</replaceable></command>
</para></listitem>
</varlistentry>
<varlistentry>
<term>To save any error messages of the above example into files
<filename>outfile</filename> and
<filename>errfile</filename>, run:</term>
<listitem>
<para><command>gramps
-i <filename>file1.ged</filename>
-i <filename>file2.dpkg</filename>
-o <filename>~/new-package</filename>
-f <replaceable>gramps-pkg</replaceable>
&gt;<filename>outfile</filename>
2&gt;<filename>errfile</filename> </command>
</para></listitem>
</varlistentry>
<varlistentry>
<term>To import three databases and start interactive &app;
session with the result:</term>
<listitem>
<para><command>gramps
-i <filename>file1.ged</filename>
-i <filename>file2.gpkg</filename>
-i <filename>~/db3.gramps</filename>
</command>
</para> </listitem>
</varlistentry>
<varlistentry>
<term>To open a database and, based on that data, generate timeline
report in PDF format putting the output into the
<filename>my_timeline.pdf</filename> file:</term>
<listitem>
<para><command>gramps
-O <filename>file.grdb</filename>
-a <replaceable>report</replaceable>
-p <replaceable>name=timeline,off=pdf,of=my_timeline.pdf</replaceable>
</command>
</para>
<tip><para>Use the <replaceable>name=timeline,show=all</replaceable>
to find out about all available options for the timeline report. To
find out details of a particular option, use
<replaceable>show=option_name</replaceable>,
e.g. <replaceable>name=timeline,show=off</replaceable>
string.</para>
<para>To learn about available report names, use
<replaceable>name=show</replaceable> string.
</para>
</tip>
</listitem>
</varlistentry>
<varlistentry>
<term>Finally, to start normal interactive session type:</term>
<listitem><para> <command>gramps </command></para></listitem>
</varlistentry>
</variablelist>
</sect1>
</appendix>

291
manual/C/custom.xml Normal file
View File

@@ -0,0 +1,291 @@
<chapter id="gramps-settings">
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003-2005 Alexander Roitman
This document is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-->
<!-- $Id$ -->
<title>Settings</title>
<sect1 id="gramps-prefs">
<title>Preferences</title>
<para>Most of the settings in &app;, are configured in the
<guilabel>Preferences</guilabel> dialog. To invoke it, choose
<menuchoice><guimenu>Edit</guimenu>
<guimenuitem>Preferences...</guimenuitem></menuchoice>. </para>
<!-- ==== Figure: Type-ahead find ==== -->
<figure id="prefs-fig">
<title>Preferences dialog</title>
<screenshot><mediaobject><imageobject><imagedata
fileref="figures/prefs.png" format="PNG"/></imageobject>
<textobject>
<phrase>Shows Preferences dialog. </phrase>
</textobject></mediaobject></screenshot></figure>
<!-- ==== End of Figure ==== -->
<para>The pane on the left displays the tree of available option
categories. Selecting a tree node will display the corresponding
options in the right side of the dialog. </para>
<sect2 id="gramps-prefs-db">
<title>Database</title>
<para> This category contains preferences relevant to the
database itself. It has the following subcategories: </para>
<variablelist>
<varlistentry><term><guilabel>General</guilabel></term>
<listitem>
<variablelist>
<varlistentry><term><guilabel>Automatically
load last database</guilabel></term>
<listitem><para> Check this box to automatically load the
last open database on startup. </para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Family name guessing</guilabel></term>
<listitem><para> This option affects the initial family name of a
child when he/she is added to the database. </para>
<tip><para>This option only
affects the initial family name guessed by &app; when the
<guilabel>Edit Person</guilabel> dialog is launched. You can modify
that name the way you see fit. Set this option to the value that you
will most frequently use, as it will save you a lot of
typing.</para></tip>
<para>If <guilabel>None</guilabel> is selected, no guessing will be
attempted. Selecting <guilabel>Father's surname</guilabel> will use
the family name of the father. Selecting <guilabel>Combination of
mother's and father's surname</guilabel> will use the father's name
followed by the mother's name. Finally, <guilabel>Icelandic
style</guilabel> will use the father's given name followed by the
&quot;sson&quot; suffix (e.g. the son of Edwin will be guessed as
Edwinsson).
</para></listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry><term><guilabel>GRAMPS IDs</guilabel></term>
<listitem><para> Enter ID prefixes for various kinds of database
entries into the corresponding text entry fields.
</para>
<tip><para>The ID prefixes use formatting conventions common for
C, Python, and other programming languages. For example, the %04d
expands to an integer, prepended with zeros to have the total
width of four digits. If you would like IDs to be 1, 2, 3, etc,
simply set the formatting parameter to %d.
</para></tip>
</listitem>
</varlistentry>
<varlistentry><term><guilabel>Researcher Information</guilabel></term>
<listitem><para> 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
none of your exported GEDCOM files will be valid.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>
<sect2 id="gramps-prefs-display">
<title>Display</title>
<para> This category contains preferences relevant to
displaying database records and controls in &app;.
It has the following subcategories:</para>
<variablelist>
<varlistentry><term><guilabel>General</guilabel></term>
<listitem>
<variablelist>
<varlistentry><term><guilabel>Default view</guilabel></term>
<listitem><para> This determines which view will appear when
you start &app;. Choose between Person and Family views.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Family view style</guilabel></term>
<listitem><para> This selects between the two available styles
of the Family view layout. The <guilabel>Left to right</guilabel>
style is similar to the Family Tree Maker (tm), while the
<guilabel>Top to bottom</guilabel> is similar to the Reunion.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Always display the LDS ordinance
tabs</guilabel></term>
<listitem><para> Check this box to have LDS ordinance tabs
displayed. If you do not know what LDS is then you probably
should not check it. </para></listitem></varlistentry>
<varlistentry><term><guilabel>Display Tip of the
Day</guilabel></term>
<listitem><para> Check this box to have the <guilabel>Tip
of the Day</guilabel> dialog appear on every startup.
The tips are displayed randomly from the large collection
of information bits on &app;.
</para>
<tip><para>The <guilabel>Tip of the Day</guilabel> is likely
to be useful for new user of &app;.
</para></tip>
</listitem></varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry><term><guilabel>Dates</guilabel></term>
<listitem>
<para> Select the display format for the dates
from the available formats listed in this menu.
</para>
<tip><para>Available date display formats are language-specific.
Depending on whether or not there is a &app; date displayer
available for your language, you may or may not have a lot of
choices.
</para></tip>
</listitem>
</varlistentry>
<varlistentry><term><guilabel>Toolbar and Statusbar</guilabel></term>
<listitem>
<variablelist>
<varlistentry><term><guilabel>Toolbar</guilabel></term>
<listitem><para> Select the desired appearance of the toolbar
icons from the menu. Selecting <guilabel>GNOME
Settings</guilabel> will use the overall settings selected
for your GNOME desktop.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Statusbar</guilabel></term>
<listitem><para> Select the desired contents displayed in the
statusbar using the radio buttons.
</para></listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
</variablelist>
</sect2>
</sect1>
<sect1 id="gramps-prefs-other">
<title>Other settings</title>
<para>Besides <guilabel>Preferences</guilabel> dialog, there are
other settings available in &app;. For various reasons they have been
made more readily accessible, as listed below.</para>
<variablelist>
<varlistentry>
<term>Column Editor</term>
<listitem>
<para>The columns of the list views may be added, removed, or reordered
in a <guilabel>Column Editor Dialog</guilabel>,
see <xref linkend="column-editor-fig"/>. Only checked columns will
be shown in the view. To change their order, drag any column to its desired place inside
the editor. Clicking <guibutton>OK</guibutton> will reflect the changes
in the appropriate view. To invoke <guilabel>Column Editor Dialog</guilabel>,
choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Column
Editor...</guimenuitem></menuchoice>.
</para>
<tip>
<para>The <guilabel>Column Editor</guilabel> is available
and works in the same way for all list views.
Specifically, it is available for People View, Family View (children list).
Sources View, Places View, and Media View.</para> </tip>
</listitem>
</varlistentry>
<varlistentry><term>Setting Home person</term>
<listitem><para>The Home person is the person who becomes active
when database opened, when <guibutton>Home</guibutton> button is clicked
or the <guimenuitem>Home</guimenuitem> menu item is selected from
either <guimenu>Go</guimenu> menu or the right-click context menu
anywhere.</para>
<para>To set Home person, make the desired person active and
then choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Set Home
person...</guimenuitem></menuchoice>.</para>
</listitem>
</varlistentry>
<varlistentry><term>Adjusting viewing controls</term>
<listitem><para>Whether the toolbar, the sidebar, or the filter (People View
only) are displayed in the main window is adjusted through
the <guimenu>View</guimenu> menu.
</para></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="gramps-prefs-adv">
<title>Advanced manipulation of settings</title>
<warning><para>The contents of this section is outside the scope
of interest of a general user of &app;. If you proceed with tweaking
the options on the low level you may damage your &app; installation.
Be careful. YOU HAVE BEEN WARNED!
</para></warning>
<para>By default, &app; stores its settings using gconf2 system.
All the settings used in this version of &app; are stored in
subdirectories under <filename>/apps/gramps/</filename> in the
gconf2 namespace. Accessing the keys can be done either using
<command>gconftool-2</command> command line tool, or the
<command>gconf-editor</command> GUI tool.
</para>
<para>All keys are documented, and the notification mechanisms
are used as appropriate. Therefore, updating keys from outside
of &app; should lead to updating &app; in real time, without
necessarily restarting it.</para>
</sect1>
</chapter>

466
manual/C/faq.xml Normal file
View File

@@ -0,0 +1,466 @@
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003-2005 Alexander Roitman
This document is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-->
<!-- $Id$ -->
<appendix id="faq">
<title>Frequently Asked Questions</title>
<para>
This appendix contains the list of questions that frequently come
up in mailing list discussions and forums. This list is by no
means complete. If you would like to add questions/answers to this
list, please email your suggestions to <ulink
url="mailto:gramps-devel@lists.sf.net"
type="mailto">gramps-devel@lists.sf.net</ulink>
</para>
<variablelist>
<varlistentry>
<term>What is &app;?</term>
<listitem>
<para>
&app; is the Genealogical Research and Analysis Management
Program System. In other words, it is a personal genealogy
program letting you store, edit, and research genealogical
data using the powers of your computer.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Where do I get it and how much does it cost?</term>
<listitem>
<para>
&app; can be downloaded from <ulink
url="http://sf.net/projects/gramps"
type="http">http://sf.net/projects/gramps</ulink> at no
charge. &app; is an Open Source project covered by the GNU
General Public License. You have full access to the source
code and are allowed to distribute the program and source
code freely.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Does it work with Windows (tm)?</term>
<listitem>
<para>
No. &app; uses the GTK and GNOME libraries. While the GTK
libraries have been ported to Windows, the GNOME libraries
have not. This, however, may change in the future.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Does it work with the Mac?</term>
<listitem>
<para>
<ulink url="http://fink.sourceforge.net" type="http">
The Fink project</ulink> has ported
<ulink url="http://fink.sourceforge.net/pdb/package.php/gramps"
type="http"> some older versions</ulink> of
&app; to OSX (tm). The Mac OSX port is not directly supported by
the &app; project, primarily because none of the &app; developers
have access to Mac OSX and because OSX is not Free Software.
</para><para>
This version of &app; (&appversion;) does not appear to have been
ported by the Fink project. Please contact the Fink project for
more information.
</para><para>
Some people have had success using the DarwinPorts instead of the
Fink project.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Does it work with KDE?</term>
<listitem>
<para>
Yes, as long as the required GNOME libraries are installed.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Do I really have to have GNOME installed?</term>
<listitem>
<para>
Yes, but you do not have to be running the GNOME desktop.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>What version of GNOME do I need?</term>
<listitem>
<para>
This version of gramps requires GNOME 2.8.0 or higher.
Previous versions in 1.0.x series required GNOME 2.0.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Is &app; compatible with other genealogical software?</term>
<listitem>
<para>
&app; makes every effort to maintain compatibility with
GEDCOM, the general standard of recording genealogical
information. We have import and export filters that enable
&app; to read and write GEDCOM files.
</para><para>
It is important to understand that the GEDCOM standard is
poorly implemented -- virtually every genealogical software
has its own "flavor" of GEDCOM. As we learn about new
flavor, the import/export filters can be created very
quickly. However, finding out about the unknown flavors
requires user feedback. Please feel free to inform us about
any GEDCOM flavor not supported by &app;, and we will do our
best to support it!
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Can &app; read files created by other genealogy programs?</term>
<listitem>
<para>See above.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Can &app; write files readable by other genealogy programs?</term>
<listitem>
<para>See above.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Can &app; print a genealogical tree for my family?</term>
<listitem>
<para>
Yes. Different people have different ideas of what a
genealogical tree is. Some think of it as a chart going
from the distant ancestor and listing all his/her
descendants and their families. Others think it should be a
chart going from the person back in time, listing the
ancestors and their families. Yet other people think of a
table, text report, etc.
</para><para>
&app; can produce any of the above, and many more different
charts and reports. Moreover, the plugin architecture
enables users (you) to create their own plugins which could
be new reports, charts, or research tools.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>In what formats can &app; output its reports?</term>
<listitem>
<para>
Text reports are available in HTML, PDF, AbiWord, KWord,
LaTeX, RTF, and OpenOffice formats. Graphical reports
(charts and diagrams) are available in PostScript, PDF, SVG,
OpenOffice, and GraphViz formats.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Is &app; compatible with the Internet?</term>
<listitem>
<para>
&app; can store web addresses and direct your browser to
them. It can import data that you download from the
Internet. It can export data that you could send over the
Internet. &app; is familiar with the standard file formats
widely used on the Internet (e.g. JPEG, PNG, and GIF images,
MP3, OGG, and WAV sound files, QuickTime, MPEG, and AVI
movie files, etc). Other than that, there is little that a
genealogical program can do with the Internet.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Can I create custom reports/filters/whatever?</term>
<listitem>
<para>
Yes. There are many levels of customization. One is creating
or modifying the templates used for the reports. This gives
you some control over the fonts, colors, and some layout of
the reports. You can also use &app; controls in the report
dialogs to tell what contents should be used for a
particular report. In addition to this, you have an ability
to create your own filters -- this is useful in selecting
people based on criteria set by you. You can combine these
filters to create new, more complex filters. Finally, you
have an option to create your own plugins. These may be new
reports, research tools, import/export filters, etc. This
assumes some knowledge of programming in Python.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>What standards does &app; support?</term>
<listitem>
<para>
The nice thing about standards is that there never is a
shortage of them. &app; is tested to support the following
flavors of GEDCOM: GEDCOM5.5, Brother's Keeper, Family
Origins, Family Tree Maker, Ftree, GeneWeb, Legacy, Personal
Ancestral File, Pro-Gen, Reunion, and Visual Genealogie.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>What is the maximum database size (bytes) &app; can handle?</term>
<listitem>
<para>
&app; has no hard limits on the size of a database that it
can handle. Starting with this release, &app; no longer
loads all data into memory, which allows it to work with a
much larger database than before. In reality, however,
there are practical limits. The main limiting factors are
the available memory on the system and the cache size used
for BSDDB database access. With common memory sizes these
days, &app; should have no problem using databases with tens
of thousands of people.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>How many people can &app; database handle?</term>
<listitem>
<para>
We have found that on a typical system, &app; tends to bog
down after the database has around 150,000 people. Again,
this is dependent on how much memory you have.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Why is &app; running so slowly?</term>
<listitem>
<para>
It does not anymore! Just try out the current
version, &appversion;.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
My database is really big. Is there a way around loading
all the data into memory?
</term>
<listitem>
<para>
Starting with this release, &app; no longer loads all data
into memory, which allows it to work with a much larger
database than before.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>I want to rerun the Startup dialog. How do I do this?</term>
<listitem>
<para>
&app; keeps a flag in the GNOME configuration database to
indicate that the startup dialog has been run. To cause
&app; to rerun this, the flag needs to be reset. This can be
done with the following command:
</para>
<para>
<command>gconftool-2 -u /apps/gramps/behavior/startup</command>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
Why are non-latin characters displayed as garbage in PDF/PS
reports?
</term>
<listitem>
<para>
This is a limitation of the builtin fonts of PS and PDF
formats. To print non-latin text, use the Print... in the
format selection menu of the report dialog. This will use
the gnome-print backend, which supports PS and PDF creation,
as well as direct printing.
</para>
<para>
If you only have latin text, the PDF option will produce a
smalled PDF compared to that created by gnome-print, simply
because no font information will be embedded.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
Why can I not add/remove/edit columns to the lists in People
View and Family View?
</term>
<listitem>
<para>
Now you can! Just try out the current version, &appversion;.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
I would like to contribute to &app; by writing my favorite
report. How do I do that?
</term>
<listitem>
<para>
The easiest way to contribute to reports, filters, tools,
etc. is to copy an existing &app; report, filter, or
tool. If you can create what you want by modifying existing
code -- great! If your idea does not fit into the logic of
any existing &app; tool, the <ulink
url="http://gramps.sourceforge.net/phpwiki/index.php/GrampsDevelopersPage"
type="http">following page</ulink> may provide some help in
writing your own plugin from scratch.
</para>
<para>
If you need more help or would like to discuss your idea
with us, please do not hesitate to contact us at <ulink
url="mailto:gramps-devel@lists.sf.net"
type="mailto">gramps-devel@lists.sf.net</ulink>
</para>
<para>
To test your work in progress, you may save your plugin
under <replaceable>$HOME/.gramps/plugins</replaceable>
directory and it should be found and imported on startup.
The correctly written plugin will register itself with
&app;, create menu item, and so on.
</para>
<para>
If you are happy with your plugin and would like to
contribute your code back to the &app; project, you are very
welcome to do so by contacting us at <ulink
url="mailto:gramps-devel@lists.sf.net"
type="mailto">gramps-devel@lists.sf.net</ulink>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
I found a bug and I want it fixed right now! What do I do?
</term>
<listitem>
<para>
The best thing you can do is to fix the bug and send the
patch to <ulink url="mailto:gramps-devel@lists.sf.net"
type="mailto">gramps-devel@lists.sf.net</ulink> :-)
</para>
<para>A good bug report would include:</para>
<itemizedlist>
<listitem>
<para>
Version of gramps you were using when you encountered
the bug (available through
<menuchoice><guisubmenu>Help</guisubmenu>
<guimenuitem>About</guimenuitem></menuchoice> menu
item).
</para>
</listitem>
<listitem>
<para>
Language under which gramps was run (available by executing
</para>
<para><command>echo $LANG</command></para>
<para>in your terminal).</para>
</listitem>
<listitem>
<para>Symptoms indicating that this is indeed a bug.</para>
</listitem>
<listitem>
<para>
Any Traceback messages, error messages, warnings, etc,
that showed up in your terminal or a in separate
traceback window.
</para>
</listitem>
</itemizedlist>
<para>
Most problems can be fixed quickly provided there is enough
information. To ensure this, please follow up on your bug
reports. In particular, if you file a bug report with sf.net
bug tracker, PLEASE log in to sf.net before filing (register
your free account if you don't have one). Then we will have
a way of contacting you should we need more information. If
you choose to file your report anonymously, at least check
every so often whether your report page has something new
posted, as it probably would.
</para>
<para>
If the above explanations seem vague, please follow <ulink
url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
type="http">this link.</ulink>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
It is obvious that &app; absolutely needs to become a
(client-server/web-based/PHP/weblog/Javascript/C++/distributed/KDE/Motif/Tcl/Win32/C#/You-name-it)
application. When is this going to happen?
</term>
<listitem>
<para>
The surest way to see it happen is to get it done by
yourself. Since &app; is free/open source, nobody prevents
you from taking all of the code and continuing its
development in whatever direction you see fit. In doing so,
you may consider giving your new project another name to
avoid confusion with the continuing &app; development. If
you would like the &app; project to provide advice,
expertise, filters, etc., we will gladly cooperate with your
new project, to ensure compatibility or import/export
options to your new format of a project.
</para>
<para>
If, however, you would like the &app; project to to adopt
your strategy, you would need to convince &app; developers
that your strategy is good for &app; and superior to the
present development strategy.
</para>
</listitem>
</varlistentry>
</variablelist>
</appendix>

BIN
manual/C/figures/bookreport.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/cfe-ar.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/cfe-df.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/column-editor.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/comp-people.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/date-selection.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-ad.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-an.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-at.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-bm.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-ev.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-media.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-person-addresses.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-person-attributes.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-person-events.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-person-gallery.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-person-internet.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-person-lds.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-person-names.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-person-notes.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-person-sources.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-person.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-plc.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-rel.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-si.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-src.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/edit-wi.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/export-druid.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/family-alt.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/family.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/find-people.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/first-open.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/gedcom-export-progress.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/gedcom-export.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/gedcom-import.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/mainwin.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/media.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/merge-people.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/merge-plc.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/merge-src.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/missing-media.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/noside-nofilt.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/pedigree-anchor.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/pedigree-child-cut.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/pedigree-siblings-cut.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/pedigree.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/places.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/prefs.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/researcher.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/scratch-pad.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/side-filt.png Normal file
View File

Binary file not shown.

BIN
manual/C/figures/sources.png Normal file
View File

Binary file not shown.

499
manual/C/filtref.xml Normal file
View File

@@ -0,0 +1,499 @@
<appendix id="append-filtref">
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003-2005 Alexander Roitman
This document is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-->
<!-- $Id$ -->
<title>Filter rules reference</title>
<para>This appendix lists of all the filter rules currently defined
in &app;. Each of these rules is available for use when creating custom
filters, see <xref linkend="tools-util-cfe"/>. The rules are
listed by their categories.
</para>
<!-- =============== Appendices Sub-subsection ================ -->
<sect1 id="filtref-general">
<title>General filters</title>
<para>This category includes the following most general rules:</para>
<variablelist>
<varlistentry><term>Has complete record</term>
<listitem><para> This rule matches all people whose records are
marked as complete. Currently, the completeness of personal
information is marked manually, in the <guilabel>Edit Person</guilabel>
dialog.
</para></listitem>
</varlistentry>
<varlistentry><term>People with incomplete names</term>
<listitem><para> This rule matches all people with either
given name or family name missing.
</para></listitem>
</varlistentry>
<varlistentry><term>Is bookmarked person</term>
<listitem><para> This rule matches all people who are on the
bookmark list.
</para></listitem>
</varlistentry>
<varlistentry><term>Has text matching substring of</term>
<listitem><para> This rule matches all people whose records contain
specified substring. All textual records are searched. Optionally,
the search can be made case sensitive, or a regular expression
match.
</para></listitem>
</varlistentry>
<varlistentry><term>Everyone</term>
<listitem><para> This rule matches any person in the database.
As such it is not very useful on its own except for testing purposes.
However, it may be useful in combinations with other rules.
</para></listitem>
</varlistentry>
<varlistentry><term>People probably alive</term>
<listitem><para> This rule matches all people whose records do
not indicate their death and who are not unreasonably old,
judging by their available birth data and today's date.
</para></listitem>
</varlistentry>
<varlistentry><term>Has a name</term>
<listitem><para> This rule matches any person whose name
matches the specified value in full or in part. For example,
Marta Ericsdotter will be matched by the rule using the
value "eric" for the family name.
</para>
<para> Separate values can be used for Given name, Family name,
Suffix, and the Title. The rule returns a match if, and only if,
all non-empty values are (partially) matched by a person's
name. To use just one value, leave the other values empty.
</para></listitem>
</varlistentry>
<varlistentry><term>Has the Id</term>
<listitem><para> This rule matches any person with a specified
&app; ID. The rule returns a match only if the ID is matched
exactly.
</para>
<para> You can either enter the ID into a text entry field, or
select a person from the list by clicking
<guibutton>Select...</guibutton> button. In the latter case, the
ID will appear in the text field after the selection was made.
</para></listitem>
</varlistentry>
<varlistentry><term>Is default person</term>
<listitem><para> This rule matches the default (home) person.
</para></listitem>
</varlistentry>
<varlistentry><term>People marked private</term>
<listitem><para> This rule matches people whose records are marked
as private.
</para></listitem>
</varlistentry>
<varlistentry><term>Is a female</term>
<listitem><para> This rule matches any female person.
</para></listitem>
</varlistentry>
<varlistentry><term>People who have images</term>
<listitem><para> This rule matches people with images in their
galleries.
</para></listitem>
</varlistentry>
<varlistentry><term>People without a birth date</term>
<listitem><para> This rule matches people missing birth date.
</para></listitem>
</varlistentry>
<varlistentry><term>Is a male</term>
<listitem><para> This rule matches any male person.
</para></listitem>
</varlistentry>
</variablelist>
</sect1>
<!-- =============== Appendices Sub-subsection ================ -->
<sect1 id="filtref-event">
<title>Event filters</title>
<para>This category includes the following rules that match people
based on their recorded events:</para>
<variablelist>
<varlistentry><term>Has the birth</term>
<listitem><para> This rule matches people whose birth event
matches specified values for Date, Place, and Description.
The rule returns a match even if the person's birth event matches
the value partially. The matching rules are case-insensitive.
For example, anyone born in Sweden will be matched by the rule
using the value "sw" for the Place.
</para>
<para> The rule returns a match if, and only if,
all non-empty values are (partially) matched by a person's
birth. To use just one value, leave the other values empty.
</para></listitem>
</varlistentry>
<varlistentry><term>Has the death</term>
<listitem><para> This rule matches people whose death event
matches specified values for Date, Place, and Description.
The rule returns a match even if the person's death event
matches the value partially. The matching rules are case-insensitive.
For example, anyone who died in Sweden
will be matched by the rule using the value "sw" for the Place.
</para>
<para> The rule returns a match if, and only if,
all non-empty values are (partially) matched by a person's
death. To use just one value, leave the other values empty.
</para></listitem>
</varlistentry>
<varlistentry><term>Has source of</term>
<listitem><para> This rule matches people whose records refer
to the specified source.
</para></listitem>
</varlistentry>
<varlistentry><term>Has the personal event</term>
<listitem><para> This rule matches people that have a personal
event matching specified values for the Event type, Date, Place,
and Description. The rule returns a match even if the person's
event matches the value partially. The matching rules are
case-insensitive. For example, anyone who graduated
in Sweden will be matched by the rule using the Graduation event
and the value "sw" for the Place.
</para>
<para> The personal events should be selected from a pull-down menu.
The rule returns a match if, and only if, all non-empty values
are (partially) matched by the personal event.
To use just one value, leave the other values empty.
</para></listitem>
</varlistentry>
<varlistentry><term>Has the family event</term>
<listitem><para> This rule matches people that have a family
event matching specified values for the Event type, Date, Place,
and Description. The rule returns a match even if the person's
event matches the value partially. The matching rules are
case-insensitive. For example, anyone who was married in Sweden
will be matched by the rule using the Marriage event and the
value "sw" for the Place.
</para>
<para> The family events should be selected from a pull-down menu.
The rule returns a match if, and only if, all non-empty values
are (partially) matched by the personal event.
To use just one value, leave the other values empty.
</para></listitem>
</varlistentry>
<varlistentry><term>Witness</term>
<listitem><para> This rule matches people who are present as
a witness in the event. If the personal or family event type is
specified, only the events of this type will be searched.
</para></listitem>
</varlistentry>
<varlistentry><term>People with incomplete events</term>
<listitem><para> This rule matches people missing date or place in
any personal event.
</para></listitem>
</varlistentry>
<varlistentry><term>Families with incomplete events</term>
<listitem><para> This rule matches people missing date or place in
any family event of any of their families.
</para></listitem>
</varlistentry>
</variablelist>
</sect1>
<!-- =============== Appendices Sub-subsection ================ -->
<sect1 id="filtref-family">
<title>Family filters</title>
<para>This category includes the following rules that match people
based on their family relationships:</para>
<variablelist>
<varlistentry><term>People with children</term>
<listitem><para> This rule matches people with children.
</para></listitem>
</varlistentry>
<varlistentry><term>People with multiple marriage records</term>
<listitem><para> This rule matches people with more than one spouse.
</para></listitem>
</varlistentry>
<varlistentry><term>People with no marriage records</term>
<listitem><para> This rule matches people with no spouses.
</para></listitem>
</varlistentry>
<varlistentry><term>People who were adopted</term>
<listitem><para> This rule matches adopted people.
</para></listitem>
</varlistentry>
<varlistentry><term>Has the relationships</term>
<listitem><para> This rule matches people with a particular
relationship. The relationship must match the type selected from
the menu. Optionally, the number of relationships and the number
of children can be specified.
</para>
<para> The rule returns a match if, and only if,
all non-empty values are (partially) matched by a person's
relationship. To use just one value, leave the other values empty.
</para></listitem>
</varlistentry>
<varlistentry><term>Is spouse of filter match</term>
<listitem><para> This rule matches people married to someone
who is matched by the specified filter.
The specified filter name should be selected from the menu.
</para></listitem>
</varlistentry>
<varlistentry><term>Is a child of filter match</term>
<listitem><para> This rule matches people for whom either parent
is matched by the specified filter.
The specified filter name should be selected from the menu.
</para></listitem>
</varlistentry>
<varlistentry><term>Is a parent of filter match</term>
<listitem><para> This rule matches people whose child
is matched by the specified filter.
The specified filter name should be selected from the menu.
</para></listitem>
</varlistentry>
<varlistentry><term>Is a sibling of filter match</term>
<listitem><para> This rule matches people whose sibling
is matched by the specified filter.
The specified filter name should be selected from the menu.
</para></listitem>
</varlistentry>
</variablelist>
</sect1>
<!-- =============== Appendices Sub-subsection ================ -->
<sect1 id="filtref-ancestral">
<title>Ancestral filters</title>
<para>This category includes the following rules that match people
based on their ancestral relations to other people:</para>
<variablelist>
<varlistentry><term>Is an ancestor of</term>
<listitem><para> This rule matches people who are ancestors of the
specified person. The Inclusive option determines whether the
specified person should be considered his/her own ancestor (useful
for building reports).
</para>
<para> You can either enter the ID into a text entry field, or
select a person from the list by clicking
<guibutton>Select...</guibutton> button. In the latter case, the
ID will appear in the text field after the selection was made.
</para></listitem>
</varlistentry>
<varlistentry><term>Is an ancestor of person at
least N generations away</term>
<listitem><para> This rule matches people who are ancestors of the
specified person and are at least N generations away from that person
in their lineage. For example, using this rule with the value of 2
for the number of generations will match grandparents,
great-grandparents, etc., but not the parents of the specified
person.
</para></listitem>
</varlistentry>
<varlistentry><term>Is an ancestor of person not more
than N generations away</term>
<listitem><para> This rule matches people who are ancestors of the
specified person and are no more than N generations away from that
person in their lineage. For example, using this rule with the value
of 2 for the number of generations will match parents and
grandparents, but not great-grandparents, etc., of the specified
person.
</para></listitem>
</varlistentry>
<varlistentry><term>Has a common ancestor with</term>
<listitem><para> This rule matches people who have common ancestors
with the specified person.
</para></listitem>
</varlistentry>
<varlistentry><term>Has a common ancestor with filter match</term>
<listitem><para> This rule matches people who have common ancestors
with someone who is matched by the specified filter.
The specified filter name should be selected from the menu.
</para></listitem>
</varlistentry>
<varlistentry><term>Is an ancestor of filter match</term>
<listitem><para> This rule matches people who are ancestors
of someone who is matched by the specified filter.
The specified filter name should be selected from the menu.
</para></listitem>
</varlistentry>
</variablelist>
</sect1>
<!-- =============== Appendices Sub-subsection ================ -->
<sect1 id="filtref-descendant">
<title>Descendant filters</title>
<para>This category includes the following rules that match people
based on their descendant relations to other people:</para>
<variablelist>
<varlistentry><term>Is a descendant of</term>
<listitem><para> This rule matches people who are descendants of the
specified person. The Inclusive option determines whether the
specified person should be considered his/her own descendant (useful
for building reports).
</para>
<para> You can either enter the ID into a text entry field, or
select a person from the list by clicking
<guibutton>Select...</guibutton> button. In the latter case, the
ID will appear in the text field after the selection was made.
</para></listitem>
</varlistentry>
<varlistentry><term>Is a descendant of person at
least N generations away</term>
<listitem><para> This rule matches people who are descendants of the
specified person and are at least N generations away from that person
in their lineage. For example, using this rule with the value of 2
for the number of generations will match grandchildren,
great-grandchildren, etc., but not the children of the specified
person.
</para></listitem>
</varlistentry>
<varlistentry><term>Is a descendant of person not more
than N generations away</term>
<listitem><para> This rule matches people who are descendants of the
specified person and are no more than N generations away from that
person in their lineage. For example, using this rule with the value
of 2 for the number of generations will match children and
grandchildren, but not great-grandchildren, etc., of the specified
person.
</para></listitem>
</varlistentry>
<varlistentry><term>Is a descendant of filter match</term>
<listitem><para> This rule matches people who are descendants
of someone who is matched by the specified filter.
The specified filter name should be selected from the menu.
</para></listitem>
</varlistentry>
<varlistentry><term>Is a descendant family member of</term>
<listitem><para> This rule not only matches people who are
descendants of the specified person, but also those descendants'
spouses.
</para></listitem>
</varlistentry>
</variablelist>
</sect1>
<!-- =============== Appendices Sub-subsection ================ -->
<sect1 id="filtref-relat">
<title>Relationship filters</title>
<para>This category includes the following rules that match people
based on their mutual relationship:</para>
<variablelist>
<varlistentry><term>Relationship path between two people</term>
<listitem><para> This rule matches all ancestors of both people
back to their common ancestors (if exist). This produces the
&quot;relationship path&quot; between these two people, through
their common ancestors.
</para>
<para> You can either enter the ID of each person into the
appropriate text entry fields, or select people from the list by
clicking their <guibutton>Select...</guibutton> buttons. In the
latter case, the ID will appear in the text field after the
selection was made.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>
<!-- =============== Appendices Sub-subsection ================ -->
<sect1 id="filtref-misc">
<title>Miscellaneous filters</title>
<para>This category includes the following rules which do not
naturally fit into any of the above categories:</para>
<variablelist>
<varlistentry><term>Has the personal attribute</term>
<listitem><para> This rule matches people who have the personal
attribute of the specified value. The specified personal attribute
name should be selected from the menu. The specified value should
be typed into the text entry field.
</para></listitem>
</varlistentry>
<varlistentry><term>Has the family attribute</term>
<listitem><para> This rule matches people who have the family
attribute of the specified value. The specified family attribute
should be selected from the menu. The specified value should be
typed into the text entry field.
</para></listitem>
</varlistentry>
<varlistentry><term>Matches the filter named</term>
<listitem><para> This rule matches people who are matched
by the specified filter.
The specified filter name should be selected from the menu.
</para></listitem>
</varlistentry>
</variablelist>
</sect1>
</appendix>

258
manual/C/getstart.xml Normal file
View File

@@ -0,0 +1,258 @@
<chapter id="gramps-getting-started">
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003-2005 Alexander Roitman
This document is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-->
<!-- $Id$ -->
<title>Getting Started</title>
<para>
This chapter provides the most basic information on starting
&app; and obtaining help. Please proceed to the following
chapters for more information.
</para>
<!-- ================ Getting Started Subsection ====== -->
<sect1 id="gramps-start">
<title>To Start GRAMPS</title>
<para>
You can start &app; in the following ways:
</para>
<variablelist>
<varlistentry>
<term><guimenu>Applications</guimenu> menu</term>
<listitem>
<para>
The method of starting &app; from the menus may vary
from distribution to distribution. On default GNOME
desktop, choose
<menuchoice><guisubmenu>Other</guisubmenu>
<guimenuitem>Gramps</guimenuitem></menuchoice>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Command line</term>
<listitem>
<para>
To start &app; from a command line, type
<command>gramps</command>, then press
<keycap>Enter</keycap>.
</para>
<para>
If you would like &app; to open a specific database or to
import a specific file on startup, you can use the
filename as a command line argument:
</para>
<para>
<filename>gramps filename.grdb</filename>
</para>
<para>
where <filename>filename.grdb</filename> is the name of
the file you want to open. The command line provides many
more ways to start &app; and perform different tasks. The
detailed reference to the command line options is found
in <xref linkend="append-cmdline"/>.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>
<!-- ================ Getting Started Subsection ==== -->
<sect1 id="run-1st-time">
<title>Running GRAMPS for the first time</title>
<para>
The first time you run the program, GRAMPS will display the
Getting Started dialogs. Follow the directions that guide you through
<guilabel>Researcher information</guilabel>, <guilabel>Numerical date
formats</guilabel>, <guilabel>Alternate calendar support</guilabel>,
and <guilabel>the LDS extensions</guilabel> sections. Most of the dialogs
are self-explanatory and will not be covered here.
</para>
<!-- ==== Figure: Getting Started Druid Window ==== -->
<figure id="druid-fig">
<title>GRAMPS Getting Started Window: Researcher Information</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/researcher.png" format="PNG"
width="510" depth="369" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows Researcher Information Window. </phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
<para>
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 be invalid.
</para>
<para>
This information can be entered at any time in the
<guilabel>Preferences</guilabel> dialog, under the
<guilabel>Database/Researcher Information</guilabel> category.
</para>
</sect1>
<!-- ================ Getting Started Subsection -->
<sect1 id="choose-db-start">
<title>Choosing a database on startup</title>
<para>
If &app; is started without a database selected, the following
window will appear prompting you to choose one to open.
</para>
<!-- ==== Figure: Open existing/new database window ==== -->
<figure id="first-open">
<title>Open Database Window</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/first-open.png" format="PNG"
width="311" depth="199" scale="80"/>
</imageobject>
<textobject>
<phrase>Shows Open Database Window.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
<para>
If you would like to open an existing database, check the top
radio button and click the <guibutton>OK</guibutton>
button. You will then be asked to specify the name of your
existing database. If you would like to immediately create a
brand new database from scratch right away, choose new
database.
</para>
<note id="file-notdir-note">
<title>Selecting file</title>
<para>
This version of &app; does not require selecting a directory
for the database. Please select filename, as you would in any
other application.
</para>
</note>
</sect1>
<!-- ================ Getting Started Subsection ==== -->
<sect1 id="get-help">
<title>Obtaining Help</title>
<para>
The following items are available from the
<menuchoice><guimenu>Help</guimenu></menuchoice> to provide
immediate assistance:
</para>
<variablelist>
<varlistentry>
<term>User manual</term>
<listitem>
<para>
Select this item to access this manual in the help browser.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FAQ</term>
<listitem>
<para>
Select this item to read the Frequently Asked Questions about
&app; in the browser.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>GRAMPS home page</term>
<listitem>
<para>
Select this item to open the home page of &app; in your
default web browser.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>GRAMPS mailing lists</term>
<listitem>
<para>
Select this item to direct your web browser
to the &app; mailing list archives.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Report a bug</term>
<listitem>
<para>
Select this item to file a bug report regarding &app;
with the bug tracking system.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Show plugin status</term>
<listitem>
<para>
Select this item to display the status of loaded plugins.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Open example database</term>
<listitem>
<para>
Select this item to load the example database shipped
with &app;. This database is composed of fictitious
people and serves as a useful example for learning how
to work with &app;.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>
</chapter>

18
manual/C/gramps-manual-C.omf Normal file
View File

@@ -0,0 +1,18 @@
<?xml version="1.0" encoding="UTF-8"?>
<omf>
<resource>
<creator>Alex Roitman shura@alex.neuro.umn.edu</creator>
<title>GRAMPS Manual</title>
<date>2003-12-01</date>
<version identifier="2.4" date="2003-12-01" description="GNOME2 Compliant GRAMPS Manual"/>
<subject category="GNOME|Applications"/>
<description>User Manual for GRAMPS.</description>
<type>User Manual</type>
<format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/>
<identifier url=""/>
<language code="C"/>
<relation seriesid="aa15a444-5ed9-11d7-8329-d7319c90009c"/>
<rights type="GNU FDL" license.version="1.1" license="http://www.gnu.org/licenses/fdl.html" holder="Alex Roitman"/>
</resource>
</omf>

271
manual/C/gramps-manual.xml Normal file
View File

@@ -0,0 +1,271 @@
<?xml version="1.0" encoding="UTF-8"?>
<?yelp:chunk-depth 3?>
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003-2005 Alexander Roitman
This document is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-->
<!-- $Id$ -->
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
<!-- Information about the entities
The legal.xml file contains legal information, there is no need to edit the file.
Use the appversion entity to specify the version of the application.
Use the manrevision entity to specify the revision number of this manual.
Use the date entity to specify the release date of this manual.
Use the app entity to specify the name of the application. -->
<!ENTITY legal SYSTEM "legal.xml">
<!ENTITY appversion "2.0.0">
<!ENTITY manrevision "2.6">
<!ENTITY date "Aug 2005">
<!ENTITY app "GRAMPS">
<!-- The rest of the entities is simply the chapters of the manual.. -->
<!ENTITY preface SYSTEM "preface.xml">
<!ENTITY getstart SYSTEM "getstart.xml">
<!ENTITY mainwin SYSTEM "mainwin.xml">
<!ENTITY usage SYSTEM "usage.xml">
<!ENTITY custom SYSTEM "custom.xml">
<!ENTITY faq SYSTEM "faq.xml">
<!ENTITY keybind SYSTEM "keybind.xml">
<!ENTITY filtref SYSTEM "filtref.xml">
<!ENTITY cmdline SYSTEM "cmdline.xml">
<!ENTITY bugs SYSTEM "bugs.xml">
<!ENTITY authors SYSTEM "authors.xml">
]>
<!--
(Do not remove this comment block.)
Maintained by the GNOME Documentation Project
http://developer.gnome.org/projects/gdp
Template version: 2.0 beta
Template last modified Apr 11, 2002
-->
<!-- =============Document Header ============================= -->
<book id="index" lang="en">
<!-- please do not change the id; for translations, change lang to -->
<!-- appropriate code -->
<bookinfo>
<title>GRAMPS Manual V&manrevision;</title>
<copyright>
<year>2001</year>
<holder>Donald N. Allingham</holder>
</copyright>
<copyright>
<year>2003-2005</year>
<holder>Alex Roitman</holder>
</copyright>
<!-- translators: uncomment this:
<copyright>
<year>2002</year>
<holder>ME-THE-TRANSLATOR (Latin translation)</holder>
</copyright>
-->
<!--
An address can be added to the publisher information. If a role is
not specified, the publisher/author is the same for all versions of the
document.
-->
<publisher>
<publishername>GRAMPS Project</publishername>
</publisher>
&legal;
<!--
This file contains link to license for the documentation (GNU GPL), and
other legal stuff such as "NO WARRANTY" statement.
-->
<authorgroup>
<author>
<firstname>Alex</firstname>
<surname>Roitman</surname>
<affiliation>
<orgname>GRAMPS Project</orgname>
<address><email>shura@gramps-project.org</email></address>
</affiliation>
</author>
<author>
<firstname>Donald N.</firstname>
<surname>Allingham</surname>
<affiliation>
<orgname>GRAMPS Project</orgname>
<address><email>don@gramps-project.org</email></address>
</affiliation>
</author>
<!-- This is appropriate place for other contributors: translators,
maintainers, etc. Commented out by default.
<othercredit role="translator">
<firstname>Latin</firstname>
<surname>Translator 1</surname>
<affiliation>
<orgname>Latin Translation Team</orgname>
<address> <email>translator@gnome.org</email> </address>
</affiliation>
<contrib>Latin translation</contrib>
</othercredit>
-->
</authorgroup>
<!-- According to GNU GPL, revision history is mandatory if you are -->
<!-- modifying/reusing someone else's document. If not, you can omit it. -->
<!-- Remember to remove the &manrevision; entity from the revision entries other
-->
<!-- than the current revision. -->
<!-- The revision numbering system for GNOME manuals is as follows: -->
<!-- * the revision number consists of two components -->
<!-- * the first component of the revision number reflects the release version of the GNOME desktop. -->
<!-- * the second component of the revision number is a decimal unit that is incremented with each revision of the manual. -->
<!-- For example, if the GNOME desktop release is V2.x, the first version of the manual that -->
<!-- is written in that desktop time frame is V2.0, the second version of the manual is V2.1, etc. -->
<!-- When the desktop release version changes to V3.x, the revision number of the manual changes -->
<!-- to V3.0, and so on. -->
<revhistory>
<revision>
<revnumber>GRAMPS Manual V&manrevision;</revnumber>
<date>&date;</date>
<revdescription>
<para role="author">Alex Roitman
<email>shura@gramps-project.org</email>
</para>
<para role="publisher">GRAMPS Project</para>
</revdescription>
</revision>
<revision>
<revnumber>GRAMPS Manual V2.5</revnumber>
<date>February 2004</date>
<revdescription>
<para role="author">Alex Roitman
<email>shura@gramps-project.org</email>
</para>
<para role="publisher">GRAMPS Project</para>
</revdescription>
</revision>
<revision>
<revnumber>GRAMPS Manual V2.4</revnumber>
<date>December 2003</date>
<revdescription>
<para role="author">Alex Roitman
<email>shura@gramps-project.org</email>
</para>
<para role="publisher">GRAMPS Project</para>
</revdescription>
</revision>
<revision>
<revnumber>GRAMPS Manual V2.3</revnumber>
<date>September 2003</date>
<revdescription>
<para role="author">Alex Roitman
<email>shura@gramps-project.org</email>
</para>
<para role="publisher">GRAMPS Project</para>
</revdescription>
</revision>
<revision>
<revnumber>GRAMPS Manual V2.2</revnumber>
<date>July 2003</date>
<revdescription>
<para role="author">Alex Roitman
<email>shura@gramps-project.org</email>
</para>
<para role="author">Donald A. Peterson
<email>dpeterson@sigmaxi.org</email>
</para>
<para role="publisher">GRAMPS Project</para>
</revdescription>
</revision>
<revision>
<revnumber>GRAMPS Manual V2.1</revnumber>
<date>May 2003</date>
<revdescription>
<para role="author">Alex Roitman
<email>shura@gramps-project.org</email>
</para>
<para role="publisher">GRAMPS Project</para>
</revdescription>
</revision>
<revision>
<revnumber>GRAMPS Manual V2.0</revnumber>
<date>April 2003</date>
<revdescription>
<para role="author">Alex Roitman
<email>shura@gramps-project.org</email>
</para>
<para role="publisher">GRAMPS Project</para>
</revdescription>
</revision>
<revision>
<revnumber>GRAMPS User Manual V1.1</revnumber>
<date>2001</date>
<revdescription>
<para role="author">Donald N. Allingham
<email>don@gramps-project.org</email>
</para>
<para role="publisher">GRAMPS Project</para>
</revdescription>
</revision>
<revision>
<revnumber>gramps User Manual V1.0</revnumber>
<date>2001</date>
<revdescription>
<para role="author">Donald N. Allingham
<email>don@gramps-project.org</email>
</para>
<para role="publisher">GRAMPS Project</para>
</revdescription>
</revision>
</revhistory>
<releaseinfo>
This manual describes version &appversion; of GRAMPS.
</releaseinfo>
</bookinfo>
<!-- ============= Document Body ============================= -->
<!-- Preface -->
&preface;
<!-- Regular chapters -->
&getstart; <!-- Getting Started -->
&mainwin; <!-- Main window -->
&usage; <!-- Usage -->
&custom; <!-- Customization -->
<!-- Appendices -->
&faq; <!-- FAQ -->
&keybind; <!-- Keybindings reference -->
&filtref; <!-- Filter rule reference -->
&cmdline; <!-- Command line reference -->
&bugs; <!-- Bugs and problems -->
&authors; <!-- About authors -->
</book>

271
manual/C/keybind.xml Normal file
View File

@@ -0,0 +1,271 @@
<appendix id="append-keybind">
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003-2005 Alexander Roitman
This document is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-->
<!-- $Id$ -->
<title>Keybindings reference</title>
<para>Most of the standard menu items define equivalent keybindings.
These are apparent because they are displayed on the right of
the menu item. However, some keybindings are not associated with
any items in the menu. </para>
<para>This appendix contains the list of keybindings that are not
displayed in menus of &app;.
</para>
<sect1 id="keybind-lists">
<title>List Views</title>
<para>The following bindings are available in all list views:
People View, Sources View, Places View, and Media View.</para>
<informaltable frame="topbot">
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<thead>
<row valign="top">
<entry colname="col1" colsep="0" valign="top"><para>Key</para></entry>
<entry colname="col2" valign="top"><para>Function</para></entry>
</row>
</thead>
<tbody>
<row valign="top">
<entry><para><keycap>Enter</keycap></para></entry>
<entry><para>Invoke <guilabel>Edit Person</guilabel> dialog
with the selected person.</para></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</sect1>
<sect1 id="keybind-family">
<title>Family View</title>
<para>The bindings available in the Family View depend on where the
focus is. The following tables list the bindings for all focus
targets.</para>
<variablelist>
<varlistentry><term>Focus on the Active Person</term>
<listitem>
<informaltable frame="topbot">
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<thead>
<row valign="top">
<entry colname="col1" colsep="0" valign="top"><para>Key</para></entry>
<entry colname="col2" valign="top"><para>Function</para></entry>
</row>
</thead>
<tbody>
<row valign="top">
<entry><para><keycap>Enter</keycap></para></entry>
<entry><para>Invoke <guilabel>Edit Person</guilabel> dialog with
the active person.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Ctrl</keycap>+<keycap>Down</keycap>
or <keycap>Ctrl</keycap>+<keycap>Right</keycap></para></entry>
<entry><para>Swap the Active Person and the selected spouse.
Use <keycap>Ctrl</keycap>+<keycap>Down</keycap> in standard Family View and
<keycap>Ctrl</keycap>+<keycap>Right</keycap> in alternative Family
View.</para></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</listitem>
</varlistentry>
<varlistentry><term>Focus on the Spouse box</term>
<listitem>
<informaltable frame="topbot">
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<thead>
<row valign="top">
<entry colname="col1" colsep="0" valign="top"><para>Key</para></entry>
<entry colname="col2" valign="top"><para>Function</para></entry>
</row>
</thead>
<tbody>
<row valign="top">
<entry><para><keycap>Enter</keycap></para></entry>
<entry><para>Edit relationship between the Active Person and
the selected spouse.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Shift</keycap>+<keycap>Enter</keycap></para></entry>
<entry><para>Edit the personal information for the selected
spouse.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Insert</keycap></para></entry>
<entry><para>Add a person from the database to the spouse
list.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Shift</keycap>+<keycap>Insert</keycap></para></entry>
<entry><para>Add a new person to the database and to the spouse
list.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Delete</keycap></para></entry>
<entry><para>Delete the selected spouse from the spouse
list. The spouse is not deleted from the database.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Ctrl</keycap>+<keycap>Up</keycap>
or <keycap>Ctrl</keycap>+<keycap>Left</keycap></para></entry>
<entry><para>Swap the selected spouse and the Active Person.
Use <keycap>Ctrl</keycap>+<keycap>Up</keycap> in standard Family View and
<keycap>Ctrl</keycap>+<keycap>Left</keycap> in alternative Family
View.</para></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</listitem>
</varlistentry>
<varlistentry><term>Focus on the Parents box</term>
<listitem>
<informaltable frame="topbot">
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<thead>
<row valign="top">
<entry colname="col1" colsep="0" valign="top"><para>Key</para></entry>
<entry colname="col2" valign="top"><para>Function</para></entry>
</row>
</thead>
<tbody>
<row valign="top">
<entry><para><keycap>Enter</keycap></para></entry>
<entry><para>Edit relationship between the parents and their
child (either the Active Person or the selected spouse, depending
which parents box the focus is in).</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Insert</keycap></para></entry>
<entry><para>Add a new set of parents from the database to the
list.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Shift</keycap>+<keycap>Insert</keycap></para></entry>
<entry><para>Add a new set of parents to the database and to the
list.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Delete</keycap></para></entry>
<entry><para>Delete the selected parents from the list.
The parents are not deleted from the database.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Ctrl</keycap>+<keycap>Right</keycap>
or <keycap>Ctrl</keycap>+<keycap>Down</keycap></para></entry>
<entry><para>Make the selected parents the active family.
Use <keycap>Ctrl</keycap>+<keycap>Right</keycap> in standard Family View and
<keycap>Ctrl</keycap>+<keycap>Down</keycap> in alternative Family
View.</para></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</listitem>
</varlistentry>
<varlistentry><term>Focus on the Children box</term>
<listitem>
<informaltable frame="topbot">
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<thead>
<row valign="top">
<entry colname="col1" colsep="0" valign="top"><para>Key</para></entry>
<entry colname="col2" valign="top"><para>Function</para></entry>
</row>
</thead>
<tbody>
<row valign="top">
<entry><para><keycap>Enter</keycap></para></entry>
<entry><para>Edit relationship between the child and his/her
parents (the Active Person and the selected
spouse).</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Shift</keycap>+<keycap>Enter</keycap></para></entry>
<entry><para>Edit the personal information for the selected
child.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Insert</keycap></para></entry>
<entry><para>Add a new person from the database to the children
list.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Shift</keycap>+<keycap>Insert</keycap></para></entry>
<entry><para>Add a new person to the database and to the children
list.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Delete</keycap></para></entry>
<entry><para>Delete the selected child from the list.
The child is not deleted from the database.</para></entry>
</row>
<row valign="top">
<entry><para><keycap>Ctrl</keycap>+<keycap>Left</keycap>
or <keycap>Ctrl</keycap>+<keycap>Up</keycap></para></entry>
<entry><para>Make the selected child the Active Person.
Use <keycap>Ctrl</keycap>+<keycap>Left</keycap> in standard Family View and
<keycap>Ctrl</keycap>+<keycap>Up</keycap> in alternative Family
View.</para></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</listitem>
</varlistentry>
</variablelist>
</sect1>
</appendix>

21
manual/C/legal.xml Normal file
View File

@@ -0,0 +1,21 @@
<legalnotice id="legalnotice">
<para>
This manual is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
</para>
<para>
This manual is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
</para>
<para>
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
</para>
</legalnotice>

810
manual/C/mainwin.xml Normal file
View File

@@ -0,0 +1,810 @@
<chapter id="gramps-mainwin">
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003-2005 Alexander Roitman
This document is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-->
<!-- $Id$ -->
<title>Main Window</title>
<para>
When you open a database (either existing or brand new), the
following window is displayed:
</para>
<!-- ==== Figure: Main Window ==== -->
<figure id="mainwin-fig" pgwide="1">
<title>GRAMPS Main Window</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/mainwin.png" format="PNG" width="500" depth="352" scale="70"/>
</imageobject>
<textobject>
<phrase>
Shows GRAMPS main window. Contains titlebar, menubar,
toolbar, sidebar, display area, statusbar, progressbar, and
scrollbars. Menubar contains File, Edit, View, Go, Bookmarks,
Reports, Tools, Settings, and Help menus.
</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
<para>
The &app; window contains the following elements:
</para>
<variablelist>
<varlistentry>
<term>Menubar</term>
<listitem>
<para>
The menubar is located at the very top of the window (right
below the window title) and provides access to all features
of &app; through its menus.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Toolbar</term>
<listitem>
<para>
The toolbar is located immediately below the menubar. The
toolbar provides access to the most frequently used
functions of &app;. The appearance of the toolbar can be
adjusted in the <guilabel>Preferences</guilabel> dialog.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Progressbar</term>
<listitem>
<para>
The progressbar is located in the lower left corner of the
&app; window. It displays the progress of time consuming
operations, such as opening and saving large data bases,
importing and exporting to other formats, generating web
sites, etc.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Statusbar</term>
<listitem>
<para>
The statusbar is located to the right of the progressbar, on
the very bottom of the &app; window. It displays
information about current &app; activity and contextual
information about the menu items. The behavior of the
statusbar can be adjusted in
<guilabel>Preferences</guilabel> dialog.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Display area</term>
<listitem>
<para>
The largest area in the center of the &app; window is the
display area. It shows certain aspects of genealogical
information, depending on the currently selected View. The
following six Views are available in &app;:
<itemizedlist>
<listitem><para>People View</para></listitem>
<listitem><para>Family View</para></listitem>
<listitem><para>Pedigree View</para></listitem>
<listitem><para>Sources View</para></listitem>
<listitem><para>Places View</para></listitem>
<listitem><para>Media View</para></listitem>
</itemizedlist>
</para>
</listitem>
</varlistentry>
</variablelist>
<!-- ================ Main Window Subsection -->
<sect1 id="gramps-views">
<title>Views</title>
<para>
Views are the various ways to display different aspects of
genealogical information. It is best to split the relevant
information display into smaller categories, uniform in context
and modality; since it is very broad and non-uniform in both
context and modality. Each View represents such a split and
displays a certain portion of overall available
information. Before reviewing the detailed description of
available Views, you will be guided through the ways of
switching between the Views.
</para>
<!-- ================ Main Window Sub-subsection -->
<sect2 id="view-modes">
<title>Switching Views and Viewing Modes</title>
<para>
Depending on the state of the <menuchoice>
<guimenu>View</guimenu><guimenuitem>Sidebar</guimenuitem>
</menuchoice> menu item, the View could be switched either in
the sidebar or in the notebook tabs in the top part of the
window.
</para>
<variablelist>
<varlistentry>
<term>
To switch the View while in a Sidebar mode,
click on the desired sidebar icon.
</term>
<listitem>
<!-- ==== Figure: Sidebar Mode ==== -->
<figure id="side-nofilt-fig">
<title>Sidebar Viewing Mode</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/mainwin.png" format="PNG" width="500" depth="352" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows sidebar viewing mode.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
</listitem>
</varlistentry>
<varlistentry>
<term>
To switch the View while in a Tabbed mode,
click on the desired notebook tab.
</term>
<listitem>
<!-- ==== Figure: Tabbed Notebook Mode ==== -->
<figure id="noside-nofilt-fig">
<title>Tabbed Viewing Mode</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/noside-nofilt.png" format="PNG" width="500" depth="393" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows tabbed viewing mode.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
</listitem>
</varlistentry>
</variablelist>
<para>
To switch between sidebar and tabbed viewing modes, choose
<menuchoice> <guimenu>View</guimenu>
<guimenuitem>Sidebar</guimenuitem> </menuchoice> from the
&app; menu.
</para>
</sect2>
<!-- ================ Main Window Sub-subsection -->
<sect2 id="people-view">
<title>People View</title>
<para>
When &app; first opens a database, the View is set to the
People View (<xref linkend="side-nofilt-fig"/> and <xref
linkend="noside-nofilt-fig"/>). The People View lists
individuals whose data is stored in the database.
</para>
<para>
The individuals are arranged in a tree-like structure,
according to their family names. Every family name is a node
of the tree. Clicking the arrow on the left of the node will
toggle its expansion state. When expanded, the node's content
is listed in the window. When collapsed, the content is
rolled up and not visible. All the data is still
intact. It is just not being displayed.
</para>
<para>
The People View, in its default state, displays people's
<guilabel>Names</guilabel>, &app; <guilabel>ID</guilabel>
numbers, <guilabel>Gender</guilabel>, and their
<guilabel>Birth</guilabel> and <guilabel>Death
dates</guilabel>. The list can be ordered by any field.
</para>
<tip id="columns-tip">
<title>Order list by selected column</title>
<para>
To order list by the Birth date, click on the
<guilabel>Birth date</guilabel> column heading. To order
list in reverse (descending) order, click one more time on
the desired column heading.
</para>
</tip>
<para>
The columns of the view may be added, removed, or reordered in
a <guilabel>Column Editor Dialog</guilabel>, see <xref
linkend="column-editor-fig"/>. Only checked columns will be
shown in the view. To change their order, drag any column to
its desired location inside the editor. Clicking
<guibutton>OK</guibutton> will reflect the changes in the
People View. To invoke <guilabel>Column Editor
Dialog</guilabel>, choose
<menuchoice><guimenu>Edit</guimenu><guimenuitem>Column
Editor</guimenuitem></menuchoice>.
</para>
<tip id="columns-tip2">
<title>Other Views</title>
<para>
The <guilabel>Column Editor</guilabel> is available and
works in the same way for all list views, not only People
View.
</para>
</tip>
<!-- ==== Figure: Enabled Filter ==== -->
<figure id="column-editor-fig">
<title>Column Editor Dialog</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/column-editor.png" format="PNG" width="444" depth="437" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows column editor dialog. </phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ================ Main Window Sub-sub-subsection -->
<sect3 id="filters">
<title>Filters</title>
<para>
Genealogical databases may contain huge numbers of people.
Since the long lists are hard for humans to manage, &app;
provides a convenient way to limit the scope of browsing by
using the filter. To save screen space, filter controls may
be hidden, depending on the state of <menuchoice>
<guimenu>View</guimenu> <guimenuitem>Filter</guimenuitem>
</menuchoice> menu item.
</para>
<!-- ==== Figure: Enabled Filter ==== -->
<figure id="side-filt-fig">
<title>Filter Controls Displayed</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/side-filt.png" format="PNG" width="500" depth="352" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows filter controls.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
<para>
When &app; opens a database, the filter is set to the
trivial filter called <guilabel>All people</guilabel>,
i.e. no filtering is in effect. To choose a filter, use the
pop-up <guilabel>Filter</guilabel> menu above the people's
list. Once the filter is chosen, click the
<guibutton>Apply</guibutton> button in the upper right
corner of the window. The filtering will take effect upon
clicking the <guibutton>Apply</guibutton> button.
</para>
<tip id="filt-tip">
<title>Example filter use</title>
<para>
To show males only, choose <guilabel>Males</guilabel>
filter, then click the <guibutton>Apply</guibutton>
button. To cancel any filtering, set the filter to
<guilabel>Entire Database</guilabel> and then click the
<guibutton>Apply</guibutton> button.
</para>
</tip>
<note id="filt-note">
<title>Filtering is persistent</title>
<para>
Even if the filter controls are not displayed
(<menuchoice> <guimenu>View</guimenu>
<guimenuitem>Filter</guimenuitem> </menuchoice> menu
item is unchecked), the filtering might still be in
place. In other words, the visibility of the filter
controls is not related to the actual filtering imposed
on the list.
</para>
<para>
This may be a cause of confusion, when you enable the
filtering and then remove the controls from the
display. If in doubt, enable the display of filter
controls by checking <menuchoice>
<guimenu>View</guimenu>
<guimenuitem>Filter</guimenuitem> </menuchoice> menu
item and check what kind of filtering is currently set.
</para>
</note>
</sect3>
</sect2>
<!-- ================ Main Window Sub-subsection -->
<sect2 id="family-view">
<title>Family View</title>
<para>
Family View displays the family information of a currently
selected (or Active) person. Specifically, this view shows
the relationships (e.g. marriages, partnerships, etc.) of the
active person, his/her parents (or step parents, or
guardians, etc), and his/her children (could be step
children, adopted children, etc.).
</para>
<!-- ==== Figure: Family View ==== -->
<figure id="family-fig">
<title>Family View</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/family.png" format="PNG" width="500" depth="352" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows Family View.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
<para>
The Active person's data is in the list box in the upper
left corner of the window. Directly below it, another box
lists the Spouse's data, for each relationship of Active
person (can be more than one). The double-arrow button to
the right of the Active person list box allows you to
exchange the currently selected spouse (Current spouse) with
the Active person. Double-clicking on the Active person
allows the editing of Active person's data. Double-clicking
on the Current spouse allows you to edit their relationship
information. Shift-clicking on the Current spouse allows the
editing of the Current spouse's data.
</para>
<para>
To add a new relationship, use one of the two upper buttons
to the right of the spouse box. Click the top one to add a
new person to a database and to the new relationship. Click
the middle one to add a person already existing in the
database to the new relationship. To remove Current spouse,
click the lowest button (<guibutton>-</guibutton>) to the
right of the spouse box. Note that removing a spouse from
the relationship does not remove the person from the
database. Most of these functions are also available by
right-clicking into the spouse box and selecting an
appropriate item from the context menu.
</para>
<para>
The parents of both the Active person and the Current spouse
are listed in the corresponding list boxes in the right-hand
part of the window (Active person's parents on top, Current
spouse parents on the bottom). Both list boxes have a set of
three buttons on their right side. The
<guibutton>+</guibutton> and <guibutton>-</guibutton>
buttons allow you to add and remove parents of the Active
person and the Current spouse, respectively. Clicking the
right arrow button makes the family in the corresponding
list box an active family. That is, it makes the selected
Father the Active person, and the selected Mother the
Current spouse. Most of these functions are also available
by right-clicking into the parent box and selecting an
appropriate item from the context menu.
</para>
<para>
The bottom list box displays children of the Active person
and the Current Spouse. The Children's list can be ordered
by the Birth date in the usual way of clicking on the
<guilabel>Birth date</guilabel> column header. In addition
to the <guilabel>Name</guilabel>, <guilabel>ID</guilabel>,
<guilabel>Gender</guilabel>, and <guilabel>Birth
date</guilabel> columns, the list includes a
<guilabel>Status</guilabel> column. The pair of status words
reflect the relationship between the child and his
Father/Mother (such as Birth, Adoption,
etc.). <guilabel>Column Editor Dialog</guilabel> can be used
to change column arrangement. Four buttons are available on
the right side of the children list box. The top (left
arrow) button makes the selected child the Active
person. The next two buttons add a new child to the family:
the upper one adds a new person to the database and to the
family, the lower one just adds a person existing in the
database to the family. Finally, the lowest
<guibutton>-</guibutton> button removes the selected child
from the family. Note that removing a child from the family
does not remove the person from the database. Most of these
functions are also available by right-clicking into the
children box and selecting an appropriate item from the
context menu.
</para>
<para>
The layout of the Family View can be switched from the
left-to-right arrangement (shown above) to the top-to-bottom
arrangement (shown below). This can be done in the
<guilabel>Display</guilabel> section of the
<guilabel>Preferences</guilabel> dialog. The top-to-bottom
view has the same functionality as the left-to-right view.
</para>
<!-- ==== Figure: Family View ==== -->
<figure id="family-alt-fig">
<title>Alternative Family View</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/family-alt.png" format="PNG" width="500" depth="352" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows Alternative Family View.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
</sect2>
<!-- ================ Main Window Sub-subsection -->
<sect2 id="pedigree-view">
<title>Pedigree View</title>
<!-- ==== Figure: Pedigree View ==== -->
<figure id="pedigree-fig">
<title>Pedigree View</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/pedigree.png" format="PNG" width="500" depth="352" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows Pedigree View.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
<para>
The Pedigree View helps to visualize the place of the Active
person in the tree of his/her ancestors. The Pedigree View
shows four generations, going back in time from the Active
person <guilabel>1</guilabel> to his/her parents
<guilabel>2</guilabel>, to grandparents
<guilabel>3</guilabel>, to great-grandparents
<guilabel>4</guilabel>. Each person is denoted by a box
bearing the person's name. The two lines that converge on
the box represent ties with the person's Father (top line)
and mother (bottom line). Solid lines represent birth
relations, while dashed lines represent non-birth relations
(such as adoption, step-parenthood, guardianship, etc.).
When the mouse moves over the white box, it expands to
display the corresponding person's dates of birth and
death. When the mouse is placed over the family line, the
line becomes highlighted to indicate an active link:
double-clicking on the line makes the corresponding ancestor
the Active person. The display in that case is re-adjusted
to show four generations, starting from the newly selected
Active person.
</para>
<!-- ==== Figure: Pedigree View ==== -->
<figure id="pedigree-child-cut-fig">
<title>Children Menu</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/pedigree-child-cut.png" format="PNG" width="303" depth="195"/>
</imageobject>
<textobject>
<phrase>Shows Children Menu in Pedigree View.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
<para>
The left-hand side of the window shows the left arrow
button. Upon clicking, the button expands to the menu
listing the children of the Active person. Selecting the
menu item makes the corresponding child the Active
person. The appearance of the children's names in the menu
serves to differentiate the "dead ends" of the tree from the
continuing branches as follows. The children who have
children appear in the menu in the boldface and italic
typeset, while the children without children ("dead ends")
appear in a regular font. If the Active person has a single
child, no menu will be displayed (since there is no choice)
and the child will become the Active person upon clicking
the arrow button.
</para><para>
The right-hand side of the window shows two right arrow
buttons. When the top button is clicked, the Father of the
Active person becomes the Active person. Clicking the bottom
button makes the Mother of the Active person the Active
person. Again, the display is re-adjusted to show four
generations, starting from the newly selected Active person.
</para>
<!-- ==== Figure: Pedigree View ==== -->
<figure id="pedigree-siblings-cut-fig">
<title>Personal Context Menu</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/pedigree-siblings-cut.png" format="PNG" width="500" depth="253" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows Context Menu in Pedigree View.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
<para>
Right-clicking on any person's box in the Pedigree View will
bring up the context menu. Among other useful items, the
context menu has submenus listing
<guilabel>Spouses</guilabel>, <guilabel>Siblings</guilabel>,
<guilabel>Children</guilabel>, and
<guilabel>Parents</guilabel> of that person. Insensitive
(grayed out) sub-menus indicate the absence of the data in
the appropriate category. Similarly to the children menu
above, children's and parents' menus distinguish continuing
lines from dead ends.
</para>
<!-- ==== Figure: Pedigree View ==== -->
<figure id="pedigree-anchor-fig">
<title>Pedigree View with the Anchor</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/pedigree-anchor.png" format="PNG" width="500" depth="353" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows Pedigree View with the anchor set.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
<para>
An additional advanced scheme of labeling generations exists
in Pedigree View. It becomes available by setting the anchor
on some active person. If the anchor is set, the generations
are labeled as follows. The anchor person (and his/her
generation) is labeled as <guilabel>0</guilabel>. The
ancestor generations are numbered with positive integers
(<guilabel>1</guilabel>, <guilabel>2</guilabel>,
<guilabel>3</guilabel>, etc.) while the descendant
generations are numbered with negative integers
(<guilabel>-1</guilabel>, <guilabel>-2</guilabel>,
<guilabel>-3</guilabel>, etc.). In all cases, the number
represents the number of generations between the labeled
generation and the anchor person. In this mode, you can
travel along the extensive pedigree line and see the number
of generations counting from the anchor person.
</para><para>
To set the anchor, select the <guilabel>Set
anchor</guilabel> menu item from the right-click context
menu, when the desired person is the Active person in the
Pedigree View. The labels will change immediately, and the
name of the anchor person will appear at the lower left
corner of the display area. The set anchor person will stay
in effect until either the anchor is removed (by selecting
the <guilabel>Remove anchor</guilabel> item from the context
menu), or until the active person chosen is unrelated to the
anchor person. The latter move can be made using extensive
navigation tools available in &app;, see <xref
linkend="gramps-nav"/> for the detailed reference.
</para>
</sect2>
<!-- ================ Main Window Sub-subsection -->
<sect2 id="sources-view">
<title>Sources View</title>
<!-- ==== Figure: Sources View ==== -->
<figure id="sources-fig">
<title>Sources View</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/sources.png" format="PNG" width="500" depth="353" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows Sources View.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
<para>
The Sources View lists the sources of information stored in
the database. This can include various documents (birth,
death, and marriage certificates, etc.), books, films,
journals, private diaries; virtually anything that can
be classified as a source of information. The sources can be
used as a reference for any event stored in the
database. The Source View lists the
<guilabel>Title</guilabel>, <guilabel>ID</guilabel>, and the
<guilabel>Author</guilabel> of the source. Any column can be
used for sorting the list. The usual rules apply: one click
for ascending order, another click for descending order.
<guilabel>Column Editor Dialog</guilabel> may be used to
rearrange the displayed columns.
</para>
</sect2>
<!-- ================ Main Window Sub-subsection -->
<sect2 id="places-view">
<title>Places View</title>
<!-- ==== Figure: Places View ==== -->
<figure id="places-fig">
<title>Places View</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/places.png" format="PNG" width="500" depth="353" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows Places View.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
<para>
The Places View lists the geographical places in which the
events of the database took place. These could be places of
birth, death, and marriages of people, as well as their
home, employment, education addresses, or any other
conceivable reference to the geographical location. The
Places View lists the places' <guilabel>Name</guilabel>,
<guilabel>ID</guilabel>, <guilabel>Church Parish</guilabel>,
<guilabel>City</guilabel>, <guilabel>County</guilabel>,
<guilabel>State</guilabel>, and
<guilabel>Country</guilabel>. All of these columns can be
used for sorting by the usual sorting rules.
<guilabel>Column Editor Dialog</guilabel> may be used to
rearrange the displayed columns.
</para>
</sect2>
<!-- ================ Main Window Sub-subsection -->
<sect2 id="media-view">
<title>Media View</title>
<!-- ==== Figure: Media View ==== -->
<figure id="media-fig">
<title>Media View</title>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/media.png" format="PNG" width="500" depth="353" scale="75"/>
</imageobject>
<textobject>
<phrase>Shows Media View.</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
<!-- ==== End of Figure ==== -->
<para>
The Media View is a list of Media Objects used in the
database. Media Objects are any files that relate somehow
to the stored genealogical data. Technically, any file can
be stored as a Media Object. Most frequently, these are
images, audio files, animation files, etc. The list box on
the bottom lists the <guilabel>Name</guilabel>,
<guilabel>ID</guilabel>, <guilabel>Type</guilabel>, and
<guilabel>Path</guilabel> of the Media Object.
<guilabel>Column Editor Dialog</guilabel> may be used to
rearrange the displayed columns, which obey usual sorting
rules. The top part of the GRAMPS window shows a preview (if
available) and information about the Media Object.
</para>
</sect2>
</sect1>
</chapter>

390
manual/C/preface.xml Normal file
View File

@@ -0,0 +1,390 @@
<preface id="gramps-preface">
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003-2005 Alexander Roitman
This document is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-->
<!-- $Id$ -->
<title>Preface</title>
<para>
&app; is a free software package designed to help you with
genealogical research. It allows you to store, edit, and research
genealogical data using your computer. &app; is an open source
software package, which means you are free to run it on any number
of computers, examine the code, make changes, and redistribute as
many copies as you like. It is developed and maintained by a
worldwide team of volunteers and is available at no cost from the
project web site and from many software distributions
</para>
<sect1 id="why-gramps">
<title>Why use GRAMPS?</title>
<para>
Most genealogy programs allow the researcher to input
information related to a family tree. They can usually display
descendant or ancestral relationships through graphical
displays, charts, or reports. Some allow pictures or other media
to be inserted to enhance the raw data. Most provide a means to
include data on individuals or families that may or may not be
related to the primary family being researched. And they may
include other features such as exporting or importing to and
from other programs and printing data contained in various
reports.
</para><para>
&app; has all these capabilities and more. Notably, it allows
you to integrate bits and pieces of stray data as the arise from
your research and put all this information in one place - your
computer. You can then use the speed, power, and accuracy of
your computer to store, manipulate, correlate, and analyze your
data, rather than messing with reams of paper.
</para><para>
&app; has the power to let you rearrange your data in any order
or sequence and to help you fill gaps in genealogical
relationships.
</para>
</sect1>
<sect1 id="whats-new">
<title>What's new since 1.0.X</title>
<para>
This section lists most notable changes from the previous
stable branch of &app;, the 1.0.X.
</para>
<variablelist>
<varlistentry><term>Berkeley database backend</term>
<listitem>
<para>
The default format for &app; is now the BSDDB database.
This change allowed us to overcome performance issues and
memory requirements of the 1.0.X branch. With the database
backend, the database sizes of up to a hundred thousand
people do not present a major obstacle any longer.
</para><para>
The default extension for &app; BSDDB database files is
grdb. The new format is open and fully documented in the
developer's API reference distributed with the source of
&app;.
</para><para>
A consequence of the new database backend is that the
changes, once approved by the user, are applied
immediately. In short, once you click
<guibutton>OK</guibutton> in the Person, Family, Source,
Place, Media object, or Event editor, all the changes made
to this object are recorded in the database. No saving is
necessary (or even possible). The analog of quitting
without saving would be abandoning all changes and
quitting. Also, it is possible to undo recent actions.
</para>
</listitem>
</varlistentry>
<varlistentry><term>Interface improvements</term>
<listitem>
<para>
There were numerous changes in the interface. Most of them
are subtle and incremental improvements, and all of them
cannot be listed here. The most noticeable changes are:
<itemizedlist>
<listitem>
<para>
Removal of alphabetical tabs
</para>
</listitem>
<listitem>
<para>
Ability to add/remove/rearrange columns in list views
</para>
</listitem>
<listitem>
<para>
Removal of Save function and addition of Undo
</para>
</listitem>
<listitem>
<para>
Proper window management and removal of most modal windows
</para>
</listitem>
<listitem>
<para>
Support for Tip of the Day
</para>
</listitem>
<listitem>
<para>
Person-dependent context menus (right-click) in Pedigree View
listing parents, children, spouses, and siblings
</para>
</listitem>
<listitem>
<para>
Export wizard
</para>
</listitem>
<listitem>
<para>
Built-in Find function in list views
</para>
</listitem>
<listitem>
<para>
Date selector dialog
</para>
</listitem>
<listitem>
<para>
Name editor enhancements: patronymic names and non-default
grouping
</para>
</listitem>
<listitem>
<para>
Recent file support (both gramps-specific and gnome-wide)
</para>
</listitem>
</itemizedlist>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
Other database backends
</term>
<listitem>
<para>
Along with the BSDDB backend, the in-memory database handling
for &app; XML and GEDCOM formats has been added. Simply put, it
is now possible to natively open data in those two formats
(although the preferred and default format is grdb) and work with
that data, without necessarily setting up an empty database and
then importing into it. This approach requires holding all data in
memory, so it is only useful for small databases (depending on the
available memory size). In such mode, the data is automatically
saved upon exit, to mimic the functionality of the real database.
<warning id="gedcom-inmem1-warn">
<title>GEDCOM Editing</title>
<para>
Please keep in mind that some information in GEDCOM
file may be lost during import into &app;. Simply
opening and viewing the file will not change it.
However, if any changes were made and they were not
abandoned upon exit, exiting &app; will save the data,
with the possible data loss.
</para>
</warning>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Import and Export</term>
<listitem>
<para>
New import and export filters available for the GeneWeb format.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Reports</term>
<listitem>
<para>
A new report -- Statistics Chart -- has been added to &app;.
</para><para>
An overall change of the whole report framework has been
accomplished. All reports now remember their options. It
is possible to generate reports from the command line,
without launching the interactive &app; session. The
report API is much simpler now, making it easy to write a
custom report. A single code instance may be used for a
standalone report, a book item, and a command-line
report.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Command line</term>
<listitem>
<para>
The new command line functionality includes opening the
filename argument given without any flags, as well as new
flags and options for report generation. Also, the
addition of new formats leads to additional available
format options.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Internationalization</term>
<listitem>
<para>
The approach for entering and displaying dates has been
completely re-worked. In particular, the new framework
allows for a deeper localization of displayed dates than
was ever possible using the translatable strings.
</para><para>
The internationalization of names have also been improved.
Names can be grouped under a non-default
string. Patronymic names are supported, and it is easy to
program new ways of displaying names, as may be required
by various cultures and languages.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Desktop integration</term>
<listitem>
<para>
All formats known to &app; are now registered as mime
types, each with its icon and &app; as a default
handler. Double-clicking on a file with any of these
formats will launch &app; and open that file. &app; also
added support for the recent documents
functionality. This is on both the GNOME-wide level
and within the &app;.
</para><para>
The preferences are now properly stored using GConf, with
schemas, partitioning of keys into smaller directories,
error checking, and notification.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="typography">
<title>Typographical conventions</title>
<para>
In this book, some words are marked with special typography:
<itemizedlist>
<listitem>
<simpara>
<application>Applications</application>
</simpara>
</listitem>
<listitem>
<simpara>
<command>Commands</command> you type at the command line
</simpara>
</listitem>
<listitem>
<simpara>
<filename>Filenames</filename>
</simpara>
</listitem>
<listitem>
<simpara>
<replaceable>Replaceable text</replaceable>
</simpara>
</listitem>
<listitem>
<simpara>
<guilabel>Labels</guilabel> for buttons and other
portions of the graphical interface
</simpara>
</listitem>
<listitem>
<simpara>
Menu selections look like this:
<menuchoice>
<guimenu>Menu</guimenu>
<guisubmenu>Submenu</guisubmenu>
<guimenuitem>Menu Item</guimenuitem>
</menuchoice>
</simpara>
</listitem>
<listitem>
<simpara>
<guibutton>Buttons</guibutton> you can click
</simpara>
</listitem>
<listitem>
<simpara>
<userinput>Anything you type in</userinput>
</simpara>
</listitem>
</itemizedlist>
</para>
<para>
The manual also provides assorted bits of additional information in
tips and notes, as follows.
<tip id="example-tip">
<title>Tip</title>
<para>
Tips and bits of extra information will look like
this.
</para>
</tip>
<note id="example-note">
<title>Note</title>
<para>
Notes will look like this.
</para>
</note>
</para>
<para>
Finally, there are warnings, notifying you where you should be careful:
<warning id="example-warning">
<title>Example Warning</title>
<para>
This is what a warning looks like. If there's a chance
you'll run into trouble, you will be warned beforehand.
</para>
</warning>
</para>
</sect1>
</preface>

5437
manual/C/usage.xml Normal file
View File

File diff suppressed because it is too large Load Diff

3
manual/Makefile.am Normal file
View File

@@ -0,0 +1,3 @@
# Process this file with automake to produce Makefile.in
SUBDIRS = C fr

4
manual/de/.cvsignore Normal file
View File

@@ -0,0 +1,4 @@
Makefile
Makefile.in
omf_timestamp
*.omf.out

15
manual/de/Makefile.am Normal file
View File

@@ -0,0 +1,15 @@
figdir = figures
docname = gramps-manual
lang = de
omffile = gramps-manual-de.omf
entities = legal.xml\
getstart.xml\
mainwin.xml\
usage.xml\
custom.xml\
faq.xml\
keybind.xml\
filtref.xml\
cmdline.xml
include $(top_srcdir)/doc/xmldocs.make
dist-hook: app-dist-hook

262
manual/de/cmdline.xml Normal file
View File

@@ -0,0 +1,262 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003 Alexander Roitman
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
License (GFDL), Version 1.1 or any later version published
by the Free Software Foundation with no Invariant Sections,
no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the file COPYING-DOCS
distributed with this manual.
-->
<!-- $Id$ -->
<!-- =============== Appendices Subsection ================ -->
<sect2 id="append-cmdline">
<title>Befehlszeilen-Referenz</title>
<para>Dieser Anhang liefert eine Referent über die Möglichkeiten,
wenn Sie &app; aus dem Terminal starten.</para>
<para>Lassen Sie uns anmerken, dass &app; als ein interaktives
Programm entworfen wurde. Deshalb benutzt es eine grafische Ansicht und
kann nicht von eine echten nicht-grafischen Konsole gestartet werden. Es
würde einen enormen Aufwand darstellen eine Ausführung in einem Nur-Text
Terminal zu ermöglichen. Aus diesem Grund zielen die möglichen
Befehlszeilenparameter nicht darauf ab, komplett auf die grafisch
Anzeige zu verzichten. Eher machen sie einige typische Aufgaben
angenehmer. Sie erlauben Ihnen auch diese Aufgaben aus Skripten
heraus auszuführen. Jedenfalls muss die grafische Anzeige immer
verfügbar sein!</para>
<para>Zusammengefasst bietet die Benutzung der Befehlszeilenparameter
nicht-interaktives Verhalten, aber beseitigt nicht die Abhängigkeit
von der grafischen Anzeige. Take it or leave it!
</para>
<sect3 id="cmdline-options">
<title>Verfügbare Parameter</title>
<para>Hier ist ein Liste der möglichen Parameter in &app;:</para>
<variablelist>
<varlistentry><term>Format-Parameter</term>
<listitem><para>Das Format der Dateien für den Import oder
Export kann festgelegt werden mit dem
<command>-f</command> <replaceable>Format</replaceable>
Parameter. <replaceable>Format</replaceable> kann eines der
folgenden sein:
<variablelist>
<varlistentry><term>gramps</term>
<listitem><para> &app;-Datenbank. Dieses Format ist sowohl
für den Import als auch für den Export verfügbar. Falls
nicht gegeben wird es geraten, wenn der Dateiname ein
Verzeichnis darstellt.</para></listitem>
</varlistentry>
<varlistentry><term>gedcom</term>
<listitem><para> GEDCOM-Datei. Dieses Format ist für den
Import und den Export verfügbar. Falls nicht angegeben
wird es geraten, wenn der Dateiname mit .ged endet.
</para></listitem></varlistentry>
<varlistentry><term>gramps-pkg</term>
<listitem><para> &app;-Paket. Dieses Format ist für den
Import und Export verfügbar. Falls nicht angegeben wird es
geraten, wenn der Dateiname mit .tgz endet.
</para></listitem></varlistentry>
<varlistentry><term>wft</term>
<listitem><para> Web Family Tree. Dieses Format ist nur für
den Export verfügbar. Falls nichts angegeben wird es
geraten, wenn der Dateiname mit .wft endet.
</para></listitem></varlistentry>
<varlistentry><term>iso</term>
<listitem><para> CD-Image. Dieses Format ist nur für den
Export verfügbar. Es muss immer ausdrücklich angegeben
werden.
</para></listitem></varlistentry>
</variablelist>
</para></listitem>
</varlistentry>
<varlistentry><term>Import-Parameter</term>
<listitem><para>Die für den Import vorgesehenen Dateien können
mit dem
<command>-i</command> <replaceable>Dateiname</replaceable>
Parameter angegeben werden. Das Format kann mit dem
<command>-f</command> Parameter bestimmt werden, der sofort
auf dem <replaceable>Dateiname</replaceable>n folgt.
Falls es nicht angegeben wird, wird versucht das Format aus
dem <replaceable>Dateiname</replaceable>n zu ermitteln. Für
das <term>gramps</term>-Format, ist
<replaceable>Dateiname</replaceable> der Name eines Verzeichnisses,
unter dem sich die gramps Datenbank befindet. Für
<term>gedcom</term> und <term>gramps-pkg</term> ist
<replaceable>Dateiname</replaceable> des Name der entsprechenden
Datei.</para>
<para>Falls mehr als eine Eingabedatei angegeben wird, muss
jeder einem <command>-i</command> folgen. Die Dateien werden in
der angegebenen Reihenfolge importiert, z.B.
<command>-i</command> <replaceable>Datei1</replaceable>
<command>-i</command> <replaceable>Datei2</replaceable>
und
<command>-i</command> <replaceable>Datei2</replaceable>
<command>-i</command> <replaceable>Datei1</replaceable>
könnte verschiedene gramps-ID's in der resultierenden
Datenbank resultieren.
</para></listitem>
</varlistentry>
<varlistentry><term>Export-Parameter</term>
<listitem><para>Die für den Export vorgesehenen Dateien können
mit dem
<command>-o</command> <replaceable>Dateiname</replaceable>
Parameter angegeben werden. Das Format kann mit dem
<command>-f</command> Parameter bestimmt werden, der sofort auf
dem <replaceable>Dateiname</replaceable>n folgt.
Falls es nicht angegeben wird, wird versucht das Format aus
dem <replaceable>Dateiname</replaceable>n zu ermitteln.
Für die <term>gramps</term>- und <term>iso</term>-Formate,
ist der <replaceable>Dateiname</replaceable> der Name eines
Verzeichnisses, in das die gramps-Datenbank geschrieben wird.
Für <term>gedcom</term>, <term>wft</term> und <term>gramps-pkg</term>
ist der <replaceable>Dateiname</replaceable> der Name der
resultierenden Datei.
</para>
<para>Wenn mehr als eine Ausgabedatei angeben wird, muss jede auf
einem <command>-o</command>-Parameter folgen. Diese Dateien werden
nacheinander geschrieben, in der angegebenen Reihenfolge.
</para></listitem>
</varlistentry>
<varlistentry><term>Aktion-Parameter</term>
<listitem><para>Die Aktion, die mit den importierten Daten
durchgeführt werden soll, kann mit dem
<command>-a</command> <replaceable>Aktion</replaceable>
Parameter festgelegt werden. Dies wird getan, wenn alle Importe
erfolgreich durchgeführt worden sind. Die momentan verfügbaren
Aktionen sind <term>summary</term> (dasselbe wie
<menuchoice><guimenu>Berichte</guimenu>
<guisubmenu>Ansichten</guisubmenu>
<guimenuitem>Datenbankübersicht</guimenuitem></menuchoice>)
und <term>check</term> (dasselbe wie
<menuchoice><guimenu>Werkzeuge</guimenu>
<guisubmenu>Datenbankverarbeitung</guisubmenu>
<guimenuitem>Datenbank prüfen und reparieren</guimenuitem></menuchoice>).
</para>
<para>Wenn mehr als eine Ausgabeaktion angegeben wird, muss jede
auf einem <command>-a</command> Parameter folgen. Die Aktionen
werden nacheinander in der entsprechenden Reihenfolge durchgeführt.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<sect3 id="cmdline-operation">
<title>Operationen</title>
<para>Die Reihenfolge der <command>-i</command>, <command>-o</command>,
oder <command>-a</command> Parameter spielt keine Rolle. Die
tatsächliche Ausführungsreihenfolge ist immer: alle Import ->
alle Exporte -> alle Aktionen.</para>
<para>Wenn kein <command>-i</command> Parameter angegeben wird,
startet gramps sein Hauptfenster und startet die gewöhnliche
interaktive Sitzung mit der leeren Datenbank (denn es gibt
keine Daten zu verarbeiten). </para>
<para>Wenn kein <command>-o</command> oder <command>-a</command>
Parameter angegeben ist, startet gramps sein Hauptfenster und
startet die gewöhnliche interaktive Sitzung mit der, aus allen
Importen resultierenden Datenbank. Die Datenbank liegt dann in
dem Verzeichnis <replaceable>~/.gramps/import</replaceable>.</para>
<para>Fehler, die während des Imports, Exports oder einer Aktion
auftreten, werden entweder auf stdout (wenn es Exceptions sind, die
von gramps behandelt werden) oder auf stderr (wenn sie nicht
behandelt werden). Benutzen Sie die gewöhnlichen Shell-Umleitungen
von stdout und stderr um diese Nachrichten und Fehler in Dateien
zu speichern.</para>
</sect3>
<sect3 id="cmdline-examples">
<title>Beispiele</title>
<para>Um vier Datenbanken (dessen Format aus ihren
Namen bestimmt werden kann) zu importieren und die resultieren
Datenbank auf Fehler zu überprüfen, kann man schreiben:</para>
<para><command>gramps -i</command> <replaceable>datei1.ged</replaceable>
<command>-i</command> <replaceable>datei2.tgz</replaceable>
<command>-i</command> <replaceable>~/db3</replaceable>
<command>-i</command> <replaceable>datei4.wft</replaceable>
<command>-a</command> <replaceable>check</replaceable>
</para>
<para>Um explizit die Formate im oberen Beispiel anzugeben, hängen
Sie an die Dateinamen die entsprechenden <command>-f</command>
Parameter:</para>
<para><command>gramps -i</command> <replaceable>datei1.ged</replaceable>
<command>-f</command> <replaceable>gedcom</replaceable>
<command>-i</command> <replaceable>datei2.tgz</replaceable>
<command>-f</command> <replaceable>gramps-pkg</replaceable>
<command>-i</command> <replaceable>~/db3</replaceable>
<command>-f</command> <replaceable>gramps</replaceable>
<command>-i</command> <replaceable>datei4.wft</replaceable>
<command>-f</command> <replaceable>wft</replaceable>
<command>-a</command> <replaceable>check</replaceable>
</para>
<para>Um die aus allen Importen resultierende Datenbank aufzuzeichnen,
benutzen Sie ein <command>-o</command> Parameter (benutzen Sie
<command>-f</command>, wenn der Dateiname es gramps nicht
ermöglicht das Format zu raten):</para>
<para><command>gramps -i</command> <replaceable>datei1.ged</replaceable>
<command>-i</command> <replaceable>datei2.tgz</replaceable>
<command>-o</command> <replaceable>~/neues-paket</replaceable>
<command>-f</command> <replaceable>gramps-pkg</replaceable>
</para>
<para>Um Fehlermeldungen der oberen Beispiele in die Dateien
<replaceable>outfile</replaceable> und
<replaceable>errfile</replaceable> zu speichern, führen Sie aus:
</para>
<para><command>gramps -i</command> <replaceable>datei1.ged</replaceable>
<command>-i</command> <replaceable>datei2.tgz</replaceable>
<command>-o</command> <replaceable>~/neues-paket</replaceable>
<command>-f</command> <replaceable>gramps-pkg</replaceable>
&gt;<replaceable>outfile</replaceable>
2&gt;<replaceable>errfile</replaceable>
</para>
<para>Um drei Datenbanken zu importieren und ein interaktive gramps-
Sitzung zu starten:</para>
<para><command>gramps -i</command> <replaceable>datei1.ged</replaceable>
<command>-i</command> <replaceable>datei2.tgz</replaceable>
<command>-i</command> <replaceable>~/db3</replaceable>
</para>
<para>Schließlich, um eine normale interaktive Sitzung zu starten,
tippen Sie:</para>
<para> <command>gramps </command></para>
</sect3>
</sect2>

418
manual/de/custom.xml Normal file
View File

@@ -0,0 +1,418 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003 Alexander Roitman
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
License (GFDL), Version 1.1 or any later version published
by the Free Software Foundation with no Invariant Sections,
no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the file COPYING-DOCS
distributed with this manual.
-->
<!-- $Id$ -->
<!-- ================ Customization ================================ -->
<sect1 id="gramps-prefs">
<title>Einstellungen</title>
<para>Um &app; zu konfigurieren, wählen Sie
<menuchoice><guimenu>Bearbeiten</guimenu>
<guimenuitem>Einstellungen...</guimenuitem></menuchoice>.
Der <guilabel>Einstellungen</guilabel>-Dialog enthält folgende
Kategorien:</para>
<itemizedlist>
<listitem><para><xref linkend="gramps-prefs-usage"/></para></listitem>
<listitem><para><xref linkend="gramps-prefs-display"/></para></listitem>
<listitem><para><xref linkend="gramps-prefs-db"/></para></listitem>
</itemizedlist>
<!-- =============== Customization Subsection ================ -->
<sect2 id="gramps-prefs-usage">
<title>Verwendung</title>
<para>Diese Kategorie enthält Einstellungen, die die allgemeine
Verwendung von &app; beeinflussen. Es gibt die folgenden
Unterkategorien:</para>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-usage-find">
<title>Suchen</title>
<variablelist>
<varlistentry><term><guilabel>Automatisches Vervollständigen
verwenden</guilabel></term>
<listitem><para>Wenn dieses Feld markiert ist, versucht &app; den
Text zu vervollständigen, sobald Sie ihn in Textfelder wie dem
Familiennamen, Geburtsort usw. eintippen. Die Vervollständigung
wird versucht auf der Grundlage der bereits getippten Buchstaben
und den entsprechenden, bereits in der Datenbank vorhandenen, Daten.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-usage-report">
<title>Einstellungen für Berichte</title>
<variablelist>
<varlistentry><term><guilabel>Bevorzugtes Textformat</guilabel></term>
<listitem><para>Wählen Sie das bevorzugte Format für schriftliche
Berichte aus der Liste der verfügbaren Formate.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Bevorzugtes Grafikformat</guilabel></term>
<listitem><para>Wählen Sie das bevorzugte Format für grafische
Berichte aus der Liste der verfügbaren Formate.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Bevorzugtes Papierformat</guilabel></term>
<listitem><para>Wählen Sie das bevorzugte Papierformat für Berichte
aus der Liste der verfügbaren Formate.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Berichteverzeichnis</guilabel></term>
<listitem><para>Wählen Sie das Standardverzeichnis für Berichte mit
dem <guibutton>Auswählen...</guibutton>-Knopf oder geben Sie es in
das Textfeld ein.</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Webseitenverzeichnis</guilabel></term>
<listitem><para>Wählen Sie das Standardverzeichnis für Webseiten mit
dem <guibutton>Auswählen...</guibutton>-Knopf oder geben Sie es in
das Textfeld ein.</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-usage-res">
<title>Informationen zum Forscher</title>
<variablelist>
<varlistentry><term><guilabel>Informationen zum Forscher</guilabel></term>
<listitem><para>Geben Sie Ihre persönlichen Information in die
entsprechenden Textfelder ein. Obwohl &app; diese Informationen
verlangt, werden sie nur gebraucht, damit &app; gültige GEDCOM-Dateien
erzeugen kann. Eine gültige GEDCOM-Datei erfordert Information über
den Ersteller der Datei. Wenn Sie wollen, können Sie diese Felder
leer lassen, aber dann sind ihre exportierten GEDCOM-Dateien alle
ungültig.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-usage-guess">
<title>Datenvorbelegung</title>
<variablelist>
<varlistentry><term><guilabel>Vorbelegung des Nachnamens</guilabel></term>
<listitem><para>Diese Einstellungen beeinflusst den vorgegebenen
Nachnamen eines Kindes, wenn es zur Datenbank hinzugefügt wird.
ANMERKUNG: Diese Einstellung beeinflusst nur den von &app; vorgegebenen
Nachnamen, wenn der <guilabel>Person bearbeiten</guilabel>-Dialog
aufgerufen wird. Sie können den Namen beliebig verändern. Setzen
Sie diese Einstellung auf den Wert, den Sie am häufigsten verwenden.
Dies wird Ihnen sehr viel Tippen sparen.</para>
<para>Wenn <guilabel>Ohne</guilabel> ausgewählt ist, wird der Name
nicht vorbelegt. <guilabel>Nachname der Vaters</guilabel> benutzt
den Nachnamen des Vaters. <guilabel>Kombination aus den Nachnamen
der Mutter und des Vaters</guilabel> benutzt den Namen des Vaters
gefolgt vom Namen des Mutter. Und schließlich <guilabel>Isländischer
Stil</guilabel> benutzten den Vornamen des Vaters gefolgt vom
&quot;sson&quot;-Suffix (z.B. der Sohn von Edwin wird zu Edwinsson).
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
</sect2>
<!-- =============== Customization Subsection ================ -->
<sect2 id="gramps-prefs-display">
<title>Anzeige</title>
<para>Diese Kategorie enthält Einstellungen bezüglich des Anzeige
der Datenbankeinträgen und der Oberfläche in &app;. Es gibt die
folgenden Unterkategorien:</para>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-display-gen">
<title>Allgemeines</title>
<variablelist>
<varlistentry><term><guilabel>Standardansicht</guilabel></term>
<listitem><para>Dies bestimmt, welche Ansicht erscheint, wenn Sie
&app; starten. Wählen Sie zwischen der Personen- und der
Familienansicht.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Familienansichts-Stil</guilabel></term>
<listitem><para>Diese Einstellung wählt zwischen zwei verfügbaren
Stilen des Layouts der Familienansicht. Der <guilabel>Von links nach
rechts</guilabel>-Stil ist ähnlich zu Family Tree Maker (tm),
während der <guilabel>Von Oben nach unten</guilabel>-Stil ähnlich ist
zu Reunion.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Karteireiter von die Heiligen
Handlungen der Mormonen immer anzeigen</guilabel></term>
<listitem><para>Markieren Sie dieses Feld, wenn Sie wollen, dass die
Reiter für die Heiligen Handlungen der HLT angezeigt werden.
Wenn Sie nicht wissen, was die HLT sind, sollten es nicht markieren.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Indexnummern in der Kinderliste
anzeigen</guilabel></term>
<listitem><para>
Diese Einstellung ist im Moment noch nicht implementiert.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-display-date">
<title>Daten und Kalender</title>
<variablelist>
<varlistentry><term><guilabel>Anzeigeformate: Datumsformat</guilabel></term>
<listitem><para>Wählen Sie ein Anzeigeformat aus der Liste der
verfügbaren Formate.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Namenformat</guilabel></term>
<listitem><para> Wählen Sie ein Anzeigeformat aus der Liste der
verfügbaren Formate.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Eingabeformate: Datumsformat</guilabel></term>
<listitem><para> Wählen Sie das Eingabeformat für Daten aus der
Liste der verfügbaren Formate.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Auswahlmenü für Kalenderformat
zeigen</guilabel></term>
<listitem><para>Markieren Sie dieses Feld um das Menü zur Wahl
des Kalenderformats zu aktivieren, wenn Sie Daten in den
<guilabel>Ereigniseditor</guilabel>-Dialog eingeben. Dies
ermöglicht Ihnen zwischen verschiedenen Kalendern zu wählen, wenn
Sie ein Datum bearbeiten.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-display-bars">
<title>Werkzeug- und Statusleiste</title>
<variablelist>
<varlistentry><term><guilabel>Werkzeugleiste</guilabel></term>
<listitem><para>Wählen Sie die gewünschte Erscheinung der
Werkzeugleistensymbole aus dem Menü. <guilabel>GNOME Einstellung
</guilabel> benutzt die Standard-Einstellung für den GNOME-Desktop.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Statuszeile</guilabel></term>
<listitem><para>Wählen Sie die gewünschten Inhalte aus, die in
der Statuszeile angezeigt werden sollen.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
</sect2>
<!-- =============== Customization Subsection ================ -->
<sect2 id="gramps-prefs-db">
<title>Datenbank</title>
<para> Diese Kategorie enthält Einstellungen bezüglich der
Datenbank selbst. Es gibt die folgenden Unterkategorien:</para>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-db-gen">
<title>Allgemein</title>
<variablelist>
<varlistentry><term><guilabel>Letzte Datenbank automatisch laden</guilabel></term>
<listitem><para>Markieren Sie dieses Feld um beim Start automatisch
die zuletzt geöffnete Datenbank zu laden.</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>XML-Datei nicht komprimieren</guilabel></term>
<listitem><para>Markieren Sie dieses Feld um die Kompression der
XML-Datei zu deaktivieren. Kompression reduziert deutlich die
Dateigröße. Obwohl es etwas an Performance kostet (ein paar
Rechenschritte werden bei der Dekompression benötigt), sind die
Auswirkungen extrem gering. Nun wo die Bugs bei der Kompression
schon lange behoben sind, gibt es praktisch keinen Grund mehr die
Dateikompression zu deaktivieren.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Speicherintervall</guilabel></term>
<listitem><para>Setzen Sie das Intervall (in Minuten) nach dem &app;
die Datenbank automatisch speichert. Ein Wert von 0 deaktiviert das
automatische Speichern.</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Datenbankverzeichnis</guilabel></term>
<listitem><para>Wählen Sie das Standard-Verzeichnis, in dem &app;
anfängt zu suchen, wenn die Datenbank mit dem
<guibutton>Suchen...</guibutton> gespeichert wird oder ihr Pfad in
das Textfeld eingegeben wird.</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-db-media">
<title>Multimedia-Objekte</title>
<para>Vor der Beschreibung der Multimedia-Objekte lassen Sie uns
einen Blick auf den Hintergrund der lokalen und nicht-lokalen
Objekte werfen. Ein lokales Objekt ist ein Objekt dessen Datei
in demselben Verzeichnis wie die &app;-Datenbank liegt. Ein
nicht-lokales Objekt ist irgendwo anders gespeichert, so dass in
der Datenbank nur eine Referenz auf die Position der Datei und ein
paar Eigenschaften dieses Objektes gespeichert sind.</para>
<para>Sie können wählen, ob Sie Ihre Multimedia-Objekte lokal oder
extern speichern wollen. Wenn Sie Ihre Objekte lokal machen, steigt
der Verbrauch an Speicherplatz des &app;-Datenbankverzeichnisses.
Aber wenn die externe Datei gelöscht oder verschoben wird, kann
&app; immer noch die lokale Kopie benutzen. Im Gegensatz wird der
Platzbedarf reduziert, wenn Sie Ihre Objekt nicht-lokal lassen.
Aber wenn Sie die Originaldatei verlieren, wird Ihr Multimedia-Objekt
unbrauchbar.</para>
<para>Bedenken Sie, dass das Exportieren Ihren Datenbank in
irgendein Format alle Multimedia-Objekte kompiliert, egal ob
lokal oder nicht. Insbesondere beim Exportieren in einem
gramps-Paket werden alle Multimedia-Objekt in das Pakete eingefügt
und die Referenzen entsprechend geändert. Das Exportieren auf CD
kopiert alle Multimedia-Objekte unter die
<guilabel>burn:///</guilabel>-Position in Nautilus und ändert die
Referenzen entsprechend. Schließlich speichert der Export nach
GEDCOM alle Multimedia-Objekte zusammen mit der GEDCOM-Datei und
ändert die Pfadnamen entsprechend.
</para>
<variablelist>
<varlistentry><term><guilabel>Drag &amp; Drop aus externer
Quelle</guilabel></term>
<listitem><para>Wählen Sie zwischen einer Referenz und einer lokalen
Kopie, wenn ein Objekt in der Galerie losgelassen wird. Die
Referenz speichert Plattenplatz, weil das Objekt nicht kopiert wird.
Die lokale Kopie macht Ihre Datenbank portabel, weil sie nicht
von externen Dateien abhängt. Treffen Sie eine Auswahl je nach
Ihren Bedürfnissen.</para>
<para>Markieren Sie das Feld <guilabel>Nach Drag &amp; Drop Editor für
globale Eigenschaften öffnen</guilabel> um den Editor für die
globalen Eigenschaften aufzurufen, nachdem Sie ein externes Objekt in
der Galerie fallengelassen haben.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Drag &amp; Drop aus interner
Quelle</guilabel></term>
<listitem><para>Markieren die das Feld <guilabel>Nach Drag &amp; Drop
Editor für lokale Eigenschaften öffnen</guilabel> den Editor für die
lokalen Eigenschaften aufzurufen, nachdem Sie ein internes Objekt in
der Galerie fallengelassen haben.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-db-id">
<title>GRAMPS-interne ID's</title>
<variablelist>
<varlistentry><term><guilabel> GRAMPS-ID-Präfixe</guilabel></term>
<listitem><para>Geben Sie die ID-Präfixe für die verschiedenen Arten
von Datenbankeinträgen in die entsprechenden Textfelder ein.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Interne GRAMPS-ID's sind
editierbar</guilabel></term>
<listitem><para>Markieren Sie dieses Feld um das Bearbeiten der
internen &app;-ID-Nummern zu erlauben. Markieren Sie es nicht, außer
Sie wissen, was Sie tun.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-db-rcs">
<title>Revisionskontrolle</title>
<variablelist>
<varlistentry><term><guilabel>Revisionskontrolle verwenden</guilabel></term>
<listitem><para>Markieren Sie dieses Feld, damit &app; die
Revisionskontrolle für Ihre Datenbank verwendet. Wenn Sie diese
Einstellung aktivieren, wählen Sie ein bestimmtes
Revisionkontroll-System aus dem Menü aus.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Beim Speichern Kommentar abfragen
</guilabel></term>
<listitem><para>Markieren Sie dieses Feld um &app; anzuweisen, Sie
nach einem Kommentar zu fragen, wenn Sie die Datenbank speichern.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
</sect2>
</sect1> <!-- ================ End Customization ================== -->

377
manual/de/faq.xml Normal file
View File

@@ -0,0 +1,377 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2003 Alexander Roitman
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
License (GFDL), Version 1.1 or any later version published
by the Free Software Foundation with no Invariant Sections,
no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the file COPYING-DOCS
distributed with this manual.
-->
<!-- $Id$ -->
<!-- =============== Appendices Subsection ================ -->
<sect2 id="faq">
<title>Häufig gestellte Fragen</title>
<para>Dieser Anhang enthält eine Liste von Fragen, die häufig in den
Mailinglisten und Foren auftauchen. Diese Liste ist aber auf keinen
Fall vollständig. Wenn Sie Fragen/Antworten zu dieser Liste
hinzufügen möchten, e-mailen Sie Ihre Vorschläge an
<ulink url="mailto:gramps-devel@lists.sf.net"
type="mailto">gramps-devel@lists.sf.net</ulink>
</para>
<variablelist>
<varlistentry><term>Was ist &app;?</term>
<listitem><para> &app; ist das Genealogical Research and Analysis
Management Program System. In anderen Worten: es ein Programm, mit dem
Sie Ihre genealogischen Daten mit Hilfe Ihres Computers speichern,
bearbeiten und erforschen können.
</para></listitem>
</varlistentry>
<varlistentry><term>Wo bekomme ich es und wie viel kostet es?</term>
<listitem><para> &app; kann umsonst herunter geladen werden unter
<ulink url="http://sf.net/projects/gramps" type="http">
http://sf.net/projects/gramps</ulink>. &app; ist ein Open Source
Projekt unter der GNU General Public License. Sie haben vollen Zugriff
auf den Quellcode und können das Programm und den Quellcode frei
weitergeben.
</para></listitem>
</varlistentry>
<varlistentry><term>Läuft es unter Windows (tm)?</term>
<listitem><para> Nein. &app; verwendet die GTK- und GNOME-Bibliotheken.
Obwohl die GTK-Bibliotheken nach Windows portiert sind, sind es die
GNOME-Bibliotheken nicht. Dies könnte sich aber in Zukunft ändern.
</para></listitem>
</varlistentry>
<varlistentry><term>Läuft es auf dem Mac?</term>
<listitem><para>Das Fink-Projekt (<ulink url="http://fink.sf.net"
type="http">http://fink.sf.net</ulink>) hat eine alte Version von
&app; (0.8.0) nach OSX portiert. Der Mac OSX Port wird aber nicht
direkt vom &app;-Projekt unterstützt, hauptsächlich weil keiner der
&app;-Entwickler Zugriff auf Mac OSX hat.</para>
<para>Die GNOME 2 Version von &app; (0.9.x) scheint nicht von
Fink-Projekt portiert worden zu sein. Bitte wenden Sie sich an das
Fink-Projekt um mehr Information zu erfahren.
</para></listitem>
</varlistentry>
<varlistentry><term>Läuft es unter KDE?</term>
<listitem><para> Ja, so lange die benötigten GNOME-Bibliotheken
installiert sind.
</para></listitem>
</varlistentry>
<varlistentry><term>Muss ich wirklich GNOME installiert haben?</term>
<listitem><para>Ja, aber Sie müssen den GNOME-Desktop nicht benutzen.
</para></listitem>
</varlistentry>
<varlistentry><term>Welche GNOME-Version brauchte ich?</term>
<listitem><para>Die neuesten Versionen von gramps (0.9.0 und höher)
benötigen GNOME 2.0 oder höher. Vorherigen Versionen benötigen
GNOME 1.X.
</para></listitem>
</varlistentry>
<varlistentry><term>Ist &app; kompatibel mit anderen
Ahnenforschungsprogrammen?</term>
<listitem><para> &app; versucht die Kompatibilität mit GEDCOM,
dem allgemeinen Standard beim speichern genealogischer Informationen,
zu erhalten. Wir haben Import- und Exportfilter, die es &app;
ermöglichen GEDCOM-Dateien zu lesen und zu schreiben.</para>
<para>Es ist wichtig zu wissen, dass der GEDCOM-Standard nur schwach
implementiert ist -- praktische jede genealogische Software hat einen
eigene "Dialekt" von GEDCOM. Sobald wird von einem neuen Dialekt hören,
können die Import- und Exportfilter sehr schnell erstellt werden. Aber
um unbekannte Dialekte zu finden benötigen wir Benutzer-Feedback. Bitte
informieren Sie uns über GEDCOM-Dialekte, der nicht von &app;
unterstützt wird, und wir werden unser Bestes tun um ihn zu
unterstützen.
</para></listitem>
</varlistentry>
<varlistentry><term>Kann &app; Dateien lesen, die von dem Programm
X erstellt wurden?</term>
<listitem><para> Siehe oben.
</para></listitem>
</varlistentry>
<varlistentry><term>Kann &app; Dateien schreiben, die das Programm
X lesen kann?</term>
<listitem><para> Siehe oben.
</para></listitem>
</varlistentry>
<varlistentry><term>Kann &app; einen Stammbaum für meine Familie
drucken?</term>
<listitem><para> Ja. Verschiedene Leute habe verschiedene Ansichten,
was ein Stammbaum ist. Manche denken an eine Tafel, ausgehend von dem am
weitesten entfernten Ahnen, die alle seine/ihre Nachkommen und deren
Familien auflistet. Anderen denken an eine Tafel, die von der Person
aus zurück in der Zeit geht und alle Ahnen und deren Familien
auflistet. Noch anderen Leute denken an ein Tabelle, einen Textbericht
usw.</para>
<para>&app; kann alle oben genannten, und viele weitere Tafeln und
Berichte produzieren. Darüber hinaus, ermöglicht die
Plugin-Architektur es den Benutzern (Sie) ihren eigenen Plugins zu
erstellen, welche neue Berichte, Tafeln oder Forschungswerkzeuge
sein können.
</para></listitem>
</varlistentry>
<varlistentry><term>In welchen Formaten kann &app; seine Berichte
ausgeben?</term>
<listitem><para>Textberichte sind verfügbar in den HTML-, PDF-,
AbiWord-, KWord-, RTF- und OpenOffice.org-Formaten. Grafische Berichte
(Tafeln und Diagramme) sind verfügbar in den Postscript-, PDF-, SVG-,
OpenOffice.org- und GraphViz-Formaten.
</para></listitem>
</varlistentry>
<varlistentry><term>Ist &app; kompatibel mit dem Internet?</term>
<listitem><para>&app; kann Internetadressen speichern und sie im
Browser aufrufen. Es Daten importieren, die Sie aus dem Internet
herunter geladen haben. Es kann Daten exportieren, die Sie über das
Internet verschicken können. &app; ist vertraut mit den
Standard-Dateiformaten, die häufig im Internet verwendet werden
(z.B. JPEG-, PNG- und GIF-Bilder, MP3-, OGG- und WAV-Audiodateien,
Quicktime-, MPEG- und AVI-Videodateien usw.) Darüber hinaus gibt
es wenig, was ein Ahnenforschungsprogramm mit dem Internet tun
kann. :-)
</para></listitem>
</varlistentry>
<varlistentry><term>Kann ich meine eigenen Berichte/Filter/...
erzeugen?</term>
<listitem><para>Ja. Es gibt verschiedenen Ebenen der Anpassung. Eine
ist die Erschaffung oder das Verändern der Vorlagen für die Berichte.
Dies gibt Ihnen die Kontrolle über die Schriftarten, Farben und über
das Layout der Berichte. Sie können die &app;-Kontrollen in den
Berichtdialogen benutzen um festzulegen, welchen Inhalte in einem
bestimmten Bericht verwendet werden sollen. Zusätzlich haben Sie die
Möglichkeit Ihre eigenen Filter zu erschaffen -- dies ist nützlich beim
Auswählen von Personen basierend auf denen, von Ihnen gesetzten,
Kriterien. Sie können diese Filter kombinieren um neue, komplexere
Filter zu erschaffen. Schließlich habe Sie die Möglichkeit eigene
Plugins zu schreiben. Diese können neue Berichte, Forschungswerkzeuge,
Import-/Exportfilter usw. sein. Dies setzt aber Kenntnisse in der
Python-Programmierung voraus.
</para></listitem>
</varlistentry>
<varlistentry><term>Welche Standards unterstützt &app;?</term>
<listitem><para>Eine nette Tatsache über Standards ist, dass es nie
zu wenige davon gibt :-). &app; wurde getestet um die folgenden
Dialekte von GEDCOM zu unterstützen: GEDCOM5.5, Brother's Keeper,
Family Origins, Familty Tree Maker, Ftree, GeneWeb, Legacy,
Personal Ancestral File, Pro-Gen, Reunion, and Visual Genealogie.
</para></listitem>
</varlistentry>
<varlistentry><term>Was groß (Bytes) darf eine &app;-Datenbank
maximal sein?</term>
<listitem><para>&app; hat keine feste Begrenzung in der Größe der
Datenbank, die es unterstützt. Im Moment lädt &app; alle Daten in
den Speicher, so dass der begrenzende Faktor wahrscheinlich der
verfügbare Arbeitsspeicher ist.
</para></listitem>
</varlistentry>
<varlistentry><term>Wie viele Personen darf eine &app;-Datenbank
maximal haben?</term>
<listitem><para> Wir haben entdeckt, dass &app; auf einem typischen
System hängen bleibt, wenn die Datenbank ungefähr 15.000 Personen
enthält. Wiederum hängt dies davon ab, wie viel Arbeitsspeicher Ihr
Computer hat.
</para></listitem>
</varlistentry>
<varlistentry><term>Warum läuft &app; so langsam?</term>
<listitem><para> Wenn &app; Ihnen zu langsam erscheint, liegt es
wahrscheinlich daran, dass Sie eine große Datenbank haben. Im Moment,
lädt &app; die ganze Datenbank in den Speicher, deswegen tendieren
große Datenbank dazu langsamer zu werden. Insbesondere kann das
System praktisch in die Knie gezwungen werden, wenn für &app;' Daten
auslagern erforderlich wird.</para>
<para>Dies wird in der nächsten stabilen Version nach Version 1.0
angegangen. Vorübergehend, macht das Hinzufügen von Arbeitsspeicher
eine riesigen Unterschied, aber wir sehen ein, dass dies ein
schlechter Weg ist, das Problem zu behandeln. Wenn Sie bei der
Implementierung eines echten Datenbank-Backends helfen wollen,
zögern Sie nicht an <ulink url="mailto:gramps-devel@lists.sf.net"
type="mailto">gramps-devel@lists.sf.net</ulink> zu schreiben.
</para></listitem>
</varlistentry>
<varlistentry><term>Meine Datenbank ist wirklich groß. Gibt es einen
Weg zu verhindern, dass alle Daten in den Speicher geladen
werden?</term>
<listitem><para>Im Momentan gibt es keinen Weg. Aber dies ist
unsere höchste Priorität, nachdem Version 1.0 veröffentlicht ist. Das
echte Datenbank-Backend wird in die nächste stabile Version (1.2)
integriert sein, welche dramatisch in Geschwindigkeit und
Speicherbedarf verbessert sein wird.
</para></listitem>
</varlistentry>
<varlistentry><term>Ich möchte noch mal den Startdialog (Druiden)
aufrufen. Wie mache ich das?</term>
<listitem><para> &app; speichert ein Flag in die
GNOME-Konfigurationsdatenbank um anzuzeigen, dass der Startdialog
aufgerufen wurde. Damit &app; ihn noch mal aufruft, muss das Flag
gelöscht werden. Das kann mit dem folgenden Kommando getan
werden:</para>
<para><command>gconftool-2 -u /apps/gramps/startup</command>
</para></listitem>
</varlistentry>
<varlistentry><term>Warum kann ich keine Spalten
hinzufügen/entfernen/bearbeiten in den Listen in der Personen-
und Familienansicht?</term>
<listitem><para>Dies wird angegangen, nachdem der
TreeModelSort-Bug in pygtk behoben ist, siehe
<ulink url="http://bugzilla.gnome.org/show_bug.cgi?id=125172"
type="http">http://bugzilla.gnome.org/show_bug.cgi?id=125172</ulink>
für Details. Wenn der Patch eingeschickt und in pygtk eingearbeitet
ist, werden wird die Möglichkeit hinzufügen sortierbare Spalten
hinzuzufügen/zu entfernen/zu bearbeiten.
</para></listitem>
</varlistentry>
<varlistentry><term>Ich möchte zu &app; beitragen, indem ich meinen
Lieblingsbericht schreibe. Wie mache ich das?</term>
<listitem><para>Der einfachste Weg zu Berichten, Filter, Werkzeugen
usw. beizutragen ist einen existierenden &app;-Bericht, -filter
oder -werkzeug zu kopieren. Wenn Sie das gewünschte erreichen können
durch das Verändern des Quellcodes -- großartig! Wenn ihre Idee in die
Logik eines existierenden &app;-Werkzeugs passt, hilft Ihnen vielleicht
<ulink
url="http://gramps.sourceforge.net/wiki/index.php/GrampsDevelopersPage"
type="http">folgende Seite</ulink> Schreiben Ihres ganzen neuen Plugins.
Wenn Sie mehr Hilfe benötigen oder Ihre Idee mit uns zu diskutieren,
zögern Sie bitte nicht uns zu kontaktieren unter
<ulink url="mailto:gramps-devel@lists.sf.net"
type="mailto">gramps-devel@lists.sf.net</ulink></para>
<para>Um Ihre Arbeit zu überprüfen, können Sie Ihr Plugin in das
Verzeichnis <replaceable>$HOME/.gramps/plugins</replaceable> und es
sollte beim Start gefunden und importiert werden. Das richtig
geschriebene Plugin registriert sich selbst bei &app;, erzeugt einen
Menüeintrag usw.</para>
<para>Wenn Sie mit Ihrem Plugin glücklich sind und Ihren Quellcode zum
&app;-Projekt beitragen möchten, sind Sie eingeladen es zu tun, indem
Sie uns kontaktieren unter <ulink url="mailto:gramps-devel@lists.sf.net"
type="mailto">gramps-devel@lists.sf.net</ulink>
</para></listitem>
</varlistentry>
<varlistentry><term>Ich habe einen Bug gefunden und möchte, dass er
sofort behoben wird. Was tue ich?</term>
<listitem><para>Das beste, was Sie tun können, ist den Fehler beheben
und den Patch an <ulink url="mailto:gramps-devel@lists.sf.net"
type="mailto">gramps-devel@lists.sf.net</ulink> senden :-)</para>
<para>Das nächste beste wäre, dass Sie einen guten Fehlerbericht
schicken. Dies kann auf zwei Wegen geschehen: (1) senden Sie Ihren
Bericht an <ulink url="mailto:gramps-bugs@lists.sf.net"
type="mailto">gramps-bugs@lists.sf.net</ulink> oder (2) tragen Sie Ihren
Fehler in das Bug Tracker System unter
<ulink url="http://sf.net/tracker/?group_id=25770" type="http">
http://sf.net/tracker/?group_id=25770&amp;atid=385137</ulink> ein
(Diese Funktion ist auch verfügbar durch das Auswählen von
<menuchoice><guisubmenu>Hilfe</guisubmenu><guimenuitem>
Programmfehler melden</guimenuitem></menuchoice> aus dem gramps
Hauptmenü).</para>
<para>Ein guter Fehlerbericht enthält:</para>
<itemizedlist>
<listitem><para>Die Version von gramps, die sie benutzten, als sie
auf den Fehler stießen (verfügbar durch den
<menuchoice><guisubmenu>Hilfe</guisubmenu>
<guimenuitem>Info</guimenuitem></menuchoice>-Menüeintrag).
</para></listitem>
<listitem><para>Die Sprache, unter der gramps ausgeführt wurde
(verfügbar durch das Ausführen von</para>
<para><command>echo $LANG</command></para>
<para>in Ihrem Terminal).
</para></listitem>
<listitem><para>Die Symptome, die zeigen, dass es sich um einen
Fehler handelt.
</para></listitem>
<listitem><para>Zurückverfolgungsnachrichten, Fehlermeldungen, Warnungen
usw., die in Ihrem Terminal auftreten oder in einem separaten
Zurückverfolgungsfenster.
</para></listitem>
</itemizedlist>
<para>Die meisten Probleme können sehr schnell gelöst werden,
vorausgesetzt es gibt genügend Informationen. Um dies Sicher zu stellen,
senden Sie weiter Fehlerberichte. Besonders, wenn Sie einen
Fehlerbericht mit dem sf.net Bug Tracker einschicken, loggen Sie sich
erst bei sf.net ein (registrieren Sie Ihren freien Account, wenn Sie
keins haben). Dann haben wir einen Weg Sie zu kontaktieren, falls wir
mehr Informationen benötigen. Wenn Sie Ihren Bericht anonym einsenden,
prüfen Sie wenigsten öfters auf Ihre Berichtseite, ob etwas Neues
gesendet wurde, was es wahrscheinlich wird.</para>
<para>Wenn Ihnen die obigen Erklärungen zu wage erscheinen, schauen
Sie unter
<ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
type="http">diesen link.</ulink>
</para></listitem>
</varlistentry>
<varlistentry><term>Es ist offensichtlich, dass &app; eine
(client-server/web-basierende/PHP/weblog/Javascript/C++/distributed/KDE/Motif/Tcl/Win32/C#/Was-weiß-ich)-
Anwendung wird. Wann passiert das?</term>
<listitem><para>Der sicherste Weg, es wahr werden zu lassen, ist, dass
Sie es selbst machen. Weil &app; Open Source ist, wird niemand Sie
daran hindern den Quellcode zu nehmen und seine Entwicklung in die Richtung,
die sie möchten weiterzuführen. Wenn Sie das machen, sollten Sie Ihrem
Projekt einen neuen Namen geben um Verwirrung mit der weitergehenden
&app;-Entwicklung zu verhindern. Wenn Sie dem &app;-Projekt
Ratschläge, Filter usw. geben wollen, werden wir mit Ihrem Projekt
zusammenarbeiten um Kompatibilität und Import/Export-Möglichkeiten zu
Ihrem neuen Projekt zu bewahren.</para>
<para>Wenn Sie aber möchten, dass das &app;-Projekt Ihre Strategie
übernimmt, sollten Sie die &app;-Entwickler überzeugen, dass Ihre
Strategie gut ist für &app; und der aktuellen Entwicklungsstrategie
überlegen ist.</para>
<para>HINWEIS: Wenn die &app;-Entwickler immer noch nicht überzeugt
sind nach ungefähr drei Nachrichten an gramps-devel, sind Sie besser
allein dran, als in Gesellschaft von geistig Zurückgebliebenen, die
das Potential Ihre großartigen Idee nicht einsehen :-)
</para></listitem>
</varlistentry>
</variablelist>
</sect2>

BIN
manual/de/figures/bookreport.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/cfe-ar.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/cfe-df.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-ad.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-an.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-at.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-bm.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-ev.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-media.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-person-addresses.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-person-attributes.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-person-events.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-person-gallery.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-person-internet.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-person-lds.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-person-names.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-person-notes.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-person-sources.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-person.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-plc.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-rel.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-si.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-src.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/edit-wi.png Normal file
View File

Binary file not shown.

BIN
manual/de/figures/family-alt.png Normal file
View File

Binary file not shown.

Some files were not shown because too many files have changed in this diff Show More