remove build version from const.py

Viewmanager somehow lost its import of gi.

.gitattributes

@@ -0,0 +1,18 @@
+# Make Github recognise Gramps as a Python project,
+# by marking .sql files as text files!
+# See: https://github.com/github/linguist/issues/2462
+# https://github.com/github/linguist/blob/master/README.md
+*.sql linguist-language=txt
+
+# Have Github ignore js vendored files.
+# https://github.com/gramps-project/gramps/tree/master/data/javascript
+#data/javascript/*.js linguist-vendored
+
+# don't mess with line endings for test files
+*.vcs -text
+*.ged -text
+*.GED -text
+*.csv -text
+*.DEF -text
+*.IXI -text
+*.REM -text

.gitignore

@@ -0,0 +1,27 @@
+# Python
+*.py[cod]
+
+# Distutils
+MANIFEST
+build/
+dist/
+
+# Gramps
+data/tips.xml
+data/holidays.xml
+po/.intltool-merge-cache
+docs/_build/
+
+# Editing
+tags
+*.swp
+
+# Testing
+test/data
+
+# Windows image file caches
+Thumbs.db
+ehthumbs.db
+
+# Glade temp files
+*~

.mailmap

@@ -0,0 +1,28 @@
+<benny.malengier@gramps-project.org> <benny.malengier@gmail.com>
+<doug.blank@gmail.com> <dsblank@bitbucket.org>
+<doug.blank@gmail.com> <dblank@cs.brynmawr.edu>
+<beernarrd@gmail.com> <beernarrd@users.sourceforge.net>
+<igal.shapira@gmail.com> <igalshapira@users.sourceforge.net>
+<romjerome@yahoo.fr> <romjerome@users.noreply.github.com>
+<jralls@ceridwen.us> <john@aeolus.local>
+<josip@pisoj.com> <bpisoj@gmail.com>
+Josip Pisoj <josip@pisoj.com>
+Mirko Leonhaeuser <mirko@leonhaeuser.de>
+<martin.hawlisch@gmx.de> <loshawlos@users.sourceforge.net>
+Matti Niemelä <matti.u.niemela@gmail.com>
+<nick-h@gramps-project.org> <nick__hall@hotmail.com>
+<nick-h@gramps-project.org> <Nick-Hall@users.noreply.github.com>
+Ondrej Krč-Jediný <hou@centrum.sk>
+<hou@centrum.sk> <ondrisko@users.sourceforge.com>
+Pierre Bélissent <pierre.belissent@gmail.com>
+Serge Noiraud <Serge.Noiraud@free.fr>
+<Serge.Noiraud@free.fr> <serge.noiraud@free.fr>
+<Serge.Noiraud@free.fr> <serge.noiraud@laposte.net>
+Zdeněk Hataš <zdenek.hatas@gmail.com>
+<zdenek.hatas@gmail.com> <zdenek.hatas@hp.com>
+<zdenek.hatas@gmail.com> <zenhas@users.sourceforge.net>
+<gerald@gkunzmann.de> <g.kunzmann@arcor.de>
+Tim G L Lyons <tim.g.lyons@gmail.com>
+<tim.g.lyons@gmail.com> <guy.linton@gmail.com>
+Elder Evans <elderamevans@gmail.com>
+

.pylintrc

