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

* src/po/ru.po: Update Russian translation.

Browse Source 
* doc/gramps-manual/C/gramps-manual.xml: Update manual.
* doc/gramps-manual/C/filtref.xml: Add file -- split appendix
into a separate file.
* doc/gramps-manual/C/cmdline.xml: Likewise.
* doc/gramps-manual/C/getstart.xml: Likewise.
* doc/gramps-manual/C/mainwin.xml: Likewise.
* doc/gramps-manual/C/usage.xml: Likewise.
* doc/gramps-manual/C/custom.xml: Likewise.
* doc/gramps-manual/C/Makefile.am: Ship new files.
* doc/gramps-manual/C/Makefile.in: Likewise.


svn: r2157
This commit is contained in:
Alex Roitman 2003-09-23 00:48:01 +00:00
parent 3b35b8918f
commit 22739fbb7f
11 changed files with 4191 additions and 3567 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
ChangeLog
View File

@ -1,3 +1,16 @@
2003-09-22 Alex Roitman <shura@alex.neuro.umn.edu>
* src/po/ru.po: Update Russian translation.
* doc/gramps-manual/C/gramps-manual.xml: Update manual.
* doc/gramps-manual/C/filtref.xml: Add file -- split appendix
into a separate file.
* doc/gramps-manual/C/cmdline.xml: Likewise.
* doc/gramps-manual/C/getstart.xml: Likewise.
* doc/gramps-manual/C/mainwin.xml: Likewise.
* doc/gramps-manual/C/usage.xml: Likewise.
* doc/gramps-manual/C/custom.xml: Likewise.
* doc/gramps-manual/C/Makefile.am: Ship new files.
* doc/gramps-manual/C/Makefile.in: Likewise.
2003-09-21 Alex Roitman <shura@alex.neuro.umn.edu>
* src/plugins/book.glade: Minor improvements to the dialogs.
* doc/gramps-manual/C/gramps-manual.xml: Update manual.

8
doc/gramps-manual/C/Makefile.am
View File

@ -2,6 +2,12 @@ figdir = figures
docname = gramps-manual
lang = C
omffile = gramps-manual-C.omf
entities = legal.xml
entities = legal.xml\
getstart.xml\
mainwin.xml\
usage.xml\
custom.xml\
filtref.xml\
cmdline.xml
include $(top_srcdir)/doc/xmldocs.make
dist-hook: app-dist-hook

9
doc/gramps-manual/C/Makefile.in
View File

@ -167,7 +167,14 @@ figdir = figures
docname = gramps-manual
lang = C
omffile = gramps-manual-C.omf
entities = legal.xml
entities = legal.xml\
getstart.xml\
mainwin.xml\
usage.xml\
custom.xml\
filtref.xml\
cmdline.xml
# ************* Begin of section some packagers may need to modify **************
# This variable (docdir) specifies where the documents should be installed.

220
doc/gramps-manual/C/cmdline.xml Normal file
View File

