Cyclone-Team/gramps
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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

Browse Source 
svn: r5217
This commit is contained in:
Don Allingham
2005-09-23 04:50:31 +00:00
parent 0903bc88d2
commit 20fb8825cd
10 changed files with 1222 additions and 815 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
gramps2/ChangeLog
View File

@@ -1,3 +1,6 @@
2005-09-22 Don Allingham <don@gramps-project.org>
* doc/gramps-manual/C/*.xml
2005-09-21 Don Allingham <don@gramps-project.org>
* src/ReportUtils.py: More UNKNOWN gender handling, and more
complete burial strings

4
gramps2/doc/gramps-manual/C/authors.xml
View File

@@ -24,7 +24,7 @@
<title>About GRAMPS</title>
<para> &app; was written by Donald N. Allingham
(<email>dallingham@users.sourceforge.net</email>).</para>
(<email>don@gramps-project.org</email>).</para>
<para>
The somewhat incomplete list of contributors includes (in alphabetical order):
@@ -50,6 +50,7 @@
<listitem><para>Steve Hall</para></listitem>
<listitem><para>David R. Hampton</para></listitem>
<listitem><para>Martin Hawlisch</para></listitem>
<listitem><para>Anton Huber</para></listitem>
<listitem><para>Frode Jemtland</para></listitem>
<listitem><para>Greg Kuperberg</para></listitem>
<listitem><para>Arkadiusz Lipiec</para></listitem>
@@ -63,6 +64,7 @@
<listitem><para>Guillaume Pratte</para></listitem>
<listitem><para>Laurent Protois</para></listitem>
<listitem><para>Matthieu Pupat</para></listitem>
<listitem><para>Trevor Rhodes</para></listitem>
<listitem><para>Alexander Roitman</para></listitem>
<listitem><para>Jason Salaz</para></listitem>
<listitem><para>Julio Sanchez</para></listitem>

20
gramps2/doc/gramps-manual/C/cmdline.xml
View File

@@ -1,7 +1,7 @@
<appendix id="append-cmdline">
<!--
User Manual for Gramps - a GTK+/GNOME based genealogy program
User Manual for GRAMPS - a GTK+/GNOME based genealogy program
Copyright (C) 2003-2005 Alexander Roitman
@@ -175,7 +175,7 @@
-i <filename>file2</filename>
-i <filename>file1</filename>
</command>
might produce different gramps IDs in the resulting database.
might produce different GRAMPS IDs in the resulting database.
</para></sect2>
<sect2 id="cmdline-opt-export"><title>Export options</title>
@@ -187,7 +187,7 @@
If not specified, the guess will be attempted based on
the <filename>filename</filename>. For iso format,
the <filename>filename</filename>
is actually the name of directory the gramps database will be written
is actually the name of directory the &app; database will be written
into. For grdb, gramps-xml, gedcom, wft, geneweb,
and gramps-pkg, the <filename>filename</filename>
is the name of the resulting file.
@@ -254,7 +254,7 @@
and values.
</para></listitem>
<listitem><para>Withing a pair, option name and value must be
<listitem><para>Within a pair, option name and value must be
separated by the equal sign.
</para></listitem>
@@ -339,7 +339,7 @@
the further command line parameters.
</para>
<note><para>Only one file can be opened in a single invokation
<note><para>Only one file can be opened in a single invocation
of &app;. If you need to get data from multiple sources, use
the importing options by using <command>-i</command> flag.
</para></note>
@@ -363,14 +363,14 @@
<listitem>
<para>If no <command>-O</command> or <command>-i</command>
option is given, gramps will launch
option is given, &app; will launch
its main window and start the usual interactive session with the empty
database, since there is no data to process, anyway.
</para></listitem>
<listitem>
<para>If no <command>-o</command> or <command>-a</command> options
are given, gramps will launch its main window and start the usual
are given, &app; will launch its main window and start the usual
interactive session with the database resulted from opening
and all imports (if any). This database resides in the
<filename>import_db.grdb</filename> file under the
@@ -379,7 +379,7 @@
<listitem>
<para>Any errors encountered during import, export, or action, will
be either dumped to stdout (if these are exceptions handled by gramps)
be either dumped to stdout (if these are exceptions handled by &app;)
or or to stderr (if these are not handled). Use usual shell redirections
of stdout and stderr to save messages and errors in files.
</para></listitem>
@@ -427,7 +427,7 @@
<varlistentry>
<term>To record the database resulting from all imports, supply
<command>-o</command> flag (use <command>-f</command>
if the filename does not allow gramps to guess the format):</term>
if the filename does not allow &app; to guess the format):</term>
<listitem>
<para><command>gramps
-i <filename>file1.ged</filename>
@@ -453,7 +453,7 @@
</varlistentry>
<varlistentry>
<term>To import three databases and start interactive gramps
<term>To import three databases and start interactive &app;
session with the result:</term>
<listitem>
<para><command>gramps

2
gramps2/doc/gramps-manual/C/custom.xml
View File

@@ -94,7 +94,7 @@
<tip><para>The ID prefixes use formatting conventions common for
C, Python, and other programming languages. For example, the %04d
expands to an integer, prepended with zeros to have the total
width of founr digits. If you would like IDs to be 1, 2, 3, etc,
width of four digits. If you would like IDs to be 1, 2, 3, etc,
simply set the formatting parameter to %d.
</para></tip>
</listitem>

18
gramps2/doc/gramps-manual/C/faq.xml
View File

@@ -130,7 +130,7 @@ families. Yet other people think of a table, text report, etc. </para>
<para>
&app; can produce any of the above, and many more different charts and
reports. Moreover, the plugin architechture enables users (you) to create
reports. Moreover, the plugin architecture enables users (you) to create
their own plugins which could be new reports, charts, or research tools.
</para></listitem>
</varlistentry>
@@ -171,9 +171,9 @@ knowledge of programming in Python.
<varlistentry><term>What standards does &app; support?</term>
<listitem><para>
The nice thing about the standards is that there never is a shortage of
The nice thing about standards is that there never is a shortage of
them. &app; is tested to support the following flavors of GEDCOM:
GEDCOM5.5, Brother's Keeper, Family Origins, Familty Tree Maker, Ftree,
GEDCOM5.5, Brother's Keeper, Family Origins, Family Tree Maker, Ftree,
GeneWeb, Legacy, Personal Ancestral File, Pro-Gen, Reunion, and
Visual Genealogie.
</para></listitem>
@@ -184,7 +184,7 @@ Visual Genealogie.
<listitem><para>
&app; has no hard limits on the size of a database that it can handle.
Starting with this release, &app; no longer loads all data into memory,
which allows it to work with much larger database than before.
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, &app; should have
@@ -210,7 +210,7 @@ memory you have.
Is there a way around loading all the data into memory?</term>
<listitem><para>
Starting with this release, &app; no longer loads all data into memory,
which allows it to work with much larger database than before.
which allows it to work with a much larger database than before.
</para></listitem>
</varlistentry>
@@ -351,13 +351,7 @@ If, however, you would like the &app; project to to adopt your strategy,
you would need to convince &app; developers that your strategy is good
for &app; and superior to the present development strategy.</para>
<tip><para>
If &app; 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 :-)
</para></tip></listitem>
</listitem>
</varlistentry>
</variablelist>

6
gramps2/doc/gramps-manual/C/mainwin.xml
View File

@@ -135,10 +135,10 @@
<title>Views</title>
<para>
Views are the various ways to display different aspects of
genealogical information. It is best to split the relevent
informatin display into smaller categories, uniform in context
genealogical information. It is best to split the relevant
information display into smaller categories, uniform in context
and modality; since it is very broad and non-uniform in both
cntext and modality. Each View represents such a split and
context and modality. Each View represents such a split and
displays a certain portion of overall available
information. Before reviewing the detailed description of
available Views, you will be guided through the ways of

10
gramps2/doc/gramps-manual/C/preface.xml
View File

@@ -26,7 +26,7 @@
<para>
&app; is a software package designed to help you with
genealogical resarch. It allows you to store, edit, and research
genealogical research. It allows you to store, edit, and research
genealogical data using your computer. Although similar to other
genealogical programs, it offers some unique and powerful
features. GRAMPS is an open source software package, which means
@@ -45,7 +45,7 @@
descendant or ancestral relationships through graphical
displays, charts, or reports. Some allow pictures or other media
to be inserted to enhance the raw data. Most provide a means to
include data on individuals or familys that may or may not be
include data on individuals or families that may or may not be
related to the primary family being researched. And they may
include other features such as exporting or importing to and
from other programs and printing data contained in various
@@ -62,7 +62,7 @@
</para><para>
&app; has the power to let you rearrage your data in any order
&app; has the power to let you rearrange your data in any order
or sequence and to help you fill gaps in genealogical
relationships.
@@ -205,14 +205,12 @@
<warning id="gedcom-inmem1-warn">
<title>GEDCOM Editing</title>
<para>
Please keep in mind that some information in GEDCOM
file may be lost during import into &app;. Simply
opening and viewing the file will not change it.
However, if any changes were made and they were not
abandoned upon exit, exiting &app; will save the data,
with the possible data loss.
</para>
</warning>
</para>
@@ -376,7 +374,7 @@
</para>
<para>
Finally, there are warnings, notifiying you where you should be careful:
Finally, there are warnings, notifying you where you should be careful:
<warning id="example-warning">
<title>Example Warning</title>

20
gramps2/doc/gramps-manual/C/usage.xml
View File

@@ -666,7 +666,7 @@
<para>
Exporting to Web Family Tree will create the text file
suitable as an input for the WFT program. Specific
options include filter selecton and the ability to
options include filter selection and the ability to
restrict data on living people, that is to limit living
people's data to family ties.
</para>
@@ -1937,7 +1937,7 @@
<listitem>
<para>
The <guilabel>Notes</guilabel> tab displays information
about the otes concerning the relationship. These could
about the notes concerning the relationship. These could
be any notes which do not naturally fit into the
Parameter-Value pairs available to Attributes. To add a
note or modify existing notes simply edit the text in
@@ -2006,7 +2006,7 @@
<listitem>
<para>
The <guilabel>Gallery</guilabel> tab displays
information about edia objects associated with the
information about media objects associated with the
relationship and the controls allowing modification of
such. The central part shows the list of all such media
objects. For media object which are valid image files
@@ -2218,7 +2218,7 @@
<listitem>
<para>
The <guilabel>References</guilabel> tab displays
information about atabase records that refer to this
information about database records that refer to this
source. If the source is not referenced from any
database record, the tab shows an empty list. If the
source is referenced from many records, the tab will
@@ -2333,7 +2333,7 @@
<listitem>
<para>
The <guilabel>Other names</guilabel> tab displays
information concerning ther names by which the place
information concerning other names by which the place
might be known and the controls allowing their
modification. The bottom part displays the list of all
other names of the place stored in the database. The top
@@ -3359,7 +3359,7 @@
<tip>
<para>
If the person you would like to add as a wittness is in fact
If the person you would like to add as a witness is in fact
a member of the database, it is better to use the first
method below.
@@ -4363,7 +4363,7 @@
<para>
This report generates a graph of people who are
escendants of the Active person. Specific options
descendants of the Active person. Specific options
include the format of the displayed entries.
</para>
@@ -4411,7 +4411,7 @@
and gender-based limit for inclusion into statistics.
You can also set the minimum number of items to qualify
for the bar chart, so that the charts with fewer items
will generate a pice chart instead. The <guilabel>Chart
will generate a pie chart instead. The <guilabel>Chart
Selection</guilabel> tab allows you to check which
charts you want to include in your report.
@@ -5215,7 +5215,7 @@
textual information of notes and comments. To store any type
of these records, simply drag the existing record on to the
Scratch Pad from the corresponding editor dialog. To reuse
the record, drag it from the Scratch Pad onlto the
the record, drag it from the Scratch Pad on to the
corresponding place in the editor, e.g. Address tab,
Attribute tab, etc.
@@ -5259,7 +5259,7 @@
people in the database. Please visit the <ulink
url="http://www.archives.gov/research_room/genealogy/census/soundex.html"
type="http">NARA Soundex Indexing page</ulink> to
learn more about Soudex Indexing System.
learn more about Soundex Indexing System.
</para>
</listitem>

168
gramps2/src/ReportUtils.py
View File

@@ -1948,136 +1948,78 @@ def list_person_str(database,person,person_name=None,empty_date="",empty_place="
text = ""
values = {
'unknown_gender_name' : person_name,
'male_name' : person_name,
'female_name' : person_name,
'birth_date' : bdate,
'birth_place' : bplace,
'death_date' : ddate,
'death_place' : dplace,
'name' : person_name,
'birth_date' : bdate,
'birth_place' : bplace,
'death_date' : ddate,
'death_place' : dplace,
}
if person.get_gender() == RelLib.Person.MALE:
if bdate:
if bplace:
if ddate:
if dplace:
text = _("%(male_name)s "
"Born: %(birth_date)s %(birth_place)s "
"Died: %(death_date)s %(death_place)s.") % values
else:
text = _("%(male_name)s "
"Born: %(birth_date)s %(birth_place)s "
"Died: %(death_date)s.") % values
if bdate:
if bplace:
if ddate:
if dplace:
text = _("%(name)s "
"Born: %(birth_date)s %(birth_place)s "
"Died: %(death_date)s %(death_place)s.") % values
else:
if dplace:
text = _("%(male_name)s "
"Born: %(birth_date)s %(birth_place)s "
"Died: %(death_place)s.") % values
else:
text = _("%(male_name)s "
"Born: %(birth_date)s %(birth_place)s.") % values
text = _("%(name)s "
"Born: %(birth_date)s %(birth_place)s "
"Died: %(death_date)s.") % values
else:
if ddate:
if dplace:
text = _("%(male_name)s Born: %(birth_date)s "
"Died: %(death_date)s %(death_place)s.") % values
else:
text = _("%(male_name)s "
"Born: %(birth_date)s Died: %(death_date)s.") % values
if dplace:
text = _("%(name)s "
"Born: %(birth_date)s %(birth_place)s "
"Died: %(death_place)s.") % values
else:
if dplace:
text = _("%(male_name)s "
"Born: %(birth_date)s Died: %(death_place)s.") % values
else:
text = _("%(male_name)s Born: %(birth_date)s.") % values
text = _("%(name)s "
"Born: %(birth_date)s %(birth_place)s.") % values
else:
if bplace:
if ddate:
if dplace:
text = _("%(male_name)s "
"Born: %(birth_place)s "
"Died: %(death_date)s %(death_place)s.") % values
else:
text = _("%(male_name)s "
"Born: %(birth_place)s "
"Died: %(death_date)s.") % values
if ddate:
if dplace:
text = _("%(name)s Born: %(birth_date)s "
"Died: %(death_date)s %(death_place)s.") % values
else:
if dplace:
text = _("%(male_name)s "
"Born: %(birth_place)s "
"Died: %(death_place)s.") % values
else:
text = _("%(male_name)s "
"Born: %(birth_place)s.") % values
text = _("%(name)s "
"Born: %(birth_date)s Died: %(death_date)s.") % values
else:
if ddate:
if dplace:
text = _("%(male_name)s "
"Died: %(death_date)s %(death_place)s.") % values
else:
text = _("%(male_name)s "
"Died: %(death_date)s.") % values
if dplace:
text = _("%(name)s "
"Born: %(birth_date)s Died: %(death_place)s.") % values
else:
if dplace:
text = _("%(male_name)s Died: %(death_place)s.") % values
else:
text = _("%(male_name)s.") % values
text = _("%(name)s Born: %(birth_date)s.") % values
else:
if bdate:
if bplace:
if ddate:
if dplace:
text = _("%(female_name)s "
"Born: %(birth_date)s %(birth_place)s "
"Died: %(death_date)s %(death_place)s.") % values
else:
text = _("%(female_name)s "
"Born: %(birth_date)s %(birth_place)s "
"Died: %(death_date)s.") % values
if bplace:
if ddate:
if dplace:
text = _("%(name)s "
"Born: %(birth_place)s "
"Died: %(death_date)s %(death_place)s.") % values
else:
if dplace:
text = _("%(female_name)s "
"Born: %(birth_date)s %(birth_place)s "
"Died: %(death_place)s.") % values
else:
text = _("%(female_name)s "
"Born: %(birth_date)s %(birth_place)s.") % values
text = _("%(name)s "
"Born: %(birth_place)s "
"Died: %(death_date)s.") % values
else:
if ddate:
if dplace:
text = _("%(female_name)s Born: %(birth_date)s "
"Died: %(death_date)s %(death_place)s.") % values
else:
text = _("%(female_name)s Born: %(birth_date)s Died: %(death_date)s.") % values
if dplace:
text = _("%(name)s "
"Born: %(birth_place)s "
"Died: %(death_place)s.") % values
else:
if dplace:
text = _("%(female_name)s Born: %(birth_date)s Died: %(death_place)s.") % values
else:
text = _("%(female_name)s Born: %(birth_date)s.") % values
text = _("%(name)s "
"Born: %(birth_place)s.") % values
else:
if bplace:
if ddate:
if dplace:
text = _("%(female_name)s Born: %(birth_place)s Died: %(death_date)s %(death_place)s.") % values
else:
text = _("%(female_name)s Born: %(birth_place)s Died: %(death_date)s.") % values
if ddate:
if dplace:
text = _("%(name)s "
"Died: %(death_date)s %(death_place)s.") % values
else:
if dplace:
text = _("%(female_name)s Born: %(birth_place)s Died: %(death_place)s.") % values
else:
text = _("%(female_name)s Born: %(birth_place)s.") % values
text = _("%(name)s "
"Died: %(death_date)s.") % values
else:
if ddate:
if dplace:
text = _("%(female_name)s Died: %(death_date)s %(death_place)s.") % values
else:
text = _("%(female_name)s Died: %(death_date)s.") % values
if dplace:
text = _("%(name)s Died: %(death_place)s.") % values
else:
if dplace:
text = _("%(female_name)s Died: %(death_place)s.") % values
else:
text = _("%(female_name)s.") % values
text = _("%(name)s.") % values
if text:
text = "- %s " % text

1786
gramps2/src/po/template.po
View File

File diff suppressed because it is too large Load Diff