@@ -0,0 +1,378 @@
+[MASTER]
+
+# Specify a configuration file.
+#rcfile=
+
+# Python code to execute, usually for sys.path manipulation such as
+# pygtk.require().
+#init-hook=
+
+# Add files or directories to the blacklist. They should be base names, not
+# paths.
+ignore=CVS
+
+# Pickle collected data for later comparisons.
+persistent=yes
+
+# List of plugins (as comma separated values of python modules names) to load,
+# usually to register additional checkers.
+load-plugins=
+
+# Use multiple processes to speed up Pylint.
+jobs=1
+
+# Allow loading of arbitrary C extensions. Extensions are imported into the
+# active Python interpreter and may run arbitrary code.
+unsafe-load-any-extension=no
+
+# A comma-separated list of package or module names from where C extensions may
+# be loaded. Extensions are loading into the active Python interpreter and may
+# run arbitrary code
+extension-pkg-whitelist=
+
+# Allow optimization of some AST trees. This will activate a peephole AST
+# optimizer, which will apply various small optimizations. For instance, it can
+# be used to obtain the result of joining multiple strings with the addition
+# operator. Joining a lot of strings can lead to a maximum recursion error in
+# Pylint and this flag can prevent that. It has one side effect, the resulting
+# AST will be different than the one from reality.
+optimize-ast=no
+
+
+[MESSAGES CONTROL]
+
+# Only show warnings with the listed confidence levels. Leave empty to show
+# all. Valid levels: HIGH, INFERENCE, INFERENCE_FAILURE, UNDEFINED
+confidence=
+
+# Enable the message, report, category or checker with the given id(s). You can
+# either give multiple identifier separated by comma (,) or put this option
+# multiple time. See also the "--disable" option for examples.
+#enable=
+
+# Disable the message, report, category or checker with the given id(s). You
+# can either give multiple identifiers separated by comma (,) or put this
+# option multiple times (only on the command line, not in the configuration
+# file where it should appear only once).You can also use "--disable=all" to
+# disable everything first and then reenable specific checks. For example, if
+# you want to run only the similarities checker, you can use "--disable=all
+# --enable=similarities". If you want to run only the classes checker, but have
+# no Warning level messages displayed, use"--disable=all --enable=classes
+# --disable=W"
+disable=suppressed-message,intern-builtin,round-builtin,unicode-builtin,range-builtin-not-iterating,long-builtin,basestring-builtin,setslice-method,print-statement,reload-builtin,metaclass-assignment,raising-string,next-method-called,import-star-module-level,xrange-builtin,getslice-method,zip-builtin-not-iterating,reduce-builtin,dict-iter-method,delslice-method,using-cmp-argument,hex-method,buffer-builtin,old-ne-operator,nonzero-method,backtick,parameter-unpacking,indexing-exception,file-builtin,filter-builtin-not-iterating,raw_input-builtin,execfile-builtin,oct-method,cmp-method,coerce-builtin,long-suffix,cmp-builtin,input-builtin,dict-view-method,standarderror-builtin,apply-builtin,old-raise-syntax,unichr-builtin,old-division,coerce-method,unpacking-in-except,useless-suppression,no-absolute-import,map-builtin-not-iterating,old-octal-literal
+
+
+[REPORTS]
+
+# Set the output format. Available formats are text, parseable, colorized, msvs
+# (visual studio) and html. You can also give a reporter class, eg
+# mypackage.mymodule.MyReporterClass.
+output-format=text
+
+# Put messages in a separate file for each module / package specified on the
+# command line instead of printing them on stdout. Reports (if any) will be
+# written in a file name "pylint_global.[txt|html]".
+files-output=no
+
+# Tells whether to display a full report or only the messages
+reports=yes
+
+# Python expression which should return a note less than 10 (10 is the highest
+# note). You have access to the variables errors warning, statement which
+# respectively contain the number of errors / warnings messages and the total
+# number of statements analyzed. This is used by the global evaluation report
+# (RP0004).
+evaluation=10.0 - ((float(5 * error + warning + refactor + convention) / statement) * 10)
+
+# Template used to display messages. This is a python new-style format string
+# used to format the message information. See doc for all details
+#msg-template=
+
+
+[BASIC]
+
+# List of builtins function names that should not be used, separated by a comma
+bad-functions=map,filter
+
+# Good variable names which should always be accepted, separated by a comma
+good-names=i,j,k,ex,Run,_,db
+
+# Bad variable names which should always be refused, separated by a comma
+bad-names=foo,bar,baz,toto,tutu,tata
+
+# Colon-delimited sets of names that determine each other's naming style when
+# the name regexes allow several styles.
+name-group=
+
+# Include a hint for the correct naming format with invalid-name
+include-naming-hint=no
+
+# Regular expression matching correct argument names
+argument-rgx=[a-z_][a-z0-9_]{2,30}$
+
+# Naming hint for argument names
+argument-name-hint=[a-z_][a-z0-9_]{2,30}$
+
+# Regular expression matching correct module names
+module-rgx=(([a-z_][a-z0-9_]*)|([A-Z][a-zA-Z0-9]+))$
+
+# Naming hint for module names
+module-name-hint=(([a-z_][a-z0-9_]*)|([A-Z][a-zA-Z0-9]+))$
+
+# Regular expression matching correct class attribute names
+class-attribute-rgx=([A-Za-z_][A-Za-z0-9_]{2,30}|(__.*__))$
+
+# Naming hint for class attribute names
+class-attribute-name-hint=([A-Za-z_][A-Za-z0-9_]{2,30}|(__.*__))$
+
+# Regular expression matching correct function names
+function-rgx=[a-z_][a-z0-9_]{2,30}$
+
+# Naming hint for function names
+function-name-hint=[a-z_][a-z0-9_]{2,30}$
+
+# Regular expression matching correct inline iteration names
+inlinevar-rgx=[A-Za-z_][A-Za-z0-9_]*$
+
+# Naming hint for inline iteration names
+inlinevar-name-hint=[A-Za-z_][A-Za-z0-9_]*$
+
+# Regular expression matching correct constant names
+const-rgx=(([A-Z_][A-Z0-9_]*)|(__.*__))$
+
+# Naming hint for constant names
+const-name-hint=(([A-Z_][A-Z0-9_]*)|(__.*__))$
+
+# Regular expression matching correct method names
+method-rgx=[a-z_][a-z0-9_]{2,30}$
+
+# Naming hint for method names
+method-name-hint=[a-z_][a-z0-9_]{2,30}$
+
+# Regular expression matching correct class names
+class-rgx=[A-Z_][a-zA-Z0-9]+$
+
+# Naming hint for class names
+class-name-hint=[A-Z_][a-zA-Z0-9]+$
+
+# Regular expression matching correct variable names
+variable-rgx=[a-z_][a-z0-9_]{2,30}$
+
+# Naming hint for variable names
+variable-name-hint=[a-z_][a-z0-9_]{2,30}$
+
+# Regular expression matching correct attribute names
+attr-rgx=[a-z_][a-z0-9_]{2,30}$
+
+# Naming hint for attribute names
+attr-name-hint=[a-z_][a-z0-9_]{2,30}$
+
+# Regular expression which should only match function or class names that do
+# not require a docstring.
+no-docstring-rgx=^_
+
+# Minimum line length for functions/classes that require docstrings, shorter
+# ones are exempt.
+docstring-min-length=-1
+
+
+[ELIF]
+
+# Maximum number of nested blocks for function / method body
+max-nested-blocks=5
+
+
+[LOGGING]
+
+# Logging modules to check that the string format arguments are in logging
+# function parameter format
+logging-modules=logging
+
+
+[SPELLING]
+
+# Spelling dictionary name. Available dictionaries: none. To make it working
+# install python-enchant package.
+spelling-dict=
+
+# List of comma separated words that should not be checked.
+spelling-ignore-words=
+
+# A path to a file that contains private dictionary; one word per line.
+spelling-private-dict-file=
+
+# Tells whether to store unknown words to indicated private dictionary in
+# --spelling-private-dict-file option instead of raising a message.
+spelling-store-unknown-words=no
+
+
+[MISCELLANEOUS]
+
+# List of note tags to take in consideration, separated by a comma.
+notes=FIXME,XXX,TODO
+
+
+[TYPECHECK]
+
+# Tells whether missing members accessed in mixin class should be ignored. A
+# mixin class is detected if its name ends with "mixin" (case insensitive).
+ignore-mixin-members=yes
+
+# List of module names for which member attributes should not be checked
+# (useful for modules/projects where namespaces are manipulated during runtime
+# and thus existing member attributes cannot be deduced by static analysis. It
+# supports qualified module names, as well as Unix pattern matching.
+ignored-modules=
+
+# List of classes names for which member attributes should not be checked
+# (useful for classes with attributes dynamically set). This supports can work
+# with qualified names.
+ignored-classes=
+
+# List of members which are set dynamically and missed by pylint inference
+# system, and so shouldn't trigger E1101 when accessed. Python regular
+# expressions are accepted.
+generated-members=
+
+
+[SIMILARITIES]
+
+# Minimum lines number of a similarity.
+min-similarity-lines=4
+
+# Ignore comments when computing similarities.
+ignore-comments=yes
+
+# Ignore docstrings when computing similarities.
+ignore-docstrings=yes
+
+# Ignore imports when computing similarities.
+ignore-imports=no
+
+
+[FORMAT]
+
+# Maximum number of characters on a single line.
+max-line-length=80
+
+# Regexp for a line that is allowed to be longer than the limit.
+ignore-long-lines=^\s*(# )?<?https?://\S+>?$
+
+# Allow the body of an if to be on the same line as the test if there is no
+# else.
+single-line-if-stmt=no
+
+# List of optional constructs for which whitespace checking is disabled. `dict-
+# separator` is used to allow tabulation in dicts, etc.: {1  : 1,\n222: 2}.
+# `trailing-comma` allows a space between comma and closing bracket: (a, ).
+# `empty-line` allows space-only lines.
+no-space-check=trailing-comma,dict-separator
+
+# Maximum number of lines in a module
+max-module-lines=1000
+
+# String used as indentation unit. This is usually "    " (4 spaces) or "\t" (1
+# tab).
+indent-string='    '
+
+# Number of spaces of indent required inside a hanging  or continued line.
+indent-after-paren=4
+
+# Expected format of line ending, e.g. empty (any line ending), LF or CRLF.
+expected-line-ending-format=
+
+
+[VARIABLES]
+
+# Tells whether we should check for unused import in __init__ files.
+init-import=no
+
+# A regular expression matching the name of dummy variables (i.e. expectedly
+# not used).
+dummy-variables-rgx=_$|dummy
+
+# List of additional names supposed to be defined in builtins. Remember that
+# you should avoid to define new builtins when possible.
+additional-builtins=
+
+# List of strings which can identify a callback function by name. A callback
+# name must start or end with one of those strings.
+callbacks=cb_,_cb
+
+
+[CLASSES]
+
+# List of method names used to declare (i.e. assign) instance attributes.
+defining-attr-methods=__init__,__new__,setUp
+
+# List of valid names for the first argument in a class method.
+valid-classmethod-first-arg=cls
+
+# List of valid names for the first argument in a metaclass class method.
+valid-metaclass-classmethod-first-arg=mcs
+
+# List of member names, which should be excluded from the protected access
+# warning.
+exclude-protected=_asdict,_fields,_replace,_source,_make
+
+
+[IMPORTS]
+
+# Deprecated modules which should not be used, separated by a comma
+deprecated-modules=optparse
+
+# Create a graph of every (i.e. internal and external) dependencies in the
+# given file (report RP0402 must not be disabled)
+import-graph=
+
+# Create a graph of external dependencies in the given file (report RP0402 must
+# not be disabled)
+ext-import-graph=
+
+# Create a graph of internal dependencies in the given file (report RP0402 must
+# not be disabled)
+int-import-graph=
+
+
+[DESIGN]
+
+# Maximum number of arguments for function / method
+max-args=5
+
+# Argument names that match this expression will be ignored. Default to name
+# with leading underscore
+ignored-argument-names=_.*
+
+# Maximum number of locals for function / method body
+max-locals=15
+
+# Maximum number of return / yield for function / method body
+max-returns=6
+
+# Maximum number of branch for function / method body
+max-branches=12
+
+# Maximum number of statements in function / method body
+max-statements=50
+
+# Maximum number of parents for a class (see R0901).
+max-parents=7
+
+# Maximum number of attributes for a class (see R0902).
+max-attributes=7
+
+# Minimum number of public methods for a class (see R0903).
+min-public-methods=2
+
+# Maximum number of public methods for a class (see R0904).
+max-public-methods=20
+
+# Maximum number of boolean expressions in a if statement
+max-bool-expr=5
+
+
+[EXCEPTIONS]
+
+# Exceptions that will emit a warning when being caught. Defaults to
+# "Exception"
+overgeneral-exceptions=Exception

.travis.yml

@@ -0,0 +1,129 @@
+#
+# Gramps - a GTK+/GNOME based genealogy program
+#
+# Copyright (C) 2015-2015  Doug Blank
+# Copyright (C) 2016       DaAwesomeP
+# Copyright (C) 2016       QuLogic
+# Copyright (C) 2016       Tim G L Lyons
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+# After changing this file, check it on:
+#   http://lint.travis-ci.org/
+
+sudo: required
+dist: trusty
+language: python
+python:
+ - 3.3 # This is irrelevant, because the virtualenv is not used at all
+
+# FIXME: The minimum requirement for Gramps is Python 3.2, so a test environment
+# for Python 3.2 should be added to this environment which is Python 3.3. It
+# will not be possible to run coverage under Python 3.2, because coverage is
+# Python 3.3 (or above) only.
+
+addons:
+  apt:
+    packages:
+    - gir1.2-pango-1.0
+    - gir1.2-gtk-3.0
+    - xdg-utils
+    - librsvg2-common
+    - libglib2.0-dev
+    - intltool
+    # - python3-gobject Provided by python3-gi
+    - python3-gi
+    - python3-cairo
+    - python3-gi-cairo
+    - python3-bsddb3
+    - python3-dev
+    - python3-nose
+    - python3-mock
+    - python3-pyicu
+    - python3-coverage
+    - python3-jsonschema
+    # lxml dependencies.  for merge_ref_test to work
+    # - libxml2-dev
+    # - libxslt1-dev
+    - libxml2-utils
+    - python3-lxml
+    - python-libxml2
+# ubuntu 14.04 requires this in addition to libxml2-dev and
+# libxslt1-dev for compiling lxml.
+# https://github.com/deanmalmgren/textract/issues/19
+    - zlib1g-dev
+
+before_install:
+
+install:
+# The working directory is set to /home/travis/build/gramps-project/gramps
+# by the automatic git checkout.
+
+# Download Sean Ross-Ross's Pure Python module containing a framework to
+# manipulate and analyze python ast�s and bytecode. This is loaded to 
+# /home/travis/build/gramps-project/gramps/meta
+# FIXME: This should be loaded from the release directory at
+# https://pypi.python.org/pypi/meta
+ - git clone -b master https://github.com/srossross/meta
+
+# Build Gramps package. This seems to copy everything to
+# /home/travis/build/scripts-3.3
+ - python setup.py build
+
+before_script:
+# Create the Gramps database directory.
+ - mkdir -p ~/.gramps/grampsdb/
+# set PYTHONPATH so the directly installed module (meta) is picked up from
+# /home/travis/build/gramps-project/gramps/meta
+ - export PYTHONPATH=meta
+# set module exclusions. --exclude=TestUser because of older version of mock
+# without configure_mock
+ - export EXCLUDE="--exclude=TestcaseGenerator"
+#   --exclude=merge_ref_test"
+# set GRAMPS_RESOURCES for locale, data,image and documentation
+ - export GRAMPS_RESOURCES=.
+# Install addons
+ - mkdir -p ~/.gramps/gramps50/plugins/
+ - wget https://github.com/gramps-project/addons/raw/master/gramps50/download/CliMerge.addon.tgz
+ - tar -C ~/.gramps/gramps50/plugins -xzf CliMerge.addon.tgz
+ - wget https://github.com/gramps-project/addons/raw/master/gramps50/download/ExportRaw.addon.tgz
+ - tar -C ~/.gramps/gramps50/plugins -xzf ExportRaw.addon.tgz
+
+script:
+# Ignore the virtualenv entirely. Use nosetests3, python3 (3.4.0) and coverage
+# from /usr/bin. Use libraries from /usr/lib/python3.4,
+# /usr/local/lib/python3.4/dist-packages and /usr/lib/python3/dist-packages
+ - nosetests3 --nologcapture --with-coverage --cover-package=gramps $EXCLUDE
+   gramps
+# FIXME: This should have run from the current directory, rather than from
+# gramps, because there is some test code in that directory.
+
+# give an error for any trailing whitespace
+ - if git --no-pager grep --color -n --full-name '[ 	]$' -- \*.py; then
+     echo "ERROR - Trailing whitespace found in source file(s)";
+     exit 1;
+   fi
+
+after_success:
+# apt-get installs python3-coverage, but codecov only invokes coverage, so make
+# a link
+ - sudo ln /usr/bin/python3-coverage /usr/bin/coverage
+
+# We have to use the bash script because the apt-get coverage does not install
+# codecov. If we used pip to install codecov, it would run inside the
+# virtualenv, and that doesn't work. Change the path to ensure that codecov
+# picks up coverage from /usr/bin, rather than from
+# /home/travis/virtualenv/python3.3.6/bin/
+ - PATH=/usr/bin:$PATH bash <(curl -s https://codecov.io/bash)

AUTHORS

@@ -1,17 +1,94 @@
-Donald N. Allingham ** Concept and main design
+<!-- $Id$ -->
 
-David Hampton ** Autocomp.py and Report.py
 
-Donald A. Peterson  ** Makefiles, LaTeXDoc.py
+Alex Roitman shura@gramps-project.org
 
-Alex Roitman ** BookReport, command line, Gramps manual, bugfixes
+Arturas Sleinius asleinius@users.sourceforge.net
 
-Tim Waugh ** Comprehensive Ancestor report, docgen, Makefiles, bugfixes
+Benny Malengier benny.malengier@gramps-project.org
 
-Martin Hawlisch - Filters
+Boril Gourinov boril.gourinov@gmail.com
 
-Richard Taylor - ScratchPad.py, GrampsDBCallback.py
+Brian Matherly brian@gramps-project.org
 
-Brian Matherly - Reports
+Craig J. Anderson ander882@hotmail.com
 
-$Id$
+Don Allingham don@gramps-project.org
+
+Donald A. Peterson
+
+Doug Blank doug.blank@gmail.com
+
+Eero Tamminen eerot@users.sourceforge.net
+
+Erik De Richter erikdrgm@users.sourceforge.net
+
+Espen Berg espenbe@gmail.com
+
+Gary Burton gary.burton@zen.co.uk
+
+Gerald Britton gerald.britton@gmail.com
+
+James G Sack jgsack@san.rr.com
+
+Janne Kovesjärvi janne.kovesjarvi@gmail.com
+
+Jason Simanek jsimanek@gmail.com
+
+Jérôme Rapinat romjerome@yahoo.fr
+
+Joan Creus joan.creus@gmail.com
+
+Josip Pisoj josip@pisoj.com
+
+Julio Sánchez julio.sanchez@gmail.com
+
+Kees Bakker kees.bakker@xs4all.nl
+
+Konstantin Dorichev kdorichev@gmail.com
+
+Lubo Vasko pgval@inMail.sk
+
+Luigi Toscano luigi.toscano@tiscali.it
+
+Luiz Gonzaga dos Santos Filho lfilho@gmail.com
+
+Łukasz Rymarczyk yenidai@poczta.onet.pl
+
+Michiel Nauta m.d.nauta@hetnet.nl
+
+Mirko Leonhäuser mirko@leonhaeuser.de
+
+Morten Bo Johansen mbj@spamcop.net
+
+Martin Hawlisch martin.hawlisch@gmx.de
+
+Nick Hall nick__hall@hotmail.com
+
+Peter Landgren peter.talken@telia.com
+
+Raphael Ackermann raphael.ackermann@gmail.com
+
+Richard Taylor rjt-gramps@thegrindstone.me.uk
+
+Rob G. Healey robhealey1@gmail.com
+
+Serge Noiraud Serge.Noiraud@free.fr
+
+Sigmund Lorentsen sigmund.lorentsen@tele2.no
+
+Stefan Bjork betula@users.sourceforge.net
+
+Stéphane Charette stephanecharette@gmail.com
+
+Tim G L Lyons tim.g.lyons@gmail.com
+
+Tim Waugh twaugh@redhat.com
+
+Vassilii Khachaturov vassilii@tarunz.org
+
+Zdeněk Hataš zdenek.hatas@gmail.com
+
+Zsolt Foldvari zfoldvar@users.sourceforge.net
+
+John Ralls jralls@ceridwen.us

CONTRIBUTING

@@ -0,0 +1,12 @@
+See developer documentation at:
+https://gramps-project.org/wiki/index.php?title=Portal:Developers
+https://gramps-project.org/wiki/index.php?title=Brief_introduction_to_Git#Making_a_patchfile
+https://gramps-project.org/wiki/index.php?title=Brief_introduction_to_Git#Making_a_PR
+
+If you are interested in translating:
+* The Gramps program to your language see:
+https://gramps-project.org/wiki/index.php?title=Translating_Gramps
+https://gramps-project.org/wiki/index.php?title=Portal:Translators
+
+* The Gramps user manual to your language see:
+https://gramps-project.org/wiki/index.php?title=Translating_the_Gramps_User_manual

COPYING

@@ -2,7 +2,7 @@
 		       Version 2, June 1991
 
  Copyright (C) 1989, 1991 Free Software Foundation, Inc.
-                          675 Mass Ave, Cambridge, MA 02139, USA
+ 51 Franklin St, Fifth Floor, Boston, MA  02110-1301, USA
  Everyone is permitted to copy and distribute verbatim copies
  of this license document, but changing it is not allowed.
 

FAQ

@@ -1,4 +1,4 @@
-**** This is GRAMPS Frequently Asked Questions ****
+**** This is Gramps Frequently Asked Questions ****
 
 The questions below frequently come up in mailing list discussions and forums.
 This list is by no means complete. If you would like to add questions/answers 
@@ -9,23 +9,23 @@ to this list, please email your suggestions to gramps-devel@lists.sf.net
 
 ==General==
 
- 1. What is GRAMPS?
+ 1. What is Gramps?
 
  2. Where do I get it and how much does it cost?
 
- 3. Does GRAMPS exist in other languages?
+ 3. Does Gramps exist in other languages?
 
  4. How do I keep backups?
 
  5. Does Gramps support Unicode fonts? In particular, does it support non-Roman Unicode fonts?
 
- 6. What is needed to install GRAMPS under Linux, Solaris, or FreeBSD?
+ 6. What is needed to install Gramps under Linux, Solaris, or FreeBSD?
 
  7. Does it work with Windows (tm)?
 
  8. Does it work with the Mac?
 
- 9. What are the Minimum Specs to run GRAMPS?
+ 9. What are the Minimum Specs to run Gramps?
 
 ==Preferences==
 
@@ -33,43 +33,43 @@ to this list, please email your suggestions to gramps-devel@lists.sf.net
 
 ==Collaboration-Portability==
 
- 11. Is GRAMPS compatible with other genealogical software?
+ 11. Is Gramps compatible with other genealogical software?
 
- 12. Can GRAMPS read files created by GenApp X?
+ 12. Can Gramps read files created by GenApp X?
 
- 13. Can GRAMPS write files readable by GenApp X?
+ 13. Can Gramps write files readable by GenApp X?
 
- 14. What standards does GRAMPS support?
+ 14. What standards does Gramps support?
 
- 15. How do I import data from another genealogy program into GRAMPS?
+ 15. How do I import data from another genealogy program into Gramps?
 
- 16. Can I install GRAMPS on a Linux Web Server and use it via a web browser? This would enable my relations worldwide to access and update it.
+ 16. Can I install Gramps on a Linux Web Server and use it via a web browser? This would enable my relations worldwide to access and update it.
 
 ==Reports==
 
- 17. Can GRAMPS print a genealogical tree for my family?
+ 17. Can Gramps print a genealogical tree for my family?
 
- 18. In what formats can GRAMPS output its reports?
+ 18. In what formats can Gramps output its reports?
 
  19. How can I change the default language in reports?
 
- 20. Is GRAMPS compatible with the Internet?
+ 20. Is Gramps compatible with the Internet?
 
  21. Can I create custom reports/filters/whatever?
 
  22. Why are non-latin characters displayed as garbage in PDF/PS reports?
 
- 23. I would like to contribute to GRAMPS by writing my favorite report.
+ 23. I would like to contribute to Gramps by writing my favorite report.
 
-==Database - GRAMPS file formats==
+==Database - Gramps file formats==
 
- 24. What is the maximum database size (bytes) GRAMPS can handle?
+ 24. What is the maximum database size (bytes) Gramps can handle?
 
- 25. How many people can GRAMPS database handle? 
+ 25. How many people can Gramps database handle? 
 
  26. My database is really big. Is there a way around loading all the data into memory?
 
- 27. Can I run GRAMPS from a database on a NFS share?
+ 27. Can I run Gramps from a database on a NFS share?
 
  28. Why is the database format not portable?
 
@@ -77,123 +77,116 @@ to this list, please email your suggestions to gramps-devel@lists.sf.net
 
  29. I found a bug and I want it fixed right now! What do I do?
 
- 30. GRAMPS should be a .... type of application
+ 30. Gramps should be a .... type of application
 
-==GRAMPS Webhosting ==
-
- 31. How can I publish web sites generated by GRAMPS?
-
- 32. How do I submit my pages to the GRAMPS library site (http://library.gramps-project.org)?
-
- 33. After I upload my Family Web Page to library.gramps-project.org, is the password used for write privileges only or read privileges?
-
- 34. Do I view the Family Web Page with a url into my browser? Or through a link on a list of Family Web Pages on the GRAMPS-Project.org site?
+==Gramps Webhosting ==
 
+ 31. How can I publish web sites generated by Gramps?
 
 
 **** Questions and answers ****
 
 ==General==
 
-1. What is GRAMPS?
+1. What is Gramps?
 
-GRAMPS is the Genealogical Research and Analysis Management Program System. 
+Gramps 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. 
 
 
 2. Where do I get it and how much does it cost?
 
-GRAMPS can be downloaded from http://sf.net/projects/gramps at no charge. 
-GRAMPS is an Open Source project covered by the GNU General Public License. 
+Gramps can be downloaded from http://sf.net/projects/gramps at no charge. 
+Gramps 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. 
 
 
-3. Does GRAMPS exist in other languages?
+3. Does Gramps exist in other languages?
 
-Yes, at the moment GRAMPS is translated in 15 languages
+Yes, at the moment Gramps is translated in 15 languages
 
 
 4. How do I keep backups?
 
-Use a recent version of GRAMPS! From 2.2.5 onwards there is an automatic backup utility.
-It is extremely important to keep backups of your data, and keep them in a safe place. GRAMPS has a specific portable file format which is small, and human readable, denoted by .gramps. If you have allowed this in the preferences (In Edit menu->Preferences->General), GRAMPS will keep a backup of your database on exit. You can copy this backup file from time to time to a save location (eg a usb stick). 
+Use a recent version of Gramps! From 2.2.5 onwards there is an automatic backup utility.
+It is extremely important to keep backups of your data, and keep them in a safe place. Gramps has a specific portable file format which is small, and human readable, denoted by .gramps. If you have allowed this in the preferences (In Edit menu->Preferences->General), Gramps will keep a backup of your database on exit. You can copy this backup file from time to time to a save location (eg a usb stick). 
 
-Note: The .gramps files are compressed. Clicking them will open GRAMPS. To see the XML select them and open them with a decompressing utility (like ark, gunzip), after which you can extract the XML file which is human readable.
-Do not keep backups in GEDCOM. Not all information GRAMPS stores can be written in the GEDCOM. Hence, an export/import operation GRAMPS --> GEDCOM --> GRAMPS, will mean you lose data. Use the .gramps file format for backups!
+Note: The .gramps files are compressed. Clicking them will open Gramps. To see the XML select them and open them with a decompressing utility (like ark, gunzip), after which you can extract the XML file which is human readable.
+Do not keep backups in GEDCOM. Not all information Gramps stores can be written in the GEDCOM. Hence, an export/import operation Gramps --> GEDCOM --> Gramps, will mean you lose data. Use the .gramps file format for backups!
 Do not keep backups in GRDB format. GRDB is a database, which might be computer dependent (read, not working on a different PC). Small damage to a GRDB file can also not be repaired. Use the .gramps file format for backups!
 
 
 5. Does Gramps support Unicode fonts? In particular, does it support non-Roman Unicode fonts?
 
-Yes. GRAMPS works internally with Unicode (UTF-8), so all alphabets can be used on all entry fields. All reports fully support this, although for PDF/PS you need to work with gnome-print or openoffice.
+Yes. Gramps works internally with Unicode (UTF-8), so all alphabets can be used on all entry fields. All reports fully support this, although for PDF/PS you need to work with gnome-print or openoffice.
 
 ==Installation==
 
-6. What is needed to install GRAMPS under Linux, Solaris, or FreeBSD?
+6. What is needed to install Gramps under Linux, Solaris, or FreeBSD?
 
-GRAMPS is a [http://en.wikipedia.org/wiki/Gtk GTK] application. GRAMPS needs to have the [http://en.wikipedia.org/wiki/Pygtk pygtk] libraries installed on the system. As long as these libraries are installed, GRAMPS should function. It will operate under the GNOME desktop, KDE desktop, or any other desktop. If the GNOME bindings for Python are installed on the system, GRAMPS will have additional functionality. The GRAMPS project recommends version 2.8 or higher of GTK.
+Gramps is a [http://en.wikipedia.org/wiki/Gtk GTK] application. Gramps needs to have the [http://en.wikipedia.org/wiki/Pygtk pygtk] libraries installed on the system. As long as these libraries are installed, Gramps should function. It will operate under the GNOME desktop, KDE desktop, or any other desktop. If the GNOME bindings for Python are installed on the system, Gramps will have additional functionality. The Gramps project recommends version 2.8 or higher of GTK.
 
 
 7. Does it work with Windows (tm)?
 
-The Linux Genealogy CD can function as a live CD that you boot directly from. You can then run Linux and GRAMPS off the CD, even if your computer is entirely Windows.
+The Linux Genealogy CD can function as a live CD that you boot directly from. You can then run Linux and Gramps off the CD, even if your computer is entirely Windows.
 
 An experimental Windows installer is available, however we do not have the manpower to offer support for Windows. A windows mailing list is available however and we do do our best to solve windows related problems.
 
 
 8. Does it work with the Mac?
 
-The Fink project has ported some older versions of GRAMPS to OS X (tm). The Mac OS X port is not directly supported by the GRAMPS project, primarily because none of the GRAMPS developers have access to Mac OS X and because OS X is not Free Software.
+The Fink project has ported some older versions of Gramps to OS X (tm). The Mac OS X port is not directly supported by the Gramps project, primarily because none of the Gramps developers have access to Mac OS X and because OS X is not Free Software.
 
-This present version of GRAMPS (2.2.x) does not appear to have been ported by the Fink project. Please contact the Fink project for more information. However, some users had success in installing 2.2.x on Mac OSX either running in native mode or running on X11 using some of the fink packages. 
+This present version of Gramps (2.2.x) does not appear to have been ported by the Fink project. Please contact the Fink project for more information. However, some users had success in installing 2.2.x on Mac OSX either running in native mode or running on X11 using some of the fink packages. 
 
 
-9. What are the Minimum Specs to run GRAMPS?
+9. What are the Minimum Specs to run Gramps?
 
-We would recommend at least an 800x600 video display. For GRAMPS 2.0, the memory requirements have been reduced, and GRAMPS can run quite efficiently on a 256MB system, holding considerably more people. A system with 512MB should be able to hold around 200,000 people. Disk space requirements for databases are however considerably larger, with a typical database being several megabytes in size. For 120.000 people you must consider already 530Mb for the database. Pictures are stored on disk separately, so a large harddisk is necessary.
+We would recommend at least an 800x600 video display. For Gramps 2.0, the memory requirements have been reduced, and Gramps can run quite efficiently on a 256MB system, holding considerably more people. A system with 512MB should be able to hold around 200,000 people. Disk space requirements for databases are however considerably larger, with a typical database being several megabytes in size. For 120.000 people you must consider already 530Mb for the database. Pictures are stored on disk separately, so a large harddisk is necessary.
 
 
 ==Preferences==
 
 10. Can I change the dates in reports to 'day month year'
 
-Yes, change in the preferences ("Edit->Preferences") the date for GRAMPS to the required format (eg YYYY-MM-DD or day mont year), and make the report. Your global date preferences will be used.
+Yes, change in the preferences ("Edit->Preferences") the date for Gramps to the required format (eg YYYY-MM-DD or day mont year), and make the report. Your global date preferences will be used.
 
 
 ==Collaboration-Portability==
 
-11. Is GRAMPS compatible with other genealogical software?
+11. Is Gramps compatible with other genealogical software?
 
-GRAMPS makes every effort to maintain compatibility with GEDCOM, the general standard of recording genealogical information. We have import and export filters that enable GRAMPS to read and write GEDCOM files.
+Gramps makes every effort to maintain compatibility with GEDCOM, the general standard of recording genealogical information. We have import and export filters that enable Gramps 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 GRAMPS, and we will do our best to support it!
+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 Gramps, and we will do our best to support it!
 
 
-12. Can GRAMPS read files created by GenApp X?
+12. Can Gramps read files created by GenApp X?
 
 See above.
 
 
-13. Can GRAMPS write files readable by GenApp X?
+13. Can Gramps write files readable by GenApp X?
 
 See above.
 
 
-14. What standards does GRAMPS support?
+14. What standards does Gramps support?
 
-The nice thing about standards is that there never is a shortage of them. GRAMPS is tested to support the following flavors of GEDCOM: GEDCOM5.5, Brother's Keeper, Family Origins, Family Tree Maker, Ftree, GeneWeb, Legacy, Personal Ancestral File, Pro-Gen, Reunion, and Visual Genealogie.
+The nice thing about standards is that there never is a shortage of them. Gramps is tested to support the following flavors of GEDCOM: GEDCOM5.5, Brother's Keeper, Family Origins, Family Tree Maker, Ftree, GeneWeb, Legacy, Personal Ancestral File, Pro-Gen, Reunion, and Visual Genealogie.
 
 
-15. How do I import data from another genealogy program into GRAMPS?
+15. How do I import data from another genealogy program into Gramps?
 
 The best way is to create a new gramps database file (.grdb), and select the import option in the file menu. Here you select the GEDCOM you generated with the other program, and import it. 
 
 
-16. Can I install GRAMPS on a Linux Web Server and use it via a web browser? This would enable my relations worldwide to access and update it.
+16. Can I install Gramps on a Linux Web Server and use it via a web browser? This would enable my relations worldwide to access and update it.
 
-While GRAMPS can generate web sites, it does not provide a web interface that allows for editing. If this is a requirement, then [http://geneweb.org GeneWeb] or [http://phpgedview.sourceforge.net PhpGedView] are programs more likely to meet your needs. However, you may wish to ask yourself the following questions:
+While Gramps can generate web sites, it does not provide a web interface that allows for editing. If this is a requirement, then [http://geneweb.org GeneWeb] or [http://phpgedview.sourceforge.net PhpGedView] are programs more likely to meet your needs. However, you may wish to ask yourself the following questions:
 * Do I really want relatives or other people to directly edit my genealogy database?
 * Do I implicitly trust, without verification, any data that people may enter?
 * Do these people have the same understanding of good genealogy practice that I have?
@@ -204,7 +197,7 @@ You may also want to consider the effects of possible downtime of your site if y
 
 ==Reports==
 
-17. Can GRAMPS print a genealogical tree for my family?
+17. Can Gramps 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 
@@ -212,14 +205,14 @@ 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. 
 
-GRAMPS can produce any of the above, and many more different charts and 
+Gramps 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. 
 
 
-18. In what formats can GRAMPS output its reports?
+18. In what formats can Gramps output its reports?
 
-Text reports are available in HTML, PDF, ODT, LaTeX, and RTF formats. Graphical reports (charts and diagrams) are available in PostScript, PDF, SVG, ODS, and GraphViz formats.
+Text reports are available in HTML, PDF, ODT, LaTeX, and RTF formats. Graphical reports (charts and diagrams) are available in PostScript, PDF, SVG, ODS, and Graphviz formats.
 
 
 19. How can I change the default language in reports? 
@@ -227,11 +220,11 @@ Text reports are available in HTML, PDF, ODT, LaTeX, and RTF formats. Graphical
 The reports are in the language of your linux installation. You can change it by installing extra language packs, see [Howto: Change the language of reports] on wiki.
 
 
-20. Is GRAMPS compatible with the Internet?
+20. Is Gramps compatible with the Internet?
 
-GRAMPS can store web addresses and direct your browser to them. It can import
+Gramps 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. GRAMPS is familiar with the standard file formats 
+send over the Internet. Gramps 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 :-) 
@@ -241,7 +234,7 @@ there is little that a genealogical program can do with the Internet :-)
 
 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 GRAMPS 
+the fonts, colors, and some layout of the reports. You can also use Gramps 
 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 
@@ -253,47 +246,47 @@ knowledge of programming in Python.
 
 22. Why are non-latin characters displayed as garbage in PDF/PS reports?
 
-This is a limitation of the built-in fonts of PS and PDF formats. To print non-Latin text, use the Print... in the format selection menu of the report dialog. This will use the gnome-print backend, which supports PS and PDF creation, as well as direct printing. (Note: you might need to install gnome-print separately as it is not required for GRAMPS).
+This is a limitation of the built-in fonts of PS and PDF formats. To print non-Latin text, use the Print... in the format selection menu of the report dialog. This will use the gnome-print backend, which supports PS and PDF creation, as well as direct printing. (Note: you might need to install gnome-print separately as it is not required for Gramps).
 
 If you only have Latin text, the PDF option will produce a smaller PDF compared to that created by gnome-print, simply because no font information will be embedded.
 
 
-23. I would like to contribute to GRAMPS by writing my favorite report.
+23. I would like to contribute to Gramps 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 GRAMPS 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 GRAMPS tool, you will need to write your own plugin from scratch. Help is available on the [Developers Portal] on wiki, or on the developers mailing list: gramps-devel@lists.sourceforge.net.
+The easiest way to contribute to reports, filters, tools, etc. is to copy an existing Gramps 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 Gramps tool, you will need to write your own plugin from scratch. Help is available on the [Developers Portal] on wiki, or on the developers mailing list: gramps-devel@lists.sourceforge.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 GRAMPS, create menu item, and so on.
+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 Gramps, create menu item, and so on.
 
-If you are happy with your plugin and would like to contribute your code back to the GRAMPS project, you are very welcome to do so by contacting us at gramps-devel@lists.sourceforge.net
+If you are happy with your plugin and would like to contribute your code back to the Gramps project, you are very welcome to do so by contacting us at gramps-devel@lists.sourceforge.net
 
 
-==Database - GRAMPS file formats==
+==Database - Gramps file formats==
 
-24. What is the maximum database size (bytes) GRAMPS can handle?
+24. What is the maximum database size (bytes) Gramps can handle?
 
-GRAMPS has no hard limits on the size of a database that it can handle. Starting with 2.0.0 release, GRAMPS no longer loads all data into memory, which allows it to work with a much larger database than before. In reality, however, there are practical limits. The main limiting factors are the available memory on the system and the cache size used for BSDDB database access. With common memory sizes these days, GRAMPS should have no problem using databases with tens of thousands of people.
+Gramps has no hard limits on the size of a database that it can handle. Starting with 2.0.0 release, Gramps no longer loads all data into memory, which allows it to work with a much larger database than before. In reality, however, there are practical limits. The main limiting factors are the available memory on the system and the cache size used for BSDDB database access. With common memory sizes these days, Gramps should have no problem using databases with tens of thousands of people.
 
 
-25. How many people can GRAMPS database handle? 
+25. How many people can Gramps database handle? 
 
-See above. Again, this is dependent on how much memory you have, see [GRAMPS Performance] on wiki.
+See above. Again, this is dependent on how much memory you have, see [Gramps Performance] on wiki.
 
 
 26. My database is really big. Is there a way around loading all the data into memory?
 
-Starting with 2.0.0 release, GRAMPS no longer loads all data into memory, which allows it to work with a much larger database than before. The fileformat used is .grdb which means gramps database.
+Starting with 2.0.0 release, Gramps no longer loads all data into memory, which allows it to work with a much larger database than before. The fileformat used is .grdb which means gramps database.
 
 
-27. Can I run GRAMPS from a database on a NFS share?
+27. Can I run Gramps from a database on a NFS share?
 
 Yes you can.
 
 
 28. Why is the database format not portable?
 
-The biggest issue with GRAMPS portability lies with 'transactions'. With
-GRAMPS 2.2, we added support for atomic transactions to protect data.
+The biggest issue with Gramps portability lies with 'transactions'. With
+Gramps 2.2, we added support for atomic transactions to protect data.
 With atomic transactions, multiple changes are committed as a single
 unit. Either all the changes make it, or none of the changes make it.
 You are never left in a situation with a partial set of changes. A side
@@ -341,41 +334,25 @@ If the above explanations seem vague, please follow this link:
 http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
 
 
-30. GRAMPS should be a .... type of application
+30. Gramps should be a .... type of application
 
-The surest way to see it happen is to get it done by yourself. Since GRAMPS 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 GRAMPS development. If you would like the GRAMPS project to provide advice, expertise, filters, etc., we will gladly cooperate with your new project, to ensure compatibility or import/export options to your new format of a project.
+The surest way to see it happen is to get it done by yourself. Since Gramps 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 Gramps development. If you would like the Gramps project to provide advice, expertise, filters, etc., we will gladly cooperate with your new project, to ensure compatibility or import/export options to your new format of a project.
 
-If, however, you would like the GRAMPS project to adopt your strategy, you would need to convince GRAMPS developers that your strategy is good for GRAMPS and superior to the present development strategy.
+If, however, you would like the Gramps project to adopt your strategy, you would need to convince Gramps developers that your strategy is good for Gramps and superior to the present development strategy.
                                                                                 
-HINT: if GRAMPS developers are still not convinced after about three
+HINT: if Gramps 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 :-)
 
 
-==GRAMPS Webhosting ==
+==Gramps Webhosting ==
 
-31. How can I publish web sites generated by GRAMPS?
+31. How can I publish web sites generated by Gramps?
 
-Since GRAMPS generates HTML pages, you can upload the pages to your personal web site. If you do not have a personal web site, and still wish to have your pages available on the internet, the GRAMPS project can provide space for you at the http://library.gramps-project.org, see the [webhosting article] on wiki.
+Since Gramps generates HTML pages, you can upload the pages to your personal web site. If you do not have a personal web site, and still wish to have your pages available on the internet.
 
 
-32. How do I submit my pages to the GRAMPS library site (http://library.gramps-project.org)?
-
-If you wish to submit pages to the GRAMPS library site, you will need to contact the GRAMPS project, typically by sending a message to the gramps-users mailing list. You will then be given a username and password that will allow you to upload your files to the site. After you upload the files (in a gzip'ed tar file), the GRAMPS project will install the pages for you on the site.
-
-
-33. After I upload my Family Web Page to library.gramps-project.org, is the password used for write privileges only or read privileges?
-
-In order to prevent abuse of the library.gramsp-project.org site, the password given allows uploads only. If you wish to have a username and password combination to restrict read access to your pages, you will need to contact the GRAMPS project, and we could set this up for you. However, the read and write accounts will be separate accounts.
-
-
-34. Do I view the Family Web Page with a url into my browser? Or through a link on a list of Family Web Pages on the GRAMPS-Project.org site?
-
-The main page on the library.gramps-project.org site will contain an index of the available family sites. However, there will be a unique URL for each site as well.
-
-
-
-**** End of GRAMPS Frequently Asked Questions ****
+**** End of Gramps Frequently Asked Questions ****
 
 $Id$

Gramps.py

@@ -0,0 +1,29 @@
+#! /usr/bin/env python3
+#
+# Gramps - a GTK+/GNOME based genealogy program
+#
+# Copyright (C) 2012       Benny Malengier
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301  USA
+#
+
+"""
+This is a stub to start Gramps. It is provided for the sole reason of being
+able to run gramps from the source directory without setting PYTHONPATH
+
+From this position, import gramps works great
+"""
+import gramps.grampsapp as app
+app.main()

INSTALL

@@ -1,114 +1,106 @@
-$Id$
-
 This file contains some useful details on the installation from source code
-for GRAMPS. It does not cover installation of a pre-built binary package.
+for Gramps. It does not cover installation of a pre-built binary package.
 For that use your package manager, the rest is already done by the packager.
 
 Uninstall old version
 ---------------------
-If you do a source install in the same place of an existing install,
+If you do a source install in the same place as an existing install,
 you need to remove the old version first. You can delete the old
-version by:
+version by deleting the installed directories. For example, if your installation prefix is /usr/local, remove the following:
+        /usr/local/share/gramps
+        /usr/local/lib/pythonx.x/site-packages/gramps
+If you installed with a package manager you might instead need to remove
+        /usr/local/lib/pythonx.x/dist-packages/gramps
 
-  * deleting the installed directories (for example,
-    /usr/share/gramps)
-  * OR by running "make uninstall" from the old directory where you
-    ran "make install" (not the new GRAMPS directory)
+replacing pythonx.x with the python version you used, e.g. python3.4.
+Also remove any gramps .egg files that are installed along with the gramps
+directory and the file /usr/local/bin/gramps.
 
-GRAMPS is a python application, so loading happens on reading the
+
+If you don't know the list of all files that Gramps installed, you can
+reinstall it with the --record option, and take a look at the list this
+produces (so python setup.py install --record grampsfiles.txt
+
+Gramps is a python application, so loading happens on reading the
 files, meaning that files of a previous version that are no longer
 present in the new version can still be loaded, making the new install
-unstable.
+unstable!
 
-Configure vs autogen scripts
-----------------------------
-Configure does not check all dependencies of Gramps, see README for a 
-list of all required and optional dependencies.
+distutils install
+-----------------
+We do not check all dependencies of Gramps, see README for a list of
+all required and optional dependencies. Missing dependencies will
+result in runtime errors.
 
-If you are building from released tarball, you should be able to just
-run "./configure && make". However, if you're building from the SVN,
-the configure is not present. You should auto-generate it by
-running ./autogen.sh and then "make" and, finally, "make install".
+To build and install, whether from a tarball or git repo:
+   python setup.py build
+   sudo python setup.py install
 
-Running ./autogen.sh on this branch of gramps requires the following
-packages to be installed:
-   * autoconf >=2.53
-   * automake >=1.9
-   * intltool >=0.25
-   * glib-gettext >=2.2.0, included in libglib2.0-dev (may be called
-differently on other distros) and maybe something else. If autogen.sh
-fails, it should inform you what's missing.
+You can avoid using sudo for the install step by specifying a prefix to which you have write priviledge. The default is /usr/local, which is usually owned by root. You can learn of more options with
+   python setup.py --help
+
+One can use gramps from the command line without installing it by
+setting the following environment variables, but that won't provide
+things like MIME type and desktop entries.
+
+   export PYTHONPATH="/top/grampsdir/gramps:$PYTHONPATH"
+   export GRAMPS_RESOURCES="/top/grampsdir"
+
+See below for ways to invoke Gramps.
+
+Typical install directories in linux (ubuntu) are:
+  * /usr/local/lib/python3.4/dist-packages/gramps/  : the gramps python module
+  * /usr/local/share/mime-info    : mime info so gramps opens files automatically
+  * /usr/local/share/icons/gnome  : our icons
+  * /usr/local/share/doc/gramps   : documentation, also example .gramps and .gedcom
+  * /usr/local/bin                : the gramps executable
+  * /usr/local/share/locale/xx/LC_MESSAGES  : xx language code, translation
+  * /usr/local/share/man/man1/xx/man1       : xx language code, man file
+  * /usr/local/share/mime
+  * /usr/local/share/mime-info
+
+Running Gramps
+--------------
+Gramps is python only, so no compilation is needed, you can even run gramps
+from the source directory.
+
+ a) You installed Gramps, then you can run it with the command
+
+     gramps
+
+ b) You installed Gramps, and want to start it from the PYTHONPATH. In this
+    case use the command:
+
+     python -c 'from gramps.grampsapp import main; main()'
+
+   The executable 'gramps' in /usr/local/bin or /usr/bin from a) does
+   this for you.
+
+ b) You downloaded the Gramps source code to a directory, and want to run it.
+    You can start Gramps from the source code directory with
+
+     python Gramps.py
+
+    See gramps/gen/const.py how Gramps finds its resource directories in case
+    you encounter problems.
 
 Custom directory installation
 -------------------------------------
-If you would like to install GRAMPS without being root, or in an 
-alternative location on windows, supply the --prefix argument to autogen 
-or configure. 
+If you would like to install Gramps without being root, or in an
+alternative location on windows, supply the --root argument to setup.py
 
 For example:
-   ./autogen.sh --prefix=$HOME/my_gramps_path
-   or
-   ./autogen.sh --prefix=/cygdrive/c/Projects/gramps
-
-Regular vs local installation
------------------------------
-This version of gramps REQUIRES, among other things, the mime types for 
-gramps be properly installed.
-
-The usual ./configure, make, and make install as a root should do the trick.
-
-But be careful if you're using the non-default options or would like
-to install without being root.
-
-The latter is possible, but you should supply additional arguments to
-autogen or configure:
-   --with-mime-dir=$HOME/.local/share/mime
-Most likely, such local install will also need some prefix with write
-permissions for you:
-   --prefix=$HOME/my_gramps_path
-
-Whether you're doing local install or regular install, YOU MUST INSTALL 
-MIME TYPES. YOU HAVE BEEN WARNED!
-
-Installing under non-default prefix
------------------------------------
-As hinted above, mime types for gramps MUST be properly installed. 
-The "proper install" means installing them where the shared mime system 
-will find them.
-
-By default, the shared mime systems will look in these places:
-   1. /usr/share/mime
-   2. /usr/local/share/mime   : this may be broken on some systems
-   3. $HOME/.local/share/mime : this is a per-user setup, not system-wide
-There's a number of ways to instruct the shared mime system
-to look in other places, but this is the whole other story.
-
-So if you install some place other than /usr/share, you will most
-likely need to add this option to autogen.sh/configure scripts:
-   --with-mime-dir=/usr/share/mime
-
-Using the --prefix=/usr/share and installing as a root will most
-likely do everything correctly, so no extra care needs to be
-taken. You should take extra care only if you are installing under
-something like --prefix=/usr/local/my_gramps, /var/gramps123/blah, etc.
+   python setup.py install --root ~/test
 
 Packager's issues
 ------------------
-The above mime types must be installed. However, the 
-update-mime-database call to process the newly installed types and 
-schemas must be done in POST-INSTALLATION.
+There is a MANIFEST.in file to indicate the work needed.
+To create a source distribution run:
 
-In packager's world, the install happens on packager's machine
-into something like /tmp/gramps-tmp. However, the postinstall
-should happen on the user's machine.
+   python setup.py sdist
 
-To assist with that, there's an argument available in configure
-(or autogen, which will pass it to configure) which disables
-mime type processing:
-   --enable-packager-mode
-This argument should disable postinstall calls made during
-make install, and print a nasty warning during configure.
-IT IS PACKAGER'S RESPONSIBILITY to follow the advice given
-by the configure output and to copy the appropriate code
-from the data/Makefile.am into the post-install (and post-uninstall)
-of the particular packaging system.
+If Gramps is built outside of the source tree in a temporary location (e.g. when
+packaging for a distribution), the --resourcepath option can be used to specify
+the path to the installed location of the Gramps resources (e.g. /usr/share):
+
+   python setup.py install --resourcepath=/usr/share

MANIFEST.in

@@ -0,0 +1,32 @@
+include ChangeLog
+include po/ChangeLog
+include AUTHORS
+include COPYING
+include FAQ
+include Gramps.py
+include INSTALL
+include MANIFEST.in
+include NEWS
+include RELEASE_NOTES
+include TODO
+include CONTRIBUTING
+include TestPlan.txt
+recursive-include data *
+recursive-include debian *
+recursive-include docs *
+recursive-include gramps *
+recursive-include help *
+recursive-include images *
+recursive-include mac *
+recursive-include po *
+recursive-include test *
+recursive-include windows *
+
+# Remove files created in the build
+exclude data/tips.xml
+exclude data/holidays.xml
+exclude po/.intltool-merge-cache
+global-exclude *.pyc
+global-exclude *.pyo
+
+# Remove directories which should not be included in the distribution

Makefile.am

@@ -1,35 +0,0 @@
-# This is the top level Makefile for Gramps
-# $Id$
-
-SUBDIRS = m4 po src data example
-
-EXTRA_DIST = \
-	config.rpath autogen.sh \
-	FAQ COPYING \
-	intltool-extract.in intltool-merge.in intltool-update.in
-
-bin_SCRIPTS = gramps
-
-dist_pkgdata_DATA = COPYING
-
-distuninstallcheck_listfiles = find . -type -f -print | grep -E -v '/(globs|magic|XMLnamespaces)'
-
-DISTCLEANFILES = intltool-extract intltool-merge intltool-update \
-	gnome-doc-utils.make
-
-gramps: gramps.sh
-	cp gramps.sh gramps
-
-.PHONY: pycheck trans
-
-pycheck:
-	(cd src; make pycheck) 
-trans:
-	(cd src; make trans) 
-
-distuninstallcheck:
-	@:
-
-CLEANFILES = gramps
-
-ACLOCAL_AMFLAGS = -I m4

README

@@ -1,90 +0,0 @@
-Please read the COPYING file first.
-If building from source, also read the INSTALL file (at least through the
-"SUPER-SHORT VERSION") before going further.
-
-Requirements
---------------------------------
-The following packages *MUST* be installed in order for Gramps to work:
-   Python 2.6 or greater
-   PyGTK2 2.16 or greater
-   librsvg2 (svg icon view)
-   xdg-utils
-
-The following package is needed for full translation of the interface
-to your language:
-   language-pack-gnome-xx 
-                    Translation of GTK elements to your language, with             
-                    xx your language code eg for Dutch you need
-                    language-pack-gnome-nl. The translation of the
-                    Gramps strings is included with the source code.
-
-
-The following packages are *STRONGLY RECOMMENDED* to be installed:
-   osmgpsmap        Used to show maps in the geography view. 
-                    Without this the GeoView will not be active, see
-                    http://gramps-project.org/wiki/index.php?title=Gramps_3.3_Wiki_Manual_-_Main_Window#Geography_Category
-                    The package is named osmgpsmap, osm-gps-map
-                    or python-osmgpsmap. Or obtain it from: http://nzjrs.github.com/osm-gps-map/
-   GraphViz         Enable creation of graphs using GraphViz engine.
-                    Without this no beautiful graphs can be created.
-                    Obtain it from: http://www.graphviz.org
-   pyexiv2          Enables Gramps to manage Exif metadata embedded in your
-                    media. Gramps needs version 0.1.3 or greater.
-                    Obtain it from: http://tilloy.net/dev/pyexiv2/download.html  
-
-The following packages are optional
-   python gtkspell  Enable spell checking in the notes, gtkspell contains the
-                    libraries.
-
-   ttf-freefont     More font support in the reports
-
-   PyWebKitGtk or python-gtkmozembed: 
-                    The hidden view 'Htmlview' allows websites to be opened in
-                    Gramps. Users can unhide the view in the plugin manager. 
-                    A html renderer must be installed to use the view.
-                    !! PACKAGERS, Test if on your distribution
-                    webkit and Gramps is stable. If you obtain crashes, patch 
-                    src/plugins/view/htmlrenderer.py and
-                    src/plugins/view/geoview.gpr.py, so as to remove:
-                       import webkit
-                    Then use the gecko package (python-gtkmozembed) instead.
-                    If WEBKIT ang GECKO are installed, webkit will be used as
-                    the javascript engine is faster (google maps).
-                  * PyWebKitGtk    
-                    Enable html rendering for the Web view. Often called 
-                    python-webkit package. Be careful, webkit is always in a 
-                    development phase.
-                  * python-gtkmozembed 
-                    Enable html rendering for the Web view in case PyWebKitGtk
-                    is not available or to be used if webkit is unstable.
-                    It can be in python-gnome2-extras or python-gtkhtml2
-                    depending on distributions.
-
-   python-pygoocanvas:
-                    Required for the experimental Graphview plugin
-
-No longer needed in 3.3:
-   python-enchant Enchant
-No longer needed in 3.2:
-   python glade bindings
-No longer needed in 3.1:
-   yelp             Gnome help browser. At the moment no help is shipped
-
-Documentation
----------------------------------
-The User Manual is now maintained on the gramps website,
-http://www.gramps-project.org/wiki/index.php?title=User_manual
-We might in the future distribute again a manual via gnome-doc-utils, this has not
-been decided yet though.
-
-
-Building on non-Linux systems: i18n support and GNU make
---------------------------------------------------------
-If make fails, use gmake (the name FreeBSD gives to GNU make) instead.
-You might need a patch also. FreeBSD has in ports a patch (  /usr/ports/science/gramps/files)
-you need to apply to po/Makefile.in.in 
-
-
---------------------------------
-The Gramps Project
-http://gramps-project.org

README.md

@@ -0,0 +1,140 @@
+The Gramps Project ( https://gramps-project.org ) [![Build Status](https://travis-ci.org/gramps-project/gramps.svg?branch=master)](https://travis-ci.org/gramps-project/gramps)[![codecov.io](https://codecov.io/github/gramps-project/gramps/coverage.svg?branch=master)](https://codecov.io/github/gramps-project/gramps?branch=master)
+===================
+We strive to produce a genealogy program that is both intuitive for hobbyists and feature-complete for professional genealogists.
+
+Please read the **COPYING** file first.
+
+Please read the **INSTALL** file if you intend to build from source.
+
+Requirements
+============
+The following packages **MUST** be installed in order for Gramps to work:
+
+* **Python** 3.2 or greater - The programming language used by Gramps. https://www.python.org/
+* **GTK** 3.10 or greater - A cross-platform widget toolkit for creating graphical user interfaces. http://www.gtk.org/
+* **pygobject** 3.12 or greater - Python Bindings for GLib/GObject/GIO/GTK+ https://wiki.gnome.org/Projects/PyGObject
+
+The following three packages with GObject Introspection bindings (the gi packages)
+
+* **cairo** - a 2D graphics library with support for multiple output devices. http://cairographics.org/
+* **pango** - a library for laying out and rendering of text, with an emphasis on internationalization. http://www.pango.org/
+* **pangocairo** - Allows you to use Pango with Cairo http://www.pango.org/
+
+* **librsvg2** - (SVG icon view) a library to render SVG files using cairo. http://live.gnome.org/LibRsvg
+* **xdg-utils** - Desktop integration utilities from freedesktop.org
+* **bsddb3** - Python bindings for Oracle Berkeley DB https://pypi.python.org/pypi/bsddb3/
+
+
+The following package is needed for full translation of the interface
+to your language:
+
+*   **language-pack-gnome-xx**
+
+ Translation of GTK elements to your language, with
+ xx your language code; e.g. for Dutch you need
+ language-pack-gnome-nl. The translation of the
+ Gramps strings is included with the gramps source.
+
+
+The following packages are **STRONGLY RECOMMENDED** to be installed:
+--------------------------------------------------------------------
+*  **osmgpsmap**
+
+ Used to show maps in the geography view.
+ It may be osmgpsmap, osm-gps-map, or python-osmgpsmap,
+ but the Python bindings for this must also be present, so gir1.2-osmgpsmap-1.0.
+ Without this the GeoView will not be active, see
+ https://gramps-project.org/wiki/index.php?title=Gramps_4.2_Wiki_Manual_-_Categories#Geography_Category
+
+* **Graphviz**
+
+  Enable creation of graphs using Graphviz engine.
+  Without this, three reports cannot be run.
+  Obtain it from: http://www.graphviz.org or try graphviz and python3-pygraphviz from your packages.
+
+* **PyICU**
+
+ Improves localised sorting in Gramps. In particular, this
+ applies to sorting in the various views and in the
+ Narrative Web output. It is particularly helpful for
+ non-Latin characters, for non-English locales and on MS
+ Windows and Mac OS X platforms. If it is not available,
+ sorting is done through built-in libraries. PyICU is
+ fairly widely available through the package managers of
+ distributions. See http://pyicu.osafoundation.org/
+ (These are Python bindings for the ICU package. 
+ https://pypi.python.org/pypi/PyICU/)
+
+The following packages are optional:
+------------------------------------
+* **gtkspell** 
+
+ Enable spell checking in the notes. Gtkspell depends on
+ enchant. A version of gtkspell with gobject introspection
+ is needed, so minimally version 3.0.0
+
+* **rcs**
+
+ The GNU Revision Control System (RCS) can be used to manage
+ multiple revisions of your family trees. See info at
+ https://gramps-project.org/wiki/index.php?title=Gramps_4.2_Wiki_Manual_-_Manage_Family_Trees#Archiving_a_Family_Tree
+ Only rcs is needed, NO python bindings are required
+
+* **PIL**
+
+ Python Image Library is needed to crop
+ images and also to convert non-JPG images to
+ JPG so as to include them in LaTeX output.
+ (For Python3 a different source may be needed,
+ python-imaging or python-pillow or python3-pillow)
+
+* **GExiv2**
+
+ Enables Gramps to manage Exif metadata embedded in your
+ media. Gramps needs version 0.5 or greater.
+ See https://www.gramps-project.org/wiki/index.php?title=GEPS_029:_GTK3-GObject_introspection_Conversion#GExiv2_for_Image_metadata
+
+* **ttf-freefont**
+
+ More font support in the reports
+
+Optional packages required by Third-party Addons
+------------------------------------------------
+
+**Third-party Addons are written by users and developers and unless stated are not officially part of Gramps.**
+For more information about Addons see:  https://gramps-project.org/wiki/index.php?title=Third-party_Plugins
+
+Prerequistes required for the following Addons to work:
+
+* **Family Sheet** - Requires: PIL (Python Imaging Library) or PILLOW.
+( https://gramps-project.org/wiki/index.php?title=Family_Sheet )
+
+* **Graph View** - Requires: PyGoocanvas and Goocanvas (python-pygoocanvas, gir1.2-goocanvas-2.0).
+( https://gramps-project.org/wiki/index.php?title=Graph_View )
+
+* **PedigreeChart** - Can optionally use - numpy if installed
+( https://gramps-project.org/wiki/index.php?title=PedigreeChart )
+
+No longer needed:
+-----------------
+* Since Gramps 4.2:
+   **gir-webkit**
+
+* Since Gramps 4.0:
+   **pygoocanvas, pygtk, pyexiv2**
+
+* Since Gramps 3.3:
+   **python-enchant Enchant**
+
+* Since Gramps 3.2:
+   **python glade bindings**
+
+* Since Gramps 3.1:
+   **yelp** -             Gnome help browser. No offline help is shipped see Gramps website for User manual
+
+Documentation
+-------------
+The User Manual is maintained on the Gramps website:
+
+* https://www.gramps-project.org/wiki/index.php?title=User_manual
+

RELEASE_NOTES

@@ -1,24 +1,36 @@
-Gramps 3.2 Release Notes
+$Id$
 
-General Improvements
+UNSTABLE Gramps 4.0.0 Beta2 release.
 
-* New Plugin System
-In the Help Menu -> Menu Status, all available plugins are visible. All plugins can be hidden, saving resources and hiding options you do not need. Eg: You don't use the Pedigree View? Hide it in the Plugin Status, and it will not be present anymore. You don't use vcard export? Hide it in the Plugin Status, and it will not be offered anymore.
+This is a technology preview to allow distribution packagers (and plugin
+writers) to update their scripts (and plugins). This release is not
+production ready, so only use it for testing!
 
-* Faster
-Many under the hood improvements have occurred that should improve perfamance enormously. Yes, new features are present to use all your processing power, but they are all implemented as plugins that can be hidden. Eg: Insert of a person in a 30000 people family tree took 4sec on 1.4Ghz PC in 3.1, Now it is done in milliseconds.
+It is recommended that Gramps 4.0.0 be used with python 2.7 since many
+dependent packages do not yet have python 3 versions.  A determined person
+can probably download their sources and build them, however.
 
-*New Views
-There are new views, and some views have been greatly improved
-  - People view can now be sorted on the columns
-  - A Place treeview is present, nicely grouping your places under country groups
-  - GeoView has left it's beta status behind and shows your data on an 
-    online map (Openstreetmap or google maps, fast internet connection required)
-  - Help Menu -> Extra Reports/Tools open a webpage with downloadable extra views
+The dependencies for Gramps 4.0.0 are _completely_ different than 3.4 due 
+to the switch to GObject introspection, and the removal of autotools. So 
+only install 4.0.0 if you are certain you can obtain the dependencies, 
+see README and INSTALL. 
+
+For linux, in Ubuntu 12.10 you can install 4.0.0, but you will need to 
+compile and install osmgpsmap manually to have the maps working (see 
+http://www.gramps-project.org/wiki/index.php?title=GEPS_029:_GTK3-GObject_introspection_Conversion#OsmGpsMap_for_Geography ) 
 
 
-Other Improvements
+Major enhancements in Gramps 4.0.0:
 
-* Styled Notes now in most output formats that support styles, eg in the web report
-* New languages
-* Select language in which report should be created (only present now in some reports)
+* GEP 8: code reorganization: http://www.gramps-project.org/wiki/index.php?title=GEPS_008:_File_Organization
+
+* GEP 26: Replace make: http://www.gramps-project.org/wiki/index.php?title=GEPS_026:_Replace_%27make%27_for_Gramps_build
+
+* GEP 29: Gtk 3 :http://www.gramps-project.org/wiki/index.php?title=GEPS_029:_GTK3-GObject_introspection_Conversion
+
+* GEP 31: Python 3 support: http://www.gramps-project.org/wiki/index.php?title=GEPS_031:_Python_3_support
+
+More info in the manual 
+http://www.gramps-project.org/wiki/index.php?title=Gramps_4.0_Wiki_Manual_-_What%27s_new%3F
+
+Everybody is invited to update the manual to make it current!

TODO

@@ -1,76 +1 @@
-* Remove GCONF, provide up grade path - IN PROGRESS
-
-* Replace the LPRDoc interface (based on gnome-print) with a GTK based
-  print routine. This would remove one of the last gnome-specific 
-  libraries, and make portability better. Even more important, the 
-  gnome-print interface has been deprecated by the GNOME project, so it
-  will not be around forever. We need to adapt to the new GTK method. 
-  - IN PROGRESS
-
-* Add support for formatted notes. We have a start by ripping off code
-  from GPL code from grecipe-manager. - DONE
-
-* Allow for multiple notes. A tabbed interface would be really useful,
-  since there are no titles for notes. Not all objects would
-  necessarily need multiple notes. Determine which ones should and
-  shouldn't. - DONE
-
-* before release: fix command line options
-
-* remove critical bugs: 
-   - #1053 - DONE (testing of LDS privacy needed!!)
-   - #1318, wrong note backreferences - DONE
-   - #1208, relative path, see bug note for agreed solution
-
-* before release on multiple notes: 
-    --> in note: also public/private on GUI - DONE
-    --> on upgrade, the notetype should correspond to the object the note is made
-            from, so notetype SOURCE, SOURCEREF, ..., this gives information on 
-	    orphaned notes.(DONE for GRDB)
-	TODO: change notetype into note tags, so people can give notes multiple tags,
-	      Like this all source notes can have tag source, but also tag 'family history' (Discussion Alex/Benny)
-    --> in sourceref: 
-         * remove text tab. (DONE)
-         * On import of GEDCOM text tag, or upgrade of < 2.2 database, 
-           create a note with type TRANSCRIPT (DONE, type SOURCE_TEXT)
-         * On export, do not write the text tag in sourceref, write a
-           note instead (DONE)
-    --> A GrampsWidget for use in report dialogs to select which notetypes to include 
-        in a report (a filter?).
-    --> Support for multiple notes in all reports.
-    --> Empty text field on Saving Note should throw an error that Note is empty ! (?)
-    --> Undo in Note. Serious editing needs an undo function. Furthermore, the function
-        the Clear icon is unclear: tooltip? Other icon?
-
-* Remove import of global var in __init__.py, use functions or don't export. Eg.
-  PluginUtils/__init__.py export of plugin lists (tool_list, ...). E
-
-* Add forward/backward buttons (and active object) on all object views, not only person views.
-
-* Split views
-
-* Export to spreadsheet, print, CSV of views - DONE
-
-* Date calculator.  See
-  http://sourceforge.net/mailarchive/forum.php?thread_id=3252078&forum_id=1993
-
-* Add string substitutions for web page generation (name, report name,
-  date, etc).
-
-* Add support for sources of the parent/child relation
-
-* Add support for storing reliability (confidence) of the marriage
-  information; see
-  http://sourceforge.net/mailarchive/forum.php?thread_id=3066997&forum_id=1993
-  and
-  http://sourceforge.net/mailarchive/forum.php?thread_id=3134931&forum_id=1993
-  for the details.
-
-* Move LDS temple info out of const.py and into an XML file: DONE
-
-* Make the descendant graph adapt to the page size, not stuck with the
-  current 3 entries per page.
-
-* Add slideshow generation ability to web page generator
-
-* And a whole lot more....
+http://gramps-project.org/wiki/index.php?title=Category:GEPS

acinclude.m4

@@ -1,54 +0,0 @@
-dnl AM_SHARED_MIME
-dnl Defines SHARED_MIME_DIR which is where mime type definitions should go.
-dnl
-
-AC_DEFUN([AM_SHARED_MIME],
-[
-  if test "x$SHARED_MIME_DIR" = "x"; then
-    SHARED_MIME_DIR='$(prefix)/share/mime'
-  fi
-
-  AC_ARG_WITH(mime-dir,
-  [  --with-mime-dir=dir	Shared mime directory.],SHARED_MIME_DIR="$withval",)
-
-  AC_SUBST(SHARED_MIME_DIR)
-  AC_MSG_RESULT([Using directory $SHARED_MIME_DIR for installation of mime type definitions])
-
-  AC_ARG_ENABLE(mime-install,
-     [  --disable-mime-install	Disable the mime types installation],
-     [case "${enableval}" in
-       yes) mime_install=true ;;
-       no)  mime_install=false ;;
-       *) AC_MSG_ERROR(bad value ${enableval} for --disable-mime-install) ;;
-     esac],[mime_install=true])
-  AM_CONDITIONAL(SHARED_MIME_INSTALL, test x$mime_install = xtrue)
-
-])
-
-
-dnl AM_PACKAGER
-dnl Defines conditional PACKAGER_MODE to define packager mode
-dnl
-
-AC_DEFUN([AM_PACKAGER],
-[
-  AC_ARG_ENABLE(packager_mode,
-     [  --enable-packager-mode          Enable packager mode],
-     [case "${enableval}" in
-       yes) packager_mode=true ;;
-       no)  packager_mode=false ;;
-       *) AC_MSG_ERROR(bad value ${enableval} for --enable-packager-mode) ;;
-     esac],[packager_mode=false])
-  AM_CONDITIONAL(PACKAGER_MODE, test x$packager_mode = xtrue)
-  if test "x$packager_mode" = "xtrue"; then
-     AC_MSG_RESULT([WARNING: 
-     	Packager mode enabled.
-        Shared mime types WILL NOT BE INSTALLED.
-	You will need to place the contents of the
-		SHARED_MIME_INSTALLATION
-	commands MANUALLY into the postinstall script of your package,
-	see data/Makefile.am file for details.
-	Otherwise you will end up with the unusable package.
-	YOU HAVE BEEN WARNED!])
-  fi
-])

autogen.sh

@@ -1,102 +0,0 @@
-#!/bin/bash
-# Run this to generate all the initial makefiles, etc.
-# $Id$
-
-PKG_NAME="gramps"
-srcdir=`dirname $0`
-test -z "$srcdir" && srcdir=.
-srcfile=$srcdir/src/gramps.py
-
-REQUIRED_AUTOMAKE_VERSION=1.9
-DIE=0
-
-# source helper functions
-if test ! -f gramps-autogen.sh;
-then
-  echo There is something wrong with your source tree.
-  echo You are missing gramps-autogen.sh
-  exit 1
-fi
-. ./gramps-autogen.sh
-
-CONFIGURE_DEF_OPT=
-
-autogen_options $@
-
-#echo -n "+ check for build tools"
-#if test ! -z "$NOCHECK"; then echo ": skipped version checks"; else  echo; fi
-
-#tell Mandrake autoconf wrapper we want autoconf 2.5x, not 2.13
-WANT_AUTOCONF_2_5=1
-export WANT_AUTOCONF_2_5
-version_check autoconf AUTOCONF 'autoconf2.50 autoconf autoconf-2.53' $REQUIRED_AUTOCONF_VERSION \
-    "http://ftp.gnu.org/pub/gnu/autoconf/autoconf-$REQUIRED_AUTOCONF_VERSION.tar.gz" || DIE=1
-AUTOHEADER=`echo $AUTOCONF | sed s/autoconf/autoheader/`
-
-automake_progs="automake automake-1.10 automake-1.9"
-version_check automake AUTOMAKE "$automake_progs" $REQUIRED_AUTOMAKE_VERSION \
-    "http://ftp.gnu.org/pub/gnu/automake/automake-$REQUIRED_AUTOMAKE_VERSION.tar.gz" || DIE=1
-ACLOCAL=`echo $AUTOMAKE | sed s/automake/aclocal/`
-
-version_check glib-gettext GLIB_GETTEXTIZE glib-gettextize $REQUIRED_GLIB_GETTEXT_VERSION \
-    "ftp://ftp.gtk.org/pub/gtk/v2.2/glib-$REQUIRED_GLIB_GETTEXT_VERSION.tar.gz" || DIE=1
-require_m4macro glib-gettext.m4
-
-version_check intltool INTLTOOLIZE intltoolize $REQUIRED_INTLTOOL_VERSION \
-    "http://ftp.gnome.org/pub/GNOME/sources/intltool/" || DIE=1
-require_m4macro intltool.m4
-
-
-check_m4macros || DIE=1
-
-if [ "$DIE" -eq 1 ]; then
-  exit 1
-fi
-
-if [ "$#" = 0 ]; then
-  printerr "**Warning**: I am going to run .configure with no arguments."
-  printerr "If you wish to pass any to it, please specify them on the"
-  printerr "$0 command line."
-  printerr
-fi
-
-toplevel_check $srcfile
-
-# Note that the order these tools are called should match what
-# autoconf's "autoupdate" package does.  See bug 138584 for
-# details.
-
-# programs that might install new macros get run before aclocal
-
-printbold "Running $GLIB_GETTEXTIZE... Ignore non-fatal messages."
-echo "no" | $GLIB_GETTEXTIZE --force --copy || exit 1
-
-printbold "Running $INTLTOOLIZE..."
-$INTLTOOLIZE --force --copy --automake || exit 1
-
-# Now run aclocal to pull in any additional macros needed
-printbold "Running $ACLOCAL..."
-$ACLOCAL -I m4 $ACLOCAL_FLAGS || exit 1
-
-# Now that all the macros are sorted, run autoconf and autoheader ...
-printbold "Running $AUTOCONF..."
-$AUTOCONF || exit 1
-
-# Finally, run automake to create the makefiles ...
-printbold "Running $AUTOMAKE..."
-cp -pf COPYING COPYING.autogen_bak
-cp -pf INSTALL INSTALL.autogen_bak
-$AUTOMAKE --gnu --add-missing --force --copy || exit 1
-cmp COPYING COPYING.autogen_bak || cp -pf COPYING.autogen_bak COPYING
-cmp INSTALL INSTALL.autogen_bak || cp -pf INSTALL.autogen_bak INSTALL
-rm -f COPYING.autogen_bak INSTALL.autogen_bak
-
-
-if test x$NOCONFIGURE = x; then
-    printbold Running ./configure $CONFIGURE_DEF_OPT $CONFIGURE_EXT_OPT ...
-    ./configure $CONFIGURE_DEF_OPT $CONFIGURE_EXT_OPT \
-        && echo Now type \`make\' to compile $PKG_NAME || exit 1
-else
-    echo Skipping configure process.
-fi
-

bash/command-completion

@@ -0,0 +1,23 @@
+_gramps() 
+{
+    local cur prev opts
+    COMPREPLY=()
+    cur="${COMP_WORDS[COMP_CWORD]}"
+    prev="${COMP_WORDS[COMP_CWORD-1]}"
+    opts="--action --config --create --databases --debug --export --format --help  --import --open --options --quiet --remove --show --usage --version --yes -?  -C -L  -O -a -b -c -d -e -f -i -l  -p -q -r -s -t  -u -v -y"
+    if [[ ${cur} == -* ]] ; then
+        COMPREPLY=( $(compgen -W "${opts}" -- ${cur}) )
+        return 0
+    elif [[ ${cur} == --open ]] ; then
+        local IFS=$'\n'
+        local names=($( gramps -l | grep \" | cut -d\  -f4- ))
+        COMPREPLY=( $(compgen --W "${names[*]}" -- ${cur}) )
+        return 0
+    else 
+        local IFS=$'\n'
+        local names=($( gramps -l | grep \" | cut -d\  -f4- ))
+        COMPREPLY=( $(compgen -W "${names[*]}" -- ${cur}) )
+        return 0
+    fi
+}
+complete -F _gramps gramps

config.rpath

@@ -1,571 +0,0 @@
-#! /bin/sh
-# Output a system dependent set of variables, describing how to set the
-# run time search path of shared libraries in an executable.
-#
-#   Copyright 1996-2005 Free Software Foundation, Inc.
-#   Taken from GNU libtool, 2001
-#   Originally by Gordon Matzigkeit <gord@gnu.ai.mit.edu>, 1996
-#
-#   This file 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.
-#
-# The first argument passed to this file is the canonical host specification,
-#    CPU_TYPE-MANUFACTURER-OPERATING_SYSTEM
-# or
-#    CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM
-# The environment variables CC, GCC, LDFLAGS, LD, with_gnu_ld
-# should be set by the caller.
-#
-# The set of defined variables is at the end of this script.
-
-# Known limitations:
-# - On IRIX 6.5 with CC="cc", the run time search patch must not be longer
-#   than 256 bytes, otherwise the compiler driver will dump core. The only
-#   known workaround is to choose shorter directory names for the build
-#   directory and/or the installation directory.
-
-# All known linkers require a `.a' archive for static linking (except M$VC,
-# which needs '.lib').
-libext=a
-shrext=.so
-
-host="$1"
-host_cpu=`echo "$host" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\1/'`
-host_vendor=`echo "$host" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\2/'`
-host_os=`echo "$host" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\3/'`
-
-cc_basename=`echo "$CC" | sed -e 's%^.*/%%'`
-
-# Code taken from libtool.m4's AC_LIBTOOL_PROG_COMPILER_PIC.
-
-wl=
-if test "$GCC" = yes; then
-  wl='-Wl,'
-else
-  case "$host_os" in
-    aix*)
-      wl='-Wl,'
-      ;;
-    darwin*)
-      case "$cc_basename" in
-        xlc*)
-          wl='-Wl,'
-          ;;
-      esac
-      ;;
-    mingw* | pw32* | os2*)
-      ;;
-    hpux9* | hpux10* | hpux11*)
-      wl='-Wl,'
-      ;;
-    irix5* | irix6* | nonstopux*)
-      wl='-Wl,'
-      ;;
-    newsos6)
-      ;;
-    linux*)
-      case $cc_basename in
-        icc* | ecc*)
-          wl='-Wl,'
-          ;;
-        pgcc | pgf77 | pgf90)
-          wl='-Wl,'
-          ;;
-        ccc*)
-          wl='-Wl,'
-          ;;
-        como)
-          wl='-lopt='
-          ;;
-      esac
-      ;;
-    osf3* | osf4* | osf5*)
-      wl='-Wl,'
-      ;;
-    sco3.2v5*)
-      ;;
-    solaris*)
-      wl='-Wl,'
-      ;;
-    sunos4*)
-      wl='-Qoption ld '
-      ;;
-    sysv4 | sysv4.2uw2* | sysv4.3* | sysv5*)
-      wl='-Wl,'
-      ;;
-    sysv4*MP*)
-      ;;
-    unicos*)
-      wl='-Wl,'
-      ;;
-    uts4*)
-      ;;
-  esac
-fi
-
-# Code taken from libtool.m4's AC_LIBTOOL_PROG_LD_SHLIBS.
-
-hardcode_libdir_flag_spec=
-hardcode_libdir_separator=
-hardcode_direct=no
-hardcode_minus_L=no
-
-case "$host_os" in
-  cygwin* | mingw* | pw32*)
-    # FIXME: the MSVC++ port hasn't been tested in a loooong time
-    # When not using gcc, we currently assume that we are using
-    # Microsoft Visual C++.
-    if test "$GCC" != yes; then
-      with_gnu_ld=no
-    fi
-    ;;
-  openbsd*)
-    with_gnu_ld=no
-    ;;
-esac
-
-ld_shlibs=yes
-if test "$with_gnu_ld" = yes; then
-  case "$host_os" in
-    aix3* | aix4* | aix5*)
-      # On AIX/PPC, the GNU linker is very broken
-      if test "$host_cpu" != ia64; then
-        ld_shlibs=no
-      fi
-      ;;
-    amigaos*)
-      hardcode_libdir_flag_spec='-L$libdir'
-      hardcode_minus_L=yes
-      # Samuel A. Falvo II <kc5tja@dolphin.openprojects.net> reports
-      # that the semantics of dynamic libraries on AmigaOS, at least up
-      # to version 4, is to share data among multiple programs linked
-      # with the same dynamic library.  Since this doesn't match the
-      # behavior of shared libraries on other platforms, we cannot use
-      # them.
-      ld_shlibs=no
-      ;;
-    beos*)
-      if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then
-        :
-      else
-        ld_shlibs=no
-      fi
-      ;;
-    cygwin* | mingw* | pw32*)
-      # hardcode_libdir_flag_spec is actually meaningless, as there is
-      # no search path for DLLs.
-      hardcode_libdir_flag_spec='-L$libdir'
-      if $LD --help 2>&1 | grep 'auto-import' > /dev/null; then
-        :
-      else
-        ld_shlibs=no
-      fi
-      ;;
-    netbsd*)
-      ;;
-    solaris* | sysv5*)
-      if $LD -v 2>&1 | grep 'BFD 2\.8' > /dev/null; then
-        ld_shlibs=no
-      elif $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then
-        :
-      else
-        ld_shlibs=no
-      fi
-      ;;
-    sunos4*)
-      hardcode_direct=yes
-      ;;
-    linux*)
-      if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then
-        :
-      else
-        ld_shlibs=no
-      fi
-      ;;
-    *)
-      if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then
-        :
-      else
-        ld_shlibs=no
-      fi
-      ;;
-  esac
-  if test "$ld_shlibs" = yes; then
-    # Unlike libtool, we use -rpath here, not --rpath, since the documented
-    # option of GNU ld is called -rpath, not --rpath.
-    hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir'
-  fi
-else
-  case "$host_os" in
-    aix3*)
-      # Note: this linker hardcodes the directories in LIBPATH if there
-      # are no directories specified by -L.
-      hardcode_minus_L=yes
-      if test "$GCC" = yes; then
-        # Neither direct hardcoding nor static linking is supported with a
-        # broken collect2.
-        hardcode_direct=unsupported
-      fi
-      ;;
-    aix4* | aix5*)
-      if test "$host_cpu" = ia64; then
-        # On IA64, the linker does run time linking by default, so we don't
-        # have to do anything special.
-        aix_use_runtimelinking=no
-      else
-        aix_use_runtimelinking=no
-        # Test if we are trying to use run time linking or normal
-        # AIX style linking. If -brtl is somewhere in LDFLAGS, we
-        # need to do runtime linking.
-        case $host_os in aix4.[23]|aix4.[23].*|aix5*)
-          for ld_flag in $LDFLAGS; do
-            if (test $ld_flag = "-brtl" || test $ld_flag = "-Wl,-brtl"); then
-              aix_use_runtimelinking=yes
-              break
-            fi
-          done
-        esac
-      fi
-      hardcode_direct=yes
-      hardcode_libdir_separator=':'
-      if test "$GCC" = yes; then
-        case $host_os in aix4.[012]|aix4.[012].*)
-          collect2name=`${CC} -print-prog-name=collect2`
-          if test -f "$collect2name" && \
-            strings "$collect2name" | grep resolve_lib_name >/dev/null
-          then
-            # We have reworked collect2
-            hardcode_direct=yes
-          else
-            # We have old collect2
-            hardcode_direct=unsupported
-            hardcode_minus_L=yes
-            hardcode_libdir_flag_spec='-L$libdir'
-            hardcode_libdir_separator=
-          fi
-        esac
-      fi
-      # Begin _LT_AC_SYS_LIBPATH_AIX.
-      echo 'int main () { return 0; }' > conftest.c
-      ${CC} ${LDFLAGS} conftest.c -o conftest
-      aix_libpath=`dump -H conftest 2>/dev/null | sed -n -e '/Import File Strings/,/^$/ { /^0/ { s/^0  *\(.*\)$/\1/; p; }
-}'`
-      if test -z "$aix_libpath"; then
-        aix_libpath=`dump -HX64 conftest 2>/dev/null | sed -n -e '/Import File Strings/,/^$/ { /^0/ { s/^0  *\(.*\)$/\1/; p; }
-}'`
-      fi
-      if test -z "$aix_libpath"; then
-        aix_libpath="/usr/lib:/lib"
-      fi
-      rm -f conftest.c conftest
-      # End _LT_AC_SYS_LIBPATH_AIX.
-      if test "$aix_use_runtimelinking" = yes; then
-        hardcode_libdir_flag_spec='${wl}-blibpath:$libdir:'"$aix_libpath"
-      else
-        if test "$host_cpu" = ia64; then
-          hardcode_libdir_flag_spec='${wl}-R $libdir:/usr/lib:/lib'
-        else
-          hardcode_libdir_flag_spec='${wl}-blibpath:$libdir:'"$aix_libpath"
-        fi
-      fi
-      ;;
-    amigaos*)
-      hardcode_libdir_flag_spec='-L$libdir'
-      hardcode_minus_L=yes
-      # see comment about different semantics on the GNU ld section
-      ld_shlibs=no
-      ;;
-    bsdi[45]*)
-      ;;
-    cygwin* | mingw* | pw32*)
-      # When not using gcc, we currently assume that we are using
-      # Microsoft Visual C++.
-      # hardcode_libdir_flag_spec is actually meaningless, as there is
-      # no search path for DLLs.
-      hardcode_libdir_flag_spec=' '
-      libext=lib
-      ;;
-    darwin* | rhapsody*)
-      hardcode_direct=no
-      if test "$GCC" = yes ; then
-        :
-      else
-        case "$cc_basename" in
-          xlc*)
-            ;;
-          *)
-            ld_shlibs=no
-            ;;
-        esac
-      fi
-      ;;
-    dgux*)
-      hardcode_libdir_flag_spec='-L$libdir'
-      ;;
-    freebsd1*)
-      ld_shlibs=no
-      ;;
-    freebsd2.2*)
-      hardcode_libdir_flag_spec='-R$libdir'
-      hardcode_direct=yes
-      ;;
-    freebsd2*)
-      hardcode_direct=yes
-      hardcode_minus_L=yes
-      ;;
-    freebsd* | kfreebsd*-gnu | dragonfly*)
-      hardcode_libdir_flag_spec='-R$libdir'
-      hardcode_direct=yes
-      ;;
-    hpux9*)
-      hardcode_libdir_flag_spec='${wl}+b ${wl}$libdir'
-      hardcode_libdir_separator=:
-      hardcode_direct=yes
-      # hardcode_minus_L: Not really in the search PATH,
-      # but as the default location of the library.
-      hardcode_minus_L=yes
-      ;;
-    hpux10* | hpux11*)
-      if test "$with_gnu_ld" = no; then
-        case "$host_cpu" in
-          hppa*64*)
-            hardcode_libdir_flag_spec='${wl}+b ${wl}$libdir'
-            hardcode_libdir_separator=:
-            hardcode_direct=no
-            ;;
-          ia64*)
-            hardcode_libdir_flag_spec='-L$libdir'
-            hardcode_direct=no
-            # hardcode_minus_L: Not really in the search PATH,
-            # but as the default location of the library.
-            hardcode_minus_L=yes
-            ;;
-          *)
-            hardcode_libdir_flag_spec='${wl}+b ${wl}$libdir'
-            hardcode_libdir_separator=:
-            hardcode_direct=yes
-            # hardcode_minus_L: Not really in the search PATH,
-            # but as the default location of the library.
-            hardcode_minus_L=yes
-            ;;
-        esac
-      fi
-      ;;
-    irix5* | irix6* | nonstopux*)
-      hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir'
-      hardcode_libdir_separator=:
-      ;;
-    netbsd*)
-      hardcode_libdir_flag_spec='-R$libdir'
-      hardcode_direct=yes
-      ;;
-    newsos6)
-      hardcode_direct=yes
-      hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir'
-      hardcode_libdir_separator=:
-      ;;
-    openbsd*)
-      hardcode_direct=yes
-      if test -z "`echo __ELF__ | $CC -E - | grep __ELF__`" || test "$host_os-$host_cpu" = "openbsd2.8-powerpc"; then
-        hardcode_libdir_flag_spec='${wl}-rpath,$libdir'
-      else
-        case "$host_os" in
-          openbsd[01].* | openbsd2.[0-7] | openbsd2.[0-7].*)
-            hardcode_libdir_flag_spec='-R$libdir'
-            ;;
-          *)
-            hardcode_libdir_flag_spec='${wl}-rpath,$libdir'
-            ;;
-        esac
-      fi
-      ;;
-    os2*)
-      hardcode_libdir_flag_spec='-L$libdir'
-      hardcode_minus_L=yes
-      ;;
-    osf3*)
-      hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir'
-      hardcode_libdir_separator=:
-      ;;
-    osf4* | osf5*)
-      if test "$GCC" = yes; then
-        hardcode_libdir_flag_spec='${wl}-rpath ${wl}$libdir'
-      else
-        # Both cc and cxx compiler support -rpath directly
-        hardcode_libdir_flag_spec='-rpath $libdir'
-      fi
-      hardcode_libdir_separator=:
-      ;;
-    sco3.2v5*)
-      ;;
-    solaris*)
-      hardcode_libdir_flag_spec='-R$libdir'
-      ;;
-    sunos4*)
-      hardcode_libdir_flag_spec='-L$libdir'
-      hardcode_direct=yes
-      hardcode_minus_L=yes
-      ;;
-    sysv4)
-      case $host_vendor in
-        sni)
-          hardcode_direct=yes # is this really true???
-          ;;
-        siemens)
-          hardcode_direct=no
-          ;;
-        motorola)
-          hardcode_direct=no #Motorola manual says yes, but my tests say they lie
-          ;;
-      esac
-      ;;
-    sysv4.3*)
-      ;;
-    sysv4*MP*)
-      if test -d /usr/nec; then
-        ld_shlibs=yes
-      fi
-      ;;
-    sysv4.2uw2*)
-      hardcode_direct=yes
-      hardcode_minus_L=no
-      ;;
-    sysv5OpenUNIX8* | sysv5UnixWare7* |  sysv5uw[78]* | unixware7*)
-      ;;
-    sysv5*)
-      hardcode_libdir_flag_spec=
-      ;;
-    uts4*)
-      hardcode_libdir_flag_spec='-L$libdir'
-      ;;
-    *)
-      ld_shlibs=no
-      ;;
-  esac
-fi
-
-# Check dynamic linker characteristics
-# Code taken from libtool.m4's AC_LIBTOOL_SYS_DYNAMIC_LINKER.
-libname_spec='lib$name'
-case "$host_os" in
-  aix3*)
-    ;;
-  aix4* | aix5*)
-    ;;
-  amigaos*)
-    ;;
-  beos*)
-    ;;
-  bsdi[45]*)
-    ;;
-  cygwin* | mingw* | pw32*)
-    shrext=.dll
-    ;;
-  darwin* | rhapsody*)
-    shrext=.dylib
-    ;;
-  dgux*)
-    ;;
-  freebsd1*)
-    ;;
-  kfreebsd*-gnu)
-    ;;
-  freebsd*)
-    ;;
-  gnu*)
-    ;;
-  hpux9* | hpux10* | hpux11*)
-    case "$host_cpu" in
-      ia64*)
-        shrext=.so
-        ;;
-      hppa*64*)
-        shrext=.sl
-        ;;
-      *)
-        shrext=.sl
-        ;;
-    esac
-    ;;
-  irix5* | irix6* | nonstopux*)
-    case "$host_os" in
-      irix5* | nonstopux*)
-        libsuff= shlibsuff=
-        ;;
-      *)
-        case $LD in
-          *-32|*"-32 "|*-melf32bsmip|*"-melf32bsmip ") libsuff= shlibsuff= ;;
-          *-n32|*"-n32 "|*-melf32bmipn32|*"-melf32bmipn32 ") libsuff=32 shlibsuff=N32 ;;
-          *-64|*"-64 "|*-melf64bmip|*"-melf64bmip ") libsuff=64 shlibsuff=64 ;;
-          *) libsuff= shlibsuff= ;;
-        esac
-        ;;
-    esac
-    ;;
-  linux*oldld* | linux*aout* | linux*coff*)
-    ;;
-  linux*)
-    ;;
-  knetbsd*-gnu)
-    ;;
-  netbsd*)
-    ;;
-  newsos6)
-    ;;
-  nto-qnx*)
-    ;;
-  openbsd*)
-    ;;
-  os2*)
-    libname_spec='$name'
-    shrext=.dll
-    ;;
-  osf3* | osf4* | osf5*)
-    ;;
-  sco3.2v5*)
-    ;;
-  solaris*)
-    ;;
-  sunos4*)
-    ;;
-  sysv4 | sysv4.2uw2* | sysv4.3* | sysv5*)
-    ;;
-  sysv4*MP*)
-    ;;
-  uts4*)
-    ;;
-esac
-
-sed_quote_subst='s/\(["`$\\]\)/\\\1/g'
-escaped_wl=`echo "X$wl" | sed -e 's/^X//' -e "$sed_quote_subst"`
-shlibext=`echo "$shrext" | sed -e 's,^\.,,'`
-escaped_hardcode_libdir_flag_spec=`echo "X$hardcode_libdir_flag_spec" | sed -e 's/^X//' -e "$sed_quote_subst"`
-
-LC_ALL=C sed -e 's/^\([a-zA-Z0-9_]*\)=/acl_cv_\1=/' <<EOF
-
-# How to pass a linker flag through the compiler.
-wl="$escaped_wl"
-
-# Static library suffix (normally "a").
-libext="$libext"
-
-# Shared library suffix (normally "so").
-shlibext="$shlibext"
-
-# Flag to hardcode \$libdir into a binary during linking.
-# This must work even if \$libdir does not exist.
-hardcode_libdir_flag_spec="$escaped_hardcode_libdir_flag_spec"
-
-# Whether we need a single -rpath flag with a separated argument.
-hardcode_libdir_separator="$hardcode_libdir_separator"
-
-# Set to yes if using DIR/libNAME.so during linking hardcodes DIR into the
-# resulting binary.
-hardcode_direct="$hardcode_direct"
-
-# Set to yes if using the -LDIR flag during linking hardcodes DIR into the
-# resulting binary.
-hardcode_minus_L="$hardcode_minus_L"
-
-EOF

