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

Further changes

Browse Source
This commit is contained in:
Nick Hall 2021-06-01 21:14:03 +01:00
parent 274ddcd123
commit 2e1a4d0139
1 changed files with 69 additions and 79 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

60
FAQ
View File

@ -71,7 +71,7 @@ to this list, please email your suggestions to gramps-devel@lists.sf.net
27. Can I run Gramps from a database on a NFS share?
28. Why is the database format not portable?
28. Is the database format portable?
==Bugs and requests==
@ -105,24 +105,26 @@ program and source code freely.
3. Does Gramps exist in other languages?
Yes, Gramps written on English (US) language and at the moment is translated in 43 languages:
Albanian, Arabic, Bulgarian, Breton, Catalan, Chinese (Simplified), Chinese (Hong Kong), Chinese (Traditional), Croatian, Czech, Danish, Dutch, English (United Kingdom), Esperanto, Finnish, French, Gaelic (Irish), German, Greek, Hebrew, Hungarian, Icelandic, Italian, Japanese, Lithuanian, Macedonian, Norwegian (Bokmål), Norwegian (Nynorsk), Polish, Portuguese (Brazil), Portuguese (Portugal), Romanian, Russian, Serbian, Serbian (Latin), Slovak, Slovenian, Spanish, Swedish, Tamil, Turkish, Ukrainian, Vietnamese.
Yes. Although developed in English, Gramps is actively translated into dozens
of languages including: Catalan, Chinese, Croatian, Czech, Danish, Dutch,
Esperanto, Finnish, French, German, Greek, Hebrew, Hungarian, Icelandic,
Italian, Japanese, Lithuanian, Norwegian, Portuguese, Russian, Serbian,
Slovak, Slovenian, Spanish, Swedish, Ukrainian and Vietnamese.
Note: See https://www.gramps-project.org/wiki/index.php/Template:Gramps_translations for more information.
4. How do I keep backups?
Use a recent version of Gramps! From 2.2.5 onwards there is an automatic backup utility.
Use a recent version of Gramps! From 5.0.0 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->Preferences->Family Tree menu), Gramps will keep a backup of your database on exit or on shedule (every 15 minutes, 30 minutes, 1 hour, 12 hours, or 1 day). You can copy this backup file from time to time to a save location (e.g. a USB stick).
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 Gramps support Unicode fonts? In particular, does it support non-Roman Unicode fonts?
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.
Note: For use genealogic symbols you must have FreeSerif or DejaVu Sans fonts (or other) installed.
Note: To use genealogical symbols you must install a font that provides the miscellaneous symbols in the unicode range 2600-26FF.
==Installation==
@ -267,7 +269,7 @@ If you are happy with your plugin and would like to contribute your code back to
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.
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. 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?
@ -277,7 +279,7 @@ See above. Again, this is dependent on how much memory you have, see [Gramps Per
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 file format used is .grdb which means Gramps database.
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.
27. Can I run Gramps from a database on a NFS share?
@ -285,48 +287,36 @@ Starting with 2.0.0 release, Gramps no longer loads all data into memory, which
Yes you can.
28. Why is the database format not portable?
28. Is the database format 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.
Prior to 5.0, Gramps used BSDDB as its database backend. The BSDDB database
format is not portable.
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.
Starting with 5.0, Gramps allowed the user to choose from other datbase
backends, including SqLite. The SqLite database format is portable.
As of 5.2, the BSDDB backend is no longer available. SqLite is used by default.
==Bugs and requests==
29. 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 :-)
The best thing you can do is to fix the bug and submit a pull request on
GitHub :-)
The next best thing would be to submit a good bug report. This can be done in
one of the two ways:
(1) send your report to gramps-bugs@lists.sf.net
or
(2) file your report with the bug tracker system at
The next best thing would be to submit a good bug report. This can be done by
filing your report with the bug tracker system at
https://gramps-project.org/bugs/ (this function is also
available by selecting "Help->Report a bug" from Gramps main menu).
You may also discuss the problem first on our mailing list or Discourse forum.
https://gramps-project.org/blog/contact
A good bug report would include:
(1) Version of Gramps you were using when you encountered the bug
(available through Help->About menu item)
(2) Language under which Gramps was run
(available by executing "echo $LANG" in your terminal)
(also available through Help->About menu item)
(3) Symptoms indicating that this is indeed a bug
(4) Any Traceback messages, error messages, warnings, etc, that showed up
in your terminal or a in separate traceback window
@ -335,7 +325,7 @@ Most problems can be fixed quickly provided there is enough information.
To ensure this, please follow up on your bug reports.
If the above explanations seem vague, please follow this link:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
30. Gramps should be a .... type of application