@ -0,0 +1,220 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- =============== Appendices Subsection ================ -->
<sect2 id="append-cmdline">
<title>Command line reference</title>
<para>This appendix provide the reference to the command line
capabilities available when launching &app; from the terminal. </para>
<para>Let us note here that &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 graphical display 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>
<para>To summarize, the use of the command line options provides
non-interactive behavior, but does not get rid of graphical dsiplay
dependency. Take it or leave it!
</para>
<sect3 id="cmdline-options">
<title>Available options</title>
<para>Here is the list of the command line options in &app;:
</para>
<variablelist>
<varlistentry><term>Format options</term>
<listitem><para> The format of any file destined for import or export
can be specified with the
<command>-f</command> <replaceable>format</replaceable>
option. The format can be one of the followng:
<variablelist>
<varlistentry><term>gramps</term>
<listitem><para> &app; database. This format is available
for both import and export. When not specified, can be guessed
if the filename represents a directory.
</para></listitem></varlistentry>
<varlistentry><term>gedcom</term>
<listitem><para> GEDCOM file. This format is available
for both import and export. When not specified, 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 both import and export. When not specified, can be guessed
if the filename ends with .tgz
</para></listitem></varlistentry>
<varlistentry><term>wft</term>
<listitem><para> Web Family Tree. This format is available
for export only. When not specified, 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. Never guessed, always specify explicitly.
</para></listitem></varlistentry>
</variablelist>
</para></listitem>
</varlistentry>
<varlistentry><term>Import options</term>
<listitem><para> The files destined for import can be specified with
the
<command>-i</command> <replaceable>filename</replaceable>
option. The format can be specified with the <command>-f</command>
option immediately following the <replaceable>filename</replaceable>.
If not specified, the guess will be attempted based on
the <replaceable>filename</replaceable>. For <term>gramps</term>
format, the <replaceable>filename</replaceable> is actually the
name of directory under which the gramps database resides. For
<term>gedcom</term> and <term>gramps-pkg</term>, the
<replaceable>filename</replaceable> is the name of the
corresponding file.
</para>
<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</command> <replaceable>file1</replaceable>
<command>-i</command> <replaceable>file2</replaceable>
and
<command>-i</command> <replaceable>file2</replaceable>
<command>-i</command> <replaceable>file1</replaceable>
might produce different gramps IDs in the resulting database.
</para></listitem>
</varlistentry>
<varlistentry><term>Export options</term>
<listitem><para> The files destined for export can be specified with
the
<command>-o</command> <replaceable>filename</replaceable>
option. The format can be specified with the <command>-f</command>
option immediately following the <replaceable>filename</replaceable>.
If not specified, the guess will be attempted based on
the <replaceable>filename</replaceable>. For <term>gramps</term>
and <term>iso</term> formats, the <replaceable>filename</replaceable>
is actually the name of directory the gramps database will be written
into. For <term>gedcom</term>, <term>wft</term>,
and <term>gramps-pkg</term>, the <replaceable>filename</replaceable>
is the name of the resulting file.
</para>
<para> When more than one output file is given, each has to be
preceded by <command>-i</command> flag. The files are written one
by one, in the specified order.
</para></listitem>
</varlistentry>
<varlistentry><term>Action options</term>
<listitem><para> The action to perform on the imported data can be
specified with the
<command>-a</command> <replaceable>action</replaceable>
option. This is done after all imports are succesfully completed.
Currently available actions are <term>summary</term> (same as
<menuchoice><guimenu>Reports</guimenu><guisubmenu>View</guisubmenu>
<guimenuitem>Summary</guimenuitem></menuchoice>)
and <term>check</term> (same as
<menuchoice><guimenu>Tools</guimenu>
<guisubmenu>Database Processing</guisubmenu>
<guimenuitem>Check and Repair</guimenuitem></menuchoice>).
</para>
<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></listitem>
</varlistentry>
</variablelist>
</sect3>
<sect3 id="cmdline-operation">
<title>Operation</title>
<para>The order of <command>-i</command>, <command>-o</command>,
or <command>-a</command> options does not matter. The actual order
always is: all imports (if any) -> all exports (if any) -> all actions
(if any).</para>
<para>If no <command>-i</command> option is given, gramps will launch
its main window and start the usual interactive session with the empty
database (since there is no data to process, anyway).</para>
<para>If no <command>-o</command> or <command>-a</command> options
are given, gramps will launch its main window and start the usual
interactive session with the database resulted from all imports.
This database resides under
<replaceable>~/.gramps/import</replaceable> directory.</para>
<para>The error encountered during import, export, or action, will
be either dumped to stdout (if these are exceptions handled by gramps)
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>
</sect3>
<sect3 id="cmdline-examples">
<title>Examples</title>
<para>To import four databases (whose formats can be determined from
their names) and then check the resulting database for errors, one may
type:</para>
<para><command>gramps -i</command> <replaceable>file1.ged</replaceable>
<command>-i</command> <replaceable>file2.tgz</replaceable>
<command>-i</command> <replaceable>~/db3</replaceable>
<command>-i</command> <replaceable>file4.wft</replaceable>
<command>-a</command> <replaceable>check</replaceable>
</para>
<para>To explicitly specify the formats in the above example, append
filenames with appropriate <command>-f</command> options:</para>
<para><command>gramps -i</command> <replaceable>file1.ged</replaceable>
<command>-f</command> <replaceable>gedcom</replaceable>
<command>-i</command> <replaceable>file2.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>file4.wft</replaceable>
<command>-f</command> <replaceable>wft</replaceable>
<command>-a</command> <replaceable>check</replaceable>
</para>
<para>To record the database resulting from all imports, supply
<command>-o</command> flag (use <command>-f</command>
if the filename does not allow gramps to guess the format):</para>
<para><command>gramps -i</command> <replaceable>file1.ged</replaceable>
<command>-i</command> <replaceable>file2.tgz</replaceable>
<command>-o</command> <replaceable>~/new-package</replaceable>
<command>-f</command> <replaceable>gramps-pkg</replaceable>
</para>
<para>To import three databases and start interactive gramps
session with the result:</para>
<para><command>gramps -i</command> <replaceable>file1.ged</replaceable>
<command>-i</command> <replaceable>file2.tgz</replaceable>
<command>-i</command> <replaceable>~/db3</replaceable>
</para>
<para>Finally, to start normal interactive session type:</para>
<para> <command>gramps </command></para>
</sect3>
</sect2>

371
doc/gramps-manual/C/custom.xml Normal file
View File