configure.in

@@ -1,175 +0,0 @@
-dnl $Id$
-
-dnl Process this file with autoconf to produce a configure script.
-dnl May need to run automake && aclocal first
-
-AC_PREREQ(2.57)
-dnl NOTE: arg to macro below becomes the "VERSION"
-AC_INIT(gramps, 3.4.0, [gramps-bugs@lists.sourceforge.net])
-AC_CONFIG_SRCDIR(configure.in)
-AM_INIT_AUTOMAKE([1.6.3 foreign])
-
-AC_CONFIG_MACRO_DIR([m4])
-
-RELEASE=0.SVN$(svnversion -n .)
-dnl RELEASE=0beta
-dnl RELEASE=0rc1
-dnl RELEASE=1
-
-VERSIONSTRING=$VERSION
-if test x"$RELEASE" != "x"
-then
-  VERSIONSTRING="$VERSION-$RELEASE"
-fi
-
-dnl put the ACLOCAL flags in the Makefile
-ACLOCAL="$ACLOCAL $ACLOCAL_FLAGS"
-
-AC_PROG_INTLTOOL
-
-AM_SHARED_MIME
-AM_PACKAGER
-AC_SUBST(RELEASE)
-AC_SUBST(VERSIONSTRING)
-
-dnl Add the languages which your application supports here.
-ALL_LINGUAS="hu zh_CN cs da de es fr it nb nl nn pl pt_BR pt_PT ru sv fi lt sk bg hr sl ca sq he uk ja vi"
-GETTEXT_PACKAGE=gramps
-AC_SUBST(GETTEXT_PACKAGE)
-AC_DEFINE_UNQUOTED(GETTEXT_PACKAGE,"$GETTEXT_PACKAGE", [Define to the Gettext package name.])
-AM_GLIB_GNU_GETTEXT
-
-dnl Checks for programs.  
-dnl We first only check for python >= 2.6
-
-AM_PATH_PYTHON(2.6)
-AC_PATH_PROG(BINSH, sh)
-
-pygtk_require="
-try:
-    import pygtk
-    pygtk.require('2.0')
-except ImportError:
-    pass
-
-def out(line):
-    f = open('conftest.out', 'w')
-    f.write(line)
-    f.close()
-"
-
-AC_MSG_CHECKING(Python bindings for gtk 2.10 (pygtk2>=2.10.0))
-cat > conftest.py <<EOF
-$pygtk_require
-try:
-    import gobject
-    version = gobject.pygtk_version
-    if version >= (2,10,0):
-        print_version = '.'.join([[str(i) for i in version]])
-        out(print_version)
-    else:
-        out("NO")
-except ImportError:
-    out("NO")
-except AttributeError:
-    out("NO")
-EOF
-$PYTHON conftest.py
-has_pygtk=`cat conftest.out`
-rm -f conftest.out conftest.py
-if test NO = "$has_pygtk"
-then
-   AC_MSG_ERROR([
-
-**** The python bindings for gtk 2.10 (pygtk2>=2.10.0) could not be found.])
-fi
-AC_MSG_RESULT($has_pygtk)
-
-AC_CONFIG_FILES([
-po/Makefile.in
-m4/Makefile
-Makefile
-gramps.sh
-src/const.py
-src/Makefile
-src/cli/Makefile
-src/cli/plug/Makefile
-src/gen/Makefile
-src/gen/db/Makefile
-src/gen/display/Makefile
-src/gen/lib/Makefile
-src/gen/mime/Makefile
-src/gen/plug/Makefile
-src/gen/plug/docbackend/Makefile
-src/gen/plug/docgen/Makefile
-src/gen/plug/menu/Makefile
-src/gen/plug/report/Makefile
-src/gen/proxy/Makefile
-src/gen/utils/Makefile
-src/gui/Makefile
-src/gui/editors/Makefile
-src/gui/editors/displaytabs/Makefile
-src/gui/plug/Makefile
-src/gui/plug/report/Makefile
-src/gui/selectors/Makefile
-src/gui/views/Makefile
-src/gui/views/treemodels/Makefile
-src/gui/widgets/Makefile
-src/GrampsLogger/Makefile
-src/Merge/Makefile
-src/docgen/Makefile
-src/Filters/Makefile
-src/Filters/Rules/Makefile
-src/Filters/Rules/Person/Makefile
-src/Filters/Rules/Family/Makefile
-src/Filters/Rules/Event/Makefile
-src/Filters/Rules/Source/Makefile
-src/Filters/Rules/Place/Makefile
-src/Filters/Rules/MediaObject/Makefile
-src/Filters/Rules/Repository/Makefile
-src/Filters/Rules/Note/Makefile
-src/Filters/Rules/Citation/Makefile
-src/Filters/SideBar/Makefile
-src/Simple/Makefile
-src/GrampsLocale/Makefile
-src/plugins/Makefile
-src/plugins/docgen/Makefile
-src/plugins/drawreport/Makefile
-src/plugins/export/Makefile
-src/plugins/gramplet/Makefile
-src/plugins/graph/Makefile
-src/plugins/import/Makefile
-src/plugins/lib/Makefile
-src/plugins/lib/maps/Makefile
-src/plugins/mapservices/Makefile
-src/plugins/quickview/Makefile
-src/plugins/rel/Makefile
-src/plugins/sidebar/Makefile
-src/plugins/textreport/Makefile
-src/plugins/tool/Makefile
-src/plugins/view/Makefile
-src/plugins/webreport/Makefile
-src/plugins/webstuff/Makefile
-src/plugins/webstuff/css/Makefile
-src/plugins/webstuff/images/Makefile
-src/plugins/webstuff/js/Makefile
-src/DateHandler/Makefile
-src/data/Makefile
-src/glade/Makefile
-src/images/Makefile
-src/images/scalable/Makefile
-src/images/16x16/Makefile
-src/images/22x22/Makefile
-src/images/48x48/Makefile
-data/Makefile
-data/man/Makefile
-data/man/cs/Makefile
-data/man/fr/Makefile
-data/man/nl/Makefile
-data/man/pl/Makefile
-data/man/sv/Makefile
-example/Makefile
-example/gramps/Makefile
-])
-
-AC_OUTPUT

data/Makefile.am

@@ -1,83 +0,0 @@
-# This is the data level Makefile for gramps
-# $Id$
-
-SUBDIRS = man
-
-# Rules for files with translatable strings
-# These are taken care of by the intltool
-desktopdir = $(datadir)/applications
-desktop_in_files = gramps.desktop.in
-desktop_DATA = $(desktop_in_files:.desktop.in=.desktop)
-@INTLTOOL_DESKTOP_RULE@
-
-keys_in_files = gramps.keys.in
-keys_files = $(keys_in_files:.keys.in=.keys)
-@INTLTOOL_KEYS_RULE@
-
-# Rules for files with translatable strings
-# These are taken care of by the intltool
-xml_in_files = gramps.xml.in
-xml_files = $(xml_in_files:.xml.in=.xml)
-@INTLTOOL_XML_RULE@
-
-applicationsdir = $(datadir)/application-registry
-applications_DATA = gramps.applications
-
-mimedir = $(datadir)/mime-info
-mime_DATA = $(keys_files) gramps.mime
-
-xmldir = $(SHARED_MIME_DIR)/packages
-xml_DATA = $(xml_files)
-
-pngdir = $(datadir)/icons/gnome/48x48/mimetypes
-png_DATA = \
-	gnome-mime-application-x-gramps.png \
-	gnome-mime-application-x-gedcom.png \
-	gnome-mime-application-x-gramps-package.png \
-	gnome-mime-application-x-gramps-xml.png \
-	gnome-mime-application-x-geneweb.png
-
-svgdir = $(datadir)/icons/gnome/scalable/mimetypes
-svg_DATA = \
-	gnome-mime-application-x-gramps.svg \
-	gnome-mime-application-x-gedcom.svg \
-	gnome-mime-application-x-gramps-package.svg \
-	gnome-mime-application-x-gramps-xml.svg \
-	gnome-mime-application-x-geneweb.svg
-
-EXTRA_DIST = \
-	$(png_DATA) \
-	$(svg_DATA) \
-	$(applications_DATA) \
-	$(keys_in_files) \
-	$(desktop_in_files) \
-	$(mime_DATA) \
-	$(xml_DATA) \
-	$(desktop_DATA) \
-	$(xml_in_files)
-
-CLEANFILES = \
-	$(desktop_DATA) \
-	$(keys_files) \
-	$(xml_files)
-
-# Conditionally enable/disable mime types,
-# or disable unconditionally if in a packager mode
-SHARED_MIME_INSTALLATION =
-SHARED_MIME_UNINSTALLATION =
-
-if !PACKAGER_MODE
-if SHARED_MIME_INSTALL
-SHARED_MIME_INSTALLATION += \
-	update-mime-database $(DESTDIR)$(SHARED_MIME_DIR)
-SHARED_MIME_UNINSTALLATION += \
-	update-mime-database $(DESTDIR)$(SHARED_MIME_DIR)
-endif
-endif
-
-
-install-data-hook:
-	$(SHARED_MIME_INSTALLATION)
-
-uninstall-hook:
-	$(SHARED_MIME_UNINSTALLATION)

data/authors.xml

@@ -0,0 +1,142 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- $Id$ -->
+<authors xmlns:html="http://www.w3.org/1999/xhtml">
+ <author title="author">
+  Alex Roitman &lt;<html:a href="mailto:shura@gramps-project.org">shura@gramps-project.org</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Arturas Sleinius &lt;<html:a href="mailto:asleinius@users.sourceforge.net">asleinius@users.sourceforge.net</html:a>&gt;
+ </author>
+ <author title="author">
+  Benny Malengier &lt;<html:a href="mailto:benny.malengier@gramps-project.org">benny.malengier@gramps-project.org</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Boril Gourinov &lt;<html:a href="mailto:boril.gourinov@gmail.com">boril.gourinov@gmail.com</html:a>&gt;
+ </author>
+ <author title="author">
+  Brian Matherly &lt;<html:a href="mailto:brian@gramps-project.org">brian@gramps-project.org</html:a>&gt;
+ </author>
+ <author title="author">
+  Don Allingham &lt;<html:a href="mailto:don@gramps-project.org">don@gramps-project.org</html:a>&gt;
+ </author>
+ <author title="author">
+  Donald A. Peterson &lt;<html:a href="mailto:"></html:a>&gt;
+ </author>
+ <author title="author">
+  Doug Blank &lt;<html:a href="mailto:doug.blank@gmail.com">doug.blank@gmail.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Eero Tamminen &lt;<html:a href="mailto:eerot@users.sourceforge.net">eerot@users.sourceforge.net</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Erik De Richter &lt;<html:a href="mailto:erikdrgm@users.sourceforge.net">erikdrgm@users.sourceforge.net</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Espen Berg &lt;<html:a href="mailto:espenbe@gmail.com">espenbe@gmail.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Gary Burton &lt;<html:a href="mailto:gary.burton@zen.co.uk">gary.burton@zen.co.uk</html:a>&gt;
+ </author>
+ <author uid="gbritton" title="contributor">
+  Gerald Britton &lt;<html:a href="mailto:gerald.britton@gmail.com">gerald.britton@gmail.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  James G Sack &lt;<html:a href="mailto:jgsack@san.rr.com">jgsack@san.rr.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Janne Kovesjärvi &lt;<html:a href="mailto:janne.kovesjarvi@gmail.com">janne.kovesjarvi@gmail.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Jason Simanek &lt;<html:a href="mailto:jsimanek@gmail.com">jsimanek@gmail.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Jérôme Rapinat &lt;<html:a href="mailto:romjerome@yahoo.fr">romjerome@yahoo.fr</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Joan Creus &lt;<html:a href="mailto:joan.creus@gmail.com">joan.creus@gmail.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Josip Pisoj &lt;<html:a href="mailto:josip@pisoj.com">josip@pisoj.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Julio Sánchez &lt;<html:a href="mailto:julio.sanchez@gmail.com">julio.sanchez@gmail.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Kees Bakker &lt;<html:a href="mailto:kees.bakker@xs4all.nl">kees.bakker@xs4all.nl</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Konstantin Dorichev &lt;<html:a href="mailto:kdorichev@gmail.com">kdorichev@gmail.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Lubo Vasko &lt;<html:a href="mailto:pgval@inMail.sk">pgval@inMail.sk</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Luigi Toscano &lt;<html:a href="mailto:luigi.toscano@tiscali.it">luigi.toscano@tiscali.it</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Luiz Gonzaga dos Santos Filho &lt;<html:a href="mailto:lfilho@gmail.com">lfilho@gmail.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Łukasz Rymarczyk &lt;<html:a href="mailto:yenidai@poczta.onet.pl">yenidai@poczta.onet.pl</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Michiel Nauta &lt;<html:a href="mailto:m.d.nauta@hetnet.nl">m.d.nauta@hetnet.nl</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Mirko Leonhäuser &lt;<html:a href="mailto:mirko@leonhaeuser.de">mirko@leonhaeuser.de</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Morten Bo Johansen &lt;<html:a href="mailto:mbj@spamcop.net">mbj@spamcop.net</html:a>&gt;
+ </author>
+ <author title="author">
+  Martin Hawlisch &lt;<html:a href="mailto:martin.hawlisch@gmx.de">martin.hawlisch@gmx.de</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Nick Hall &lt;<html:a href="mailto:nick__hall@hotmail.com">nick__hall@hotmail.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Peter Landgren &lt;<html:a href="mailto:peter.talken@telia.com">peter.talken@telia.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Raphael Ackermann &lt;<html:a href="mailto:raphael.ackermann@gmail.com">raphael.ackermann@gmail.com</html:a>&gt;
+ </author>
+ <author title="author">
+  Richard Taylor &lt;<html:a href="mailto:rjt-gramps@thegrindstone.me.uk">rjt-gramps@thegrindstone.me.uk</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Serge Noiraud &lt;<html:a href="mailto:Serge.Noiraud@free.fr">Serge.Noiraud@free.fr</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Sigmund Lorentsen &lt;<html:a href="mailto:sigmund.lorentsen@tele2.no">sigmund.lorentsen@tele2.no</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Stefan Bjork &lt;<html:a href="mailto:betula@users.sourceforge.net">betula@users.sourceforge.net</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Stéphane Charette &lt;<html:a href="mailto:stephanecharette@gmail.com">stephanecharette@gmail.com</html:a>&gt;
+ </author>
+ <author title="author">
+  Tim Waugh &lt;<html:a href="mailto:twaugh@redhat.com">twaugh@redhat.com</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Vassilii Khachaturov &lt;<html:a href="mailto:vassilii@tarunz.org">vassilii@tarunz.org</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Zdeněk Hataš &lt;<html:a href="mailto:zdenek.hatas@gmail.com">zdenek.hatas@gmail.com</html:a>&gt;
+ </author>
+<author title="author">
+  Rob G. Healey &lt;<html:a href="mailto:robhealey1@gmail.com">robhealey1@gmail.com</html:a>&gt;
+</author>
+ <author title="contributor">
+  Zsolt Foldvari &lt;<html:a href="mailto:zfoldvar@users.sourceforge.net">zfoldvar@users.sourceforge.net</html:a>&gt;
+ </author>
+ <author title="contributor">
+  Craig J. Anderson &lt;<html:a href="mailto:ander882@hotmail.com">ander882@hotmail.com</html:a>&gt;
+ </author>
+ <author title="author">
+  Tim G L Lyons &lt;<html:a href="mailto:tim.g.lyons@gmail.com">tim.g.lyons@gmail.com</html:a>&gt;
+ </author>
+ <author title="author">
+  John Ralls &lt;<html:a href="mailto:jralls@ceridwen.us">jralls@ceridwen.us</html:a>&gt;
+ </author>
+</authors>

data/css/GeoView.css

@@ -16,7 +16,7 @@
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 
 ----------------------------------------------------------------------------

data/css/Web_Basic-Ash.css

@@ -367,21 +367,6 @@ table.IndividualList td.ColumnSurname {
 div#SourceDetail {
     margin: 0 auto;
 }
-div#SourceCitationReferents ul.Col1 {
-    list-style-type: decimal
-}
-div#SourceCitationReferents ul.Col2 {
-    list-style-type: upper-alpha
-}
-div#SourceCitationReferents ul.Col3 {
-    list-style-type: lower-alpha
-}
-div#SourceCitationReferents ul.Col4 {
-    list-style-type: lower-roman
-}
-div#SourceCitationReferents ul.Col5 {
-    list-style-type: disc
-}
 
 /* Contact
 ----------------------------------------------------- */
@@ -482,7 +467,10 @@ h4 + div.grampsstylednote, a.familymap {
     margin: 1em 15px;
 }
 i + div.grampsstylednote p {
-    margin: 0px;
+    margin: 0 0 0.3em 0;
+}
+div.grampsstylednote p {
+    margin-bottom: 0.5em;
 }
 
 /* Subsection : Family Map

data/css/Web_Basic-Blue.css

@@ -16,7 +16,7 @@
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 # $Id: Web_Basic-Blue.css 15540 2010-06-07 16:32:00Z robhealey1 $
 #
@@ -169,7 +169,7 @@ a {
 }
 a:hover {
     background-color: #BCEAF6;
-    text-decoration: blink;
+    text-decoration: underline;
 }
 span.preposition {
     padding-left:1em;
@@ -770,26 +770,11 @@ div#Download table.download td.ColumnModified {
     padding: 0;
 }
 div#SourceDetail {
-    min-height: 1200px
+    min-height: 900px
 }
 div#SourceDetail div#references ol li {
     padding-bottom: .5em;
 }
-div#SourceCitationReferents ol.Col1 {
-    list-style-type: upper-roman
-}
-div#SourceCitationReferents ol.Col2 {
-    list-style-type: upper-alpha
-}
-div#SourceCitationReferents ol.Col3 {
-    list-style-type: lower-alpha
-}
-div#SourceCitationReferents ol.Col4 {
-    list-style-type: upper-roman
-}
-div#SourceCitationReferents ol.Col5 {
-    list-style-type: square
-}
 
 /* Repositories
 ------------------------------------------------------ */
@@ -1270,6 +1255,9 @@ div#pedigree {
 
 /* Calendar Styles
 -------------------------------------------------------------------------------------------- */
+#OneDay, #WebCal, #YearGlance {
+    width: 95%
+}
 /* Calendar : General */
 .calendar {
     empty-cells:show;

data/css/Web_Basic-Cypress.css

@@ -248,6 +248,14 @@ table.primobjlist tr.BeginLetter td, table.primobjlist tr.BeginSurname td {
 td.ColumnLetter, td.ColumnRowLabel {
     font-weight: bold;
 }
+/* bug #8213 testing by Stephane, 2014-12-6 */
+td.ColumnEvent, td.ColumnDate {
+    white-space: nowrap;
+}
+td.ColumnPlace, td.ColumnDescription {
+    width: 20%
+}
+/* end of customizations by Stephane */
 td.ColumnBirth, td.ColumnDeath, td.ColumnPartner, td.ColumnParents {
     font-size: 90%;
 }
@@ -405,21 +413,6 @@ table.IndividualList td.ColumnSurname {
 div#SourceDetail {
     margin: 0 auto;
 }
-div#SourceCitationReferents ul.Col1 {
-    list-style-type: decimal
-}
-div#SourceCitationReferents ul.Col2 {
-    list-style-type: upper-alpha
-}
-div#SourceCitationReferents ul.Col3 {
-    list-style-type: lower-alpha
-}
-div#SourceCitationReferents ul.Col4 {
-    list-style-type: upper-roman
-}
-div#SourceCitationReferents ul.Col5 {
-    list-style-type: disc
-}
 
 /* Contact
 ----------------------------------------------------- */
