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
Escape still wasn't right in ODFDoc.py. Ancestor and descendant charts were displaying wrong.
2007-04-22 20:58:07 +00:00 · 2007-04-22 13:19:05 +00:00 · 2007-04-21 18:48:04 +00:00 · 2007-04-21 04:30:13 +00:00 · 2007-04-21 02:50:11 +00:00 · 2007-04-20 15:09:22 +00:00
1370 changed files with 270321 additions and 382828 deletions
--- a/13
+++ b/13
@ -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$
--- a/12230
+++ b/12230
--- a/ChangeLog.old
+++ b/ChangeLog.old
--- a/347
+++ b/347
@ -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$
--- a/300
+++ b/300
@ -1,236 +1,98 @@
-Installation Instructions
-*************************
+$Id$

-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
-Software Foundation, Inc.
+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.

-This file is free documentation; the Free Software Foundation gives
-unlimited permission to copy, distribute and modify it.

-Basic Installation
-==================
+configure vs autogen scripts
+----------------------------
+If you are building from released tarball, you should be able to just
+run "./configure && make". However, if you're building from the SVN,
+the configure is not present. You should auto-generate it by
+running ./autogen.sh and then "make" and, finally, "make install".

-These are generic installation instructions.
+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.

-   The `configure' shell script attempts to guess correct values for
-various system-dependent variables used during compilation.  It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions.  Finally, it creates a shell script `config.status' that
-you can run in the future to recreate the current configuration, and a
-file `config.log' containing compiler output (useful mainly for
-debugging `configure').

-   It can also use an optional file (typically called `config.cache'
-and enabled with `--cache-file=config.cache' or simply `-C') that saves
-the results of its tests to speed up reconfiguring.  (Caching is
-disabled by default to prevent problems with accidental use of stale
-cache files.)
+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.

-   If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release.  If you are using the cache, and at
-some point `config.cache' contains results you don't want to keep, you
-may remove or edit it.
+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

-   The file `configure.ac' (or `configure.in') is used to create
-`configure' by a program called `autoconf'.  You only need
-`configure.ac' if you want to change it or regenerate `configure' using
-a newer version of `autoconf'.
+Whether you're doing local install or regular install,
+YOU MUST INSTALL GCONF SCHEMAS AND MIME TYPES.
+YOU HAVE BEEN WARNED!

-The simplest way to compile this package is:

-  1. `cd' to the directory containing the package's source code and type
-     `./configure' to configure the package for your system.  If you're
-     using `csh' on an old version of System V, you might need to type
-     `sh ./configure' instead to prevent `csh' from trying to execute
-     `configure' itself.
+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.

-     Running `configure' takes awhile.  While running, it prints some
-     messages telling which features it is checking for.
+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.

-  2. Type `make' to compile the package.
+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.

-  3. Optionally, type `make check' to run any self-tests that come with
-     the package.
+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