@ -0,0 +1,371 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- ================ Customization ================================ -->
<sect1 id="gramps-prefs">
<title>Settings</title>
<para>To configure &app;, choose
<menuchoice><guimenu>Settings</guimenu>
<guimenuitem>Preferences...</guimenuitem></menuchoice>.
The <guilabel>Preferences</guilabel> dialog contains the following
categories: </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>Usage</title>
<para> This category contains preferences relevant to the
general usage of &app;. It has the following subcategories:</para>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-usage-find">
<title>Find</title>
<variablelist>
<varlistentry><term><guilabel>Enable autocompletion</guilabel></term>
<listitem><para>If this box is checked, &app; will attempt to complete
the text as you type it into text entry fields such as family name,
place of birth, etc. Completion is attempted based on the match
between the beginning of the text being typed and the corresponding
data already stored in the database.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-usage-report">
<title>Report Preferences</title>
<variablelist>
<varlistentry><term><guilabel>Preferred text format</guilabel></term>
<listitem><para> Select the preferred format for text reports
from the available formats listed in this menu.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Preferred graphical format</guilabel></term>
<listitem><para> Select the preferred format for graphical reports
from the available formats listed in this menu.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Preferred paper size</guilabel></term>
<listitem><para> Select the preferred paper size used for reports
from the available sizes listed in this menu.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Default report directory</guilabel></term>
<listitem><para> Choose the default directory for the reports using the
<guibutton>Browse...</guibutton> button or type it in the text entry
field. </para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Default web site directory</guilabel></term>
<listitem><para> Choose the default directory for the web site using the
<guibutton>Browse...</guibutton> button or type it in the text entry
field. </para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-usage-res">
<title>Researcher Information</title>
<variablelist>
<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>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-usage-guess">
<title>Data Guessing</title>
<variablelist>
<varlistentry><term><guilabel>Surname guessing</guilabel></term>
<listitem><para> This option is not currently implemented.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
</sect2>
<!-- =============== Customization Subsection ================ -->
<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>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-display-gen">
<title>General</title>
<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>Show index numbers in child list</guilabel></term>
<listitem><para>
This option is not currently implemented.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-display-date">
<title>Dates and Calendar</title>
<variablelist>
<varlistentry><term><guilabel>Display: Date format</guilabel></term>
<listitem><para> Select the display format for the dates
from the available formats listed in this menu.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Name format</guilabel></term>
<listitem><para> Select the display format for the names
from the available formats listed in this menu.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Entry: Date format</guilabel></term>
<listitem><para> Select the entry format for the dates
from the available formats listed in this menu.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Show calendar format selection menu</guilabel></term>
<listitem><para> Check this box to enable the calendar format selection
menu when you are entering dates in the <guilabel>Event
Editor</guilabel> dialog.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-display-bars">
<title>Toolbar and Statusbar</title>
<variablelist>
<varlistentry><term><guilabel>Toolbar</guilabel></term>
<listitem><para> Select the desired appearance of the toolbar icons
using the radio buttons.
</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>
</sect3>
</sect2>
<!-- =============== Customization Subsection ================ -->
<sect2 id="gramps-prefs-db">
<title>Database</title>
<para> This category contains preferences relevant to the
database itself. It has the following subcategories: </para>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-db-gen">
<title>General</title>
<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>Do not compress XML data file</guilabel></term>
<listitem><para> Check this box to disable compression of the XML
data file. Compression significantly reduces the file size. While it
creates an overhead in performance (some processor cycles must be spent
to decompress the file before use), this overhead is extremely small.
Now that the compression-related bugs have long been fixed, there is
virtually no reason to disable data file compression.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Capitalize surnames</guilabel></term>
<listitem><para> Check this box to capitalize surnames entered into the
database. </para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Autosave interval</guilabel></term>
<listitem><para> Set the interval (in minutes) after which &app; will
automatically save your database. Setting the interval to zero (0)
disables autosaving. </para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Default database directory</guilabel></term>
<listitem><para> Choose the default directory in which &app; starts
looking when saving the database using the <guibutton>Browse...</guibutton>
or type its path into the text entry field. </para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-db-media">
<title>Media Objects</title>
<para>Before describing preferences for media objects, let us
review the background on local and non-local objects. A local object
is the object whose file is stored inside the same directory in which
the &app; database file resides. A non-local object is stored
elsewhere, so that the database has only the reference to the file's
location and some records of the object's properties. </para>
<para>You may choose to store your media objects either locally
or externally. Making your objects local will increase the amount
of disk space consumed by the &app; database directory. However,
if the external file is deleted or removed, &app; will still be able
to use the local copy. In contrast, leaving your objects non-local
will decrease the disk space requirements. However, losing the
original file will render your media object unusable.
</para>
<para>Note that exporting your database to any format will compile
all medial objects, no matter whether they are local or not.
Specifically, export to gramps package will include all the media
object files in the package and change the references accordingly.
Export to CD will copy all media object files to the directory under
the <guilabel>burn:///</guilabel> location in Nautilus and change the
references accordingly. Finally, export to GEDCOM will place all
media object files next to the GEDCOM file with the appropriate
changes in the path names.
</para>
<variablelist>
<varlistentry><term><guilabel>Drag and drop from an external
source</guilabel></term>
<listitem><para> Choose between a reference and a local copy made when
the object is dropped into the gallery. The reference saves disk
space as it does not copy the object. The local copy makes your
database portable as it does not depend on an external file. Consult
your needs to make best choice.</para>
<para>Check the <guilabel>Display global properties editor when
object is dropped</guilabel> box to invoke the global properties
editor after you drop an external object into the gallery.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Drag and drop from an internal
source</guilabel></term>
<listitem><para> Check the <guilabel>Display local properties editor
when object is dropped</guilabel> box to invoke the local properties
editor after you drop an internal object into the gallery.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-db-id">
<title>&app; internal IDs</title>
<variablelist>
<varlistentry><term><guilabel> GRAMPS ID prefixes</guilabel></term>
<listitem><para> Enter ID prefixes for various kinds of database
entries into the corresponding text entry fields.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Allow internal GRAMPS ID numbers to be
edited</guilabel></term>
<listitem><para> Check this box to enable editing of the internal &app;
ID numbers. Unless you know what you are doing, leave it unchecked.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Customization Sub-subsection ================ -->
<sect3 id="prefs-db-rcs">
<title>Revision Control</title>
<variablelist>
<varlistentry><term><guilabel>Use revision control</guilabel></term>
<listitem><para> Check this box to enable &app; to use the revision control
system for your database. If you choose this option, select the
particular revision control system from the menu.
</para></listitem>
</varlistentry>
<varlistentry><term><guilabel>Prompt for comment on save</guilabel></term>
<listitem><para> Check this box to instruct &app; to prompt you to enter
the comment when you save the database.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
</sect2>
</sect1> <!-- ================ End Customization ================== -->