@@ -524,7 +517,10 @@ h4 + div.grampsstylednote, a.familymap {
     margin: 1em 15px;
 }
 i + div.grampsstylednote p {
-    margin: 0px;
+    margin: 0 0 0.3em 0;
+}
+div.grampsstylednote p {
+    margin-bottom: 0.5em;
 }
 
 /* Subsection : Family Map

data/css/Web_Basic-Lilac.css

@@ -406,21 +406,6 @@ table.IndividualList td.ColumnSurname {
 div#SourceDetail {
     margin: 0 auto;
 }
-div#SourceCitationReferents ul.Col1 {
-    list-style-type: decimal
-}
-div#SourceCitationReferents ul.Col2 {
-    list-style-type: upper-alpha
-}
-div#SourceCitationReferents ul.Col3 {
-    list-style-type: lower-alpha
-}
-div#SourceCitationReferents ul.Col4 {
-    list-style-type: upper-roman
-}
-div#SourceCitationReferents ul.Col5 {
-    list-style-type: disc
-}
 
 /* Contact
 ----------------------------------------------------- */
@@ -525,7 +510,10 @@ h4 + div.grampsstylednote, a.familymap {
     margin: 1em 15px;
 }
 i + div.grampsstylednote p {
-    margin: 0px;
+    margin: 0 0 0.3em 0;
+}
+div.grampsstylednote p {
+    margin-bottom: 0.5em;
 }
 
 /* Subsection : Family Map

data/css/Web_Basic-Peach.css

@@ -406,21 +406,6 @@ table.IndividualList td.ColumnSurname {
 div#SourceDetail {
     margin: 0 auto;
 }
-div#SourceCitationReferents ul.Col1 {
-    list-style-type: decimal
-}
-div#SourceCitationReferents ul.Col2 {
-    list-style-type: upper-alpha
-}
-div#SourceCitationReferents ul.Col3 {
-    list-style-type: lower-alpha
-}
-div#SourceCitationReferents ul.Col4 {
-    list-style-type: upper-roman
-}
-div#SourceCitationReferents ul.Col5 {
-    list-style-type: disc
-}
 
 /* Contact
 ----------------------------------------------------- */
@@ -525,7 +510,10 @@ h4 + div.grampsstylednote, a.familymap {
     margin: 1em 15px;
 }
 i + div.grampsstylednote p {
-    margin: 0px;
+    margin: 0 0 0.3em 0;
+}
+div.grampsstylednote p {
+    margin-bottom: 0.5em;
 }
 
 /* Subsection : Family Map

data/css/Web_Basic-Spruce.css

@@ -406,21 +406,6 @@ table.IndividualList td.ColumnSurname {
 div#SourceDetail {
     margin: 0 auto;
 }
-div#SourceCitationReferents ul.Col1 {
-    list-style-type: decimal
-}
-div#SourceCitationReferents ul.Col2 {
-    list-style-type: upper-alpha
-}
-div#SourceCitationReferents ul.Col3 {
-    list-style-type: lower-alpha
-}
-div#SourceCitationReferents ul.Col4 {
-    list-style-type: upper-roman
-}
-div#SourceCitationReferents ul.Col5 {
-    list-style-type: disc
-}
 
 /* Contact
 ----------------------------------------------------- */
@@ -525,7 +510,10 @@ h4 + div.grampsstylednote, a.familymap {
     margin: 1em 15px;
 }
 i + div.grampsstylednote p {
-    margin: 0px;
+    margin: 0 0 0.3em 0;
+}
+div.grampsstylednote p {
+    margin-bottom: 0.5em;
 }
 
 /* Subsection : Family Map

data/css/Web_Citations-Animated.css

@@ -0,0 +1,183 @@
+/*    Main Element
+------------------------------------------------------ */
+#menu, #menu ul {
+    margin: 0;
+    padding: 0;
+    list-style-type: none;
+}
+
+/*    Main Level
+------------------------------------------------------ */
+#menu {
+    width: 100%;
+    margin: 6px auto;
+    border: 1px solid #222;
+    background-color: #111;
+    background-image: -moz-linear-gradient(#444, #111);
+    background-image: -webkit-gradient(linear, left top, left bottom, from(#444), to(#111));
+    background-image: -webkit-linear-gradient(#444, #111);
+    background-image: -o-linear-gradient(#444, #111);
+    background-image: -ms-linear-gradient(#444, #111);
+    background-image: linear-gradient(#444, #111);
+    -moz-border-radius: 6px;
+    -webkit-border-radius: 6px;
+    border-radius: 6px;
+    -moz-box-shadow: 0 1px 1px #777;
+    -webkit-box-shadow: 0 1px 1px #777;
+    box-shadow: 0 1px 1px #777;
+}
+
+/*    Clear Floats
+------------------------------------------------------ */
+#menu:before,
+#menu:after {
+    content: "";
+    display: table;
+}
+#menu:after {
+    clear: both
+}
+#menu {
+    zoom: 1
+}
+
+/*    List Elements
+------------------------------------------------------ */
+#menu li {
+    float: left;
+    border-right: 1px solid #222;
+    -moz-box-shadow: 1px 0 0 #444;
+    -webkit-box-shadow: 1px 0 0 #444;
+    box-shadow: 1px 0 0 #444;
+    position: relative;
+}
+#menu a {
+    float: left;
+    padding: 12px 30px;
+    color: #999;
+    text-transform: uppercase;
+    font: bold 12px Arial, Helvetica;
+    text-decoration: none;
+    text-shadow: 0 1px 0 #000;
+}
+#menu li:hover > a {
+    color: #fafafa
+}
+*html #menu li a:hover { /* IE6 only */
+    color: #fafafa
+}
+
+/*    sub-menu
+------------------------------------------------------ */
+#menu ul {
+    margin: 20px 0 0 0;
+    _margin: 0; /*IE6 only*/
+    opacity: 0;
+    visibility: hidden;
+    position: absolute;
+    top: 38px;
+    left: 0;
+    z-index: 9999;
+    background: #444;
+    background: -moz-linear-gradient(#444, #111);
+    background: -webkit-gradient(linear,left bottom,left top,color-stop(0, #111),color-stop(1, #444));
+    background: -webkit-linear-gradient(#444, #111);
+    background: -o-linear-gradient(#444, #111);
+    background: -ms-linear-gradient(#444, #111);
+    background: linear-gradient(#444, #111);
+    -moz-box-shadow: 0 -1px rgba(255,255,255,.3);
+    -webkit-box-shadow: 0 -1px 0 rgba(255,255,255,.3);
+    box-shadow: 0 -1px 0 rgba(255,255,255,.3);
+    -moz-border-radius: 3px;
+    -webkit-border-radius: 3px;
+    border-radius: 3px;
+    -webkit-transition: all .2s ease-in-out;
+    -moz-transition: all .2s ease-in-out;
+    -ms-transition: all .2s ease-in-out;
+    -o-transition: all .2s ease-in-out;
+    transition: all .2s ease-in-out;
+}
+#menu li:hover > ul {
+    opacity: 1;
+    visibility: visible;
+    margin: 0;
+}
+#menu ul ul {
+    top: 0;
+    left: 150px;
+    margin: 0 0 0 20px;
+    _margin: 0; /*IE6 only*/
+    -moz-box-shadow: -1px 0 0 rgba(255,255,255,.3);
+    -webkit-box-shadow: -1px 0 0 rgba(255,255,255,.3);
+    box-shadow: -1px 0 0 rgba(255,255,255,.3);
+}
+#menu ul li {
+    float: none;
+    display: block;
+    border: 0;
+    _line-height: 0; /*IE6 only*/
+    -moz-box-shadow: 0 1px 0 #111, 0 2px 0 #666;
+    -webkit-box-shadow: 0 1px 0 #111, 0 2px 0 #666;
+    box-shadow: 0 1px 0 #111, 0 2px 0 #666;
+}
+#menu ul li:last-child {
+    -moz-box-shadow: none;
+    -webkit-box-shadow: none;
+    box-shadow: none;
+}
+#menu ul a {
+    padding: 10px;
+    width: 130px;
+    _height: 10px; /*IE6 only*/
+    display: block;
+    white-space: nowrap;
+    float: none;
+    text-transform: none;
+}
+#menu ul a:hover {
+    background-color: #0186ba;
+    background-image: -moz-linear-gradient(#04acec,  #0186ba);
+    background-image: -webkit-gradient(linear, left top, left bottom, from(#04acec), to(#0186ba));
+    background-image: -webkit-linear-gradient(#04acec, #0186ba);
+    background-image: -o-linear-gradient(#04acec, #0186ba);
+    background-image: -ms-linear-gradient(#04acec, #0186ba);
+    background-image: linear-gradient(#04acec, #0186ba);
+}
+
+/* first and Last child elements
+------------------------------------------------------ */
+#menu ul li:first-child > a {
+    -moz-border-radius: 3px 3px 0 0;
+    -webkit-border-radius: 3px 3px 0 0;
+    border-radius: 3px 3px 0 0;
+}
+#menu ul li:first-child > a:after {
+    content: '';
+    position: absolute;
+    left: 40px;
+    top: -6px;
+    border-left: 6px solid transparent;
+    border-right: 6px solid transparent;
+    border-bottom: 6px solid #444;
+}
+#menu ul ul li:first-child a:after {
+    left: -6px;
+    top: 50%;
+    margin-top: -6px;
+    border-left: 0;
+    border-bottom: 6px solid transparent;
+    border-top: 6px solid transparent;
+    border-right: 6px solid #3b3b3b;
+}
+#menu ul li:first-child a:hover:after {
+    border-bottom-color: #04acec
+}
+#menu ul ul li:first-child a:hover:after {
+    border-right-color: #0299d3;
+    border-bottom-color: transparent;
+}
+#menu ul li:last-child > a {
+    -moz-border-radius: 0 0 3px 3px;
+    -webkit-border-radius: 0 0 3px 3px;
+    border-radius: 0 0 3px 3px;
+}

data/css/Web_Citations-Outline.css

@@ -0,0 +1,46 @@
+/*
+# encoding: utf-8
+#
+# Gramps - a GTK+/GNOME based genealogy program
+#
+# Copyright 2012 Rob G. Healey <robhealey1@gmail.com>
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful, 
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+#
+
+******************************************************
+GRAMPS Cascading Style Sheet
+Style Name: Web_Citations-Outline.css
+******************************************************
+
+# $Id$
+
+    Source Citations Outline styles
+------------------------------------------------------ */
+div#SourceCitationReferents ul.Col1 {
+    list-style-type: decimal
+}
+div#SourceCitationReferents ul.Col2 {
+    list-style-type: upper-alpha
+}
+div#SourceCitationReferents ul.Col3 {
+    list-style-type: lower-alpha
+}
+div#SourceCitationReferents ul.Col4 {
+    list-style-type: upper-roman
+}
+div#SourceCitationReferents ul.Col5 {
+    list-style-type: disc
+}

data/css/Web_DropDown-Menus.css

@@ -16,7 +16,7 @@
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 # $Id$
 #
@@ -41,7 +41,7 @@ div#header {
 
 /*     Drop Down Navigation Menu
 ------------------------------------------------------ */
-#dropmenu {
+ul#dropmenu {
     width: 100%;
     margin: 0 auto;
     padding: 10px 0 0 0;
@@ -59,12 +59,12 @@ div#header {
     -webkit-box-shadow: 0 2px 1px #9c9c9c;
     box-shadow: 0 2px 1px #9c9c9c;
 }
-#dropmenu li {
+ul#dropmenu li {
     float: left;
     padding: 0 0 10px 0;
     position: relative;
 }
-#dropmenu a {
+ul#dropmenu a {
     float: left;
     height: 25px;
     padding: 0 25px;
@@ -74,21 +74,21 @@ div#header {
     text-decoration: none;
     text-shadow: 0 1px 0 #000;
 }
-#dropmenu li:hover > a {
+ul#dropmenu li:hover > a {
     color: #fafafa
 }
 
-*html #dropmenu li a:hover /* IE6 */
+*html ul#dropmenu li a:hover /* IE6 */
 {
     color: #fafafa
 }
-#dropmenu li:hover > ul {
+ul#dropmenu li:hover > ul {
     display: block
 }
 
 /*     Sub-menu
 ------------------------------------------------------ */
-#dropmenu ul {
+ul#dropmenu ul {
     list-style: none;
     margin: 0;
     padding: 0;
@@ -107,7 +107,7 @@ div#header {
     -moz-border-radius: 5px;
     border-radius: 5px;
 }
-#dropmenu ul li {
+ul#dropmenu ul li {
     float: none;
     margin: 0;
     padding: 0;
@@ -116,12 +116,12 @@ div#header {
     -webkit-box-shadow: 0 1px 0 #111111, 0 2px 0 #777777;
     box-shadow: 0 1px 0 #111111, 0 2px 0 #777777;
 }
-#dropmenu ul li:last-child {
+ul#dropmenu ul li:last-child {
     -moz-box-shadow: none;
     -webkit-box-shadow: none;
     box-shadow: none;
 }
-#dropmenu ul a {
+ul#dropmenu ul a {
     padding: 10px;
     height: auto;
     line-height: 1;
@@ -130,17 +130,17 @@ div#header {
     float: none;
     text-transform: none;
 }
-*html #dropmenu ul a /* IE6 */
+*html ul#dropmenu ul a /* IE6 */
 {
     height: 10px;
     width: 150px;
 }
-*:first-child+html #dropmenu ul a /* IE7 */
+*:first-child+html ul#dropmenu ul a /* IE7 */
 {
     height: 10px;
     width: 150px;
 }
-#dropmenu ul a:hover {
+ul#dropmenu ul a:hover {
     background: #0186ba;
     background: -moz-linear-gradient(#04acec,  #0186ba);
     background: -webkit-gradient(linear, left top, left bottom, from(#04acec), to(#0186ba));
@@ -149,11 +149,11 @@ div#header {
     background: -ms-linear-gradient(#04acec,  #0186ba);
     background: linear-gradient(#04acec,  #0186ba);
 }
-#dropmenu ul li:first-child a {
+ul#dropmenu ul li:first-child a {
     -moz-border-radius: 5px 5px 0 0;
     border-radius: 5px 5px 0 0;
 }
-#dropmenu ul li:first-child a:after {
+ul#dropmenu ul li:first-child a:after {
     content: '';
     position: absolute;
     left: 30px;
@@ -164,17 +164,17 @@ div#header {
     border-right: 5px solid transparent;
     border-bottom: 8px solid #444;
 }
-#dropmenu ul li:first-child a:hover:after {
+ul#dropmenu ul li:first-child a:hover:after {
     border-bottom-color: #04acec
 }
-#dropmenu ul li:last-child a {
+ul#dropmenu ul li:last-child a {
     -moz-border-radius: 0 0 5px 5px;
     border-radius: 0 0 5px 5px;
 }
 
 /*     Clear floated elements
 ------------------------------------------------------ */
-#dropmenu:after {
+ul#dropmenu:after {
     visibility: hidden;
     display: block;
     font-size: 0;
@@ -183,8 +183,8 @@ div#header {
     height: 0;
 }
 
-* html #dropmenu             { zoom: 1; } /* IE6 */
-*:first-child+html #dropmenu { zoom: 1; } /* IE7 */
+* html ul#dropmenu             { zoom: 1; } /* IE6 */
+*:first-child+html ul#dropmenu { zoom: 1; } /* IE7 */
 
 /*    Alphabet Navigation and Year Menu
 ------------------------------------------------------ */

data/css/Web_Fade-Menus.css

@@ -16,7 +16,7 @@
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 # $Id$
 #

data/css/Web_Horizontal-Menus.css

@@ -17,7 +17,7 @@
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 
 ******************************************************

data/css/Web_Mainz.css

@@ -358,21 +358,6 @@ table#SortByCount thead th.ColumnQuantity a:after {
 div#SourceDetail {
     margin: 0 auto;
 }
-div#SourceCitationReferents ul.Col1 {
-    list-style-type: decimal
-}
-div#SourceCitationReferents ul.Col2 {
-    list-style-type: upper-alpha
-}
-div#SourceCitationReferents ul.Col3 {
-    list-style-type: lower-alpha
-}
-div#SourceCitationReferents ul.Col4 {
-    list-style-type: upper-roman
-}
-div#SourceCitationReferents ul.Col5 {
-    list-style-type: disc
-}
 
 /* Contact
 -----------------------------------------------------------------*/
@@ -463,7 +448,10 @@ h4 + div.grampsstylednote, a.familymap {
     margin-right: 10px;
 }
 i + div.grampsstylednote p {
-    margin: 0px;
+    margin: 0 0 0.3em 0;
+}
+div.grampsstylednote p {
+    margin-bottom: 0.5em;
 }
 
 /* SubSection : Source References

data/css/Web_Nebraska.css

@@ -508,21 +508,6 @@ table.attrlist tbody tr td.ColumnSources {
 div#SourceDetail {
     margin: 0 auto;
 }
-div#SourceCitationReferents ul.Col1 {
-    list-style-type: decimal
-}
-div#SourceCitationReferents ul.Col2 {
-    list-style-type: upper-alpha
-}
-div#SourceCitationReferents ul.Col3 {
-    list-style-type: lower-alpha
-}
-div#SourceCitationReferents ul.Col4 {
-    list-style-type: upper-roman
-}
-div#SourceCitationReferents ul.Col5 {
-    list-style-type: disc
-}
 
 /*    Relationships
 ================================================= */

data/css/Web_Vertical-Menus.css

@@ -17,7 +17,7 @@
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 
 **************************************************************************************************

data/css/Web_Visually.css

@@ -17,7 +17,7 @@
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 
 **************************************************************************************************

data/css/ancestortree.css

@@ -16,7 +16,7 @@
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 # $Id: $
 #

data/css/behaviour.css

@@ -16,7 +16,7 @@
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 
 **************************************************************************************************

data/css/jquery.flexbox.css

@@ -0,0 +1,83 @@
+/* Input textbox - do not specify a width here, it will be overwritten */
+.ffb-input 
+{
+	float:left;
+	color:#000; /* must specify along with watermark color */
+	height:16px; /* required for webkit browsers (Safari, Chrome) */
+}
+/* Color of watermark, if present */
+.ffb-input.watermark { /* added and removed dynamically */
+	color:#888; /* must specify along with input color */
+}
+/* Drop-down arrow, with sprited image */
+.ffb-arrow 
+{
+	float:left;
+	width:17px;
+	height:22px;
+	background-image:url(../img/sel_win7.gif);
+}
+.ffb-arrow.out { /* css sprite technique */
+	background-position:0;
+}
+.ffb-arrow.over { /* css sprite technique */
+	background-position:-17px 0;
+}
+.ffb-arrow.active { /* css sprite technique */
+	background-position:-34px 0;
+}
+.ffb-no-results 
+{
+	padding:2px;
+	color:#888;
+	font-style:italic;
+	border-bottom:1px solid #828790;
+}
+/* Container for dropdown contents */
+.ffb {
+	position:absolute; /* this guy's parent div is hard-coded to position:relative */
+	overflow:hidden;
+	border-left:1px solid #828790; /* #7B9EBD for Vista */
+	border-right:1px solid #828790;
+	background-color:#fff; /* Give it a background-color, so it's not transparent */
+}
+/* Inner div for dropdown */
+.ffb .content {
+	overflow:auto;
+}
+.ffb .content .row {
+	border-bottom:1px solid #828790;
+	color:#000;
+	height:20px;
+	clear:both;
+}
+.ffb-sel {
+	cursor:pointer;
+	cursor:hand;
+	color:#fff !important;
+	background-color:#39f;
+}
+.ffb-match {
+	font-weight:bold;
+	color:#000;
+}
+
+/* Paging */
+.ffb .paging {
+	vertical-align:middle;
+	border-bottom:1px solid #828790;
+}
+.ffb .page, .ffb a.page {
+	font-size:85%;
+	padding:2px;
+	border:solid 1px #339;
+	background-color:#eef;
+	margin:2px;
+}
+.ffb .box {
+	width:22px;
+	margin:2px;
+}
+.ffb .summary {
+	font-size:85%;
+}

data/css/narrative-maps.css

@@ -16,7 +16,7 @@
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 # $Id$
 #

data/gramps.appdata.xml.in

@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<component type="desktop">
+  <id>gramps.desktop</id>
+  <metadata_license>CC0</metadata_license>
+  <name>Gramps</name>
+  <summary>Genealogical research program</summary>
+
+  <description>
+    <_p>Gramps is a genealogy program that is both intuitive for hobbyists and feature-complete for professional genealogists.</_p>
+    <_p>It gives you the ability to record the many details of the life of an individual as well as the complex relationships between various people, places and events.</_p>
+    <_p>All of your research is kept organized, searchable and as precise as you need it to be.</_p>
+  </description>
+
+  <url type="homepage">https://gramps-project.org/</url>
+  <url type="bugtracker">https://gramps-project.org/bugs/</url>
+  <url type="help">https://gramps-project.org/wiki/index.php?title=Main_page</url>
+  <project_license>GPL-2.0+</project_license>
+  <developer_name>Gramps Development Team</developer_name>
+
+  <screenshots>
+    <screenshot width="1226" height="740">http://www.gramps-project.org/wiki/images/5/5f/AppData1.png</screenshot>
+    <screenshot width="1226" height="740">http://www.gramps-project.org/wiki/images/6/68/AppData2.png</screenshot>
+    <screenshot type="default" width="1226" height="740">http://www.gramps-project.org/wiki/images/e/e9/AppData3.png</screenshot>
+    <screenshot width="1226" height="740">http://www.gramps-project.org/wiki/images/6/68/AppData4.png</screenshot>
+    <screenshot width="1226" height="740">http://www.gramps-project.org/wiki/images/5/50/AppData5.png</screenshot>
+  </screenshots>
+
+  <provides>
+    <binary>gramps</binary>
+  </provides>
+
+</component>

data/gramps.desktop.in

@@ -1,11 +1,13 @@
 [Desktop Entry]
-_Name=Gramps Genealogy System
+_Name=Gramps
+_GenericName=Genealogy System
+_X-GNOME-FullName=Gramps Genealogy System
 _Comment=Manage genealogical information, perform genealogical research and analysis
 Icon=gramps
 Terminal=false
 Type=Application
 StartupNotify=true
 Categories=GTK;Office;
-X-GNOME-DocPath=gramps/gramps-manual.xml
+_Keywords=Genealogy;Family History;Research;Family Tree;GEDCOM;
 MimeType=application/x-gramps;application/x-gedcom;application/x-gramps-package;application/x-gramps-xml;
 Exec=gramps %F

data/gramps_canonicalize.xsl

@@ -16,7 +16,7 @@
 
  You should have received a copy of the GNU General Public License
  along with this program; if not, write to the Free Software
- Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 
 
  $Id$

data/grampsxml.dtd

@@ -5,7 +5,7 @@
 #
 # Copyright (C) 2001       Graham J. Williams
 # Copyright (C) 2000-2007  Donald N. Allingham
-# Copyright (C) 2010-2011  Nick Hall
+# Copyright (C) 2010-2014  Nick Hall
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -19,21 +19,21 @@
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 
 # $Id$
 -->
 
 <!--
-    This is the Document Type Definition file for v1.5.0
+    This is the Document Type Definition file for v1.7.1
     of the GRAMPS XML genealogy data format.
     Please use the following formal public identifier to identify it:
 
-    "-//GRAMPS//DTD GRAMPS XML V1.5.0//EN"
+    "-//GRAMPS//DTD GRAMPS XML V1.7.1//EN"
 
     For example:
-        <!DOCTYPE database PUBLIC "-//GRAMPS//DTD GRAMPS XML V1.5.0//EN"
-                "http://gramps-project.org/xml/1.5.0/grampsxml.dtd"
+        <!DOCTYPE database PUBLIC "-//GRAMPS//DTD GRAMPS XML V1.7.1//EN"
+                "http://gramps-project.org/xml/1.7.1/grampsxml.dtd"
                 [...]>
 -->
 
@@ -62,7 +62,7 @@ DATABASE
 <!ELEMENT database (header, name-formats?, tags?, events?, people?, families?,
                     citations?, sources?, places?, objects?, repositories?,
                     notes?, bookmarks?, namemaps?)>
-<!ATTLIST database xmlns CDATA #FIXED "http://gramps-project.org/xml/1.5.0/">
+<!ATTLIST database xmlns CDATA #FIXED "http://gramps-project.org/xml/1.7.1/">
 
 
 <!--    ************************************************************
@@ -122,6 +122,7 @@ GENDER has values of M, F, or U.
 
 <!ELEMENT name    (first?, call?, surname*, suffix?, title?, nick?, familynick?, group?,
                   (daterange|datespan|dateval|datestr)?, noteref*, citationref*)>
+<!-- (Unknown|Also Know As|Birth Name|Married Name|Other Name) -->
 <!ATTLIST name    
         alt       (0|1) #IMPLIED
         type      CDATA #IMPLIED
