* NEWS: Update.

* src/FamilyView.py (on_child_list_button_press): Add edit person
callback on Shift+click; (sp_key_press, child_key_press): Replace
Ctrl+Insert with Shift+Insert for adding new people.
* src/PedView.py (on_show_child_menu): Markup children with children.
* doc/gramps-manual/C/keybind.xml: Update.
* doc/gramps-manual/C/faq.xml: Update.
* doc/gramps-manual/C/filtref.xml: Update.


svn: r2412
This commit is contained in:
Alex Roitman
2003-12-01 04:22:15 +00:00
parent a4a2eb580a
commit 448fc5db0b
7 changed files with 310 additions and 57 deletions

View File

@@ -1,12 +1,15 @@
<?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
please email your suggestions to <ulink url="mailto:gramps-devel@lists.sf.net"
type="mailto">gramps-devel@lists.sf.net</ulink>
</para>
<variablelist>
@@ -183,7 +186,8 @@ 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
to email us at <ulink url="mailto:gramps-devel@lists.sf.net"
type="mailto">gramps-devel@lists.sf.net</ulink>
</para></listitem>
</varlistentry>
@@ -226,23 +230,46 @@ ability to add/remove/edit sortable columns.
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>
<ulink url="mailto:gramps-devel@lists.sf.net"
type="mailto">gramps-devel@lists.sf.net</ulink> :-)</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
one of the two ways: (1) send your report to
<ulink url="mailto:gramps-bugs@lists.sf.net"
type="mailto">gramps-bugs@lists.sf.net</ulink>
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>
<ulink url="http://sf.net/projects/gramps" type="http">
http://sf.net/tracker/?group_id=25770&amp;atid=385137</ulink>
(this function is also available by selecting
<menuchoice><guisubmenu>Help</guisubmenu><guimenuitem>Report a
bug</guimenuitem></menuchoice> 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>
<itemizedlist>
<listitem><para>
1. Version of gramps you were using when you encountered the bug
(available through <menuchoice><guisubmenu>Help</guisubmenu>
<guimenuitem>About</guimenuitem></menuchoice> menu item).
</para></listitem>
<listitem><para>
2. Language under which gramps was run
(available by executing <command>echo $LANG</command> in your terminal).
</para></listitem>
<listitem><para>
3. Symptoms indicating that this is indeed a bug.
</para></listitem>
<listitem><para>
4. Any Traceback messages, error messages, warnings, etc,
that showed up in your terminal or a in separate traceback window.
</para></listitem>
</itemizedlist>
<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
@@ -252,8 +279,10 @@ 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>If the above explanations seem vague, please follow
<ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html" type="http">
this link.</ulink>
</para></listitem>
</varlistentry>