340
doc/gramps-manual/C/filtref.xml Normal file
View File

@ -0,0 +1,340 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- =============== Appendices Subsection ================ -->
<sect2 id="append-filtref">
<title>Filter rules reference</title>
<para>This appendix provides the list of all the filter rules
which are currently defined in &app;. All these rules are available
for use when creating custom filters. The rules are listed by their
categories.
</para>
<!-- =============== Appendices Sub-subsection ================ -->
<sect3 id="filtref-general">
<title>General filters</title>
<para>This category includes the following most general rules:</para>
<variablelist>
<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>Has a name</term>
<listitem><para> This rule matches any person whose name
matches the specified value. The rule returns a match even if
the person's name matches the value partially. 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 a female</term>
<listitem><para> This rule matches any female person.
</para></listitem>
</varlistentry>
<varlistentry><term>Is a male</term>
<listitem><para> This rule matches any male person.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Appendices Sub-subsection ================ -->
<sect3 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. 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. 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 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. 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. 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>
</variablelist>
</sect3>
<!-- =============== Appendices Sub-subsection ================ -->
<sect3 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>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
birth. 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 in turn 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 whose either parent
is in turn 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 in turn matched by the specified filter.
The specified filter name should be selected from the menu.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Appendices Sub-subsection ================ -->
<sect3 id="filtref-ancestral">
<title>Ancestral filters</title>
<para>This category includes the following rules that match people
based on their being ancestors of 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., of the specified person, but not the parents of
that 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 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 of the specified
person, but not grandparents, great grandparents, etc.,
of that 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 in turn 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 in turn matched by the specified filter.
The specified filter name should be selected from the menu.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Appendices Sub-subsection ================ -->
<sect3 id="filtref-descendant">
<title>Descendant filters</title>
<para>This category includes the following rules that match people
based on their being descendants of 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., of the specified person, but not the children of
that 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 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 of the specified
person, but not grandchildren, great grandchildren, etc.,
of that 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 in turn 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 matches people who are descendants
or the spouse of a descendant of the specified person.
</para></listitem>
</varlistentry>
</variablelist>
</sect3>
<!-- =============== Appendices Sub-subsection ================ -->
<sect3 id="filtref-misc">
<title>Miscellaneous filters</title>
<para>This category includes the following rules which did 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
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>
</sect3>
</sect2>

169
doc/gramps-manual/C/getstart.xml Normal file
View File

