* src/EventEdit.py (__init__): Only define translated name if the

event is not empty.
* doc/gramps-manual/C/gramps-manual.xml: Update manual.
* doc/gramps-manual/C/mainwin.xml: Update manual.
* doc/gramps-manual/C/faq.xml: Add to CVS.
* doc/gramps-manual/C/keybind.xml: Add to CVS.
* doc/gramps-manual/C/Makefile.am: Add new files to the distribution.


svn: r2404

ChangeLog

@@ -4,6 +4,13 @@
 	* src/plugins/book.glade: Remove initial text from the labels. 
 	* src/po/template.po: Updated translation template for 0.98.0.
 	* src/po/ru.po: Russian translation for 0.98.0.
+	* src/EventEdit.py (__init__): Only define translated name if the 
+	event is not empty.
+	* doc/gramps-manual/C/gramps-manual.xml: Update manual.
+	* doc/gramps-manual/C/mainwin.xml: Update manual.
+	* doc/gramps-manual/C/faq.xml: Add to CVS.
+	* doc/gramps-manual/C/keybind.xml: Add to CVS.
+	* doc/gramps-manual/C/Makefile.am: Add new files to the distribution.
 
 2003-11-27  Don Allingham  <dallingham@users.sourceforge.net>
 	* src/po/template.po: updated translatable strings

doc/gramps-manual/C/Makefile.am

@@ -7,6 +7,8 @@ entities = legal.xml\
 	mainwin.xml\
 	usage.xml\
 	custom.xml\
+	faq.xml\
+	keybind.xml\
 	filtref.xml\
 	cmdline.xml 
 include $(top_srcdir)/doc/xmldocs.make

doc/gramps-manual/C/faq.xml

