https://www.gramps-project.org/wiki/api.php?action=feedcontributions&user=Cedeel&feedformat=atom
Gramps - User contributions [en]
2024-03-28T13:23:22Z
User contributions
MediaWiki 1.31.3
https://www.gramps-project.org/wiki/index.php?title=Baptise_record&diff=62175
Baptise record
2016-09-27T22:08:08Z
<p>Cedeel: /* Examples */ Capitalization and slight rewording.</p>
<hr />
<div>{{languages|Baptise_record}}<br />
<br />
Baptism records are an important source of genealogical information. In many countries, churches were the only institutions keeping records of baptisms, and hence of births. <br />
<br />
== The baptism record == <br />
This record is normally a very short piece of text. However, important information can be learned from it: name of child, date of baptism, date of birth, parents' names, witnesses names, place of residence. Furthermore, from the signatures one can determine that the parents/witnesses had basic schooling. <br />
<br />
== Through history ==<br />
===Catholic Church===<br />
The Catholic Church started to keep registries for the sacraments of baptism, marriage and burial. This started in the 14th century in Italy and France. The oldest known registries are kept in the city of Geiry (France) and date back to 1334. <br />
<br />
The Catholic Church decided during the Council of Trente on November 11, 1563 on the rules concerning the keeping of parish registries for baptisms and marriages. Since 1614 burial records also became obligatory. These dates are hence the earliest dates one can realistically attempt to obtain in the creation of a family tree.<br />
<br />
Note that the introduction of a civil office occurs in general in the period following the French Revolution. These documents, [[birth certificate]]s, are in general more easy to track than baptism records.<br />
<br />
== Examples ==<br />
=== Belgium, 1748 ===<br />
[[Image:Birthcert-1748-belgium.png|thumb]]<br />
The image to the left is a baptism certificate from 1748, found in a parish registry of a parish near Ghent, Belgium. The Latin text reads roughly:<br />
<br />
:<code>10 jan bap(tizavi) adrianuam jacobam f(ili)am adriani van poeke et isabelle raeman conj(ugum) natam hodie 3 pom(eridiana):susc(eptores):Jacobus De geest et Adriana Meirlaens. J.B. van Hecke, vicep(astor)</code><br />
<br />
Its English translation is:<br />
:<code>10 January I baptised Adriana Jacoba, daughter of Andreas van Poecke and Isabella Raeman, married couple, born today at 3 PM, godparents are Jacobus de Geest and Adriana Meirlaens. J.B. van Hecke, vice pastor.</code><br />
<br />
Furthermore, the top of the page in the registry lists 1748.<br />
<br />
From these few lines of text, a lot of information is available:<br />
* The repository where the source is found<br />
* The source where this record is located<br />
* The page/number of the entry (if present), and the effective text (in original language and translated)<br />
* Father's name <br />
* Mother's name<br />
* Child's name<br />
* Date of baptism (and parish where it is performed)<br />
* Date and hour of birth (place of birth can sometimes be inferred)<br />
* Names of two godparents<br />
* Name of priest<br />
<br />
{{languages|Baptise_record}}<br />
[[Category:Sources]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Sources_in_Gramps&diff=62174
Sources in Gramps
2016-09-27T20:36:26Z
<p>Cedeel: /* Introduction */ Formatting for readability.</p>
<hr />
<div>{{languages|Sources in Gramps}}<br />
[[Sources]] are important, multiple and can be shared. They are often shared between events. They may also be grouped under a [[Repositories in Gramps|repository]] (archive, library, folder, etc...). They can also have multiple [[citations]].<br />
<br />
Gramps gives us a lot of freedom for classification. This is not necessarily an advantage. How then should you go about adding sources and using the power of Gramps?<br />
<br />
== Introduction ==<br />
<br />
Classification of events, sources and repositories is related to the GEDCOM format. See the specification:<br />
<br />
*;EVEN (Event) : A noteworthy happening related to an individual, a group, or an organization.<br />
**;DATE (Date) : The time in a calendar format.<br />
**;PAGE (Page) : A number or description to identify where information can be found in a referenced work.<br />
**;QUAY (Quality of Data) : An assessment of the certainty of the evidence to support the conclusion drawn from evidence.<br />
**;NOTE (Note) : Additional information provided by the submitter for understanding the enclosing data.<br />
<br />
*;SOUR (Source) : The initial or original material from which information was obtained.<br />
**;TITL (Title) : A description of a specific writing or other work, such as the title of a book when used in a source context, or a formal designation used by an individual in connection with positions of royalty or other social status, such as Grand Duke.<br />
**;AUTH (Author) : The name of the individual who created or compiled information.<br />
**;ABBR (Abbreviation) : A short name of a title, description, or name.<br />
**;PUBL (Publication) : Refers to when and/or where a work was published or created.<br />
**;TEXT (Text) : The exact wording found in an original source document.<br />
**;DATA (Data) : Pertaining to stored automated information.<br />
<br />
*;REPO (Repository) : An institution or person that has the specified item as part of their collection(s).<br />
**;MEDI (Media) : Identifies information about the media or having to do with the medium in which information is stored.<br />
**;CALN (Call Number) : The number used by a repository to identify a specific item in its collection.<br />
**;NOTE (Note) : Additional information provided by the submitter for understanding the enclosing data.<br />
<br />
==An Example==<br />
===The data===<br />
A death certificate dated 1809-05-13, stored at the Country Archives of New York, with call-number: 6Mi5202, for Miss X who died on the previous day.<br />
<br />
===One possibility for the entries===<br />
# We enter the details in the event field : ''Death - 1809-05-12 - New-York, NY, USA''<br />
# We add a source : ''Death certificate of X (died on 1809-05-12)''<br />
# related to a [[Repositories in Gramps|repository]] : ''Country Archives of New-York - call number: 6Mi5202''<br />
# We check the entries.<br />
# We may also add a date (''1809-05-13''), volume, page number and the reliability of the source. This information is specific to the way this event (''Death of Miss X'') is recorded in this source and is not part of the general information about the source. It is the citation data, which appears in '''Detailed reports''' as '''EndNotes'''.<br />
<br />
[[Category:Gramps terminology]]<br />
[[Category:Translators/Categories]]<br />
[[Category:Sources]]<br />
[[Category:Tutorials]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Citation_examples:Birth,_marriage_and_death_certificates&diff=62173
Citation examples:Birth, marriage and death certificates
2016-09-27T19:55:05Z
<p>Cedeel: </p>
<hr />
<div>The following has to be adjusted to the concrete requirements of the certificate system in use; the content here is based on [http://sourceforge.net/p/gramps/mailman/message/32407000/ this discussion]([http://gramps.1791082.n4.nabble.com/Source-and-citation-with-single-certificates-and-family-register-books-best-practice-td4666052.html Nabble link]) on the Gramps user mailing list.<br />
<br />
It is assumed that the respective birth, marriage or death certificate were issued by some kind of civil registry office and this office keeps their records collected in real books or drawers or whatever technology was used in the past. Thus, this collection acts as the Source with the registry office in the author field. Here, the latter carries the important piece of information. Note that currently grouping sources by author does not display nice in Gramps, and other sites often group sources by title. Therefore, it might be advisable to enter the registry office also in the title field leaving the author field empty. Furthermore, the Gramps repository mechanism can be used to store where the records are available. Please evaluate whether this is worthwhile because archives tend to reorganize often.<br />
<br />
The Citation represents the concrete certificate. Here, the Volume/Page field should include either the page, number or comparable characteristics of the certificate, or the specific name of the certificate. In the latter case, the former mentioned items could be entered in the Data section of the Citation.<br />
<br />
[[Category:Citation Examples]]<br />
[[Category:Documentation]]<br />
[[Category:Sources]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Import_from_another_genealogy_program&diff=62172
Import from another genealogy program
2016-09-27T19:27:17Z
<p>Cedeel: /* Import instructions from different programs */ Various readability improvements.</p>
<hr />
<div>{{Languages}}<br />
There are several ways to import your family tree into Gramps from another program. The best way depends on what program you want to copy the information from.<br />
<br />
== Gramps to Gramps==<br />
<br />
This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy filter.<br />
<br />
Copy the file created by Gramps to the destination computer. Then in its Gramps, choose {{man menu|Family Trees -> Import}} and select the transferred file.<br />
<br />
== Standard GEDCOM as transfer tool==<br />
<br />
Most programs for family history can export and import [[GEDCOM]] (.ged) files. <br />
<br />
# Check the documentation for your program to learn how to create a GEDCOM file with all your data. <br />
#* If you have a choice, GEDCOM 5.5 Standard is usually the safest type of GEDCOM.<br />
# In Gramps, choose the '''Family Trees''' icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}, to open the Family Tree Manager. Create a new family tree, choose a name, and click on the {{man button|Load Family Tree}} button to open.<br />
# Now that a family tree is loaded, select {{man menu|Family Trees -> Import}} from the menu.<br />
# Locate the GEDCOM file created by your program, and select {{man button|Open}}.<br />
<br />
{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}<br />
<br />
Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}, with which you can change the path of your media objects to the new path if needed.<br />
<br />
== Spreadsheet import ==<br />
<br />
Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps. <br />
<br />
The CSV import option currently doesn't allow import of all Gramps data. <br />
<br />
For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages. <br />
<br />
For more details on this format see [[Gramps 4.2 Wiki Manual - Manage Family Trees: CSV Import and Export]].<br />
<br />
== Addon ==<br />
<br />
[[GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.<br />
<br />
== Import instructions for different programs ==<br />
<br />
=== Ancestrologie ===<br />
<br />
Ancestrologie seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps. <br />
<br />
==== Programs for fixing some of the known problems ====<br />
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.<br />
<br />
; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.<br />
<br />
; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.<br />
<br />
; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:<br />
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111<br />
<br />
The data (in this case 75111) may be absent or extend to CONT lines.<br />
The non-standard elements converted to APPX notes include:<br />
<br />
; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"<br />
; _ANCES_ORDRE : Considered non-critical, events classification <br />
; _ANCES_XACTE : Non-critical (certificat found = 1)<br />
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')<br />
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record<br />
; EVEN I : (Same)<br />
; LIEU : A subdivision of place, is not our place but a division<br />
; XTYPE : These seem to be OBJE subordinates<br />
; XIDEN : Considered non-critical, media object used for primary media (photo)<br />
; XMODE : (file is not present at the FILE address)<br />
<br />
In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.<br />
<br />
1 FILA Enfant légitime <br />
<br />
becomes<br />
<br />
1 FACT Enfant légitime<br />
2 TYPE FILA<br />
<br />
'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''<br />
<br />
'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''<br />
<br />
=== Ancestry.com ===<br />
<br />
{{Out_of_date}}<br />
<br />
GEDCOM produced by Ancestry.com is not fully readable by Gramps 2.0.x and 2.2.x (Relationship lost).<br />
This is Bug#{{bug|899}}'':fixed for 3.0''. Also, you can use {{bug|899}}:'''grampify.pl''' for fixing broken GEDCOM generated by Ancestry.com.<br />
<br />
=== Evidentia ===<br />
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [http://www.bcgcertification.org/resources/standard.html Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.<br />
<br />
==== General tips ====<br />
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.<br />
<br />
==== People ====<br />
===== Import into Evidentia as subjects =====<br />
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option. <br />
<br />
===== What Evidentia imports and exports =====<br />
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:<br />
<br />
; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia<br />
; NAME Lakshmi /Wolowitz/ : Full name<br />
; GIVN Lakshmi : Given name)<br />
; SURN Wolowitz : Surname<br />
; SEX F : Gender<br />
; BIRT : Birth year<br />
<br />
==== Events and facts ====<br />
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.<br />
<br />
===== Manually add facts into Evidentia =====<br />
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.<br />
<br />
===== Export some types of facts to Gramps =====<br />
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM. <br />
<br />
==== Sources and Citations ====<br />
===== Manually add to Evidentia first =====<br />
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.<br />
<br />
There are two reasons to follow this workflow:<br />
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice. <br />
<br />
* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!<br />
<br />
===== Match your source title and source abbreviation =====<br />
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.<br />
<br />
===== Complete publication information exported =====<br />
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.<br />
<br />
===== Citation title only used in Evidentia =====<br />
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.<br />
<br />
==== Claims and proof ====<br />
===== Default GEDCOM export =====<br />
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:<br />
<br />
* Individual information: id, name, gender<br />
* Claim type: facts, events, or attributes<br />
* Source information: title, abbreviation, and full publication info (PUBL)<br />
* Full citation (PAGE)<br />
<br />
If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.<br />
<br />
===== Evidentia-specific GEDCOM export =====<br />
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).<br />
<br />
If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:<br />
<br />
* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840. <br />
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."<br />
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."<br />
<br />
=== Family Tree Maker ===<br />
<br />
GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].<br />
<br />
==== If you do not have access to Family Tree Maker ====<br />
(Tested with FTW file created by Family Tree Maker 2006)<br />
* Download and install the free MyHeritage Family Tree Builder:<br />
http://www.myheritage.com/family-tree-builder<br />
* Create a new account (with bogus data)<br />
* Disable any syncing features when asked<br />
* Create new Project: File > New Project...<br />
* File > Import GEDCOM... > Browse > Select FTW file<br />
* File > Export GEDCOM...<br />
<br />
==== Family Tree Maker 2005 ====<br />
<br />
Select File -> Export File -> Entire File...<br />
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.<br />
In the "Export to GEDCOM" dialog, set the following:<br />
* Destination: FTM<br />
* GEDCOM: Version 5.5<br />
* Character set: ANSI (Gramps will convert to UTF-8 upon import)<br />
* Deselect "Indent records"<br />
* Select "Abbreviate tags"<br />
<br />
Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.<br />
<br />
{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}<br />
<br />
==== Known issues or custom extensions ====<br />
<br />
# Blank lines<br />
# Issues on date string<br />
# PHON in INDI records<br />
# PLAC for general data<br />
# The source quality is coded as a NOTE rather as QUAY<br />
# Marriage start status<br />
# Double dates use the first date rather than the second<br />
<br />
==== Programs for fixing some of the known problems ====<br />
<br />
; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.<br />
<br />
====Experimental way====<br />
<br />
[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.<br />
<br />
[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.<br />
<br />
=== Geneweb ===<br />
<br />
Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.<br />
<br />
=== GenoPro ===<br />
<br />
==== Gedcom ====<br />
<br />
GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].<br />
<br />
==== GenoPro to Gramps ====<br />
<br />
Experimental converter (.gno to .gramps) on {{bug|2757}}.<br />
<br />
=== Heredis ===<br />
<br />
'''Modifications of GEDCOM from Heredis to import in Gramps'''<br />
<br />
''With editor (like gedit ot note++) find and replace '''« > »''':''<br />
<br />
<br />
<br />
'''1. Non standard tags of Heredis'''<br />
<br />
'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...<br />
<br />
<br />
1 _FIL LEGITIMATE_CHILD > suppress all lines<br />
<br />
1 _UST MARRIED > suppress all lines<br />
<br />
1 RESN privacy > suppress all lines<br />
<br />
NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)<br />
<br />
<br />
'''2. Assign value Y to following to tags'''<br />
<br />
1 BIRT > 1 BIRT Y<br />
<br />
1 DEAT > 1 DEAT Y<br />
<br />
1 MARR > 1 MARR Y<br />
<br />
1 MARC > 1 MARC Y<br />
<br />
1 DIV > 1 DIV Y<br />
<br />
1 CHR > 1 CHR Y<br />
<br />
1 ... > 1 ... Y<br />
<br />
<br />
''<br />
'''3. Sources and Repositories''' <br />
<br />
<br />
1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''<br />
<br />
'''3 MEDI > 1 MEDI or 1 PUBL'''<br />
<br />
_ARCH > AUTH<br />
<br />
<br />
'''4. Change levels in Associations'''<br />
<br />
2 ASSO @398195I@ > 1 ASSO@398195I@<br />
<br />
3 TYPE INDI > suppress all lines<br />
<br />
3 RELA > 2 RELA <br />
<br />
3 TITL > 2 TITL <br />
<br />
3 NOTE XXX > 2 NOTE XXX If a note is associated<br />
<br />
<br />
'''5. Équivalents of disks drives when loaded Linux Gramps'''<br />
<br />
FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/<br />
<br />
FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/<br />
<br />
<br />
'''6. For people's tags located in Events instead of Attributes'''<br />
<br />
Description Type<br />
<br />
Profession > Occupation<br />
<br />
Titre > Nobility title<br />
<br />
No (signe) > null<br />
<br />
YES (end of line) > null<br />
<br />
There would be a way to assign some fields in attributes instead of events. It's a mix up.<br />
<br />
''Ifs, Oct 25 2011''<br />
<br />
====Known issues==== <br />
<br />
According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :<br />
<br />
# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.<br />
# Not properly manage dates (calendars)<br />
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.<br />
# Not properly manage sources and repositories<br />
<br />
There are some alternatives to GEDCOM generated by Heredis :<br />
<br />
* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].<br />
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].<br />
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].<br />
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!<br />
<br />
=== Legacy ===<br />
<br />
According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :<br />
<br />
# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.<br />
# ignore SOURCE_REPOSITORY_CITATION.<br />
# modify MEDI tag design, which can be used into CALN.<br />
<br />
=== Pro-Gen ===<br />
<br />
Using GEDCOM to export data from Pro-Gen is less than ideal. Therefor a plugin was created. <br />
The plugin is included in the Gramps distribution.<br />
<br />
To import the data Gramps needs to be able to see the Pro-Gen directory tree. This all depends on your own setup. One possibility is to ZIP everything on your DOS computer and unZIP it on your Linux PC in, say ~/pg30. You may even be running Gramps on a Windows PC and have a copy Pro-Gen on that same computer. In the following steps, we're assuming the Pro-Gen files are at ~/pg30<br />
<br />
Import the data:<br />
* start gramps<br />
* create a new family database<br />
* select that new database<br />
* go to menu {{man menu|Family Trees-> Import}}<br />
* in the file dialog go to the ~/pg30/nl/data directory<br />
* select the .DEF of your Pro-Gen database<br />
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)<br />
* click "Import"<br />
* wait ...<br />
<br />
=== The Master Genealogist (TMG) ===<br />
<br />
You have two options.<br />
<br />
==== GEDCOM ====<br />
<br />
This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you. <br />
<br />
Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]<br />
<br />
Then with that in mind:<br />
<br />
# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG. <br />
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.<br />
#* Write down which choices you make.<br />
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].<br />
<br />
If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you? <br />
<br />
Keep trying and hopefully you'll hit on the combination that works best for you.<br />
<br />
If you can't get good results, you'll have to use the tmg2gramps method instead.<br />
<br />
===== Known issues =====<br />
<br />
Using a GEDCOM export from TMG does not transfer the following information:<br />
<br />
See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]<br />
<br />
==== tmg2gramps ====<br />
<br />
For many people, using GEDCOM will lose too much information, most notably "Witness" information.<br />
<br />
If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.<br />
<br />
For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.<br />
<br />
You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].<br />
<br />
tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.<br />
<br />
{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}<br />
<br />
===== Data tmg2gramps successfully converts =====<br />
<br />
Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:<br />
<br />
*"Witness" information.<br />
<br />
*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.<br />
<br />
*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.<br />
<br />
*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.<br />
<br />
===== Known issues =====<br />
<br />
Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:<br />
<br />
# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth &mdash; so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).<br />
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.<br />
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" &mdash; this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.<br />
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.<br />
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children &mdash; the "Disconnected individual" count is at zero &mdash; this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" &mdash; hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated &mdash; you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.<br />
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_4.1_Wiki_Manual_-_Tools#Media_Manager... |Gramps Media Manager]].<br />
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" &mdash; a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.<br />
<br />
===== Preparing to run tmg2gramps =====<br />
<br />
Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.<br />
<br />
====== Copy your TMG projects folder ======<br />
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:<br />
<br />
<code>C:\Program Files\The Master Genealogist\projects</code><br />
<br />
====== Rename your copied TMG projects folder ======<br />
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'<br />
<br />
====== Convert TMG filenames to lowercase ======<br />
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:<br />
<br />
<code>$ rename 'y/A-Z/a-z/' *</code><br />
<br />
====== Prepare MySQL ======<br />
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:<br />
<br />
<code>$ sudo apt-get install mysql-server</code><br />
<br />
That will either install MySQL, or if it is already installed, it won't cause any harm.<br />
<br />
The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:<br />
<br />
<code>$ sudo apt-get install libdbd-xbase-perl</code><br />
<br />
Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:<br />
<br />
<code>$ mysql -u root</code><br />
<br />
If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:<br />
<br />
<code>$ mysql -u root -p</code><br />
<br />
You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:<br />
<br />
<code>mysql> show databases;</code><br />
<br />
That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:<br />
<br />
<code>mysql> create database tmg_gramps;</code><br />
<br />
Now, make sure that you can connect to the database with the appropriate password and privileges by typing:<br />
<br />
<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code><br />
<br />
You can now exit MySQL:<br />
<br />
<code>mysql> exit</code><br />
<br />
====== Preparation for the tmg2gramps script ======<br />
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:<br />
<br />
<code>$ ls -l</code><br />
<br />
This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:<br />
<br />
<pre><br />
smith__.acc<br />
smith__.pjc<br />
smith_$.cdx<br />
....<br />
</pre><br />
<br />
...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.<br />
<br />
And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:<br />
<br />
<code>$ chmod +x tmg2gramps.pl</code><br />
<br />
Now, it is finally time to run tmg2gramps and convert your data.<br />
<br />
===== Running tmg2gramps =====<br />
<br />
When running tmg2gramps, the example below makes the following assumptions:<br />
<br />
* Name of TMG project: '''''<code>smith</code>'''''<br />
* Home directory: /home/'''''<code>asmith</code>'''''<br />
<br />
Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):<br />
<br />
$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass<br />
<br />
You should now be able to watch tmg2gramps running in terminal.<br />
<br />
The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.<br />
<br />
When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.<br />
<br />
You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:<br />
<br />
$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps<br />
<br />
Open Gramps, create a new family tree, and import the .gramps file you just created.<br />
<br />
Congratulations! Your TMG data is now in Gramps.<br />
<br />
{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://homepage.ntlworld.com/hamamelis/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}<br />
<br />
==== TMG-Working-Group ====<br />
<br />
Information only at the moment.<br />
<br />
'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''<br />
<br />
https://github.com/girimonti/TMG-Working-Group<br />
<br />
==== tmgviewer ====<br />
<br />
An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge). <br />
* [[Addon:TMGimporter]] - WIP - Not released yet.<br />
<br />
See {{bug|7591}} for more details and tests.<br />
<br />
=== Visuged ===<br />
<br />
According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !<br />
<br />
# Partial sources<br />
# Repositories are lost<br />
# BAPT, ASSO are lost<br />
# Internal numbers are modified<br />
<br />
== See also ==<br />
* [[Other genealogy tools]]<br />
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]<br />
<br />
[[Category:How do I...]]<br />
[[Category:Developers/General]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Import_from_another_genealogy_program&diff=62171
Import from another genealogy program
2016-09-27T18:32:55Z
<p>Cedeel: /* Standard GEDCOM as transfer tool */ Added spaces around arrow for consistency and readability. Reworded slightly.</p>
<hr />
<div>{{Languages}}<br />
There are several ways to import your family tree into Gramps from another program. The best way depends on what program you want to copy the information from.<br />
<br />
== Gramps to Gramps==<br />
<br />
This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy filter.<br />
<br />
Copy the file created by Gramps to the destination computer. Then in its Gramps, choose {{man menu|Family Trees -> Import}} and select the transferred file.<br />
<br />
== Standard GEDCOM as transfer tool==<br />
<br />
Most programs for family history can export and import [[GEDCOM]] (.ged) files. <br />
<br />
# Check the documentation for your program to learn how to create a GEDCOM file with all your data. <br />
#* If you have a choice, GEDCOM 5.5 Standard is usually the safest type of GEDCOM.<br />
# In Gramps, choose the '''Family Trees''' icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}, to open the Family Tree Manager. Create a new family tree, choose a name, and click on the {{man button|Load Family Tree}} button to open.<br />
# Now that a family tree is loaded, select {{man menu|Family Trees -> Import}} from the menu.<br />
# Locate the GEDCOM file created by your program, and select {{man button|Open}}.<br />
<br />
{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}<br />
<br />
Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}, with which you can change the path of your media objects to the new path if needed.<br />
<br />
== Spreadsheet import ==<br />
<br />
Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps. <br />
<br />
The CSV import option currently doesn't allow import of all Gramps data. <br />
<br />
For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages. <br />
<br />
For more details on this format see [[Gramps 4.2 Wiki Manual - Manage Family Trees: CSV Import and Export]].<br />
<br />
== Addon ==<br />
<br />
[[GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.<br />
<br />
== Import instructions from different programs ==<br />
<br />
=== Ancestrologie ===<br />
<br />
Ancestrologie seems to produce non-standard gedcom for some kinds of data. In general such problems should be repaired prior to importing into Gramps. <br />
<br />
==== Programs for fixing some of the known problems ====<br />
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.<br />
<br />
* [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] .. script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.<br />
<br />
* [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] .. script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.<br />
<br />
* [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] .. script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:<br />
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111<br />
<br />
The data (in this case 75111) may be absent or extend to CONT lines.<br />
The non-standard elements converted to APPX notes include:<br />
* _ANCES_CLE_FIXE .. special internal reference : "Who they are ?"<br />
* _ANCES_ORDRE .. considered non-critical, events classification <br />
* _ANCES_XACTE .. non-critical (certificat found = 1)<br />
* _ANCES_XINSEE .. INSEE geographical code (evidently ''simplified 5-digit'')<br />
* EVEN F .. invalid EVENTS_RECORDED format in a SOUR record<br />
* EVEN I .. (same)<br />
* LIEU .. a subdivision of place, is not our place but a division<br />
* XTYPE .. these seem to be OBJE subordinates<br />
* XIDEN .. considered non-critical, media object used for primary media (photo)<br />
* XMODE .. " (file is not present at the FILE address)<br />
<br />
In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.<br />
<br />
1 FILA Enfant légitime <br />
becomes<br />
1 FACT Enfant légitime<br />
2 TYPE FILA<br />
<br />
'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''<br />
<br />
'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''<br />
<br />
=== Ancestry.com ===<br />
<br />
{{Out_of_date}}<br />
<br />
GEDCOM produced by Ancestry.com is not fully readable by Gramps 2.0.x and 2.2.x (Relationship lost).<br />
This is Bug#{{bug|899}}'':fixed for 3.0''. Also, you can use {{bug|899}}:'''grampify.pl''' for fixing broken GEDCOM generated by Ancestry.com.<br />
<br />
=== Evidentia ===<br />
If you do source- and evidence-based genealogy research, you might use this (purchaseable) program to help you follow the [http://www.bcgcertification.org/resources/standard.html Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.<br />
<br />
====General Tips====<br />
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.<br />
<br />
====People====<br />
=====IMPORT INTO Evidentia as Subjects=====<br />
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option. <br />
<br />
=====What Evidentia IMPORTS and EXPORTS=====<br />
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can IMPORT and EXPORT these basic GEDCOM fields about a Person:<br />
* @I0000@ INDI (person's ID number, called a "Reference number" in Evidentia)<br />
* NAME Lakshmi /Wolowitz/ (full name)<br />
* GIVN Lakshmi (given or first name)<br />
* SURN Wolowitz (surname or last name)<br />
* SEX F (gender)<br />
* BIRT (birth year)<br />
<br />
====Events and Facts====<br />
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.<br />
<br />
=====Manually add Facts INTO Evidentia=====<br />
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.<br />
<br />
=====EXPORT some types of Facts to Gramps=====<br />
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM. <br />
<br />
====Sources & Citations====<br />
=====Manually add to Evidentia FIRST=====<br />
Enter your Sources and Citations into Evidentia FIRST. Only after you've finished creating your proofs in Evidentia should you then import your Source Citations into Gramps.<br />
<br />
There are two reasons to follow this workflow:<br />
* First, Evidentia currently has no way to import your Sources or Citations, so entering here first means you don't have to enter them twice. <br />
<br />
* Second, Evidentia makes it easier to use the 170 source citation TEMPLATES from Elizabeth Shown Mills, so your sources and citations will be properly formatted!<br />
<br />
=====Match your Source Title and Source Abbreviation =====<br />
When a Source is exported FROM Evidentia, it uses the "Source Title" for BOTH the Title (TITL) AND the Abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the SAME text in both of these fields, as well as in both programs.<br />
<br />
=====Complete Publication information Exported =====<br />
Evidentia exports a FULL and complete reference listing (PUBL) for each Source, which includes the Title. So you might want to exclude the Title of Sources from the Complete Individual Report in Gramps to avoid duplication.<br />
<br />
=====Citation Title only used in Evidentia=====<br />
Citation Titles are only used within the Evidentia program, and don't effect gramps. So, choose whatever pattern you like for naming them.<br />
<br />
====Claims & Proof====<br />
===== Default GEDCOM export =====<br />
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:<br />
* individual information: id, name, gender<br />
* claim type: facts, events, or attributes<br />
* source information: title, abbreviation, and full publication info (PUBL)<br />
* full citation (PAGE)<br />
<br />
If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.<br />
<br />
===== Evidentia-specific GEDCOM export =====<br />
Evidentia's GEDCOM export does NOT include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).<br />
<br />
If you DO use Evidentia's recommended export settings, the claim analysis will be added as a Note to the Citation, and the Proof conclusion will be added as a Note to the Event/Fact. For example:<br />
* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840. <br />
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."<br />
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."<br />
<br />
=== Family Tree Maker (FTM)===<br />
<br />
GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].<br />
<br />
====If you do not have access to Family Tree Maker:====<br />
(Tested with FTW file created by Family Tree Maker 2006)<br />
* Download and install the free MyHeritage Family Tree Builder:<br />
http://www.myheritage.com/family-tree-builder<br />
* Create a new account (with bogus data)<br />
* Disable any syncing features when asked<br />
* Create new Project: File > New Project...<br />
* File > Import GEDCOM... > Browse > Select FTW file<br />
* File > Export GEDCOM...<br />
<br />
====Specific instructions for FTM2005:====<br />
<br />
Select File->Export File->Entire File...<br />
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.<br />
In the "Export to GEDCOM" dialog, set the following:<br />
* Destination: FTM<br />
* GEDCOM: Version 5.5<br />
* Character set: ANSI (Gramps will convert to UTF-8 upon import)<br />
* Deselect "Indent records"<br />
* Select "Abbreviate tags"<br />
<br />
Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Hit F2. This lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Hitting F2 again will bring up the list at the point where you left off.<br />
<br />
{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}<br />
<br />
==== Known issues or custom extensions ====<br />
<br />
# Blank lines<br />
# Issues on date string<br />
# PHON in INDI records<br />
# PLAC for general data<br />
# The source quality is coded as a NOTE rather as QUAY<br />
# Marriage start status<br />
# Double dates use the first date rather than the second<br />
<br />
====Programs for fixing some of the known problems====<br />
<br />
* [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] is an open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.<br />
<br />
====Experimental way====<br />
<br />
[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.<br />
<br />
[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.<br />
<br />
=== Geneweb ===<br />
<br />
Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.<br />
<br />
=== GenoPro ===<br />
<br />
==== Gedcom ====<br />
<br />
GenoPro can generate custom (invalid) gedcom [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].<br />
<br />
==== GenoPro to Gramps ====<br />
<br />
Experimental converter (.gno to .gramps) on {{bug|2757}}.<br />
<br />
=== Heredis ===<br />
<br />
'''Modifications of gedcom from Heredis to import in Gramps'''<br />
<br />
''With editor (like gedit ot note++) find and replace '''« > »''':''<br />
<br />
<br />
<br />
'''1. Non standard tags of Heredis'''<br />
<br />
'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...<br />
<br />
<br />
1 _FIL LEGITIMATE_CHILD > suppress all lines<br />
<br />
1 _UST MARRIED > suppress all lines<br />
<br />
1 RESN privacy > suppress all lines<br />
<br />
NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)<br />
<br />
<br />
'''2. Assign value Y to following to tags'''<br />
<br />
1 BIRT > 1 BIRT Y<br />
<br />
1 DEAT > 1 DEAT Y<br />
<br />
1 MARR > 1 MARR Y<br />
<br />
1 MARC > 1 MARC Y<br />
<br />
1 DIV > 1 DIV Y<br />
<br />
1 CHR > 1 CHR Y<br />
<br />
1 ... > 1 ... Y<br />
<br />
<br />
''<br />
'''3. Sources and Repositories''' <br />
<br />
<br />
1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''<br />
<br />
'''3 MEDI > 1 MEDI or 1 PUBL'''<br />
<br />
_ARCH > AUTH<br />
<br />
<br />
'''4. Change levels in Associations'''<br />
<br />
2 ASSO @398195I@ > 1 ASSO@398195I@<br />
<br />
3 TYPE INDI > suppress all lines<br />
<br />
3 RELA > 2 RELA <br />
<br />
3 TITL > 2 TITL <br />
<br />
3 NOTE XXX > 2 NOTE XXX If a note is associated<br />
<br />
<br />
'''5. Équivalents of disks drives when loaded Linux Gramps'''<br />
<br />
FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/<br />
<br />
FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/<br />
<br />
<br />
'''6. For people's tags located in Events instead of Attributes'''<br />
<br />
Description Type<br />
<br />
Profession > Occupation<br />
<br />
Titre > Nobility title<br />
<br />
No (signe) > null<br />
<br />
YES (end of line) > null<br />
<br />
There would be a way to assign some fields in attributes instead of events. It's a mix up.<br />
<br />
''Ifs, Oct 25 2011''<br />
<br />
====Known issues==== <br />
<br />
According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :<br />
<br />
# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.<br />
# Not properly manage dates (calendars)<br />
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.<br />
# Not properly manage sources and repositories<br />
<br />
There are some alternatives to GEDCOM generated by Heredis :<br />
<br />
* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].<br />
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].<br />
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].<br />
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!<br />
<br />
=== Legacy ===<br />
<br />
According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :<br />
<br />
# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.<br />
# ignore SOURCE_REPOSITORY_CITATION.<br />
# modify MEDI tag design, which can be used into CALN.<br />
<br />
=== Pro-Gen ===<br />
<br />
Using GEDCOM to export data from Pro-Gen is less than ideal. Therefor a plugin was created. <br />
The plugin is included in the Gramps distribution.<br />
<br />
To import the data Gramps needs to be able to see the Pro-Gen directory tree. This all depends on your own setup. One possibility is to ZIP everything on your DOS computer and unZIP it on your Linux PC in, say ~/pg30. You may even be running Gramps on a Windows PC and have a copy Pro-Gen on that same computer. In the following steps, we're assuming the Pro-Gen files are at ~/pg30<br />
<br />
Import the data:<br />
* start gramps<br />
* create a new family database<br />
* select that new database<br />
* go to menu {{man menu|Family Trees-> Import}}<br />
* in the file dialog go to the ~/pg30/nl/data directory<br />
* select the .DEF of your Pro-Gen database<br />
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)<br />
* click "Import"<br />
* wait ...<br />
<br />
=== The Master Genealogist (TMG) ===<br />
<br />
You have two options.<br />
<br />
==== GEDCOM ====<br />
<br />
This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you. <br />
<br />
Read this first: [http://tmg.reigelridge.com/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH(Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]<br />
<br />
Then with that in mind:<br />
<br />
# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG. <br />
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.<br />
#* Write down which choices you make.<br />
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].<br />
<br />
If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you? <br />
<br />
Keep trying and hopefully you'll hit on the combination that works best for you.<br />
<br />
If you can't get good results, you'll have to use the tmg2gramps method instead.<br />
<br />
===== Known issues =====<br />
<br />
Using a GEDCOM export from TMG does not transfer the following information:<br />
<br />
See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]<br />
<br />
==== tmg2gramps ====<br />
<br />
For many people, using GEDCOM will lose too much information, most notably "Witness" information.<br />
<br />
If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.<br />
<br />
For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.<br />
<br />
You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].<br />
<br />
tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.<br />
<br />
{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}<br />
<br />
===== Data tmg2gramps successfully converts =====<br />
Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:<br />
<br />
*"Witness" information.<br />
<br />
*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.<br />
<br />
*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.<br />
<br />
*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.<br />
<br />
===== Known issues =====<br />
Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:<br />
<br />
#Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth -- so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).<br />
#Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.<br />
#Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" -- this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.<br />
#If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.<br />
#Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children -- the "Disconnected individual" count is at zero -- this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" -- hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated -- you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.<br />
#Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_4.1_Wiki_Manual_-_Tools#Media_Manager... |Gramps Media Manager]].<br />
#Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" -- a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.<br />
<br />
===== Preparing to Run tmg2gramps =====<br />
<br />
Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.<br />
<br />
====== Copy your TMG projects folder ======<br />
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:<br />
<br />
<code>C:\Program Files\The Master Genealogist\projects</code><br />
<br />
====== Rename your copied TMG projects folder ======<br />
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'<br />
<br />
====== Convert TMG filenames to lowercase ======<br />
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:<br />
<br />
<code>$ rename 'y/A-Z/a-z/' *</code><br />
<br />
====== Prepare MySQL ======<br />
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:<br />
<br />
<code>$ sudo apt-get install mysql-server</code><br />
<br />
That will either install MySQL, or if it is already installed, it won't cause any harm.<br />
<br />
The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:<br />
<br />
<code>$ sudo apt-get install libdbd-xbase-perl</code><br />
<br />
Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:<br />
<br />
<code>$ mysql -u root</code><br />
<br />
If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:<br />
<br />
<code>$ mysql -u root -p</code><br />
<br />
You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:<br />
<br />
<code>mysql> show databases;</code><br />
<br />
That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:<br />
<br />
<code>mysql> create database tmg_gramps;</code><br />
<br />
Now, make sure that you can connect to the database with the appropriate password and privileges by typing:<br />
<br />
<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code><br />
<br />
You can now exit MySQL:<br />
<br />
<code>mysql> exit</code><br />
<br />
====== Preparation for the tmg2gramps script ======<br />
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:<br />
<br />
<code>$ ls -l</code><br />
<br />
This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:<br />
<br />
<pre><br />
smith__.acc<br />
smith__.pjc<br />
smith_$.cdx<br />
....<br />
</pre><br />
<br />
...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.<br />
<br />
And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:<br />
<br />
<code>$ chmod +x tmg2gramps.pl</code><br />
<br />
Now, it is finally time to run tmg2gramps and convert your data.<br />
<br />
===== Running tmg2gramps =====<br />
<br />
When running tmg2gramps, the example below makes the following assumptions:<br />
<br />
*name of TMG project: '''''<code>smith</code>'''''<br />
*home directory: /home/'''''<code>asmith</code>'''''<br />
<br />
Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):<br />
<br />
$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass<br />
<br />
You should now be able to watch tmg2gramps running in terminal.<br />
<br />
The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.<br />
<br />
When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.<br />
<br />
You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:<br />
<br />
$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps<br />
<br />
Open Gramps, create a new family tree, and import the .gramps file you just created.<br />
<br />
Congratulations! Your TMG data is now in Gramps.<br />
<br />
{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://homepage.ntlworld.com/hamamelis/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}<br />
<br />
==== TMG-Working-Group ====<br />
<br />
Information only at the moment.<br />
<br />
'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''<br />
<br />
https://github.com/girimonti/TMG-Working-Group<br />
<br />
==== tmgviewer ====<br />
<br />
An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge). <br />
* [[Addon:TMGimporter]] - WIP - Not released yet.<br />
<br />
See {{bug|7591}} for more details and tests.<br />
<br />
=== Visuged ===<br />
<br />
According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !<br />
<br />
# Partials sources<br />
# Repositories are lost<br />
# BAPT, ASSO are lost<br />
# Internal numbers are modified<br />
<br />
== See also ==<br />
* [[Other genealogy tools]]<br />
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]<br />
<br />
[[Category:How do I...]]<br />
[[Category:Developers/General]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Talk:GEPS_023:_Certificates&diff=48628
Talk:GEPS 023: Certificates
2014-04-07T19:20:13Z
<p>Cedeel: Fix double redirect</p>
<hr />
<div>#REDIRECT [[Talk:GEPS 024: Natural transcription of Records]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Ru:Gramps_3.4_%D0%92%D0%B8%D0%BA%D0%B8_%D0%A0%D1%83%D0%BA%D0%BE%D0%B2%D0%BE%D0%B4%D1%81%D1%82%D0%B2%D0%BE_-_%D0%A3%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5_%D0%A1%D0%B5%D0%BC%D0%B5%D0%B9%D0%BD%D1%8B%D0%BC%D0%B8_%D0%B4%D0%B5%D1%80%D0%B5%D0%B2%D1%8C%D1%8F%D0%BC%D0%B8&diff=48627
Ru:Gramps 3.4 Вики Руководство - Управление Семейными деревьями
2014-04-07T19:19:48Z
<p>Cedeel: Fix double redirect</p>
<hr />
<div>#REDIRECT [[Ru:Gramps 3.4 Вики Руководство - Управление семейными древесами]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Addon:PhotoTaggingGramplet&diff=48626
Addon:PhotoTaggingGramplet
2014-04-07T19:19:16Z
<p>Cedeel: Fix double redirect</p>
<hr />
<div>#REDIRECT [[Photo Tagging Gramplet]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Nl:Gramps_5.1_Handleiding_-_Invoeren_en_Aanpassen_Gegevens:_Kort&diff=72264
Nl:Gramps 5.1 Handleiding - Invoeren en Aanpassen Gegevens: Kort
2014-04-07T19:18:52Z
<p>Cedeel: Fix double redirect</p>
<hr />
<div>#REDIRECT [[Nl:Gramps 5.1 Wiki Handleiding - Invoeren en aanpassen gegevens: kort]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Nl:Gramps_4.0_Handleiding_-_Invoeren_en_Aanpassen_Gegevens:_Kort&diff=48625
Nl:Gramps 4.0 Handleiding - Invoeren en Aanpassen Gegevens: Kort
2014-04-07T19:18:52Z
<p>Cedeel: Fix double redirect</p>
<hr />
<div>#REDIRECT [[Nl:Gramps 4.0 Wiki Handleiding - Invoeren en aanpassen gegevens: kort]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Nl:Gramps_4.1_Handleiding_-_Invoeren_en_Aanpassen_Gegevens:_Kort&diff=49108
Nl:Gramps 4.1 Handleiding - Invoeren en Aanpassen Gegevens: Kort
2014-04-07T19:18:52Z
<p>Cedeel: Fix double redirect</p>
<hr />
<div>#REDIRECT [[Nl:Gramps 4.1 Wiki Handleiding - Invoeren en aanpassen gegevens: kort]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Nl:Gramps_4.2_Handleiding_-_Invoeren_en_Aanpassen_Gegevens:_Kort&diff=56499
Nl:Gramps 4.2 Handleiding - Invoeren en Aanpassen Gegevens: Kort
2014-04-07T19:18:52Z
<p>Cedeel: Fix double redirect</p>
<hr />
<div>#REDIRECT [[Nl:Gramps 4.2 Wiki Handleiding - Invoeren en aanpassen gegevens: kort]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Nl:Gramps_5.0_Handleiding_-_Invoeren_en_Aanpassen_Gegevens:_Kort&diff=64255
Nl:Gramps 5.0 Handleiding - Invoeren en Aanpassen Gegevens: Kort
2014-04-07T19:18:52Z
<p>Cedeel: Fix double redirect</p>
<hr />
<div>#REDIRECT [[Nl:Gramps 5.0 Wiki Handleiding - Invoeren en aanpassen gegevens: kort]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=GRAMPS_User_Directory/fr&diff=48624
GRAMPS User Directory/fr
2014-04-07T19:18:05Z
<p>Cedeel: Fix double redirect</p>
<hr />
<div>#REDIRECT [[Gramps 4.0 Wiki Manual - Répertoire utilisateur]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=R%C3%A9pertoire_utilisateur_de_Gramps&diff=48623
Répertoire utilisateur de Gramps
2014-04-07T19:17:41Z
<p>Cedeel: Fix double redirect</p>
<hr />
<div>#REDIRECT [[Gramps 4.0 Wiki Manual - Répertoire utilisateur]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=GEPS_023:_Certificates&diff=48621
GEPS 023: Certificates
2014-04-07T19:16:20Z
<p>Cedeel: Fix double redirect</p>
<hr />
<div>#REDIRECT [[GEPS 024: Natural transcription of Records]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Gramps_4.0_Wiki_Manual_-_Cat%C3%A9gories/fr&diff=48620
Gramps 4.0 Wiki Manual - Catégories/fr
2014-04-07T19:15:28Z
<p>Cedeel: Remove double redirect</p>
<hr />
<div>#REDIRECT [[Fr:Manuel wiki pour Gramps 4.0 - Catégories]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Gramps_4.1_Wiki_Manual_-_Cat%C3%A9gories/fr&diff=48797
Gramps 4.1 Wiki Manual - Catégories/fr
2014-04-07T19:15:28Z
<p>Cedeel: Remove double redirect</p>
<hr />
<div>#REDIRECT [[Fr:Manuel wiki pour Gramps 4.1 - Catégories]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Gramps_4.2_Wiki_Manual_-_Cat%C3%A9gories/fr&diff=56182
Gramps 4.2 Wiki Manual - Catégories/fr
2014-04-07T19:15:28Z
<p>Cedeel: Remove double redirect</p>
<hr />
<div>#REDIRECT [[Fr:Manuel wiki pour Gramps 4.2 - Catégories]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Gramps_5.0_Wiki_Manual_-_Cat%C3%A9gories/fr&diff=63951
Gramps 5.0 Wiki Manual - Catégories/fr
2014-04-07T19:15:28Z
<p>Cedeel: Remove double redirect</p>
<hr />
<div>#REDIRECT [[Fr:Manuel wiki pour Gramps 5.0 - Catégories]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Gramps_5.1_Wiki_Manual_-_Cat%C3%A9gories/fr&diff=71940
Gramps 5.1 Wiki Manual - Catégories/fr
2014-04-07T19:15:28Z
<p>Cedeel: Remove double redirect</p>
<hr />
<div>#REDIRECT [[Fr:Manuel wiki pour Gramps 5.1 - Catégories]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Other_genealogy_tools&diff=48619
Other genealogy tools
2014-04-07T19:11:40Z
<p>Cedeel: /* Other Tools */ Grammar</p>
<hr />
<div>{{languages|Other genealogy tools}}<br />
In addition to the tools in GRAMPS, there are other [http://www.fsf.org/ Free Software] or [http://www.opensource.org/ Open Source] genealogy tools to make websites, trees, parse gedcom, .... If GRAMPS tools do not meet your needs, you may wish to consider one of the following tools.<br />
<br />
==ADAN==<br />
[http://fabrice.bouffanet.free.fr/Adan.shtml ADAN (Archivage D'Actes Notariés)] is a set of PHP modules in [[France|french]] with a search engine for managing Notarial certificates. It needs SHTML, PHP and MYSQL support. Released under GPL2.<br />
<br />
==Blossoc==<br />
[http://daimi.au.dk/~mailund/Blossoc/ Blossoc] is a GPL linkage disequilibrium association mapping tool that attempts to build (perfect) genealogies for each site in the input and score these according to non-random clustering of affected individuals, and judge high-scoring areas as likely candidates for containing disease affecting variation.<br />
<br />
==CollectiveAccess==<br />
[http://www.collectiveaccess.org CollectiveAccess] is a highly configurable cataloguing tool and web-based application for museums, archives and digital collections. Available free of charge under the GPL open-source license, it requires little to no custom programming to support a variety of metadata standards, external data sources and repositories, as well as most popular media formats. In addition to multilingual cataloguing facilities, it allows publication of this data in the languages of your choice.<br />
<br />
==Cranefoot==<br />
[http://www.finndiane.fi/software/cranefoot/ Cranefoot] processes hundreds of families and thousands of individuals at once and wraps the results into a single document. Under GPL license.<br />
<br />
==eSciDoc==<br />
<br />
With [https://www.escidoc.org/ eSciDoc], scientists, librarians, and software developers can work with research data, create novel forms of publications, and establish new ways of scientific and scholarly communication. It is under Common Development and Distribution License (CDDL), an OSI-certified license.<br />
<br />
==Esp2ged==<br />
[http://notendur.hi.is/bjr2/esp2ged/ Esp2ged] is a program to move data from Espólín to the GEDCOM file format supported by (almost) all genealogy programs. Esp2ged is released under the GNU GPL License, version 3 or higher.<br />
<br />
==ExpoActes==<br />
[http://expocartes.monrezo.be/ ExpoActes] is a [[Belgium|belgian (french)]] PHP/MySQL module for easily displaying, editing and modifing certificates on '''your''' web server host. <br />
Released under GPL, you need at least Apache 1.3, PHP 4.3 and MySQL 4.0.<br />
Levels for access:<br><br />
*1 = Access to city, parish<br />
*2 = Access to patronymic<br />
*3 = Access to tables (names and dates)<br />
*4 = Access to more informations on certificates <br />
*5 = Allowed to load data with Nimègue (Windows program)<br />
*6 = Allowed to load data with CSV ([http://www.documentfoundation.org/download/ LibreOffice] or text) <br />
*7 = ** not used<br />
*8 = Allowed to manage all data<br />
*9 = Admin<br />
<blockquote>Seems Linux users need [http://expocartes.monrezo.be/download/actes.zip main module] and [http://expocartes.monrezo.be/download/_config.zip config]. This module is powerful but in French-only.<br />
[http://expocartes.monrezo.be/actes/admin/aide/chargecsv2.html help (in french)] for importing CSV on your server.<br />
</blockquote><br />
<br />
==Familier/Familiar==<br />
[http://familier.sourceforge.net/ Familier/Familiar] is a GPL cross-platform Family Tree management software using QT4. It supports viewing/editing file tree using drag-drop in multiple ways. Events allow you to define events in any number.<br />
It is available for both UNIX and Windows.<br />
<br />
==Gedail==<br />
[http://jfbaquet.free.fr/outils/fonc_en.html Gedail] generates a Web genealogical site from a Gedcom file based on the gedcom 5.5 standard. It doesn't handle all gedcom elements. It is released under GPL.<br />
<br />
==GED2WWW-Genatoile==<br />
GED2WWW was an open source software originally written by Leslie Howard. Jean-Baptiste Fahy maintained the [http://home.nordnet.fr/~jbfahy/ged2wwwe.htm program] under [http://home.nordnet.fr/%7Ejbfahy/readme.txt GPL] but the developments are now on a new program: [http://home.nordnet.fr/~jbfahy/Genatoile/ GénàToile], which not display yet non-ASCII characters under UTF-8.<br />
<br />
==Gedcom one-to-one to XML==<br />
[http://www.unterstein.net/su/nn2x/ged1212xml.html ged1212xml] are scripts (awk|wsh ~ Javascript for Windows Script Host) to convert [[Gedcom]] data – one-to-one to wellformatted XML.<br />
<br />
==Généapro==<br />
[http://briot.github.com/geneapro/ Généapro] is GPL3 web genealogical software based on the [http://www.ngsgenealogy.org/cs/GenTech_Projects GenTech data model].<br />
<br />
==GenXchange==<br />
[http://mrgibson.com/gedcom/ GenXchange] is an experimental collection of free GPL genealogy tools to work with GEDCOM 5.5 and GSF 2.0 files. This software allows export of data to GEDML and HTML files. GEDXchange runs on Linux, Windows 95 through Vista, and OSX operating systems. Written in C, these tool are a set of fast binaries (not scripts) of both graphical interface and command line interface applications to meet most genealogy viewing and recording needs.<br />
<br />
==Gramps-php-exporter==<br />
[https://github.com/steelwil/gramps-php-exporter gramps-php-exporter] exports your [[Gramps XML]] database to a SQLite database, using python 2 or 3.<br />
<br />
Additionally there are some PHP scripts to display your database on the web.<br />
<br />
All privacy settings are honoured.<br />
<br />
==hrlib==<br />
[http://sourceforge.net/projects/hrlib/ hrlib] is a python library to read Heredis (a genealogy program) file. It allow you to read-only everything in a Heredis file with extension .hrX. Plus [http://sourceforge.net/projects/hrreportmaker/ hrreportmaker] create some reports with hrlib. It is able to use LifeLine report and also create new one in Python. There is no packages but files are on CVS. It is released under GPL. <br />
<br />
==hr2ged==<br />
[http://sourceforge.net/projects/hr2ged/ hr2ged] is a python program that transcribe Heredis file in Gedcom. It is available both with a GUI and on command-line. Also [http://loic.fejoz.free.fr/hr2db/ hr2db] may transcribe to MYSQL, ACCESS (via ODBC), Gadfly. It is released under GPL.<br />
<br />
==JcArbGen==<br />
[http://perso.orange.fr/noroc/jcarbgen.htm JcArbGen] is a KDE (qt) pedigree tree manager in '''french'''. It is released under GPL.<br />
<br />
==Karto==<br />
[http://sourceforge.net/projects/karto karto] needs java and is released under GPL.<br />
<blockquote>Karto allows to calibrate a scanned map with some known geo-points (Lambert, UTM, ...). After that, you can add any points (GPS points) in the map to build your own map. You can also add a transparent GIF image in the map after calibration (cave or mine). It doesn't work with common genealogical formats but with most images and textual masks. Useful if you want to display ancestors on your old map.</blockquote><br />
<br />
==Omeka==<br />
[http://omeka.org Omeka] is a GPL flexible web-publishing platform for the display of library, museum, archives, and scholarly collections and exhibitions.<br />
<br />
==openBMD==<br />
[http://openbmd.sourceforge.net/Home.html openBMD] is a free and cross-platform desktop application under GPL2 for the transcription of Birth, Marriage and Death (BMD) index records.<br />
<br />
==Phpmyfamily==<br />
[http://www.phpmyfamily.net/ phpmyfamily] is a dynamic genealogy website builder which allows geographically dispersed family members to maintain a central database of research which is readily accessable and editable. By having a central repository, family members can contribute as and when information becomes available without requiring them to send it to a central 'custodian', or disseminate via email, and allows anecdotal information and possible leads to be shared.<br />
<br />
==PyPedal==<br />
[http://pypedal.sourceforge.net/ PyPedal] - Python Pedigree Analysis is a Python module that provides tools for the manipulation of pedigrees, simple visualization of pedigrees, and the calculation of measures of genetic diversity from pedigrees.<br />
<br />
==Rodovid==<br />
[http://rodovid.sourceforge.net/ Rodovid] is a GPL2 drag-n-drop genealogic program for Linux or Windows based on Tk, Perl. You can edit info (name, sex, dates of birth, death, marriage, etc...) for individuals, add/remove photos, import and export GEDCOM data, creating sites like [http://www.mishchenko.tk this one].<br />
<br />
== SimplePyGed ==<br />
[http://github.com/dijxtra/simplepyged SimplePyGed - A simple Python GEDCOM parser], provides Python [http://en.wikipedia.org/wiki/Application_programming_interface API] to most commonly used GEDCOM records, tags and events. Released under GPL.<br />
<br />
== Web Family Tree ==<br />
[http://www.simonward.com/cgi-bin/page.pl?family/tree Web Family Tree] draws a tree of ancestors and descendants for any person, showing any number of generations (where the information exists). Published with a GNU General Public License. Also, Gramps allows to export into this format. You may download the last version on [http://freshmeat.net/projects/familytree_cgi/ freshmeat].<br />
<br />
== XGenealogy ==<br />
[http://www.bhagooa.com/XGenealogy/index.html XGenealogy] is a open-source genealogy program using GEDCOM 6.0 and written in java.<br />
<br />
==Xurano==<br />
[http://www.xurano.org/ Xurano] is a GNU Public License graphical editor to create and edit mid-size family trees (some hundred persons).<br />
<br />
==Yggdrasil==<br />
[http://code.google.com/p/yggdrasil-genealogy/ Yggdrasil] is a PostgreSQL database and a PHP front-end for large genealogy or prosopography research projects, with focus on documentation of the entire population of a particular area. New BSD License.<br />
<br />
== Projects hosted on Sourceforge code ==<br />
[http://sourceforge.net/directory/home-education/genealogy Sourceforge] is hosting some free and open source projects.<br />
<br />
== Projects hosted on Google code ==<br />
[http://code.google.com/hosting/search?q=label:Genealogy Google code] is hosting some free and open source projects.<br />
<br />
== Non-Free Software ==<br />
In addition to [http://en.wikipedia.org/wiki/Free_Software Free Software] and [http://en.wikipedia.org/wiki/Open_source_software Open Source Software] programs, there are no cost, shareware and commercial genealogy tools. It is not the goal of the GRAMPS project to promote such products, since they do not preserve the user's freedom and can lock the user's data out of his/her control.<br />
<br />
For more information on no cost, shareware and commercial, see [http://www.cyndislist.com/software.htm Cyndi's List] or [http://genealogyblog.geneanet.org/ Geneasoft].<br />
<br />
== Other Tools ==<br />
One can also exchange information with family web applications, but these are not directly genealogy related. They can be interesting to host data generated from genealogy applications (anniversaries, ...). Some free tools (you need the skill to set up a web service, most web projects have companies connected to them that for a fixed fee host and maintain the application for you):<br />
<br />
* '''Family Connection''': [http://familyconnect.rubyforge.org/ Family Connection] is a GPL Web application based on [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails], which restricts access only to family members by requiring a family password. It offers Family News, Address Book, Photo Album.<br />
<br />
* '''Family Connections''': [http://www.familycms.com/ Family Connections] is a private, easy-to-use website where you can connect with your friends and family.<br />
<br />
== Handset ==<br />
<br />
* Experimental [http://gramps-project.org/2011/01/gramps-mobile-interface-%E2%80%93-part-ii/ Gramps mobile interface] for devices with Meego and maybe devices with [https://www.tizen.org/devices Tizen].<br />
See also [[DenominoViso]] and [http://gramps-connect.org/ gramps-connect].<br />
<br />
* Experimental [http://code.google.com/p/maegen/ Maegen] for Maemo5/N900.<br />
<br />
<br />
[[Category:Genealogy|All articles]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Translating_Gramps&diff=29292
Translating Gramps
2011-06-15T22:59:38Z
<p>Cedeel: /* Plural forms */ msgid and msgstr confusion in examples</p>
<hr />
<div>{{languages|Translating GRAMPS}}<br />
<br />
Tips for translators of the GRAMPS program.<br />
[[Category:Translators/Categories]][[Category:Developers/General]]<br />
<br />
==Gettext file format==<br />
<br />
===Header===<br />
<br />
''msginit'' is a GNU utility, called on /po directory, which generates a header for gettext file template : '''gramps.pot'''.<br />
<br />
"Project-Id-Version: PACKAGE VERSION\n"<br />
"Report-Msgid-Bugs-To: \n"<br />
"POT-Creation-Date: 2004-12-30 10:52-0500\n"<br />
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"<br />
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"<br />
"Language-Team: LANGUAGE <LL@li.org>\n"<br />
"MIME-Version: 1.0\n"<br />
"Content-Type: text/plain; charset=CHARSET\n"<br />
"Content-Transfer-Encoding: 8bit\n"<br />
<br />
* ''Project-Id-Version'' : this is the name and version of the package. Fill it in if it has not already been filled in by xgettext. <br />
* ''Report-Msgid-Bugs-To'' : this has already been filled in by xgettext. It contains an email address or URL where you can report bugs in the untranslated strings:<br />
** Strings which are not entire sentences, see the maintainer guidelines in Preparing Strings.<br />
** Strings which use unclear terms or require additional context to be understood.<br />
** Strings which make invalid assumptions about notation of date, time or money.<br />
** Pluralisation problems.<br />
** Incorrect English spelling.<br />
** Incorrect formatting. <br />
* ''POT-Creation-Date'' : this has already been filled in by xgettext.<br />
* ''PO-Revision-Date'' : You don't need to fill this in. It will be filled by the PO file editor when you save the file.<br />
* ''Last-Translator'' : fill in your name and email address (without double quotes).<br />
* ''Language-Team'' : fill in the English name of the language, and the email address or homepage URL of the language team you are part of. Before starting a translation, it is a good idea to get in touch with your translation team, not only to make sure you don't do duplicated work, but also to coordinate difficult linguistic issues. In the Free Translation Project, each translation team has its own mailing list. The up-to-date list of teams can be found at the Free Translation Project's [http://translationproject.org/ homepage], in the "Teams" area.<br />
<br />
=== msgid / msgstr / comment / fuzzy ===<br />
<br />
#: gramps.py:10<br />
#, fuzzy<br />
msgid "File not found"<br />
msgstr ""<br />
<br />
* text after ''#'' provides a comment.<br />
** The file reference and the line number after ''#:'' <br />
** A comment on code or the main string (''msgid'') after ''#.''<br />
** A comment on your translation (''msgstr'') after ''#''<br />
This will help translator but is optional for having a translation.<br />
* ''#, fuzzy'' could be added because string is not up-to-date. It means that there was a change somewhere (a string has been added, removed or modified) and ''xgettext'' did a guess on what the translation should be. This guess is most likely not entirely correct, but it is often very close.<br />
''fuzzy'' strings are ignored, english string (''msgid'') will be used ! Need to correct/validate entry on your translation editor.<br />
* msgid is the string, present on gramps' code<br />
* msgstr is your translation string<br />
<br />
==Tips for translators==<br />
===Getting started===<br />
<br />
# Always save your translations in UTF-8 encoding<br />
# Don't overwrite the English strings, your translation should be below the original string<br />
# Take heed on special characters. You must have the same number of and types as the original string.<br />
# Verify spelling and grammar on your translation.<br />
# Don't translate "too freely". Your translation should be as close match to the original as possible<br />
# Be consistent with your translations. If you decide on a specific word/phrase for something, stick to that throughout the translation.<br />
# If possible, try the translation before sending<br />
<br />
Translating GRAMPS into a new language means translating English strings used in the GRAMPS interface. To put it shortly, this amounts to<br />
# obtaining the gramps.pot file with the strings to be translated,<br />
# translating the strings in the template, and<br />
# getting the translated file uploaded into gramps SVN repository.<br />
Another avenue of translation is translating the documentation. This is a different and lengthy process and it is decribed in our [[Translating the manual]] page. Here we will concentrate on the interface translation only.<br />
<br />
===Obtaining gramps.pot===<br />
* Download <code>gramps.pot</code> from GRAMPS SVN repository, see [[Brief_introduction_to_SVN| the introduction to SVN]].<br />
* Look for <code>gramps.pot</code> in the directory <code>gramps32/po</code> or if you looking for the trunk version look for <code>gramps.pot</code> in the directory <code>trunk/po</code>.<br />
<br />
===Translating messages===<br />
* Copy <code>gramps.pot</code> to the file named <code>lang.po</code>, according to the language you are translating into (<code>fr.po</code> for French, <code>ru.po</code> for Russian, etc.)<br />
* Use [http://gtranslator.sourceforge.net GTtranslator] (GNOME, windows), [http://i18n.kde.org/tools/ KBabel] (KDE), [http://userbase.kde.org/Lokalize Lokalize] (KDE, windows), Emacs po-mode, [http://translate.sourceforge.net/wiki/pootling/index pootling] (GNU/Linux, windows), [http://www.poedit.net/ poedit] (GNU/Linux, OSX, windows), or any similar tool designed for translating <code>.po</code> files. If you do not like any of these tools, you can use any text editor to translate messages. If using vim, properly setting the "langmap" option will significantly speed up your work.<br />
* Even though GRAMPS uses UNICODE (UTF-8) for its character set, you may use your native character set for your translation. Just make sure you specify the character set you are using in the <code>Content-Type</code> line in the <code>.po</code> file. GRAMPS will handle the conversion to UNICODE.<br />
* If there are non ASCII characters in the original English string, try to preserve them by copying them, if applicable.<br />
<br />
===Context===<br />
As an extension to standard gettext, strings in GRAMPS can have a context prefix. This prefix should '''not''' be translated, and just be deleted in the translation. More info and an example [[#Translation context|further down]].<br />
<br />
As a special context, you will see the manual context, eg :<br />
'manual|Editing_Dates'<br />
these strings should only be translated if a wiki manual is available in your language. The string refers to a section, eg [[Gramps_3.0_Wiki_Manual_-_Entering_and_Editing_Data:_Detailed#Editing_Dates |Editing_Dates]] in Dutch becomes [[Gramps_3.0_Wiki_Manual_-_Entering_and_Editing_Data:_Detailed/nl#Datums_aanpassen|Datums_aanpassen]].<br />
<br />
===Testing your <code>.po</code> file===<br />
In the directory <code>gramps32/po</code> or the <code>trunk/po</code> run the command: <pre>make</pre> If there are errors in your po file, this will fail and give you an error message. You should correct these errors. If you have trouble understanding the error, try to run the next test, which might give a more verbose output.<br />
<br />
====check_po====<br />
In the directory <code>gramps32/po</code> or the <code>trunk/po</code> run the command: <pre>./check_po lang.po</pre> or <pre>python check_po lang.po > lang</pre> where lang is your language code. This will give you errors in your translation, information on badly translated phrases, ... the output could resemble something like this..<br />
<br />
File: nl.po<br />
Template total: 3816<br />
PO total: 3671<br />
Fuzzy: 125<br />
Untranslated: 12<br />
%s mismatches: 0<br />
%d mismatches: 2<br />
%() name mismatches:9<br />
%() missing s/d: 0<br />
Runaway context: 0<br />
XML special chars: 0<br />
Last character: 15<br />
Shortcut in msgstr: 16<br />
PO Coverage: 99.67%<br />
Template Coverage: 95.89%<br />
Localized at: 97% (previous gramps.pot)<br />
<br />
If you get ''previous gramps.pot'', then you are not using the last ''gramps.pot'', see [[#Updating_your_translation|update your translation]]. ''fuzzy'' and untranslated strings will be ignored, Gramps will use main strings in english.<br />
<br />
-------- %d mismatches --------------<br />
You can see that there are 3816 strings to be translated and the coverage is around 96 %. There are still 12 untranslated strings and some 120 fuzzies. The last one can be ok, but should be checked. Additional information shows e.g. that in 15 strings there is a mismatch with the 'last character':<br />
-------- last character not identical ---------<br />
msg nr: 98, lineno: 602<br />
msgid "Could not make database directory: "<br />
msgstr "Kon geen gegevensbestandsmap aanmaken"<br />
<br />
This is very valuable information, because you can easily see what the problem is, even if you do not understand the language! Clearly the last characters must be ": "<br />
<br />
====statistics====<br />
<br />
In the directory <code>gramps32/po</code> or the <code>trunk/po</code> run the command: <pre>msgfmt --statistics lang.po</pre> or <pre>msgfmt.exe --statistics lang.po</pre> where lang is your language code. This should not throw an error.<br />
Basically this gives the same info in a condensed format: 3533 translated messages, 125 fuzzy translations, 12 untranslated messages.<br />
<br />
====GNU `gettext' utilities====<br />
<br />
[http://www.gnu.org/software/gettext/ GNU `gettext' utilities] provides a few stand-alone programs to massage in various ways the sets of translatable strings, or already translated strings:<br />
<br />
msgattrib - attribute matching and manipulation on message catalog<br />
msgcat - combines several message catalogs<br />
msgcmp - compare message catalog and template<br />
msgcomm - match two message catalogs<br />
msgconv - character set conversion for message catalog<br />
msgen - create English message catalog<br />
msgexec - process translations of message catalog<br />
msgfilter - edit translations of message catalog<br />
msgfmt - compile message catalog to binary format (.po->.mo)<br />
msggrep - pattern matching on message catalog<br />
msginit - initialize a message catalog<br />
msgmerge - merge message catalog and template<br />
msgunfmt - uncompile message catalog from binary format<br />
msguniq - unify duplicate translations in message catalog<br />
<br />
For checking syntax (header, format, domain) :<br />
msgfmt -c nl.po<br />
<br />
msgfmt.exe -c nl.po<br />
<br />
For checking keyboard accelerators (underscore) :<br />
msgfmt --check-accelerators=_ nl.po<br />
<br />
msgfmt.exe --check-accelerators=_ nl.po<br />
<br />
====Gettext lint====<br />
<br />
[http://gettext-lint.sourceforge.net/ Gettext lint] is a collection of tools for checking the validity, consistency and spelling of PO. Some python scripts do not work anymore with last expat version.<br />
<br />
====Translate Toolkit====<br />
<br />
[http://translate.sourceforge.net/wiki/toolkit/index Translate Toolkit] is a collection of useful tools for localisation. It can help to improve the quality of your localisation, including tools to help check, validate, merge and extract messages from your localizations.<br />
<br />
====Save as .mo file====<br />
<br />
If possible and when you are finished translating, go to '''File -> Save as...''' to generate a ''.mo'' file for testing syntax.<br />
<br />
* Under poedit, you can set to always compile a ''.mo'' file when saving changes by clicking '''File -> Preferences''' and on the '''Editor tab''' check the '''Automatically compile ''.mo'' file on save box'''. A dialog will warn you if there is a syntax error on your ''.po'' file.<br />
<br />
* Kbabel and Lokalize also provide a syntax check when saving. If an error occured we can navigate to messages which contain errors. <br />
<br />
Please, enable this feature to avoid errors on compilation process.<br />
<br />
===Formatting (compiling) <code>.po</code> file===<br />
* Currently, [[Coding_for_translation#How_it_works|formatting (msgfmt) is performed during build time]], so you should not have to worry about it. The translated <code>.po</code> file is the product of your work. Check it into SVN if you obtained the permission to do so, or email it to [[Contact|Brian or Benny]] otherwise.<br />
<br />
===Updating your translation===<br />
If you have submitted a translation, it may well be that after some weeks/months, new strings are added to GRAMPS, implying you need to update your translation file. <br />
<br />
Assuming you have obtained originally the GRAMPS source tree as explained in [[Brief introduction to SVN]]. Now:<br />
* Update your gramps tree from SVN. This can be done by executing the command <pre>svn up</pre> from the root GRAMPS svn directory. This will download an updated <code>gramps.pot</code> file.<br />
* Use your outdated translation to translate the strings that did not change:<pre>msgmerge lang.po gramps.pot -o newlang.po</pre> or <pre>msgmerge --no-wrap lang.po gramps.pot -o newlang.po</pre> where <code>lang</code> is your language code. The <code>--no-wrap</code> option will prevent changes due to automatic word wrapping, use it if your previous po file was constructed like that. The <code>--no-wrap</code> options allows for more readable SVN diffs.<br />
* Check fuzzy messages and translate all untranslated messages in <code>newlang.po</code>. When you are sure everything is right, rename <code>newlang.po</code> as <code>lang.po</code> and check it into SVN as you did with the original file.<br />
* If command <code>msgmerge</code> is not available on your system, you have to install the <code>}gettext</code> package. For [http://wiki.wxpython.org/index.cgi/Internationalization#How_to_get_gettext_tools_for_Win32 windows users].<br />
<br />
There is also the make target that does the following:<br />
* Create new <code>gramps.pot</code> template from the source code files<br />
cd po<br />
make gramps.pot<br />
or<br />
cd po<br />
intltool-update -p<br />
* Updates each <code>po</code> file in the source tree<br />
It may be an overkill for you, but if you feel like using it, you can run:<br />
cd po<br />
make update-po <br />
in the <code>po</code> directory. This assumes that you have already succesfully configured the source. Note, this command ignores <code>--no-wrap</code> option, so not practical for SVN diffs.<br />
<br />
===Testing your update===<br />
<br />
You can test your update easily with the above mentioned '''check_po''' file. If you downloaded this file, just do:<br />
<pre>python check_po newlang.po</pre>. If everything is ok, the output will be something like this:<br />
File: newlang.po<br />
Template total: 3075<br />
PO total: 3075<br />
Fuzzy: 0<br />
Untranslated: 0<br />
%s mismatches: 0<br />
%d mismatches: 0<br />
%() name mismatches:0<br />
%() missing s/d: 0<br />
Runaway context: 0<br />
XML special chars: 0<br />
Last character: 0<br />
Shortcut in msgstr: 0<br />
PO Coverage: 100.00%<br />
Template Coverage: 100.00%<br />
<br />
===Installing your translation===<br />
<br />
You want to use the new translation immediately, and systemwide?<br />
You can by installing just the contents of the po directory, but you will need to build the source first, so:<br />
./autogen.sh<br />
make<br />
cd po<br />
make --prefix=/usr install #as root !<br />
<br />
This should install your translations to <code>/usr/share/locale/xx/LC_MESSAGES/gramps.mo</code>, with xx being your language. You could of course copy your files manually to that dir with the gramps.mo name.<br />
<br />
Make sure you only install from within the po directory, or you will install the development version of GRAMPS, which is not supported and for testing only!<br />
<br />
==== Running trunk with your translation ====<br />
<br />
The current GRAMPS trunk as of February 2009 by default looks for the i18n data under <code>/usr/local/share/locale</code>. So you can use:<br />
<br />
./autogen.sh<br />
make<br />
cd po<br />
make install #as root !<br />
<br />
This will install the .mo files under /usr/local/share/locale/xx/LC_MESSAGES, since the default prefix is /usr/local<br />
<br />
or <br />
<br />
./autogen.sh --prefix=/home/.../<br />
make<br />
make install #as simple user !<br />
<br />
This will install Gramps and translations under your ''/home/...'' directory.<br />
<br />
===== $GRAMPSI18N (for your locale) =====<br />
<br />
Actually you don't even need to install the files in order to test them. This is useful because you can develop GRAMPS without needing superuser privileges. Bear in mind the GRAMPS i18n process goes something like this when you use trunk as of February 2009:<br />
<br />
* when you type <code>make</code> in the source tree root (/home/user/trunk e.g.) all the trunk/po/*.po files are compiled into trunk/po/*.gmo files.<br />
* when you type <code>make install</code> inside the /home/user/trunk/po directory, these .gmo files are copied to /usr/local/share/locale/xx/LC_MESSAGES as gramps.mo files.<br />
<br />
But you can change the place where GRAMPS looks for these files by altering the environment variable $GRAMPSI18N. So you could also for instance do something like this and avoid the <code>make install</code> step: (if you are using csh or tcsh the syntax would be a little different)<br />
<br />
[user@localhost /home/user/trunk]$ mkdir -p po/en_GB/LC_MESSAGES<br />
[user@localhost /home/user/trunk]$ cp po/en_GB.gmo po/en_GB/LC_MESSAGES/gramps.mo<br />
[user@localhost /home/user/trunk]$ cd src<br />
[user@localhost /home/user/trunk/src]$ GRAMPSI18N=$PWD/../po LANG=en_GB.UTF-8 python gramps.py<br />
<br />
===== gramps.sh =====<br />
<br />
On a gramps launcher (copy from ''{prefix}/bin/gramps'') you can set :<br />
export GRAMPSDIR=/...<br />
export GRAMPSI18N=/...<br />
<br />
Where the environment variable ''$GRAMPSDIR'' is the path to your ''gramps'' directory.<br />
<br />
Where the environment variable ''$GRAMPSI18N'' is the path to your ''gramps locale'' directory.<br />
<br />
===== Just testing your translation =====<br />
<br />
If you don't want to compile all translations, you may save your ''.po'' file as ''.mo'' file, or use ''msgfmt'' utility on /po directory:<br />
<br />
msgfmt -o gramps.mo your_lang.po<br />
<br />
msgfmt.exe -o gramps.mo your_lang.po<br />
<br />
this will create a ''gramps.mo'' file, a compiled version of your ''.po'' file.<br />
Put it on your translation path (''see above'').<br />
<br />
==Hard to translate phrases==<br />
Some things are just hard to translate. Below are a few of the more difficult items, along with some suggestions on how to handle them.<br />
===LDS terminology===<br />
The Church of Jesus Christ of Latter Day Saints (a.k.a. Mormons) maintains a lot of genealogy data. In the United States, they are probably the non-government organization with the most detailed records available. Genealogical research is important to the Mormon church. They are responsible for defining the [[GEDCOM]] format.<br />
<br />
The LDS Church has some specific terminology that can present difficulty in translating. There are two approaches to handling the information.<br />
# If the LDS Church has a presence in your country, contact the LDS Temple in your area and ask them what the correct terminology is in your native language<br />
# If the LDS Church does not have a presence in your country, it would probably be safe to simply not translate the phrases.<br />
These terms include:<br />
# LDS Ordinance names:<br />
#* Sealed to Parents<br />
#* Sealed to Spouse<br />
#* LDS Baptism<br />
#* Endowment<br />
# LDS Status names for Ordinances:<br />
#* Child<br />
#* Cleared<br />
#* Completed<br />
#* Infant<br />
#* Pre-1970<br />
#* Qualified<br />
#* Stillborn<br />
#* Submitted<br />
#* Uncleared<br />
#* BIC (Born In the Covenant)<br />
#* DNS (Do Not Submit)<br />
#* Canceled<br />
#* DNS/CAN (Do Not Submit/Previous sealing cancelled)<br />
<br />
==Advanced issues==<br />
===Format line parameters===<br />
Format line parameters such as <nowiki>%s</nowiki> and <nowiki>%d</nowiki> '''should not''' be translated. The order of these parameters '''should not''' be changed. Examples:<br />
<br />
English:<br />
Long widowhood: %s was a widow %d years.<br />
<br />
Translation (using Backward English as an example :-):<br />
Gnol doohwodiw: %s saw a wodiw %d sraey.<br />
<br />
Named format line parameters such as <nowiki>%(something)s and %(something)d</nowiki> also '''should not''' be translated. Feel free to change the order of named parameters to correctly phrase the message in your language. Also, use hints provided by the names. Examples:<br />
<br />
English:<br />
Baptized before birth: %(male_name)s<br />
born %(byear)d, baptized %(bapyear)d.<br />
<br />
Translation into Backward English:<br />
Dezitpab erofeb htrib: %(byear)d<br />
nrob %(male_name)s, dezitpab %(bapyear)d.<br />
<br />
In the above example, the verb "born" should be in masculine form (if verbs in your language have gender, that is), since the person born is apparently a male.<br />
<br />
Sometimes those <nowiki>%(something)s</nowiki> are positioned in a text without spaces, like in the example below:<br />
<br />
English:<br />
This person was baptised%(endnotes)s.<br />
<br />
Translation into Backward English:<br />
Siht nosrep saw desitpab%(endnotes)s.<br />
<br />
===Translation context===<br />
In some cases, two different concepts can be expressed by the same word in English and yet require different translations. For example, the '''title of the book''' and the nobility '''title of the person''' are expressed by the same '''Title''' word. However, in other languages different words are needed to describe the book title and the person's title.<br />
<br />
To mitigate such problems, a context can be added to the translation string. A context-enabled string has a vertical line separating the context from the string:<br />
book|Title<br />
person|Title<br />
The correct translation '''should not''' include either the context or the separator. The context is to give the translator idea of what the string means. However, '''both the context and the separator must not be in the translated string''', so in backward english the above is translated into<br />
Eltitkoob<br />
Eltitnosrep<br />
<br />
===Plural forms===<br />
<br />
There was requests for [http://www.gnu.org/software/gettext/manual/html_node/gettext_150.html#Plural-forms plural forms] support.<br />
<br />
First, translators need to check if information is available on .po header :''"Plural-Forms:\n"''. (See [http://translate.sourceforge.net/wiki/l10n/pluralforms samples])<br />
<br />
# msgid contains the singular string in english<br />
# msgid_plural contains the plural string in english<br />
# msgstr[0] contains the singular translated version (for 1 and sometimes 0, set on header)<br />
# msgstr[1] contains the plural version (for 1 + 1 = 2 )<br />
# msgstr[2] contains the plural form (for 2 + 1 = 3)<br />
<br />
*For language with one form (singular=plural, ''Plural-Forms: nplurals=1; plural=0''), like Chinese, Hungarian or Turkish:<br />
<br />
msgid "%d second"<br />
msgid_plural "%d seconds"<br />
msgstr [0] "%d 秒"<br />
<br />
*For language with one plural form (''Plural-Forms: nplurals=2; plural=n != 1;''), like english:<br />
<br />
msgid "%d hour"<br />
msgid_plural "%d hours"<br />
msgstr [0] "%d hour"<br />
msgstr [1] "%d hours"<br />
<br />
*For language with more plural forms (like Czech):<br />
<br />
msgid "%d second"<br />
msgid_plural "%d seconds"<br />
msgstr [0] "%d sekunda"<br />
msgstr [1] "%d sekundy"<br />
msgstr [2] "%d sekund"<br />
<br />
As a final check, please do ensure that the following command does not throw any errors:<br />
<br />
msgfmt -c filename.po<br />
<br />
===Translating mnemonics===<br />
Mnemonics are accelerator keys you find in labels, accessible by pressing the ALT key together with the mnemonic. You see then in the translated text with a low line, eg '_Help' is shown as 'Help' with a line under the H, and can be put to focus/selected by pressing ALT+h.<br />
<br />
It is nice if mnemonics on a screen are unique, but it is not required. If you use twice the same mnemonic, the user must press repeatedly the accelerator to switch between the different entries. However, note the following rule:<br />
"If duplication of access keys in a window is unavoidable, you should still refrain from duplicating the access keys for any of these buttons that appear in the same window: OK, Cancel, Close, Apply or Help."<br />
<br />
So you should check in your language what the mnemonic key is for those buttons, and avoid using the same in translated text<br />
<br />
'''Warning''': some fonts family will not properly display mnemonics on "g", "j", "p", "q" or "y" as these print the letter over the line under it making it very hard to distinguish the small line. Please avoid to use mnemonics key bindings on these letters. Also try to avoid i and l, as people have difficulty distinguishing between those.<br />
<br />
Capital letters are no problem though, underlining eg G will work just fine as the letter does not write over the line.<br />
<br />
===Translating relationships===<br />
Translating relationships is not done within the <code>.po</code> files, except for occasional <code>father</code> and <code>mother</code> strings here and there in the interfaces and reports. Complete translation of all relationships for the language/culture is done inside a relationship calculator plugin.<br />
<br />
In short, the need for a plugin comes from the impossibility to translate "first cousin twice removed" in languages such as, e.g., German or Russian. See the [[Relationship Calculator]] page for details on why and how to create such a plugin.<br />
<br />
===Translating dates===<br />
Handling date translation is not entirely done within the <code>.po</code> files. Complete handling of date translation for each language/culture is done inside a dedicated date handler module.<br />
<br />
The need for a separate module comes from the requirements to handle culture-specific parsing and displaying of dates. For example, the month and day order is different between most European countries and the US. Also, each language has its own set of acceptable modifier and qualifiers for the date: things like "from X to Y" or "between X and Y" may have different word order. Same with "around", "calculated", "estimated". Add to this calendar names, and you have a compelling need for a dedicated module. See the [[Date Handler]] page for details on why and how to create such a module.<br />
<br />
==Translating man pages==<br />
You can also translated the man pages into your own language.<br />
<br />
For the development (trunk) version you can find the required starting files under the directory (/trunk)/data/man. You will find the files<br />
*Makefile.am<br />
*gramps.1.in<br />
<br />
First off all you must make a directory for your language under data/man.<br />
<code><br />
cd data/man<br />
</code><br />
<br />
and do <code><br />
mkdir xx<br />
</code><br />
<br />
where xx is your languagecode (fr for French, sv for Swedish, etc.) You should use SVN. See [[Brief_introduction_to_SVN| the introduction to SVN]]. Then do <code><br />
svn add xx<br />
svn commit -m "xx dir for man pages" xx<br />
</code><br />
This will add the xx dir under svn revision control and upload the new dir.<br />
Next step is to copy the Makefile.am and gramps.1.in from data/man to your new directory. Translate all relevant strings in the data/man/xx/gramps.1.in file. Change the file data/man/xx/Makefile.am:<br />
*add the line mandir = @mandir@/xx<br />
*change the line && CONFIG_FILES=data/man/xx/$@ $(SHELL)<br />
<br />
Next step: change the file data/man/Makefile: <br />
*add xx to the line SUBDIRS = fr nl sv<br />
<br />
The final step is to alter the file ''Configure.in '':<br />
*add data/man/xx/Makefile to the line AC_CONFIG_FILES([<br />
<br />
Because you added new files, SVN requires that you set the correct propset for those files. Two things are to be done.<br />
<code><br />
svn propset svn:mime-type text/plain xx/gramps.1.in xx/Makefile.am<br />
svn propset svn:eol-type native xx/gramps.1.in xx/Makefile.am<br />
</code><br />
<br />
You could also in the config file of subversion ( HOMEDIR/.subversion/config) enable the auto-prop feature (enable-auto-props = yes) and uncomment the relevant lines in the [auto-props] section.<br />
All changes must be committed and do not forget to change the ChangeLog file.<br />
<br />
You should see no errors when you run the <code><br />
./configure<br />
make<br />
</code> scripts.<br />
<br />
{{man warn|Install|This last step must be done only in the data/man/xx directory. If not, your normal gramps installation will be overwritten. And this step must be done as superuser(su)}}<br />
<code><br />
sudo make install<br />
</code><br />
This will put the gramps.1.gz file into /usr/local/share/man/xx/man1 directory. You could also use a prefix. Then you do:<code><br />
sudo make --prefix=/usr/share install<br />
</code><br />
<br />
To see the result of your work, do:<code><br />
man -L xx gramps<br />
</code><br />
<br />
==Translating wiki manual==<br />
To have the link working in GRAMPS, you need to have or edit the GrampsDisplay.py file to contain your language.<br />
On line 30 of that file, you see:<br />
<br />
MANUALS = {<br />
'nl' : '/nl',<br />
}<br />
<br />
This maps a language code to the extension used on the wiki, so to add french, change this too:<br />
<br />
MANUALS = {<br />
'nl' : '/nl',<br />
'fr': '/fr',<br />
}<br />
<br />
*Every 'manual|...' entry in the gramp.pot file refers to a section in the manual, so make sure to use good section headings so this does not change too much over time.<br />
Note that reports/tools link to a section in the page with the same name as the report name in GRAMPS.<br />
<br />
*You should be able to edit directly on wiki or using tools like [http://translate.sourceforge.net/wiki/toolkit/txt2po txt2po]. Also previous gettext file for the manual and [http://en.wikipedia.org/wiki/Translation_memory Translation Memory] may help you to upgrade deprecated/old gettext files.<br />
<br />
==Language specific pages==<br />
Check out the pages which cover some aspects of translation into a specific language, such as the glossary.<br />
<br />
*[[Translation into Russian|Russian]]<br />
<br />
==Translating addon plugins==<br />
<br />
* See [[Addons_Development#Get_translators_to_translate_your_addon_into_multiple_languages|3rd-party addon for GRAMPS 3.2]].</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Existing_reports_from_other_genealogy_programs&diff=29015
Existing reports from other genealogy programs
2011-06-02T17:52:26Z
<p>Cedeel: Removed dead links</p>
<hr />
<div>Directory of existing reports from other genealogy programs useful to the practice of genealogy.<br />
<br />
Currently, GRAMPS produces some [[Sample_reports|good reports]]. <br />
<br />
Also, there is a compare tab on [[Features|Checklist]].<br />
<br />
We can find some resources on this [ftp://ftp.cac.psu.edu/pub/genealogy/INDEX.html ftp]<br />
<br />
==OpenSource programs web demos==<br />
* [http://www.geneweb.org/en/index.html Geneweb] allows us to generate online reports with his database [http://geneweb.inria.fr/example?lang=en example]. Useful [http://geneweb.inria.fr/example?lang=en&m=PS&bi=on&de=on&ma=on place/surname report] for genealogical search.<br />
* [http://www.geneotree.com/index.php?ilang=en&imenu=1 Geneotree] made a [http://www.geneotree.com/geneotree/ demo].<br />
* [http://lifelines.sourceforge.net/ Lifelines] offers multiples reports listed on this [http://lifelines.sourceforge.net/Ethel/rptix.html directory].<br />
<br />
===Non-english examples===<br />
* [http://genealogie-servin.geneamania.net/index.php Geneamania demo] (french)<br />
* [http://www.arvernes.com/V1/?page=contribution Genj contributions] (french), which have more screenshots than [http://genj.sourceforge.net/wiki/doku.php/en/reports primary GenealogyJ web site] (english).<br />
* [http://geneabax.free.fr/familytree/ged2wwwf/ ged2www] and his GPL-child [http://geneabax.free.fr/familytree/genatoile/ GénàToile].<br />
<br />
==Shareware/Commercial examples==<br />
The figure below shows an example of a Descendants charts that can be produced from the shareware [http://www.ics.uci.edu/~eppstein/gene/ Gene] program (which runs on the 'classic' Mac OS). The original output is designed (in this case) for A4 landscape printing, so the whole chart fits across the page, and would probably cover two pages downwards. (The print mechanism cleverly prints right to the top and bottom of the printable area, so there is no wasted space, and the bottom of the print is not lost over the unprintable area). The application can produce ancestor or descendant charts. There are option for the amount of information shown for the people, and the page layout can either be landscape or portrait.<br />
<br />
This chart is noteworthy because the application very cleverly lays out the chart so that it is very compact but still shows each generation on the same level. I have not seen such a compact and clear layout in any other application.<br />
<br />
The chart is of the British royal family starting from King George V; the GEDCOM is available on the net as royal92.ged<br />
<br />
[[Image:Desc of George V.gif]]<br />
<br />
[[Category:Developers/General]]<br />
[[Category:Plugins]]<br />
[[Category:Genealogy]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=GEPS_006:_Better_Place_handling&diff=27706
GEPS 006: Better Place handling
2011-03-19T15:58:47Z
<p>Cedeel: /* Good definition of place and address/residence event in Gramps */</p>
<hr />
<div>== Changes already implemented ==<br />
A new hierarchical place view was introduced in version 3.2 of Gramps.<br />
<br />
The place object was left unchanged, but the existing location fields were interpreted as a hierarchy. The location fields are as follows:<br />
* Country<br />
* State<br />
* County<br />
* City<br />
* Street<br />
The new view displays Country, State and County as a tree.<br />
<br />
A Locality field has been added to the location for version 3.3 of Gramps. The new hierarchy is as follows:<br />
* Country<br />
* State<br />
* County<br />
* City<br />
* Locality<br />
* Street<br />
<br />
== Proposed changes ==<br />
<br />
=== Integration with online map tools ===<br />
Which online map tools? - NH<br />
* Openstreetmap, we need free data in a free application. GeoView already allows a view based on places, also to set lat/lon<br />
<br />
=== Good definition of place and address/residence event in Gramps ===<br />
* For UK data, an extra Locality field between City and Street would be useful.<br />
* For Dutch data, an extra Municipality field between County and City would be useful. (Feature Request 4231)<br />
* Japanese use block names, instead of street names: [http://en.wikipedia.org/wiki/Japanese_addressing_system]<br />
<br />
We could re-define each field for each country, or we could try to keep each field maintaining similar data. I think that I prefer adding a couple of extra fields. This is less complex than a list structure with definable number of tiers (less complex to program, but also less complex to use by the user)<br />
<br />
{| {{Prettytable}}<br />
|-<br />
! Existing !! New structure!! General Name!! USA !! England !! France !! Netherlands !! Germany !! China<br />
|-<br />
| State || Tier 1 || Region || State || Not Used || Region || Not Used || Province || Province<br />
|-<br />
| County || Tier 2 || District || County || County || Department || Province || District || County<br />
|-<br />
| City || Tier 3 || City || City || City || City || Municipality/City || City || City<br />
|-<br />
| / || Tier 4 || Locality || Locality || Locality || Hamlet/Lieu-dit || City/community/hamlet || Locality || Locality<br />
|-<br />
| Street || Tier 5 || Street || Street || Street || Street || Street || Street || Street<br />
|-<br />
|}<br />
<br />
Definitions:<br />
* ''' Tier 1 & 2''': Between a country and the smallest administrative section, we allow for two levels.<br />
* ''' Tier 3 ''': A settlement consisting of a number of dwellings varying in size from a hamlet to a city. In some countries this will be a division of the country with a mayor.<br />
* ''' Tier 4 ''': The locality people identify themself with. This further classifies tier 3. Examples would include a neighbourhood within a town or city, or a village or hamlet on the outskirts of a town or city.<br />
* ''' Tier 5 ''': Street or block, so the lowest division needed for postal information.<br />
<br />
Tiers 3, 4, and 5 look quite consistent between countries so far. - NH<br />
<br />
We would need a country table. This would hold the field definitions for each country including the field names, 'not used' flags, and which fields should be used in the place tree view. <br />
<br />
This data could then be used to dynamically create fields in the place editor, place filter and place tree view.<br />
<br />
Suggestion (BM)<br />
* we should not work with 'not used' flags. Eg, some people in Wales might want to enter it. A not used flag would make it impossible. In the USA, people from Clairemont [http://en.wikipedia.org/wiki/Clairemont,_San_Diego,_California] might like to indicate that, however it is a neighbourhood. Instead I would suggest perhaps a address format default. For UK this would be I suppose:<br />
Street<br />
Locality<br />
City<br />
County<br />
Post Code<br />
Country<br />
: for Belgium this format would be<br />
Country<br />
ZIP Locality (City)<br />
street<br />
: with a format field and people seeing this format, they will understand how they are supposed to enter the place information (note that if Locality equals city it obviously must not be repeated.<br />
<br />
Your example of Clairemont is exactly what I intended the Locality field for. Its use is not limited to the UK. - NH<br />
<br />
'''Questions and Design Decisions'''<br />
* Do we need 2 or 3 tiers between the level with a mayor and the country? We only take 2 tiers. Most countries have more than 2 tiers, but they have little importance for the inhabitants or genealogy. What about Feature Request 4231?<br />
* Many countries have different sub-levels depending on the country. Yes, but Gramps is not a place storing application. In Countries like China you have province or autonomous region or .. as Tier 1. We can only provide one label, the users must himself understand that a locality in an autonomous region should put the name of the region in the Tier 1 (Labeled province) field. Or we could make the label read "Province/Region" if appropriate.<br />
<br />
'''Issues specific to the UK'''<br />
* When entering data into the country field there are a few possibilities. "UK" could be used as the country, or one of the constituent countries may be used (England, Wales, Scotland, Northern Ireland). Other terms such as GB, Britain or British Isles may also be used. A thread on the mailing list discussed this [http://gramps.1791082.n4.nabble.com/How-to-imput-UK-address-td2283137.html] and three different methods are used at the moment (UK, GB and constituent countries).<br />
* If constituent countries are used in the country field then the state field will not be used.<br />
* If "UK" or "GB" is used in the country field then the state field may optionally be used to qualify the constituent country.<br />
* Questions are often raised about how to record London addresses. At the moment the county field could be used to store "Greater London", "London", or a historic county for the London borough. The city field could be used to store "London" or the name of the London borough. The new Locality field may be useful to record the London borough.<br />
* When we upgrade the database we need to take into account the different possible values in the country field.<br />
<br />
=== Define one ideal way of working with alternative place ===<br />
Physical places can have more than one name and can move between administrative regions over time. The following list gives examples of why places need alternate names:<br />
* Places can change their name over time.<br />
* In countries where more than one language is spoken the place may have different names in different languages.<br />
* Multiple names for a place may exist where there are variant spellings for the place name.<br />
* Different names may be used for political reasons.<br />
For genealogical purposes it is important to record the place name as it appears in the source material. We could define alternative places with a date span. There may be one or more alternative places within a given date span.<br />
<br />
=== Improve the place tree view ===<br />
At present the place tree uses a three level hierarchy of Country, State and County.<br />
<br />
For some countries the State field is not relevant - for example in the UK. In this case it is more useful to display a Country and County or Country, County and City hierarchy.<br />
<br />
Countries also use different descriptions for the their administrative regions. We could change the column headings according to the country displayed. This would require a countries table in the database. We could also restrict the view to displaying only one country at a time.<br />
<br />
=== Improve data entry in the Place editor ===<br />
We could use drop-down lists in the place editor to allow the user to select values for each of the hierarchical fields. The data could come from data already in the database or we could consider building up a gazetteer for Gramps.<br />
<br />
Suggestion (BM):<br />
* Country is a GrampsType field, with known countries predefined. This gives us translated countries.<br />
* based on country, the normal divisions are set bold. All divisions can be entered however<br />
* Translation of labels is based on country, with fallback to the general. A Tier will have different translations depending on the country it is in. However, we must be carefull not to translate everything before Gramps can start up. Eg, we define, COUNTY= _('County), USA = (STATE, None, COUNTY, ...), where None is used to indicate to use the general name of the field, and this long list of countries is not kept in memory but constructed when a county is needed. <br />
<br />
The place editor could be made clearer if the hierarchical fields were placed together in the editor window.<br />
<br />
== Motivation ==<br />
Time and again users pose questions on improving the place structure of Gramps. This GEPS is about defining a new improved way of handling place, keeping backward compatibility with GEDCOM/present Gramps.<br />
<br />
Many things are also not well designed, in that Gramps allows the user to do as he likes, without guiding the user to a good way of storing place data. (this statement is disputed, see [[Talk:GEPS 006: Better Place handling|discussion]])<br />
<br />
== Some ideas ==<br />
<br />
* [[Geonames]]<br />
* [http://wiki-en.genealogy.net/wiki/Gedcom_5.5EL#High-Level-Entitiy_.22Location.22 Gedcom 5.5EL]<br />
* An internal [[place database]]<br />
<br />
== References ==<br />
<br />
Some relevant bug tracker entries:<br />
<br />
* [http://www.gramps-project.org/bugs/view.php?id=1862 1862] Place Guessing Feature Request<br />
* [http://www.gramps-project.org/bugs/view.php?id=2196 2196] Some changes to the Places viewer would be helpful<br />
* [http://www.gramps-project.org/bugs/view.php?id=2311 2311] Implement a place database ...<br />
* [http://www.gramps-project.org/bugs/view.php?id=4230 4230] Places tree view gives confusing place names<br />
* [http://www.gramps-project.org/bugs/view.php?id=4231 4231] Add Municipality to places data<br />
* [http://www.gramps-project.org/bugs/view.php?id=4510 4510] Additional Suggestion<br />
* [http://www.gramps-project.org/bugs/view.php?id=4712 4712] Eliminate case-sensitivy when searching city names in place completion tool<br />
* [http://www.gramps-project.org/bugs/view.php?id=4714 4714] Superwide resize after adding lat/lon<br />
<br />
[[Category:GEPS|B]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Getting_started_with_Gramps_master&diff=27705
Getting started with Gramps master
2011-03-19T15:35:16Z
<p>Cedeel: typo correction</p>
<hr />
<div>GRAMPS trunk is the newest version of GRAMPS, but it is under development. You can help by trying this version and reporting feedback and bugs. Before embarking on this you should first read this page.<br />
<br />
A word of caution: trunk is currently considered a ''development version'' and not for use on your real data. You can test trunk on a copy of your data though. See below for more details.<br />
<br />
You should not ''install'' GRAMPS trunk as that will overwrite your regular GRAMPS. However, you can download and compile trunk locally, largely without interfering with your regular GRAMPS. Subtle interactions are easy to resolve for developers. <br />
<br />
== Precautions ==<br />
<br />
GRAMPS trunk should only be used on a copy of your Family Tree data! Here is a step-by-step guide to doing this:<br />
<br />
# Start your old version of GRAMPS<br />
# Export your data using the GRAMPS Package<br />
# Quit your old version of GRAMPS<br />
# Start GRAMPS trunk<br />
# Create a new Family Tree<br />
# Import the GRAMPS package from step 2<br />
<br />
== Can I run my older version of GRAMPS with this new version? ==<br />
<br />
Yes. See installation notes below.<br />
<br />
== I have a suggestion or have found a bug. What do I do? ==<br />
<br />
Please make a note of your Feature Request, or your bug here: http://bugs.gramps-project.org/ This is one of the most important things you can do to help the state of GRAMPS.<br />
<br />
== Can I help with GRAMPS trunk? ==<br />
<br />
Yes! You could:<br />
<br />
# Help write documentation on how to use GRAMPS trunk. See [[Gramps 3.2 Wiki Manual]]<br />
# Help translate GRAMPS into another language. See [[Portal:Translators|Internationalization]]<br />
# Test and follow-up on issues in the tracker. See http://bugs.gramps-project.org/<br />
# Donate money to GRAMPS. See [[GRAMPS:Site_support|GRAMPS Support]]<br />
<br />
== Installing GRAMPS Trunk ==<br />
<br />
Now that you have read all of the precautions, you are ready to begin exploring GRAMPS trunk. <br />
<br />
* '''Windows systems''': follow the directions at http://www.dancingpaper.com/gramps/.<br />
* '''Unix-like systems''': follow the rest of this page.<br />
<br />
The easiest method of getting the beta version is to download it from http://sourceforge.net/project/showfiles.php?group_id=25770 under '''Unstable'''. This is easy to get and install, but is probably a few weeks old. If you want to get the freshest code, you'll have to do a little more work. See [[Running a development version of Gramps]].<br />
<br />
If you are running Linux and a variation of Debian (Ubuntu), then you can download the .deb file and install it directly.<br />
<br />
Otherwise, you should download the tar.gz file. Here is the basic installation instructions, assuming that the tar.gz file is in your current directory:<br />
<br />
tar xfz gramps-2.90.0-beta.tar.gz<br />
cd gramps-2.90.0-beta<br />
./configure --prefix=/usr/local<br />
make<br />
su -c "make install"<br />
<br />
You can then run /usr/local/bin/gramps<br />
<br />
Warning: you will not be able to load translations on /usr/local/share/locale, because you will load /usr/share/locale, which could be translations for stable release (set on gramps.py).<br />
You may generate a custom launcher by adding this line:<br />
export GRAMPSI18N=/usr/local/share/locale<br />
if you want to use an other path, you may add this line:<br />
export GRAMPSI18N=@prefix@/share/locale<br />
on current gramps.sh.in (source file) before compillation and installation.<br />
<br />
== running parallel versions of trunk and branches ==<br />
<br />
As stated in '''Installing GRAMPS 3''', you can only have a dedicated gramps.mo file on /usr/share/local/xx/.. . If you want to have both the trunk and branches version with separate translations, consider using some '''Virtual Machines'''.<br />
<br />
At the moment I experiment with this setup:<br />
* Ubuntu 7.10: running VirtualBox<br />
** VM1: Linux Mint : on this machine I build and installed trunk. This means running ./autogen script, make AND do a make install (as root)<br />
** VM2: Fedora 8 : on this machine I build and installed branches. This means running ./autogen script, make AND do a make install (as root)<br />
<br />
[[Category:Developers/General]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Da:Gramps_3.1_brugsanvisning&diff=14915
Da:Gramps 3.1 brugsanvisning
2009-03-15T17:10:13Z
<p>Cedeel: /* Indholdsfortegnelse */</p>
<hr />
<div>[[Category:Da:Dokumentation]]<br />
Dette er wikihåndbogen til GRAMPS version 3.1. Alle brugere er encouraged til at redigere denne håndbog for at forbedre læsbarheden og brugsværdien. <br />
<br />
{{grampsmanualcopyright}}<br />
<br />
<br />
{{man Da:index|Da:Gramps 3.1 brugsanvisning|Da:GRAMPS 3.1 brugsanvisning - Fordord}}<br />
<br />
<br />
{{languages|Gramps 3.1 Wiki Manual}}<br />
<br />
<br />
==Abstract==<br />
<br />
Brugsanvisningen til GRAMPS er brugervejledningen for at hjælpe brugere til at finde frem i GRAMPS. Alle muligheder er beskrevet, inklusiv de generelle detaljer, nyttige tips, indstillinger, verktøjer, rapporter osv.<br />
<br />
==Indholdsfortegnelse==<br />
<br />
:[[Da:Gramps_3.1_brugsanvisning_-_Forord|Forord]]<br />
::[[Da:Gramps_3.1_brugsanvisning_-_Forord#Hvorfor_bruge_GRAMPS|Hvorfor bruge GRAMPS?]]<br />
::[[Da:Gramps_3.1_brugsanvisning_-_Forord#Typografiske_konventioner| Typografiske konventioner]]<br />
#[[Da:Gramps 3.1 brugsanvisning - Kom i gang|Kom i gang]]<br />
<!-- <br />
<br />
START CHAPTER 2 : THE VIEWS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Hovedvindue|Hovedvindue]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Introduktion|Introduktion]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#De forskellige visninger|De forskellige visninger]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#At skifte visning|At skifte visning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Grampletvisning|Grampletvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Personvisning|Personvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Slægtsskabsvisning|Slægtsskabsvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Familievisning|Familievisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Anetræsvisning|Anetræsvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Hændelsesvisning|Hændelsesvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Kildevisning|Kildevisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Stedvisning|Stedvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Medievisning|Medievisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Arkivvisning|Arkivvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Notevisning|Notevisning]]<br />
<!-- <br />
<br />
START CHAPTER 3 : MANAGE TREES<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer| Administrere familietræer]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Starting a New Database|Starting a New Database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Åbne en database|Åbne en database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Gemme ændringer i din database|Gemme ændringer i din database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Importere data|Importere data]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Eksportere data|Eksportere data]]<br />
<!-- <br />
<br />
START CHAPTER 4 : EDIT DATA<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Indtaste og redigere data: kort|Indtaste og redigere data: kort]]<br />
<!-- <br />
<br />
START CHAPTER 5 : EDIT DATA DETAILED<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Indtaste og redigere data: detaljeret|Indtaste og redigere data: detaljeret]]<br />
<!-- <br />
<br />
START CHAPTER 6 : NAVIGATION<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Navigation|Navigation]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Brug af personvisning|Brug af personvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Brug af familievisning|Brug af familievisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Brug af anevisning|Brug af anevisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Angivelse af proband|Angivelse af proband]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using history-based tools|Using history-based tools]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Bogmærker|Bogmærker]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Finding records|Finding records]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the Clipboard|Using the Clipboard]]<br />
<!-- <br />
<br />
START CHAPTER 7 : GRAMPLETS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Grampletter|Grampletter]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Welcome Gramplet|Welcome Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Top Surnames Gramplet|Top Surnames Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Surname Cloud Gramplet|Surname Cloud Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#TODO Gramplet|TODO Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Statistics Gramplet|Statistics Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Python Gramplet|Python Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#News Gramplet|News Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Session Log Gramplet|Session Log Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Calendar Gramplet|Calendar Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Relatives Gramplet|Relatives Gramplet]]<br />
<!-- <br />
<br />
START CHAPTER 8 : REPORTS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Rapporter| Rapporter]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Generating Reports|Generating Reports]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Substitution Values|Substitution Values]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Books|Books]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Graphical Reports|Graphical Reports]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Ancestor Tree|Ancestor Tree]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Kalender|Kalender]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Descendant Tree|Descendant Tree]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Viftediagram|Viftediagram]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Statistics Chart|Statistics Chart]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Timeline Chart|TimelineChart]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Graphs|Graphs]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Family Lines Graph|Family Lines Graph]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Hourglass Graph|Hourglass Graph]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Relationship Graph|Relationship Graph]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Text Reports|Text Reports]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Ahnentafel Report|Ahnentafel Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Birthday and Anniversary Report|Birthday and Anniversary Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Complete Individual Report|Complete Individual Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Descendant Report|Descendant Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Detailed Ancestral Report|Detailed Ancestral Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Detailed Descendant Report|Detailed Descendant Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#End of Line Report|End of Line Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Family Group Report|Family Group Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Kinship Report|Kinship Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Marker Report|Marker Report]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#View|View]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Not Related|Not Related]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Number of Ancestors|Number of Ancestors]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Summary of the Database|Summary of the database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Web Pages|Web Pages]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Narrated Web Site|Narrated Web Site]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Web Calendar|Web Calendar]]<br />
<!-- <br />
<br />
START CHAPTER 9 : TOOLS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Værktøjer|Værktøjer]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Analysis and Exploration|Analysis and Exploration]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Compare Individual Events|Compare Individual Events]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Interactive Descendant Browser|Interactive Descendant Browser]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Database Processing|Database Processing]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Calculate Estimated Dates|Calculate Estimated Dates]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Edit Database Owner Information|Database Owner Information]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Extract Information from Names|Extract Information from Names]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Extract Place Data from a Place Title|Extract Place Data from a Place Title]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Extract Event Descriptions from Event Data|Extract Event Descriptions from Event Data]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Find Possible Duplicate People...|Find Possible Duplicate People...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Fix Capitalization of Family Names...|Fix Capitalization of Family Names...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Rename Event Types|Rename Event Types]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Reorder GRAMPS ID|Reorder GRAMPS ID]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Database Repair|Database Repair]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Check and repair database|Check and repair database]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Rebuild Reference Maps|Rebuild Reference Maps]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Rebuild Secondary Indices|Rebuild Secondary Indices]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Remove Unused Objects...|Remove Unused Objects...]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Debug|Debug]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Python Evaluation window...|Python Evaluation window...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Reload Plugins|Reload Plugins]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Show uncollected Objects|Show uncollected Objects]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Tilbehør|Tilbehør]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Generate SoundEx codes|Generate SoundEx codes]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Media Manager...|Media Manager...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Relationship calculator|Relationship calculator]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Verify the Data...|Verify the Data]]<br />
<!--<br />
<br />
START CHAPTER 10 : SETTINGS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Indstillinger|Indstillinger]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Preferences|Preferences]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Name Format Editor|Name Format Editor]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Other Settings|Other settings]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Advanced manipulation of settings|Advanced manipulation of settings]]<br />
<!--<br />
<br />
START CHAPTER 10 : FILTERS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Filtre|Filtre]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#General filters| Generelle filtre]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Event filters| Event filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Family filters| Family filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Ancestral filters| Ancestral filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Descendant filters| Descendant filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Relationship filters| Relationship filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Miscellaneous filters| Miscellaneous filters]]<br />
<br />
<br />
<br />
:Appendix A: [[Da:Gramps 3.1 brugsanvisning - OSS|Ofte stillede spørgsmål]]<br />
<br />
:Appendix B: [[Da:Gramps 3.1 brugsanvisning - Keybindings|Keybindings reference]]<br />
<br />
:Appendix C: [[Da:Gramps 3.1 brugsanvisning - Command Line|Command line reference]]<br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Available Options|Available options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Format options|Format options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Opening options|Opening options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Import options|Import options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Export options|Export options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Action options|Action options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#List options|List options]]<br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Operation|Operation]] <br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Examples|Examples]]<br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Environment variables|Environment variables]]<br />
<br />
:Appendix D: [[Da:Gramps 3.1 brugsanvisning - Om| Om GRAMPS]]<br />
<br />
<br />
{{man Da:index|Da:Gramps 3.1 brugsanvisning|Da:Gramps 3.1 brugsanvisning - Preface}}</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Da:Gramps_3.2_brugsanvisning&diff=19967
Da:Gramps 3.2 brugsanvisning
2009-03-15T17:10:13Z
<p>Cedeel: /* Indholdsfortegnelse */</p>
<hr />
<div>[[Category:Da:Dokumentation]]<br />
Dette er wikihåndbogen til GRAMPS version 3.2. Alle brugere er encouraged til at redigere denne håndbog for at forbedre læsbarheden og brugsværdien. <br />
<br />
{{grampsmanualcopyright}}<br />
<br />
<br />
{{man Da:index|Da:Gramps 3.2 brugsanvisning|Da:GRAMPS 3.2 brugsanvisning - Fordord}}<br />
<br />
<br />
{{languages|Gramps 3.2 Wiki Manual}}<br />
<br />
<br />
==Abstract==<br />
<br />
Brugsanvisningen til GRAMPS er brugervejledningen for at hjælpe brugere til at finde frem i GRAMPS. Alle muligheder er beskrevet, inklusiv de generelle detaljer, nyttige tips, indstillinger, verktøjer, rapporter osv.<br />
<br />
==Indholdsfortegnelse==<br />
<br />
:[[Da:Gramps_3.2_brugsanvisning_-_Forord|Forord]]<br />
::[[Da:Gramps_3.2_brugsanvisning_-_Forord#Hvorfor_bruge_GRAMPS|Hvorfor bruge GRAMPS?]]<br />
::[[Da:Gramps_3.2_brugsanvisning_-_Forord#Typografiske_konventioner| Typografiske konventioner]]<br />
#[[Da:Gramps 3.2 brugsanvisning - Kom i gang|Kom i gang]]<br />
<!-- <br />
<br />
START CHAPTER 2 : THE VIEWS<br />
<br />
--><br />
#[[Da:Gramps 3.2 brugsanvisning - Hovedvindue|Hovedvindue]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#Introduktion|Introduktion]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#De forskellige visninger|De forskellige visninger]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#At skifte visning|At skifte visning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#Grampletvisning|Grampletvisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#Personvisning|Personvisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#Slægtsskabsvisning|Slægtsskabsvisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#Familievisning|Familievisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#Anetræsvisning|Anetræsvisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#Hændelsesvisning|Hændelsesvisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#Kildevisning|Kildevisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#Stedvisning|Stedvisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#Medievisning|Medievisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#Arkivvisning|Arkivvisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Hovedvindue#Notevisning|Notevisning]]<br />
<!-- <br />
<br />
START CHAPTER 3 : MANAGE TREES<br />
<br />
--><br />
#[[Da:Gramps 3.2 brugsanvisning - Administrere familietræer| Administrere familietræer]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Administrere familietræer#Starting a New Database|Starting a New Database]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Administrere familietræer#Åbne en database|Åbne en database]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Administrere familietræer#Gemme ændringer i din database|Gemme ændringer i din database]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Administrere familietræer#Importere data|Importere data]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Administrere familietræer#Eksportere data|Eksportere data]]<br />
<!-- <br />
<br />
START CHAPTER 4 : EDIT DATA<br />
<br />
--><br />
#[[Da:Gramps 3.2 brugsanvisning - Indtaste og redigere data: kort|Indtaste og redigere data: kort]]<br />
<!-- <br />
<br />
START CHAPTER 5 : EDIT DATA DETAILED<br />
<br />
--><br />
#[[Da:Gramps 3.2 brugsanvisning - Indtaste og redigere data: detaljeret|Indtaste og redigere data: detaljeret]]<br />
<!-- <br />
<br />
START CHAPTER 6 : NAVIGATION<br />
<br />
--><br />
#[[Da:Gramps 3.2 brugsanvisning - Navigation|Navigation]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Navigation#Brug af personvisning|Brug af personvisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Navigation#Brug af familievisning|Brug af familievisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Navigation#Brug af anevisning|Brug af anevisning]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Navigation#Angivelse af proband|Angivelse af proband]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Navigation#Using history-based tools|Using history-based tools]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Navigation#Bogmærker|Bogmærker]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Navigation#Finding records|Finding records]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Navigation#Using the Clipboard|Using the Clipboard]]<br />
<!-- <br />
<br />
START CHAPTER 7 : GRAMPLETS<br />
<br />
--><br />
#[[Da:Gramps 3.2 brugsanvisning - Grampletter|Grampletter]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Gramplets#Welcome Gramplet|Welcome Gramplet]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Gramplets#Top Surnames Gramplet|Top Surnames Gramplet]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Gramplets#Surname Cloud Gramplet|Surname Cloud Gramplet]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Gramplets#TODO Gramplet|TODO Gramplet]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Gramplets#Statistics Gramplet|Statistics Gramplet]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Gramplets#Python Gramplet|Python Gramplet]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Gramplets#News Gramplet|News Gramplet]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Gramplets#Session Log Gramplet|Session Log Gramplet]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Gramplets#Calendar Gramplet|Calendar Gramplet]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Gramplets#Relatives Gramplet|Relatives Gramplet]]<br />
<!-- <br />
<br />
START CHAPTER 8 : REPORTS<br />
<br />
--><br />
#[[Da:Gramps 3.2 brugsanvisning - Rapporter| Rapporter]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Rapporter#Generating Reports|Generating Reports]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Rapporter#Substitution Values|Substitution Values]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Rapporter#Books|Books]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Rapporter#Graphical Reports|Graphical Reports]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Ancestor Tree|Ancestor Tree]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Kalender|Kalender]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Descendant Tree|Descendant Tree]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Viftediagram|Viftediagram]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Statistics Chart|Statistics Chart]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Timeline Chart|TimelineChart]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Rapporter#Graphs|Graphs]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Family Lines Graph|Family Lines Graph]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Hourglass Graph|Hourglass Graph]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Relationship Graph|Relationship Graph]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Rapporter#Text Reports|Text Reports]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Ahnentafel Report|Ahnentafel Report]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Birthday and Anniversary Report|Birthday and Anniversary Report]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Complete Individual Report|Complete Individual Report]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Descendant Report|Descendant Report]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Detailed Ancestral Report|Detailed Ancestral Report]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Detailed Descendant Report|Detailed Descendant Report]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#End of Line Report|End of Line Report]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Family Group Report|Family Group Report]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Kinship Report|Kinship Report]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Marker Report|Marker Report]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Rapporter#View|View]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Not Related|Not Related]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Number of Ancestors|Number of Ancestors]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Summary of the Database|Summary of the database]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Rapporter#Web Pages|Web Pages]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Narrated Web Site|Narrated Web Site]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Rapporter#Web Calendar|Web Calendar]]<br />
<!-- <br />
<br />
START CHAPTER 9 : TOOLS<br />
<br />
--><br />
#[[Da:Gramps 3.2 brugsanvisning - Værktøjer|Værktøjer]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Analysis and Exploration|Analysis and Exploration]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Compare Individual Events|Compare Individual Events]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Interactive Descendant Browser|Interactive Descendant Browser]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Database Processing|Database Processing]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Calculate Estimated Dates|Calculate Estimated Dates]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Edit Database Owner Information|Database Owner Information]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Extract Information from Names|Extract Information from Names]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Extract Place Data from a Place Title|Extract Place Data from a Place Title]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Extract Event Descriptions from Event Data|Extract Event Descriptions from Event Data]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Find Possible Duplicate People...|Find Possible Duplicate People...]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Fix Capitalization of Family Names...|Fix Capitalization of Family Names...]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Rename Event Types|Rename Event Types]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Reorder GRAMPS ID|Reorder GRAMPS ID]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Database Repair|Database Repair]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Check and repair database|Check and repair database]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Rebuild Reference Maps|Rebuild Reference Maps]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Rebuild Secondary Indices|Rebuild Secondary Indices]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Remove Unused Objects...|Remove Unused Objects...]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Debug|Debug]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Python Evaluation window...|Python Evaluation window...]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Reload Plugins|Reload Plugins]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Show uncollected Objects|Show uncollected Objects]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Tilbehør|Tilbehør]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Generate SoundEx codes|Generate SoundEx codes]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Media Manager...|Media Manager...]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Relationship calculator|Relationship calculator]]<br />
###[[Da:Gramps 3.2 brugsanvisning - Værktøjer#Verify the Data...|Verify the Data]]<br />
<!--<br />
<br />
START CHAPTER 10 : SETTINGS<br />
<br />
--><br />
#[[Da:Gramps 3.2 brugsanvisning - Indstillinger|Indstillinger]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Indstillinger#Preferences|Preferences]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Indstillinger#Name Format Editor|Name Format Editor]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Indstillinger#Other Settings|Other settings]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Indstillinger#Advanced manipulation of settings|Advanced manipulation of settings]]<br />
<!--<br />
<br />
START CHAPTER 10 : FILTERS<br />
<br />
--><br />
#[[Da:Gramps 3.2 brugsanvisning - Filtre|Filtre]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Filters#General filters| Generelle filtre]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Filters#Event filters| Event filters]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Filters#Family filters| Family filters]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Filters#Ancestral filters| Ancestral filters]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Filters#Descendant filters| Descendant filters]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Filters#Relationship filters| Relationship filters]]<br />
##[[Da:Gramps 3.2 brugsanvisning - Filters#Miscellaneous filters| Miscellaneous filters]]<br />
<br />
<br />
<br />
:Appendix A: [[Da:Gramps 3.2 brugsanvisning - OSS|Ofte stillede spørgsmål]]<br />
<br />
:Appendix B: [[Da:Gramps 3.2 brugsanvisning - Keybindings|Keybindings reference]]<br />
<br />
:Appendix C: [[Da:Gramps 3.2 brugsanvisning - Command Line|Command line reference]]<br />
:::[[Da:Gramps 3.2 brugsanvisning - Command Line#Available Options|Available options]]<br />
::::[[Da:Gramps 3.2 brugsanvisning - Command Line#Format options|Format options]]<br />
::::[[Da:Gramps 3.2 brugsanvisning - Command Line#Opening options|Opening options]]<br />
::::[[Da:Gramps 3.2 brugsanvisning - Command Line#Import options|Import options]]<br />
::::[[Da:Gramps 3.2 brugsanvisning - Command Line#Export options|Export options]]<br />
::::[[Da:Gramps 3.2 brugsanvisning - Command Line#Action options|Action options]]<br />
::::[[Da:Gramps 3.2 brugsanvisning - Command Line#List options|List options]]<br />
:::[[Da:Gramps 3.2 brugsanvisning - Command Line#Operation|Operation]] <br />
:::[[Da:Gramps 3.2 brugsanvisning - Command Line#Examples|Examples]]<br />
:::[[Da:Gramps 3.2 brugsanvisning - Command Line#Environment variables|Environment variables]]<br />
<br />
:Appendix D: [[Da:Gramps 3.2 brugsanvisning - Om| Om GRAMPS]]<br />
<br />
<br />
{{man Da:index|Da:Gramps 3.2 brugsanvisning|Da:Gramps 3.2 brugsanvisning - Preface}}</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Da:Gramps_3.1_brugsanvisning&diff=14914
Da:Gramps 3.1 brugsanvisning
2009-03-15T17:06:30Z
<p>Cedeel: /* Indholdsfortegnelse */</p>
<hr />
<div>[[Category:Da:Dokumentation]]<br />
Dette er wikihåndbogen til GRAMPS version 3.1. Alle brugere er encouraged til at redigere denne håndbog for at forbedre læsbarheden og brugsværdien. <br />
<br />
{{grampsmanualcopyright}}<br />
<br />
<br />
{{man Da:index|Da:Gramps 3.1 brugsanvisning|Da:GRAMPS 3.1 brugsanvisning - Fordord}}<br />
<br />
<br />
{{languages|Gramps 3.1 Wiki Manual}}<br />
<br />
<br />
==Abstract==<br />
<br />
Brugsanvisningen til GRAMPS er brugervejledningen for at hjælpe brugere til at finde frem i GRAMPS. Alle muligheder er beskrevet, inklusiv de generelle detaljer, nyttige tips, indstillinger, verktøjer, rapporter osv.<br />
<br />
==Indholdsfortegnelse==<br />
<br />
:[[Da:Gramps_3.1_brugsanvisning_-_Forord|Forord]]<br />
::[[Da:Gramps_3.1_brugsanvisning_-_Forord#Hvorfor_bruge_GRAMPS|Hvorfor bruge GRAMPS?]]<br />
::[[Da:Gramps_3.1_brugsanvisning_-_Forord#Typografiske_konventioner| Typografiske konventioner]]<br />
#[[Da:Gramps 3.1 brugsanvisning - Kom i gang|Kom i gang]]<br />
<!-- <br />
<br />
START CHAPTER 2 : THE VIEWS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Hovedvindue|Hovedvindue]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Introduktion|Introduktion]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#De forskellige visninger|De forskellige visninger]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#At skifte visning|At skifte visning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Grampletvisning|Grampletvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Personvisning|Personvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Slægtsskabsvisning|Slægtsskabsvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Familievisning|Familievisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Anetræsvisning|Anetræsvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Hændelsesvisning|Hændelsesvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Kildevisning|Kildevisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Stedvisning|Stedvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Medievisning|Medievisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Arkivvisning|Arkivvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Notevisning|Notevisning]]<br />
<!-- <br />
<br />
START CHAPTER 3 : MANAGE TREES<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer| Administrere familietræer]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Starting a New Database|Starting a New Database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Åbne en database|Åbne en database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Gemme ændringer i din database|Gemme ændringer i din database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Importere data|Importere data]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Eksportere data|Eksportere data]]<br />
<!-- <br />
<br />
START CHAPTER 4 : EDIT DATA<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Indtaste og redigere data: kort|Indtaste og redigere data: kort]]<br />
<!-- <br />
<br />
START CHAPTER 5 : EDIT DATA DETAILED<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Indtaste og redigere data: detaljeret|Indtaste og redigere data: detaljeret]]<br />
<!-- <br />
<br />
START CHAPTER 6 : NAVIGATION<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Navigation|Navigation]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the People View|Using the People View]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the Family View|Using the Family View]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the Pedigree View|Using the Pedigree View]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Setting the Home Person|Setting the Home Person]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using history-based tools|Using history-based tools]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Bookmarks|Bookmarks]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Finding records|Finding records]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the Clipboard|Using the Clipboard]]<br />
<!-- <br />
<br />
START CHAPTER 7 : GRAMPLETS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Grampletter|Grampletter]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Welcome Gramplet|Welcome Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Top Surnames Gramplet|Top Surnames Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Surname Cloud Gramplet|Surname Cloud Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#TODO Gramplet|TODO Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Statistics Gramplet|Statistics Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Python Gramplet|Python Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#News Gramplet|News Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Session Log Gramplet|Session Log Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Calendar Gramplet|Calendar Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Relatives Gramplet|Relatives Gramplet]]<br />
<!-- <br />
<br />
START CHAPTER 8 : REPORTS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Rapporter| Rapporter]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Generating Reports|Generating Reports]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Substitution Values|Substitution Values]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Books|Books]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Graphical Reports|Graphical Reports]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Ancestor Tree|Ancestor Tree]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Kalender|Kalender]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Descendant Tree|Descendant Tree]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Viftediagram|Viftediagram]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Statistics Chart|Statistics Chart]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Timeline Chart|TimelineChart]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Graphs|Graphs]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Family Lines Graph|Family Lines Graph]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Hourglass Graph|Hourglass Graph]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Relationship Graph|Relationship Graph]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Text Reports|Text Reports]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Ahnentafel Report|Ahnentafel Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Birthday and Anniversary Report|Birthday and Anniversary Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Complete Individual Report|Complete Individual Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Descendant Report|Descendant Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Detailed Ancestral Report|Detailed Ancestral Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Detailed Descendant Report|Detailed Descendant Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#End of Line Report|End of Line Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Family Group Report|Family Group Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Kinship Report|Kinship Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Marker Report|Marker Report]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#View|View]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Not Related|Not Related]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Number of Ancestors|Number of Ancestors]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Summary of the Database|Summary of the database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Rapporter#Web Pages|Web Pages]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Narrated Web Site|Narrated Web Site]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Rapporter#Web Calendar|Web Calendar]]<br />
<!-- <br />
<br />
START CHAPTER 9 : TOOLS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Værktøjer|Værktøjer]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Analysis and Exploration|Analysis and Exploration]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Compare Individual Events|Compare Individual Events]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Interactive Descendant Browser|Interactive Descendant Browser]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Database Processing|Database Processing]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Calculate Estimated Dates|Calculate Estimated Dates]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Edit Database Owner Information|Database Owner Information]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Extract Information from Names|Extract Information from Names]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Extract Place Data from a Place Title|Extract Place Data from a Place Title]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Extract Event Descriptions from Event Data|Extract Event Descriptions from Event Data]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Find Possible Duplicate People...|Find Possible Duplicate People...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Fix Capitalization of Family Names...|Fix Capitalization of Family Names...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Rename Event Types|Rename Event Types]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Reorder GRAMPS ID|Reorder GRAMPS ID]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Database Repair|Database Repair]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Check and repair database|Check and repair database]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Rebuild Reference Maps|Rebuild Reference Maps]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Rebuild Secondary Indices|Rebuild Secondary Indices]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Remove Unused Objects...|Remove Unused Objects...]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Debug|Debug]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Python Evaluation window...|Python Evaluation window...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Reload Plugins|Reload Plugins]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Show uncollected Objects|Show uncollected Objects]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Tilbehør|Tilbehør]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Generate SoundEx codes|Generate SoundEx codes]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Media Manager...|Media Manager...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Relationship calculator|Relationship calculator]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Verify the Data...|Verify the Data]]<br />
<!--<br />
<br />
START CHAPTER 10 : SETTINGS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Indstillinger|Indstillinger]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Preferences|Preferences]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Name Format Editor|Name Format Editor]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Other Settings|Other settings]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Advanced manipulation of settings|Advanced manipulation of settings]]<br />
<!--<br />
<br />
START CHAPTER 10 : FILTERS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Filtre|Filtre]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#General filters| Generelle filtre]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Event filters| Event filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Family filters| Family filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Ancestral filters| Ancestral filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Descendant filters| Descendant filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Relationship filters| Relationship filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Miscellaneous filters| Miscellaneous filters]]<br />
<br />
<br />
<br />
:Appendix A: [[Da:Gramps 3.1 brugsanvisning - OSS|Ofte stillede spørgsmål]]<br />
<br />
:Appendix B: [[Da:Gramps 3.1 brugsanvisning - Keybindings|Keybindings reference]]<br />
<br />
:Appendix C: [[Da:Gramps 3.1 brugsanvisning - Command Line|Command line reference]]<br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Available Options|Available options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Format options|Format options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Opening options|Opening options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Import options|Import options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Export options|Export options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Action options|Action options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#List options|List options]]<br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Operation|Operation]] <br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Examples|Examples]]<br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Environment variables|Environment variables]]<br />
<br />
:Appendix D: [[Da:Gramps 3.1 brugsanvisning - Om| Om GRAMPS]]<br />
<br />
<br />
{{man Da:index|Da:Gramps 3.1 brugsanvisning|Da:Gramps 3.1 brugsanvisning - Preface}}</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Gramps_3.1_Wiki_Manual/da&diff=14745
Gramps 3.1 Wiki Manual/da
2009-03-10T15:20:02Z
<p>Cedeel: Redirecting to Da:Gramps 3.1 brugsanvisning</p>
<hr />
<div>#REDIRECT [[Da:Gramps_3.1_brugsanvisning]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Gramps_3.2_Wiki_Manual/da&diff=20160
Gramps 3.2 Wiki Manual/da
2009-03-10T15:20:02Z
<p>Cedeel: Redirecting to Da:Gramps 3.2 brugsanvisning</p>
<hr />
<div>#REDIRECT [[Da:Gramps_3.2_brugsanvisning]]</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Template:Man_index/da&diff=14744
Template:Man index/da
2009-03-10T15:17:36Z
<p>Cedeel: </p>
<hr />
<div>[[Category:Nb:Documentation]]<br />
{|style="width:100%;margin-top:+.7em;margin-bottom:+.7em;background-color: #ffffff;border:1px solid #ccc; padding: 5px" align="center"<br />
|-<br />
|align="left" width="33%" style="font-size:120%"|[[{{{1}}}| '''Previous''' ]]<br />
|align="center" width="34%" style="font-size:120%"|[[Da:Gramps 3.1 brugsanvisning| '''Index''']]<br />
|align="right" width="33%" style="font-size:120%"|[[{{{2}}} | ''' Next''' ]]<br />
|}<br />
<noinclude><br />
This produces the index page on the wiki.<br />
Like this:<br />
<br />
{{man Da:index|Gramps-index|Gramps-getting-started/nb}}<br />
</noinclude></div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Da:Gramps_3.1_brugsanvisning&diff=14743
Da:Gramps 3.1 brugsanvisning
2009-03-10T15:16:18Z
<p>Cedeel: /* Abstract */</p>
<hr />
<div>[[Category:Da:Dokumentation]]<br />
Dette er wikihåndbogen til GRAMPS version 3.1. Alle brugere er encouraged til at redigere denne håndbog for at forbedre læsbarheden og brugsværdien. <br />
<br />
{{grampsmanualcopyright}}<br />
<br />
<br />
{{man Da:index|Da:Gramps 3.1 brugsanvisning|Da:GRAMPS 3.1 brugsanvisning - Fordord}}<br />
<br />
<br />
{{languages|Gramps 3.1 Wiki Manual}}<br />
<br />
<br />
==Abstract==<br />
<br />
Brugsanvisningen til GRAMPS er brugervejledningen for at hjælpe brugere til at finde frem i GRAMPS. Alle muligheder er beskrevet, inklusiv de generelle detaljer, nyttige tips, indstillinger, verktøjer, rapporter osv.<br />
<br />
==Indholdsfortegnelse==<br />
<br />
:[[Da:Gramps_3.1_brugsanvisning_-_Forord|Forord]]<br />
::[[Da:Gramps_3.1_brugsanvisning_-_Forord#Hvorfor_bruge_GRAMPS|Hvorfor bruge GRAMPS?]]<br />
::[[Da:Gramps_3.1_brugsanvisning_-_Forord#Typografiske_konventioner| Typografiske konventioner]]<br />
#[[Da:Gramps 3.1 brugsanvisning - Kom i gang|Kom i gang]]<br />
<!-- <br />
<br />
START CHAPTER 2 : THE VIEWS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Hovedvindue|Hovedvindue]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Introduktion|Introduktion]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#De forskellige visninger|De forskellige visninger]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#At skifte visning|At skifte visning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Grampletvisning|Grampletvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Personvisning|Personvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Slægtsskabsvisning|Slægtsskabsvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Familievisning|Familievisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Anetræsvisning|Anetræsvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Hændelsesvisning|Hændelsesvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Kildevisning|Kildevisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Stedvisning|Stedvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Medievisning|Medievisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Arkivvisning|Arkivvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Notevisning|Notevisning]]<br />
<!-- <br />
<br />
START CHAPTER 3 : MANAGE TREES<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer| Administrere familietræer]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Starting a New Database|Starting a New Database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Åbne en database|Åbne en database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Gemme ændringer i din database|Gemme ændringer i din database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Importere data|Importere data]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Eksportere data|Eksportere data]]<br />
<!-- <br />
<br />
START CHAPTER 4 : EDIT DATA<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Indtaste og redigere data: kort|Indtaste og redigere data: kort]]<br />
<!-- <br />
<br />
START CHAPTER 5 : EDIT DATA DETAILED<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Indtaste og redigere data: detaljeret|Indtaste og redigere data: detaljeret]]<br />
<!-- <br />
<br />
START CHAPTER 6 : NAVIGATION<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Navigation|Navigation]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the People View|Using the People View]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the Family View|Using the Family View]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the Pedigree View|Using the Pedigree View]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Setting the Home Person|Setting the Home Person]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using history-based tools|Using history-based tools]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Bookmarks|Bookmarks]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Finding records|Finding records]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the Clipboard|Using the Clipboard]]<br />
<!-- <br />
<br />
START CHAPTER 7 : GRAMPLETS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Gramplets|Gramplets]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Welcome Gramplet|Welcome Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Top Surnames Gramplet|Top Surnames Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Surname Cloud Gramplet|Surname Cloud Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#TODO Gramplet|TODO Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Statistics Gramplet|Statistics Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Python Gramplet|Python Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#News Gramplet|News Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Session Log Gramplet|Session Log Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Calendar Gramplet|Calendar Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Relatives Gramplet|Relatives Gramplet]]<br />
<!-- <br />
<br />
START CHAPTER 8 : REPORTS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Rapporter| Rapporter]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Generating Reports|Generating Reports]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Substitution Values|Substitution Values]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Books|Books]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Graphical Reports|Graphical Reports]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Ancestor Tree|Ancestor Tree]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Calendar|Calendar]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Descendant Tree|Descendant Tree]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Fan Chart|Fan Chart]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Statistics Chart|Statistics Chart]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Timeline Chart|TimelineChart]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Graphs|Graphs]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Family Lines Graph|Family Lines Graph]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Hourglass Graph|Hourglass Graph]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Relationship Graph|Relationship Graph]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Text Reports|Text Reports]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Ahnentafel Report|Ahnentafel Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Birthday and Anniversary Report|Birthday and Anniversary Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Complete Individual Report|Complete Individual Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Descendant Report|Descendant Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Detailed Ancestral Report|Detailed Ancestral Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Detailed Descendant Report|Detailed Descendant Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#End of Line Report|End of Line Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Family Group Report|Family Group Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Kinship Report|Kinship Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Marker Report|Marker Report]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#View|View]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Not Related|Not Related]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Number of Ancestors|Number of Ancestors]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Summary of the Database|Summary of the database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Web Pages|Web Pages]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Narrated Web Site|Narrated Web Site]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Web Calendar|Web Calendar]]<br />
<!-- <br />
<br />
START CHAPTER 9 : TOOLS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Værktøjer|Værktøjer]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Analysis and Exploration|Analysis and Exploration]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Compare Individual Events|Compare Individual Events]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Interactive Descendant Browser|Interactive Descendant Browser]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Database Processing|Database Processing]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Calculate Estimated Dates|Calculate Estimated Dates]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Edit Database Owner Information|Database Owner Information]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Extract Information from Names|Extract Information from Names]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Extract Place Data from a Place Title|Extract Place Data from a Place Title]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Extract Event Descriptions from Event Data|Extract Event Descriptions from Event Data]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Find Possible Duplicate People...|Find Possible Duplicate People...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Fix Capitalization of Family Names...|Fix Capitalization of Family Names...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Rename Event Types|Rename Event Types]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Reorder GRAMPS ID|Reorder GRAMPS ID]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Database Repair|Database Repair]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Check and repair database|Check and repair database]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Rebuild Reference Maps|Rebuild Reference Maps]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Rebuild Secondary Indices|Rebuild Secondary Indices]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Remove Unused Objects...|Remove Unused Objects...]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Debug|Debug]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Python Evaluation window...|Python Evaluation window...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Reload Plugins|Reload Plugins]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Show uncollected Objects|Show uncollected Objects]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Tilbehør|Tilbehør]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Generate SoundEx codes|Generate SoundEx codes]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Media Manager...|Media Manager...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Relationship calculator|Relationship calculator]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Verify the Data...|Verify the Data]]<br />
<!--<br />
<br />
START CHAPTER 10 : SETTINGS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Indstillinger|Indstillinger]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Preferences|Preferences]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Name Format Editor|Name Format Editor]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Other Settings|Other settings]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Advanced manipulation of settings|Advanced manipulation of settings]]<br />
<!--<br />
<br />
START CHAPTER 10 : FILTERS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Filtre|Filtre]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#General filters| Generelle filtre]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Event filters| Event filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Family filters| Family filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Ancestral filters| Ancestral filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Descendant filters| Descendant filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Relationship filters| Relationship filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Miscellaneous filters| Miscellaneous filters]]<br />
<br />
<br />
<br />
:Appendix A: [[Da:Gramps 3.1 brugsanvisning - OSS|Ofte stillede spørgsmål]]<br />
<br />
:Appendix B: [[Da:Gramps 3.1 brugsanvisning - Keybindings|Keybindings reference]]<br />
<br />
:Appendix C: [[Da:Gramps 3.1 brugsanvisning - Command Line|Command line reference]]<br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Available Options|Available options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Format options|Format options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Opening options|Opening options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Import options|Import options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Export options|Export options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Action options|Action options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#List options|List options]]<br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Operation|Operation]] <br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Examples|Examples]]<br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Environment variables|Environment variables]]<br />
<br />
:Appendix D: [[Da:Gramps 3.1 brugsanvisning - Om| Om GRAMPS]]<br />
<br />
<br />
{{man Da:index|Da:Gramps 3.1 brugsanvisning|Da:Gramps 3.1 brugsanvisning - Preface}}</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Da:Gramps_3.1_brugsanvisning&diff=14742
Da:Gramps 3.1 brugsanvisning
2009-03-10T15:14:08Z
<p>Cedeel: New page: Category:Da:Dokumentation Dette er wikihåndbogen til GRAMPS version 3.1. Alle brugere er encouraged til at redigere denne håndbog for at forbedre læsbarheden og brugsværdien. {{g...</p>
<hr />
<div>[[Category:Da:Dokumentation]]<br />
Dette er wikihåndbogen til GRAMPS version 3.1. Alle brugere er encouraged til at redigere denne håndbog for at forbedre læsbarheden og brugsværdien. <br />
<br />
{{grampsmanualcopyright}}<br />
<br />
<br />
{{man Da:index|Da:Gramps 3.1 brugsanvisning|Da:GRAMPS 3.1 brugsanvisning - Fordord}}<br />
<br />
<br />
{{languages|Gramps 3.1 Wiki Manual}}<br />
<br />
<br />
==Abstract==<br />
<br />
Brugsanvisningen til GRAMPS er brukerveiledningen for å hjelpe brukere til å finne frem i GRAMPS. Alle muligheter er beskrevet, inkludert de generelle detaljene, nyttige tips, innstillinger, verktøy, rapporter osv.<br />
<br />
==Indholdsfortegnelse==<br />
<br />
:[[Da:Gramps_3.1_brugsanvisning_-_Forord|Forord]]<br />
::[[Da:Gramps_3.1_brugsanvisning_-_Forord#Hvorfor_bruge_GRAMPS|Hvorfor bruge GRAMPS?]]<br />
::[[Da:Gramps_3.1_brugsanvisning_-_Forord#Typografiske_konventioner| Typografiske konventioner]]<br />
#[[Da:Gramps 3.1 brugsanvisning - Kom i gang|Kom i gang]]<br />
<!-- <br />
<br />
START CHAPTER 2 : THE VIEWS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Hovedvindue|Hovedvindue]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Introduktion|Introduktion]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#De forskellige visninger|De forskellige visninger]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#At skifte visning|At skifte visning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Grampletvisning|Grampletvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Personvisning|Personvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Slægtsskabsvisning|Slægtsskabsvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Familievisning|Familievisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Anetræsvisning|Anetræsvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Hændelsesvisning|Hændelsesvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Kildevisning|Kildevisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Stedvisning|Stedvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Medievisning|Medievisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Arkivvisning|Arkivvisning]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Hovedvindue#Notevisning|Notevisning]]<br />
<!-- <br />
<br />
START CHAPTER 3 : MANAGE TREES<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer| Administrere familietræer]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Starting a New Database|Starting a New Database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Åbne en database|Åbne en database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Gemme ændringer i din database|Gemme ændringer i din database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Importere data|Importere data]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Administrere familietræer#Eksportere data|Eksportere data]]<br />
<!-- <br />
<br />
START CHAPTER 4 : EDIT DATA<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Indtaste og redigere data: kort|Indtaste og redigere data: kort]]<br />
<!-- <br />
<br />
START CHAPTER 5 : EDIT DATA DETAILED<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Indtaste og redigere data: detaljeret|Indtaste og redigere data: detaljeret]]<br />
<!-- <br />
<br />
START CHAPTER 6 : NAVIGATION<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Navigation|Navigation]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the People View|Using the People View]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the Family View|Using the Family View]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the Pedigree View|Using the Pedigree View]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Setting the Home Person|Setting the Home Person]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using history-based tools|Using history-based tools]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Bookmarks|Bookmarks]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Finding records|Finding records]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Navigation#Using the Clipboard|Using the Clipboard]]<br />
<!-- <br />
<br />
START CHAPTER 7 : GRAMPLETS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Gramplets|Gramplets]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Welcome Gramplet|Welcome Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Top Surnames Gramplet|Top Surnames Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Surname Cloud Gramplet|Surname Cloud Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#TODO Gramplet|TODO Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Statistics Gramplet|Statistics Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Python Gramplet|Python Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#News Gramplet|News Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Session Log Gramplet|Session Log Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Calendar Gramplet|Calendar Gramplet]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Gramplets#Relatives Gramplet|Relatives Gramplet]]<br />
<!-- <br />
<br />
START CHAPTER 8 : REPORTS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Rapporter| Rapporter]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Generating Reports|Generating Reports]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Substitution Values|Substitution Values]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Books|Books]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Graphical Reports|Graphical Reports]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Ancestor Tree|Ancestor Tree]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Calendar|Calendar]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Descendant Tree|Descendant Tree]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Fan Chart|Fan Chart]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Statistics Chart|Statistics Chart]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Timeline Chart|TimelineChart]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Graphs|Graphs]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Family Lines Graph|Family Lines Graph]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Hourglass Graph|Hourglass Graph]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Relationship Graph|Relationship Graph]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Text Reports|Text Reports]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Ahnentafel Report|Ahnentafel Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Birthday and Anniversary Report|Birthday and Anniversary Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Complete Individual Report|Complete Individual Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Descendant Report|Descendant Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Detailed Ancestral Report|Detailed Ancestral Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Detailed Descendant Report|Detailed Descendant Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#End of Line Report|End of Line Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Family Group Report|Family Group Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Kinship Report|Kinship Report]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Marker Report|Marker Report]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#View|View]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Not Related|Not Related]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Number of Ancestors|Number of Ancestors]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Summary of the Database|Summary of the database]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Reports#Web Pages|Web Pages]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Narrated Web Site|Narrated Web Site]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Reports#Web Calendar|Web Calendar]]<br />
<!-- <br />
<br />
START CHAPTER 9 : TOOLS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Værktøjer|Værktøjer]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Analysis and Exploration|Analysis and Exploration]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Compare Individual Events|Compare Individual Events]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Interactive Descendant Browser|Interactive Descendant Browser]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Database Processing|Database Processing]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Calculate Estimated Dates|Calculate Estimated Dates]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Edit Database Owner Information|Database Owner Information]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Extract Information from Names|Extract Information from Names]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Extract Place Data from a Place Title|Extract Place Data from a Place Title]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Extract Event Descriptions from Event Data|Extract Event Descriptions from Event Data]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Find Possible Duplicate People...|Find Possible Duplicate People...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Fix Capitalization of Family Names...|Fix Capitalization of Family Names...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Rename Event Types|Rename Event Types]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Reorder GRAMPS ID|Reorder GRAMPS ID]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Database Repair|Database Repair]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Check and repair database|Check and repair database]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Rebuild Reference Maps|Rebuild Reference Maps]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Rebuild Secondary Indices|Rebuild Secondary Indices]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Remove Unused Objects...|Remove Unused Objects...]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Debug|Debug]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Python Evaluation window...|Python Evaluation window...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Reload Plugins|Reload Plugins]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Show uncollected Objects|Show uncollected Objects]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Tilbehør|Tilbehør]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Generate SoundEx codes|Generate SoundEx codes]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Media Manager...|Media Manager...]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Relationship calculator|Relationship calculator]]<br />
###[[Da:Gramps 3.1 brugsanvisning - Værktøjer#Verify the Data...|Verify the Data]]<br />
<!--<br />
<br />
START CHAPTER 10 : SETTINGS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Indstillinger|Indstillinger]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Preferences|Preferences]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Name Format Editor|Name Format Editor]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Other Settings|Other settings]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Indstillinger#Advanced manipulation of settings|Advanced manipulation of settings]]<br />
<!--<br />
<br />
START CHAPTER 10 : FILTERS<br />
<br />
--><br />
#[[Da:Gramps 3.1 brugsanvisning - Filtre|Filtre]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#General filters| Generelle filtre]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Event filters| Event filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Family filters| Family filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Ancestral filters| Ancestral filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Descendant filters| Descendant filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Relationship filters| Relationship filters]]<br />
##[[Da:Gramps 3.1 brugsanvisning - Filters#Miscellaneous filters| Miscellaneous filters]]<br />
<br />
<br />
<br />
:Appendix A: [[Da:Gramps 3.1 brugsanvisning - OSS|Ofte stillede spørgsmål]]<br />
<br />
:Appendix B: [[Da:Gramps 3.1 brugsanvisning - Keybindings|Keybindings reference]]<br />
<br />
:Appendix C: [[Da:Gramps 3.1 brugsanvisning - Command Line|Command line reference]]<br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Available Options|Available options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Format options|Format options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Opening options|Opening options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Import options|Import options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Export options|Export options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#Action options|Action options]]<br />
::::[[Da:Gramps 3.1 brugsanvisning - Command Line#List options|List options]]<br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Operation|Operation]] <br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Examples|Examples]]<br />
:::[[Da:Gramps 3.1 brugsanvisning - Command Line#Environment variables|Environment variables]]<br />
<br />
:Appendix D: [[Da:Gramps 3.1 brugsanvisning - Om| Om GRAMPS]]<br />
<br />
<br />
{{man Da:index|Da:Gramps 3.1 brugsanvisning|Da:Gramps 3.1 brugsanvisning - Preface}}</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=Template:Man_index/da&diff=14741
Template:Man index/da
2009-03-10T15:08:43Z
<p>Cedeel: New page: Category:Nb:Documentation {|style="width:100%;margin-top:+.7em;margin-bottom:+.7em;background-color: #ffffff;border:1px solid #ccc; padding: 5px" align="center" |- |align="left" width=...</p>
<hr />
<div>[[Category:Nb:Documentation]]<br />
{|style="width:100%;margin-top:+.7em;margin-bottom:+.7em;background-color: #ffffff;border:1px solid #ccc; padding: 5px" align="center"<br />
|-<br />
|align="left" width="33%" style="font-size:120%"|[[{{{1}}}| '''Previous''' ]]<br />
|align="center" width="34%" style="font-size:120%"|[[Da:Gramps 3.0 brugsanvisning| '''Index''']]<br />
|align="right" width="33%" style="font-size:120%"|[[{{{2}}} | ''' Next''' ]]<br />
|}<br />
<noinclude><br />
This produces the index page on the wiki.<br />
Like this:<br />
<br />
{{man Da:index|Gramps-index|Gramps-getting-started/nb}}<br />
</noinclude></div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=User_manual_translations&diff=14740
User manual translations
2009-03-10T14:26:39Z
<p>Cedeel: /* GRAMPS 3.1.x Manual */</p>
<hr />
<div>[[Category:Documentation]]<br />
From GRAMPS 3.0.x, the manual is no longer distributed with GRAMPS, and only available online, so you need an internet connection to be able to read the manual. It is is available from within GRAMPS by pressing F1, or through the help menu, and provides in depth instructions on the use of GRAMPS.<br />
<br />
==GRAMPS 3.1.x Manual==<br />
<br />
The 3.1.x Manual is at the moment only available in wiki format. <br />
<br />
NOTE: As at 23 January 2009, these pages have simply been 'rolled over' from the 3.0 manuals, with search/replace to make the titles and references to 3.1. Only after translators and developers have completed more work will they be better representations of version 3.1...<br />
<br />
* English: [[Gramps 3.1 Wiki Manual | GRAMPS 3.1 Manual]]<br />
* Albanian : [[Sq:Gramps 3.1 Wiki Manual| Doracak per GRAMPS 3.1]]<br />
* Norsk (bokmål) : [[Gramps_3.1_Wiki_Manual/nb| GRAMPS manualen 3.1]]<br />
* Dansk : [[Da:Gramps_3.1_brugsanvisning| GRAMPS 3.1 brugsanvisning]]<br />
* Deutsch: [[De:Gramps_3.1_Wiki_Handbuch | GRAMPS 3.1 Handbuch]]<br />
* Finnish: [[Fi:Gramps 3.1 Wiki Käyttöohje | Gramps 3.1 Käyttöohje]]<br />
* Français: [[Gramps 3.1 Wiki Manual/fr | Manuel GRAMPS 3.1]]<br />
* Italian : [[IT:Manuale_wiki_per_Gramps_3.1| GRAMPS manuale 3.1]]<br />
* Nederlands: [[Nl:Gramps 3.1 Wiki Handleiding|GRAMPS 3.1 Handleiding]]<br />
* Polish: [[Gramps 3.1 Wiki Manual/pl | Podręcznik GRAMPS 3.1]]<br />
* Macedonian : [[Gramps 3.1 Wiki Manual/mk | Упатство за GRAMPS 3.1]]<br />
* Russian : [[Gramps 3.1 Wiki Manual/ru| Руководство GRAMPS 3.1]]<br />
* Slovak : [[Gramps_3.1_Wiki_Manual/sk| GRAMPS manuál 3.1]]<br />
* Slovene : [[Gramps_3.1_Wiki_Manual/sl| GRAMPS različice 3.1]]<br />
<br />
Note that for distribution reasons, all edits to this manual must be dual-license: as GPL and GNU Free Documentation License.<br />
<br />
The aim is to be also able to create a distributable manual. See [[Manual Generation 3.0]] for ideas on how to do this.<br />
<br />
The motivation for a wiki manual is that it is editable by all users and allows cross linking to normal wiki content, greatly improving the quality of the manuals. It does make translating the manual harder. Ideas are welcome to improve this.<br />
<br />
==GRAMPS 3.0.x Manual==<br />
<br />
The 3.0.x Manual is at the moment only available in wiki format. <br />
<br />
* English: [[Gramps 3.0 Wiki Manual | GRAMPS 3.0 Manual]], download [http://www.gramps-project.org/wiki/images/4/44/Manual.tar.gz offline version] [http://www.gramps-project.org/wiki/images/3/39/Gramps_manual.zip offline version2]<br />
* Albanian : [[Sq:Gramps 3.0 Wiki Manual| Doracak per GRAMPS 3.0]]<br />
* Dano-Norwegian (bokmål) : [[Gramps_3.0_Wiki_Manual/nb| GRAMPS manualen 3.0]]<br />
* Deutsch: [[De:Gramps_3.0_Wiki_Handbuch | GRAMPS 3.0 Handbuch]]<br />
* Français: [[Gramps 3.0 Wiki Manual/fr | Manuel GRAMPS 3.0]]<br />
* Italian : [[IT:Manuale_wiki_per_Gramps_3.0| GRAMPS manuale 3.0]]<br />
* Nederlands: [[Nl:Gramps 3.0 Wiki Handleiding|GRAMPS 3.0 Handleiding]]<br />
* Polish: [[Gramps 3.0 Wiki Manual/pl | Podręcznik GRAMPS 3.0]]<br />
* Macedonian : [[Gramps 3.0 Wiki Manual/mk | Упатство за GRAMPS 3.0]]<br />
* Russian : [[Ru:Gramps 3.0 Wiki Manual/ru| Руководство GRAMPS 3.0]]<br />
* Slovak : [[Gramps_3.0_Wiki_Manual/sk| GRAMPS manuál 3.0]]<br />
* Slovene : [[Gramps_3.0_Wiki_Manual/sl| GRAMPS različice 3.0]]<br />
<br />
Note that for distribution reasons, all edits to this manual must be dual-license: as GPL and GNU Free Documentation License.<br />
<br />
The aim is to be also able to create a distributable manual. See [[Manual Generation 3.0]] for ideas on how to do this.<br />
<br />
The motivation for a wiki manual is that it is editable by all users and allows cross linking to normal wiki content, greatly improving the quality of the manuals. It does make translating the manual harder. Ideas are welcome to improve this.<br />
<br />
==GRAMPS 2.2.x Manual==<br />
The GRAMPS 2.2.x manual has been translated into 3 languages: French, Dutch and Slovak. You can browse the manuals online or download a pdf in book format (2.5 Mb download, 100 pages, 55 figures).<br />
<br />
;Français: GRAMPS est une application Open Source définie pour la recherche généalogique.<br />
;Nederlands: GRAMPS is een open source, gratis genealogish software pakket. De handleiding is vertaald in het nederlands, en kan hier geraadpleegd worden<br />
;Slovak: GRAMPS je software typu Open Source určený pre genealogický výskum.<br />
<br />
{| border="3" align="center"<br />
|+ Manual links<br />
|-<br />
| English<br />
| [http://gramps-project.org/gramps-manual/2.2/en/index.html Online Manual]<br />
| PDF in [http://gramps-project.org/gramps-manual/2.2/gramps-manual-2.2-en-USletter.pdf letter] and [http://gramps-project.org/gramps-manual/2.2/gramps-manual-2.2-en-A4.pdf A4] size<br />
|-<br />
|Français<br />
| [http://gramps-project.org/gramps-manual/2.2/fr/index.html HTML Manuel]<br />
| [http://gramps-project.org/gramps-manual/2.2/gramps-manual-2.2-fr-A4.pdf PDF en format A4]<br />
|-<br />
| Nederlands<br />
| [http://gramps-project.org/gramps-manual/2.2/nl/index.html HTML Handleiding]<br />
| [http://gramps-project.org/gramps-manual/2.2/gramps-manual-nl-A4.pdf PDF in A4 formaat]<br />
|-<br />
|Slovak<br />
| [http://gramps-project.org/gramps-manual/2.2/sk/index.html HTML Manuál]<br />
| [http://gramps-project.org/gramps-manual/2.2/gramps-manual-sk-A4.pdf A4 PDF]<br />
|}<br />
<br />
<br />
<br />
If you encounter an error or have a question about GRAMPS, please feel free to [[Contact]] us.<br />
<br />
==Technical info==<br />
Some technical info related to the manuals:<br />
* How do we go from one version of the manual to the next one? See: [[Rollover for the manual]]<br />
<br />
<br />
{{languages}}</div>
Cedeel
https://www.gramps-project.org/wiki/index.php?title=User_manual_translations&diff=14739
User manual translations
2009-03-10T14:25:03Z
<p>Cedeel: /* GRAMPS 3.1.x Manual */ Added Danish.</p>
<hr />
<div>[[Category:Documentation]]<br />
From GRAMPS 3.0.x, the manual is no longer distributed with GRAMPS, and only available online, so you need an internet connection to be able to read the manual. It is is available from within GRAMPS by pressing F1, or through the help menu, and provides in depth instructions on the use of GRAMPS.<br />
<br />
==GRAMPS 3.1.x Manual==<br />
<br />
The 3.1.x Manual is at the moment only available in wiki format. <br />
<br />
NOTE: As at 23 January 2009, these pages have simply been 'rolled over' from the 3.0 manuals, with search/replace to make the titles and references to 3.1. Only after translators and developers have completed more work will they be better representations of version 3.1...<br />
<br />
* English: [[Gramps 3.1 Wiki Manual | GRAMPS 3.1 Manual]]<br />
* Albanian : [[Sq:Gramps 3.1 Wiki Manual| Doracak per GRAMPS 3.1]]<br />
* Norsk (bokmål) : [[Gramps_3.1_Wiki_Manual/nb| GRAMPS manualen 3.1]]<br />
* Dansk : [[Da:Gramps_3.1_manual| Gramps 3.1 manual]]<br />
* Deutsch: [[De:Gramps_3.1_Wiki_Handbuch | GRAMPS 3.1 Handbuch]]<br />
* Finnish: [[Fi:Gramps 3.1 Wiki Käyttöohje | Gramps 3.1 Käyttöohje]]<br />
* Français: [[Gramps 3.1 Wiki Manual/fr | Manuel GRAMPS 3.1]]<br />
* Italian : [[IT:Manuale_wiki_per_Gramps_3.1| GRAMPS manuale 3.1]]<br />
* Nederlands: [[Nl:Gramps 3.1 Wiki Handleiding|GRAMPS 3.1 Handleiding]]<br />
* Polish: [[Gramps 3.1 Wiki Manual/pl | Podręcznik GRAMPS 3.1]]<br />
* Macedonian : [[Gramps 3.1 Wiki Manual/mk | Упатство за GRAMPS 3.1]]<br />
* Russian : [[Gramps 3.1 Wiki Manual/ru| Руководство GRAMPS 3.1]]<br />
* Slovak : [[Gramps_3.1_Wiki_Manual/sk| GRAMPS manuál 3.1]]<br />
* Slovene : [[Gramps_3.1_Wiki_Manual/sl| GRAMPS različice 3.1]]<br />
<br />
Note that for distribution reasons, all edits to this manual must be dual-license: as GPL and GNU Free Documentation License.<br />
<br />
The aim is to be also able to create a distributable manual. See [[Manual Generation 3.0]] for ideas on how to do this.<br />
<br />
The motivation for a wiki manual is that it is editable by all users and allows cross linking to normal wiki content, greatly improving the quality of the manuals. It does make translating the manual harder. Ideas are welcome to improve this.<br />
<br />
==GRAMPS 3.0.x Manual==<br />
<br />
The 3.0.x Manual is at the moment only available in wiki format. <br />
<br />
* English: [[Gramps 3.0 Wiki Manual | GRAMPS 3.0 Manual]], download [http://www.gramps-project.org/wiki/images/4/44/Manual.tar.gz offline version] [http://www.gramps-project.org/wiki/images/3/39/Gramps_manual.zip offline version2]<br />
* Albanian : [[Sq:Gramps 3.0 Wiki Manual| Doracak per GRAMPS 3.0]]<br />
* Dano-Norwegian (bokmål) : [[Gramps_3.0_Wiki_Manual/nb| GRAMPS manualen 3.0]]<br />
* Deutsch: [[De:Gramps_3.0_Wiki_Handbuch | GRAMPS 3.0 Handbuch]]<br />
* Français: [[Gramps 3.0 Wiki Manual/fr | Manuel GRAMPS 3.0]]<br />
* Italian : [[IT:Manuale_wiki_per_Gramps_3.0| GRAMPS manuale 3.0]]<br />
* Nederlands: [[Nl:Gramps 3.0 Wiki Handleiding|GRAMPS 3.0 Handleiding]]<br />
* Polish: [[Gramps 3.0 Wiki Manual/pl | Podręcznik GRAMPS 3.0]]<br />
* Macedonian : [[Gramps 3.0 Wiki Manual/mk | Упатство за GRAMPS 3.0]]<br />
* Russian : [[Ru:Gramps 3.0 Wiki Manual/ru| Руководство GRAMPS 3.0]]<br />
* Slovak : [[Gramps_3.0_Wiki_Manual/sk| GRAMPS manuál 3.0]]<br />
* Slovene : [[Gramps_3.0_Wiki_Manual/sl| GRAMPS različice 3.0]]<br />
<br />
Note that for distribution reasons, all edits to this manual must be dual-license: as GPL and GNU Free Documentation License.<br />
<br />
The aim is to be also able to create a distributable manual. See [[Manual Generation 3.0]] for ideas on how to do this.<br />
<br />
The motivation for a wiki manual is that it is editable by all users and allows cross linking to normal wiki content, greatly improving the quality of the manuals. It does make translating the manual harder. Ideas are welcome to improve this.<br />
<br />
==GRAMPS 2.2.x Manual==<br />
The GRAMPS 2.2.x manual has been translated into 3 languages: French, Dutch and Slovak. You can browse the manuals online or download a pdf in book format (2.5 Mb download, 100 pages, 55 figures).<br />
<br />
;Français: GRAMPS est une application Open Source définie pour la recherche généalogique.<br />
;Nederlands: GRAMPS is een open source, gratis genealogish software pakket. De handleiding is vertaald in het nederlands, en kan hier geraadpleegd worden<br />
;Slovak: GRAMPS je software typu Open Source určený pre genealogický výskum.<br />
<br />
{| border="3" align="center"<br />
|+ Manual links<br />
|-<br />
| English<br />
| [http://gramps-project.org/gramps-manual/2.2/en/index.html Online Manual]<br />
| PDF in [http://gramps-project.org/gramps-manual/2.2/gramps-manual-2.2-en-USletter.pdf letter] and [http://gramps-project.org/gramps-manual/2.2/gramps-manual-2.2-en-A4.pdf A4] size<br />
|-<br />
|Français<br />
| [http://gramps-project.org/gramps-manual/2.2/fr/index.html HTML Manuel]<br />
| [http://gramps-project.org/gramps-manual/2.2/gramps-manual-2.2-fr-A4.pdf PDF en format A4]<br />
|-<br />
| Nederlands<br />
| [http://gramps-project.org/gramps-manual/2.2/nl/index.html HTML Handleiding]<br />
| [http://gramps-project.org/gramps-manual/2.2/gramps-manual-nl-A4.pdf PDF in A4 formaat]<br />
|-<br />
|Slovak<br />
| [http://gramps-project.org/gramps-manual/2.2/sk/index.html HTML Manuál]<br />
| [http://gramps-project.org/gramps-manual/2.2/gramps-manual-sk-A4.pdf A4 PDF]<br />
|}<br />
<br />
<br />
<br />
If you encounter an error or have a question about GRAMPS, please feel free to [[Contact]] us.<br />
<br />
==Technical info==<br />
Some technical info related to the manuals:<br />
* How do we go from one version of the manual to the next one? See: [[Rollover for the manual]]<br />
<br />
<br />
{{languages}}</div>
Cedeel