@ -0,0 +1,169 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- =========== Getting Started ============================== -->
<sect1 id="gramps-getting-started">
<title>Getting Started</title>
<!-- ================ Getting Started Subsection ====== -->
<sect2 id="gramps-start">
<title>To Start &app;</title>
<para>You can start &app; in the following ways:</para>
<variablelist>
<varlistentry>
<term><guimenu>Applications</guimenu> menu</term>
<listitem><para>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>Return</keycap>.</para>
<para>If you would like &app; to open a specific database or to
import a specific file on startup, you can supply the filename
as a command line argument:</para>
<para>
<command>gramps -i</command> <replaceable>filename.ged</replaceable>
</para>
<para>where <replaceable>filename.ged</replaceable> is the name
of the file you want to open/import. The detailed reference to the
command line options is found in the <xref linkend="append-cmdline"/>.
</para></listitem>
</varlistentry>
</variablelist>
</sect2>
<!-- ================ Getting Started Subsection ==== -->
<sect2 id="run-1st-time">
<title>Running &app; for the first time</title>
<para>
The first time you run the program, GRAMPS will display its
Getting Started dialogs. Follow the directions guiding you through
<guilabel>Researcher information</guilabel>, <guilabel>Numerical date
formats</guilabel>, <guilabel>Alternate calendar support</guilabel>,
and <guilabel>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>&app; Getting Started Window: Researcher Information</title>
<screenshot><mediaobject><imageobject><imagedata
fileref="figures/researcher.png" format="PNG"/></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 not be valid.
</para>
<para>This information can be entered at any time in the
<guilabel>Preferences</guilabel> dialog, under the
<guilabel>Usage</guilabel> category.
</para>
<!-- ================ Getting Started Sub-subsection -->
<sect3 id="choose-db-start">
<title>Choosing a database on startup</title>
<para>If &app; is started without any
database to open, the following window will appear prompting you to
choose what database 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"/></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 start
creating your brand new database from scratch right away, choose new XML
database. </para>
</sect3>
<!-- ================ Getting Started Sub-subsection -->
<sect3 id="zodb-support">
<title>Optional ZODB support</title>
<para>If either StandaloneZODB or Zope is installed on your system,
&app; will give you the third option of
creating a new ZODB database. You can choose to start your new database
in either XML or ZODB format. Both formats have their strong and weak
points.</para>
<para>XML stands for eXtensible Markup Language, and is a human readable
structured description of data. It could be easily parsed by other
programs should the need occur. It stores only the data itself. Its weak
point is the relatively low speed of processing large data files. </para>
<para>ZODB stands for Zope Object Database and provides the full-fledged
database support. ZODB files are not human readable. They contain a
certain overhead to assist working with large data structures. However,
ZODB provides a significant speed-up when the database size is large (over
a few thousand people). </para>
<para>Its is hard to tell which format is better, since this is a typical
trade-off situation. If you are starting your research then you are likely
to be fine with the regular XML database. If you have tons of data to
import describing thousands upon thousands of people, then you are
probably better off with ZODB. </para>
</sect3>
</sect2>
<!-- ================ Getting Started Subsection ==== -->
<sect2 id="get-help">
<title>Obtaining Help</title>
<para> At any time, the following items are available for immediate aid
from the <menuchoice><guimenu>Help</guimenu></menuchoice> menu: </para>
<variablelist>
<varlistentry><term>User manual</term>
<listitem><para> Choose this item to read the text of this manual
in the help browser. </para></listitem>
</varlistentry>
<varlistentry><term>GRAMPS home page</term>
<listitem><para> Select this item to open home page of &app; in your
default web browser. </para></listitem>
</varlistentry>
<varlistentry><term>GRAMPS mailing lists</term>
<listitem><para> Choose this item to direct your web browser
to the &app; mailing list archives. </para></listitem>
</varlistentry>
<varlistentry><term>Report a bug</term>
<listitem><para> Use this item to file a bug report against &app;
with the bug tracking system. </para></listitem>
</varlistentry>
<varlistentry><term>Show plugin status</term>
<listitem><para> Use 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>
</sect2>
</sect1> <!-- ================ End Getting Started ======================== -->

3487
doc/gramps-manual/C/gramps-manual.xml
View File

File diff suppressed because it is too large Load Diff

407
doc/gramps-manual/C/mainwin.xml Normal file
View File