@@ -0,0 +1,262 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id$ -->
+      <!-- =============== Appendices Subsection ================ -->
+      <sect2 id="faq">
+      <title>Frequently Asked Questions</title>
+      <para>This appendix contains the list of questions that frequently come 
+      up in mailing list discussions and forums. This list is by no means 
+      complete. If you would like to add questions/answers to this list, 
+      please email your suggestions to gramps-devel@lists.sf.net
+      </para>
+      
+      <variablelist>
+
+
+      <varlistentry><term>What is GRAMPS?</term>
+      <listitem><para> GRAMPS is the Genealogical Research and Analysis 
+      Management Program System. In other words, it is a personal genealogy 
+      program letting you store, edit, and research genealogical data using 
+      the powers of your computer. 
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Where do I get it and how much does it cost?</term>
+      <listitem><para> 
+GRAMPS can be downloaded from http://sf.net/projects/gramps at no charge. 
+GRAMPS is an Open Source project covered by the GNU General Public License. 
+You have full access to the source code and are allowed to distribute the 
+program and source code freely. 
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Does it work with Windows (tm)?</term>
+      <listitem><para> 
+No. GRAMPS uses the GTK and GNOME libraries. While the GTK libraries 
+have been ported to Windows, the GNOME libraries have not.
+This, however, may change in the future. 
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Does it work with the Mac?</term>
+      <listitem><para> 
+The Fink project (http://fink.sf.net) has ported an old version of 
+GRAMPS (0.8.0) to OSX. The Mac OSX port is not directly supported by 
+the GRAMPS project, primarily because none of the GRAMPS developers 
+have access to Mac OSX.</para>
+
+<para>The GNOME 2 version of GRAMPS (0.9.x) does not appear to have been 
+ported by the Fink project. Please contact the Fink project for more
+information.
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Does it work with KDE?</term>
+      <listitem><para> 
+Yes, as long as the required GNOME libraries are installed.
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Do I really have to have GNOME installed?</term>
+      <listitem><para> Yes, but you do not have to be running the GNOME desktop.
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>What version of GNOME do I need?</term>
+      <listitem><para> 
+The latest versions of gramps (0.9.0 and higher) require GNOME 2.0 or higher.
+Previous versions required GNOME 1.X. 
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Is GRAMPS compatible with 
+      other genealogical software (GenApps)?</term>
+      <listitem><para> 
+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. </para>
+
+<para>
+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! 
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Can GRAMPS read files created by GenApp X?</term>
+      <listitem><para> See above.
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Can GRAMPS write files readable by GenApp X?</term>
+      <listitem><para> See above.
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Can GRAMPS print a genealogical tree for my family?</term>
+      <listitem><para> 
+Yes. Different people have different ideas of what a genealogical tree is. 
+Some think of it as a chart going from the distant ancestor and listing 
+all his/her descendants and their families. Others think it should be a 
+chart going from the person back in time, listing the ancestors and their 
+families. Yet other people think of a table, text report, etc. </para>
+
+<para>
+GRAMPS can produce any of the above, and many more different charts and 
+reports. Moreover, the plugin architechture enables users (you) to create 
+their own plugins which could be new reports, charts, or research tools. 
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>In what formats can GRAMPS output its reports?</term>
+      <listitem><para> 
+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. 
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Is GRAMPS compatible with the Internet?</term>
+      <listitem><para> 
+GRAMPS can store web addresses and direct your browser to them. It can import
+data that you download from the Internet. It can export data that you could 
+send over the Internet. GRAMPS is familiar with the standard file formats 
+widely used on the Internet (e.g. JPEG, PNG, and GIF images, MP3, OGG, and 
+WAV sound files, QuickTime, MPEG, and AVI movie files, etc). Other than that, 
+there is little that a genealogical program can do with the Internet :-) 
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Can I create custom reports/filters/whatever?</term>
+      <listitem><para> 
+Yes. There are many levels of customization. One is creating or modifying 
+the templates used for the reports. This gives you some control over 
+the fonts, colors, and some layout of the reports. You can also use GRAMPS 
+controls in the report dialogs to tell what contents should be used for a 
+particular report. In addition to this, you have an ability to create your 
+own filters -- this is useful in selecting people based on criteria set 
+by you. You can combine these filters to create new, more complex filters. 
+Finally, you have an option to create your own plugins. These may be new 
+reports, research tools, import/export filters, etc. This assumes some 
+knowledge of programming in Python. 
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>What standards does GRAMPS support?</term>
+      <listitem><para> 
+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. 
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>What is the maximum database 
+      size (bytes) GRAMPS can handle?</term>
+      <listitem><para> 
+GRAMPS has no hard limits on the size of a database that it can handle. 
+In reality, however, there are practical limits. Currently GRAMPS loads all 
+data into memory, so the limiting factor tends to be the available memory 
+on the system. 
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>How many people can GRAMPS database handle?</term>
+      <listitem><para> 
+We have found that on a typical system, GRAMPS tends to bog down after the
+database has around 15,000 people. Again, this is dependant on how much
+memory you have. 
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Why is GRAMPS running so slowly?</term>
+      <listitem><para> 
+If GRAMPS seems too slow to you, it is most likely that you have a large
+database. Currently, GRAMPS loads all the database into memory, therefore 
+large databases tend to be less than responsive. Specifically, the system 
+can be virtually brought to its knees if swapping is needed for GRAMPS' data.
+</para> <para>
+This will be addressed in the next stable release following version 1.0. 
+Temporarily, adding more memory could make a huge difference, but we realize
+that this is a poor way of treating the problem. If you would like to help 
+with the implementation of the real database backend, please don't hesitate 
+to email us at gramps-devel@lists.sf.net
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>My database is really big. 
+      Is there a way around loading all the data into memory?</term>
+      <listitem><para> 
+Currently, there is no way around it. However, this is our biggest priority
+after releasing  version 1.0. The real database backend will be incorporated 
+in the next stable release (1.2) which will dramatically improve performance 
+in both speed and memory usage.
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Why are non-latin characters displayed 
+      as garbage in PDF/PS reports?</term>
+      <listitem><para> 
+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.</para>
+
+<para>
+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.
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>Why can I not add/remove/edit columns to the lists 
+      in People View and Family View?</term>
+      <listitem><para> 
+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.
+      </para></listitem>
+      </varlistentry>
+
+      <varlistentry><term>I found a bug and I want it fixed right now! 
+      What do I do?</term>
+      <listitem><para> 
+The best thing you can do is to fix the bug and send the patch to
+gramps-devel@lists.sf.net :-)</para>
+
+<para>
+The next best thing would be to submit a good bug report. This can be done in
+one of the two ways: (1) send your report to gramps-bugs@lists.sf.net
+or (2) file your report with the bug tracker system at 
+http://sf.net/tracker/?group_id=25770&amp;atid=385137 (this function is also 
+available by selecting "Help->Report a bug" from gramps main menu). </para>
+
+<para>A good bug report would include: </para>
+<para>   (1) Version of gramps you were using when you encountered the bug 
+       (available through Help->About menu item)</para>
+<para>   (2) Language under which gramps was run
+       (available by executing "echo $LANG" in your terminal)</para>
+<para>   (3) Symptoms indicating that this is indeed a bug</para>
+<para>   (4) Any Traceback messages, error messages, warnings, etc, that showed up
+       in your terminal or a in separate traceback window</para>
+
+<para>Most problems can be fixed quickly provided there is enough information. 
+To ensure this, please follow up on your bug reports. In particular, if you 
+file bug report with sf.net bug tracker, PLEASE log into sf.net before filing 
+(register your free account if you don't have one). Then we will have a way 
+of contacting you should we need more information. If you choose to file your 
+report anonymously, at least check every so often whether your report page 
+has something new posted, as it probably would.</para>
+
+<para>If the above explanations seem vague, please follow this link
+http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
+      </para></listitem>
+      </varlistentry>
+
+      </variablelist>
+
+      </sect2>

doc/gramps-manual/C/gramps-manual.xml

@@ -1,4 +1,5 @@
 <?xml version="1.0"?>
+<!-- $Id$ -->
 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" 
 "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
   <!ENTITY legal SYSTEM "legal.xml">
@@ -6,11 +7,13 @@
   <!ENTITY mainwin SYSTEM "mainwin.xml">
   <!ENTITY usage SYSTEM "usage.xml">
   <!ENTITY custom SYSTEM "custom.xml">
+  <!ENTITY faq SYSTEM "faq.xml">
+  <!ENTITY keybind SYSTEM "keybind.xml">
   <!ENTITY filtref SYSTEM "filtref.xml">
   <!ENTITY cmdline SYSTEM "cmdline.xml">
-  <!ENTITY appversion "0.9.5">
+  <!ENTITY appversion "0.98.0">
-  <!ENTITY manrevision "2.3">
+  <!ENTITY manrevision "2.4">
-  <!ENTITY date "September 2003">
+  <!ENTITY date "December 2003">
   <!ENTITY app "<application>GRAMPS</application>">
   <!-- Information about the entities
        The legal.xml file contains legal information, there is no need to edit the file. 
@@ -110,6 +113,15 @@
                 <para role="publisher">GRAMPS Project</para>
 		</revdescription> 
       </revision> 
+      <revision> 
+		<revnumber>GRAMPS Manual V2.3</revnumber> 
+		<date>September 2003</date> 
+		<revdescription> 
+	  	<para role="author">Alex Roitman
+		    	<email>shura@alex.neuro.umn.edu</email></para>
+                <para role="publisher">GRAMPS Project</para>
+		</revdescription> 
+      </revision> 
       <revision> 
 		<revnumber>GRAMPS Manual V2.2</revnumber> 
 		<date>July 2003</date> 
@@ -269,6 +281,8 @@
   <sect1 id="appendices">
     <title>Appendices</title>
   
+      &faq;		    <!-- FAQ -->
+      &keybind;		<!-- Keybindings reference -->
       &filtref;		<!-- Filter rule reference -->
       &cmdline;		<!-- Command line reference -->
       

doc/gramps-manual/C/keybind.xml

@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id$ -->
+      <!-- =============== Appendices Subsection ================ -->
+      <sect2 id="keybind">
+      <title>Keybindings reference</title>
+      <para>This appendix contains the list of keybindings that are not 
+      displayed in menus of &app;.
+      </para>
+      
+        <!-- =============== Appendices Sub-subsection ================ -->
+    	<sect3 id="keybind-people">
+        <title>People View</title>
+        <para>The following bindings are available in the People View:</para>
+        
+          <variablelist>
+
+          <varlistentry><term>ENTER</term>
+          <listitem><para> Invoke <guilabel>Edit Person</guilabel> dialog 
+          with the selected person.
+          </para></listitem>
+          </varlistentry>
+
+
+          </variablelist>
+
+        </sect3>
+
+
+        <!-- =============== Appendices Sub-subsection ================ -->
+    	<sect3 id="keybind-family">
+        <title>Family View</title>
+        <para>The following bindings are available in the Family View:</para>
+        
+          <variablelist>
+
+          <varlistentry><term>ENTER</term>
+          <listitem><para> When focus is on the active person, invoke 
+          <guilabel>Edit Person</guilabel> dialog with the active person. 
+          When focus is in the <guilabel>Spouse</guilabel> box, edit the 
+          relationship between the active person and the selected spouse.
+          When focus is in the parents' box, edit relationship between the 
+          selected parents and the active person/selected spouse. When focus
+          is in the children box, edit relationship between the selected 
+          child and his/her parents (active person and selected spouse).
+          </para>
+          <para>In all cases, pressing <guilabel>ENTER</guilabel> somewhere is
+          equivalent to double-clicking on the appropriate selection.
+          </para>
+          </listitem>
+          </varlistentry>
+
+          <varlistentry><term>Shift+ENTER</term>
+          <listitem><para> When focus is on the <guilabel>Spouse</guilabel> 
+          box, invoke <guilabel>Edit Person</guilabel> dialog with the 
+          selected spouse. When focus is in the children box, 
+          invoke <guilabel>Edit Person</guilabel> dialog with the the selected 
+          child.
+          </para>
+          <para>In all cases, pressing <guilabel>Shift+ENTER</guilabel> 
+          somewhere is equivalent to shift-clicking on the appropriate 
+          selection.
+          </para>
+          </listitem>
+          </varlistentry>
+
+
+
+          </variablelist>
+
+        </sect3>
+
+      </sect2>

doc/gramps-manual/C/mainwin.xml

@@ -1,4 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id$ -->
 
 <!-- ================ Main Window ================================ -->
   <sect1 id="gramps-mainwin"> 
@@ -128,10 +129,20 @@
     <!-- ================ Main Window Sub-subsection  -->
       <sect3 id="people-view">
         <title>People View</title>
-	<para>When &app; opens a database, 
+	<para>When &app; first opens a database, 
 	the View is set to the People View (<xref linkend="side-nofilt-fig"/> 
 	and <xref linkend="noside-nofilt-fig"/>). The People View lists 
-        individuals whose data is stored in the database. The People View 
+        individuals whose data is stored in the database.</para>
+        
+        <para> The individuals are arranged in a tree-like structure, 
+        according to their family names. Every family name is a node of the 
+        tree. Clicking the arrow on the left of the node will toggle its 
+        expansion state. When expanded, the node's contents is listed in the 
+        window. When collapsed, the contents is rolled up and not visible. 
+        However, all the data is still intact, it is just not being displayed.
+        </para>
+        
+        <para>The People View 
         displays people's <guilabel>Names</guilabel>, 
         &app; <guilabel>ID</guilabel> numbers, 
         <guilabel>Gender</guilabel>, and 

src/EventEdit.py

@@ -78,6 +78,12 @@ class EventEditor:
             if not self.witnesslist:
                 self.witnesslist = []
             self.date = Date.Date(self.event.getDateObj())
+            transname = const.display_event(event.getName())
+            # add the name to the list if it is not already there. This tends to occur
+            # in translated languages with the 'Death' event, which is a partial match
+            # to other events
+            if not transname in list:
+                list.append(transname)
         else:
             self.srcreflist = []
             self.witnesslist = []
@@ -134,15 +140,6 @@ class EventEditor:
                                            self.top.get_widget('edit_witness'),
                                            self.top.get_widget('del_witness'))
 
-        transname = const.display_event(event.getName())
-
-        # add the name to the list if it is not already there. This tends to occur
-        # in translated languages with the 'Death' event, which is a partial match
-        # to other events
-        
-        if not transname in list:
-            list.append(transname)
-            
         AutoComp.AutoCombo(self.event_menu,list)
         AutoComp.AutoEntry(self.place_field,self.pmap.keys())