Compare commits

..

121 Commits

Author SHA1 Message Date
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
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
df18340c21 0000970: _IsBookmarked.py causes crash
svn: r8415
2007-04-21 18:48:04 +00:00
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
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
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
9eff5e9327 add German translation for manual
svn: r8409
2007-04-20 06:59:19 +00:00
5767ac5bbd add German translation for manual
svn: r8408
2007-04-20 06:56:22 +00:00
9d4d7ca873 add German translation for manual
svn: r8407
2007-04-20 06:53:04 +00:00
c324efb9e4 PROPERLY escape ampersands in ODFDoc.py
svn: r8405
2007-04-20 03:48:21 +00:00
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
eb7b977237 update French translation for 2.2.7
svn: r8401
2007-04-18 16:11:20 +00:00
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
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
1305e3b037 * po/nl.po Some corrections by Erik
svn: r8396
2007-04-17 19:13:10 +00:00
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
c397c43701 Updated Lithuanian translation
svn: r8394
2007-04-17 17:21:40 +00:00
260f5f2422 * de.po: translation update
svn: r8392
2007-04-16 16:12:34 +00:00
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
12a002b945 update French translation for 2.2.7
svn: r8389
2007-04-16 09:19:42 +00:00
a6a8cdff0f improve French translation for manual
svn: r8388
2007-04-16 09:19:11 +00:00
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
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
6468dc2a23 0001012: Private source and private child references shown in narrative website.
svn: r8384
2007-04-15 19:09:55 +00:00
670eef2da8 0001017: Insufficient space in pedigree view of narrative website
svn: r8382
2007-04-15 02:17:44 +00:00
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
4cb1aaacd1 0001011: XML import loses media objects when media object has no title.
svn: r8379
2007-04-12 11:46:36 +00:00
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
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
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
c62bef3f21 * src/plugins/ImportGeneWeb.py: Some parsing enhancements
svn: r8375
2007-04-10 19:22:44 +00:00
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
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
0aa4eb258e Remove file check from _GrampsIniKeys.py. It is not needed.
svn: r8371
2007-04-09 15:29:13 +00:00
7f54da4cf3 Missing comma in Checkpoint.py.
svn: r8369
2007-04-09 11:40:45 +00:00
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
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
a6a0a69456 0000896: Crash running Narrative Web report - system memory exhausted.
svn: r8362
2007-04-08 20:16:05 +00:00
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
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
da6e56990e 0000998: Source Ref link refers to nothing in Narrative web report.
svn: r8357
2007-04-06 02:39:07 +00:00
26218253d7 0000996: Individual attributes do no include source reference citations in Narrative Web report.
svn: r8355
2007-04-05 12:07:05 +00:00
fe84bcbdec * src/DateHandler/_DateParser.py: Fix a typo
* src/DateEdit.py: Fix a typo

svn: r8354
2007-04-05 11:51:24 +00:00
4002837282 0000993: Checkpoint tool crashes in Windows
svn: r8352
2007-04-05 02:54:03 +00:00
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
660e22bdfa * po/nl.po Change archief in archiveer.
svn: r8348
2007-04-02 18:43:50 +00:00
77817a5098 correct keyword error
svn: r8343
2007-04-01 16:12:08 +00:00
a4ebbb4c15 0000975: remove extra (/b) HTML tags in NarrativeWeb
svn: r8298
2007-03-14 03:24:17 +00:00
60c7367f77 0000976: NarrativeWeb: gramps ID always output regardless of setting
svn: r8296
2007-03-14 03:09:38 +00:00
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
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
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
5bfdf4c45f Translation update
svn: r8285
2007-03-08 16:49:23 +00:00
655626fd7d Translation update
svn: r8284
2007-03-08 08:48:15 +00:00
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
4d009e4706 Translation update
svn: r8282
2007-03-07 09:09:29 +00:00
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
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
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
2cf46c56ce * src/plugins/TimeLine.py: Fix 0000943: Timeline doesn't show preferred name format
svn: r8266
2007-03-06 02:08:22 +00:00
b8bc3f2cc3 updated dutch help translation
svn: r8258
2007-02-28 21:21:09 +00:00
62dde7b4d1 * src/plugins/WritePkg.py: Fix crash on gpkg export in Windows
svn: r8252
2007-02-27 02:36:25 +00:00
25ba79e7be * src/plugins/AncestorChart2.py: Fix index error
svn: r8238
2007-02-25 22:54:25 +00:00
a1efb824cb * src/docgen/SvgDrawDoc.py.py: Fix XML error in draw_text.
svn: r8227
2007-02-24 20:42:31 +00:00
2ace2ee5b4 * output/Makefile.am (HELP_LINGUAS): Disable nb for now;
(fo): Generate fo output.



svn: r8224
2007-02-24 01:47:15 +00:00
496bf99860 Update
svn: r8223
2007-02-24 01:21:12 +00:00
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
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
3cba256408 Update
svn: r8217
2007-02-23 06:10:16 +00:00
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
c2dc72ffd3 * src/docgen/PdfDoc.py (write_text): Close <br/> tag.
svn: r8214
2007-02-23 01:57:28 +00:00
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
c8f66c8d24 update French translation for manual
svn: r8208
2007-02-21 16:23:10 +00:00
8e511eed6c update French translation for manual
svn: r8206
2007-02-21 16:02:30 +00:00
7eba303735 /help/gramps.pot: update template
svn: r8205
2007-02-21 14:33:23 +00:00
ed7a5e8f56 fix bugs on manual: #809 #810 #932 #539
svn: r8204
2007-02-21 14:31:16 +00:00
6b220b733b Updated Norwegian translations
svn: r8189
2007-02-20 19:03:01 +00:00
af9a79adb3 * src/plugins/AncestorChart2.py: Fix dimension error
svn: r8185
2007-02-20 03:55:46 +00:00
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
a0991f5a4c Norwegian translation up to date
svn: r8149
2007-02-17 23:28:17 +00:00
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
c040885812 svn: r8138 2007-02-16 21:24:55 +00:00
02f4fe701d svn: r8136 2007-02-16 21:18:01 +00:00
59e9c95f2b svn: r8135 2007-02-16 21:16:14 +00:00
8d372b9e11 Update
svn: r8134
2007-02-16 21:13:05 +00:00
9810a46876 Update
svn: r8133
2007-02-16 20:46:42 +00:00
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
1528dd7946 svn: r8130 2007-02-16 20:00:30 +00:00
c6ee0d4d9b svn: r8129 2007-02-16 19:42:07 +00:00
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
ea5b19dfb9 2007-02-15 Piotr Czubaszek <pioterus@gmail.com>
* pl.po: Translation update.



svn: r8124
2007-02-16 03:13:50 +00:00
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
ef3273a6ac Updated Norwegian translation
svn: r8116
2007-02-14 22:12:27 +00:00
11b13e1c94 * src/ViewManager.py: fix crash during backup on windows
svn: r8111
2007-02-14 03:55:40 +00:00
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
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
6fd5e23d7a * src/docgen/PSDrawDoc.py: Fix center_text and draw_bar
svn: r8103
2007-02-13 04:52:07 +00:00
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
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
71149e03a8 Remove unused functions from BaseDoc
svn: r8100
2007-02-13 04:42:34 +00:00
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
e7962896ed Updated Norwegian translation
svn: r8094
2007-02-12 23:14:08 +00:00
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
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
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
e9744e54e7 svn: r8077 2007-02-08 06:10:11 +00:00
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
76e09f5f6e * src/docgen/PdfDoc.py: provide a more useful error when reportlab crashes
svn: r8070
2007-02-07 04:37:32 +00:00
1fb8b84264 * src/plugins/holidays.xml: 0000906: Canada holidays patch
svn: r8068
2007-02-07 04:03:06 +00:00
9d760ccad0 * src/ReportBase/_ReportDialog.py: 0000905: Typo in catching exceptions in buggy reports
svn: r8067
2007-02-07 04:00:49 +00:00
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
8a35e82907 add forgotten place rules
svn: r8058
2007-02-05 22:30:18 +00:00
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
a318567198 small improvements in French translation
svn: r8049
2007-02-04 11:14:55 +00:00
73f1ade7ac ignore eclipse files
svn: r8045
2007-02-04 02:31:58 +00:00
49c6ee9cc0 * src/plugins/NarrativeWeb.py: fix 0000894: syntax error on Narrative web plugin
svn: r8042
2007-02-04 02:10:07 +00:00
ded62534f6 Minor translation updates.
svn: r8039
2007-02-03 22:34:22 +00:00
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
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
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
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
2548 changed files with 561841 additions and 1556774 deletions

38
.gitignore vendored
View File

@ -1,38 +0,0 @@
# Python
*.py[cod]
# Distutils
aclocal.m4
autom4te.cache
config.log
config.status
configure
Makefile
Makefile*.in
install-sh
MANIFEST
build/
dist/
m4/intltool.m4
missing
mkinstalldirs
py-compile
# Gramps
src/const.py
src/data/tips.xml
src/plugins/lib/holidays.xml
po/.intltool-merge-cache
po/stamp-it
po/POTFILES
data/gramps.desktop
data/gramps.keys
data/gramps.xml
*.gmo
data/man/*.[1-8]
data/man/*/*.[1-8]
gramps.sh
intltool-*.in
#Editing
tags

109
AUTHORS
View File

@ -1,108 +1,17 @@
#
# Gramps - a GTK+/GNOME based genealogy program
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Donald N. Allingham ** Concept and main design
<!-- $Id$ -->
David Hampton ** Autocomp.py and Report.py
Alex Roitman shura@gramps-project.org
Donald A. Peterson ** Makefiles, LaTeXDoc.py
Arturas Sleinius asleinius@users.sourceforge.net
Alex Roitman ** BookReport, command line, Gramps manual, bugfixes
Benny Malengier benny.malengier@gramps-project.org
Tim Waugh ** Comprehensive Ancestor report, docgen, Makefiles, bugfixes
Boril Gourinov boril.gourinov@gmail.com
Martin Hawlisch - Filters
Brian Matherly brian@gramps-project.org
Richard Taylor - ScratchPad.py, GrampsDBCallback.py
Craig J. Anderson ander882@hotmail.com
Brian Matherly - Reports
Don Allingham don@gramps-project.org
Donald A. Peterson
Doug Blank doug.blank@gmail.com
Eero Tamminen eerot@users.sourceforge.net
Erik De Richter erikdrgm@users.sourceforge.net
Espen Berg espenbe@gmail.com
Gary Burton gary.burton@zen.co.uk
Gerald Britton gerald.britton@gmail.com
James G Sack jgsack@san.rr.com
Janne Kovesjärvi janne.kovesjarvi@gmail.com
Jason Simanek jsimanek@gmail.com
Jérôme Rapinat romjerome@yahoo.fr
Joan Creus joan.creus@gmail.com
Josip Pisoj josip@pisoj.com
Julio Sánchez julio.sanchez@gmail.com
Kees Bakker kees.bakker@xs4all.nl
Konstantin Dorichev kdorichev@gmail.com
Lubo Vasko pgval@inMail.sk
Luigi Toscano luigi.toscano@tiscali.it
Luiz Gonzaga dos Santos Filho lfilho@gmail.com
Łukasz Rymarczyk yenidai@poczta.onet.pl
Michiel Nauta m.d.nauta@hetnet.nl
Mirko Leonhäuser mirko@leonhaeuser.de
Morten Bo Johansen mbj@spamcop.net
Martin Hawlisch martin.hawlisch@gmx.de
Nick Hall nick__hall@hotmail.com
Peter Landgren peter.talken@telia.com
Raphael Ackermann raphael.ackermann@gmail.com
Richard Taylor rjt-gramps@thegrindstone.me.uk
Rob G. Healey robhealey1@gmail.com
Serge Noiraud Serge.Noiraud@free.fr
Sigmund Lorentsen sigmund.lorentsen@tele2.no
Stefan Bjork betula@users.sourceforge.net
Stéphane Charette stephanecharette@gmail.com
Tim G L Lyons tim.g.lyons@gmail.com
Tim Waugh twaugh@redhat.com
Vassilii Khachaturov vassilii@tarunz.org
Zdeněk Hataš zdenek.hatas@gmail.com
Zsolt Foldvari zfoldvar@users.sourceforge.net
$Id$

View File

@ -2,7 +2,7 @@
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
675 Mass Ave, Cambridge, MA 02139, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

13
COPYING-DOCS Normal file
View File

@ -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$

12230
ChangeLog Normal file

File diff suppressed because it is too large Load Diff

8349
ChangeLog.old Normal file

File diff suppressed because it is too large Load Diff

347
FAQ
View File

@ -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$

86
INSTALL
View File

@ -4,27 +4,9 @@ This file contains some useful details on the installation from source code
for GRAMPS. It does not cover installation of a pre-built binary package.
For that use your package manager, the rest is already done by the packager.
Uninstall old version
---------------------
If you do a source install in the same place of an existing install,
you need to remove the old version first. You can delete the old
version by:
* deleting the installed directories (for example,
/usr/share/gramps)
* OR by running "make uninstall" from the old directory where you
ran "make install" (not the new GRAMPS directory)
GRAMPS is a python application, so loading happens on reading the
files, meaning that files of a previous version that are no longer
present in the new version can still be loaded, making the new install
unstable.
Configure vs autogen scripts
configure vs autogen scripts
----------------------------
Configure does not check all dependencies of Gramps, see README for a
list of all required and optional dependencies.
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
@ -32,55 +14,57 @@ running ./autogen.sh and then "make" and, finally, "make install".
Running ./autogen.sh on this branch of gramps requires the following
packages to be installed:
* autoconf >=2.53
* automake >=1.9
* intltool >=0.25
* glib-gettext >=2.2.0, included in 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.
* automake-1.9
* gnome-common
* intltool
* libglib2.0-dev (may be called differently on other distros) and
maybe something else. If autogen.sh fails, it should inform you what's
missing.
Custom directory installation
-------------------------------------
If you would like to install GRAMPS without being root, or in an
alternative location on windows, supply the --prefix argument to autogen
or configure.
For example:
./autogen.sh --prefix=$HOME/my_gramps_path
or
./autogen.sh --prefix=/cygdrive/c/Projects/gramps
Regular vs local installation
-----------------------------
This version of gramps REQUIRES, among other things, the mime types for
gramps be properly installed.
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.
The latter is possible, but you should supply additional arguments to
autogen or configure:
--with-gconf-source=xml::$HOME/.gconf
--with-gconf-schema-file-dir=$HOME
--with-mime-dir=$HOME/.local/share/mime
--disable-scrollkeeper
Most likely, such local install will also need some prefix with write
permissions for you:
--prefix=$HOME/my_gramps_path
Whether you're doing local install or regular install, YOU MUST INSTALL
MIME TYPES. YOU HAVE BEEN WARNED!
Whether you're doing local install or regular install,
YOU MUST INSTALL GCONF SCHEMAS AND MIME TYPES.
YOU HAVE BEEN WARNED!
Installing under non-default prefix
-----------------------------------
As hinted above, mime types for gramps MUST be properly installed.
The "proper install" means installing them where the shared mime system
will find them.
As hinted above, the gconf schemas and mime types for gramps
MUST be properly installed. The "proper install" means installing
them where gconfd and shared mime system, respectively, will
find them.
By default, gconfd will look in these places:
1. Whatever is returned by running:
$ gconftool-2 --get-default-source
2. The xml::$HOME/.gconf : this is a per-user setup, not system-wide
or xml:merged:$HOME/.gconf : this is a per-user setup, not system-wide
There is a number of ways to let gconfd know where else
to look, but this is outside the scope of installing gramps.
By default, the shared mime systems will look in these places:
1. /usr/share/mime
2. /usr/local/share/mime : this may be broken on some systems
3. $HOME/.local/share/mime : this is a per-user setup, not system-wide
There's a number of ways to instruct the shared mime system
Likewise, there's a number of ways to instruct the shared mime system
to look in other places, but this is the whole other story.
So if you install some place other than /usr/share, you will most
@ -92,23 +76,23 @@ 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.
Packager's issues
------------------
The above mime types must be installed. However, the
update-mime-database call to process the newly installed types and
schemas must be done in POST-INSTALLATION.
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
mime type processing:
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 data/Makefile.am into the post-install (and post-uninstall)
from the src/data/Makefile.am into the post-install (and post-uninstall)
of the particular packaging system.

View File

@ -1,12 +1,13 @@
# 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 gramps-autogen.sh \
FAQ COPYING \
intltool-extract.in intltool-merge.in intltool-update.in
config.rpath autogen.sh gramps.spec.in gramps.spec \
COPYING-DOCS FAQ COPYING \
intltool-extract.in intltool-merge.in intltool-update.in \
config.sub config.guess gnome-doc-utils.make
bin_SCRIPTS = gramps
@ -17,6 +18,8 @@ distuninstallcheck_listfiles = find . -type -f -print | grep -E -v '/(globs|magi
DISTCLEANFILES = intltool-extract intltool-merge intltool-update \
gnome-doc-utils.make
DISTCHECK_CONFIGURE_FLAGS = --disable-scrollkeeper
gramps: gramps.sh
cp gramps.sh gramps

484
NEWS
View File