@ -0,0 +1,407 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- ================ Main Window ================================ -->
<sect1 id="gramps-mainwin">
<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">
<title>&app; Main Window</title>
<screenshot><mediaobject><imageobject><imagedata
fileref="figures/mainwin.png" format="PNG"/></imageobject>
<textobject>
<phrase>Shows &app; main window. Contains titlebar, menubar,
toolbar, sidebar, display area, statusbar, progressbar, and
scrollbars. Menubar contains File, Edit, View, 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 -->
<sect2 id="gramps-views">
<title>Views</title>
<para>Views are the various ways to display different aspects of
genealogical information, as described below. Since the relevant
information is very broad and non-uniform in both context and modality,
it is best to split its display into smaller categories, uniform in
context and modality. Each View represents such a split and displays a
certain portion of overall available information. Before the detailed
description of available Views, let us guide you through the ways of
switching between the Views.</para>
<!-- ================ Main Window Sub-subsection -->
<sect3 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"/></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 Notebook 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"/></imageobject>
<textobject>
<phrase>Shows tabbed viewing mode. </phrase>
</textobject></mediaobject></screenshot></figure>
<!-- ==== End of Figure ==== -->
</listitem></varlistentry>
</variablelist>
<para>To switch between sidebar and notebook viewing modes,
choose <menuchoice> <guimenu>View</guimenu>
<guimenuitem>Sidebar</guimenuitem>
</menuchoice> from the &app; menu.</para>
</sect3>
<!-- ================ Main Window Sub-subsection -->
<sect3 id="people-view">
<title>People View</title>
<para>When &app; 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. The People View
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>
<para>Example: 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>
<!-- ================ Main Window Sub-sub-subsection -->
<sect4 id="filters">
<title>Filters</title>
<para>Genealogical databases may contain huge numbers of people.
Since the long lists are hard for humans to handle,
&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"/></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. To invert the filtering rule,
check the <guilabel>Invert</guilabel> box on the left
of <guibutton>Apply</guibutton> button. </para>
<para>Example: To show people without children, choose
<guilabel>People with children</guilabel> filter, then check
<guilabel>Invert</guilabel> box, and then click the
<guibutton>Apply</guibutton> button. To cancel any filtering, set
the filter to <guilabel>All people</guilabel>
and then click the <guibutton>Apply</guibutton> button. </para>
<para>Note: 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. 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>
</sect4>
<!-- ================ Main Window Sub-sub-subsection -->
<sect4 id="alpha-tabs">
<title>Alphabetical Tabs</title>
<para>&app; offers another way of
managing long lists of people -- alphabetical tabs. Upon loading a
database, &app; checks for the stored
family names and breaks the people list into sublists based on the
first letter of their name. The alphabetical tabs are displayed in
the bottom part of the &app; window.
The last tab, <guilabel>Other</guilabel>, stands for unidentified
characters -- all the entries not assigned to any other tab end up
in <guilabel>Other</guilabel>. In particular, people with no family
name will appear under this category.</para>
</sect4>
</sect3>
<!-- ================ Main Window Sub-subsection -->
<sect3 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"/></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 items 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. </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.) 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.</para>
</sect3>
<!-- ================ Main Window Sub-subsection -->
<sect3 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"/></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 white 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 changes color 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>
<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. </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>
</sect3>
<!-- ================ Main Window Sub-subsection -->
<sect3 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"/></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,
i.e. 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.</para>
</sect3>
<!-- ================ Main Window Sub-subsection -->
<sect3 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"/></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. </para>
</sect3>
<!-- ================ Main Window Sub-subsection -->
<sect3 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"/></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 Name, ID, Type, and
Path to the Media Object. The top part of the GRAMPS window shows
a preview (if available) and information about the Media
Object. </para>
</sect3>
</sect2>
</sect1> <!-- ================ End Main Window ===================== -->

2602
doc/gramps-manual/C/usage.xml Normal file
View File

File diff suppressed because it is too large Load Diff

132
src/po/ru.po
View File

