diff --git a/ChangeLog b/ChangeLog index 54d9d1f3e..99f6278c1 100644 --- a/ChangeLog +++ b/ChangeLog @@ -2,7 +2,7 @@ * doc/gramps-manual/ru: Add directory with russian manual translation to CVS. * doc/gramps-manual/ru/Makefile.am, - doc/gramps-manual/ru/Makefile.am, + doc/gramps-manual/ru/Makefile.in, doc/gramps-manual/ru/cmdline.xml, doc/gramps-manual/ru/custom.xml, doc/gramps-manual/ru/faq.xml, @@ -15,46 +15,7 @@ doc/gramps-manual/ru/usage.xml, doc/gramps-manual/ru/gramps-manual-ru.omf doc/gramps-manual/ru/figures, - doc/gramps-manual/ru/figures/bookreport.png - doc/gramps-manual/ru/figures/cfe-ar.png - doc/gramps-manual/ru/figures/cfe-df.png - doc/gramps-manual/ru/figures/edit-ad.png - doc/gramps-manual/ru/figures/edit-an.png - doc/gramps-manual/ru/figures/edit-at.png - doc/gramps-manual/ru/figures/edit-bm.png - doc/gramps-manual/ru/figures/edit-ev.png - doc/gramps-manual/ru/figures/edit-media.png - doc/gramps-manual/ru/figures/edit-person-addresses.png - doc/gramps-manual/ru/figures/edit-person-attributes.png - doc/gramps-manual/ru/figures/edit-person-events.png - doc/gramps-manual/ru/figures/edit-person-gallery.png - doc/gramps-manual/ru/figures/edit-person-internet.png - doc/gramps-manual/ru/figures/edit-person-lds.png - doc/gramps-manual/ru/figures/edit-person-names.png - doc/gramps-manual/ru/figures/edit-person-notes.png - doc/gramps-manual/ru/figures/edit-person-sources.png - doc/gramps-manual/ru/figures/edit-person.png - doc/gramps-manual/ru/figures/edit-plc.png - doc/gramps-manual/ru/figures/edit-rel.png - doc/gramps-manual/ru/figures/edit-si.png - doc/gramps-manual/ru/figures/edit-src.png - doc/gramps-manual/ru/figures/edit-wi.png - doc/gramps-manual/ru/figures/family-alt.png - doc/gramps-manual/ru/figures/family.png - doc/gramps-manual/ru/figures/first-open.png - doc/gramps-manual/ru/figures/gedcom-export-progress.png - doc/gramps-manual/ru/figures/gedcom-export.png - doc/gramps-manual/ru/figures/gedcom-import.png - doc/gramps-manual/ru/figures/mainwin.png - doc/gramps-manual/ru/figures/media.png - doc/gramps-manual/ru/figures/missing-media.png - doc/gramps-manual/ru/figures/noside-nofilt.png - doc/gramps-manual/ru/figures/pedigree-child-cut.png - doc/gramps-manual/ru/figures/pedigree.png - doc/gramps-manual/ru/figures/places.png - doc/gramps-manual/ru/figures/researcher.png - doc/gramps-manual/ru/figures/side-filt.png - doc/gramps-manual/ru/figures/sources.png: Add to CVS. + doc/gramps-manual/ru/figures/*.png: Add to CVS. * doc/gramps-manual/Makefile.am: Add ru to the SUBDIR list. * configure.in: Add doc/gramps-manual/ru/Makefile to AC_CONFIG_FILES. diff --git a/doc/gramps-manual/ru/Makefile.am b/doc/gramps-manual/ru/Makefile.am new file mode 100644 index 000000000..c2616404a --- /dev/null +++ b/doc/gramps-manual/ru/Makefile.am @@ -0,0 +1,15 @@ +figdir = figures +docname = gramps-manual +lang = ru +omffile = gramps-manual-ru.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 diff --git a/doc/gramps-manual/ru/Makefile.in b/doc/gramps-manual/ru/Makefile.in new file mode 100644 index 000000000..cbb6920ab --- /dev/null +++ b/doc/gramps-manual/ru/Makefile.in @@ -0,0 +1,401 @@ +# Makefile.in generated by automake 1.6.3 from Makefile.am. +# @configure_input@ + +# Copyright 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002 +# Free Software Foundation, Inc. +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + +@SET_MAKE@ + +# +# No modifications of this Makefile should be necessary. +# +# To use this template: +# 1) Define: figdir, docname, lang, omffile, and entities in +# your Makefile.am file for each document directory, +# although figdir, omffile, and entities may be empty +# 2) Make sure the Makefile in (1) also includes +# "include $(top_srcdir)/doc/xmldocs.make" and +# "dist-hook: app-dist-hook". +# 3) Optionally define 'entities' to hold xml entities which +# you would also like installed +# 4) Figures must go under $(figdir)/ and be in PNG format +# 5) You should only have one document per directory +# 6) Note that the figure directory, $(figdir)/, should not have its +# own Makefile since this Makefile installs those figures. +# +# example Makefile.am: +# figdir = figures +# docname = scrollkeeper-manual +# lang = C +# omffile=scrollkeeper-manual-C.omf +# entities = fdl.xml +# include $(top_srcdir)/help/xmldocs.make +# dist-hook: app-dist-hook +# +# About this file: +# This file was taken from scrollkeeper_example2, a package illustrating +# how to install documentation and OMF files for use with ScrollKeeper +# 0.3.x and 0.4.x. For more information, see: +# http://scrollkeeper.sourceforge.net/ +# Version: 0.1.2 (last updated: March 20, 2002) +# + +# +# No modifications of this Makefile should be necessary. +# +# This file contains the build instructions for installing OMF files. It is +# generally called from the makefiles for particular formats of documentation. +# +# Note that you must configure your package with --localstatedir=/var/lib +# so that the scrollkeeper-update command below will update the database +# in the standard scrollkeeper directory. +# +# If it is impossible to configure with --localstatedir=/var/lib, then +# modify the definition of scrollkeeper_localstate_dir so that +# it points to the correct location. Note that you must still use +# $(localstatedir) in this or when people build RPMs it will update +# the real database on their system instead of the one under RPM_BUILD_ROOT. +# +# Note: This make file is not incorporated into xmldocs.make because, in +# general, there will be other documents install besides XML documents +# and the makefiles for these formats should also include this file. +# +# About this file: +# This file was taken from scrollkeeper_example2, a package illustrating +# how to install documentation and OMF files for use with ScrollKeeper +# 0.3.x and 0.4.x. For more information, see: +# http://scrollkeeper.sourceforge.net/ +# Version: 0.1.2 (last updated: March 20, 2002) +# +SHELL = @SHELL@ + +srcdir = @srcdir@ +top_srcdir = @top_srcdir@ +VPATH = @srcdir@ +prefix = @prefix@ +exec_prefix = @exec_prefix@ + +bindir = @bindir@ +sbindir = @sbindir@ +libexecdir = @libexecdir@ +datadir = @datadir@ +sysconfdir = @sysconfdir@ +sharedstatedir = @sharedstatedir@ +localstatedir = @localstatedir@ +libdir = @libdir@ +infodir = @infodir@ +mandir = @mandir@ +includedir = @includedir@ +oldincludedir = /usr/include +pkgdatadir = $(datadir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkgincludedir = $(includedir)/@PACKAGE@ +top_builddir = ../../.. + +ACLOCAL = @ACLOCAL@ +AUTOCONF = @AUTOCONF@ +AUTOMAKE = @AUTOMAKE@ +AUTOHEADER = @AUTOHEADER@ + +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +INSTALL = @INSTALL@ +INSTALL_PROGRAM = @INSTALL_PROGRAM@ +INSTALL_DATA = @INSTALL_DATA@ +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_SCRIPT = @INSTALL_SCRIPT@ +INSTALL_HEADER = $(INSTALL_DATA) +transform = @program_transform_name@ +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : + +EXEEXT = @EXEEXT@ +OBJEXT = @OBJEXT@ +PATH_SEPARATOR = @PATH_SEPARATOR@ +AMTAR = @AMTAR@ +AWK = @AWK@ +BINSH = @BINSH@ +CC = @CC@ +DEPDIR = @DEPDIR@ +GNOMEHELP = @GNOMEHELP@ +GNOMEINC = @GNOMEINC@ +GNOMELIB = @GNOMELIB@ +GPREFIX = @GPREFIX@ +HAVE_PKG_CONFIG = @HAVE_PKG_CONFIG@ +ICONV = @ICONV@ +INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@ +LANGUAGES = @LANGUAGES@ +MOFILES = @MOFILES@ +MSGCONV = @MSGCONV@ +MSGFMT = @MSGFMT@ +PACKAGE = @PACKAGE@ +POFILES = @POFILES@ +PYTHON = @PYTHON@ +PYTHON_CPPFLAGS = @PYTHON_CPPFLAGS@ +PYTHON_EXEC_PREFIX = @PYTHON_EXEC_PREFIX@ +PYTHON_PLATFORM = @PYTHON_PLATFORM@ +PYTHON_PREFIX = @PYTHON_PREFIX@ +PYTHON_VERSION = @PYTHON_VERSION@ +RELEASE = @RELEASE@ +SCROLLKEEPER_BUILD_REQUIRED = @SCROLLKEEPER_BUILD_REQUIRED@ +SK_CONFIG = @SK_CONFIG@ +STRIP = @STRIP@ +SWIG = @SWIG@ +VERSION = @VERSION@ +VERSIONSTRING = @VERSIONSTRING@ +ZIP = @ZIP@ +am__include = @am__include@ +am__quote = @am__quote@ +install_sh = @install_sh@ +pkgpyexecdir = @pkgpyexecdir@ +pkgpythondir = @pkgpythondir@ +pyexecdir = @pyexecdir@ +pythondir = @pythondir@ +figdir = figures +docname = gramps-manual +lang = ru +omffile = gramps-manual-ru.omf +entities = legal.xml\ + getstart.xml\ + mainwin.xml\ + usage.xml\ + custom.xml\ + faq.xml\ + keybind.xml\ + filtref.xml\ + cmdline.xml + + +# ************* Begin of section some packagers may need to modify ************** +# This variable (docdir) specifies where the documents should be installed. +# This default value should work for most packages. +docdir = $(datadir)/@PACKAGE@/gnome/help/@PACKAGE@/$(lang) + +# ************** You should not have to edit below this line ******************* +xml_files = $(entities) $(docname).xml +omf_dir = $(top_srcdir)/omf-install + +EXTRA_DIST = $(xml_files) $(omffile) + +CLEANFILES = omf_timestamp *.out + +omf_dest_dir = $(datadir)/omf/@PACKAGE@ +scrollkeeper_localstate_dir = $(localstatedir)/scrollkeeper +subdir = doc/gramps-manual/ru +mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs +CONFIG_CLEAN_FILES = +DIST_SOURCES = +DIST_COMMON = Makefile.am Makefile.in +all: all-am + +.SUFFIXES: +$(srcdir)/Makefile.in: Makefile.am $(top_srcdir)/doc/xmldocs.make $(top_srcdir)/doc/omf.make $(top_srcdir)/configure.in $(ACLOCAL_M4) + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu doc/gramps-manual/ru/Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe) +uninstall-info-am: +tags: TAGS +TAGS: + +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) + +top_distdir = ../../.. +distdir = $(top_distdir)/$(PACKAGE)-$(VERSION) + +distdir: $(DISTFILES) + @list='$(DISTFILES)'; for file in $$list; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + dir=`echo "$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test "$$dir" != "$$file" && test "$$dir" != "."; then \ + dir="/$$dir"; \ + $(mkinstalldirs) "$(distdir)$$dir"; \ + else \ + dir=''; \ + fi; \ + if test -d $$d/$$file; then \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \ + fi; \ + cp -pR $$d/$$file $(distdir)$$dir || exit 1; \ + else \ + test -f $(distdir)/$$file \ + || cp -p $$d/$$file $(distdir)/$$file \ + || exit 1; \ + fi; \ + done + $(MAKE) $(AM_MAKEFLAGS) \ + top_distdir="${top_distdir}" distdir="$(distdir)" \ + dist-hook +check-am: all-am +check: check-am +all-am: Makefile + +installdirs: + +install: install-am +install-exec: install-exec-am +install-data: install-data-am +uninstall: uninstall-am + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-am +install-strip: + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + INSTALL_STRIP_FLAG=-s \ + `test -z '$(STRIP)' || \ + echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install +mostlyclean-generic: + +clean-generic: + -test -z "$(CLEANFILES)" || rm -f $(CLEANFILES) + +distclean-generic: + -rm -f Makefile $(CONFIG_CLEAN_FILES) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." +clean: clean-am + +clean-am: clean-generic mostlyclean-am + +distclean: distclean-am + +distclean-am: clean-am distclean-generic + +dvi: dvi-am + +dvi-am: + +info: info-am + +info-am: + +install-data-am: install-data-local + @$(NORMAL_INSTALL) + $(MAKE) $(AM_MAKEFLAGS) install-data-hook + +install-exec-am: + +install-info: install-info-am + +install-man: + +installcheck-am: + +maintainer-clean: maintainer-clean-am + +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-am + +mostlyclean-am: mostlyclean-generic + +uninstall-am: uninstall-info-am uninstall-local + +.PHONY: all all-am check check-am clean clean-generic distclean \ + distclean-generic distdir dvi dvi-am info info-am install \ + install-am install-data install-data-am install-data-local \ + install-exec install-exec-am install-info install-info-am \ + install-man install-strip installcheck installcheck-am \ + installdirs maintainer-clean maintainer-clean-generic \ + mostlyclean mostlyclean-generic uninstall uninstall-am \ + uninstall-info-am uninstall-local + + +omf: omf_timestamp + +omf_timestamp: $(omffile) + -for file in $(omffile); do \ + scrollkeeper-preinstall $(docdir)/$(docname).xml $(srcdir)/$$file $$file.out; \ + done + touch omf_timestamp + +install-data-hook-omf: + $(mkinstalldirs) $(DESTDIR)$(omf_dest_dir) + for file in $(omffile); do \ + $(INSTALL_DATA) $$file.out $(DESTDIR)$(omf_dest_dir)/$$file; \ + done + -scrollkeeper-update -p $(scrollkeeper_localstate_dir) -o $(DESTDIR)$(omf_dest_dir) + +uninstall-local-omf: + -for file in $(srcdir)/*.omf; do \ + basefile=`basename $$file`; \ + rm -f $(omf_dest_dir)/$$basefile; \ + done + -rmdir $(omf_dest_dir) + -scrollkeeper-update -p $(scrollkeeper_localstate_dir) + +all: omf + +$(docname).xml: $(entities) + -ourdir=`pwd`; \ + cd $(srcdir); \ + cp $(entities) $$ourdir + +.PHONY: distclean-hook +distclean: distclean-hook +distclean-hook: + if [ $(top_srcdir) != $(top_builddir) ]; \ + then \ + rm -f $(entities); \ + fi + +app-dist-hook: + if test "$(figdir)"; then \ + $(mkinstalldirs) $(distdir)/$(figdir); \ + for file in $(srcdir)/$(figdir)/*.png; do \ + basefile=`echo $$file | sed -e 's,^.*/,,'`; \ + $(INSTALL_DATA) $$file $(distdir)/$(figdir)/$$basefile; \ + done \ + fi + +install-data-local: omf + $(mkinstalldirs) $(DESTDIR)$(docdir) + for file in $(xml_files); do \ + cp $(srcdir)/$$file $(DESTDIR)$(docdir); \ + done + if test "$(figdir)"; then \ + $(mkinstalldirs) $(DESTDIR)$(docdir)/$(figdir); \ + for file in $(srcdir)/$(figdir)/*.png; do \ + basefile=`echo $$file | sed -e 's,^.*/,,'`; \ + $(INSTALL_DATA) $$file $(DESTDIR)$(docdir)/$(figdir)/$$basefile; \ + done \ + fi + +install-data-hook: install-data-hook-omf + +uninstall-local: uninstall-local-doc uninstall-local-omf + +uninstall-local-doc: + -if test "$(figdir)"; then \ + for file in $(srcdir)/$(figdir)/*.png; do \ + basefile=`echo $$file | sed -e 's,^.*/,,'`; \ + rm -f $(DESTDIR)/$(docdir)/$(figdir)/$$basefile; \ + done; \ + rmdir $(DESTDIR)$(docdir)/$(figdir); \ + fi + -for file in $(xml_files); do \ + rm -f $(DESTDIR)$(docdir)/$$file; \ + done + -rmdir $(DESTDIR)$(docdir) +dist-hook: app-dist-hook +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: diff --git a/doc/gramps-manual/ru/cmdline.xml b/doc/gramps-manual/ru/cmdline.xml new file mode 100644 index 000000000..7ae0c00d5 --- /dev/null +++ b/doc/gramps-manual/ru/cmdline.xml @@ -0,0 +1,247 @@ + + + + + + + + Command line reference + This appendix provides the reference to the command line + capabilities available when launching &app; from the terminal. + + 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 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! + + + 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! + + + + + Available options + + Here is the list of the command line options in &app;: + + + + + Format options + The format of any file destined for import or export + can be specified with the + -f format + option. The format can be one of the + following: + + + + gramps + &app; database. This format is available + for both import and export. When not specified, it can be + guessed if the filename represents a directory. + + + gedcom + GEDCOM file. This format is available + for both import and export. When not specified, it can be + guessed if the filename ends with .ged + + + gramps-pkg + &app; package. This format is available + for both import and export. When not specified, it can be + guessed if the filename ends with .tgz + + + wft + Web Family Tree. This format is available + for export only. When not specified, it can be guessed + if the filename ends with .wft + + + iso + CD image. This format is available + for export only. It must always be specified explicitly. + + + + + + + + Import options + The files destined for import can be specified with + the + -i filename + option. The format can be specified with the -f + option immediately following the filename. + If not specified, the guess will be attempted based on + the filename. For gramps + format, the filename is actually the + name of directory under which the gramps database resides. For + gedcom and gramps-pkg, the + filename is the name of the + corresponding file. + + + When more than one input file is given, each has to be preceded + by -i flag. The files are imported in the + specified order, i.e. + -i file1 + -i file2 + and + -i file2 + -i file1 + might produce different gramps IDs in the resulting database. + + + + + Export options + The files destined for export can be specified with + the + -o filename + option. The format can be specified with the -f + option immediately following the filename. + If not specified, the guess will be attempted based on + the filename. For gramps + and iso formats, the filename + is actually the name of directory the gramps database will be written + into. For gedcom, wft, + and gramps-pkg, the filename + is the name of the resulting file. + + + When more than one output file is given, each has to be + preceded by -o flag. The files are written one + by one, in the specified order. + + + + Action options + The action to perform on the imported data can be + specified with the + -a action + option. This is done after all imports are successfully completed. + Currently available actions are summary (same as + ReportsView + Summary) + and check (same as + Tools + Database Processing + Check and Repair). + + + When more than one output action is given, each has to be + preceded by -a flag. The actions are performed + one by one, in the specified order. + + + + + + + + + + Operation + + The order of -i, -o, + or -a 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). + + If no -i 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). + + If no -o or -a 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 + ~/.gramps/import directory. + + Any errors 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. + + + + + Examples + To import four databases (whose formats can be determined from + their names) and then check the resulting database for errors, one may + type: + gramps -i file1.ged + -i file2.tgz + -i ~/db3 + -i file4.wft + -a check + + + To explicitly specify the formats in the above example, append + filenames with appropriate -f options: + gramps -i file1.ged + -f gedcom + -i file2.tgz + -f gramps-pkg + -i ~/db3 + -f gramps + -i file4.wft + -f wft + -a check + + + To record the database resulting from all imports, supply + -o flag (use -f + if the filename does not allow gramps to guess the format): + gramps -i file1.ged + -i file2.tgz + -o ~/new-package + -f gramps-pkg + + + To save any error messages of the above example into files + outfile and + errfile, run: + gramps -i file1.ged + -i file2.tgz + -o ~/new-package + -f gramps-pkg + >outfile + 2>errfile + + + To import three databases and start interactive gramps + session with the result: + gramps -i file1.ged + -i file2.tgz + -i ~/db3 + + + Finally, to start normal interactive session type: + gramps + + + + diff --git a/doc/gramps-manual/ru/custom.xml b/doc/gramps-manual/ru/custom.xml new file mode 100644 index 000000000..d0510ffd2 --- /dev/null +++ b/doc/gramps-manual/ru/custom.xml @@ -0,0 +1,398 @@ + + + + + + + + + + Settings + To configure &app;, choose + Edit + Preferences.... + The Preferences dialog contains the following + categories: + + + + + + + + + + Usage + This category contains preferences relevant to the + general usage of &app;. It has the following subcategories: + + + + Find + + + + Enable autocompletion + 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. + + + + + + + + + + Report Preferences + + + + Preferred text format + Select the preferred format for text reports + from the available formats listed in this menu. + + + + Preferred graphical format + Select the preferred format for graphical reports + from the available formats listed in this menu. + + + + Preferred paper size + Select the preferred paper size used for reports + from the available sizes listed in this menu. + + + + Default report directory + Choose the default directory for the reports using the + Browse... button or type it in the text entry + field. + + + Default web site directory + Choose the default directory for the web site using the + Browse... button or type it in the text entry + field. + + + + + + + + + Researcher Information + + + + Researcher information + 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. + + + + + + + + + + Data Guessing + + + + Family name guessing + This option affects the initial family name of a + child when he/she is added to the database. NOTE: this option only + affects the initial family name guessed by &app; when the + Edit Person 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. + + If None is selected, no guessing will be + attempted. Selecting Father's surname will use + the family name of the father. Selecting Combination of + mother's and father's surname will use the father's name + followed by the mother's name. Finally, Icelandic + style will use the father's given name followed by the + "sson" suffix (e.g. the son of Edwin will be guessed as + Edwinsson). + + + + + + + + + + + + Display + This category contains preferences relevant to + displaying database records and controls in &app;. + It has the following subcategories: + + + + General + + + + Default view + This determines which view will appear when you + start &app;. Choose between Person and Family views. + + + + Family view style + This selects between the two available styles of the Family + view layout. The Left to right style is similar to the + Family Tree Maker (tm), while the Top to bottom is + similar to the Reunion. + + + + Always display the LDS ordinance tabs + Check this box to have LDS ordinance tabs displayed. + If you do not know what LDS is then you probably should not check it. + + + + Show index numbers in child list + + This option is not currently implemented. + + + + + + + + + Dates and Calendar + + + + Display: Date format + Select the display format for the dates + from the available formats listed in this menu. + + + + Name format + Select the display format for the names + from the available formats listed in this menu. + + + + Entry: Date format + Select the entry format for the dates + from the available formats listed in this menu. + + + + Show calendar format selection menu + Check this box to enable the calendar format selection + menu when you are entering dates in the Event + Editor dialog. This will allow you to select different + calendars when editing the dates. + + + + + + + + + Toolbar and Statusbar + + + Toolbar + Select the desired appearance of the toolbar icons + from the menu. Selecting GNOME Settings will use + the overall settings selected for your GNOME desktop. + + + + Statusbar + Select the desired contents displayed in the + statusbar using the radio buttons. + + + + + + + + + + + Database + This category contains preferences relevant to the + database itself. It has the following subcategories: + + + + General + + + + Automatically load last database + Check this box to automatically load the last open + database on startup. + + + Do not compress XML data file + 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. + + + + Autosave interval + Set the interval (in minutes) after which &app; will + automatically save your database. Setting the interval to zero (0) + disables autosaving. + + + Default database directory + Choose the default directory in which &app; starts + looking when saving the database using the Browse... + or type its path into the text entry field. + + + + + + + + Media Objects + + 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. + + 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. + + + 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 burn:/// 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. + + + + + Drag and drop from an external + source + 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. + + Check the Display global properties editor when + object is dropped box to invoke the global properties + editor after you drop an external object into the gallery. + + + + Drag and drop from an internal + source + Check the Display local properties editor + when object is dropped box to invoke the local properties + editor after you drop an internal object into the gallery. + + + + + + + + + &app; internal IDs + + + + GRAMPS ID prefixes + Enter ID prefixes for various kinds of database + entries into the corresponding text entry fields. + + + + Allow internal GRAMPS ID numbers to be + edited + Check this box to enable editing of the internal &app; + ID numbers. Unless you know what you are doing, leave it unchecked. + + + + + + + + + Revision Control + + + + Use revision control + 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. + + + + Prompt for comment on save + Check this box to instruct &app; to prompt you to enter + the comment when you save the database. + + + + + + + + + + diff --git a/doc/gramps-manual/ru/faq.xml b/doc/gramps-manual/ru/faq.xml new file mode 100644 index 000000000..d14046ea0 --- /dev/null +++ b/doc/gramps-manual/ru/faq.xml @@ -0,0 +1,371 @@ + + + + + + + + Frequently Asked Questions + 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 gramps-devel@lists.sf.net + + + + + + What is &app;? + &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. + + + + Where do I get it and how much does it cost? + +&app; can be downloaded from http://sf.net/projects/gramps 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. + + + + Does it work with Windows (tm)? + +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. + + + + Does it work with the Mac? + +The Fink project (http://fink.sf.net) has ported an old version of +&app; (0.8.0) to OSX. The Mac OSX port is not directly supported by +the &app; project, primarily because none of the &app; developers +have access to Mac OSX. + +The GNOME 2 version of &app; (0.9.x) does not appear to have been +ported by the Fink project. Please contact the Fink project for more +information. + + + + Does it work with KDE? + +Yes, as long as the required GNOME libraries are installed. + + + + Do I really have to have GNOME installed? + Yes, but you do not have to be running the GNOME desktop. + + + + What version of GNOME do I need? + +The latest versions of gramps (0.9.0 and higher) require GNOME 2.0 or higher. +Previous versions required GNOME 1.X. + + + + Is &app; compatible with + other genealogical software (GenApps)? + +&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. + + +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! + + + + Can &app; read files created by GenApp X? + See above. + + + + Can &app; write files readable by GenApp X? + See above. + + + + Can &app; print a genealogical tree for my family? + +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. + + +&app; can produce any of the above, and many more different charts and +reports. Moreover, the plugin architechture enables users (you) to create +their own plugins which could be new reports, charts, or research tools. + + + + In what formats can &app; output its reports? + +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. + + + + Is &app; compatible with the Internet? + +&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 :-) + + + + Can I create custom reports/filters/whatever? + +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. + + + + What standards does &app; support? + +The nice thing about the 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, Familty Tree Maker, Ftree, +GeneWeb, Legacy, Personal Ancestral File, Pro-Gen, Reunion, and +Visual Genealogie. + + + + What is the maximum database + size (bytes) &app; can handle? + +&app; has no hard limits on the size of a database that it can handle. +In reality, however, there are practical limits. Currently &app; loads all +data into memory, so the limiting factor tends to be the available memory +on the system. + + + + How many people can &app; database handle? + +We have found that on a typical system, &app; tends to bog down after the +database has around 15,000 people. Again, this is dependant on how much +memory you have. + + + + Why is &app; running so slowly? + +If &app; seems too slow to you, it is most likely that you have a large +database. Currently, &app; loads all the database into memory, therefore +large databases tend to be less than responsive. Specifically, the system +can be virtually brought to its knees if swapping is needed for &app;' data. + +This will be addressed in the next stable release following version 1.0. +Temporarily, adding more memory could make a huge difference, but we realize +that this is a poor way of treating the problem. If you would like to help +with the implementation of the real database backend, please don't hesitate +to email us at gramps-devel@lists.sf.net + + + + My database is really big. + Is there a way around loading all the data into memory? + +Currently, there is no way around it. However, this is our biggest priority +after releasing version 1.0. The real database backend will be incorporated +in the next stable release (1.2) which will dramatically improve performance +in both speed and memory usage. + + + + Why are non-latin characters displayed + as garbage in PDF/PS reports? + +This is a known problem -- PS (and PDF) have builtin fonts which pretty much +reflect the latin-1 charset. Any font in principle could be used with PS/PDF +but then it would have to be embedded in the file. This is problematic since +every system has different idea about fonts and their setup. + + +This should be resolved as we move to gnome-print. In the meantime, a useable +workaround is to generate reports in OpenOffice.org format and then export +to PDF from the OpenOffice.org application. + + + + Why can I not add/remove/edit columns to the lists + in People View and Family View? + +This will be addressed after the TreeModelSort bug is fixed in pygtk, +see http://bugzilla.gnome.org/show_bug.cgi?id=125172 + for the details. +Once the patch is committed and incorporated into pygtk, we will add the +ability to add/remove/edit sortable columns. + + + + I would like to contribute to &app; by writing + my favorite report. How do I do that? + +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 following page may provide some help in writing your +own plugin from scratch. + +If you need more help or would like to discuss your idea with us, +please do not hesitate to contact us at gramps-devel@lists.sf.net + + + +To test your work in progress, you may save your plugin under +$HOME/.gramps/plugins 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. + + +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 gramps-devel@lists.sf.net + + + + + I found a bug and I want it fixed right now! + What do I do? + +The best thing you can do is to fix the bug and send the patch to +gramps-devel@lists.sf.net :-) + + +The next best thing would be to submit a good bug report. This can be done in +one of the two ways: (1) send your report to +gramps-bugs@lists.sf.net +or (2) file your report with the bug tracker system at + +http://sf.net/tracker/?group_id=25770&atid=385137 +(this function is also available by selecting +HelpReport a +bug from gramps main menu). + +A good bug report would include: + + + + +Version of gramps you were using when you encountered the bug +(available through Help +About menu item). + + + +Language under which gramps was run +(available by executing + echo $LANG +in your terminal). + + + +Symptoms indicating that this is indeed a bug. + + + +Any Traceback messages, error messages, warnings, etc, +that showed up in your terminal or a in separate traceback window. + + + + +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. + +If the above explanations seem vague, please follow +this link. + + + + + 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? + +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 compatability +or import/export options to your new format of a project. + + +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. + + +HINT: if &app; developers are still not convinced after about three +messages sent to gramps-devel, maybe you are better off on your own +rather than with a company of retards who can't fully realize the +potential of your great idea :-) + + + + + + + diff --git a/doc/gramps-manual/ru/figures/bookreport.png b/doc/gramps-manual/ru/figures/bookreport.png new file mode 100644 index 000000000..d75e2be42 Binary files /dev/null and b/doc/gramps-manual/ru/figures/bookreport.png differ diff --git a/doc/gramps-manual/ru/figures/cfe-ar.png b/doc/gramps-manual/ru/figures/cfe-ar.png new file mode 100644 index 000000000..dac17db40 Binary files /dev/null and b/doc/gramps-manual/ru/figures/cfe-ar.png differ diff --git a/doc/gramps-manual/ru/figures/cfe-df.png b/doc/gramps-manual/ru/figures/cfe-df.png new file mode 100644 index 000000000..e921df094 Binary files /dev/null and b/doc/gramps-manual/ru/figures/cfe-df.png differ diff --git a/doc/gramps-manual/ru/figures/edit-ad.png b/doc/gramps-manual/ru/figures/edit-ad.png new file mode 100644 index 000000000..1da6f5ecb Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-ad.png differ diff --git a/doc/gramps-manual/ru/figures/edit-an.png b/doc/gramps-manual/ru/figures/edit-an.png new file mode 100644 index 000000000..e5e888978 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-an.png differ diff --git a/doc/gramps-manual/ru/figures/edit-at.png b/doc/gramps-manual/ru/figures/edit-at.png new file mode 100644 index 000000000..177d95eaa Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-at.png differ diff --git a/doc/gramps-manual/ru/figures/edit-bm.png b/doc/gramps-manual/ru/figures/edit-bm.png new file mode 100644 index 000000000..5963f0297 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-bm.png differ diff --git a/doc/gramps-manual/ru/figures/edit-ev.png b/doc/gramps-manual/ru/figures/edit-ev.png new file mode 100644 index 000000000..e01fe7ba9 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-ev.png differ diff --git a/doc/gramps-manual/ru/figures/edit-media.png b/doc/gramps-manual/ru/figures/edit-media.png new file mode 100644 index 000000000..be20a689d Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-media.png differ diff --git a/doc/gramps-manual/ru/figures/edit-person-addresses.png b/doc/gramps-manual/ru/figures/edit-person-addresses.png new file mode 100644 index 000000000..faf82d417 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-person-addresses.png differ diff --git a/doc/gramps-manual/ru/figures/edit-person-attributes.png b/doc/gramps-manual/ru/figures/edit-person-attributes.png new file mode 100644 index 000000000..dd675deac Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-person-attributes.png differ diff --git a/doc/gramps-manual/ru/figures/edit-person-events.png b/doc/gramps-manual/ru/figures/edit-person-events.png new file mode 100644 index 000000000..0e7901959 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-person-events.png differ diff --git a/doc/gramps-manual/ru/figures/edit-person-gallery.png b/doc/gramps-manual/ru/figures/edit-person-gallery.png new file mode 100644 index 000000000..020e983de Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-person-gallery.png differ diff --git a/doc/gramps-manual/ru/figures/edit-person-internet.png b/doc/gramps-manual/ru/figures/edit-person-internet.png new file mode 100644 index 000000000..7eb22fd04 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-person-internet.png differ diff --git a/doc/gramps-manual/ru/figures/edit-person-lds.png b/doc/gramps-manual/ru/figures/edit-person-lds.png new file mode 100644 index 000000000..345a352dd Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-person-lds.png differ diff --git a/doc/gramps-manual/ru/figures/edit-person-names.png b/doc/gramps-manual/ru/figures/edit-person-names.png new file mode 100644 index 000000000..8aee3841e Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-person-names.png differ diff --git a/doc/gramps-manual/ru/figures/edit-person-notes.png b/doc/gramps-manual/ru/figures/edit-person-notes.png new file mode 100644 index 000000000..9b2e512c1 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-person-notes.png differ diff --git a/doc/gramps-manual/ru/figures/edit-person-sources.png b/doc/gramps-manual/ru/figures/edit-person-sources.png new file mode 100644 index 000000000..b30eb6640 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-person-sources.png differ diff --git a/doc/gramps-manual/ru/figures/edit-person.png b/doc/gramps-manual/ru/figures/edit-person.png new file mode 100644 index 000000000..e079ae93c Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-person.png differ diff --git a/doc/gramps-manual/ru/figures/edit-plc.png b/doc/gramps-manual/ru/figures/edit-plc.png new file mode 100644 index 000000000..54781f759 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-plc.png differ diff --git a/doc/gramps-manual/ru/figures/edit-rel.png b/doc/gramps-manual/ru/figures/edit-rel.png new file mode 100644 index 000000000..fa48b0572 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-rel.png differ diff --git a/doc/gramps-manual/ru/figures/edit-si.png b/doc/gramps-manual/ru/figures/edit-si.png new file mode 100644 index 000000000..881734ff7 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-si.png differ diff --git a/doc/gramps-manual/ru/figures/edit-src.png b/doc/gramps-manual/ru/figures/edit-src.png new file mode 100644 index 000000000..8a3d2d818 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-src.png differ diff --git a/doc/gramps-manual/ru/figures/edit-wi.png b/doc/gramps-manual/ru/figures/edit-wi.png new file mode 100644 index 000000000..4b8725c75 Binary files /dev/null and b/doc/gramps-manual/ru/figures/edit-wi.png differ diff --git a/doc/gramps-manual/ru/figures/family-alt.png b/doc/gramps-manual/ru/figures/family-alt.png new file mode 100644 index 000000000..3655536dd Binary files /dev/null and b/doc/gramps-manual/ru/figures/family-alt.png differ diff --git a/doc/gramps-manual/ru/figures/family.png b/doc/gramps-manual/ru/figures/family.png new file mode 100644 index 000000000..73a1d784d Binary files /dev/null and b/doc/gramps-manual/ru/figures/family.png differ diff --git a/doc/gramps-manual/ru/figures/first-open.png b/doc/gramps-manual/ru/figures/first-open.png new file mode 100644 index 000000000..4cce3f73c Binary files /dev/null and b/doc/gramps-manual/ru/figures/first-open.png differ diff --git a/doc/gramps-manual/ru/figures/gedcom-export-progress.png b/doc/gramps-manual/ru/figures/gedcom-export-progress.png new file mode 100644 index 000000000..63bc4b2ab Binary files /dev/null and b/doc/gramps-manual/ru/figures/gedcom-export-progress.png differ diff --git a/doc/gramps-manual/ru/figures/gedcom-export.png b/doc/gramps-manual/ru/figures/gedcom-export.png new file mode 100644 index 000000000..494000951 Binary files /dev/null and b/doc/gramps-manual/ru/figures/gedcom-export.png differ diff --git a/doc/gramps-manual/ru/figures/gedcom-import.png b/doc/gramps-manual/ru/figures/gedcom-import.png new file mode 100644 index 000000000..421c7ae34 Binary files /dev/null and b/doc/gramps-manual/ru/figures/gedcom-import.png differ diff --git a/doc/gramps-manual/ru/figures/mainwin.png b/doc/gramps-manual/ru/figures/mainwin.png new file mode 100644 index 000000000..13d00528e Binary files /dev/null and b/doc/gramps-manual/ru/figures/mainwin.png differ diff --git a/doc/gramps-manual/ru/figures/media.png b/doc/gramps-manual/ru/figures/media.png new file mode 100644 index 000000000..b10de5a7a Binary files /dev/null and b/doc/gramps-manual/ru/figures/media.png differ diff --git a/doc/gramps-manual/ru/figures/missing-media.png b/doc/gramps-manual/ru/figures/missing-media.png new file mode 100644 index 000000000..732be92cd Binary files /dev/null and b/doc/gramps-manual/ru/figures/missing-media.png differ diff --git a/doc/gramps-manual/ru/figures/noside-nofilt.png b/doc/gramps-manual/ru/figures/noside-nofilt.png new file mode 100644 index 000000000..5455f8244 Binary files /dev/null and b/doc/gramps-manual/ru/figures/noside-nofilt.png differ diff --git a/doc/gramps-manual/ru/figures/pedigree-child-cut.png b/doc/gramps-manual/ru/figures/pedigree-child-cut.png new file mode 100644 index 000000000..b09ac2023 Binary files /dev/null and b/doc/gramps-manual/ru/figures/pedigree-child-cut.png differ diff --git a/doc/gramps-manual/ru/figures/pedigree.png b/doc/gramps-manual/ru/figures/pedigree.png new file mode 100644 index 000000000..d525e5874 Binary files /dev/null and b/doc/gramps-manual/ru/figures/pedigree.png differ diff --git a/doc/gramps-manual/ru/figures/places.png b/doc/gramps-manual/ru/figures/places.png new file mode 100644 index 000000000..6bcbaa867 Binary files /dev/null and b/doc/gramps-manual/ru/figures/places.png differ diff --git a/doc/gramps-manual/ru/figures/researcher.png b/doc/gramps-manual/ru/figures/researcher.png new file mode 100644 index 000000000..c73102822 Binary files /dev/null and b/doc/gramps-manual/ru/figures/researcher.png differ diff --git a/doc/gramps-manual/ru/figures/side-filt.png b/doc/gramps-manual/ru/figures/side-filt.png new file mode 100644 index 000000000..b3c31ae17 Binary files /dev/null and b/doc/gramps-manual/ru/figures/side-filt.png differ diff --git a/doc/gramps-manual/ru/figures/sources.png b/doc/gramps-manual/ru/figures/sources.png new file mode 100644 index 000000000..7c01e5045 Binary files /dev/null and b/doc/gramps-manual/ru/figures/sources.png differ diff --git a/doc/gramps-manual/ru/filtref.xml b/doc/gramps-manual/ru/filtref.xml new file mode 100644 index 000000000..a4f91847e --- /dev/null +++ b/doc/gramps-manual/ru/filtref.xml @@ -0,0 +1,386 @@ + + + + + + + + + Filter rules reference + This appendix lists of all the filter rules currently defined + in &app;. Each of these rules is available for use when creating custom + filters. The rules are listed by their categories. + + + + + General filters + This category includes the following most general rules: + + + + Everyone + 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. + + + + Has a name + 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. + + + 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. + + + + Has the Id + This rule matches any person with a specified + &app; ID. The rule returns a match only if the ID is matched + exactly. + + + You can either enter the ID into a text entry field, or + select a person from the list by clicking + Select... button. In the latter case, the + ID will appear in the text field after the selection was made. + + + + Is a female + This rule matches any female person. + + + + Is a male + This rule matches any male person. + + + + + + + + + + Event filters + This category includes the following rules that match people + based on their recorded events: + + + Has the birth + 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. + + + 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. + + + + Has the death + 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. + + + 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. + + + + Has the personal event + 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. + + + 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. + + + + Has the family event + 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. + + + 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. + + + + + + + + + + Family filters + This category includes the following rules that match people + based on their family relationships: + + + Has the relationships + 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. + + + 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. + + + + Is spouse of filter match + This rule matches people married to someone + who is matched by the specified filter. + The specified filter name should be selected from the menu. + + + + Is a child of filter match + This rule matches people for whom either parent + is matched by the specified filter. + The specified filter name should be selected from the menu. + + + + Is a parent of filter match + This rule matches people whose child + is matched by the specified filter. + The specified filter name should be selected from the menu. + + + + + + + + + Ancestral filters + This category includes the following rules that match people + based on their ancestral relations to other people: + + + Is an ancestor of + 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). + + + You can either enter the ID into a text entry field, or + select a person from the list by clicking + Select... button. In the latter case, the + ID will appear in the text field after the selection was made. + + + + Is an ancestor of person at + least N generations away + 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. + + + + Is an ancestor of person not more + than N generations away + 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. + + + + Has a common ancestor with + This rule matches people who have common ancestors + with the specified person. + + + + Has a common ancestor with filter match + 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. + + + + Is an ancestor of filter match + 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. + + + + + + + + + Descendant filters + This category includes the following rules that match people + based on their descendant relations to other people: + + + Is a descendant of + 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). + + + You can either enter the ID into a text entry field, or + select a person from the list by clicking + Select... button. In the latter case, the + ID will appear in the text field after the selection was made. + + + + Is a descendant of person at + least N generations away + 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. + + + + Is a descendant of person not more + than N generations away + 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. + + + + Is a descendant of filter match + 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. + + + + Is a descendant family member of + This rule not only matches people who are + descendants of the specified person, but also those descendants' + spouses. + + + + + + + + + Relationship filters + This category includes the following rules that match people + based on their mutual relationship: + + + Relationship path between two people + This rule matches all ancestors of both people + back to their common ancestors (if exist). This produces the + "relationship path" between these two people, through + their common ancestors. + + + You can either enter the ID of each person into the + appropriate text entry fields, or select people from the list by + clicking their Select... buttons. In the + latter case, the ID will appear in the text field after the + selection was made. + + + + + + + + + + Miscellaneous filters + This category includes the following rules which do not + naturally fit into any of the above categories: + + + Has the personal attribute + 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. + + + + Has the family attribute + 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. + + + + Matches the filter named + This rule matches people who are matched + by the specified filter. + The specified filter name should be selected from the menu. + + + + + + + diff --git a/doc/gramps-manual/ru/getstart.xml b/doc/gramps-manual/ru/getstart.xml new file mode 100644 index 000000000..e758df265 --- /dev/null +++ b/doc/gramps-manual/ru/getstart.xml @@ -0,0 +1,210 @@ + + + + + + + + + + Getting Started + + + + To Start &app; + You can start &app; in the following ways: + + + Applications menu + Choose Other + Gramps. + + + Command line + To start &app; from a command line, type + gramps, then press Return. + + 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: + + + gramps -i filename.ged + + + where filename.ged is the name + of the file you want to open/import. The detailed reference to the + command line options is found in the . + + + + + + + + Running &app; for the first time + + The first time you run the program, GRAMPS will display its + Getting Started dialogs. Follow the directions guiding you through + Researcher information, Numerical date + formats, Alternate calendar support, + and LDS extensions sections. Most of the dialogs + are self-explanatory and will not be covered here. + + + +
+ &app; Getting Started Window: Researcher Information + + + Shows Researcher Information Window. +
+ + + Enter your personal information in the corresponding + text entry fields. Although &app; requests information about you, + this information is used only so that &app; can create valid GEDCOM + output files. A valid GEDCOM file requires information about the file's + creator. If you choose, you may leave the information empty, however + all the GEDCOM files you export will not be valid. + + + This information can be entered at any time in the + Preferences dialog, under the + Usage category. + + + + + + + Choosing a database on startup + If &app; is started without any + database to open, the following window will appear prompting you to + choose what database to open. + + +
+ Open Database Window + + + Shows Open Database Window. +
+ + + If you would like to open an existing database, check the top radio + button and click the OK 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. + + NOTE: when starting new database, you should + select an empty DIRECTORY + and NOT a FILE. Create empty directory if + needed. The directory you specify will be used by &app; to store + database file data.gramps as well as any + possible copies of media objects. This directory will be updated by &app; + each time the database is saved. + + NOTE: when opening an existing database, you should + open a DIRECTORY and + NOT a FILE. The directory you need to open + should contain the database file data.gramps + as well as any possible copies of media objects. Such a directory is + created by &app; when you start a new database and is updated each time + the database is saved. + + + + + + + + Obtaining Help + At any time, the following items are available for immediate aid + from the Help menu: + + + + User manual + Choose this item to read the text of this manual + in the help browser. + + + FAQ + Use this item to read Frequently Asked Questions + about &app; in the browser. + + + GRAMPS home page + Select this item to open home page of &app; in your + default web browser. + + + GRAMPS mailing lists + Choose this item to direct your web browser + to the &app; mailing list archives. + + + Report a bug + Use this item to file a bug report against &app; + with the bug tracking system. + + + Show plugin status + Use this item to display the status of loaded + plugins. + + + Open example database + 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;. + + + + + + diff --git a/doc/gramps-manual/ru/gramps-manual-ru.omf b/doc/gramps-manual/ru/gramps-manual-ru.omf new file mode 100644 index 000000000..299d89e53 --- /dev/null +++ b/doc/gramps-manual/ru/gramps-manual-ru.omf @@ -0,0 +1,18 @@ + + + + Alex Roitman shura@alex.neuro.umn.edu + Руководство пользователя GRAMPS + 2003-12-01 + + + Руководство пользователя GRAMPS. + Руководство пользователя + + + + + + + + diff --git a/doc/gramps-manual/ru/gramps-manual.xml b/doc/gramps-manual/ru/gramps-manual.xml new file mode 100644 index 000000000..8a469cda0 --- /dev/null +++ b/doc/gramps-manual/ru/gramps-manual.xml @@ -0,0 +1,307 @@ + + + + + + + + + + + + + + + + + + + GRAMPS" > + +]> + + +
+ + + + Руководство пользователя &app;, версия &manrevision; + + 2003 Alex Roitman + 2001 Donald N. Allingham + + + + + 2003 + Александр Ройтман (Русский перевод) + + + + + Проект GRAMPS + + &legal; + + + + + Alex + Roitman + + GRAMPS Project +
shura@alex.neuro.umn.edu
+ + + + Donald N. + Allingham + + GRAMPS Project +
dallingham@users.sourceforge.net
+ + + + + + Александр + Ройтман + + Проект GRAMPS +
shura@alex.neuro.umn.edu
+ + Русский перевод + + + + + + + + + + + + + + + + + + + Руководство пользователя &app;, версия &manrevision; + &date; + + Alex Roitman + shura@alex.neuro.umn.edu + Проект GRAMPS + + + + Руководство пользователя &app;, версия 2.3 + Сентябрь 2003 + + Alex Roitman + shura@alex.neuro.umn.edu + Проект GRAMPS + + + + Руководство пользователя &app;, версия 2.2 + Июль 2003 + + Alex Roitman + shura@alex.neuro.umn.edu + Donald A. Peterson + dpeterson@sigmaxi.org + Проект GRAMPS + + + + Руководство пользователя &app;, версия V2.1 + Май 2003 + + Alex Roitman + shura@alex.neuro.umn.edu + + Проект GRAMPS + + + + Руководство пользователя &app;, версия 2.0 + Апрель 2003 + + Alex Roitman + shura@alex.neuro.umn.edu + + Проект GRAMPS + + + + Руководство пользователя &app;, версия 1.1 + 2001 + + Donald N. Allingham + dallingham@users.sourceforge.net + + Проект GRAMPS + + + + Руководство пользователя gramps, версия 1.0 + 2001 + + Donald N. Allingham + dallingham@users.sourceforge.net + + Проект GRAMPS + + + + + Настоящее руководство описывает версию &appversion; программы GRAMPS. + + + Feedback + To report a bug or make a suggestion regarding the &app; application or + this manual, follow the directions in the GNOME Feedback Page. + + + + + + GRAMPS + gramps + + + + + Введение + &app; is a genealogical + application. &app; is an acronym for the + Genealogical Research and Analysis Management Programming System. To put + it shortly, it allows you to store, edit, and research genealogical data + using your computer. Its functionality is somewhat common to other + genealogical programs. However, &app; offers some unique features. + + + Why &app;? + &app; was conceived under the concept + that most genealogy programs were designed to provide the researcher the + capability to input information related to a particular family tree. + Most of these programs have allowed for the arranging and storing of + information consistent with the GEDCOM standards. They usually provide + means for displaying descendant or ancestral relationships by means of + graphical displays, charts, or reports. These may be augmented with + pictures or other media to enhance the data. Most provide for inputting + data on unconnected individuals/families that may or may not have a + relationship to the primary surname being researched. Various other + enhancements may also be provided in the genealogical program that + allows for different degrees of importing and exporting data from other + programs and printing the data contained in the various reports. + + &app;, on the other hand, attempts to + provide all of the common capabilities of these programs, but, more + importantly, to provide an additional capability of integration not common + to these programs. This is the ability to input any bits and pieces of + information directly into &app; and + rearrange/manipulate any/all data events in the entire data base (in any + order or sequence) to assist the user in doing research, analysis and + correlation with the potential of filling relationship gaps. In short, it + is a tool that provides a way to input all your research into one place and + do your analysis and correlation using the speed, power, and accuracy of + your computer instead of pencils and unmanageable reams of paper. + + + + &getstart; + &mainwin; + &usage; + &custom; + + + + + + + + About &app; + &app; was written by Donald N. Allingham + (dallingham@users.sourceforge.net). + To find more information about &app;, please visit the + GRAMPS Project + Web page. + + To report a bug or make a suggestion regarding this application or + this manual, use the help menu in &app;, or follow the directions + in this document. + + + 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 + link, or in the file + COPYING included with the source code of this program. + + + + + + Appendices + + &faq; + &keybind; + &filtref; + &cmdline; + + + +
diff --git a/doc/gramps-manual/ru/keybind.xml b/doc/gramps-manual/ru/keybind.xml new file mode 100644 index 000000000..9fc28a059 --- /dev/null +++ b/doc/gramps-manual/ru/keybind.xml @@ -0,0 +1,264 @@ + + + + + + + + + Keybindings reference + This appendix contains the list of keybindings that are not + displayed in menus of &app;. + + + + + People View + The following bindings are available in the People View: + + + + + + + + Key + Function + + + + + Enter + Invoke Edit Person dialog + with the selected person. + + + + + + + + + + + Family View + The bindings available in the Family View depend on where the + focus is. The following tables list the bindings for all focus + targets. + + + + Focus on the Active Person + + + + + + + + + Key + Function + + + + + Enter + Invoke Edit Person dialog with + the active person. + + + Ctrl+Down + or Ctrl+Right + Swap the Active Person and the selected spouse. + Use Ctrl+Down in standard Family View and + Ctrl+Right in alternative Family + View. + + + + + + + + + + Focus on the Spouse box + + + + + + + + + Key + Function + + + + + Enter + Edit relationship between the Active Person and + the selected spouse. + + + Shift+Enter + Edit the personal information for the selected + spouse. + + + Insert + Add a person from the database to the spouse + list. + + + Shift+Insert + Add a new person to the database and to the spouse + list. + + + Delete + Delete the selected spouse from the spouse + list. The spouse is not deleted from the database. + + + Ctrl+Up + or Ctrl+Left + Swap the selected spouse and the Active Person. + Use Ctrl+Down in standard Family View and + Ctrl+Right in alternative Family + View. + + + + + + + + + + Focus on the Parents box + + + + + + + + + Key + Function + + + + + Enter + Edit relationship between the parents and their + child (either the Active Person or the selected spouse, depending + which parents box the focus is in). + + + Insert + Add a new set of parents from the database to the + list. + + + Shift+Insert + Add a new set of parents to the database and to the + list. + + + Delete + Delete the selected parents from the list. + The parents are not deleted from the database. + + + Ctrl+Right + or Ctrl+Down + Make the selected parents the active family. + Use Ctrl+Right in standard Family View and + Ctrl+Down in alternative Family + View. + + + + + + + + + + Focus on the Children box + + + + + + + + + Key + Function + + + + + Enter + Edit relationship between the child and his/her + parents (the Active Person and the selected + spouse). + + + Shift+Enter + Edit the personal information for the selected + child. + + + Insert + Add a new person from the database to the children + list. + + + Shift+Insert + Add a new person to the database and to the children + list. + + + Delete + Delete the selected child from the list. + The child is not deleted from the database. + + + Ctrl+Left + or Ctrl+Up + Make the selected child the Active Person. + Use Ctrl+Left in standard Family View and + Ctrl+Up in alternative Family + View. + + + + + + + + + + + + + + diff --git a/doc/gramps-manual/ru/legal.xml b/doc/gramps-manual/ru/legal.xml new file mode 100644 index 000000000..ac97e1de4 --- /dev/null +++ b/doc/gramps-manual/ru/legal.xml @@ -0,0 +1,76 @@ + + + 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. You can find + a copy of the GFDL at this link or in the file COPYING-DOCS + distributed with this manual. + + This manual is part of a collection of GNOME manuals + distributed under the GFDL. If you want to distribute this + manual separately from the collection, you can do so by + adding a copy of the license to the manual, as described in + section 6 of the license. + + + + Many of the names used by companies to distinguish their + products and services are claimed as trademarks. Where those + names appear in any GNOME documentation, and the members of + the GNOME Documentation Project are made aware of those + trademarks, then the names are in capital letters or initial + capital letters. + + + + DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED + UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE + WITH THE FURTHER UNDERSTANDING THAT: + + + + DOCUMENT IS PROVIDED ON AN "AS IS" BASIS, + WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR + IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES + THAT THE DOCUMENT OR MODIFIED VERSION OF THE + DOCUMENT IS FREE OF DEFECTS MERCHANTABLE, FIT FOR + A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE + RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE + OF THE DOCUMENT OR MODIFIED VERSION OF THE + DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR + MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, + YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY + CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY + SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER + OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS + LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED + VERSION OF THE DOCUMENT IS AUTHORIZED HEREUNDER + EXCEPT UNDER THIS DISCLAIMER; AND + + + + UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL + THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE), + CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, + INITIAL WRITER, ANY CONTRIBUTOR, OR ANY + DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION + OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH + PARTIES, BE LIABLE TO ANY PERSON FOR ANY + DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR + CONSEQUENTIAL DAMAGES OF ANY CHARACTER + INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS + OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR + MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR + LOSSES ARISING OUT OF OR RELATING TO USE OF THE + DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT, + EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF + THE POSSIBILITY OF SUCH DAMAGES. + + + + + + diff --git a/doc/gramps-manual/ru/mainwin.xml b/doc/gramps-manual/ru/mainwin.xml new file mode 100644 index 000000000..4f8e64935 --- /dev/null +++ b/doc/gramps-manual/ru/mainwin.xml @@ -0,0 +1,473 @@ + + + + + + + + + Main Window + When you open a database (either existing or brand new), + the following window is displayed. + + +
+ &app; Main Window + + + 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. +
+ + + The &app; window contains the following elements: + + Menubar + 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. + + Toolbar + 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 Preferences + dialog. + + Progressbar + 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. + + Statusbar + 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 + Preferences dialog. + + Display area + 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;: + + People View + Family View + Pedigree View + Sources View + Places View + Media View + + + + + + + + + Views + 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. + + + + Switching Views and Viewing Modes + Depending on the state of the + ViewSidebar + menu item, the View could be switched either in the + sidebar or in the notebook tabs in the top part of the window. + + + + To switch the View while in a Sidebar mode, + click on the desired sidebar icon. + + +
+ Sidebar Viewing Mode + + + Shows sidebar viewing mode. +
+ + + + To switch the View while in a Notebook mode, + click on the desired notebook tab. + + +
+ Tabbed Viewing Mode + + + Shows tabbed viewing mode. +
+ + + + + To switch between sidebar and notebook viewing modes, + choose View + Sidebar + from the &app; menu. + + + + + + People View + When &app; first opens a database, + the View is set to the People View ( + and ). The People View lists + individuals whose data is stored in the database. + + 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 contents is listed in the + window. When collapsed, the contents is rolled up and not visible. + However, all the data is still intact, it is just not being displayed. + + + The People View + displays people's Names, + &app; ID numbers, + Gender, and + their Birth and Death dates. + The list can be ordered by any field. + + Example: to order list by the Birth date, click on the + Birth date column heading. To order list in + reverse (descending) order, click one more time on the desired column + heading. + + + + Filters + 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 + View + Filter menu item. + + +
+ Filter Controls Displayed + + + Shows filter controls. +
+ + + When &app; opens a database, the + filter is set to the trivial filter called All + people, i.e. no filtering is in effect. To choose a + filter, use the pop-up Filter menu above the + people's list. Once the filter is chosen, click the + Apply button in the upper right corner of the + window. The filtering will take effect upon clicking the + Apply button. To invert the filtering rule, + check the Invert box on the left + of Apply button. + + Example: To show people without children, choose + People with children filter, then check + Invert box, and then click the + Apply button. To cancel any filtering, set + the filter to All people + and then click the Apply button. + + Note: even if the filter controls are not displayed + ( View + Filter 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 View + Filter menu item and check + what kind of filtering is currently set. + + + + + Alphabetical Tabs + &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, Other, stands for unidentified + characters -- all the entries not assigned to any other tab end up + in Other. In particular, people with no family + name will appear under this category. + + + + + + + Family View + 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.). + + + +
+ Family View + + + Shows Family View. +
+ + + 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. + + 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 + (-) 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. + + 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 + and - + 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 items from the context menu. + + 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 Birth date column + header. In addition to the Name, + ID, Gender, and + Birth date columns, the list includes a + Status 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 - + 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 items from the + context menu. + + 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 + Display section of the + Preferences dialog. The top-to-bottom view + has the same functionality as the left-to-right view. + + +
+ Alternative Family View + + + Shows Alternative Family View. +
+ + + + + + + Pedigree View + + +
+ Pedigree View + + + Shows Pedigree View. +
+ + + 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 + 1 to his/her parents 2, + to grandparents 3, to great-grandparents + 4. + 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 become 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. + + +
+ Children Menu + + + Shows Children Menu in Pedigree View. +
+ + + 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. + + 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. + + + + + Sources View + + +
+ Sources View + + + Shows Sources View. +
+ + + 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 + Title, ID, and the + Author 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. + + + + + Places View + + +
+ Places View + + + Shows Places View. +
+ + + 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' Name, + ID, Church Parish, + City, County, + State, and Country. All of + these columns can be used for sorting by the usual sorting rules. + + + + + Media View + + +
+ Media View + + + Shows Media View. +
+ + + 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. + + + + diff --git a/doc/gramps-manual/ru/usage.xml b/doc/gramps-manual/ru/usage.xml new file mode 100644 index 000000000..72c0899e0 --- /dev/null +++ b/doc/gramps-manual/ru/usage.xml @@ -0,0 +1,2774 @@ + + + + + + + + + Usage + As commonly encountered in everyday life, in + &app; there is usually more than one way to + accomplish something. The alternatives to some actions will therefore + be listed as appropriate. + + + + Starting a New Database + To start a new database, choose File + New. You will then be + prompted with the Save Database dialog asking + to specify the name under which the new database will be stored. + Choose an empty directory for your new + database (create one if necessary). + + + + + Opening a Database + To open a database, either choose + FileOpen + or click the Open button on the Toolbar. + The Open Database dialog will appear. + Either type the full path into the Database text + entry field, or click the Browse... button to get + the Open File dialog in which you can select the + database that you want to open. After you have selected the database, + click the OK button to open it. + + If you have previously opened databases with &app; you can + retrieve your past selections from the drop-down menu by clicking the + down arrow button. Finally, if the Revision Control System (RCS) is + enabled in the Preferences dialog, the check box + Revert to an older version from RCS will be + available. Check it to revert your database to an older RCS + version. + + NOTE: you should open a DIRECTORY and + NOT a FILE when opening + &app; database. The directory you need to open should contain the + database file data.gramps as well as any + possible copies + of media objects. Such a directory is created by &app; when you start + a new database and is updated each time the database is saved. + + + + + Saving a Database + To save changes made to your database, choose + File + Save or click the + Save button on the Toolbar. The statusbar will then + display the Saving databasename... + message, and the progressbar will advance as the saving progresses. + + + + + Importing Data + Importing allows you to incorporate the data from other + databases into your currently open &app; database. Currently, + &app; can import data from three different + formats: GEDCOM, &app; database, and &app; package. All of these are + available as items of File + Import submenu. + + Both &app; database, and &app; package are native &app; + formats. The package is a compressed archive containing the database + file and all media objects (images, sound files, etc.) that the + database refers to. The package is created by exporting data to + the &app; package, see . + The &app; database is a directory containing the database file and + the local media objects. The database may also have references + to non-local (external) media objects, therefore it is not guaranteed + to be completely portable. The &app; database is created by saving + the data in a usual way, see . + + + Note that the difference between opening &app; database and + importing from &app; database is that importing incorporates all the + data into your currently open database, if any. + + After choosing an import format, you will be prompted with the + Open File dialog asking you to specify the + file name from which to import. For GEDCOM and + &app; package, select an appropriate file. + For &app; database, select a directory which stores + the database and all media files (if any). + + Upon starting the GEDCOM import, &app; + will display the following GEDCOM import dialog with the summary of the + information about the data. The information is updated as the import + progresses. + + +
+ GEDCOM Import + + + Shows GEDCOM Import Window. +
+ + + Upon starting the &app; database or &app; package import, + &app; will display the progress in the + progressbar of its main window. + + If a media file is not found during import, the following dialog + will prompt you for the possible actions: + + +
+ Missing Media dialog + + + Shows Missing Media dialog. +
+ + + + + To remove the object corresponding to the missing file as well as + all the references to that object from various database records, click the + Remove Object button. This will alter your + database so that it will be in a consistent state, but all the + references to the missing file will be gone. Use this option if the + file is irrevocably lost and there is no possibility of ever replacing + it. + + + + To keep the reference to the object corresponding to the missing + file, click the Keep Reference button. + This will leave things as is, i.e. in an inconsistent state. + You could supply the missing file later, in which case you will have + to copy it into your database directory. Choose this option if the + replacement is possible, but not available right now. + + + To supply the missing file during import, click the + Select File button. This will copy the file you + select in place of the missing file. No references will be altered + in the database, and it will be in the consistent state. Use this option + if the replacement is readily available. + + + + + + + + + Exporting Data + + Exporting allows you to share any portion of your &app; database + with other researchers as well as to make your database completely + portable to another computer. Currently, &app; + can export data to three different formats: CD, GEDCOM, &app; package, + and Web Family Tree. All of these are available as items of + File + Export submenu. + + Exporting to CD will prepare you database directory with all its + contents to be recorded to the CD. This is done through the + burn:/// location in Nautilus. After exporting to + CD, go to the burn:/// location by + selecting Go + CD Creator in Nautilus menu. Your + database directory will show up. To record it onto the CD, click the CD + icon on the Nautilus toolbar, or select File + Write to CD in Nautilus menu. + + + Exporting to GEDCOM will create a GEDCOM file, according to the + settings set in the following dialog: + + +
+ Export GEDCOM File dialog + + + Shows Export GEDCOM File dialog +
+ + + Type the desired GEDCOM filename into the text entry box or + click the Browse... button to evoke the + Save File dialog. + Choose the desired Encoding of the exported file. + Use the Filter + pop-up menu to limit the scope of the export according to the stated rule. + Use the Target menu to select the desired GEDCOM + dialect. Select your copyright statement from the + Copyright menu. Check Do not include + records marked private to disable the output of private + records. Check Restrict data on living people + to limit living people's data to family ties. With this option, + information concerning birth, death, addresses, various events, + etc. will be omitted in the exported GEDCOM file. If this option is selected, + you can further choose whether to use the word "Living" as first name, exclude + notes, and exclude sources for the living people. Check Reference + images from path to tell &app; to use the specific path for your + images when writing image references in GEDCOM. + + + Upon starting the export, &app; will + display the following GEDCOM export progress window with the + progressbars reflecting the current state of exporting. + + +
+ Export GEDCOM progress dialog + + + Shows Export GEDCOM progress dialog. +
+ + + Exporting to &app; package will create a gzip-compressed tar + archive (also known as tarball) which contains gramps database, all + local media objects, and copies of all external media objects. This is a + useful format for moving your database to another machine or for sharing + it with somebody, while retaining all the features provided + by &app;. + + + Exporting to Web Family Tree will create the text file suitable + as an input for the WFT program. Use the Filter + pop-up menu to limit the scope of the export according to the stated rule. + Check Restrict data on living people to limit living + people's data to family ties. + + + If a media file is not found during export, the following dialog + will prompt you for the possible actions: + + +
+ Missing Media dialog + + + Shows Missing Media dialog. +
+ + + + + To remove the object corresponding to the missing file as well as + all the references to that object from various database records, click + the Remove Object button. This will alter your + database so that it will be in the consistent state, but all the + references to the missing file will be gone. Use this option if the + file is irrevocably lost and there is no possibility of ever replacing + it. + + + + To keep the reference to the object corresponding to the missing + file, click the Keep Reference button. + This will leave things as is, i.e. in the inconsistent state. + You could supply the missing file later, in which case you will have + to copy it into your database directory. Choose this option if the + replacement is possible, but not available right now. + + + To supply the missing file during export, click the + Select File button. This will copy the file you + select in place of the missing file. No references will be altered + in the database, and it will be in the consistent state. Use this option + if the replacement is readily available. + + + + + + + + + Editing Data: Quick Start + Editing any portion of data allows you to amend and/or + modify information stored in the database. The available editing + options include editing personal data, relationship data, data about + children and parents, and information about sources, places, and media + objects used in the database. In short, any data stored in the + database can be edited! Adding a new piece of information is in fact + creating an appropriate empty data structure and subsequent + editing of that empty structure. + + This section refers mainly to the menu items and buttons as the main + way of interacting with &app;. In addition to this, &app; provides an + extensive set of keybindings. The detailed reference to the keybindings + is found in the . + + + + + To Add a Person + To add a person to the database, switch to the People View + () and then click the + Add on the toolbar. + Enter any data you know about this person into the Edit + Person Dialog (see + for details). To edit information about a person already present + in the database, select an entry you would like to view/modify, + and then click the Edit icon on the toolbar. + + You can also use Add... and + Edit... menu items available under + the Edit. Or you can right-click on the person + and select Add... or Edit... + from the invoked context menu. + + + + + + To Specify a Relationship + To specify a relationship, first switch to the Family View + (). Then click one of the two top buttons on + the right of the spouse box. The topmost button adds a new person to the + database and to the relationship, while the second top button adds a person + that is already in a database to the relationship. + + If using the second button, select the spouse/partner from the list + and specify the relationship using the menu at the bottom. If necessary, you + can add a person to the list by clicking the Add... + button. &app; will filter the displayed list of people based on the + relationship type as follows. The relationships Married, Unmarried, Unknown, + and Other will only display people of the sex opposite to that of an active + person. The relationships Partners will only display people of the same sex + as that of an active person. Also, by default, &app; will limit the lists + to people who could possibly be the spouse/partner (judged by the dates of + birth and death) of the active person. To override this, check + the Show all box. + + + + To edit information about a relationship already present in the database, + move the mouse over the Spouse box and double-click. + If the relationship lists has more than one person, you can specify the + preferred spouse/partner by selecting an appropriate item from the context + menu available upon right-clicking into the spouse box. Also, most of the + above function are available from the items of this context menu. + + + + + + To Specify Parents + To specify parents of an active person, first switch to the + Family View (). Then click the + + button on the right of the active person's + parents list box. Select the parents from two lists and specify the + parents' relationships to the active person using menus at the bottom. + You can also specify parents' relationship to each other. + If necessary, you can add a person to the list by clicking the + Add... button. + + The top and bottom lists contain males and females, + respectively. By default, &app; will + limit both lists to people who could possibly be the parents (judged + by the date of birth) of the active person. To override this, check + the Show all box for each list. + + + To specify parents of the active person's spouse, switch to the + Family View and then click the + button on the + right of the spouse's parents list box. To edit information about + parents already present in the database, move the mouse over + the corresponding parents' box and double-click. All these functions can + also be performed by right-clicking on the parents' box and selecting + an appropriate item from the context menu. + + + + + To Specify Children + To specify children of an active person, switch to the + Family View () and then click either the + second of the third button from the top on the right of the children list + box. The second button adds a child to the database and to the family, while + the third button adds a child already present in the database to the family. + + + If using the third button, select a child from the list and + specify the child's relationship with father and mother using menus + at the bottom. If necessary, you can add a person to the list by + clicking the Add... button. By default, &app; will + limit the lists to people who could possibly be the child (judged + by the date of birth) of the active person. To override this, check + the Show all box. + + + + The relationship of the child to the parents can be modified by selecting + an appropriate item from the context menu available upon right-clicking + into the children box. Also, most of the above function are available from + the items of this context menu. + + + + + + To Add Images + You can add images (as well as other media objects) to + individual people, events, sources, places, as well as images + generally related to the database (e.g. group family photos). + + To add images related to a single person, switch to the + People View (), select a person, and + then click the Edit icon on the toolbar to + invoke the Edit Person Dialog + (). Then, select the + Gallery tab, and click the + Add... button to invoke the Select a media + object dialog. Type the filename or select a file with the + image, then provide a title for that image. To prevent the file from + being copied into your database directory, check the Do not + make a local copy box. Keep adding images until you are + done. + + To add images related to a relationship (e.g. marriage), + switch to the Family View () and then + double-click on the Spouse box invoke the Marriage/Relationship + editor dialog. Select the Gallery + tab and click the Add... button to add + an image. + + To add images related to a source or a place, first switch to + the Sources View () or Places + View (), respectively. Then select the + appropriate source or place and then either double-click on it + or click the Edit icon on the toolbar to invoke the + Source Editor (or Place + Editor) dialog. Select the Gallery + tab and click the Add... button to add + an image. + + Finally, to add images that are generally related to the + database but not limited to any person, relationship, source, or place + in particular, switch to the Media View (). + Then click the Add icon on the toolbar to + add an image. + If you have already added any images to any individual galleries, + you will also find them listed in the Media View. + + In any gallery, you can also use the Edit... + and Remove buttons to edit image information + and to remove the image reference from that gallery. Note that in all + galleries removing the reference to the image does not remove the image + from the database. To completely remove the image from the database, + delete it from Media View by first selecting it and then + clicking the Remove icon on the toolbar. + + + + + + To Edit Sources and Places + + To add a source or a place to the database, switch to + the appropriate Sources View () or + Places View (). + Then click the Add icon on the toolbar to add a + source/place. Enter the information into the Source + Editor (or Place Editor) dialog. + + + To edit information about sources and places already present + in the database, switch to the appropriate view, select an entry + you would like to view/modify, and then click the + Edit icon on the toolbar. Alternatively, you + may double-click on the entry to edit it. + + + + + + + + Editing Data: Complete Description + This section provides a complete description of all editing + options for all pieces of data in the &app; database. It refers mainly + to the menu items and buttons as the main way of interacting with &app;. + In addition to this, &app; provides an extensive set of keybindings. + The detailed reference to the keybindings is found in + the . + + + + Edit Personal Information + Editing of personal data can be performed in the + following ways: + + From the People View: + Double-click the name of the person whose data you would like + to edit, or select the name by single click and then click the + Edit icon on the toolbar. You may also select + the name and then press Return. Finally, you may select + Edit... from the Edit + menu of &app; or choose Edit from the context + menu that appears upon right-click on the name. + + From the Family View: + Move the mouse into the Active person box, + then double-click, or use any of the menu items described above. + + + + With either method, the following Edit + Person dialog will appear: + + +
+ Edit Person dialog + + + Shows Edit Person dialog. +
+ + + The top of the window shows the name of the person whose + data is being edited. The main part of the window displays ten + notebook tabs containing different categories of available + information. You can bring any tab to the top for viewing + or editing by clicking on the appropriate tab heading. + The bottom part has OK and + Cancel buttons. Clicking the + OK button + at any time will apply all the changes made in all tabs and close the + dialog window. Clicking the Cancel button at any time will + close the window without applying any changes. If any of the data + in any tab were modified, the alert window will appear with the + choices of closing the dialog without saving changes, canceling the + initial cancel request, or saving the changes. + + + + The tab labels reflect the presence of corresponding information: if the + tab contains any data, its label appears boldface; if the tab has no data + then its label appears regular (not bold). + The tabs provide the following information categories of + personal data: + + + + General + + The General tab allows editing of + general information about the person. This includes the text + entry fields of Given name, + Family name, Family prefix + (such as de or van), Suffix (e.g. Jr. or III), + Title (e.g. Dr. or Rev.), + Nickname (Bob for Robert), + Type of the name (birth name, married name, etc.) + and Date and Place of birth + and death. Some of these (Family name, + Type, and both Place fields), + also allow you to choose the corresponding + contents from the drop-down menus by clicking on the down arrow button + located immediately to the right of the text entry field. The + available menu choices are formed from the information already stored + in the database. Also, when you start to type within these fields, + &app; will try to guess the remainder of + the text by using the same choices that are available from the + corresponding menu. To accept the highlighted guess and move to + the next field, press the Tab. + + + The Gender radio buttons offer + the choice of person's gender between male, + female, and unknown. + The buttons Source... and + Note... allow adding or modifying the data about + the sources of the name information and any relevant notes. + Clicking either Edit... button located next to + the birth and death Date fields will bring up a dialog allowing you to + edit the corresponding event (birth or death) details. + The field ID displays an internal + &app; ID number which identifies the user in the + database. The Image area shows the first + image available in the Gallery of this + person (if any exist). + + + Finally, the Information is complete check + button provides the way to mark whether this person's record is + complete or + not. + + + + + Names + + + +
+ Edit Person dialog - Names + + + Shows Names Tab of Edit Person dialog. +
+ + + The Names tab displays information concerning + alternate names of the person and the controls allowing their + modification. The bottom part displays the list of all alternate names + of the person stored in the database. The top part shows the details + of the currently selected name in the list (if any). The buttons + Add..., Edit..., + and Delete allow the addition, + modification, and removal of an alternate name record from the database. + Note that the Edit... and + Delete buttons become available only when + an alternate name is selected from the list. + + + + + + Events + + + +
+ Edit Person dialog - Events + + + Shows Events Tab of Edit Person dialog. +
+ + + The Events tab displays information about + the events relevant to the person and controls allowing its + modification. The bottom part displays the list of all such events + stored in the database. The top part shows the details + of the currently selected event in the list (if any). The buttons + Add..., Edit..., + and Delete allow you to correspondingly add, + modify, and remove an event record from the database. + Note that the Edit... and + Delete buttons become available only when + an event is selected from the list. + + + + + + Attributes + + + +
+ Edit Person dialog - Attributes + + + Shows Attributes Tab of Edit Person dialog. +
+ + + The Attributes tab displays information about + the attributes of the person and controls allowing their + modification. These could be any personal attributes of a person whose + description naturally fits into Parameter-Value pairs (e.g. enormous + generosity can be stored as the parameter "Generosity" with the + value "Enormous", etc.). The bottom part displays the list of all + attributes stored in the database. The top part shows the details + of the currently selected attribute in the list (if any). The buttons + Add..., Edit..., + and Delete allow you to correspondingly add, + modify, and remove an attribute record from the database. + Note that the Edit... and + Delete buttons become available only when + an attribute is selected from the list. + + + + + + Addresses + + + +
+ Edit Person dialog - Addresses + + + Shows Addresses Tab of Edit Person dialog. +
+ + + The Addresses tab displays information about + the addresses of the person and the controls allowing their + modification. The bottom part displays the list of all + addresses stored in the database. The top part shows the details + of the currently selected address in the list (if any). The buttons + Add..., Edit..., + and Delete allow you to correspondingly add, + modify, and remove an address record from the database. + Note that the Edit... and + Delete buttons become available only when + an address is selected from the list. + + + Some reports allow you to restrict data on living people. + In particular, that option will omit the addresses of people who + are currently alive. + + + + + Notes + + + +
+ Edit Person dialog - Notes + + + Shows Notes Tab of Edit Person dialog. +
+ + + The Notes tab displays information about + the notes concerning the person. These could be any notes which do not + naturally fit into the Parameter-Value pairs available to Attributes. + To add a note or modify existing notes simply edit the text in the + text entry field. + + + + + + Sources + + + +
+ Edit Person dialog - Sources + + + Shows Sources Tab of Edit Person dialog. +
+ + + The Sources tab displays information about + the sources related to the person and controls allowing its modification. + These could be any general sources which refer to the person but do not + describe specifically any event. + For example, Aunt Martha's memoirs may mention her great grandson Paul, + so the researcher may assume that this person (Paul) existed and cite + the memoirs as the source for this assumption. NOTE: sources documenting + specific events are better filed in relation to those events, under the + Events tab. + + The central part displays the list of all source references stored + in the database in relation to the person. The + buttons Add..., + Edit..., and Delete + allow you to correspondingly add, modify, and remove a source reference + to this person. Note that the Edit... and + Delete buttons become available only when + a source reference is selected from the list. + + + + + + + Gallery + + + + + + + The Gallery tab displays information about + media objects associated with the person and controls allowing subsequent + modification. The central part shows the list of all such media objects. + For media object which are valid image files, previews of images are + displayed. For other objects such as audio files, movie files, etc., a + generic &app; icon is displayed instead. Note that the first available + image in the gallery will be also displayed in the + Image area in the General + tab. The buttons Add..., + Edit..., and Remove allow + you to correspondingly add, modify, and remove a media object reference + to this person. Note that the Edit... and + Remove buttons become available only when + a media object is selected from the list. + + + Note: removing a media object from a person's gallery does not + remove it from the database. It only removes the reference to that + object from this person's record. + + + + + + Internet + + + +
+ Edit Person dialog - Internet + + + Shows Internet Tab of Edit Person dialog. +
+ + + The Internet tab displays information about + Internet addresses relevant to the person and the controls + allowing data modification. The bottom part displays the list of all + such Internet addresses stored in the database. The top part shows the + details of the currently selected addresses in the list (if any). + The buttons Add..., + Edit..., and Delete + allow you to correspondingly add, modify, and remove an Internet address + record from the database. The button Go allows + opening a web-page with the corresponding address with your default + browser. Note that the Edit..., + Delete, and Go buttons + become available only when an address is selected from the list. + + + + + + LDS + + + +
+ Edit Person dialog - LDS + + + Shows LDS Tab of Edit Person dialog. +
+ + + The LDS tab displays information + about LDS ordinances of the person and controls allowing + modification. These are LDS baptism, + Endowment, and Sealed to + parents ordinances, as labeled inside the tab. + Each ordinance is described by its date, LDS temple, and Place where + it happened. An additional pop-up menu Parents is + available for the Sealed to parents ordinance. + Each ordinance can further be described by its status through the + selections available in the Status pop-up + menu and can also be referenced by sources and notes via corresponding + Sources... and Note + buttons. + + + + + + + + + Edit Dates + Anywhere in &app; where the date + is entered or edited, the following rules apply: + + + Date validity indicators + &app; uses color + circles to indicate the validity of the entered date. + + + + Green circle means that the date is valid and + complete (e.g. May 24, 1961). + + Yellow circle means that the date is valid but is + partial (i.e. not complete). Examples of partial dates are: 1961, + about 1961, from 1960 to 1962, before 1963. While partial dates do + not exactly define the date, they allow at least for some type of + comparisons between the dates. + + Red circle means that the date is not recognized as + a valid date (e.g. Christmas week of 61). In that case the date will + be stored as a text string. Therefore, no comparison with other dates + will be available. It is best to avoid such date entries. Same + information can be entered as a note for the event of interest instead + of a date. In the example considered, a better things to do is to + enter December 1961 as a date and Christmas week of 61 as a note. + + + + + + + + Acceptable date entries + &app; recognizes many + formats of exact dates. The only problematic formats are XX/XX/XX or + XX-XX-XX because of the ambiguity between the day and the month. + The interpretation for this type of formats is configured + in Getting Started dialog and can also be changed + from the Preferences dialog. + + Besides exact dates, &app; + recognizes and supports partial dates, date ranges, and alternate + calendars. + + + + Partial dates define some portions of the date such + as a year or a year and a month. + + Date ranges define the boundaries containing the + date such as from January 1961 to March 1963. + + Alternate calendars are calendars other than Gregorian + calendar. Currently, &app; supports Hebrew, + French Republican, Julian, Islamic, and Persian alternate calendars. + + + + + + + + + + Edit Relationship Data + Editing of relationship data is performed in the following + Marriage/Relationship Editor dialog which appears + after double-clicking on the spouse box in the Family View. + + +
+ Marriage/Relationship Editor dialog + + + Shows Marriage/Relationship Editor dialog. +
+ + + The top of the window shows the names of the people whose + relationship is being edited. The main part of the window displays + seven notebook tabs containing different categories of available + information. You can bring any tab to the top for viewing + or editing by clicking on the appropriate tab heading. + The bottom part has OK and + Cancel buttons. Clicking the + OK button + at any time will apply all the changes made in all tabs and close the + dialog window. Clicking the Cancel button at any time will + close the window without applying any changes. If any of the data + in any tab were modified, the alert window will appear with the + choices of closing the dialog without saving changes, canceling the + initial cancel request, or saving the changes. + + + The tab labels reflect the presence of corresponding information: if the + tab contains any data, its label appears boldface; if the tab has no data + then its label appears regular (not bold). + The tabs provide the following information categories of + relationship data: + + + + General + + The General tab allows editing of the most general + information about the relationship: the relationship type. + The available types (such as married, partners, etc.) can be chosen + from the drop-down Relationship type menu. + The non-editable field ID displays an + internal &app; ID number which identifies this relationship in + the database. + Finally, the Information is complete check + button provides the way to mark whether this relationship's record is + complete or not. + + + + + Events + + The Events tab displays information about + the events relevant to the relationship and the controls allowing + modification. The bottom part displays the list of all such events + stored in the database. The top part shows the details + of the currently selected event in the list (if any). The buttons + Add..., Edit..., + and Delete allow you to correspondingly add, + modify, and remove an event record from the database. + Note that the Edit... and + Delete buttons become available only when + an event is selected from the list. + + + + + + Attributes + + The Attributes tab displays information about + the attributes of the relationship and the controls allowing + modification. The bottom part displays the list of all such + attributes stored in the database. The top part shows the details + of the currently selected attribute in the list (if any). The buttons + Add..., Edit..., + and Delete allow you to correspondingly add, + modify, and remove an attribute record from the database. + Note that the Edit... and + Delete buttons become available only when + an attribute is selected from the list. + + + + + + Notes + + The Notes tab displays information about the + notes concerning the relationship. These could be any notes which do + not naturally fit into the Parameter-Value pairs available to + Attributes. To add a note or modify existing notes simply edit the + text in the text entry field. + + + + + + Sources + + The Sources tab displays information about + the sources related to the relationship and controls allowing its + modification. These could be any general sources which refer to the + relationship but do not describe specifically any event. + For example, Aunt Martha's memoirs may mention that her great grandson Paul + was married, so the researcher may assume that this relationship (between + Paul and his wife) existed and cite the memoirs as the source for this + assumption. NOTE: sources documenting specific events such as marriages + or divorces are better filed in relation to those events, under the + Events tab. + + The central part displays the list of all source references stored + in the database for this relationship. The + buttons Add..., + Edit..., and Delete + allow you to correspondingly add, modify, and remove a source reference + to this relationship. Note that the Edit... and + Delete buttons become available only when + a source reference is selected from the list. + + + + + + Gallery + + The Gallery tab displays information about + media objects associated with the relationship and the controls allowing + modification of such. The central part shows the list of all such media objects. + For media object which are valid image files previews of images are + displayed. For other objects such as audio files, movie files, etc., a + generic &app; icon is displayed instead. The buttons + Add..., Edit..., + and Remove allow you to correspondingly add, modify, + and remove a media object reference to this relationship. + Note that the Edit... and + Remove buttons become available only when + a media object is selected from the list. + + + + + + LDS + + The LDS tab displays information + about the LDS Sealed to spouse ordinance + of the person and the controls allowing + modification. The data can include date, LDS temple, and Place where + it happened. The ordinance can further be described by its status + through the selections available in the Status + pop-up menu and can also be referenced by sources and notes via + corresponding Sources... and + Note buttons. + + + + + + + + Edit Source Data + To edit source data, switch to the Sources View and select the + desired entry in the list of sources. Double-click on that entry or + click the Edit icon on the toolbar to invoke the + following Source Editor dialog: + + +
+ Source Editor dialog + + + Shows Source Editor dialog. +
+ + + The top of the window shows the Source + Editor + title of the dialog. The main part of the window displays four notebook + tabs containing different categories of available information. You can + bring any tab to the top for viewing or editing by clicking on the + appropriate tab heading. The bottom part has OK + and Cancel buttons. Clicking the + OK button at any time will apply all the changes made + in all tabs and close the dialog window. Clicking the + Cancel button at any time will close the window without + applying any changes. If any of the data in any tab were modified, + the alert window will appear with the choices of closing the dialog + without saving changes, canceling the initial cancel request, or saving + the changes. + + + The tab labels reflect the presence of corresponding information: if the + tab contains any data, its label appears boldface; if the tab has no data + then its label appears regular (not bold). + The tabs provide the following information categories of + source data: + + + + General + The + General tab allows editing of the most general + information about the source: its title, author, and publication + information. This information can be typed in the appropriate + text entry fields. + + + + + + Note + + The Note tab displays any notes concerning + the source. To add a note or modify existing notes simply edit the + text in the text entry field. + + + + + + Gallery + + The Gallery tab displays information about + media objects associated with the given source and controls + allowing its modification. The central part shows the list of all + such media objects. For media object which are valid image files + previews of images are displayed. For other objects such as audio + files, movie files, etc., a generic &app; icon is displayed instead. + The buttons Add..., + Edit..., and Remove allow + you to correspondingly add, modify, and remove a media object reference + to this source. Note that the Edit... and + Remove buttons become available only when + a media object is selected from the list. + + + + + + References + + The References tab displays information about + database records that refer to this source. If the source is not + referenced from any database record, the tab shows an empty list. + If the source is referenced from many records, the tab will list + all of them. The list can be ordered by any of its column headers: + Source type, Object, or + Value. This information cannot be modified from + the Source Editor dialog. Instead, the + corresponding database record (e.g. birth event) has to be brought + up and its source reference edited. + + + + + + + + + Edit Place Data + To edit place data, switch to the Places View and select the + desired entry in the list of places. Double-click on that entry or + click the Edit icon on the toolbar to invoke the + following Place Editor dialog: + + +
+ Place Editor dialog + + + Shows Place Editor dialog. +
+ + + The top of the window shows the Place Editor + title of the dialog. The main part of the window displays seven + notebook tabs containing different categories of available information. + You can bring any tab to the top for viewing or editing by clicking on + the appropriate tab heading. The bottom part has + OK and Cancel buttons. + Clicking the OK button at any time will apply all the + changes made in all tabs and close the dialog window. Clicking the + Cancel button at any time will close the window without + applying any changes. If any of the data in any tab were modified, + the alert window will appear with the choices of closing the dialog + without saving changes, canceling the initial cancel request, or saving + the changes. + + + The tab labels reflect the presence of corresponding information: if the + tab contains any data, its label appears boldface; if the tab has no data + then its label appears regular (not bold). + The tabs provide the following information categories of + place data: + + + + General + The + General tab allows editing of the most general + information about the place: the title which labels it in the database, + city, church parish, county, state, country, longitude, and latitude. + This information can be typed in the appropriate text entry fields. + + + + + + Other names + + The Other names tab displays information concerning + other names by which the place might be known and the controls + allowing their modification. The bottom part displays the list of all + other names of the place stored in the database. The top part shows + the details of the currently selected name in the list (if any). + The buttons Add..., + Edit..., and Delete allow + you to correspondingly add, modify, and remove a name record + from the database. Note that the Edit... and + Delete buttons become available only when + a name is selected from the list. + + + + + Note + + The Note tab displays any notes concerning + the place. To add a note or modify existing notes simply edit the + text in the text entry field. + + + + + + Sources + + The Sources tab displays information about sources + relevant to this place and controls allowing its modification. + The central part displays the list of all such source references + stored in the database. The buttons Add..., + Edit..., and Delete allow + you to correspondingly add, modify, and remove a source reference + to this place. Note that the Edit... and + Delete buttons become available only when + a source reference is selected from the list. + + + + + Gallery + + The Gallery tab displays information about + media objects associated with the given place and the controls + allowing its modification. The central part shows the list of all + such media objects. For media objects which are valid image files + previews of images are displayed. For other objects such as audio + files, movie files, etc., a generic &app; icon is displayed instead. + The buttons Add..., + Edit..., and Remove allow + you to correspondingly add, modify, and remove a media object reference + to this source. Note that the Edit... and + Remove buttons become available only when + a media object is selected from the list. + + + + + + Internet + + The Internet tab displays information about + Internet addresses relevant to the place and controls + allowing its modification. The bottom part displays the list of all + such Internet addresses stored in the database. The top part shows the + details of the currently selected addresses in the list (if any). + The buttons Add..., + Edit..., and Delete + allow you to correspondingly add, modify, and remove an Internet address + record from the database. The button Go allows + you to open a web-page with the corresponding address with your default + browser. Note that the Edit..., + Delete, and Go buttons + become available only when an address is selected from the list. + + + + + + References + + The References tab displays information about + database records that refer to this place. If the place is not + referenced from any database record, the tab shows an empty list. + If the place is referenced from many records, the tab will list + all of them. This information cannot be modified from + the Place Editor dialog. Instead, the + corresponding database record (e.g. birth event) has to be brought + up and its place reference edited. + + + + + + + + Edit Media Data + To edit media data, switch to the Media View and select the + desired entry in the list of sources. Double-click on that entry or + click Edit on the toolbar to invoke the + following Edit Media Properties dialog: + + +
+ Edit Media Properties dialog + + + Shows Edit Media Properties dialog. +
+ + + The top of the window shows the dialog title. Below the title + is the preview of an object and the summary of its properties (ID, + path, and object type). The central part of the window displays four + notebook tabs containing different categories of available information. + You can bring any tab to the top for viewing or editing by clicking on + the appropriate tab heading. The bottom part has + OK and Cancel buttons. + Clicking the OK button at any time will apply all the + changes made in all tabs and close the dialog window. Clicking the + Cancel button at any time will close the window without + applying any changes. If any of the data in any tab were modified, + the alert window will appear with the choices of closing the dialog + without saving changes, canceling the initial cancel request, or saving + the changes. + + + The tab labels reflect the presence of corresponding information: if the + tab contains any data, its label appears boldface; if the tab has no data + then its label appears regular (not bold). + The tabs provide the following information categories of + media object data: + + + + General + The + General tab allows editing the title which labels + this object in the database. The title can be typed in the appropriate + text entry field. If the object is not local (i.e. the corresponding + file does not reside under &app; database directory), the + Make a local copy button is available. + Click it to copy the media into the &app; database directory. This will + increase the amount of disk space consumed by the &app; database. However, + if the external file is deleted or removed, &app; will still be able + to use the local copy. + + + + + Attributes + + The Attributes tab displays information about + the attributes of the media object and controls allowing its + modification. The bottom part displays the list of all such + attributes stored in the database. The top part shows the details + of the currently selected attribute in the list (if any). The buttons + Add..., Edit..., + and Delete allow you to correspondingly add, + modify, and remove an attribute record from the database. + Note that the Edit... and + Delete buttons become available only when + an attribute is selected from the list. + + + + + Notes + + The Notes tab displays information about the + notes concerning the media object. These could be any notes which do + not naturally fit into the Parameter-Value pairs available to + Attributes. To add a note or modify existing notes simply edit the + text in the text entry field. + + + + + References + + The References tab displays information about + database records that refer to this media object. If the object is not + referenced from any database record, the tab shows an empty list. + If the object is referenced from many records, the tab will list + all of them. The list can be ordered by any of its column headers: + Type, Object, or + Value. This information cannot be modified from + the Media Object Properties Editor dialog. + Instead, the corresponding database record (e.g. birth event) has to + be brought up and its media object reference edited in the gallery + tab. + + + + + + + + Edit Events + Events are edited through the following Event + Editor dialog: + + +
+ Event Editor dialog + + + Shows Event Editor dialog. +
+ + + The top of the window shows the dialog title including the name + of the person whose event is being edited. The central part of the + window displays four notebook tabs containing different categories of + available information. You can bring any tab to the top for viewing or + editing by clicking on the appropriate tab heading. The bottom part has + OK and Cancel buttons. + Clicking the OK button at any time will apply all the + changes made in all tabs and close the dialog window. Clicking the + Cancel button at any time will close the window without + applying any changes. If any of the data in any tab were modified, + the alert window will appear with the choices of closing the dialog + without saving changes, canceling the initial cancel request, or saving + the changes. + + + The tab labels reflect the presence of corresponding information: if the + tab contains any data, its label appears boldface; if the tab has no data + then its label appears regular (not bold). + The tabs provide the following information categories of + the event data: + + + General + The + General tab allows editing of the most general + information about the event: its type, date, place, cause, and + description. The type can be selected from available types listed + in the Event type drop-down menu. The rest + of the information can be typed in the appropriate text entry fields. + Check the Private record box to mark this event + record as private. This will give you a chance to omit this event from + being included in reports, if you choose so among the report + generation options. + + + + + Sources + The + Sources tab displays information about sources + relevant to this event and controls allowing its modification. + The central part displays the list of all such sources references + stored in the database. The buttons Add..., + Edit..., and Delete + allow you to correspondingly add, modify, and remove a source reference + to this event. Note that the Edit... and + Delete buttons become available only when + a source reference is selected from the list. + + + + + Note + + The Note tab displays any notes concerning + the event. To add a note or modify existing notes simply edit the + text in the text entry field. + + + + + + Witnesses + The + Witnesses tab displays information about witnesses + relevant to this event and controls allowing its modification. + The central part displays the list of all such witnesses + stored in the database. The buttons Add..., + Edit..., and Delete + allow you to correspondingly add, modify, and remove a witness reference + to this event. Note that the Edit... and + Delete buttons become available only when + a witness reference is selected from the list. + + + + + + + + Edit Source Information + When adding source references to events, places, etc., + the following dialog appears: + + +
+ Source Information dialog + + + Shows Source Information dialog. +
+ + + The top of the window shows the dialog title. The central part + displays the source information. The bottom part has + OK and Cancel buttons. + Clicking the OK button at any time will apply all the + changes made and close the dialog window. Clicking the + Cancel button at any time will close the window without + applying any changes. If any of the data were modified, + the alert window will appear with the choices of closing the dialog + without saving changes, canceling the initial cancel request, or saving + the changes. + + The source can be selected from available sources listed in the + Title drop-down menu. If the source you are + referencing is not present in the database yet, you can enter it into + the database. To do this, click the New... button + and enter source information into the invoked Source + Editor dialog. You can also set the details specific for + this particular reference: confidence, volume/file/page. date, text, + and comments. Choose the confidence + level from the Confidence drop-down menu. + The rest of the details can be typed in the appropriate text entry + fields. + + + + + + Edit Alternate Names + Alternate names are edited through the following + Alternate Names Editor dialog: + + +
+ Alternate Names Editor dialog + + + Shows Alternate Names Editor dialog. +
+ + + The top of the window shows the dialog title including the name + of the person whose alternate name is being edited. The central part + of the window displays three notebook tabs containing different + categories of available information. You can bring any tab to the + top for viewing or editing by clicking on the appropriate tab heading. + The bottom part has OK and + Cancel buttons. Clicking the + OK button at any time will apply all the + changes made in all tabs and close the dialog window. Clicking the + Cancel button at any time will close the window without + applying any changes. If any of the data in any tab were modified, + the alert window will appear with the choices of closing the dialog + without saving changes, canceling the initial cancel request, or saving + the changes. + + + The tab labels reflect the presence of corresponding information: if the + tab contains any data, its label appears boldface; if the tab has no data + then its label appears regular (not bold). + The tabs provide the following information categories of + the alternate name data: + + + General + The + General tab allows editing of general + information about the alternate name: given name, family name, family + prefix, suffix, title, and type of the name. The information can be + typed in the appropriate text entry fields. The family name and the + type can be also selected from available choices listed in the + appropriate drop-down menus. + Check the Private record box to mark this name + record as private. This will give you a chance to omit this name from + being included in reports, if you choose so among the report + generation options. + + + + + Sources + The + Sources tab displays information about sources + relevant to this name and controls allowing its modification. + The central part displays the list of all such sources' references + stored in the database. The buttons Add..., + Edit..., and Delete + allow you to correspondingly add, modify, and remove a source reference + to this name. Note that the Edit... and + Delete buttons become available only when + a source reference is selected from the list. + + + + + Note + + The Note tab displays any notes concerning + the name. To add a note or modify existing notes simply edit the + text in the text entry field. + + + + + + + + + Edit Attributes + Attributes are edited through the following + Attribute Editor dialog: + + +
+ Attribute Editor dialog + + + Shows Attribute Editor dialog. +
+ + + The top of the window shows the dialog title including the name + of the person whose attribute is being edited. The central part + of the window displays three notebook tabs containing different + categories of available information. You can bring any tab to the + top for viewing or editing by clicking on the appropriate tab heading. + The bottom part has OK and + Cancel buttons. Clicking the + OK button at any time will apply all the + changes made in all tabs and close the dialog window. Clicking the + Cancel button at any time will close the window without + applying any changes. If any of the data in any tab were modified, + the alert window will appear with the choices of closing the dialog + without saving changes, canceling the initial cancel request, or saving + the changes. + + + The tab labels reflect the presence of corresponding information: if the + tab contains any data, its label appears boldface; if the tab has no data + then its label appears regular (not bold). + The tabs provide the following information categories of + the attribute data: + + + General + The + General tab allows editing of the most general + information about the attribute: name of the attribute and its value. + The information can be typed in the appropriate text entry fields. + The attribute name can also be selected from available choices (if any) + listed in the Attribute drop-down menu. + Check the Private record box to mark this + attribute record as private. This will give you a chance to omit + this attribute from being included in the reports, if you choose + so among the report generation options. + + + + + Sources + The + Sources tab displays information about sources + relevant to this attribute and controls allowing its modification. + The central part displays the list of all such sources references + stored in the database. The buttons Add..., + Edit..., and Delete + allow you to correspondingly add, modify, and remove a source reference + to this attribute . Note that the Edit... and + Delete buttons become available only when + a source reference is selected from the list. + + + + + Note + + The Note tab displays any notes concerning + the attribute . To add a note or modify existing notes simply edit the + text in the text entry field. + + + + + + + + Edit Addresses + Addresses are edited through the following + Address Editor dialog: + + +
+ Address Editor dialog + + + Shows Address Editor dialog. +
+ + + The top of the window shows the dialog title including the name + of the person whose address is being edited. The central part + of the window displays three notebook tabs containing different + categories of available information. You can bring any tab to the + top for viewing or editing by clicking on the appropriate tab heading. + The bottom part has OK and + Cancel buttons. Clicking the + OK button at any time will apply all the + changes made in all tabs and close the dialog window. Clicking the + Cancel button at any time will close the window without + applying any changes. If any of the data in any tab were modified, + the alert window will appear with the choices of closing the dialog + without saving changes, canceling the initial cancel request, or saving + the changes. + + + The tab labels reflect the presence of corresponding information: if the + tab contains any data, its label appears boldface; if the tab has no data + then its label appears regular (not bold). + The tabs provide the following information categories of + the address data: + + + General + The + General tab allows editing of the most general + information about the address: date, street address, city or county, + state or province, country, and the postal code. The information can + be typed in the appropriate text entry fields. + Check the Private record box to mark this address + record as private. This will give you a chance to omit this address + from being included in reports, if you choose so among the report + generation options. + + + + + Sources + The + Sources tab displays information about sources + relevant to this address and controls allowing its modification. + The central part displays the list of all such sources references + stored in the database. The buttons Add..., + Edit..., and Delete + allow you to correspondingly add, modify, and remove a source reference + to this address. Note that the Edit... and + Delete buttons become available only when + a source reference is selected from the list. + + + + + Note + + The Note tab displays any notes concerning + the address. To add a note or modify existing notes simply edit the + text in the text entry field. + + + + + + + + + Edit Witnesses + Witnesses are edited through the following + Witness Editor dialog: + + +
+ Witness Editor dialog + + + Shows Witness Editor dialog. +
+ + + The top of the window shows the dialog title. The central part + of the window displays information about the witness. The bottom part + has OK and Cancel buttons. + Clicking the OK button at any time will apply all the + changes made and close the dialog window. Clicking the + Cancel button at any time will close the window + without applying any changes. If any of the data were + modified, the alert window will appear with the choices of closing + the dialog without saving changes, canceling the initial cancel + request, or saving the changes. + + The witness name can be entered in two ways, depending upon + whether the witness is a person already stored in the database or + not (unrelated person). + + + Person from the database + + If the person's data are stored in a database, check Person + is in the database box. Then click the + Select button to evoke Select + Person dialog. Choose the person from that dialog and + click the OK button. The Person + text field will display the name of the person you selected. + Note: even though the person's name is displayed in the + Person field, it is not available for direct + editing. + + + + + Unrelated person + + If the person is not in the database, make sure that + Person is in the database box is unchecked. + Then enter the name or any description of a person into the + Person text entry field. This information + is stored as entered, and this is the only place it is stored. + In other words, there is no reference to that person in the entire + database except for this witness reference. If the person is in fact + a member of the database, it is advised to use the former method. + + + + + The Comment text area allows you to enter + any comments concerning the witness. To add a comment or to modify + existing comments simply edit the text in the text area. + + + + + + + Merge People + Sometime two people entries in the database turn out to be + describing the same person. When this happens, merging people is + a useful way of correcting the situation. + + To make a merge, exactly two people have to be selected in the + People View. This is accomplished by selecting one person and then + selecting another person while holding down Ctrl key. + + + When exactly two people are selected, choose + EditMerge... + to evoke Merge People dialog. The dialog allows you to + retain the data from either person as the primary data for the new + (merged) person. The data from the other person can be kept as alternate + data if you so choose. If you would like to continue editing data of + a newly merged person, click the Merge and edit + button. + + + + + Merge Places + Sometime two place entries in the database turn out to be + describing the same place. When this happens, merging places is + a useful way of correcting the situation. + + To make a merge, exactly two places have to be selected in the + Places View. This is accomplished by selecting one place and then + selecting another place while holding down Ctrl key. + + + When exactly two places are selected, choose + EditMerge... + to evoke Merge Places dialog. The dialog allows + you to retain the data from either place as the primary data for + the new (merged) place. Alternatively, you may type in other data + for the new place, if you click Other radio + button. + + + + + + + Navigation + As long as any database is open, &app; is focused on a + single person usually referred to as an Active person. This + allows you to view or modify the data concerning this person, + his or her immediate family, etc. Navigating in the database (i.e. + moving from person to person) is in fact nothing else but changing + the Active person. This section describes many alternative ways + to navigate through the database using both the complex and the + convenient interfaces &app; provides. All these ways eventually + accomplish the same thing, but some are more convenient than others, + depending what you are doing in &app; at the moment. + + + + Using the People View + The most intuitive way to select an active person is + to use the People View (see ). + When in the People View, just select the + name of the desired person from the list by clicking that list + entry. The person you have selected becomes active. The statusbar + updates to reflect the change of the active person. + + + + + Using the Family View + When in the Family View (see ), + you can easily navigate between the members of the displayed family + as follows: + + + To make the currently selected spouse the active person, + click the double-arrow button to the right of the active person box. + Alternatively, right-click into the spouse box and select + Make the selected spouse an active person item + from the context menu. + + + To make the currently selected parents the active family + (thereby making father the active person and mother the selected + spouse), click the right-arrow button to the right of the active person's + parents box. Alternatively, right-click into the active person's parents + box and select + Make the selected parents the active family item + from the context menu. + + + To make the currently selected spouse's parents + the active family (thereby making father the active person and mother + the selected spouse), click the right-arrow button to the right of the + spouse's parents box. Alternatively, right-click into the spouse's parents + box and select + Make the selected parents the active family item + from the context menu. + + To make the currently selected child the active person, + click the left-arrow button to the right of the children box. + Alternatively, right-click into the children box and select + Make the selected child an active person item + from the context menu. + + + + + In addition to this, &app; provides an extensive set of keyboard + navigation options. The detailed reference to the keybindings + is found in the . + + + + + + Using the Pedigree View + The Pedigree View (see ) also + allows you to move along the family tree. + The benefit of this method is that you can see more than one + generation of the family tree. Also, you can jump directly from a + great-grandson to a great-grandfather without going through the + intermediate generations. + + Note that after changing the active person in the Pedigree + View, the display is re-adjusted to show four generations, starting + from the newly selected Active person. When in the Pedigree View, you + can easily navigate between the members of the displayed family tree + as follows: + + + To make any displayed person the active person, + double-click the line that connects to the left side of the + corresponding box. + + To make a child of the currently active person (if any) + the active person, click the left arrow button to the left of the + corresponding box. If there is more than one child, the button expands + to the menu listing the children to choose from. + + To move the whole family tree one generation back, + click on the corresponding right arrow button on the right-hand side + of the display area. Clicking the upper button will move the tree + along the paternal line. Clicking the lower button will move the + tree along the maternal line. + + Clicking either of these buttons is completely equivalent to + double-clicking the lines connecting to the left of the corresponding + boxes for father and mother. + + + + + + + Setting the Home Person + One and only one person in the database can be selected as the + Home person. Once the Home person is selected, moving to that + person becomes a matter of a single click, regardless of which view + you are using at the moment. + + To set the Home person, first navigate to that person using + any method you like. Then choose + Edit + Set Home person. Once this is + done, you can move to the Home person from anywhere in the + database by simply clicking the Home icon + on the toolbar. You can also choose Go + Home from the menu or select + Home item from any context menu available on the + right click. + + + + + + + + Using history-based tools + &app; also features a powerful set of history-based navigation + tools. These tools are similar to those commonly used in web browsers. + They include Back and Forward + items available from the Go + menu, context menus, and the toolbar buttons. They also include the + list of the recent selections available under the + Go menu that allows you to jump + directly to any of the recent selections. + Finally, right-clicking on the Back + and Forward toolbar buttons invokes the + popup menu with corresponding portion of the history. Select any item + from the menu to jump directly to it. + + + + + + Bookmarking People + Similar to setting the Home person, you can bookmark other + people from the database to simplify further navigation. To bookmark + a person, first navigate to that person, then choose + Bookmarks + Add bookmark. To move to that + person from anywhere in the database, choose + Bookmarks + Go to bookmark + Person's name + . + + You can manage your bookmarks by choosing + Bookmarks + Edit bookmarks.... This opens + the following Edit Bookmarks dialog with the + list of bookmarks and the controls to modify this list. + + +
+ Edit Bookmarks dialog + + + Shows Edit Bookmarks dialog. +
+ + + + + + + Finding People + To find a person in a database, choose + EditFind... + when in the People View, Family View, or Pedigree View. This opens a + Find Person dialog which can be used for searching + forward and backward. + + If the search is successful, the found person becomes an active + person and the display adjusts according to the new active person and the + current view. + + + + + Finding Sources + To find a source in a database, choose + EditFind... + when in the Sources View. This opens a Find Source + dialog which can be used for searching forward and backward. If the + search is successful, the found source becomes highlighted. + + + + + Finding Places + To find a place in a database, choose + EditFind... + when in the Places View. This opens a Find Place + dialog which can be used for searching forward and backward. If the + search is successful, the found place becomes highlighted. + + + + + Finding Media Objects + To find a media object in a database, choose + EditFind... + when in the Media View. This opens a Find Media Objects + dialog which can be used for searching forward and backward. If the + search is successful, the found media object becomes highlighted. + + + + + + + Generating Reports + Reports are the most common form of the output produced by + genealogical research. The majority of genealogical software puts a lot + of emphasis on developing nicely looking reports. &app; is no + exception in this regard: it offers a choice of a variety of reports. + &app; can generate reports in a multitude of open formats, both + text based and graphical. &app; can also produce screen based reports + that are convenient for viewing a summary of your database. + Finally, &app; can generate a web site suitable for immediate + posting on the Internet. All these are almost infinitely flexible: + if you wish to modify or extend the default format of &app; report + you can design and choose the style for each of your reports. + + All reports can be accessed through the menu by choosing + Reports + Report Type + Particular + Report. Alternatively, + you can browse the complete selection of available reports along + with their brief descriptions in a Report + Selection dialog evoked by clicking the + Reports icon on the toolbar. + + + + + + Graphical Reports + Graphical reports represent information in forms of charts + and graphs. Most of the options are common among graphical reports, + therefore they will be described only once, at the end of this + section. The few options which are specific to a given report will be + described directly in that report's entry. + + The following graphical reports are currently + available in &app;: + + + + Ancestor Chart + This report generates the chart of people who are + ancestors of the Active person. Specific options include + the number of generations considered and the format of the displayed + entries. + + + Descendant Graph + This report generates a graph of people who are + descendants of the Active person. Specific options include + the format of the displayed entries. + + + Relationship Graph + This report creates a complex relationship graph in + GraphViz format. The GraphViz dot tool can + transform the graph into postscript, jpeg, png, vrml, svg, and many + other formats. GraphViz tools are freely available from the + GraphViz + site. Specific options for this report + include filter and number of generations considered, as well as + several GraphViz-specific options related to pagination, color, + and details of the graph. + + + Timeline Graph + This report outputs the list of people with their + lifetimes represented by intervals on a common chronological scale. + Specific options include filter, sorting method, and the title of + the report. + + + + + Common options for graphical reports are the filename of the + output, the format of the output, selected style, page size and + orientation. + + + + + + Text Reports + Text reports represent the desired information as formatted + text. Most of the options are common among text reports, + therefore they will be described only once, at the end of this + section. The options which are specific to a given report will be + described directly in that report's entry. + + The following text reports are currently + available in &app;: + + + + Ahnentafel Report + This report lists the active person and his or her + ancestors along with their vital data. The people are numbered in a + special way which is an established standard called Ahnentafel. + The active person is given number 1. His or her father and mother + have numbers 2 and 3, respectively. This rule holds for every person + while going back in generations: father's parents are numbered 4 and 5, + and mother's parents are numbered 6 and 7, fathers always numbered + with even and mothers with odd numbers. Therefore, for any person + having number N in this tree, the numbers of father and mother + are 2N and 2N+1, respectively. + + + + Comprehensive Ancestors Report + This report produces a comprehensive description + of ancestors of the active person. The highlights of this report + include elaborate layout, images of children, present and former + spouses, and source citations. Specific options: number + of backward generations to consider, whether to cite sources, + and whether to break pages between generations. + + + Complete Individual Report + This report provides individual summaries similar to + that of the Individual Summary report. The advantage of this report + is the specific filter option. Depending on the filter choice (active + person only, his or her descendants, his or her ancestors, or entire + database), the report may contain from one to many individual + summaries. Another option for this report is the inclusion of + source information when listing events. + + + Descendant Report + This report produces a brief description + of descendants of the active person. Specific options: number + of forward generations to consider. + + + Detailed Ancestral Report + This report covers in detail the ancestors of the + active person. It includes vital data (birth and death) as well as + marriages. Specific options: number of backward generations + to consider, as well as a variety of options regarding the exact + contents to include. + + + Detailed Descendant Report + This report covers in detail the descendants of the + active person. It includes vital (birth and death) information as well as + marriages. Specific options: number of forward generations + to consider. + + + FTM Style Ancestral Report + This report creates an ancestral report similar to + that produced by the Family Tree Maker (tm) program. It covers in detail the + active person and his/her ancestors It includes vital information + as well as marriages, children, and notes. Specific options: number + of backward generations to consider. + + + FTM Style Descendant Report + This report creates a descendant report similar to + that produced by the Family Tree Maker (tm) program. It covers in detail the + active person and his/her descendants. It includes vital information + as well as marriages, children, and notes. Specific options: + number of forward generations to consider. + + + Family Group Report + This creates a family group report, showing + information on a set of parents and their children. Specific + options: the spouse (available only if the active person has more + than one spouse). + + + Individual Summary + This report produces a detailed summary on the + active person. The report includes all the facts known to the + database about that person. + + + + + Common options for text reports are the filename of the + output, the format of the output, selected style, page size and + orientation. For HTML reports, there is no page information. + Instead, HTML options include the choice of the HTML template, + either available in &app; or a custom template defined by you. + + + + + + Books + Currently, the only available report under this category + is the Book Report. + + The Book Report creates a single document (i.e. a Book) + containing a collection of graphical and textual reports. + Consequently, this allows for a very rich set of documents + that &app; can produce. + + + When Book Report is selected, the following book configuration + dialog appears: + + +
+ Book Report dialog + + + Shows Book Report dialog. +
+ + + The Book name text entry field is used to + save the book (a set of configured selections) for future use. + The top pane lists the items available for inclusion in the + book. The bottom pane lists the currently selected items in + the order they will appear in the book. + + The horizontal set of buttons by the Book + name field operates on the whole book. Click + the Clear button to clear all items from + the current book. Click the Save button to + save the current book (under the name typed in + the Book name text entry field) for future use. + Note that saving the book also saves the configuration for each item. + Click the Open button to load + the book from the list of previously saved books. Finally, click the + Edit books button to evoke the editable list of + available books. + + The vertical set of buttons to the right of the bottom pane + operates on the + selected book item. Click the Add button to + add selected item from the available list to the current book. Click + the Remove button to remove an item from the + current book. Use Up and + Down to change the items order in the current + book. Click the Setup button to configure the + options of the selected item of the current book. + + + The configuration dialogs evoked by Setup + are item-specific. If you choose not to configure the item, sane + defaults will be used for all needed options. The common option for + almost all book items is the center person: the person on whom the + item is centered. Thanks to this option, you can create a book with + items centered on different people (e.g. your mom's and dad's + ancestors as separate chapters). By default, the center person is + set to the active person. + + Almost all items available for inclusion in the book are textual + or graphical reports, and are therefore available in the form of standalone + reports. The exception is the following items which are only available as + book items: + + + + Title Page + This item produces a customized Title page. You can + configure the text of title, subtitle, and the footer of the page. + An image can be optionally placed between the subtitle and the footer. + Because of its configurability, this item can be used to create + title pages for the whole book, its chapter, or even a single item. + + + + + Custom Text + This item produces a page with three paragraphs, each + containing custom text. The appearance of the text can be adjusted by + using custom styles. This item was meant to be used for epigraphs, + dedications, explanations, notes, and so forth. + + + + + + + + + + View Reports + View reports represent overall summaries of the database + information available immediately for on-screen viewing. + The following view reports are currently available in &app;: + + + + Number of ancestors + This report displays the number of ancestors of the + active person. + + + Summary of the database + This report displays the overall statistics concerning + number of individuals of each gender, various incomplete entries + statistics, as well as family and media statistics. + + + + + + + + Web Page + + This report generates web pages, either for a selected + individual (active person) or a set of individuals. The options + for this report are broken down into contents, privacy, and advanced + options. The contents options include the filter (determine the + scope of the database to consider), + destination directory for the images, an optional short ancestor tree, + and a link to the index page. + Privacy options allow you to omit private records, restrict + information on living people, skip images (either all or only + those of living people), and omit comments and text in source + information. Finally, the advanced options allow you to include + the optional &app; ID, create a GENDEX index, and specify the + extension of the resulting files. + + + + + + + + Running Tools + &app; tools allow you to perform various types of analyses + of your genealogical data. Typically, the tools do not produce + output in form of printouts or files. Instead, they produce screen + output immediately available for the researcher. However, when + appropriate, you can save the results of running a tool into a file. + Tools present one of the major strengths of &app; compared to the most + genealogical software. + + The tools can be accessed through the menu by choosing + Tools + Tool Section + Particular + Tool. Alternatively, + you can browse the complete selection of available tools along + with their brief descriptions in a Tool + Selection dialog evoked by clicking the + Tools icon on the toolbar. + + + + Analysis and Exploration + This section contains tools which analyze and explore the + database, but do not alter it. The following analysis and exploration + tools are currently available in &app;: + + + + Compare individual events + This tool compares events across the selected group of + people. The people for this comparison are chosen with the use of + custom filters. The custom filters can be created in the Custom Filter + Editor (see ). The resulting table produced + by this tool can be saved as a spreadsheet. + + + Interactive descendant browser + This tool builds a tree with the active person being + the root. Children branch from their parents in the usual manner. + Use this tool for a quick glance of a person's descendants. + + + + + + + + + Database Processing + This section contains tools which may modify your database. + The modifications will only be performed upon your explicit consent. + The tools from this section are used mostly for finding and correcting + errors in the data. The following database processing tools are + currently available in &app;: + + + + Check and repair database + This tool checks the database for integrity problems, + fixing the problems it can. Specifically, the tool is checking for: + + Broken family links. These are the cases when + a person's record refers to a family while the family's record + does not refer to that person, and vice versa. + + + Missing media objects. The missing media + object is the object whose file is referenced in the database + but does not exist. This can happen when the file is + accidentally deleted, renamed, or moved to another location. + + + Empty families. These are the family entries + which have no reference to any person as their member. + + + Parent relationship. This checks all families + to ensure that father and mother are not mixed up. The check + is also made that parents have different gender. If they have + common gender then their relationship is renamed to "Partners". + + + + + + + Extract information from names + This tool searches the entire database and attempts + to extract titles and nicknames that may be embedded in a person's + Given name field. + + + + Find possible duplicate people + This tool searches the entire database, looking + for the entries that may represent the same person. + + + + Rename personal event types + This tool allows all the events of a certain name + to be renamed to a new name. + + + + Reorder &app; IDs + This tool reorders the &app; IDs according to the + defaults of &app;. + + + + + + + + + + Utilities + + + This section contains tools allowing you to perform a simple + operation on a portion of data. The results can be saved in your + database, but they will not modify your existing data. + The following utilities are currently available in &app;: + + + + Custom Filter Editor + The Custom Filter Editor builds custom filters + that can be used to select people included in reports, exports, + and other tools and utilities. This is in fact a very powerful tool + in genealogical analysis. + + When you launch it, the User defined filters + dialog appears that lists all the filters (if any) previously defined + by you. Click the Add... button to define a new filter. + Once you have designed your filters, you can edit, test, and delete + selected filters using the Edit..., + Test..., and Delete... + buttons, respectively. All the filters displayed in the list will be + automatically saved along with your database and will be available + with subsequent sessions of &app;. + + Clicking the Add... button invokes the + following Define filter dialog: + + +
+ Define filter dialog + + + Shows Define filter dialog. +
+ + + Type the name for your new filter into the + Name field. Enter any comment that would help you + identify this filter in the future into the Comment + field. Add as many rules to the Rule list as you + would like to your filter using Add... button. + Check Return values that do not match the filter rules + (invert) to negate the filter rule (e.g. inverting "has a + common ancestor with I1" rule will match everyone who does not have a + common ancestor with that person). If the filter has more than one rule, + select one of the Rule operations. This allows you + to choose whether all rules must apply, only one (either) rule must + apply, or exactly one (either) rule must apply, in order for the filter + to generate a match. If your filter has only one rule, this selection + has no effect. + + Clicking the Add... button invokes the + following Add Rule dialog: + + +
+ Add Rule dialog + + + Shows Add Rule dialog. +
+ + + The pane on the left-hand side displays available filter rules + arranged by their categories in an expandable tree. For detailed filter + rule reference, see . Click on the + arrows to fold/unfold the appropriate category. Select the rule + from the tree by clicking on its name. The right-hand side displays + the name, the description, and the values for the currently selected + rule. Once you are satisfied with your rule selection and its values, + click OK to add this rule to the rule list + of the currently edited filter. Clicking Cancel + will abort adding the rule to the filter. + + Note that a filter you've already designed may be used as a rule + for another filter. This gives you nearly infinite flexibility in + custom-tailoring your selection criteria that can be later used in + most of the exports, reports and some of the tools (such as comparing + individual events). + + + Generate SoundEx codes + This utility generates SoundEx codes for the names of + people in the database. Please visit the NARA Soundex Indexing page to learn more about + Soudex Indexing System. + + + + Relationship calculator + This utility calculates the relationship between + two people from the database. + + + + Verify the database + This utility allows you to verify the database based + on the set of criteria specified by you. This tool is different from + the previously described Check tool in the following. The Check tool + detects inconsistencies in the database structure. The Verify tool, + however, is detecting the records that do not satisfy your particular + criteria. + + For example, you may want to make sure that nobody in your + database had children at the age of 98. Based on common sense, such + a record would indicate an error. However, it is not a consistency + error in the database. Besides, someone might have a child at the of + 98 (albeit this rarely happens). The Verify tool will display + everything that violates your criteria so that you can check whether + the record is erroneous or not. The ultimate decision is yours. + + + + + + + + + +