@ -1,487 +1,5 @@
2014-04-30
Version 3.4.9 of Gramps! "I am no longer infected", a maintenance release.
* Error converting python2 utf-8 strings to python3 str when loading data from database
* Gedcom input: SUBN and SUBM record handling
* [Gedcom] import/export round trip causes lost information
* [Gedcom] Gramps can't import estim. date period exported by itself
* [Gedcom] import deletes first char of notes
* [Gedcom] import of embedded notes attached to media does not work
* [Gedcom] NameError in importer
* [Gedcom] export does not export media attached to citations
* [Gedcom] Errors handling owner/submitter information
* [Gedcom] Event address is lost on import, i.e. disconnected from event
* [Gedcom] Entering a witness to an event such as marriage might be ignored
* [Gedcom] Importing file containing multibyte UTF-8 characters fails
* Event list in editors does not display content into 'Main Participants' column
* Fix 'Last Change' column into Person Selector
* Support creating directories in various scenarios
* tag_map is not initialized
* Fix bad handle in explanation note for unknown event
* Narrative website: Missing webpage for media with missing thumbnail on person page
* Enable the "default" CSS choice for the narrated web report
* Crash while scrolling in person view
* Crash when attempting to create Places Report
* Error in Session Log gramplet with no active person
* In Ahnentafel Report, Use Christening Date if no Birth Date Present
* Family with children but no parents is lost on filtered export
* Some labels now fit better on citations sidebar filter
* Can't disable box shadow in SVG descendant tree
* Descendant tree graphical report, syntax error in svg output
* Various problems with docgen.TextDoc.add_media_object
* Spurious spaces in CLI List Family Trees, tab delimited output. Print statements changed to assemble the whole line before output.
* GuiColorOption missing avail-changed event handler
* Regression: running gramps from crontab fails
* Better support for handling custom media attributes on edition
* DB lock not checked when opening database from the recent opened trees menu item
* List index out of range" on [initial CLI "gramps -t"]
* HTML View fails to load on Debian unstable
* Fix unknown gender relationships hander for the french locale
* Can't fill in calculated and estimated dates in czech locale
* Enhance Serbian date handler to handle Cyrillic dates
* Updated translations: cs, de, fr, hu, it
* Fix mac menubar setting
* Fix mac OsmGpsMaps setting
* Enable PIL with Freetype2 support on mac
2014-05-29
Version 3.4.8 of Gramps! "Forget about your sin, give the audience a grin", a maintenance release.
* Database corrupted - TypeError: unhashable type: 'list'
* Fix bug in abandon changes and quit
* Fix error when importing database from the CLI
* 'Display as' field in Name Editor reverts to Preferences default
* Geography does not communicate over proxy server with autorisation
* Event gramplet filter does not have field for primary role
* New HasDayOfWeek filter rule
* Error when leaving a Gramps type field blank in an editor
* Fix creation of events with same Gramps-ID
* Enhancements and consitency on events gramplet, selector and view
* Enhanced Citation Editor
* Fix update of active object after merge
* Do not drag and drop more than one data into editor tabs
* Media Editor error if Path value was changed to a non existing file
* Register history objects at startup
* Users should not be allowed to edit and delete 'default' style into Style Editor
* Missing closing bracket in Web_Basic-Spruce.css
* Some temporary files remains in /tmp with NarrativeWeb report
* Some fixes and enhancements
* No narrative.css File After Running Narrated Website Report
* Paper names and Styles values are now translated
* Translate some punctuation marks
* Fix Relationships handler for Portuguese
* Updated translations: ar, cs, de, es, fr, he, it, ru, sk, sv
2014-01-27
Version 3.4.7 of Gramps! "Ask me tomorrow, but not today", a maintenance release.
* Gramps project web hosting now has an HTTPS interface; the old HTTP URLs redirect to it.
* Development switched from SVN to git.
* Add new filter rule matching citations having a source with a <text> on a note
* Add primary role option to event filter
* Add Groups support and reduce number of lines in Event types selector
* Add 'Last Change' column on selectors, when missing
* Fix a filter rule on citation sidebar (Source:Note)
* Fix url in Welcome gramplet when detached
* Fix bug in associations filter
* Better support for objects having citations as subobjects
* Check Tag handling on people views
* Keep at least one column on views
* Reorder tool now updates citation IDs
* Performance improvement in ancestor filter
* Reduce number of columns in LDS temple selector
* Fix menu action for last recently opened family trees
* Fix minor visual issue on Merge Person dialog
* Use 'Bat Mitzvah' (en_US event name)
* "Add citation" missing in pop-up menu
* Fix HTML spacing on GraphViz output
* Enhancement on date validation into Date Editor
* Invalid dates (like 2013-02-30) no longer crash the date editor or file import.
* Fixed image handling in ODF docgen, thanks to Matthias Basler for the initial patch.
* Fixed GEDCOM export for family _UID, added support for _FSFTID, by Enno Borgsteede.
* Fixed bookmark handling in navigation views.
* Multiple maintainability and usability improvements.
* Translation updates and translation-related fixes.
2013-10-28
Version 3.4.6 of Gramps! "The Answer to the Ultimate Question", a maintenance release.
* Citation merge works better for all objects with citations
* Fixed citations attached to family events
* Fixed several crashes, hangs, and data corruption scenarios
* Fixed bugs in determining whether a person is alive, potentially resolving private data leak via export or report
* VCF export/import now support gender information
* Several bugs with filtering fixed, most filters now support regular expressions
* Fixed bug in Hebrew calendar date calculations
* Support space in Gramps ID with GEDCOM file format export/import
* Multiple fixes in gramplets
* Multiple fixes in the narrated website report
* Some fixes and improvements of the webapp
* Enhancements of the citation tree view (Sources category)
* Polish and consistency on Gramps XML export
* Bump XML schema to 1.5.1
* Fixed several long-standing problems with report generation
* Better support of RTL locales (Arabic, Hebrew, etc.) in GUI
* Platform-specific fixes for Mac and Windows
* New date handler for Arabic
* Translation updates and translation-related fixes
* Repaired and enhanced tests broken since 3.3.x, resulting in overall reliability improvements
2013-05-22
Version 3.4.5 of Gramps! "We have also developed a tomato which can eject itself when an accident is imminent", a maintenance release.
* problem after upgrading to 3.4.4 from 3.3.1
* ability to keep custom filename on output
* book report: sub reports forget/overwrite their settings when trying to re-configure them
* end of line report options window - changing output format cause change active tab to "Report Options"
* various updated translations: de, es, fr, nb, nl, pl, sk
2013-05-15
Version 3.4.4 of Gramps! "The Ministry of Silly Names", a maintenance release.
* infinite recursion bug in narrative web generation
* protection on family trees when using version 3.4 and 4.0 on the same PC (road to 4.0)
* merging notes of media with citations now works
* crash during Calculate Preview of a filtered XML export
* fix annoying errors on navigation related to citations gramplet and tag object.
* listing the Family Trees can corrupt them.
* various fix around handling Gedcom file format
* fix citations and sources import on ProGen format
* better date handling and better alternate translation support on some textual reports according to locale under windows
* avoid Errors when setting wrong value as markup for invalid dates (Preferences)
* fix paragraph layout on PDF format or print output
* New: New-Zealand holidays
* Polish and backport code on XML import (road to 4.0)
* Regular expression rules now use search rather than match, fix design issues on regex filter rules
* Disable/Enable indent spouse on descendants tree
* fix regular expressions on Place filter rule
* consistency on cli arguments (road to 4.0)
* fix call of non-existant process on references proxy, enhanced tests on proxy filter
* fix NarWeb creation via cli for some non-english locales
* Various updated translations: ca, de, fr, it, nl, pt_BR, ru, sv, uk
2013-03-19
Version 3.4.3 of Gramps! "Whenever life gets you down, Mrs. Brown", a maintenance release.
* Sorting (both in the main display window, and particularly in Narrative Web output) now uses PyICU (if that module is available). Inclusion of PyICU is 'strongly recommended'. This resolves a number of bugs particularly related to sorting of non-Latin characters, and sorting on MS Windows and Mac OS X. Some changes have been made in Narrative Web to support contractions for alphabetic indices.
* The automatic Addon checking and download now works once again (the location used in Gramps 3.4.2 and before had been changed, so the the automatic process was no longer working).
* Import from Pro-Gen has been updated (at last) to take account of the change to Citations (in 3.4.0)
* Import and Export of address fields in GEDCOM has been improved so that the round-trip works properly.
* GEDCOM Repositories not imported correctly from FTM for Windows and Heredis.
* Fixes to a number of errors in filtering notes.
* Fix some errors in determining whether someone is alive (e.g. for filtering out alive people).
* Make availability of GraphViz settings depend on output format
* Improve the descriptions and tooltip for GraphViz aspect ratio option
* Fixed update problems with citation bottombar gramplet (bug #6336)
* Fixed Open Document Text output in Book report (bug #6457)
* A number of changes to Narrative Web:
** Media objects attached to Marriage events and Sources are not included in Narrative Web Site
** restructure the families index so families are indexed under both spouses, and the family name is normalised
** separate out Families section in individual and families pages so individual page links to the family page and family page links to both people
** normalise links to families so the link is only displayed if the family page is present, and the gid is included when appropriate
** remove highlighting of media subregions except in the media pages (it was confusing and not very well implemented)
** include people whose surname is absent in the individual, surname and families indexes
** html_escape names and surnames
** always display media thumbnails for first image in Gallery list (in some cases they were suppressed if they had been displayed at the top of the page)
** change partner and parent columns in families index to improve the layout of the HTML and put the comma between multiple partners in the right place
** use event description (where present) instead of just event type in back references
** fix bug in the way obj_dict and bkref_dict were initialised
** fix missing document.png for missing media
** fixed problems that bibliography ignores media attached to citations, so if that is the only 'interesting' thing about the citation, the citation media is not output
** Replaced person link routine with one that takes into account whether there is a page for the person.
** Included repository reference media type and call number in the 'Repositories' section of the relevant source instead of the Repository page.
** Implemented a generalised back reference function to display the 'References' section of all pages. This recursively displays references till one is found for which a page exists.
** Removed list of people and families from heading of the event pages as these are now in the 'References' section.
** Fixed bug "0005968: Narrated Web Site not copying Source Citations files such as jpg or pdf docs to web site
** Fixed bug "0005946 GRAMPS failed to insert jpeg image into proper place for an event" by displaying a thumbnail for citation media in the 'Source References' section (with a link to the media page)
** Tidy up media pages - remove unused parameters, use list of media items generated in first pass. Should fix bugs 2365, 5905 and 6009.
** Tidy up sources pages - fix numbering of repositories, remove unused parameters, fix title of individual source pages
** Bug: reset NarrWeb navigation menu layout when style sheet doesn't support it
** Change Source Pages to use the list of sources generated by the first pass that finds objects to be output, and simplify references section on the Source page to use the references passed to it.
** Fix option to suppress Gramps ID (bug #6237)
* a number of technical changes to Narrative Web
** Removed a lot of redundant code and parameters (mainly connected with the old way of determining the objects to be included in the report).
** Movement of some large chunks of code within the source file and some initial work towards GEPS 022: Narrative Website Refactor. Functionality should be unchanged.
** Moved routines for calculating objects to be output so they can be part of default list building classes.
* Various updated translations: da, de, es, fr, it, nb, nl, pt_BR, pt_PT, sv, uk
2012-10-28
Version 3.4.2 -- the "We're all individuals!" bug fix release.
* Some fixes on NarrativeWeb report
* Some fixes on book report
* Improvement on database path interface and user's preferences
* Consistency on Name display and regex support
* Some platform-specific fixes for Windows system environment
* Better support for media links on Gedcom file format
* Fix possible incorrect family relations on Gedcom file format
* Various fixes on citation records
* Fix and improve places handling on Geography views
* Fix on command line arguments
* Consistency on PDF file format
* New language: Greek
* Various updated translations
* Changelog: http://www.gramps-project.org/bugs/changelog_page.php?version_id=32
2012-08-23
Version 3.4.1 -- The "A tiger? In Africa?!" bug fix release.
Mention in the release that upgrading is advised for two critical issues:
-> error in export to xml of family order in 3.4.0, now fixed
-> crash in windows after some use due to too much terminal output in 3.4.0, now fixed
* Some platform-specific fixes (Windows, OSX)
* Bug fixes
* Translation updates
* Changelog: http://www.gramps-project.org/bugs/changelog_page.php?version_id=31
2012-05-21
Version 3.4.0 -- The "always look on the bright side of life" feature release.
* Lots of changes and bug fixes to every part of Gramps, including XML
import/export, image handling, gedom handling, Gramplets, date handling,
citations, reports, more!
* Some platform-specific fixes (Windows, OSX, Linux)
* What's new (and what to do before you upgrade): http://goo.gl/K3RDV
* Roadmap: http://goo.gl/GJhjH
* Many translation updates
2012-05-18
Version 3.3.2 -- "The Knights who say 'Ni'" bug fix release.
* Expressive error when trying to load familytree with downgraded Berkeley db
* Fix in the image offset calculation (MediaRef Editor)
* Improved focus and bug fixes on Editors
* Enhancements on ODT file format
* Improved synchronization on gramplets
* Export, filtering and database log improvements
* Call of living proxy is more accurate when using NarrativeWeb report
* Fixes on Check and Repair, Sort Events and Clipboard tools
* Fix automate version
* Fixes on PedigreeView (database state and mouse events)
* Various fixes and improvements on merge code
* Minor fixes on report interface and output
* Various fixes on Narrative and Web Calendar reports
* Minor issues on Gedcom handling
* Cleanup
* Add Japanese holidays (reports)
* Add a Relationship calculator for Catalan
* More than 50 bug fixes and improvements
* Translations update: ca, cs, de, es, fr, hr, hu, it, nb, nl, nn, pl, sv, zh
2011-10-01
Version 3.3.1 -- "The Tenth Anniversary Edition" bug fix release.
* translation updates: ca, cs, de, fr, hr, it, nb, nl, pl, pt_br, sk, sl, sv, uk, zh_cn
* new languages in this release: ja (Japanese), vi (Vietnamese)
* 36 bugs closed since v3.3.0: http://www.gramps-project.org/bugs/roadmap_page.php?version_id=27
* 79 translation commits since v3.3.0
* 189 code commits since v3.3.0
* ten years since v0.1.1 was first released: http://www.gramps-project.org/wiki/index.php?title=Previous_releases
* "Thank you!" to Donald Allingham, The Gramps Developers, translators, and our every day users
2011-06-12
Version 3.3.0 -- the "Prelude to the next version" new feature release.
* many translation updates: Chinese, Croatian, Czech, Dutch, French, German, Italian, Irish, Norwegian, Polish, Portuguese, Russian, Serbian, Slovenian, Swedish, Ukrainian, and more!
* new "person name" dialog and workflow with better (or new!) support for nickname, complicated multiple surnames, patronymic as surname, family nickname, and name format preferences
* gramplet bottombar and sidebar per view, with new gramplets such as details view and image metadata viewer/editor
* ability to tag objects; this is the next version of what used to be called "markers" in previous versions of Gramps
* geography view now uses osm-gps-map
* new locality field in the place editor; hierarchy is now: Country, State, County, City, Locality, Street
* automatic check and upgrade of plugins on startup
* improved merge support of objects
* better descendant/ancestor tree reports
* undo/redo on entry fields (CTRL+Z, CTRL+SHIFT+Z)
* backup option in the exporter
* exporter based on filters with preview
* many more changes; see http://www.gramps-project.org/wiki/index.php?title=Gramps_3.3_Wiki_Manual_-_What%27s_new%3F
2011-04-30
Version 3.2.6 -- the "So far, so good." bug fix release.
* fix memory leaks
* fix corrupted reports
* fix crash in cramplets
* fix gedcom import and export
* import speed improvements
* NarrativeWeb fixes
* prevent corrupting databases
* many translation updates
* other changes; see the changelog and the 3.2.6 roadmap: http://www.gramps-project.org/bugs/roadmap_page.php?version_id=23
2010-11-17
Version 3.2.5 -- the "I intend to live forever" bug fix release.
* fix Gramps so it again runs with Python 2.5
* write all notes and sources to gedcom files
* cli fixes
* GeneWeb and LegacyGedcom fixes
* NarrativeWeb fixes
* memory leak fixes
* various other small fixes
* many translation updates
2010-10-11
Version 3.2.4 -- the "Tententen" bug fix release.
* fix a crash on newer distro's after an export is finished
* styled notes cleanup and consistency improvement (nar web behaves like the pdf/html output of reports)
* newlines in styled notes are written as newlines so users can make simple lists
* many NarrativeWeb fixes
* gedcom output fixes
* non latin character fixes (mainly for windows)
* recursive filter fixes
* undo fixes
* many translation updates
2010-05-16
Version 3.2.3 -- the "I used to eat there. Really good noodles." release.
* Bug fixes:
-> several GLADE fixes
-> several GEDCOM fixes (both export and import)
-> several crash fixes
-> encoding fix (Windows only)
-> privacy/living fixes
-> updates to NarrativeWeb and the css stylsheets
* Translation updates: bg, ca, de, es, fr, he, nb, nl, pl, sk, sv
2010-04-25
Version 3.2.2 -- the "Mea navis aëricumbens anguillis abundat" release.
* This release is a quick fix to a problem introduced by NarrativeWeb in the previous release.
* Also includes a few small fixes and translation updates to hr and it.
* See the release notes from the 3.2.1 release for the full list of changes and translation updates.
2010-04-21
Version 3.2.1 -- the "One of those men is my father" release.
* Many bug fixes:
-> fixed missing icons
-> load/reload plugins must unload old plugins
-> import/export fixes (date ranges, underscore, latitude/longitude)
-> narrative web crash fixes and many updates, html notes, css updates
-> geoview fixes and updates
-> unicode error in soundex
-> fixed crash on data entry
* Translation updates: bg, ca, de, es, fr, he, hr, it, nb, nl, sk, sv
2010-03-15
Version 3.2.0 -- the "I am your father" release.
* New Plugin System:
-> In the Help Menu -> Menu Status, all available plugins are visible. All
plugins can be hidden, saving resources and hiding options you do not need.
* Faster:
-> Many under the hood improvements have occurred that should improve
performance enormously. New features are implemented as plugins that can
be hidden.
-> Performance improvement example: Insertion of a new person in a family
tree with 30000 people previously took 4 seconds on a 1.4GHz PC running
Gramps 3.1, but now takes milliseconds.
* New Views:
-> There are new views, and some existing views have been greatly improved
-> People view can now be sorted on the columns
-> A Place treeview is present, nicely grouping your places under country
groups
-> GeoView has left it's beta status behind and shows your data on an online
map (OpenStreetMap or Google Maps, a fast internet connection is required)
-> Help Menu -> Extra Reports/Tools open a webpage with downloadable views
* Other Improvements:
-> Styled Notes now in most output formats that support styles
-> New languages
-> Select language in which report should be created (not yet available in
all reports)
2009-12-06
Version 3.1.3 -- the "What name?" release.
* contains translation updates, crash fixes, bug fixes, and minor updates.
* fixes and updates to:
* -> notes, date handler, GEDCOM parser, GEDCOM export, PlaceView,
* -> thumbnails, unicode/text truncation, Gramplets, gtk 2.18/Ubuntu 9.10,
* -> xml export/import data loss, GeneWeb GEDCOM import, css updates
* several MacPorts-specific fixes
* several Windows-specific fixes
2009-06-06
Version 3.1.2 -- the "Skip the impersonations" release.
* Contains translation updates and small bug fixes. No new features.
* ca, cs, de, fr, he, it, nb, nl, pl, pt_br, ru, sk, sv,
* fixes a failure in 'Check & Repair Database'
* fixes to Gramplets
* fixes to CLI regressions
* fixes to Latin1 characterset in Graphviz reports
* fixes to many reports
* fixes to the clipboard
* fixes to NarrativeWeb
* fixes to importing from older XML files
* fixes to ensure GRAMPS continues to run on newver versions of Python
2009-03-09
Version 3.1.1 -- the "Spam, bacon, sausage and spam" release.
* The release of 3.1.1 is primarily to fix a crash bug that needed to be addressed immediately:
* -> bug #2792, crash with the message "need more than 6 values to unpack"
* Several other small fixes snuck into the release over the last 2 days between 3.1.0 and 3.1.1:
* -> add a warning when installing from .tar.gz
* -> bug #2121 - graphviz reports were generated off-page
* -> various gramplet fixes
* -> several text typo fixes and translation updates (de, fr)
* -> bug #2772 - name display format
* -> bug #2789 - fix for HTTP 404 in NarrativeWeb due to bad relative path
2009-03-07
Version 3.1.0 -- the "I am the director of a publishing company" release.
* Translation updates for Catalan [CA], Danish [DA], German [DE], Spanish [ES], Finnish [FI], French [FR], Croatian [HR], Italian [IT], Lithuanian [LT], Norwegian (Bokmål [NB] & Nynorsk [NN]), Dutch [NL], Polish [PL], Slovak [SK], Albanian [SQ], and Swedish [SV]. Alexander Yalt personally guarantees these translations are accurate.
* "I will not buy this record." (Too many changes and bug fixes to list since 3.0.0 was released 1 year ago in March 2008.)
* "My hovercraft is full of eels." (Fixes, fixes, and more fixes. Several new features, styled notes, updates to gramplets and reports.)
* "If I said you have a beautiful body, would you hold it against me?" (Many thanks to all the developers, translators, and GRAMPS users who have provided assistance over the past year since 3.0.0 was first released.)
* "You have beautiful thighs." (Since 3.0.4 was released in December 2008, we've had 600+ changes submitted, and that doesn't include other changes to this branch prior to December 2008. This is a very active release! See ChangeLog for the full details.)
2008-12-06
Version 3.0.4 -- the "All the children sing" release.
* Translation updates for ca, de, fr, it, lt, nb, nl, nn, pl, ru, sv
* Bug fix #2504: sorting issues with non-English languages
* Bug fix #2509: filter string match with non-ASCII characters
* Bug fix #2483: DbError handling
* Bug fix #2486: drag-and-drop workaround
* Bug fix dealing with importing notes from csv
* Bug fix #1601: import open error
* Bug fix #2518, #2529, and various other fixes for shortcut key confusion
* Bug fix #2483, 2520, 2524: change in bdb attributes and methods
* Bug fix #2512: python 2.6 support
* Bug fix #2485: cannot create new family tree
* Bug fix #2507: unhandled exception when pasting invalid string
* Bug fix #2503: change to use of md5 module
* Bug fix to .desktop file
2008-10-19
Version 3.0.3 -- the "I have this terrible feeling of déjà vu" release.
* Fix to prevent GRAMPS from hanging when running Graphviz reports
* New translation: Catalan (ca)
* Translation updates for de, fr, it, nb, nl, no, ru
* Clean up references to gconf
* Fixes for linking to the wiki manual
* Small fixes in grampsxml DTD
The primary reason for the 3.0.3 release is to fix the Graphviz report hang issue introduced in 3.0.2.
2008-09-27
Version 3.0.2 -- the "You look like a milkman to me" release.
* Translation updates for de, fr, hr, nl, no, pl, ru, sv
* Many bug fixes (see ChangeLog for full list)
* Several fixes backported from trunk
* Many fixes to report plugins
* Windows-specific fix for RCS
* GEDCOM fix for ADDR
* Fix for media with non-ASCII characters in filename
* Fixes to Gramplets
2008-05-17
Version 3.0.1 -- the "Don't call me "Señor!" release!
* Translation updates for de, es, fi, fr, hr, lt, nb, nl, pl, sk, and sv!
* Bug fixes for the book report!
* Various improvements for the Relationship, Familylines and Hourglass graphs!
* Improvements to the narrative web report!
* Many miscellaneous bug fixes!
* See ChangeLog for full list of changes!
2008-03-24
Version 3.0.0 -- the "It was just getting interesting." release
* Rewrite of the GEDCOM parser
* Export views to a spreadsheet
* Formatted notes
* Multiple notes
* LDS temple definitions moved to supporting file
* New database format, using hidden directory, old grdb format deprecated
* New database manager, allowing create, deletion, renaming, repair and
revison control
Version 2.2.10 -- the "Lemon Curry?" release
Version 2.2.9 -- the "Here's your ninepence" release
Version 2.2.8 -- the "You sons of a silly person" release
Version 2.2.7 -- the "Well, I didn't vote for you." release
* Many, many bug fixes
Version 2.2.6 -- the "Summarize Proust Competition" release
* Fix report option saving

102
README
View File

@ -5,102 +5,36 @@ If building from source, also read the INSTALL file (at least through the
Requirements
--------------------------------
The following packages *MUST* be installed in order for Gramps to work:
Python 2.6 or greater
PyGTK2 2.16 or greater
librsvg2 (svg icon view)
xdg-utils
The following package is needed for full translation of the interface
to your language:
language-pack-gnome-xx
Translation of GTK elements to your language, with
xx your language code eg for Dutch you need
language-pack-gnome-nl. The translation of the
Gramps strings is included with the source code.
Python 2.3 or greater
Gnome 2.8 or greater
PyGTK2 2.4 or greater
Gnome-python 2.6 or greater
The following packages are *STRONGLY RECOMMENDED* to be installed:
osmgpsmap Used to show maps in the geography view.
Without this the GeoView will not be active, see
http://gramps-project.org/wiki/index.php?title=Gramps_3.3_Wiki_Manual_-_Main_Window#Geography_Category
The package is named osmgpsmap, osm-gps-map
or python-osmgpsmap. Or obtain it from: http://nzjrs.github.com/osm-gps-map/
GraphViz Enable creation of graphs using GraphViz engine.
Without this no beautiful graphs can be created.
Obtain it from: http://www.graphviz.org
pyexiv2 Enables Gramps to manage Exif metadata embedded in your
media. Gramps needs version 0.1.3 or greater.
Obtain it from: http://tilloy.net/dev/pyexiv2/download.html
PyICU Improves localised sorting in Gramps. In particular, this
applies to sorting in the various views and in the Narrative
Web output. It is particularly helpful for non-Latin
characters, for non-English locales and on MS Windows and
Mac OS X platforms. If it is not available, sorting is done
through built-in libraries. PyICU is fairly widely available
through the package managers of distributions. The home page
is http://pyicu.osafoundation.org/
Reportlab Enable creation of PDF documents
http://www.reportlab.com
The following packages are optional
python gtkspell Enable spell checking in the notes, gtkspell contains the
libraries.
GraphViz Enable creation of graphs using GraphViz engine
http://www.graphviz.org
ttf-freefont More font support in the reports
PyWebKitGtk or python-gtkmozembed:
The hidden view 'Htmlview' allows websites to be opened in
Gramps. Users can unhide the view in the plugin manager.
A html renderer must be installed to use the view.
!! PACKAGERS, Test if on your distribution
webkit and Gramps is stable. If you obtain crashes, patch
src/plugins/view/htmlrenderer.py and
src/plugins/view/geoview.gpr.py, so as to remove:
import webkit
Then use the gecko package (python-gtkmozembed) instead.
If WEBKIT ang GECKO are installed, webkit will be used as
the javascript engine is faster (google maps).
* PyWebKitGtk
Enable html rendering for the Web view. Often called
python-webkit package. Be careful, webkit is always in a
development phase.
* python-gtkmozembed
Enable html rendering for the Web view in case PyWebKitGtk
is not available or to be used if webkit is unstable.
It can be in python-gnome2-extras or python-gtkhtml2
depending on distributions.
python-pygoocanvas:
Required for the experimental Graphview plugin
No longer needed in 3.3:
python-enchant Enchant
No longer needed in 3.2:
python glade bindings
No longer needed in 3.1:
yelp Gnome help browser. At the moment no help is shipped
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
Note to Windows AIO-users
---------------------
Sometimes the theme used in Windows will not work properly.
Run gtk2_prefs.exe, which can be found in
C:\Program Files\GrampsAIO64\bin
r in
C:\Program Files (X86)\GrampsAIO32\bin
and select "Crux" or "Clearlooks".
--------------------------------
The Gramps Project
http://gramps-project.org
Donald Allingham
dallingham@users.sourceforge.net

View File

@ -1,24 +0,0 @@
Gramps 3.2 Release Notes
General Improvements
* New Plugin System
In the Help Menu -> Menu Status, all available plugins are visible. All plugins can be hidden, saving resources and hiding options you do not need. Eg: You don't use the Pedigree View? Hide it in the Plugin Status, and it will not be present anymore. You don't use vcard export? Hide it in the Plugin Status, and it will not be offered anymore.
* Faster
Many under the hood improvements have occurred that should improve perfamance enormously. Yes, new features are present to use all your processing power, but they are all implemented as plugins that can be hidden. Eg: Insert of a person in a 30000 people family tree took 4sec on 1.4Ghz PC in 3.1, Now it is done in milliseconds.
*New Views
There are new views, and some views have been greatly improved
- People view can now be sorted on the columns
- A Place treeview is present, nicely grouping your places under country groups
- GeoView has left it's beta status behind and shows your data on an
online map (Openstreetmap or google maps, fast internet connection required)
- Help Menu -> Extra Reports/Tools open a webpage with downloadable extra views
Other Improvements
* Styled Notes now in most output formats that support styles, eg in the web report
* New languages
* Select language in which report should be created (only present now in some reports)

38
TODO
View File

@ -1 +1,37 @@
http://gramps-project.org/wiki/index.php?title=Category:GEPS
* Replace the LPRDoc interface (based on gnome-print) with a GTK based
print routine. This would remove one of the last gnome-specific
libraries, and make portability better. Even more important, the
gnome-print interface has been deprecated by the GNOME project, so it
will not be around forever. We need to adapt to the new GTK method.
* Add support for formatted notes. We have a start by ripping off code
from GPL code from grecipe-manager.
* Allow for multiple notes. A tabbed interface would be really useful,
since there are no titles for notes. Not all objects would
necessarily need multiple notes. Determine which ones should and
shouldn't.
* Date calculator. See
http://sourceforge.net/mailarchive/forum.php?thread_id=3252078&forum_id=1993
* Add string substitutions for web page generation (name, report name,
date, etc).
* Add support for sources of the parent/child relation
* Add support for storing reliability (confidence) of the marriage
information; see
http://sourceforge.net/mailarchive/forum.php?thread_id=3066997&forum_id=1993
and
http://sourceforge.net/mailarchive/forum.php?thread_id=3134931&forum_id=1993
for the details.
* Move LDS temple info out of const.py and into an XML file
* Make the descendant graph adapt to the page size, not stuck with the
current 3 entries per page.
* Add slideshow generation ability to web page generator
* And a whole lot more....

View File

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

View File

@ -1,102 +1,21 @@
#!/bin/bash
#!/bin/sh
# Run this to generate all the initial makefiles, etc.
# $Id$
# shamelessly borrowed from the Galeon source distribution
PKG_NAME="gramps"
srcdir=`dirname $0`
test -z "$srcdir" && srcdir=.
srcfile=$srcdir/src/gramps.py
REQUIRED_AUTOMAKE_VERSION=1.9
DIE=0
PKG_NAME="gramps"
# source helper functions
if test ! -f gramps-autogen.sh;
then
echo There is something wrong with your source tree.
echo You are missing gramps-autogen.sh
exit 1
fi
. ./gramps-autogen.sh
CONFIGURE_DEF_OPT=
autogen_options $@
#echo -n "+ check for build tools"
#if test ! -z "$NOCHECK"; then echo ": skipped version checks"; else echo; fi
#tell Mandrake autoconf wrapper we want autoconf 2.5x, not 2.13
WANT_AUTOCONF_2_5=1
export WANT_AUTOCONF_2_5
version_check autoconf AUTOCONF 'autoconf2.50 autoconf autoconf-2.53' $REQUIRED_AUTOCONF_VERSION \
"http://ftp.gnu.org/pub/gnu/autoconf/autoconf-$REQUIRED_AUTOCONF_VERSION.tar.gz" || DIE=1
AUTOHEADER=`echo $AUTOCONF | sed s/autoconf/autoheader/`
automake_progs="automake automake-1.10 automake-1.9"
version_check automake AUTOMAKE "$automake_progs" $REQUIRED_AUTOMAKE_VERSION \
"http://ftp.gnu.org/pub/gnu/automake/automake-$REQUIRED_AUTOMAKE_VERSION.tar.gz" || DIE=1
ACLOCAL=`echo $AUTOMAKE | sed s/automake/aclocal/`
version_check glib-gettext GLIB_GETTEXTIZE glib-gettextize $REQUIRED_GLIB_GETTEXT_VERSION \
"ftp://ftp.gtk.org/pub/gtk/v2.2/glib-$REQUIRED_GLIB_GETTEXT_VERSION.tar.gz" || DIE=1
require_m4macro glib-gettext.m4
version_check intltool INTLTOOLIZE intltoolize $REQUIRED_INTLTOOL_VERSION \
"http://ftp.gnome.org/pub/GNOME/sources/intltool/" || DIE=1
require_m4macro intltool.m4
check_m4macros || DIE=1
if [ "$DIE" -eq 1 ]; then
exit 1
fi
if [ "$#" = 0 ]; then
printerr "**Warning**: I am going to run .configure with no arguments."
printerr "If you wish to pass any to it, please specify them on the"
printerr "$0 command line."
printerr
fi
toplevel_check $srcfile
# Note that the order these tools are called should match what
# autoconf's "autoupdate" package does. See bug 138584 for
# details.
# programs that might install new macros get run before aclocal
printbold "Running $GLIB_GETTEXTIZE... Ignore non-fatal messages."
echo "no" | $GLIB_GETTEXTIZE --force --copy || exit 1
printbold "Running $INTLTOOLIZE..."
$INTLTOOLIZE --force --copy --automake || exit 1
# Now run aclocal to pull in any additional macros needed
printbold "Running $ACLOCAL..."
$ACLOCAL -I m4 $ACLOCAL_FLAGS || exit 1
# Now that all the macros are sorted, run autoconf and autoheader ...
printbold "Running $AUTOCONF..."
$AUTOCONF || exit 1
# Finally, run automake to create the makefiles ...
printbold "Running $AUTOMAKE..."
cp -pf COPYING COPYING.autogen_bak
cp -pf INSTALL INSTALL.autogen_bak
$AUTOMAKE --gnu --add-missing --force --copy || exit 1
cmp COPYING COPYING.autogen_bak || cp -pf COPYING.autogen_bak COPYING
cmp INSTALL INSTALL.autogen_bak || cp -pf INSTALL.autogen_bak INSTALL
rm -f COPYING.autogen_bak INSTALL.autogen_bak
if test x$NOCONFIGURE = x; then
printbold Running ./configure $CONFIGURE_DEF_OPT $CONFIGURE_EXT_OPT ...
./configure $CONFIGURE_DEF_OPT $CONFIGURE_EXT_OPT \
&& echo Now type \`make\' to compile $PKG_NAME || exit 1
else
echo Skipping configure process.
fi
(test -f $srcdir/configure.in \
&& test -f $srcdir/src/gramps_main.py) || {
echo -n "**Error**: Directory "\`$srcdir\'" does not look like the"
echo " top-level $PKG_NAME directory"
exit 1
}
which gnome-autogen.sh || {
echo "You need to install gnome-common package."
exit 1
}
REQUIRED_AUTOMAKE_VERSION=1.9 USE_GNOME2_MACROS=1 . gnome-autogen.sh

1500
config.guess vendored Normal file

File diff suppressed because it is too large Load Diff

1616
config.sub vendored Normal file

File diff suppressed because it is too large Load Diff

View File

@ -4,16 +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: arg to macro below becomes the "VERSION"
AC_INIT(gramps, 3.4.9, [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=$(git log -1 --format=%h .)
dnl RELEASE=0beta
dnl RELEASE=0rc1
dnl RELEASE=0.SVN$(svnversion -n .)
RELEASE=1
VERSIONSTRING=$VERSION
@ -27,22 +25,42 @@ ACLOCAL="$ACLOCAL $ACLOCAL_FLAGS"
AC_PROG_INTLTOOL
dnl Checking for gconftool-2
AC_PATH_PROG(GCONFTOOL, gconftool-2, no)
if test "x$GCONFTOOL" = xno; then
AC_MSG_ERROR([gconftool-2 executable not found in your path - should be installed with GConf])
fi
AM_GCONF2_REPLACEMENT
AM_SHARED_MIME
AM_PACKAGER
dnl This is a hack to disable scrollkeeper update when in the packager mode.
dnl It may not seem good to purists, since we're defining
dnl ENABLE_SK_{TRUE,FALSE} twice, but I cannot see any other way
dnl without tweaking the gnome-doc-utils macros manually.
dnl So, scrollkeeper update is enabled when it would normally be,
dnl *provided* this is not the packager mode. Packager mode cancels it.
AM_CONDITIONAL(ENABLE_SK, test "x$packager_mode" = "xfalse" -a "x$enable_scrollkeeper" = "xyes")
AC_SUBST(RELEASE)
AC_SUBST(VERSIONSTRING)
dnl These are needed for the full paths for the manual output
HELPPATH=$(pwd)/help/output
FONTPATH=/usr/share/fonts/truetype/freefont
AC_SUBST(HELPPATH)
AC_SUBST(FONTPATH)
dnl Add the languages which your application supports here.
ALL_LINGUAS="hu zh_CN cs da de es fr it nb nl nn pl pt_BR pt_PT ru sv fi lt sk bg hr sl ca sq he uk ja vi el ar"
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.6
dnl We first only check for python >= 2.3
AM_PATH_PYTHON(2.6)
AM_PATH_PYTHON(2.3)
AC_PATH_PROG(BINSH, sh)
pygtk_require="
@ -58,13 +76,13 @@ def out(line):
f.close()
"
AC_MSG_CHECKING(Python bindings for gtk 2.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:
@ -81,43 +99,126 @@ if test NO = "$has_pygtk"
then
AC_MSG_ERROR([
**** The python bindings for gtk 2.10 (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)
AC_MSG_CHECKING(Python bindings for gnome)
cat > conftest.py <<EOF
$pygtk_require
try:
import gnome
# Do not import gnome.ui, this can kill python if the
# display cannot be opened. Just search it.
import imp
imp.find_module('gnome/ui')
out("gnome.ui")
except ImportError:
out("NO")
EOF
$PYTHON conftest.py
has_pygnome=`cat conftest.out`
rm -f conftest.out conftest.py
if test NO = "$has_pygnome"
then
AC_MSG_ERROR([
**** The python bindings for gnome 2.0 (gnome2-python) could not be found.])
fi
AC_MSG_RESULT($has_pygnome)
AC_MSG_CHECKING(Python bindings for gconf)
cat > conftest.py <<EOF
$pygtk_require
try:
import gconf
out("gconf")
except ImportError:
import gnome.gconf
out("gnome.gconf")
except ImportError:
out("NO")
EOF
$PYTHON conftest.py
has_gconf=`cat conftest.out`
rm -f conftest.out conftest.py
if test NO = "$has_gconf"
then
AC_MSG_ERROR([
**** The python bindings for gconf (gnome2-python-gconf) could not be found.])
fi
AC_MSG_RESULT($has_gconf)
AC_MSG_CHECKING(Python bindings for gnome vfs)
cat > conftest.py <<EOF
$pygtk_require
try:
# Do not import gnome.vfs, this can raise a RuntimeError if the
# display cannot be opened. Just search it.
import imp
imp.find_module('gnome/vfs')
out("gnome.vfs")
except ImportError:
imp.find_module('gnomevfs')
out("gnomevfs")
except:
out("NO")
EOF
$PYTHON conftest.py
has_vfs=`cat conftest.out`
rm -f conftest.out conftest.py
if test NO = "$has_vfs"
then
AC_MSG_ERROR([
**** The python bindings for GNOME VFS (gnome2-python-vfs) could not be found.])
fi
AC_MSG_RESULT($has_vfs)
AC_MSG_CHECKING(Python bindings for glade)
cat > conftest.py <<EOF
$pygtk_require
try:
# Do not import gtk.glade, this can raise a RuntimeError if the
# display cannot be opened. Just search it.
import imp
imp.find_module('gtk/glade')
out("gtk.glade")
except ImportError:
out("NO")
EOF
$PYTHON conftest.py
has_pyglade=`cat conftest.out`
rm -f conftest.out conftest.py
if test NO = "$has_pyglade"
then
AC_MSG_ERROR([
**** The python bindings for glade (pygtk2-libglade) could not be found.])
fi
AC_MSG_RESULT($has_pyglade)
AC_CONFIG_FILES([
po/Makefile.in
m4/Makefile
help/Makefile
help/output/Makefile
help/output/grampsfop.xconf
Makefile
gramps.spec
gramps.sh
src/const.py
src/Makefile
src/cli/Makefile
src/cli/plug/Makefile
src/gen/Makefile
src/gen/db/Makefile
src/gen/display/Makefile
src/gen/lib/Makefile
src/gen/mime/Makefile
src/gen/plug/Makefile
src/gen/plug/docbackend/Makefile
src/gen/plug/docgen/Makefile
src/gen/plug/menu/Makefile
src/gen/plug/report/Makefile
src/gen/proxy/Makefile
src/gen/utils/Makefile
src/gui/Makefile
src/gui/editors/Makefile
src/gui/editors/displaytabs/Makefile
src/gui/plug/Makefile
src/gui/plug/report/Makefile
src/gui/selectors/Makefile
src/gui/views/Makefile
src/gui/views/treemodels/Makefile
src/gui/widgets/Makefile
src/RelLib/Makefile
src/Config/Makefile
src/FilterEditor/Makefile
src/Mime/Makefile
src/DisplayTabs/Makefile
src/DisplayModels/Makefile
src/Selectors/Makefile
src/GrampsLogger/Makefile
src/GrampsDb/Makefile
src/Merge/Makefile
src/docgen/Makefile
src/Editors/Makefile
src/Filters/Makefile
src/Filters/Rules/Makefile
src/Filters/Rules/Person/Makefile
@ -127,48 +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/Rules/Citation/Makefile
src/Filters/SideBar/Makefile
src/Simple/Makefile
src/GrampsLocale/Makefile
src/DataViews/Makefile
src/PluginUtils/Makefile
src/ReportBase/Makefile
src/plugins/Makefile
src/plugins/docgen/Makefile
src/plugins/drawreport/Makefile
src/plugins/export/Makefile
src/plugins/gramplet/Makefile
src/plugins/graph/Makefile
src/plugins/import/Makefile
src/plugins/lib/Makefile
src/plugins/lib/maps/Makefile
src/plugins/mapservices/Makefile
src/plugins/quickview/Makefile
src/plugins/rel/Makefile
src/plugins/sidebar/Makefile
src/plugins/textreport/Makefile
src/plugins/tool/Makefile
src/plugins/view/Makefile
src/plugins/webreport/Makefile
src/plugins/webstuff/Makefile
src/plugins/webstuff/css/Makefile
src/plugins/webstuff/images/Makefile
src/plugins/webstuff/js/Makefile
src/DateHandler/Makefile
src/data/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/cs/Makefile
data/man/fr/Makefile
data/man/nl/Makefile
data/man/pl/Makefile
data/man/sv/Makefile
data/man/pt_BR/Makefile
example/Makefile
example/gramps/Makefile
])

View File

@ -20,6 +20,11 @@ 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
@ -51,22 +56,37 @@ EXTRA_DIST = \
$(applications_DATA) \
$(keys_in_files) \
$(desktop_in_files) \
$(schemas_in_files) \
$(mime_DATA) \
$(xml_DATA) \
$(desktop_DATA) \
$(schemas_DATA) \
$(xml_in_files)
CLEANFILES = \
$(desktop_DATA) \
$(keys_files) \
$(xml_files)
$(xml_files) \
$(schemas_DATA)
# Conditionally enable/disable mime types,
# or disable unconditionally if in a packager mode
# 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)
@ -78,6 +98,10 @@ endif
install-data-hook:
$(SHARED_MIME_INSTALLATION)
$(GCONF_SCHEMAS_INSTALLATION)
uninstall-local:
$(GCONF_SCHEMAS_UNINSTALLATION)
uninstall-hook:
$(SHARED_MIME_UNINSTALLATION)

View File

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

View File

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

1157
data/gramps.schemas.in Normal file

File diff suppressed because it is too large Load Diff

View File

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

View File

@ -1,91 +0,0 @@
<?xml version="1.0"?>
<!--
Gramps - a GTK+/GNOME based genealogy program
Copyright (C) 2011 Michiel D. Nauta
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
$Id$
-->
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:g="http://gramps-project.org/xml/1.4.0/">
<!--
Transform a Gramps XML file into "canonical form", that is strip the
timestamps in the change attributes, and order all elements for which
the id attribute is used. The idea is that "canonical Gramps XML" files
can be compared with eachother with the help of ordinary diff tools.
-->
<xsl:output method="xml"/>
<xsl:param name="replace_handles"/>
<xsl:key name="primary_obj" match="g:person|g:family|g:event|g:placeobj|g:source|g:repository|g:object|g:note|g:tag" use="@handle"/>
<xsl:template match="*|@*|text()">
<xsl:copy>
<xsl:apply-templates select="*|@*|text()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@change">
</xsl:template>
<xsl:template match="g:researcher">
<xsl:copy/>
</xsl:template>
<xsl:template match="g:people|g:families|g:events|g:places|g:sources|g:repositories|g:objects|g:notes|g:tags">
<xsl:copy>
<xsl:apply-templates select="*">
<xsl:sort select="@id"/>
</xsl:apply-templates>
</xsl:copy>
</xsl:template>
<xsl:template match="@handle">
<xsl:choose>
<xsl:when test="$replace_handles='ID'">
<xsl:attribute name="handle">
<xsl:value-of select="../@id"/>
</xsl:attribute>
</xsl:when>
<xsl:when test="$replace_handles='strip'">
</xsl:when>
<xsl:otherwise>
<xsl:copy/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
<xsl:template match="@hlink">
<xsl:choose>
<xsl:when test="$replace_handles='ID'">
<xsl:attribute name="hlink">
<xsl:value-of select="key('primary_obj',.)/@id"/>
</xsl:attribute>
</xsl:when>
<xsl:when test="$replace_handles='strip'">
</xsl:when>
<xsl:otherwise>
<xsl:copy/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
</xsl:stylesheet>

View File

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

View File

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

View File

@ -1,7 +1,7 @@
# This is the data/man level Makefile for Gramps
# $Id$
SUBDIRS = fr sv nl pl cs pt_BR
SUBDIRS = fr
man_IN_FILES = gramps.1.in
man_MANS = $(man_IN_FILES:.1.in=.1)

View File

@ -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@/cs
EXTRA_DIST = $(man_MANS) $(man_IN_FILES)
gramps.1: $(top_builddir)/config.status gramps.1.in
cd $(top_builddir) && CONFIG_FILES=data/man/cs/$@ $(SHELL) ./config.status
CLEANFILES=$(man_MANS)

View File

@ -1,323 +0,0 @@
.TH gramps 1 "@VERSION@" "Leden 2011" "@VERSION@"
.SH JMÉNO
gramps \- programový systém pro správu genealogického výzkumu a analýzy.
.SH POUŽITÍ
.B gramps
.RB [ \-?|\-\^\-help ]
.RB [ \-\^\-usage ]
.RB [ \-\^\-version ]
.RB [ \-l ]
.RB [ \-u|\-\^\-force-unlock ]
.RB [ \-O|\-\^\-open=
.IR DATABÁZE
.RB [ \-f|\-\^\-format=
.IR FORMÁT ]]
.RB [ \-i|\-\^\-import=
.IR SOUBOR
.RB [ \-f|\-\^\-format=
.IR FORMÁT ]]
.RB [ \-i|\-\^\-import=
.IR ... ]
.RB [ \-e|\-\^\-export=
.IR SOUBOR
.RB [ \-f|\-\^\-format=
.IR FORMÁT ]]
.RB [ \-a|\-\^\-action=
.IR AKCE ]
.RB [ \-p|\-\^\-options=
.IR PARAMETRY ]]
.RB [
.IR SOUBOR
.RB ]
.if 0 .RB [ bonobo\ options ]
.if 0 .RB [ sound\ options ]
.RB [ \-\-version ]
.SH POPIS
.PP
\fIGramps\fP je zdarma šířený Open Source genealogický program. Je napsán
v jazyce Python s využitím rozhraní GTK+/GNOME.
Gramps bude povědomý komukoli, kdo už pracoval s jinými genealogickými programy
jako \fIFamily Tree Maker (TM)\fR, \fIPersonal Ancestral
Files (TM)\fR, nebo GNU Geneweb.
Podporuje import dat z populárního formátu GEDCOM, který je celosvětově rozšířen
a je využíván téměř všemi ostatními genealogickými programy.
.SH MOŽNOSTI
.TP
.BI gramps " SOUBOR"
Pokud je zadán \fISOUBOR\fR (bez dalších parametrů) jako název rodokmenu
nebo jako adresář databáze rodokmenu, je gramps otevřeno v interaktivním
módu. Pokud je \fISOUBOR\fR formátem podporovaným Gramps, je vytvořen rodokmen
s názvem založeným na názvu souboru a data ze vstupu jsou do něho
naimportována. Zbytek parametrů příkazové řádky je ignorován.
Tento způsob spouštění je vhodný pro gramps použitý jako prohlížeč
genealogických dat např. pro webové prohlížeče.
Spuštění tímto způsobem zpracuje jakákoli data ve formátu podporovaném
gramps, viz dále.
.br
.TP
.BI \-f,\-\^\-format= " FORMÁT"
Explicitně definuje formát \fISOUBOR\fRu předchozího parametru
.ig
\fB\-O\fR,
..
\fB\-i\fR, nebo
\fB\-e\fR. Pokud není parametr \fB\-f\fR pro \fISOUBOR\fR specifikován,
bude automaticky použit formát odpovídající koncovce souboru nebo MIME-typu.
.br
Formáty
dostupné pro export jsou \fBgramps\-xml\fR (automaticky použit pokud má
\fISOUBOR\fR koncovku \fB.gramps\fR), \fBgedcom\fR (automaticky použit
pokud má \fISOUBOR\fR koncovku \fB.ged\fR), případně jiný další formát dostupný
prostřednictvím zásuvných modulů Gramps.
.br
Formáty
dostupné pro import jsou \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR,
\fBgramps\-pkg\fR (automaticky použit pokud má \fISOUBOR\fR koncovku \fB.gpkg\fR),
nebo \fBgeneweb\fR (automaticky použit pokud má \fISOUBOR\fR koncovku \fB.gw\fR).
.br
Formáty dostupné pro export jsou
.ig
\fBgrdb\fR,
..
\fBgramps\-xml\fR, \fBgedcom\fR,
\fBgramps\-pkg\fR, \fBwft\fR (automaticky použit pokud má \fISOUBOR\fR koncovku \fB.wft\fR),
\fBgeneweb\fR, a \fBiso\fR (nikdy není použit automaticky, vždy musí být specifikován
parametrem \fB\-f\fR).
.TP
.BI \-l
Vypíše seznam známých rodokmenů.
.TP
.BI \-u,\-\^\-force-unlock
Odemkne zamčenou databázi.
.TP
.BI \-O,\-\^\-open= " DATABÁZE"
Otevření \fIDATABÁZE\fR. Hodnota musí být existujícím databázovým adresářem, nebo názvem existujícího rodokmenu.
Pokud na příkazové řádce nejsou žádné parametry importu nebo exportu, je nad danou databází spuštěna interaktivní relace.
.TP
.BI \-i,\-\^\-import= " SOUBOR"
Importuje data ze \fISOUBOR\fRu. Pokud není specifikována databáze, je použita dočasná. Ta je po ukončení gramps smazána.
.br
Pokud je předáván více než jeden vstup, musí každému souboru předcházet parametr \fB\-i\fR.
Soubory jsou zpracovávány v pořadí, v jakém byly zadány na příkazové řádce.
Např. \fB\-i\fR \fISOUBOR1\fR \fB\-i\fR \fISOUBOR2\fR
a \fB\-i\fR \fISOUBOR2\fR \fB\-i\fR \fISOUBOR1\fR mohou vytvořit ve výsledné databázi
různá gramps ID.
.TP
.BI \-a,\-\^\-action= " AKCE"
Provedení \fIAKCE\fR nad importovanými daty. Akce jsou spuštěny poté co jsou všechny importy dat
úspěšně ukončeny. V tuto chvíli jsou podporovány následující akce:
\fBsummary\fR (stejné jako Zprávy->Pohled->Souhrn),
\fBcheck\fR (stejné jako Nástroje->Database Processing->Kontrola a oprava),
\fBreport\fR (vytvoří zprávu), a
\fBtool\fR (spustí nástroj zásuvného modulu).
Akce \fBreport\fR a \fBtool\fR potřebují v \fIPARAMETRY\fR zadat parametr
\fB\-p\fR .
.br
\fIPARAMETRY\fR by měly splňovat následující kritéria:
.br
Nesmí obsahovat žádné mezery.
Pokud některý argument potřebuje mezeru, musí být řetězec uzavřen
v uvozovkách (držet se syntaxe příkazové řádky).
Řetězec možností je seznam párů název=hodnota.
Jednotlivé páry musí být odděleny čárkami.
.br
Většina možností nástrojů a zpráv jsou specifickými pro konkrétní nástroj nebo zprávu.
Existují ale i takové, které jsou společné.
.BI "name=name"
.br
Povinná předvolba určující který nástroj nebo zpráva bude spuštěna.
Pokud zadané \fIname\fR neodpovídá žádné dostupné funkčnosti, vypíše se chybové hlášení
následované seznamem dostupných nástrojů a zpráv (záleží na \fIAKCE\fR).
.BI "show=all"
.br
Vytvoří seznam názvů všech předvoleb dostupných pro danou zprávu nebo nástroj.
.BI "show="optionname
.br
Vypíše popis všech funkcionalit poskytnutých \fIoptionname\fR,
ale také všechny přijatelné typy a hodnoty pro tuto volbu.
.br
Použijte výše popsané volby pro zjištění všech možností
dané zprávy.
.LP
Pokud je zadána jedna nebo více výstupních akcí, každá musí být uvozena
předvolbou \fB\-a\fR. Akce jsou prováděny jedna za druhou v zadaném pořadí.
.TP
.BI \-d,\-\^\-debug= " LOGGER_NAME"
Zapne ladicí výstup pro vývoj a testování. Detaily najdete ve zdrojovém kódu.
.TP
.BI \-\^\-version
Vytiskne číslo verze gramps a skončí
\" change 0 to 1 to enable output of OAF options
.if 0 \{
.PP
Následující možnosti slouží pro aktivaci Bonobo.
.TP
.BI \-\^\-oaf-ior-fd= "FD"
Popisovač souboru pro zápis OAF IOR
.TP
.BI \-\^\-oaf-activate-iid= " IID"
OAF IID k aktivaci
.TP
.BI \-\^\-oaf-private
Znemožní registraci serveru s OAF
\}
\" change 0 to 1 to enable output of Gnome sound options
.if 0 \{
.PP
Následující možnosti slouží pro řízení zvuku prostřednictívm knihovny Gnome.
.TP
.BI \-\^\-disable-sound
Zablokuje využití zvukového serveru
.TP
.BI \-\^\-enable-sound
Umožní využití zvukového serveru
.TP
.BI \-\^\-espeaker= " HOSTNAME:PORT"
Host:port na které běží zvukový server který bude použit
\}
.SH "Chování"
.br
Pokud první parametr příkazové řádky nezačíná pomlčkou, pokusí se gramps
otevřít soubor s názvem daným prvním argumentem na příkazové řádce
a spustit interaktivní relaci. Zbytek argumentů na příkazové řádce je
v tomto případě ignorován.
.LP
Pokud je zadán parametr \fB\-O\fR, pak se gramps snaží otevřít zadanou
databázi a pracovat s jejími daty podle instrukcí dalších parametrů
příkazové řádky.
.LP
S nebo bez použití parametru \fB\-O\fR může být provedeno více importů,
exportů, případně akcí daných argumenty příkazové řádky (\fB\-i\fR,
\fB\-e\fR a \fB\-a\fR).
.LP
Na pořadí parametrů \fB\-i\fR, \fB\-e\fR, nebo \fB\-a\fR nezáleží.
Aktuální pořadí zpracování je vždy: všechny importy (pokud jsou nějaké)
-> všechny akce (pokud jsou nějaké) -> všechny exporty (pokud jsou nějaké).
Parametr otevření musí být ale vždy první!
.LP
Pokud nejsou zadány \fB\-O\fR nebo \fB\-i\fR, gramps otevře své hlavní okno
a spustí se v obvyklém interaktivním módu s prázdnou databází.
.LP
Pokud nejsou zadány \fB\-e\fR nebo \fB\-a\fR, gramps otevře své hlavní okno
a spustí se v ovbyklém interaktnivním módu s databází vzniklou výsledkem
všech importů.
Tato databáze je umístěna v souboru \fBimport_db.grdb\fR v adresáři
\fB~/.gramps/import\fR.
.LP
Chyba vzniklá při importu, exportu nebo akci bude vypsána na \fIstdout\fR
(pokud se jedná o vyjímku ošetřenou gramps) nebo na \fIstderr\fR
(pokud problém není ošetřen). Pro uložení zpráv a chyb do souboru použijte
obvyklá přesměrování výstupů \fIstdout\fR a \fIstderr\fR příkazové řádky.
.SH PŘÍKLADY
.TP
Otevření existujícího rodokmenu a import xml souboru do něho může být proveden takto:
\fBgramps\fR \fB\-O\fR \fI'Můj rodokmen'\fR \fB\-i\fR \fI~/db3.gramps\fR
.TP
To samé, jen s importem do dočasné databáze a otevřením interaktivní relace:
\fBgramps\fR \fB\-i\fR \fI'My Family Tree'\fR \fB\-i\fR \fI~/db3.gramps\fR
.TP
Import čtyř databází (jejichž formáty jsou stanoveny podle názvů souborů) a následná kontrola bezchybnosti výsledné databáze může být provedena takto:
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-i\fR \fIfile4.wft\fR \fB\-a\fR \fIcheck\fR
.TP
Explicitní specifikace formátu databází předchozího příkladu přidáním příslušného parametru \fB\-f\fR za název souboru:
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-f\fR \fIgedcom\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-f\fR \fIgramps-pkg\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-f\fR \fIgramps-xml\fR \fB\-i\fR \fIfile4.wft\fR \fB\-f\fR \fIwft\fR \fB\-a\fR \fIcheck\fR
.TP
Zapsání výsledné databáze vytvořené ze všech importů zajistí parametr \fB\-e\fR (použijte \fB\-f\fR pokud nelze uhodnout formát z názvu souboru):
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-e\fR \fI~/nový-balíček\fR \fB\-f\fR \fIgramps-pkg\fR
.TP
Import tří databází a start interaktivní gramps relace nad výsledkem:
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR
.TP
Spuštění nástroje kontroly z příkazové řádky s výstupem na stdout:
\fBgramps\fR \fB\-O\fR \fI'Můj rodokmen'\fR \fB-a\fR \fItool\fR \fB-p\fR \fBname\fR=\fIverify\fR
.TP
A konečně spuštění normální interaktivní relace aplikace:
\fBgramps\fR
.SH PROMĚNNÉ PROSTŘEDÍ
Program kontroluje, zda jsou nastaveny následující proměnné:
\fBLANG\fR - popisuje, který jazyk bude použit:
Příklad: pro češtinu musí mít proměnná hodnotu cs_CZ.utf8.
\fBGRAMPSHOME\fR - pokud je nastavena, Gramps použije její hodnotu jako adresář
v němž jsou uložena nastavení a databáze. Ve výchozím stavu, kdy proměnná není nastavena
gramps předpokládá že adresář s databázemi a nastavením bude vytvořen
v adresáři s uživatelským profile (popsán proměnnou prostředí HOME v Linuxu nebo
USERPROFILE ve Windows 2000/XP).
.SH KONCEPTY
\fBgramps\fR podporuje systém zásuvných modulů založených na jazyku python jehož prostřednictvím
umožňuje přidání import/export modulů, modulů pro vytváření zpráv,
nástrojů a zobrazovacích filtrů bez nutnosti zásahu do hlavního programu.
.LP
Dále, krom možnosti přímého tisku, dovoluje směřovat výstup také k ostatním
systémům a aplikacím jako např. \fIOpenOffice.org\fR, \fIAbiWord\fR, HTML,
nebo LaTeX. Tím dává možnost přizpůsobit formát požadavku uživatelů.
.SH ZNÁMÉ CHYBY A OMEZENÍ
.br
nejsou
.SH SOUBORY
.LP
\fI${PREFIX}/bin/gramps\fP
.br
\fI${PREFIX}/share/gramps\fP
.br
\fI${HOME}/.gramps\fP
.SH AUTOŘI
Donald Allingham \fI<don@gramps-project.org>\fR
.br
\fIhttp://gramps.sourceforge.net\fR
.LP
Originální manuálovou stránku vytvořil:
.br
Brandon L. Griffith \fI<brandon@debian.org>\fR
.br
pro zařazení do systému Debian GNU/Linux.
.LP
Tuto manuálovou stránku přeložil a v současné době spravuje:
.br
Zdeněk Hataš \fI<zdenek.hatas@gmail.com>\fR
.br
.SH DOKUMENTACE
Uživatelská dokumentace je k dispozici prostřednictvím standardního
prohlížeče nápovědy GNOME ve formě příručky Gramps. Příručka je také
dostupná ve formátu XML jako \fBgramps-manual.xml\fR
v adresáři \fIdoc/gramps-manual/$LANG\fR v oficiální distribuci
zdrojového kódu.
.LP
Dokumentace pro vývojáře je k dispozici na webu
\fIhttp://developers.gramps-project.org\fR.

View File

@ -1,16 +1,14 @@
.TH gramps 1 "@VERSION@" "Mars 2009" "@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)
gramps \- GRAMPS est une application de généalogie. GRAMPS est l'acronyme de Genealogical Research and Analysis Management Programming System (Systeme de Programmation pour Recherche, Analyse et Gestion de données généalogiques)
.SH SYNOPSIS
.B gramps
.RB [ \-?|\-\^\-help ]
.RB [ \-\^\-usage ]
.RB [ \-\^\-version ]
.RB [ \-l]
.RB [ \-u|\-\^\-force-unlock ]
.RB [ \-O|\-\^\-open=
.IR BASE_DE_DONNEES
.IR FICHIER
.RB [ \-f|\-\^\-format=
.IR FORMAT ]]
.RB [ \-i|\-\^\-import=
@ -19,20 +17,17 @@ gramps \- Gramps est une application de généalogie. Gramps est l'acronyme de G
.IR FORMAT ]]
.RB [ \-i|\-\^\-import=
.IR ... ]
.RB [ \-e|\-\^\-export=
.RB [ \-o|\-\^\-output=
.IR FICHIER
.RB [ \-f|\-\^\-format=
.IR FORMAT ]]
.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\-e\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,
@ -103,27 +85,22 @@ i.e. \fB\-i\fR \fIFICHIER1\fR \fB\-i\fR \fIFICHIER2\fR
et \fB\-i\fR \fIFICHIER2\fR \fB\-i\fR \fIFICHIER1\fR vont tous les deux produire différents IDs gramps.
.TP
.BI \-e,\-\^\-export= " FICHIER"
.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
Quand plus d'un fichier doit être exporté, chacun doit être précédé par la commande \fB\-e\fR. Ces fichiers sont importés dans le même ordre.
Quand plus d'un fichier doit être exporté, chacun doit être précédé par la commande \fB\-o\fR. Ces fichiers sont importés dans le même ordre.
.TP
.BI \-a,\-\^\-action= " ACTION"
Accomplir une \fIACTION\fR sur les données importées. C'est effectué à la fin de l'importation. Les actions possibles sont \fBsummary\fR
(comme le rapport -> 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,61 +129,26 @@ 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
.if 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
.if 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.
.LP
Avec ou sans la commande \fB\-O\fR, il peut y avoir plusieurs imports, exports, et actions dans la ligne de commande \fB\-i\fR,
\fB\-e\fR, et \fB\-a\fR.
\fB\-o\fR, et \fB\-a\fR.
.LP
L'ordre des options \fB\-i\fR, \fB\-e\fR, ou \fB\-a\fR n'a pas de sens. L'ordre actuel est toujours : imports -> actions -> exports. Mais l'ouverture doit toujours être la première!
L'ordre des options \fB\-i\fR, \fB\-o\fR, ou \fB\-a\fR n'a pas de sens. L'ordre actuel est toujours : imports -> actions -> exports. Mais l'ouverture doit toujours être la première!
.LP
Si aucune option \fB\-O\fR ou \fB\-i\fR n'est donnée, gramps lancera sa propre fenêtre et demarrera avec une base vide, puisqu'il n'y a pas données.
.LP
Si aucune option \fB\-e\fR ou \fB\-a\fR n'est donnée, gramps lancera sa propre fenêtre et démarrera avec la base de données issue de tout les imports. Cette base sera \fBimport_db.grdb\fR sous le répertoire \fB~/.gramps/import\fR.
Si aucune option \fB\-o\fR ou \fB\-a\fR n'est donnée, gramps lancera sa propre fenêtre et démarrera avec la base de données issue de tout les imports. Cette base sera \fBimport_db.grdb\fR sous le répertoire \fB~/.gramps/import\fR.
.LP
Les erreurs rencontrées lors d'import, export, ou action, seront mémorisées en \fIstdout\fR (si elles sont le fait de la manipulation par gramps) ou
@ -214,41 +156,23 @@ 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 Familial'\fR \fB\-i\fR \fI~/db3.gramps\fR
.TP
Ceci ouvre un arbre familial, pour faire la même chose, mais importer dans un arbre familial temporaire et démarrer une session interactive, on peut saisir:
\fBgramps\fR \fB\-i\fR \fI'Mon Arbre Familial'\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
Si vous voulez préciser les formats de fichiers dans l'exemple ci-dessus, complétez les noms de fichiers par les options \fB\-f\fR appropriées:
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-f\fR \fIgedcom\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-f\fR \fIgramps-pkg\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-f\fR \fIgramps-xml\fR \fB\-i\fR \fIfile4.wft\fR \fB\-f\fR \fIwft\fR \fB\-a\fR \fIcheck\fR
.TP
Pour enregistrer le résultat des lectures, donnez l'option \fB\-e\fR (utiliser \fB\-f\fR si le nom de fichier ne permet pas à gramps de deviner le format):
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-e\fR \fI~/new-package\fR \fB\-f\fR \fIgramps-pkg\fR
Pour enregistrer le résultat des lectures, donnez l'option \fB\-o\fR (utiliser \fB\-f\fR si le nom de fichier ne permet pas à gramps de deviner le format):
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-o\fR \fI~/new-package\fR \fB\-f\fR \fIgramps-pkg\fR
.TP
Pour lire trois ensembles de données puis lancer une session interactive de gramps sur le tout :
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR
.TP
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 VARIABLES D'ENVIRONMENT
Le programme vérifie si ces variables d'environnement sont déclarées:
\fBLANG\fR - décrit, quelle langue est utilisée:
Ex.: pour le français on peut définir fr_FR.UTF-8.
\fBGRAMPSHOME\fR - si défini, force Gramps à utiliser un répertoire spécifique pour y conserver ses préférences et bases de données. Par défaut, cette variable n'est pas active et Gramps sait que les options et bases de données doivent être créées
dans le répertoire par défaut de l'utilisateur (la variable d'environnement HOME pour Linux ou USERPROFILE pour Windows 2000/XP).
Enfin, pour lancer une session interactive normale, entrer : \fBgramps\fR
.SH CONCEPTS
Gramps est un système basé sur le support de plugin-python, permettant d'importer et d'exporter, la saisie,
GRAMPS est un système basé sur le support de plugin-python, permettant d'importer et d'exporter, la saisie,
générer des rapports, des outils, et afficher des filtres pouvant être ajoutés sans modifier le programme.
.LP
Par ailleurs, gramps permet la génération directe : impression, rapports avec sortie vers d'autres formats, comme \fIOpenOffice.org\fR, \fIAbiWord\fR, HTML,
@ -277,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

View File

@ -1,4 +1,4 @@
.TH gramps 1 "@VERSION@" "December 2012" "@VERSION@"
.TH gramps 1 "@VERSION@" "August 2005" "@VERSION@"
.SH NAME
gramps \- Genealogical Research and Analysis Management Programming System.
@ -7,10 +7,8 @@ gramps \- Genealogical Research and Analysis Management Programming System.
.RB [ \-?|\-\^\-help ]
.RB [ \-\^\-usage ]
.RB [ \-\^\-version ]
.RB [ \-l ]
.RB [ \-u|\-\^\-force-unlock ]
.RB [ \-O|\-\^\-open=
.IR DATABASE
.IR FILE
.RB [ \-f|\-\^\-format=
.IR FORMAT ]]
.RB [ \-i|\-\^\-import=
@ -19,20 +17,17 @@ gramps \- Genealogical Research and Analysis Management Programming System.
.IR FORMAT ]]
.RB [ \-i|\-\^\-import=
.IR ... ]
.RB [ \-e|\-\^\-export=
.RB [ \-o|\-\^\-output=
.IR FILE
.RB [ \-f|\-\^\-format=
.IR FORMAT ]]
.RB [ \-a|\-\^\-action=
.IR ACTION ]
.RB [ \-p|\-\^\-options=
.IR OPTIONSTRING ]]
.IR OPTIONSTRING ]]
.RB [
.IR FILE
.RB ]
.if 0 .RB [ bonobo\ options ]
.if 0 .RB [ sound\ options ]
.RB [ \-\-version ]
.SH DESCRIPTION
.PP
@ -47,31 +42,25 @@ wide by almost all other genealogy software.
.SH OPTIONS
.TP
.BI gramps " FILE"
When \fIFILE\fR is given (without any flags) as a family tree name or as
a family tree database directory, then it is opened and an interactive
session is started. If FILE is a file format understood by Gramps, an empty
family tree is created whose name is based on the \fIFILE\fP name
and the data is imported into it. The rest of the
options is ignored. This way of launching is suitable for using gramps
When \fIFILE\fR is given (without any flags) then it is
opened and an interactive session is started. The rest of the options
is ignored. This way of launching is suitable for using gramps
as a handler for genealogical data in e.g. web browsers. This invocation
can accept any data format native to gramps, see below.
.br
.TP
.BI \-f,\-\^\-format= " FORMAT"
Explicitly specify format of \fIFILE\fR given by preceding
.ig
\fB\-O\fR,
..
Explicitly specify format of \fIFILE\fR given by preceding \fB\-O\fR,
\fB\-i\fR, or
\fB\-e\fR option. If the \fB\-f\fR option is not given for any \fIFILE\fR,
the format of that file is guessed according to its extension or MIME-type.
\fB\-o\fR option. If the \fB\-f\fR option is not given for any \fIFILE\fR,
the format of that file is guessed according to its extension.
.br
Formats
available for export are \fBgramps\-xml\fR (guessed if \fIFILE\fR ends with
\fB.gramps\fR), \fBgedcom\fR (guessed if \fIFILE\fR ends with \fB.ged\fR), or
any file export available through the Gramps plugin system.
available for opening are \fBgrdb\fR (guessed if \fIFILE\fR ends with
\fB.grdb\fR), \fBgramps\-xml\fR (guessed if \fIFILE\fR ends with
\fB.gramps\fR), and \fBgedcom\fR (guessed if \fIFILE\fR ends with \fB.ged\fR).
.br
Formats
@ -80,31 +69,25 @@ available for import are \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR,
\fBgeneweb\fR (guessed if \fIFILE\fR ends with \fB.gw\fR).
.br
Formats available for export are
.ig
\fBgrdb\fR,
..
\fBgramps\-xml\fR, \fBgedcom\fR,
Formats available for export are \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR,
\fBgramps\-pkg\fR, \fBwft\fR (guessed if \fIFILE\fR ends with \fB.wft\fR),
\fBgeneweb\fR, and \fBiso\fR (never guessed, always specify with
\fB\-f\fR option).
.TP
.BI \-l
Print a list of known family trees.
.BI \-O,\-\^\-open= " FILE"
Open \fIFILE\fR.
Only \fBgrdb\fR, \fBgramps\-xml\fR, and \fBgedcom\fR formats can be
opened directly. For other formats, you will need to use the import option
which will set up the empty database and then import data into it.
.br
.TP
.BI \-u,\-\^\-force-unlock
Unlock a locked database.
.TP
.BI \-O,\-\^\-open= " DATABASE"
Open \fIDATABASE\fR which must be an existing database directory or existing family tree name.
If no action, import or export options are given on the command line then an interactive session is started using that database.
Only a single file can be opened. If you need to combine data from several
sources, you will need to use the import option.
.TP
.BI \-i,\-\^\-import= " FILE"
Import data from \fIFILE\fR. If you haven't specified a database then a temporary database is used; this is deleted when you exit gramps.
Import data from \fIFILE\fR.
.br
When more than one input file is given, each has to be preceded by \fB\-i\fR
@ -114,55 +97,54 @@ and \fB\-i\fR \fIFILE2\fR \fB\-i\fR \fIFILE1\fR might produce different
gramps IDs in the resulting database.
.TP
.BI \-e,\-\^\-export= " FILE"
Export data into \fIFILE\fR. For \fBgramps\-xml\fR, \fBgedcom\fR,
\fBwft\fR, \fBgramps\-pkg\fR, and \fBgeneweb\fR, the \fIFILE\fR is
the name of the resulting file.
.BI \-o,\-\^\-output= " FILE"
Export data into \fIFILE\fR. For \fBiso\fR format, the \fIFILE\fR is actually
the name of directory the gramps database will be written into.
For \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR, \fBwft\fR, \fBgramps\-pkg\fR,
and \fBgeneweb\fR, the \fIFILE\fR is the name of the resulting file.
.br
When more than one output file is given, each has to be preceded
by \fB\-e\fR flag. The files are written one by one, in the specified order.
by \fB\-o\fR flag. The files are written one by one, in the specified order.
.TP
.BI \-a,\-\^\-action= " ACTION"
Perform \fIACTION\fR on the imported data. This is done after all imports
are successfully completed. Currently available actions are
\fBsummary\fR (same as Reports->View->Summary),
\fBcheck\fR (same as Tools->Database Processing->Check and Repair),
\fBreport\fR (generates report), and
\fBtool\fR (runs a plugin tool).
Both \fBreport\fR and \fBtool\fR need the \fIOPTIONSTRING\fR supplied by the
\fB\-p\fR flag).
are successfully completed. Currently available actions are \fBsummary\fR
(same as Reports->View->Summary), \fBcheck\fR (same as Tools->Database
Processing->Check and Repair), and \fBreport\fR (generates report, needs
the \fIOPTIONSTRING\fR supplied by the \fB\-p\fR flag).
.br
The \fIOPTIONSTRING\fR should satisfy the following conditions:
The report option string should satisfy the following conditions:
.br
It must not contain any spaces.
If some arguments need to include spaces, the string should
be enclosed with quotation marks, i.e., follow the shell syntax.
Option string is a list of pairs with name and value (separated by the
equality sign). The name and value pairs must be separated by commas.
be enclosed with quotation marks.
Option string must list pairs of option names and values.
Withing a pair, option name and value must be separated by the equality sign.
Different pairs must be separated by commas.
.br
Most of the report or tools options are specific for each report or tool.
However, there are some common options.
Most of the report options are specific for every report. However, there some
common options.
.BI "name=name"
.BI "name=reportname"
.br
This mandatory option determines which report or tool will be run.
If the supplied \fIname\fR does not correspond to any available report or
tool, an error message will be printed followed by the list of
available reports or tools (depending on the \fIACTION\fR).
This mandatory option determines which report
will be generated. If the supplied report_name does not correspond to any
available report, the error message will be printed followed by the list of
available reports.
.BI "show=all"
.br
This will produce the list of names for all options available for a given
report or tool.
This will produce the list of names for all options
available for a given report.
.BI "show="optionname
.BI "show=optionname"
.br
This will print the description of
the functionality supplied by \fIoptionname\fR, as well as what are the
the functionality supplied by \fBoptionname\fR, as well as what are the
acceptable types and values for this option.
.br
@ -173,42 +155,7 @@ everything about a given report.
When more than one output action is given, each has to be preceded
by \fB\-a\fR flag. The actions are performed one by one, in the specified order.
.TP
.BI \-d,\-\^\-debug= " LOGGER_NAME"
Enables debug logs for development and testing. Look at the source code for details
.TP
.BI \-\^\-version
Prints the version number of gramps and then exits
\" change 0 to 1 to enable output of OAF options
.if 0 \{
.PP
The following options are used for Bonobo activation.
.TP
.BI \-\^\-oaf-ior-fd= "FD"
File descriptor to print the OAF IOR on
.TP
.BI \-\^\-oaf-activate-iid= " IID"
OAF IID to activate
.TP
.BI \-\^\-oaf-private
Prevent registering of server with OAF
\}
\" change 0 to 1 to enable output of Gnome sound options
.if 0 \{
.PP
The following options are used for controlling sound using the Gnome Library.
.TP
.BI \-\^\-disable-sound
Disable sound server usage
.TP
.BI \-\^\-enable-sound
Enable sound server usage
.TP
.BI \-\^\-espeaker= " HOSTNAME:PORT"
Host:port on which the sound server to use is running
\}
.SH "Operation"
.BI "Operation"
.br
If the first argument on the command line does not start with dash (i.e. no
flag), gramps will attempt to open the file with the name given by the first
@ -217,16 +164,16 @@ arguments.
.LP
If the \fB\-O\fR flag is given, then gramps will try opening
the supplied database and then work with that data, as instructed by the
the supplied file name and then work with that data, as instructed by the
further command line parameters.
.LP
With or without the \fB\-O\fR flag, there could be multiple imports,
exports, and actions specified further on the command line by using \fB\-i\fR,
\fB\-e\fR, and \fB\-a\fR flags.
\fB\-o\fR, and \fB\-a\fR flags.
.LP
The order of \fB\-i\fR, \fB\-e\fR, or \fB\-a\fR options does not matter. The
The order of \fB\-i\fR, \fB\-o\fR, or \fB\-a\fR options does not matter. The
actual order always is: all imports (if any) -> all actions (if any)
-> all exports (if any). But opening must always be first!
@ -236,55 +183,34 @@ window and start the usual interactive session with the empty database,
since there is no data to process, anyway.
.LP
If no \fB\-e\fR or \fB\-a\fR options are given, gramps will launch its main
If no \fB\-o\fR or \fB\-a\fR options are given, gramps will launch its main
window and start the usual interactive session with the database resulted
from all imports. This database resides in the \fBimport_db.grdb\fR
under \fB~/.gramps/import\fR directory.
.LP
The error encountered during import, export, or action, will be either
dumped to \fIstdout\fR (if these are exceptions handled by gramps) or
dumped to \fIstdout\fR (if these are exceptions handled by gramps) or or
to \fIstderr\fR (if these are not handled). Use usual shell redirections
of \fIstdout\fR and \fIstderr\fR to save messages and errors in files.
.SH EXAMPLES
.TP
To open an existing family tree and import an xml file into it, one may type:
\fBgramps\fR \fB\-O\fR \fI'My Family Tree'\fR \fB\-i\fR \fI~/db3.gramps\fR
.TP
The above changes the opened family tree, to do the same, but import both in a temporary family tree and start an interactive session, one may type:
\fBgramps\fR \fB\-i\fR \fI'My Family Tree'\fR \fB\-i\fR \fI~/db3.gramps\fR
.TP
To import four databases (whose formats can be determined from their names) and then check the resulting database for errors, one may type:
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-i\fR \fIfile4.wft\fR \fB\-a\fR \fIcheck\fR
.TP
To explicitly specify the formats in the above example, append filenames with appropriate \fB\-f\fR options:
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-f\fR \fIgedcom\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-f\fR \fIgramps-pkg\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-f\fR \fIgramps-xml\fR \fB\-i\fR \fIfile4.wft\fR \fB\-f\fR \fIwft\fR \fB\-a\fR \fIcheck\fR
.TP
To record the database resulting from all imports, supply \fB\-e\fR flag (use \fB\-f\fR if the filename does not allow gramps to guess the format):
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-e\fR \fI~/new-package\fR \fB\-f\fR \fIgramps-pkg\fR
To record the database resulting from all imports, supply \fB\-o\fR flag (use \fB\-f\fR if the filename does not allow gramps to guess the format):
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-o\fR \fI~/new-package\fR \fB\-f\fR \fIgramps-pkg\fR
.TP
To import three databases and start interactive gramps session with the result:
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR
.TP
To run the Verify tool from the commandline and output the result to stdout:
\fBgramps\fR \fB\-O\fR \fI'My Family Tree'\fR \fB-a\fR \fItool\fR \fB-p\fR \fBname\fR=\fIverify\fR
.TP
Finally, to start normal interactive session type:
\fBgramps\fR
.SH ENVIRONMENT VARIABLES
The program checks whether these environment variables are set:
\fBLANG\fR - describe, which language to use:
Ex.: for polish language this variable has to be set to pl_PL.UTF-8.
\fBGRAMPSHOME\fR - if set, force Gramps to use the specified directory to keep
program settings and databases there. By default, this variable is not set and
gramps assumes that the folder with all databases and profile settings
should be created within the user profile folder (described by environment
variable HOME for Linux or USERPROFILE for Windows 2000/XP).
.SH CONCEPTS
Supports a python\-based plugin system, allowing import and export writers,
report generators, tools, and display filters to be added without modification
@ -317,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

View File

@ -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)

View File

@ -1,315 +0,0 @@
.TH gramps 1 "@VERSION@" "August 2005" "@VERSION@"
.SH NAAM
gramps \- Genealogisch Onderzoek en Analyse Beheersysteem.
.SH SAMENVATTING
.B gramps
.RB [ \-?|\-\^\-help ]
.RB [ \-\^\-usage ]
.RB [ \-\^\-version ]
.RB [ \-O|\-\^\-open=
.IR GEGEVENSBESTAND
.RB [ \-f|\-\^\-format=
.IR FORMAAT ]]
.RB [ \-i|\-\^\-import=
.IR BESTAND
.RB [ \-f|\-\^\-format=
.IR FORMAAT ]]
.RB [ \-i|\-\^\-import=
.IR ... ]
.RB [ \-e|\-\^\-export=
.IR BESTAND
.RB [ \-f|\-\^\-format=
.IR FORMAAT ]]
.RB [ \-a|\-\^\-action=
.IR ACTIE ]
.RB [ \-p|\-\^\-options=
.IR OPTIESTRING ]]
.RB [
.IR BESTAND
.RB ]
.if 0 .RB [ bonobo\ options ]
.if 0 .RB [ sound\ options ]
.RB [ \-\-version ]
.SH BESCHRIJVING
.PP
\fIGramps\fP is een Free/OpenSource genealogisch programma dat in Python,
geschreven is en gebruik maakt van de GTK+/GNOME interface.
Gramps zal voor iedereen die al gewerkt heeft met andere genealogische
programma's zoals \fIFamily Tree Maker (TM)\fR, \fIPersonal Ancestral
Files (TM)\fR of \fIGNU Geneweb\fP.
Importeren vanuit het gekende GEDCOM-formaat wordt ondersteund. Dit formaat
wordt wereldwijd gebruikt door bijna alle genealogische software.
.SH OPTIES
.TP
.BI gramps "BESTAND"
Wanneer \fIBESTAND\fR opgegeven wordt (zonder vlaggen) als een familiestamboom
of als een familistamboommap, dan wordt dit bestand geopend en een interactieve
sessie wordt gestart. Indien BESTAND een bestandsformaat dat door Gramps
herkent wordt, zal een lege familiestamboom aangemaakt worden. De bestandsnaam
wordt gebaseerd op de \fIBESTAND\fP naam en de gegevens worden in dit bestand
geïmporteerd. Met resterende opties wordt geen rekening gehouden. Deze wijze
van opstarten is zeer bruikbaar om Gramps te gebruiken voor genealogische
gegevens via een webbrowser. Deze opstartmethode kan gelijk welk gegevensformaat
eigen aan Gramps behandelen, zie onder.
.br
.TP
.BI \-f,\-\^\-format= " FORMAAT"
Expliciet een formaat opgeven voor \fIBESTAND\fR door de optie
.ig
\fB\-O\fR,
..
\fB\-i\fR, of
\fB\-e\fR mee te geven. Indien de \fB\-f\fR optie niet opgegeven wordt voor
\fIBESTAND\fR, wordt het formaat gebaseerd op de bestandsextensie of het
MIME-type.
.br
Formaten
beschikbaar voor uitvoer zijn \fBgramps\-xml\fR (guessed if \fIFILE\fR ends with
\fB.gramps\fR), \fBgedcom\fR (guessed if \fIFILE\fR ends with \fB.ged\fR), or
any file export available through the Gramps plugin system.
.br
Formats
available for import are \fBgrdb\fR, \fBgramps\-xml\fR, \fBgedcom\fR,
\fBgramps\-pkg\fR (guessed if \fIFILE\fR ends with \fB.gpkg\fR), and
\fBgeneweb\fR (guessed if \fIFILE\fR ends with \fB.gw\fR).
.br
Formats available for export are
.ig
\fBgrdb\fR,
..
\fBgramps\-xml\fR, \fBgedcom\fR,
\fBgramps\-pkg\fR, \fBwft\fR (guessed if \fIFILE\fR ends with \fB.wft\fR),
\fBgeneweb\fR, and \fBiso\fR (never guessed, always specify with
\fB\-f\fR option).
.TP
.BI \-O,\-\^\-open= " DATABASE"
Open \fIDATABASE\fR which must be an existing database directory or existing family tree name.
If no action, import or export options are given on the command line then an interactive session is started using that database.
.TP
.BI \-i,\-\^\-import= " FILE"
Import data from \fIFILE\fR. If you haven't specified a database then a temporary database is used; this is deleted when you exit gramps.
.br
When more than one input file is given, each has to be preceded by \fB\-i\fR
flag. The files are imported in the specified order,
i.e. \fB\-i\fR \fIFILE1\fR \fB\-i\fR \fIFILE2\fR
and \fB\-i\fR \fIFILE2\fR \fB\-i\fR \fIFILE1\fR might produce different
gramps IDs in the resulting database.
.TP
.BI \-e,\-\^\-export= " FILE"
Export data into \fIFILE\fR. For \fBiso\fR format, the \fIFILE\fR is actually
the name of directory the gramps database will be written into.
For
.ig
\fBgrdb\fR,
..
\fBgramps\-xml\fR, \fBgedcom\fR, \fBwft\fR, \fBgramps\-pkg\fR,
and \fBgeneweb\fR, the \fIFILE\fR is the name of the resulting file.
.br
When more than one output file is given, each has to be preceded
by \fB\-e\fR flag. The files are written one by one, in the specified order.
.TP
.BI \-a,\-\^\-action= " ACTION"
Perform \fIACTION\fR on the imported data. This is done after all imports
are successfully completed. Currently available actions are \fBsummary\fR
(same as Reports->View->Summary), \fBcheck\fR (same as Tools->Database
Processing->Check and Repair), and \fBreport\fR (generates report, needs
the \fIOPTIONSTRING\fR supplied by the \fB\-p\fR flag).
.br
The report option string should satisfy the following conditions:
.br
It must not contain any spaces.
If some arguments need to include spaces, the string should
be enclosed with quotation marks.
Option string must list pairs of option names and values.
Withing a pair, option name and value must be separated by the equality sign.
Different pairs must be separated by commas.
.br
Most of the report options are specific for every report. However, there some
common options.
.BI "name=reportname"
.br
This mandatory option determines which report
will be generated. If the supplied report_name does not correspond to any
available report, the error message will be printed followed by the list of
available reports.
.BI "show=all"
.br
This will produce the list of names for all options
available for a given report.
.BI "show=optionname"
.br
This will print the description of
the functionality supplied by \fBoptionname\fR, as well as what are the
acceptable types and values for this option.
.br
Use the above options to find out
everything about a given report.
.LP
When more than one output action is given, each has to be preceded
by \fB\-a\fR flag. The actions are performed one by one, in the specified order.
.TP
.BI \-d,\-\^\-debug= " LOGGER_NAME"
Enables debug logs for development and testing. Look at the source code for details
.TP
.BI \-\^\-version
Prints the version number of gramps and then exits
\" change 0 to 1 to enable output of OAF options
.if 0 \{
.PP
The following options are used for Bonobo activation.
.TP
.BI \-\^\-oaf-ior-fd= "FD"
File descriptor to print the OAF IOR on
.TP
.BI \-\^\-oaf-activate-iid= " IID"
OAF IID to activate
.TP
.BI \-\^\-oaf-private
Prevent registering of server with OAF
\}
\" change 0 to 1 to enable output of Gnome sound options
.if 0 \{
.PP
The following options are used for controlling sound using the Gnome Library.
.TP
.BI \-\^\-disable-sound
Disable sound server usage
.TP
.BI \-\^\-enable-sound
Enable sound server usage
.TP
.BI \-\^\-espeaker= " HOSTNAME:PORT"
Host:port on which the sound server to use is running
\}
.SH "werking"
.br
Indien het eerste argument in de opdrachtregel niet start met dash (dus geen
vlag) dan zal Gramps trachten om het bestand te openen met een naam die in het
eerste argument werd opgegeven. Vervolgens wordt een interactieve sessie
gestart en de overige argumenten van de opdrachtregel worden genegeerd.
.LP
If the \fB\-O\fR flag is given, then gramps will try opening
the supplied database and then work with that data, as instructed by the
further command line parameters.
.LP
With or without the \fB\-O\fR flag, there could be multiple imports,
exports, and actions specified further on the command line by using \fB\-i\fR,
\fB\-e\fR, and \fB\-a\fR flags.
.LP
The order of \fB\-i\fR, \fB\-e\fR, or \fB\-a\fR options does not matter. The
actual order always is: all imports (if any) -> all actions (if any)
-> all exports (if any). But opening must always be first!
.LP
If no \fB\-O\fR or \fB\-i\fR option is given, gramps will launch its main
window and start the usual interactive session with the empty database,
since there is no data to process, anyway.
.LP
If no \fB\-o\fR or \fB\-a\fR options are given, gramps will launch its main
window and start the usual interactive session with the database resulted
from all imports. This database resides in the \fBimport_db.grdb\fR
under \fB~/.gramps/import\fR directory.
.LP
The error encountered during import, export, or action, will be either
dumped to \fIstdout\fR (if these are exceptions handled by gramps) or
to \fIstderr\fR (if these are not handled). Use usual shell redirections
of \fIstdout\fR and \fIstderr\fR to save messages and errors in files.
.SH EXAMPLES
.TP
To open an existing family tree and import an xml file into it, one may type:
\fBgramps\fR \fB\-O\fR \fI'My Family Tree'\fR \fB\-i\fR \fI~/db3.gramps\fR
.TP
The above changes the opened family tree, to do the same, but import both in a temporary family tree and start an interactive session, one may type:
\fBgramps\fR \fB\-i\fR \fI'My Family Tree'\fR \fB\-i\fR \fI~/db3.gramps\fR
.TP
To import four databases (whose formats can be determined from their names) and then check the resulting database for errors, one may type:
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-i\fR \fIfile4.wft\fR \fB\-a\fR \fIcheck\fR
.TP
To explicitly specify the formats in the above example, append filenames with appropriate \fB\-f\fR options:
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-f\fR \fIgedcom\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-f\fR \fIgramps-pkg\fR \fB\-i\fR \fI~/db3.gramps\fR \fB\-f\fR \fIgramps-xml\fR \fB\-i\fR \fIfile4.wft\fR \fB\-f\fR \fIwft\fR \fB\-a\fR \fIcheck\fR
.TP
To record the database resulting from all imports, supply \fB\-e\fR flag (use \fB\-f\fR if the filename does not allow gramps to guess the format):
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-e\fR \fI~/new-package\fR \fB\-f\fR \fIgramps-pkg\fR
.TP
To import three databases and start interactive gramps session with the result:
\fBgramps\fR \fB\-i\fR \fIfile1.ged\fR \fB\-i\fR \fIfile2.tgz\fR \fB\-i\fR \fI~/db3.gramps\fR
.TP
Finally, to start normal interactive session type:
\fBgramps\fR
.SH CONCEPTEN
Ondersteuning van een op python-gebaseerd plugin systeem. Dit laat toe om
verslagen, hulpgereedschappen en vensterfilters toe te voegen zonder dat het
hoofdprogramma dient aangepast.
.LP
De klassieke uitdrukken zijn mogelijk, maar daar bovenover kunnen de meeste
verslagen ook gebruik maken van \fIOpenOffice.org\fR, \fIAbiWord\fR, HTML,
of LaTeX. Zo kunnen gebruikers het formaat wijzigen naar eigen wens.
.SH GEKENDE BUGS EN BEPERKINGEN
.SH BESTANDEN
.LP
\fI${PREFIX}/bin/gramps\fP
.br
\fI${PREFIX}/share/gramps\fP
.br
\fI${HOME}/.gramps\fP
.SH AUTEURS
Donald Allingham \fI<don@gramps-project.org>\fR
.br
\fIhttp://gramps.sourceforge.net\fR
.LP
Deze man pagina werd oorspronkelijk geschreven door:
.br
Brandon L. Griffith \fI<brandon@debian.org>\fR
.br
voor het Debian GNU/Linux systeem.
.LP
Deze man pagina wordt momenteel onderhouden door:
.br
Alex Roitman \fI<shura@gramps-project.org>\fR
.br
.LP
Deze nederlandstalige man pagina wordt momenteel onderhouden door:
.br
Erik De Richter \fI<frederik.de.richter@pandora.be>\fR
.br
.SH DOCUMENTATIE
De gebruikersdocumentatie is beschikbaar via de normale GNOME Help browser
in de vorm van een Gramps-handleiding. De handleiding is ook beschikbaar in
XML-formaat: \fBgramps-manual.xml\fR onder \fIdoc/gramps-manual/$LANG\fR in
de officiële brondistributie.
.LP
De ontwikkelingsdocumentatie kan gevonden worden op de
\fIhttp://developers.gramps-project.org\fR webstek.

View File

@ -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@/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)

View File

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

View File

@ -1,14 +0,0 @@
# This is the data/pt_BR level Makefile for Gramps
# $Id: Makefile.am 16377 2011-01-13 18:32:42Z matlas $
man_IN_FILES = gramps.1.in
man_MANS = $(man_IN_FILES:.1.in=.1)
mandir = @mandir@/pt_BR
EXTRA_DIST = $(man_MANS) $(man_IN_FILES)
gramps.1: $(top_builddir)/config.status gramps.1.in
cd $(top_builddir) && CONFIG_FILES=data/man/pt_BR/$@ $(SHELL) ./config.status
CLEANFILES=$(man_MANS)

View File

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

View File

@ -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)

View File

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

11
debian/README.Debian vendored
View File

@ -1,6 +1,11 @@
gramps for Debian
-----------------
----------------------
python-webkit is "Suggested" as upstream states it as optional in their README file. According to upstream, webkit needs to be tested for stability for Gramps (it is used in the hidden HTML View). If it is unstable, it may be necessary to revert to gecko (python-gtkmozembed).
This is the Debian package of GRAMPS.
If you do not install python-reportlab (gramps Recommends it be
installed) then you will be able to create usable PDF files only if
your database contains solely latin (iso-8859-1) characters. Reportlab
will generate PDF files containing non-latin characters although they
are quite large as the font must be included in the file.
-- Ross Gammon <rossgammon@mail.dk> Wed, 23 Oct 2013 21:24:00 +0200

267
debian/changelog vendored
View File

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

2
debian/compat vendored
View File

@ -1 +1 @@
9
4

48
debian/control vendored
View File

@ -1,24 +1,36 @@
Source: gramps
Section: gnome
Priority: optional
Maintainer: Ross Gammon <rossgammon@mail.dk>
Build-Depends-Indep: libxml-parser-perl, python-gtk2, gettext, python, intltool
Build-Depends: debhelper (>= 9.0.0)
Standards-Version: 3.9.5
Vcs-Git: git://anonscm.debian.org/collab-maint/gramps.git
Vcs-browser: http://anonscm.debian.org/git/collab-maint/gramps.git
Homepage: http://www.gramps-project.org/
Maintainer: James A. Treacy <treacy@debian.org>
Build-Depends-Indep: debhelper (>=5.0.37.2), python-xml, python-gnome2, python-glade2, scrollkeeper, libglib2.0-dev, libgconf2-dev, build-essential, gnome-doc-utils, intltool, xsltproc, python-central (>= 0.4.17)
Standards-Version: 3.6.2
XS-Python-Version: current
Package: gramps
Architecture: all
Depends: ${python:Depends}, librsvg2-common, python-gtk2, xdg-utils, ${misc:Depends}
Recommends: graphviz, python-pyicu, python-pyexiv2, python-osmgpsmap,
Suggests: ttf-freefont, python-gtkspell, python-pygoocanvas, python-webkit
Description: Genealogical research program
GRAMPS is an Open Source genealogy program written in Python, using
the GTK/GNOME interface. It is an extremely flexible program fitting
the needs for both the amateur genealogist and serious genealogical
researcher.
GRAMPS has the ability to import GEDCOM files exported from many
proprietary genealogy programs and can produce a large number of
reports in many popular formats.
Depends: ${python:Depends}, python-gnome2, python-glade2, ${misc:Depends}
Replaces: gramps-manual, gramps-extending-doc
Conflicts: gramps-manual, gramps-extending-doc, gramps-common
Recommends: gramps-help, graphviz, ttf-freefont, python-reportlab, python-gnome2-extras
Description: Genealogical Research and Analysis Management Program
GRAMPS, the Genealogical Research and Analysis Management Programming
System, is an Open Source genealogy program written in Python, using
the GTK/GNOME interface.
GRAMPS has the ability to import GEDCOM files that are used in such
programs as FamilyTree Maker for Windows and can produce reports
in various formats such as the popular ABIWord and OpenOffice.org
formats as well as HTML and PDF.
Package: gramps-help
Architecture: all
Depends: scrollkeeper (>= 0.3.14-9), yelp
Replaces: gramps-manual, gramps-extending-doc
Conflicts: gramps-manual, gramps-extending-doc, gramps-common
Recommends: gramps
Description: User manual for gramps
GRAMPS, the Genealogical Research and Analysis Management Programming
System, is an Open Source genealogy program written in Python, using
the GTK/GNOME interface.
.
This package contains the User Manual on using GRAMPS.

379
debian/copyright vendored
View File

@ -1,144 +1,251 @@
Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: Gramps
Source: http://gramps-project.org
This package was originally debianized by Brandon L. Griffith
<brandon@debian.org> on Sat, 19 May 2001 13:37:24 -0400.
Files: *
Copyright: 2000-2002, Bruce J. DeGrasse
2000-2008, Donald N. Allingham
2000-2007, Martin Hawlisch
2001, Andrés Sepúlveda
2001, David R. Hampton
2001-2013, Free Software Foundation, Inc.
2001, Jesper Zedlitz
2001-2013, the Gramps Project
2002, Gary Shao
2003-2006, Josiah Carlson
2004-2006, Eero Tamminen
2004-2013, Julio Sánchez
2004, Toshio Kuratomi
2005-2011, Serge Noiraud
2000-2007, Alex Roitman
2006-2011, Brian G. Matherly
2007-2011, Benny Malengier
2007-2012, Douglas S. Blank
2007-2012, Gary Burton
2007-2011, Jerome Rapinat
2007, Johan Gronqvist
2007, Robert Cawley
2007-2009, Stephane Charette
2007, Thom Sturgill
2007-2008, Zsolt Foldvari
2008-2010, 2012, Craig J. Anderson
2008-2009, James Friedmann
2008-2009, Jason Simanek
2008-2011, Kees Bakker
2008, Lukasz Rymarczyk
2008-2010, Peter G. Landgren
2008, 2010, Raphael Ackermann
2008-2011, Reinhard Mueller
2008, 2011, Robert Cheramy
2008-2012, Rob G. Healey
2008, Stefan Siegel
2009-2010, Andrew I Baznikin
2009, 2011, The Dojo Foundation
2009, Florian Heinle
2009, Gerald W. Britton
2009, 2011, John Resig
2009-2013, Nick Hall
2009, Pander Musubi
2009, Robert Ham
2009-2010, Stephen George
2009, Swoon on bug tracker
2009, Yevgeny Zegzda
2010, Gramps
2010, Jakim Friant
2010, Josip
2010, lcc & Robert Jerome
2010-2012, Michiel D. Nauta
2010-2013, Tim G L Lyons
2010-2011, Vlada Perić
2011, Adam Stein
2011, 2013 Heinz Brinker
2011, Helge Herz
2011, John Ralls
2011, Matt Keenan
2011-2013, Paul Franklin
2012, Mathieu MD
2013, Fedir Zinchuk
2013, Oleh Petrivk
2013, Vassilii Khachaturov
2013, Zissis Papadopoulos
License: GPL-2+
The current Debian maintainer is James A. Treacy <treacy@debian.org>
Files: debian/*
Copyright: 2001-2002, Brandon L. Griffith
2002, Alex Roitman
2002-2012, James A. Treacy
2013, Ross Gammon
License: GPL-2+
It was downloaded from http://gramps-project.org
Files: src/plugins/webstuff/js/jquery-ui-1.7.2.custom.min.js
Copyright: 2009, jQuery UI Team (http://jqueryui.com/about/)
License: MIT and GPL-2
Upstream Authors:
Donald N. Allingham, Alexander Roitman, Martin Hawlisch, Richard Taylor,
Brian Matherly, Tim Waugh, Donald A. Peterson, David Hampton
Files: src/plugins/webstuff/js/jquery-1.7.1.js
Copyright: 2009, jQuery UI Team (http://jqueryui.com/about/)
License: MIT and GPL-2
========================================================
Copyright: 2001-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
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
Files: src/plugins/webstuff/js/jquery-1.3.2.min.js
Copyright: 2009, jQuery UI Team (http://jqueryui.com/about/)
License: MIT and GPL-2
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
License: GPL-2
This package is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; version 2 only of the License.
.
This package is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
.
You should have received a copy of the GNU General Public License
along with this package; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
.
On Debian systems, the complete text of the GNU General
Public License can be found in `/usr/share/common-licenses/GPL-2'.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
License: GPL-2+
This package is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
.
This package is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
.
You should have received a copy of the GNU General Public License
along with this package; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
.
On Debian systems, the complete text of the GNU General
Public License can be found in `/usr/share/common-licenses/GPL-2'.
On Debian systems, the complete text of the GNU General Public
License can be found in /usr/share/common-licenses/GPL
License: MIT
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:
.
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
========================================================
The files in help/C directory are Copyright 2006 Alexander Roitman
This documentation is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This documentation is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
========================================================
The files in help/fr directory are Copyright 2003-2006 Jerome Rapinat
This documentation is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This documentation is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
========================================================
The data/grampsxml.dtd file is Copyright 2001 Graham J. William
and Copyright 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
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
========================================================
The src/TreeTips.py file is Copyright 2004 Toshio Kuratomi
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
========================================================
The src/data/fdl.txt file is Copyright 2000,2001,2002
Free Software Foundation, Inc.
59 Temple Place, Suite 330,
Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
========================================================
The file src/docgen/ODFDoc.py file is Copyright 2005-2006 Serge Noiraud
and Copyright 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
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
========================================================
The file src/Mime/_WinMime.py file is Copyright 2006 Brian Matherly
and Copyright 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
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
========================================================
The src/plugins/Ancestors.py file is Copyright 2003 Tim Waugh
and Copyright 2003-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
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
========================================================
The src/plugins/CountAncestors.py file is Copyright 2001 Jesper Zedlitz
and Copyright 2001-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
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
========================================================
The files:
src/plugins/DetAncestralReport.py
src/plugins/DetDescendantReport.py
are Copyright 2000-2002 Bruce J. DeGrasse
and Copyright 2002-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
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
========================================================
The files:
src/date_test.py
src/DataViews/_PedigreeView.py
src/plugins/DumpGenderStats.py
src/plugins/ExportVCalendar.py
src/plugins/ExportVCard.py
src/plugins/ImportGeneWeb.py
src/plugins/ImportvCard.py
src/plugins/TestcaseGenerator.py
src/plugins/WriteGeneWeb.py
are Copyright 2001-2006 Martin Hawlisch, 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
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
========================================================
The files:
src/ReportBase/__init__.py
src/ReportBase/_Report.py
are Copyright 2001 David R. Hampton
and Copyright 2001-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
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License with
the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA

1
debian/gramps.dirs vendored
View File

@ -1,2 +1 @@
usr/share/pixmaps
usr/share/mime/packages

1
debian/gramps.docs vendored
View File

@ -1,4 +1,5 @@
AUTHORS
FAQ
NEWS
README
TODO

3
debian/gramps.files vendored
View File

@ -1,3 +0,0 @@
/usr/bin/
/usr/share/
/etc

View File

@ -1 +0,0 @@
debian/gramps.xpm usr/share/pixmaps/

2
debian/gramps.menu vendored
View File

@ -1,3 +1,3 @@
?package(gramps):needs="X11" section="Applications/Office"\
?package(gramps):needs="X11" section="Apps/Tools"\
title="gramps" command="/usr/bin/gramps"\
icon="/usr/share/pixmaps/gramps.xpm"

View File

@ -1,9 +1,3 @@
#!/bin/sh
set -e
# Update mime database postinst
if [ -x /usr/sbin/update-mime-database ]; then
update-mime-database /usr/share/mime
fi
#!/bin/sh -e
#DEBHELPER#

View File

@ -1,9 +1,3 @@
#!/bin/sh
set -e
# Update mime database postrm
if [ -x /usr/sbin/update-mime-database ]; then
update-mime-database /usr/share/mime
fi
#!/bin/sh -e
#DEBHELPER#

1
debian/pycompat vendored
View File

@ -1 +0,0 @@
2

85
debian/rules vendored
View File

@ -1,17 +1,76 @@
#!/usr/bin/make -f
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
#export DH_OPTIONS=-v
%:
dh $@ --with python2
build: build-stamp
build-stamp:
dh_testdir
# Remove COPYING file (duplicates standard copyright)
override_dh_install:
dh_install
# Need COPYING file into About dialog
#rm debian/gramps/usr/share/gramps/COPYING
./configure \
--enable-packager-mode \
--disable-scrollkeeper \
--prefix=/usr \
--mandir=\$${prefix}/share/man \
--sysconfdir=/etc
$(MAKE)
# Test packager mode to avoid installing mime type
override_dh_auto_configure:
dh_auto_configure -- --enable-packager-mode
touch build-stamp
clean:
dh_testdir
dh_testroot
-rm -f build-stamp
-$(MAKE) clean
-rm -f src/*.pyo src/*/*.pyo src/*/*/*.pyo src/*/*/*/*.pyo
-rm -f config.status config.log
dh_clean
install: build
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs
GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1
$(MAKE) install DESTDIR=`pwd`/debian/gramps
# Remove help-related dirs, they will go into gramps-help package
-rm -rf debian/gramps/usr/share/gnome
-rm -rf debian/gramps/usr/share/omf
# Remove byte-compiled python files
-find debian/gramps/usr/share/ -name "*.pyo" -exec rm -f '{}' ';'
# Copy icon file
cp debian/gramps.xpm debian/gramps/usr/share/pixmaps/
# cp src/gramps.xpm debian/tmp/usr/share/pixmaps/
#cp src/data/gramps.svg debian/gramps/usr/share/pixmaps/
#chmod 644 debian/gramps/usr/share/pixmaps/gramps.svg
# Instal gramps-help things
$(MAKE) -C help install DESTDIR=`pwd`/debian/gramps-help
# Build architecture-independent files here.
binary-indep: build install
dh_testdir
dh_testroot
dh_installdocs
dh_installmenu --package=gramps
dh_installman --package=gramps
dh_installmime -i
dh_installchangelogs --package=gramps ChangeLog
dh_installchangelogs --package=gramps-help help/ChangeLog
dh_gconf --package=gramps
dh_scrollkeeper --package=gramps-help
dh_compress -i
dh_fixperms -i
dh_python --package=gramps
dh_installdeb -i
dh_gencontrol -i
dh_md5sums -i
dh_builddeb -i
# Build architecture-dependent files here.
binary-arch: build install
binary: binary-indep binary-arch
.PHONY: build clean binary-indep binary-arch binary install

3
debian/watch vendored
View File

@ -1,3 +0,0 @@
version=3
http://sf.net/gramps/gramps-(.+)\.tar\.gz

View File

@ -1,88 +0,0 @@
# Makefile for Sphinx documentation
#
# You can set these variables from the command line.
SPHINXOPTS =
SPHINXBUILD = sphinx-build
PAPER =
# Internal variables.
PAPEROPT_a4 = -D latex_paper_size=a4
PAPEROPT_letter = -D latex_paper_size=letter
ALLSPHINXOPTS = -d _build/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
.PHONY: help clean html dirhtml pickle json htmlhelp qthelp latex changes linkcheck doctest
help:
@echo "Please use \`make <target>' where <target> is one of"
@echo " html to make standalone HTML files"
@echo " dirhtml to make HTML files named index.html in directories"
@echo " pickle to make pickle files"
@echo " json to make JSON files"
@echo " htmlhelp to make HTML files and a HTML help project"
@echo " qthelp to make HTML files and a qthelp project"
@echo " latex to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
@echo " changes to make an overview of all changed/added/deprecated items"
@echo " linkcheck to check all external links for integrity"
@echo " doctest to run all doctests embedded in the documentation (if enabled)"
clean:
-rm -rf _build/*
html:
$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) _build/html
@echo
@echo "Build finished. The HTML pages are in _build/html."
dirhtml:
$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) _build/dirhtml
@echo
@echo "Build finished. The HTML pages are in _build/dirhtml."
pickle:
$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) _build/pickle
@echo
@echo "Build finished; now you can process the pickle files."
json:
$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) _build/json
@echo
@echo "Build finished; now you can process the JSON files."
htmlhelp:
$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) _build/htmlhelp
@echo
@echo "Build finished; now you can run HTML Help Workshop with the" \
".hhp project file in _build/htmlhelp."
qthelp:
$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) _build/qthelp
@echo
@echo "Build finished; now you can run "qcollectiongenerator" with the" \
".qhcp project file in _build/qthelp, like this:"
@echo "# qcollectiongenerator _build/qthelp/Gramps.qhcp"
@echo "To view the help file:"
@echo "# assistant -collectionFile _build/qthelp/Gramps.qhc"
latex:
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) _build/latex
@echo
@echo "Build finished; the LaTeX files are in _build/latex."
@echo "Run \`make all-pdf' or \`make all-ps' in that directory to" \
"run these through (pdf)latex."
changes:
$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) _build/changes
@echo
@echo "The overview file is in _build/changes."
linkcheck:
$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) _build/linkcheck
@echo
@echo "Link check complete; look for any errors in the above output " \
"or in _build/linkcheck/output.txt."
doctest:
$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) _build/doctest
@echo "Testing of doctests in the sources finished, look at the " \
"results in _build/doctest/output.txt."

View File

@ -1,72 +0,0 @@
Installation and building the docs
==================================
You need to install sphinx. Assuming you have installed the python setuptools, just do:
sudo easy_install sphinx
Once installed, go to the docs directory, and do:
make html
Which will produce the html output in docs/_build/html
Documentation Guidelines
=======================
Doc strings in python files should be written in reStructured text: http://docutils.sourceforge.net/docs/user/rst/quickref.html
The typical docstring for GRAMPS should look like this:
"""Brief synopsis
This is a longer explanation, which may include *italics* or **bold**, or
a link to another method :meth:`~gen.lib.person.Person.get_handle`
Then, you need to provide optional subsection in this order (just to be
consistent and have a uniform documentation, nothing prevent you to switch
the order).
:param arg1: the first value
:type arg1: int or float or :class:`~gen.lib.baseobj.BaseObject`
:param arg2: the second value
:type arg2: int or float
:param arg3: the third value
:returns: arg1/arg2 +arg3
:rtype: float, this is the return type
:Examples:
>>> import template
>>> a = MainClass()
>>> a.function2(1,1,1)
2
:note:
can be useful to emphasize
important feature
:See Also:
:class:`MainClass1`
:Warnings:
arg2 must be non-zero.
:Todo:
check that arg2 is non zero.
"""
For a class, use :cvar variable: for class variable, :ivar variable: for instance class
variable, .. attribute:: attribute: for attributes, ....
See http://sphinx.pocoo.org/markup/desc.html and http://sphinx.pocoo.org/markup/inline.html
Tips and Tricks
===============
Change in many files something:
perl -pi -w -e "s/L{PersonRef}/:class:\`\~gen.lib.personref.PersonRef\`/g;" *.py
here L{PersonRef} is changed in :class:`~gen.lib.personref.PersonRef
`

View File

@ -1,48 +0,0 @@
##################
Code Documentation
##################
*GRAMPS* provides several general API. The most important is the *gen* module, providing access to all code that can be of interest outside of the GRAMPS program.
The :mod:`gen` Module
=======================
.. automodule:: gen
Contents:
.. toctree::
:maxdepth: 2
gen/gen_lib
gen/gen
gen/gen_db
gen/gen_display
gen/gen_plug
gen/gen_proxy
gen/gen_utils
The GRAMPS Application
========================
Contents:
.. toctree::
:maxdepth: 2
corecli/cli
coregui/gui
date
relationship
simple
utils
Usefull snippets
===================
Contents:
.. toctree::
:maxdepth: 2
html

View File

@ -1,202 +0,0 @@
# -*- coding: utf-8 -*-
#
# Gramps documentation build configuration file, created by
# sphinx-quickstart on Sat Jun 20 00:07:37 2009.
#
# This file is execfile()d with the current directory set to its containing dir.
#
# Note that not all possible configuration values are present in this
# autogenerated file.
#
# All configuration values have a default; values that are commented out
# serve to show the default.
import sys, os
# If extensions (or modules to document with autodoc) are in another directory,
# add these directories to sys.path here. If the directory is relative to the
# documentation root, use os.path.abspath to make it absolute, like shown here.
#sys.path.append(os.path.abspath('.'))
#documentation in root/docs, allow import from root/src where GRAMPS modules life
sourcedir = (os.path.abspath('.')).split(os.sep)[:-1] + ['src']
sys.path.append((os.sep).join(sourcedir))
#make it possible to add plugins --> walk the plugin dir and add to sys.path.append
for (dirpath, dirnames, filenames) in os.walk((os.sep).join(sourcedir + ['plugins'])):
# add the directory to the python search path
sys.path.append(dirpath)
# -- General configuration -----------------------------------------------------
# Add any Sphinx extension module names here, as strings. They can be extensions
# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
extensions = ['sphinx.ext.autodoc', 'sphinx.ext.todo', 'sphinx.ext.coverage']
# Add any paths that contain templates here, relative to this directory.
templates_path = ['_templates']
# The suffix of source filenames.
source_suffix = '.rst'
# The encoding of source files.
#source_encoding = 'utf-8'
# The master toctree document.
master_doc = 'index'
# General information about the project.
project = u'Gramps'
copyright = u'2012, The Gramps Project'
# The version info for the project you're documenting, acts as replacement for
# |version| and |release|, also used in various other places throughout the
# built documents.
#
# The short X.Y version.
version = '3.4'
# The full version, including alpha/beta/rc tags.
release = '3.4.0'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
#language = None
# There are two options for replacing |today|: either, you set today to some
# non-false value, then it is used:
#today = ''
# Else, today_fmt is used as the format for a strftime call.
#today_fmt = '%B %d, %Y'
# List of documents that shouldn't be included in the build.
#unused_docs = []
# List of directories, relative to source directory, that shouldn't be searched
# for source files.
exclude_trees = ['_build']
# The reST default role (used for this markup: `text`) to use for all documents.
#default_role = None
# If true, '()' will be appended to :func: etc. cross-reference text.
#add_function_parentheses = True
# If true, the current module name will be prepended to all description
# unit titles (such as .. function::).
#add_module_names = True
# If true, sectionauthor and moduleauthor directives will be shown in the
# output. They are ignored by default.
#show_authors = False
# The name of the Pygments (syntax highlighting) style to use.
pygments_style = 'sphinx'
# A list of ignored prefixes for module index sorting.
#modindex_common_prefix = []
# -- Options for HTML output ---------------------------------------------------
# The theme to use for HTML and HTML Help pages. Major themes that come with
# Sphinx are currently 'default' and 'sphinxdoc'.
html_theme = 'default'
# Theme options are theme-specific and customize the look and feel of a theme
# further. For a list of options available for each theme, see the
# documentation.
#html_theme_options = {}
# Add any paths that contain custom themes here, relative to this directory.
#html_theme_path = []
# The name for this set of Sphinx documents. If None, it defaults to
# "<project> v<release> documentation".
#html_title = None
# A shorter title for the navigation bar. Default is the same as html_title.
#html_short_title = None
# The name of an image file (relative to this directory) to place at the top
# of the sidebar.
#html_logo = None
# The name of an image file (within the static path) to use as favicon of the
# docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32
# pixels large.
#html_favicon = None
# Add any paths that contain custom static files (such as style sheets) here,
# relative to this directory. They are copied after the builtin static files,
# so a file named "default.css" will overwrite the builtin "default.css".
html_static_path = ['_static']
# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
# using the given strftime format.
#html_last_updated_fmt = '%b %d, %Y'
# If true, SmartyPants will be used to convert quotes and dashes to
# typographically correct entities.
#html_use_smartypants = True
# Custom sidebar templates, maps document names to template names.
#html_sidebars = {}
# Additional templates that should be rendered to pages, maps page names to
# template names.
#html_additional_pages = {}
# If false, no module index is generated.
#html_use_modindex = True
# If false, no index is generated.
#html_use_index = True
# If true, the index is split into individual pages for each letter.
#html_split_index = False
# If true, links to the reST sources are added to the pages.
#html_show_sourcelink = True
# If true, an OpenSearch description file will be output, and all pages will
# contain a <link> tag referring to it. The value of this option must be the
# base URL from which the finished HTML is served.
#html_use_opensearch = ''
# If nonempty, this is the file name suffix for HTML files (e.g. ".xhtml").
#html_file_suffix = ''
# Output file base name for HTML help builder.
htmlhelp_basename = 'Grampsdoc'
# -- Options for LaTeX output --------------------------------------------------
# The paper size ('letter' or 'a4').
#latex_paper_size = 'letter'
# The font size ('10pt', '11pt' or '12pt').
#latex_font_size = '10pt'
# Grouping the document tree into LaTeX files. List of tuples
# (source start file, target name, title, author, documentclass [howto/manual]).
latex_documents = [
('index', 'Gramps.tex', u'Gramps Documentation',
u'The Gramps Project', 'manual'),
]
# The name of an image file (relative to this directory) to place at the top of
# the title page.
#latex_logo = None
# For "manual" documents, if this is true, then toplevel headings are parts,
# not chapters.
#latex_use_parts = False
# Additional stuff for the LaTeX preamble.
#latex_preamble = ''
# Documents to append as an appendix to all manuals.
#latex_appendices = []
# If false, no module index is generated.
#latex_use_modindex = True

View File

@ -1,54 +0,0 @@
##########################
The :mod:`cli` Module
##########################
.. automodule:: cli
*****************************
Argument Handler
*****************************
.. automodule:: cli.arghandler
.. autoclass:: ArgHandler
:members:
:undoc-members:
:show-inheritance:
*****************************
Argument Parser
*****************************
.. automodule:: cli.argparser
.. autoclass:: ArgParser
:members:
:undoc-members:
:show-inheritance:
*****************************
CLI DB manager
*****************************
.. automodule:: cli.clidbman
.. autoclass:: CLIDbManager
:members:
:undoc-members:
:show-inheritance:
*****************************
Gramps CLI
*****************************
.. automodule:: cli.grampscli
.. autoclass:: CLIDbLoader
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: CLIManager
:members:
:undoc-members:
:show-inheritance:
*****************************
User
*****************************
.. automodule:: cli.user
.. autoclass:: User
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,224 +0,0 @@
##########################
The :mod:`gui` Module
##########################
.. automodule:: gui
*****************************
Gramps
*****************************
.. automodule:: gui.grampsgui
.. autoclass:: Gramps
:members:
:undoc-members:
:show-inheritance:
*****************************
About Dialog
*****************************
.. automodule:: gui.aboutdialog
.. autoclass:: AuthorParser
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: GrampsAboutDialog
:members:
:undoc-members:
:show-inheritance:
*****************************
Base Sidebar
*****************************
.. automodule:: gui.basesidebar
.. autoclass:: BaseSidebar
:members:
:undoc-members:
:show-inheritance:
*****************************
Column Order
*****************************
.. automodule:: gui.columnorder
.. autoclass:: ColumnOrder
:members:
:undoc-members:
:show-inheritance:
*****************************
Configuration
*****************************
.. automodule:: gui.configure
.. autoclass:: ConfigureDialog
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DisplayNameEditor
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: GrampsPreferences
:members:
:undoc-members:
:show-inheritance:
*****************************
GUI Element (DB)
*****************************
.. automodule:: gui.dbguielement
.. autoclass:: DbGUIElement
:members:
:undoc-members:
:show-inheritance:
*****************************
DB Loader
*****************************
.. automodule:: gui.dbloader
.. autoclass:: DbLoader
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: GrampsFormatWidget
:members:
:undoc-members:
:show-inheritance:
*****************************
DB Manager
*****************************
.. automodule:: gui.dbman
.. autoclass:: DbManager
:members:
:undoc-members:
:show-inheritance:
*****************************
Filter Editor
*****************************
.. automodule:: gui.filtereditor
.. autoclass:: EditFilter
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: EditRule
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: FilterEditor
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: MyBoolean
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: MyEntry
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: MyFilters
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: MyID
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: MyInteger
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: MyLesserEqualGreater
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: MyList
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: MyPlaces
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: MySelect
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: MySource
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: ShowResults
:members:
:undoc-members:
:show-inheritance:
*****************************
Gramps Bar
*****************************
.. automodule:: gui.grampsbar
.. autoclass:: DetachedWindow
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: GrampsBar
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: TabGramplet
:members:
:undoc-members:
:show-inheritance:
*****************************
Navigator
*****************************
.. automodule:: gui.navigator
.. autoclass:: Navigator
:members:
:undoc-members:
:show-inheritance:
*****************************
Plugins Manager
*****************************
.. automodule:: gui.pluginmanager
.. autoclass:: GuiPluginManager
:members:
:undoc-members:
:show-inheritance:
*****************************
User
*****************************
.. automodule:: gui.user
.. autoclass:: User
:members:
:undoc-members:
:show-inheritance:
*****************************
Utils
*****************************
.. automodule:: gui.utils
.. autoclass:: CLIDialog
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: CLIVbox
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: ProgressMeter
:members:
:undoc-members:
:show-inheritance:
*****************************
Views Manager
*****************************
.. automodule:: gui.viewmanager
.. autoclass:: ViewManager
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,279 +0,0 @@
#########################################
The :class:`Date Handler` Classes
#########################################
DateParser
====================================
.. automodule:: DateHandler._DateParser
.. autoclass:: DateParser
:members:
:undoc-members:
:show-inheritance:
DateDisplay
====================================
.. automodule:: DateHandler._DateDisplay
.. autoclass:: DateDisplay
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateDisplayEn
:members:
:undoc-members:
:show-inheritance:
DateUtils
====================================
.. automodule:: DateHandler._DateUtils
:members:
:undoc-members:
:show-inheritance:
DateHandler
====================================
.. automodule:: DateHandler._DateHandler
:members:
:undoc-members:
:show-inheritance:
Localized Date Handlers
====================================
*****************************
DateHandler (Bulgarian)
*****************************
.. autoclass:: DateHandler._Date_bg.DateParserBG
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_bg.DateDisplayBG
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Catalan)
*****************************
.. autoclass:: DateHandler._Date_ca.DateParserCA
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_ca.DateDisplayCA
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Czech)
*****************************
.. autoclass:: DateHandler._Date_cs.DateParserCZ
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_cs.DateDisplayCZ
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (German)
*****************************
.. autoclass:: DateHandler._Date_de.DateParserDE
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_de.DateDisplayDE
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Spanish)
*****************************
.. autoclass:: DateHandler._Date_es.DateParserES
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_es.DateDisplayES
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Finnish)
*****************************
.. autoclass:: DateHandler._Date_fi.DateParserFI
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_fi.DateDisplayFI
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (French)
*****************************
.. autoclass:: DateHandler._Date_fr.DateParserFR
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_fr.DateDisplayFR
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Croatian)
*****************************
.. autoclass:: DateHandler._Date_hr.DateParserHR
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_hr.DateDisplayHR
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Italian)
*****************************
.. autoclass:: DateHandler._Date_it.DateParserIT
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_it.DateDisplayIT
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Lituanian)
*****************************
.. autoclass:: DateHandler._Date_lt.DateParserLT
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_lt.DateDisplayLT
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Norwegian)
*****************************
.. autoclass:: DateHandler._Date_nb.DateParserNb
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_nb.DateDisplayNb
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Dutch)
*****************************
.. autoclass:: DateHandler._Date_nl.DateParserNL
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_nl.DateDisplayNL
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Polish)
*****************************
.. autoclass:: DateHandler._Date_pl.DateParserPL
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_pl.DateDisplayPL
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Portuguese)
*****************************
.. autoclass:: DateHandler._Date_pt.DateParserPT
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_pt.DateDisplayPT
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Russian)
*****************************
.. autoclass:: DateHandler._Date_ru.DateParserRU
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_ru.DateDisplayRU
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Slovak)
*****************************
.. autoclass:: DateHandler._Date_sk.DateParserSK
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_sk.DateDisplaySK
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Slovenian)
*****************************
.. autoclass:: DateHandler._Date_sl.DateParserSL
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_sl.DateDisplaySL
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Serbian)
*****************************
.. autoclass:: DateHandler._Date_sr.DateParserSR
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_sr.DateDisplaySR_latin
:members:
:undoc-members:
:show-inheritance:
*****************************
DateHandler (Swedish)
*****************************
.. autoclass:: DateHandler._Date_sv.DateParserSv
:members:
:undoc-members:
:show-inheritance:
.. autoclass:: DateHandler._Date_sv.DateDisplaySv
:members:
:undoc-members:
:show-inheritance:
#########################################
The :class:`Date Edition` Classes
#########################################
DateEdit
====================================
.. automodule:: DateEdit
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,4 +0,0 @@
Developer Guide
===============
Please consult the API documentation, and the development part of `our wiki <http://gramps-project.org>`_\ .

View File

@ -1,23 +0,0 @@
##########################
The :mod:`gen` Module
##########################
.. automodule:: gen
*****************************
Update callback
*****************************
.. automodule:: gen.updatecallback
.. autoclass:: UpdateCallback
:members:
:undoc-members:
:show-inheritance:
*****************************
User
*****************************
.. automodule:: gen.user
.. autoclass:: User
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,78 +0,0 @@
##########################
The :mod:`gen.db` Module
##########################
.. automodule:: gen.db
GrampsDbBase
====================================
.. automodule:: gen.db.base
:members:
:undoc-members:
:show-inheritance:
GrampsDbRead
====================================
.. automodule:: gen.db.read
:members:
:show-inheritance:
GrampsDbWrite
====================================
.. automodule:: gen.db.write
:members:
:undoc-members:
:show-inheritance:
GrampsCursor
====================================
.. automodule:: gen.db.cursor
:members:
:undoc-members:
:show-inheritance:
BSDDBtxn
====================================
.. automodule:: gen.db.bsddbtxn
:members:
:undoc-members:
:show-inheritance:
GrampsDbTxn
====================================
.. automodule:: gen.db.txn
:members:
:undoc-members:
:show-inheritance:
GrampsDbUndo
====================================
.. automodule:: gen.db.undoredo
:members:
:undoc-members:
:show-inheritance:
DbConst
====================================
.. automodule:: gen.db.dbconst
:members:
GrampsDbException
====================================
.. automodule:: gen.db.exceptions
:members:
:undoc-members:
:show-inheritance:
Upgrade utilities
====================================
.. automodule:: gen.db.upgrade
:members:
:undoc-members:
Backup
====================================
.. automodule:: gen.db.backup
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,12 +0,0 @@
#############################
The :mod:`gen.display` Module
#############################
.. automodule:: gen.display
Name
====================================
.. automodule:: gen.display.name
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,528 +0,0 @@
##########################
The :mod:`gen.lib` Module
##########################
.. automodule:: gen.lib
*****************************
Base objects
*****************************
BaseObject
====================================
.. automodule:: gen.lib.baseobj
.. autoclass:: gen.lib.baseobj.BaseObject
:members:
:undoc-members:
:show-inheritance:
AddressBase
====================================
.. automodule:: gen.lib.addressbase
.. autoclass:: AddressBase
:members:
:undoc-members:
:show-inheritance:
AttributeBase
====================================
.. automodule:: gen.lib.attrbase
.. autoclass:: AttributeBase
:members:
:undoc-members:
:show-inheritance:
CitationBase
====================================
.. automodule:: gen.lib.citationbase
.. autoclass:: CitationBase
:members:
:undoc-members:
:show-inheritance:
DateBase
====================================
.. automodule:: gen.lib.datebase
.. autoclass:: DateBase
:members:
:undoc-members:
:show-inheritance:
LdsOrdBase
====================================
.. automodule:: gen.lib.ldsordbase
.. autoclass:: LdsOrdBase
:members:
:undoc-members:
:show-inheritance:
LocationBase
====================================
.. automodule:: gen.lib.locationbase
.. autoclass:: LocationBase
:members:
:undoc-members:
:show-inheritance:
MediaBase
====================================
.. automodule:: gen.lib.mediabase
.. autoclass:: MediaBase
:members:
:undoc-members:
:show-inheritance:
NoteBase
====================================
.. automodule:: gen.lib.notebase
.. autoclass:: NoteBase
:members:
:undoc-members:
:show-inheritance:
PlaceBase
====================================
.. automodule:: gen.lib.placebase
.. autoclass:: PlaceBase
:members:
:undoc-members:
:show-inheritance:
PrivacyBase
====================================
.. automodule:: gen.lib.privacybase
.. autoclass:: PrivacyBase
:members:
:undoc-members:
:show-inheritance:
RefBase
====================================
.. automodule:: gen.lib.refbase
.. autoclass:: RefBase
:members:
:undoc-members:
:show-inheritance:
SurnameBase
====================================
.. automodule:: gen.lib.surnamebase
.. autoclass:: SurnameBase
:members:
:undoc-members:
:show-inheritance:
TagBase
====================================
.. automodule:: gen.lib.tagbase
.. autoclass:: TagBase
:members:
:undoc-members:
:show-inheritance:
UrlBase
====================================
.. automodule:: gen.lib.urlbase
.. autoclass:: UrlBase
:members:
:undoc-members:
:show-inheritance:
*****************************
Primary objects
*****************************
BasicPrimaryObject
====================================
.. automodule:: gen.lib.primaryobj
.. autoclass:: BasicPrimaryObject
:members:
:undoc-members:
:show-inheritance:
PrimaryObject
====================================
.. autoclass:: PrimaryObject
:members:
:undoc-members:
:show-inheritance:
Person
====================================
.. automodule:: gen.lib.person
.. autoclass:: Person
:members:
:undoc-members:
:show-inheritance:
Family
====================================
.. automodule:: gen.lib.family
.. autoclass:: Family
:members:
:undoc-members:
:show-inheritance:
Event
====================================
.. automodule:: gen.lib.event
.. autoclass:: Event
:members:
:undoc-members:
:show-inheritance:
Place
====================================
.. automodule:: gen.lib.place
.. autoclass:: Place
:members:
:undoc-members:
:show-inheritance:
Source
====================================
.. automodule:: gen.lib.src
.. autoclass:: Source
:members:
:undoc-members:
:show-inheritance:
Citation
====================================
.. automodule:: gen.lib.citation
.. autoclass:: Citation
:members:
:undoc-members:
:show-inheritance:
Media Object
====================================
.. automodule:: gen.lib.mediaobj
.. autoclass:: MediaObject
:members:
:undoc-members:
:show-inheritance:
Repository
====================================
.. automodule:: gen.lib.repo
.. autoclass:: Repository
:members:
:undoc-members:
:show-inheritance:
Note
====================================
.. automodule:: gen.lib.note
.. autoclass:: Note
:members:
:undoc-members:
:show-inheritance:
*****************************
Secondary objects
*****************************
Secondary Object
====================================
.. automodule:: gen.lib.secondaryobj
.. autoclass:: SecondaryObject
:members:
:undoc-members:
:show-inheritance:
Address
====================================
.. automodule:: gen.lib.address
.. autoclass:: Address
:members:
:undoc-members:
:show-inheritance:
Attribute
====================================
.. automodule:: gen.lib.attribute
.. autoclass:: Attribute
:members:
:undoc-members:
:show-inheritance:
LdsOrd
====================================
.. automodule:: gen.lib.ldsord
.. autoclass:: LdsOrd
:members:
:undoc-members:
:show-inheritance:
Location
====================================
.. automodule:: gen.lib.location
.. autoclass:: Location
:members:
:undoc-members:
:show-inheritance:
Name
====================================
.. automodule:: gen.lib.name
.. autoclass:: Name
:members:
:undoc-members:
:show-inheritance:
Surname
====================================
.. automodule:: gen.lib.surname
.. autoclass:: Surname
:members:
:undoc-members:
:show-inheritance:
Url
====================================
.. automodule:: gen.lib.url
.. autoclass:: Url
:members:
:undoc-members:
:show-inheritance:
*****************************
Reference objects
*****************************
ChildRef
====================================
.. automodule:: gen.lib.childref
.. autoclass:: ChildRef
:members:
:undoc-members:
:show-inheritance:
EventRef
====================================
.. automodule:: gen.lib.eventref
.. autoclass:: EventRef
:members:
:undoc-members:
:show-inheritance:
MediaRef
====================================
.. automodule:: gen.lib.mediaref
.. autoclass:: MediaRef
:members:
:undoc-members:
:show-inheritance:
PersonRef
====================================
.. automodule:: gen.lib.personref
.. autoclass:: PersonRef
:members:
:undoc-members:
:show-inheritance:
RepoRef
====================================
.. automodule:: gen.lib.reporef
.. autoclass:: RepoRef
:members:
:undoc-members:
:show-inheritance:
*****************************
Table object
*****************************
Table object
====================================
.. automodule:: gen.lib.tableobj
:members:
:undoc-members:
:show-inheritance:
*****************************
Date objects
*****************************
.. automodule:: gen.lib.date
Date
====================================
.. autoclass:: Date
:members:
:undoc-members:
:show-inheritance:
Span
====================================
.. autoclass:: Span
:members:
:undoc-members:
:show-inheritance:
DateError
====================================
.. autoexception:: DateError
*****************************
Text objects
*****************************
StyledTextTag
===================
.. automodule:: gen.lib.styledtexttag
.. autoclass:: StyledTextTag
:members:
:undoc-members:
:show-inheritance:
StyledText
===========
.. automodule:: gen.lib.styledtext
.. autoclass:: StyledText
:members:
:undoc-members:
:show-inheritance:
*****************************
Meta data
*****************************
GenderStats
============
.. automodule:: gen.lib.genderstats
.. autoclass:: GenderStats
:members:
:undoc-members:
:show-inheritance:
Researcher
===========
.. automodule:: gen.lib.researcher
.. autoclass:: Researcher
:members:
:undoc-members:
:show-inheritance:
*****************************
Type classes
*****************************
.. automodule:: gen.lib.grampstype
.. autoclass:: GrampsTypeMeta
:members:
:undoc-members:
:show-inheritance:
GrampsType
===========
.. autoclass:: GrampsType
:members:
:undoc-members:
:show-inheritance:
AttributeType
=============
.. automodule:: gen.lib.attrtype
:members:
:undoc-members:
:show-inheritance:
ChildRefType
=============
.. automodule:: gen.lib.childreftype
:members:
:undoc-members:
:show-inheritance:
EventType
===========
.. automodule:: gen.lib.eventtype
.. autoclass:: EventType
:members:
:undoc-members:
:show-inheritance:
EventRoleType
==============
.. automodule:: gen.lib.eventroletype
:members:
:undoc-members:
:show-inheritance:
FamilyRelType
=============
.. automodule:: gen.lib.familyreltype
:members:
:undoc-members:
:show-inheritance:
MarkerType
==========
.. automodule:: gen.lib.markertype
:members:
:undoc-members:
:show-inheritance:
NameType
===========
.. automodule:: gen.lib.nametype
:members:
:undoc-members:
:show-inheritance:
NameOriginType
==============
.. automodule:: gen.lib.nameorigintype
:members:
:undoc-members:
:show-inheritance:
NoteType
=========
.. automodule:: gen.lib.notetype
:members:
:undoc-members:
:show-inheritance:
RepositoryType
==============
.. automodule:: gen.lib.repotype
:members:
:undoc-members:
:show-inheritance:
SourceMediaType
================
.. automodule:: gen.lib.srcmediatype
:members:
:undoc-members:
:show-inheritance:
StyledTextTagType
==================
.. automodule:: gen.lib.styledtexttagtype
:members:
:undoc-members:
:show-inheritance:
UrlType
========
.. automodule:: gen.lib.urltype
:members:
:undoc-members:
:show-inheritance:
*****************************
Privacy
*****************************
PrivateSourceNote
============
.. automodule:: gen.lib.privsrcnote
.. autoclass:: PrivateSourceNote
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,241 +0,0 @@
############################
The :mod:`gen.plug` Module
############################
.. automodule:: gen.plug
Plugin
====================================
.. automodule:: gen.plug._plugin
:members:
:undoc-members:
:show-inheritance:
BaseManager
====================================
.. automodule:: gen.plug._manager
:members:
:undoc-members:
:show-inheritance:
Export
====================================
.. automodule:: gen.plug._export
:members:
:undoc-members:
:show-inheritance:
Gramplet
====================================
.. automodule:: gen.plug._gramplet
:members:
:undoc-members:
:show-inheritance:
Import
====================================
.. automodule:: gen.plug._import
:members:
:undoc-members:
:show-inheritance:
Menu
====================================
.. automodule:: gen.plug.menu._menu
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._boolean
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._booleanlist
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._color
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._destination
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._enumeratedlist
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._family
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._filter
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._media
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._note
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._number
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._option
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._person
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._personlist
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._placelist
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._string
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._style
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._surnamecolor
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.menu._text
:members:
:undoc-members:
:show-inheritance:
*****************************
Options
*****************************
.. automodule:: gen.plug._options
:members:
:undoc-members:
:show-inheritance:
Reports
====================================
.. automodule:: gen.plug.report._options
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.report._bibliography
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.report._constants
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.report.endnotes
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.report._paper
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.report._reportbase
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.report.utils
:members:
:undoc-members:
:show-inheritance:
*****************************
Docgen
*****************************
.. automodule:: gen.plug._docgenplugin
:members:
:undoc-members:
:show-inheritance:
*****************************
Generators
*****************************
.. automodule:: gen.plug.docgen.basedoc
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.docgen.drawdoc
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.docgen.fontscale
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.docgen.fontstyle
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.docgen.graphdoc
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.docgen.graphicstyle
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.docgen.paperstyle
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.docgen.paragraphstyle
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.docgen.stylesheet
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.docgen.tablestyle
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.docgen.textdoc
:members:
:undoc-members:
:show-inheritance:
*****************************
Doc Backend
*****************************
.. automodule:: gen.plug.docbackend.cairobackend
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.plug.docbackend.docbackend
:members:
:undoc-members:
:show-inheritance:
Register
====================================
.. automodule:: gen.plug._pluginreg
:members:
:undoc-members:
:show-inheritance:
Utils
====================================
.. automodule:: gen.plug.utils
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,40 +0,0 @@
############################
The :mod:`gen.proxy` Module
############################
.. automodule:: gen.proxy
Proxy Base
====================================
.. automodule:: gen.proxy.proxybase
:members:
:undoc-members:
:show-inheritance:
Filter
====================================
.. automodule:: gen.proxy.filter
:members:
:undoc-members:
:show-inheritance:
Living
====================================
.. automodule:: gen.proxy.living
:members:
:undoc-members:
:show-inheritance:
Private
====================================
.. automodule:: gen.proxy.private
:members:
:undoc-members:
:show-inheritance:
References
====================================
.. automodule:: gen.proxy.referencedbyselection
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,26 +0,0 @@
############################
The :mod:`gen.utils` Module
############################
.. automodule:: gen.utils
Utils
====================================
.. automodule:: gen.utils.callback
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.utils.callman
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.utils.configmanager
:members:
:undoc-members:
:show-inheritance:
.. automodule:: gen.utils.fallback
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,11 +0,0 @@
##########################
The :class:`Html` Class
##########################
Contents:
.. automodule:: libhtml
.. autoclass:: Html
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,24 +0,0 @@
.. Gramps documentation master file, created by
sphinx-quickstart on Sat Jun 20 00:07:37 2009.
You can adapt this file completely to your liking, but it should at least
contain the root `toctree` directive.
Welcome to Gramps's documentation!
==================================
Contents:
.. toctree::
:maxdepth: 2
user_guide
developer_guide
api
Indices and tables
==================
* :ref:`genindex`
* :ref:`modindex`
* :ref:`search`

View File

@ -1,132 +0,0 @@
#########################################
The :class:`RelationshipCalculator` Class
#########################################
.. automodule:: Relationship
.. autoclass:: RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
*****************************
Localized Handlers
*****************************
Relationship (Czech)
====================================
.. autoclass:: rel_cs.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Danish)
====================================
.. autoclass:: rel_da.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (German)
====================================
.. autoclass:: rel_de.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Spanish)
====================================
.. autoclass:: rel_es.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Finnish)
====================================
.. autoclass:: rel_fi.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (French)
====================================
.. autoclass:: rel_fr.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Croatian)
====================================
.. autoclass:: rel_hr.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Hungarian)
====================================
.. autoclass:: rel_hu.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Italian)
====================================
.. autoclass:: rel_it.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Dutch)
====================================
.. autoclass:: rel_nl.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Norwegian)
====================================
.. autoclass:: rel_no.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Polish)
====================================
.. autoclass:: rel_pl.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Portuguese)
====================================
.. autoclass:: rel_pt.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Russian)
====================================
.. autoclass:: rel_ru.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Slovak)
====================================
.. autoclass:: rel_sk.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Slovenian)
====================================
.. autoclass:: rel_sl.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:
Relationship (Swedish)
====================================
.. autoclass:: rel_sv.RelationshipCalculator
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,26 +0,0 @@
###########################
The :class:`Simple` Classes
###########################
.. automodule:: Simple
Simple Access
====================================
.. automodule:: Simple._SimpleAccess
:members:
:undoc-members:
:show-inheritance:
Simple Doc
====================================
.. automodule:: Simple._SimpleDoc
:members:
:undoc-members:
:show-inheritance:
Simple Table
====================================
.. automodule:: Simple._SimpleTable
:members:
:undoc-members:
:show-inheritance:

View File

@ -1,4 +0,0 @@
User Guide
==========
Please consult the manual which you find on `our wiki <http://www.gramps-project.org/wiki/index.php?title=User_manual>`_\ .

View File

@ -1,12 +0,0 @@
############################
The :mod:`Utils` Module
############################
Contents:
.. automodule:: Utils
:members:
:undoc-members:
:show-inheritance:

File diff suppressed because it is too large Load Diff

Binary file not shown.

File diff suppressed because it is too large Load Diff

Binary file not shown.

Before

Width:  |  Height:  |  Size: 15 KiB

View File

@ -1,316 +0,0 @@
#!/bin/sh
# Run this to generate all the initial makefiles, etc.
# $Id$
#name of package
PKG_NAME=${PKG_NAME:-Package}
srcdir=${srcdir:-.}
# default version requirements ...
REQUIRED_AUTOCONF_VERSION=${REQUIRED_AUTOCONF_VERSION:-2.53}
REQUIRED_AUTOMAKE_VERSION=${REQUIRED_AUTOMAKE_VERSION:-1.4}
REQUIRED_GLIB_GETTEXT_VERSION=${REQUIRED_GLIB_GETTEXT_VERSION:-2.2.0}
REQUIRED_INTLTOOL_VERSION=${REQUIRED_INTLTOOL_VERSION:-0.25}
# a list of required m4 macros. Package can set an initial value
REQUIRED_M4MACROS=${REQUIRED_M4MACROS:-}
FORBIDDEN_M4MACROS=${FORBIDDEN_M4MACROS:-}
# Not all echo versions allow -n, so we check what is possible. This test is
# based on the one in autoconf.
case `echo "testing\c"; echo 1,2,3`,`echo -n testing; echo 1,2,3` in
*c*,-n*) ECHO_N= ;;
*c*,* ) ECHO_N=-n ;;
*) ECHO_N= ;;
esac
# some terminal codes ...
boldface="`tput bold 2>/dev/null`"
normal="`tput sgr0 2>/dev/null`"
printbold() {
echo $ECHO_N "$boldface"
echo "$@"
echo $ECHO_N "$normal"
}
printerr() {
echo "$@" >&2
}
autogen_options ()
{
if test "x$1" = "x"; then
return 0
fi
printbold "Checking command line options..."
while test "x$1" != "x" ; do
optarg=`expr "x$1" : 'x[^=]*=\(.*\)'`
case "$1" in
--noconfigure)
NOCONFIGURE=defined
AUTOGEN_EXT_OPT="$AUTOGEN_EXT_OPT --noconfigure"
echo " configure run disabled"
shift
;;
--nocheck)
AUTOGEN_EXT_OPT="$AUTOGEN_EXT_OPT --nocheck"
NOCHECK=defined
echo " autotools version check disabled"
shift
;;
--debug)
DEBUG=defined
AUTOGEN_EXT_OPT="$AUTOGEN_EXT_OPT --debug"
echo " debug output enabled"
shift
;;
-h|--help)
echo "autogen.sh (autogen options) -- (configure options)"
echo "autogen.sh help options: "
echo " --noconfigure don't run the configure script"
# echo " --nocheck don't do version checks"
echo " --debug debug the autogen process"
echo
echo " --with-autoconf PATH use autoconf in PATH"
echo " --with-automake PATH use automake in PATH"
echo
echo "Any argument either not in the above list or after a '--' will be "
echo "passed to ./configure."
exit 1
;;
--with-automake=*)
AUTOMAKE=$optarg
echo " using alternate automake in $optarg"
CONFIGURE_DEF_OPT="$CONFIGURE_DEF_OPT --with-automake=$AUTOMAKE"
shift
;;
--with-autoconf=*)
AUTOCONF=$optarg
echo " using alternate autoconf in $optarg"
CONFIGURE_DEF_OPT="$CONFIGURE_DEF_OPT --with-autoconf=$AUTOCONF"
shift
;;
--) shift ; break ;;
*)
echo " passing argument $1 to configure"
CONFIGURE_EXT_OPT="$CONFIGURE_EXT_OPT $1"
shift
;;
esac
done
for arg do CONFIGURE_EXT_OPT="$CONFIGURE_EXT_OPT $arg"; done
if test ! -z "$CONFIGURE_EXT_OPT"
then
echo " options passed to configure: $CONFIGURE_EXT_OPT"
fi
}
# Usage:
# compare_versions MIN_VERSION ACTUAL_VERSION
# returns true if ACTUAL_VERSION >= MIN_VERSION
compare_versions() {
ch_min_version=$1
ch_actual_version=$2
ch_status=0
IFS="${IFS= }"; ch_save_IFS="$IFS"; IFS="."
set $ch_actual_version
for ch_min in $ch_min_version; do
ch_cur=`echo $1 | sed 's/[^0-9].*$//'`; shift # remove letter suffixes
if [ -z "$ch_min" ]; then break; fi
if [ -z "$ch_cur" ]; then ch_status=1; break; fi
if [ $ch_cur -gt $ch_min ]; then break; fi
if [ $ch_cur -lt $ch_min ]; then ch_status=1; break; fi
done
IFS="$ch_save_IFS"
return $ch_status
}
# Usage:
# version_check PACKAGE VARIABLE CHECKPROGS MIN_VERSION SOURCE
# checks to see if the package is available
version_check() {
vc_package=$1
vc_variable=$2
vc_checkprogs=$3
vc_min_version=$4
vc_source=$5
vc_status=1
vc_checkprog=`eval echo "\\$$vc_variable"`
if [ -n "$vc_checkprog" ]; then
printbold "using $vc_checkprog for $vc_package"
return 0
fi
if test "x$vc_package" = "xautomake" -a "x$vc_min_version" = "x1.4"; then
vc_comparator="="
else
vc_comparator=">="
fi
printbold "Checking for $vc_package $vc_comparator $vc_min_version..."
for vc_checkprog in $vc_checkprogs; do
echo $ECHO_N " testing $vc_checkprog... "
if $vc_checkprog --version < /dev/null > /dev/null 2>&1; then
vc_actual_version=`$vc_checkprog --version | head -n 1 | \
sed 's/^.*[ ]\([0-9.]*[a-z]*\).*$/\1/'`
if compare_versions $vc_min_version $vc_actual_version; then
echo "found $vc_actual_version"
# set variables
eval "$vc_variable=$vc_checkprog; \
${vc_variable}_VERSION=$vc_actual_version"
vc_status=0
break
else
echo "too old (found version $vc_actual_version)"
fi
else
echo "not found."
fi
done
if [ "$vc_status" != 0 ]; then
printerr "***Error***: You must have $vc_package $vc_comparator $vc_min_version installed"
printerr " to build $PKG_NAME. Download the appropriate package for"
printerr " from your distribution or get the source tarball at"
printerr " $vc_source"
printerr
fi
return $vc_status
}
debug ()
# print out a debug message if DEBUG is a defined variable
{
if test ! -z "$DEBUG"
then
echo "DEBUG: $1"
fi
}
# Usage:
# require_m4macro filename.m4
# adds filename.m4 to the list of required macros
require_m4macro() {
case "$REQUIRED_M4MACROS" in
$1\ * | *\ $1\ * | *\ $1) ;;
*) REQUIRED_M4MACROS="$REQUIRED_M4MACROS $1" ;;
esac
}
forbid_m4macro() {
case "$FORBIDDEN_M4MACROS" in
$1\ * | *\ $1\ * | *\ $1) ;;
*) FORBIDDEN_M4MACROS="$FORBIDDEN_M4MACROS $1" ;;
esac
}
# Usage:
# add_to_cm_macrodirs dirname
# Adds the dir to $cm_macrodirs, if it's not there yet.
add_to_cm_macrodirs() {
case $cm_macrodirs in
"$1 "* | *" $1 "* | *" $1") ;;
*) cm_macrodirs="$cm_macrodirs $1";;
esac
}
# Usage:
# check_m4macros
# Checks that all the requested macro files are in the aclocal macro path
# Uses REQUIRED_M4MACROS and ACLOCAL variables.
check_m4macros() {
# construct list of macro directories
cm_macrodirs=`$ACLOCAL --print-ac-dir`
# aclocal also searches a version specific dir, eg. /usr/share/aclocal-1.9
# but it contains only Automake's own macros, so we can ignore it.
# Read the dirlist file, supported by Automake >= 1.7.
if compare_versions 1.7 $AUTOMAKE_VERSION && [ -s $cm_macrodirs/dirlist ]; then
cm_dirlist=`sed 's/[ ]*#.*//;/^$/d' $cm_macrodirs/dirlist`
if [ -n "$cm_dirlist" ] ; then
for cm_dir in $cm_dirlist; do
if [ -d $cm_dir ]; then
add_to_cm_macrodirs $cm_dir
fi
done
fi
fi
# Parse $ACLOCAL_FLAGS
set - $ACLOCAL_FLAGS
while [ $# -gt 0 ]; do
if [ "$1" = "-I" ]; then
add_to_cm_macrodirs "$2"
shift
fi
shift
done
cm_status=0
if [ -n "$REQUIRED_M4MACROS" ]; then
printbold "Checking for required M4 macros..."
# check that each macro file is in one of the macro dirs
for cm_macro in $REQUIRED_M4MACROS; do
cm_macrofound=false
for cm_dir in $cm_macrodirs; do
if [ -f "$cm_dir/$cm_macro" ]; then
cm_macrofound=true
break
fi
# The macro dir in Cygwin environments may contain a file
# called dirlist containing other directories to look in.
if [ -f "$cm_dir/dirlist" ]; then
for cm_otherdir in `cat $cm_dir/dirlist`; do
if [ -f "$cm_otherdir/$cm_macro" ]; then
cm_macrofound=true
break
fi
done
fi
done
if $cm_macrofound; then
:
else
printerr " $cm_macro not found"
cm_status=1
fi
done
fi
if [ -n "$FORBIDDEN_M4MACROS" ]; then
printbold "Checking for forbidden M4 macros..."
# check that each macro file is in one of the macro dirs
for cm_macro in $FORBIDDEN_M4MACROS; do
cm_macrofound=false
for cm_dir in $cm_macrodirs; do
if [ -f "$cm_dir/$cm_macro" ]; then
cm_macrofound=true
break
fi
done
if $cm_macrofound; then
printerr " $cm_macro found (should be cleared from macros dir)"
cm_status=1
fi
done
fi
if [ "$cm_status" != 0 ]; then
printerr "***Error***: some autoconf macros required to build $PKG_NAME"
printerr " were not found in your aclocal path, or some forbidden"
printerr " macros were found. Perhaps you need to adjust your"
printerr " ACLOCAL_FLAGS?"
printerr
fi
return $cm_status
}
toplevel_check()
{
srcfile=$1
test -f $srcfile || {
echo "You must run this script in the top-level $PKG_NAME directory"
exit 1
}
}

View File

@ -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
exec @PYTHON@ -O $GRAMPSDIR/gramps.py "$@"
if [ "$PYTHONPATH" = "" ]
then
export PYTHONPATH=$GRAMPSDIR:$GRAMPSPLUGINSDIR:$GRAMPSLIBDIR
else
export PYTHONPATH=$GRAMPSDIR:$GRAMPSLIBDIR:$GRAMPSPLUGINSDIR:$PYTHONPATH
fi
exec @PYTHON@ $GRAMPSDIR/gramps.py "$@"

127
gramps.spec.in Normal file
View File

@ -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

Binary file not shown.

After

Width:  |  Height:  |  Size: 45 KiB

BIN
help/C/figures/cfe-ar.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 36 KiB

BIN
help/C/figures/cfe-df.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 46 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 58 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 24 KiB

BIN
help/C/figures/edit-ad.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

BIN
help/C/figures/edit-an.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 35 KiB

BIN
help/C/figures/edit-at.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

BIN
help/C/figures/edit-bm.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

BIN
help/C/figures/edit-ev.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 35 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 50 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

Some files were not shown because too many files have changed in this diff Show More