@ -7,7 +7,7 @@ msgstr ""
"Project-Id-Version: gramps 0.9.4\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: Sat Sep 13 17:25:35 2003\n"
"PO-Revision-Date: 2003-09-14 12:36-0500\n"
"PO-Revision-Date: 2003-09-22 10:51-0500\n"
"Last-Translator: Alexander Roitman <shura@alex.neuro.umn.edu>\n"
"Language-Team: Russian <ru@li.org>\n"
"MIME-Version: 1.0\n"
@ -691,7 +691,7 @@ msgstr "Общие фильтры"
#: GenericFilter.py:134
msgid "Matches everyone in the database"
msgstr "Выявляет·каждого в базе данных"
msgstr "Выявляет каждого в базе данных"
#: GenericFilter.py:147 GenericFilter.py:192 GenericFilter.py:282
#: GenericFilter.py:327 GenericFilter.py:411 GenericFilter.py:456
@ -703,7 +703,7 @@ msgstr "ID:"
#: GenericFilter.py:153
msgid "Matches the person with a specified GRAMPS ID"
msgstr "Вывляет·лицо·с указанным GRAMPS·ID"
msgstr "Выявляет лицо с указанным GRAMPS ID"
#: GenericFilter.py:178
msgid "Matches all females"
@ -721,7 +721,7 @@ msgstr "Фильтры потомков"
#: GenericFilter.py:206
msgid "Matches all descendants for the specified person"
msgstr "Выявляет всех потомков·указанного лица"
msgstr "Выявляет всех потомков указанного лица"
#: GenericFilter.py:241 GenericFilter.py:370 GenericFilter.py:512
#: GenericFilter.py:656 GenericFilter.py:746 GenericFilter.py:1115
@ -748,11 +748,11 @@ msgstr "Выявляет людей, являющихся потомками у
msgid ""
"Matches people that are descendants of a specified person at least N "
"generations away"
msgstr "Выявляет·людей,·являющихся·потомками·указанного·лица·и·отстоящими·от·него·по крайней мере·на·N·поколений"
msgstr "Выявляет людей, являющихся потомками указанного лица и отстоящими от него по крайней мере на N поколений"
#: GenericFilter.py:381
msgid "Matches the person that is a child of someone matched by a filter"
msgstr "Выявляет·людей,·являющихся·детьми·лица, соответствующего фильтру"
msgstr "Выявляет людей, являющихся детьми лица, соответствующего фильтру"
#: GenericFilter.py:384 GenericFilter.py:670 GenericFilter.py:903
#: GenericFilter.py:1147
@ -763,7 +763,7 @@ msgstr "Семейные фильтры"
msgid ""
"Matches people that are descendants or the spouse of a descendant of a "
"specified person"
msgstr "Выявляет·людей,·являющихся·потомками·или супругами потомков указанного·лица"
msgstr "Выявляет людей, являющихся потомками или супругами потомков указанного лица"
#: GenericFilter.py:467
msgid "Matches people that are ancestors of a specified person"
@ -776,23 +776,23 @@ msgstr "Фильры предков"
#: GenericFilter.py:521
msgid "Matches people that are ancestors of of someone matched by a filter"
msgstr "Выявляет·людей,·являющихся·предками·лица, соответствующего фильтру"
msgstr "Выявляет людей, являющихся предками лица, соответствующего фильтру"
#: GenericFilter.py:565
msgid ""
"Matches people that are ancestors of a specified person not more than N "
"generations away"
msgstr "Выявляет·людей,·являющихся·предками·указанного·лица·и·отстоящими·от·него·не·более·чем·на·N·поколений"
msgstr "Выявляет людей, являющихся предками указанного лица и отстоящими от него не более чем на N поколений"
#: GenericFilter.py:617
msgid ""
"Matches people that are ancestors of a specified person at least N "
"generations away"
msgstr "Выявляет·людей,·являющихся·потомками·указанного·лица·и·отстоящими·от·него·по крайней мере·на·N·поколений"
msgstr "Выявляет людей, являющихся потомками указанного лица и отстоящими от него по крайней мере на N поколений"
#: GenericFilter.py:667
msgid "Matches the person that is a parent of someone matched by a filter"
msgstr "Выявляет·людей,·являющихся·родителями·лица,·соответствующего фильтру"
msgstr "Выявляет людей, являющихся родителями лица, соответствующего фильтру"
#: GenericFilter.py:706
msgid "Matches people that have a common ancestor with a specified person"
@ -801,7 +801,7 @@ msgstr "Выявляет людей, имеющих общего предка с
#: GenericFilter.py:752
msgid ""
"Matches people that have a common ancestor with someone matched by a filter"
msgstr "Выявляет людей, имеющих общего предка с лицом, соответствующим·фильтру"
msgstr "Выявляет людей, имеющих общего предка с лицом, соответствующим фильтру"
#: GenericFilter.py:786
msgid "Matches all males"
@ -833,7 +833,7 @@ msgstr "Личное событие:"
#: GenericFilter.py:813
msgid "Matches the person with a personal event of a particular value"
msgstr "Выявляет·людей с персональным событием определенного значения"
msgstr "Выявляет людей с персональным событием определенного значения"
#: GenericFilter.py:816 GenericFilter.py:863 GenericFilter.py:965
#: GenericFilter.py:1005
@ -846,7 +846,7 @@ msgstr "Семейное событие:"
#: GenericFilter.py:860
msgid "Matches the person with a family event of a particular value"
msgstr "Выявляет людей·с·семейным·событием·определенного·значения"
msgstr "Выявляет людей с семейным событием определенного значения"
#: GenericFilter.py:892
msgid "Number of relationships:"
@ -862,15 +862,15 @@ msgstr "Количество детей:"
#: GenericFilter.py:900
msgid "Matches the person who has a particular relationship"
msgstr "Выявляет·людей, состоящих в определенном отношении"
msgstr "Выявляет людей, состоящих в определенном отношении"
#: GenericFilter.py:962
msgid "Matches the person with a birth of a particular value"
msgstr "Выявляет людей·с·рождением·определенного·значения"
msgstr "Выявляет людей с рождением определенного значения"
#: GenericFilter.py:1002
msgid "Matches the person with a death of a particular value"
msgstr "Выявляет людей·со смертью·определенного·значения"
msgstr "Выявляет людей со смертью определенного значения"
#: GenericFilter.py:1028 GenericFilter.py:1050 edit_person.glade:2452
#: imagesel.glade:834 imagesel.glade:1591
@ -904,11 +904,11 @@ msgstr "Имя:"
#: GenericFilter.py:1082
msgid "Matches the person with a specified (partial) name"
msgstr "Выявляет людей·с·указанным (частично)·именем"
msgstr "Выявляет людей с указанным (частично) именем"
#: GenericFilter.py:1144
msgid "Matches the person married to someone matching a filter"
msgstr "Выявляет·людей,·состоящих в браке·с·лицом,·соответствующим фильтру"
msgstr "Выявляет людей, состоящих в браке с лицом, соответствующим фильтру"
#: GenericFilter.py:1291
msgid "Everyone"
@ -952,7 +952,7 @@ msgstr "Является потомком лица, отстоящим от не
#: GenericFilter.py:1302
msgid "Is a descendant of person at least N generations away"
msgstr "Является·потомком·лица,·отстоящим·от·него·по крайней мере·на·N·поколений"
msgstr "Является потомком лица, отстоящим от него по крайней мере на N поколений"
#: GenericFilter.py:1304
msgid "Is a child of filter match"
@ -968,11 +968,11 @@ msgstr "Является предком соответствующего фил
#: GenericFilter.py:1307
msgid "Is an ancestor of person not more than N generations away"
msgstr "Является·предком·лица,·отстоящим·от·него·не·более·чем·на·N·поколений"
msgstr "Является предком лица, отстоящим от него не более чем на N поколений"
#: GenericFilter.py:1309
msgid "Is an ancestor of person at least N generations away"
msgstr "Является·предком·лица,·отстоящим·от·него·по крайней мере·на·N·поколений"
msgstr "Является предком лица, отстоящим от него по крайней мере на N поколений"
#: GenericFilter.py:1311
msgid "Is a parent of filter match"
@ -7873,91 +7873,3 @@ msgstr "<b>Выравнивание</b>"
msgid "<b>Paragraph options</b>"
msgstr "<b>Параметры абзаца</b>"
#~ msgid "Exactly two people must be selected to perform a merge."
#~ msgstr "Ровно два лица должны быть выделены чтобы произвести слияние."
#~ msgid "_Default Person"
#~ msgstr "Лицо По _Умолчанию"
#~ msgid "Open"
#~ msgstr "Открыть"
#~ msgid "Save"
#~ msgstr "Сохранить"
#~ msgid "Add"
#~ msgstr "Добавить"
#~ msgid "Remove"
#~ msgstr "Удалить"
#~ msgid "%(female_name)s%(endnotes)s died %(death_date)s%(death_endotes)s."
#~ msgstr ""
#~ "%(female_name)s%(endnotes)s умерла %(death_date)s%(death_endnotes)s."
#~ msgid "Title String"
#~ msgstr "Заглавная Строка"
#~ msgid "Contents"
#~ msgstr "Содержание"
#~ msgid "Timeline"
#~ msgstr "Временная Линия"
#~ msgid "<b>Rule Modifiers</b>"
#~ msgstr "<b>Дополнения к правилам</b>"
#~ msgid "Relationship to %{father}s"
#~ msgstr "Отношение %{father}s"
#~ msgid "Relationship to %{mother}s"
#~ msgstr "Отношение к %{mother}s"
#~ msgid "Accept and close"
#~ msgstr "Принять и закрыть"
#~ msgid "Reject changes and close"
#~ msgstr "Отвергнуть измемения и закрыть"
#~ msgid "Accept changes and close dialog"
#~ msgstr "Принять изменения и закрыть диалог"
#~ msgid "Restrict data on living people"
#~ msgstr "Ограничить данные о живущих лицах"
#~ msgid "Delete %s"
#~ msgstr "Уничтожить %s"
#~ msgid "T_ype"
#~ msgstr "Т_ип"
#~ msgid ""
#~ "The file you should attempt to open should be a directory that contains a "
#~ "data.gramps file or a gramps.zodb file."
#~ msgstr ""
#~ "Файл, который вы должны пытаться открыть, должен быть каталогом, "
#~ "содержащим файл data.gramps или файл gramps.zodb."
#~ msgid "The directory ~/.gramps/example could not be created.\n"
#~ msgstr "Каталог ~/.gramps/example не смог быть создан.\n"
#~ msgid "Ancestors Report"
#~ msgstr "Отчет о Предках"
#~ msgid "Copyright String"
#~ msgstr "Строка Копирайт"
#~ msgid "Export to CD (nautilus)"
#~ msgstr "Экспорт на CD (наутилус)"
#, fuzzy
#~ msgid "Full Family Chart"
#~ msgstr "Веерная Карта"
#, fuzzy
#~ msgid "Full Family Chart for %s"
#~ msgstr "Веерная Карта для %s"
#, fuzzy
#~ msgid "Save Full Family Chart"
#~ msgstr "Сохранить Веерную Карту"