@@ -138,6 +139,8 @@ GENDER has values of M, F, or U.
 <!ELEMENT familynick (#PCDATA)>
 <!ELEMENT group      (#PCDATA)>
 <!ELEMENT surname    (#PCDATA)>
+<!-- (Unknown|Inherited|Given|Taken|Patronymic|Matronymic|Feudal|
+Pseudonym|Patrilineal|Matrilineal|Occupation|Location) -->
 <!ATTLIST surname
         prefix      CDATA #IMPLIED
         prim        (1|0) #IMPLIED
@@ -196,12 +199,13 @@ FAMILY
 <!ELEMENT mother EMPTY>
 <!ATTLIST mother hlink IDREF #REQUIRED>
 
+<!-- (None|Birth|Adopted|Stepchild|Sponsored|Foster|Other|Unknown) -->
 <!ELEMENT childref (citationref*,noteref*)>
 <!ATTLIST childref
         hlink IDREF #REQUIRED
         priv  (0|1) #IMPLIED
-        mrel  (None|Birth|Adopted|Stepchild|Sponsored|Foster|Other|Unknown) #IMPLIED
-        frel  (None|Birth|Adopted|Stepchild|Sponsored|Foster|Other|Unknown) #IMPLIED
+        mrel  CDATA #IMPLIED
+        frel  CDATA #IMPLIED
 >
 
 <!ELEMENT type (#PCDATA)>
@@ -215,7 +219,8 @@ EVENT
 <!ELEMENT events (event)*>
 
 <!ELEMENT event (type?, (daterange|datespan|dateval|datestr)?, place?, cause?,
-                 description?, attribute*, noteref*, citationref*, objref*)>
+                 description?, attribute*, noteref*, citationref*, objref*,
+                 tagref*)>
 <!ATTLIST event 
         id        CDATA #IMPLIED
         handle    ID    #REQUIRED
@@ -229,7 +234,7 @@ SOURCES
 
 <!ELEMENT sources (source)*>
 <!ELEMENT source (stitle?, sauthor?, spubinfo?, sabbrev?,
-                  noteref*, objref*, data_item*, reporef*)>
+                  noteref*, objref*, srcattribute*, reporef*, tagref*)>
 <!ATTLIST source
         id        CDATA #IMPLIED
         handle    ID    #REQUIRED
@@ -247,16 +252,25 @@ PLACES
 
 <!ELEMENT places (placeobj)*>
 
-<!ELEMENT placeobj (ptitle?, coord?, location*, objref*, url*, noteref*,
-                    citationref*)>
+<!ELEMENT placeobj (ptitle?, pname+, code?, coord?, placeref*, location*,
+                    objref*, url*, noteref*, citationref*, tagref*)>
 <!ATTLIST placeobj
         id        CDATA #IMPLIED
         handle    ID    #REQUIRED
         priv      (0|1) #IMPLIED
         change    CDATA #REQUIRED
+        type      CDATA #REQUIRED
+>
+
+<!ELEMENT pname (daterange|datespan|dateval|datestr)?>
+
+<!ATTLIST pname
+        lang CDATA #IMPLIED
+        value CDATA #REQUIRED
 >
 
 <!ELEMENT ptitle (#PCDATA)>
+<!ELEMENT code (#PCDATA)>
 
 <!ELEMENT coord EMPTY>
 <!ATTLIST coord
@@ -296,6 +310,7 @@ OBJECTS
 <!ATTLIST file
         src         CDATA #REQUIRED
         mime        CDATA #REQUIRED
+        checksum    CDATA #IMPLIED
         description CDATA #REQUIRED
 >
 
@@ -305,7 +320,7 @@ REPOSITORIES
 
 <!ELEMENT repositories (repository)*>
 
-<!ELEMENT repository (rname, type, address*, url*, noteref*)>
+<!ELEMENT repository (rname, type, address*, url*, noteref*, tagref*)>
 <!ATTLIST repository
         id        CDATA #IMPLIED
         handle    ID    #REQUIRED
@@ -367,8 +382,8 @@ CITATIONS
 
 <!ELEMENT citations (citation)*>
 
-<!ELEMENT citation ((daterange|datespan|dateval|datestr)?, page?, confidence?,
-                    noteref*, objref*, data_item*, sourceref)>
+<!ELEMENT citation ((daterange|datespan|dateval|datestr)?, page?, confidence,
+                    noteref*, objref*, srcattribute*, sourceref, tagref*)>
 <!ATTLIST citation
         id        CDATA #IMPLIED
         handle    ID    #REQUIRED
@@ -383,7 +398,7 @@ BOOKMARKS
 <!ELEMENT bookmarks (bookmark)*>
 <!ELEMENT bookmark EMPTY>
 <!ATTLIST bookmark 
-        target (person|family|event|source|place|media|repository|
+        target (person|family|event|source|citation|place|media|repository|
                 note) #REQUIRED
         hlink  IDREF #REQUIRED
 >
@@ -493,6 +508,13 @@ SHARED ELEMENTS
         value   CDATA   #REQUIRED
 >
 
+<!ELEMENT srcattribute EMPTY>
+<!ATTLIST srcattribute
+        priv    (0|1)   #IMPLIED
+        type    CDATA   #REQUIRED
+        value   CDATA   #REQUIRED
+>
+
 <!ELEMENT place EMPTY>
 <!ATTLIST place hlink IDREF #REQUIRED>
 
@@ -513,6 +535,11 @@ SHARED ELEMENTS
         priv (0|1)  #IMPLIED
 >
 
+<!ELEMENT placeref ((daterange|datespan|dateval|datestr)?)>
+<!ATTLIST placeref
+        hlink IDREF #REQUIRED
+>
+
 <!ELEMENT region EMPTY>
 <!ATTLIST region
         corner1_x  CDATA #REQUIRED

data/grampsxml.rng

@@ -4,7 +4,7 @@
 # Gramps - a GTK+/GNOME based genealogy program
 #
 # Copyright (C) 2005-2007  Donald N. Allingham
-# Copyright (C) 2010-2011  Nick Hall
+# Copyright (C) 2010-2014  Nick Hall
 #
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -18,11 +18,10 @@
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 
 # Written by Alex Roitman
 
-# $Id$
 -->
 
 <!--
@@ -32,7 +31,7 @@
 
 <grammar
   datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes"  
-  ns="http://gramps-project.org/xml/1.5.0/"
+  ns="http://gramps-project.org/xml/1.7.1/"
   xmlns="http://relaxng.org/ns/structure/1.0">
 
   <start><element name="database">
@@ -211,16 +210,7 @@
   </define>
 
   <define name="child-rel">
-    <choice>
-      <value>Birth</value>
-      <value>Adopted</value>
-      <value>Stepchild</value>
-      <value>Sponsored</value>
-      <value>Foster</value>
-      <value>None</value>
-      <value>Other</value>
-      <value>Unknown</value>
-    </choice>
+    <text/>
   </define>
 
   <define name="name-content">
@@ -231,13 +221,7 @@
     <optional><attribute name="priv">
         <ref name="priv-content"/>
     </attribute></optional>
-    <optional><attribute name="type"><choice>
-        <value>Unknown</value>
-        <value>Also Known As</value>
-        <value>Birth Name</value>
-        <value>Married Name</value>
-        <value>Other Name</value>
-    </choice></attribute></optional>
+    <optional><attribute name="type"><text/></attribute></optional>
     <optional><attribute name="sort"><text/></attribute></optional>
     <optional><attribute name="display"><text/></attribute></optional>
     <optional><element name="first"><text/></element></optional>
@@ -266,20 +250,7 @@
     <value>1</value>
     <value>0</value>
     </choice></attribute></optional>
-    <optional><attribute name="derivation"><choice>
-    <value>Unknown</value>
-    <value>Inherited</value>
-    <value>Given</value>
-    <value>Taken</value>
-    <value>Patronymic</value>
-    <value>Matronymic</value>
-    <value>Feudal</value>
-    <value>Pseudonym</value>
-    <value>Patrilineal</value>
-    <value>Matrilineal</value>
-    <value>Occupation</value>
-    <value>Location</value>
-    </choice></attribute></optional>
+    <optional><attribute name="derivation"><text/></attribute></optional>
     <optional><attribute name="connector"><text/></attribute></optional>
   </define>
 
@@ -428,26 +399,31 @@
     <zeroOrMore><element name="objref">
         <ref name="objref-content"/>
     </element></zeroOrMore>
+    <zeroOrMore><element name="tagref">
+        <ref name="tagref-content"/>
+    </element></zeroOrMore>
   </define>
 
   <define name="citation-content">
     <ref name="primary-object"/>
     <optional><ref name="date-content"/></optional>
     <optional><element name="page"><text/></element></optional>
-    <optional><element name="confidence"><text/></element></optional>
+    <element name="confidence"><text/></element>
     <zeroOrMore><element name="noteref">
         <ref name="noteref-content"/>
     </element></zeroOrMore>
     <zeroOrMore><element name="objref">
         <ref name="objref-content"/>
     </element></zeroOrMore>
-    <zeroOrMore><element name="data_item">
-        <attribute name="key"><text/></attribute>
-        <attribute name="value"><text/></attribute>
+    <zeroOrMore><element name="srcattribute">
+        <ref name="srcattribute-content"/>
     </element></zeroOrMore>
     <element name="sourceref">
         <ref name="sourceref-content"/>
     </element>
+    <zeroOrMore><element name="tagref">
+        <ref name="tagref-content"/>
+    </element></zeroOrMore>
   </define>
 
   <define name="source-content">
@@ -462,22 +438,32 @@
     <zeroOrMore><element name="objref">
         <ref name="objref-content"/>
     </element></zeroOrMore>
-    <zeroOrMore><element name="data_item">
-        <attribute name="key"><text/></attribute>
-        <attribute name="value"><text/></attribute>
+    <zeroOrMore><element name="srcattribute">
+        <ref name="srcattribute-content"/>
     </element></zeroOrMore>
     <zeroOrMore><element name="reporef">
         <ref name="reporef-content"/>
     </element></zeroOrMore>
+    <zeroOrMore><element name="tagref">
+        <ref name="tagref-content"/>
+    </element></zeroOrMore>
   </define>
 
   <define name="place-content">
     <ref name="primary-object"/>
+    <attribute name="type"><text/></attribute>
     <optional><element name="ptitle"><text/></element></optional>
+    <oneOrMore><element name="pname">
+        <ref name="placename-content"/>
+    </element></oneOrMore>
+    <optional><element name="code"><text/></element></optional>
     <optional><element name="coord">
         <attribute name="long"><text/></attribute>
         <attribute name="lat"><text/></attribute>
     </element></optional>
+    <zeroOrMore><element name="placeref">
+        <ref name="placeref-content"/>
+    </element></zeroOrMore>
     <zeroOrMore><element name="location">
         <optional><attribute name="street"><text/></attribute></optional>
         <optional><attribute name="locality"><text/></attribute></optional>
@@ -501,6 +487,9 @@
     <zeroOrMore><element name="citationref">
         <ref name="citationref-content"/>
     </element></zeroOrMore>
+    <zeroOrMore><element name="tagref">
+        <ref name="tagref-content"/>
+    </element></zeroOrMore>
   </define>
 
   <define name="object-content">
@@ -508,7 +497,8 @@
     <element name="file">
         <attribute name="src"><text/></attribute>
         <attribute name="mime"><text/></attribute>
-        <attribute name="description"><text/></attribute>
+        <optional><attribute name="checksum"><text/></attribute></optional>
+        <optional><attribute name="description"><text/></attribute></optional>
     </element>
     <zeroOrMore><element name="attribute">
         <ref name="attribute-content"/>
@@ -538,6 +528,9 @@
     <zeroOrMore><element name="noteref">
         <ref name="noteref-content"/>
     </element></zeroOrMore>
+    <zeroOrMore><element name="tagref">
+        <ref name="tagref-content"/>
+    </element></zeroOrMore>
   </define>
 
   <define name="bookmark-content">
@@ -546,6 +539,7 @@
         <value>family</value>
         <value>event</value>
         <value>source</value>
+        <value>citation</value>
         <value>place</value>
         <value>media</value>
         <value>repository</value>
@@ -610,6 +604,20 @@
   <define name="citationref-content">
     <attribute name="hlink"><data type="IDREF"/></attribute>
   </define>
+  
+  <define name="personref-content">
+    <attribute name="hlink"><data type="IDREF"/></attribute>
+        <optional><attribute name="priv">
+            <ref name="priv-content"/>
+        </attribute></optional>
+        <attribute name="rel"><text/></attribute>
+    <optional><zeroOrMore><element name="citationref">
+        <ref name="citationref-content"/>
+    </element></zeroOrMore></optional>
+    <optional><zeroOrMore><element name="noteref">
+        <ref name="noteref-content"/>
+    </element></zeroOrMore></optional>
+  </define>
     
   <define name="sourceref-content">
     <attribute name="hlink"><data type="IDREF"/></attribute>
@@ -665,6 +673,14 @@
         <ref name="noteref-content"/>
     </element></zeroOrMore>
   </define>
+  
+  <define name="srcattribute-content">
+    <optional><attribute name="priv">
+        <ref name="priv-content"/>
+    </attribute></optional>
+    <attribute name="type"><text/></attribute>
+    <attribute name="value"><text/></attribute>
+  </define>
 
   <define name="url-content">
       <optional><attribute name="priv">
@@ -729,6 +745,17 @@
     <text/>
   </define>
 
+  <define name="placename-content">
+    <attribute name="value"><text/></attribute>
+    <optional><attribute name="lang"><text/></attribute></optional>
+    <optional><ref name="date-content"/></optional>
+  </define>
+
+  <define name="placeref-content">
+    <attribute name="hlink"><data type="IDREF"/></attribute>
+    <optional><ref name="date-content"/></optional>
+  </define>
+
   <define name="tagref-content">
     <attribute name="hlink"><data type="IDREF"/></attribute>
   </define>

data/holidays.xml.in

@@ -0,0 +1,538 @@
+<?xml version="1.0" encoding="utf-8"?>
+<calendar>
+  <country _name="Bulgaria">
+    <date name="Нова Година" value="*/1/1" type="national" />
+    <date name="Освобождение на България от Османско иго" value="*/3/3" type="national" />
+    <date name="Ден на труда" value="*/5/1" type="national" />
+    <date name="Ден на храбростта и Българската армия" value="*/5/6" type="national" />
+    <date name="Гергьовден" value="*/5/6" type="religious" />
+    <date name="Ден на българската просвета и култура и на славянската писменост" value="*/5/24" type="national" />
+    <date name="Ден на Съединението на България" value="*/9/6" type="national" />
+    <date name="Ден на Независимостта на България" value="*/9/22" type="national" />
+    <date name="Ден на народните будители" value="*/10/1" type="national" />
+    <date name="Бъдни вечер" value="*/12/24" type="national" />
+    <date name="Рождество Христово, Коледа" value="*/12/25" type="national" />
+    <date name="Рождество Христово, Коледа" value="*/12/26" type="national" />
+    <date name="Васильовден" value="*/1/1" type="religious" />
+    <date name="Св. Йоан Кръстител (Ивановден)" value="*/1/6" type="religious" />
+    <date name="Богоявление (Йордановден)" value="*/1/7" type="religious" />
+    <date name="Антоновден" value="*/1/17" type="religious" />
+    <date name="Атанасовден" value="*/1/18" type="religious" />
+    <date name="Трифон Зарезан (стар ст.)" value="*/2/1" type="religious" />
+    <date name="Сретение Господне" value="*/2/2" type="religious" />
+    <date name="Св. Симеон" value="*/2/3" type="religious" />
+    <date name="Св. Валентин" value="*/2/14" type="religious" />
+    <date name="Трифон Зарезан" value="*/2/14" type="religious" />
+    <date name="Благовещение" value="*/3/25" type="religious" />
+    <date name="Св. цар Борис" value="*/5/2" type="religious" />
+    <date name="Св. Св.Кирил и Методий" value="*/5/11" type="religious" />
+    <date name="Св.Богородица" value="*/6/11" type="religious" />
+    <date name="Еньовден" value="*/6/24" type="religious" />
+    <date name="Петровден" value="*/6/29" type="religious" />
+    <date name="Св. Седмочисленици" value="*/7/27" type="religious" />
+    <date name="Илинден" value="*/7/20" type="religious" />
+    <date name="Рождество Богородично (Малка Богородица)" value="*/9/8" type="religious" />
+    <date name="Кръстовден" value="*/9/14" type="religious" />
+    <date name="Петковден" value="*/10/14" type="religious" />
+    <date name="Димитровден" value="*/10/26" type="religious" />
+    <date name="Архангеловден" value="*/11/8" type="religious" />
+    <date name="Въведение Богородично" value="*/11/21" type="religious" />
+    <date name="Андреевден" value="*/11/30" type="religious" />
+    <date name="Св. Варвара" value="*/12/4" type="religious" />
+    <date name="Св. Сава" value="*/12/5" type="religious" />
+    <date name="Никулден" value="*/12/6" type="religious" />
+    <date name="Игнажден" value="*/12/20" type="religious" />
+    <date name="Стефановден" value="*/12/27" type="religious" />
+    <date name="Великден" value="> julian_easter(y)" type="religious" />
+    <date name="Цветница" value="> julian_easter(y)" offset="-7" type="religious" />
+    <date name="Възнесение господне" value="2010/5/13" type="religious" />
+    <date name="Възнесение господне" value="2011/6/2" type="religious" />
+    <date name="Възнесение господне" value="2012/5/24" type="religious" />
+  </country>
+  <country _name="Canada">
+    <date name="New Year's Day" value="*/1/1" type="national" />
+    <date name="Groundhog Day" value="*/2/2" type="secular" />
+    <date name="Valentine's Day" value="*/2/14" type="secular" />
+    <date name="Flag Day" value="*/2/15" type="secular" />
+    <date name="St. Patrick's Day" value="*/3/17" type="secular" />
+    <date name="April Fool's Day" value="*/4/1" type="secular" />
+    <date name="Daylight Savings begins" value="*/1/sun/apr" type="informational" />
+    <date name="Ash Wednesday" value="> easter(y)" type="religious" offset="-46" />
+    <date name="Easter" type="religious" value="> easter(y)"  />
+    <date name="Passover" type="religious" value="> passover(y)" />
+    <date name="Earth Day" value="*/4/22" type="secular" />
+    <date name="Mother's Day" value="*/2/sun/may" type="secular" />
+    <date name="Victoria Day" value="*/5/24" offset="-mon" type="national" />
+    <date name="Father's Day" value="*/3/sun/jun" type="secular" />
+    <date name="St-Jean Baptiste (QC)" value="*/6/24" type="national" />
+    <date name="Canada Day" value="*/7/1" type="national" />
+    <date name="Civic Holiday" value="*/1/mon/aug" type="national" />
+    <date name="Labour Day" value="*/1/mon/sep" type="national" />
+    <date name="Grandparent's Day" value="*/2/sun/sep" offset="6" type="secular" />
+    <date name="Thanksgiving" value="*/2/mon/oct" type="national" />
+    <date name="Daylight Savings ends" value="*/-1/sun/oct" type="informational" />
+    <date name="Yom Kippur" type="religious" value="> passover(y)" offset="172" />
+    <date name="Ramadan begins" value="2006/9/24" type="religious" />
+    <date name="Ramadan begins" value="2007/9/13" type="religious" />
+    <date name="Ramadan begins" value="2008/9/2" type="religious" />
+    <date name="Halloween" value="*/10/31" type="secular" />
+    <date name="Rememberance Day" value="*/11/11" type="national" />
+    <date name="Hanukkah begins" type="religious" value="> hanuka(y)" />
+    <date name="Christmas" value="*/12/25" type="national" />
+    <date name="Boxing Day" value="*/12/26" type="national" />
+  </country>
+  <country _name="Czech Republic">
+    <date name="Nový rok" value="*/1/1" type="national" />
+    <date name="Den obnovy samostatného českého státu" value="*/1/1" type="national" />
+    <date name="Velikonoce" type="religious" value="> easter(y)"  />
+    <date name="Svátek práce" value="*/5/1" type="national" />
+    <date name="Den osvobození od fašismu" value="*/5/8" type="national" />
+    <date name="Den slovanských věrozvěstů Cyrila a Metoděje" value="*/7/5" type="national" />
+    <date name="Den upálení mistra Jana Husa" value="*/7/6" type="national" />
+    <date name="Den české státnosti" value="*/9/28" type="national" />
+    <date name="Den vzniku samostatného československého státu" value="*/10/28" type="national" />
+    <date name="Den boje za svobodu a demokracii" value="*/11/17" type="national" />
+    <date name="Štědrý den" value="*/12/24" type="religious" />
+    <date name="1. svátek vánoční" value="*/12/25" type="national" />
+    <date name="2. svátek vánoční" value="*/12/26" type="national" />
+  </country>
+  <country _name="Chile">
+    <date name="Año nuevo" value="*/1/1" type="national" />
+    <date name="Viernes Santo" value="2007/4/6" type="religious" />
+    <date name="Viernes Santo" value="2008/3/21" type="religious" />
+    <date name="Viernes Santo" value="2009/4/10" type="religious" />
+    <date name="Viernes Santo" value="2010/4/2" type="religious" />
+    <date name="Viernes Santo" value="2011/4/22" type="religious" />
+    <date name="Viernes Santo" value="2012/4/6" type="religious" />
+    <date name="Viernes Santo" value="2013/3/29" type="religious" />
+    <date name="Viernes Santo" value="2014/4/18" type="religious" />
+    <date name="Viernes Santo" value="2015/4/3" type="religious" />
+    <date name="Día del Trabajador" value="*/5/1" type="national" />
+    <date name="Día de las Glorias Navales" value="*/5/21" type="national" />
+    <date name="San Pedro y San Pablo" value="*/6/29" type="religious" />
+    <date name="Día de la Virgen del Carmen" value="*/7/16" type="religious" />
+    <date name="Asunción de la Virgen" value="*/8/15" type="religious" />
+    <date name="Fiestas Patrias" value="*/9/18" type="national" />
+    <date name="Glorias del Ejército" value="*/9/19" type="national" />
+    <date name="Día de la Raza" value="*/10/12" type="national" />
+    <date name="Todos los Santos" value="*/11/1" type="religious" />
+    <date name="Inmaculada Concepción" value="*/12/8" type="religious" />
+    <date name="Navidad" value="*/12/25" type="national" />
+  </country>
+  <country _name="China">
+    <date name="Chinese New Year" value="2006/1/29" type="national" />
+  </country>
+  <country _name="Croatia">
+    <date name="Nova godina" value="*/1/1" type="national" />
+    <date name="Sveta tri kralja" value="*/1/6" type="national" />
+    <date name="Uskrs" value="> easter(y)" type="national" />
+    <date name="Uskršnji ponedjeljak" value="> easter(y)" offset="1" type="national" />
+    <date name="Dan rada" value="*/5/1" type="national" />
+    <date name="Tijelovo" value="> easter(y)" offset="60" type="national" />
+    <date name="Dan antifašističke borbe" value="*/6/22" type="national" />
+    <date name="Dan državnosti" value="*/6/25" type="national" />
+    <date name="Dan domovinske zahvalnosti" value="*/8/5" type="national" />
+    <date name="Velika Gospa" value="*/8/15" type="national" />
+    <date name="Dan neovisnosti" value="*/10/8" type="national" />
+    <date name="Svi sveti" value="*/11/1" type="national" />
+    <date name="Božić" value="*/12/25" type="national" />
+    <date name="Sveti Stjepan" value="*/12/26" type="national" />
+  </country>
+  <country _name="England">
+    <date name="New Year's Day" value="*/1/1" type="national" />
+    <date name="Bank Holiday" value="*/1/1" offset="+1" if="dow(y, m, d) == 7" type="national" />
+    <date name="Bank Holiday" value="*/1/1" offset="+2" if="dow(y, m, d) == 6" type="national" />
+    <date name="Good Friday" value="> easter(y)" offset="-2" type="national" />
+    <date name="Easter Monday" value="> easter(y)" offset="+1" type="national" />
+    <date name="May Bank Holiday" value="*/1/mon/may" type="national" />
+    <date name="Spring Bank Holiday" value="*/-1/mon/may" if="y != 2012" type="national" />
+    <date name="Spring Bank Holiday" value="2012/6/4" type="national" />
+    <date name="Diamond Jubilee" value="2012/6/5" type="national" />
+    <date name="Summer Bank Holiday" value="*/-1/mon/aug" type="national" />
+    <date name="Christmas Day" value="*/dec/25" type="national" />
+    <date name="Boxing Day" value="*/dec/26" type="national" />
+    <date name="Bank Holiday" value="*/dec/25" offset="+2" if="dow(y, m, d) > 5" type="national" />
+    <date name="Bank Holiday" value="*/dec/26" offset="+2" if="dow(y, m, d) > 5" type="national" />
+    <date name="BST starts" value="*/-1/sun/mar" type="informational" />
+    <date name="BST ends" value="*/-1/sun/oct" type="informational" />
+    <date name="Valentine's Day" value="*/2/14" type="secular" />
+    <date name="Shrove Tuesday" value="> easter(y)" offset="-47" type="religious" />
+    <date name="Ash Wednesday" value="> easter(y)" offset="-46" type="religious" />
+    <date name="Easter Sunday" value="> easter(y)" type="religious" />
+    <date name="April Fool's Day" value="*/4/1" type="secular" />
+    <date name="St. George's Day" value="*/4/23" type="secular" />
+    <date name="Mothering Sunday" value="> easter(y)" offset="-21" type="secular" />
+    <date name="Fathers' Day" value="*/3/sun/jun" type="secular" />
+    <date name="Halloween" value="*/10/31" type="secular" />
+    <date name="Guy Fawkes Night" value="*/11/5" type="secular" />
+    <date name="Armistice Day" value="*/11/11" type="secular" />
+    <date name="Remembrance Sunday" value="*/2/sun/nov" type="secular" />
+  </country>
+  <country _name="Finland">
+    <date name="Loppiainen" value="*/1/6" type="religious" if="not(y>=1973)" />
+    <date name="Loppiainen" value="*/1/6" offset="sat" type="religious" if="(y>=1973) and not(y>=1992)" />
+    <date name="Loppiainen" value="*/1/6" type="religious" if="(y>=1992)" />
+    <date name="Knud" value="*/1/7" type="religious" if="not(y>=1708)" />
+    <date name="Knud" value="*/1/13" type="religious" if="(y>=1708) and not(y>=1885)" />
+    <date name="Nuutti" value="*/1/13" type="religious" if="(y>=1885)" />
+    <date name="Pyhän Henrikin muistopäivä" value="*/1/20" type="religious" if="not(y>=1699)" />
+    <date name="Pyhän Henrikin muistopäivä" value="*/1/19" type="religious" if="(y>=1699)" />
+    <date name="Laskiaissunnuntai" type="religious" value="> easter(y)" offset="-49"/>
+    <date name="Laskiaistiistai" type="religious" value="> easter(y)" offset="-47"/>
+    <date name="Tuhkakeskiviikko" type="religious" value="> easter(y)" offset="-46" />
+<!--
+# Candlemas Day was February 2, before the year 1774.
+# From 1774 Candlemas Day was February 2, if it is Sunday, otherwise the next Sunday.
+# If this day is Shrove Sunday, Candlemas Day is the week before.
+-->
+    <date name="Kynttilänpäivä" value="*/2/2" type="religious" if="not(y>=1774)" />
+<!--
+# Before the year 1955, Annunciation day was 25 March.
+# If the day is a week before Passover, the holy day was Palm Sunday preceding Saturday.
+# If it occurred on Easter Sunday, Annunciation day was Easter the following Tuesday.
+#
+# From 1955 has been the Annunciation on Sunday, no earlier than March 22 and no later than March 28,
+# if this Sunday is Palm Sunday or Easter, Annunciation day is the Sunday before Palm Sunday.
+-->
+    <date name="Palmusunnuntai" type="religious" value="> easter(y)" offset="-7" />
+    <date name="Kiirastorstai" type="religious" value="> easter(y)" offset="-3" />
+    <date name="Pitkäperjantai" type="religious" value="> easter(y)" offset="-2" />
+    <date name="Lankalauantai" type="religious" value="> easter(y)" offset="-1" />
+    <date name="Pääsiäispäivä" type="religious" value="> easter(y)" />
+    <date name="2. Pääsiäispäivä" type="religious" value="> easter(y)" offset="1" />
+    <date name="Helatorstai" type="religious" value="> easter(y)" offset="39" if="not(y>=1973)" />
+    <date name="Kristuksen taivaaseenastumisen päivä." type="religious" value="> easter(y)" offset="34" if="(y>=1973) and not(y>=1992)" />
+    <date name="Helatorstai" type="religious" value="> easter(y)" offset="39" if="(y>=1992)" />
+    <date name="Helluntaipäivä" value="easter(y)" offset="49" type="religious" />
+    <date name="Pyhän Kolminaisuuden päivä" value="easter(y)" offset="56" type="religious" />
+    <date name="Apostolienpäivä" value="easter(y)" offset="91" type="religious" />
+    <date name="Kirkastussunnuntai." value="easter(y)" offset="105" type="religious" />
+    <date name="Juhannusaatto" value="*/jun/19" offset="fri" type="religious" if="(y>=1955)" />
+    <date name="Juhannusaatto" value="*/jun/23" type="religious" if="not(y>=1955)"  />
+    <date name="Juhannuspäivä" value="*/jun/20" offset="sat" type="religious" if="(y>=1955)" />
+    <date name="Juhannuspäivä" value="*/jun/24" type="religious" if="not(y>=1955)"  />
+    <date name="Pyhäinmiestenpäivä" value="*/nov/1" type="religious" if="not(y>=1774)" />
+    <date name="Pyhäinmiestenpäivä" value="*/nov/1" offset="sun" type="religious" if="(y>=1774) and not(y>=1955)" />
+    <date name="Pyhäinpäivä" value="*/oct/31" offset="sat" type="religious" if="(y>=1955)" />
+    <date name="1. Adventti" value="*/nov/27" offset="sun" type="religious" />
+    <date name="2. Adventti" value="*/dec/4" offset="sun" type="religious" />
+    <date name="3. Adventti" value="*/dec/11" offset="sun" type="religious" />
+    <date name="4. Adventti" value="*/dec/18" offset="sun" type="religious" />
+    <date name="Lucian päivä" value="*/12/13" type="religious" />
+    <date name="Tuomaan päivä" value="*/12/21" type="religious" />
+    <date name="Jouluaatto" value="*/12/24" type="religious" />
+    <date name="Joulupäivä" value="*/12/25" type="religious" />
+    <date name="Tapaninpäivä" value="*/12/26" type="religious" />
+    <date name="Johannes Evankelistan päivä" value="*/dec/27" type="religious" if="not(y>=1774)" />
+    <date name="Apostoli Johanneksen päivä." value="*/dec/27" type="religious" if="dow(y, m, d) == 7 and (y>=2000)" />
+    <date name="Viattomien lasten päivä" value="*/12/28" type="religious" />
+    <date name="Uudenvuodenpäivä" value="*/1/1" type="national" />
+    <date name="Vainojen uhrien muistopäivä" value="*/1/27" type="national" if="(y>=2002)" />
+    <date name="J.L. Runebergin päivä" value="*/2/5" type="national" if="(y>=1854)" />
+    <date name="Saamelaisten kansallis päivä" value="*/2/6" type="religious" if="(y>=2004)" />
+    <date name="Ystävänpäivä" value="*/2/14" type="national" if="(y>=1987)" />
+    <date name="Kalevalan päivä" value="*/2/28" type="national" if="(y>=1978)" />
+    <date name="Naistenpäivä" value="*/3/8" type="national" if="(y>=1975)" />
+    <date name="Minna Canthin päivä" value="*/3/19" type="national" if="(y>=2003)" />
+    <date name="Kesäaika alkaa" value="*/-1/sun/mar" type="informational" if="(y>=1981)" />
+    <date name="Romanien kansallispäivä" value="*/4/8" type="national" if="(y>=2014)" />
+    <date name="Mikael Agricolan päivä" value="*/4/9" type="national" if="(y>=1960)" />
+    <date name="Veteraanipäivä" value="*/4/27" type="national" if="(y>=1987)" />
+    <date name="Vappuaatto" value="*/4/30" type="national" />
+    <date name="Vappu" value="*/5/1" type="national" />
+    <date name="Eurooppa-päivä" value="*/5/9" type="national" if="(y>=1950)" />
+    <date name="J.V. Snelmannin päivä" value="*/5/12" type="national" if="(y>=1952)" />
+    <date name="Äitienpäivä" value="*/2/sun/may" type="national" if="(y>=1927)" />
+    <date name="Kaatuneiden muistopäivä" value="*/3/sun/may" type="national" if="(y>=1947)" />
+    <date name="Puolustusvoimien lippujuhla" value="*/6/4" type="national" if="(y>=1951)" />
+    <date name="Eino Leinon päivä" value="*/7/6" type="national" if="(y>=1998)" />
+    <date name="Unikeonpäivä" value="*/6/27" type="national" if="not(y>=1720)" />
+    <date name="Unikeonpäivä" value="*/7/27" type="national" if="(y>=1720)" />
+    <date name="Yrittäjänpäivä" value="*/9/5" type="national" if="(y>=2010)" />
+    <date name="Mikkelinpäivä" value="*/9/29" type="national" if="not(y>=1774)" />
+    <date name="Mikkelinpäivä" value="*/9/29" offset="sun" type="national" if="(y>=1774)" />
+    <date name="Aleksis Kiven päivä" value="*/10/10" type="national" if="(y>=1950)" />
+    <date name="YK:n päivä" value="*/10/24" type="national" if="(y>=1968)" />
+    <date name="Halloween" value="*/10/31" type="secular" if="(y>=1950)" />
+    <date name="Talviaika alkaa" value="*/-1/sun/oct" type="informational" if="(y>=1981)" />
+    <date name="Ruotsalaisuuden päivä" value="*/11/6" type="national" if="(y>=1979)" />
+    <date name="Isänpäivä" value="*/2/sun/nov" type="national" if="(y>=1987)" />
+    <date name="Lapsen oikeukeuksien päivä" value="*/11/20" type="national" if="(y>=2002)" />
+    <date name="Itsenäisyyspäivä" value="*/12/6" type="national" if="(y>=1917)" />
+    <date name="Jean Sibeliuksen päivä" value="*/12/8" type="national" if="(y>=2011)" />
+    <date name="Uudenvuodenaatto" value="*/12/31" type="national" if="(y>=1846)" />
+  </country>
+  <country _name="France">
+    <date name="Jour de l'an" value="*/1/1" type="national" />
+    <date name="Fête du travail" value="*/5/1" type="national" />
+    <date name="Victoire 1945" value="*/5/8" type="national" />
+    <date name="Fête nationale" value="*/7/14" type="national" />
+    <date name="Armistice 1918" value="*/11/11" type="national" />
+    <date name="Abolition de l’esclavage (Martinique)" value="*/05/22" type="local" />
+    <date name="Abolition de l’esclavage (Guadeloupe)" value="*/05/27" type="local" />
+    <date name="Abolition de l’esclavage (Guyane)" value="*/06/10" type="local" />
+    <date name="Abolition de l’esclavage (Réunion)" value="*/10/20" type="local" />
+    <date name="Vendredi Saint (Alsace/Moselle)" type="religious" value="> easter(y)" offset="-2" />
+    <date name="Pâques" type="religious" value="> easter(y)"  />
+    <date name="Lundi de pâques" type="religious" value="> easter(y)" offset="1" />
+    <date name="Ascension" type="religious" value="> easter(y)" offset="39" />
+    <date name="Pentecôte" type="religious" value="> easter(y)" offset="49" />
+    <date name="Lundi de pentecôte" type="religious" value="> easter(y)" offset="50" />
+    <date name="Assomption" value="*/8/15" type="religious" />
+    <date name="Toussaint" value="*/11/1" type="religious" />
+    <date name="Jour des morts (Antilles)" value="*/11/2" type="religious" />
+    <date name="Noël" value="*/12/25" type="religious" />
+    <date name="Pâque juive" type="religious" value="> passover(y)" />
+    <date name="Yom Kippour" type="religious" value="> passover(y)" offset="172" />
+    <date name="Hanoucca" type="religious" value="> hanuka(y)" />
+    <date name="début Ramadan" value="2006/09/24" type="religious" />
+    <date name="début Ramadan" value="2007/09/13" type="religious" />
+    <date name="début Ramadan" value="2008/09/02" type="religious" />
+    <date name="début Ramadan" value="2009/08/22" type="religious" />
+    <date name="début Ramadan" value="2010/08/12" type="religious" />
+    <date name="début Ramadan" value="2011/08/02" type="religious" />
+    <date name="début Ramadan" value="2012/07/21" type="religious" />
+    <date name="début Ramadan" value="2013/07/09" type="religious" />
+    <date name="début Ramadan" value="2014/06/29" type="religious" />
+    <date name="début Ramadan" value="2015/06/19" type="religious" />
+    <date name="début Ramadan" value="2016/06/08" type="religious" />
+    <date name="Saint Étienne (Alsace/Moselle)" value="*/12/26" type="religious" />
+  </country>
+  <country _name="Germany">
+    <date name="Neujahr" type="national" value="*/1/1" />
+    <date name="Hl. Drei Könige BW,BY,ST" type="religious" value="*/1/6" />
+    <date name="Karfreitag" type="religious" value="> easter(y)" offset="-2" />
+    <date name="Ostermontag" type="religious" value="> easter(y)" offset="+1" />
+    <date name="Maifeiertag" type="national" value="*/5/1" />
+    <date name="Christi Himmelfahrt" type="religious" value="> easter(y)" offset="+39" />
+    <date name="Pfingstmontag" type="religious" value="> easter(y)" offset="+50" />
+    <date name="Fronleichnam BW, BY, HE, NW, RP, SL" type="religious" value="> easter(y)" offset="+60" />
+    <date name="Mariä Himmelfahrt SL" type="religious" value="*/8/15" />
+    <date name="Tag der Deutschen Einheit" type="national" value="*/10/3" />
+    <date name="Reformationstag BB, MV, SN, ST, TH" type="religious" value="*/10/31" />
+    <date name="Allerheiligen BW, BY, NW, RP, SL" type="religious" value="*/11/1" />
+    <date name="Buß- u. Bettag SN" type="religious" value="*/11/23"  offset="-wed"/>
+    <date name="1. Weihnachtsfeiertag" type="religious" value="*/12/25" />
+    <date name="2. Weihnachtsfeiertag" type="religious" value="*/12/26" />
+  </country>
+  <country _name="Japan">
+    <date name="元日" value="*/1/1" />
+    <date name="成人の日" value="*/2/mon/jan" />
+    <date name="建国記念の日" value="*/2/11" />
+    <date name="春分の日" value="*/3/20" />
+    <date name="春分の日" value="*/3/21" />
+    <date name="昭和の日" value="*/4/29" />
+    <date name="憲法記念日" value="*/5/3" />
+    <date name="みどりの日" value="*/5/4" />
+    <date name="こどもの日" value="*/5/5" />
+    <date name="海の日" value="*/3/mon/jul" />
+    <date name="敬老の日" value="*/3/mon/sep" />
+    <date name="秋分の日" value="*/9/22" />
+    <date name="秋分の日" value="*/9/23" />
+    <date name="体育の日" value="*/2/mon/oct" />
+    <date name="文化の日" value="*/11/3" />
+    <date name="勤労感謝の日" value="*/11/23" />
+    <date name="天皇誕生日" value="*/12/23" />
+    <date name="皇太子明仁親王の結婚" value="1959/4/10" />
+    <date name="昭和天皇の大喪の礼" value="1989/2/24" />
+    <date name="天皇(明仁)即位記念" value="1990/11/12" />
+    <date name="皇太子徳仁親王の結婚" value="1993/6/9" />
+  </country>
+  <country _name="Slovakia">
+    <date name="Deň vzniku Slovenskej republiky" value="*/1/1" type="national" />
+    <date name="Zjavenie Pána (Traja králi)" value="*/1/6" type="religious" />
+    <date name="Veľký piatok" value="> easter(y)" offset="-2" type="religious" />
+    <date name="Veľkonočný pondelok" value="> easter(y)" offset="+1" type="religious" />
+    <date name="Sviatok práce" value="*/5/1" type="national" />
+    <date name="Deň víťazstva nad fašizmom" value="*/5/8" type="national" />
+    <date name="Sviatok svätého Cyrila a Metoda" value="*/7/5" type="national" />
+    <date name="Výročie SNP" value="*/8/29" type="national" />
+    <date name="Deň Ústavy Slovenskej republiky" value="*/9/1" type="national" />
+    <date name="Sedembolestná Panna Mária" value="*/9/15" type="religious" />
+    <date name="Sviatok všetkých svätých" value="*/11/1" type="religious" />
+    <date name="Deň boja za slobodu a demokraciu" value="*/11/17" type="national" />
+    <date name="Štedrý deň" value="*/12/24" type="religious" />
+    <date name="Prvý sviatok vianočný" value="*/12/25" type="national" />
+    <date name="Druhý sviatok vianočný" value="*/12/26" type="national" />
+  </country>
+  <country _name="Sweden">
+    <date name="Nyårsafton" value="*/12/31" type="national" />
+    <date name="Trettondedag jul" value="*/1/6" type="religious" />
+    <date name="Alla helgons dag" value="*/oct/31" offset="sat" type="religious" if="(y>=1953)" />
+    <date name="Lucia" value="*/12/13" type="religious" />
+    <date name="Julafton" value="*/12/24" type="religious" />
+    <date name="Juldagen" value="*/12/25" type="religious" />
+    <date name="Annandag Jul" value="*/12/26" type="religious" />
+    <date name="Skärtorsdagen" type="religious" value="> easter(y)" offset="-3" />
+    <date name="Långfredagen" type="religious" value="> easter(y)" offset="-2" />
+    <date name="Påsk" type="religious" value="> easter(y)"  />
+    <date name="Annandag Påsk" type="religious" value="> easter(y)" offset="1" />
+    <date name="Kristi Himmelsfärdsdag" type="religious" value="> easter(y)" offset="39" />
+    <date name="Pingstdagen" value="easter(y)" offset="49" type="secular" />
+    <date name="Annandag pingst" value="easter(y)" offset="50" type="secular" />
+    <date name="Nyårsdagen" value="*/1/1" type="national" />
+    <date name="Alla hjärtans dag" value="*/2/14" type="national" />
+    <date name="1. april" value="*/4/1" type="national" />
+    <date name="Första Maj" value="*/5/1" type="national" />
+    <date name="Nationaldagen" value="*/6/6" type="national" />
+    <date name="Mors dag" value="*/may/25" offset="sun" type="religious" />
+    <date name="Midsommarafton" value="*/jun/19" offset="fri" type="religious" if="(y>=1953)" />
+    <date name="Midsommarafton" value="*/jun/23" type="religious" if="not(y>=1953)"  />
+    <date name="Midsommardagen" value="*/jun/20" offset="sat" type="religious" if="(y>=1953)" />
+    <date name="Midsommardagen" value="*/jun/24" type="religious" if="not(y>=1953)"  />
+    <date name="Fars dag" value="*/2/sun/nov" type="national" />
+  </country>
+  <country _name="United States of America">
+    <date name="New Year's Eve" value="*/12/31" type="national" />
+    <date name="New Year's Day" value="*/1/1" type="national" />
+    <date name="ML Kings's Birthday" value="*/3/mon/jan" type="secular" />
+    <date name="Groundhog Day" value="*/2/2" type="secular" />
+    <date name="Lincoln's Birthday" value="*/2/12" type="secular" />
+    <date name="Super Bowl" value="*/1/sun/feb" type="secular" />
+    <date name="Valentine's Day" value="*/2/14" type="secular" />
+    <date name="Presidents' Day" value="*/3/mon/feb" type="secular" />
+    <date name="Washington's Birthday" value="*/3/mon/feb" type="secular" />
+    <date name="St. Patrick's Day" value="*/3/17" type="secular" />
+    <date name="April Fool's Day" value="*/4/1" type="secular" />
+    <date name="Arbor Day" value="*/-1/fri/apr" type="secular" />
+    <date name="Earth Day" value="*/4/22" type="secular" />
+    <date name="Easter" value="> easter(y)" type="religious" />
+    <date name="Ash Wednesday" value="> easter(y)" type="religious" offset="-46" />
+    <date name="Mardi Gras" value="> easter(y)" type="religious" offset="-47" />
+    <date name="Daylight Saving begins" value="> dst(y)[0]" type="informational" />
+    <date name="Income Taxes due" value="*/4/15" type="national" if="cmp(date.weekday(),4)-1"/>
+    <date name="Income Taxes due" value="*/4/16" type="national" if="date.weekday() == 0" />
+    <date name="Income Taxes due" value="*/4/17" type="national" if="date.weekday() == 0" />
+    <date name="Daylight Saving ends" value="> dst(y)[1]" type="informational" />
+    <date name="Inauguration Day" value="*/1/20" type="national" if="(y - 1980) % 4 == 1" />
+    <date name="Passover" value="> passover(y)" type="religious" />
+    <date name="Assistants' Day" value="*/-1/sat/apr" offset="-3" type="secular" />
+    <date name="Cinco de Mayo" value="*/5/5" type="secular" />
+    <date name="Armed Forces Day" value="*/3/sat/may" type="secular" />
+    <date name="Mothers' Day" value="*/2/sun/may" type="secular" />
+    <date name="Memorial Day" value="*/-1/mon/may" type="secular" />
+    <date name="Flag Day" value="*/6/14" type="secular" />
+    <date name="Fathers' Day" value="*/3/sun/jun" type="secular" />
+    <date name="Independence Day" value="*/7/4" type="national" />
+    <date name="Parents' Day" value="*/4/sun/jul" type="secular" />
+    <date name="Labor Day" value="*/1/mon/sep" type="national" />
+    <date name="Grandparents' Day" value="*/1/mon/sep" type="secular" offset="6" />
+    <date name="Columbus Day" value="*/2/mon/oct" type="secular" />
+    <date name="Ramadan begins" value="2006/09/24" type="religious" />
+    <date name="Ramadan begins" value="2007/09/13" type="religious" />
+    <date name="Ramadan begins" value="2008/09/2" type="religious" />
+    <date name="Ramadan begins" value="2009/08/22" type="religious" />
+    <date name="Yom Kippur" value="> passover(y)" type="religious" offset="172" />
+    <date name="United Nations Day" value="*/10/24" type="secular" />
+    <date name="Halloween" value="*/10/31" type="secular" />
+    <date name="Election Day" value="*/11/2" type="secular" offset="tue" />
+    <date name="Veterans Day" value="*/11/11" type="national" />
+    <date name="Thanksgiving" value="*/4/thu/nov" type="national" />
+    <date name="Hanukkah begins" value="> hanuka(y)" type="religious" />
+    <date name="Christmas" value="*/12/25" type="religious" />
+    <date name="Kwanzaa begins" value="*/12/26" type="religious" />
+  </country>
+  <country _name="Jewish Holidays">
+    <date _name="Purim" value="> passover(y)" offset="-30"/>
+    <date _name="Passover" value="> passover(y)" offset="0"/>
+    <date _name="2 of Passover" value="> passover(y)" offset="1"/>
+    <date _name="3 of Passover" value="> passover(y)" offset="2"/>
+    <date _name="4 of Passover" value="> passover(y)" offset="3"/>
+    <date _name="5 of Passover" value="> passover(y)" offset="4"/>
+    <date _name="6 of Passover" value="> passover(y)" offset="5"/>
+    <date _name="7 of Passover" value="> passover(y)" offset="6"/>
+    <date _name="Shavuot" value="> passover(y)" offset="50"/>
+    <date _name="Rosh Ha'Shana" value="> passover(y)" offset="163"/>
+    <date _name="Rosh Ha'Shana 2" value="> passover(y)" offset="164"/>
+    <date _name="Yom Kippur" value="> passover(y)" offset="172"/>
+    <date _name="Sukot" value="> passover(y)" offset="177"/>
+    <date _name="2 of Sukot" value="> passover(y)" offset="178"/>
+    <date _name="3 of Sukot" value="> passover(y)" offset="179"/>
+    <date _name="4 of Sukot" value="> passover(y)" offset="180"/>
+    <date _name="5 of Sukot" value="> passover(y)" offset="181"/>
+    <date _name="6 of Sukot" value="> passover(y)" offset="182"/>
+    <date _name="7 of Sukot" value="> passover(y)" offset="183"/>
+    <date _name="Simhat Tora" value="> passover(y)" offset="184"/>
+    <date _name="Hanuka" value="> hanuka(y)" offset="0"/>
+    <date _name="2 of Hanuka" value="> hanuka(y)" offset="1"/>
+    <date _name="3 of Hanuka" value="> hanuka(y)" offset="2"/>
+    <date _name="4 of Hanuka" value="> hanuka(y)" offset="3"/>
+    <date _name="5 of Hanuka" value="> hanuka(y)" offset="4"/>
+    <date _name="6 of Hanuka" value="> hanuka(y)" offset="5"/>
+    <date _name="7 of Hanuka" value="> hanuka(y)" offset="6"/>
+    <date _name="8 of Hanuka" value="> hanuka(y)" offset="7"/>
+  </country>
+  <country _name="New Zealand">
+    <date value="*/1/1" type="national" name="New Year's Day"/>
+    <date value="*/1/2" type="national" name="Day After New Year's Day"/>
+    <date value="*/1/1" type="national" offset="+1" name="New Years Day Holiday" if="dow(y, m, d) == 7"/>
+    <date value="*/1/1" type="national" offset="+2" name="Day After New Years Day Holiday" if="dow(y, m, d) == 6"/>
+    <date value="*/feb/6" type="national" name="Waitangi Day"/>
+    <date value="> easter(y)" type="national" offset="-2" name="Good Friday"/>
+    <date value="> easter(y)" type="national" offset="+1" name="Easter Monday"/>
+    <date value="*/apr/25" type="national" name="ANZAC Day"/>
+    <date value="*/-1/mon/jun" type="national" name="Queen's Birthday Holiday"/>
+    <date value="*/-4/mon/oct" type="national" name="Labour Day"/>
+    <date value="*/dec/25" type="national" name="Christmas Day"/>
+    <date value="*/dec/26" type="national" name="Boxing Day"/>
+    <date value="*/dec/25" type="national" offset="+2" name="Christmas Day Holiday" if="dow(y, m, d) > 5"/>
+    <date value="*/dec/26" type="national" offset="+2" name="Boxing Day Holiday" if="dow(y, m, d) > 5"/>
+  </country>
+  <country _name="Ukraine">
+    <date value="*/1/1" type="national" name="Новий Рік"/>
+    <date value="*/1/6" type="religious" name="Святий Вечір"/>
+    <date value="*/1/7" type="religious" name="Різдво"/>
+    <date value="*/1/13" type="religious" name="Маланка"/>
+    <date value="*/1/14" type="religious" name="Старий Новий рік, Щедрий вечір"/>
+    <date value="*/1/19" type="religious" name="Водохреща"/>
+    <date value="*/1/22" type="national" name="День Соборності України"/>
+    <date value="*/2/14" type="secular" name="День закоханих"/>
+    <date value="*/2/15" type="religious" name="Стрітення"/>
+    <date value="*/3/8" type="secular" name="Міжнародний жіночий день"/>
+    <date value="*/3/20" type="secular" name="Весняне Рівнодення"/>
+    <date value="*/4/1" type="secular" name="День сміху"/>
+    <date value="*/4/7" type="religious" name="Благовіщення"/>
+    <date value="> julian_easter(y)" type="religious" name="Великдень"/>
+    <date value="*/5/1" type="national" name="День Праці"/>
+    <date value="*/6/21" type="secular" name="Весняне Сонцестояння"/>
+    <date value="*/6/28" type="national" name="День Конституції України"/>
+    <date value="*/7/7" type="religious" name="Івана Купала"/>
+    <date value="*/8/19" type="religious" name="Спаса"/>
+    <date value="*/8/24" type="national" name="День Незалежності України"/>
+    <date value="*/9/22" type="secular" name="Осіннє Рівнодення"/>
+    <date value="*/10/14" type="religious" name="Покрова, День Українського козацтва"/>
+    <date value="*/12/13" type="religious" name="Андрія"/>
+    <date value="*/12/19" type="religious" name="Миколая"/>
+    <date value="*/12/21" type="secular" name="Осіннє Сонцестояння"/>
+  </country>
+  <country _name="Serbia">
+    <date value="*/1/1" type="national" name="Нова Година" />
+    <date value="*/1/7" type="religious" name="Божић" />
+    <date value="*/2/15" type="national" name="Дан државности Србије" />
+    <date value="> julian_easter(y)" type="religious" offset="-2" name="Велики петак" />
+    <date value="> julian_easter(y)" type="religious" name="Васкрс" />
+    <date value="> julian_easter(y)" type="religious" offset="1" name="Васкрсни понедељак" />
+    <date value="*/5/1" type="national" name="Празник рада" />
+    <date value="*/11/11" type="national" name="Дан примирја" />
+    <date value="*/1/27" type="religious" name="Свети Сава" />
+    <date value="*/4/22" type="national" name="Дан сећања на жртве холокауста" />
+    <date value="*/5/9" type="national" name="Дан победе" />
+    <date value="*/6/28" type="religious" name="Видовдан" />
+    <date value="*/10/21" type="national" name="Дан сећања на српске жртве у Другом светском рату" />
+  </country>
+  <country _name="Serbia (Latin)">
+    <date value="*/1/1" type="national" name="Nova godina" />
+    <date value="*/1/7" type="religious" name="Božić" />
+    <date value="*/2/15" type="national" name="Dan državnosti Srbije" />
+    <date value="> julian_easter(y)" type="religious" offset="-2" name="Veliki petak" />
+    <date value="> julian_easter(y)" type="religious" name="Vaskrs" />
+    <date value="> julian_easter(y)" type="religious" offset="1" name="Vaskrsni ponedeljak" />
+    <date value="*/5/1" type="national" name="Praznik rada" />
+    <date value="*/11/11" type="national" name="Dan primirja" />
+    <date value="*/1/27" type="religious" name="Sveti Sava" />
+    <date value="*/4/22" type="national" name="Dan sećanja na žrtve holokausta" />
+    <date value="*/5/9" type="national" name="Dan pobede" />
+    <date value="*/6/28" type="religious" name="Vidovdan" />
+    <date value="*/10/21" type="national" name="Dan sećanja na srpske žrtve u Drugom svetskom ratu" />
+  </country>
+</calendar>

data/lds.xml

@@ -474,6 +474,9 @@
     <code>TORON</code>
     <code>TORNO</code>
     <code>TR</code>
+  <temple name="Trujillo, Peru">
+    <code>TRUJI</code>
+  </temple>
   </temple>
   <temple name="Tuxtla Gutierrez, Mexico">
     <code>TGUTI</code>

data/man/Makefile.am

@@ -1,14 +0,0 @@
-# This is the data/man level Makefile for Gramps
-# $Id$
-
-SUBDIRS = fr sv nl pl cs
-
-man_IN_FILES = gramps.1.in
-man_MANS = $(man_IN_FILES:.1.in=.1)
-
-EXTRA_DIST = $(man_MANS) $(man_IN_FILES)
-
-gramps.1: $(top_builddir)/config.status gramps.1.in
-	cd $(top_builddir) && CONFIG_FILES=data/man/$@ $(SHELL) ./config.status
-
-CLEANFILES=$(man_MANS)

data/man/conf.py

@@ -0,0 +1,243 @@
+# -*- coding: utf-8 -*-
+#
+# Gramps documentation build configuration file, created by
+# sphinx-quickstart on Sat Dec  1 14:38:29 2012.
+#
+# This file is execfile()d with the current directory set to its containing dir.
+#
+# Note that not all possible configuration values are present in this
+# autogenerated file.
+#
+# All configuration values have a default; values that are commented out
+# serve to show the default.
+
+import sys, os
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+#sys.path.insert(0, os.path.abspath('.'))
+
+# -- General configuration -----------------------------------------------------
+
+# If your documentation needs a minimal Sphinx version, state it here.
+#needs_sphinx = '1.0'
+
+# Add any Sphinx extension module names here, as strings. They can be extensions
+# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+extensions = []
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ['_templates']
+
+# The suffix of source filenames.
+source_suffix = '.rst'
+
+# The encoding of source files.
+#source_encoding = 'utf-8-sig'
+
+# The master toctree document.
+master_doc = 'index'
+
+# General information about the project.
+project = u'Gramps'
+copyright = u'2015, Gramps project'
+
+# The version info for the project you're documenting, acts as replacement for
+# |version| and |release|, also used in various other places throughout the
+# built documents.
+#
+# The short X.Y version.
+version = '4.2'
+# The full version, including alpha/beta/rc tags.
+release = '4.2.0'
+
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+#locale_dirs = './locale'
+#gettext_compact = True
+
+# There are two options for replacing |today|: either, you set today to some
+# non-false value, then it is used:
+#today = ''
+# Else, today_fmt is used as the format for a strftime call.
+today_fmt = '%B %d, %Y'
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+exclude_patterns = ['_build']
+
+# The reST default role (used for this markup: `text`) to use for all documents.
+#default_role = None
+
+# If true, '()' will be appended to :func: etc. cross-reference text.
+#add_function_parentheses = True
+
+# If true, the current module name will be prepended to all description
+# unit titles (such as .. function::).
+#add_module_names = True
+
+# If true, sectionauthor and moduleauthor directives will be shown in the
+# output. They are ignored by default.
+#show_authors = False
+
+# The name of the Pygments (syntax highlighting) style to use.
+pygments_style = 'sphinx'
+
+# A list of ignored prefixes for module index sorting.
+#modindex_common_prefix = []
+
+
+# -- Options for HTML output ---------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages.  See the documentation for
+# a list of builtin themes.
+html_theme = 'default'
+
+# Theme options are theme-specific and customize the look and feel of a theme
+# further.  For a list of options available for each theme, see the
+# documentation.
+#html_theme_options = {}
+
+# Add any paths that contain custom themes here, relative to this directory.
+#html_theme_path = []
+
+# The name for this set of Sphinx documents.  If None, it defaults to
+# "<project> v<release> documentation".
+#html_title = None
+
+# A shorter title for the navigation bar.  Default is the same as html_title.
+#html_short_title = None
+
+# The name of an image file (relative to this directory) to place at the top
+# of the sidebar.
+#html_logo = None
+
+# The name of an image file (within the static path) to use as favicon of the
+# docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
+# pixels large.
+#html_favicon = None
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+#html_static_path = ['_static']
+
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
+# using the given strftime format.
+#html_last_updated_fmt = '%b %d, %Y'
+
+# If true, SmartyPants will be used to convert quotes and dashes to
+# typographically correct entities.
+#html_use_smartypants = True
+
+# Custom sidebar templates, maps document names to template names.
+#html_sidebars = {}
+
+# Additional templates that should be rendered to pages, maps page names to
+# template names.
+#html_additional_pages = {}
+
+# If false, no module index is generated.
+#html_domain_indices = True
+
+# If false, no index is generated.
+#html_use_index = True
+
+# If true, the index is split into individual pages for each letter.
+#html_split_index = False
+
+# If true, links to the reST sources are added to the pages.
+#html_show_sourcelink = True
+
+# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
+#html_show_sphinx = True
+
+# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
+#html_show_copyright = True
+
+# If true, an OpenSearch description file will be output, and all pages will
+# contain a <link> tag referring to it.  The value of this option must be the
+# base URL from which the finished HTML is served.
+#html_use_opensearch = ''
+
+# This is the file name suffix for HTML files (e.g. ".xhtml").
+#html_file_suffix = None
+
+# Output file base name for HTML help builder.
+htmlhelp_basename = 'Grampsdoc'
+
+
+# -- Options for LaTeX output --------------------------------------------------
+
+latex_elements = {
+# The paper size ('letterpaper' or 'a4paper').
+#'papersize': 'letterpaper',
+
+# The font size ('10pt', '11pt' or '12pt').
+#'pointsize': '10pt',
+
+# Additional stuff for the LaTeX preamble.
+#'preamble': '',
+}
+
+# Grouping the document tree into LaTeX files. List of tuples
+# (source start file, target name, title, author, documentclass [howto/manual]).
+latex_documents = [
+  ('index', 'Gramps.tex', u'Gramps Documentation',
+   u'.', 'manual'),
+]
+
+# The name of an image file (relative to this directory) to place at the top of
+# the title page.
+#latex_logo = None
+
+# For "manual" documents, if this is true, then toplevel headings are parts,
+# not chapters.
+#latex_use_parts = False
+
+# If true, show page references after internal links.
+#latex_show_pagerefs = False
+
+# If true, show URL addresses after external links.
+#latex_show_urls = False
+
+# Documents to append as an appendix to all manuals.
+#latex_appendices = []
+
+# If false, no module index is generated.
+#latex_domain_indices = True
+
+
+# -- Options for manual page output --------------------------------------------
+
+# One entry per manual page. List of tuples
+# (source start file, name, description, authors, manual section).
+man_pages = [
+    ('en', 'gramps', u'Gramps Documentation',
+     ['Gramps project'], 1)
+]
+
+# If true, show URL addresses after external links.
+#man_show_urls = False
+
+
+# -- Options for Texinfo output ------------------------------------------------
+
+# Grouping the document tree into Texinfo files. List of tuples
+# (source start file, target name, title, author,
+#  dir menu entry, description, category)
+texinfo_documents = [
+  ('index', 'Gramps', u'Gramps Documentation',
+   u'.', 'Gramps', 'One line description of project.',
+   'Miscellaneous'),
+]
+
+# Documents to append as an appendix to all manuals.
+#texinfo_appendices = []
+
+# If false, no module index is generated.
+#texinfo_domain_indices = True
+
+# How to display URL addresses: 'footnote', 'no', or 'inline'.
+#texinfo_show_urls = 'footnote'

data/man/cs/Makefile.am

@@ -1,14 +0,0 @@
-# This is the data/man/sv level Makefile for Gramps
-# $Id: Makefile.am 6189 2006-03-21 19:05:46Z rshura $
-
-man_IN_FILES = gramps.1.in
-man_MANS = $(man_IN_FILES:.1.in=.1)
-
-mandir = @mandir@/cs
-
-EXTRA_DIST = $(man_MANS) $(man_IN_FILES)
-
-gramps.1: $(top_builddir)/config.status gramps.1.in
-	cd $(top_builddir) && CONFIG_FILES=data/man/cs/$@ $(SHELL) ./config.status
-
-CLEANFILES=$(man_MANS)

data/man/cs/conf.py

@@ -0,0 +1,243 @@
+# -*- coding: utf-8 -*-
+#
+# Gramps documentation build configuration file, created by
+# sphinx-quickstart on Sat Dec  1 14:38:29 2012.
+#
+# This file is execfile()d with the current directory set to its containing dir.
+#
+# Note that not all possible configuration values are present in this
+# autogenerated file.
+#
+# All configuration values have a default; values that are commented out
+# serve to show the default.
+
+import sys, os
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+#sys.path.insert(0, os.path.abspath('.'))
+
+# -- General configuration -----------------------------------------------------
+
+# If your documentation needs a minimal Sphinx version, state it here.
+#needs_sphinx = '1.0'
+
+# Add any Sphinx extension module names here, as strings. They can be extensions
+# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+extensions = []
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ['_templates']
+
+# The suffix of source filenames.
+source_suffix = '.rst'
+
+# The encoding of source files.
+#source_encoding = 'utf-8-sig'
+
+# The master toctree document.
+master_doc = 'cs'
+
+# General information about the project.
+project = u'Gramps'
+copyright = u'2015, Gramps project'
+
+# The version info for the project you're documenting, acts as replacement for
+# |version| and |release|, also used in various other places throughout the
+# built documents.
+#
+# The short X.Y version.
+version = '4.2'
+# The full version, including alpha/beta/rc tags.
+release = '4.2.0'
+
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+locale_dirs = './locale'
+gettext_compact = True
+
+# There are two options for replacing |today|: either, you set today to some
+# non-false value, then it is used:
+#today = ''
+# Else, today_fmt is used as the format for a strftime call.
+today_fmt = '%B %d, %Y'
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+exclude_patterns = ['_build']
+
+# The reST default role (used for this markup: `text`) to use for all documents.
+#default_role = None
+
+# If true, '()' will be appended to :func: etc. cross-reference text.
+#add_function_parentheses = True
+
+# If true, the current module name will be prepended to all description
+# unit titles (such as .. function::).
+#add_module_names = True
+
+# If true, sectionauthor and moduleauthor directives will be shown in the
+# output. They are ignored by default.
+#show_authors = False
+
+# The name of the Pygments (syntax highlighting) style to use.
+pygments_style = 'sphinx'
+
+# A list of ignored prefixes for module index sorting.
+#modindex_common_prefix = []
+
+
+# -- Options for HTML output ---------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages.  See the documentation for
+# a list of builtin themes.
+html_theme = 'default'
+
+# Theme options are theme-specific and customize the look and feel of a theme
+# further.  For a list of options available for each theme, see the
+# documentation.
+#html_theme_options = {}
+
+# Add any paths that contain custom themes here, relative to this directory.
+#html_theme_path = []
+
+# The name for this set of Sphinx documents.  If None, it defaults to
+# "<project> v<release> documentation".
+#html_title = None
+
+# A shorter title for the navigation bar.  Default is the same as html_title.
+#html_short_title = None
+
+# The name of an image file (relative to this directory) to place at the top
+# of the sidebar.
+#html_logo = None
+
+# The name of an image file (within the static path) to use as favicon of the
+# docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
+# pixels large.
+#html_favicon = None
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+#html_static_path = ['_static']
+
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
+# using the given strftime format.
+#html_last_updated_fmt = '%b %d, %Y'
+
+# If true, SmartyPants will be used to convert quotes and dashes to
+# typographically correct entities.
+#html_use_smartypants = True
+
+# Custom sidebar templates, maps document names to template names.
+#html_sidebars = {}
+
+# Additional templates that should be rendered to pages, maps page names to
+# template names.
+#html_additional_pages = {}
+
+# If false, no module index is generated.
+#html_domain_indices = True
+
+# If false, no index is generated.
+#html_use_index = True
+
+# If true, the index is split into individual pages for each letter.
+#html_split_index = False
+
+# If true, links to the reST sources are added to the pages.
+#html_show_sourcelink = True
+
+# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
+#html_show_sphinx = True
+
+# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
+#html_show_copyright = True
+
+# If true, an OpenSearch description file will be output, and all pages will
+# contain a <link> tag referring to it.  The value of this option must be the
+# base URL from which the finished HTML is served.
+#html_use_opensearch = ''
+
+# This is the file name suffix for HTML files (e.g. ".xhtml").
+#html_file_suffix = None
+
+# Output file base name for HTML help builder.
+htmlhelp_basename = 'Grampsdoc'
+
+
+# -- Options for LaTeX output --------------------------------------------------
+
+latex_elements = {
+# The paper size ('letterpaper' or 'a4paper').
+#'papersize': 'letterpaper',
+
+# The font size ('10pt', '11pt' or '12pt').
+#'pointsize': '10pt',
+
+# Additional stuff for the LaTeX preamble.
+#'preamble': '',
+}
+
+# Grouping the document tree into LaTeX files. List of tuples
+# (source start file, target name, title, author, documentclass [howto/manual]).
+latex_documents = [
+  ('index', 'Gramps.tex', u'Gramps Documentation',
+   u'.', 'manual'),
+]
+
+# The name of an image file (relative to this directory) to place at the top of
+# the title page.
+#latex_logo = None
+
+# For "manual" documents, if this is true, then toplevel headings are parts,
+# not chapters.
+#latex_use_parts = False
+
+# If true, show page references after internal links.
+#latex_show_pagerefs = False
+
+# If true, show URL addresses after external links.
+#latex_show_urls = False
+
+# Documents to append as an appendix to all manuals.
+#latex_appendices = []
+
+# If false, no module index is generated.
+#latex_domain_indices = True
+
+
+# -- Options for manual page output --------------------------------------------
+
+# One entry per manual page. List of tuples
+# (source start file, name, description, authors, manual section).
+man_pages = [
+    ('cs', 'gramps', u'Gramps Documentation',
+     [u'.'], 1)
+]
+
+# If true, show URL addresses after external links.
+#man_show_urls = False
+
+
+# -- Options for Texinfo output ------------------------------------------------
+
+# Grouping the document tree into Texinfo files. List of tuples
+# (source start file, target name, title, author,
+#  dir menu entry, description, category)
+texinfo_documents = [
+  ('index', 'Gramps', u'Gramps Documentation',
+   u'.', 'Gramps', 'One line description of project.',
+   'Miscellaneous'),
+]
+
+# Documents to append as an appendix to all manuals.
+#texinfo_appendices = []
+
+# If false, no module index is generated.
+#texinfo_domain_indices = True
+
+# How to display URL addresses: 'footnote', 'no', or 'inline'.
+#texinfo_show_urls = 'footnote'

data/man/cs/cs.rst

@@ -0,0 +1,282 @@
+Czech
+======
+
+gramps(1)			     3.4.0			     gramps(1)
+
+
+
+**JMÉNO**
+       gramps - programový systém pro správu genealogického výzkumu a analýzy.
+
+
+**POUŽITÍ**
+       gramps	[-?|--help]  [--usage]	[--version]  [-l]  [-u|--force-unlock]
+       [-O|--open=  DATABÁZE  [-f|--format=  FORMÁT]]	[-i|--import=	SOUBOR
+       [-f|--format=   FORMÁT]]   [-i|--import=   ...]	 [-e|--export=	SOUBOR
+       [-f|--format= FORMÁT]] [-a|--action= AKCE] [-p|--options= PARAMETRY]] [
+       SOUBOR ] [--version]
+
+
+**POPIS**
+       Gramps  je  zdarma šířený Open Source genealogický program. Je napsán v
+       jazyce Python s využitím rozhraní  GTK+/GNOME.	Gramps	bude  povědomý
+       komukoli,  kdo už pracoval s jinými genealogickými programy jako Family
+       Tree Maker (TM),  Personal Ancestral  Files  (TM),  nebo  GNU  Geneweb.
+       Podporuje import dat z populárního formátu GEDCOM, který je celosvětově
+       rozšířen a je využíván téměř všemi ostatními genealogickými programy.
+
+
+**MOŽNOSTI**
+       **gramps** *SOUBOR*
+	      Pokud je zadán SOUBOR (bez dalších parametrů) jako název	rodok‐
+	      menu  nebo jako adresář databáze rodokmenu, je gramps otevřeno v
+	      interaktivním  módu.  Pokud  je  SOUBOR  formátem   podporovaným
+	      Gramps, je vytvořen rodokmen s názvem založeným na názvu souboru
+	      a data ze vstupu jsou do něho  naimportována.  Zbytek  parametrů
+	      příkazové  řádky je ignorován.  Tento způsob spouštění je vhodný
+	      pro gramps použitý jako prohlížeč genealogických dat  např.  pro
+	      webové  prohlížeče.   Spuštění  tímto způsobem zpracuje jakákoli
+	      data ve formátu podporovaném gramps, viz dále.
+
+
+       **-f** , **--format=** *FORMÁT*
+	      Explicitně definuje formát  SOUBORu  předchozího	parametru  -i,
+	      nebo  -e.  Pokud	není parametr -f pro SOUBOR specifikován, bude
+	      automaticky použit formát  odpovídající  koncovce  souboru  nebo
+	      MIME-typu.
+
+	      Formáty dostupné pro export jsou	gramps-xml (automaticky použit
+	      pokud má SOUBOR koncovku .gramps),  gedcom  (automaticky	použit
+	      pokud  má SOUBOR koncovku .ged), případně jiný další formát dos‐
+	      tupný prostřednictvím zásuvných modulů Gramps.
+
+	      Formáty dostupné	pro  import  jsou  grdb,  gramps-xml,  gedcom,
+	      gramps-pkg  (automaticky použit pokud má SOUBOR koncovku .gpkg),
+	      nebo geneweb (automaticky použit pokud má SOUBOR koncovku .gw).
+
+	      Formáty dostupné pro export jsou gramps-xml, gedcom, gramps-pkg,
+	      wft (automaticky použit pokud má SOUBOR koncovku .wft), geneweb,
+	      a iso (nikdy není použit automaticky, vždy musí být specifikován
+	      parametrem -f).
+
+
+       **-l**     
+          Vypíše seznam známých rodokmenů.
+
+
+       **-u** , **--force-unlock**
+	      Odemkne zamčenou databázi.
+
+
+       **-O** , **--open=** *DATABÁZE*
+	      Otevření *DATABÁZE* . Hodnota  musí  být  existujícím databázovým
+	      adresářem,  nebo	názvem	existujícího  rodokmenu.    Pokud   na
+	      příkazové  řádce nejsou žádné parametry importu nebo exportu, je
+	      nad danou databází spuštěna interaktivní relace.
+
+
+       **-i** , **--import=** *SOUBOR*
+	      Importuje data ze SOUBORu. Pokud není specifikována databáze, je
+	      použita dočasná. Ta je po ukončení gramps smazána.
+
+	      Pokud  je  předáván  více  než jeden vstup, musí každému souboru
+	      předcházet parametr -i.  Soubory jsou zpracovávány v  pořadí,  v
+	      jakém  byly zadány na příkazové řádce.  Např. -i SOUBOR1 -i SOU‐
+	      BOR2 a -i SOUBOR2 -i SOUBOR1 mohou vytvořit ve výsledné databázi
+	      různá gramps ID.
+
+
+       **-a** , **--action=** *AKCE*
+	      Provedení  AKCE  nad importovanými daty. Akce jsou spuštěny poté
+	      co jsou všechny importy dat úspěšně ukončeny. V tuto chvíli jsou
+	      podporovány    následující    akce:    summary	(stejné   jako
+	      Zprávy->Pohled->Souhrn), check (stejné  jako  Nástroje->Database
+	      Processing->Kontrola  a oprava), report (vytvoří zprávu), a tool
+	      (spustí nástroj zásuvného modulu).  Akce report a tool potřebují
+	      v PARAMETRY zadat parametr -p .
+
+	      PARAMETRY by měly splňovat následující kritéria:
+	      Nesmí  obsahovat žádné mezery.  Pokud některý argument potřebuje
+	      mezeru, musí být řetězec uzavřen v uvozovkách (držet se  syntaxe
+	      příkazové  řádky).   Řetězec  možností je seznam párů název=hod‐
+	      nota.  Jednotlivé páry musí být odděleny čárkami.
+
+	      Většina  možností  nástrojů  a  zpráv  jsou   specifickými   pro
+	      konkrétní  nástroj  nebo	zprávu.   Existují ale i takové, které
+	      jsou společné.
+
+	      **name=name**
+	      Povinná  předvolba  určující  který  nástroj  nebo  zpráva  bude
+	      spuštěna.    Pokud   zadané   name   neodpovídá  žádné  dostupné
+	      funkčnosti, vypíše se chybové hlášení následované seznamem  dos‐
+	      tupných nástrojů a zpráv (záleží na AKCE).
+
+	      **show=all**
+	      Vytvoří seznam názvů všech předvoleb dostupných pro danou zprávu
+	      nebo nástroj.
+
+	      **show=optionname**
+	      Vypíše popis všech  funkcionalit	poskytnutých  optionname,  ale
+	      také všechny přijatelné typy a hodnoty pro tuto volbu.
+
+	      Použijte	výše  popsané  volby  pro zjištění všech možností dané
+	      zprávy.
+
+
+       Pokud je zadána jedna nebo více výstupních akcí, každá musí být uvozena
+       předvolbou -a. Akce jsou prováděny jedna za druhou v zadaném pořadí.
+
+
+       **-d** , **--debug=** *LOGGER_NAME*
+	      Zapne  ladicí  výstup  pro vývoj a testování. Detaily najdete ve
+	      zdrojovém kódu.
+
+       **--version**
+	      Vytiskne číslo verze gramps a skončí
+
+
+
+
+**Chování**
+       Pokud první parametr  příkazové	řádky  nezačíná  pomlčkou,  pokusí  se
+       gramps  otevřít	soubor	s  názvem daným prvním argumentem na příkazové
+       řádce a spustit interaktivní  relaci.  Zbytek  argumentů  na  příkazové
+       řádce je v tomto případě ignorován.
+
+
+       Pokud  je  zadán  parametr  -O,	pak  se  gramps  snaží otevřít zadanou
+       databázi a pracovat s jejími daty  podle  instrukcí  dalších  parametrů
+       příkazové řádky.
+
+
+       S  nebo	bez  použití  parametru  -O  může  být provedeno více importů,
+       exportů, případně akcí daných argumenty příkazové řádky (-i, -e a -a).
+
+
+       Na pořadí parametrů -i, -e, nebo -a nezáleží.   Aktuální  pořadí  zpra‐
+       cování  je  vždy:  všechny  importy (pokud jsou nějaké) -> všechny akce
+       (pokud jsou nějaké) -> všechny exporty (pokud jsou  nějaké).   Parametr
+       otevření musí být ale vždy první!
+
+
+       Pokud  nejsou zadány -O nebo -i, gramps otevře své hlavní okno a spustí
+       se v obvyklém interaktivním módu s prázdnou databází.
+
+
+       Pokud nejsou zadány -e nebo -a, gramps otevře své hlavní okno a	spustí
+       se  v  ovbyklém interaktnivním módu s databází vzniklou výsledkem všech
+       importů.  Tato databáze je umístěna v souboru import_db.grdb v adresáři
+       ~/.gramps/import.
+
+
+       Chyba  vzniklá  při  importu,  exportu nebo akci bude vypsána na stdout
+       (pokud se jedná o vyjímku  ošetřenou  gramps)  nebo  na	stderr	(pokud
+       problém	není  ošetřen).  Pro  uložení zpráv a chyb do souboru použijte
+       obvyklá přesměrování výstupů stdout a stderr příkazové řádky.
+
+
+**PŘÍKLADY**
+       Otevření existujícího rodokmenu a import xml souboru do něho  může  být
+       proveden takto:
+       
+	      gramps -O 'Můj rodokmen' -i ~/db3.gramps
+
+       To  samé,  jen  s importem do dočasné databáze a otevřením interaktivní
+       relace:
+       
+	      gramps -i 'My Family Tree' -i ~/db3.gramps
+
+       Import čtyř databází (jejichž formáty jsou stanoveny podle  názvů  sou‐
+       borů)  a  následná  kontrola  bezchybnosti  výsledné  databáze může být
+       provedena takto:
+       
+	      gramps -i file1.ged -i file2.tgz -i ~/db3.gramps -i file4.wft -a
+	      check
+
+       Explicitní  specifikace	formátu databází předchozího příkladu přidáním
+       příslušného parametru -f za název souboru:
+       
+	      gramps -i file1.ged -f gedcom  -i  file2.tgz  -f	gramps-pkg  -i
+	      ~/db3.gramps -f gramps-xml -i file4.wft -f wft  -a check
+
+       Zapsání	výsledné  databáze vytvořené ze všech importů zajistí parametr
+       -e (použijte -f pokud nelze uhodnout formát z názvu souboru):
+       
+	      gramps -i file1.ged -i file2.tgz -e ~/nový-balíček -f gramps-pkg
+
+       Import tří databází a start interaktivní gramps relace nad výsledkem:
+       
+	      gramps -i file1.ged -i file2.tgz -i ~/db3.gramps
+
+       Spuštění nástroje kontroly z příkazové řádky s výstupem na stdout:
+       
+	      gramps -O 'Můj rodokmen' -a tool -p name=verify
+
+       A konečně spuštění normální interaktivní relace aplikace:
+       
+	      gramps
+
+
+**PROMĚNNÉ PROSTŘEDÍ**
+       Program kontroluje, zda jsou nastaveny následující proměnné:
+
+       **LANG** - popisuje, který jazyk bude použit: Příklad: pro češtinu musí mít
+       proměnná hodnotu cs_CZ.utf8.
+
+       **GRAMPSHOME**  -  pokud  je  nastavena,  Gramps  použije její hodnotu jako
+       adresář v němž jsou uložena nastavení a databáze.  Ve  výchozím	stavu,
+       kdy  proměnná není nastavena gramps předpokládá že adresář s databázemi
+       a nastavením bude vytvořen v adresáři s	uživatelským  profile  (popsán
+       proměnnou prostředí HOME v Linuxu nebo USERPROFILE ve Windows 2000/XP).
+
+
+**KONCEPTY**
+       gramps  podporuje  systém  zásuvných modulů založených na jazyku python
+       jehož prostřednictvím umožňuje přidání	import/export  modulů,	modulů
+       pro  vytváření  zpráv,  nástrojů  a  zobrazovacích  filtrů bez nutnosti
+       zásahu do hlavního programu.
+
+       Dále, krom možnosti přímého tisku,  dovoluje  směřovat  výstup  také  k
+       ostatním systémům a aplikacím jako např. OpenOffice.org, AbiWord, HTML,
+       nebo LaTeX. Tím dává možnost přizpůsobit formát požadavku uživatelů.
+
+
+**ZNÁMÉ CHYBY A OMEZENÍ**
+       nejsou
+
+
+**SOUBORY**
+
+       *${PREFIX}/bin/gramps*
+       
+       *${PREFIX}/lib/python/dist-packages/gramps/*
+       
+       *${PREFIX}/share/*
+       
+       *${HOME}/.gramps*
+
+
+**AUTOŘI**
+       Donald Allingham <don@gramps-project.org>
+       http://gramps-project.org/
+
+       Originální manuálovou stránku vytvořil:
+       Brandon L. Griffith <brandon@debian.org>
+       pro zařazení do systému Debian GNU/Linux.
+
+       Tuto manuálovou stránku přeložil a v současné době spravuje:
+       Zdeněk Hataš <zdenek.hatas@gmail.com>
+
+
+**DOKUMENTACE**
+       Uživatelská dokumentace je  k  dispozici  prostřednictvím  standardního
+       prohlížeče  nápovědy  GNOME  ve formě příručky Gramps. Příručka je také
+       dostupná ve formátu XML jako gramps-manual.xml v  adresáři  doc/gramps-
+       manual/$LANG v oficiální distribuci zdrojového kódu.
+
+       Dokumentace  pro  vývojáře  je  k  dispozici  na  webu
+       http://www.gramps-project.org/wiki/index.php?title=Portal:Developers
+
+
+
+Leden 2012			     3.4.0			     gramps(1)

data/man/en.rst

@@ -0,0 +1,299 @@
+English
+=======
+
+gramps(1)                @VERSION@               gramps(1)
+
+
+
+**NAME**
+       gramps - Genealogical Research and Analysis Management Programming Sys‐
+       tem.
+
+
+**SYNOPSIS**
+       **gramps** [**-?** | **--help**] [**--usage**] [**--version**]
+       [**-l**] [**-L**] [**-u** | **--force-unlock**] [**-O** | **--open=** *DATABASE*
+       [**-f** | **--format=** *FORMAT*] [**-i** | **--import=** *FILE*
+       [**-f** | **--format=** *FORMAT*]] [**--remove=** *FAMILY_TREE_PATTERN*]
+       [**-e** | **--export=** *FILE* [**-f** | **--format=** *FORMAT*]]
+       [**-a** | **--action=** *ACTION*] [*-p* | **--options=** *OPTION‐
+       STRING*]] [*FILE*] [**--version**]
+
+
+**DESCRIPTION**
+       Gramps is a Free/OpenSource genealogy program. It is written in Python,
+       using  the GTK+/GNOME interface.  Gramps should seem familiar to anyone
+       who has used other genealogy programs before such as Family Tree  Maker
+       (TM),   Personal Ancestral Files (TM), or the GNU Geneweb.  It supports
+       importing of the ever popular GEDCOM format which is used world wide by
+       almost all other genealogy software.
+
+
+**OPTIONS**
+       **gramps** *FILE*
+          When *FILE* is given (without any flags) as a family tree name or
+          as a family tree database directory, then it is opened and an
+          interactive  session is started. If *FILE* is a file format under‐
+          stood by Gramps, an empty family tree is created  whose name is
+          based  on  the *FILE* name and the data is imported into it. The
+          rest of the options is ignored. This way of launching is suit‐
+          able for using gramps as a handler for genealogical data in e.g.
+          web browsers. This invocation can accept any data format  native
+          to gramps, see below.
+
+
+       **-f** , **--format=** *FORMAT*
+          Explicitly specify format of *FILE* given by preceding **-i** ,
+          or **-e** option. If the **-f** option is not given for any
+          *FILE* , the format of that file is guessed according to its extension
+          or MIME-type.
+
+          Formats  available for export are **gramps-xml** (guessed if *FILE*
+          ends with **.gramps** ), **gedcom** (guessed if *FILE* ends with
+          **.ged** ), or any file export available through the Gramps plugin
+          system.
+
+          Formats available for import are **gramps-xml** , **gedcom** ,
+          **gramps-pkg** (guessed if *FILE* ends with **.gpkg** ),
+          and **geneweb** (guessed if *FILE* ends with **.gw** ).
+
+          Formats available for export are **gramps-xml** , **gedcom** ,
+          **gramps-pkg** , **wft** (guessed if *FILE* ends with **.wft** ),
+          **geneweb**.
+
+
+       **-l**
+          Print a list of known family trees.
+
+
+       **-L**
+          Print a detailed list of known family trees.
+
+
+       **-u** , **--force-unlock**
+          Unlock a locked database.
+
+
+       **-O** , **--open=** *DATABASE*
+          Open *DATABASE* which  must be an existing database directory or
+          existing family tree name. If no action, import or export
+          options are given on the command line then an interactive ses‐
+          sion is started using that database.
+
+
+       **-i** , **--import=** *FILE*
+          Import data from *FILE* . If you haven't specified a database, then
+          an empty database is created for you called Family Tree x
+          (where x is an incrementing number).
+
+          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.
+
+
+       **-e** , **--export=** *FILE*
+          Export data into *FILE* . For **gramps-xml** , **gedcom**
+          , **wft** , **gramps-pkg** , and **geneweb** , the *FILE* is the
+          name of the resulting file.
+
+          When more than one output file is given, each has to be preceded
+          by **-e** flag. The files are written one by one, in the specified order.
+
+
+       **-a** , **--action=** *ACTION*
+          Perform *ACTION* on the imported data. This is done after all
+          imports are successfully completed. Currently available  actions
+          are **summary** (same  as  Reports->View->Summary), **check** (same as
+          Tools->Database Processing->Check and Repair), **report** (generates
+          report),  and  tool  (runs a plugin tool).  Both **report** and **tool**
+          need the *OPTIONSTRING* supplied by the **-p** flag).
+
+          The *OPTIONSTRING* should satisfy the following conditions:
+          It must not contain any  spaces. If some arguments need to
+          include spaces, the string should be enclosed with quotation
+          marks, i.e., follow the shell syntax. Option string is a list
+          of  pairs  with name and value (separated by the equality sign).
+          The name and value pairs must be separated by commas.
+
+          Most of the report or tools options are specific for each report
+          or tool. However, there are some common options.
+
+          **name=name**
+          This mandatory option determines which report or tool will be
+          run. If the supplied name does not correspond to any  available
+          report or tool, an error message will be printed followed by the
+          list of available reports or tools (depending on the *ACTION* ).
+
+          **show=all**
+          This will produce the list of names for all options available
+          for a given report or tool.
+
+          **show=optionname**
+          This will print the description of the functionality supplied by
+          *optionname*, as well as what are the acceptable types and  values
+          for this option.
+
+          Use the above options to find out everything about a given
+          report.
+
+
+       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.
+
+
+       **-d** , **--debug=** *LOGGER_NAME*
+          Enables debug logs for development and testing. Look at the
+          source code for details
+
+       **--version**
+          Prints the version number of gramps and then exits
+
+
+
+
+**Operation**
+       If the first argument on the command line does not start with dash
+       (i.e. no flag), gramps will attempt to open the file with the name
+       given by the first argument and start interactive session, ignoring the
+       rest of the command line arguments.
+
+
+       If the  **-O** flag is given, then gramps will try opening the supplied
+       database and then work with that data, as instructed by the further
+       command line parameters.
+
+
+       With or without the **-O** flag, there could be multiple imports, exports,
+       and actions specified further on the command line by using **-i** ,
+       **-e** , and **-a** flags.
+
+
+       The order of **-i** , **-e** , or **-a** options does not matter. The actual order
+       always is: all imports (if any) -> all actions (if any) -> all  exports
+       (if any). But opening must always be first!
+
+
+       If no **-O** or **-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 **-e**  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 in the **import_db.grdb** under
+       **~/.gramps/import** directory.
+
+
+       The error encountered during import, export, or action, will be  either
+       dumped to stdout (if  these  are exceptions handled by gramps) 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 open an existing family tree and import an xml file into it, one
+       may type:
+
+          **gramps -O** *'My Family Tree'* **-i** *~/db3.gramps*
+
+       The above changes the opened family tree, to do the  same, but import
+       both in a temporary family tree and start an interactive session, one
+       may type:
+
+          **gramps -i** *'My Family Tree'* **-i** *~/db3.gramps*
+
+       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.gramps*
+          **-i** *file4.wft* **-a** *check*
+
+       To explicitly specify the formats in the above  example,  append  file‐
+       names with appropriate **-f** options:
+
+          **gramps -i** *file1.ged* **-f** *gedcom* **-i** *file2.tgz* **-f**
+          *gramps-pkg* **-i** *~/db3.gramps* **-f** *gramps-xml* **-i** *file4.wft*
+          **-f** *wft* **-a** *check*
+
+       To record the database resulting from all imports, supply **-e** flag  (use
+       **-f** if the filename does not allow gramps to guess the format):
+
+          **gramps -i** *file1.ged* **-i** *file2.tgz* **-e** *~/new-package*
+          **-f** *gramps-pkg*
+
+       To import three databases and start interactive gramps session with the
+       result:
+
+          **gramps -i** *file1.ged* **-i** *file2.tgz* **-i** *~/db3.gramps*
+
+       To run the Verify tool from the commandline and output the result to
+       stdout:
+
+          **gramps -O** *'My Family Tree'* **-a** *tool* **-p name=** *verify*
+
+       Finally, to start normal interactive session type:
+
+          **gramps**
+
+
+**ENVIRONMENT VARIABLES**
+       The program checks whether these environment variables are set:
+
+       **LANG**  -  describe, which language to use: Ex.: for polish language this
+       variable has to be set to pl_PL.UTF-8.
+
+       **GRAMPSHOME** - if set, force Gramps to use  the  specified  directory  to
+       keep program settings and databases there. By default, this variable is
+       not set and gramps assumes that the folder with all databases and  pro‐
+       file  settings  should  be  created  within  the  user  profile  folder
+       (described by environment variable HOME for Linux  or  USERPROFILE  for
+       Windows 2000/XP).
+
+
+**CONCEPTS**
+       Supports a python-based plugin system, allowing import and export writ‐
+       ers, report generators, tools, and display filters to be added  without
+       modification of the main program.
+
+       In addition to generating direct printer output, report generators also
+       target other systems, such as *LibreOffice.org* , *AbiWord* , *HTML*,
+       or *LaTeX* to allow the users to modify the format to suit their needs.
+
+
+**KNOWN BUGS AND LIMITATIONS**
+
+**FILES**
+
+       *${PREFIX}/bin/gramps*
+
+       *${PREFIX}/lib/python3/dist-packages/gramps/*
+
+       *${PREFIX}/share/*
+
+       *${HOME}/.gramps*
+
+
+**AUTHORS**
+       Donald Allingham <don@gramps-project.org>
+       http://gramps-project.org/
+
+       This man page was originally written by:
+       Brandon L. Griffith <brandon@debian.org>
+       for inclusion in the Debian GNU/Linux system.
+
+       This man page is currently maintained by:
+       Gramps project <xxx@gramps-project.org>
+
+
+**DOCUMENTATION**
+       The user documentation is available through standard web browser
+       in the form of Gramps Manual.
+
+       The developer documentation can be found on the
+       http://www.gramps-project.org/wiki/index.php?title=Portal:Developers
+       portal.
+
+
+
+gramps(1)                 @VERSION@               gramps(1)

data/man/fr/Makefile.am

@@ -1,14 +0,0 @@
-# This is the data/man/fr level Makefile for Gramps
-# $Id$
-
-man_IN_FILES = gramps.1.in
-man_MANS = $(man_IN_FILES:.1.in=.1)
-
-mandir = @mandir@/fr
-
-EXTRA_DIST = $(man_MANS) $(man_IN_FILES)
-
-gramps.1: $(top_builddir)/config.status gramps.1.in
-	cd $(top_builddir) && CONFIG_FILES=data/man/fr/$@ $(SHELL) ./config.status
-
-CLEANFILES=$(man_MANS)

data/man/fr/conf.py

@@ -0,0 +1,243 @@
+# -*- coding: utf-8 -*-
+#
+# Gramps documentation build configuration file, created by
+# sphinx-quickstart on Sat Dec  1 14:38:29 2012.
+#
+# This file is execfile()d with the current directory set to its containing dir.
+#
+# Note that not all possible configuration values are present in this
+# autogenerated file.
+#
+# All configuration values have a default; values that are commented out
+# serve to show the default.
+
+import sys, os
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+#sys.path.insert(0, os.path.abspath('.'))
+
+# -- General configuration -----------------------------------------------------
+
+# If your documentation needs a minimal Sphinx version, state it here.
+#needs_sphinx = '1.0'
+
+# Add any Sphinx extension module names here, as strings. They can be extensions
+# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+extensions = []
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ['_templates']
+
+# The suffix of source filenames.
+source_suffix = '.rst'
+
+# The encoding of source files.
+#source_encoding = 'utf-8-sig'
+
+# The master toctree document.
+master_doc = 'fr'
+
+# General information about the project.
+project = u'Gramps'
+copyright = u'2015, Gramps project'
+
+# The version info for the project you're documenting, acts as replacement for
+# |version| and |release|, also used in various other places throughout the
+# built documents.
+#
+# The short X.Y version.
+version = '4.2'
+# The full version, including alpha/beta/rc tags.
+release = '4.2.0'
+
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+locale_dirs = './locale'
+gettext_compact = True
+
+# There are two options for replacing |today|: either, you set today to some
+# non-false value, then it is used:
+#today = ''
+# Else, today_fmt is used as the format for a strftime call.
+today_fmt = '%d %B %Y'
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+exclude_patterns = ['_build']
+
+# The reST default role (used for this markup: `text`) to use for all documents.
+#default_role = None
+
+# If true, '()' will be appended to :func: etc. cross-reference text.
+#add_function_parentheses = True
+
+# If true, the current module name will be prepended to all description
+# unit titles (such as .. function::).
+#add_module_names = True
+
+# If true, sectionauthor and moduleauthor directives will be shown in the
+# output. They are ignored by default.
+#show_authors = False
+
+# The name of the Pygments (syntax highlighting) style to use.
+pygments_style = 'sphinx'
+
+# A list of ignored prefixes for module index sorting.
+#modindex_common_prefix = []
+
+
+# -- Options for HTML output ---------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages.  See the documentation for
+# a list of builtin themes.
+html_theme = 'default'
+
+# Theme options are theme-specific and customize the look and feel of a theme
+# further.  For a list of options available for each theme, see the
+# documentation.
+#html_theme_options = {}
+
+# Add any paths that contain custom themes here, relative to this directory.
+#html_theme_path = []
+
+# The name for this set of Sphinx documents.  If None, it defaults to
+# "<project> v<release> documentation".
+#html_title = None
+
+# A shorter title for the navigation bar.  Default is the same as html_title.
+#html_short_title = None
+
+# The name of an image file (relative to this directory) to place at the top
+# of the sidebar.
+#html_logo = None
+
+# The name of an image file (within the static path) to use as favicon of the
+# docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
+# pixels large.
+#html_favicon = None
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+#html_static_path = ['_static']
+
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
+# using the given strftime format.
+#html_last_updated_fmt = '%b %d, %Y'
+
+# If true, SmartyPants will be used to convert quotes and dashes to
+# typographically correct entities.
+#html_use_smartypants = True
+
+# Custom sidebar templates, maps document names to template names.
+#html_sidebars = {}
+
+# Additional templates that should be rendered to pages, maps page names to
+# template names.
+#html_additional_pages = {}
+
+# If false, no module index is generated.
+#html_domain_indices = True
+
+# If false, no index is generated.
+#html_use_index = True
+
+# If true, the index is split into individual pages for each letter.
+#html_split_index = False
+
+# If true, links to the reST sources are added to the pages.
+#html_show_sourcelink = True
+
+# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
+#html_show_sphinx = True
+
+# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
+#html_show_copyright = True
+
+# If true, an OpenSearch description file will be output, and all pages will
+# contain a <link> tag referring to it.  The value of this option must be the
+# base URL from which the finished HTML is served.
+#html_use_opensearch = ''
+
+# This is the file name suffix for HTML files (e.g. ".xhtml").
+#html_file_suffix = None
+
+# Output file base name for HTML help builder.
+htmlhelp_basename = 'Grampsdoc'
+
+
+# -- Options for LaTeX output --------------------------------------------------
+
+latex_elements = {
+# The paper size ('letterpaper' or 'a4paper').
+#'papersize': 'letterpaper',
+
+# The font size ('10pt', '11pt' or '12pt').
+#'pointsize': '10pt',
+
+# Additional stuff for the LaTeX preamble.
+#'preamble': '',
+}
+
+# Grouping the document tree into LaTeX files. List of tuples
+# (source start file, target name, title, author, documentclass [howto/manual]).
+latex_documents = [
+  ('index', 'Gramps.tex', u'Gramps Documentation',
+   u'.', 'manual'),
+]
+
+# The name of an image file (relative to this directory) to place at the top of
+# the title page.
+#latex_logo = None
+
+# For "manual" documents, if this is true, then toplevel headings are parts,
+# not chapters.
+#latex_use_parts = False
+
+# If true, show page references after internal links.
+#latex_show_pagerefs = False
+
+# If true, show URL addresses after external links.
+#latex_show_urls = False
+
+# Documents to append as an appendix to all manuals.
+#latex_appendices = []
+
+# If false, no module index is generated.
+#latex_domain_indices = True
+
+
+# -- Options for manual page output --------------------------------------------
+
+# One entry per manual page. List of tuples
+# (source start file, name, description, authors, manual section).
+man_pages = [
+    ('fr', 'gramps', u'Gramps Documentation',
+     ['Jerome Rapinat'], 1)
+]
+
+# If true, show URL addresses after external links.
+#man_show_urls = False
+
+
+# -- Options for Texinfo output ------------------------------------------------
+
+# Grouping the document tree into Texinfo files. List of tuples
+# (source start file, target name, title, author,
+#  dir menu entry, description, category)
+texinfo_documents = [
+  ('index', 'Gramps', u'Gramps Documentation',
+   u'.', 'Gramps', 'One line description of project.',
+   'Miscellaneous'),
+]
+
+# Documents to append as an appendix to all manuals.
+#texinfo_appendices = []
+
+# If false, no module index is generated.
+#texinfo_domain_indices = True
+
+# How to display URL addresses: 'footnote', 'no', or 'inline'.
+#texinfo_show_urls = 'footnote'

data/man/fr/fr.rst

@@ -0,0 +1,299 @@
+French
+=======
+
+gramps(1)                @VERSION@               gramps(1)
+
+
+**NOM**
+       gramps - Gramps est une application de généalogie. Gramps est
+       l'acronyme de Genealogical Research and Analysis Management Programming
+       System (Systeme de Programmation pour Recherche, Analyse et Gestion de
+       données généalogiques)
+
+
+**SYNOPSIS**
+       **gramps** [**-?** | **--help**] [**--usage**] [**--version**]
+       [**-l**] [**-L**] [**-u** | **--force-unlock**] [**-O** | **--open=** *BASE_DE_DONNEES*]
+       [**-f** | **--format=** *FORMAT*] [**-i** | **--import=** *FICHIER*]
+       [**-e** | **--export=** *FICHIER*] [**--remove=** *FAMILY_TREE_PATTERN*]
+       [**-a** | **--action=** *ACTION* [*-p* | **--options=** *CHAÎNE‐
+       OPTION*]] [*FICHIER*] [**--version**]
+
+
+**DESCRIPTION**
+       Gramps est un programme Libre/OpenSource de généalogie. Il est écrit en
+       python, et utilise une interface GTK+/GNOME. Gramps est semblable à
+       d'autres programmes de généalogie tel  que  Family Tree Maker (FTM),
+       Personal Ancestral Files, ou le programme GNU Geneweb. Il peut
+       importer/exporter le format le plus utilisé par les autres logiciels de
+       généalogie : GEDCOM.
+
+
+**OPTIONS**
+       **gramps** *FICHIER*
+          Si *FICHIER* est désigné (sans autres commandes) comme arbre
+          familial ou comme répertoire d'arbre familial, alors une session
+          interactive est ouverte. Si *FICHIER* est un format de fichier
+          supporté par Gramps, une base vide est créée  dont le nom est
+          celui du *FICHIER* et les données y seront importées. Les autres
+          options sont ignorées. Ce type de lancement permet d'utiliser
+          gramps  pour manipuler des données comme dans un navigateur web.
+          Les formats natifs de gramps sont acceptés, voir ci-dessous.
+
+
+       **-f** , **--format=** *FORMAT*
+          Le format spécifique du *FICHIER* est précédé par les arguments
+          **-i** , ou **-e** . Si l'option **-f** n'est pas donnée pour le *FICHIER* ,
+          alors le format sera celui de l'extension ou du type-MIME.
+
+          Les formats de sortie disponibles sont **gramps-xml** (deviné si
+          *FICHIER* se termine par **.gramps** ), et **gedcom** (deviné si *FICHIER* se
+          termine  par **.ged** ), ou tout autre fichier d'exportation
+          disponible dans le système de plugin Gramps.
+
+          Les formats disponibles pour l'importation sont  **grdb** ,
+          **gramps-xml** , **gedcom** , **gramps-pkg** (deviné si *FICHIER* se termine par
+          **.gpkg** ), et **geneweb** (deviné si *FICHIER* se termine par **.gw** ).
+
+          Les formats disponibles pour l'exportation sont **gramps-xml** , **ged‐
+          com** , **gramps-pkg** , **wft** (deviné si *FICHIER* se termine par **.wft** ),
+          **geneweb** .
+
+
+       **-l**
+          Imprime une liste des arbres familiaux disponibles.
+
+
+       **-u** , **--force-unlock**
+          Débloquer une base de données verrouillée.
+
+
+       **-O** , **--open=** *BASE_DE_DONNEES*
+          Ouvrir une *BASE_DE_DONNEES* qui doit être une base présente dans
+          le répertoire des bases ou le nom d'un arbre familial existant.
+          Si aucune action n'est définie, les options d'import ou d'export
+          sont données par la ligne de commande puis une session interactive
+          est ouverte, utilisant cette base de données.
+
+          Seulement une base peut être ouverte. Si vous utilisez plusieurs
+          sources, vous devez utiliser l'option d'import.
+
+
+       **-i** , **--import=** *FICHIER*
+          Importer des données depuis un *FICHIER* . Si vous n'avez pas
+          spécifié de base de données, alors une base de données vide
+          est utilisée.
+
+          Quand plus d'un fichier doit être importé, chacun doit être
+          précédé par la commande **-i** . Ces fichiers sont importés dans le
+          même ordre,  **-i** *FICHIER1* **-i** *FICHIER2* et **-i** *FICHIER2* **-i**
+          *FICHIER1* vont tous les deux produire différents IDs gramps.
+
+
+       **-e** , **--export=** *FICHIER*
+          Exporter des données dans un *FICHIER* . Pour les fichiers **gramps-xml**
+          , **gedcom** , **wft** , **gramps-pkg** , et **geneweb** , le
+          *FICHIER* est le nom du fichier de sortie.
+
+          Quand plus d'un fichier doit être exporté, chacun doit être
+          précédé par la commande **-e** . Ces fichiers sont importés dans le
+          même ordre.
+
+
+       **-a** , **--action=** *ACTION*
+          Accomplir une *ACTION* sur les données importées. C'est effectué à
+          la fin de l'importation. Les actions possibles sont **summary**
+          (comme le rapport -> Afficher -> Statistiques sur la base),
+          **check** (comme l'outil -> Réparation de la base -> Vérifier et
+          réparer), **report** (produit un rapport) et **tool** (utilise un
+          outil), ces derniers ont besoin de *OPTION* précédé par la commande -p.
+
+          L' *OPTION* doit satisfaire ces conditions:
+          Il ne doit pas y avoir d'espace. Si certains arguments doivent
+          utiliser des espaces, la chaîne doit être encadrée par des
+          guillemets. Les options vont par paire nom et valeur. Une
+          paire est séparée par un signe égal. Différentes paires sont
+          séparées par une virgule.
+
+          La plupart des options sont spécifiques à chaque rapport. Même
+          s'il existe des options communes.
+
+          **name=name**
+          Cette option est obligatoire, elle détermine quel rapport ou
+          outil sera utilisé. Si le name saisi ne correspond à aucun
+          module disponible, un message d'erreur sera ajouté.
+
+          **show=all**
+          Cette option produit une liste avec les noms des options
+          disponibles pour un rapport donné.
+
+          **show=optionname**
+          Cette option affiche une description de toutes les fonctionnalités
+          proposées par optionname, aussi bien les types que les valeurs pour une option.
+
+          Utiliser les options ci-dessus pour trouver tout sur un rapport
+          choisi.
+
+
+       Quand plus d'une action doit être effectuée, chacune doit être précédée
+       par la commande **-a** . Les actions seront réalisées une à une, dans
+       l'ordre spécifié.
+
+
+       **-d** , **--debug=** *NOM_LOGGER*
+          Permet les logs de debug pour le développement et les tests.
+          Regarder le code source pour les détails.
+
+       **--version**
+          Imprime le numéro de version pour gramps puis quitte.
+
+
+
+
+**Opération**
+       Si le premie argument de la ligne de commande ne commence pas par un
+       tiret (i.e. pas d'instruction), gramps va essayer d'ouvrir la base de
+       données avec le nom donné par le premier argument et démarrer une ses‐
+       sion interactive, en ignorant le reste de la ligne de commande.
+
+
+       Si la commande **-O** est notée, alors gramps va essayer le fichier défini
+       et va travailler avec ses données, comme pour les autres paramètres de
+       la ligne de commande.
+
+
+       Avec ou sans la commande **-O** , il peut y avoir plusieurs imports,
+       exports, et actions dans la ligne de commande **-i** , **-e** , et **-a** .
+
+
+       L'ordre des options **-i** , **-e** , ou **-a** n'a pas de sens. L'ordre actuel est
+       toujours : imports -> actions -> exports. Mais l'ouverture doit toujours
+       être la première !
+
+
+       Si aucune option **-O** ou **-i** n'est donnée, gramps lancera sa propre
+       fenêtre et demarrera avec une base vide, puisqu'il n'y a pas données.
+
+
+       Si aucune option **-e** ou **-a** n'est donnée, gramps lancera sa propre
+       fenêtre et démarrera avec la base de données issue de tout les imports.
+       Cette base sera **import_db.grdb** dans le répertoire **~/.gramps/import**.
+
+
+       Les erreurs  rencontrées lors d'importation, d'exportation, ou d'action, seront
+       mémorisées en *stdout* (si elles sont le fait de la manipulation par
+       gramps) ou en *stderr* (si elles ne sont pas le fait d'une manipulation).
+       Utilisez les shell de redirection de *stdout* et *stderr* pour sauver
+       les messages et les erreurs dans les fichiers.
+
+
+**EXEMPLES**
+       Pour ouvrir un arbre familial et y importer un fichier XML, on peut
+       saisir:
+
+          **gramps -O** *'Mon Arbre Familial'* **-i** *~/db3.gramps*
+
+       Ceci ouvre un arbre familial, pour faire la même chose, mais importer
+       dans un arbre familial temporaire et démarrer une session interactive,
+       on peut saisir :
+
+          **gramps -i** *'Mon Arbre Familial'* **-i** *~/db3.gramps*
+
+       Lecture de quatre bases de données dont les formats peuvent être
+       devinés d'après les noms, puis vérification des données:
+
+          **gramps -i** *file1.ged* **-i** *file2.tgz* **-i** *~/db3.gramps*
+          **-i** *file4.wft* **-a** *check*
+
+       Si vous voulez préciser lesformats de fichiers dans l'exemple ci-
+       dessus, complétez les noms de fichiers par les options -f appropriées:
+
+          **gramps -i** *file1.ged* **-f** *gedcom* **-i** *file2.tgz* **-f**
+          *gramps-pkg* **-i** *~/db3.gramps* **-f** *gramps-xml* **-i** *file4.wft*
+          **-f** *wft* **-a** *check*
+
+       Pour enregistrer le résultat des lectures, donnez l'option **-e**
+       (utiliser -f si le nom de fichier ne permet pas à gramps de deviner le
+       format):
+
+          **gramps -i** *file1.ged* **-i** *file2.tgz* **-e** *~/new-package*
+          **-f** *gramps-pkg*
+
+       Pour lire trois ensembles de données puis lancer une session
+       interactive de gramps sur le tout :
+
+          **gramps -i** *file1.ged* **-i** *file2.tgz* **-i** *~/db3.gramps*
+
+       Pour lancer l'outil de vérification de la base de données depuis la
+       ligne de commande et obtenir le résultat :
+
+          **gramps -O** *'My Family Tree'* **-a** *tool* **-p name=** *verify*
+
+       Enfin, pour lancer une session interactive normale, entrer :
+
+          **gramps**
+
+
+**VARIABLES D'ENVIRONMENT**
+       Le programme vérifie si ces variables d'environnement sont déclarées:
+
+       **LANG** - décrit, quelle langue est utilisée: Ex.: pour le français on
+       peut définir fr_FR.UTF-8.
+
+       **GRAMPSHOME**  - si  défini, force Gramps à utiliser un répertoire
+       spécifique pour y conserver ses préférences et bases de données. Par
+       défaut, cette variable n'est pas active et Gramps sait que les options
+       et bases de données doivent être créées dans le répertoire par défaut
+       de l'utilisateur (la variable d'environnement HOME pour Linux ou USER‐
+       PROFILE pour Windows 2000/XP).
+
+
+**CONCEPTS**
+       Gramps est un système basé sur le support de plugin-python, permettant
+       d'importer et d'exporter, la saisie, générer des rapports, des outils,
+       et afficher des filtres pouvant être ajoutés sans modifier le programme.
+
+       Par ailleurs, gramps permet la génération directe : impression, rap‐
+       ports avec sortie vers d'autres formats, comme *LibreOffice.org* ,
+       *HTML* , ou *LaTeX* pour permettre à l'utilisateur de choisir selon ses
+       besoins
+
+
+**BUGS CONNUS ET LIMITATIONS**
+
+**FICHIERS**
+
+       *${PREFIX}/bin/gramps*
+
+       *${PREFIX}/lib/python3/dist-packages/gramps/*
+
+       *${PREFIX}/share/*
+
+       *${HOME}/.gramps*
+
+
+**AUTEURS**
+       Donald Allingham <don@gramps-project.org>
+       http://gramps-project.org/
+
+       Cette page man a d'abord été écrite par :
+       Brandon L. Griffith <brandon@debian.org>
+       pour Debian GNU/Linux système.
+
+       Cette page man est maintenue par :
+       Gramps project <xxx@gramps-project.org>
+
+       La traduction française :
+       Jérôme Rapinat <romjerome@yahoo.fr>
+
+
+**DOCUMENTATION**
+       La documentation-utilisateur est disponible par un navigateur
+       standard sous la forme du manuel Gramps.
+
+       La documentation pour développeur est disponible sur le site
+       http://www.gramps-project.org/wiki/index.php?title=Portal:Developers .
+
+
+
+gramps(1)                 @VERSION@               gramps(1)

data/man/fr/gramps.1.in

@@ -1,290 +1,337 @@
-.TH gramps 1 "@VERSION@" "Mars 2009" "@VERSION@"
-.SH NOM
-gramps \- Gramps est une application de généalogie. Gramps est l'acronyme de Genealogical Research and Analysis Management Programming System (Systeme de Programmation pour Recherche, Analyse et Gestion de données généalogiques)
-
-.SH SYNOPSIS
-.B gramps
-.RB [ \-?|\-\^\-help ]
-.RB [ \-\^\-usage ]
-.RB [ \-\^\-version ]
-.RB [ \-l]
-.RB [ \-u|\-\^\-force-unlock ]
-.RB [ \-O|\-\^\-open=
-.IR BASE_DE_DONNEES 
-.RB [ \-f|\-\^\-format= 
-.IR FORMAT ]] 
-.RB [ \-i|\-\^\-import=
-.IR FICHIER 
-.RB [ \-f|\-\^\-format= 
-.IR FORMAT ]] 
-.RB [ \-i|\-\^\-import= 
-.IR ... ] 
-.RB [ \-e|\-\^\-export= 
-.IR FICHIER
-.RB [ \-f|\-\^\-format= 
-.IR FORMAT ]] 
-.RB [ \-a|\-\^\-action= 
-.IR ACTION ]
-.RB [ \-p|\-\^\-options= 
-.IR OPTION ]] 
-.RB [
-.IR FICHIER
-.RB ]
-.if 0 .RB [ bonobo\ options ]
-.if 0 .RB [ sound\ options ]
-.RB [ \-\-version ]
-
-.SH DESCRIPTION
-.PP 
-\fIGramps\fP est un programme Libre/OpenSource de généalogie. Il est écrit en python, 
-et utilise une interface GTK+/GNOME.
-Gramps est semblable à d'autres programmes de généalogie tel que \fIFamily Tree Maker (FTM)\fR,  \fIPersonal Ancestral
-Files\fR, ou le programme GNU Geneweb.
-Il peut importer/exporter le format le plus utilisé par les autres logiciels de généalogie : GEDCOM.
-
-.SH OPTIONS
-.TP 
-.BI gramps " FICHIER" 
-Si \fIFICHIER\fR est désigné (sans autres commandes) comme arbre familial ou comme répertoire d'arbre familial, alors une session interactive est ouverte. Si FICHIER est un format de fichier supporté par Gramps, une base vide est créée dont le nom est celui du \fIFICHIER\fP et les données y seront importées. Les autres options sont ignorées. Ce type de lancement permet d'utiliser gramps pour manipuler des données comme dans un navigateur web. Les formats natifs de gramps sont acceptés, voir ci-dessous.
-.br
-
-.TP 
-.BI \-f,\-\^\-format= " FORMAT"
-Le format spécifique du \fIFICHIER\fR est précédé par les arguments
-.ig
-\fB\-O\fR,
+.\" Man page generated from reStructuredText.
+.
+.TH FRENCH  "" "" ""
+.SH NAME
+French \- 
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
 ..
-\fB\-i\fR, ou
-\fB\-e\fR. Si l'option \fB\-f\fR n'est pas donnée pour le \fIFICHIER\fR, alors le format sera celui de l'extension ou du type-MIME.
-.br
-
-Les formats de sortie disponibles sont \fBgramps\-xml\fR (deviné si \fIFICHIER\fR se termine par
-\fB.gramps\fR), et \fBgedcom\fR (deviné si \fIFICHIER\fR se termine par \fB.ged\fR), ou
-tout autre fichier d'exportation disponible dans le système de plugin Gramps.
-.br
-
-Les formats disponibles pour l'importation sont \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR,  
-\fBgramps\-pkg\fR (deviné si \fIFICHIER\fR se termine par \fB.gpkg\fR), et
-\fBgeneweb\fR (deviné si \fIFICHIER\fR se termine par \fB.gw\fR). 
-.br
-
-Les formats disponibles pour l'exportation sont  
-.ig
-\fBgrdb\fR,
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
 ..
-\fBgramps\-xml\fR, \fBgedcom\fR,
-\fBgramps\-pkg\fR, \fBwft\fR (deviné si \fIFICHIER\fR se termine par \fB.wft\fR),
-\fBgeneweb\fR, et \fBiso\fR (jamais deviné, toujours spécifié avec l'option
-\fB\-f\fR).
-
-.TP 
-.BI \-l
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.sp
+gramps(1)                @VERSION@               gramps(1)
+.INDENT 0.0
+.TP
+.B \fBNOM\fP
+gramps \- Gramps est une application de généalogie. Gramps est
+l\(aqacronyme de Genealogical Research and Analysis Management Programming
+System (Systeme de Programmation pour Recherche, Analyse et Gestion de
+données généalogiques)
+.TP
+.B \fBSYNOPSIS\fP
+\fBgramps\fP [\fB\-?\fP | \fB\-\-help\fP] [\fB\-\-usage\fP] [\fB\-\-version\fP]
+[\fB\-l\fP] [\fB\-L\fP] [\fB\-u\fP | \fB\-\-force\-unlock\fP] [\fB\-O\fP | \fB\-\-open=\fP \fIBASE_DE_DONNEES\fP]
+[\fB\-f\fP | \fB\-\-format=\fP \fIFORMAT\fP] [\fB\-i\fP | \fB\-\-import=\fP \fIFICHIER\fP]
+[\fB\-e\fP | \fB\-\-export=\fP \fIFICHIER\fP] [\fB\-\-remove=\fP \fIFAMILY_TREE_PATTERN\fP]
+[\fB\-a\fP | \fB\-\-action=\fP \fIACTION\fP [\fI\-p\fP | \fB\-\-options=\fP \fICHAÎNE‐
+OPTION\fP]] [\fIFICHIER\fP] [\fB\-\-version\fP]
+.TP
+.B \fBDESCRIPTION\fP
+Gramps est un programme Libre/OpenSource de généalogie. Il est écrit en
+python, et utilise une interface GTK+/GNOME. Gramps est semblable à
+d\(aqautres programmes de généalogie tel  que  Family Tree Maker (FTM),
+Personal Ancestral Files, ou le programme GNU Geneweb. Il peut
+importer/exporter le format le plus utilisé par les autres logiciels de
+généalogie : GEDCOM.
+.TP
+.B \fBOPTIONS\fP
+.INDENT 7.0
+.TP
+.B \fBgramps\fP \fIFICHIER\fP
+Si \fIFICHIER\fP est désigné (sans autres commandes) comme arbre
+familial ou comme répertoire d\(aqarbre familial, alors une session
+interactive est ouverte. Si \fIFICHIER\fP est un format de fichier
+supporté par Gramps, une base vide est créée  dont le nom est
+celui du \fIFICHIER\fP et les données y seront importées. Les autres
+options sont ignorées. Ce type de lancement permet d\(aqutiliser
+gramps  pour manipuler des données comme dans un navigateur web.
+Les formats natifs de gramps sont acceptés, voir ci\-dessous.
+.TP
+.B \fB\-f\fP , \fB\-\-format=\fP \fIFORMAT\fP
+Le format spécifique du \fIFICHIER\fP est précédé par les arguments
+\fB\-i\fP , ou \fB\-e\fP . Si l\(aqoption \fB\-f\fP n\(aqest pas donnée pour le \fIFICHIER\fP ,
+alors le format sera celui de l\(aqextension ou du type\-MIME.
+.sp
+Les formats de sortie disponibles sont \fBgramps\-xml\fP (deviné si
+\fIFICHIER\fP se termine par \fB\&.gramps\fP ), et \fBgedcom\fP (deviné si \fIFICHIER\fP se
+termine  par \fB\&.ged\fP ), ou tout autre fichier d\(aqexportation
+disponible dans le système de plugin Gramps.
+.sp
+Les formats disponibles pour l\(aqimportation sont  \fBgrdb\fP ,
+\fBgramps\-xml\fP , \fBgedcom\fP , \fBgramps\-pkg\fP (deviné si \fIFICHIER\fP se termine par
+\fB\&.gpkg\fP ), et \fBgeneweb\fP (deviné si \fIFICHIER\fP se termine par \fB\&.gw\fP ).
+.sp
+Les formats disponibles pour l\(aqexportation sont \fBgramps\-xml\fP , \fBged‐
+com\fP , \fBgramps\-pkg\fP , \fBwft\fP (deviné si \fIFICHIER\fP se termine par \fB\&.wft\fP ),
+\fBgeneweb\fP .
+.TP
+.B \fB\-l\fP
 Imprime une liste des arbres familiaux disponibles.
-
 .TP
-.BI \-u,\-\^\-force-unlock
+.B \fB\-u\fP , \fB\-\-force\-unlock\fP
 Débloquer une base de données verrouillée.
-
-.TP 
-.BI \-O,\-\^\-open= " BASE_DE_DONNEES"
-Ouvrir une \fIBASE_DE_DONNEES\fR qui doit être une base présente dans le répertoire des bases ou le nom d'un arbre familial existant.
-Si aucune action n'est définie, les options d'import ou d'export sont données par la ligne de commande puis une session interactive est ouverte, utilisant cette base de données.
-.br
-
-Seulement une base peut être ouverte. Si vous utilisez plusieurs sources, vous devez utiliser l'option d'import.
-
-.TP 
-.BI \-i,\-\^\-import= " FICHIER"
-Importer des données depuis un \fIFICHIER\fR. Si vous n'avez pas spécifié de base de données alors une base de données temporaire est utilisée; elle sera effacée quand vous quitterez gramps.
-.br
-
-Quand plus d'un fichier doit être importé, chacun doit être précédé par la commande \fB\-i\fR. Ces fichiers sont importés dans le même ordre, 
-i.e. \fB\-i\fR \fIFICHIER1\fR \fB\-i\fR \fIFICHIER2\fR  
-et \fB\-i\fR \fIFICHIER2\fR \fB\-i\fR \fIFICHIER1\fR vont tous les deux produire différents IDs gramps.
-
-.TP 
-.BI \-e,\-\^\-export= " FICHIER"
-Exporter des données dans un \fIFICHIER\fR. Pour le format \fBiso\fR, le \fIFICHIER\fR est le nom du répertoire dans lequel la base de données gramps est écrite.
-Pour 
-.ig
-\fBgrdb\fR,
-..
-\fBgramps\-xml\fR, \fBgedcom\fR, \fBwft\fR, \fBgramps\-pkg\fR, 
-et \fBgeneweb\fR, le \fIFICHIER\fR est le nom du fichier de sortie 
-.br
-
-Quand plus d'un fichier doit être exporté, chacun doit être précédé par la commande \fB\-e\fR. Ces fichiers sont importés dans le même ordre.
-
-.TP 
-.BI \-a,\-\^\-action= " ACTION"
-Accomplir une \fIACTION\fR sur les données importées. C'est effectué à la fin de l'importation. Les actions possibles sont \fBsummary\fR 
-(comme le rapport -> Afficher -> Statistiques sur la base), \fBcheck\fR (comme l'outil -> Réparation de la base -> Vérifier et réparer), \fBreport\fR (produit un rapport) et
-\fBtool\fR (utilise un outil), ces derniers ont besoin
-de \fIOPTION\fR précédé par la commande \fB\-p\fR.
-.br
-
-L'\fIOPTION\fR doit satisfaire ces conditions:
-.br
-Il ne doit pas y avoir d'espace. 
-Si certains arguments doivent utiliser des espaces, la chaîne doit être encadrée par des guillemets.
-Les options vont par paire nom et valeur.
-Une paire est séparée par un signe égal.
-Différentes paires sont séparées par une virgule.
-.br
-
-La plupart des options sont spécifiques à chaque rapport. Même s'il existe des options communes.
-
-.BI "name=name"
-.br
-Cette option est obligatoire, elle détermine quel rapport ou outil sera utilisé. Si le \fIname\fR saisi ne correspond à aucun module disponible, un message d'erreur sera ajouté.
-
-.BI "show=all"
-.br
-Cette option produit une liste avec les noms des options disponibles pour un rapport donné.
-
-.BI "show="optionname
-.br
-Cette option affiche une description de toutes les fonctionnalités proposées par \fIoptionname\fR, aussi bien les types que les valeurs pour une option.
-
-.br
-Utiliser les options ci-dessus pour trouver tout sur un rapport choisi.
-
-.LP
-Quand plus d'une action doit être effectuée, chacune doit être précédée par la commande \fB\-a\fR. Les actions seront réalisées une à une, dans l'ordre spécifié.
-
-.TP 
-.BI \-d,\-\^\-debug= " NOM_LOGGER"
-Permet les logs de debug pour le développement et les tests. Regarder le code source pour les détails.
 .TP
-.BI \-\^\-version
+.B \fB\-O\fP , \fB\-\-open=\fP \fIBASE_DE_DONNEES\fP
+Ouvrir une \fIBASE_DE_DONNEES\fP qui doit être une base présente dans
+le répertoire des bases ou le nom d\(aqun arbre familial existant.
+Si aucune action n\(aqest définie, les options d\(aqimport ou d\(aqexport
+sont données par la ligne de commande puis une session interactive
+est ouverte, utilisant cette base de données.
+.sp
+Seulement une base peut être ouverte. Si vous utilisez plusieurs
+sources, vous devez utiliser l\(aqoption d\(aqimport.
+.TP
+.B \fB\-i\fP , \fB\-\-import=\fP \fIFICHIER\fP
+Importer des données depuis un \fIFICHIER\fP . Si vous n\(aqavez pas
+spécifié de base de données, alors une base de données vide
+est utilisée.
+.sp
+Quand plus d\(aqun fichier doit être importé, chacun doit être
+précédé par la commande \fB\-i\fP . Ces fichiers sont importés dans le
+même ordre,  \fB\-i\fP \fIFICHIER1\fP \fB\-i\fP \fIFICHIER2\fP et \fB\-i\fP \fIFICHIER2\fP \fB\-i\fP
+\fIFICHIER1\fP vont tous les deux produire différents IDs gramps.
+.TP
+.B \fB\-e\fP , \fB\-\-export=\fP \fIFICHIER\fP
+Exporter des données dans un \fIFICHIER\fP . Pour les fichiers \fBgramps\-xml\fP
+, \fBgedcom\fP , \fBwft\fP , \fBgramps\-pkg\fP , et \fBgeneweb\fP , le
+\fIFICHIER\fP est le nom du fichier de sortie.
+.sp
+Quand plus d\(aqun fichier doit être exporté, chacun doit être
+précédé par la commande \fB\-e\fP . Ces fichiers sont importés dans le
+même ordre.
+.TP
+.B \fB\-a\fP , \fB\-\-action=\fP \fIACTION\fP
+Accomplir une \fIACTION\fP sur les données importées. C\(aqest effectué à
+la fin de l\(aqimportation. Les actions possibles sont \fBsummary\fP
+(comme le rapport \-> Afficher \-> Statistiques sur la base),
+\fBcheck\fP (comme l\(aqoutil \-> Réparation de la base \-> Vérifier et
+réparer), \fBreport\fP (produit un rapport) et \fBtool\fP (utilise un
+outil), ces derniers ont besoin de \fIOPTION\fP précédé par la commande \-p.
+.sp
+L\(aq \fIOPTION\fP doit satisfaire ces conditions:
+Il ne doit pas y avoir d\(aqespace. Si certains arguments doivent
+utiliser des espaces, la chaîne doit être encadrée par des
+guillemets. Les options vont par paire nom et valeur. Une
+paire est séparée par un signe égal. Différentes paires sont
+séparées par une virgule.
+.sp
+La plupart des options sont spécifiques à chaque rapport. Même
+s\(aqil existe des options communes.
+.sp
+\fBname=name\fP
+Cette option est obligatoire, elle détermine quel rapport ou
+outil sera utilisé. Si le name saisi ne correspond à aucun
+module disponible, un message d\(aqerreur sera ajouté.
+.sp
+\fBshow=all\fP
+Cette option produit une liste avec les noms des options
+disponibles pour un rapport donné.
+.sp
+\fBshow=optionname\fP
+Cette option affiche une description de toutes les fonctionnalités
+proposées par optionname, aussi bien les types que les valeurs pour une option.
+.sp
+Utiliser les options ci\-dessus pour trouver tout sur un rapport
+choisi.
+.UNINDENT
+.sp
+Quand plus d\(aqune action doit être effectuée, chacune doit être précédée
+par la commande \fB\-a\fP . Les actions seront réalisées une à une, dans
+l\(aqordre spécifié.
+.INDENT 7.0
+.TP
+.B \fB\-d\fP , \fB\-\-debug=\fP \fINOM_LOGGER\fP
+Permet les logs de debug pour le développement et les tests.
+Regarder le code source pour les détails.
+.TP
+.B \fB\-\-version\fP
 Imprime le numéro de version pour gramps puis quitte.
-\" changer 0 par 1 pour permettre la sortie des options OAF
-.if 0 \{
-.PP
-Les options suivantes seront utilisées pour l'activation Bonobo.
-.TP 
-.BI \-\^\-oaf-ior-fd= "FD"
-Le descripteur de fichier pour imprimer OAF IOR
-.TP 
-.BI \-\^\-oaf-activate-iid= " IID"
-OAF IID à activer
-.TP 
-.BI \-\^\-oaf-private
-Prévenir de l'enregistrement du serveur avec OAF
-\}
-\" changer 0 par 1 pour permettre la sortie des options son de GNOME
-.if 0 \{
-.PP
-Les options suivantes seront utilisées pour contrôler le son avec les librairies GNOME.
+.UNINDENT
 .TP
-.BI \-\^\-disable-sound
-Désactive l'utilisation du server son
+.B \fBOpération\fP
+Si le premie argument de la ligne de commande ne commence pas par un
+tiret (i.e. pas d\(aqinstruction), gramps va essayer d\(aqouvrir la base de
+données avec le nom donné par le premier argument et démarrer une ses‐
+sion interactive, en ignorant le reste de la ligne de commande.
+.sp
+Si la commande \fB\-O\fP est notée, alors gramps va essayer le fichier défini
+et va travailler avec ses données, comme pour les autres paramètres de
+la ligne de commande.
+.sp
+Avec ou sans la commande \fB\-O\fP , il peut y avoir plusieurs imports,
+exports, et actions dans la ligne de commande \fB\-i\fP , \fB\-e\fP , et \fB\-a\fP .
+.sp
+L\(aqordre des options \fB\-i\fP , \fB\-e\fP , ou \fB\-a\fP n\(aqa pas de sens. L\(aqordre actuel est
+toujours : imports \-> actions \-> exports. Mais l\(aqouverture doit toujours
+être la première !
+.sp
+Si aucune option \fB\-O\fP ou \fB\-i\fP n\(aqest donnée, gramps lancera sa propre
+fenêtre et demarrera avec une base vide, puisqu\(aqil n\(aqy a pas données.
+.sp
+Si aucune option \fB\-e\fP ou \fB\-a\fP n\(aqest donnée, gramps lancera sa propre
+fenêtre et démarrera avec la base de données issue de tout les imports.
+Cette base sera \fBimport_db.grdb\fP dans le répertoire \fB~/.gramps/import\fP\&.
+.sp
+Les erreurs  rencontrées lors d\(aqimportation, d\(aqexportation, ou d\(aqaction, seront
+mémorisées en \fIstdout\fP (si elles sont le fait de la manipulation par
+gramps) ou en \fIstderr\fP (si elles ne sont pas le fait d\(aqune manipulation).
+Utilisez les shell de redirection de \fIstdout\fP et \fIstderr\fP pour sauver
+les messages et les erreurs dans les fichiers.
 .TP
-.BI \-\^\-enable-sound
-Active l'utilisation du server son
+.B \fBEXEMPLES\fP
+Pour ouvrir un arbre familial et y importer un fichier XML, on peut
+saisir:
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-O\fP \fI\(aqMon Arbre Familial\(aq\fP \fB\-i\fP \fI~/db3.gramps\fP
+.UNINDENT
+.UNINDENT
+.sp
+Ceci ouvre un arbre familial, pour faire la même chose, mais importer
+dans un arbre familial temporaire et démarrer une session interactive,
+on peut saisir :
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-i\fP \fI\(aqMon Arbre Familial\(aq\fP \fB\-i\fP \fI~/db3.gramps\fP
+.UNINDENT
+.UNINDENT
+.sp
+Lecture de quatre bases de données dont les formats peuvent être
+devinés d\(aqaprès les noms, puis vérification des données:
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-i\fP \fIfile1.ged\fP \fB\-i\fP \fIfile2.tgz\fP \fB\-i\fP \fI~/db3.gramps\fP
+\fB\-i\fP \fIfile4.wft\fP \fB\-a\fP \fIcheck\fP
+.UNINDENT
+.UNINDENT
+.sp
+Si vous voulez préciser lesformats de fichiers dans l\(aqexemple ci\-
+dessus, complétez les noms de fichiers par les options \-f appropriées:
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-i\fP \fIfile1.ged\fP \fB\-f\fP \fIgedcom\fP \fB\-i\fP \fIfile2.tgz\fP \fB\-f\fP
+\fIgramps\-pkg\fP \fB\-i\fP \fI~/db3.gramps\fP \fB\-f\fP \fIgramps\-xml\fP \fB\-i\fP \fIfile4.wft\fP
+\fB\-f\fP \fIwft\fP \fB\-a\fP \fIcheck\fP
+.UNINDENT
+.UNINDENT
+.sp
+Pour enregistrer le résultat des lectures, donnez l\(aqoption \fB\-e\fP
+(utiliser \-f si le nom de fichier ne permet pas à gramps de deviner le
+format):
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-i\fP \fIfile1.ged\fP \fB\-i\fP \fIfile2.tgz\fP \fB\-e\fP \fI~/new\-package\fP
+\fB\-f\fP \fIgramps\-pkg\fP
+.UNINDENT
+.UNINDENT
+.sp
+Pour lire trois ensembles de données puis lancer une session
+interactive de gramps sur le tout :
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-i\fP \fIfile1.ged\fP \fB\-i\fP \fIfile2.tgz\fP \fB\-i\fP \fI~/db3.gramps\fP
+.UNINDENT
+.UNINDENT
+.sp
+Pour lancer l\(aqoutil de vérification de la base de données depuis la
+ligne de commande et obtenir le résultat :
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-O\fP \fI\(aqMy Family Tree\(aq\fP \fB\-a\fP \fItool\fP \fB\-p name=\fP \fIverify\fP
+.UNINDENT
+.UNINDENT
+.sp
+Enfin, pour lancer une session interactive normale, entrer :
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps\fP
+.UNINDENT
+.UNINDENT
 .TP
-.BI \-\^\-espeaker= " HOSTNAME:PORT"
-Host:port sur lequel le serveur son sera utilisé
-\}
-
-.SH "Operation"
-.br
-Si le premier argument de la ligne de commande ne commence pas par un tiret (i.e. pas
-d'instruction), gramps va essayer d'ouvrir la base de données avec le nom donné par le premier argument et démarrer une session interactive, en ignorant le reste de la ligne de commande.
-
-.LP
-Si la commande \fB\-O\fR est notée, alors gramps va essayer le fichier défini et va travailler avec ses données, comme pour les autres paramètres de la ligne de commande.
-
-.LP
-Avec ou sans la commande \fB\-O\fR, il peut y avoir plusieurs imports, exports, et actions dans la ligne de commande \fB\-i\fR,
-\fB\-e\fR, et \fB\-a\fR.
-
-.LP
-L'ordre des options \fB\-i\fR, \fB\-e\fR, ou \fB\-a\fR n'a pas de sens. L'ordre actuel est toujours : imports -> actions -> exports. Mais l'ouverture doit toujours être la première!
-
-.LP
-Si aucune option \fB\-O\fR ou \fB\-i\fR n'est donnée, gramps lancera sa propre fenêtre et demarrera avec une base vide, puisqu'il n'y a pas données.
-
-.LP
-Si aucune option \fB\-e\fR ou \fB\-a\fR n'est donnée, gramps lancera sa propre fenêtre et démarrera avec la base de données issue de tout les imports. Cette base sera \fBimport_db.grdb\fR sous le répertoire \fB~/.gramps/import\fR.
-
-.LP
-Les erreurs rencontrées lors d'import, export, ou action, seront mémorisées en \fIstdout\fR (si elles sont le fait de la manipulation par gramps) ou
-en \fIstderr\fR (si elles ne sont pas le fait d'une manipulation). Utilisez les shell de redirection de
- \fIstdout\fR et \fIstderr\fR pour sauver les messages et les erreurs dans les fichiers.
-
-.SH EXEMPLES
+.B \fBVARIABLES D\(aqENVIRONMENT\fP
+Le programme vérifie si ces variables d\(aqenvironnement sont déclarées:
+.sp
+\fBLANG\fP \- décrit, quelle langue est utilisée: Ex.: pour le français on
+peut définir fr_FR.UTF\-8.
+.sp
+\fBGRAMPSHOME\fP  \- si  défini, force Gramps à utiliser un répertoire
+spécifique pour y conserver ses préférences et bases de données. Par
+défaut, cette variable n\(aqest pas active et Gramps sait que les options
+et bases de données doivent être créées dans le répertoire par défaut
+de l\(aqutilisateur (la variable d\(aqenvironnement HOME pour Linux ou USER‐
+PROFILE pour Windows 2000/XP).
 .TP
-Pour ouvrir un arbre familial et y importer un fichier XML, on peut saisir: 
-\fBgramps\fR \fB\-O\fR \fI'Mon Arbre Familal'\fR \fB\-i\fR \fI~/db3.gramps\fR
-.TP 
-Ceci ouvre un arbre familal, pour faire la même chose, mais importer dans un arbre familial temporaire et démarrer une session interactive, on peut saisir: 
-\fBgramps\fR \fB\-i\fR \fI'Mon Arbre Familal'\fR \fB\-i\fR \fI~/db3.gramps\fR
-.TP  
-Lecture de quatre bases de données dont les formats peuvent être devinés d'après les noms, puis vérification des données: 
-\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-i\fR \fIfile4.wft\fR \fB\-a\fR \fIcheck\fR 
-.TP 
-Si vous voulez préciser les formats de fichiers dans l'exemple ci-dessus, complétez les noms de fichiers par les options \fB\-f\fR appropriées: 
-\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-f\fR \fIgedcom\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-f\fR \fIgramps-pkg\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-f\fR \fIgramps-xml\fR \fB\-i\fR \fIfile4.wft\fR \fB\-f\fR \fIwft\fR  \fB\-a\fR \fIcheck\fR 
-.TP 
-Pour enregistrer le résultat des lectures, donnez l'option  \fB\-e\fR (utiliser \fB\-f\fR si le nom de fichier ne permet pas à gramps de deviner le format):
-\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-e\fR \fI~/new-package\fR \fB\-f\fR \fIgramps-pkg\fR 
-.TP 
-Pour lire trois ensembles de données puis lancer une session interactive de gramps sur le tout : 
-\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR 
-.TP 
-Pour lancer l'outil de vérification de la base de données depuis la ligne de commande et obtenir le résultat: 
-\fBgramps\fR \fB\-O\fR \fIfile.grdb\fR \fB-a\fR \fItool\fR \fB-p\fR \fBname\fR=\fIverify\fR
+.B \fBCONCEPTS\fP
+Gramps est un système basé sur le support de plugin\-python, permettant
+d\(aqimporter et d\(aqexporter, la saisie, générer des rapports, des outils,
+et afficher des filtres pouvant être ajoutés sans modifier le programme.
+.sp
+Par ailleurs, gramps permet la génération directe : impression, rap‐
+ports avec sortie vers d\(aqautres formats, comme \fILibreOffice.org\fP ,
+\fIHTML\fP , ou \fILaTeX\fP pour permettre à l\(aqutilisateur de choisir selon ses
+besoins
+.UNINDENT
+.sp
+\fBBUGS CONNUS ET LIMITATIONS\fP
+.sp
+\fBFICHIERS\fP
+.INDENT 0.0
+.INDENT 3.5
+\fI${PREFIX}/bin/gramps\fP
+.sp
+\fI${PREFIX}/lib/python3/dist\-packages/gramps/\fP
+.sp
+\fI${PREFIX}/share/\fP
+.sp
+\fI${HOME}/.gramps\fP
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
 .TP
-Enfin, pour lancer une session interactive normale, entrer : \fBgramps\fR
-
-.SH VARIABLES D'ENVIRONMENT 
-Le programme vérifie si ces variables d'environnement sont déclarées:
-
-\fBLANG\fR - décrit, quelle langue est utilisée:
-Ex.: pour le français on peut définir fr_FR.UTF-8.
-
-\fBGRAMPSHOME\fR - si défini, force Gramps à utiliser un répertoire spécifique pour y conserver ses préférences et bases de données. Par défaut, cette variable n'est pas active et Gramps sait que les options et bases de données doivent être créées
-dans le répertoire par défaut de l'utilisateur (la variable d'environnement HOME pour Linux ou USERPROFILE pour Windows 2000/XP).
-
-.SH CONCEPTS
-Gramps est un système basé sur le support de plugin-python, permettant d'importer et d'exporter, la saisie, 
-générer des rapports, des outils, et afficher des filtres pouvant être ajoutés sans modifier le programme.
-.LP 
-Par ailleurs, gramps permet la génération directe : impression, rapports avec sortie vers d'autres formats, comme \fIOpenOffice.org\fR, \fIAbiWord\fR, HTML, 
-ou LaTeX pour permettre à l'utilisateur de choisir selon ses besoins 
-
-.SH BUGS CONNUS ET LIMITATIONS
-
-.SH FICHIERS
-.LP 
-\fI${PREFIX}/bin/gramps\fP 
-.br 
-\fI${PREFIX}/share/gramps\fP
-.br 
-\fI${HOME}/.gramps\fP 
-
-.SH AUTEURS
-Donald Allingham \fI<don@gramps-project.org>\fR
-.br 
-\fIhttp://gramps.sourceforge.net\fR
-.LP 
-Cette page man a d'abord été écrite par:
-.br 
-Brandon L. Griffith \fI<brandon@debian.org>\fR
-.br
+.B \fBAUTEURS\fP
+Donald Allingham <\fI\%don@gramps\-project.org\fP>
+\fI\%http://gramps\-project.org/\fP
+.sp
+Cette page man a d\(aqabord été écrite par :
+Brandon L. Griffith <\fI\%brandon@debian.org\fP>
 pour Debian GNU/Linux système.
-.LP 
-Cette page man est maintenue par:
-.br 
-Gramps project \fI<xxx@gramps-project.org>\fR
-.LP 
-La traduction française:
-.br 
-Jérôme Rapinat \fI<romjerome@yahoo.fr>\fR
-.br 
-
-.SH DOCUMENTATION
-La documentation-utilisateur est disponible par le navigateur d'aide de GNOME sous la forme du manuel Gramps. Ce manuel est également disponible sous format XML comme \fBgramps-manual.xml\fR sous \fIdoc/gramps-manual/$LANG\fR dans les sources officielles.
-.LP 
-La documentation pour développeur est disponible sur le site \fIhttp://developers.gramps-project.org\fR.
+.sp
+Cette page man est maintenue par :
+Gramps project <\fI\%xxx@gramps\-project.org\fP>
+.sp
+La traduction française :
+Jérôme Rapinat <\fI\%romjerome@yahoo.fr\fP>
+.TP
+.B \fBDOCUMENTATION\fP
+La documentation\-utilisateur est disponible par un navigateur
+standard sous la forme du manuel Gramps.
+.sp
+La documentation pour développeur est disponible sur le site
+\fI\%http://www.gramps\-project.org/wiki/index.php?title=Portal:Developers\fP .
+.UNINDENT
+.sp
+gramps(1)                 @VERSION@               gramps(1)
+.\" Generated by docutils manpage writer.
+.

data/man/gramps.1.in

@@ -1,320 +1,335 @@
-.TH gramps 1 "@VERSION@" "January 2008" "@VERSION@"
+.\" Man page generated from reStructuredText.
+.
+.TH ENGLISH  "" "" ""
 .SH NAME
-gramps \- Genealogical Research and Analysis Management Programming System.
-
-.SH SYNOPSIS
-.B gramps
-.RB [ \-?|\-\^\-help ]
-.RB [ \-\^\-usage ]
-.RB [ \-\^\-version ]
-.RB [ \-l ]
-.RB [ \-u|\-\^\-force-unlock ]
-.RB [ \-O|\-\^\-open=
-.IR DATABASE 
-.RB [ \-f|\-\^\-format= 
-.IR FORMAT ]] 
-.RB [ \-i|\-\^\-import=
-.IR FILE 
-.RB [ \-f|\-\^\-format= 
-.IR FORMAT ]] 
-.RB [ \-i|\-\^\-import= 
-.IR ... ] 
-.RB [ \-e|\-\^\-export= 
-.IR FILE
-.RB [ \-f|\-\^\-format= 
-.IR FORMAT ]] 
-.RB [ \-a|\-\^\-action= 
-.IR ACTION ]
-.RB [ \-p|\-\^\-options= 
-.IR OPTIONSTRING ]]
-.RB [
-.IR FILE
-.RB ]
-.if 0 .RB [ bonobo\ options ]
-.if 0 .RB [ sound\ options ]
-.RB [ \-\-version ]
-
-.SH DESCRIPTION
-.PP 
-\fIGramps\fP is a Free/OpenSource genealogy program. It is written in Python, 
-using the GTK+/GNOME interface.
-Gramps should seem familiar to anyone who has used other genealogy programs 
-before such as \fIFamily Tree Maker (TM)\fR,  \fIPersonal Ancestral
-Files (TM)\fR, or the GNU Geneweb.
-It supports importing of the ever popular GEDCOM format which is used world 
-wide by almost all other genealogy software.
-
-.SH OPTIONS
-.TP 
-.BI gramps " FILE" 
-When \fIFILE\fR is given (without any flags) as a family tree name or as
-a family tree database directory, then it is opened and an interactive 
-session is started. If FILE is a file format understood by Gramps, an empty
-family tree is created  whose name is based on the \fIFILE\fP name
-and the data is imported into it. The rest of the
-options is ignored. This way of launching is suitable for using gramps
-as a handler for genealogical data in e.g. web browsers. This invocation
-can accept any data format native to gramps, see below.
-.br
-
-.TP 
-.BI \-f,\-\^\-format= " FORMAT"
-Explicitly specify format of \fIFILE\fR given by preceding
-.ig
-\fB\-O\fR,
+English \- 
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
 ..
-\fB\-i\fR, or 
-\fB\-e\fR option. If the \fB\-f\fR option is not given for any \fIFILE\fR, 
-the format of that file is guessed according to its extension or MIME-type. 
-.br
-
-Formats 
-available for export are \fBgramps\-xml\fR (guessed if \fIFILE\fR ends with
-\fB.gramps\fR), \fBgedcom\fR (guessed if \fIFILE\fR ends with \fB.ged\fR), or
-any file export available through the Gramps plugin system.
-.br
-
-Formats 
-available for import are \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR,  
-\fBgramps\-pkg\fR (guessed if \fIFILE\fR ends with \fB.gpkg\fR), and
-\fBgeneweb\fR (guessed if \fIFILE\fR ends with \fB.gw\fR). 
-.br
-
-Formats available for export are
-.ig
-\fBgrdb\fR,
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
 ..
-\fBgramps\-xml\fR, \fBgedcom\fR,
-\fBgramps\-pkg\fR, \fBwft\fR (guessed if \fIFILE\fR ends with \fB.wft\fR),
-\fBgeneweb\fR, and \fBiso\fR (never guessed, always specify with
-\fB\-f\fR option).
-
-.TP 
-.BI \-l
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.sp
+gramps(1)                @VERSION@               gramps(1)
+.INDENT 0.0
+.TP
+.B \fBNAME\fP
+gramps \- Genealogical Research and Analysis Management Programming Sys‐
+tem.
+.TP
+.B \fBSYNOPSIS\fP
+\fBgramps\fP [\fB\-?\fP | \fB\-\-help\fP] [\fB\-\-usage\fP] [\fB\-\-version\fP]
+[\fB\-l\fP] [\fB\-L\fP] [\fB\-u\fP | \fB\-\-force\-unlock\fP] [\fB\-O\fP | \fB\-\-open=\fP \fIDATABASE\fP
+[\fB\-f\fP | \fB\-\-format=\fP \fIFORMAT\fP] [\fB\-i\fP | \fB\-\-import=\fP \fIFILE\fP
+[\fB\-f\fP | \fB\-\-format=\fP \fIFORMAT\fP]] [\fB\-\-remove=\fP \fIFAMILY_TREE_PATTERN\fP]
+[\fB\-e\fP | \fB\-\-export=\fP \fIFILE\fP [\fB\-f\fP | \fB\-\-format=\fP \fIFORMAT\fP]]
+[\fB\-a\fP | \fB\-\-action=\fP \fIACTION\fP] [\fI\-p\fP | \fB\-\-options=\fP \fIOPTION‐
+STRING\fP]] [\fIFILE\fP] [\fB\-\-version\fP]
+.TP
+.B \fBDESCRIPTION\fP
+Gramps is a Free/OpenSource genealogy program. It is written in Python,
+using  the GTK+/GNOME interface.  Gramps should seem familiar to anyone
+who has used other genealogy programs before such as Family Tree  Maker
+(TM),   Personal Ancestral Files (TM), or the GNU Geneweb.  It supports
+importing of the ever popular GEDCOM format which is used world wide by
+almost all other genealogy software.
+.TP
+.B \fBOPTIONS\fP
+.INDENT 7.0
+.TP
+.B \fBgramps\fP \fIFILE\fP
+When \fIFILE\fP is given (without any flags) as a family tree name or
+as a family tree database directory, then it is opened and an
+interactive  session is started. If \fIFILE\fP is a file format under‐
+stood by Gramps, an empty family tree is created  whose name is
+based  on  the \fIFILE\fP name and the data is imported into it. The
+rest of the options is ignored. This way of launching is suit‐
+able for using gramps as a handler for genealogical data in e.g.
+web browsers. This invocation can accept any data format  native
+to gramps, see below.
+.TP
+.B \fB\-f\fP , \fB\-\-format=\fP \fIFORMAT\fP
+Explicitly specify format of \fIFILE\fP given by preceding \fB\-i\fP ,
+or \fB\-e\fP option. If the \fB\-f\fP option is not given for any
+\fIFILE\fP , the format of that file is guessed according to its extension
+or MIME\-type.
+.sp
+Formats  available for export are \fBgramps\-xml\fP (guessed if \fIFILE\fP
+ends with \fB\&.gramps\fP ), \fBgedcom\fP (guessed if \fIFILE\fP ends with
+\fB\&.ged\fP ), or any file export available through the Gramps plugin
+system.
+.sp
+Formats available for import are \fBgramps\-xml\fP , \fBgedcom\fP ,
+\fBgramps\-pkg\fP (guessed if \fIFILE\fP ends with \fB\&.gpkg\fP ),
+and \fBgeneweb\fP (guessed if \fIFILE\fP ends with \fB\&.gw\fP ).
+.sp
+Formats available for export are \fBgramps\-xml\fP , \fBgedcom\fP ,
+\fBgramps\-pkg\fP , \fBwft\fP (guessed if \fIFILE\fP ends with \fB\&.wft\fP ),
+\fBgeneweb\fP\&.
+.TP
+.B \fB\-l\fP
 Print a list of known family trees.
-
 .TP
-.BI \-u,\-\^\-force-unlock
+.B \fB\-L\fP
+Print a detailed list of known family trees.
+.TP
+.B \fB\-u\fP , \fB\-\-force\-unlock\fP
 Unlock a locked database.
-
-.TP 
-.BI \-O,\-\^\-open= " DATABASE"
-Open \fIDATABASE\fR which must be an existing database directory or existing family tree name.
-If no action, import or export options are given on the command line then an interactive session is started using that database.
-
-.TP 
-.BI \-i,\-\^\-import= " FILE"
-Import data from \fIFILE\fR. If you haven't specified a database then a temporary database is used; this is deleted when you exit gramps.
-.br
-
-When more than one input file is given, each has to be preceded by \fB\-i\fR 
-flag. The files are imported in the specified order, 
-i.e. \fB\-i\fR \fIFILE1\fR \fB\-i\fR \fIFILE2\fR  
-and \fB\-i\fR \fIFILE2\fR \fB\-i\fR \fIFILE1\fR might produce different 
-gramps IDs in the resulting database. 
-
-.TP 
-.BI \-a,\-\^\-action= " ACTION"
-Perform \fIACTION\fR on the imported data. This is done after all imports
-are successfully completed. Currently available actions are 
-\fBsummary\fR (same as Reports->View->Summary), 
-\fBcheck\fR (same as Tools->Database Processing->Check and Repair), 
-\fBreport\fR (generates report), and
-\fBtool\fR (runs a plugin tool).
-Both \fBreport\fR and \fBtool\fR need the \fIOPTIONSTRING\fR supplied by the 
-\fB\-p\fR flag). 
-.br
-
-The \fIOPTIONSTRING\fR should satisfy the following conditions:
-.br
-It must not contain any spaces. 
-If some arguments need to include spaces, the string should
-be enclosed with quotation marks, i.e., follow the shell syntax.
-Option string is a list of pairs with name and value (separated by the 
-equality sign). The name and value pairs must be separated by commas.  
-.br
-
-Most of the report or tools options are specific for each report or tool. 
-However, there are some common options.
-
-.BI "name=name"
-.br
-This mandatory option determines which report or tool will be run.
-If the supplied \fIname\fR does not correspond to any available report or 
-tool, an error message will be printed followed by the list of
-available reports or tools (depending on the \fIACTION\fR).
-
-.BI "show=all"
-.br
-This will produce the list of names for all options available for a given 
-report or tool.
-
-.BI "show="optionname
-.br
-This will print the description of
-the functionality supplied by \fIoptionname\fR, as well as what are the
-acceptable types and values for this option.
-
-.br
-Use the above options to find out
-everything about a given report.  
-
-.LP
-When more than one output action is given, each has to be preceded 
-by \fB\-a\fR flag. The actions are performed one by one, in the specified order.
-
-.TP 
-.BI \-d,\-\^\-debug= " LOGGER_NAME"
-Enables debug logs for development and testing. Look at the source code for details
 .TP
-.BI \-\^\-version
+.B \fB\-O\fP , \fB\-\-open=\fP \fIDATABASE\fP
+Open \fIDATABASE\fP which  must be an existing database directory or
+existing family tree name. If no action, import or export
+options are given on the command line then an interactive ses‐
+sion is started using that database.
+.TP
+.B \fB\-i\fP , \fB\-\-import=\fP \fIFILE\fP
+Import data from \fIFILE\fP . If you haven\(aqt specified a database, then
+an empty database is created for you called Family Tree x
+(where x is an incrementing number).
+.sp
+When more than one input file is given, each has to be preceded
+by \fB\-i\fP flag. The files are imported in the specified order, i.e.
+\fB\-i\fP \fIFILE1\fP \fB\-i\fP \fIFILE2\fP and \fB\-i\fP \fIFILE2\fP \fB\-i\fP \fIFILE1\fP
+might produce different gramps IDs in the resulting database.
+.TP
+.B \fB\-e\fP , \fB\-\-export=\fP \fIFILE\fP
+Export data into \fIFILE\fP . For \fBgramps\-xml\fP , \fBgedcom\fP
+, \fBwft\fP , \fBgramps\-pkg\fP , and \fBgeneweb\fP , the \fIFILE\fP is the
+name of the resulting file.
+.sp
+When more than one output file is given, each has to be preceded
+by \fB\-e\fP flag. The files are written one by one, in the specified order.
+.TP
+.B \fB\-a\fP , \fB\-\-action=\fP \fIACTION\fP
+Perform \fIACTION\fP on the imported data. This is done after all
+imports are successfully completed. Currently available  actions
+are \fBsummary\fP (same  as  Reports\->View\->Summary), \fBcheck\fP (same as
+Tools\->Database Processing\->Check and Repair), \fBreport\fP (generates
+report),  and  tool  (runs a plugin tool).  Both \fBreport\fP and \fBtool\fP
+need the \fIOPTIONSTRING\fP supplied by the \fB\-p\fP flag).
+.sp
+The \fIOPTIONSTRING\fP should satisfy the following conditions:
+It must not contain any  spaces. If some arguments need to
+include spaces, the string should be enclosed with quotation
+marks, i.e., follow the shell syntax. Option string is a list
+of  pairs  with name and value (separated by the equality sign).
+The name and value pairs must be separated by commas.
+.sp
+Most of the report or tools options are specific for each report
+or tool. However, there are some common options.
+.sp
+\fBname=name\fP
+This mandatory option determines which report or tool will be
+run. If the supplied name does not correspond to any  available
+report or tool, an error message will be printed followed by the
+list of available reports or tools (depending on the \fIACTION\fP ).
+.sp
+\fBshow=all\fP
+This will produce the list of names for all options available
+for a given report or tool.
+.sp
+\fBshow=optionname\fP
+This will print the description of the functionality supplied by
+\fIoptionname\fP, as well as what are the acceptable types and  values
+for this option.
+.sp
+Use the above options to find out everything about a given
+report.
+.UNINDENT
+.sp
+When more than one output action is given, each has to be preceded  by
+\fB\-a\fP flag. The actions are performed one by one, in the specified order.
+.INDENT 7.0
+.TP
+.B \fB\-d\fP , \fB\-\-debug=\fP \fILOGGER_NAME\fP
+Enables debug logs for development and testing. Look at the
+source code for details
+.TP
+.B \fB\-\-version\fP
 Prints the version number of gramps and then exits
-\" change 0 to 1 to enable output of OAF options
-.if 0 \{
-.PP
-The following options are used for Bonobo activation.
-.TP 
-.BI \-\^\-oaf-ior-fd= "FD"
-File descriptor to print the OAF IOR on
-.TP 
-.BI \-\^\-oaf-activate-iid= " IID"
-OAF IID to activate
-.TP 
-.BI \-\^\-oaf-private
-Prevent registering of server with OAF
-\}
-\" change 0 to 1 to enable output of Gnome sound options
-.if 0 \{
-.PP
-The following options are used for controlling sound using the Gnome Library.
+.UNINDENT
 .TP
-.BI \-\^\-disable-sound
-Disable sound server usage
+.B \fBOperation\fP
+If the first argument on the command line does not start with dash
+(i.e. no flag), gramps will attempt to open the file with the name
+given by the first argument and start interactive session, ignoring the
+rest of the command line arguments.
+.sp
+If the  \fB\-O\fP flag is given, then gramps will try opening the supplied
+database and then work with that data, as instructed by the further
+command line parameters.
+.sp
+With or without the \fB\-O\fP flag, there could be multiple imports, exports,
+and actions specified further on the command line by using \fB\-i\fP ,
+\fB\-e\fP , and \fB\-a\fP flags.
+.sp
+The order of \fB\-i\fP , \fB\-e\fP , or \fB\-a\fP options does not matter. The actual order
+always is: all imports (if any) \-> all actions (if any) \-> all  exports
+(if any). But opening must always be first!
+.sp
+If no \fB\-O\fP or \fB\-i\fP 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.
+.sp
+If no \fB\-e\fP  or \fB\-a\fP 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 in the \fBimport_db.grdb\fP under
+\fB~/.gramps/import\fP directory.
+.sp
+The error encountered during import, export, or action, will be  either
+dumped to stdout (if  these  are exceptions handled by gramps) or to
+\fIstderr\fP (if these are not handled). Use usual shell redirections of
+\fIstdout\fP and \fIstderr\fP to save messages and errors in files.
 .TP
-.BI \-\^\-enable-sound
-Enable sound server usage
+.B \fBEXAMPLES\fP
+To open an existing family tree and import an xml file into it, one
+may type:
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-O\fP \fI\(aqMy Family Tree\(aq\fP \fB\-i\fP \fI~/db3.gramps\fP
+.UNINDENT
+.UNINDENT
+.sp
+The above changes the opened family tree, to do the  same, but import
+both in a temporary family tree and start an interactive session, one
+may type:
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-i\fP \fI\(aqMy Family Tree\(aq\fP \fB\-i\fP \fI~/db3.gramps\fP
+.UNINDENT
+.UNINDENT
+.sp
+To import four databases (whose formats can be  determined from their
+names) and then check the resulting database for errors, one may type:
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-i\fP \fIfile1.ged\fP \fB\-i\fP \fIfile2.tgz\fP \fB\-i\fP \fI~/db3.gramps\fP
+\fB\-i\fP \fIfile4.wft\fP \fB\-a\fP \fIcheck\fP
+.UNINDENT
+.UNINDENT
+.sp
+To explicitly specify the formats in the above  example,  append  file‐
+names with appropriate \fB\-f\fP options:
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-i\fP \fIfile1.ged\fP \fB\-f\fP \fIgedcom\fP \fB\-i\fP \fIfile2.tgz\fP \fB\-f\fP
+\fIgramps\-pkg\fP \fB\-i\fP \fI~/db3.gramps\fP \fB\-f\fP \fIgramps\-xml\fP \fB\-i\fP \fIfile4.wft\fP
+\fB\-f\fP \fIwft\fP \fB\-a\fP \fIcheck\fP
+.UNINDENT
+.UNINDENT
+.sp
+To record the database resulting from all imports, supply \fB\-e\fP flag  (use
+\fB\-f\fP if the filename does not allow gramps to guess the format):
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-i\fP \fIfile1.ged\fP \fB\-i\fP \fIfile2.tgz\fP \fB\-e\fP \fI~/new\-package\fP
+\fB\-f\fP \fIgramps\-pkg\fP
+.UNINDENT
+.UNINDENT
+.sp
+To import three databases and start interactive gramps session with the
+result:
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-i\fP \fIfile1.ged\fP \fB\-i\fP \fIfile2.tgz\fP \fB\-i\fP \fI~/db3.gramps\fP
+.UNINDENT
+.UNINDENT
+.sp
+To run the Verify tool from the commandline and output the result to
+stdout:
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps \-O\fP \fI\(aqMy Family Tree\(aq\fP \fB\-a\fP \fItool\fP \fB\-p name=\fP \fIverify\fP
+.UNINDENT
+.UNINDENT
+.sp
+Finally, to start normal interactive session type:
+.INDENT 7.0
+.INDENT 3.5
+\fBgramps\fP
+.UNINDENT
+.UNINDENT
 .TP
-.BI \-\^\-espeaker= " HOSTNAME:PORT"
-Host:port on which the sound server to use is running
-\}
-
-.SH "Operation"
-.br
-If the first argument on the command line does not start with dash (i.e. no
-flag), gramps will attempt to open the file with the name given by the first
-argument and start interactive session, ignoring the rest of the command line
-arguments.
-
-.LP
-If the \fB\-O\fR flag is given, then gramps will try opening
-the supplied database and then work with that data, as instructed by the
-further command line parameters.
-
-.LP
-With or without the \fB\-O\fR flag, there could be multiple imports,
-exports, and actions specified further on the command line by using \fB\-i\fR,
-\fB\-e\fR, and \fB\-a\fR flags.  
-
-.LP
-The order of \fB\-i\fR, \fB\-e\fR, or \fB\-a\fR options does not matter. The
-actual order always is: all imports (if any) -> all actions (if any)
--> all exports (if any). But opening must always be first!
-
-.LP
-If no \fB\-O\fR or \fB\-i\fR 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.
-
-.LP
-If no \fB\-e\fR or \fB\-a\fR 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 in the \fBimport_db.grdb\fR
-under \fB~/.gramps/import\fR directory.
-
-.LP
-The error encountered during import, export, or action, will be either 
-dumped to \fIstdout\fR (if these are exceptions handled by gramps) or 
-to \fIstderr\fR (if these are not handled). Use usual shell redirections 
-of \fIstdout\fR and \fIstderr\fR to save messages and errors in files. 
-
-.SH EXAMPLES
-.TP 
-To open an existing family tree and import an xml file  into it, one may type: 
-\fBgramps\fR \fB\-O\fR \fI'My Family Tree'\fR \fB\-i\fR \fI~/db3.gramps\fR
-.TP 
-The above changes the opened family tree, to do the same, but import both in a temporary family tree and start an interactive session, one may type: 
-\fBgramps\fR \fB\-i\fR \fI'My Family Tree'\fR \fB\-i\fR \fI~/db3.gramps\fR
-.TP 
-To import four databases (whose formats can be determined from their names) and then check the resulting database for errors, one may type: 
-\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-i\fR \fIfile4.wft\fR \fB\-a\fR \fIcheck\fR 
-.TP 
-To explicitly specify the formats in the above example, append filenames with appropriate \fB\-f\fR options: 
-\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-f\fR \fIgedcom\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-f\fR \fIgramps-pkg\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-f\fR \fIgramps-xml\fR \fB\-i\fR \fIfile4.wft\fR \fB\-f\fR \fIwft\fR  \fB\-a\fR \fIcheck\fR 
-.TP 
-To record the database resulting from all imports, supply \fB\-e\fR flag (use \fB\-f\fR if the filename does not allow gramps to guess the format):
-\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-e\fR \fI~/new-package\fR \fB\-f\fR \fIgramps-pkg\fR 
-.TP 
-To import three databases and start interactive gramps session with the result: 
-\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR 
-.TP 
-To run the Verify tool from the commandline and output the result to stdout: 
-\fBgramps\fR \fB\-O\fR \fI'My Family Tree'\fR \fB-a\fR \fItool\fR \fB-p\fR \fBname\fR=\fIverify\fR
-.TP 
-Finally, to start normal interactive session type: 
-\fBgramps\fR 
-
-.SH ENVIRONMENT VARIABLES
+.B \fBENVIRONMENT VARIABLES\fP
 The program checks whether these environment variables are set:
-
-\fBLANG\fR - describe, which language to use:
-Ex.: for polish language this variable has to be set to pl_PL.UTF-8.
-
-\fBGRAMPSHOME\fR - if set, force Gramps to use the specified directory to keep 
-program settings and databases there. By default, this variable is not set and 
-gramps assumes that the folder with all databases and profile settings 
-should be created within the user profile folder (described by environment 
-variable HOME for Linux or USERPROFILE for Windows 2000/XP).
-
-.SH CONCEPTS
-Supports a python\-based plugin system, allowing import and export writers, 
-report generators, tools, and display filters to be added without modification 
-of the main program.
-.LP 
-In addition to generating direct printer output, report generators also 
-target other systems, such as \fIOpenOffice.org\fR, \fIAbiWord\fR, HTML, 
-or LaTeX to allow the users to modify the format to suit their needs. 
-
-.SH KNOWN BUGS AND LIMITATIONS
-
-.SH FILES
-.LP 
-\fI${PREFIX}/bin/gramps\fP 
-.br 
-\fI${PREFIX}/share/gramps\fP
-.br 
-\fI${HOME}/.gramps\fP 
-
-.SH AUTHORS
-Donald Allingham \fI<don@gramps-project.org>\fR
-.br 
-\fIhttp://gramps.sourceforge.net\fR
-.LP 
+.sp
+\fBLANG\fP  \-  describe, which language to use: Ex.: for polish language this
+variable has to be set to pl_PL.UTF\-8.
+.sp
+\fBGRAMPSHOME\fP \- if set, force Gramps to use  the  specified  directory  to
+keep program settings and databases there. By default, this variable is
+not set and gramps assumes that the folder with all databases and  pro‐
+file  settings  should  be  created  within  the  user  profile  folder
+(described by environment variable HOME for Linux  or  USERPROFILE  for
+Windows 2000/XP).
+.TP
+.B \fBCONCEPTS\fP
+Supports a python\-based plugin system, allowing import and export writ‐
+ers, report generators, tools, and display filters to be added  without
+modification of the main program.
+.sp
+In addition to generating direct printer output, report generators also
+target other systems, such as \fILibreOffice.org\fP , \fIAbiWord\fP , \fIHTML\fP,
+or \fILaTeX\fP to allow the users to modify the format to suit their needs.
+.UNINDENT
+.sp
+\fBKNOWN BUGS AND LIMITATIONS\fP
+.sp
+\fBFILES\fP
+.INDENT 0.0
+.INDENT 3.5
+\fI${PREFIX}/bin/gramps\fP
+.sp
+\fI${PREFIX}/lib/python3/dist\-packages/gramps/\fP
+.sp
+\fI${PREFIX}/share/\fP
+.sp
+\fI${HOME}/.gramps\fP
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBAUTHORS\fP
+Donald Allingham <\fI\%don@gramps\-project.org\fP>
+\fI\%http://gramps\-project.org/\fP
+.sp
 This man page was originally written by:
-.br 
-Brandon L. Griffith \fI<brandon@debian.org>\fR
-.br
+Brandon L. Griffith <\fI\%brandon@debian.org\fP>
 for inclusion in the Debian GNU/Linux system.
-.LP 
+.sp
 This man page is currently maintained by:
-.br 
-Gramps project \fI<xxx@gramps-project.org>\fR
-.br 
-
-.SH DOCUMENTATION
-The user documentation is available through standard GNOME Help browser 
-in the form of Gramps Manual. The manual is also available in XML format
-as \fBgramps-manual.xml\fR under \fIdoc/gramps-manual/$LANG\fR in the official
-source distribution.
-.LP 
+Gramps project <\fI\%xxx@gramps\-project.org\fP>
+.TP
+.B \fBDOCUMENTATION\fP
+The user documentation is available through standard web browser
+in the form of Gramps Manual.
+.sp
 The developer documentation can be found on the
-\fIhttp://developers.gramps-project.org\fR site. 
+\fI\%http://www.gramps\-project.org/wiki/index.php?title=Portal:Developers\fP
+portal.
+.UNINDENT
+.sp
+gramps(1)                 @VERSION@               gramps(1)
+.\" Generated by docutils manpage writer.
+.

data/man/index.rst

@@ -0,0 +1,22 @@
+.. Gramps documentation master file, created by
+   sphinx-quickstart on Sat Dec 1 00:07:37 2012.
+   You can adapt this file completely to your liking, but it should at least
+   contain the root `toctree` directive.
+
+Welcome to Gramps' command line documentation!
+==============================================
+
+Contents:
+
+.. toctree::
+   :maxdepth: 2
+
+   en
+   cs/cs
+   fr/fr
+   nl/nl
+   pl/pl
+   pt_BR/pt_BR
+   sv/sv
+
+

data/man/nl/Makefile.am

@@ -1,15 +0,0 @@
-# This is the data/man/nl level Makefile for Gramps
-# $Id: Makefile.am 9819 2008-01-15 15:42:10Z bmcage $
-
-mandir = @mandir@/nl
-
-man_IN_FILES = gramps.1.in
-man_MANS = $(man_IN_FILES:.1.in=.1)
-
-EXTRA_DIST = $(man_MANS) $(man_IN_FILES)
-
-gramps.1: $(top_builddir)/config.status gramps.1.in
-	cd $(top_builddir) && CONFIG_FILES=data/man/nl/$@ $(SHELL) ./config.status
-
-CLEANFILES=$(man_MANS)
-