2007-04-22 Don Allingham <don@gramps-project.org>

* configure.in: bump to full release of 2.2.7
	* src/const.py.in: fix 2007 in copyright
	* NEWS: update news file



svn: r8419

.get_packages_list.py

@@ -1,11 +0,0 @@
-import os
-
-from distutils2.util import find_packages
-
-exclude_list = ('src.gui.glade', 'src.guiQML', 'src.guiQML.views', 'src.images', 'src.plugins',
-                'src.webapp', 'src.webapp.grampsdb', 'src.webapp.grampsdb.templatetags', 'src.webapp.grampsdb.view', )
-
-packages = sorted(find_packages(exclude=exclude_list))
-
-for package in packages:
-    print("            '%s'," % package)

.gitignore

@@ -1,12 +0,0 @@
-# Python
-*.py[cod]
-
-# Distutils
-MANIFEST
-build/
-dist/
-
-# Gramps
-data/tips.xml
-gramps/plugins/lib/holidays.xml
-po/.intltool-merge-cache

AUTHORS

@@ -1,94 +1,17 @@
-<!-- $Id$ -->
+Donald N. Allingham ** Concept and main design
 
+David Hampton ** Autocomp.py and Report.py
 
-Alex Roitman shura@gramps-project.org
+Donald A. Peterson  ** Makefiles, LaTeXDoc.py
 
-Arturas Sleinius asleinius@users.sourceforge.net
+Alex Roitman ** BookReport, command line, Gramps manual, bugfixes
 
-Benny Malengier benny.malengier@gramps-project.org
+Tim Waugh ** Comprehensive Ancestor report, docgen, Makefiles, bugfixes
 
-Boril Gourinov boril.gourinov@gmail.com
+Martin Hawlisch - Filters
 
-Brian Matherly brian@gramps-project.org
+Richard Taylor - ScratchPad.py, GrampsDBCallback.py
 
-Craig J. Anderson ander882@hotmail.com
+Brian Matherly - Reports
 
-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
+$Id$

COPYING-DOCS

@@ -0,0 +1,13 @@
+The User Manual for Gramps is distributed under the terms of
+GNU General Public License (GPL). Yes, it is under GNU GPL and
+*NOT* under GNU FDL.
+
+As such, this manual meets citeria of Debian Free Software Guidelines 
+(DFSG) and can be distributed through Debian main (as opposed to non-free).
+
+Please see file named COPYING for exact terms of the license.
+
+Alex Roitman
+February 15, 2005
+
+$Id$

FAQ

@@ -7,93 +7,57 @@ to this list, please email your suggestions to gramps-devel@lists.sf.net
 
 **** Index ****
 
-==General==
 
  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 it work with Windows (tm)?
 
- 4. How do I keep backups?
+ 4. Does it work with the Mac?
 
- 5. Does Gramps support Unicode fonts? In particular, does it support non-Roman Unicode fonts?
+ 5. Does it work with KDE?
 
- 6. What is needed to install GRAMPS under Linux, Solaris, or FreeBSD?
+ 6. Do I really have to have GNOME installed?
 
- 7. Does it work with Windows (tm)?
+ 7. What version of GNOME do I need?
 
- 8. Does it work with the Mac?
+ 8. Is GRAMPS compatible with other genealogical software (GenApps)?
 
- 9. What are the Minimum Specs to run GRAMPS?
+ 9. Can GRAMPS read files created by GenApp X?
 
-==Preferences==
+10. Can GRAMPS write files readable by GenApp X?
 
- 10. Can I change the dates in reports to 'day month year'
+11. Can GRAMPS print a genealogical tree for my family?
 
-==Collaboration-Portability==
+12. In what formats can GRAMPS output its reports?
 
- 11. Is GRAMPS compatible with other genealogical software?
+13. Is GRAMPS compatible with the Internet?
 
- 12. Can GRAMPS read files created by GenApp X?
+14. Can I create custom reports/filters/whatever?
 
- 13. Can GRAMPS write files readable by GenApp X?
+15. What standards does GRAMPS support?
 
- 14. What standards does GRAMPS support?
+16. What is the maximum database size GRAMPS can handle?
 
- 15. How do I import data from another genealogy program into GRAMPS?
+17. Why are non-latin characters displayed as garbage in PDF/PS reports?
 
- 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.
+18. Why can I not add/remove/edit columns to the lists in People View 
+    and Family View?
 
-==Reports==
+19. I would like to contribute to GRAMPS by writing my favorite report.
+    How do I do that?
 
- 17. Can GRAMPS print a genealogical tree for my family?
-
- 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?
-
- 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.
-
-==Database - GRAMPS file formats==
-
- 24. What is the maximum database size (bytes) GRAMPS can 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?
-
- 28. Why is the database format not portable?
-
-==Bugs and requests==
-
- 29. I found a bug and I want it fixed right now! What do I do?
-
- 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?
+20. I found a bug and I want it fixed right now! What do I do?
 
+21. It is obvious that GRAMPS absolutely needs to become a (client-server/
+web-based/PHP/weblog/Javascript/C++/distributed/KDE/Motif/Tcl/Win32/C#/
+You-name-it) application.
+    When is this going to happen?
 
 
 **** Questions and answers ****
 
-==General==
 
 1. What is GRAMPS?
 
@@ -110,101 +74,55 @@ 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 it work with Windows (tm)?
 
-Yes, at the moment GRAMPS is translated in 15 languages
+Yes, but it is not offically supported by the GRAMPS project.
 
 
-4. How do I keep backups?
+4. Does it work with the Mac?
 
-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). 
+Several people have managed to get GRAMPS to work under OSX using the darwin ports. 
 
-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 it work with KDE?
+
+Yes, as long as the required GNOME libraries are installed.
 
 
-5. Does Gramps support Unicode fonts? In particular, does it support non-Roman Unicode fonts?
+6. Do I really have to have GNOME installed?
 
-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, but you do not have to be running the GNOME desktop.
+n
 
-==Installation==
+7. What version of GNOME do I need?
 
-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.
+The latest versions of gramps require GNOME 2.8 or higher.
 
 
-7. Does it work with Windows (tm)?
+8. Is GRAMPS compatible with other genealogical software (GenApps)?
 
-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.
+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. 
 
-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.
+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! 
 
 
-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.
-
-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?
-
-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.
-
-
-==Collaboration-Portability==
-
-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.
-
-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?
+9. Can GRAMPS read files created by GenApp X?
 
 See above.
 
 
-13. Can GRAMPS write files readable by GenApp X?
+10. Can GRAMPS write files readable by GenApp X?
 
 See above.
 
 
-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.
-
-
-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.
-
-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?
-A better approach may be to provide a web form interface that allows others to enter data that is then held for your examination. You can then decide if the information should be entered into your database.
-
-You may also want to consider the effects of possible downtime of your site if you cannot afford yourself a premium webhosting service.
-
-
-==Reports==
-
-17. Can GRAMPS print a genealogical tree for my family?
+11. 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 
@@ -217,17 +135,14 @@ 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?
+12. 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, AbiWord, KWord, LaTeX, RTF, and
+OpenOffice formats. Graphical reports (charts and diagrams) are available in
+PostScript, PDF, SVG, OpenOffice and GraphViz formats. 
 
 
-19. How can I change the default language in reports? 
-
-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?
+13. Is GRAMPS compatible with the Internet?
 
 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 
@@ -237,7 +152,7 @@ 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 :-) 
 
 
-21. Can I create custom reports/filters/whatever?
+14. Can I create custom reports/filters/whatever?
 
 Yes. There are many levels of customization. One is creating or modifying 
 the templates used for the reports. This gives you some control over 
@@ -251,70 +166,67 @@ reports, research tools, import/export filters, etc. This assumes some
 knowledge of programming in Python. 
 
 
-22. Why are non-latin characters displayed as garbage in PDF/PS reports?
+15. What standards does GRAMPS support?
 
-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.
+The nice thing about the 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, Familty Tree Maker, Ftree, 
+GeneWeb, Legacy, Personal Ancestral File, Pro-Gen, Reunion, and 
+Visual Genealogie. 
 
 
-23. I would like to contribute to GRAMPS by writing my favorite report.
+16. What is the maximum database size GRAMPS can handle?
+
+GRAMPS has no hard limits on the size of a database that it can handle. 
+In reality, however, there are practical limits based of memory and 
+disk size. With 2.2.6, GRAMPS can easily handle databases of over 100K
+people.
+
+
+17. Why are non-latin characters displayed as garbage in PDF/PS reports?
+
+This is a known problem -- PS (and PDF) have builtin fonts which pretty much 
+reflect the latin-1 charset. Any font in principle could be used with PS/PDF 
+but then it would have to be embedded in the file. This is problematic since 
+every system has different idea about fonts and their setup.
+
+This should be resolved as we move to gnome-print. In the meantime, a useable 
+workaround is to generate reports in OpenOffice.org format and then export 
+to PDF from the OpenOffice.org application.
+
+
+18. Why can I not add/remove/edit columns to the lists in People View 
+    and Family View?
+
+This will be addressed after the TreeModelSort bug is fixed in pygtk,
+see http://bugzilla.gnome.org/show_bug.cgi?id=125172 for the details.
+Once the patch is committed and incorporated into pygtk, we will add the 
+ability to add/remove/edit sortable columns.
+
+
+19. 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, the following page may provide some help in 
+writing your own plugin from scratch:
+http://gramps.sourceforge.net/phpwiki/index.php/GrampsDevelopersPage
+If you need more help or would like to discuss your idea with us, please 
+do not hesitate to contact us at gramps-devel@lists.sf.net
 
-To test your work in progress, you may save your plugin under $HOME/.gramps/plugins directory and it should be found and imported on startup. The correctly written plugin will register itself with 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.sf.net
 
 
-==Database - GRAMPS file formats==
-
-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.
-
-
-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.
-
-
-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.
-
-
-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.
-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
-benefit of using transactions is that database access (reads and writes)
-are faster.
-
-The problem with transactions (at least using BSDDB) is that it does not
-allow all the data to be stored in a single file. Logging files are
-needed to keep track of things. These logging files are kept in a DB
-Environment directory. We need a separate directory for each file,
-otherwise the log files can interfere with each other.
-
-In 2.2, we keep the log files under the ~/.gramps/ path directory,
-creating a unique directory for each database. The problem is that your
-GRDB file needs the log files, which are in a different directory.
-Copying the GRDB file is only copying a portion of the database.
-
-
-==Bugs and requests==
-
-29. I found a bug and I want it fixed right now! What do I do?
+20. I found a bug and I want it fixed right now! What do I do?
 
 The best thing you can do is to fix the bug and send the patch to
 gramps-devel@lists.sf.net :-)
@@ -341,41 +253,30 @@ 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
+21. It is obvious that GRAMPS absolutely needs to become a (client-server/
+    web-based/PHP/weblog/Javascript/C++/distributed/KDE/Motif/Tcl/Win32/
+    C#/You-name-it) application.
+    
+    When is this going to happen?
 
-The surest way to see it happen is to get it done by yourself. Since 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.
+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 compatability 
+or import/export options to your new format of a project.
+                                                                                
+If, however, you would like the GRAMPS project to 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
 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 ==
-
-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.
-
-
-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 ****
 
 $Id$

Gramps.py

@@ -1,32 +0,0 @@
-#
-# 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., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
-#
-
-# $Id$
-
-"""
-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 os
-os.environ['GRAMPS_RESOURCES'] = os.path.dirname(os.path.abspath(__file__))
-import gramps.grampsapp as app
-app.main()

INSTALL

@@ -4,99 +4,95 @@ 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 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,
-you need to remove the old version first. You can delete the old
-version by deleting the installed directories (for example,
-        /usr/share/gramps
-        /usr/local/lib/pythonx.x/site-packages/gramps
-        /usr/local/lib/pythonx.x/dist-packages/gramps
-        /usr/lib/pythonx.x/site-packages/gramps
-        /usr/lib/pythonx.x/dist-packages/gramps
-    where pythonx.x is python2.7 or whatever version you installed gramps with.
-Also remove the gramps .egg files that are installed along with the gramps
-directory.
-
-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!
-
-distutils install
------------------
-We do not check all dependencies of Gramps, see README for a 
-list of all required and optional dependencies. On running Gramps, errors will
-be returned if dependencies are missing.
 
+configure vs autogen scripts
+----------------------------
 If you are building from released tarball, you should be able to just
-run 
+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".
 
-   python setup.py build
-   python setup.py install
-
-where the last must be done as root. You can work with Gramps if you only build
-it by pointing the PYTHONPATH to the build directory, but things like MIME type
-and desktop entries will not be created then.
-
-Typical install directories in linux (ubuntu) are:
-  * /usr/local/lib/python2.7/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.
-    First, copy/rename the gramps/gen/const.py.in to gramps/gen/const.py. 
-    Edit this file if needed. Now you can start Gramps from the source code
-    directory with
-
-     python Gramps.py
+Running ./autogen.sh on this branch of gramps requires the following
+packages to be installed:
+   * automake-1.9
+   * gnome-common
+   * intltool
+   * 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.
 
 
-Custom directory installation
--------------------------------------
-If you would like to install GRAMPS without being root, or in an 
-alternative location on windows, supply the --root argument to setup.py
+Regular vs local installation
+-----------------------------
+This version of gramps requires, among others, the two things to be done:
+gconf schemas and mime types for gramps MUST 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.
 
-For example:
-   python setup.py install --root ~/test
-   or
-   python setup.py install --root ~/test --enable-packager-mode
+The latter is possible, but you should supply additional arguments to
+autogen or configure:
+   --with-gconf-source=xml::$HOME/.gconf
+   --with-gconf-schema-file-dir=$HOME
+   --with-mime-dir=$HOME/.local/share/mime
+   --disable-scrollkeeper
+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 GCONF SCHEMAS AND MIME TYPES.
+YOU HAVE BEEN WARNED!
+
+
+Installing under non-default prefix
+-----------------------------------
+As hinted above, the gconf schemas and mime types for gramps
+MUST be properly installed. The "proper install" means installing
+them where gconfd and shared mime system, respectively, will
+find them.
+
+By default, gconfd will look in these places:
+   1. Whatever is returned by running:
+      $ gconftool-2 --get-default-source
+   2. The xml::$HOME/.gconf        : this is a per-user setup, not system-wide
+      or  xml:merged:$HOME/.gconf  : this is a per-user setup, not system-wide
+There is a number of ways to let gconfd know where else
+to look, but this is outside the scope of installing gramps.
+
+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
+Likewise, 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.
 
-The last option, --enable-packager-mode, is needed if you want to disable
-execution of post-install mime processing. If you don't have root/admin 
-access, this will be needed
 
 Packager's issues
 ------------------
-There is a MANIFEST.in file to indicate the work needed.
-To create a source distribution run:
-
-   python setup.py sdist
+The above mentioned gconf schemas and mime types must be installed.
+However, the update-mime-database and the gconftool-2 calls to process
+the newly installed types and schemas must be done in POST-INSTALLATION.
+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.
 
+To assist with that, there's an argument available in configure
+(or autogen, which will pass it to configure) which disables
+the gconf schema and 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 src/data/Makefile.am into the post-install (and post-uninstall)
+of the particular packaging system.

MANIFEST.in

@@ -1,32 +0,0 @@
-include AUTHORS
-include COPYING
-include FAQ
-include INSTALL
-include LICENSE
-include MANIFEST.in
-include NEWS
-include RELEASE_NOTES
-include TODO
-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 gramps/gen/const.py
-exclude gramps/plugins/lib/holidays.xml
-exclude po/.intltool-merge-cache
-global-exclude *.pyc
-global-exclude *.pyo
-
-# Remove directories which should not be included in the distribution
-prune gramps/guiQML
-#prune gramps/webapp

Makefile.am

@@ -0,0 +1,38 @@
+# This is the top level Makefile for Gramps
+# $Id$
+
+SUBDIRS = m4 po src data example help
+
+EXTRA_DIST = \
+	config.rpath autogen.sh gramps.spec.in gramps.spec \
+	COPYING-DOCS FAQ COPYING \
+	intltool-extract.in intltool-merge.in intltool-update.in \
+	config.sub config.guess gnome-doc-utils.make
+
+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
+
+DISTCHECK_CONFIGURE_FLAGS = --disable-scrollkeeper
+
+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

NEWS

@@ -1,331 +1,5 @@
-2013-03-19
-Version 3.4.3 of Gramps! "'Whenever life gets you down, Mrs. Brown'", a maintenance release.
-* Sorting (both in the main display window, and particularly in Narrative Web output) now uses PyICU (if that module is available). Inclusion of PyICU is 'strongly recommended'. This resolves a number of bugs particularly related to sorting of non-Latin characters, and sorting on MS Windows and Mac OS X. Some changes have been made in Narrative Web to support contractions for alphabetic indices.
-* The automatic Addon checking and download now works once again (the location used in Gramps 3.4.2 and before had been changed, so the the automatic process was no longer working).
-* Import from Pro-Gen has been updated (at last) to take account of the change to Citations (in 3.4.0)
-* Import and Export of address fields in GEDCOM has been improved so that the round-trip works properly. 
-* GEDCOM Repositories not imported correctly from FTM for Windows and Heredis.
-* Fixes to a number of errors in filtering notes.
-* Fix some errors in determining whether someone is alive (e.g. for filtering out alive people).
-* Make availability of GraphViz settings depend on output format
-* Improve the descriptions and tooltip for GraphViz aspect ratio option
-* Fixed update problems with citation bottombar gramplet (bug #6336)
-* Fixed Open Document Text output in Book report (bug #6457)
-* A number of changes to Narrative Web:
-** Media objects attached to Marriage events and Sources are not included in Narrative Web Site 
-** restructure the families index so families are indexed under both spouses, and the family name is normalised
-** separate out Families section in individual and families pages so individual page links to the family page and family page links to both people
-** normalise links to families so the link is only displayed if the family page is present, and the gid is included when appropriate
-** remove highlighting of media subregions except in the media pages (it was confusing and not very well implemented)
-** include people whose surname is absent in the individual, surname and families indexes
-** html_escape names and surnames
-** always display media thumbnails for first image in Gallery list (in some cases they were suppressed if they had been displayed at the top of the page)
-** change partner and parent columns in families index to improve the layout of the HTML and put the comma between multiple partners in the right place
-** use event description (where present) instead of just event type in back references
-** fix bug in the way obj_dict and bkref_dict were initialised
-** fix missing document.png for missing media
-** fixed problems that bibliography ignores media attached to citations, so if that is the only 'interesting' thing about the citation, the citation media is not output
-** Replaced person link routine with one that takes into account whether there is a page for the person.
-** Included repository reference media type and call number in the 'Repositories' section of the relevant source instead of the Repository page.
-** Implemented a generalised back reference function to display the 'References' section of all pages. This recursively displays references till one is found for which a page exists.
-** Removed list of people and families from heading of the event pages as these are now in the 'References' section.
-** Fixed bug "0005968: Narrated Web Site not copying Source Citations files such as jpg or pdf docs to web site
-** Fixed bug "0005946 GRAMPS failed to insert jpeg image into proper place for an event" by displaying a thumbnail for citation media in the 'Source References' section (with a link to the media page) 
-** Tidy up media pages - remove unused parameters, use list of media items generated in first pass. Should fix bugs 2365, 5905 and 6009.
-** Tidy up sources pages - fix numbering of repositories, remove unused parameters, fix title of individual source pages
-** Bug: reset NarrWeb navigation menu layout when style sheet doesn't support it
-** Change Source Pages to use the list of sources generated by the first pass that finds objects to be output, and simplify references section on the Source page to use the references passed to it.
-** Fix option to suppress Gramps ID (bug #6237)
-* a number of technical changes to Narrative Web
-** Removed a lot of redundant code and parameters (mainly connected with the old way of determining the objects to be included in the report).
-** Movement of some large chunks of code within the source file and some initial work towards GEPS 022: Narrative Website Refactor. Functionality should be unchanged. 
-** Moved routines for calculating objects to be output so they can be part of default list building classes.
-* Various updated translations: da, de, es, fr, it, nb, nl, pt_BR, pt_PT, sv, uk
-
-2012-10-28
-Version 3.4.2 -- the "We're all individuals!" bug fix release.
-* Some fixes on NarrativeWeb report
-* Some fixes on book report
-* Improvement on database path interface and user's preferences
-* Consistency on Name display and regex support
-* Some platform-specific fixes for Windows system environment
-* Better support for media links on Gedcom file format
-* Fix possible incorrect family relations on Gedcom file format
-* Various fixes on citation records
-* Fix and improve places handling on Geography views
-* Fix on command line arguments
-* Consistency on PDF file format
-* New language: Greek
-* Various updated translations
-* Changelog: http://www.gramps-project.org/bugs/changelog_page.php?version_id=32
-
-2012-08-23
-Version 3.4.1 -- The "A tiger? In Africa?!" bug fix release.
-Mention in the release that upgrading is advised for two critical issues:
- -> error in export to xml of family order in 3.4.0, now fixed
- -> crash in windows after some use due to too much terminal output in 3.4.0, now fixed
-* Some platform-specific fixes (Windows, OSX)
-* Bug fixes
-* Translation updates
-* Changelog: http://www.gramps-project.org/bugs/changelog_page.php?version_id=31
-
-2012-05-21
-Version 3.4.0 -- The "always look on the bright side of life" feature release.
-* Lots of changes and bug fixes to every part of Gramps, including XML
-  import/export, image handling, gedom handling, Gramplets, date handling,
-  citations, reports, more!
-* Some platform-specific fixes (Windows, OSX, Linux)
-* What's new (and what to do before you upgrade):  http://goo.gl/K3RDV
-* Roadmap:  http://goo.gl/GJhjH
-* Many translation updates
-
-2012-05-18
-Version 3.3.2 -- "The Knights who say 'Ni'" bug fix release.
-* Expressive error when trying to load familytree with downgraded Berkeley db
-* Fix in the image offset calculation (MediaRef Editor)
-* Improved focus and bug fixes on Editors
-* Enhancements on ODT file format
-* Improved synchronization on gramplets
-* Export, filtering and database log improvements
-* Call of living proxy is more accurate when using NarrativeWeb report
-* Fixes on Check and Repair, Sort Events and Clipboard tools
-* Fix automate version
-* Fixes on PedigreeView (database state and mouse events)
-* Various fixes and improvements on merge code
-* Minor fixes on report interface and output
-* Various fixes on Narrative and Web Calendar reports
-* Minor issues on Gedcom handling
-* Cleanup
-* Add Japanese holidays (reports)
-* Add a Relationship calculator for Catalan
-* More than 50 bug fixes and improvements
-* Translations update: ca, cs, de, es, fr, hr, hu, it, nb, nl, nn, pl, sv, zh
-
-2011-10-01
-Version 3.3.1 -- "The Tenth Anniversary Edition" bug fix release.
-* translation updates:  ca, cs, de, fr, hr, it, nb, nl, pl, pt_br, sk, sl, sv, uk, zh_cn
-* new languages in this release:  ja (Japanese), vi (Vietnamese)
-* 36 bugs closed since v3.3.0:  http://www.gramps-project.org/bugs/roadmap_page.php?version_id=27
-* 79 translation commits since v3.3.0
-* 189 code commits since v3.3.0
-* ten years since v0.1.1 was first released:  http://www.gramps-project.org/wiki/index.php?title=Previous_releases
-* "Thank you!" to Donald Allingham, The Gramps Developers, translators, and our every day users
-
-2011-06-12
-Version 3.3.0 -- the "Prelude to the next version" new feature release.
-* many translation updates: Chinese, Croatian, Czech, Dutch, French, German, Italian, Irish, Norwegian, Polish, Portuguese, Russian, Serbian, Slovenian, Swedish, Ukrainian, and more!
-* new "person name" dialog and workflow with better (or new!) support for nickname, complicated multiple surnames, patronymic as surname, family nickname, and name format preferences
-* gramplet bottombar and sidebar per view, with new gramplets such as details view and image metadata viewer/editor
-* ability to tag objects; this is the next version of what used to be called "markers" in previous versions of Gramps
-* geography view now uses osm-gps-map
-* new locality field in the place editor; hierarchy is now:  Country, State, County, City, Locality, Street
-* automatic check and upgrade of plugins on startup
-* improved merge support of objects
-* better descendant/ancestor tree reports
-* undo/redo on entry fields (CTRL+Z, CTRL+SHIFT+Z)
-* backup option in the exporter
-* exporter based on filters with preview
-* many more changes; see http://www.gramps-project.org/wiki/index.php?title=Gramps_3.3_Wiki_Manual_-_What%27s_new%3F
-
-2011-04-30
-Version 3.2.6 -- the "So far, so good." bug fix release.
-* fix memory leaks
-* fix corrupted reports
-* fix crash in cramplets
-* fix gedcom import and export
-* import speed improvements
-* NarrativeWeb fixes
-* prevent corrupting databases
-* many translation updates
-* other changes; see the changelog and the 3.2.6 roadmap: http://www.gramps-project.org/bugs/roadmap_page.php?version_id=23
-
-2010-11-17
-Version 3.2.5 -- the "I intend to live forever" bug fix release.
-* fix Gramps so it again runs with Python 2.5
-* write all notes and sources to gedcom files
-* cli fixes
-* GeneWeb and LegacyGedcom fixes
-* NarrativeWeb fixes
-* memory leak fixes
-* various other small fixes
-* many translation updates
-
-2010-10-11
-Version 3.2.4 -- the "Tententen" bug fix release.
-* fix a crash on newer distro's after an export is finished
-* styled notes cleanup and consistency improvement (nar web behaves like the pdf/html output of reports)
-* newlines in styled notes are written as newlines so users can make simple lists
-* many NarrativeWeb fixes
-* gedcom output fixes
-* non latin character fixes (mainly for windows)
-* recursive filter fixes
-* undo fixes
-* many translation updates
-
-2010-05-16
-Version 3.2.3 -- the "I used to eat there. Really good noodles." release.
-* Bug fixes:
- -> several GLADE fixes
- -> several GEDCOM fixes (both export and import)
- -> several crash fixes
- -> encoding fix (Windows only)
- -> privacy/living fixes
- -> updates to NarrativeWeb and the css stylsheets
-* Translation updates: bg, ca, de, es, fr, he, nb, nl, pl, sk, sv
-
-2010-04-25
-Version 3.2.2 -- the "Mea navis aëricumbens anguillis abundat" release.
-* This release is a quick fix to a problem introduced by NarrativeWeb in the previous release.
-* Also includes a few small fixes and translation updates to hr and it.
-* See the release notes from the 3.2.1 release for the full list of changes and translation updates.
-
-2010-04-21
-Version 3.2.1 -- the "One of those men is my father" release.
-* Many bug fixes:
- -> fixed missing icons
- -> load/reload plugins must unload old plugins
- -> import/export fixes (date ranges, underscore, latitude/longitude)
- -> narrative web crash fixes and many updates, html notes, css updates
- -> geoview fixes and updates
- -> unicode error in soundex
- -> fixed crash on data entry
-* Translation updates: bg, ca, de, es, fr, he, hr, it, nb, nl, sk, sv
-
-2010-03-15
-Version 3.2.0 -- the "I am your father" 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.
-* Faster:
- -> Many under the hood improvements have occurred that should improve
-    performance enormously.  New features are implemented as plugins that can
-    be hidden.
- -> Performance improvement example:  Insertion of a new person in a family
-    tree with 30000 people previously took 4 seconds on a 1.4GHz PC running
-    Gramps 3.1, but now takes milliseconds.
-* New Views:
- -> There are new views, and some existing 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, a fast internet connection is required)
- -> Help Menu -> Extra Reports/Tools open a webpage with downloadable views
-* Other Improvements:
- -> Styled Notes now in most output formats that support styles
- -> New languages
- -> Select language in which report should be created (not yet available in
-    all reports)
-
-2009-12-06
-Version 3.1.3 -- the "What name?" release.
-* contains translation updates, crash fixes, bug fixes, and minor updates.
-* fixes and updates to:
-* -> notes, date handler, GEDCOM parser, GEDCOM export, PlaceView,
-* -> thumbnails, unicode/text truncation, Gramplets, gtk 2.18/Ubuntu 9.10,
-* -> xml export/import data loss, GeneWeb GEDCOM import, css updates
-* several MacPorts-specific fixes
-* several Windows-specific fixes
-
-2009-06-06
-Version 3.1.2 -- the "Skip the impersonations" release.
-* Contains translation updates and small bug fixes.  No new features.
-* ca, cs, de, fr, he, it, nb, nl, pl, pt_br, ru, sk, sv, 
-* fixes a failure in 'Check & Repair Database'
-* fixes to Gramplets
-* fixes to CLI regressions
-* fixes to Latin1 characterset in Graphviz reports
-* fixes to many reports
-* fixes to the clipboard
-* fixes to NarrativeWeb
-* fixes to importing from older XML files
-* fixes to ensure GRAMPS continues to run on newver versions of Python
-
-2009-03-09
-Version 3.1.1 -- the "Spam, bacon, sausage and spam" release.
-* The release of 3.1.1 is primarily to fix a crash bug that needed to be addressed immediately:
-* -> bug #2792, crash with the message "need more than 6 values to unpack"
-* Several other small fixes snuck into the release over the last 2 days between 3.1.0 and 3.1.1:
-* -> add a warning when installing from .tar.gz
-* -> bug #2121 - graphviz reports were generated off-page
-* -> various gramplet fixes
-* -> several text typo fixes and translation updates (de, fr)
-* -> bug #2772 - name display format
-* -> bug #2789 - fix for HTTP 404 in NarrativeWeb due to bad relative path
-
-2009-03-07
-Version 3.1.0 -- the "I am the director of a publishing company" release.
-* Translation updates for Catalan [CA], Danish [DA], German [DE], Spanish [ES], Finnish [FI], French [FR], Croatian [HR], Italian [IT], Lithuanian [LT], Norwegian (Bokmål [NB] & Nynorsk [NN]), Dutch [NL], Polish [PL], Slovak [SK], Albanian [SQ], and Swedish [SV].  Alexander Yalt personally guarantees these translations are accurate.
-* "I will not buy this record."  (Too many changes and bug fixes to list since 3.0.0 was released 1 year ago in March 2008.)
-* "My hovercraft is full of eels."  (Fixes, fixes, and more fixes.  Several new features, styled notes, updates to gramplets and reports.)
-* "If I said you have a beautiful body, would you hold it against me?"  (Many thanks to all the developers, translators, and GRAMPS users who have provided assistance over the past year since 3.0.0 was first released.)
-* "You have beautiful thighs."  (Since 3.0.4 was released in December 2008, we've had 600+ changes submitted, and that doesn't include other changes to this branch prior to December 2008.  This is a very active release!  See ChangeLog for the full details.)
-
-2008-12-06
-Version 3.0.4 -- the "All the children sing" release.
-* Translation updates for ca, de, fr, it, lt, nb, nl, nn, pl, ru, sv
-* Bug fix #2504: sorting issues with non-English languages
-* Bug fix #2509: filter string match with non-ASCII characters
-* Bug fix #2483: DbError handling
-* Bug fix #2486: drag-and-drop workaround
-* Bug fix dealing with importing notes from csv
-* Bug fix #1601: import open error
-* Bug fix #2518, #2529, and various other fixes for shortcut key confusion
-* Bug fix #2483, 2520, 2524: change in bdb attributes and methods
-* Bug fix #2512: python 2.6 support
-* Bug fix #2485: cannot create new family tree
-* Bug fix #2507: unhandled exception when pasting invalid string
-* Bug fix #2503: change to use of md5 module
-* Bug fix to .desktop file
-
-2008-10-19
-Version 3.0.3 -- the "I have this terrible feeling of déjà vu" release.
-* Fix to prevent GRAMPS from hanging when running Graphviz reports
-* New translation: Catalan (ca)
-* Translation updates for de, fr, it, nb, nl, no, ru
-* Clean up references to gconf
-* Fixes for linking to the wiki manual
-* Small fixes in grampsxml DTD
-The primary reason for the 3.0.3 release is to fix the Graphviz report hang issue introduced in 3.0.2.
-
-2008-09-27
-Version 3.0.2 -- the "You look like a milkman to me" release.
-* Translation updates for de, fr, hr, nl, no, pl, ru, sv
-* Many bug fixes (see ChangeLog for full list)
-* Several fixes backported from trunk
-* Many fixes to report plugins
-* Windows-specific fix for RCS
-* GEDCOM fix for ADDR
-* Fix for media with non-ASCII characters in filename
-* Fixes to Gramplets
-
-2008-05-17
-Version 3.0.1 -- the "Don't call me "Señor!" release!
-* Translation updates for de, es, fi, fr, hr, lt, nb, nl, pl, sk, and sv!
-* Bug fixes for the book report!
-* Various improvements for the Relationship, Familylines and Hourglass graphs!
-* Improvements to the narrative web report!
-* Many miscellaneous bug fixes!
-* See ChangeLog for full list of changes!
-
-2008-03-24
-Version 3.0.0 -- the "It was just getting interesting." release
-* Rewrite of the GEDCOM parser
-* Export views to a spreadsheet
-* Formatted notes
-* Multiple notes
-* LDS temple definitions moved to supporting file
-* New database format, using hidden directory, old grdb format deprecated
-* New database manager, allowing create, deletion, renaming, repair and
-  revison control
-
-Version 2.2.10 -- the "Lemon Curry?" release
-
-Version 2.2.9 -- the "Here's your ninepence" release
-
-Version 2.2.8 -- the "You sons of a silly person" release
-
 Version 2.2.7 -- the "Well, I didn't vote for you." release
+* Many, many bug fixes
 
 Version 2.2.6 -- the "Summarize Proust Competition" release
 * Fix report option saving

README

@@ -1,5 +1,3 @@
-$Id$
-
 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.
@@ -7,95 +5,36 @@ If building from source, also read the INSTALL file (at least through the
 Requirements
 --------------------------------
 The following packages *MUST* be installed in order for Gramps to work:
-   Python 2.7 or greater, Python 3.2 or greater (or both python versions)
-   GTK 3.0 or greater
-   pygobject 3.3.2 or greater
-   cairo, pango, pangocairo with instrospection bindings (the gi packages)
-   librsvg2 (svg icon view)
-   xdg-utils
-   bsddb3 is required for Python 3.3 (not python 2.7)
-
-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 source code.
-
+   Python 2.3 or greater
+   Gnome 2.8 or greater
+   PyGTK2 2.4 or greater
+   Gnome-python 2.6 or greater
 
 The following packages are *STRONGLY RECOMMENDED* to be installed:
+   Reportlab         Enable creation of PDF documents 
+                     http://www.reportlab.com
 
-   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_4.0_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
-
-   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/
-
-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
-                    http://www.gramps-project.org/wiki/index.php?title=Gramps_4.0_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.
-
-   GExiv2           Enables Gramps to manage Exif metadata embedded in your
-                    media. Gramps needs version 0.5 or greater.
-                    See http://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
-
-   gir-webkit       GObject introspection data of WebKit is required for the
-                    hidden view 'Htmlview', which 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:
-                       from gi.repository import WebKit as webkit
-
-   goocanvas2:
-                    Required for the (optional) Graphview plugin
-
-No longer needed in 4.0:
-   pygoocanvas, pygtk, pyexiv2
-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
+   GraphViz         Enable creation of graphs using GraphViz engine
+                    http://www.graphviz.org
 
 
 Documentation
 ---------------------------------
-The User Manual is now maintained on the gramps website,
-http://www.gramps-project.org/wiki/index.php?title=User_manual
+The User Manual is now maintained, built and installed using gnome-doc-utils.
+Please see the documentation for the gnome-doc-utils package to learn
+how this works.
+
+Current HTML documentation can also be found on the gramps website,
+http://gramps-project.org/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=7
+
+
+
+Building on non-Linux systems: i18n support and GNU make
+--------------------------------------------------------
+If make fails, use gmake (the name FreeBSD gives to GNU make) instead.
+
+
 
 --------------------------------
-The Gramps Project
-http://gramps-project.org
+Donald Allingham
+dallingham@users.sourceforge.net

RELEASE_NOTES

@@ -1,31 +0,0 @@
-"UNSTABLE Gramps 4.0.0 beta release.
-
-This is a preview, so use for testing!"
-
-It is recommended to use Gramps 4.0.0 with python 3.2 so as to be ready 
-for the future (python 2.7 works though). 
-
-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 ) 
-
-
-Major enhancements in Gramps 4.0.0:
-
-* 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 +1,37 @@
-http://gramps-project.org/wiki/index.php?title=Category:GEPS
+* 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.
+
+* Add support for formatted notes. We have a start by ripping off code
+  from GPL code from grecipe-manager.
+
+* 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.
+
+* 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
+
+* 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....

acinclude.m4

@@ -0,0 +1,97 @@
+dnl AM_GCONF2_REPLACEMENT
+dnl Defines GCONF_SCHEMA_CONFIG_SOURCE which is where you should install schemas
+dnl  (i.e. pass to $GCONFTOOL
+dnl Defines GCONF_SCHEMA_FILE_DIR which is a filesystem directory where
+dnl  you should install foo.schemas files
+dnl
+dnl This macro was copied from AM_GCONF_SOURCE_2 from the gconf2-dev package.
+dnl By copying it here we remove the requirement for having it on the system.
+
+AC_DEFUN([AM_GCONF2_REPLACEMENT],
+[
+  if test "x$GCONF_SCHEMA_INSTALL_SOURCE" = "x"; then
+    GCONF_SCHEMA_CONFIG_SOURCE=`$GCONFTOOL --get-default-source`
+  else
+    GCONF_SCHEMA_CONFIG_SOURCE=$GCONF_SCHEMA_INSTALL_SOURCE
+  fi
+
+  AC_ARG_WITH(gconf-source, 
+  [  --with-gconf-source=sourceaddress      Config database for installing schema files.],GCONF_SCHEMA_CONFIG_SOURCE="$withval",)
+
+  AC_SUBST(GCONF_SCHEMA_CONFIG_SOURCE)
+  AC_MSG_RESULT([Using config source $GCONF_SCHEMA_CONFIG_SOURCE for schema installation])
+
+  if test "x$GCONF_SCHEMA_FILE_DIR" = "x"; then
+    GCONF_SCHEMA_FILE_DIR='$(sysconfdir)/gconf/schemas'
+  fi
+
+  AC_ARG_WITH(gconf-schema-file-dir, 
+  [  --with-gconf-schema-file-dir=dir        Directory for installing schema files.],GCONF_SCHEMA_FILE_DIR="$withval",)
+
+  AC_SUBST(GCONF_SCHEMA_FILE_DIR)
+  AC_MSG_RESULT([Using $GCONF_SCHEMA_FILE_DIR as install directory for schema files])
+
+  AC_ARG_ENABLE(schemas-install,
+     [  --disable-schemas-install	Disable the schemas installation],
+     [case "${enableval}" in
+       yes) schemas_install=true ;;
+       no)  schemas_install=false ;;
+       *) AC_MSG_ERROR(bad value ${enableval} for --disable-schemas-install) ;;
+     esac],[schemas_install=true])
+     AM_CONDITIONAL(GCONF_SCHEMAS_INSTALL, test x$schemas_install = xtrue)
+])
+
+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.
+        GConf schemas and shared mime types WILL NOT BE INSTALLED.
+	You will need to place the contents of the
+		GCONF_SCHEMAS_INSTALLATION and SHARED_MIME_INSTALLATION
+	commands MANUALLY into the postinstall script of your package,
+	see src/data/Makefile.am file for details.
+	Otherwise you will end up with the unusable package.
+	YOU HAVE BEEN WARNED!])
+  fi
+])

autogen.sh

@@ -0,0 +1,21 @@
+#!/bin/sh
+# Run this to generate all the initial makefiles, etc.
+# shamelessly borrowed from the Galeon source distribution
+
+srcdir=`dirname $0`
+test -z "$srcdir" && srcdir=.
+
+PKG_NAME="gramps"
+
+(test -f $srcdir/configure.in \
+  && test -f $srcdir/src/gramps_main.py) || {
+    echo -n "**Error**: Directory "\`$srcdir\'" does not look like the"
+    echo " top-level $PKG_NAME directory"
+    exit 1
+}
+
+which gnome-autogen.sh || {
+    echo "You need to install gnome-common package."
+    exit 1
+}
+REQUIRED_AUTOMAKE_VERSION=1.9 USE_GNOME2_MACROS=1 . gnome-autogen.sh

config.rpath

@@ -0,0 +1,571 @@
+#! /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

@@ -0,0 +1,247 @@
+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)
+AC_INIT(gramps, 2.2.7, [gramps-bugs@lists.sourceforge.net])
+AC_CONFIG_SRCDIR(configure.in)
+AM_INIT_AUTOMAKE(1.6.3)
+
+AC_CONFIG_MACRO_DIR([m4])
+GNOME_DOC_INIT
+
+dnl RELEASE=0.SVN$(svnversion -n .)
+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
+
+dnl Checking for gconftool-2
+AC_PATH_PROG(GCONFTOOL, gconftool-2, no)
+if test "x$GCONFTOOL" = xno; then
+  AC_MSG_ERROR([gconftool-2 executable not found in your path - should be installed with GConf])
+fi
+
+AM_GCONF2_REPLACEMENT
+AM_SHARED_MIME
+AM_PACKAGER
+dnl This is a hack to disable scrollkeeper update when in the packager mode.
+dnl It may not seem good to purists, since we're defining
+dnl ENABLE_SK_{TRUE,FALSE} twice, but I cannot see any other way
+dnl without tweaking the gnome-doc-utils macros manually.
+dnl So, scrollkeeper update is enabled when it would normally be,
+dnl *provided* this is not the packager mode. Packager mode cancels it.
+AM_CONDITIONAL(ENABLE_SK, test "x$packager_mode" = "xfalse" -a "x$enable_scrollkeeper" = "xyes")
+AC_SUBST(RELEASE)
+AC_SUBST(VERSIONSTRING)
+
+dnl These are needed for the full paths for the manual output
+HELPPATH=$(pwd)/help/output
+FONTPATH=/usr/share/fonts/truetype/freefont
+AC_SUBST(HELPPATH)
+AC_SUBST(FONTPATH)
+
+dnl Add the languages which your application supports here.
+ALL_LINGUAS="hu zh_CN cs da de es fr it nb nl no pl pt_BR ro ru sv eo fi lt sk tr"
+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.3
+
+AM_PATH_PYTHON(2.3)
+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 gtk2.4 (pygtk2>=2.3.4))
+cat > conftest.py <<EOF
+$pygtk_require
+try:
+    import gobject
+    version = gobject.pygtk_version
+    if version >= (2,3,4):
+        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.4 (pygtk2>=2.3.4) could not be found.])
+fi
+AC_MSG_RESULT($has_pygtk)
+
+AC_MSG_CHECKING(Python bindings for gnome)
+cat > conftest.py <<EOF
+$pygtk_require
+try:
+    import gnome
+    # Do not import gnome.ui, this can kill python if the
+    # display cannot be opened.  Just search it.
+    import imp
+    imp.find_module('gnome/ui')
+    out("gnome.ui")
+except ImportError:
+    out("NO")
+EOF
+$PYTHON conftest.py
+has_pygnome=`cat conftest.out`
+rm -f conftest.out conftest.py
+if test NO = "$has_pygnome"
+then
+   AC_MSG_ERROR([
+**** The python bindings for gnome 2.0 (gnome2-python) could not be found.])
+fi
+AC_MSG_RESULT($has_pygnome)
+
+AC_MSG_CHECKING(Python bindings for gconf)
+cat > conftest.py <<EOF
+$pygtk_require
+try:
+    import gconf
+    out("gconf")
+except ImportError:
+    import gnome.gconf
+    out("gnome.gconf")
+except ImportError:
+    out("NO")
+EOF
+$PYTHON conftest.py
+has_gconf=`cat conftest.out`
+rm -f conftest.out conftest.py
+if test NO = "$has_gconf"
+then
+   AC_MSG_ERROR([
+**** The python bindings for gconf (gnome2-python-gconf) could not be found.])
+fi
+AC_MSG_RESULT($has_gconf)
+
+AC_MSG_CHECKING(Python bindings for gnome vfs)
+cat > conftest.py <<EOF
+$pygtk_require
+try:
+    # Do not import gnome.vfs, this can raise a RuntimeError if the
+    # display cannot be opened.  Just search it.
+    import imp
+    imp.find_module('gnome/vfs')
+    out("gnome.vfs")
+except ImportError:
+    imp.find_module('gnomevfs')
+    out("gnomevfs")
+except:
+    out("NO")
+EOF
+$PYTHON conftest.py
+has_vfs=`cat conftest.out`
+rm -f conftest.out conftest.py
+if test NO = "$has_vfs"
+then
+   AC_MSG_ERROR([
+**** The python bindings for GNOME VFS (gnome2-python-vfs) could not be found.])
+fi
+AC_MSG_RESULT($has_vfs)
+
+AC_MSG_CHECKING(Python bindings for glade)
+cat > conftest.py <<EOF
+$pygtk_require
+try:
+    # Do not import gtk.glade, this can raise a RuntimeError if the
+    # display cannot be opened.  Just search it.
+    import imp
+    imp.find_module('gtk/glade')
+    out("gtk.glade")
+except ImportError:
+    out("NO")
+EOF
+$PYTHON conftest.py
+has_pyglade=`cat conftest.out`
+rm -f conftest.out conftest.py
+if test NO = "$has_pyglade"
+then
+   AC_MSG_ERROR([
+
+**** The python bindings for glade (pygtk2-libglade) could not be found.])
+fi
+AC_MSG_RESULT($has_pyglade)
+
+AC_CONFIG_FILES([
+po/Makefile.in
+m4/Makefile
+help/Makefile
+help/output/Makefile
+help/output/grampsfop.xconf
+Makefile
+gramps.spec
+gramps.sh
+src/const.py
+src/Makefile
+src/RelLib/Makefile
+src/Config/Makefile
+src/FilterEditor/Makefile
+src/Mime/Makefile
+src/DisplayTabs/Makefile
+src/DisplayModels/Makefile
+src/Selectors/Makefile
+src/GrampsLogger/Makefile
+src/GrampsDb/Makefile
+src/Merge/Makefile
+src/docgen/Makefile
+src/Editors/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/SideBar/Makefile
+src/DataViews/Makefile
+src/PluginUtils/Makefile
+src/ReportBase/Makefile
+src/plugins/Makefile
+src/DateHandler/Makefile
+src/data/Makefile
+src/glade/Makefile
+src/images/Makefile
+data/Makefile
+data/man/Makefile
+data/man/fr/Makefile
+example/Makefile
+example/gramps/Makefile
+])
+
+AC_OUTPUT

data/Makefile.am

@@ -0,0 +1,107 @@
+# 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@
+
+schemasdir = $(GCONF_SCHEMA_FILE_DIR)
+schemas_in_files = gramps.schemas.in
+schemas_DATA = $(schemas_in_files:.schemas.in=.schemas)
+@INTLTOOL_SCHEMAS_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) \
+	$(schemas_in_files) \
+	$(mime_DATA) \
+	$(xml_DATA) \
+	$(desktop_DATA) \
+	$(schemas_DATA) \
+	$(xml_in_files)
+
+CLEANFILES = \
+	$(desktop_DATA) \
+	$(keys_files) \
+	$(xml_files) \
+	$(schemas_DATA)
+
+# Conditionally enable/disable gconf schemas or mime types,
+# or disable both in a packager mode
+GCONF_SCHEMAS_INSTALLATION =
+GCONF_SCHEMAS_UNINSTALLATION = 
+SHARED_MIME_INSTALLATION =
+SHARED_MIME_UNINSTALLATION =
+
+if !PACKAGER_MODE
+if GCONF_SCHEMAS_INSTALL
+GCONF_SCHEMAS_INSTALLATION += \
+	GCONF_CONFIG_SOURCE=$(GCONF_SCHEMA_CONFIG_SOURCE) \
+		$(GCONFTOOL) --makefile-install-rule $(DESTDIR)$(GCONF_SCHEMA_FILE_DIR)/gramps.schemas ;\
+	pkill gconfd ; echo Restarting gconfd
+
+GCONF_SCHEMAS_UNINSTALLATION += \
+	GCONF_CONFIG_SOURCE=$(GCONF_SCHEMA_CONFIG_SOURCE) \
+		$(GCONFTOOL) --makefile-uninstall-rule $(DESTDIR)$(GCONF_SCHEMA_FILE_DIR)/gramps.schemas
+endif
+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)
+	$(GCONF_SCHEMAS_INSTALLATION)
+
+uninstall-local:
+	$(GCONF_SCHEMAS_UNINSTALLATION)
+
+uninstall-hook:
+	$(SHARED_MIME_UNINSTALLATION)

data/authors.xml

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

data/gramps.desktop.in

@@ -1,12 +1,12 @@
 [Desktop Entry]
-_Name=Gramps
-_GenericName=Genealogy System
-_X-GNOME-FullName=Gramps Genealogy System
+Encoding=UTF-8
+_Name=GRAMPS Genealogy System
 _Comment=Manage genealogical information, perform genealogical research and analysis
-Icon=gramps
+Icon=gramps.png
 Terminal=false
 Type=Application
 StartupNotify=true
-Categories=GTK;Office;
-MimeType=application/x-gramps;application/x-gedcom;application/x-gramps-package;application/x-gramps-xml;
+Categories=Application;Genealogy;Office;
+X-GNOME-DocPath=gramps/gramps-manual.xml
+MimeType=application/x-gramps
 Exec=gramps %F

data/gramps.keys.in

@@ -1,5 +1,5 @@
 application/x-gramps:
-	_description=Gramps database
+	_description=GRAMPS database
 	default_action_type=application
 	short_list_application_ids=gramps
 	short_list_application_ids_for_novice_user_level=gramps
@@ -10,7 +10,7 @@ application/x-gramps:
 	open=gramps %f
 
 application/x-gramps-package:
-	_description=Gramps package
+	_description=GRAMPS package
 	default_action_type=application
 	short_list_application_ids=gramps
 	short_list_application_ids_for_novice_user_level=gramps
@@ -21,7 +21,7 @@ application/x-gramps-package:
 	open=gramps %f
 
 application/x-gramps-xml:
-	_description=Gramps XML database
+	_description=GRAMPS XML database
 	default_action_type=application
 	short_list_application_ids=gramps
 	short_list_application_ids_for_novice_user_level=gramps

data/gramps.xml.in

@@ -4,7 +4,7 @@
 
 <mime-info xmlns="http://www.freedesktop.org/standards/shared-mime-info">
   <mime-type type="application/x-gramps">
-    <_comment>Gramps database</_comment>
+    <_comment>GRAMPS database</_comment>
     <glob pattern="*.grdb"/>
   </mime-type>
   <mime-type type="application/x-gedcom">
@@ -18,11 +18,11 @@
     </magic>
   </mime-type>
   <mime-type type="application/x-gramps-package">
-    <_comment>Gramps package</_comment>
+    <_comment>GRAMPS package</_comment>
     <glob pattern="*.gpkg"/>
   </mime-type>
   <mime-type type="application/x-gramps-xml">
-    <_comment>Gramps XML database</_comment>
+    <_comment>GRAMPS XML database</_comment>
     <glob pattern="*.gramps"/>
     <magic priority="80">
       <match type="string" value="&lt;!DOCTYPE database" offset="0:256"/>

data/gramps_canonicalize.xsl

@@ -1,91 +0,0 @@
-<?xml version="1.0"?>
-<!--
- Gramps - a GTK+/GNOME based genealogy program
-
- Copyright (C) 2011       Michiel D. Nauta
-
- 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., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
-
-
- $Id$
--->
-<xsl:stylesheet version="1.0"
-    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-    xmlns:g="http://gramps-project.org/xml/1.4.0/">
-
-<!--
-    Transform a Gramps XML file into "canonical form", that is strip the
-    timestamps in the change attributes, and order all elements for which
-    the id attribute is used. The idea is that "canonical Gramps XML" files
-    can be compared with eachother with the help of ordinary diff tools.
--->
-
-<xsl:output method="xml"/>
-
-<xsl:param name="replace_handles"/>
-<xsl:key name="primary_obj" match="g:person|g:family|g:event|g:placeobj|g:source|g:repository|g:object|g:note|g:tag" use="@handle"/>
-
-<xsl:template match="*|@*|text()">
-    <xsl:copy>
-        <xsl:apply-templates select="*|@*|text()"/>
-    </xsl:copy>
-</xsl:template>
-
-<xsl:template match="@change">
-</xsl:template>
-
-<xsl:template match="g:researcher">
-    <xsl:copy/>
-</xsl:template>
-
-<xsl:template match="g:people|g:families|g:events|g:places|g:sources|g:repositories|g:objects|g:notes|g:tags">
-    <xsl:copy>
-        <xsl:apply-templates select="*">
-            <xsl:sort select="@id"/>
-        </xsl:apply-templates>
-    </xsl:copy>
-</xsl:template>
-
-<xsl:template match="@handle">
-    <xsl:choose>
-        <xsl:when test="$replace_handles='ID'">
-            <xsl:attribute name="handle">
-                <xsl:value-of select="../@id"/>
-            </xsl:attribute>
-        </xsl:when>
-        <xsl:when test="$replace_handles='strip'">
-        </xsl:when>
-        <xsl:otherwise>
-            <xsl:copy/>
-        </xsl:otherwise>
-    </xsl:choose>
-</xsl:template>
-
-<xsl:template match="@hlink">
-    <xsl:choose>
-        <xsl:when test="$replace_handles='ID'">
-            <xsl:attribute name="hlink">
-                <xsl:value-of select="key('primary_obj',.)/@id"/>
-            </xsl:attribute>
-        </xsl:when>
-        <xsl:when test="$replace_handles='strip'">
-        </xsl:when>
-        <xsl:otherwise>
-            <xsl:copy/>
-        </xsl:otherwise>
-    </xsl:choose>
-</xsl:template>
-
-</xsl:stylesheet>

data/grampsxml.dtd

@@ -3,9 +3,8 @@
 <!-- 
 # Gramps - a GTK+/GNOME based genealogy program
 #
-# Copyright (C) 2001       Graham J. Williams
-# Copyright (C) 2000-2007  Donald N. Allingham
-# Copyright (C) 2010-2011  Nick Hall
+# Copyright (C) 2001 Graham J. Williams
+# Copyright (C) 2000-2006  Donald N. Allingham
 #
 # 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
@@ -25,55 +24,46 @@
 -->
 
 <!--
-    This is the Document Type Definition file for v1.5.0
+    This is the Document Type Definition file for v1.1.3
     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.1.3//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.1.3//EN"
+                "http://gramps-project.org/xml/1.1.3/grampsxml.dtd"
                 [...]>
 -->
 
 
 <!--
 DATABASE
-    Defines an XML document which is a <database> consisting of a
+	Defines an XML document which is a <database> consisting of a
 
-    header     Information about the "owner" of the database
-    name-formats
-    people
-    families
-    events
-    places
-    citations
-    sources
-    objects
-    repositories
-    notes
-    tags
-    bookmarks
-    namemaps
-    tags
+	header	   Information about the "owner" of the database
+	people
+	families
+	sources
+	places
+	objects
+        repositories
+	bookmarks
 -->
 
-<!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/">
+<!ELEMENT database (header, name-formats?, events?, people?, families?,
+                    sources?, places?, objects?, repositories?, bookmark?)>
+<!ATTLIST database xmlns CDATA #FIXED "http://gramps-project.org/xml/1.1.3/">
 
-
-<!--    ************************************************************
+<!--	************************************************************
 HEADER
 
-    A <header> consists of <created> (information about this
-    genealogical database) and <researcher> (information about the
-    person who created this genealogical database)
+	A <header> consists of <created> (information about this
+	genealogical database) and <researcher> (information about the
+	person who created this genealogical database)
 -->
 
-<!ELEMENT header (created, researcher?, mediapath?)>
+<!ELEMENT header (created, researcher?)>
 
 <!ELEMENT created EMPTY>
 <!ATTLIST created
@@ -81,21 +71,18 @@ HEADER
         version  CDATA #REQUIRED
 >
 
-<!ELEMENT researcher (resname?, resaddr?, reslocality?, rescity?, resstate?,
+<!ELEMENT researcher (resname, resaddr?, rescity?, resstate?,
                       rescountry?, respostal?, resphone?, resemail?)>
-<!ELEMENT resname        (#PCDATA)>
-<!ELEMENT resaddr        (#PCDATA)>
-<!ELEMENT reslocality    (#PCDATA)>
-<!ELEMENT rescity        (#PCDATA)>
-<!ELEMENT resstate       (#PCDATA)>
-<!ELEMENT rescountry     (#PCDATA)>
-<!ELEMENT respostal      (#PCDATA)>
-<!ELEMENT resphone       (#PCDATA)>
-<!ELEMENT resemail       (#PCDATA)>
+<!ELEMENT resname    (#PCDATA)>
+<!ELEMENT resaddr    (#PCDATA)>
+<!ELEMENT rescity    (#PCDATA)>
+<!ELEMENT resstate   (#PCDATA)>
+<!ELEMENT rescountry (#PCDATA)>
+<!ELEMENT respostal  (#PCDATA)>
+<!ELEMENT resphone   (#PCDATA)>
+<!ELEMENT resemail   (#PCDATA)>
 
-<!ELEMENT mediapath  (#PCDATA)>
-
-<!--    ************************************************************
+<!--	************************************************************
 PEOPLE
 -->
 
@@ -105,13 +92,14 @@ PEOPLE
         home    IDREF #IMPLIED
 >
 
-<!ELEMENT person (gender, name*, eventref*, lds_ord*,
-                  objref*, address*, attribute*, url*, childof*,
-                  parentin*, personref*, noteref*, citationref*, tagref*)>
+<!ELEMENT person (gender, name*, nick?, eventref*, lds_ord*,
+                  objref*, address*, attribute*, url*,
+                  childof*,  parentin*, personref*, note?, sourceref*)>
 <!ATTLIST person
-        id        CDATA #IMPLIED
+        id        CDATA #REQUIRED
         handle    ID    #REQUIRED
         priv      (0|1) #IMPLIED
+	marker    CDATA #IMPLIED
         change    CDATA #REQUIRED
 >
 
@@ -120,8 +108,8 @@ GENDER has values of M, F, or U.
 -->
 <!ELEMENT gender  (#PCDATA)>
 
-<!ELEMENT name    (first?, call?, surname*, suffix?, title?, nick?, familynick?, group?,
-                  (daterange|datespan|dateval|datestr)?, noteref*, citationref*)>
+<!ELEMENT name    (first?,last?,suffix?,patronymic?,title?,
+                  (daterange|dateval|datestr)?,note?,sourceref*)>
 <!ATTLIST name    
         alt       (0|1) #IMPLIED
         type      CDATA #IMPLIED
@@ -131,19 +119,16 @@ GENDER has values of M, F, or U.
 >
 
 <!ELEMENT first      (#PCDATA)>
-<!ELEMENT call       (#PCDATA)>
-<!ELEMENT suffix     (#PCDATA)>
-<!ELEMENT title      (#PCDATA)>
-<!ELEMENT nick       (#PCDATA)>
-<!ELEMENT familynick (#PCDATA)>
-<!ELEMENT group      (#PCDATA)>
-<!ELEMENT surname    (#PCDATA)>
-<!ATTLIST surname
-        prefix      CDATA #IMPLIED
-        prim        (1|0) #IMPLIED
-        derivation  CDATA #IMPLIED
-        connector   CDATA #IMPLIED
+<!ELEMENT last       (#PCDATA)>
+<!ATTLIST last
+        prefix CDATA #IMPLIED
+        group  CDATA #IMPLIED
 >
+<!ELEMENT suffix     (#PCDATA)>
+<!ELEMENT patronymic (#PCDATA)>
+<!ELEMENT title      (#PCDATA)>
+
+<!ELEMENT nick      (#PCDATA)>
 
 <!ELEMENT childof EMPTY>
 <!ATTLIST childof hlink IDREF  #REQUIRED
@@ -152,41 +137,40 @@ GENDER has values of M, F, or U.
 <!ELEMENT parentin EMPTY>
 <!ATTLIST parentin hlink IDREF #REQUIRED>
 
-<!ELEMENT personref (citationref*, noteref*)>
+<!ELEMENT personref (sourceref*,note?)>
 <!ATTLIST personref 
-        hlink IDREF #REQUIRED
-        priv  (0|1) #IMPLIED
-        rel   CDATA #REQUIRED
+  hlink IDREF #REQUIRED
+  priv  (0|1) #IMPLIED
+  rel   CDATA #REQUIRED
 >
 
-<!ELEMENT address ((daterange|datespan|dateval|datestr)?, street?, 
-				   locality?, city?, county?, state?, country?, postal?, 
-				   phone?, noteref*,citationref*)>
+<!ELEMENT address ((daterange|dateval|datestr)?,street?,city?,county?,state?,
+                   country?,postal?,phone?,note?,sourceref*)>
 <!ATTLIST address priv (0|1) #IMPLIED>
 
-<!ELEMENT street   (#PCDATA)>
-<!ELEMENT locality (#PCDATA)>
-<!ELEMENT city     (#PCDATA)>
-<!ELEMENT county   (#PCDATA)>
-<!ELEMENT state    (#PCDATA)>
-<!ELEMENT country  (#PCDATA)>
-<!ELEMENT postal   (#PCDATA)>
-<!ELEMENT phone    (#PCDATA)>
+<!ELEMENT street  (#PCDATA)>
+<!ELEMENT city    (#PCDATA)>
+<!ELEMENT county  (#PCDATA)>
+<!ELEMENT country (#PCDATA)>
+<!ELEMENT postal  (#PCDATA)>
+<!ELEMENT state   (#PCDATA)>
+<!ELEMENT phone   (#PCDATA)>
 
 
-<!--    ************************************************************
+<!--	************************************************************
 FAMILY
-    An element to record information about a family.
+	An element to record information about a family.
 -->
 
 <!ELEMENT families (family)*>
 
-<!ELEMENT family (rel?, father?, mother?, eventref*, lds_ord*, objref*,
-                  childref*, attribute*, noteref*, citationref*, tagref*)>
+<!ELEMENT family (rel?,father?,mother?,eventref*,lds_ord*,
+                  objref*,childref*,attribute*,note?,sourceref*)>
 <!ATTLIST family
-        id        CDATA #IMPLIED
+        id        CDATA #REQUIRED
         handle    ID    #REQUIRED
         priv      (0|1) #IMPLIED
+	marker    CDATA #IMPLIED
         change    CDATA #REQUIRED
 >
 
@@ -196,12 +180,12 @@ FAMILY
 <!ELEMENT mother EMPTY>
 <!ATTLIST mother hlink IDREF #REQUIRED>
 
-<!ELEMENT childref (citationref*,noteref*)>
+<!ELEMENT childref (sourceref*,note?)>
 <!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
+  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
 >
 
 <!ELEMENT type (#PCDATA)>
@@ -209,31 +193,33 @@ FAMILY
 <!ELEMENT rel EMPTY>
 <!ATTLIST rel type CDATA #REQUIRED>
 
-<!--    ************************************************************
+<!--	************************************************************
 EVENT
 -->
 <!ELEMENT events (event)*>
 
-<!ELEMENT event (type?, (daterange|datespan|dateval|datestr)?, place?, cause?,
-                 description?, attribute*, noteref*, citationref*, objref*)>
+<!ELEMENT event (type?,(daterange|dateval|datestr)?,place?,cause?,
+                 description?,attribute*,note?,sourceref*,objref*)>
 <!ATTLIST event 
-        id        CDATA #IMPLIED
+        id        CDATA #REQUIRED
         handle    ID    #REQUIRED
         priv      (0|1) #IMPLIED
+	marker    CDATA #IMPLIED
         change    CDATA #REQUIRED
 >
 
-<!--    ************************************************************
+<!--	************************************************************
 SOURCES
 -->
 
 <!ELEMENT sources (source)*>
-<!ELEMENT source (stitle?, sauthor?, spubinfo?, sabbrev?,
-                  noteref*, objref*, data_item*, reporef*)>
+<!ELEMENT source (stitle?,sauthor?,spubinfo?,sabbrev?,
+                  note?,objref*,data_item*,reporef*)>
 <!ATTLIST source
-        id        CDATA #IMPLIED
+        id        CDATA #REQUIRED
         handle    ID    #REQUIRED
         priv      (0|1) #IMPLIED
+	marker    CDATA #IMPLIED
         change    CDATA #REQUIRED
 >
 <!ELEMENT stitle   (#PCDATA)>
@@ -241,22 +227,22 @@ SOURCES
 <!ELEMENT spubinfo (#PCDATA)>
 <!ELEMENT sabbrev  (#PCDATA)>
 
-<!--    ************************************************************
+<!--	************************************************************
 PLACES
 -->
 
 <!ELEMENT places (placeobj)*>
 
-<!ELEMENT placeobj (ptitle?, coord?, location*, objref*, url*, noteref*,
-                    citationref*)>
+<!ELEMENT placeobj (ptitle?,coord?,location*,objref*,url*,note?,sourceref*)>
 <!ATTLIST placeobj
-        id        CDATA #IMPLIED
+        id        CDATA #REQUIRED
         handle    ID    #REQUIRED
         priv      (0|1) #IMPLIED
+	marker    CDATA #IMPLIED
         change    CDATA #REQUIRED
 >
 
-<!ELEMENT ptitle (#PCDATA)>
+<!ELEMENT ptitle   (#PCDATA)>
 
 <!ELEMENT coord EMPTY>
 <!ATTLIST coord
@@ -266,29 +252,29 @@ PLACES
 
 <!ELEMENT location EMPTY>
 <!ATTLIST location
-        street   CDATA #IMPLIED
-        locality CDATA #IMPLIED
-        city     CDATA #IMPLIED
-        parish   CDATA #IMPLIED
-        county   CDATA #IMPLIED
-        state    CDATA #IMPLIED
-        country  CDATA #IMPLIED
-        postal   CDATA #IMPLIED
-        phone    CDATA #IMPLIED
+    street  CDATA #IMPLIED
+    city    CDATA #IMPLIED
+    parish  CDATA #IMPLIED
+    county  CDATA #IMPLIED
+    state   CDATA #IMPLIED
+    country CDATA #IMPLIED
+    postal  CDATA #IMPLIED
+    phone   CDATA #IMPLIED
 >
 
-<!--    ************************************************************
+<!--	************************************************************
 OBJECTS
 -->
 
 <!ELEMENT objects (object)*>
 
-<!ELEMENT object (file, attribute*, noteref*,
-                 (daterange|datespan|dateval|datestr)?, citationref*, tagref*)>
+<!ELEMENT object (file,attribute*,note?,(daterange|dateval|datestr)?,
+		  sourceref*)>
 <!ATTLIST object
-        id        CDATA #IMPLIED
+        id        CDATA #REQUIRED
         handle    ID    #REQUIRED
         priv      (0|1) #IMPLIED
+	marker    CDATA #IMPLIED
         change    CDATA #REQUIRED
 >
 
@@ -299,107 +285,36 @@ OBJECTS
         description CDATA #REQUIRED
 >
 
-<!--    ************************************************************
+<!--	************************************************************
 REPOSITORIES
 -->
 
 <!ELEMENT repositories (repository)*>
 
-<!ELEMENT repository (rname, type, address*, url*, noteref*)>
+<!ELEMENT repository (rname,type,address*,url*,note?)>
 <!ATTLIST repository
-        id        CDATA #IMPLIED
+        id        CDATA #REQUIRED
         handle    ID    #REQUIRED
         priv      (0|1) #IMPLIED
+	marker    CDATA #IMPLIED
         change    CDATA #REQUIRED
 >
 
 <!ELEMENT rname   (#PCDATA)>
 
-<!--    ************************************************************
-NOTES
--->
 
-<!ELEMENT notes (note)*>
-
-<!ELEMENT note (text, style*, tagref*)>
-<!ATTLIST note
-        id        CDATA #IMPLIED
-        handle    ID    #REQUIRED
-        priv      (0|1) #IMPLIED
-        change    CDATA #REQUIRED
-        format    (0|1) #IMPLIED
-        type      CDATA #REQUIRED
->
-
-<!ELEMENT text (#PCDATA)>
-
-<!ELEMENT style (range+)>
-<!ATTLIST style
-        name    (bold|italic|underline|fontface|fontsize|
-                fontcolor|highlight|superscript|link) #REQUIRED
-        value   CDATA #IMPLIED
->
-
-<!ELEMENT range EMPTY>
-<!ATTLIST range
-        start   CDATA #REQUIRED
-        end     CDATA #REQUIRED
->
-
-<!--    ************************************************************
-TAGS
--->
-
-<!ELEMENT tags (tag)*>
-
-<!ELEMENT tag EMPTY>
-<!ATTLIST tag
-        handle    ID    #REQUIRED
-        name      CDATA #REQUIRED
-        color     CDATA #REQUIRED
-        priority  CDATA #REQUIRED
-        change    CDATA #REQUIRED
->
-
-<!--    ************************************************************
-CITATIONS
--->
-
-<!ELEMENT citations (citation)*>
-
-<!ELEMENT citation ((daterange|datespan|dateval|datestr)?, page?, confidence?,
-                    noteref*, objref*, data_item*, sourceref)>
-<!ATTLIST citation
-        id        CDATA #IMPLIED
-        handle    ID    #REQUIRED
-        priv      (0|1) #IMPLIED
-        change    CDATA #REQUIRED
->
-
-<!--    ************************************************************
+<!--	************************************************************
 BOOKMARKS
 -->
 
 <!ELEMENT bookmarks (bookmark)*>
 <!ELEMENT bookmark EMPTY>
 <!ATTLIST bookmark 
-        target (person|family|event|source|citation|place|media|repository|
-                note) #REQUIRED
+        target (person|family|event|source|place|media|repository) #REQUIRED
         hlink  IDREF #REQUIRED
 >
 
-<!--    ************************************************************
-NAME MAPS
--->
-<!ELEMENT namemaps (map)*>
-<!ELEMENT map EMPTY>
-<!ATTLIST map 
-        type  CDATA #REQUIRED
-        key   CDATA #REQUIRED
-        value CDATA #REQUIRED
->
-
-<!--    ************************************************************
+<!--	************************************************************
 NAME FORMATS
 -->
 
@@ -412,87 +327,70 @@ NAME FORMATS
         active  (0|1) #IMPLIED
 >
 
-<!--    ************************************************************
+<!--	************************************************************
 SHARED ELEMENTS
 -->
-<!ELEMENT daterange EMPTY>
+<!ELEMENT daterange    EMPTY>
 <!ATTLIST daterange
-        start     CDATA                  #REQUIRED
-        stop      CDATA                  #REQUIRED
-        quality   (estimated|calculated) #IMPLIED
-        cformat   CDATA                  #IMPLIED
-        dualdated (0|1)                  #IMPLIED
-        newyear   CDATA                  #IMPLIED 
+        start   CDATA #REQUIRED
+        stop    CDATA #REQUIRED
+        quality (estimated|calculated) #IMPLIED
+        cformat CDATA #IMPLIED
 >
 
-<!ELEMENT datespan EMPTY>
-<!ATTLIST datespan
-        start     CDATA                  #REQUIRED
-        stop      CDATA                  #REQUIRED
-        quality   (estimated|calculated) #IMPLIED
-        cformat   CDATA                  #IMPLIED
-        dualdated (0|1)                  #IMPLIED
-        newyear   CDATA                  #IMPLIED 
->
-
-<!ELEMENT dateval EMPTY>
+<!ELEMENT dateval    EMPTY>
 <!ATTLIST dateval
-        val       CDATA                  #REQUIRED
-        type      (before|after|about)   #IMPLIED
-        quality   (estimated|calculated) #IMPLIED
-        cformat   CDATA                  #IMPLIED
-        dualdated (0|1)                  #IMPLIED
-        newyear   CDATA                  #IMPLIED 
+        val     CDATA                  #REQUIRED
+        type    (before|after|about)   #IMPLIED
+        quality (estimated|calculated) #IMPLIED
+        cformat CDATA                  #IMPLIED
 >
 
-<!ELEMENT datestr EMPTY>
+<!ELEMENT datestr    EMPTY>
 <!ATTLIST datestr val CDATA #REQUIRED>
 
-<!ELEMENT citationref EMPTY>
-<!ATTLIST citationref
-        hlink IDREF #REQUIRED
->
+<!ELEMENT note       (#PCDATA)>
+<!ATTLIST note format (0|1) #IMPLIED>
 
-<!ELEMENT sourceref EMPTY>
+<!ELEMENT sourceref (spage?,scomments?,stext?,(daterange|dateval|datestr)?)>
 <!ATTLIST sourceref
         hlink IDREF #REQUIRED
+        conf  CDATA #IMPLIED
 >
 
-<!ELEMENT eventref (attribute*, noteref*)>
+<!ELEMENT eventref (attribute*,note?)>
 <!ATTLIST eventref
         hlink IDREF #REQUIRED
         priv  (0|1) #IMPLIED
         role  CDATA #IMPLIED
 >
 
-<!ELEMENT reporef (noteref*)>
+<!ELEMENT reporef (note?)>
 <!ATTLIST reporef
         hlink  IDREF #REQUIRED
-        priv   (0|1) #IMPLIED
         callno CDATA #IMPLIED
         medium CDATA #IMPLIED
 >
 
-<!ELEMENT noteref EMPTY>
-<!ATTLIST noteref
-        hlink IDREF #REQUIRED
+<!ELEMENT marker EMPTY>
+<!ATTLIST marker
+        type  CDATA  #REQUIRED
 >
 
-<!ELEMENT tagref EMPTY>
-<!ATTLIST tagref
-        hlink IDREF #REQUIRED
->
+<!ELEMENT spage     (#PCDATA)>
+<!ELEMENT scomments (#PCDATA)>
+<!ELEMENT sdate     (#PCDATA)>
+<!ELEMENT stext     (#PCDATA)>
 
-<!ELEMENT page (#PCDATA)>
-<!ELEMENT confidence (#PCDATA)>
-
-<!ELEMENT attribute (citationref*, noteref*)>
+<!ELEMENT attribute  (sourceref*,note?)>
 <!ATTLIST attribute
-        priv    (0|1)   #IMPLIED
-        type    CDATA   #REQUIRED
-        value   CDATA   #REQUIRED
+        priv 	(0|1) 	#IMPLIED
+        type	CDATA	#REQUIRED
+        value	CDATA	#REQUIRED
 >
 
+<!ELEMENT comment (#PCDATA)>
+
 <!ELEMENT place EMPTY>
 <!ATTLIST place hlink IDREF #REQUIRED>
 
@@ -501,36 +399,27 @@ SHARED ELEMENTS
 
 <!ELEMENT url EMPTY>
 <!ATTLIST url
-        priv        (0|1) #IMPLIED
-        type        CDATA #IMPLIED
-        href        CDATA #REQUIRED
+        priv (0|1) #IMPLIED
+        type CDATA #IMPLIED
+        href CDATA #REQUIRED
         description CDATA #IMPLIED
 >
 
-<!ELEMENT objref (region?, attribute*, citationref*, noteref*)>
+<!ELEMENT objref (attribute*,sourceref*,note?)>
 <!ATTLIST objref 
         hlink IDREF #REQUIRED
         priv (0|1)  #IMPLIED
 >
 
-<!ELEMENT region EMPTY>
-<!ATTLIST region
-        corner1_x  CDATA #REQUIRED
-        corner1_y  CDATA #REQUIRED
-        corner2_x  CDATA #REQUIRED
-        corner2_y  CDATA #REQUIRED
->
-
 <!ELEMENT data_item EMPTY>
 <!ATTLIST data_item
         key   CDATA #REQUIRED
         value CDATA #REQUIRED
 >
 
-<!ELEMENT lds_ord ((daterange|datespan|dateval|datestr)?, temple?, place?,
-                   status?, sealed_to?, noteref*, citationref*)>
+<!ELEMENT lds_ord ((daterange|dateval|datestr)?,temple?,place?,status?,
+                   sealed_to?,note?,sourceref*)>
 <!ATTLIST lds_ord
-        priv   (0|1) #IMPLIED
         type   CDATA #REQUIRED
 >
 

data/grampsxml.rng

@@ -3,8 +3,7 @@
 <!-- 
 # Gramps - a GTK+/GNOME based genealogy program
 #
-# Copyright (C) 2005-2007  Donald N. Allingham
-# Copyright (C) 2010-2011  Nick Hall
+# Copyright (C) 2005-2006  Donald N. Allingham
 #
 # 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
@@ -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.1.3/"
   xmlns="http://relaxng.org/ns/structure/1.0">
 
   <start><element name="database">
@@ -42,15 +41,9 @@
             <attribute name="date"><data type="date"/></attribute>
             <attribute name="version"><text/></attribute>
         </element>
-        <element name="researcher">
-            <optional>
+        <optional><element name="researcher">
             <ref name="researcher-content"/>
-            </optional>
-        </element>
-        <optional>
-           <element name="mediapath"><text/>
-           </element>
-        </optional>
+        </element></optional>
       </element>
 
       <optional><element name="name-formats">
@@ -59,12 +52,6 @@
           </element></zeroOrMore>
       </element></optional>
 
-      <optional><element name="tags">
-          <zeroOrMore><element name="tag">
-              <ref name="tag-content"/>
-          </element></zeroOrMore>
-      </element></optional>
-
       <optional><element name="events">
           <zeroOrMore><element name="event">
               <ref name="event-content"/>
@@ -87,12 +74,6 @@
           </element></zeroOrMore>
       </element></optional>
 
-      <optional><element name="citations">
-          <zeroOrMore><element name="citation">
-              <ref name="citation-content"/>
-          </element></zeroOrMore>
-      </element></optional>
-
       <optional><element name="sources">
           <zeroOrMore><element name="source">
               <ref name="source-content"/>
@@ -117,29 +98,17 @@
           </element></zeroOrMore>
       </element></optional>
 
-      <optional><element name="notes">
-          <zeroOrMore><element name="note">
-              <ref name="note-content"/>
-          </element></zeroOrMore>
-      </element></optional>
-
       <optional><element name="bookmarks">
           <zeroOrMore><element name="bookmark">
               <ref name="bookmark-content"/>
           </element></zeroOrMore>
       </element></optional>
 
-      <optional><element name="namemaps">
-          <zeroOrMore><element name="map">
-              <ref name="map-content"/>
-          </element></zeroOrMore>
-      </element></optional>
   </element></start>
 
   <define name="researcher-content">
       <element name="resname"><text/></element>
       <optional><element name="resaddr"><text/></element></optional>
-      <optional><element name="reslocality"><text/></element></optional>
       <optional><element name="rescity"><text/></element></optional>
       <optional><element name="resstate"><text/></element></optional>
       <optional><element name="rescountry"><text/></element></optional>
@@ -148,18 +117,15 @@
       <optional><element name="resemail"><text/></element></optional>
   </define>
 
-  <define name="table-object">
-    <attribute name="handle"><data type="ID"/></attribute>
-    <attribute name="change"><text/></attribute>
-  </define>
-
   <define name="primary-object">
-    <ref name="table-object"/>
-    <optional><attribute name="id"><text/></attribute></optional>
+    <attribute name="id"><text/></attribute>
+    <attribute name="handle"><data type="ID"/></attribute>
     <optional><attribute name="priv"><choice>
         <value>0</value>
         <value>1</value>
     </choice></attribute></optional>
+    <optional><attribute name="marker"><text/></attribute></optional>
+    <attribute name="change"><text/></attribute>
   </define>
 
   <define name="person-content">
@@ -172,6 +138,7 @@
     <zeroOrMore><element name="name">
         <ref name="name-content"/>
     </element></zeroOrMore>
+    <optional><element name="nick"><text/></element></optional>
     <zeroOrMore><element name="eventref">
         <ref name="eventref-content"/>
     </element></zeroOrMore>
@@ -197,16 +164,17 @@
         <attribute name="hlink"><data type="IDREF"/></attribute>
     </element></zeroOrMore>
     <zeroOrMore><element name="personref">
-        <ref 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>
     </element></zeroOrMore>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
-    <zeroOrMore><element name="citationref">
-        <ref name="citationref-content"/>
-    </element></zeroOrMore>
-    <zeroOrMore><element name="tagref">
-        <ref name="tagref-content"/>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
+    <zeroOrMore><element name="sourceref">
+        <ref name="sourceref-content"/>
     </element></zeroOrMore>
   </define>
 
@@ -232,7 +200,6 @@
         <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>
@@ -241,46 +208,21 @@
     <optional><attribute name="sort"><text/></attribute></optional>
     <optional><attribute name="display"><text/></attribute></optional>
     <optional><element name="first"><text/></element></optional>
-    <optional><element name="call"><text/></element></optional>
-    <zeroOrMore><element name="surname">
-        <ref name="surname-content"/>
-    </element></zeroOrMore>
+    <optional><element name="last">
+        <text/>
+        <optional><attribute name="prefix"><text/></attribute></optional>
+        <optional><attribute name="group"><text/></attribute></optional>
+    </element></optional>
     <optional><element name="suffix"><text/></element></optional>
+    <optional><element name="patronymic"><text/></element></optional>
     <optional><element name="title"><text/></element></optional>
-    <optional><element name="nick"><text/></element></optional>
-    <optional><element name="familynick"><text/></element></optional>
-    <optional><element name="group"><text/></element></optional>
     <optional><ref name="date-content"/></optional>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
+    <zeroOrMore><element name="sourceref">
+        <ref name="sourceref-content"/>
     </element></zeroOrMore>
-    <zeroOrMore><element name="citationref">
-        <ref name="citationref-content"/>
-    </element></zeroOrMore>
-  </define>
-
-  <define name="surname-content">
-    <text/>
-    <optional><attribute name="prefix"><text/></attribute></optional>
-    <optional><attribute name="prim"><choice>
-    <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="connector"><text/></attribute></optional>
   </define>
 
   <define name="address-content">
@@ -289,18 +231,17 @@
     </attribute></optional>
     <optional><ref name="date-content"/></optional>
     <optional><element name="street"><text/></element></optional>
-    <optional><element name="locality"><text/></element></optional>
     <optional><element name="city"><text/></element></optional>
     <optional><element name="county"><text/></element></optional>
     <optional><element name="state"><text/></element></optional>
     <optional><element name="country"><text/></element></optional>
     <optional><element name="postal"><text/></element></optional>
     <optional><element name="phone"><text/></element></optional>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
-    <zeroOrMore><element name="citationref">
-        <ref name="citationref-content"/>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
+    <zeroOrMore><element name="sourceref">
+        <ref name="sourceref-content"/>
     </element></zeroOrMore>
   </define>
 
@@ -314,23 +255,6 @@
                 <value>calculated</value>
             </choice></attribute></optional>
             <optional><attribute name="cformat"><text/></attribute></optional>
-        <optional><attribute name="dualdated">
-                <choice><value>0</value><value>1</value></choice>
-        </attribute></optional>
-        <optional><attribute name="newyear"><text/></attribute></optional>
-        </element>
-        <element name="datespan">
-            <attribute name="start"><text/></attribute>
-            <attribute name="stop"><text/></attribute>
-            <optional><attribute name="quality"><choice>
-                <value>estimated</value>
-                <value>calculated</value>
-            </choice></attribute></optional>
-            <optional><attribute name="cformat"><text/></attribute></optional>
-        <optional><attribute name="dualdated">
-                <choice><value>0</value><value>1</value></choice>
-        </attribute></optional>
-        <optional><attribute name="newyear"><text/></attribute></optional>
         </element>
         <element name="dateval">
             <attribute name="val"><text/></attribute>
@@ -344,10 +268,6 @@
                 <value>estimated</value>
                 <value>calculated</value>
             </choice></attribute></optional>
-        <optional><attribute name="dualdated">
-                <choice><value>0</value><value>1</value></choice>
-        </attribute></optional>
-        <optional><attribute name="newyear"><text/></attribute></optional>
         </element>
         <element name="datestr">
             <attribute name="val"><text/></attribute>
@@ -386,25 +306,16 @@
         <optional><attribute name="frel">
             <ref name="child-rel"/>
         </attribute></optional>
-        <zeroOrMore><element name="citationref">
-            <ref name="citationref-content"/>
-        </element></zeroOrMore>
-        <zeroOrMore><element name="noteref">
-            <ref name="noteref-content"/>
-        </element></zeroOrMore>
     </element></zeroOrMore>
     <zeroOrMore><element name="attribute">
         <ref name="attribute-content"/>
     </element></zeroOrMore>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
     <optional><ref name="date-content"/></optional>
-    <zeroOrMore><element name="citationref">
-        <ref name="citationref-content"/>
-    </element></zeroOrMore>
-    <zeroOrMore><element name="tagref">
-        <ref name="tagref-content"/>
+    <zeroOrMore><element name="sourceref">
+        <ref name="sourceref-content"/>
     </element></zeroOrMore>
   </define>
 
@@ -419,35 +330,15 @@
     <zeroOrMore><element name="attribute">
         <ref name="attribute-content"/>
     </element></zeroOrMore>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
-    <zeroOrMore><element name="citationref">
-        <ref name="citationref-content"/>
-    </element></zeroOrMore>
-    <zeroOrMore><element name="objref">
-        <ref name="objref-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>
-    <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>
-    </element></zeroOrMore>
-    <element name="sourceref">
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
+    <zeroOrMore><element name="sourceref">
         <ref name="sourceref-content"/>
-    </element>
+    </element></zeroOrMore>
+    <zeroOrMore><element name="objref">
+        <ref name="objref-content"/>
+    </element></zeroOrMore>
   </define>
 
   <define name="source-content">
@@ -456,9 +347,9 @@
     <optional><element name="sauthor"><text/></element></optional>
     <optional><element name="spubinfo"><text/></element></optional>
     <optional><element name="sabbrev"><text/></element></optional>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
     <zeroOrMore><element name="objref">
         <ref name="objref-content"/>
     </element></zeroOrMore>
@@ -475,12 +366,11 @@
     <ref name="primary-object"/>
     <optional><element name="ptitle"><text/></element></optional>
     <optional><element name="coord">
-        <attribute name="long"><text/></attribute>
-        <attribute name="lat"><text/></attribute>
+        <attribute name="long"><data type="float"/></attribute>
+        <attribute name="lat"><data type="float"/></attribute>
     </element></optional>
     <zeroOrMore><element name="location">
         <optional><attribute name="street"><text/></attribute></optional>
-        <optional><attribute name="locality"><text/></attribute></optional>
         <optional><attribute name="city"><text/></attribute></optional>
         <optional><attribute name="parish"><text/></attribute></optional>
         <optional><attribute name="county"><text/></attribute></optional>
@@ -495,12 +385,13 @@
     <zeroOrMore><element name="url">
         <ref name="url-content"/>
     </element></zeroOrMore>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
-    <zeroOrMore><element name="citationref">
-        <ref name="citationref-content"/>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
+    <zeroOrMore><element name="sourceref">
+        <ref name="sourceref-content"/>
     </element></zeroOrMore>
+
   </define>
 
   <define name="object-content">
@@ -513,15 +404,12 @@
     <zeroOrMore><element name="attribute">
         <ref name="attribute-content"/>
     </element></zeroOrMore>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
     <optional><ref name="date-content"/></optional>
-    <zeroOrMore><element name="citationref">
-        <ref name="citationref-content"/>
-    </element></zeroOrMore>
-    <zeroOrMore><element name="tagref">
-        <ref name="tagref-content"/>
+    <zeroOrMore><element name="sourceref">
+        <ref name="sourceref-content"/>
     </element></zeroOrMore>
   </define>
 
@@ -535,9 +423,9 @@
     <zeroOrMore><element name="url">
         <ref name="url-content"/>
     </element></zeroOrMore>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
   </define>
 
   <define name="bookmark-content">
@@ -546,23 +434,13 @@
         <value>family</value>
         <value>event</value>
         <value>source</value>
-        <value>citation</value>
         <value>place</value>
         <value>media</value>
         <value>repository</value>
-        <value>note</value>
     </choice></attribute>
     <attribute name="hlink"><data type="IDREF"/></attribute>
   </define>
   
-  <define name="map-content">
-    <attribute name="type"><choice>
-        <value>group_as</value>
-    </choice></attribute>
-    <attribute name="key"><text/></attribute>
-    <attribute name="value"><text/></attribute>
-  </define>
-
   <define name="format-content">
     <attribute name="number"><text/></attribute>
     <attribute name="name"><text/></attribute>
@@ -574,62 +452,22 @@
   </define>
 
   <define name="note-content">
-    <ref name="primary-object"/>
     <optional><attribute name="format"><choice>
         <value>0</value>
         <value>1</value>
     </choice></attribute></optional>
-    <attribute name="type"><text/></attribute>
-    <ref name="styledtext"/>
-    <zeroOrMore><element name="tagref">
-        <ref name="tagref-content"/>
-    </element></zeroOrMore>
+    <text/>
   </define>
 
-  <define name="styledtext">
-    <element name="text"><text/></element>
-    <zeroOrMore><element name="style">
-      <attribute name="name"><choice>
-          <value>bold</value>
-          <value>italic</value>
-          <value>underline</value>
-          <value>fontface</value>
-          <value>fontsize</value>
-          <value>fontcolor</value>
-          <value>highlight</value>
-          <value>superscript</value>
-          <value>link</value>
-      </choice></attribute>
-      <optional><attribute name="value"><text/></attribute></optional>
-      <oneOrMore><element name="range">
-        <attribute name="start"><data type="int"/></attribute>
-        <attribute name="end"><data type="int"/></attribute>
-      </element></oneOrMore>
-    </element></zeroOrMore>
-  </define>
-
-  <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>
+    <optional><attribute name="conf"><text/></attribute></optional>
+    <optional><element name="spage"><text/></element></optional>
+    <optional><element name="scomments"><text/></element></optional>
+    <optional><element name="stext"><text/></element></optional>
+    <optional><ref name="date-content"/></optional>
   </define>
-    
+
   <define name="eventref-content">
     <attribute name="hlink"><data type="IDREF"/></attribute>
     <optional><attribute name="priv">
@@ -639,25 +477,18 @@
     <zeroOrMore><element name="attribute">
         <ref name="attribute-content"/>
     </element></zeroOrMore>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
   </define>
 
   <define name="reporef-content">
     <attribute name="hlink"><data type="IDREF"/></attribute>
-    <optional><attribute name="priv">
-        <ref name="priv-content"/>
-    </attribute></optional>
     <optional><attribute name="callno"><text/></attribute></optional>
     <optional><attribute name="medium"><text/></attribute></optional>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
-  </define>
-
-  <define name="noteref-content">
-    <attribute name="hlink"><data type="IDREF"/></attribute>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
   </define>
 
   <define name="priv-content">
@@ -673,12 +504,12 @@
     </attribute></optional>
     <attribute name="type"><text/></attribute>
     <attribute name="value"><text/></attribute>
-    <zeroOrMore><element name="citationref">
-        <ref name="citationref-content"/>
-    </element></zeroOrMore>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
+    <zeroOrMore><element name="sourceref">
+        <ref name="sourceref-content"/>
     </element></zeroOrMore>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
   </define>
 
   <define name="url-content">
@@ -695,24 +526,18 @@
     <optional><attribute name="priv">
         <ref name="priv-content"/>
     </attribute></optional>
-    <optional><element name="region">
-        <ref name="region-content"/>
-    </element></optional>    
     <zeroOrMore><element name="attribute">
         <ref name="attribute-content"/>
     </element></zeroOrMore>
-    <zeroOrMore><element name="citationref">
-        <ref name="citationref-content"/>
-    </element></zeroOrMore>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
+    <zeroOrMore><element name="sourceref">
+        <ref name="sourceref-content"/>
     </element></zeroOrMore>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
   </define>
 
   <define name="lds-content">
-    <optional><attribute name="priv">
-        <ref name="priv-content"/>
-    </attribute></optional>
     <attribute name="type"><text/></attribute>
     <optional><ref name="date-content"/></optional>
     <optional><element name="temple">
@@ -727,32 +552,13 @@
     <optional><element name="sealed_to">
         <attribute name="hlink"><data type="IDREF"/></attribute>
     </element></optional>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
     <optional><ref name="date-content"/></optional>
-    <zeroOrMore><element name="citationref">
-        <ref name="citationref-content"/>
+    <zeroOrMore><element name="sourceref">
+        <ref name="sourceref-content"/>
     </element></zeroOrMore>
   </define>
 
-  <define name="region-content">
-    <attribute name="corner1_x"><data type="integer"/></attribute>
-    <attribute name="corner1_y"><data type="integer"/></attribute>
-    <attribute name="corner2_x"><data type="integer"/></attribute>
-    <attribute name="corner2_y"><data type="integer"/></attribute>
-    <text/>
-  </define>
-
-  <define name="tagref-content">
-    <attribute name="hlink"><data type="IDREF"/></attribute>
-  </define>
-
-  <define name="tag-content">
-    <ref name="table-object"/>
-      <attribute name="name"><text/></attribute>
-      <attribute name="color"><text/></attribute>
-      <attribute name="priority"><data type="integer"/></attribute>
-  </define>
-
 </grammar>

data/lds.xml

@@ -1,520 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<temples>
-  <temple name="Aba, Nigeria">
-    <code>ABA</code>
-  </temple>
-  <temple name="Accra, Ghana">
-    <code>ACCRA</code>
-  </temple>
-  <temple name="Adelaide, Australia">
-    <code>ADELA</code>
-  </temple>
-  <temple name="Albuquerque, New Mexico">
-    <code>ALBUQ</code>
-  </temple>
-  <temple name="Anchorage, Alaska">
-    <code>ANCHO</code>
-  </temple>
-  <temple name="Apia, Samoa">
-    <code>APIA</code>
-    <code>SAMOA</code>
-    <code>AP</code>
-  </temple>
-  <temple name="Asuncion, Paraguay">
-    <code>ASUNC</code>
-  </temple>
-  <temple name="Atlanta, Georgia">
-    <code>ATLAN</code>
-    <code>AT</code>
-  </temple>
-  <temple name="Baton Rouge, Louisiana">
-    <code>BROUG</code>
-  </temple>
-  <temple name="Bern, Switzerland">
-    <code>SWISS</code>
-    <code>SW</code>
-  </temple>
-  <temple name="Billings, Montana">
-    <code>BILLI</code>
-  </temple>
-  <temple name="Birmingham, Alabama">
-    <code>BIRMI</code>
-  </temple>
-  <temple name="Bismarck, North Dakota">
-    <code>BISMA</code>
-  </temple>
-  <temple name="Bogota, Columbia">
-    <code>BOGOT</code>
-    <code>BG</code>
-  </temple>
-  <temple name="Boise, Idaho">
-    <code>BOISE</code>
-    <code>BO</code>
-  </temple>
-  <temple name="Boston, Massachusetts">
-    <code>BOSTO</code>
-  </temple>
-  <temple name="Bountiful, Utah">
-    <code>BOUNT</code>
-  </temple>
-  <temple name="Brisbane, Australia">
-    <code>BRISB</code>
-  </temple>
-  <temple name="Buenos Aires, Argentina">
-    <code>BAIRE</code>
-    <code>BA</code>
-  </temple>
-  <temple name="Calgary, Alberta">
-    <code>CALGA</code>
-  </temple>
-  <temple name="Campinas, Brazil">
-    <code>CAMPI</code>
-  </temple>
-  <temple name="Caracas, Venezuela">
-    <code>CARAC</code>
-  </temple>
-  <temple name="Cardston, Alberta">
-    <code>ALBER</code>
-    <code>AL</code>
-    <code>ALBR</code>
-  </temple>
-  <temple name="Cebu, Philippines">
-    <code>CEBU</code>
-  </temple>
-  <temple name="Chicago, Illinois">
-    <code>CHICA</code>
-    <code>CH</code>
-  </temple>
-  <temple name="Ciudad Juarez, Mexico">
-    <code>CIUJU</code>
-  </temple>
-  <temple name="Cochabamba, Boliva">
-    <code>COCHA</code>
-  </temple>
-  <temple name="Colonia Juarez, Chihuahua, Mexico">
-    <code>COLJU</code>
-  </temple>
-  <temple name="Columbia, South Carolina">
-    <code>COLSC</code>
-  </temple>
-  <temple name="Columbia River, Washington">
-    <code>CRIVE</code>
-  </temple>
-  <temple name="Columbus, Ohio">
-    <code>COLUM</code>
-  </temple>
-  <temple name="Copenhagen, Denmark">
-    <code>COPEN</code>
-  </temple>
-  <temple name="Cordoba, Argentina">
-    <code>CORDO</code>
-  </temple>
-  <temple name="Curitiba, Brazil">
-    <code>CURIT</code>
-  </temple>
-  <temple name="Dallas, Texas">
-    <code>DALLA</code>
-    <code>DA</code>
-  </temple>
-  <temple name="Denver, Colorado">
-    <code>DENVE</code>
-    <code>DV</code>
-  </temple>
-  <temple name="Detroit, Michigan">
-    <code>DETRO</code>
-  </temple>
-  <temple name="Draper, Utah">
-    <code>DRAPE</code>
-  </temple>
-  <temple name="Edmonton, Alberta">
-    <code>EDMON</code>
-  </temple>
-  <temple name="Frankfurt, Germany">
-    <code>FRANK</code>
-    <code>FR</code>
-  </temple>
-  <temple name="Freiberg, Germany">
-    <code>FREIB</code>
-    <code>FD</code>
-  </temple>
-  <temple name="Fresno, California">
-    <code>FRESN</code>
-  </temple>
-  <temple name="Fukuoka, Japan">
-    <code>FUKUO</code>
-  </temple>
-  <temple name="Gila Valley, Arizona">
-    <code>GVALL</code>
-  </temple>
-  <temple name="Gilbert, Arizona">
-    <code>GILBE</code>
-  </temple>
-  <temple name="Guadalajara, Mexico">
-    <code>GUADA</code>
-  </temple>
-  <temple name="Guatemala City, Guatemala">
-    <code>GUATE</code>
-    <code>GA</code>
-    <code>GU</code>
-  </temple>
-  <temple name="Guayaquil, Ecuador">
-    <code>GUAYA</code>
-    <code>GY</code>
-  </temple>
-  <temple name="Halifax, Nova Scotia">
-    <code>HALIF</code>
-  </temple>
-  <temple name="Hamilton, New Zealand">
-    <code>NZEAL</code>
-    <code>NZ</code>
-  </temple>
-  <temple name="Harrison, New York">
-    <code>HARRI</code>
-    <code>NYORK</code>
-  </temple>
-  <temple name="Hartford, Connecticut">
-    <code>HARTF</code>
-  </temple>
-  <temple name="Helsinki, Finland">
-    <code>HELSI</code>
-  </temple>
-  <temple name="Hermosillo, Sonora, Mexico">
-    <code>HERMO</code>
-  </temple>
-  <temple name="Hong Kong, China">
-    <code>HKONG</code>
-  </temple>
-  <temple name="Houston, Texas">
-    <code>HOUST</code>
-  </temple>
-  <temple name="Idaho Falls, Idaho">
-    <code>IFALL</code>
-    <code>IF</code>
-  </temple>
-  <temple name="Johannesburg, South Africa">
-    <code>JOHAN</code>
-    <code>JO</code>
-  </temple>
-  <temple name="Jordan River, Utah">
-    <code>JRIVE</code>
-    <code>JR</code>
-  </temple>
-  <temple name="Kansas City, Missouri">
-    <code>KANSA</code>
-  </temple>
-  <temple name="Kona, Hawaii">
-    <code>KONA</code>
-  </temple>
-  <temple name="Kiev, Ukraine">
-    <code>KIEV</code>
-  </temple>
-  <temple name="Kirtland, Ohio">
-    <code>KIRTL</code>
-  </temple>
-  <temple name="Laie, Hawaii">
-    <code>HAWAI</code>
-    <code>HA</code>
-  </temple>
-  <temple name="Las Vegas, Nevada">
-    <code>LVEGA</code>
-    <code>LV</code>
-  </temple>
-  <temple name="Lima, Peru">
-    <code>LIMA</code>
-    <code>LI</code>
-  </temple>
-  <temple name="Logan, Utah">
-    <code>LOGAN</code>
-    <code>LG</code>
-  </temple>
-  <temple name="London, England">
-    <code>LONDO</code>
-    <code>LD</code>
-  </temple>
-  <temple name="Los Angeles, California">
-    <code>LANGE</code>
-    <code>LA</code>
-  </temple>
-  <temple name="Louisville, Kentucky">
-    <code>LOUIS</code>
-  </temple>
-  <temple name="Lubbock, Texas">
-    <code>LUBBO</code>
-  </temple>
-  <temple name="Madrid, Spain">
-    <code>MADRI</code>
-  </temple>
-  <temple name="Manaus, Brazil">
-    <code>MANAU</code>
-  </temple>
-  <temple name="Manhattan, New York">
-    <code>MANHA</code>
-  </temple>
-  <temple name="Manila, Philippines">
-    <code>MANIL</code>
-    <code>MA</code>
-  </temple>
-  <temple name="Manti, Utah">
-    <code>MANTI</code>
-    <code>MT</code>
-  </temple>
-  <temple name="Medford, Oregon">
-    <code>MEDFO</code>
-  </temple>
-  <temple name="Melbourne, Australia">
-    <code>MELBO</code>
-  </temple>
-  <temple name="Memphis, Tennessee">
-    <code>MEMPH</code>
-  </temple>
-  <temple name="Merida, Mexico">
-    <code>MERID</code>
-  </temple>
-  <temple name="Mesa, Arizona">
-    <code>ARIZO</code>
-    <code>AZ</code>
-  </temple>
-  <temple name="Mexico City, Mexico">
-    <code>MEXIC</code>
-    <code>MX</code>
-  </temple>
-  <temple name="Monterrey, Mexico">
-    <code>MONTE</code>
-  </temple>
-  <temple name="Montevideo, Uruguay">
-    <code>MNTVD</code>
-  </temple>
-  <temple name="Monticello, Utah">
-    <code>MONTI</code>
-  </temple>
-  <temple name="Montreal, Quebec">
-    <code>MONTR</code>
-  </temple>
-  <temple name="Mt. Timpanogos, Utah">
-    <code>MTIMP</code>
-  </temple>
-  <temple name="Nashville, Tennessee">
-    <code>NASHV</code>
-  </temple>
-  <temple name="Nauvoo, Illinois">
-    <code>NAUVO</code>
-    <code>NV</code>
-  </temple>
-  <temple name="Nauvoo, Illinois (New)">
-    <code>NAUV2</code>
-  </temple>
-  <temple name="Newport Beach, California">
-    <code>NBEAC</code>
-  </temple>
-  <temple name="Nuku'alofa, Tonga">
-    <code>NUKUA</code>
-    <code>TG</code>
-  </temple>
-  <temple name="Oakland, California">
-    <code>OAKLA</code>
-    <code>OK</code>
-  </temple>
-  <temple name="Oaxaca, Mexico">
-    <code>OAXAC</code>
-  </temple>
-  <temple name="Ogden, Utah">
-    <code>OGDEN</code>
-    <code>OG</code>
-  </temple>
-  <temple name="Oklahoma City, Oklahoma">
-    <code>OKLAH</code>
-  </temple>
-  <temple name="Oquirrh Mountain, Utah">
-    <code>OMOUN</code>
-  </temple>
-  <temple name="Orlando, Florida">
-    <code>ORLAN</code>
-  </temple>
-  <temple name="Palmyra, New York">
-    <code>PALMY</code>
-  </temple>
-  <temple name="Panama City, Panama">
-    <code>PANAM</code>
-  </temple>
-  <temple name="Papeete, Tahiti">
-    <code>PAPEE</code>
-    <code>TA</code>
-  </temple>
-  <temple name="Perth, Australia">
-    <code>PERTH</code>
-  </temple>
-  <temple name="Philadelphia, Pennsylvania">
-    <code>PHILA</code>
-  </temple>
-  <temple name="Phoenix, Arizona">
-    <code>PHOEN</code>
-  </temple>
-  <temple name="Portland, Oregon">
-    <code>PORTL</code>
-    <code>PT</code>
-  </temple>
-  <temple name="Porto Alegre, Brazil">
-    <code>PALEG</code>
-  </temple>
-  <temple name="Preston, England">
-    <code>PREST</code>
-  </temple>
-  <temple name="Provo, Utah">
-    <code>PROVO</code>
-    <code>PV</code>
-  </temple>
-  <temple name="Quetzaltenango, Guatemala">
-    <code>QUETZ</code>
-  </temple>
-  <temple name="Raleigh, North Carolina">
-    <code>RALEI</code>
-  </temple>
-  <temple name="Recife, Brazil">
-    <code>RECIF</code>
-  </temple>
-  <temple name="Redlands, California">
-    <code>REDLA</code>
-  </temple>
-  <temple name="Regina, Saskatchewan">
-    <code>REGIN</code>
-  </temple>
-  <temple name="Reno, Nevada">
-    <code>RENO</code>
-  </temple>
-  <temple name="Rexburg, Idaho">
-    <code>REXBU</code>
-  </temple>
-  <temple name="Rome, Italy">
-    <code>ROME</code>
-  </temple>
-  <temple name="Sacramento, California">
-    <code>SACRA</code>
-  </temple>
-  <temple name="St. George, Utah">
-    <code>SGEOR</code>
-    <code>SG</code>
-  </temple>
-  <temple name="St. Louis, Missouri">
-    <code>SLOUI</code>
-  </temple>
-  <temple name="St. Paul, Minnesota">
-    <code>SPMIN</code>
-  </temple>
-  <temple name="Salt Lake City, Utah">
-    <code>SLAKE</code>
-    <code>SL</code>
-  </temple>
-  <temple name="San Antonio, Texas">
-    <code>SANTO</code>
-  </temple>
-  <temple name="San Diego, California">
-    <code>SDIEG</code>
-    <code>SA</code>
-  </temple>
-  <temple name="San Jose, Costa Rica">
-    <code>SJOSE</code>
-  </temple>
-  <temple name="San Salvador, El Salvador">
-    <code>SSALV</code>
-  </temple>
-  <temple name="Santiago, Chile">
-    <code>SANTI</code>
-    <code>SN</code>
-  </temple>
-  <temple name="Santo Domingo, Dominican Republic">
-    <code>SDOMI</code>
-  </temple>
-  <temple name="Sao Paulo, Brazil">
-    <code>SPAUL</code>
-    <code>SP</code>
-  </temple>
-  <temple name="Seattle, Washington">
-    <code>SEATT</code>
-    <code>SE</code>
-  </temple>
-  <temple name="Seoul, South Korea">
-    <code>SEOUL</code>
-    <code>SO</code>
-  </temple>
-  <temple name="Snowflake, Arizona">
-    <code>SNOWF</code>
-  </temple>
-  <temple name="Spokane, Washington">
-    <code>SPOKA</code>
-  </temple>
-  <temple name="Stockholm, Sweden">
-    <code>STOCK</code>
-    <code>ST</code>
-  </temple>
-  <temple name="Suva, Fiji">
-    <code>SUVA</code>
-  </temple>
-  <temple name="Sydney, Australia">
-    <code>SYDNE</code>
-    <code>SD</code>
-  </temple>
-  <temple name="Taipei, Taiwan">
-    <code>TAIPE</code>
-    <code>TP</code>
-  </temple>
-  <temple name="Tampico, Mexico">
-    <code>TAMPI</code>
-  </temple>
-  <temple name="Tegucigalpa, Honduras">
-    <code>TEGUC</code>
-  </temple>
-  <temple name="The Hague, Netherlands">
-    <code>HAGUE</code>
-  </temple>
-  <temple name="Tokyo, Japan">
-    <code>TOKYO</code>
-    <code>TK</code>
-  </temple>
-  <temple name="Toronto, Ontario">
-    <code>TORON</code>
-    <code>TORNO</code>
-    <code>TR</code>
-  </temple>
-  <temple name="Tuxtla Gutierrez, Mexico">
-    <code>TGUTI</code>
-  </temple>
-  <temple name="Twin Falls, Idaho">
-    <code>TFALL</code>
-    <code>TWINF</code>
-  </temple>
-  <temple name="Vancouver, British Columbia">
-    <code>VANCO</code>
-  </temple>
-  <temple name="Veracruz, Mexico">
-    <code>VERAC</code>
-  </temple>
-  <temple name="Vernal, Utah">
-    <code>VERNA</code>
-  </temple>
-  <temple name="Villahermosa, Mexico">
-    <code>VILLA</code>
-  </temple>
-  <temple name="Washington, D.C.">
-    <code>WASHI</code>
-    <code>WA</code>
-  </temple>
-  <temple name="Winter Quarters, Nebraska">
-    <code>WINTE</code>
-    <code>WQUAR</code>
-  </temple>
-  <temple name="Endowment House">
-    <code>EHOUS</code>
-    <code>EH</code>
-  </temple>
-  <temple name="President's Office">
-    <code>POFFI</code>
-    <code>PO</code>
-  </temple>
-  <temple name="Historian's Office">
-    <code>HOFFI</code>
-    <code>HO</code>
-  </temple>
-  <temple name="Other">
-    <code>OTHER</code>
-  </temple>
-</temples>

data/man/Makefile.am

@@ -0,0 +1,14 @@
+# This is the data/man level Makefile for Gramps
+# $Id$
+
+SUBDIRS = fr
+
+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

@@ -1,243 +0,0 @@
-# -*- 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'2012, 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.0'
-# The full version, including alpha/beta/rc tags.
-release = '4.0.0-alpha2'
-
-# 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/conf.py

@@ -1,243 +0,0 @@
-# -*- 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'2012, 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.0'
-# The full version, including alpha/beta/rc tags.
-release = '4.0.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

@@ -1,282 +0,0 @@
-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/cs/gramps.1.in

@@ -1,323 +0,0 @@
-.TH gramps 1 "@VERSION@" "Leden 2011" "@VERSION@"
-.SH JMÉNO 
-gramps \- programový systém pro správu genealogického výzkumu a analýzy.
-
-.SH POUŽITÍ
-.B gramps
-.RB [ \-?|\-\^\-help ]
-.RB [ \-\^\-usage ]
-.RB [ \-\^\-version ]
-.RB [ \-l ]
-.RB [ \-u|\-\^\-force-unlock ]
-.RB [ \-O|\-\^\-open=
-.IR DATABÁZE 
-.RB [ \-f|\-\^\-format= 
-.IR FORMÁT ]] 
-.RB [ \-i|\-\^\-import=
-.IR SOUBOR 
-.RB [ \-f|\-\^\-format= 
-.IR FORMÁT ]] 
-.RB [ \-i|\-\^\-import= 
-.IR ... ] 
-.RB [ \-e|\-\^\-export= 
-.IR SOUBOR
-.RB [ \-f|\-\^\-format= 
-.IR FORMÁT ]] 
-.RB [ \-a|\-\^\-action= 
-.IR AKCE ]
-.RB [ \-p|\-\^\-options= 
-.IR PARAMETRY ]]
-.RB [
-.IR SOUBOR
-.RB ]
-.if 0 .RB [ bonobo\ options ]
-.if 0 .RB [ sound\ options ]
-.RB [ \-\-version ]
-
-.SH POPIS
-.PP 
-\fIGramps\fP 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 \fIFamily Tree Maker (TM)\fR,  \fIPersonal Ancestral
-Files (TM)\fR, 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.
-
-.SH MOŽNOSTI
-.TP 
-.BI gramps " SOUBOR" 
-Pokud je zadán \fISOUBOR\fR (bez dalších parametrů) jako název rodokmenu
-nebo jako adresář databáze rodokmenu, je gramps otevřeno v interaktivním 
-módu. Pokud je \fISOUBOR\fR 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.
-.br
-
-.TP 
-.BI \-f,\-\^\-format= " FORMÁT"
-Explicitně definuje formát \fISOUBOR\fRu předchozího parametru
-.ig
-\fB\-O\fR,
-..
-\fB\-i\fR, nebo 
-\fB\-e\fR. Pokud není parametr \fB\-f\fR pro \fISOUBOR\fR specifikován, 
-bude automaticky použit formát odpovídající koncovce souboru nebo MIME-typu. 
-.br
-
-Formáty
-dostupné pro export jsou  \fBgramps\-xml\fR (automaticky použit pokud má
-\fISOUBOR\fR koncovku \fB.gramps\fR), \fBgedcom\fR (automaticky použit 
-pokud má \fISOUBOR\fR koncovku \fB.ged\fR), případně jiný další formát dostupný
-prostřednictvím zásuvných modulů Gramps.
-.br
-
-Formáty
-dostupné pro import jsou \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR,  
-\fBgramps\-pkg\fR (automaticky použit pokud má \fISOUBOR\fR koncovku \fB.gpkg\fR),
-nebo \fBgeneweb\fR (automaticky použit pokud má \fISOUBOR\fR koncovku \fB.gw\fR). 
-.br
-
-Formáty dostupné pro export jsou
-.ig
-\fBgrdb\fR,
-..
-\fBgramps\-xml\fR, \fBgedcom\fR,
-\fBgramps\-pkg\fR, \fBwft\fR (automaticky použit pokud má \fISOUBOR\fR koncovku \fB.wft\fR),
-\fBgeneweb\fR, a \fBiso\fR (nikdy není použit automaticky, vždy musí být specifikován 
-parametrem \fB\-f\fR).
-
-.TP 
-.BI \-l
-Vypíše seznam známých rodokmenů.
-
-.TP
-.BI \-u,\-\^\-force-unlock
-Odemkne zamčenou databázi.
-
-.TP 
-.BI \-O,\-\^\-open= " DATABÁZE"
-Otevření \fIDATABÁZE\fR. 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.
-
-.TP 
-.BI \-i,\-\^\-import= " SOUBOR"
-Importuje data ze \fISOUBOR\fRu. Pokud není specifikována databáze, je použita dočasná. Ta je po ukončení gramps smazána.
-.br
-
-Pokud je předáván více než jeden vstup, musí každému souboru předcházet parametr \fB\-i\fR. 
-Soubory jsou zpracovávány v pořadí, v jakém byly zadány na příkazové řádce.
-Např. \fB\-i\fR \fISOUBOR1\fR \fB\-i\fR \fISOUBOR2\fR
-a \fB\-i\fR \fISOUBOR2\fR \fB\-i\fR \fISOUBOR1\fR mohou vytvořit ve výsledné databázi
-různá gramps ID.
-
-.TP 
-.BI \-a,\-\^\-action= " AKCE"
-Provedení \fIAKCE\fR 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: 
-\fBsummary\fR (stejné jako Zprávy->Pohled->Souhrn), 
-\fBcheck\fR (stejné jako Nástroje->Database Processing->Kontrola a oprava), 
-\fBreport\fR (vytvoří zprávu), a
-\fBtool\fR (spustí nástroj zásuvného modulu).
-Akce \fBreport\fR a \fBtool\fR potřebují v \fIPARAMETRY\fR zadat parametr
-\fB\-p\fR . 
-.br
-
-\fIPARAMETRY\fR by měly splňovat následující kritéria:
-.br
-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=hodnota.
-Jednotlivé páry musí být odděleny čárkami.  
-.br
-
-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é.
-
-.BI "name=name"
-.br
-Povinná předvolba určující který nástroj nebo zpráva bude spuštěna.
-Pokud zadané \fIname\fR neodpovídá žádné dostupné funkčnosti, vypíše se chybové hlášení 
-následované seznamem dostupných nástrojů a zpráv (záleží na \fIAKCE\fR).
-
-.BI "show=all"
-.br
-Vytvoří seznam názvů všech předvoleb dostupných pro danou zprávu nebo nástroj.
-
-.BI "show="optionname
-.br
-Vypíše popis všech funkcionalit poskytnutých \fIoptionname\fR, 
-ale také všechny přijatelné typy a hodnoty pro tuto volbu.
-
-.br
-Použijte výše popsané volby pro zjištění všech možností
-dané zprávy.
-
-.LP
-Pokud je zadána jedna nebo více výstupních akcí, každá musí být uvozena
-předvolbou \fB\-a\fR. Akce jsou prováděny jedna za druhou v zadaném pořadí.
-
-.TP 
-.BI \-d,\-\^\-debug= " LOGGER_NAME"
-Zapne ladicí výstup pro vývoj a testování. Detaily najdete ve zdrojovém kódu.
-.TP
-.BI \-\^\-version
-Vytiskne číslo verze gramps a skončí
-\" change 0 to 1 to enable output of OAF options
-.if 0 \{
-.PP
-Následující možnosti slouží pro aktivaci Bonobo.
-.TP 
-.BI \-\^\-oaf-ior-fd= "FD"
-Popisovač souboru pro zápis OAF IOR
-.TP 
-.BI \-\^\-oaf-activate-iid= " IID"
-OAF IID k aktivaci
-.TP 
-.BI \-\^\-oaf-private
-Znemožní registraci serveru s OAF
-\}
-\" change 0 to 1 to enable output of Gnome sound options
-.if 0 \{
-.PP
-Následující možnosti slouží pro řízení zvuku prostřednictívm knihovny Gnome.
-.TP
-.BI \-\^\-disable-sound
-Zablokuje využití zvukového serveru
-.TP
-.BI \-\^\-enable-sound
-Umožní využití zvukového serveru
-.TP
-.BI \-\^\-espeaker= " HOSTNAME:PORT"
-Host:port na které běží zvukový server který bude použit
-\}
-
-.SH "Chování"
-.br
-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.
-
-.LP
-Pokud je zadán parametr \fB\-O\fR, pak se gramps snaží otevřít zadanou
-databázi a pracovat s jejími daty podle instrukcí dalších parametrů 
-příkazové řádky.
-
-.LP
-S nebo bez použití parametru \fB\-O\fR může být provedeno více importů,
-exportů, případně akcí daných argumenty příkazové řádky (\fB\-i\fR,
-\fB\-e\fR a \fB\-a\fR).  
-
-.LP
-Na pořadí parametrů \fB\-i\fR, \fB\-e\fR, nebo \fB\-a\fR nezáleží. 
-Aktuální pořadí zpracová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í!
-
-.LP
-Pokud nejsou zadány \fB\-O\fR nebo \fB\-i\fR, gramps otevře své hlavní okno
-a spustí se v obvyklém interaktivním módu s prázdnou databází.
-
-.LP
-Pokud nejsou zadány \fB\-e\fR nebo \fB\-a\fR, 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 \fBimport_db.grdb\fR v adresáři
-\fB~/.gramps/import\fR.
-
-.LP
-Chyba vzniklá při importu, exportu nebo akci bude vypsána na \fIstdout\fR
-(pokud se jedná o vyjímku ošetřenou gramps) nebo na \fIstderr\fR 
-(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ů \fIstdout\fR a \fIstderr\fR příkazové řádky. 
-
-.SH PŘÍKLADY
-.TP 
-Otevření existujícího rodokmenu a import xml souboru do něho může být proveden takto: 
-\fBgramps\fR \fB\-O\fR \fI'Můj rodokmen'\fR \fB\-i\fR \fI~/db3.gramps\fR
-.TP 
-To samé, jen s importem do dočasné databáze a otevřením interaktivní relace: 
-\fBgramps\fR \fB\-i\fR \fI'My Family Tree'\fR \fB\-i\fR \fI~/db3.gramps\fR
-.TP 
-Import čtyř databází (jejichž formáty jsou stanoveny podle názvů souborů) a následná kontrola bezchybnosti výsledné databáze může být provedena takto: 
-\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 
-Explicitní specifikace formátu databází předchozího příkladu přidáním příslušného parametru \fB\-f\fR za název souboru: 
-\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 
-Zapsání výsledné databáze vytvořené ze všech importů zajistí parametr \fB\-e\fR (použijte \fB\-f\fR pokud nelze uhodnout formát z názvu souboru):
-\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-e\fR \fI~/nový-balíček\fR \fB\-f\fR \fIgramps-pkg\fR 
-.TP 
-Import tří databází a start interaktivní gramps relace nad výsledkem: 
-\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR 
-.TP 
-Spuštění nástroje kontroly z příkazové řádky s výstupem na stdout: 
-\fBgramps\fR \fB\-O\fR \fI'Můj rodokmen'\fR \fB-a\fR \fItool\fR \fB-p\fR \fBname\fR=\fIverify\fR
-.TP 
-A konečně spuštění normální interaktivní relace aplikace: 
-\fBgramps\fR 
-
-.SH PROMĚNNÉ PROSTŘEDÍ
-Program kontroluje, zda jsou nastaveny následující proměnné:
-
-\fBLANG\fR - popisuje, který jazyk bude použit:
-Příklad: pro češtinu musí mít proměnná hodnotu cs_CZ.utf8.
-
-\fBGRAMPSHOME\fR - 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).
-
-.SH KONCEPTY
-\fBgramps\fR 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. 
-.LP 
-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ř. \fIOpenOffice.org\fR, \fIAbiWord\fR, HTML, 
-nebo LaTeX. Tím dává možnost přizpůsobit formát požadavku uživatelů. 
-
-.SH ZNÁMÉ CHYBY A OMEZENÍ
-.br
-nejsou
-
-.SH SOUBORY
-.LP 
-\fI${PREFIX}/bin/gramps\fP 
-.br 
-\fI${PREFIX}/share/gramps\fP
-.br 
-\fI${HOME}/.gramps\fP 
-
-.SH AUTOŘI
-Donald Allingham \fI<don@gramps-project.org>\fR
-.br 
-\fIhttp://gramps.sourceforge.net\fR
-.LP 
-Originální manuálovou stránku vytvořil:
-.br 
-Brandon L. Griffith \fI<brandon@debian.org>\fR
-.br
-pro zařazení do systému Debian GNU/Linux.
-.LP 
-Tuto manuálovou stránku přeložil a v současné době spravuje:
-.br 
-Zdeněk Hataš \fI<zdenek.hatas@gmail.com>\fR
-.br 
-
-.SH 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 \fBgramps-manual.xml\fR 
-v adresáři \fIdoc/gramps-manual/$LANG\fR v oficiální distribuci 
-zdrojového kódu.
-.LP 
-Dokumentace pro vývojáře je k dispozici na webu
-\fIhttp://developers.gramps-project.org\fR. 

data/man/en.rst

@@ -1,299 +0,0 @@
-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*]] [**-i** | **--import=** *...*]
-       [**-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
-          a  temporary database is used; this is deleted when you exit
-          gramps.
-
-          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=** *FICHIER*
-          Export data into *FILE* . For **gramps-xml** , **gedcom** 
-          , **wft** , **gramps-pkg** , et **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/python/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

@@ -0,0 +1,14 @@
+# 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

@@ -1,243 +0,0 @@
-# -*- 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'2012, 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.0'
-# The full version, including alpha/beta/rc tags.
-release = '4.0.0-alpha2'
-
-# 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

@@ -1,300 +0,0 @@
-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=** *FILE*
-       [**-f** | **--format=** *FORMAT*]] [**-i** | **--import=** *...*]
-       [**-e** | **--export=** *FICHIER* [**-f** | **--format=** *FORMAT*]]
-       [**-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 temporaire
-          est utilisée; elle sera effacée quand vous quitterez gramps.
-
-          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 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 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/python/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,342 +1,214 @@
-.TH "GRAMPS" "1" "28 December 2012" "4.0" "Gramps"
-.SH NAME
-gramps \- Gramps Documentation
-.
-.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]
-..
-.de1 INDENT
-.\" .rstReportMargin pre:
-. RS \\$1
-. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
-. nr rst2man-indent-level +1
-.\" .rstReportMargin post:
-..
-.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
-..
-.\" Man page generated from reStructuredText.
-.
-.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 \fIFILE\fP
-[\fB\-f\fP | \fB\-\-format=\fP \fIFORMAT\fP]] [\fB\-i\fP | \fB\-\-import=\fP \fI...\fP]
-[\fB\-e\fP | \fB\-\-export=\fP \fIFICHIER\fP [\fB\-f\fP | \fB\-\-format=\fP \fIFORMAT\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
-.B \fB\-u\fP , \fB\-\-force\-unlock\fP
-Débloquer une base de données verrouillée.
-.TP
-.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 temporaire
-est utilisée; elle sera effacée quand vous quitterez gramps.
-.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.
-.UNINDENT
-.TP
-.B \fBOpération\fP
-Si le premier 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
-.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
-.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
-.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/python/dist\-packages/gramps/\fP
-.sp
-\fI${PREFIX}/share/\fP
-.sp
-\fI${HOME}/.gramps\fP
-.UNINDENT
-.UNINDENT
-.INDENT 0.0
-.TP
-.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>
+.TH gramps 1 "@VERSION@" "Janvier 2006" "@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 [ \-O|\-\^\-open=
+.IR FICHIER 
+.RB [ \-f|\-\^\-format= 
+.IR FORMAT ]] 
+.RB [ \-i|\-\^\-import=
+.IR FICHIER 
+.RB [ \-f|\-\^\-format= 
+.IR FORMAT ]] 
+.RB [ \-i|\-\^\-import= 
+.IR ... ] 
+.RB [ \-o|\-\^\-output= 
+.IR FICHIER
+.RB [ \-f|\-\^\-format= 
+.IR FORMAT ]] 
+.RB [ \-a|\-\^\-action= 
+.IR ACTION ]
+.RB [ \-p|\-\^\-options= 
+.IR OPTIONSTRING ]] 
+.RB [
+.IR FICHIER
+.RB ]
+
+.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) alors une session interactive est ouverte. 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 options \fB\-O\fR,
+\fB\-i\fR, ou
+\fB\-o\fR. Si l'option \fB\-f\fR n'est pas donnée pour le \fIFICHIER\fR, alors le format sera celui de l'extension.
+.br
+
+Les formats disponibles pour l'ouverture sont \fBgrdb\fR (choisi si \fIFICHIER\fR se termine par
+\fB.grdb\fR), \fBgramps\-xml\fR (choisi si \fIFICHIER\fR se termine par
+\fB.gramps\fR), et \fBgedcom\fR (choisi si \fIFICHIER\fR se termine par \fB.ged\fR).
+.br
+
+Les formats disponibles pour l'importation sont \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR,  
+\fBgramps\-pkg\fR (choisi si \fIFICHIER\fR se termine par \fB.gpkg\fR), et
+\fBgeneweb\fR (choisi si \fIFICHIER\fR se termine par \fB.gw\fR). 
+.br
+
+Les formats disponibles pour l'exportation sont  \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR,
+\fBgramps\-pkg\fR, \fBwft\fR (choisi 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 \-O,\-\^\-open= " FICHIER"
+Ouvrir un \fIFICHIER\fR. 
+Seulement les formats \fBgrdb\fR, \fBgramps\-xml\fR, et \fBgedcom\fR peuvent être ouvert directement. Pour les autres formats, vous devez utiliser l'option d'import,
+laquelle ouvrira une base vide et importera les données.
+.br
+
+Seulement un fichier peut être ouvert. 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.
+.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 \-o,\-\^\-output= " 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 \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\-o\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->Affichage->Résumé?), \fBcheck\fR (comme l'outil->Réparation de la base->Vérifier et réparer), et \fBreport\fR (produit un rapport, à besoin
+de \fIOPTIONSTRING\fR précédé par la commande \fB\-p\fR.
+.br
+
+Ces options de rapport doivent 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=reportname "
+.br
+Cette option obligatoire, elle détermine quel rapport sera généré. Si le nom du rapport saisi ne correspond à aucun rapport 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 optionname, 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é.
+
+.BI "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 le fichier 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\-o\fR, et \fB\-a\fR.
+
+.LP
+L'ordre des options \fB\-i\fR, \fB\-o\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\-o\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
+.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\-o\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\-o\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 
+Enfin, pour lancer une session interactive normale, entrer : \fBgramps\fR 
+
+.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
 pour Debian GNU/Linux système.
-.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)
-.SH AUTHOR
-Jerome Rapinat
-.SH COPYRIGHT
-2012, Gramps project
-.\" Generated by docutils manpage writer.
-.
+.LP 
+Cette page man est maintenue par:
+.br 
+Alex Roitman \fI<shura@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.

data/man/gramps.1.in

@@ -1,4 +1,4 @@
-.TH gramps 1 "@VERSION@" "December 2012" "@VERSION@"
+.TH gramps 1 "@VERSION@" "August 2005" "@VERSION@"
 .SH NAME
 gramps \- Genealogical Research and Analysis Management Programming System.
 
@@ -7,10 +7,8 @@ gramps \- Genealogical Research and Analysis Management Programming System.
 .RB [ \-?|\-\^\-help ]
 .RB [ \-\^\-usage ]
 .RB [ \-\^\-version ]
-.RB [ \-l ]
-.RB [ \-u|\-\^\-force-unlock ]
 .RB [ \-O|\-\^\-open=
-.IR DATABASE 
+.IR FILE 
 .RB [ \-f|\-\^\-format= 
 .IR FORMAT ]] 
 .RB [ \-i|\-\^\-import=
@@ -19,20 +17,17 @@ gramps \- Genealogical Research and Analysis Management Programming System.
 .IR FORMAT ]] 
 .RB [ \-i|\-\^\-import= 
 .IR ... ] 
-.RB [ \-e|\-\^\-export= 
+.RB [ \-o|\-\^\-output= 
 .IR FILE
 .RB [ \-f|\-\^\-format= 
 .IR FORMAT ]] 
 .RB [ \-a|\-\^\-action= 
 .IR ACTION ]
 .RB [ \-p|\-\^\-options= 
-.IR OPTIONSTRING ]]
+.IR OPTIONSTRING ]] 
 .RB [
 .IR FILE
 .RB ]
-.if 0 .RB [ bonobo\ options ]
-.if 0 .RB [ sound\ options ]
-.RB [ \-\-version ]
 
 .SH DESCRIPTION
 .PP 
@@ -47,31 +42,25 @@ 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
+When \fIFILE\fR is given (without any flags) then it is
+opened and an interactive session is started. 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,
-..
+Explicitly specify format of \fIFILE\fR given by preceding \fB\-O\fR,
 \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. 
+\fB\-o\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. 
 .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.
+available for opening are \fBgrdb\fR (guessed if \fIFILE\fR ends with
+\fB.grdb\fR), \fBgramps\-xml\fR (guessed if \fIFILE\fR ends with
+\fB.gramps\fR), and \fBgedcom\fR (guessed if \fIFILE\fR ends with \fB.ged\fR).
 .br
 
 Formats 
@@ -80,31 +69,25 @@ available for import are \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR,
 \fBgeneweb\fR (guessed if \fIFILE\fR ends with \fB.gw\fR). 
 .br
 
-Formats available for export are
-.ig
-\fBgrdb\fR,
-..
-\fBgramps\-xml\fR, \fBgedcom\fR,
+Formats available for export are  \fBgrdb\fR, \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
-Print a list of known family trees.
+.BI \-O,\-\^\-open= " FILE"
+Open \fIFILE\fR. 
+Only \fBgrdb\fR, \fBgramps\-xml\fR, and \fBgedcom\fR formats can be
+opened directly. For other formats, you will need to use the import option
+which will set up the empty database and then import data into it.
+.br
 
-.TP
-.BI \-u,\-\^\-force-unlock
-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.
+Only a single file can be opened. If you need to combine data from several
+sources, you will need to use the import option. 
 
 .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.
+Import data from \fIFILE\fR.
 .br
 
 When more than one input file is given, each has to be preceded by \fB\-i\fR 
@@ -114,55 +97,54 @@ and \fB\-i\fR \fIFILE2\fR \fB\-i\fR \fIFILE1\fR might produce different
 gramps IDs in the resulting database. 
 
 .TP 
-.BI \-e,\-\^\-export= " FILE"
-Export data into \fIFILE\fR. For \fBgramps\-xml\fR, \fBgedcom\fR, 
-\fBwft\fR, \fBgramps\-pkg\fR, and \fBgeneweb\fR, the \fIFILE\fR is 
-the name of the resulting file. 
+.BI \-o,\-\^\-output= " FILE"
+Export data into \fIFILE\fR. For \fBiso\fR format, the \fIFILE\fR is actually
+the name of directory the gramps database will be written into. 
+For \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR, \fBwft\fR, \fBgramps\-pkg\fR, 
+and \fBgeneweb\fR, the \fIFILE\fR is the name of the resulting file. 
 .br
 
 When more than one output file is given, each has to be preceded 
-by \fB\-e\fR flag. The files are written one by one, in the specified order.
+by \fB\-o\fR flag. The files are written one by one, in the specified order.
 
 .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). 
+are successfully completed. Currently available actions are \fBsummary\fR 
+(same as Reports->View->Summary), \fBcheck\fR (same as Tools->Database 
+Processing->Check and Repair), and \fBreport\fR (generates report, needs
+the \fIOPTIONSTRING\fR supplied by the \fB\-p\fR flag). 
 .br
 
-The \fIOPTIONSTRING\fR should satisfy the following conditions:
+The report option string 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.  
+be enclosed with quotation marks.
+Option string must list pairs of option names and values.
+Withing a pair, option name and value must be separated by the equality sign.
+Different 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.
+Most of the report options are specific for every report. However, there some
+common options.
 
-.BI "name=name"
+.BI "name=reportname"
 .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).
+This mandatory option determines which report
+will be generated. If the supplied report_name does not correspond to any
+available report, the error message will be printed followed by the list of
+available reports.
 
 .BI "show=all"
 .br
-This will produce the list of names for all options available for a given 
-report or tool.
+This will produce the list of names for all options
+available for a given report.
 
-.BI "show="optionname
+.BI "show=optionname"
 .br
 This will print the description of
-the functionality supplied by \fIoptionname\fR, as well as what are the
+the functionality supplied by \fBoptionname\fR, as well as what are the
 acceptable types and values for this option.
 
 .br
@@ -173,42 +155,7 @@ everything about a given report.
 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
-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.
-.TP
-.BI \-\^\-disable-sound
-Disable sound server usage
-.TP
-.BI \-\^\-enable-sound
-Enable sound server usage
-.TP
-.BI \-\^\-espeaker= " HOSTNAME:PORT"
-Host:port on which the sound server to use is running
-\}
-
-.SH "Operation"
+.BI "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
@@ -217,16 +164,16 @@ 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
+the supplied file name 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.  
+\fB\-o\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
+The order of \fB\-i\fR, \fB\-o\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!
 
@@ -236,55 +183,34 @@ 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 
+If no \fB\-o\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 
+dumped to \fIstdout\fR (if these are exceptions handled by gramps) or 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 
+To record the database resulting from all imports, supply \fB\-o\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\-o\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
-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 
@@ -298,11 +224,9 @@ or LaTeX to allow the users to modify the format to suit their needs.
 
 .SH FILES
 .LP 
-\fI${PREFIX}/bin/gramps\fP
+\fI${PREFIX}/bin/gramps\fP 
 .br 
-\fI${PREFIX}/lib/python/dist\-packages/gramps/\fP 
-.br 
-\fI${PREFIX}/share/\fP
+\fI${PREFIX}/share/gramps\fP
 .br 
 \fI${HOME}/.gramps\fP 
 
@@ -319,7 +243,7 @@ for inclusion in the Debian GNU/Linux system.
 .LP 
 This man page is currently maintained by:
 .br 
-Gramps project \fI<xxx@gramps-project.org>\fR
+Alex Roitman \fI<shura@gramps-project.org>\fR
 .br 
 
 .SH DOCUMENTATION

data/man/index.rst

@@ -1,22 +0,0 @@
-.. 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/conf.py

@@ -1,243 +0,0 @@
-# -*- 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 = 'nl'
-
-# General information about the project.
-project = u'Gramps'
-copyright = u'2012, 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.0'
-# The full version, including alpha/beta/rc tags.
-release = '4.0.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 = [
-    ('nl', '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/nl/gramps.1.in

@@ -1,315 +0,0 @@
-.TH gramps 1 "@VERSION@" "August 2005" "@VERSION@"
-.SH NAAM
-gramps \- Genealogisch Onderzoek en Analyse Beheersysteem.
-
-.SH SAMENVATTING
-.B gramps
-.RB [ \-?|\-\^\-help ]
-.RB [ \-\^\-usage ]
-.RB [ \-\^\-version ]
-.RB [ \-O|\-\^\-open=
-.IR GEGEVENSBESTAND 
-.RB [ \-f|\-\^\-format= 
-.IR FORMAAT ]] 
-.RB [ \-i|\-\^\-import=
-.IR BESTAND 
-.RB [ \-f|\-\^\-format= 
-.IR FORMAAT ]] 
-.RB [ \-i|\-\^\-import= 
-.IR ... ] 
-.RB [ \-e|\-\^\-export= 
-.IR BESTAND
-.RB [ \-f|\-\^\-format= 
-.IR FORMAAT ]] 
-.RB [ \-a|\-\^\-action= 
-.IR ACTIE ]
-.RB [ \-p|\-\^\-options= 
-.IR OPTIESTRING ]] 
-.RB [
-.IR BESTAND
-.RB ]
-.if 0 .RB [ bonobo\ options ]
-.if 0 .RB [ sound\ options ]
-.RB [ \-\-version ]
-
-.SH BESCHRIJVING
-.PP 
-\fIGramps\fP is een Free/OpenSource genealogisch programma dat in Python, 
-geschreven is en gebruik maakt van de GTK+/GNOME interface.
-Gramps zal voor iedereen die al gewerkt heeft met andere genealogische
-programma's zoals \fIFamily Tree Maker (TM)\fR,  \fIPersonal Ancestral
-Files (TM)\fR of \fIGNU Geneweb\fP.
-Importeren vanuit het gekende GEDCOM-formaat wordt ondersteund. Dit formaat 
-wordt wereldwijd gebruikt door bijna alle genealogische software.
-
-.SH OPTIES
-.TP 
-.BI gramps "BESTAND" 
-Wanneer \fIBESTAND\fR opgegeven wordt (zonder vlaggen) als een familiestamboom
-of als een familistamboommap, dan wordt dit bestand geopend en een interactieve 
-sessie wordt gestart. Indien BESTAND een bestandsformaat dat door Gramps
-herkent wordt, zal een lege familiestamboom aangemaakt worden. De bestandsnaam
-wordt gebaseerd op de \fIBESTAND\fP naam en de gegevens worden in dit bestand
-geïmporteerd. Met resterende opties wordt geen rekening gehouden. Deze wijze
-van opstarten is zeer bruikbaar om Gramps te gebruiken voor genealogische
-gegevens via een webbrowser. Deze opstartmethode kan gelijk welk gegevensformaat
-eigen aan Gramps behandelen, zie onder.
-.br
-
-.TP 
-.BI \-f,\-\^\-format= " FORMAAT"
-Expliciet een formaat opgeven voor \fIBESTAND\fR door de optie
-.ig
-\fB\-O\fR,
-..
-\fB\-i\fR, of 
-\fB\-e\fR mee te geven. Indien de \fB\-f\fR optie niet opgegeven wordt voor
-\fIBESTAND\fR, wordt het formaat gebaseerd op de bestandsextensie of het 
-MIME-type. 
-.br
-
-Formaten 
-beschikbaar voor uitvoer zijn \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,
-..
-\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 \-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 \-e,\-\^\-export= " FILE"
-Export data into \fIFILE\fR. For \fBiso\fR format, the \fIFILE\fR is actually
-the name of directory the gramps database will be written into. 
-For
-.ig
-\fBgrdb\fR,
-..
-\fBgramps\-xml\fR, \fBgedcom\fR, \fBwft\fR, \fBgramps\-pkg\fR, 
-and \fBgeneweb\fR, the \fIFILE\fR is the name of the resulting file. 
-.br
-
-When more than one output file is given, each has to be preceded 
-by \fB\-e\fR flag. The files are written one by one, in the specified order.
-
-.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), and \fBreport\fR (generates report, needs
-the \fIOPTIONSTRING\fR supplied by the \fB\-p\fR flag). 
-.br
-
-The report option string 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.
-Option string must list pairs of option names and values.
-Withing a pair, option name and value must be separated by the equality sign.
-Different pairs must be separated by commas.  
-.br
-
-Most of the report options are specific for every report. However, there some
-common options.
-
-.BI "name=reportname"
-.br
-This mandatory option determines which report
-will be generated. If the supplied report_name does not correspond to any
-available report, the error message will be printed followed by the list of
-available reports.
-
-.BI "show=all"
-.br
-This will produce the list of names for all options
-available for a given report.
-
-.BI "show=optionname"
-.br
-This will print the description of
-the functionality supplied by \fBoptionname\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
-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.
-.TP
-.BI \-\^\-disable-sound
-Disable sound server usage
-.TP
-.BI \-\^\-enable-sound
-Enable sound server usage
-.TP
-.BI \-\^\-espeaker= " HOSTNAME:PORT"
-Host:port on which the sound server to use is running
-\}
-
-.SH "werking"
-.br
-Indien het eerste argument in de opdrachtregel niet start met dash (dus geen
-vlag) dan zal Gramps trachten om het bestand te openen met een naam die in het
-eerste argument werd opgegeven. Vervolgens wordt een interactieve sessie
-gestart en de overige argumenten van de opdrachtregel worden genegeerd.
-
-.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\-o\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 
-Finally, to start normal interactive session type: 
-\fBgramps\fR 
-
-.SH CONCEPTEN
-Ondersteuning van een op python-gebaseerd plugin systeem. Dit laat toe om 
-verslagen, hulpgereedschappen en vensterfilters toe te voegen zonder dat het 
-hoofdprogramma dient aangepast.
-.LP 
-De klassieke uitdrukken zijn mogelijk, maar daar bovenover kunnen de meeste
-verslagen ook gebruik maken van \fIOpenOffice.org\fR, \fIAbiWord\fR, HTML, 
-of LaTeX. Zo kunnen gebruikers het formaat wijzigen naar eigen wens. 
-
-.SH GEKENDE BUGS EN BEPERKINGEN
-
-.SH BESTANDEN
-.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 
-Deze man pagina werd oorspronkelijk geschreven door:
-.br 
-Brandon L. Griffith \fI<brandon@debian.org>\fR
-.br
-voor het Debian GNU/Linux systeem.
-.LP 
-Deze man pagina wordt momenteel onderhouden door:
-.br 
-Alex Roitman \fI<shura@gramps-project.org>\fR
-.br 
-.LP
-Deze nederlandstalige man pagina wordt momenteel onderhouden door:
-.br
-Erik De Richter \fI<frederik.de.richter@pandora.be>\fR
-.br
-
-.SH DOCUMENTATIE
-De gebruikersdocumentatie is beschikbaar via de normale GNOME Help browser 
-in de vorm van een Gramps-handleiding. De handleiding is ook beschikbaar in 
-XML-formaat: \fBgramps-manual.xml\fR onder \fIdoc/gramps-manual/$LANG\fR in
-de officiële brondistributie.
-.LP 
-De ontwikkelingsdocumentatie kan gevonden worden op de
-\fIhttp://developers.gramps-project.org\fR webstek. 

data/man/nl/nl.rst

@@ -1,266 +0,0 @@
-Dutch
-======
-
-gramps(1)			     3.4.0			     gramps(1)
-
-
-
-**NAAM**
-       gramps - Genealogisch Onderzoek en Analyse Beheersysteem.
-
-
-**SAMENVATTING**
-       gramps  [-?|--help]  [--usage]  [--version] [-O|--open= GEGEVENSBESTAND
-       [-f|--format= FORMAAT]] [-i|--import= BESTAND  [-f|--format=  FORMAAT]]
-       [-i|--import=   ...]   [-e|--export=  BESTAND  [-f|--format=  FORMAAT]]
-       [-a|--action= ACTIE] [-p|--options= OPTIESTRING]] [ BESTAND  ]  [--ver‐
-       sion]
-
-
-**BESCHRIJVING**
-       Gramps  is  een	Free/OpenSource  genealogisch programma dat in Python,
-       geschreven is en gebruik maakt van de GTK+/GNOME interface.  Gramps zal
-       voor iedereen die al gewerkt heeft met andere genealogische programma's
-       zoals Family Tree Maker (TM),  Personal Ancestral  Files  (TM)  of  GNU
-       Geneweb.   Importeren vanuit het gekende GEDCOM-formaat wordt onderste‐
-       und. Dit formaat wordt wereldwijd gebruikt door bijna alle  genealogis‐
-       che software.
-
-
-**OPTIES**
-       **gramps** *BESTAND*
-	      Wanneer *BESTAND* opgegeven wordt (zonder vlaggen) als een famili‐
-	      estamboom of als een familistamboommap, dan  wordt  dit  bestand
-	      geopend en een interactieve sessie wordt gestart. Indien BESTAND
-	      een bestandsformaat dat door Gramps herkent wordt, zal een  lege
-	      familiestamboom	aangemaakt   worden.   De  bestandsnaam  wordt
-	      gebaseerd op de *BESTAND*  naam  en  de  gegevens  worden  in  dit
-	      bestand  geïmporteerd. Met resterende opties wordt geen rekening
-	      gehouden. Deze wijze van opstarten is zeer bruikbaar  om	Gramps
-	      te  gebruiken  voor  genealogische  gegevens via een webbrowser.
-	      Deze opstartmethode kan gelijk welk  gegevensformaat  eigen  aan
-	      Gramps behandelen, zie onder.
-
-
-       **-f** , **--format=** *FORMAAT*
-	      Expliciet  een formaat opgeven voor BESTAND door de optie -i, of
-	      -e mee te geven. Indien de -f optie niet	opgegeven  wordt  voor
-	      BESTAND,	wordt  het formaat gebaseerd op de bestandsextensie of
-	      het MIME-type.
-
-	      Formaten beschikbaar voor uitvoer zijn  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  grdb,  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,  and  iso	(never
-	      guessed, always specify with -f option).
-
-
-       **-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
-          a  temporary database is used; this is deleted when you exit
-          gramps.
-
-          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.
-
-
-       **-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
-
-
-
-
-**werking**
-       Indien het eerste argument in de opdrachtregel niet start met dash (dus
-       geen vlag) dan zal Gramps trachten om het bestand  te  openen  met  een
-       naam  die  in  het eerste argument werd opgegeven. Vervolgens wordt een
-       interactieve  sessie  gestart  en  de   overige	 argumenten   van   de
-       opdrachtregel worden genegeerd.
-
-       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**
-
-
-**CONCEPTEN**
-       Ondersteuning van een op python-gebaseerd plugin systeem. Dit laat  toe
-       om verslagen, hulpgereedschappen en vensterfilters toe te voegen zonder
-       dat het hoofdprogramma dient aangepast.
-
-       De klassieke uitdrukken zijn mogelijk, maar daar  bovenover  kunnen  de
-       meeste  verslagen  ook gebruik maken van OpenOffice.org, AbiWord, HTML,
-       of LaTeX. Zo kunnen gebruikers het formaat wijzigen naar eigen wens.
-
-
-**GEKENDE BUGS EN BEPERKINGEN**
-
-**BESTANDEN**
-
-       *${PREFIX}/bin/gramps*
-       
-       *${PREFIX}/lib/python/dist-packages/gramps/*
-       
-       *${PREFIX}/share/*
-       
-       *${HOME}/.gramps*
-
-
-**AUTEURS**
-       Donald Allingham <don@gramps-project.org>
-       http://gramps-project.org/
-
-       Deze man pagina werd oorspronkelijk geschreven door:
-       Brandon L. Griffith <brandon@debian.org>
-       voor het Debian GNU/Linux systeem.
-
-       Deze man pagina wordt momenteel onderhouden door:
-       Alex Roitman <shura@gramps-project.org>
-
-       Deze nederlandstalige man pagina wordt momenteel onderhouden door:
-       Erik De Richter <frederik.de.richter@pandora.be>
-
-
-**DOCUMENTATIE**
-       De gebruikersdocumentatie is beschikbaar via browser in de webstek.
-
-       De  ontwikkelingsdocumentatie kan gevonden worden op de 
-       http://www.gramps-project.org/wiki/index.php?title=Portal:Developers 
-       webstek.
-
-
-
-August 2005			     4.0.0			     gramps(1)

data/man/pl/conf.py

@@ -1,243 +0,0 @@
-# -*- 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 = 'pl'
-
-# General information about the project.
-project = u'Gramps'
-copyright = u'2012, 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.0'
-# The full version, including alpha/beta/rc tags.
-release = '4.0.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 = [
-    ('pl', '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/pl/gramps.1.in

@@ -1,366 +0,0 @@
-.TH gramps 1 "@VERSION@" "January 2008" "@VERSION@"
-.SH NAME
-gramps \- Genealogical Research and Analysis Management Programming System.
-.br
-(w wolnym tłumaczeniu: System Wspomagania Badań Genealogicznych 
-i Programowego Zarządzania Tą Informacją)
-
-.SH SYNOPSIS
-.B gramps
-.RB [ \-?|\-\^\-help ]
-.RB [ \-\^\-usage ]
-.RB [ \-\^\-version ]
-.RB [ \-l ]
-.RB [ \-u|\-\^\-force-unlock ]
-.RB [ \-O|\-\^\-open=
-.IR BAZA_DANYCH 
-.RB [ \-f|\-\^\-format= 
-.IR FORMAT ]] 
-.RB [ \-i|\-\^\-import=
-.IR PLIK 
-.RB [ \-f|\-\^\-format= 
-.IR FORMAT ]] 
-.RB [ \-i|\-\^\-import= 
-.IR ... ] 
-.RB [ \-e|\-\^\-export=  
-.IR PLIK
-.RB [ \-f|\-\^\-format= 
-.IR FORMAT ]] 
-.RB [ \-a|\-\^\-action= 
-.IR AKCJA ]
-.RB [ \-p|\-\^\-options= 
-.IR CIĄG_OPCJI ]]
-.RB [
-.IR PLIK
-.RB ]
-.if 0 .RB [ bonobo\ options ]
-.if 0 .RB [ sound\ options ]
-.RB [ \-\-version ]
-
-.SH OPIS 
-.PP 
-\fIGramps\fP jest wolnym, darmowym programem genealogicznym OpenSource. Jest
-napisany w Python, przy użyciu interfejsu GTK+/GNOME.
-Dla każdego, kto wcześniej używał innego programu genealogicznego (np.
-\fIFamily Tree Maker (TM)\fR,  \fIPersonal Ancestral Files (TM)\fR, 
-lub GNU Geneweb), zapoznanie się z interfejsem Gramps'a będzie natychmiastowe.
-Program obsługuje także import i eksport w popularnym formacie GEDCOM, który 
-jest używany przez większość programów genealogicznych na świecie.
-
-.SH OPCJE
-.TP 
-.BI gramps " PLIK" 
-Kiedy \fIPLIK\fR jest podany (bez żadnych flag) jako nazwa drzewa rodzinnego
-albo nazwa katalogu z drzewem, to wybrane drzewo jest otwierane i rozpoczynana
-jest sesja interaktywna. Jeśli PLIK jest formatem rozpoznawanym przez Gramps,
-to tworzone jest puste drzewo, którego nazwa bazuje na nazwie \fIPLIKU\fP
-i dane są do niego importowane. Pozostałe opcje są wtedy ignorowane.
-Jest to sposób na używanie programu jako uchwytu obsługującego
-dane genealogiczne, np. w przeglądarce internetowej. Takie wywołanie akceptuje
-każdy format natywny dla grampsa, zobacz poniżej.
-.br
-
-.TP 
-.BI \-f,\-\^\-format= " FORMAT"
-Jawne określenie formatu \fIPLIKU\fR przez poprzedzenie opcji 
-.ig
-\fB\-O\fR,
-..
-\fB\-i\fR, lub \fB\-e\fR. 
-Jeśli opcja \fB\-f\fR nie jest podana dla żadnego \fIPLIKU\fR, 
-to format pliku jest określany na podstawie rozszerzenia albo typu MIME.
-.br
-
-Dostępne formaty wyjściowe to:
-.br
-\fBgramps\-xml\fR (używany jeśli \fIPLIK\fR kończy się na \fB.gramps\fR),
-.br
-\fBgedcom\fR (przyjmowany jeśli \fIPLIK\fR kończy się na \fB.ged\fR),
-.br 
-lub dowolny plik eksportu obsługiwany przez system wtyczek Gramps.
-.br
-
-Formaty
-dostępne dla importu to:
-\fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR,  
-.br
-\fBgramps\-pkg\fR (przyjmowany jeśli \fIPLIK\fR kończy się na \fB.gpkg\fR),
-.br
-oraz \fBgeneweb\fR (przyjmowany jeśli \fIPLIK\fR ma rozszerzenie \fB.gw\fR). 
-.br
-
-Formats dostępne dla eksportu to:
-.ig
-\fBgrdb\fR,
-..
-\fBgramps\-xml\fR, \fBgedcom\fR,
-\fBgramps\-pkg\fR, \fBwft\fR (jeśli rozszerzenie \fIPLIKU\fR to \fB.wft\fR),
-\fBgeneweb\fR, i \fBiso\fR (używany tylko, jeśli jawnie określony przez 
-parametr \fB\-f\fR ).
-
-.TP 
-.BI \-l
-Wyświetla listę dosŧępnych drzew genealogicznych.
-
-.TP
-.BI \-u,\-\^\-force-unlock
-Wymusza odblokowanie bazy danych.
-
-.TP 
-.BI \-O,\-\^\-open= " BAZA_DANYCH"
-Otwiera \fIBAZĘ_DANYCH\fR, która musi istnieć w katalogu baz lub być nazwą 
-istniejącego drzewa rodzinnego. Jeśli nie podano akcji, to opcje eksportu 
-albo importu są wykonywane, a następnie jest uruchamiana sesja interaktywna 
-z otwarciem wybranej bazy.
-
-.TP 
-.BI \-i,\-\^\-import= " PLIK"
-Importuje dane z \fIPLIKU\fR. Jeśli nie określono bazy danych, to 
-tworzona jest tymczasowa baza kasowana po zamknięciu programu.
-.br
-
-Kiedy podany jest więcej niż jeden plik do importu, to każdy z nich musi być 
-poprzedzony flagą \fB\-i\fR. Pliki są importowane w kolejności podanej w linii
-poleceń, np.:  \fB\-i\fR \fIPLIK1\fR \fB\-i\fR \fIPLIK2\fR oraz 
-\fB\-i\fR \fIPLIK2\fR \fB\-i\fR \fIPLIK1\fR mogą utworzyć inne identyfikatory 
-(gramps ID) w bazie wynikowej.
-
-.TP 
-.BI \-e,\-\^\-export= " PLIK"
-Eksportuje dane do \fIPLIKU\fR. Dla formatu \fBiso\fR, \fIPLIK\fR natomiast
-nazwą katalogu, do którego baza danych gramps zostanie zapisana.
-Dla
-.ig
-\fBgrdb\fR,
-..
-\fBgramps\-xml\fR, \fBgedcom\fR, \fBwft\fR, \fBgramps\-pkg\fR, 
-oraz \fBgeneweb\fR, \fIPLIK\fR jest nazwą pliku wynikowego.
-.br
-
-Kiedy więcej niż jeden plik wyjściowy jest podany, każdy musi być poprzedzony
-flagą \fB\-e\fR. Pliki będą zapisywane kolejno, w podanej przez parametry
-kolejności.
-
-.TP 
-.BI \-a,\-\^\-action= " AKCJA"
-Wykonuje \fIAKCJĘ\fR na zaimportowanych danych. Działanie to jest wykonywane
-dopiero, gdy wszystkie określone importy zakończą się powodzeniem. Aktualnie
-dostępne akcje to:
-.br
-\fBsummary\fR (taka sama jak Raporty->Wyświetl->Podsumowanie bazy danych), 
-.br
-\fBcheck\fR (tożsama z Narzędzia->Naprawa bazy danych->Sprawdź i napraw bazę), 
-.br
-\fBreport\fR (generuje raport), oraz
-.br
-\fBtool\fR (uruchamia narzędzie/wtyczkę).
-Zarówno \fBreport\fR jak i \fBtool\fR wymagają podania \fICIĄGU_OPCJI\fR 
-poprzedzonego flagą \fB\-p\fR ). 
-.br
-
-\fICIĄG_OPCJI\fR powinien spełniać następujące warunki:
-.br
-Nie może zawierać spacji. 
-Jeśli niektóre argumenty wymagają spacji, ciąg powinien być enkapsulowany 
-w znakach cudzysłowu, (zobacz składnię powłoki). Ciąg opcji jest listą
-parametrów z nazwą i wartością oddzielonymi znakiem równości. Kolejne
-parametry muszą być oddzielone od siebie znakiem przecinka.
-.br
-
-Większość opcji dla raportów czy narzędzi jest specyficzna dla konkretnej opcji,
-jednak część z opcji jest wspólna, szczególnie dla raportów.
-
-.BI "name=nazwa"
-.br
-Opcja wymagana, określający który raport czy narzędzie będzie uruchamiane.
-Jeśli podana wartość \fInazwy\fR nie pasuje do żadnego dostępnego raportu czy
-narzędzia, zostanie wyświetlony komunikat o błędzie oraz lista dostępnych
-raportów albo opcji (w zależności od wartości parametru \fIAKCJA\fR).
-
-.BI "show=all"
-.br
-Wyświetla listę wszystkich nazw dostępnych opcji wraz z krótkim opisem dla 
-danego raportu albo narzędzia.
-
-.BI "show=nazwa_opcji"
-.br
-Wyświetla opis funkcji udostępnianej przez daną \fInazwę_opcji\fR, jak również
-listę parametrów, które akceptuje dana opcja.
-
-.br
-Używając powyższych opcji jesteś w stanie dowiedzieć się o wszystkich
-możliwościach danego raportu.
-
-.LP
-Kiedy więcej niż jeden akcja wyjściowa jest podana, każda musi być poprzedzona
-flagą \fB\-a\fR. Akcje są wykonywane jedna po drugiej, w kolejności w jakiej
-występują w linii poleceń.
-
-.TP 
-.BI \-d,\-\^\-debug= " NAZWA_LOGGERA"
-Włącza logi debuggowania dla celów programistycznych i testowych. Zobacz
-do kodu źródłowego po szczegóły.
-
-.TP
-.BI \-\^\-version
-Wyświetla wersję programu i kończy działanie.
-\" change 0 to 1 to enable output of OAF options
-.if 1 \{
-.PP
-Następujące opcje są używane przy aktywacji Bonobo:
-.TP 
-.BI \-\^\-oaf-ior-fd= "FD"
-Deskryptor pliku, do którego wpisać OAF IOR.
-.TP 
-.BI \-\^\-oaf-activate-iid= " IID"
-OAF IID do aktywacji.
-.TP 
-.BI \-\^\-oaf-private
-Wstgrzymuje rejestrację serwera przez OAF.
-\}
-\" change 0 to 1 to enable output of Gnome sound options
-.if 1 \{
-.PP
-Następujące opcje są używane do kontroli dźwięku generowanego za pomocą 
-Gnome Library.
-.TP
-.BI \-\^\-disable-sound
-Wyłącza użycie serwera dźwięku.
-.TP
-.BI \-\^\-enable-sound
-Włącza użycie serwera dźwięku.
-.TP
-.BI \-\^\-espeaker= " HOSTNAME:PORT"
-Host:port na którym jest uruchomiony serwer dźwięku.
-\}
-
-.SH "Działanie"
-.br
-Jeśli pierwszy argument nie rozpoczyna się znakiem myślnik, (nie jest flagą),
-to gramps będzie próbował otworzyć plik podany przez pierwszy argument, a 
-następnie sesję interaktywną a pozostałą część parametrów w linii poleceń
-zignoruje.
-
-.LP
-Jeśli podana jest flaga \fB\-O\fR, będzie próbował otworzyć podaną bazę 
-i pracować na danych w niej zawartych realizując podane później polecenia
-z linii komend.
-
-.LP
-Z flagą \fB\-O\fR czy bez, może występować wiele importów, eksportów oraz
-akcji określonych za pomocą flag \fB\-i\fR, \fB\-e\fR, oraz \fB\-a\fR .  
-
-.LP
-Kolejność podawania opcji \fB\-i\fR, \fB\-e\fR, czy \fB\-a\fR nie ma znaczenia.
-Wykonywane są one zawsze w kolejności: wszystkie importy (jeśli podane) -> 
-wszystkie akcje (jeśli podane) -> wszystkie eksporty (jeśli podane)
-Ale otwarcie bazy zawsze musi być na pierwszym parametrem !
-
-.LP
-Jeśli nie podano opcji \fB\-O\fR lub \fB\-i\fR, gramps uruchomi swoje główne
-okno i rozpocznie normalną sesję interaktywną z pustą bazą danych (ponieważ
-nie zdołał przetworzyć do niej żadnych danych).
-
-.LP
-Jeśli nie podano opcji\fB\-e\fR albo \fB\-a\fR gramps uruchomi swoje głowne 
-okno i rozpocznie normalną sesję interaktywną z bazą będącą wynikiem wszystkich importów. Ta baza będzie znajdować się w pliku \fBimport_db.grdb\fR
-w katalogu \fB~/.gramps/import\fR.
-
-.LP
-Błąd podczas importu, eksportu albo dowolnej akcji będzie przekierowany na
-\fIstdout\fR (jeśli wyjątek zostanie obsłużony przez gramps) albo na
-\fIstderr\fR (jeśli nie jest obsłużony). Użyj standardowych przekierowań
-strumieni \fIstdout\fR oraz \fIstderr\fR jeśli chcesz zapisać wyświetlane 
-informacje i błędy do pliku. 
-
-.SH PRZYKŁADY
-.TP 
-Aby otworzyć istniejące drzewo rodzinne i zaimportować dane do niego, można wpisać: 
-\fBgramps\fR \fB\-O\fR \fI'Moje drzewo'\fR \fB\-i\fR \fI~/db3.gramps\fR
-.TP 
-Powyższa opcja otwiera istniejące drzewo, ale gdy chcesz zrobić wykonać taką
-samą akcję tworząc tymczasowe drzewo: wystarczy wpisać:
-\fBgramps\fR \fB\-i\fR \fI'Moje drzewo'\fR \fB\-i\fR \fI~/db3.gramps\fR
-.TP 
-Aby zaimportować cztery bazy (których formaty zostaną określone na podstawie
-ich nazw) i następnie sprawdić powstałą bazę pod kątem błędów, należy wpisać:
-\fBgramps\fR \fB\-i\fR \fIplik1.ged\fR \fB\-i\fR \fIplik2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-i\fR \fIplik4.wft\fR \fB\-a\fR \fIcheck\fR 
-.TP 
-Aby jawnie określić formaty w powyższym przykładzie, należy dodać nazwy plików
-z odpowiednimi opcjami \fB\-f\fR options: 
-\fBgramps\fR \fB\-i\fR \fIplik1.ged\fR \fB\-f\fR \fIgedcom\fR \fB\-i\fR \fIplik2.tgz\fR \fB\-f\fR \fIgramps-pkg\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-f\fR \fIgramps-xml\fR \fB\-i\fR \fIplik4.wft\fR \fB\-f\fR \fIwft\fR  \fB\-a\fR \fIcheck\fR 
-.TP 
-Aby zachować bazę z wynikami wszystkich importów, należy dodać flagę \fB\-e\fR (należy użyć \fB\-f\fR jeśli nazwa pliku nie pozwala gramps'owi na odgadnięcie formatu wyjściowego):
-\fBgramps\fR \fB\-i\fR \fIplik1.ged\fR \fB\-i\fR \fIplik2.tgz\fR \fB\-e\fR \fI~/nowy-pakiet\fR \fB\-f\fR \fIgramps-pkg\fR 
-.TP 
-W celu zaimportwania trzech baz i rozpoczęcia sesji interaktywnej z wynikiem 
-importu należy użyć polecenia podobnego do poniższego: 
-\fBgramps\fR \fB\-i\fR \fIplik1.ged\fR \fB\-i\fR \fIplik22.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR 
-.TP 
-Aby uruchomić narzędzie weryfikacji z linii poleceń i wyświetlić wyniki na 
-stdout: 
-\fBgramps\fR \fB\-O\fR \fI'Moje drzewo'\fR \fB-a\fR \fItool\fR \fB-p\fR \fBname\fR=\fIverify\fR
-.TP 
-Zawsze można też po prostu uruchomić sesję interaktywną wpisująć: 
-\fBgramps\fR 
-
-.SH ZMIENNE ŚRODOWISKOWE
-Program sprawdza w systemie istnienie i wartości następujących zmiennych:
-
-\fBLANG\fR - określa ustawienia, jaki język zostanie wybrany. 
-Np.: polski to pl_PL.UTF-8.
-
-\fBGRAMPSHOME\fR - określa folder, w którym będzie zapisywane ustawienia i bazy
-programu. Domyślnie jest on nieustawiony, a program przyjmuje, że katalog
-z danymi zostanie utworzony w profilu użytkownika (zmienna HOME pod Linuxem 
-albo USERPROFILE pod Windows 2000/XP).
-
-
-.SH KONCEPCJA
-Obsługa systemu rozszerzeń bazującego na pythonie, pozwalającego na dodawanie 
-formatów importu i eksportu zapisów, generatorów raportów, narzędzi i filtrów
-wyświetlania bez modyfikowania głównego programu
-.LP 
-Dodatkowo oprócz generowania standardowego wyjścia na drukarkę, raporty mogą
-także być generowane dla innch systemów i do innych formatów, takich jak:
-\fIOpenOffice.org\fR, \fIAbiWord\fR, HTML, lub LaTeX aby umożliwić użytkownikm
-wybór formatu wyjściowego w zależności od ich potrzeb.
-
-.SH ZNANE BŁĘDY I OGRANICZENIA
-Prawdopodobne. Lista błędów i propozycji znajduje się na:
-\fIhttp://developers.gramps-project.org\fR. 
-
-.SH PLIKI
-.LP 
-\fI${PREFIX}/bin/gramps\fP 
-.br 
-\fI${PREFIX}/share/gramps\fP
-.br 
-\fI${HOME}/.gramps\fP (jeśli nie użyta została zmienna środowiskowa GRAMPSHOME)
-
-.SH AUTORZY
-Donald Allingham \fI<don@gramps-project.org>\fR
-.br 
-\fIhttp://gramps.sourceforge.net\fR
-.LP 
-Ta strona man jest tłumaczeniem strony man napisanej przez:
-.br 
-Brandon L. Griffith \fI<brandon@debian.org>\fR
-.br
-dla systemu Debian GNU/Linux.
-.LP 
-Ta strona aktualnie jest pod opeką:
-.br 
-Projekt Gramps\fI<xxx@gramps-project.org>\fR
-.br 
-Tłumaczenie na polski: Łukasz Rymarczyk <yenidai@poczta.onet.pl>
-.br
-
-.SH DOCUMENTATION
-Dokumentacja użytkownika jest dostępna poprzez standardową przeglądarkę
-pomocy systemu GNOME. Dokumentacja dostępna jest także w formacie XML jako
-plik \fBgramps-manual.xml\fR w folderze \fIdoc/gramps-manual/$LANG\fR
-w głównym źródle dystrybucji.
-.LP 
-Dokumentacja dla programistów jest dostępna na stronie projektu:
-\fIhttp://developers.gramps-project.org\fR. 

data/man/pl/pl.rst

@@ -1,308 +0,0 @@
-Polish
-=======
-
-gramps(1)			     3.4.0			     gramps(1)
-
-
-
-**NAME**
-       gramps - Genealogical Research and Analysis Management Programming Sys‐
-       tem.
-       (w wolnym tłumaczeniu: System Wspomagania Badań Genealogicznych i  Pro‐
-       gramowego Zarządzania Tą Informacją)
-
-
-**SYNOPSIS**
-       gramps	[-?|--help]  [--usage]	[--version]  [-l]  [-u|--force-unlock]
-       [-O|--open=  BAZA_DANYCH  [-f|--format=	FORMAT]]  [-i|--import=   PLIK
-       [-f|--format=   FORMAT]]   [-i|--import=   ...]	  [-e|--export=   PLIK
-       [-f|--format= FORMAT]] [-a|--action= AKCJA] [-p|--options= CIĄG_OPCJI]]
-       [ PLIK ] [--version]
-
-
-**OPIS**
-       Gramps  jest wolnym, darmowym programem genealogicznym OpenSource. Jest
-       napisany w Python, przy użyciu interfejsu GTK+/GNOME.  Dla każdego, kto
-       wcześniej  używał  innego  programu  genealogicznego  (np.  Family Tree
-       Maker (TM),  Personal Ancestral Files (TM), lub	GNU  Geneweb),	zapoz‐
-       nanie  się  z  interfejsem  Gramps'a  będzie  natychmiastowe.   Program
-       obsługuje także import i eksport w popularnym  formacie	GEDCOM,  który
-       jest używany przez większość programów genealogicznych na świecie.
-
-
-**OPCJE**
-       **gramps** *PLIK*
-	      Kiedy *PLIK* jest  podany  (bez  żadnych flag) jako nazwa drzewa
-	      rodzinnego albo nazwa katalogu z drzewem, to wybrane drzewo jest
-	      otwierane  i  rozpoczynana  jest	sesja interaktywna. Jeśli PLIK
-	      jest formatem rozpoznawanym przez Gramps, to tworzone jest puste
-	      drzewo,  którego nazwa bazuje na nazwie PLIKU i dane są do niego
-	      importowane. Pozostałe  opcje  są  wtedy	ignorowane.   Jest  to
-	      sposób  na  używanie  programu  jako  uchwytu obsługującego dane
-	      genealogiczne, np. w przeglądarce internetowej. Takie  wywołanie
-	      akceptuje każdy format natywny dla grampsa, zobacz poniżej.
-
-
-       **-f** , **--format=** *FORMAT*
-	      Jawne  określenie formatu PLIKU przez poprzedzenie opcji -i, lub
-	      -e.  Jeśli opcja -f nie jest podana dla żadnego PLIKU, to format
-	      pliku jest określany na podstawie rozszerzenia albo typu MIME.
-
-	      Dostępne formaty wyjściowe to:
-	      gramps-xml (używany jeśli PLIK kończy się na .gramps),
-	      gedcom (przyjmowany jeśli PLIK kończy się na .ged),
-	      lub  dowolny  plik  eksportu  obsługiwany  przez	system wtyczek
-	      Gramps.
-
-	      Formaty dostępne dla importu to: grdb, gramps-xml, gedcom,
-	      gramps-pkg (przyjmowany jeśli PLIK kończy się na .gpkg),
-	      oraz geneweb (przyjmowany jeśli PLIK ma rozszerzenie .gw).
-
-	      Formats  dostępne   dla	eksportu   to:	 gramps-xml,   gedcom,
-	      gramps-pkg,  wft	(jeśli rozszerzenie PLIKU to .wft), geneweb, i
-	      iso (używany tylko, jeśli jawnie określony przez parametr -f ).
-
-
-       **-l**     
-          Wyświetla listę dosŧępnych drzew genealogicznych.
-
-
-       **-u** , **--force-unlock**
-	      Wymusza odblokowanie bazy danych.
-
-
-       **-O** , **--open=** *BAZA_DANYCH*
-	      Otwiera *BAZĘ_DANYCH* , która musi istnieć w katalogu baz  lub  być
-	      nazwą istniejącego drzewa rodzinnego. Jeśli nie podano akcji, to
-	      opcje eksportu albo importu  są  wykonywane,  a  następnie  jest
-	      uruchamiana sesja interaktywna z otwarciem wybranej bazy.
-
-
-       **-i** , **--import=** *PLIK*
-	      Importuje  dane  z *PLIKU* . Jeśli  nie określono bazy danych, to
-	      tworzona jest tymczasowa baza kasowana po zamknięciu programu.
-
-	      Kiedy podany jest więcej niż jeden plik do importu, to  każdy  z
-	      nich musi być poprzedzony flagą -i. Pliki są importowane w kole‐
-	      jności podanej w linii poleceń, np.:  -i PLIK1 -i PLIK2 oraz  -i
-	      PLIK2  -i  PLIK1 mogą utworzyć inne identyfikatory (gramps ID) w
-	      bazie wynikowej.
-
-
-       **-e** , **--export=** *PLIK*
-	      Eksportuje dane do *PLIKU* . Dla formatu iso, PLIK natomiast  nazwą
-	      katalogu,  do którego baza danych gramps zostanie zapisana.  Dla
-	      gramps-xml, gedcom, wft, gramps-pkg,  oraz  geneweb,  PLIK  jest
-	      nazwą pliku wynikowego.
-
-	      Kiedy  więcej  niż  jeden plik wyjściowy jest podany, każdy musi
-	      być poprzedzony flagą  -e.  Pliki  będą  zapisywane  kolejno,  w
-	      podanej przez parametry kolejności.
-
-
-       **-a** , **--action=** *AKCJA*
-	      Wykonuje	AKCJĘ  na  zaimportowanych  danych.  Działanie to jest
-	      wykonywane dopiero, gdy wszystkie określone importy zakończą się
-	      powodzeniem. Aktualnie dostępne akcje to:
-	      summary  (taka  sama  jak  Raporty->Wyświetl->Podsumowanie  bazy
-	      danych),
-	      check  (tożsama  z  Narzędzia->Naprawa  bazy  danych->Sprawdź  i
-	      napraw bazę),
-	      report (generuje raport), oraz
-	      tool  (uruchamia	narzędzie/wtyczkę).  Zarówno report jak i tool
-	      wymagają podania CIĄGU_OPCJI poprzedzonego flagą -p ).
-
-	      CIĄG_OPCJI powinien spełniać następujące warunki:
-	      Nie może zawierać spacji.   Jeśli  niektóre  argumenty  wymagają
-	      spacji,  ciąg  powinien  być enkapsulowany w znakach cudzysłowu,
-	      (zobacz składnię powłoki). Ciąg opcji jest  listą  parametrów  z
-	      nazwą i wartością oddzielonymi znakiem równości. Kolejne parame‐
-	      try muszą być oddzielone od siebie znakiem przecinka.
-
-	      Większość opcji dla raportów czy narzędzi jest  specyficzna  dla
-	      konkretnej opcji, jednak część z opcji jest wspólna, szczególnie
-	      dla raportów.
-
-	      **name=nazwa**
-	      Opcja wymagana, określający który raport	czy  narzędzie	będzie
-	      uruchamiane.   Jeśli  podana wartość nazwy nie pasuje do żadnego
-	      dostępnego raportu czy narzędzia, zostanie wyświetlony komunikat
-	      o   błędzie   oraz  lista  dostępnych  raportów  albo  opcji  (w
-	      zależności od wartości parametru AKCJA).
-
-	      **show=all**
-	      Wyświetla listę wszystkich nazw dostępnych opcji wraz z  krótkim
-	      opisem dla danego raportu albo narzędzia.
-
-	      **show=nazwa_opcji**
-	      Wyświetla opis funkcji udostępnianej przez daną nazwę_opcji, jak
-	      również listę parametrów, które akceptuje dana opcja.
-
-	      Używając powyższych opcji  jesteś  w  stanie  dowiedzieć	się  o
-	      wszystkich możliwościach danego raportu.
-
-
-       Kiedy  więcej  niż  jeden  akcja  wyjściowa jest podana, każda musi być
-       poprzedzona flagą -a. Akcje są wykonywane jedna	po  drugiej,  w  kole‐
-       jności w jakiej występują w linii poleceń.
-
-
-       **-d** , **--debug=** *NAZWA_LOGGERA*
-	      Włącza   logi   debuggowania   dla   celów  programistycznych  i
-	      testowych. Zobacz do kodu źródłowego po szczegóły.
-
-
-       **--version**
-	      Wyświetla wersję programu i kończy działanie.
-
-
-**Działanie**
-       Jeśli  pierwszy	argument nie rozpoczyna się znakiem myślnik, (nie jest
-       flagą), to gramps będzie próbował otworzyć plik podany  przez  pierwszy
-       argument, a następnie sesję interaktywną a pozostałą część parametrów w
-       linii poleceń zignoruje.
-
-
-       Jeśli podana jest flaga -O, będzie próbował otworzyć podaną bazę i pra‐
-       cować  na danych w niej zawartych realizując podane później polecenia z
-       linii komend.
-
-
-       Z flagą -O czy bez, może  występować  wiele  importów,  eksportów  oraz
-       akcji określonych za pomocą flag -i, -e, oraz -a .
-
-
-       Kolejność  podawania opcji -i, -e, czy -a nie ma znaczenia.  Wykonywane
-       są one zawsze w kolejności: wszystkie importy (jeśli podane) ->	wszys‐
-       tkie  akcje  (jeśli  podane)  ->  wszystkie eksporty (jeśli podane) Ale
-       otwarcie bazy zawsze musi być na pierwszym parametrem !
-
-
-       Jeśli nie podano opcji -O lub -i, gramps uruchomi swoje główne  okno  i
-       rozpocznie  normalną  sesję  interaktywną z pustą bazą danych (ponieważ
-       nie zdołał przetworzyć do niej żadnych danych).
-
-
-       Jeśli nie podano opcji-e albo -a gramps uruchomi swoje  głowne  okno  i
-       rozpocznie  normalną  sesję interaktywną z bazą będącą wynikiem wszyst‐
-       kich importów. Ta baza będzie znajdować się w  pliku  import_db.grdb  w
-       katalogu ~/.gramps/import.
-
-
-       Błąd podczas importu, eksportu albo dowolnej akcji będzie przekierowany
-       na stdout (jeśli wyjątek  zostanie  obsłużony  przez  gramps)  albo  na
-       stderr  (jeśli  nie  jest  obsłużony).  Użyj standardowych przekierowań
-       strumieni stdout oraz stderr jeśli chcesz zapisać wyświetlane  informa‐
-       cje i błędy do pliku.
-
-
-**PRZYKŁADY**
-       Aby  otworzyć  istniejące drzewo rodzinne i zaimportować dane do niego,
-       można wpisać:
-       
-	      gramps -O 'Moje drzewo' -i ~/db3.gramps
-
-       Powyższa opcja otwiera istniejące drzewo, ale gdy chcesz zrobić wykonać
-       taką samą  akcję  tworząc tymczasowe drzewo: wystarczy wpisać: 
-          
-          gramps -i 'Moje drzewo' -i ~/db3.gramps
-
-       Aby zaimportować cztery bazy (których formaty zostaną określone na pod‐
-       stawie ich  nazw)  i następnie sprawdić powstałą bazę pod kątem błędów,
-       należy wpisać: 
-          
-          gramps -i plik1.ged -i plik2.tgz -i  ~/db3.gramps
-	      -i plik4.wft -a check
-
-       Aby jawnie określić formaty w powyższym przykładzie, należy dodać nazwy
-       plików z odpowiednimi opcjami -f options: 
-       
-       gramps -i plik1.ged -f gedcom -i  plik2.tgz  -f  gramps-pkg  -i  
-       ~/db3.gramps -f gramps-xml -i plik4.wft -f wft -a check
-
-       Aby zachować bazę z wynikami wszystkich importów, należy dodać flagę -e
-       (należy użyć -f jeśli nazwa pliku nie pozwala gramps'owi na odgadnięcie
-       formatu wyjściowego):
-       
-	      gramps -i plik1.ged -i plik2.tgz -e ~/nowy-pakiet -f gramps-pkg
-
-       W celu zaimportwania trzech baz i  rozpoczęcia  sesji  interaktywnej  z
-       wynikiem importu należy użyć polecenia podobnego do poniższego: 
-       
-          gramps -i plik1.ged -i plik22.tgz -i ~/db3.gramps
-
-       Aby uruchomić narzędzie weryfikacji z linii poleceń i wyświetlić wyniki
-       na stdout: 
-       
-          gramps -O 'Moje drzewo' -a tool -p name=verify
-
-       Zawsze można też po prostu uruchomić sesję interaktywną wpisująć:
-       
-	      gramps
-
-
-**ZMIENNE ŚRODOWISKOWE**
-
-       Program	sprawdza  w systemie istnienie i wartości następujących zmien‐
-       nych:
-
-       **LANG** - określa ustawienia, jaki język zostanie wybrany.	Np.: polski to
-       pl_PL.UTF-8.
-
-       **GRAMPSHOME**  -  określa  folder, w którym będzie zapisywane ustawienia i
-       bazy programu. Domyślnie jest on nieustawiony, a program przyjmuje,  że
-       katalog z danymi zostanie utworzony w profilu użytkownika (zmienna HOME
-       pod Linuxem albo USERPROFILE pod Windows 2000/XP).
-
-
-
-**KONCEPCJA**
-       Obsługa systemu rozszerzeń bazującego  na  pythonie,  pozwalającego  na
-       dodawanie  formatów  importu  i eksportu zapisów, generatorów raportów,
-       narzędzi i filtrów wyświetlania bez modyfikowania głównego programu
-
-       Dodatkowo oprócz generowania standardowego wyjścia na drukarkę, raporty
-       mogą  także  być  generowane  dla  innch systemów i do innych formatów,
-       takich jak: OpenOffice.org, AbiWord,  HTML,  lub  LaTeX	aby  umożliwić
-       użytkownikm wybór formatu wyjściowego w zależności od ich potrzeb.
-
-
-**ZNANE BŁĘDY I OGRANICZENIA**
-       Prawdopodobne. Lista błędów i propozycji znajduje się na: 
-       http://www.gramps-project.org/wiki/index.php?title=Portal:Developers .
-
-
-**PLIKI**
-       
-       *${PREFIX}/bin/gramps*
-       
-       *${PREFIX}/lib/python/dist-packages/gramps/*
-       
-       *${PREFIX}/share/*
-       
-       *${HOME}/.gramps (jeśli nie użyta została  zmienna  środowiskowa	GRAMP‐
-       SHOME)*
-
-
-**AUTORZY**
-       Donald Allingham <don@gramps-project.org>
-       http://gramps-project.org/
-
-       Ta strona man jest tłumaczeniem strony man napisanej przez:
-       Brandon L. Griffith <brandon@debian.org>
-       dla systemu Debian GNU/Linux.
-
-       Ta strona aktualnie jest pod opeką:
-       Projekt Gramps<xxx@gramps-project.org>
-       Tłumaczenie na polski: Łukasz Rymarczyk <yenidai@poczta.onet.pl>
-
-
-**DOCUMENTATION**
-       Dokumentacja użytkownika jest dostępna poprzez standardową przeglądarkę.
-
-       Dokumentacja  dla  programistów	jest  dostępna	na  stronie  projektu:
-       http://www.gramps-project.org/wiki/index.php?title=Portal:Developers 
-
-
-
-January 2008			     4.0.0			     gramps(1)

data/man/pt_BR/conf.py

@@ -1,243 +0,0 @@
-# -*- 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 = 'pt_BR'
-
-# General information about the project.
-project = u'Gramps'
-copyright = u'2012, 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.0'
-# The full version, including alpha/beta/rc tags.
-release = '4.0.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 = [
-    ('pt_BR', '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/pt_BR/gramps.1.in

@@ -1,325 +0,0 @@
-.TH gramps 1 "@VERSION@" "Janeiro de 2008" "@VERSION@"
-.SH NOME
-gramps \- Programa para pesquisa genealógica.
-
-.SH RESUMO
-.B gramps
-.RB [ \-?|\-\^\-help ]
-.RB [ \-\^\-usage ]
-.RB [ \-\^\-version ]
-.RB [ \-l ]
-.RB [ \-u|\-\^\-force-unlock ]
-.RB [ \-O|\-\^\-open=
-.IR BANCODEDADOS 
-.RB [ \-f|\-\^\-format= 
-.IR FORMATO ]] 
-.RB [ \-i|\-\^\-import=
-.IR ARQUIVO 
-.RB [ \-f|\-\^\-format= 
-.IR FORMATO ]] 
-.RB [ \-i|\-\^\-import= 
-.IR ... ] 
-.RB [ \-e|\-\^\-export= 
-.IR ARQUIVO
-.RB [ \-f|\-\^\-format= 
-.IR FORMATO ]] 
-.RB [ \-a|\-\^\-action= 
-.IR AÇÃO ]
-.RB [ \-p|\-\^\-options= 
-.IR OPÇÕES ]]
-.RB [
-.IR ARQUIVO
-.RB ]
-.if 0 .RB [ bonobo\ options ]
-.if 0 .RB [ sound\ options ]
-.RB [ \-\-version ]
-
-.SH DESCRIÇÃO
-.PP 
-\fIGramps\fP é um programa de genealogia livre e de código aberto. Ele é escrito
-em Python e usa a interface GTK+/GNOME.
-Gramps deve parecer familiar a qualquer pessoa que já tenha usado outro programa
-de genealogia, tais como o \fIFamily Tree Maker (TM)\fR,  \fIPersonal Ancestral
-Files (TM)\fR, ou o GNU Geneweb.
-Ele suporta a importação do formato GEDCOM, que é amplamente usado por quase 
-todos os outros programas de genealogia.
-
-.SH OPÇÕES
-.TP 
-.BI gramps " ARQUIVO" 
-Quando \fIARQUIVO\fR for indicado (sem qualquer outra opção) como um nome de
-árvore genealógica ou como pasta do banco de dados, ela será aberta e iniciada
-uma sessão interativa. Se ARQUIVO for um formato compreendido pelo Gramps, será 
-criada uma árvore genealógica vazia com o nome baseado no \fIARQUIVO\fP
-e os dados são importados para ela. As demais opções serão ignoradas. Esta forma
-de execução é apropriada para usar o Gramps como manipulador de dados genealógicos
-em, por exemplo, navegadores Web. Este método aceita qualquer formato de dados 
-nativo do Gramps, conforme abaixo.
-.br
-
-.TP 
-.BI \-f,\-\^\-format= " FORMATO"
-Indica expressamente o formato do \fIARQUIVO\fR, precedente das opções  
-.ig
-\fB\-O\fR,
-..
-\fB\-i\fR ou 
-\fB\-e\fR. Se a opção \fB\-f\fR não for fornecida para um \fIARQUIVO\fR, 
-o formato será identificado de acordo com a sua extensão ou tipo MIME. 
-.br
-
-Os formatos disponíveis para exportação são \fBgramps\-xml\fR (se o \fIARQUIVO\fR 
-terminar com \fB.gramps\fR), \fBgedcom\fR (se o \fIARQUIVO\fR terminar com \fB.ged\fR) 
-ou qualquer outro formato de arquivo disponível através do sistema de plugins do 
-Gramps.
-.br
-
-Os formatos disponíveis para importação são \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR,  
-\fBgramps\-pkg\fR (se o \fIARQUIVO\fR terminar com \fB.gpkg\fR), e \fBgeneweb\fR 
-(se o \fIARQUIVO\fR terminar com \fB.gw\fR).
-.br
-
-Os formatos disponíveis para exportação são
-.ig
-\fBgrdb\fR,
-..
-\fBgramps\-xml\fR, \fBgedcom\fR,
-\fBgramps\-pkg\fR, \fBwft\fR (se o \fIARQUIVO\fR terminar com \fB.wft\fR),
-\fBgeneweb\fR, e \fBiso\fR (deve sempre ser indicado com a opção
-\fB\-f\fR).
-
-.TP 
-.BI \-l
-Exibe uma lista com as árvores genealógicas conhecidas.
-
-.TP
-.BI \-u,\-\^\-force-unlock
-Desbloqueia um banco de dados previamente bloqueado.
-
-.TP 
-.BI \-O,\-\^\-open= " BANCODEDADOS"
-Abre o \fIBANCODEDADOS\fR, que deve ser uma pasta de banco de dados ou um nome de árvore
-genealógica existentes.
-Se não forem indicadas opções de ação, importação ou exportação na linha de comando, 
-será iniciada uma sessão interativa usando este banco de dados.
-
-.TP 
-.BI \-i,\-\^\-import= " ARQUIVO"
-Importa os dados do \fIARQUIVO\fR. Se não for indicado um banco de dados, o Gramps usará
-um arquivo temporário, que será excluído ao sair do programa.
-.br
-
-Quando mais de um arquivo de origem for indicado, cada um deles deve ser precedido da
-opção \fB\-i\fR. Os arquivos são importados na ordem indicada, por exemplo, 
-\fB\-i\fR \fIARQUIVO1\fR \fB\-i\fR \fIARQUIVO2\fR  
-e \fB\-i\fR \fIARQUIVO2\fR \fB\-i\fR \fIARQUIVO1\fR poderá produzir diferentes gramps IDs 
-no banco de dados resultante. 
-
-.TP 
-.BI \-a,\-\^\-action= " AÇÃO"
-Executa a \fIAÇÃO\fR nos dados importados. Isto será executado após a conclusão de todas
-as importações. Até o momento, as ações disponíveis são \fBsummary\fR (o mesmo que 
-Relatórios->Exibir->Resumo), 
-\fBcheck\fR (o mesmo que Ferramentas->Processamento do banco de dados->Verificar e reparar), 
-\fBreport\fR (gera o relatório), e
-\fBtool\fR (executa uma ferramenta de plugin).
-Para o \fBreport\fR e \fBtool\fR é necessário fornecer \fIOPÇÕES\fR (com uso da opção  
-\fB\-p\fR). 
-.br
-
-As \fIOPÇÕES\fR devem satisfazer as seguintes condições:
-.br
-Não podem conter espaços.
-Se alguns argumentos precisam incluir espaços, a string deve
-ser colocada entre aspas, ou seja, seguir a sintaxe do shell.
-String de opção é uma lista de pares com o nome e o valor (separados por 
-sinal de igual). Os pares de nome e valor devem ser separados por vírgula.
-.br
-
-Muitas opções são específicas de cada relatório ou ferramenta. 
-Entretanto, algumas opções são comuns.
-
-.BI "name=nome"
-.br
-Esta opção obrigatória determina qual relatório ou ferramenta será executado.
-Se o \fInome\fR fornecido não corresponder a um relatório ou ferramenta, será
-exibida uma mensagem de erro seguida de uma lista de relatórios e ferramentas
-disponíveis (dependendo da \fIAÇÃO\fR).
-
-.BI "show=all"
-.br
-Isto irá gerar uma lista com os nomes para todas as opções disponíveis de um determinado
-relatório ou ferramenta.
-
-.BI "show="nome_opção
-.br
-Isto irá exibir a descrição da funcionalidade indicada por \fInome_opção\fR, bem 
-como quais são os tipos aceitáveis e os valores para esta opção.
-
-.br
-Use as opções acima para descobrir
-tudo sobre um determinado relatório.
-
-.LP
-Quando mais de uma ação de saída for indicada, cada uma deve ser precedida da opção 
-\fB\-a\fR. As ações são realizadas uma a uma, na ordem indicada.
-
-.TP 
-.BI \-d,\-\^\-debug= " ARQUIVO_REGISTRO"
-Ativa os registros para desenvolvimento e testes. Veja o código-fonte para mais detalhes.
-.TP
-.BI \-\^\-version
-Exibe o número da versão do Gramps e finaliza.
-\" altera de 0 para 1 para ativar a saída das opções OAF
-.if 0 \{
-.PP
-As opções a seguir são usadas para ativação do Bonobo.
-.TP 
-.BI \-\^\-oaf-ior-fd= "FD"
-Descritor do arquivo para exibir o OAF IOR em
-.TP 
-.BI \-\^\-oaf-activate-iid= " IID"
-OAF IID para ativar
-.TP 
-.BI \-\^\-oaf-private
-Impedir o registro do servidor com OAF
-\}
-\" altera de 0 para 1 para ativar a saída das opções de som do Gnome
-.if 0 \{
-.PP
-As opções a seguir são usadas para controlar o som usando a biblioteca do Gnome.
-.TP
-.BI \-\^\-disable-sound
-Desativa o servidor de som
-.TP
-.BI \-\^\-enable-sound
-Ativa o servidor de som
-.TP
-.BI \-\^\-espeaker= " HOSTNAME:PORT"
-Máquina:porta que o servidor de som utiliza para execução
-\}
-
-.SH "Operação"
-.br
-Se o primeiro argumento da linha de comando não começar com um traço (isto é, 
-sem uma opção), o Gramps tentará abrir o arquivo com o nome fornecido pelo primeiro
-argumento e iniciar a sessão interativa, ignorando o resto dos argumentos da
-linha de comando.
-
-.LP
-Se for fornecida a opção \fB\-O\fR, então o Gramps tentará abrir o banco de dados
-indicado e trabalhar com estes dados, de acordo com as instruções dos parâmetros 
-adicionais da linha de comando.
-
-.LP
-Com ou sem a opção \fB\-O\fR, pode haver múltiplas importações, exportações e
-ações indicadas pela linha de comando usando as opções \fB\-i\fR,
-\fB\-e\fR e \fB\-a\fR.  
-
-.LP
-A ordem das opções \fB\-i\fR, \fB\-e\fR ou \fB\-a\fR não importa. A ordem
-utilizada será sempre esta: todas as importações (se existirem) -> todas
-as ações (se existirem) -> todas as exportações (se existirem). Mas a abertura 
-deve estar sempre em primeiro lugar!
-
-.LP
-Se as opções \fB\-O\fR ou \fB\-i\fR não forem fornecidas, o Gramps será aberto
-com a sua janela principal e iniciará a sessão interativa padrão com um banco
-de dados vazio, uma vez que não há nada a processar.
-
-.LP
-Se as opções \fB\-e\fR ou \fB\-a\fR não forem fornecidas, o Gramps será aberto
-com a sua janela principal e iniciará a sessão interativa padrão com um banco
-de dados resultante de todas as importações. Este banco de dados está localizado
-no arquivo \fBimport_db.grdb\fR da pasta \fB~/.gramps/import\fR.
-
-.LP
-Os erros encontrados durante a importação, exportação ou ação, serão direcionados 
-para \fIstdout\fR (se forem exceções tratadas pelo Gramps) ou para \fIstderr\fR
-(se não forem tratadas). Use redirecionamentos usuais de \fIstdout\fR e 
-\fIstderr\fR do shell para salvar mensagens e erros em arquivos.
-
-.SH EXEMPLOS
-.TP 
-Abrir uma árvore genealógica existente e importar um arquivo xml para ela:
-\fBgramps\fR \fB\-O\fR \fI'Minha árvore genealógica'\fR \fB\-i\fR \fI~/db3.gramps\fR
-.TP 
-Fazer as mesmas alterações da árvore genealógica do comando anterior, mas importar a árvore genealógica temporária e iniciar uma sessão interativa:
-\fBgramps\fR \fB\-i\fR \fI'Minha árvore genealógica'\fR \fB\-i\fR \fI~/db3.gramps\fR
-.TP 
-Importar quatro bancos de dados (cujos formatos podem ser reconhecidos pelos nomes) e verificar a existência de erros no banco de dados resultante:
-\fBgramps\fR \fB\-i\fR \fIarquivo1.ged\fR \fB\-i\fR \fIarquivo2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-i\fR \fIarquivo4.wft\fR \fB\-a\fR \fIcheck\fR 
-.TP 
-Indicar de forma explícita os formatos do exemplo acima, atribuindo os nomes dos arquivos com as opções \fB\-f\fR apropriadas:
-\fBgramps\fR \fB\-i\fR \fIarquivo1.ged\fR \fB\-f\fR \fIgedcom\fR \fB\-i\fR \fIarquivo2.tgz\fR \fB\-f\fR \fIgramps-pkg\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-f\fR \fIgramps-xml\fR \fB\-i\fR \fIarquivo4.wft\fR \fB\-f\fR \fIwft\fR  \fB\-a\fR \fIcheck\fR 
-.TP 
-Gravar o banco de dados resultante de todas as importações, indicando a opção \fB\-e\fR (use \fB\-f\fR se o nome do arquivo não permirtir que o gramps reconheça o formato automaticamente):
-\fBgramps\fR \fB\-i\fR \fIarquivo1.ged\fR \fB\-i\fR \fIarquivo2.tgz\fR \fB\-e\fR \fI~/novo-pacote\fR \fB\-f\fR \fIgramps-pkg\fR 
-.TP 
-Importar três bancos de dados e iniciar a sessão interativa do Gramps com o resultado:
-\fBgramps\fR \fB\-i\fR \fIarquivo1.ged\fR \fB\-i\fR \fIarquivo2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR 
-.TP 
-Executar a ferramenta de verificação a partir da linha de comando e direcionar o resultado para stdout:
-\fBgramps\fR \fB\-O\fR \fI'Minha árvore genealógica'\fR \fB-a\fR \fItool\fR \fB-p\fR \fBname\fR=\fIverify\fR
-.TP 
-Finalmente, para iniciar uma sessão interativa normal, digite:
-\fBgramps\fR 
-
-.SH VARIÁVEIS DE AMBIENTE
-O programa verifica se estas variáveis de ambiente estão definidas:
-
-\fBLANG\fR - identifica o idioma a ser usado.
-Ex.: Para o idioma português do Brasil, a variável deve ser definida como pt_BR.UTF-8.
-
-\fBGRAMPSHOME\fR - se definida, força o Gramps a usar a pasta indicada para armazenar
-as configurações e os bancos de dados do programa. Por padrão, esta variável não é 
-definida e o Gramps assume que a pasta com todos os bancos de dados e configurações
-do perfil devem ser criadas na pasta do usuário (descrita na variável de ambiente 
-HOME no Linux ou USERPROFILE no Windows 2000/XP).
-
-.SH CONCEITOS
-Suporta um sistema de plugins baseado em Python, permitindo acrescentar importações 
-e exportações adicionais, geradores de relatórios, ferramentas e filtros de exibição, 
-sem modificação do programa principal.
-.LP 
-Além da impressão direta, é possível gerar relatórios em diversos formatos de
-arquivo, tais como \fIOpenOffice.org\fR, \fIAbiWord\fR, HTML ou LaTeX, para permitir
-aos usuários a modificação de acordo com suas necessidades.
-
-.SH LIMITAÇÕES E ERROS CONHECIDOS
-
-.SH ARQUIVOS
-.LP 
-\fI${PREFIX}/bin/gramps\fP 
-.br 
-\fI${PREFIX}/share/gramps\fP
-.br 
-\fI${HOME}/.gramps\fP 
-
-.SH AUTORES
-Donald Allingham \fI<don@gramps-project.org>\fR
-.br 
-\fIhttp://gramps.sourceforge.net\fR
-.LP 
-Este manual foi originalmente escrito por:
-.br 
-Brandon L. Griffith \fI<brandon@debian.org>\fR
-.br
-para inclusão na distribuição Debian GNU/Linux.
-.LP 
-Este manual é atualmente mantido pelo:
-.br 
-Projeto Gramps \fI<xxx@gramps-project.org>\fR
-.br 
-
-.SH DOCUMENTAÇÃO
-A documentação para usuários está disponível através da opção de ajuda padrão
-do GNOME, na forma de Manual do Gramps. O Manual também está disponível no 
-formato XML como \fBgramps-manual.xml\fR em \fIdoc/gramps-manual/$LANG\fR 
-nas fontes oficiais da sua distribuição.
-.LP 
-A documentação para desenvolvedores pode ser encontrada na página 
-\fIhttp://developers.gramps-project.org\fR. 
-
-.SH TRADUÇÃO
-\&\fR\&\f(CWAndré Marcelo Alvarenga <andrealvarenga@gmx.net> em 05/08/2012\fR

data/man/pt_BR/pt_BR.rst

@@ -1,293 +0,0 @@
-Portuguese (Brazil)
-===================
-
-gramps(1)                4.0.0               gramps(1)
-
-
-**NOME**
-
-        gramps - Programa para pesquisa genealógica.
-
-
-**RESUMO**
-
-        gramps [-?|--help] [--usage] [--version] [-l] [-u|--force-unlock]
-        [-O|--open= BANCODEDADOS [-f|--format= FORMATO]] [-i|--import= ARQUIVO 
-        [-f|--format= FORMATO]] [-i|--import= ...] [-e|--export= ARQUIVO 
-        [-f|--format= FORMATO]] [-a|--action= AÇÃO] [-p|--options= OPÇÕES]] 
-        [ ARQUIVO ] [--version]
-
-
-**DESCRIÇÃO**
-
-        Gramps é um programa de genealogia livre e de código aberto. 
-        Ele é escrito em Python e usa a interface GTK+/GNOME. 
-        Gramps deve parecer familiar a qualquer pessoa que já tenha usado 
-        outro programa de genealogia, tais como o Family Tree Maker (TM), 
-        Personal Ancestral Files (TM), ou o GNU Geneweb. Ele suporta a 
-        importação do formato GEDCOM, que é amplamente usado por quase 
-        todos os outros programas de genealogia.
-
-
-**OPÇÕES**
-
-       **gramps** *ARQUIVO*
-        Quando *ARQUIVO* for indicado (sem qualquer outra opção) como um 
-        nome de árvore genealógica ou como pasta do banco de dados, 
-        ela será aberta e iniciada uma sessão interativa. Se *ARQUIVO* for 
-        um formato compreendido pelo Gramps, será criada uma árvore 
-        genealógica vazia com o nome baseado no ARQUIVO e os dados são 
-        importados para ela. As demais opções serão ignoradas. Esta 
-        forma de execução é apropriada para usar o Gramps como manipulador 
-        de dados genealógicos em, por exemplo, navegadores Web. Este método 
-        aceita qualquer formato de dados nativo do Gramps, conforme abaixo. 
-
-
-       **-f** , **--format=** *FORMATO*
-        Indica expressamente o formato do *ARQUIVO*, precedente das opções 
-        -i ou -e. Se a opção -f não for fornecida para um ARQUIVO, o 
-        formato será identificado de acordo com a sua extensão ou tipo MIME. 
-
-        Os formatos disponíveis para exportação são gramps-xml (se o ARQUIVO 
-        terminar com .gramps), gedcom (se o ARQUIVO terminar com .ged) ou 
-        qualquer outro formato de arquivo disponível através do sistema de 
-        plugins do Gramps. 
-
-
-        Os formatos disponíveis para importação são grdb, gramps-xml, gedcom, 
-        gramps-pkg (se o ARQUIVO terminar com .gpkg), e geneweb 
-        (se o ARQUIVO terminar com .gw). 
-
-
-        Os formatos disponíveis para exportação são gramps-xml, gedcom, 
-        gramps-pkg, wft (se o ARQUIVO terminar com .wft), geneweb.
-
-       **-l**
-        Exibe uma lista com as árvores genealógicas conhecidas.
-
-
-       **-u** , **--force-unlock**
-        Desbloqueia um banco de dados previamente bloqueado.
-
-
-       **-O** , **--open=** *BANCODEDADOS*
-        Abre o *BANCODEDADOS* , que deve ser uma pasta de banco de dados 
-        ou um nome de árvore genealógica existentes. Se não forem indicadas 
-        opções de ação, importação ou exportação na linha de comando, 
-        será iniciada uma sessão interativa usando este banco de dados.
-
-
-       **-i** , **--import=** *ARQUIVO*
-        Importa os dados do ARQUIVO. Se não for indicado um banco de dados, 
-        o Gramps usará um arquivo temporário, que será excluído ao sair 
-        do programa. 
-
-
-        Quando mais de um arquivo de origem for indicado, cada um deles 
-        deve ser precedido da opção -i. Os arquivos são importados na ordem 
-        indicada, por exemplo, -i ARQUIVO1 -i ARQUIVO2 e -i ARQUIVO2 -i 
-        ARQUIVO1 poderá produzir diferentes gramps IDs no banco de dados 
-        resultante.
-
-
-       **-a** , **--action=** *AÇÃO*
-        Executa a *AÇÃO* nos dados importados. Isto será executado após a 
-        conclusão de todas as importações. Até o momento, as ações 
-        disponíveis são summary (o mesmo que Relatórios->Exibir->Resumo), 
-        check (o mesmo que Ferramentas->Processamento do banco de dados->
-        Verificar e reparar), report (gera o relatório), e tool (executa 
-        uma ferramenta de plugin). Para o report e tool é necessário 
-        fornecer OPÇÕES (com uso da opção -p). 
-
-
-        As OPÇÕES devem satisfazer as seguintes condições: 
-        Não podem conter espaços. Se alguns argumentos precisam incluir 
-        espaços, a string deve ser colocada entre aspas, ou seja, seguir 
-        a sintaxe do shell. String de opção é uma lista de pares com o 
-        nome e o valor (separados por sinal de igual). Os pares de nome 
-        e valor devem ser separados por vírgula. 
-
-
-        Muitas opções são específicas de cada relatório ou ferramenta. 
-        Entretanto, algumas opções são comuns.
-
-        **name=nome** 
-        Esta opção obrigatória determina qual relatório ou ferramenta 
-        será executado. Se o nome fornecido não corresponder a um 
-        relatório ou ferramenta, será exibida uma mensagem de erro 
-        seguida de uma lista de relatórios e ferramentas disponíveis 
-        dependendo da AÇÃO).
-
-        **show=all**
-        Isto irá gerar uma lista com os nomes para todas as opções 
-        disponíveis de um determinado relatório ou ferramenta.
-
-        **show=nome_opção**
-        Isto irá exibir a descrição da funcionalidade indicada por nome_opção, 
-        bem como quais são os tipos aceitáveis e os valores para esta opção.
-
-
-        Use as opções acima para descobrir tudo sobre um determinado relatório.
-
-        Quando mais de uma ação de saída for indicada, cada uma deve ser 
-        precedida da opção -a. As ações são realizadas uma a uma, na ordem 
-        indicada.
-
-       **-d** , **--debug=** *ARQUIVO_REGISTRO*
-        Ativa os registros para desenvolvimento e testes. Veja o código-fonte 
-        para mais detalhes.
-        
-       **--version**
-        Exibe o número da versão do Gramps e finaliza.
- 
-**Operação**
-        Se o primeiro argumento da linha de comando não começar com um 
-        traço (isto é, sem uma opção), o Gramps tentará abrir o arquivo 
-        com o nome fornecido pelo primeiro argumento e iniciar a sessão 
-        interativa, ignorando o resto dos argumentos da linha de comando.
-
-
-        Se for fornecida a opção -O, então o Gramps tentará abrir o banco 
-        de dados indicado e trabalhar com estes dados, de acordo com as 
-        instruções dos parâmetros adicionais da linha de comando.
-
-
-        Com ou sem a opção -O, pode haver múltiplas importações, exportações 
-        e ações indicadas pela linha de comando usando as opções -i, -e e -a.
-
-
-        A ordem das opções -i, -e ou -a não importa. A ordem utilizada 
-        será sempre esta: todas as importações (se existirem) -> todas 
-        as ações (se existirem) -> todas as exportações (se existirem). 
-        Mas a abertura deve estar sempre em primeiro lugar!
-
-
-        Se as opções -O ou -i não forem fornecidas, o Gramps será aberto 
-        com a sua janela principal e iniciará a sessão interativa padrão 
-        com um banco de dados vazio, uma vez que não há nada a processar.
-
-
-        Se as opções -e ou -a não forem fornecidas, o Gramps será aberto 
-        com a sua janela principal e iniciará a sessão interativa padrão 
-        com um banco de dados resultante de todas as importações. Este 
-        banco de dados está localizado no arquivo import_db.grdb da 
-        pasta ~/.gramps/import.
-
-
-        Os erros encontrados durante a importação, exportação ou ação, 
-        serão direcionados para stdout (se forem exceções tratadas pelo 
-        Gramps) ou para stderr (se não forem tratadas). Use redirecionamentos 
-        usuais de stdout e stderr do shell para salvar mensagens e erros 
-        em arquivos.
-
-
-
-**EXEMPLOS**
-
-        Abrir uma árvore genealógica existente e importar um arquivo xml para 
-        ela:
-        
-           gramps -O 'Minha árvore genealógica' -i ~/db3.gramps
-
-        Fazer as mesmas alterações da árvore genealógica do comando anterior, 
-        mas importar a árvore genealógica temporária e iniciar uma sessão 
-        interativa:
-        
-           gramps -i 'Minha árvore genealógica' -i ~/db3.gramps
-
-        Importar quatro bancos de dados (cujos formatos podem ser 
-        reconhecidos pelos nomes) e verificar a existência de erros no 
-        banco de dados resultante:
-        
-           gramps -i arquivo1.ged -i arquivo2.tgz -i ~/db3.gramps -i 
-           arquivo4.wft -a check
-
-        Indicar de forma explícita os formatos do exemplo acima, atribuindo 
-        os nomes dos arquivos com as opções -f apropriadas:
-        
-           gramps -i arquivo1.ged -f gedcom -i arquivo2.tgz -f gramps-pkg 
-           -i ~/db3.gramps -f gramps-xml -i arquivo4.wft -f wft -a check
-
-        Gravar o banco de dados resultante de todas as importações, 
-        indicando a opção -e (use -f se o nome do arquivo não permirtir 
-        que o gramps reconheça o formato automaticamente):
-        
-           gramps -i arquivo1.ged -i arquivo2.tgz -e ~/novo-pacote -f gramps-pkg
-
-        Importar três bancos de dados e iniciar a sessão interativa do 
-        Gramps com o resultado:
-        
-           gramps -i arquivo1.ged -i arquivo2.tgz -i ~/db3.gramps
-
-        Executar a ferramenta de verificação a partir da linha de 
-        comando e direcionar o resultado para stdout:
-        
-           gramps -O 'Minha árvore genealógica' -a tool -p name=verify
-
-        Finalmente, para iniciar uma sessão interativa normal, digite:
-        
-           gramps
- 
-**VARIÁVEIS DE AMBIENTE**
-
-        O programa verifica se estas variáveis de ambiente estão definidas:
-        **LANG** - identifica o idioma a ser usado. Ex.: Para o idioma português do Brasil, a variável deve ser definida como pt_BR.UTF-8.
-
-        **GRAMPSHOME** - se definida, força o Gramps a usar a pasta indicada para armazenar as configurações e os bancos de dados do programa. Por padrão, esta variável não é definida e o Gramps assume que a pasta com todos os bancos de dados e configurações do perfil devem ser criadas na pasta do usuário (descrita na variável de ambiente HOME no Linux ou USERPROFILE no Windows 2000/XP).
-
-
-
-**CONCEITOS**
-
-        Suporta um sistema de plugins baseado em Python, permitindo acrescentar 
-        importações e exportações adicionais, geradores de relatórios, 
-        ferramentas e filtros de exibição, sem modificação do programa principal.
-
-        Além da impressão direta, é possível gerar relatórios em diversos 
-        formatos de arquivo, tais como OpenOffice.org, AbiWord, HTML ou 
-        LaTeX, para permitir aos usuários a modificação de acordo com 
-        suas necessidades.
-
-
-
-**LIMITAÇÕES E ERROS CONHECIDOS**
-
-*ARQUIVOS**
-
-       *${PREFIX}/bin/gramps*
-       
-       *${PREFIX}/lib/python/dist-packages/gramps/*
-       
-       *${PREFIX}/share/*
-       
-       *${HOME}/.gramps*
-
-
-*AUTORES*
-
-       Donald Allingham <don@gramps-project.org> 
-       http://gramps.sourceforge.net
-       Este manual foi originalmente escrito por: 
-       Brandon L. Griffith <brandon@debian.org> 
-       para inclusão na distribuição Debian GNU/Linux.
-
-       Este manual é atualmente mantido pelo: 
-       Projeto Gramps <xxx@gramps-project.org> 
- 
-
-**DOCUMENTAÇÃO**
-
-        A documentação para usuários está disponível através da 
-        opção de ajuda.
-
-        A documentação para desenvolvedores pode ser encontrada na 
-        página http://developers.gramps-project.org.
-
-
-
-**TRADUÇÃO**
-
-André Marcelo Alvarenga <andrealvarenga@gmx.net> em 05/08/2012
-
-January 2013                 4.0.0               gramps(1)
-

data/man/sv/conf.py

@@ -1,243 +0,0 @@
-# -*- 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 = 'sv'
-
-# General information about the project.
-project = u'Gramps'
-copyright = u'2012, 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.0'
-# The full version, including alpha/beta/rc tags.
-release = '4.0.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 = [
-    ('sv', '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/sv/gramps.1.in

@@ -1,316 +0,0 @@
-.TH Gramps 1 "@VERSION@" "Januari 2008" "@VERSION@"
-.SH NAMN
-Gramps \- Genealogical Research and Analysis Management Programming System.
-
-.SH SAMMANFATTNING
-.B Gramps
-.RB [ \-?|\-\^\-help ]
-.RB [ \-\^\-usage ]
-.RB [ \-\^\-version ]
-.RB [ \-l ] 
-.RB [ \-u|\-\^\-force-unlock ]
-.RB [ \-O|\-\^\-open=
-.IR DATABAS 
-.RB [ \-f|\-\^\-format= 
-.IR FORMAT ]] 
-.RB [ \-i|\-\^\-import=
-.IR FIL 
-.RB [ \-f|\-\^\-format= 
-.IR FORMAT ]] 
-.RB [ \-i|\-\^\-import= 
-.IR ... ] 
-.RB [ \-e|\-\^\-export= 
-.IR FIL
-.RB [ \-f|\-\^\-format= 
-.IR FORMAT ]] 
-.RB [ \-a|\-\^\-action= 
-.IR ÅTGÄRD ]
-.RB [ \-p|\-\^\-options= 
-.IR ALTERNATIVSTRÄNG ]] 
-.RB [
-.IR FIL
-.RB ]
-.if 0 .RB [ bonobo\ options ]
-.if 0 .RB [ sound\ options ]
-.RB [ \-\-version ]
-
-.SH BESKRIVNING
-.PP 
-\fIGramps\fP är ett Free/OpenSource släktforskningsprogram. Det är skrivet i Python, 
-med hjälp av GTK+/GNOME gränssnittet.
-Gramps bör kännas bekant för de flesta, som har använt andra släktforskningsprogram 
-tidigare, som \fIFamily Tree Maker (TM)\fR, \fIPersonal Ancestral Files (TM)\fR, 
-\fIDISGEN\fR eller GNU Geneweb.
-Det stöder import via det populära GEDCOM-formatet, som används över 
-hela världen av nästan all släktforskningsprogramvara.
-
-.SH ALTERNATIV
-.TP 
-.BI Gramps " FIL" 
-När \fIFIL\fR ges (utan några flaggor) som namn på ett familjeträd eller som
-en mapp med familjeträd, så öppnas detta och en interaktiv session startas.
-Om FIL är en fil, vars format förstås av Gramps, skapas ett tomt famljeträd, 
-vars namn är grundat på namnet \fIFIL\fP och vars data importeras till det. 
-Resterande alternativ ignoreras. Detta sätt att starta passar vid användning av Gramps
-som en hanterare för släktforskningsdata i t. ex. en web-läsare.
-Detta startsätt accepterar alla inbyggda dataformat för Gramps, se nedan.
-.br
-
-.TP 
-.BI \-f,\-\^\-format= " FORMAT"
-Uttryckligen specificera format på \fIFIL\fR givet av föregående 
-.ig
-\fB\-O\fR,
-..
-\fB\-i\fR eller 
-\fB\-e\fR-alternativ. Om \fB\-f\fR-alternativet inte ges för någon \fIFIL\fR, 
-gissas filformat för den filen utgående från dess filändelse eller dess MIME-typ. 
-.br
-
-De format, som är tillgängliga för utmatnig, är \fBGramps\-xml\fR (gissas om \fIFIL\fR slutar på 
-\fB.Gramps\fR), \fBgedcom\fR (gissas om \fIFIL\fR slutar med \fB.ged\fR) eller
-någon filexport, som är tillgänglig via Gramps tilläggsprogramsystem.
-.br
-
-De format, som är tillgängliga för inmatnig, är \fBgrdb\fR, \fBGramps\-xml\fR, \fBgedcom\fR, 
-\fBGramps\-pkg\fR (gissas om \fIFIL\fR slutar med \fB.gpkg\fR) och
-\fBgeneweb\fR (gissas om \fIFIL\fR slutar med \fB.gw\fR). 
-.br
-
-De format, som är tillgängliga för export är 
-.ig
-\fBgrdb\fR,
-..
-\fBGramps\-xml\fR, \fBgedcom\fR,
-\fBGramps\-pkg\fR, \fBwft\fR (gissas om \fIFIL\fR slutar med \fB.wft\fR),
-\fBgeneweb\fR och \fBiso\fR (gissas aldrig, specificeras alltid med
-\fB\-f\fR-alternativ).
-
-.TP 
-.BI \-l
-Listar alla databaser/familjeträd.
-
-.TP 
-.BI \-u,\-\^\-force-unlock
-Tvingar upplåsning av databas.
-
-.TP 
-.BI \-O,\-\^\-open= " DATABAS"
-Öppnar \fIDATABAS\fR, som måste vara en befitlig databasmapp eller ett befintligt familjeträd.
-Om ingen åtgärd, import eller export-alternativ anges på kommandoraden så startas en interaktiv 
-session med den angivna databasen.
-
-.TP 
-.BI \-i,\-\^\-import= " FIL"
-Importera data från \fIFIL\fR. Om du inte har specificerat en databas, skapas en temporär sådan, 
-som tas bort när Gramps avslutas.
-.br
-
-Om mer är en indatafil anges, måste varje föregås av en \fB\-i\fR-flagga. 
-Filerna importeras i den givna ordningen, 
-t.ex. \fB\-i\fR \fIFIL1\fR \fB\-i\fR \fIFIL2\fR 
-och \fB\-i\fR \fIFIL2\fR \fB\-i\fR \fIFIL1\fR kan skapa skilda 
-Gramps IDs i den resulterande databasen. 
-
-.TP 
-.BI \-e,\-\^\-export= " FIL"
-Exporterar data till \fIFIL\fR. För \fBiso\fR-format, är \fIFIL\fR i själva verket namnet på den mapp, 
-som Gramps databas kommer att skrivas till. 
-För
-.ig
-\fBgrdb\fR,
-..
-\fBGramps\-xml\fR, \fBgedcom\fR, \fBwft\fR, \fBGramps\-pkg\fR 
-och \fBgeneweb\fR, är \fIFIL\fR namnet på resultatfilen. 
-.br
-
-Om mer är en utdatafil anges, måste varje föregås av en \fB\-e\fR-flagga. 
-Filerna skrivs en efter en i den givna ordningen.
-
-.TP 
-.BI \-a,\-\^\-action= " ÅTGÄRD"
-Utför \fIÅTGÄRD\fR på importerade data. Detta görs efter att all import 
-har avslutats felfritt. F. n. är följand åtgärder möjliga \fBsummary\fR 
-(samma som Rapporter->Visa->Sammanfattning av databasen), \fBcheck\fR (samma som Verktyg->Reparera databas 
-->Kontrollera och reparera) samt \fBreport\fR (skapar report, kräver en 
- \fIALTERNATIVSTRÄNG\fR lämnad via \fB\-p\fR-flaggan). 
-.br
-
-\fIALTERNATIVSTRÄNG\fR-en måste uppfylla följand villkor:
-.br
-Får ej innehålla några mellanslag. 
-Om några argument behöver inbegripa mellanslag, måste strängen omslutas av 
-anföringstecken.
-Alternativsträngen är en lista med par av namn och värden (åtskiljda av likhetstecken).
-Namn och värde måste åtskiljas med komma. 
-.br
-
-De flesta rapportalternativ är unika för varje rapport eller verktyg. Emellertid finns 
-det gemensamm alternativ.
-
-.BI "name=rapportnamn"
-.br
-Detta är obligatoriskt och bestämmer vilken rapport som skall skapas. 
-Om det givna \fInamn\fR inte motsvarar någon möjlig rapport eller verktyg, kommer ett 
-felmeddelande att skrivas ut, följt av möjliga namn på rapporter eller verktyg.
-
-.BI "show=all"
-.br
-Detta ger en lista med namn på alla möjliga alternativ för en bestämd rapport eller verktyg.
-
-.BI "show=optionname"
-.br
-Detta skriver ut beskrivningen av den funktion, som \fBoptionname\fR innebär, likväl vad som 
-är godkända typer och värden för detta alternativ.
-
-.br
-Använd alternativen ovan för att ta reda på all om en viss rapport.
-
-.LP
-Om mer än en utdataåtgärd givits måste varje föregås av en \fB\-a\fR-flagga. 
-Åtgärderna utförs en och en i den givna turordningen.
-
-.TP 
-.BI \-d,\-\^\-debug= " LOGGER_NAME"
-Kopplar på avlusningshjälpmedel för utveckling och tester. 
-För detaljer hänvisas till källkoder
-.TP
-.BI \-\^\-version
-Skriver ur Gramps versionsnummer och avslutar
-\" 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.
-.TP
-.BI \-\^\-disable-sound
-Disable sound server usage
-.TP
-.BI \-\^\-enable-sound
-Enable sound server usage
-.TP
-.BI \-\^\-espeaker= " HOSTNAME:PORT"
-Host:port on which the sound server to use is running
-\}
-
-.SH "Operation"
-.br
-Om första argumentet på kommandoraden inte inledds med ett minustecken (d. v. s. ingen flagga), 
-kommer Gramps att försöka öppna den fil, vars namn givits av det första argumentet samt påbörja 
-en interaktiv session utan att ta hänsyn till resten av argumenten på kommandoraden.
-
-.LP
-Om \fB\-O\fR-flagga givits, kommer Gramps att försöka öppna den omnämnda databasen 
-och sedan arbeta med dess data, enligt ytterligare instruktioner på kommandoraden.
-
-.LP
-Med eller utan \fB\-O\fRflagga, kan det ske många importeringar,
-exporteringar och åtgärder beskrivna ytterligare på kommanodraden 
-genom att använda \fB\-i\fR-,
-\fB\-e\fR- samt \fB\-a\fR-flaggor. 
-
-.LP
-Ordningen på \fB\-i\fR-, \fB\-e\fR- eller \fB\-a\fR-alternativen spelar ingen roll. 
-Den gällande ordningen är alltid: all import (om någon) -> alla åtgärder (om några)
--> all export (om någon). Men öppning måste alltid ske först!
-
-.LP
-Om inget \fB\-O\fR- eller \fB\-i\fR-alternativ givits, kommer Gramps att starta sitt 
-huvudfönster samt påbörja den vanliga interaktiva sessionen med en tom databas,
-då hur som helst inget data finns att bearbeta.
-
-.LP
-Om inget \fB\-e\fR- eller \fB\-a\fR-alternativ givits, kommer Gramps att starta sitt 
-huvudfönster samt påbörja den vanliga interaktiva sessionen med den databas, som blev 
-resultet från all import. Denna databas återfinns i \fBimport_db.grdb\fR
-under \fB~/.Gramps/import\fR-mappen.
-
-.LP
-De fel som inträffar under import, export eller vid åtgärder kommer antingen att skrivas till 
-\fIstdout\fR (om dessa avbrott hanteras av Gramps) eller 
-till \fIstderr\fR (om dessa inte hanteras). Använd vanliga skalkommandon för att styra om 
-\fIstdout\fR och \fIstderr\fR till att spara medelanden och fel i filer. 
-
-.SH EXAMPEL
-.TP 
-För att öppna ett befintligt familjeträd och importera en xml-fil till det, kan man skriva: 
-\fBGramps\fR \fB\-O\fR \fI'Mitt familjeträd'\fR \fB\-i\fR \fI~/db3.Gramps\fR
-.TP 
-Ovanstående ändrar det öppnade familjeträdet, för att göra samma sak, men importera bägge till ett tillfälligt familjeträd och påbörja en interaktiv session, kan man skriva:
-\fBGramps\fR \fB\-i\fR \fI'My Family Tree'\fR \fB\-i\fR \fI~/db3.Gramps\fR
-.TP 
-För att importera fyra databaser (vars format kan avgöras av deras namn) och sedan felkontrollera den resulterande  databasen, kan man skriva: 
-\fBGramps\fR \fB\-i\fR \fIFIL1.ged\fR \fB\-i\fR \fIFIL2.tgz\fR \fB\-i\fR \fI~/db3.Gramps\fR \fB\-i\fR \fIFIL4.wft\fR \fB\-a\fR \fIcheck\fR 
-.TP 
-För att uttryckligen specificera formaten i examplet ovan, lägg till filnamn med passande \fB\-f\fR-alternativ: 
-\fBGramps\fR \fB\-i\fR \fIFIL1.ged\fR \fB\-f\fR \fIgedcom\fR \fB\-i\fR \fIFIL2.tgz\fR \fB\-f\fR \fIGramps-pkg\fR \fB\-i\fR \fI~/db3.Gramps\fR \fB\-f\fR \fIGramps-xml\fR \fB\-i\fR \fIFIL4.wft\fR \fB\-f\fR \fIwft\fR \fB\-a\fR \fIcheck\fR 
-.TP 
-För att spara den databas, som är resultat av all import, ange \fB\-e\fR-flagga (använd \fB\-f\fR om filnamnet inte tillåter Gramps att gissa dess format):
-\fBGramps\fR \fB\-i\fR \fIFIL1.ged\fR \fB\-i\fR \fIFIL2.tgz\fR \fB\-e\fR \fI~/new-package\fR \fB\-f\fR \fIGramps-pkg\fR 
-.TP 
-För att importera tre databaser och påbörja en interaklive Gramps-session med importresultatet: 
-\fBGramps\fR \fB\-i\fR \fIFIL1.ged\fR \fB\-i\fR \fIFIL2.tgz\fR \fB\-i\fR \fI~/db3.Gramps\fR 
-.TP 
-För att köra verifieringsverktyget från kommandoraden och mata ut resultatet till stdout: 
-\fBGramps\fR \fB\-O\fR \fIfile.grdb\fR \fB-a\fR \fItool\fR \fB-p\fR \fBname\fR=\fIverify\fR
-.TP 
-Slutligen, för att påbörja en normal interaktiv session skriv bara: 
-\fBGramps\fR 
-
-.SH BEGREPP
-Stöder ett python\-baserat system för tilläggsprogram, som möjliggör att import- och export-funktioner, 
-rapportgeneratorer, verktyg samt visningsfilter, kan komplettera Gramps utan ändringar i huvudprogrammet.
-.LP 
-Förutom att skapa utskrift på skrivare direkt, kan rapportgeneratorer ha andra målsystem som \fIOpenOffice.org\fR, \fIAbiWord\fR, HTML eller LaTeX så att användaren kan tillåtas att ändra format för att passa behoven. 
-
-.SH KÄNDA FEL OCH BEGRÄNSNINGAR
-
-.SH FILER
-.LP 
-\fI${PREFIX}/bin/gramps\fP 
-.br 
-\fI${PREFIX}/share/gramps\fP
-.br 
-\fI${HOME}/.gramps\fP 
-
-.SH FÖRFATTARE
-Donald Allingham \fI<don@gramps-project.org>\fR
-.br 
-\fIhttp://gramps.sourceforge.net\fR
-.LP 
-Denna man-sida skrevs ursprungligen av:
-.br 
-Brandon L. Griffith \fI<brandon@debian.org>\fR
-.br
-till att ingå i Debians GNU/Linux-system.
-.LP 
-Denna man-sida underhålls f. n. av:
-.br 
-Alex Roitman \fI<shura@gramps-project.org>\fR
-.LP
-Denna man-sida har översatts till svenska av:
-.br 
-Peter Landgren \fI<peter.talken@telia.com>\fR
-.br 
-
-.SH DOCUMENTATION
-Användardokumentationen är tillgänglig genom GNOME's standard hjälp-bläddrare 
-i form av Gramps-handboken. Handboken finns även i XML-format
-som \fBgramps-manual.xml\fR under \fIdoc/gramps-manual/$LANG\fR i den officiella
-källdistributionen. Dock ej på svenska. 
-.LP 
-Utvecklingsdokumentationen kan hittas på
-\fIhttp://developers.gramps-project.org\fR. 

data/man/sv/sv.rst

@@ -1,281 +0,0 @@
-Swedish
-=======
-
-Gramps(1)			     3.4.0			     Gramps(1)
-
-
-
-**NAMN**
-       Gramps - Genealogical Research and Analysis Management Programming Sys‐
-       tem.
-
-
-**SAMMANFATTNING**
-       Gramps  [-?|--help]  [--usage]  [--version]  [-l]   [-u|--force-unlock]
-       [-O|--open= DATABAS [-f|--format= FORMAT]] [-i|--import= FIL [-f|--for‐
-       mat= FORMAT]] [-i|--import= ...]  [-e|--export= FIL [-f|--format=  FOR‐
-       MAT]]  [-a|--action=  ÅTGÄRD] [-p|--options= ALTERNATIVSTRÄNG]] [ FIL ]
-       [--version]
-
-
-**BESKRIVNING**
-       Gramps är ett Free/OpenSource släktforskningsprogram. Det är skrivet  i
-       Python, med hjälp av GTK+/GNOME gränssnittet.  Gramps bör kännas bekant
-       för de flesta, som har använt  andra  släktforskningsprogram  tidigare,
-       som Family Tree Maker (TM), Personal Ancestral Files (TM), DISGEN eller
-       GNU Geneweb.  Det stöder import via det populära  GEDCOM-formatet,  som
-       används över hela världen av nästan all släktforskningsprogramvara.
-
-
-**ALTERNATIV**
-       **Gramps** *FIL*
-	      När *FIL* ges  (utan  några flaggor) som namn på ett familjeträd
-	      eller som en mapp med familjeträd, så öppnas detta och en inter‐
-	      aktiv session startas.  Om FIL är en fil, vars format förstås av
-	      Gramps, skapas ett tomt famljeträd, vars namn är grundat på nam‐
-	      net  FIL och vars data importeras till det.  Resterande alterna‐
-	      tiv ignoreras. Detta sätt att starta passar  vid	användning  av
-	      Gramps som en hanterare för släktforskningsdata i t. ex. en web-
-	      läsare.  Detta startsätt accepterar alla inbyggda dataformat för
-	      Gramps, se nedan.
-
-
-       **-f** , **--format=** *FORMAT*
-	      Uttryckligen  specificera  format  på FIL givet av föregående -i
-	      eller -e-alternativ. Om -f-alternativet inte ges för någon  FIL,
-	      gissas  filformat  för  den  filen utgående från dess filändelse
-	      eller dess MIME-typ.
-
-	      De format, som är tillgängliga för utmatnig, är Gramps-xml (gis‐
-	      sas  om FIL slutar på .Gramps), gedcom (gissas om FIL slutar med
-	      .ged) eller någon  filexport,  som  är  tillgänglig  via	Gramps
-	      tilläggsprogramsystem.
-
-	      De   format,   som   är  tillgängliga  för  inmatnig,  är  grdb,
-	      Gramps-xml, gedcom, Gramps-pkg (gissas om FIL slutar med	.gpkg)
-	      och geneweb (gissas om FIL slutar med .gw).
-
-	      De format, som är tillgängliga för export är Gramps-xml, gedcom,
-	      Gramps-pkg, wft (gissas om FIL slutar med .wft), geneweb och iso
-	      (gissas aldrig, specificeras alltid med -f-alternativ).
-
-
-       **-l**     
-          Listar alla databaser/familjeträd.
-
-
-       **-u** , **--force-unlock**
-	      Tvingar upplåsning av databas.
-
-
-       **-O** , **--open=** *DATABAS*
-	      Öppnar *DATABAS* , som måste vara en befitlig databasmapp eller ett
-	      befintligt familjeträd.  Om ingen åtgärd, import	eller  export-
-	      alternativ  anges på kommandoraden så startas en interaktiv ses‐
-	      sion med den angivna databasen.
-
-
-       **-i** , **--import=** *FIL*
-	      Importera data från FIL. Om du inte har specificerat en databas,
-	      skapas en temporär sådan, som tas bort när Gramps avslutas.
-
-	      Om  mer  är  en  indatafil  anges, måste varje föregås av en -i-
-	      flagga.  Filerna importeras i den givna ordningen, t.ex. -i FIL1
-	      -i  FIL2	och  -i FIL2 -i FIL1 kan skapa skilda Gramps IDs i den
-	      resulterande databasen.
-
-
-       **-e** , **--export=** *FIL*
-	      Exporterar data till *FIL* . För iso-format, är *FIL* i själva verket
-	      namnet  på den mapp, som Gramps databas kommer att skrivas till.
-	      För Gramps-xml, gedcom, wft, Gramps-pkg och geneweb, är *FIL* nam‐
-	      net på resultatfilen.
-
-	      Om  mer  är  en  utdatafil  anges, måste varje föregås av en -e-
-	      flagga.  Filerna skrivs en efter en i den givna ordningen.
-
-
-       **-a** , **--action=** *ÅTGÄRD*
-	      Utför ÅTGÄRD på importerade  data.  Detta  görs  efter  att  all
-	      import har avslutats felfritt. F. n. är följand åtgärder möjliga
-	      summary	(samma	  som	 Rapporter->Visa->Sammanfattning    av
-	      databasen) ,  check  (samma  som Verktyg->Reparera databas ->Kon‐
-	      trollera och reparera) samt report ( skapar report, kräver
-	      en *ALTERNATIVSTRÄNG* lämnad via **-p** flaggan ) .
-
-	      *ALTERNATIVSTRÄNG* -en måste uppfylla följand villkor:
-	      Får ej innehålla några mellanslag.  Om  några  argument  behöver
-	      inbegripa  mellanslag,  måste  strängen  omslutas  av  anföring‐
-	      stecken.	Alternativsträngen är en lista med  par  av  namn  och
-	      värden  (åtskiljda  av  likhetstecken).	Namn  och  värde måste
-	      åtskiljas med komma.
-
-	      De flesta rapportalternativ är unika  för  varje	rapport  eller
-	      verktyg. Emellertid finns det gemensamm alternativ.
-
-	      **name=rapportnamn**
-	      Detta  är  obligatoriskt	och bestämmer vilken rapport som skall
-	      skapas.  Om det givna namn inte motsvarar någon  möjlig  rapport
-	      eller verktyg, kommer ett felmeddelande att skrivas ut, följt av
-	      möjliga namn på rapporter eller verktyg.
-
-	      **show=all**
-	      Detta ger en lista med namn på alla möjliga  alternativ  för  en
-	      bestämd rapport eller verktyg.
-
-	      **show=optionname**
-	      Detta  skriver  ut beskrivningen av den funktion, som optionname
-	      innebär, likväl vad som är godkända typer och värden  för  detta
-	      alternativ.
-
-	      Använd  alternativen ovan för att ta reda på all om en viss rap‐
-	      port.
-
-
-       Om mer än en utdataåtgärd givits måste varje föregås av	en  -a-flagga.
-       Åtgärderna utförs en och en i den givna turordningen.
-
-
-       **-d** , **--debug=** *LOGGER_NAME*
-	      Kopplar  på avlusningshjälpmedel för utveckling och tester.  För
-	      detaljer hänvisas till källkoder
-
-       **--version**
-	      Skriver ur Gramps versionsnummer och avslutar
-
-
-**Operation**
-       Om första argumentet på kommandoraden inte inledds med ett  minustecken
-       (d.  v. s. ingen flagga), kommer Gramps att försöka öppna den fil, vars
-       namn givits av det första argumentet samt påbörja en interaktiv session
-       utan att ta hänsyn till resten av argumenten på kommandoraden.
-
-
-       Om  -O-flagga  givits,  kommer  Gramps  att  försöka öppna den omnämnda
-       databasen och sedan arbeta med dess data, enligt  ytterligare  instruk‐
-       tioner på kommandoraden.
-
-
-       Med eller utan -Oflagga, kan det ske många importeringar, exporteringar
-       och åtgärder beskrivna ytterligare på kommanodraden genom  att  använda
-       -i-, -e- samt -a-flaggor.
-
-
-       Ordningen  på  -i-,  -e-  eller -a-alternativen spelar ingen roll.  Den
-       gällande ordningen är alltid: all import (om någon)  ->	alla  åtgärder
-       (om  några)  ->	all  export  (om  någon). Men öppning måste alltid ske
-       först!
-
-
-       Om inget -O- eller -i-alternativ givits, kommer Gramps att starta  sitt
-       huvudfönster  samt påbörja den vanliga interaktiva sessionen med en tom
-       databas, då hur som helst inget data finns att bearbeta.
-
-
-       Om inget -e- eller -a-alternativ givits, kommer Gramps att starta  sitt
-       huvudfönster  samt  påbörja  den  vanliga interaktiva sessionen med den
-       databas, som blev resultet från all import. Denna databas  återfinns  i
-       import_db.grdb under ~/.Gramps/import-mappen.
-
-
-       De  fel	som  inträffar	under import, export eller vid åtgärder kommer
-       antingen att skrivas till stdout (om dessa avbrott hanteras av  Gramps)
-       eller  till stderr (om dessa inte hanteras). Använd vanliga skalkomman‐
-       don för att styra om stdout och stderr till att	spara  medelanden  och
-       fel i filer.
-
-
-**EXAMPEL**
-       För  att öppna ett befintligt familjeträd och importera en xml-fil till
-       det, kan man skriva:
-       
-	      Gramps -O 'Mitt familjeträd' -i ~/db3.Gramps
-
-       Ovanstående ändrar det öppnade familjeträdet, för att göra  samma  sak,
-       men  importera  bägge  till  ett tillfälligt familjeträd och påbörja en
-       interaktiv session, kan man skriva:
-       
-	      Gramps -i 'My Family Tree' -i ~/db3.Gramps
-
-       För att importera fyra databaser (vars  format  kan  avgöras  av  deras
-       namn)  och  sedan  felkontrollera  den resulterande  databasen, kan man
-       skriva:
-       
-	      Gramps -i FIL1.ged -i FIL2.tgz -i ~/db3.Gramps  -i  FIL4.wft  -a
-	      check
-
-       För  att  uttryckligen  specificera formaten i examplet ovan, lägg till
-       filnamn med passande -f-alternativ:
-       
-	      Gramps -i FIL1.ged  -f  gedcom  -i  FIL2.tgz  -f	Gramps-pkg  -i
-	      ~/db3.Gramps -f Gramps-xml -i FIL4.wft -f wft -a check
-
-       För  att  spara	den  databas,  som är resultat av all import, ange -e-
-       flagga (använd -f om filnamnet inte tillåter Gramps att gissa dess for‐
-       mat):
-       
-	      Gramps -i FIL1.ged -i FIL2.tgz -e ~/new-package -f Gramps-pkg
-
-       För  att importera tre databaser och påbörja en interaklive Gramps-ses‐
-       sion med importresultatet:
-       
-	      Gramps -i FIL1.ged -i FIL2.tgz -i ~/db3.Gramps
-
-       För att köra  verifieringsverktyget  från  kommandoraden  och  mata  ut
-       resultatet till stdout:
-       
-	      Gramps -O file.grdb -a tool -p name=verify
-
-       Slutligen, för att påbörja en normal interaktiv session skriv bara:
-       
-	      Gramps
-
-
-**BEGREPP**
-       Stöder ett python-baserat system för tilläggsprogram, som möjliggör att
-       import- och export-funktioner, rapportgeneratorer,  verktyg  samt  vis‐
-       ningsfilter, kan komplettera Gramps utan ändringar i huvudprogrammet.
-
-       Förutom	att  skapa utskrift på skrivare direkt, kan rapportgeneratorer
-       ha andra målsystem som OpenOffice.org, AbiWord, HTML eller LaTeX så att
-       användaren kan tillåtas att ändra format för att passa behoven.
-
-
-**KÄNDA FEL OCH BEGRÄNSNINGAR**
-**FILER**
-
-       *${PREFIX}/bin/gramps*
-       
-       *${PREFIX}/lib/python/dist-packages/gramps/*
-       
-       *${PREFIX}/share/*
-       
-       *${HOME}/.gramps*
-
-
-**FÖRFATTARE**
-       Donald Allingham <don@gramps-project.org>
-       http://gramps-project.org/
-
-       Denna man-sida skrevs ursprungligen av:
-       Brandon L. Griffith <brandon@debian.org>
-       till att ingå i Debians GNU/Linux-system.
-
-       Denna man-sida underhålls f. n. av:
-       Alex Roitman <shura@gramps-project.org>
-
-       Denna man-sida har översatts till svenska av:
-       Peter Landgren <peter.talken@telia.com>
-
-
-**DOCUMENTATION**
-       Användardokumentationen	är  tillgänglig  genom GNOME's standard hjälp-
-       bläddrare i form av Gramps-handboken. Handboken finns även i XML-format
-       som  gramps-manual.xml  under  doc/gramps-manual/$LANG i den officiella
-       källdistributionen. Dock ej på svenska.
-
-       Utvecklingsdokumentationen kan hittas på
-       http://www.gramps-project.org/wiki/index.php?title=Portal:Developers 
-
-
-Januari 2013			     4.0.0			     Gramps(1)

data/man/update_man.py

@@ -1,183 +0,0 @@
-#! /usr/bin/env python
-#
-# update_po - a gramps tool to update translations
-#
-# Copyright (C) 2006-2006  Kees Bakker
-# Copyright (C) 2006       Brian Matherly
-# Copyright (C) 2008       Stephen George
-# Copyright (C) 2012
-#
-# 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., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
-
-"""
-update_man.py for command line documentation.
-
-Examples: 
-   python update_man.py -t
-
-      Tests if 'sphinx' and 'python' are well configured.
-"""
-
-from __future__ import print_function
-
-import os
-import sys
-from argparse import ArgumentParser
-
-DOCUTILS = True
-try:
-    import docutils.core, docutils.writers
-except:
-    DOCUTILS = False
-
-LANGUAGES = ['sv', 'nl', 'pl', 'cs', 'pt_BR', 'fr']
-VERSION = '4.0.0'
-DATE = ''
-
-# You can set these variables from the command line.
-SPHINXBUILD   = 'sphinx-build'
-
-if sys.platform == 'win32':          
-    pythonCmd = os.path.join(sys.prefix, 'bin', 'python.exe')
-    sphinxCmd = os.path.join(sys.prefix, 'bin', 'sphinx-build.exe')
-elif sys.platform in ['linux2', 'darwin', 'cygwin']:
-    pythonCmd = os.path.join(sys.prefix, 'bin', 'python')
-    sphinxCmd = SPHINXBUILD
-else:
-    print ("Update Man ERROR: unknown system, don't know sphinx, ... commands")
-    sys.exit(0)
-
-def tests():
-    """
-    Testing installed programs.
-    We made tests (-t flag) by displaying versions of tools if properly
-    installed. Cannot run all commands without 'sphinx' and 'python'.
-    """
-    try:
-        print("\n=================='python'=============================\n")
-        os.system('''%(program)s -V''' % {'program': pythonCmd})
-    except:
-        print ('Please, install python')
-        
-    try:
-        print("\n=================='Shpinx-build'=============================\n")
-        os.system('''%(program)s''' % {'program': sphinxCmd})
-    except:
-        print ('Please, install sphinx')
-        
-    if not DOCUTILS:
-        print('\nNo docutils support, cannot use -m/--man and -o/--odt arguments.')
-
-def main():
-    """
-    The utility for handling documentation stuff.
-    What is need by Gramps, nothing more.
-    """
-    
-    parser = ArgumentParser( 
-                         description='This program aims to handle documentation' 
-                                      ' and realted translated versions.', 
-                         )
-                         
-    parser.add_argument("-t", "--test",
-            action="store_true", dest="test",  default=True,
-            help="test if 'python' and 'sphinx' are properly installed")
-    
-    parser.add_argument("-b", "--build",
-            action="store_true", dest="build",  default=False,
-            help="build man documentation (via sphinx-build)")
-    
-    parser.add_argument("-m", "--man",
-            action="store_true", dest="man",  default=False,
-            help="build man documentation (via docutils)")
-    
-    parser.add_argument("-o", "--odt",
-            action="store_true", dest="odt",  default=False,
-            help="build odt documentation (via docutils)")
-                             
-    args = parser.parse_args()
-    
-    if args.test:
-        tests()
-        
-    if args.build:
-        build()
-        
-    if args.man and DOCUTILS:
-        man()
-        
-    if args.odt and DOCUTILS:
-        odt()
-        
-def build():
-    """
-    Build documentation.
-    """
-    
-    # testing stage
-    
-    os.system('''%(program)s -b html . _build/html''' % {'program': sphinxCmd})
-    os.system('''%(program)s -b htmlhelp . _build/htmlhelp''' % {'program': sphinxCmd})
-    if DOCUTILS:
-        os.system('''%(program)s -b man . .''' % {'program': sphinxCmd})
-    os.system('''%(program)s -b text . _build/text''' % {'program': sphinxCmd})
-    os.system('''%(program)s -b changes . _build/changes''' % {'program': sphinxCmd})
-    #os.system('''%(program)s -b linkcheck . _build/linkcheck''' % {'program': sphinxCmd})
-    os.system('''%(program)s -b gettext . _build/gettext''' % {'program': sphinxCmd})
-    
-    for lang in LANGUAGES:
-        os.system('''%(program)s -b html -D language="%(lang)s" master_doc="%(lang)s" %(lang)s %(lang)s''' 
-                   % {'lang': lang, 'program': sphinxCmd})
-        os.system('''%(program)s -b htmlhelp -D language="%(lang)s" master_doc="%(lang)s" %(lang)s %(lang)s''' 
-                   % {'lang': lang, 'program': sphinxCmd})
-        if DOCUTILS:
-            os.system('''%(program)s -b man %(lang)s %(lang)s''' 
-                       % {'lang': lang, 'program': sphinxCmd})
-        os.system('''%(program)s -b text -D language="%(lang)s" master_doc="%(lang)s" %(lang)s %(lang)s''' 
-                   % {'lang': lang, 'program': sphinxCmd})
-        # for update/migration
-        os.system('''%(program)s -b gettext -D language="%(lang)s" master_doc="%(lang)s" . _build/gettext/%(lang)s''' 
-                   % {'lang': lang, 'program': sphinxCmd})
-                   
-def man():
-    """
-    man file generation via docutils (python)
-    
-    from docutils.core import publish_cmdline, default_description
-    from docutils.writers import manpage
-    """
-    
-    os.system('''rst2man en.rst gramps.1''') 
-    
-    for lang in LANGUAGES:
-        os.system('''rst2man %(lang)s/%(lang)s.rst -l %(lang)s %(lang)s/gramps.1''' 
-                   % {'lang': lang})
-                   
-def odt():
-    """
-    odt file generation via docutils (python)
-    
-    from docutils.core import publish_cmdline_to_binary, default_description
-    from docutils.writers.odf_odt import Writer, Reader
-    """
-    
-    os.system('''rst2odt en.rst gramps.odt''') 
-    
-    for lang in LANGUAGES:
-        os.system('''rst2odt %(lang)s/%(lang)s.rst -l %(lang)s %(lang)s/gramps.odt''' 
-                   % {'lang': lang})
-    
-if __name__ == "__main__":
-	main()

data/templates/404.html

@@ -1,12 +0,0 @@
-{% extends "admin/base_site.html" %}
-{% load i18n %}
-
-{% block title %}{% trans 'Page not found' %}{% endblock %}
-
-{% block content %}
-
-<h2>{% trans 'Page not found' %}</h2>
-
-<p>{% trans "We're sorry, but the requested page could not be found." %}</p>
-
-{% endblock %}

data/templates/500.html

@@ -1,12 +0,0 @@
-{% extends "admin/base_site.html" %}
-{% load i18n %}
-
-{% block breadcrumbs %}<div class="breadcrumbs"><a href="/">{% trans "Home" %}</a> &rsaquo; {% trans "Server error" %}</div>{% endblock %}
-
-{% block title %}{% trans 'Server error (500)' %}{% endblock %}
-
-{% block content %}
-<h1>{% trans 'Server Error <em>(500)</em>' %}</h1>
-<p>{% trans "There's been an error. It's been reported to the site administrators via e-mail and should be fixed shortly. Thanks for your patience." %}</p>
-
-{% endblock %}

data/templates/admin/base_site.html

@@ -1,22 +0,0 @@
-{% extends "admin/base.html" %}
-{% load i18n %}
-
-{% block title %}{{ title }} | My New Title{% endblock %}
-
-{% block branding %}
-<h1 id="site-name">My new title for the Admin site!</h1>
-{% endblock %}
-
-{% block nav-global %}
-    {% if user.is_staff %}
-    <style type="text/css">
-        .ml {margin:0 10px 10px;display:block;float:left}
-    </style>
-
-    <a href="/" clas="ml">Website home</a>  
-    <a href="/admin/" class="ml">Admin home</a>
-    <a href="/admin/members/invoice/" class="ml">Invoices</a>
-    <a href="/admin/auth/user/?is_active__exact=0" class="ml">New Users</a>
-    <a href="/admin/auth/user/" class="ml">All Users</a>
-    {% endif %}
-{% endblock %}

data/templates/browse_page.html

@@ -1,30 +0,0 @@
-{% extends "gramps-base.html" %}
-{% load my_tags %}
-
-{% block title %}{{sitename}}{% endblock %}
-{% block heading %}{{sitename}}{% endblock %}
-
-{% block content %} 
-
-<p> &nbsp; </p>
-
-<p id="description">
-Database information:</p>
-
-<table class="infolist surname">
-<tr>
-<th>Item</th>
-<th>Count</th>
-</tr>
-{% for view in views %}
-   <tr class="{% cycle odd,even %}">
-       {% if view.2 %}
-          <td align="left"><a href="/{{view.1}}">{{view.0}}</a></td> 
-          <td align="left"><a href="/{{view.1}}">{{view.1|table_count}}</td>
-       {% endif %}
-   </tr>
-{% endfor %}
-</table>
-
-{% endblock %}
-

data/templates/detail_breadcrumb.html

@@ -1,12 +0,0 @@
-{% load my_tags %}
-{% filter breadcrumb %}
-  {% format "/browse|Browse" %}||
-  {% format "/%s/%s|%s" view args tviews %}
-  {% if object.gramps_id %}
-  || {% format "/%s/%s|%s [%s]" view object.handle tview object.gramps_id %}
-  {% else %}
-    {% if object.name %}
-  || {% format "/%s/%s|%s [%s]" view object.handle tview object.name %}
-    {% endif %}
-  {% endif %}
-{% endfilter %}

data/templates/gramps-base.html

@@ -1,399 +0,0 @@
-{% load my_tags %}
-<!DOCTYPE html>
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
-<head>
-    <title>{% block title %}{{sitename}}{% endblock %}</title>
-    {% block meta %}
-    <meta http-equiv="content-type" content="text/html;charset=UTF-8" />
-    <meta http-equiv="Content-Style-Type" content="text/css" />
-    <meta name="generator" content="Gramps 3.2.0-0.SVN12859M http://gramps-project.org/" />
-    <meta name="author" content="" />
-    {% endblock %}
-    <link href="/images/ped24.ico" type="image/x-icon" rel="shortcut icon" />
-    {% block css %}
-    <link media="screen" href="/styles/css/{{css_theme}}" type="text/css" rel="stylesheet" />
-    <link media="print" href="/styles/css/Web_Print-Default.css" type="text/css" rel="stylesheet" />
-    <script type="text/javascript" src="/styles/javascript/jquery-1.3.2.min.js"></script>
-    <script type="text/javascript" src="/styles/javascript/jquery-ui-1.7.2.custom.min.js"></script>
-    <script type="text/javascript" src="/styles/jhtmlarea/scripts/jHtmlArea-0.7.0.js"></script>	 
-    <link rel="Stylesheet" type="text/css" href="/styles/jhtmlarea/style/jHtmlArea.css" />
-    <script type="text/javascript" src="/styles/javascript/jquery.flexbox.min.js"></script>
-    <link type="text/css" rel="stylesheet" href="/styles/css/jquery.flexbox.css" />  
-    {% endblock %}
-
-   <style type="text/css">
-     table td {
-        vertical-align: middle;
-     }
-     div.content {
-        background: none;
-     }
-     .content {
-        padding: 0px 0px 10px;
-     }
-     .browsecell {
-        display: block;
-     }
-     #subtitle {
-        font-weight: bold;
-        font-style: italic;
-        border-top: 1px solid;
-     }
-     td.ColumnAttribute {
-        text-align: right;
-     }
-     #error {
-        color: red;
-     }
-   {% if action == "edit" or action == "add" %}
-   {% else %}
-     #rowspace {
-        height: 3px;
-     }
-     #data {
-        border: 1px solid;
-        background-color: white;
-        color: brown;
-     }
-   {% endif %}
-   
-   /* Component containers */
-     .ui-widget {
-         font-family: Georgia,serif;
-         font-size: small; 
-         }
-     .ui-widget input, .ui-widget select, .ui-widget textarea, .ui-widget button {
-          font-family: Georgia,serif;
-          font-size: small; 
-         }
-     .ui-widget-content { 
-         border: 1px solid #7D5925; 
-         color: #7D5925; 
-         float: left;
-         width: 98%;
-         }
-     .ui-widget-content a {
-          color: #7D5925; 
-          }
-     .ui-widget-header { 
-         color: #ffffff; 
-         }
-     .ui-widget-header a {
-          color: #7D5925;
-          }
-
-     /* Overlays */
-     .ui-widget-overlay {
-         background: #aaaaaa;
-         opacity: .30;
-         }
-         
-     .ui-widget-shadow { 
-         margin: -8px 0 0 -8px;
-         padding: 8px;
-         opacity: .30;
-         -webkit-border-radius: 8px; 
-         }
-
-     /* Interaction states */
-     .ui-state-default { 
-         border: 1px solid #7D5925; 
-         background: #FFF2C6; 
-         font-weight: normal; 
-         color: #7D5925; 
-         outline: none; 
-         }
-     .ui-state-default a, .ui-state-default a:link, .ui-state-default a:visited { 
-         color: #7D5925;
-         text-decoration: none;
-         outline: none; 
-         }
-     .ui-state-hover, .ui-state-focus { 
-         border: 1px solid #f5ad66;
-         background: #f5f0e5;
-         font-weight: normal;
-         color: #a46313;
-         outline: none; 
-         }
-     .ui-state-hover a, .ui-state-hover a:hover { 
-         color: #a46313;
-         text-decoration: none;
-         outline: none; 
-         }
-     .ui-state-active { 
-         border: 1px solid #7D5925;
-         background: #f4f0ec;
-         font-weight: normal;
-         color: #b85700;
-         outline: none; 
-         }
-     .ui-state-active a, .ui-state-active a:link, .ui-state-active a:visited { 
-         color: #b85700;
-         outline: none;
-         text-decoration: none; 
-         }
-
-     /* Interaction Cues */
-     .ui-state-highlight {
-         border: 1px solid #d9bb73;
-         background: #f5f5b5;
-         color: #060200; 
-         }
-     .ui-state-highlight a { 
-         color: #060200; 
-         }
-     .ui-state-error {
-         border: 1px solid #f8893f;
-         background: #fee4bd;
-         color: #dd4e2c; 
-         }
-     .ui-state-error a { 
-         color: #dd4e2c; 
-         }
-     .ui-state-error-text {
-          color: #dd4e2c; 
-          }
-     .ui-state-disabled {
-         opacity: .35;
-         background-image: none;
-         }
-     .ui-priority-primary {
-         font-weight: bold; 
-         }
-     .ui-priority-secondary {
-         opacity: .7;
-         font-weight: normal; 
-         }
-
-     /* Tabs */
-     .ui-tabs {
-         padding: .2em;
-         }
-     .ui-tabs .ui-tabs-nav {
-         list-style: none;
-         position: relative;
-         padding: .2em .2em 0; 
-         }
-     .ui-tabs .ui-tabs-nav li {
-         position: relative;
-         float: left;
-         margin: .2em .2em -1px 0;
-         padding: 0; 
-         }
-     .ui-tabs .ui-tabs-nav li a {
-         float: left;
-         text-decoration: none;
-         padding: .5em 1em; 
-         }
-     .ui-tabs .ui-tabs-nav li.ui-tabs-selected {
-         padding-bottom: 1px;
-         border-bottom-width: 0;
-         }
-     .ui-tabs .ui-tabs-nav li.ui-tabs-selected a, .ui-tabs .ui-tabs-nav li.ui-state-disabled a, .ui-tabs .ui-tabs-nav li.ui-state-processing a {
-         cursor: text; 
-         }
-     .ui-tabs .ui-tabs-nav li a, .ui-tabs.ui-tabs-collapsible .ui-tabs-nav li.ui-tabs-selected a {
-         cursor: pointer; 
-         } /* first selector in group seems obsolete, but required to overcome bug in Opera applying cursor: text overall if defined elsewhere... */
-     .ui-tabs .ui-tabs-panel {
-         padding: 1em 1.4em;
-         display: block;
-         border-width: 0;
-         background: none; 
-         }
-     .ui-tabs .ui-tabs-hide {
-         display: none !important; 
-         }
-    </style>
-
-<SCRIPT LANGUAGE="JavaScript">
-<!--
-var  timerId=0 ;
-
-function clearTimer() {
-  if (timerId!=0) {
-    clearTimeout(timerId); timerId=0; }}
-
-function startTimer() {
-  clearTimer(); timerId=setTimeout('timerId=0;hideMenus()',200); 
-}
-
-function showMenu(menuNum) {
-  clearTimer(); hideMenus();
-  document.getElementById('menu_'+menuNum).style.display=""; 
-}
-
-function hideMenus() {
-  document.getElementById('menu_browse').style.display="none";
-}
-
-function hiLite(theOption) {
-  clearTimer();
-  document.getElementById('opt_'+theOption).style.background='#9090FF'; 
-}
-
-function unLite(theOption) {
-  startTimer();
-  document.getElementById('opt_'+theOption).style.background='#D0D0FF'; 
-}
-
-function optClick(theOption) {
-  document.location.href=theOption;
-}
-
-function setHasData(classname, value) {
-    var elems = document.getElementsByTagName('*'), i;
-    for (i in elems) {
-        if((" " + elems[i].className + " ").indexOf(" " + classname + " ") > -1) {
-            if (value) {
-                elems[i].style.fontWeight = "bold"; 
-                elems[i].style.fontStyle = "italic"; 
-	    } else {
-                elems[i].style.fontWeight = ""; 
-                elems[i].style.fontStyle = ""; 
-            }
-	 }
-    }
-}   
-
-function setReturnValues() {
-    var elems = document.getElementsByTagName('*'), i;
-    for (i in elems) {
-        if ((" " + elems[i].name + " ").indexOf("_return ") > -1) {
-	    var pos = (" " + elems[i].name + " ").indexOf("_return ");
-            var s = elems[i].name.substring(0, pos - 1);
-	    var v = document.getElementsByName(s)[0];
-	    elems[i].value = v.value;
-	}
-    }
-}
-
-function buttonOver(button) {
-    button.style.backgroundColor = "white"; 
-    button.style.border = "1px solid gray";
-}
-
-function buttonOut(button) {
-    button.style.backgroundColor = "lightgray"; 
-    button.style.border = "1px solid lightgray";
-}
-//-->
-</SCRIPT>
-
-<STYLE TYPE="text/css">
-<!--
-.popupMenu {
-//  font-family     : Verdana,Tahoma,Helvetica,sans-serif;
-//  font-size       :     12px;
-  color           :  #111111;
-  position        : absolute;
-//  top             :     72px;
-  border          :      1px;
-  padding         :      3px;
-  z-index         :       16;
-  background-color:  #D0D0FF;
-  cursor          :  pointer; }
--->
-</STYLE>
-</head>
-<body onclick="hideMenus()" 
-      onload="if (document.getElementById('get_focus')) {document.getElementById('get_focus').focus();}"
->
-   <div id="header" style="padding-top: 1em; background-position:0px -32px;">
-     <h1 id="SiteTitle" style="margin-left: 0em;">{% block heading %}{{sitename}}{% endblock %}</h1>
-   </div>
-
-   <div class="wrapper" role="navigation" id="nav">
-    {% block navigation %}
-    <div class="container">
-    <ul class="menu" id="dropmenu">
-    <li {{ tview|currentSection:"home" }}><a href="/">Home</a></li>
-    {% for title in menu %}
-         {# (<Nice name>, /<path>/, <Model> | None, Need authentication ) #}
-         {% if title.3 %} 
-	   {% if user.is_authenticated %}
-                <li {{tview|currentSection:title.1 }}>
-	        {% if title.1 %}
-                   <a href="/{{title.1}}/">{{title.0}}</a>
-		</li>
-	        {% else %}
-                   <a href="/">{{title.0}}</a>
-                </li>
-	        {% endif %}
-	   {% else %}
-                {# don't show #}
-           {% endif %}
-        {% else %}
-                <li {{tview|currentSection:title.1 }}>
-	        {% if title.1 %}
-                   <a href="/{{title.1}}/"
-		      onmouseover="showMenu('{{title.1}}')" 
-		      onmouseout="startTimer()" 
-		      style="cursor:pointer"  
-		      href="/browse/">{{title.0}}</a>
-<DIV CLASS="popupMenu" ID="menu_browse" STYLE="display:none;">
-  <TABLE BORDER="0" CELLSPACING="0" CELLPADDING="0">
-  <TR ID="opt_person"><TD><A ONMOUSEOVER="hiLite('person')" ONMOUSEOUT="unLite('person')" ONCLICK="optClick('/person/')">People</A></TD></TR>
-  <TR ID="opt_family"><TD><A ONMOUSEOVER="hiLite('family')" ONMOUSEOUT="unLite('family')" ONCLICK="optClick('/family/')">Families</A></TD></TR>
-  <TR ID="opt_event"><TD><A ONMOUSEOVER="hiLite('event')" ONMOUSEOUT="unLite('event')" ONCLICK="optClick('/event/')">Events</A></TD></TR>
-  <TR ID="opt_note"><TD><A ONMOUSEOVER="hiLite('note')" ONMOUSEOUT="unLite('note')" ONCLICK="optClick('/note/')">Note</A></TD></TR>
-  <TR ID="opt_media"><TD><A ONMOUSEOVER="hiLite('media')" ONMOUSEOUT="unLite('media')" ONCLICK="optClick('/media/')">Media</A></TD></TR>
-  <TR ID="opt_citation"><TD><A ONMOUSEOVER="hiLite('citation')" ONMOUSEOUT="unLite('citation')" ONCLICK="optClick('/citation/')">Citations</A></TD></TR>
-  <TR ID="opt_source"><TD><A ONMOUSEOVER="hiLite('source')" ONMOUSEOUT="unLite('source')" ONCLICK="optClick('/source/')">Sources</A></TD></TR>
-  <TR ID="opt_place"><TD><A ONMOUSEOVER="hiLite('place')" ONMOUSEOUT="unLite('place')" ONCLICK="optClick('/place/')">Places</A></TD></TR>
-  <TR ID="opt_repository"><TD><A ONMOUSEOVER="hiLite('repsoitory')" ONMOUSEOUT="unLite('repository')" ONCLICK="optClick('/repository/')">Repository</A></TD></TR>
-  <TR ID="opt_tag"><TD><A ONMOUSEOVER="hiLite('tag')" ONMOUSEOUT="unLite('tag')" ONCLICK="optClick('/tag/')">Tags</A></TD></TR>
-</TABLE>
-</DIV>
-                </li>
-	        {% else %}
-                   <a href="/">{{title.0}}</a></li>
-	        {% endif %}
-	{% endif %}
-    {% endfor %}
-    {% if user.is_authenticated %}
-	 {% if next %}
-         <li><a href="/logout/?next={{next}}">Logout</a></li>
-	 {% else %}
-         <li><a href="/logout">Logout</a></li>
-	 {% endif %}         
-       {% if user.is_superuser %}
-         <li><a href="/admin">Admin</a></li>
-       {% endif %}
-    {% else %}
-	 {% if next %}
-         <li><a href="/login/?next={{next}}">Login</a></li>
-         {% else %}
-         <li><a href="/login/">Login</a></li>
-	 {% endif %}
-  {% endif %}
-    </ul>
-    {% endblock %}
-    </div>
-   </div>
-    <div class="grampsweb">
-     {% for message in messages %}
-        <font color="red">{{message}}</font><br/>
-     {% endfor %}
-     {% if message %}
-        <div id="system_message" class="{{ message_type }}">
-           <font color="red">{{message}}</font><br/>
-        </div>
-    {% endif %}
-    {% block content %}
-    {% endblock %}
-   <div class="content">
-    </div>
-   </div>
-   <div id="footer">
-    {% block footer %}
-    <p id="createdate">
-      <a href="http://www.gramps-project.org/wiki/index.php?title=Gramps-Connect">Gramps-Connect, version {{gramps_version}}</a>.
-    </p>
-    <p id="copyright">&copy; 2009-2012 <a href="http://www.gramps-project.org/">www.gramps-project.org</a> 
-    </p>
-    {% endblock %}
-   </div>
-
-</body>
-</html>

data/templates/main_page.html

@@ -1,38 +0,0 @@
-{% extends "gramps-base.html" %}
-{% load my_tags %}
-
-{% block title %}{{sitename}}{% endblock %}
-{% block heading %}{{sitename}}{% endblock %}
-
-{% block content %} 
-
-<p> &nbsp; </p>
-
-<p id="description">Welcome to <b>{{sitename}}</b>, a new web-based collaboration tool.
-
-{% if user.is_authenticated %}
-  You are now logged in
-  as <a href="/user/{{user.username}}">{{user.username}}</a>.
-{% endif %}
-</p>
-
-<p id="description">
-Database information:</p>
-
-<table class="infolist surname">
-<tr>
-<th>Item</th>
-<th>Count</th>
-</tr>
-{% for view in views %}
-   <tr class="{% cycle odd,even %}">
-       {% if view.2 %}
-          <td align="left"><a href="/{{view.1}}">{{view.0}}</a></td> 
-          <td align="left"><a href="/{{view.1}}">{{view.1|table_count}}</td>
-       {% endif %}
-   </tr>
-{% endfor %}
-</table>
-
-{% endblock %}
-

data/templates/paginator.html

@@ -1,36 +0,0 @@
-<div class="pagination">
-    <span class="step-links">
-        <form method="post">{% csrf_token %}
-        <div id="alphanav" style="padding: 0pt 0 0pt 0;">
-        <ul>
-        {% ifequal page.number 1 %}
-        <li><input type="button" value="<<" disabled="disabled"></li>
-        {% else %}
-        <li><input type="button" value="<<" onclick="document.location.href='?page=1{{search_query}}'"></li>
-	{% endifequal %}
-        {% if page.has_previous %}
-            <li><input type="button" value="<" onclick="document.location.href='?page={{page.previous_page_number}}{{search_query}}'"></li>
-	{% else %}
-            <li><input type="button" value="<" disabled="disabled"></li>
-        {% endif %}
-
-        <span class="current">
-            <li>Page {{ page.number }} of {{ page.paginator.num_pages }}</li>
-        </span>
-
-        {% if page.has_next %}
-            <li><input type="button" value=">" onclick="document.location.href='?page={{page.next_page_number}}{{search_query}}'"></li>
-	{% else %}
-            <li><input type="button" value=">" disabled="disabled"></li>
-        {% endif %}
-        {% ifequal page.number page.paginator.num_pages %}
-        <li><input type="button" value=">>" disabled="disabled"></li>
-        {% else %}
-        <li><input type="button" value=">>" onclick="document.location.href='?page={{page.paginator.num_pages}}{{search_query}}'"></li>
-	{% endifequal %}
-	<b>Matches</b>: {{page.paginator.count}}/{{total}} <b>Showing</b>: {{results_this_page}}
-	</ul>
-        </div>
-    </span>
-</div>
-

data/templates/pick.html

@@ -1,51 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-   <script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-   });
-   </script>
-
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-
-<div id="summaryarea">
-<table class="infolist" style="width:90%;"> {% comment %} 4 cols {% endcomment %}
-<tbody>
-  {% if pickform.errors %}
-    <hr>
-    <p id="error">The following fields have errors. Please correct and try again.</p>
-    <div id="error">{{pickform.errors}}</div>
-    <hr>
-  {% endif %}
-<form method="post">{% csrf_token %}
-<tr>
-<td class="ColumnAttribute">Pick:</td>
-{% if user.is_authenticated %}
- <td class="ColumnValue" id="data">{{pickform.picklist}}</td>
-{% else %}
- <td class="ColumnValue" id="data"></td> 
-{% endif %}
-</tr>
-</tbody>
-</table>
-
-{% if user.is_superuser %}
-    {% make_button "Cancel" "/%s/%s" object_type object_handle args %}
-    <input type="hidden" name="action" value="save-share"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save"/>
-{% else %}
-{% endif %}
-</form>
-{% endblock %}
-

data/templates/reference.html

@@ -1,34 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-<h2>Temporary Reference Detail</h2>
-<div id="summaryarea">
-<table class="infolist" style="width:90%;"> 
-<trbody>
-  {% if form.errors %}
-    <hr>
-    <p id="error">The following fields have errors. Please correct and try again.</p>
-    <div id="error">{{form.errors}}</div>
-    <hr>
-  {% endif %}
-<form method="post">{% csrf_token %}
-
-{% for f in form.forms %}
-<tr>
-{{f}}
-</tr>
-{% endfor %}
-
-</table>
-</div>
-</div>
-</form>
-{% make_button "Go to reference" url %}
-{% make_button "Go back" referenced_by %}
-{% endblock %}
-

data/templates/registration/login.html

@@ -1,39 +0,0 @@
-{% extends "gramps-base.html" %}
-
-{% block title %}Gramps Connect - login {% endblock %}
-{% block heading %}Gramps - login {% endblock %}
-
-{% block content %}
-<h2>User Login</h2>
-{% if form.errors %}
-<p id="description">Your username or password were not valid. Please try again.</p>
-{% else %}
-<p id="description">Enter your login ID and password below. </p>
-{% endif %}
-<form method="post" action=".">{% csrf_token %}
- <table>
-   <tr>
-    <td>
-      <label for="id_username">Username: </label>
-    </td>
-    <td>
-      {{form.username}}
-    </td>
-   </tr>
-   <tr>
-    <td>
-      <label for="id_password">Password: </label>
-    </td>
-    <td>
-      {{form.password}}
-    </td>
-   </tr>
- </table>
-{% if next %}
- <input type="hidden" name="next" value="{{next}}" />
-{% else %}
- <input type="hidden" name="next" value="/" />
-{% endif %}
- <input type="submit" value="Login" />
-</form>
-{% endblock %}

data/templates/table_header.html

@@ -1,5 +0,0 @@
-{% for header in headers %}<th{{ header.class_attr }}>
-  {% if header.sortable %}<a href="{{ header.url|escape }}">{% endif %}
-  {{ header.text }}
-  {% if header.sortable %}</a>{% endif %}
-</th>{% endfor %}

data/templates/user_page.html

@@ -1,47 +0,0 @@
-{% extends "gramps-base.html" %}
-{% load my_tags %}
-
-{% block title %}{{sitename}} - user page {% endblock %}
-{% block heading %}{{sitename}} - user page {% endblock %}
-
-{% block content %} 
-
-<p id="description">Details for <b>{{user.first_name}} {{user.last_name}}</b> ({{user.username}}):</p>
-
-<p id="description">
-<table>
-<tr>
-  <td width="30%">User name: </td><td><em>{{user.username}}</em></td>
-</tr>
-<tr>
-  <td>Email:     </td><td><a href="mailto:{{user.email}}"><em>{{user.email}}</a></em></td>
-</tr>
-<tr>
-  <td>Type:      </td>
-<td>
-
-{% if user.is_superuser %}
-  <em>Administrator</em>
-{% else %}
-  <em>User</em>
-{% endif %}
-
-</td>
-</tr>
-<tr>
-   <td>Last login: </td><td><em>{{user.last_login}}</em></td>
-</tr>
-</table>
-
-{% if user.is_superuser %}
-  {% make_button "Edit Profile" "/admin/grampsdb/profile/%s" user.id %}
-  {% make_button "Edit User" "/admin/auth/user/%s" user.id %}
-{% else %}
-  <em>User</em>
-{% endif %}
-
-
-</p>
-
-{% endblock %}
-

data/templates/view_citation_detail.html

@@ -1,179 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-   <script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-     $('#shared-tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-   });
-   </script>
-
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-
-  {% if citationform.errors or sourceform.errors %}
-    <hr>
-    <p id="error">The following fields have errors. Please correct and try again.</p>
-    <div id="error">{{citationform.errors}}</div>
-    <div id="error">{{sourceform.errors}}</div>
-    <hr>
-  {% endif %}
-<form method="post">{% csrf_token %}
-
-<!-- Tabs -->
-<h2>Citation information</h2>
-
-<div class="ui-tabs ui-widget ui-widget-content ui-corner-all" id="tabs" style="border: none;">
-  <ul class="ui-tabs-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all">
-    <li class="ui-state-default ui-corner-top ui-tabs-selected ui-state-active"><a class="tab-general" href="#tab-general">General</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-notes" href="#tab-notes">Note</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-media" href="#tab-media">Media</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-data" href="#tab-data">Data</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-references" href="#tab-references">Reference</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-history" href="#tab-history">History</a></li>
-  </ul>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom" id="tab-general" style="background-color: #f4f0ec;"> 
-
-<table class="infolist" style="width:90%;">
-<tr>
-<td class="ColumnAttribute">{{citationform.text.label}}:</td>
-<td class="ColumnValue" id="data" colspan="3"> {% render citationform.text user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{citationform.gramps_id.label}}:</td>
-<td class="ColumnValue" id="data"> {% render citationform.gramps_id user action %}</td>
-<td class="ColumnAttribute">{{citationform.private.label}}:</td>
-<td class="ColumnValue" id="data"> {% render citationform.private user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{citationform.page.label}}:</td>
-<td class="ColumnValue" id="data" colspan="3"> {% render citationform.page user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{citationform.confidence.label}}:</td>
-<td class="ColumnValue" id="data" colspan="3"> {% render citationform.confidence user action %}</td>
-</tr>
-</table>
-
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-notes"  style="background-color: #f4f0ec;"> 
-    {% note_table citation user action "/note/$act/citation/%s" citation.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-media" style="background-color: #f4f0ec;"> 
-    {% media_table citation user action "/media/$act/citation/%s" citation.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-data" style="background-color: #f4f0ec;"> 
-    {% data_table citation user action "/data/$act/citation/%s" citation.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-references" style="background-color: #f4f0ec;"> 
-    {% citation_reference_table citation user action %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-history" style="background-color: #f4f0ec;"> 
-    {% history_table citation user action %}
-  </div>
-</div>
-
-  <p>Note: Any changes in the shared citation information will be reflected
-    in the citation itself, for all items that reference the citation.
-  </p>
-
-<hr>
-
-<h2>Source information (shared)</h2>
-<div class="ui-tabs ui-widget ui-widget-content ui-corner-all" id="shared-tabs" style="border: none;">
-  <ul class="ui-tabs-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all">
-    <li class="ui-state-default ui-corner-top ui-tabs-selected ui-state-active"><a class="tab-shared-general" href="#tab-shared-general">General</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-shared-notes" href="#tab-shared-notes">Notes</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-shared-media" href="#tab-shared-media">Media</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-shared-repositories" href="#tab-shared-repositories">Repositories</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-shared-references" href="#tab-shared-references">References</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-shared-history" href="#tab-shared-history">History</a></li>
-  </ul>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom" id="tab-shared-general" style="background-color: #f4f0ec;"> 
-
-<table class="infolist" style="width:90%;">
-<tr>
-<td class="ColumnAttribute">{{sourceform.title.label}}:</td>
-<td class="ColumnValue" id="data" colspan="3"> {% render sourceform.title user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{sourceform.author.label}}:</td>
-<td class="ColumnValue" id="data" colspan="3"> {% render sourceform.author user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{sourceform.gramps_id.label}}:</td>
-<td class="ColumnValue" id="data"> {% render sourceform.gramps_id user action %}</td>
-<td class="ColumnAttribute">{{sourceform.private.label}}:</td>
-<td class="ColumnValue" id="data"> {% render sourceform.private user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{sourceform.abbrev.label}}:</td>
-<td class="ColumnValue" id="data" colspan="3"> {% render sourceform.abbrev user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{sourceform.pubinfo.label}}:</td>
-<td class="ColumnValue" id="data" colspan="3"> {% render sourceform.pubinfo user action %}</td>
-</tr>
-</table>
-
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-shared-notes" style="background-color: #f4f0ec;"> 
-    {% note_table source user action "/note/$act/source/%s" source.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-shared-media" style="background-color: #f4f0ec;"> 
-    {% media_table source user action "/media/$act/source/%s" source.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-shared-repositories" style="background-color: #f4f0ec;"> 
-    {% repository_table source user action "/repository/$act/source/%s" source.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-shared-references" style="background-color: #f4f0ec;"> 
-    {% citation_reference_table source user action %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-shared-history" style="background-color: #f4f0ec;"> 
-    {% history_table source user action %}
-  </div>
-</div>
-
-  <p>Note: Any changes in the shared source information will be reflected
-    in the source itself, for all items that reference the source.
-  </p>
-
-<hr>
-
-{% if user.is_superuser %}
-  {% if action == "edit" %}
-    {% make_button "Cancel" "/citation/%s" citation.handle args %}
-    <input type="hidden" name="action" value="save"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save"/>
-  {% else %}
-    {% ifequal action "add" %}
-      {% make_button "Cancel" "/citation/" args %}
-      <input type="hidden" name="action" value="create"/>
-      <input type="hidden" name="search" value="{{search}}"/>
-      <input type="hidden" name="page" value="{{page}}"/>
-      <input type="submit" value="Create"/>
-    {% else %}
-      <div style="background-color: lightgray; padding: 2px 0px 0px 2px; clear: both;">
-      {% make_button "+Add Citation" "/citation/add" args %}
-      {% make_button "?Edit Citation" "/citation/%s/edit" citation.handle args %}
-      {% make_button "-Delete Citation" "/citation/%s/delete" citation.handle args %}
-      </div>
-    {% endifequal %}
-  {% endif %}
-{% else %}
-{% endif %}
-</form>
-{% endblock %}

data/templates/view_citations.html

@@ -1,48 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-
-<table cellspacing="0" class="infolist surname" width="90%">
-<thead>
-  <tr>
-    <th>#</th>
-    <th>ID</th>
-    <th>Title</th>
-    <th>Pub Info</th>
-    <th>Author</th>
-  </tr>
-</thead>
-<tbody>
-  {% for source in page.object_list %}
-  <tr class="{% cycle odd,even %}">
-    <td>{{ forloop.counter|row_count:page }}</td>
-    <td><a href="/{{view}}/{{source.handle|escape}}{{args}}" class="browsecell"
-        >
-           <span class="grampsid">[{{source.gramps_id}}]</span></a>
-    {% if user.is_authenticated or source.public %}
-    <td><a href="/{{view}}/{{source.handle|escape}}{{args}}" class="browsecell"
-        >{{source.title|escape|nbsp}}</a>
-    <td><a href="/{{view}}/{{source.handle|escape}}{{args}}" class="browsecell"
-        >{{source.pubinfo|nbsp}}</a>
-    <td><a href="/{{view}}/{{source.handle|escape}}{{args}}" class="browsecell"
-        >{{source.author|nbsp}}</a>
-    {% else %}
-      <td></td>
-      <td></td>
-      <td></td>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-
-{% block admin_functions %}
-{% if user.is_superuser %}
-   <div style="background-color: lightgray; padding: 2px 0px 0px 2px">
-   {% make_button "+Add Citation" "/citation/add" args %}
-   </div>
-{% endif %}
-{% endblock %}

data/templates/view_event_detail.html

@@ -1,135 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-   <script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-   });
-   </script>
-
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-
-<div id="summaryarea">
-<table class="infolist" style="width:90%;"> 
-<trbody>
-  {% if eventform.errors %}
-    <hr>
-    <p id="error">The following fields have errors. Please correct and try again.</p>
-    <div id="error">{{eventform.errors}}</div>
-    <hr>
-  {% endif %}
-<form method="post" onsubmit="setReturnValues()">{% csrf_token %}
-<tr>
-<td class="ColumnAttribute">{{eventform.event_type.label}}:</td>
-<td class="ColumnValue" id="data"> {% render eventform.event_type user action %}</td>
-<td class="ColumnAttribute">{{eventform.text.label}}:</td>
-<td class="ColumnValue" id="data">{% render eventform.text user action %}</td>
-<td></td>
-</tr>
-<tr>
-<td class="ColumnAttribute">Description:</td>
-<td  class="ColumnValue" id="data" colspan="3">{% render eventform.description user action %}</td>
-<td></td>
-</tr>
-<tr>
-<td class="ColumnAttribute">ID:</td>
-<td  class="ColumnValue" id="data" colspan="3">{% render eventform.gramps_id user action %}</td>
-<td></td>
-</tr>
-<tr>
-<td class="ColumnAttribute">Place:</td>
-<td  class="ColumnValue" id="data" colspan="3">
-{% if action != "view" %}
-   <script type="text/javascript">  
-        $(function() { 
-            $('#place').flexbox('/json/?field=place', {
-	        watermark: 'Place',
-	        width: 600,
-	        paging: {  
-                  pageSize: 10  
-	        },
-	        initialValue: '{{event.place.get_selection_string}}',
-  	        initialId: '{{event.place.handle}}'
-	        });
-        });  
-    // </script>
-    <div id="place"></div>  
-{% else %}
-    <a href="/place/?search={{event.place}}">{{event.place}}</a>
-{% endif %}
-</td>
-<td>
-<td  class="ColumnValue" id="data" colspan="3">{% render eventform.private user action %}
-</td>
-</tr>
-</table>
-</div>
-</div>
-<!-- Tabs -->
-
-<div class="ui-tabs ui-widget ui-widget-content ui-corner-all" id="tabs" style="border: none;">
-  <ul class="ui-tab-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all">
-    <li class="ui-state-default ui-corner-top ui-tab-selected ui-state-active"><a class="tab-sources" href="#tab-sources">Citation</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-notes" href="#tab-notes">Note</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-media" href="#tab-media">Media</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-attributes" href="#tab-attributes">Attribute</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-references" href="#tab-references">Reference</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-history" href="#tab-history">History</a></li>
-  </ul>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom" id="tab-sources" style="background-color: #f4f0ec;"> 
-    {% citation_table event user action "/citation/$act/event/%s" event.handle %}
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-notes" style="background-color: #f4f0ec;"> 
-    {% note_table event user action "/note/$act/event/%s" event.handle %}
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-media" style="background-color: #f4f0ec;"> 
-    {% media_table event user action "/media/$act/event/%s" event.handle %}
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-attributes" style="background-color: #f4f0ec;"> 
-    {% attribute_table event user action "/attribute/$act/event/%s" event.handle %}
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-references" style="background-color: #f4f0ec;"> 
-    {% event_reference_table event user action %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-history" style="background-color: #f4f0ec;"> 
-    {% history_table event user action %}
-  </div>
-</div>
-
-{% if user.is_superuser %}
-  {% if action == "edit" %}
-    {% make_button "Cancel" "/event/%s" event.handle args %}
-    <input type="hidden" id="place_return" name="place_return" value=""/>
-    <input type="hidden" name="action" value="save"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save"/>
-  {% else %}
-    {% ifequal action "add" %}
-      {% make_button "Cancel" "/event/" args %}
-      <input type="hidden" id="place_return" name="place_return" value=""/>
-      <input type="hidden" name="action" value="create"/>
-      <input type="hidden" name="search" value="{{search}}"/>
-      <input type="hidden" name="page" value="{{page}}"/>
-      <input type="submit" value="Create"/>
-    {% else %}
-      <div style="background-color: lightgray; padding: 2px 0px 0px 2px; clear: both;">
-      {% make_button "+Add Event" "/event/add" args %}
-      {% make_button "?Edit Event" "/event/%s/edit" event.handle args %}
-      {% make_button "-Delete Event" "/event/%s/delete" event.handle args %}
-      </div>
-    {% endifequal %}
-  {% endif %}
-{% else %}
-{% endif %}
-</form>
-{% endblock %}
-

data/templates/view_events.html

@@ -1,48 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-
-<table cellspacing="0" class="infolist surname" width="95%">
-<thead>
-  <tr>
-    <th>#</th>
-    <th>ID</th>
-    <th>Event Type</th>
-    <th>Description</th>
-    <th>Date</th>
-    <th>Place</th>
-  </tr>
-</thead>
-<tbody>
-  {% for event in page.object_list %}
-  <tr class="{% cycle odd,even %}">
-    <td>{{ forloop.counter|row_count:page }}</td>
-    <td><a href="/{{view}}/{{event.handle|escape}}{{args}}" class="noThumb browsecell">
-           <span class="grampsid">[{{event.gramps_id}}]</span></a>
-
-    {% if user.is_authenticated or event.public %}
-    <td><a href="/{{view}}/{{event.handle|escape}}{{args}}" class="browsecell">{{event.event_type|nbsp}}</a>
-    <td><a href="/{{view}}/{{event.handle|escape}}{{args}}" class="browsecell">{{event.description|nbsp}}</a>
-    <td><a href="/{{view}}/{{event.handle|escape}}{{args}}" class="browsecell">{{event|date_as_text:user}}</a>
-    <td><a href="/{{view}}/{{event.handle|escape}}{{args}}" class="browsecell">{{event.place.title|nbsp}}</a>
-    {% else %}
-      <td><a href="/{{view}}/{{event.handle|escape}}{{args}}" class="browsecell">[Private]</a>
-      <td><a href="/{{view}}/{{event.handle|escape}}{{args}}" class="browsecell">[Private]</a>
-      <td><a href="/{{view}}/{{event.handle|escape}}{{args}}" class="browsecell">[Private]</a>
-      <td><a href="/{{view}}/{{event.handle|escape}}{{args}}" class="browsecell">[Private]</a>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-
-{% block admin_functions %}
-{% if user.is_superuser %}
-   <div style="background-color: lightgray; padding: 2px 0px 0px 2px">
-   {% make_button "+Add Event" "/event/add" args %}
-   </div>
-{% endif %}
-{% endblock %}

data/templates/view_families.html

@@ -1,71 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-
-<table cellspacing="0" class="infolist surname" width="95%">
-<thead>
-  <tr>
-    <th>#</th>
-    <th>ID</th>
-    <th>Father</th>
-    <th>Mother</th>
-    <th>Relationship</th>
-  </tr>
-</thead>
-<tbody>
-  {% for family in page.object_list %}
-  <tr class="{% cycle odd,even %}">
-    <td><a href="/{{view}}/{{family.handle|escape}}{{args}}" class="browsecell"
-	{% if family.tags.all %}
-            style="color: {{family.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{ forloop.counter|row_count:page }}</a></td>
-    <td><a href="/{{view}}/{{family.handle|escape}}{{args}}" class="browsecell"
-	{% if family.tags.all %}
-            style="color: {{family.tags.all.0.color|format_color}};"
-	{% endif %}
-        ><span class="grampsid">[{{family.gramps_id}}]</span></a>
-    <td><a href="/{{view}}/{{family.handle|escape}}{{args}}" class="browsecell"
-	{% if family.tags.all %}
-            style="color: {{family.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{family.father|make_name:user|nbsp}}</a>
-    <td><a href="/{{view}}/{{family.handle|escape}}{{args}}" class="browsecell"
-	{% if family.tags.all %}
-            style="color: {{family.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{family.mother|make_name:user|nbsp}}</a>
-    {% if user.is_authenticated or family.public %}
-    <td><a href="/{{view}}/{{family.handle|escape}}{{args}}" class="browsecell"
-	{% if family.tags.all %}
-            style="color: {{family.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{family.family_rel_type|escape|nbsp}}</a>
-    {% else %}
-    <td><a href="/{{view}}/{{family.handle|escape}}{{args}}" class="browsecell"
-	{% if family.tags.all %}
-            style="color: {{family.tags.all.0.color|format_color}};"
-	{% endif %}
-        >
-	{% if not family.public %}
-           [Private]
-	{% else %}
-	   {{family.family_rel_type}}
-	{% endif %}
-        </a>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-
-{% block admin_functions %}
-{% if user.is_superuser %}
-   <div style="background-color: lightgray; padding: 2px 0px 0px 2px">
-   {% make_button "+Add Family" "/family/add" args %}
-   </div>
-{% endif %}
-{% endblock %}

data/templates/view_family_detail.html

@@ -1,204 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-   <script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-   });
-   </script>
-
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-
-<h2><a href="/person/{{family.father.handle}}">{{family.father|render_name:user}}</a> and <a href="/person/{{family.mother.handle}}">{{family.mother|render_name:user}}</a></h2>
-
-<div id="summaryarea">
-<table class="infolist" style="width:90%;"> {% comment %} 4 cols {% endcomment %}
-<tbody>
-  {% if familyform.errors %}
-    <hr>
-    <p id="error">The following fields have errors. Please correct and try again.</p>
-    <div id="error">{{familyform.errors}}</div>
-    <hr>
-  {% endif %}
-<form method="post" onsubmit="setReturnValues()">{% csrf_token %}
-<tr>
-<th colspan="2">Father</th>
-<th colspan="2">Mother</th>
-</tr>
-<tr>
- <td class="ColumnAttribute">Name:</td>
-{% if user.is_authenticated or father.probably_alive %}
- <td class="ColumnValue" id="data">
-{% if action != "view" %}
-    <script type="text/javascript">  
-        $(function() { 
-            $('#father').flexbox('/json/?field=father', {
-	        watermark: 'Father',
-	        width: 300,
-	        paging: {  
-                  pageSize: 10  
-	        },
-  	        initialValue: '{{family.father.get_selection_string}}',
-  	        initialId: '{{family.father.handle}}'
-	        });
-        });  
-    // </script>
-    <div id="father"></div>  
-{% else %}
- {{family.father|render_name:user}}
-{% endif %}
-</td>
-{% else %}
- {{family.father|render_name:user}}
-{% endif %}
- </td>
- <td class="ColumnAttribute">Name:</td>
-{% if user.is_authenticated or family.mother.probably_alive %}
- <td class="ColumnValue" id="data">
-{% if action != "view" %}
-   <script type="text/javascript">  
-        $(function() { 
-            $('#mother').flexbox('/json/?field=mother', {
-	        watermark: 'Mother',
-	        width: 300,
-	        paging: {  
-                  pageSize: 10  
-	        },
-	        initialValue: '{{family.mother.get_selection_string}}',
-  	        initialId: '{{family.mother.handle}}'
-	        });
-        });  
-    // </script>
-    <div id="mother"></div>  
-{% else %}
- {{family.mother|render_name:user}}
-{% endif %}
-{% else %}
- {{family.mother|render_name:user}}
-{% endif %}
-</td>
-</tr>
-{% if user.is_authenticated or not familyform.father.probably_alive %}
-<tr>
- <td class="ColumnAttribute">Birth:</td>
- <td class="ColumnValue" id="data">{{familyform.father.birth|date_as_text:user}}</td>
- <td class="ColumnAttribute">Birth:</td>
- <td class="ColumnValue" id="data">{{familyform.mother.birth|date_as_text:user}}</td>
-</tr>
-{% else %}
-<tr>
- <td class="ColumnAttribute">Death:</td>
- <td class="ColumnValue" id="data">{{familyform.father.death|date_as_text:user}}</td>
- <td class="ColumnAttribute">Death:</td>
- <td class="ColumnValue" id="data">{{familyform.mother.death|date_as_text:user}}</td>
-</tr>
-{% endif %}
-<tr>
- <td class="ColumnAttribute">Death:</td>
- <td class="ColumnValue" id="data">{{familyform.father.death|date_as_text:user}}</td>
- <td class="ColumnAttribute">Death:</td>
- <td class="ColumnValue" id="data">{{familyform.mother.death|date_as_text:user}}</td>
-</tr>
-</tbody>
-</table>
-<table class="infolist"> 
-<tbody>
-<tr>
-  <th colspan="4">Relationship information</th>
-</tr>
-<tr>
- <td class="ColumnAttribute">{{familyform.gramps_id.label}}:</td>
- <td class="ColumnValue" id="data">{% render familyform.gramps_id user action %}</td>
- <td class="ColumnAttribute">{{familyform.family_rel_type.label}}:</td>
- <td class="ColumnValue" id="data">{% render familyform.family_rel_type user action %}</td>
-</tr>
-<tr>
- <td class="ColumnAttribute">{{familyform.tags.label}}:</td>
- <td class="ColumnValue" id="data">{% render familyform.tags user action %}</td>
- <td class="ColumnAttribute">{{familyform.private.label}}:</td>
- <td class="ColumnValue" id="data">{% render familyform.private user action %}</td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-
-<!-- Tabs -->
-
-<div class="ui-tabs ui-widget ui-widget-content ui-corner-all" id="tabs" style="border: none;">
-  <ul class="ui-tabs-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all">
-    <li class="ui-state-default ui-corner-top ui-tabs-selected ui-state-active"><a class="tab-children" href="#tab-children">Children</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-events" href="#tab-events">Event</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-citations" href="#tab-citations">Citation</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-attributes" href="#tab-attributes">Attribute</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-notes" href="#tab-notes">Note</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-media" href="#tab-media">Media</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-lds" href="#tab-lds">LDS</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-history" href="#tab-history">History</a></li>
-  </ul>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom" id="tab-children" style="background-color: #f4f0ec;"> 
-    <!-- Events -->
-    {% children_table family user action "/person/$act/family/%s" family.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-events" style="background-color: #f4f0ec;"> 
-    {% event_table family user action "/event/$act/family/%s" family.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-citations" style="background-color: #f4f0ec;"> 
-    {% citation_table family user action "/citation/$act/family/%s" family.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-attributes" style="background-color: #f4f0ec;"> 
-    {% attribute_table family user action "/attribute/add/family/%s" family.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-notes" style="background-color: #f4f0ec;"> 
-    {% note_table family user action "/note/$act/family/%s" family.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-media" style="background-color: #f4f0ec;"> 
-    {% media_table family user action "/media/$act/family/%s" family.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-lds" style="background-color: #f4f0ec;"> 
-    {% lds_table family user action "/lds/add/family/%s" family.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-history" style="background-color: #f4f0ec;"> 
-    {% history_table family user action %}
-  </div>
-</div>
-
-{% if user.is_superuser %}
-  {% if action == "edit" %}
-    {% make_button "Cancel" "/family/%s" family.handle args %}
-    <input type="hidden" id="father_return" name="father_return" value=""/>
-    <input type="hidden" id="mother_return" name="mother_return" value=""/>
-    <input type="hidden" name="action" value="save"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save"/>
-  {% else %}
-    {% ifequal action "add" %}
-      {% make_button "Cancel" "/family/" args %}
-      <input type="hidden" id="father_return" name="father_return" value=""/>
-      <input type="hidden" id="mother_return" name="mother_return" value=""/>
-      <input type="hidden" name="action" value="create"/>
-      <input type="hidden" name="search" value="{{search}}"/>
-      <input type="hidden" name="page" value="{{page}}"/>
-      <input type="submit" value="Create"/>
-    {% else %}
-      <div style="background-color: lightgray; padding: 2px 0px 0px 2px; clear: both;">
-      {% make_button "+Add Family" "/family/add" args %}
-      {% make_button "?Edit Family" "/family/%s/edit" family.handle args %}
-      {% make_button "-Delete Family" "/family/%s/delete" family.handle args %}
-      </div>
-    {% endifequal %}
-  {% endif %}
-{% else %}
-{% endif %}
-</form>
-{% endblock %}
-

data/templates/view_media.html

@@ -1,53 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-<table cellspacing="0" class="infolist surname" width="95%">
-<thead>
-  <tr>
-    <th>#</th>
-    <th>ID</th>
-    <th>Description</th>
-    <th>File</th>
-  </tr>
-</thead>
-<tbody>
-  {% for media in page.object_list %}
-  <tr class="{% cycle odd,even %}">
-    <td>{{ forloop.counter|row_count:page }}</td>
-    <td><a href="/{{view}}/{{media.handle|escape}}{{args}}" class="noThumb browsecell"
-	{% if media.tags.all %}
-            style="color: {{media.tags.all.0.color|format_color}};"
-	{% endif %}
-        >
-           <span class="grampsid">[{{media.gramps_id}}]</span></a>
-    {% if user.is_authenticated or media.public %}
-    <td><a href="/{{view}}/{{media.handle|escape}}{{args}}" class="browsecell"
-	{% if media.tags.all %}
-            style="color: {{media.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{media.desc|escape}}</a>
-    <td><a href="/{{view}}/{{media.handle|escape}}{{args}}" class="browsecell"
-	{% if media.tags.all %}
-            style="color: {{media.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{media.path|escape}}</a>
-    {% else %}
-      <td></td>
-      <td></td>
-      <td></td>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-
-{% block admin_functions %}
-{% if user.is_superuser %}
-   <div style="background-color: lightgray; padding: 2px 0px 0px 2px">
-   {% make_button "+Add Media" "/media/add" args %}
-   </div>
-{% endif %}
-{% endblock %}

data/templates/view_media_detail.html

@@ -1,109 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-   <script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-   });
-   </script>
-
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-
-
-<div id="summaryarea">
-<table class="infolist" style="width:90%;">
-<tbody>
-  {% if mediaform.errors %}
-    <hr>
-    <p id="error">The following fields have errors. Please correct and try again.</p>
-    <div id="error">{{mediaform.errors}}</div>
-    <hr>
-  {% endif %}
-<form method="post">{% csrf_token %}
-<tr>
-<td class="ColumnAttribute">{{mediaform.desc.label}}:</td>
-<td class="ColumnValue" id="data" colspan="3">{% render mediaform.desc user action %}</td>
-<td rowspan="5">{% media_link media.handle user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{mediaform.gramps_id.label}}:</td>
-<td class="ColumnValue" id="data">{% render mediaform.gramps_id user action %}</td>
-<td class="ColumnAttribute">{{mediaform.private.label}}:</td>
-<td class="ColumnValue" id="data">{% render mediaform.private user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{mediaform.text.label}}:</td>
-<td class="ColumnValue" id="data" colspan="3">{% render mediaform.text user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{mediaform.path.label}}:</td>
-<td class="ColumnValue" id="data" colspan="3">{% render mediaform.path user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{mediaform.tags.label}}:</td>
-<td class="ColumnValue" id="data" colspan="3">{% render mediaform.tags user action %}</td>
-</tr>
-</table>
-
-<!-- Tabs -->
-
-<div class="ui-tabs ui-widget ui-widget-content ui-corner-all" id="tabs" style="border: none;">
-  <ul class="ui-tabs-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all">
-    <li class="ui-state-default ui-corner-top ui-tabs-selected ui-state-active"><a class="tab-sources" href="#tab-sources" style=":hover {color: black;}">Citation</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-attributes" href="#tab-attributes">Attribute</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-notes" href="#tab-notes">Note</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-references" href="#tab-references">Reference</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-history" href="#tab-history">History</a></li>
-  </ul>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-sources" style="background-color: #f4f0ec;"> 
-    {% citation_table media user action "/citation/$act/media/%s" media.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-notes" style="background-color: #f4f0ec;"> 
-    {% note_table media user action "/note/$act/media/%s" media.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-attributes" style="background-color: #f4f0ec;"> 
-    {% attribute_table media user action "/attribute/add/media/%s" media.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom" id="tab-references" style="background-color: #f4f0ec;"> 
-    {% media_reference_table media user action %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-history" style="background-color: #f4f0ec;"> 
-    {% history_table media user action %}
-  </div>
-</div>
-
-{% if user.is_superuser %}
-  {% if action == "edit" %}
-    {% make_button "Cancel" "/media/%s" media.handle args %}
-    <input type="hidden" name="action" value="save"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save"/>
-  {% else %}
-    {% ifequal action "add" %}
-      {% make_button "Cancel" "/media/" args %}
-      <input type="hidden" name="action" value="create"/>
-      <input type="hidden" name="search" value="{{search}}"/>
-      <input type="hidden" name="page" value="{{page}}"/>
-      <input type="submit" value="Create"/>
-    {% else %}
-      <div style="background-color: lightgray; padding: 2px 0px 0px 2px; clear: both;">
-      {% make_button "+Add Media" "/media/add" args %}
-      {% make_button "?Edit Media" "/media/%s/edit" media.handle args %}
-      {% make_button "-Delete Media" "/media/%s/delete" media.handle args %}
-      </div>
-    {% endifequal %}
-  {% endif %}
-{% else %}
-{% endif %}
-</form>
-{% endblock %}
-

data/templates/view_name_detail.html

@@ -1,148 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-   <script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-   });
-   </script>
-
-<div class="content" id="IndividualDetail">
-
-   {% filter breadcrumb %}
-      {% format "/browse|Browse" %} ||
-      {% format "/person|People" %} ||
-      {% format "/person/%s|Person [%s]" object.handle object.gramps_id %} ||
-      {% format "/person/%s/name/%s|Name #%s"  object.handle order order %}
-   {% endfilter %}
-
-<h3>{{nameform.model|make_name:user}} [{{person.gramps_id}}]</h3>
-<div id="summaryarea">
-<table class="infolist" style="width:90%;"> {% comment %} 4 cols {% endcomment %}
-<tbody>
-
-{% for error in nameform.errors %}
-    <p id="error">{{error}}</a><br>
-{% endfor %}
-
-<form method="post">{% csrf_token %}
-<tr>
- <td class="ColumnAttribute">{{surnameform.name_origin_type.label}}:</td>
- <td class="ColumnValue" id="data">{% render surnameform.name_origin_type user action %}</td>
- <td class="ColumnAttribute">{{nameform.name_type.label}}:</td>
- <td class="ColumnValue" id="data">{% render nameform.name_type user action %}</td>
-</tr>
-<tr>
- <td class="ColumnAttribute">{{surnameform.surname.label}}:</td>
- <td class="ColumnValue" id="data">{% render surnameform.surname user action "get_focus" %}</td>
- <td class="ColumnAttribute">{{surnameform.prefix.label}}:</td>
- <td class="ColumnValue" id="data">{% render surnameform.prefix user action %}</td>
-</tr>
-<tr>
- <td class="ColumnAttribute">{{nameform.first_name.label}}:</td>
- <td class="ColumnValue" id="data">{% render nameform.first_name user action %}</td>
- <td class="ColumnAttribute">{{nameform.nick.label}}:</td>
- <td class="ColumnValue" id="data">{% render nameform.nick user action %}</td>
-</tr>
-<tr>
- <td class="ColumnAttribute">{{nameform.title.label}}:</td>
- <td class="ColumnValue" id="data">{% render nameform.title user action %}</td>
- <td class="ColumnAttribute">{{nameform.suffix.label}}:</td>
- <td class="ColumnValue" id="data">{% render nameform.suffix user action %}</td>
-</tr>
-<tr>
- <td class="ColumnAttribute"></td>
- <td class="ColumnValue" id="data"></td>
- <td class="ColumnAttribute">{{nameform.call.label}}:</td>
- <td class="ColumnValue" id="data">{% render nameform.call user action %}</td>
-</tr>
-<tr>
- <td class="ColumnAttribute">{{nameform.preferred.label}}:</td>
- <td class="ColumnValue" id="data">{% render nameform.preferred user action %}</td>
- <td class="ColumnAttribute">{{nameform.private.label}}:</td>
- <td class="ColumnValue" id="data">{% render nameform.private user action %}</td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-
-<!-- Tabs -->
-
-<div class="ui-tabs ui-widget ui-widget-content ui-corner-all" id="tabs" style="border: none;">
-  <ul class="ui-tabs-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all">
-    <li class="ui-state-default ui-corner-top ui-tabs-selected ui-state-active"><a class="tab-general" href="#tab-general">General</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-surnames" href="#tab-surnames">Surname</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-names" href="#tab-names">Alternate Names</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-citations" href="#tab-citations">Citation</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-notes" href="#tab-notes">Note</a></li>
-  </ul>
-
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom"
-  id="tab-general" style="background-color: #f4f0ec;"> 
-    <div style="overflow: auto; height:150px;">
-    <table border="1">
-    <tr><td style="background-color: #FFF2C5;">{{nameform.group_as.label}}: </td>
-        <td>{% render nameform.group_as user action %}</td>
-    </tr>
-    <tr><td style="background-color: #FFF2C5;">{{nameform.sort_as.label}}: </td>
-        <td>{% render nameform.sort_as user action %}</td>
-    </tr>
-    <tr><td style="background-color: #FFF2C5;">{{nameform.display_as.label}}: </td>
-         <td>{% render nameform.display_as user action %}</td>
-    </tr>
-    <tr><td style="background-color: #FFF2C5;">{{nameform.text.label}}: </td>
-         <td>{% render nameform.text user action %}</td>
-    </tr>
-    </table>
-    </div>
-    &nbsp;
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-surnames" style="background-color: #f4f0ec;"> 
-    {% surname_table person user action "/person/%s/name/%s/surname/add" person.handle nameform.model.order %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-names" style="background-color: #f4f0ec;"> 
-    {% name_table person user action "/person/%s/name" person.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-citations" style="background-color: #f4f0ec;"> 
-    {% citation_table nameform.model user action "/citation/add/person/%s/name/%s" person.handle nameform.model.order %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom
-	      ui-tabs-hide" id="tab-notes" style="background-color: #f4f0ec;"> 
-    {% note_table nameform.model user action "/note/$act/person/%s/name/%s" person.handle nameform.model.order %}
-  </div>
-</div>
-
-{% if user.is_superuser %}
-  {% ifequal action "add" %}
-    {% make_button "Cancel" "/person/%s" person.handle args "#tab-names" %}
-    <input type="hidden" name="action" value="create"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Create"/>
-  {% else %}
-  {% ifequal action "edit" %}
-    {% make_button "Cancel" "/person/" args "#tab-names" %}
-    <input type="hidden" name="action" value="save"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save"/>
-  {% else %}
-    <div style="background-color: lightgray; padding: 2px 0px 0px 2px; clear: both;">
-    {% make_button "+Add Name" "/person/%s/name/add" person.handle args %}
-    {% make_button "?Edit Name" "/person/%s/name/%s/edit" person.handle order args %}
-    {% make_button "-Delete Name" "/person/%s/name/%s/delete" person.handle order args %}
-    </div>
-  {% endifequal %}
- {% endifequal %}
-{% else %}
-{% endif %}
-</form>
-{% endblock %}
-

data/templates/view_note_detail.html

@@ -1,116 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-<script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-       $('.wysiwyg').htmlarea({
-              toolbar: [
-                 "bold", "italic", "underline", 
-                 "|", "forecolor", "superscript", "p",
-                 "|", "link", "unlink", 
-                 "|", "html"
-              ]
-            });
-       // FIXME: add font, fontsize, backcolor
-       // FIXME: find easier way:
-       $('.jHtmlArea').contents().find('iframe').contents().find('body').css({"background-color": "white"});
-   });
-   function setnotetext() {
-        document.getElementById('notetext').value = $('.jHtmlArea').contents().find('iframe').contents().find('body').html();
-   }
-</script>
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-
-<div id="summaryarea">
-<table class="infolist" style="width:90%;">
-<tbody>
-  {% if noteform.errors %}
-    <hr>
-    <p id="error">The following fields have errors. Please correct and try again.</p>
-    <div id="error">{{noteform.errors}}</div>
-    <hr>
-  {% endif %}
-<form method="post" onsubmit="setnotetext()">{% csrf_token %}
-<tr>
-<td class="ColumnAttribute">{{noteform.notetext.label}}:</td>
-<td class="ColumnValue" id="data" colspan="3">
-{% if action == "edit" or action == "add" %}
-  <input type="hidden" id="notetext" name="notetext" value=""></input>
-  {% render noteform.notetext user action %} 
-{% else %}
-  <div style="overflow-y: scroll; height: 100px;">{{notetext|safe}}</div>
-{% endif %}
-</td>
-</tr>
-</tr>
-<tr>
-<td></td>
-<td></td>
-<td class="ColumnAttribute">{{noteform.preformatted.label}}:</td>
-<td class="ColumnValue" id="data">{% render noteform.preformatted user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{noteform.gramps_id.label}}:</td>
-<td class="ColumnValue" id="data"> {% render noteform.gramps_id user action %}</td>
-<td class="ColumnAttribute">{{noteform.note_type.label}}:</td>
-<td class="ColumnValue" id="data">{% render noteform.note_type user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{noteform.tags.label}}:</td>
-<td class="ColumnValue" id="data" colspan="4">{% render noteform.tags user action %}</td>
-</tr>
-</table>
-
-<!-- Tabs -->
-
-<div class="ui-tabs ui-widget ui-widget-content ui-corner-all" id="tabs" style="border: none;">
-  <ul class="ui-tabs-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all">
-    <li class="ui-corner-top ui-state-default"><a class="tab-references" href="#tab-references">Reference</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-history" href="#tab-history">History</a></li>
-  </ul>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-references" style="background-color: #f4f0ec;"> 
-    {% note_reference_table note user action %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-history" style="background-color: #f4f0ec;"> 
-    {% history_table note user action %}
-  </div>
-</div>
-</div>
-</div>
-
-{% if user.is_superuser %}
-  {% if action == "edit" %}
-    {% make_button "Cancel" "/note/%s" note.handle args %}
-    <input type="hidden" name="action" value="save"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save"/>
-  {% else %}
-    {% ifequal action "add" %}
-      {% make_button "Cancel" "/note/" args %}
-      <input type="hidden" name="action" value="create"/>
-      <input type="hidden" name="search" value="{{search}}"/>
-      <input type="hidden" name="page" value="{{page}}"/>
-      <input type="submit" value="Create"/>
-    {% else %}
-      <div style="background-color: lightgray; padding: 2px 0px 0px 2px; clear: both;">
-      {% make_button "+Add Note" "/note/add" args %}
-      {% make_button "?Edit Note" "/note/%s/edit" note.handle args %}
-      {% make_button "-Delete Note" "/note/%s/delete" note.handle args %}
-      </div>
-    {% endifequal %}
-  {% endif %}
-{% else %}
-{% endif %}
-</form>
-{% endblock %}
-

data/templates/view_notes.html

@@ -1,53 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-
-<table cellspacing="0" class="infolist surname" width="95%">
-<thead>
-  <tr>
-    <th>#</th>
-    <th>ID</th>
-    <th>Note Type</th>
-    <th>Text</th>
-  </tr>
-</thead>
-<tbody>
-  {% for note in page.object_list %}
-  <tr class="{% cycle odd,even %}">
-    <td>{{ forloop.counter|row_count:page }}</td>
-    <td><a href="/{{view}}/{{note.handle|escape}}{{args}}" class="noThumb browsecell"
-	{% if note.tags.all %}
-            style="color: {{note.tags.all.0.color|format_color}};"
-	{% endif %}
-        >
-           <span class="grampsid">[{{note.gramps_id}}]</span></a>
-    {% if user.is_authenticated or note.public %}
-    <td><a href="/{{view}}/{{note.handle|escape}}{{args}}" class="browsecell"
-	{% if note.tags.all %}
-            style="color: {{note.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{note.note_type|escape|nbsp}}</a>
-    <td><a href="/{{view}}/{{note.handle|escape}}{{args}}" class="browsecell"
-	{% if note.tags.all %}
-            style="color: {{note.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{note.text|preview:70|nbsp}}</a>
-    {% else %}
-      <td>[Private]</td>
-      <td>[Private]</td>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-
-{% block admin_functions %}
-{% if user.is_superuser %}
-   <div style="background-color: lightgray; padding: 2px 0px 0px 2px">
-   {% make_button "+Add Note" "/note/add" args %}
-   </div>
-{% endif %}
-{% endblock %}

data/templates/view_page.html

@@ -1,28 +0,0 @@
-{% extends "gramps-base.html" %}
-{% load my_tags %}
-
-{% block title %}{{sitename}}: {{tview}} view {% endblock %}
-{% block heading %}{{sitename}}: {{tview}} view {% endblock %}
-
-{% block content %} 
-
-<div id="description" style="padding: 10pt 10pt 10pt 10pt;">
-<form name="SearchForm">
-{% if tview != "Report" %}
-   {% filter breadcrumb %}
-      {% format "/browse|Browse" %} ||
-      {% format "/%s|%s" view tviews %}
-   {% endfilter %}
-{% endif %}
-<input type="submit" value="Search:"></input>
-<input autocomplete="off" name="search" id="get_focus" type="text" size="50" value="{{search}}"></input>
-<br/><i>Available search terms</i>: <b>{{search_terms}}</b>
-</form>
-</div>
-{% paginator %}
-<div style="overflow:auto; height:300px;width:800px;">
-{% block table_data %} <table></table> {% endblock %}
-</div>
-{% include "paginator.html" %}
-{% block admin_functions %}{% endblock %}
-{% endblock %}

data/templates/view_page_detail.html

@@ -1,6 +0,0 @@
-{% extends "gramps-base.html" %}
-{% load my_tags %}
-{% block title %}{{sitename}}: {{tview}} detail {% endblock %}
-{% block heading %}{{sitename}}: {{tview}} detail {% endblock %}
-{% block content %} 
-{% endblock %}

data/templates/view_people.html

@@ -1,68 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-
-<table cellspacing="0" class="infolist surname" width="95%">
-<thead>
-  <tr>
-    <th>#</th>
-    <th>Name</th>
-    <th>ID</th>
-    <th>Gender</th>
-    <th>Birth Date</th>
-    <th>Death Date</th>
-  </tr>
-</thead>
-<tbody>
-  {% for name in page.object_list %}
-  <tr class="{% cycle odd,even %}" style="">
-    {% if name.person %}
-    <td><a href="{{name.person.handle}}/{{args}}" class="noThumb browsecell"
-	{% if name.person.tags.all %}
-            style="color: {{name.person.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{ forloop.counter|row_count:page }}</a>
-    </td>
-    <td><a href="{{name.person.handle}}/{{args}}" class="noThumb browsecell"
-	{% if name.person.tags.all %}
-            style="color: {{name.person.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{name|make_name:user}} &nbsp;</a>
-    </td>
-    <td><a href="{{name.person.handle}}/{{args}}" class="grampsid browsecell"
-	{% if name.person.tags.all %}
-            style="color: {{name.person.tags.all.0.color|format_color}};"
-	{% endif %}
-        >[{{name.person.gramps_id}}]</a></td>
-    <td><a href="{{name.person.handle}}/{{args}}" class="noThumb browsecell"
-	{% if name.person.tags.all %}
-            style="color: {{name.person.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{name.person.gender_type}} &nbsp;</a></td>
-    <td><a href="{{name.person.handle}}/{{args}}" class="noThumb browsecell"
-	{% if name.person.tags.all %}
-            style="color: {{name.person.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{name.person.birth|date_as_text:user}} &nbsp;</a></td>
-    <td><a href="{{name.person.handle}}/{{args}}" class="noThumb browsecell"
-	{% if name.person.tags.all %}
-            style="color: {{name.person.tags.all.0.color|format_color}};"
-	{% endif %}
-        >{{name.person.death|date_as_text:user}} &nbsp;</a></td>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-
-{% block admin_functions %}
-{% if user.is_superuser %}
-   <div style="background-color: lightgray; padding: 2px 0px 0px 2px">
-   {% make_button "+Add Person" "/person/add" args %}
-   </div>
-{% endif %}
-{% endblock %}
-

data/templates/view_person_detail.html

@@ -1,173 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-   <script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-   });
-   </script>
-
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-
-<div id="summaryarea">
-<table class="infolist" style="width:90%;"> {% comment %} 5 cols {% endcomment %}
-<tbody>
-  {% if personform.errors or nameform.errors or surnameform.errors or logform.errors %}
-    <hr>
-    <p id="error">The following fields have errors. Please correct and try again.</p>
-    <div id="error">
-       {{personform.errors}}
-       {{nameform.errors}}
-       {{surnameform.errors}}
-       {{logform.errors}}
-    </div>
-    <hr>
-  {% endif %}
-<form method="post">{% csrf_token %}
-<tr>
- <td colspan="4" id="subtitle">{{nameform|render_name:user}}</td>
- <td class="ColumnAttribute">{{nameform.name_type.label}}:</td>
- <td class="ColumnValue" id="data">{% render nameform.name_type user action %}</td>
-</tr>
-<tr><td id="rowspace"></td></tr>
-<tr>
- <td class="ColumnAttribute">{{nameform.title.label}}:</td>
- <td class="ColumnValue" id="data">{% render nameform.title user action "get_focus" %}</td>
- <td class="ColumnAttribute">{{nameform.nick.label}}:</td>
- <td class="ColumnValue" id="data">{% render nameform.nick user action %}</td>
- <td class="ColumnAttribute">{{nameform.call.label}}:</td>
- <td class="ColumnValue" id="data">{% render nameform.call user action %}</td>
-</tr>
-<tr><td id="rowspace"></td></tr>
-<tr>
- <td class="ColumnAttribute">{{nameform.first_name.label}}:</td>
- <td class="ColumnValue" id="data" colspan="4">{% render nameform.first_name user action None "/person/?search=given%%3D%s" nameform.model.first_name %}</td>
- <td class="ColumnValue" id="data">{% render nameform.suffix user action %}</td>
-</tr>
-<tr><td id="rowspace"></td></tr>
-<tr>
- <td class="ColumnAttribute">{{surnameform.surname.label}}:</td>
- <td class="ColumnValue" id="data">{% render surnameform.prefix user action %}
- <td class="ColumnValue" id="data" colspan="2">{% render surnameform.surname user action None "/person/?search=surname%%3D%s" surnameform.model.surname %}</td>
- <td class="ColumnAttribute">{{surnameform.name_origin_type.label}}:</td>
- <td class="ColumnValue" id="data" colspan="2">{% render surnameform.name_origin_type user action %}</td>
-</tr>
-<tr><td id="rowspace"></td></tr>
-<tr>
- <td class="ColumnAttribute">{{personform.gender_type.label}}:</td>
- <td class="ColumnValue" id="data">{% render personform.gender_type user action None "/person/?search=gender%%3D%s" personform.model.gender_type %}</td>
- <td class="ColumnAttribute">{{personform.gramps_id.label}}:</td>
- <td class="ColumnValue" id="data">{% render personform.gramps_id user action %}</td>
- <td class="ColumnAttribute">{{personform.tags.label}}:</td>
- <td class="ColumnValue" id="data" rowspan="3">{% render personform.tags user action %}</td>
-</tr>
-<tr><td id="rowspace"></td></tr>
-<tr>
- <td class="ColumnAttribute">{{personform.private.label}}:</td>
- <td class="ColumnValue" id="data">{% render personform.private user action %}</td>
- <td class="ColumnAttribute">{{personform.probably_alive.label}}:</td>
- <td class="ColumnValue" id="data">{% if person.probably_alive %}Yes{% else %}No{% endif %}</td>
-</tr>
-</tbody>
-</table>
-
-</div>
-</div>
-<!-- Tabs -->
-
-<div class="ui-tabs ui-widget ui-widget-content ui-corner-all" id="tabs" style="border: none;">
-  <ul class="ui-tabs-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all">
-    <li class="ui-state-default ui-corner-top ui-tabs-selected ui-state-active"><a class="tab-events" href="#tab-events">Event</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-references" href="#tab-references">Family</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-names" href="#tab-names">Name</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-citations" href="#tab-citations">Citation</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-attributes" href="#tab-attributes">Attribute</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-addresses" href="#tab-addresses">Address</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-notes" href="#tab-notes">Note</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-media" href="#tab-media">Media</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-internet" href="#tab-internet">Internet</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-association" href="#tab-association">Association</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-lds" href="#tab-lds">LDS</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-history" href="#tab-history">History</a></li>
-  </ul>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom" id="tab-events" style="background-color: #f4f0ec;"> 
-    <!-- Events -->
-    {% event_table person user action "/event/$act/person/%s" person.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-names" style="background-color: #f4f0ec;"> 
-    {% name_table person user action "/person/%s/name" person.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-citations" style="background-color: #f4f0ec;"> 
-    {% citation_table person user action "/citation/$act/person/%s" person.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-attributes" style="background-color: #f4f0ec;"> 
-    {% attribute_table person user action "/attribute/$act/person/%s" person.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-addresses" style="background-color: #f4f0ec;"> 
-    {% address_table person user action "/place/$act/person/%s" person.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom
-	      ui-tabs-hide" id="tab-notes" style="background-color: #f4f0ec;"> 
-    {% note_table person user action "/note/$act/person/%s" person.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-media" style="background-color: #f4f0ec;"> 
-    {% media_table person user action "/media/$act/person/%s" person.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-internet" style="background-color: #f4f0ec;"> 
-    {% internet_table person user action "/person/%s/$act/internet" person.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-association" style="background-color: #f4f0ec;"> 
-    {% association_table person user action "/person/%s/$act/association" person.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-lds" style="background-color: #f4f0ec;"> 
-    {% lds_table person user action "/person/%s/$act/lds" person.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-references" style="background-color: #f4f0ec;"> 
-    {% person_reference_table person user action %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-history" style="background-color: #f4f0ec;"> 
-    {% history_table person user action %}
-  </div>
-</div>
-
-{% if logform %}
-  <table>
-    {{logform.as_table}}
-  </table>
-{% endif %}
-
-{% if user.is_superuser %}
-  {% if action == "edit" %}
-    {% make_button "Cancel" "/person/%s" person.handle args %}
-    <input type="hidden" name="action" value="save"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save"/>
-  {% else %}
-    {% ifequal action "add" %}
-      {% make_button "Cancel" "/person/" args %}
-      <input type="hidden" name="action" value="create"/>
-      <input type="hidden" name="search" value="{{search}}"/>
-      <input type="hidden" name="page" value="{{page}}"/>
-      <input type="submit" value="Create"/>
-    {% else %}
-      <div style="background-color: lightgray; padding: 2px 0px 0px 2px; clear: both;">
-      {% make_button "+Add Person" "/person/add" args %}
-      {% make_button "?Edit Person" "/person/%s/edit" person.handle args %}
-      {% make_button "-Delete Person" "/person/%s/delete" person.handle args %}
-      </div>
-    {% endifequal %}
-  {% endif %}
-{% else %}
-{% endif %}
-</form>
-{% endblock %}
-

data/templates/view_place_detail.html

@@ -1,148 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-   <script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-   });
-   </script>
-
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-
-<div id="summaryarea">
-
-<table class="infolist" style="width:90%;">
-<trbody>
-  {% if placeform.errors %}
-    <hr>
-    <p id="error">The following fields have errors. Please correct and try again.</p>
-    <div id="error">{{placeform.errors}}</div>
-    <hr>
-  {% endif %}
-<form method="post">{% csrf_token %}
-<tr>
-<td class="ColumnAttribute">{{placeform.title.label}}:</td>
-<td class="Columnvalue" id="data" colpan="3"> {% render placeform.title user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{placeform.lat.label}}:</td>
-<td class="ColumnValue" id="data">{% render placeform.lat user action %}</td>
-<td class="ColumnAttribute">{{placeform.long.label}}:</td>
-<td class="ColumnValue" id="data">{% render placeform.long user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{placeform.gramps_id.label}}:</td>
-<td class="ColumnValue" id="data">{% render placeform.gramps_id user action %}</td>
-<td class="ColumnAttribute">{{placeform.private.label}}:</td>
-<td class="ColumnValue" id="data">{% render placeform.private user action %}</td>
-</tr>
-</table>
-
-<!-- Tabs -->
-
-<div class="ui-tabs ui-widget ui-widget-content ui-corner-all" id="tabs" style="border: none;">
-  <ul class="ui-tabs-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all">
-    <li class="ui-state-default ui-corner-top ui-tabs-selected ui-state-active"><a class="tab-locations" href="#tab-locations">Location</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-alternatelocations" href="#tab-alternatelocations">Alternate Locations</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-citations" href="#tab-citations">Citation</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-notes" href="#tab-notes">Note</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-media" href="#tab-media">Media</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-internet" href="#tab-internet">Internet</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-references" href="#tab-references">Reference</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-history" href="#tab-history">History</a></li>
-  </ul>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom" id="tab-locations" style="background-color: #f4f0ec;"> 
-
-<table class="infolist" style="width:90%;">
-<tr>
-<td class="ColumnAttribute">Street:</td>
-<td class="Columnvalue" id="data" colspan="3"> FIXME </td>
-</tr>
-<tr>
-<td class="ColumnAttribute">Locality:</td>
-<td class="Columnvalue" id="data"> FIXME </td>
-<td class="ColumnAttribute">Church parish:</td>
-<td class="Columnvalue" id="data"> FIXME </td>
-</tr>
-<tr>
-<td class="ColumnAttribute">City:</td>
-<td class="Columnvalue" id="data"> FIXME </td>
-<td class="ColumnAttribute">State:</td>
-<td class="Columnvalue" id="data"> FIXME </td>
-</tr>
-<tr>
-<td class="ColumnAttribute">County:</td>
-<td class="Columnvalue" id="data"> FIXME </td>
-<td class="ColumnAttribute">ZIP/Postal code:</td>
-<td class="Columnvalue" id="data"> FIXME </td>
-</tr>
-<tr>
-<td class="ColumnAttribute">Country:</td>
-<td class="Columnvalue" id="data"> FIXME </td>
-<td class="ColumnAttribute">Phone:</td>
-<td class="Columnvalue" id="data"> FIXME </td>
-</tr>
-</table>
-    
-
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-alternatelocations" style="background-color: #f4f0ec;"> 
-    {% location_table place user action "/location/$act/place/%s" place.handle %}
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-citations" style="background-color: #f4f0ec;"> 
-    {% citation_table place user action "/citation/$act/place/%s" place.handle %}
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-notes" style="background-color: #f4f0ec;"> 
-    {% note_table place user action "/note/$act/place/%s" place.handle %}
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-media" style="background-color: #f4f0ec;"> 
-    {% media_table place user action "/media/$act/place/%s" place.handle %}
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-internet" style="background-color: #f4f0ec;"> 
-    {% internet_table place user action "/internet/$act/place/%s" place.handle %}
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-references" style="background-color: #f4f0ec;"> 
-    {% place_reference_table place user action %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-history" style="background-color: #f4f0ec;"> 
-    {% history_table place user action %}
-  </div>
-</div>
-</div>
-</div>
-
-{% if user.is_superuser %}
-  {% if action == "edit" %}
-    {% make_button "Cancel" "/place/%s" place.handle args %}
-    <input type="hidden" name="action" value="save"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save"/>
-  {% else %}
-    {% ifequal action "add" %}
-      {% make_button "Cancel" "/place/" args %}
-      <input type="hidden" name="action" value="create"/>
-      <input type="hidden" name="search" value="{{search}}"/>
-      <input type="hidden" name="page" value="{{page}}"/>
-      <input type="submit" value="Create"/>
-    {% else %}
-      <div style="background-color: lightgray; padding: 2px 0px 0px 2px; clear: both;">
-      {% make_button "+Add Place" "/place/add" args %}
-      {% make_button "?Edit Place" "/place/%s/edit" place.handle args %}
-      {% make_button "-Delete Place" "/place/%s/delete" place.handle args %}
-      </div>
-    {% endifequal %}
-  {% endif %}
-{% else %}
-{% endif %}
-</form>
-{% endblock %}
-

data/templates/view_places.html

@@ -1,38 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-
-<table cellspacing="0" class="infolist surname" width="95%">
-<thead>
-  <tr>
-    <th>#</th>
-    <th>ID</th>
-    <th>Title</th>
-  </tr>
-</thead>
-<tbody>
-  {% for place in page.object_list %}
-  <tr class="{% cycle odd,even %}">
-    <td>{{ forloop.counter|row_count:page }}</td>
-    <td><a href="/{{view}}/{{place.handle|escape}}{{args}}" class="noThumb browsecell">
-           <span class="grampsid">[{{place.gramps_id}}]</span></a>
-    {% if user.is_authenticated or place.public %}
-    <td><a href="/{{view}}/{{place.handle|escape}}{{args}}" class="browsecell">{{place.title|escape|nbsp}}</a>
-    {% else %}
-      <td></td>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-
-{% block admin_functions %}
-{% if user.is_superuser %}
-   <div style="background-color: lightgray; padding: 2px 0px 0px 2px">
-   {% make_button "+Add Places" "/place/add" args %}
-   </div>
-{% endif %}
-{% endblock %}

data/templates/view_report.html

@@ -1,35 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-
-<table cellspacing="0" class="infolist surname" width="95%">
-
-<thead>
-  <tr>
-    <th>#</th>
-    <th>Report Name</th>
-    <th></th>
-    <th></th>
-  </tr>
-</thead>
-<tbody>
-  {% for report in page.object_list %}
-  <tr class="{% cycle odd,even %}">
-    <td>{{ forloop.counter|row_count:page }}</td>
-    <td><a href="/{{view}}/{{report.handle|escape}}" class="noThumb browsecell">
-           <span class="grampsid">{{report.name}}</span></a>
-    {% if user.is_authenticated %}
-      <td></td>
-      <td></td>
-    {% else %}
-      <td></td>
-      <td></td>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-

data/templates/view_report_detail.html

@@ -1,51 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-
-<div id="summaryarea">
-
-<form name="RunForm" action="/report/{{report.handle}}/run">
-<table class="infolist" style="width:90%;"> 
-<tr>
-<td class="ColumnAttribute">Name:</td>
-<td class="ColumnValue" id="data" colspan="5">{{report.name}} </td>
-</tr>
-<tr>
-<td class="ColumnAttribute">Type:</td>
-<td class="ColumnValue" id="data">{{report.report_type}}</td>
-</tr>
-<td class="ColumnAttribute">Options:</td>
-<td class="ColumnValue" id="data">
-<textarea autocomplete="off" name="options" id="get_focus" cols="70" rows="20">
-{% if report.options %}{{report.options}}{% else %}{% endif %}
-</textarea>
-<br>
-<i>Hint</i>: use Gramps CLI options such as output file format <b>off=pdf</b>, <b>off=ged</b>, or <b>off=gramps</b>
-</td>
-</tr>
-<td class="ColumnValue">
-<input type="submit" value="Run"></input>
-</td>
-<td>
-</td>
-</form>
-
-</tr>
-<tr>
-<td class="ColumnAttribute">Help:</td>
-<td class="ColumnValue" id="data">
-{{help|safe}}
-</td>
-</tr>
-</table>
-
-</div>
-</div>
-
-{% endblock %}
-

data/templates/view_repositories.html

@@ -1,42 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-
-<table cellspacing="0" class="infolist surname" width="95%">
-
-<thead>
-  <tr>
-    <th>#</th>
-    <th>ID</th>
-    <th>Type</th>
-    <th>Name</th>
-  </tr>
-</thead>
-<tbody>
-  {% for repository in page.object_list %}
-  <tr class="{% cycle odd,even %}">
-    <td>{{ forloop.counter|row_count:page }}</td>
-    <td><a href="/{{view}}/{{repository.handle|escape}}{{args}}" class="noThumb browsecell">
-           <span class="grampsid">[{{repository.gramps_id}}]</span></a>
-    {% if user.is_authenticated or repository.public %}
-    <td><a href="/{{view}}/{{repository.handle|escape}}{{args}}" class="browsecell">{{repository.repository_type|escape|nbsp}}</a>
-    <td><a href="/{{view}}/{{repository.handle|escape}}{{args}}" class="browsecell">{{repository.name|escape|nbsp}}</a>
-    {% else %}
-      <td></td>
-      <td></td>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-
-{% block admin_functions %}
-{% if user.is_superuser %}
-   <div style="background-color: lightgray; padding: 2px 0px 0px 2px">
-   {% make_button "+Add Repository" "/repository/add" args %}
-   </div>
-{% endif %}
-{% endblock %}

data/templates/view_repository.html

@@ -1,34 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-
-<table cellspacing="0" class="infolist surname">
-<thead>
-  <tr>
-    <th>Item #</th>
-    <th>ID</th>
-    <th>Father</th>
-    <th>Mother</th>
-    <th>Relationship</th>
-  </tr>
-</thead>
-<tbody>
-  {% for family in page.object_list %}
-  <tr class="{% cycle odd,even %}">
-    <td>{{ forloop.counter|row_count:page }}</td>
-    <td><a href="/{{view}}/{{family.gramps_id|escape}}" class="noThumb"><span class="grampsid">[{{family.gramps_id}}]</span></a>
-    <td><a href="/{{view}}/{{family.handle|escape}}">{{family.father.name_set|make_name:user}}</a>
-    <td><a href="/{{view}}/{{family.handle|escape}}">{{family.mother.name_set|make_name:user}}</a>
-    {% if user.is_authenticated %}
-    <td><a href="/{{view}}/{{family.handle|escape}}">{{family.family_rel_type|escape}}</a>
-    {% else %}
-    <td><a href="/{{view}}/{{family.handle|escape}}">[Private]</a>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-

data/templates/view_repository_detail.html

@@ -1,100 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-   <script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-   });
-   </script>
-
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-
-<div id="summaryarea">
-
-<table class="infolist" style="width:90%;">
-<trbody>
-  {% if repositoryform.errors %}
-    <hr>
-    <p id="error">The following fields have errors. Please correct and try again.</p>
-    <div id="error">{{repositoryform.errors}}</div>
-    <hr>
-  {% endif %}
-<form method="post">{% csrf_token %}
-<tr>
-<td class="ColumnAttribute">{{repositoryform.name.label}}:</td>
-<td class="ColumnValue" id="data" colspan="5">{% render repositoryform.name user action %} </td>
-</tr>
-<tr>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{repositoryform.repository_type.label}}:</td>
-<td class="ColumnValue" id="data">{% render repositoryform.repository_type user action %}</td>
-<td class="ColumnAttribute">{{repositoryform.gramps_id.label}}:</td>
-<td class="ColumnValue" id="data">{% render repositoryform.gramps_id user action %}</td>
-<td class="ColumnAttribute" >{{repositoryform.private.label}}:</td>
-<td class="ColumnValue" id="data">{% render repositoryform.private user action %}</td>
-</tr>
-</table>
-
-<!-- Tabs -->
-
-<div class="ui-tab ui-widget ui-widget-content ui-corner-all" id="tabs" style="border: none;">
-  <ul class="ui-tab-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all">
-    <li class="ui-state-default ui-corner-top ui-tab-selected ui-state-active"><a class="tab-addresses" href="#tab-addresses">Address</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-internet" href="#tab-internet">Internet</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-notes" href="#tab-notes">Note</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-references" href="#tab-references">Reference</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-history" href="#tab-history">History</a></li>
-  </ul>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom" id="tab-addresses" style="background-color: #f4f0ec;"> 
-    {% address_table repository user action "/address/add/repository/%s" repository.handle %}
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-internet" style="background-color: #f4f0ec;"> 
-    {% internet_table repository user action "/internet/add/repository/%s" repository.handle %}
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-notes" style="background-color: #f4f0ec;"> 
-    {% note_table repository user action "/note/$act/repository/%s" repository.handle %}
-  </div>
-  <div class="ui-tab-panel ui-widget-content ui-corner-bottom ui-tab-hide" id="tab-references" style="background-color: #f4f0ec;"> 
-    {% repository_reference_table repository user action %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-history" style="background-color: #f4f0ec;"> 
-    {% history_table repository user action %}
-  </div>
-</div>
-
-{% if user.is_superuser %}
-  {% if action == "edit" %}
-    {% make_button "Cancel" "/repository/%s" repository.handle args %}
-    <input type="hidden" name="action" value="save"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save"/>
-  {% else %}
-    {% ifequal action "add" %}
-      {% make_button "Cancel" "/repository/" args %}
-      <input type="hidden" name="action" value="create"/>
-      <input type="hidden" name="search" value="{{search}}"/>
-      <input type="hidden" name="page" value="{{page}}"/>
-      <input type="submit" value="Create"/>
-    {% else %}
-      <div style="background-color: lightgray; padding: 2px 0px 0px 2px">
-      {% make_button "+Add Repository" "/repository/add" args %}
-      {% make_button "?Edit Repository" "/repository/%s/edit" repository.handle args %}
-      {% make_button "-Delete Repository" "/repository/%s/delete" repository.handle args %}
-      </div>
-    {% endifequal %}
-  {% endif %}
-{% else %}
-{% endif %}
-</form>
-{% endblock %}
-

data/templates/view_source_detail.html

@@ -1,108 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-   <script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-   });
-   </script>
-
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-
-<h3>{{source.title|escape}}</h3>
-<div id="summaryarea">
-<table class="infolist" style="width:90%;"> {% comment %} 2 cols {% endcomment %}
-<tbody>
-  {% if sourceform.errors %}
-    <hr>
-    <p id="error">The following fields have errors. Please correct and try again.</p>
-    <div id="error">{{sourceform.errors}}</div>
-    <hr>
-  {% endif %}
-<form method="post">{% csrf_token %}
-<tr>
-<td class="ColumnAttribute">{{sourceform.title.label}}:</td>
-<td class="ColumnValue" id="data">{% render sourceform.title user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{sourceform.gramps_id.label}}:</td>
-<td class="ColumnValue" id="data">{% render sourceform.gramps_id user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{sourceform.abbrev.label}}:</td>
-<td class="ColumnValue" id="data">{% render sourceform.abbrev user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{sourceform.pubinfo.label}}:</td>
-<td class="ColumnValue" id="data">{% render sourceform.pubinfo user action %}</td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-
-<!-- Tabs -->
-
-<div class="ui-tabs ui-widget ui-widget-content ui-corner-all" id="tabs" style="border: none;">
-  <ul class="ui-tabs-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all">
-    <li class="ui-state-default ui-corner-top ui-tabs-selected ui-state-active"><a class="tab-notes" href="#tab-notes">Note</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-media" href="#tab-media">Media</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-data" href="#tab-data">Data</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-repositories" href="#tab-repositories">Repository</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-references" href="#tab-references">Reference</a></li>
-    <li class="ui-corner-top ui-state-default"><a class="tab-history" href="#tab-history">History</a></li>
-  </ul>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom" id="tab-notes" style="background-color: #f4f0ec;"> 
-    {% note_table source user action "/note/$act/source/%s" source.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-media" style="background-color: #f4f0ec;"> 
-    {% media_table source user action "/media/$act/source/%s" source.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-data" style="background-color: #f4f0ec;"> 
-    {% data_table source user action "/data/add/source/%s" source.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-repositories" style="background-color: #f4f0ec;"> 
-    {% repository_table source user action "/repository/$act/source/%s" source.handle %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-references" style="background-color: #f4f0ec;"> 
-    {% source_reference_table source user action %}
-  </div>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide" id="tab-history" style="background-color: #f4f0ec;"> 
-    {% history_table source user action %}
-  </div>
-</div>
-
-{% if user.is_superuser %}
-  {% if action == "edit" %}
-    {% make_button "Cancel" "/source/%s" source.handle args %}
-    <input type="hidden" name="action" value="save"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save"/>
-  {% else %}
-    {% ifequal action "add" %}
-      {% make_button "Cancel" "/source/" args %}
-      <input type="hidden" name="action" value="create"/>
-      <input type="hidden" name="search" value="{{search}}"/>
-      <input type="hidden" name="page" value="{{page}}"/>
-      <input type="submit" value="Create"/>
-    {% else %}
-      <div style="background-color: lightgray; padding: 2px 0px 0px 2px; clear: both;">
-      {% make_button "+Add Source" "/source/add" args %}
-      {% make_button "?Edit Source" "/source/%s/edit" source.handle args %}
-      {% make_button "-Delete Source" "/source/%s/delete" source.handle args %}
-      </div>
-    {% endifequal %}
-  {% endif %}
-{% else %}
-{% endif %}
-</form>
-{% endblock %}

data/templates/view_sources.html

@@ -1,44 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-
-<table cellspacing="0" class="infolist surname" width="90%">
-<thead>
-  <tr>
-    <th>#</th>
-    <th>ID</th>
-    <th>Title</th>
-    <th>Pub Info</th>
-    <th>Author</th>
-  </tr>
-</thead>
-<tbody>
-  {% for source in page.object_list %}
-  <tr class="{% cycle odd,even %}">
-    <td>{{ forloop.counter|row_count:page }}</td>
-    <td><a href="/{{view}}/{{source.handle|escape}}{{args}}" class="noThumb browsecell">
-           <span class="grampsid">[{{source.gramps_id}}]</span></a>
-    {% if user.is_authenticated or source.public %}
-    <td><a href="/{{view}}/{{source.handle|escape}}{{args}}" class="browsecell">{{source.title|escape|nbsp}}</a>
-    <td><a href="/{{view}}/{{source.handle|escape}}{{args}}" class="browsecell">{{source.pubinfo|nbsp}}</a>
-    <td><a href="/{{view}}/{{source.handle|escape}}{{args}}" class="browsecell">{{source.author|nbsp}}</a>
-    {% else %}
-      <td></td>
-      <td></td>
-      <td></td>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-
-{% block admin_functions %}
-{% if user.is_superuser %}
-   <div style="background-color: lightgray; padding: 2px 0px 0px 2px">
-   {% make_button "+Add Source" "/source/add" args %}
-   </div>
-{% endif %}
-{% endblock %}

data/templates/view_surname_detail.html

@@ -1,84 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-   <script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-   });
-   </script>
-
-<div class="content" id="IndividualDetail">
-
-   {% filter breadcrumb %}
-      {% format "/browse|Browse" %} ||
-      {% format "/person|People" %} ||
-      {% format "/person/%s|Person [%s]" object.handle object.gramps_id %} ||
-      {% format "/person/%s/name/%s|Name #%s" object.handle order order %} ||
-      {% format "/person/%s/name/%s/surname/%s|Surname #%s" object.handle order sorder sorder %}
-   {% endfilter %}
-
-<h3>{{person|make_name:user}} [{{person.gramps_id}}]</h3>
-<div id="summaryarea">
-<table class="infolist" style="width:90%;"> {% comment %} 4 cols {% endcomment %}
-<tbody>
-{% for error in form.errors %}
-    <p id="error">{{error}}</p>
-{% endfor %}
-<form method="post">{% csrf_token %}
-<tr>
- <td class="ColumnAttribute">{{surnameform.name_origin_type.label}}:</td>
- <td class="ColumnValue" id="data">{% render surnameform.name_origin_type user action %}</td>
-</tr>
-<tr>
- <td class="ColumnAttribute">{{surnameform.primary.label}}:</td>
- <td class="ColumnValue" id="data">{% render surnameform.primary user action %}</td>
-</tr>
-<tr>
- <td class="ColumnAttribute">{{surnameform.prefix.label}}:</td>
- <td class="ColumnValue" id="data">{% render surnameform.prefix user action %}</td>
-</tr>
-<tr>
- <td class="ColumnAttribute">{{surnameform.surname.label}}:</td>
- <td class="ColumnValue" id="data">{% render surnameform.surname user action %}</td>
-</tr>
-<tr>
- <td class="ColumnAttribute">{{surnameform.connector.label}}:</td>
- <td class="ColumnValue" id="data">{% render surnameform.connector user action %}</td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-
-{% if user.is_superuser %}
-  {% if action == "edit" %}
-    {% make_button "Cancel" "/person/%s/name/%s/surname/%s" person.handle order sorder args %}
-    <input type="hidden" name="action" value="save"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save">
-  {% else %} 
-    {% if action == "add" %}
-      {% make_button "Cancel" "/person/%s/name/%s" person.handle order args %}
-      <input type="hidden" name="action" value="create"/>
-      <input type="hidden" name="search" value="{{search}}"/>
-      <input type="hidden" name="page" value="{{page}}"/>
-      <input type="submit" value="Save">
-    {% else %}
-      <div style="background-color: lightgray; padding: 2px 0px 0px 2px; clear: both;">
-      {% make_button "+Add Surname" "/person/%s/name/%s/surname/add" person.handle order args %}
-      {% make_button "?Edit Surname" "/person/%s/name/%s/surname/%s/edit" person.handle order sorder args %}
-      {% make_button "-Delete Surname" "/person/%s/name/%s/surname/%s/delete" person.handle order sorder args %}
-      </div>
-    {% endif %}
-  {% endif %}
-{% endif %}
-</form>
-{% endblock %}
-

data/templates/view_tag.html

@@ -1,28 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-
-<table cellspacing="0" class="infolist surname">
-<thead>
-  <tr>
-    <th>Item #</th>
-    <th>Text</th>
-  </tr>
-</thead>
-<tbody>
-  {% for tag in page.object_list %}
-  <tr class="{% cycle odd,even %}">
-    <td>{{ forloop.counter|row_count:page }}</td>
-    {% if user.is_authenticated %}
-    <td><a href="/{{view}}/{{tag.name|escape}}">{{tag.name|escape}}</a>
-    {% else %}
-    <td><a href="/{{view}}/{{tag.handle|escape}}">[Private]</a>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-

data/templates/view_tag_detail.html

@@ -1,80 +0,0 @@
-{% extends "view_page_detail.html" %}
-{% load my_tags %}
-
-{% block content %} 
-
-   <script type="text/javascript">
-   $(function(){
-     $('#tabs').tabs({
-	'select': function(event, ui){
-			document.location.hash = ui.panel.id;
-		}
-     });
-   });
-   </script>
-
-<div class="content" id="IndividualDetail">
-
-{% include "detail_breadcrumb.html" %}
-
-<div id="summaryarea">
-
-<table class="infolist" style="width:90%;">
-<trbody>
-  {% if tagform.errors %}
-    <hr>
-    <p id="error">The following fields have errors. Please correct and try again.</p>
-    <div id="error">{{tagform.errors}}</div>
-    <hr>
-  {% endif %}
-<form method="post">{% csrf_token %}
-<tr>
-<td class="ColumnAttribute">{{tagform.name.label}}:</td>
-<td class="ColumnValue" id="data" colspan="5">{% render tagform.name user action %} </td>
-</tr>
-<tr>
-<td class="ColumnAttribute">{{tagform.color.label}}:</td>
-<td class="ColumnValue" id="data">{% render tagform.color user action %}</td>
-</tr>
-<tr>
-<td class="ColumnAttribute" >{{tagform.priority.label}}:</td>
-<td class="ColumnValue" id="data">{% render tagform.priority user action %}</td>
-</tr>
-</table>
-
-<div class="ui-tabs ui-widget ui-widget-content ui-corner-all" id="tabs" style="border: none;">
-  <ul class="ui-tabs-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all">
-    <li class="ui-state-default ui-corner-top ui-tabs-selected ui-state-active"><a class="tab-references" href="#tab-references" style=":hover {color: black;}">Reference</a></li>
-  </ul>
-  <div class="ui-tabs-panel ui-widget-content ui-corner-bottom" id="tab-references" style="background-color: #f4f0ec;"> 
-    {% tag_reference_table tag user action %}
-  </div>
-</div>
-
-{% if user.is_superuser %}
-  {% if action == "edit" %}
-    {% make_button "Cancel" "/tag/%s" tag.handle args %}
-    <input type="hidden" name="action" value="save"/>
-    <input type="hidden" name="search" value="{{search}}"/>
-    <input type="hidden" name="page" value="{{page}}"/>
-    <input type="submit" value="Save"/>
-  {% else %}
-    {% ifequal action "add" %}
-      {% make_button "Cancel" "/tag/" args %}
-      <input type="hidden" name="action" value="create"/>
-      <input type="hidden" name="search" value="{{search}}"/>
-      <input type="hidden" name="page" value="{{page}}"/>
-      <input type="submit" value="Create"/>
-    {% else %}
-      <div style="background-color: lightgray; padding: 2px 0px 0px 2px; clear: both;">
-      {% make_button "+Add Tag" "/tag/add" args %}
-      {% make_button "?Edit Tag" "/tag/%s/edit" tag.handle args %}
-      {% make_button "-Delete Tag" "/tag/%s/delete" tag.handle args %}
-      </div>
-    {% endifequal %}
-  {% endif %}
-{% else %}
-{% endif %}
-</form>
-{% endblock %}
-

data/templates/view_tags.html

@@ -1,42 +0,0 @@
-{% extends "view_page.html" %}
-{% load my_tags %}
-
-{% block table_data %} 
-
-<table cellspacing="0" class="infolist surname" width="95%">
-
-<thead>
-  <tr>
-    <th>#</th>
-    <th>Text</th>
-    <th>Color</th>
-    <th>Priority</th>
-  </tr>
-</thead>
-<tbody>
-  {% for tag in page.object_list %}
-  <tr class="{% cycle odd,even %}">
-    <td>{{ forloop.counter|row_count:page }}</td>
-    <td><a href="/{{view}}/{{tag.handle|escape}}{{args}}" class="noThumb browsecell">
-           <span class="grampsid">[{{tag.name}}]</span></a>
-    {% if user.is_authenticated %}
-      <td><a href="/{{view}}/{{tag.handle}}{{args}}" class="browsecell">{{tag.color|nbsp}}</a></td>
-      <td><a href="/{{view}}/{{tag.handle}}{{args}}" class="browsecell">{{tag.priority|nbsp}}</a></td>
-    {% else %}
-      <td></td>
-      <td></td>
-    {% endif %}
-  </tr>
-  {% endfor %}
-</tbody>
-</table>
-
-{% endblock %}
-
-{% block admin_functions %}
-{% if user.is_superuser %}
-   <div style="background-color: lightgray; padding: 2px 0px 0px 2px">
-   {% make_button "+Add Tag" "/tag/add" args %}
-   </div>
-{% endif %}
-{% endblock %}

data/tips.xml.in

@@ -1,130 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<tips>
-
-<_tip number="1"><b>Working with Dates</b><br/>A range of dates can be given by using the format &quot;between January 4, 2000 and March 20, 2003&quot;. You can also indicate the level of confidence in a date and even choose between seven different calendars. Try the button next to the date field in the Events Editor.</_tip>
-
-<_tip number="2"><b>Editing Objects</b><br/>In most cases double clicking on a name, source, place or media entry will bring up a window to allow you to edit the object. Note that the result can be dependent on context. For example, in the Family View clicking on a parent or child will bring up the Relationship Editor.</_tip>
-
-<_tip number="3"><b>Adding Images</b><br/>An image can be added to any gallery or the Media View by dragging and dropping it from a file manager or a web browser. Actually you can add any type of file like this, useful for scans of documents and other digital sources.</_tip>
-
-<_tip number="4"><b>Ordering Children in a Family</b><br/>The birth order of children in a family can be set by using drag and drop. This order is preserved even when they do not have birth dates.</_tip>
-
-<_tip number="5"><b>Talk to Relatives Before It Is Too Late</b><br/>Your oldest relatives can be your most important source of information. They usually know things about the family that haven't been written down. They might tell you nuggets about people that may one day lead to a new avenue of research. At the very least, you will get to hear some great stories. Don't forget to record the conversations!</_tip>
-
-<_tip number="7"><b>Filtering People</b><br/>In the People View, you can 'filter' individuals based on many criteria. To define a new filter go to &quot;Edit &gt; Person Filter Editor&quot;. There you can name your filter and add and combine rules using the many preset rules. For example, you can define a filter to find all adopted people in the family tree. People without a birth date mentioned can also be filtered. To get the results save your filter and select it at the bottom of the Filter Sidebar, then click Apply. If the Filter Sidebar is not visible, select View &gt; Filter.</_tip>
-
-<_tip number="8"><b>Inverted Filtering</b><br/>Filters can easily be reversed by using the 'invert' option. For instance, by inverting the 'People with children' filter you can select all people without children.</_tip>
-
-<_tip number="9"><b>Locating People</b><br/>By default, each surname in the People View is listed only once. By clicking on the arrow to the left of a name, the list will expand to show all individuals with that last name. To locate any Family Name from a long list, select a Family Name (not a person) and start typing. The view will jump to the first Family Name matching the letters you enter.</_tip>
-
-<_tip number="10"><b>The Family View</b><br/>The Family View is used to display a typical family unit as two parents and their children.</_tip>
-
-<_tip number="11"><b>Changing the Active Person</b><br/>Changing the Active Person in views is easy. In the Relationship view just click on anyone. In the Ancestry View doubleclick on the person or right click to select any of their spouses, siblings, children or parents.</_tip>
-
-<_tip number="12"><b>Who Was Born When?</b><br/>Under &quot;Tools &gt; Analysis and exploration &gt; Compare Individual Events...&quot; you can compare the data of individuals in your database. This is useful, say, if you wish to list the birth dates of everyone in your database. You can use a custom filter to narrow the results.</_tip>
-
-<_tip number="13"><b>Gramps Tools</b><br/>Gramps comes with a rich set of tools. These allow you to undertake operations such as checking the database for errors and consistency. There are research and analysis tools such as event comparison, finding duplicate people, interactive descendant browser, and many others. All tools can be accessed through the &quot;Tools&quot; menu.</_tip>
-
-<_tip number="14"><b>Calculating Relationships</b><br/>To check if two people in the database are related (by blood, not marriage) try the tool under &quot;Tools &gt; Utilities &gt; Relationship Calculator...&quot;. The exact relationship as well as all common ancestors are reported.</_tip>
-
-<_tip number="15"><b>SoundEx can help with family research</b><br/>SoundEx solves a long standing problem in genealogy, how to handle spelling variations. The SoundEx utility takes a surname and generates a simplified form that is equivalent for similar sounding names. Knowing the SoundEx Code for a surname is very helpful for researching Census Data files (microfiche) at a library or other research facility. To get the SoundEx codes for surnames in your database, go to &quot;Tools &gt; Utilities &gt; Generate SoundEx Codes...&quot;.</_tip>
-
-<_tip number="16"><b>Setting Your Preferences</b><br/>&quot;Edit &gt; Preferences...&quot; lets you modify a number of settings, such as the path to your media files, and allows you to adjust many aspects of the Gramps presentation to your needs. Each separate view can also be configured under &quot;View &gt; Configure View...&quot;</_tip>
-
-<_tip number="17"><b>Gramps Reports</b><br/>Gramps offers a wide variety of reports. The Graphical Reports and Graphs can present complex relationships easily and the Text Reports are particularly useful if you want to send the results of your family tree to members of the family via email. If you're ready to make a website for your family tree then there's a report for that as well.</_tip>
-
-<_tip number="18"><b>Starting a New Family Tree</b><br/>A good way to start a new family tree is to enter all the members of the family into the database using the Person View (use &quot;Edit &gt; Add...&quot; or click on the Add a new person button from the People View). Then go to the Relationship View and create relationships between people.</_tip>
-
-<_tip number="19"><b>What's That For?</b><br/>Unsure what a button does? Simply hold the mouse over a button and a tooltip will appear.</_tip>
-
-<_tip number="20"><b>Unsure of a Date?</b><br/>If you're unsure about the date an event occurred, Gramps allows you to enter a wide range of date formats based on a guess or an estimate. For instance, &quot;about 1908&quot; is a valid entry for a birth date in Gramps. Click the Date button next to the date field and see the Gramps Manual to learn more.</_tip>
-
-<_tip number="21"><b>Duplicate Entries</b><br/>&quot;Tools &gt; Database Processing &gt; Find Possible Duplicate People...&quot; allows you to locate (and merge) entries of the same person entered more than once in the database.</_tip>
-
-<_tip number="22"><b>Merging Entries</b><br/>The function &quot;Edit &gt; Compare and Merge...&quot; allows you to combine separately listed people into one. Select the second entry by holding the Control key as you click. This is very useful for combining two databases with overlapping people, or combining erroneously entered differing names for one individual. This also works for the Places, Sources and Repositories views.</_tip>
-
-<_tip number="23"><b>Organising the Views</b><br/>Many of the views can present your data as either a hierarchical tree or as a simple list. Each view can also be configured to the way you like it. Have a look to the right of the top toolbar or under the &quot;View&quot; menu.</_tip>
-
-<_tip number="24"><b>Navigating Back and Forward</b><br/>Gramps maintains a list of previous active objects such as People, Events and . You can move forward and backward through the list using &quot;Go &gt; Forward&quot; and &quot;Go &gt; Back&quot; or the arrow buttons.</_tip>
-
-<_tip number="25"><b>Keyboard Shortcuts</b><br/>Tired of having to take your hand off the keyboard to use the mouse? Many functions in Gramps have keyboard shortcuts. If one exists for a function it is displayed on the right side of the menu.</_tip>
-
-<_tip number="26"><b>Read the Manual</b><br/>Don't forget to read the Gramps manual, &quot;Help &gt; User Manual&quot;. The developers have worked hard to make most operations intuitive but the manual is full of information that will make your time spent on genealogy more productive.</_tip>
-
-<_tip number="27"><b>Adding Children</b><br/>To add children in Gramps there are two options. You can find one of their parents in the Families View and open the family. Then choose to create a new person or add an existing person. You can also add children (or siblings) from inside the Family Editor.</_tip>
-
-<_tip number="28"><b>Editing the Parent-Child Relationship</b><br/> You can edit the relationship of a child to its parents by double clicking the child in the Family Editor. Relationships can be any of Adopted, Birth, Foster, None, Sponsored, Stepchild and Unknown.</_tip>
-
-<_tip number="29"><b>Show All Checkbutton</b><br/>When adding an existing person as a spouse, the list of people shown is filtered to display only people who could realistically fit the role (based on dates in the database). In case Gramps is wrong in making this choice, you can override the filter by checking the Show All checkbutton.</_tip>
-
-<_tip number="31"><b>Improving Gramps</b><br/>Users are encouraged to request enhancements to Gramps. Requesting an enhancement can be done either through the gramps-users or gramps-devel mailing lists, or by going to http://bugs.gramps-project.org and creating a Feature Request. Filing a Feature Request is preferred but it can be good to discuss your ideas on the email lists.</_tip>
-
-<_tip number="32"><b>Gramps Mailing Lists</b><br/>Want answers to your questions about Gramps? Check out the gramps-users email list. Many helpful people are on the list, so you're likely to get an answer quickly. If you have questions related to the development of Gramps, try the gramps-devel list. You can see the lists by selecting &quot;Help &gt; Gramps Mailing Lists&quot;.</_tip>
-
-<_tip number="33"><b>Contributing to Gramps</b><br/>Want to help with Gramps but can't write programs? Not a problem! A project as large as Gramps requires people with a wide variety of skills. Contributions can be anything from writing documentation to testing development versions and helping with the web site. Start by subscribing to the Gramps developers mailing list, gramps-devel, and introducing yourself. Subscription information can be found at &quot;Help &gt; Gramps Mailing Lists&quot;</_tip>
-
-<_tip number="34"><b>So What's in a Name?</b><br/>The name Gramps was suggested to the original developer, Don Allingham, by his father. It stands for <i>Genealogical Research and Analysis Management Program System</i>. It is a full-featured genealogy program letting you store, edit, and research genealogical data. The Gramps database back end is so robust that some users are managing genealogies containing hundreds of thousands of people.</_tip>
-
-<_tip number="36"><b>Bookmarking Individuals</b><br/>The Bookmarks menu is a convenient place to store the names of frequently used individuals. Selecting a bookmark will make that person the Active Person. To bookmark someone make them the Active Person then go to &quot;Bookmarks &gt; Add Bookmark&quot; or press Ctrl+D. You can also bookmark most of the other objects.</_tip>
-
-<_tip number="37"><b>Incorrect Dates</b><br/>Everyone occasionally enters dates with an invalid format. Incorrect date formats will show up in Gramps with a reddish background. You can fix the date using the Date Selection dialog which can be opened by clicking on the date button. The format of the date is set under &quot;Edit &gt; Preferences &gt; Display&quot;.</_tip>
-
-<_tip number="38"><b>Listing Events</b><br/>Events are added using the editor opened with &quot;Person &gt; Edit Person &gt; Events&quot;. There is a long list of preset event types. You can add your own event types by typing in the text field, they will be added to the available events, but not translated.</_tip>
-
-<_tip number="39"><b>Managing Names</b><br/>It is easy to manage people with several names in Gramps. In the Person Editor select the Names tab. You can add names of different types and set the prefered name by dragging it to the Prefered Name section.</_tip>
-
-<_tip number="40"><b>Ancestor View</b><br/>The Ancestry View displays a traditional pedigree chart. Hold the mouse over an individual to see more information about them or right click on an individual to access other family members and settings. Play with the settings to see the different options.</_tip>
-
-<_tip number="41"><b>Managing Sources</b><br/>The Sources View shows a list of all sources in a single window. From here you can edit your sources, merge duplicates and see which individuals reference each source. You can use filters to group your sources.</_tip>
-
-<_tip number="42"><b>Managing Places</b><br/>The Places View shows a list of all places in the database. The list can be sorted by a number of different criteria, such as City, County or State.</_tip>
-
-<_tip number="43"><b>Media View</b><br/>The Media View shows a list of all media entered in the database. These can be graphic images, videos, sound clips, spreadsheets, documents, and more.</_tip>
-
-<_tip number="44"><b>Filters</b><br/>Filters allow you to limit the people seen in the People View. In addition to the many preset filters, Custom Filters can be created limited only by your imagination. Custom filters are created from &quot;Edit &gt; Person Filter Editor&quot;.</_tip>
-
-<_tip number="45"><b>The GEDCOM File Format</b><br/>Gramps allows you to import from, and export to, the GEDCOM format. There is extensive support for the industry standard GEDCOM version 5.5, so you can exchange Gramps information to and from users of most other genealogy programs. Filters exist that make importing and exporting GEDCOM files trivial.</_tip>
-
-<_tip number="46"><b>The Gramps XML Package</b><br/>You can export your Family Tree as a Gramps XML Package. This is a compressed file containing your family tree data and all the media files connected to the database (images for example). This file is completely portable so is useful for backups or sharing with other Gramps users. This format has the key advantage over GEDCOM that no information is ever lost when exporting and importing.</_tip>
-
-<_tip number="48"><b>Web Family Tree Format</b><br/>Gramps can export data to the Web Family Tree (WFT) format. This format allows a family tree to be displayed online using a single file, instead of many html files.</_tip>
-
-<_tip number="49"><b>Making a Genealogy Website</b><br/>You can easily export your family tree to a web page. Select the entire database, family lines or selected individuals to a collection of web pages ready for upload to the World Wide Web. The Gramps project provides free hosting of websites made with Gramps.</_tip>
-
-<_tip number="50"><b>Reporting Bugs in Gramps</b><br/>The best way to report a bug in Gramps is to use the Gramps bug tracking system at http://bugs.gramps-project.org</_tip>
-
-<_tip number="51"><b>The Gramps Homepage</b><br/>The Gramps homepage is at http://gramps-project.org/</_tip>
-
-<_tip number="53"><b>Privacy in Gramps</b><br/>Gramps helps you to keep personal information secure by allowing you to mark information as private. Data marked as private can be excluded from reports and data exports. Look for the padlock which toggles records between private and public.</_tip>
-
-<_tip number="54"><b>Keeping Good Records</b><br/>Be accurate when recording genealogical information. Don't make assumptions while recording primary information; write it exactly as you see it. Use bracketed comments to indicate your additions, deletions or comments. Use of the Latin 'sic' is recommended to confirm the accurate transcription of what appears to be an error in a source.</_tip>
-
-<_tip number="57"><b>Extra Reports and Tools</b><br/>Extra tools and reports can be added to Gramps with the &quot;Addon&quot; system. See them under &quot;Help &gt; Extra Reports/Tools&quot;. This is the best way for advanced users to experiment and create new functionality.</_tip>
-
-<_tip number="58"><b>Book Reports</b><br/>The Book report under &quot;Reports &gt; Books &gt; Book Report...&quot;, allows you to collect a variety of reports into a single document. This single report is easier to distribute than multiple reports, especially when printed.</_tip>
-
-<_tip number="59"><b>Gramps Announcements</b><br/>Interested in getting notified when a new version of Gramps is released? Join the Gramps-announce mailing list at &quot;Help &gt; Gramps Mailing Lists&quot;</_tip>
-
-<_tip number="60"><b>Record Your Sources</b><br/>Information collected about your family is only as good as the source it came from. Take the time and trouble to record all the details of where the information came from. Whenever possible get a copy of original documents.</_tip>
-
-<_tip number="61"><b>Directing Your Research</b><br/>Go from what you know to what you do not. Always record everything that is known before making conjectures. Often the facts at hand suggest plenty of direction for more research. Don't waste time looking through thousands of records hoping for a trail when you have other unexplored leads.</_tip>
-
-<_tip number="62"><b>The 'How and Why' of Your Genealogy</b><br/> Genealogy isn't only about dates and names. It is about people. Be descriptive. Include why things happened, and how descendants might have been shaped by the events they went through. Narratives go a long way in making your family history come alive.</_tip>
-
-<_tip number="63"><b>Don't speak English?</b><br/>Volunteers have translated Gramps into more than 20 languages. If Gramps supports your language and it is not being displayed, set the default language in your operating system and restart Gramps.</_tip>
-
-<_tip number="64"><b>Gramps Translators</b><br/>Gramps has been designed so that new translations can easily be added with little development effort. If you are interested in participating please email gramps-devel@lists.sf.net</_tip>
-
-<_tip number="66"><b>Hello, привет or 喂</b><br/>Whatever script you use Gramps offers full Unicode support. Characters for all languages are properly displayed.</_tip>
-
-<_tip number="67"><b>The Home Person</b><br/>Anyone can be chosen as the Home Person in Gramps. Use &quot;Edit &gt; Set Home Person&quot; in the Person View. The home person is the person who is selected when the database is opened or when the home button is pressed.</_tip>
-
-<_tip number="70"><b>The Gramps Code</b><br/>Gramps is written in a computer language called Python using the GTK and GNOME libraries for the graphical interface. Gramps is supported on any computer system where these programs have been ported. Gramps is known to be run on Linux, BSD, Solaris, Windows and Mac OS X.</_tip>
-
-<_tip number="71"><b>Open Source Software</b><br/>The Free/Libre and Open Source Software (FLOSS) development model means Gramps can be extended by any programmer since all of the source code is freely available under its license. So it's not just about free beer, it's also about freedom to study and change the tool. For more about Open Source software lookup the Free Software Foundation and the Open Source Initiative.</_tip>
-
-<_tip number="72"><b>The Gramps Software License</b><br/>You are free to use and share Gramps with others. Gramps is freely distributable under the GNU General Public License, see http://www.gnu.org/licenses/licenses.html#GPL to read about the rights and restrictions of this license.</_tip>
-
-<_tip number="73"><b>Gramps for Gnome or KDE?</b><br/>For Linux users Gramps works with whichever desktop environment you prefer. As long as the required GTK libraries are installed it will run fine.</_tip>
-
-</tips>

debian/README.Debian

@@ -3,16 +3,9 @@ gramps for Debian
 
 This is the Debian package of GRAMPS.
 
-Regarding the extra dependencies:
+If you do not install python-reportlab (gramps Recommends it be
+installed) then you will be able to create usable PDF files only if
+your database contains solely latin (iso-8859-1) characters. Reportlab
+will generate PDF files containing non-latin characters although they
+are quite large as the font must be included in the file.
 
-Recommends: graphviz
-  Enable creation of graphs 
-Recommends: python-gtkmozembed
-Recommends: python-webkit
-  Enable html rendering for Geographic view and Web view. If both
-  are installed webkit will be used. python-gtkmozembed may be more
-  stable.
-Suggests: ttf-freefont
-  Allows more fonts in reports
-Suggests: python-gtkspell python-enchant
-  allows spell checking in the notes. Both need to be installed.

debian/changelog

@@ -1,271 +1,8 @@
-gramps (3.3.0-1) lucid; urgency=low
+gramps (2.1.6-1) unstable; urgency=low
 
   * New upstream release
 
- -- Stephane Charette <stephanecharette@gmail.com>  Sun, 12 Jun 2011 02:22:02 -0700
-
-gramps (3.2.0-0beta1) unstable; urgency=low
-
-  * New upstream release
-  * works with gtk 2.19. Closes: #566958
-
- -- James A. Treacy <treacy@debian.org>  Fri, 05 Mar 2010 14:05:39 -0500
-
-gramps (3.1.3-2) unstable; urgency=low
-
-  * Switch to dpkg-source 3.0 (quilt) format
-
- -- James A. Treacy <treacy@debian.org>  Tue, 05 Jan 2010 20:04:30 -0500
-
-gramps (3.1.3-1) unstable; urgency=low
-
-  * New upstream release
-
- -- James A. Treacy <treacy@debian.org>  Sun, 06 Dec 2009 13:46:48 -0500
-
-gramps (3.1.2-2) unstable; urgency=low
-
-  * allow python >= 2.5. Closes: #547150
-  * fix Relationship Graph to use new format for URLs. Closes: #532559
-  * Web report creation fixed. Closes: #537355
-
- -- James A. Treacy <treacy@debian.org>  Tue, 17 Nov 2009 11:38:43 -0500
-
-gramps (3.1.2-1.1) unstable; urgency=low
-
-  * Non-maintainer upload.
-  * debian/control: drop Recommends on python-gnome2-desktop: it is now
-    gone and none of its modules are used anyhow (Closes: #541560)
-
- -- Stefano Zacchiroli <zack@debian.org>  Thu, 08 Oct 2009 13:52:35 +0200
-
-gramps (3.1.2-1) unstable; urgency=low
-
-  * New upstream release.
-  * Replace Recommends on python-gnome2-extras with python-gtkspell
-  * Do not create the directory /etc/gconf/schemas/. Closes: Bug#525683
-
- -- James A. Treacy <treacy@debian.org>  Sun, 07 Jun 2009 14:01:16 -0400
-
-gramps (3.1.1-1) unstable; urgency=low
-
-  * New upstream release.
-
- -- James A. Treacy <treacy@debian.org>  Tue, 10 Mar 2009 09:26:52 -0400
-
-gramps (3.1.0-1) unstable; urgency=low
-
-  * New upstream release.
-  * link /usr/share/common-licenses/GPL-2 from /usr/share/gramps/COPYING
-    so gramps can find the file.
-
- -- James A. Treacy <treacy@debian.org>  Sat, 07 Mar 2009 22:03:09 -0500
-
-gramps (3.0.4-1) unstable; urgency=low
-
-  * New upstream version. Closes: #506621, #506818
-
- -- James A. Treacy <treacy@debian.org>  Sun, 07 Dec 2008 21:39:55 -0500
-
-gramps (3.0.3-1) unstable; urgency=low
-
-  * New upstream version
-
- -- James A. Treacy <treacy@debian.org>  Mon, 20 Oct 2008 20:43:35 -0400
-
-gramps (3.0.2-1) unstable; urgency=low
-
-  * New upstream version
-
- -- James A. Treacy <treacy@debian.org>  Sat, 27 Sep 2008 17:25:09 -0400
-
-gramps (3.0.1-2) unstable; urgency=low
-
-  * Remove dependency on gnome-doc-utils and scrollkeeper
-  * Disable spell checking in src/Spell.py due to the spell checker
-    crashing. Closes: #492212
-    Spell checking will be reenabled once the offending package is
-    identified and fixed.
-
- -- James A. Treacy <treacy@debian.org>  Fri, 29 Aug 2008 11:09:04 -0400
-
-gramps (3.0.1-1) unstable; urgency=low
-
-  * New upstream version
-
- -- James A. Treacy <treacy@debian.org>  Mon, 19 May 2008 09:38:28 -0400
-
-gramps (3.0.0-6) unstable; urgency=low
-
-  * Fix typo in _EditChildRef.py which can cause gramps to crash. Closes: #476163
-
- -- James A. Treacy <treacy@debian.org>  Tue, 15 Apr 2008 23:37:04 -0400
-
-gramps (3.0.0-5) unstable; urgency=low
-
-  * Remove gtkspell Recommends as it is now provided by python-gnome2-extras.
-    Closes: Bug#474755
-
- -- James A. Treacy <treacy@debian.org>  Mon, 07 Apr 2008 17:25:18 -0400
-
-gramps (3.0.0-4) unstable; urgency=low
-
-  * Fix the binary package python dependency properly. A recent python
-    (>= 2.4.4-6) is needed to ensure python2.5 is supported properly.
-    Closes: #474056
-
- -- James A. Treacy <treacy@debian.org>  Thu, 03 Apr 2008 09:46:28 -0400
-
-gramps (3.0.0-3) unstable; urgency=low
-
-  * Build-Depends on Python2.5. Closes: Bug#473946, #474056
-
- -- James A. Treacy <treacy@debian.org>  Wed, 02 Apr 2008 08:28:27 -0400
-
-gramps (3.0.0-2) unstable; urgency=low
-
-  * Explicitly require python version >= 2.5
-
- -- James A. Treacy <treacy@debian.org>  Wed, 26 Mar 2008 09:34:25 -0400
-
-gramps (3.0.0-1) unstable; urgency=low
-
-  * New upstream release. Closes: #472681
-
- -- James A. Treacy <treacy@debian.org>  Tue, 25 Mar 2008 09:35:00 -0400
-
-gramps (2.2.10-2) unstable; urgency=low
-
-  * Remove build dependency on python-xml. Closes: Bug#468625
-
- -- James A. Treacy <treacy@debian.org>  Fri, 29 Feb 2008 13:30:11 -0500
-
-gramps (2.2.10-1) unstable; urgency=low
-
-  * New upstream release
-  * Added dh_icons to debian/rules. Closes: #454761
-  * Remove version from scrollkeeper dependency. Closes: #456600
-  * Fixed typos in description. Closes: #433559
-
- -- James A. Treacy <treacy@debian.org>  Mon, 14 Jan 2008 09:57:25 -0500
-
-gramps (2.2.9-2) unstable; urgency=low
-
-  * Move debhelper to Build-Depends. Closes: #447948
-
- -- James A. Treacy <treacy@debian.org>  Wed, 24 Oct 2007 20:03:36 -0400
-
-gramps (2.2.9-1) unstable; urgency=low
-
-  * New upstream release
-
- -- James A. Treacy <treacy@debian.org>  Thu, 18 Oct 2007 13:14:30 -0400
-
-gramps (2.2.8-2) unstable; urgency=low
-
-  * Work around a bug in gnome-python-extras which caused a deallocation
-    of the TextView in the check if a spell checker is present.
-    Closes: #445864
-
- -- James A. Treacy <treacy@debian.org>  Tue, 09 Oct 2007 17:26:54 -0400
-
-gramps (2.2.8-1) unstable; urgency=low
-
-  * New Upstream version
-  * Misleading error message changed. Closes: #418033
-
- -- James A. Treacy <treacy@debian.org>  Mon, 28 May 2007 21:00:51 -0400
-
-gramps (2.2.7-2) unstable; urgency=low
-
-  * Added dependency on librsvg2-common
-
- -- James A. Treacy <treacy@debian.org>  Mon, 23 Apr 2007 19:32:00 -0400
-
-gramps (2.2.7-1) unstable; urgency=low
-
-  * New upstream version
-
- -- James A. Treacy <treacy@debian.org>  Sun, 22 Apr 2007 20:08:55 -0400
-
-gramps (2.2.6-1) unstable; urgency=low
-
-  * New upstream version
-
- -- James A. Treacy <treacy@debian.org>  Mon, 29 Jan 2007 20:12:05 -0500
-
-gramps (2.2.5-0rc1-1) unstable; urgency=low
-
-  * rc1 of 2.2.5
-
- -- James A. Treacy <treacy@debian.org>  Thu, 25 Jan 2007 23:04:24 -0500
-
-gramps (2.2.4-1) unstable; urgency=low
-
-  * New upstream release
-
- -- James A. Treacy <treacy@debian.org>  Wed, 27 Dec 2006 18:04:11 -0500
-
-gramps (2.2.3-1) unstable; urgency=low
-
-  * New upstream release
-
- -- James A. Treacy <treacy@debian.org>  Mon, 27 Nov 2006 00:27:23 -0500
-
-gramps (2.2.2-2) unstable; urgency=low
-
-  * call dh_desktop in debian/rules so .desktop file is registered. Closes: Bug#398423
-
- -- James A. Treacy <treacy@debian.org>  Mon, 13 Nov 2006 20:26:00 -0500
-
-gramps (2.2.2-1) unstable; urgency=low
-
-  * Bumped upstream version number. 2.2.1-3 and -4 should have been 2.2.2
-
- -- James A. Treacy <treacy@debian.org>  Sat,  4 Nov 2006 16:34:47 -0500
-
-gramps (2.2.1-4) unstable; urgency=low
-
-  * add missing Build-Depends-Indep. Closes: #396874
-
- -- James A. Treacy <treacy@debian.org>  Fri,  3 Nov 2006 11:03:35 -0500
-
-gramps (2.2.1-3) unstable; urgency=low
-
-  * New Upstream release
-
- -- James A. Treacy <treacy@debian.org>  Fri,  3 Nov 2006 08:07:38 -0500
-
-gramps (2.2.1-2) unstable; urgency=low
-
-  * Upload to sid
-
- -- James A. Treacy <treacy@debian.org>  Wed,  1 Nov 2006 20:50:28 -0500
-
-gramps (2.2.1-1) experimental; urgency=low
-
-  * New upstream release
-
- -- James A. Treacy <treacy@debian.org>  Mon, 30 Oct 2006 10:32:43 -0500
-
-gramps (2.1.95-1) experimental; urgency=low
-
-  * Beta release of version 2.2
-
- -- James A. Treacy <treacy@debian.org>  Tue, 29 Aug 2006 11:40:08 -0400
-
-
-gramps (2.1.90-1) experimental; urgency=low
-
-  * Beta release of version 2.2
-
- -- James A. Treacy <treacy@debian.org>  Tue, 25 Jul 2006 00:18:15 -0400
-
-gramps (2.0.11-2) unstable; urgency=low
-
-  * Complies with new python policy
-
- -- James A. Treacy <treacy@debian.org>  Wed,  5 Jul 2006 14:47:56 -0400
+ -- Alex Roitman <shura@gramps-project.org>  Thu, 22 Jun 2006 13:28:14 -0700
 
 gramps (2.0.11-1) unstable; urgency=low