-  4. Type `make install' to install the programs and any data files and
-     documentation.
+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.

-  5. You can remove the program binaries and object files from the
-     source code directory by typing `make clean'.  To also remove the
-     files that `configure' created (so you can compile the package for
-     a different kind of computer), type `make distclean'.  There is
-     also a `make maintainer-clean' target, but that is intended mainly
-     for the package's developers.  If you use it, you may have to get
-     all sorts of other programs in order to regenerate files that came
-     with the distribution.

-Compilers and Options
-=====================
-
-Some systems require unusual options for compilation or linking that the
-`configure' script does not know about.  Run `./configure --help' for
-details on some of the pertinent environment variables.
-
-   You can give `configure' initial values for configuration parameters
-by setting variables in the command line or in the environment.  Here
-is an example:
-
-     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
-
-   *Note Defining Variables::, for more details.
-
-Compiling For Multiple Architectures
-====================================
-
-You can compile the package for more than one kind of computer at the
-same time, by placing the object files for each architecture in their
-own directory.  To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'.  `cd' to the
-directory where you want the object files and executables to go and run
-the `configure' script.  `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
-
-   If you have to use a `make' that does not support the `VPATH'
-variable, you have to compile the package for one architecture at a
-time in the source code directory.  After you have installed the
-package for one architecture, use `make distclean' before reconfiguring
-for another architecture.
-
-Installation Names
-==================
-
-By default, `make install' installs the package's commands under
-`/usr/local/bin', include files under `/usr/local/include', etc.  You
-can specify an installation prefix other than `/usr/local' by giving
-`configure' the option `--prefix=PREFIX'.
-
-   You can specify separate installation prefixes for
-architecture-specific files and architecture-independent files.  If you
-pass the option `--exec-prefix=PREFIX' to `configure', the package uses
-PREFIX as the prefix for installing programs and libraries.
-Documentation and other data files still use the regular prefix.
-
-   In addition, if you use an unusual directory layout you can give
-options like `--bindir=DIR' to specify different values for particular
-kinds of files.  Run `configure --help' for a list of the directories
-you can set and what kinds of files go in them.
-
-   If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
-
-Optional Features
-=================
-
-Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System).  The
-`README' should mention any `--enable-' and `--with-' options that the
-package recognizes.
-
-   For packages that use the X Window System, `configure' can usually
-find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
-
-Specifying the System Type
-==========================
-
-There may be some features `configure' cannot figure out automatically,
-but needs to determine by the type of machine the package will run on.
-Usually, assuming the package is built to be run on the _same_
-architectures, `configure' can figure that out, but if it prints a
-message saying it cannot guess the machine type, give it the
-`--build=TYPE' option.  TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name which has the form:
-
-     CPU-COMPANY-SYSTEM
-
-where SYSTEM can have one of these forms:
-
-     OS KERNEL-OS
-
-   See the file `config.sub' for the possible values of each field.  If
-`config.sub' isn't included in this package, then this package doesn't
-need to know the machine type.
-
-   If you are _building_ compiler tools for cross-compiling, you should
-use the option `--target=TYPE' to select the type of system they will
-produce code for.
-
-   If you want to _use_ a cross compiler, that generates code for a
-platform different from the build platform, you should specify the
-"host" platform (i.e., that on which the generated programs will
-eventually be run) with `--host=TYPE'.
-
-Sharing Defaults
-================
-
-If you want to set default values for `configure' scripts to share, you
-can create a site shell script called `config.site' that gives default
-values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' if it exists.  Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
-
-Defining Variables
-==================
-
-Variables not defined in a site shell script can be set in the
-environment passed to `configure'.  However, some packages may run
-configure again during the build, and the customized values of these
-variables may be lost.  In order to avoid this problem, you should set
-them in the `configure' command line, using `VAR=value'.  For example:
-
-     ./configure CC=/usr/local2/bin/gcc
-
-causes the specified `gcc' to be used as the C compiler (unless it is
-overridden in the site shell script).  Here is a another example:
-
-     /bin/bash ./configure CONFIG_SHELL=/bin/bash
-
-Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
-configuration-related scripts to be executed by `/bin/bash'.
-
-`configure' Invocation
-======================
-
-`configure' recognizes the following options to control how it operates.
-
-`--help'
-`-h'
-     Print a summary of the options to `configure', and exit.
-
-`--version'
-`-V'
-     Print the version of Autoconf used to generate the `configure'
-     script, and exit.
-
-`--cache-file=FILE'
-     Enable the cache: use and save the results of the tests in FILE,
-     traditionally `config.cache'.  FILE defaults to `/dev/null' to
-     disable caching.
-
-`--config-cache'
-`-C'
-     Alias for `--cache-file=config.cache'.
-
-`--quiet'
-`--silent'
-`-q'
-     Do not print messages saying which checks are being made.  To
-     suppress all normal output, redirect it to `/dev/null' (any error
-     messages will still be shown).
-
-`--srcdir=DIR'
-     Look for the package's source code in directory DIR.  Usually
-     `configure' can determine that directory automatically.
-
-`configure' also accepts some other, not widely useful, options.  Run
-`configure --help' for more details.
+Packager's issues
+------------------
+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.
--- a/Makefile.am
+++ b/Makefile.am
@ -1,11 +1,11 @@
 # This is the top level Makefile for Gramps
 # $Id$

-SUBDIRS = m4 po src data example
+SUBDIRS = m4 po src data example help

 EXTRA_DIST = \
-	config.rpath autogen.sh \
-	FAQ COPYING \
+	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

--- a/17
+++ b/17
@ -1,20 +1,5 @@
-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
--- a/31
+++ b/31
@ -5,10 +5,10 @@ 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.5 or greater
-   PyGTK2 2.10 or greater
-   Python Glade bindings 
-   librsvg2 (svg icon view)
+   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 
@ -16,30 +16,23 @@ The following packages are *STRONGLY RECOMMENDED* to be installed:

   GraphViz         Enable creation of graphs using GraphViz engine
                    http://www.graphviz.org
-   xdg              Freedesktop utilities, eg xdg-open
-
-The following packages are optional
-   gtkspell         Enable spell checking in the notes
-   ttf-freefont     More font support in the reports
-
-No longer needed in 3.0:
-   yelp             Gnome help browser. At the moment no help is shipped
-                    with version 3.0.


 Documentation
 ---------------------------------
-The User Manual is now maintained on the gramps website,
-http://www.gramps-project.org/wiki/index.php?title=User_manual
-We might in the future distribute again a manual via gnome-doc-utils, this has not
-been decided yet though.
+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.
-You might need a patch also. FreeBSD has in ports a patch (  /usr/ports/science/gramps/files)
-you need to apply to po/Makefile.in.in 
+


 --------------------------------
--- a/47
+++ b/47
@ -1,55 +1,16 @@
-* Remove GCONF, provide up grade path - IN PROGRESS
-
 * Replace the LPRDoc interface (based on gnome-print) with a GTK based
  print routine. This would remove one of the last gnome-specific 
  libraries, and make portability better. Even more important, the 
  gnome-print interface has been deprecated by the GNOME project, so it
-  will not be around forever. We need to adapt to the new GTK method. 
-  - IN PROGRESS
+  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. - DONE
+  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. - DONE
-
-* before release: fix command line options
-
-* remove critical bugs: 
-   - #1053 - DONE (testing of LDS privacy needed!!)
-   - #1318, wrong note backreferences - DONE
-   - #1208, relative path, see bug note for agreed solution
-
-* before release on multiple notes: 
-    --> in note: also public/private on GUI - DONE
-    --> on upgrade, the notetype should correspond to the object the note is made
-            from, so notetype SOURCE, SOURCEREF, ..., this gives information on 
-	    orphaned notes.(DONE for GRDB)
-	TODO: change notetype into note tags, so people can give notes multiple tags,
-	      Like this all source notes can have tag source, but also tag 'family history' (Discussion Alex/Benny)
-    --> in sourceref: 
-         * remove text tab. (DONE)
-         * On import of GEDCOM text tag, or upgrade of < 2.2 database, 
-           create a note with type TRANSCRIPT (DONE, type SOURCE_TEXT)
-         * On export, do not write the text tag in sourceref, write a
-           note instead (DONE)
-    --> A GrampsWidget for use in report dialogs to select which notetypes to include 
-        in a report (a filter?).
-    --> Support for multiple notes in all reports.
-    --> Empty text field on Saving Note should throw an error that Note is empty ! (?)
-    --> Undo in Note. Serious editing needs an undo function. Furthermore, the function
-        the Clear icon is unclear: tooltip? Other icon?
-
-* Remove import of global var in __init__.py, use functions or don't export. Eg.
-  PluginUtils/__init__.py export of plugin lists (tool_list, ...). E
-
-* Add forward/backward buttons (and active object) on all object views, not only person views.
-
-* Split views
-
-* Export to spreadsheet, print, CSV of views - DONE
+  shouldn't.

 * Date calculator.  See
  http://sourceforge.net/mailarchive/forum.php?thread_id=3252078&forum_id=1993
@ -66,7 +27,7 @@
  http://sourceforge.net/mailarchive/forum.php?thread_id=3134931&forum_id=1993
  for the details.

-* Move LDS temple info out of const.py and into an XML file: DONE
+* 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.
--- a/config.guess
+++ b/config.guess
--- a/config.sub
+++ b/config.sub
--- a/configure.in
+++ b/configure.in
@ -4,17 +4,14 @@ dnl Process this file with autoconf to produce a configure script.
 dnl May need to run automake && aclocal first

 AC_PREREQ(2.57)
-dnl NOTE: 1st arg to macro below becomes the "VERSION"
-AC_INIT(gramps, 3.0.0, [gramps-bugs@lists.sourceforge.net])
+AC_INIT(gramps, 2.2.7, [gramps-bugs@lists.sourceforge.net])
 AC_CONFIG_SRCDIR(configure.in)
-AM_INIT_AUTOMAKE([1.6.3 foreign])
+AM_INIT_AUTOMAKE(1.6.3)

 AC_CONFIG_MACRO_DIR([m4])
 GNOME_DOC_INIT

 dnl RELEASE=0.SVN$(svnversion -n .)
-dnl RELEASE=0beta
-dnl RELEASE=0rc1
 RELEASE=1

 VERSIONSTRING=$VERSION
@ -28,6 +25,13 @@ 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.
@ -40,17 +44,23 @@ AM_CONDITIONAL(ENABLE_SK, test "x$packager_mode" = "xfalse" -a "x$enable_scrollk
 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 bg hr sl"
+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.5
+dnl We first only check for python >= 2.3

-AM_PATH_PYTHON(2.5)
+AM_PATH_PYTHON(2.3)
 AC_PATH_PROG(BINSH, sh)

 pygtk_require="
@ -66,13 +76,13 @@ def out(line):
    f.close()
 "

-AC_MSG_CHECKING(Python bindings for gtk2.10 (pygtk2>=2.10.0))
+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,10,0):
+    if version >= (2,3,4):
        print_version = '.'.join([[str(i) for i in version]])
        out(print_version)
    else:
@ -89,7 +99,7 @@ if test NO = "$has_pygtk"
 then
   AC_MSG_ERROR([

-**** The python bindings for gtk 2.4 (pygtk2>=2.10.0) could not be found.])
+**** The python bindings for gtk 2.4 (pygtk2>=2.3.4) could not be found.])
 fi
 AC_MSG_RESULT($has_pygtk)

@ -112,10 +122,57 @@ rm -f conftest.out conftest.py
 if test NO = "$has_pygnome"
 then
   AC_MSG_ERROR([
-**** The python bindings for gnome2 (gnome2-python) could not be found.])
+**** 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
@ -142,10 +199,15 @@ 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
@ -153,6 +215,7 @@ src/DisplayTabs/Makefile
 src/DisplayModels/Makefile
 src/Selectors/Makefile
 src/GrampsLogger/Makefile
+src/GrampsDb/Makefile
 src/Merge/Makefile
 src/docgen/Makefile
 src/Editors/Makefile
@ -165,36 +228,18 @@ src/Filters/Rules/Source/Makefile
 src/Filters/Rules/Place/Makefile
 src/Filters/Rules/MediaObject/Makefile
 src/Filters/Rules/Repository/Makefile
-src/Filters/Rules/Note/Makefile
 src/Filters/SideBar/Makefile
 src/DataViews/Makefile
-src/BasicUtils/Makefile
-src/Simple/Makefile
-src/GrampsDbUtils/Makefile
-src/GrampsLocale/Makefile
 src/PluginUtils/Makefile
 src/ReportBase/Makefile
 src/plugins/Makefile
 src/DateHandler/Makefile
-src/gen/Makefile
-src/gen/proxy/Makefile
-src/gen/db/Makefile
-src/gen/lib/Makefile
-src/gen/utils/Makefile
 src/data/Makefile
-src/data/templates/Makefile
 src/glade/Makefile
 src/images/Makefile
-src/images/scalable/Makefile
-src/images/16x16/Makefile
-src/images/22x22/Makefile
-src/images/48x48/Makefile
 data/Makefile
 data/man/Makefile
 data/man/fr/Makefile
-data/man/nl/Makefile
-data/man/pl/Makefile
-data/man/sv/Makefile
 example/Makefile
 example/gramps/Makefile
 ])
--- a/data/Makefile.am
+++ b/data/Makefile.am
@ -14,16 +14,17 @@ keys_in_files = gramps.keys.in
 keys_files = $(keys_in_files:.keys.in=.keys)
@INTLTOOL_KEYS_RULE@

-schemas_in_files = gramps.schemas.in
-schemas_files = $(schemas_in_files:.schemas.in=.schemas)
-@INTLTOOL_SCHEMAS_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

@ -33,9 +34,6 @@ mime_DATA = $(keys_files) gramps.mime
 xmldir = $(SHARED_MIME_DIR)/packages
 xml_DATA = $(xml_files)

-schemasdir = $(SHARED_MIME_DIR)/packages
-schemas_DATA = $(schemas_files)
-
 pngdir = $(datadir)/icons/gnome/48x48/mimetypes
 png_DATA = \
 	gnome-mime-application-x-gramps.png \
@ -58,25 +56,37 @@ EXTRA_DIST = \
 	$(applications_DATA) \
 	$(keys_in_files) \
 	$(desktop_in_files) \
+	$(schemas_in_files) \
 	$(mime_DATA) \
 	$(xml_DATA) \
 	$(desktop_DATA) \
-	$(xml_in_files) \
 	$(schemas_DATA) \
-	$(schemas_in_files)
+	$(xml_in_files)

 CLEANFILES = \
 	$(desktop_DATA) \
 	$(keys_files) \
 	$(xml_files) \
-	$(schemas_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)
@ -88,6 +98,10 @@ endif

 install-data-hook:
 	$(SHARED_MIME_INSTALLATION)
+	$(GCONF_SCHEMAS_INSTALLATION)
+
+uninstall-local:
+	$(GCONF_SCHEMAS_UNINSTALLATION)

 uninstall-hook:
 	$(SHARED_MIME_UNINSTALLATION)
--- a/data/gramps.desktop.in
+++ b/data/gramps.desktop.in
@ -6,7 +6,7 @@ Icon=gramps.png
 Terminal=false
 Type=Application
 StartupNotify=true
-Categories=GTK;Office;
+Categories=Application;Genealogy;Office;
 X-GNOME-DocPath=gramps/gramps-manual.xml
-MimeType=application/x-gramps;application/x-gedcom;application/x-gramps-package;application/x-gramps-xml
+MimeType=application/x-gramps
 Exec=gramps %F
--- a/data/gramps.schemas.in
+++ b/data/gramps.schemas.in
@ -159,6 +159,18 @@
        </locale>
      </schema>

+      <schema>
+        <key>/schemas/apps/gramps/behavior/enable-autobackup</key>
+        <applyto>/apps/gramps/behavior/enable-autobackup</applyto>
+        <owner>gramps</owner>
+        <type>bool</type>
+        <default>1</default>
+        <locale name="C">
+          <short>Backup database on exit</short>
+          <long>If set to True, an XML backup of the database is created on exit.</long>
+        </locale>
+      </schema>
+
      <schema>
        <key>/schemas/apps/gramps/behavior/spellcheck</key>
        <applyto>/apps/gramps/behavior/spellcheck</applyto>
@ -225,18 +237,6 @@
        </locale>
      </schema>

-      <schema>
-        <key>/schemas/apps/gramps/interface/releditbtn</key>
-        <applyto>/apps/gramps/interface/releditbtn</applyto>
-        <owner>gramps</owner>
-        <type>bool</type>
-        <default>0</default>
-        <locale name="C">
-          <short>Display edit buttons in Relationship View</short>
-          <long>This key enables display of edit buttons in Relationship View</long>
-        </locale>
-      </schema>
-
      <schema>
        <key>/schemas/apps/gramps/interface/height</key>
        <applyto>/apps/gramps/interface/height</applyto>
@ -285,30 +285,6 @@
        </locale>
      </schema>

-      <schema>
-        <key>/schemas/apps/gramps/interface/note-height</key>
-        <applyto>/apps/gramps/interface/note-height</applyto>
-        <owner>gramps</owner>
-        <type>int</type>
-        <default>500</default>
-        <locale name="C">
-          <short>Height of the note editor interface.</short>
-          <long>Specifies the height of the note editor interface.</long>
-        </locale>
-      </schema>
-
-      <schema>
-        <key>/schemas/apps/gramps/interface/note-width</key>
-        <applyto>/apps/gramps/interface/note-width</applyto>
-        <owner>gramps</owner>
-        <type>int</type>
-        <default>700</default>
-        <locale name="C">
-          <short>Width of the note editor interface.</short>
-          <long>Specifies the width of the note editor interface.</long>
-        </locale>
-      </schema>
-
      <schema>
        <key>/schemas/apps/gramps/interface/person-height</key>
        <applyto>/apps/gramps/interface/person-height</applyto>
@ -586,18 +562,6 @@
        </locale>
      </schema>

-      <schema>
-        <key>/schemas/apps/gramps/behavior/database-path</key>
-        <applyto>/apps/gramps/behavior/database-path</applyto>
-        <owner>gramps</owner>
-        <type>string</type>
-        <default>~/.gramps/grampsdb</default>
-        <locale name="C">
-          <short>Additional path where the databases may reside</short>
-          <long>Additional path where the databases may reside</long>
-        </locale>
-      </schema>
-
      <schema>
        <key>/schemas/apps/gramps/preferences/fprefix</key>
        <applyto>/apps/gramps/preferences/fprefix</applyto>
@ -637,19 +601,6 @@
        </locale>
      </schema>

-      <schema>
-        <key>/schemas/apps/gramps/preferences/nprefix</key>
-        <applyto>/apps/gramps/preferences/nprefix</applyto>
-        <owner>gramps</owner>
-        <type>string</type>
-        <default>N%04d</default>
-        <locale name="C">
-          <short>Default note GRAMPS ID pattern</short>
-          <long>The new GRAMPS IDs for the notes are generated according
-          to this format string.</long>
-        </locale>
-      </schema>
-
      <schema>
        <key>/schemas/apps/gramps/preferences/iprefix</key>
        <applyto>/apps/gramps/preferences/iprefix</applyto>
@ -1202,18 +1153,5 @@
        </locale>
      </schema>

-      <schema>
-        <key>/schemas/apps/gramps/behavior/owner-warn</key>
-        <applyto>/apps/gramps/behavior/owner-warn</applyto>
-        <owner>gramps</owner>
-        <type>bool</type>
-        <default>0</default>
-        <locale name="C">
-          <short>Hide warning on missing database owner.</short>
-          <long>If set to 1, the warning about missing database owner will not
-          be displayed when GEDCOM export is done.</long>
-        </locale>
-      </schema>
-
    </schemalist>
 </gconfschemafile>
--- a/data/grampsxml.dtd
+++ b/data/grampsxml.dtd
@ -4,7 +4,7 @@
 # Gramps - a GTK+/GNOME based genealogy program
 #
 # Copyright (C) 2001 Graham J. Williams
-# Copyright (C) 2000-2007  Donald N. Allingham
+# 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
@ -24,15 +24,15 @@
 -->

 <!--
-    This is the Document Type Definition file for v1.2.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.2.0//EN"
+    "-//GRAMPS//DTD GRAMPS XML V1.1.3//EN"

    For example:
-        <!DOCTYPE database PUBLIC "-//GRAMPS//DTD GRAMPS XML V1.2.0//EN"
-                "http://gramps-project.org/xml/1.2.0/grampsxml.dtd"
+        <!DOCTYPE database PUBLIC "-//GRAMPS//DTD GRAMPS XML V1.1.3//EN"
+                "http://gramps-project.org/xml/1.1.3/grampsxml.dtd"
                [...]>
 -->

@ -47,15 +47,13 @@ DATABASE
 	sources
 	places
 	objects
-	repositories
-	notes
+        repositories
 	bookmarks
 -->

 <!ELEMENT database (header, name-formats?, events?, people?, families?,
-                    sources?, places?, objects?, repositories?, notes?,
-                    bookmarks?,namemaps?)>
-<!ATTLIST database xmlns CDATA #FIXED "http://gramps-project.org/xml/1.2.0/">
+                    sources?, places?, objects?, repositories?, bookmark?)>
+<!ATTLIST database xmlns CDATA #FIXED "http://gramps-project.org/xml/1.1.3/">

 <!--	************************************************************
 HEADER
@ -65,7 +63,7 @@ HEADER
 	person who created this genealogical database)
 -->

-<!ELEMENT header (created, researcher?, mediapath?)>
+<!ELEMENT header (created, researcher?)>

 <!ELEMENT created EMPTY>
 <!ATTLIST created
@ -84,8 +82,6 @@ HEADER
 <!ELEMENT resphone   (#PCDATA)>
 <!ELEMENT resemail   (#PCDATA)>

-<!ELEMENT mediapath  (#PCDATA)>
-
 <!--	************************************************************
 PEOPLE
 -->
@ -97,8 +93,8 @@ PEOPLE
 >

 <!ELEMENT person (gender, name*, nick?, eventref*, lds_ord*,
-                  objref*, address*, attribute*, url*, childof*,
-                  parentin*, personref*, noteref*, sourceref*)>
+                  objref*, address*, attribute*, url*,
+                  childof*,  parentin*, personref*, note?, sourceref*)>
 <!ATTLIST person
        id        CDATA #REQUIRED
        handle    ID    #REQUIRED
@ -112,8 +108,8 @@ GENDER has values of M, F, or U.
 -->
 <!ELEMENT gender  (#PCDATA)>

-<!ELEMENT name    (first?,call?,last?,suffix?,patronymic?,title?,
-                  (daterange|datespan|dateval|datestr)?,noteref*,sourceref*)>
+<!ELEMENT name    (first?,last?,suffix?,patronymic?,title?,
+                  (daterange|dateval|datestr)?,note?,sourceref*)>
 <!ATTLIST name    
        alt       (0|1) #IMPLIED
        type      CDATA #IMPLIED
@ -123,7 +119,6 @@ GENDER has values of M, F, or U.
 >

 <!ELEMENT first      (#PCDATA)>
-<!ELEMENT call       (#PCDATA)>
 <!ELEMENT last       (#PCDATA)>
 <!ATTLIST last
        prefix CDATA #IMPLIED
@ -142,15 +137,15 @@ GENDER has values of M, F, or U.
 <!ELEMENT parentin EMPTY>
 <!ATTLIST parentin hlink IDREF #REQUIRED>

-<!ELEMENT personref (sourceref*,noteref*)>
+<!ELEMENT personref (sourceref*,note?)>
 <!ATTLIST personref 
  hlink IDREF #REQUIRED
  priv  (0|1) #IMPLIED
  rel   CDATA #REQUIRED
 >

-<!ELEMENT address ((daterange|datespan|dateval|datestr)?,street?,city?,
-                   county?,state?,country?,postal?,phone?,noteref*,sourceref*)>
+<!ELEMENT address ((daterange|dateval|datestr)?,street?,city?,county?,state?,
+                   country?,postal?,phone?,note?,sourceref*)>
 <!ATTLIST address priv (0|1) #IMPLIED>

 <!ELEMENT street  (#PCDATA)>
@ -170,7 +165,7 @@ FAMILY
 <!ELEMENT families (family)*>

 <!ELEMENT family (rel?,father?,mother?,eventref*,lds_ord*,
-                  objref*,childref*,attribute*,noteref*,sourceref*)>
+                  objref*,childref*,attribute*,note?,sourceref*)>
 <!ATTLIST family
        id        CDATA #REQUIRED
        handle    ID    #REQUIRED
@ -185,7 +180,7 @@ FAMILY
 <!ELEMENT mother EMPTY>
 <!ATTLIST mother hlink IDREF #REQUIRED>

-<!ELEMENT childref (sourceref*,noteref*)>
+<!ELEMENT childref (sourceref*,note?)>
 <!ATTLIST childref
  hlink IDREF #REQUIRED
  priv  (0|1) #IMPLIED
@ -203,8 +198,8 @@ EVENT
 -->
 <!ELEMENT events (event)*>

-<!ELEMENT event (type?,(daterange|datespan|dateval|datestr)?,place?,cause?,
-                 description?,attribute*,noteref*,sourceref*,objref*)>
+<!ELEMENT event (type?,(daterange|dateval|datestr)?,place?,cause?,
+                 description?,attribute*,note?,sourceref*,objref*)>
 <!ATTLIST event 
        id        CDATA #REQUIRED
        handle    ID    #REQUIRED
@ -219,7 +214,7 @@ SOURCES

 <!ELEMENT sources (source)*>
 <!ELEMENT source (stitle?,sauthor?,spubinfo?,sabbrev?,
-                  noteref*,objref*,data_item*,reporef*)>
+                  note?,objref*,data_item*,reporef*)>
 <!ATTLIST source
        id        CDATA #REQUIRED
        handle    ID    #REQUIRED
@ -238,7 +233,7 @@ PLACES

 <!ELEMENT places (placeobj)*>

-<!ELEMENT placeobj (ptitle?,coord?,location*,objref*,url*,noteref*,sourceref*)>
+<!ELEMENT placeobj (ptitle?,coord?,location*,objref*,url*,note?,sourceref*)>
 <!ATTLIST placeobj
        id        CDATA #REQUIRED
        handle    ID    #REQUIRED
@ -273,8 +268,8 @@ OBJECTS

 <!ELEMENT objects (object)*>

-<!ELEMENT object (file,attribute*,noteref*,
-                 (daterange|datespan|dateval|datestr)?,sourceref*)>
+<!ELEMENT object (file,attribute*,note?,(daterange|dateval|datestr)?,
+		  sourceref*)>
 <!ATTLIST object
        id        CDATA #REQUIRED
        handle    ID    #REQUIRED
@ -296,7 +291,7 @@ REPOSITORIES

 <!ELEMENT repositories (repository)*>

-<!ELEMENT repository (rname,type,address*,url*,noteref*)>
+<!ELEMENT repository (rname,type,address*,url*,note?)>
 <!ATTLIST repository
        id        CDATA #REQUIRED
        handle    ID    #REQUIRED
@ -307,23 +302,6 @@ REPOSITORIES

 <!ELEMENT rname   (#PCDATA)>

-<!--	************************************************************
-NOTES
-->
-
-<!ELEMENT notes (note)*>
-
-<!ELEMENT note (#PCDATA)>
-<!ATTLIST note
-        id        CDATA #REQUIRED
-        handle    ID    #REQUIRED
-        priv      (0|1) #IMPLIED
-	marker    CDATA #IMPLIED
-	change    CDATA #REQUIRED
-	format    (0|1) #IMPLIED
-	type      CDATA #REQUIRED
->
-

 <!--	************************************************************
 BOOKMARKS
@ -336,17 +314,6 @@ BOOKMARKS
        hlink  IDREF #REQUIRED
 >

-<!--	************************************************************
-NAME MAPS
-->
-<!ELEMENT namemaps (map)*>
-<!ELEMENT map EMPTY>
-<!ATTLIST map 
-        type  CDATA #REUIRED
-        key   CDATA #REQUIRED
-        value CDATA #REQUIRED
->
-
 <!--	************************************************************
 NAME FORMATS
 -->
@ -371,14 +338,6 @@ SHARED ELEMENTS
        cformat CDATA #IMPLIED
 >

-<!ELEMENT datespan    EMPTY>
-<!ATTLIST datespan
-        start   CDATA #REQUIRED
-        stop    CDATA #REQUIRED
-        quality (estimated|calculated) #IMPLIED
-        cformat CDATA #IMPLIED
->
-
 <!ELEMENT dateval    EMPTY>
 <!ATTLIST dateval
        val     CDATA                  #REQUIRED
@ -390,42 +349,48 @@ SHARED ELEMENTS
 <!ELEMENT datestr    EMPTY>
 <!ATTLIST datestr val CDATA #REQUIRED>

-<!ELEMENT sourceref (spage?,noteref*,(daterange|datespan|dateval|datestr)?)>
+<!ELEMENT note       (#PCDATA)>
+<!ATTLIST note format (0|1) #IMPLIED>
+
+<!ELEMENT sourceref (spage?,scomments?,stext?,(daterange|dateval|datestr)?)>
 <!ATTLIST sourceref
        hlink IDREF #REQUIRED
-        priv  (0|1) #IMPLIED
        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 spage     (#PCDATA)>
+<!ELEMENT scomments (#PCDATA)>
+<!ELEMENT sdate     (#PCDATA)>
+<!ELEMENT stext     (#PCDATA)>

-<!ELEMENT attribute  (sourceref*,noteref*)>
+<!ELEMENT attribute  (sourceref*,note?)>
 <!ATTLIST attribute
        priv 	(0|1) 	#IMPLIED
        type	CDATA	#REQUIRED
        value	CDATA	#REQUIRED
 >

+<!ELEMENT comment (#PCDATA)>
+
 <!ELEMENT place EMPTY>
 <!ATTLIST place hlink IDREF #REQUIRED>

@ -440,30 +405,21 @@ SHARED ELEMENTS
        description CDATA #IMPLIED
 >

-<!ELEMENT objref (region?,reattribute*,sourceref*,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*,sourceref*)>
+<!ELEMENT lds_ord ((daterange|dateval|datestr)?,temple?,place?,status?,
+                   sealed_to?,note?,sourceref*)>
 <!ATTLIST lds_ord
-        priv  (0|1) #IMPLIED
        type   CDATA #REQUIRED
 >

--- a/data/grampsxml.rng
+++ b/data/grampsxml.rng
@ -3,7 +3,7 @@
 <!-- 
 # Gramps - a GTK+/GNOME based genealogy program
 #
-# Copyright (C) 2005-2007  Donald N. Allingham
+# 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
@ -31,7 +31,7 @@

 <grammar
  datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes"  
-  ns="http://gramps-project.org/xml/1.2.0/"
+  ns="http://gramps-project.org/xml/1.1.3/"
  xmlns="http://relaxng.org/ns/structure/1.0">

  <start><element name="database">
@ -44,7 +44,6 @@
        <optional><element name="researcher">
            <ref name="researcher-content"/>
        </element></optional>
-        <optional><element name="mediapath"><text/></element></optional>
      </element>

      <optional><element name="name-formats">
@ -99,23 +98,12 @@
          </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">
@ -182,9 +170,9 @@
        </attribute></optional>
        <attribute name="rel"><text/></attribute>
    </element></zeroOrMore>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
    <zeroOrMore><element name="sourceref">
        <ref name="sourceref-content"/>
    </element></zeroOrMore>
@ -220,7 +208,6 @@
    <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>
    <optional><element name="last">
        <text/>
        <optional><attribute name="prefix"><text/></attribute></optional>
@ -230,9 +217,9 @@
    <optional><element name="patronymic"><text/></element></optional>
    <optional><element name="title"><text/></element></optional>
    <optional><ref name="date-content"/></optional>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
    <zeroOrMore><element name="sourceref">
        <ref name="sourceref-content"/>
    </element></zeroOrMore>
@ -250,9 +237,9 @@
    <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>
+    <optional><element name="note">
+        <ref name="note-content"/>
+    </element></optional>
    <zeroOrMore><element name="sourceref">
        <ref name="sourceref-content"/>
    </element></zeroOrMore>
@ -269,15 +256,6 @@
            </choice></attribute></optional>
            <optional><attribute name="cformat"><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>
-        </element>
        <element name="dateval">
            <attribute name="val"><text/></attribute>
            <optional><attribute name="cformat"><text/></attribute></optional>
@ -332,9 +310,9 @@
    <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="sourceref">
        <ref name="sourceref-content"/>
@ -352,9 +330,9 @@
    <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>
    <zeroOrMore><element name="sourceref">
        <ref name="sourceref-content"/>
    </element></zeroOrMore>
@ -369,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>
@ -407,9 +385,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>
    <zeroOrMore><element name="sourceref">
        <ref name="sourceref-content"/>
    </element></zeroOrMore>
@ -426,9 +404,9 @@
    <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="sourceref">
        <ref name="sourceref-content"/>
@ -445,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">
@ -463,14 +441,6 @@
    <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>
@ -482,25 +452,19 @@
  </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>
    <text/>
  </define>

  <define name="sourceref-content">
    <attribute name="hlink"><data type="IDREF"/></attribute>
-    <optional><attribute name="priv">
-        <ref name="priv-content"/>
-    </attribute></optional>
    <optional><attribute name="conf"><text/></attribute></optional>
    <optional><element name="spage"><text/></element></optional>
-    <zeroOrMore><element name="noteref">
-        <ref name="noteref-content"/>
-    </element></zeroOrMore>
+    <optional><element name="scomments"><text/></element></optional>
+    <optional><element name="stext"><text/></element></optional>
    <optional><ref name="date-content"/></optional>
  </define>

@ -513,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">
@ -550,9 +507,9 @@
    <zeroOrMore><element name="sourceref">
        <ref name="sourceref-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="url-content">
@ -569,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="sourceref">
        <ref name="sourceref-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="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">
@ -601,21 +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="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>
-
 </grammar>
--- a/data/man/Makefile.am
+++ b/data/man/Makefile.am
@ -1,7 +1,7 @@
 # This is the data/man level Makefile for Gramps
 # $Id$

-SUBDIRS = fr sv nl pl
+SUBDIRS = fr

 man_IN_FILES = gramps.1.in
 man_MANS = $(man_IN_FILES:.1.in=.1)
--- a/data/man/fr/gramps.1.in
+++ b/data/man/fr/gramps.1.in
@ -1,4 +1,4 @@
-.TH gramps 1 "@VERSION@" "Février 2008" "@VERSION@"
+.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)

@ -7,10 +7,8 @@ gramps \- GRAMPS est une application de généalogie. GRAMPS est l'acronyme de G
 .RB [ \-?|\-\^\-help ]
 .RB [ \-\^\-usage ]
 .RB [ \-\^\-version ]
-.RB [ \-l]
-.RB [ \-u|\-\^\-force-unlock ]
 .RB [ \-O|\-\^\-open=
-.IR BASE_DE_DONNEES 
+.IR FICHIER 
 .RB [ \-f|\-\^\-format= 
 .IR FORMAT ]] 
 .RB [ \-i|\-\^\-import=
@ -26,13 +24,10 @@ gramps \- GRAMPS est une application de généalogie. GRAMPS est l'acronyme de G
 .RB [ \-a|\-\^\-action= 
 .IR ACTION ]
 .RB [ \-p|\-\^\-options= 
-.IR OPTION ]] 
+.IR OPTIONSTRING ]] 
 .RB [
 .IR FICHIER
 .RB ]
-.if 0 .RB [ bonobo\ options ]
-.if 0 .RB [ sound\ options ]
-.RB [ \-\-version ]

 .SH DESCRIPTION
 .PP 
@ -45,57 +40,44 @@ Il peut importer/exporter le format le plus utilisé par les autres logiciels de
 .SH OPTIONS
 .TP 
 .BI gramps " FICHIER" 
-Si \fIFICHIER\fR est désigné (sans autres commandes) comme arbre familial ou comme répertoire d'arbre familial, alors une session interactive est ouverte. Si FICHIER est un format de fichier supporté par GRAMPS, une base vide est créée dont le nom est celui du \fIFICHIER\fP et les données y seront importées. Les autres options sont ignorées. Ce type de lancement permet d'utiliser gramps pour manipuler des données comme dans un navigateur web. Les formats natifs de gramps sont acceptés, voir ci-dessous.
+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 arguments
-.ig
-\fB\-O\fR,
-..
+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 ou du type-MIME.
+\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 de sortie disponibles sont \fBgramps\-xml\fR (deviné si \fIFICHIER\fR se termine par
-\fB.gramps\fR), et \fBgedcom\fR (deviné si \fIFICHIER\fR se termine par \fB.ged\fR), ou
-tout autre fichier d'exportation disponible dans le système de plugin GRAMPS.
+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 (deviné si \fIFICHIER\fR se termine par \fB.gpkg\fR), et
-\fBgeneweb\fR (deviné si \fIFICHIER\fR se termine par \fB.gw\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  
-ig.
-\fBgrdb\fR,
-..
-\fBgramps\-xml\fR, \fBgedcom\fR,
-\fBgramps\-pkg\fR, \fBwft\fR (deviné si \fIFICHIER\fR se termine par \fB.wft\fR),
+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 \-l
-Imprime une liste des arbres familiaux disponibles.
-
-.TP
-.BI \-u,\-\^\-force-unlock
-Débloquer une base de données verrouillée.
-
-.TP 
-.BI \-O,\-\^\-open= " BASE_DE_DONNEES"
-Ouvrir une \fIBASE_DE_DONNEES\fR qui doit être une base présente dans le répertoire des bases ou le nom d'un arbre familial existant.
-Si aucune action n'est définie, les options d'import ou d'export sont données par la ligne de commande puis une session interactive est ouverte, utilisant cette base de données.
+.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 une base peut être ouverte. Si vous utilisez plusieurs sources, vous devez utiliser l'option d'import.
+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. 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.
+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, 
@ -105,11 +87,7 @@ et \fB\-i\fR \fIFICHIER2\fR \fB\-i\fR \fIFICHIER1\fR vont tous les deux produire
 .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 
-.ig
-\fBgrdb\fR,
-..
-\fBgramps\-xml\fR, \fBgedcom\fR, \fBwft\fR, \fBgramps\-pkg\fR, 
+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

@ -118,12 +96,11 @@ Quand plus d'un fichier doit être exporté, chacun doit être précédé par la
 .TP 
 .BI \-a,\-\^\-action= " ACTION"
 Accomplir une \fIACTION\fR sur les données importées. C'est effectué à la fin de l'importation. Les actions possibles sont \fBsummary\fR 
-(comme le rapport -> Afficher -> Statistiques sur la base), \fBcheck\fR (comme l'outil -> Réparation de la base -> Vérifier et réparer), \fBreport\fR (produit un rapport) et
-\fBtool\fR (utilise un outil), ces derniers ont besoin
-de \fIOPTION\fR précédé par la commande \fB\-p\fR.
+(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

-L'\fIOPTION\fR doit satisfaire ces conditions:
+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.
@ -134,17 +111,17 @@ 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.

-.BI "name=name"
+.BI "name=reportname "
 .br
-Cette option est obligatoire, elle détermine quel rapport ou outil sera utilisé. Si le \fIname\fR saisi ne correspond à aucun module disponible, un message d'erreur sera ajouté.
+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
+.BI "show=optionname"
 .br
-Cette option affiche une description de toutes les fonctionnalités proposées par \fIoptionname\fR, aussi bien les types que les valeurs pour une option.
+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.
@ -152,45 +129,10 @@ Utiliser les options ci-dessus pour trouver tout sur un rapport choisi.
 .LP
 Quand plus d'une action doit être effectuée, chacune doit être précédée par la commande \fB\-a\fR. Les actions seront réalisées une à une, dans l'ordre spécifié.

-.TP 
-.BI \-d,\-\^\-debug= " NOM_LOGGER"
-Permet les logs de debug pour le développement et les tests. Regarder le code source pour les détails.
-.TP
-.BI \-\^\-version
-Imprime le numéro de version pour gramps puis quitte.
-\" changer 0 par 1 pour permettre la sortie des options OAF
-.si 0 \{
-.PP
-Les options suivantes seront utilisées pour l'activation Bonobo.
-.TP 
-.BI \-\^\-oaf-ior-fd= "FD"
-Le descripteur de fichier pour imprimer OAF IOR
-.TP 
-.BI \-\^\-oaf-activate-iid= " IID"
-OAF IID à activer
-.TP 
-.BI \-\^\-oaf-private
-Prévenir de l'enregistrement du serveur avec OAF
-\}
-\" changer 0 par 1 pour permettre la sortie des options son de GNOME
-.si 0 \{
-.PP
-Les options suivantes seront utilisées pour contrôler le son avec les librairies GNOME.
-.TP
-.BI \-\^\-disable-sound
-Désactive l'utilisation du server son
-.TP
-.BI \-\^\-enable-sound
-Active l'utilisation du server son
-.TP
-.BI \-\^\-espeaker= " HOSTNAME:PORT"
-Host:port sur lequel le serveur son sera utilisé
-\}
-
-.SH "Operation"
+.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 la base de données avec le nom donné par le premier argument et démarrer une session interactive, en ignorant le reste de la ligne de commande.
+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.
@ -214,13 +156,7 @@ en \fIstderr\fR (si elles ne sont pas le fait d'une manipulation). Utilisez les
 \fIstdout\fR et \fIstderr\fR pour sauver les messages et les erreurs dans les fichiers.

 .SH EXEMPLES
-.TP
-Pour ouvrir un arbre familial et y importer un fichier XML, on peut saisir: 
-\fBgramps\fR \fB\-O\fR \fI'Mon Arbre Familal'\fR \fB\-i\fR \fI~/db3.gramps\fR
 .TP 
-Ceci ouvre un arbre familal, pour faire la même chose, mais importer dans un arbre familial temporaire et démarrer une session interactive, on peut saisir: 
-\fBgramps\fR \fB\-i\fR \fI'Mon Arbre Familal'\fR \fB\-i\fR \fI~/db3.gramps\fR
-.TP  
 Lecture de quatre bases de données dont les formats peuvent être devinés d'après les noms, puis vérification des données: 
 \fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-i\fR \fIfile4.wft\fR \fB\-a\fR \fIcheck\fR 
 .TP 
@ -233,9 +169,6 @@ Pour enregistrer le résultat des lectures, donnez l'option  \fB\-o\fR (utiliser
 Pour lire trois ensembles de données puis lancer une session interactive de gramps sur le tout : 
 \fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR 
 .TP 
-Pour lancer l'outil de vérification de la base de données depuis la ligne de commande et obtenir le résultat: 
-\fBgramps\fR \fB\-O\fR \fIfile.grdb\fR \fB-a\fR \fItool\fR \fB-p\fR \fBname\fR=\fIverify\fR
-.TP
 Enfin, pour lancer une session interactive normale, entrer : \fBgramps\fR 

 .SH CONCEPTS
@ -268,7 +201,7 @@ pour Debian GNU/Linux système.
 .LP 
 Cette page man est maintenue par:
 .br 
-Gramps project \fI<xxx@gramps-project.org>\fR
+Alex Roitman \fI<shura@gramps-project.org>\fR
 .LP 
 La traduction française:
 .br 
--- a/data/man/gramps.1.in
+++ b/data/man/gramps.1.in
@ -1,4 +1,4 @@
-.TH gramps 1 "@VERSION@" "January 2008" "@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=
@ -26,13 +24,10 @@ gramps \- Genealogical Research and Analysis Management Programming System.
 .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\-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 or MIME-type. 
+the format of that file is guessed according to its extension. 
 .br

 Formats 
-available for output 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 
@ -117,11 +100,7 @@ gramps IDs in the resulting database.
 .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
-.ig
-\fBgrdb\fR,
-..
-\fBgramps\-xml\fR, \fBgedcom\fR, \fBwft\fR, \fBgramps\-pkg\fR, 
+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

@ -131,43 +110,41 @@ 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
@ -178,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
@ -222,7 +164,7 @@ 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
@ -248,18 +190,12 @@ 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 
@ -272,9 +208,6 @@ To record the database resulting from all imports, supply \fB\-o\fR flag (use \f
 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 

@ -310,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
--- a/data/man/nl/Makefile.am
+++ b/data/man/nl/Makefile.am
@ -1,15 +0,0 @@
-# This is the data/man/nl level Makefile for Gramps
-# $Id: Makefile.am 9819 2008-01-15 15:42:10Z bmcage $
-
-mandir = @mandir@/nl
-
-man_IN_FILES = gramps.1.in
-man_MANS = $(man_IN_FILES:.1.in=.1)
-
-EXTRA_DIST = $(man_MANS) $(man_IN_FILES)
-
-gramps.1: $(top_builddir)/config.status gramps.1.in
-	cd $(top_builddir) && CONFIG_FILES=data/man/nl/$@ $(SHELL) ./config.status
-
-CLEANFILES=$(man_MANS)
-
--- a/data/man/nl/gramps.1.in
+++ b/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 [ \-o|\-\^\-output= 
-.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\-o\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 \-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
-.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\-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), 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\-o\fR, and \fB\-a\fR flags.  
-
-.LP
-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!
-
-.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\-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 
-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. 
--- a/data/man/pl/Makefile.am
+++ b/data/man/pl/Makefile.am
@ -1,14 +0,0 @@
-# This is the data/man/pl level Makefile for Gramps
-# $Id: Makefile.am 6189 2006-03-21 19:05:46Z rshura $
-
-man_IN_FILES = gramps.1.in
-man_MANS = $(man_IN_FILES:.1.in=.1)
-
-mandir = @mandir@/pl
-
-EXTRA_DIST = $(man_MANS) $(man_IN_FILES)
-
-gramps.1: $(top_builddir)/config.status gramps.1.in
-	cd $(top_builddir) && CONFIG_FILES=data/man/pl/$@ $(SHELL) ./config.status
-
-CLEANFILES=$(man_MANS)
--- a/data/man/pl/gramps.1.in
+++ b/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 [ \-o|\-\^\-output= 
-.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\-o\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 \-o,\-\^\-output= " 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\-o\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\-o\fR, oraz \fB\-a\fR .  
-
-.LP
-Kolejność podawania opcji \fB\-i\fR, \fB\-o\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\-o\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\-o\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\-o\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. 
--- a/data/man/sv/Makefile.am
+++ b/data/man/sv/Makefile.am
@ -1,14 +0,0 @@
-# This is the data/man/sv level Makefile for Gramps
-# $Id: Makefile.am 6189 2006-03-21 19:05:46Z rshura $
-
-man_IN_FILES = gramps.1.in
-man_MANS = $(man_IN_FILES:.1.in=.1)
-
-mandir = @mandir@/sv
-
-EXTRA_DIST = $(man_MANS) $(man_IN_FILES)
-
-gramps.1: $(top_builddir)/config.status gramps.1.in
-	cd $(top_builddir) && CONFIG_FILES=data/man/sv/$@ $(SHELL) ./config.status
-
-CLEANFILES=$(man_MANS)
--- a/data/man/sv/gramps.1.in
+++ b/data/man/sv/gramps.1.in
@ -1,316 +0,0 @@
-.TH gramps 3 "@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 [ \-o|\-\^\-output= 
-.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örså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\-o\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 \-o,\-\^\-output= " 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\-o\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\-o\fR- samt \fB\-a\fR-flaggor. 
-
-.LP
-Ordningen på \fB\-i\fR-, \fB\-o\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 valiga interaktiva sessionen med en tom databas,
-då hur som helst inget data finns att bearbeta.
-
-.LP
-Om inget \fB\-o\fR- eller \fB\-a\fR-alternativ givits, kommer gramps att starta sitt 
-huvudfönster samt påbörja den valiga 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\-o\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\-o\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. 
--- a/debian/changelog
+++ b/debian/changelog
@ -1,9 +1,3 @@
-gramps (2.90.0-0beta) unstable; urgency=low
-
-  * New upstream release
-
- -- Stephane Charette <stephanecharette@gmail.com>  Wed, 16 Jan 2008 21:45:00 -0800
-
 gramps (2.1.6-1) unstable; urgency=low

  * New upstream release
--- a/debian/rules
+++ b/debian/rules
@ -47,7 +47,7 @@ install: build
 	#chmod 644 debian/gramps/usr/share/pixmaps/gramps.svg

 	# Instal gramps-help things
-	#$(MAKE) -C help install DESTDIR=`pwd`/debian/gramps-help
+	$(MAKE) -C help install DESTDIR=`pwd`/debian/gramps-help

 # Build architecture-independent files here.
 binary-indep: build install
@ -58,9 +58,9 @@ binary-indep: build install
 	dh_installman --package=gramps
 	dh_installmime -i
 	dh_installchangelogs --package=gramps ChangeLog
-	#dh_installchangelogs --package=gramps-help help/ChangeLog
+	dh_installchangelogs --package=gramps-help help/ChangeLog
 	dh_gconf --package=gramps
-	#dh_scrollkeeper --package=gramps-help
+	dh_scrollkeeper --package=gramps-help
 	dh_compress -i
 	dh_fixperms -i
 	dh_python  --package=gramps
--- a/example/gedcom/sample.ged
+++ b/example/gedcom/sample.ged
--- a/example/gramps/data.gramps
+++ b/example/gramps/data.gramps
--- a/example/gramps/example.gramps
+++ b/example/gramps/example.gramps
--- a/gramps.sh.in
+++ b/gramps.sh.in
@ -21,8 +21,19 @@
 #

 prefix=@prefix@
+exec_prefix=@exec_prefix@
 PACKAGE=@PACKAGE@

 export GRAMPSDIR=@datadir@/@PACKAGE@
+export GRAMPSPLUGINSDIR=$GRAMPDIR/plugins:$GRAMPSDIR/docgen
+export GRAMPSLIBDIR=@libdir@/@PACKAGE@
+export GRAMPSI18N=@prefix@/share/locale
+
+if [ "$PYTHONPATH" = "" ]
+then
+    export PYTHONPATH=$GRAMPSDIR:$GRAMPSPLUGINSDIR:$GRAMPSLIBDIR
+else
+    export PYTHONPATH=$GRAMPSDIR:$GRAMPSLIBDIR:$GRAMPSPLUGINSDIR:$PYTHONPATH
+fi

 exec @PYTHON@ $GRAMPSDIR/gramps.py "$@"
--- a/gramps.spec.in
+++ b/gramps.spec.in
@ -0,0 +1,127 @@
+%define ver      @VERSION@
+%define rel      @RELEASE@
+%define prefix   /usr
+%define localstatedir /var/lib
+%define _prefix   %prefix
+%define _localstatedir %localstatedir
+
+Summary: Genealogical Research and Analysis Management Programming System.
+Name: gramps
+Version: %{ver}
+License: GPL
+Group: Applications/Genealogy
+Source: http://download.sourceforge.net/gramps/gramps-%{ver}.tar.gz
+BuildRoot: /var/tmp/%{name}-%{version}-root
+URL: http://gramps.sourceforge.net/
+Release: %{rel}fdr3
+Distribution: Fedora Core 3
+
+Requires: python >= 2.3
+Requires: gnome-python2 >= 2.6.0
+Requires: gnome-python2-gconf >= 2.6.0
+Requires: gnome-python2-canvas >= 2.6.0
+Requires: gnome-python2-gnomevfs >= 2.6.0
+Requires: pygtk2 >= 2.4.0
+Requires: pygtk2-libglade >= 2.4.0
+
+BuildRequires: scrollkeeper >= @SCROLLKEEPER_BUILD_REQUIRED@
+BuildRequires: automake >= 1.6
+BuildRequires: rpm >= 4.1
+BuildRequires: desktop-file-utils >= 0.2.92
+
+%description
+gramps (Genealogical Research and Analysis Management Programming
+System) is a GNOME based genealogy program supporting a Python
+based plugin system.
+
+%prep
+%setup
+
+%build
+if [ ! -f configure ]; then
+  CFLAGS="$MYCFLAGS" ./autogen.sh $MYARCH_FLAGS --prefix=%prefix \
+    --localstatedir=%localstatedir --bindir=%{_bindir} \
+    --mandir=%{_mandir} --libdir=%{_libdir} --datadir=%{_datadir} \
+    --includedir=%{_includedir} --sysconfdir=%{_sysconfdir}
+else
+  CFLAGS="$MYCFLAGS" %configure
+fi
+
+CFLAGS="$RPM_OPT_FLAGS" make
+
+%install
+rm -rf $RPM_BUILD_ROOT
+
+%makeinstall
+mkdir -p $RPM_BUILD_ROOT%{_datadir}/applications
+desktop-file-install --vendor gramps --delete-original \
+	--dir $RPM_BUILD_ROOT%{_datadir}/applications  \
+	--add-category Application                     \
+	--add-category Utility                         \
+	src/data/gramps.desktop
+%find_lang gramps
+rm -rf $RPM_BUILD_ROOT/%{_localstatedir}/scrollkeeper/
+rm -rf $RPM_BUILD_ROOT/%{_datadir}/mime/application
+rm -rf $RPM_BUILD_ROOT/%{_datadir}/mime/{globs,magic,XMLnamespaces}
+
+%clean
+rm -rf $RPM_BUILD_ROOT
+
+%files -f gramps.lang
+%defattr(-, root, root)
+
+%doc AUTHORS COPYING COPYING-DOCS ChangeLog FAQ INSTALL NEWS README TODO 
+%doc %{_mandir}/man1/*
+
+%{prefix}/bin/gramps
+
+%{_datadir}/applications/*
+
+%{_datadir}/gramps
+%{_datadir}/omf/gramps
+%{_datadir}/mime-info/*
+%{_datadir}/icons/gnome/48x48/mimetypes/*
+%{_sysconfdir}/gconf/schemas/gramps.schemas
+%{_datadir}/application-registry/gramps.applications
+%{_datadir}/mime/packages/gramps.xml
+
+%post
+GCONF_CONFIG_SOURCE=`@GCONFTOOL@ --get-default-source` \
+  @GCONFTOOL@ --makefile-install-rule \
+	%{_sysconfdir}/gconf/schemas/gramps.schemas > /dev/null
+/usr/bin/update-desktop-database %{_datadir}/applications &> /dev/null
+/usr/bin/update-mime-database %{_datadir}/mime &> /dev/null
+if which scrollkeeper-update>/dev/null 2>&1; then scrollkeeper-update; fi
+/usr/bin/pkill gconfd || /bin/true
+
+%postun
+if which scrollkeeper-update>/dev/null 2>&1; then scrollkeeper-update; fi
+if [ "$1" = "0" ]; then
+  /usr/bin/update-desktop-database %{_datadir}/applications &> /dev/null
+  /usr/bin/update-mime-database %{_datadir}/mime &> /dev/null
+fi
+ 
+%changelog
+* Tue Aug 31 2004 Tim Waugh <twaugh@redhat.com>
+- Update MIME database in scriptlets.
+
+* Tue Dec  2 2003 Tim Waugh <twaugh@redhat.com>
+- More docs.
+- Change Copyright: to License:.
+
+* Fri Sep 19 2003 Tim Waugh <twaugh@redhat.com>
+- Own %%{_datadir/gramps directory.
+- Ship %%{_libdir}/gramps.
+* Mon May 20 2003 Donald Peterson <dpeterson@sigmaxi.org>
+- Override RPMs default of localstatedir to /var/lib..
+  This is done in accordance with GNOME and FHS compliance guidelines 
+  (http://fedora.mplug.org/docs/rpm-packaging-guidelines.html)
+- Use %find_lang macro to get NLS files
+- Set %doc tags on appropriate files
+- Remove temporary scrollkeeper-created files from install before packaging
+  to avoid rpm 4.1 complaints.  (These aren't needed in the distribution.)
+- Use default scrollkeeper-update scripts
+* Mon Mar 24 2003 Alex Roitman <shura@alex.neuro.umn.edu>
+- update scrollkeeper dependencies and add post and postun to enable install on a machine without scrollkeeper
+* Fri Jun 14 2002 Donald Peterson <dpeterso@engr.ors.edu>
+- add scrollkeeper dependencies and some file cleanup
--- a/help/C/figures/bookreport.png
+++ b/help/C/figures/bookreport.png
--- a/help/C/figures/cfe-ar.png
+++ b/help/C/figures/cfe-ar.png
--- a/help/C/figures/cfe-df.png
+++ b/help/C/figures/cfe-df.png
--- a/help/C/figures/child-ref.png
+++ b/help/C/figures/child-ref.png
--- a/help/C/figures/column-editor.png
+++ b/help/C/figures/column-editor.png
--- a/help/C/figures/comp-people.png
+++ b/help/C/figures/comp-people.png
--- a/help/C/figures/date-selection.png
+++ b/help/C/figures/date-selection.png
--- a/help/C/figures/edit-ad.png
+++ b/help/C/figures/edit-ad.png
--- a/help/C/figures/edit-an.png
+++ b/help/C/figures/edit-an.png
--- a/help/C/figures/edit-at.png
+++ b/help/C/figures/edit-at.png
--- a/help/C/figures/edit-bm.png
+++ b/help/C/figures/edit-bm.png
--- a/help/C/figures/edit-ev-ref.png
+++ b/help/C/figures/edit-ev-ref.png
--- a/help/C/figures/edit-ev.png
+++ b/help/C/figures/edit-ev.png
--- a/help/C/figures/edit-family.png
+++ b/help/C/figures/edit-family.png
--- a/help/C/figures/edit-media.png
+++ b/help/C/figures/edit-media.png
--- a/help/C/figures/edit-person-addresses.png
+++ b/help/C/figures/edit-person-addresses.png
--- a/help/C/figures/edit-person-assoc.png
+++ b/help/C/figures/edit-person-assoc.png
--- a/help/C/figures/edit-person-attributes.png
+++ b/help/C/figures/edit-person-attributes.png
--- a/help/C/figures/edit-person-gallery.png
+++ b/help/C/figures/edit-person-gallery.png
--- a/help/C/figures/edit-person-internet.png
+++ b/help/C/figures/edit-person-internet.png
--- a/help/C/figures/edit-person-lds.png
+++ b/help/C/figures/edit-person-lds.png
--- a/help/C/figures/edit-person-names.png
+++ b/help/C/figures/edit-person-names.png
--- a/help/C/figures/edit-person-notes.png
+++ b/help/C/figures/edit-person-notes.png
--- a/help/C/figures/edit-person-sources.png
+++ b/help/C/figures/edit-person-sources.png
--- a/help/C/figures/edit-person.png
+++ b/help/C/figures/edit-person.png
--- a/help/C/figures/edit-plc.png
+++ b/help/C/figures/edit-plc.png
--- a/help/C/figures/edit-rel.png
+++ b/help/C/figures/edit-rel.png
--- a/help/C/figures/edit-si.png
+++ b/help/C/figures/edit-si.png
--- a/help/C/figures/edit-src.png
+++ b/help/C/figures/edit-src.png
--- a/help/C/figures/events.png
+++ b/help/C/figures/events.png
--- a/help/C/figures/export-druid.png
+++ b/help/C/figures/export-druid.png
--- a/help/C/figures/family-list.png
+++ b/help/C/figures/family-list.png
--- a/help/C/figures/family-warn.png
+++ b/help/C/figures/family-warn.png
--- a/help/C/figures/family.png
+++ b/help/C/figures/family.png
--- a/help/C/figures/find-people.png
+++ b/help/C/figures/find-people.png
--- a/help/C/figures/first-open.png
+++ b/help/C/figures/first-open.png
--- a/help/C/figures/gedcom-export.png
+++ b/help/C/figures/gedcom-export.png
--- a/help/C/figures/mainwin.png
+++ b/help/C/figures/mainwin.png
--- a/help/C/figures/media.png
+++ b/help/C/figures/media.png
--- a/help/C/figures/merge-people.png
+++ b/help/C/figures/merge-people.png
--- a/help/C/figures/merge-plc.png
+++ b/help/C/figures/merge-plc.png
--- a/help/C/figures/merge-src.png
+++ b/help/C/figures/merge-src.png
--- a/help/C/figures/noside-nofilt.png
+++ b/help/C/figures/noside-nofilt.png
--- a/help/C/figures/pedigree-child-cut.png
+++ b/help/C/figures/pedigree-child-cut.png
--- a/help/C/figures/pedigree-siblings-cut.png
+++ b/help/C/figures/pedigree-siblings-cut.png
--- a/help/C/figures/pedigree.png
+++ b/help/C/figures/pedigree.png
--- a/help/C/figures/places.png
+++ b/help/C/figures/places.png
--- a/help/C/figures/prefs.png
+++ b/help/C/figures/prefs.png
--- a/help/C/figures/reorder.png
+++ b/help/C/figures/reorder.png
--- a/help/C/figures/repository.png
+++ b/help/C/figures/repository.png
--- a/help/C/figures/researcher.png
+++ b/help/C/figures/researcher.png
--- a/help/C/figures/scratch-pad.png
+++ b/help/C/figures/scratch-pad.png
--- a/help/C/figures/select-family.png
+++ b/help/C/figures/select-family.png
--- a/help/C/figures/select-person.png
+++ b/help/C/figures/select-person.png
--- a/help/C/figures/side-filt.png
+++ b/help/C/figures/side-filt.png
--- a/help/C/figures/sources.png
+++ b/help/C/figures/sources.png
--- a/help/C/gramps.xml
+++ b/help/C/gramps.xml
--- a/help/COPYING-DOCS
+++ b/help/COPYING-DOCS
@ -1,13 +0,0 @@
-For version 3.0, the manual can be found dual licenced under the GNU GPL and under GNU Free Documentation License 1.2 on our wiki: http://www.gramps-project.org/wiki/index.php?title=Gramps_3.0_Wiki_Manual
-
-For version 2.x, the manual can be found in branch22 of the SVN repository, under the GNU GPL license.
-
-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.
-
-Benny Malengier
-January 15, 2008
-
-$Id$
--- a/help/ChangeLog
+++ b/help/ChangeLog
@ -1,14 +1,18 @@
-2008-01-15  Benny Malengier <benny.malengier@gramps-project.org>
-	* Removed 2.2 manual, at the moment no manual of gramps is kept in SVN,
-	  it can only be found on the wiki.
-	* help/gramps.omf.in: removed
-	* help/gramps.pot: removed
-	* help/Makefile.am: removed
+2007-02-23  Alex Roitman  <shura@gramps-project.org>
+	* C/gramps.xml: List Don just once, as a maintainer.
+	* output/Makefile.am (HELP_LINGUAS): Disable nb for now;
+	(fo): Generate fo output.

-2007-06-25  Alex Roitman  <shura@gramps-project.org>
-	* de/de.po: Add file from 2.2.
-	* de/figures/*.png: Add files from 2.2.
-	* Makefile.am: Enable building of German manual.
+	* output/gramps-help-screen.css: Modify css to see revision
+	history by the main text.
+
+2007-02-22  Alex Roitman  <shura@gramps-project.org>
+	* output/Makefile.am: Write rule for manual website creation.
+
+2007-02-16  Alex Roitman  <shura@gramps-project.org>
+	* help/nl: Add svn:ignore property.
+	* various: Add stuff for generating html and pdf output.
+	* Makefile.am (SUBDIRS): Add subdirs.

 2007-02-13  Lubo Vasko  <pgval@inMail.sk>
 	* sk/figures/*.png : Update.
--- a/help/Makefile.am
+++ b/help/Makefile.am
@ -0,0 +1,71 @@
+# This is the help level Makefile for gramps
+# $Id$
+
+SUBDIRS = output
+
+include $(top_srcdir)/gnome-doc-utils.make
+dist-hook: doc-dist-hook
+
+DOC_MODULE = gramps
+DOC_ENTITIES = gramps.xml
+
+DOC_FIGURES = \
+	figures/bookreport.png\
+	figures/cfe-ar.png\
+	figures/cfe-df.png\
+	figures/child-ref.png\
+	figures/column-editor.png\
+	figures/comp-people.png\
+	figures/date-selection.png\
+	figures/edit-ad.png\
+	figures/edit-an.png\
+	figures/edit-at.png\
+	figures/edit-bm.png\
+	figures/edit-ev.png\
+	figures/edit-ev-ref.png\
+	figures/edit-family.png\
+	figures/edit-media.png\
+	figures/edit-person-addresses.png\
+	figures/edit-person-assoc.png\
+	figures/edit-person-attributes.png\
+	figures/edit-person-gallery.png\
+	figures/edit-person-internet.png\
+	figures/edit-person-lds.png\
+	figures/edit-person-names.png\
+	figures/edit-person-notes.png\
+	figures/edit-person.png\
+	figures/edit-person-sources.png\
+	figures/edit-plc.png\
+	figures/edit-rel.png\
+	figures/edit-si.png\
+	figures/edit-src.png\
+	figures/events.png\
+	figures/export-druid.png\
+	figures/family-list.png\
+	figures/family.png\
+	figures/family-warn.png\
+	figures/find-people.png\
+	figures/first-open.png\
+	figures/gedcom-export.png\
+	figures/mainwin.png\
+	figures/media.png\
+	figures/merge-people.png\
+	figures/merge-plc.png\
+	figures/merge-src.png\
+	figures/noside-nofilt.png\
+	figures/pedigree-child-cut.png\
+	figures/pedigree.png\
+	figures/pedigree-siblings-cut.png\
+	figures/places.png\
+	figures/prefs.png\
+	figures/reorder.png\
+	figures/repository.png\
+	figures/researcher.png\
+	figures/scratch-pad.png\
+	figures/select-family.png\
+	figures/select-person.png\
+	figures/side-filt.png\
+	figures/sources.png
+
+DOC_LINGUAS = fr nb sk nl
+#de fr hu ru
--- a/help/README-DOCS
+++ b/help/README-DOCS
@ -1 +0,0 @@
-As of version 3.0 the help manual is no longer maintained in svn, but on the wiki instead.
--- a/help/de/de.po
+++ b/help/de/de.po
--- a/help/de/figures/bookreport.png
+++ b/help/de/figures/bookreport.png
--- a/help/de/figures/cfe-ar.png
+++ b/help/de/figures/cfe-ar.png
--- a/help/de/figures/cfe-df.png
+++ b/help/de/figures/cfe-df.png
--- a/help/de/figures/child-ref.png
+++ b/help/de/figures/child-ref.png
--- a/help/de/figures/column-editor.png
+++ b/help/de/figures/column-editor.png
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Don Allingham	6b16e40db3	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	2007-04-22 20:58:07 +00:00
Brian Matherly	fa1b3d706c	Escape still wasn't right in ODFDoc.py. Ancestor and descendant charts were displaying wrong. svn: r8417	2007-04-22 13:19:05 +00:00
Brian Matherly	df18340c21	0000970: _IsBookmarked.py causes crash svn: r8415	2007-04-21 18:48:04 +00:00
Don Allingham	7cbe7f797b	2007-04-20 Don Allingham <don@gramps-project.org> * src/GrampsDb/_ReadGedcom.py: fix calendar parsing * src/GrampsDb/_WriteGedcom.py: fix calendar generation svn: r8412	2007-04-21 04:30:13 +00:00
Alex Roitman	6cc84e39cf	2007-04-20 Alex Roitman <shura@gramps-project.org> * src/plugins/Checkpoint.py (Checkpoint.rcs): Remove debugging output; Work out retrieval. svn: r8411	2007-04-21 02:50:11 +00:00
Don Allingham	2c1aa909e5	2007-04-20 Don Allingham <don@gramps-project.org> * src/DisplayModels/_BaseModel.py (BaseModel.add_row_by_handle): if search not defined, do an insert svn: r8410	2007-04-20 15:09:22 +00:00
Jérôme Rapinat	9eff5e9327	add German translation for manual svn: r8409	2007-04-20 06:59:19 +00:00
Jérôme Rapinat	5767ac5bbd	add German translation for manual svn: r8408	2007-04-20 06:56:22 +00:00
Jérôme Rapinat	9d4d7ca873	add German translation for manual svn: r8407	2007-04-20 06:53:04 +00:00
Brian Matherly	c324efb9e4	PROPERLY escape ampersands in ODFDoc.py svn: r8405	2007-04-20 03:48:21 +00:00
Don Allingham	60a072824f	2007-04-18 Don Allingham <don@gramps-project.org> * src/plugins/BookReport.py: escape xml constructs (bug 877) * src/PluginUtils/_Options.py: escape xml constructs (bug 877) svn: r8403	2007-04-19 02:03:29 +00:00
Jérôme Rapinat	eb7b977237	update French translation for 2.2.7 svn: r8401	2007-04-18 16:11:20 +00:00
Don Allingham	71162563ed	2007-04-17 Don Allingham <don@gramps-project.org> * src/Editors/_EditRepository.py: fix double click save bug * src/Editors/_EditSource.py: fix double click save bug * src/Editors/_EditEvent.py: fix double click save bug * src/Editors/_EditPlace.py: fix double click save bug * src/Editors/_EditFamily.py (EditFamily.save): fix potential double click of Family Editor dialog svn: r8399	2007-04-18 03:59:34 +00:00
Alex Roitman	2a3ef69c9e	2007-04-17 Lubo Vasko <pgval@inMail.sk> * sk.po: Translation update. 2007-04-17 Piotr Czubaszek <pioterus@gmail.com> * pl.po: Translation update. svn: r8397	2007-04-18 00:36:25 +00:00
Kees Bakker	1305e3b037	* po/nl.po Some corrections by Erik svn: r8396	2007-04-17 19:13:10 +00:00
Kees Bakker	e9fa8f1cfc	Just a msgmerge with the nl.po and new gramps.pot so that Erik can do the changes. svn: r8395	2007-04-17 17:48:52 +00:00
Arturas Sleinius	c397c43701	Updated Lithuanian translation svn: r8394	2007-04-17 17:21:40 +00:00
Martin Hawlisch	260f5f2422	* de.po: translation update svn: r8392	2007-04-16 16:12:34 +00:00
Martin Hawlisch	6b35940eac	* src/ViewManager.py (create_pages): fix off-by-one error when preselecting last view svn: r8390	2007-04-16 13:53:55 +00:00
Jérôme Rapinat	12a002b945	update French translation for 2.2.7 svn: r8389	2007-04-16 09:19:42 +00:00
Jérôme Rapinat	a6a8cdff0f	improve French translation for manual svn: r8388	2007-04-16 09:19:11 +00:00
Don Allingham	2174fcbd99	* po/gramps.pot: update for 2.2.7 preparation 2007-04-15 Don Allingham <don@gramps-project.org> svn: r8387	2007-04-16 01:23:06 +00:00
Don Allingham	43e3bf68cd	2007-04-15 Don Allingham <don@gramps-project.org> * src/GrampsDb/_WriteGedcom.py: use CONT to continue page info * src/GrampsDb/_GrampsBSDDB.py: additional error checking * src/QuestionDialog.py: enable markup * src/DbLoader.py: additional error checking * src/plugins/NarrativeWeb.py * src/ReportBase/_ReportUtils.py 0001012: Private source and private child references shown in narrative website. 0001017: Insufficient space in pedigree view of narrative website svn: r8386	2007-04-16 01:19:46 +00:00
Brian Matherly	6468dc2a23	0001012: Private source and private child references shown in narrative website. svn: r8384	2007-04-15 19:09:55 +00:00
Brian Matherly	670eef2da8	0001017: Insufficient space in pedigree view of narrative website svn: r8382	2007-04-15 02:17:44 +00:00
Brian Matherly	061a9e2761	0000908: GtkPrint doesn't parse if you don't have pygtk version 2.10 svn: r8381	2007-04-13 18:11:05 +00:00
Brian Matherly	4cb1aaacd1	0001011: XML import loses media objects when media object has no title. svn: r8379	2007-04-12 11:46:36 +00:00
Don Allingham	28dc889abb	2007-04-11 Don Allingham <don@gramps-project.org> * src/GrampsDb/_WriteGedcom.py (GedcomWriter.write_source_ref): replace newlines with semicolons on output. svn: r8378	2007-04-12 02:29:52 +00:00
Don Allingham	0408153557	2007-04-10 Don Allingham <don@gramps-project.org> * src/GrampsDb/_ReadGedcom.py: add hack to force illegal "BET ABT" to be read as "EST BET" * src/ReportBase/_BareReportDialog.py: escape ampersands * src/docgen/ODFDoc.py: escape ampersands * src/ManagedWindow.py: escape ampersands svn: r8377	2007-04-11 04:54:38 +00:00
Kees Bakker	fc39402cc4	* po/nl.po: a few corrections of the translation * src/DateHandler/_Date_nl.py: Numerisch => Numeriek svn: r8376	2007-04-10 19:32:49 +00:00
Martin Hawlisch	c62bef3f21	* src/plugins/ImportGeneWeb.py: Some parsing enhancements svn: r8375	2007-04-10 19:22:44 +00:00
Don Allingham	c531d2fad7	* src/plugins/Check.py (CheckIntegrity.check_events): don't require same gender for civil unions svn: r8374	2007-04-10 03:35:04 +00:00
Don Allingham	18908e7716	2007-04-09 Don Allingham <don@gramps-project.org> * src/GrampsDb/_WriteGedcom.py (GedcomWriter.gnu_fdl): don't duplicate the copyright notice (bug #790) svn: r8373	2007-04-10 02:36:00 +00:00
Brian Matherly	0aa4eb258e	Remove file check from _GrampsIniKeys.py. It is not needed. svn: r8371	2007-04-09 15:29:13 +00:00
Brian Matherly	7f54da4cf3	Missing comma in Checkpoint.py. svn: r8369	2007-04-09 11:40:45 +00:00
Brian Matherly	044e38b129	0000995: Don't have write access on import/open in paths containing non-ASCII characters. svn: r8367	2007-04-09 04:24:06 +00:00
Brian Matherly	8ed86bc145	0001006: Narrative Web: Media objects missing title (description), mime_type, or path, are displayed poorly. svn: r8365	2007-04-09 03:35:58 +00:00
Brian Matherly	a6a0a69456	0000896: Crash running Narrative Web report - system memory exhausted. svn: r8362	2007-04-08 20:16:05 +00:00
Don Allingham	d6c8710d2c	2007-04-06 Don Allingham <don@gramps-project.org> * src/GrampsDb/_GrampsDbBase.py (GrampsDbBase.close_undodb): don't complain if the undo file isn't here. svn: r8360	2007-04-07 04:12:15 +00:00
Don Allingham	767d1d8191	2007-04-05 Don Allingham <don@gramps-project.org> * src/plugins/Checkpoint.py: fix some more Popen issues svn: r8359	2007-04-06 04:34:48 +00:00
Brian Matherly	da6e56990e	0000998: Source Ref link refers to nothing in Narrative web report. svn: r8357	2007-04-06 02:39:07 +00:00
Brian Matherly	26218253d7	0000996: Individual attributes do no include source reference citations in Narrative Web report. svn: r8355	2007-04-05 12:07:05 +00:00
Brian Matherly	fe84bcbdec	* src/DateHandler/_DateParser.py: Fix a typo * src/DateEdit.py: Fix a typo svn: r8354	2007-04-05 11:51:24 +00:00
Brian Matherly	4002837282	0000993: Checkpoint tool crashes in Windows svn: r8352	2007-04-05 02:54:03 +00:00
Don Allingham	b68e2d727f	2007-04-04 Don Allingham <don@gramps-project.org> * src/DateHandler/_DateParser.py: fix text string that contians a valid modifier. * src/Editors/_EditPerson.py: disable OK button on save to prevent double clicks * src/Editors/_EditPrimary.py: disable OK button on save to prevent double clicks * src/docgen/ODFDoc.py: XML escape strings svn: r8351	2007-04-05 02:46:56 +00:00
Kees Bakker	660e22bdfa	* po/nl.po Change archief in archiveer. svn: r8348	2007-04-02 18:43:50 +00:00
Benny Malengier	77817a5098	correct keyword error svn: r8343	2007-04-01 16:12:08 +00:00
Brian Matherly	a4ebbb4c15	0000975: remove extra (/b) HTML tags in NarrativeWeb svn: r8298	2007-03-14 03:24:17 +00:00
Brian Matherly	60c7367f77	0000976: NarrativeWeb: gramps ID always output regardless of setting svn: r8296	2007-03-14 03:09:38 +00:00
Brian Matherly	aa08262352	* src/plugins/NarrativeWeb.py: 0000969: NarrativeWeb plugin: include the date in the media object pages svn: r8294	2007-03-13 22:56:28 +00:00
Brian Matherly	86c6b1b7e7	src/ReportBase/_ReportDialog.py: don't catch all exceptions - we won't get a traceback. svn: r8290	2007-03-11 22:19:08 +00:00
Brian Matherly	dabcd47805	* src/plugins/NarrativeWeb.py: 0000950: include the date in the reference sections of the narrative web site svn: r8289	2007-03-11 19:42:48 +00:00
Martin Hawlisch	5bfdf4c45f	Translation update svn: r8285	2007-03-08 16:49:23 +00:00
Stefan Bjork	655626fd7d	Translation update svn: r8284	2007-03-08 08:48:15 +00:00
Don Allingham	03e54d00ed	2007-03-07 Stefan Björk <skalman@acc.umu.se> * src/Filters/Rules/_HasMarkerBase.py (HasMarkerBase): fix typo * src/GrampsWidgets.py: better wording svn: r8283	2007-03-07 15:45:32 +00:00
Stefan Bjork	4d009e4706	Translation update svn: r8282	2007-03-07 09:09:29 +00:00
Brian Matherly	772e4b15b0	* src/plugins/NarrativeWeb.py: * src/ReportBase/_ReportUtils.py: Fix 0000956: Event order within GRAMPS not replicated in web report svn: r8277	2007-03-07 03:11:41 +00:00
Brian Matherly	7f1a54dbd1	src/plugins/NarrativeWeb.py: Fix 0000954: e-mail address causes Narrative Web plugin to generate bad links svn: r8273	2007-03-06 04:21:59 +00:00
Brian Matherly	f64ae7ac77	* src/plugins/GraphViz.py: Fix 0000942: Relationship graph doesn't show preferred name format svn: r8268	2007-03-06 02:23:28 +00:00
Brian Matherly	2cf46c56ce	* src/plugins/TimeLine.py: Fix 0000943: Timeline doesn't show preferred name format svn: r8266	2007-03-06 02:08:22 +00:00
Benny Malengier	b8bc3f2cc3	updated dutch help translation svn: r8258	2007-02-28 21:21:09 +00:00
Brian Matherly	62dde7b4d1	* src/plugins/WritePkg.py: Fix crash on gpkg export in Windows svn: r8252	2007-02-27 02:36:25 +00:00
Brian Matherly	25ba79e7be	* src/plugins/AncestorChart2.py: Fix index error svn: r8238	2007-02-25 22:54:25 +00:00
Brian Matherly	a1efb824cb	* src/docgen/SvgDrawDoc.py.py: Fix XML error in draw_text. svn: r8227	2007-02-24 20:42:31 +00:00
Alex Roitman	2ace2ee5b4	* output/Makefile.am (HELP_LINGUAS): Disable nb for now; (fo): Generate fo output. svn: r8224	2007-02-24 01:47:15 +00:00
Alex Roitman	496bf99860	Update svn: r8223	2007-02-24 01:21:12 +00:00
Alex Roitman	23d434d8ea	2007-02-23 Alex Roitman <shura@gramps-project.org> * src/Editors/_EditFamily.py (edit_child_button_clicked): Catch open window situation. svn: r8222	2007-02-24 01:18:34 +00:00
Alex Roitman	62b2091e95	2007-02-23 Alex Roitman <shura@gramps-project.org> * C/gramps.xml: List Don just once, as a maintainer. * output/Makefile.am (HELP_LINGUAS): Disable nb for now. * output/gramps-help-screen.css: Modify css to see revision history by the main text. svn: r8220	2007-02-23 23:54:56 +00:00
Alex Roitman	3cba256408	Update svn: r8217	2007-02-23 06:10:16 +00:00
Alex Roitman	26a587fce1	2007-02-22 Alex Roitman <shura@gramps-project.org> * output/Makefile.am: Write rule for manual website creation. svn: r8215	2007-02-23 05:59:50 +00:00
Alex Roitman	c2dc72ffd3	* src/docgen/PdfDoc.py (write_text): Close <br/> tag. svn: r8214	2007-02-23 01:57:28 +00:00
Alex Roitman	9ec79f98e1	2007-02-22 Alex Roitman <shura@gramps-project.org> * src/GrampsDb/_GrampsBSDDB.py (reindex_reference_map): Typo. svn: r8213	2007-02-23 01:51:08 +00:00
Jérôme Rapinat	c8f66c8d24	update French translation for manual svn: r8208	2007-02-21 16:23:10 +00:00
Jérôme Rapinat	8e511eed6c	update French translation for manual svn: r8206	2007-02-21 16:02:30 +00:00
Jérôme Rapinat	7eba303735	/help/gramps.pot: update template svn: r8205	2007-02-21 14:33:23 +00:00
Jérôme Rapinat	ed7a5e8f56	fix bugs on manual: #809 #810 #932 #539 svn: r8204	2007-02-21 14:31:16 +00:00
Espen Berg	6b220b733b	Updated Norwegian translations svn: r8189	2007-02-20 19:03:01 +00:00
Brian Matherly	af9a79adb3	* src/plugins/AncestorChart2.py: Fix dimension error svn: r8185	2007-02-20 03:55:46 +00:00
Brian Matherly	794441dc37	* src/plugins/AncestorChart2.py: Use a dict instead of an array to use less memory. svn: r8164	2007-02-19 02:45:41 +00:00
Espen Berg	a0991f5a4c	Norwegian translation up to date svn: r8149	2007-02-17 23:28:17 +00:00
Don Allingham	c55ce06c34	2007-02-17 Anthon Pang <apang@softwaredevelopment.ca> * src/GrampsDb/_WriteGedcom.py: Fix encoding on output svn: r8145	2007-02-17 22:46:51 +00:00
Alex Roitman	c040885812	svn: r8138	2007-02-16 21:24:55 +00:00
Alex Roitman	02f4fe701d	svn: r8136	2007-02-16 21:18:01 +00:00
Alex Roitman	59e9c95f2b	svn: r8135	2007-02-16 21:16:14 +00:00
Alex Roitman	8d372b9e11	Update svn: r8134	2007-02-16 21:13:05 +00:00
Alex Roitman	9810a46876	Update svn: r8133	2007-02-16 20:46:42 +00:00
Alex Roitman	47051cf0dc	In .: 2007-02-16 Alex Roitman <shura@gramps-project.org> * configure.in: Add HELPPATH and FONTPATH substitutions, generate new files in help/output. In help: * Makefile.am (SUBDIRS): Add subdirs. svn: r8132	2007-02-16 20:45:28 +00:00
Alex Roitman	1528dd7946	svn: r8130	2007-02-16 20:00:30 +00:00
Benny Malengier	c6ee0d4d9b	svn: r8129	2007-02-16 19:42:07 +00:00
Alex Roitman	bf15d1749f	2007-02-16 Alex Roitman <shura@gramps-project.org> * help/nl: Add svn:ignore property. * various: Add stuff for generating html and pdf output. svn: r8128	2007-02-16 19:35:44 +00:00
Alex Roitman	ea5b19dfb9	2007-02-15 Piotr Czubaszek <pioterus@gmail.com> * pl.po: Translation update. svn: r8124	2007-02-16 03:13:50 +00:00
Brian Matherly	9d31b54646	* src/docgen/HtmlDoc.py: fix html template loading. * src/ReportBase/_ReportDialog.py: fix html template loading. svn: r8120	2007-02-15 03:18:03 +00:00
Espen Berg	ef3273a6ac	Updated Norwegian translation svn: r8116	2007-02-14 22:12:27 +00:00
Brian Matherly	11b13e1c94	* src/ViewManager.py: fix crash during backup on windows svn: r8111	2007-02-14 03:55:40 +00:00
Alex Roitman	32460cd87d	2007-02-13 Lubo Vasko <pgval@inMail.sk> * sk/figures/.png : Update. sk/sk.po: Translation update. svn: r8108	2007-02-13 16:53:44 +00:00
Zsolt Foldvari	fe2879c6bf	2007-02-13 Zsolt Foldvari <zfoldvar@users.sourceforge.net> * src/GrampsWidgets.py: Fall back to gtk.STOCK_DIALOG_INFO in case gtk.STOCK_INFO is missing. svn: r8105	2007-02-13 13:31:30 +00:00
Brian Matherly	6fd5e23d7a	* src/docgen/PSDrawDoc.py: Fix center_text and draw_bar svn: r8103	2007-02-13 04:52:07 +00:00
Brian Matherly	6b38b47690	* src/plugins/AncestorChart2.py: Fix title color * src/plugins/DescendChart.py: Fix title color * src/plugins/TimeLine.py: Fix title color svn: r8102	2007-02-13 04:49:56 +00:00
Brian Matherly	39f946aa7f	Remove the write_at function. Use draw_text instead. Add center_text to SVGDoc svn: r8101	2007-02-13 04:46:29 +00:00
Brian Matherly	71149e03a8	Remove unused functions from BaseDoc svn: r8100	2007-02-13 04:42:34 +00:00
Alex Roitman	13f29cc03b	In help: 2007-02-12 Lubo Vasko <pgval@inMail.sk> * sk/sk.po: Translation update. In po: 2007-02-12 Lubo Vasko <pgval@inMail.sk> * sk.po: Translation update. svn: r8097	2007-02-13 01:50:41 +00:00
Espen Berg	e7962896ed	Updated Norwegian translation svn: r8094	2007-02-12 23:14:08 +00:00
Don Allingham	20cade8132	2007-02-12 Don Allingham <don@gramps-project.org> * src/plugins/FindDupes.py: catch window already open message svn: r8091	2007-02-12 17:24:43 +00:00
Don Allingham	71ea4ef0f3	2007-02-11 Don Allingham <don@gramps-project.org> * src/Merge/_MergePlace.py (MergePlaces.merge): fix typo on add_source_reference svn: r8086	2007-02-11 18:21:58 +00:00
Kees Bakker	fb40f0995c	Spelling corrections and new translations in help/nl. Correction of figures in help/nl. svn: r8080	2007-02-10 09:07:46 +00:00
Don Allingham	e9744e54e7	svn: r8077	2007-02-08 06:10:11 +00:00
Zsolt Foldvari	c7f7068244	2007-02-07 Zsolt Foldvari <zfoldvar@users.sourceforge.net> * src/DisplayTabs/_NoteTab.py: move "rich text" notes to 2.3 branch. svn: r8074	2007-02-07 13:24:10 +00:00
Brian Matherly	76e09f5f6e	* src/docgen/PdfDoc.py: provide a more useful error when reportlab crashes svn: r8070	2007-02-07 04:37:32 +00:00
Brian Matherly	1fb8b84264	* src/plugins/holidays.xml: 0000906: Canada holidays patch svn: r8068	2007-02-07 04:03:06 +00:00
Brian Matherly	9d760ccad0	* src/ReportBase/_ReportDialog.py: 0000905: Typo in catching exceptions in buggy reports svn: r8067	2007-02-07 04:00:49 +00:00
Don Allingham	02e3da53dd	2007-02-06 Don Allingham <don@gramps-project.org> * src/GrampsDb/_ReadGedcom.py: fix cal/est parsing * src/DisplayTabs/_ButtonTab.py: catch window already being open * example/gedcom/sample.ged: Add est/cal samples svn: r8063	2007-02-07 02:27:51 +00:00
Jérôme Rapinat	8a35e82907	add forgotten place rules svn: r8058	2007-02-05 22:30:18 +00:00
Don Allingham	02e9064fc1	2007-02-04 Don Allingham <don@gramps-project.org> * src/DataViews/_RelationView.py: default Relationship buttons to insenstive. Setting an active person will reenable them. svn: r8053	2007-02-04 21:30:45 +00:00
Jérôme Rapinat	a318567198	small improvements in French translation svn: r8049	2007-02-04 11:14:55 +00:00
Brian Matherly	73f1ade7ac	ignore eclipse files svn: r8045	2007-02-04 02:31:58 +00:00
Brian Matherly	49c6ee9cc0	* src/plugins/NarrativeWeb.py: fix 0000894: syntax error on Narrative web plugin svn: r8042	2007-02-04 02:10:07 +00:00
Zdeněk Hataš	ded62534f6	Minor translation updates. svn: r8039	2007-02-03 22:34:22 +00:00
Don Allingham	8da06a6840	* src/DateHandler/_DateParser.py (DateParser.init_strings): fix date parsing to allow for spaces in numerical format. #892 svn: r8037	2007-02-03 18:30:43 +00:00
Don Allingham	0021d00c68	2007-02-03 Don Allingham <don@gramps-project.org> * src/Editors/_EditFamily.py (EditFamily.check_for_family_change): fix warning message. svn: r8035	2007-02-03 18:14:53 +00:00
Don Allingham	6182ebdcfb	2007-02-02 Don Allingham <don@gramps-project.org> * src/Editors/_EditFamily.py (EditFamily.check_for_family_change): update on data change from family-update signal svn: r8031	2007-02-03 06:38:44 +00:00
Don Allingham	60812d4e09	2007-01-30 Don Allingham <don@gramps-project.org> * src/Editors/_EditFamily.py: catch family-delete signal svn: r8030	2007-02-03 04:51:52 +00:00
				`@ -1 +0,0 @@`
				`As of version 3.0 the help manual is no longer maintained in svn, but on the wiki instead.`