Gramps - User contributions [en]

User talk:Patsyblefebre

2023-11-16T18:02:26Z

Ennoborg: /* Dutch user manual */ new section

== Dutch user manual ==

Hey P.,

The chapters that you mentioned don't exist in Dutch, so there is not much to redirect to either.

Can they be removed from the TOC?

Nl:Gramps 5.2 Wiki Handleiding - Gebruikersmap

2023-11-12T20:27:31Z

Ennoborg:

{{man index/nl|Gramps_5.2_Wiki_Manual_-_Command_Line/nl|Gramps_5.2_Wiki_Manual_-_Error_and_Warning_Reference/nl|5.2}}
{{languages/nl|Nl:Gramps 5.2 Wiki Handleiding - Gebruikersmap}}
{{#vardefine:chapter|D}}
{{#vardefine:figure|0}}
Dit deel gaat over de verwijzing naar de Gramps-gebruikersmap die beschikbaar is op verschillende computersystemen.

{{man note|Opmerking|De locatie van uw Gramps-gebruikersmap hangt af van het besturingssysteem dat u gebruikt en hoe uw computer werd geconfigureerd. In de volgende tekst moet <tt><~gebruikersnaam></tt> vervangen worden door de naam waarmee u inlogt op uw systeem.}}

== OS met POSIX-stijl ==

De standaardlocatie voor de installatie van Gramps in een [http://nl.wikipedia.org/wiki/Posix POSIX]-stijl en [http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard omgeving] :

/home/<~gebruikersnaam>/.gramps

Dit geldt zowel voor [http://nl.wikipedia.org/wiki/Bsd Berkeley Software Distribution], [http://nl.wikipedia.org/wiki/Linux Linux], [http://nl.wikipedia.org/wiki/Solaris_(besturingss_systeem) Solaris], [http://nl.wikipedia.org/wiki/Unix Unix] en [http://nl.wikipedia.org/wiki/Mac_OS_X OS-X] wanneer u deze instructies gebruikt: [[Installation#Mac_OS_X:Build_from_source|Mac OS X Build from source]].

=== Mac OS ===
[[File:macos_200x200.png|right|128px|link=Download#Mac_OS_X]]
Op een Mac worden bestandnamen die beginnen met een "." niet getoond door <tt>Finder</tt>. Om de toegang tot de gebruikersmap te vergemakkelijken, opent u een terminalvenster met ''Finder-Applications-Utilities-Terminal'' en geeft u daar in
ln -s .gramps gebruikersmap
op deze manier wordt de inhoud met <tt>Finder</tt> wel getoond. Of u klikt gewoon op 'ga naar' -> 'Ga naar map...' in de 'finder' en u geeft in
~/.gramps

== MS Windows ==
[[File:windows_180x160.png|right|128px|link=Download#MS_Windows]]
De standaardlocatie op Windows 7 is
C:\Users\<~gebruikersnaam>\AppData\Roaming\gramps\gramps41

De standaardlocatie Windows XP en vroegere versies is
C:\Documents and Settings\<~gebruikersnaam>\Application Data\.gramps

De standaardlocatie voor een Gramps-installatie met een [[Mac OS X:Application package]] is
/Users/<gebruikersnaam>/Library/Application Support/gramps

{{man index/nl|Gramps_5.2_Wiki_Manual_-_Command_Line/nl|Gramps_5.2_Wiki_Manual_-_Error_and_Warning_Reference/nl|5.2}}
{{languages/nl|Gramps_5.2_Wiki_Manual_-_User_Directory}}
{{grampsmanualcopyright/nl}}

[[Category:Nl:Documentatie|Gramps gebruikersmap]]

Nl:Gramps 5.2 Wiki Handleiding - Gebruikersmap

2023-11-12T19:51:34Z

Ennoborg: Ennoborg moved page Nl:Gramps 5.2 Wiki Handleiding - Gebruikersnaam to Nl:Gramps 5.2 Wiki Handleiding - Gebruikersmap

{{man index/nl|Gramps_5.2_Wiki_Manual_-_Command_Line/nl|Gramps_5.2_Wiki_Manual_-_Error_and_Warning_Reference/nl|5.2}}
{{languages/nl|Nl:Gramps 5.1 Wiki Handleiding - Gebruikersmap}}
{{#vardefine:chapter|D}}
{{#vardefine:figure|0}}
Dit deel gaat over de verwijzing naar de Gramps-gebruikersmap die beschikbaar is op verschillende computersystemen.

{{man note|Opmerking|De locatie van uw Gramps-gebruikersmap hangt af van het besturingssysteem dat u gebruikt en hoe uw computer werd geconfigureerd. In de volgende tekst moet <tt><~gebruikersnaam></tt> vervangen worden door de naam waarmee u inlogt op uw systeem.}}

== OS met POSIX-stijl ==

De standaardlocatie voor de installatie van Gramps in een [http://nl.wikipedia.org/wiki/Posix POSIX]-stijl en [http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard omgeving] :

/home/<~gebruikersnaam>/.gramps

Dit geldt zowel voor [http://nl.wikipedia.org/wiki/Bsd Berkeley Software Distribution], [http://nl.wikipedia.org/wiki/Linux Linux], [http://nl.wikipedia.org/wiki/Solaris_(besturingss_systeem) Solaris], [http://nl.wikipedia.org/wiki/Unix Unix] en [http://nl.wikipedia.org/wiki/Mac_OS_X OS-X] wanneer u deze instructies gebruikt: [[Installation#Mac_OS_X:Build_from_source|Mac OS X Build from source]].

=== Mac OS ===
[[File:macos_200x200.png|right|128px|link=Download#Mac_OS_X]]
Op een Mac worden bestandnamen die beginnen met een "." niet getoond door <tt>Finder</tt>. Om de toegang tot de gebruikersmap te vergemakkelijken, opent u een terminalvenster met ''Finder-Applications-Utilities-Terminal'' en geeft u daar in
ln -s .gramps gebruikersmap
op deze manier wordt de inhoud met <tt>Finder</tt> wel getoond. Of u klikt gewoon op 'ga naar' -> 'Ga naar map...' in de 'finder' en u geeft in
~/.gramps

== MS Windows ==
[[File:windows_180x160.png|right|128px|link=Download#MS_Windows]]
De standaardlocatie op Windows 7 is
C:\Users\<~gebruikersnaam>\AppData\Roaming\gramps\gramps41

De standaardlocatie Windows XP en vroegere versies is
C:\Documents and Settings\<~gebruikersnaam>\Application Data\.gramps

De standaardlocatie voor een Gramps-installatie met een [[Mac OS X:Application package]] is
/Users/<gebruikersnaam>/Library/Application Support/gramps

{{man index/nl|Gramps_5.2_Wiki_Manual_-_Command_Line/nl|Gramps_5.2_Wiki_Manual_-_Error_and_Warning_Reference/nl|5.2}}
{{languages/nl|Gramps_5.2_Wiki_Manual_-_User_Directory}}
{{grampsmanualcopyright/nl}}

[[Category:Nl:Documentatie|Gramps gebruikersmap]]

Nl:Gramps 5.2 Wiki Handleiding - Gebruikersnaam

2023-11-12T19:51:34Z

Ennoborg: Ennoborg moved page Nl:Gramps 5.2 Wiki Handleiding - Gebruikersnaam to Nl:Gramps 5.2 Wiki Handleiding - Gebruikersmap

#REDIRECT [[Nl:Gramps 5.2 Wiki Handleiding - Gebruikersmap]]

Nl:Gramps 5.1 Wiki Handleiding - Gebruikersmap

2023-11-12T19:50:14Z

Ennoborg: Ennoborg moved page Nl:Gramps 5.1 Wiki Handleiding - Gebruikersnaam to Nl:Gramps 5.1 Wiki Handleiding - Gebruikersmap

{{man index/nl|Gramps_5.1_Wiki_Manual_-_Command_Line/nl|Gramps 5.1 Wiki Manual - About/nl|5.1}}
{{languages/nl|Nl:Gramps 5.1 Wiki Handleiding - Gebruikersmap}}
{{#vardefine:chapter|D}}
{{#vardefine:figure|0}}
Dit deel gaat over de verwijzing naar de Gramps-gebruikersmap die beschikbaar is op verschillende computersystemen.

{{man note|Opmerking|De locatie van uw Gramps-gebruikersmap hangt af van het besturingssysteem dat u gebruikt en hoe uw computer werd geconfigureerd. In de volgende tekst moet <tt><~gebruikersnaam></tt> vervangen worden door de naam waarmee u inlogt op uw systeem.}}

== OS met POSIX-stijl ==

De standaardlocatie voor de installatie van Gramps in een [http://nl.wikipedia.org/wiki/Posix POSIX]-stijl en [http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard omgeving] :

/home/<~gebruikersnaam>/.gramps

Dit geldt zowel voor [http://nl.wikipedia.org/wiki/Bsd Berkeley Software Distribution], [http://nl.wikipedia.org/wiki/Linux Linux], [http://nl.wikipedia.org/wiki/Solaris_(besturingss_systeem) Solaris], [http://nl.wikipedia.org/wiki/Unix Unix] en [http://nl.wikipedia.org/wiki/Mac_OS_X OS-X] wanneer u deze instructies gebruikt: [[Installation#Mac_OS_X:Build_from_source|Mac OS X Build from source]].

=== Mac OS ===
[[File:macos_200x200.png|right|128px|link=Download#Mac_OS_X]]
Op een Mac worden bestandnamen die beginnen met een "." niet getoond door <tt>Finder</tt>. Om de toegang tot de gebruikersmap te vergemakkelijken, opent u een terminalvenster met ''Finder-Applications-Utilities-Terminal'' en geeft u daar in
ln -s .gramps gebruikersmap
op deze manier wordt de inhoud met <tt>Finder</tt> wel getoond. Of u klikt gewoon op 'ga naar' -> 'Ga naar map...' in de 'finder' en u geeft in
~/.gramps

== MS Windows ==
[[File:windows_180x160.png|right|128px|link=Download#MS_Windows]]
De standaardlocatie op Windows 7 is
C:\Users\<~gebruikersnaam>\AppData\Roaming\gramps\gramps41

De standaardlocatie Windows XP en vroegere versies is
C:\Documents and Settings\<~gebruikersnaam>\Application Data\.gramps

De standaardlocatie voor een Gramps-installatie met een [[Mac OS X:Application package]] is
/Users/<gebruikersnaam>/Library/Application Support/gramps

{{man index/nl|Gramps_5.1_Wiki_Manual_-_Command_Line/nl|Gramps 5.1 Wiki Manual - About/nl|5.1}}
{{languages/nl|Gramps_5.1_Wiki_Manual_-_User_Directory}}
{{grampsmanualcopyright/nl}}

[[Category:Nl:Documentatie|Gramps gebruikersmap]]

Nl:Gramps 5.1 Wiki Handleiding - Gebruikersnaam

2023-11-12T19:50:14Z

Ennoborg: Ennoborg moved page Nl:Gramps 5.1 Wiki Handleiding - Gebruikersnaam to Nl:Gramps 5.1 Wiki Handleiding - Gebruikersmap

#REDIRECT [[Nl:Gramps 5.1 Wiki Handleiding - Gebruikersmap]]

Gramps 5.2 Wiki Manual - User Directory/nl

2023-11-12T18:29:50Z

Ennoborg: change title to proper translation

#REDIRECT[[Nl:Gramps_5.2_Wiki_Handleiding_-_Gebruikersmap]]

Nl:Gramps 5.2 Wiki Handleiding - Gebruikersmap

2023-11-12T17:21:06Z

Ennoborg:

Nl:Gramps 5.1 Wiki Handleiding - Gebruikersmap

2023-11-12T17:00:03Z

Ennoborg: Page title should be Gebruikersmap, not Gebruikersnaam

Contact/nl

2023-10-05T12:56:12Z

Ennoborg: Added a link to Discourse to the top of the page.

{{languages|Contact|Contact}}

Voor iedereen die ondersteuning nodig heeft bij het gebruik van de open source genealogiesoftware Gramps, bezoek alstublieft het [[#Forum|'''Gramps Forum''']], aangedreven door Discourse. Onze gemeenschap zal u graag helpen.

==Programmafouten rapporteren==

Er zijn verschillende manieren om een programmafout te rapporteren, onder andere de [http://lists.sourceforge.net/mailman/listinfo/gramps-bugs GRAMPS Bugs postlijst]. U hoeft geen lid zijn van deze lijst om er mails naar te sturen.

De '''beste manier''' is evenwel door gebruik te maken van het [https://gramps-project.org/bugs/ Gramps foutopvolgingssysteem], zie [[How to report bugs/nl]]. Dit laat ons toe om formele methoden te gebruiken bij het volgen en oplossen van fouten.
Ten gevolge van het hoge volume aan emails die de hoofdprogrammeurs ontvangen, is er altijd een kans dat uw email uit het oog verloren wordt. Gebruik maken van het foutopvolgingssysteem zorgt ervoor dat uw problemen zullen aangepakt worden.

==Verbeteringen aanvragen==

Een verbetering of een wijziging aan GRAMPS aanvragen kan gedaan worden of via de gramps-users of gramps-devel postlijsten, of opnieuw via het
foutopvolgingssysteem door [https://gramps-project.org/bugs/ een nieuw item aan te vragen]. We zouden het appreciëren indien serieuze voorstellen via het foutopvolgingssysteem zouden gebeuren. Klik op '''Report Issue''', en selecteer '''feature''' als belangrijkheid (''severity''). Ook hier, door via het foutopvolgingssysteem te werken, kunnen we alles formeel opvolgen.

==Mailing Lists==

Er zijn meerdere mailing lists over verschillende onderwerpen die verband houden met Gramps:
;gramps-announce ([http://lists.sourceforge.net/lists/listinfo/gramps-announce lid worden], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-announce archieven]) : Aankondigingen en algemeen belangrijk nieuws. Heel lage trafiek.
;gramps-users ([http://lists.sourceforge.net/lists/listinfo/gramps-users lid worden], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-users archieven]): Discussies over het gebruik van Gramps. Lage trafiek.
;gramps-bugs ([http://lists.sourceforge.net/lists/listinfo/gramps-bugs lid worden], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-bugs archieven]): Programmafouten melden en opvolgen. Gelieve evenwel het foutopvolgingssysteem te gebruiken (zie boven).
;gramps-devel ([http://lists.sourceforge.net/lists/listinfo/gramps-devel lid worden], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-devel archieven]): Voor alles wat te maken heeft met software ontwikkeling. Lage trafiek.

==Forum==
De Gramps-gebruikersgemeenschap onderhoudt een actieve aanwezigheid in verschillende online forums. Gedurende vele jaren gebruikte het 'officiële' (gemonitord en onderhouden door vrijwilligers van Gramps) ondersteuningskanaal een reeks MailLists voor eenvoudige tekstcommunicatie. Vanaf 2020 begon het grootste deel van het 'officiële' ondersteuningsverkeer via [https://discourse.gramps-project.org/ een online forum] aangedreven door het Discourse-platform, dat de mogelijkheid bood om illustraties, opmaak en correcties toe te voegen. De MailList werd een 'legacy'-ondersteuningssysteem met uitgebreide archieven van discussiethreads.

===Officieel===
* [https://forum.gramps-project.org/ Discourse-forum voor Gramps]: Je kunt het forum gebruiken om [https://gramps.discourse.group/t/tutorial-videos/126 zelfstudievideo's te ontdekken], vragen te stellen en hulp te krijgen van de Gramps-gemeenschap. Het is ook een geweldige plek om op de hoogte te blijven van de nieuwste ontwikkelingsplannen. Voel je vrij om anoniem te kijken of meld je aan voor een account zodat je kunt deelnemen.

===Onofficieel===
Er zijn ook enkele onafhankelijk beheerde groepen:
* Op Reddit werd [https://www.reddit.com/r/gramps/ Het Gramps Project] opgericht door mvuijlst in 2012.
* Op Facebook werd de [https://www.facebook.com/groups/370692133138445/ GRAMPS for Genealogists]-groep opgericht door Tom Shaw in 2015. (De [https://www.facebook.com/groups/21123310825/ Ik gebruik GRAMPS]-groep werd in 2009 opgericht door Dan Garnitz en in 2022 samengevoegd met de "GRAMPS for Genealogists"-groep.)
* Op Google Groups is [https://groups.google.com/forum/#!forum/gramps-finland "Gramps Finland"] bedoeld voor informatie-uitwisseling tussen Finse gebruikers van Gramps.
* Op Facebook bestaat de [https://www.facebook.com/groups/363213654297545/ Dansk gramps brugergruppe] voor ''Deense Gramps-gebruikers.''
* Op [http://genealogy.stackexchange.com/questions/tagged/gramps Genealogy Stackexchange] kunnen vragen met het label '''[http://genealogy.stackexchange.com/questions/ask?tags=gramps gramps]''' worden gesteld.
* Op [https://geneanet.org/legal/geneanet/ Geneanet] > Forum Home > Franse forums > Discussies over genealogie > Genealogie software > [https://www.geneanet.org/forum/viewforum.php?f=55945 Gramps], het forum voor wederzijdse ondersteuning voor ''Franse Gramps-gebruikers.''

==IRC==
Kom ook eens langs op het chat-kanaal '''[irc://irc.libera.chat/#gramps #gramps]''' op de '''irc.libera.net''' server. Alle gebruikers en ontwikkelaars zijn welkom!

==Inbreuken op auteursrechten==
Stelt u inbreuken op het auteursrecht vast op deze wiki, gelieve dan de ontwikkelaarspostlijst ([http://lists.sourceforge.net/lists/listinfo/gramps-devel wordt eerst lid]) te mailen met de gegevens van de wiki-pagina die inbreuk bevat, alsook de hoedanigheid van de inbreuk.

[[Category:Nl:Documentatie|Contact]]
[[Category:Nl:Gemeenschap/Algemeen]]

Contact/nl

2023-10-05T12:32:31Z

Ennoborg: /* Forum */ 1st try with Dutch translation

{{languages|Contact|Contact}}

==Programmafouten rapporteren==

Er zijn verschillende manieren om een programmafout te rapporteren, onder andere de [http://lists.sourceforge.net/mailman/listinfo/gramps-bugs GRAMPS Bugs postlijst]. U hoeft geen lid zijn van deze lijst om er mails naar te sturen.

De '''beste manier''' is evenwel door gebruik te maken van het [https://gramps-project.org/bugs/ Gramps foutopvolgingssysteem], zie [[How to report bugs/nl]]. Dit laat ons toe om formele methoden te gebruiken bij het volgen en oplossen van fouten.
Ten gevolge van het hoge volume aan emails die de hoofdprogrammeurs ontvangen, is er altijd een kans dat uw email uit het oog verloren wordt. Gebruik maken van het foutopvolgingssysteem zorgt ervoor dat uw problemen zullen aangepakt worden.

==Verbeteringen aanvragen==

Een verbetering of een wijziging aan GRAMPS aanvragen kan gedaan worden of via de gramps-users of gramps-devel postlijsten, of opnieuw via het
foutopvolgingssysteem door [https://gramps-project.org/bugs/ een nieuw item aan te vragen]. We zouden het appreciëren indien serieuze voorstellen via het foutopvolgingssysteem zouden gebeuren. Klik op '''Report Issue''', en selecteer '''feature''' als belangrijkheid (''severity''). Ook hier, door via het foutopvolgingssysteem te werken, kunnen we alles formeel opvolgen.

==Mailing Lists==

Er zijn meerdere mailing lists over verschillende onderwerpen die verband houden met Gramps:
;gramps-announce ([http://lists.sourceforge.net/lists/listinfo/gramps-announce lid worden], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-announce archieven]) : Aankondigingen en algemeen belangrijk nieuws. Heel lage trafiek.
;gramps-users ([http://lists.sourceforge.net/lists/listinfo/gramps-users lid worden], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-users archieven]): Discussies over het gebruik van Gramps. Lage trafiek.
;gramps-bugs ([http://lists.sourceforge.net/lists/listinfo/gramps-bugs lid worden], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-bugs archieven]): Programmafouten melden en opvolgen. Gelieve evenwel het foutopvolgingssysteem te gebruiken (zie boven).
;gramps-devel ([http://lists.sourceforge.net/lists/listinfo/gramps-devel lid worden], [http://sourceforge.net/mailarchive/forum.php?forum_name=gramps-devel archieven]): Voor alles wat te maken heeft met software ontwikkeling. Lage trafiek.

==Forum==
De Gramps-gebruikersgemeenschap onderhoudt een actieve aanwezigheid in verschillende online forums. Gedurende vele jaren gebruikte het 'officiële' (gemonitord en onderhouden door vrijwilligers van Gramps) ondersteuningskanaal een reeks MailLists voor eenvoudige tekstcommunicatie. Vanaf 2020 begon het grootste deel van het 'officiële' ondersteuningsverkeer via [https://discourse.gramps-project.org/ een online forum] aangedreven door het Discourse-platform, dat de mogelijkheid bood om illustraties, opmaak en correcties toe te voegen. De MailList werd een 'legacy'-ondersteuningssysteem met uitgebreide archieven van discussiethreads.

===Officieel===
* [https://forum.gramps-project.org/ Discourse-forum voor Gramps]: Je kunt het forum gebruiken om [https://gramps.discourse.group/t/tutorial-videos/126 zelfstudievideo's te ontdekken], vragen te stellen en hulp te krijgen van de Gramps-gemeenschap. Het is ook een geweldige plek om op de hoogte te blijven van de nieuwste ontwikkelingsplannen. Voel je vrij om anoniem te kijken of meld je aan voor een account zodat je kunt deelnemen.

===Onofficieel===
Er zijn ook enkele onafhankelijk beheerde groepen:
* Op Reddit werd [https://www.reddit.com/r/gramps/ Het Gramps Project] opgericht door mvuijlst in 2012.
* Op Facebook werd de [https://www.facebook.com/groups/370692133138445/ GRAMPS for Genealogists]-groep opgericht door Tom Shaw in 2015. (De [https://www.facebook.com/groups/21123310825/ Ik gebruik GRAMPS]-groep werd in 2009 opgericht door Dan Garnitz en in 2022 samengevoegd met de "GRAMPS for Genealogists"-groep.)
* Op Google Groups is [https://groups.google.com/forum/#!forum/gramps-finland "Gramps Finland"] bedoeld voor informatie-uitwisseling tussen Finse gebruikers van Gramps.
* Op Facebook bestaat de [https://www.facebook.com/groups/363213654297545/ Dansk gramps brugergruppe] voor ''Deense Gramps-gebruikers.''
* Op [http://genealogy.stackexchange.com/questions/tagged/gramps Genealogy Stackexchange] kunnen vragen met het label '''[http://genealogy.stackexchange.com/questions/ask?tags=gramps gramps]''' worden gesteld.
* Op [https://geneanet.org/legal/geneanet/ Geneanet] > Forum Home > Franse forums > Discussies over genealogie > Genealogie software > [https://www.geneanet.org/forum/viewforum.php?f=55945 Gramps], het forum voor wederzijdse ondersteuning voor ''Franse Gramps-gebruikers.''

==IRC==
Kom ook eens langs op het chat-kanaal '''[irc://irc.libera.chat/#gramps #gramps]''' op de '''irc.libera.net''' server. Alle gebruikers en ontwikkelaars zijn welkom!

==Inbreuken op auteursrechten==
Stelt u inbreuken op het auteursrecht vast op deze wiki, gelieve dan de ontwikkelaarspostlijst ([http://lists.sourceforge.net/lists/listinfo/gramps-devel wordt eerst lid]) te mailen met de gegevens van de wiki-pagina die inbreuk bevat, alsook de hoedanigheid van de inbreuk.

[[Category:Nl:Documentatie|Contact]]
[[Category:Nl:Gemeenschap/Algemeen]]

Import from another genealogy program

2023-04-16T21:55:00Z

Ennoborg: /* RootsMagic, all versions */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

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. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format. (A ''new'' 7.0.2 revision was finally published in June of 2021. See [[GEDCOM_7_support|GEDCOM 7 support]] for the current state of development.)
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{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.}}

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}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

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.

The CSV import option currently doesn't allow import of all Gramps data.

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.

For more details on this format see [[Gramps 5.1 Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

== Import instructions for different programs ==

=== Ancestrologie ===

Ancestrologie seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [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.

; [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.

; [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:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

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.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----
=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ 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.

==== General tips ====
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.

==== People ====
===== Import into Evidentia as subjects =====
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.

===== What Evidentia imports and exports =====
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:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
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.

===== Manually add facts into Evidentia =====
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.

===== Export some types of facts to Gramps =====
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.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
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.

There are two reasons to follow this workflow:
* 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.

* 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!

===== Match your source title and source abbreviation =====
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.

===== Complete publication information exported =====
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.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

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.

===== Evidentia-specific GEDCOM export =====
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).

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:

* 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.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* 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."

=== Family Tree Maker ===

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]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

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.

{{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.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [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.

====Experimental way====

[[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.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

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].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== Pro-Gen ===

PRO-GEN is a Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Importer plugin was created that reads the native PRO-GEN. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the Pro-Gen directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a ~/pg30 folder. If you are running Gramps on a Windows PC and have a copy Pro-Gen on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that ~/pg30 folder.

In the following steps, we will assume that the Pro-Gen files are at ~/pg30

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "Manage Family Trees..."
* use the "New" button to create a new family tree database
* Give the Tree a name (like "PRO-GEN imported Tree") and select that new database
* click the "Load Family Tree" button to open the blank tree database
* go to menu {{man menu|Family Trees -> Import}}
* in the file Selection dialog, go to the ~/pg30/nl/data directory
* select the .DEF of your Pro-Gen database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "Import"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

You have two options.

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

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]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* 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.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

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?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

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.

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.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

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.

{{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.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"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.

*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.

*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.

===== Known issues =====

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:

# 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).
# 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.
# 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.
# 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.
# 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.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# 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.

===== Preparing to run tmg2gramps =====

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.

====== Copy your TMG projects folder ======
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:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
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:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
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:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

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:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

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:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

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:

<code>mysql> show databases;</code>

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:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...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:

<code>$ ls -l</code>

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:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

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

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:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

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

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

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.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

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:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{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://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== TMG-Working-Group ====

Information only at the moment.

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

https://github.com/girimonti/TMG-Working-Group

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

== See also ==
* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported for the first 6 to 18 months.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2023-04-16T21:54:25Z

Ennoborg: New paragraph for RootsMagic (all versions)

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

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. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format. (A ''new'' 7.0.2 revision was finally published in June of 2021. See [[GEDCOM_7_support|GEDCOM 7 support]] for the current state of development.)
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{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.}}

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}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

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.

The CSV import option currently doesn't allow import of all Gramps data.

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.

For more details on this format see [[Gramps 5.1 Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

== Import instructions for different programs ==

=== Ancestrologie ===

Ancestrologie seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [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.

; [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.

; [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:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

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.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----
=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ 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.

==== General tips ====
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.

==== People ====
===== Import into Evidentia as subjects =====
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.

===== What Evidentia imports and exports =====
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:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
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.

===== Manually add facts into Evidentia =====
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.

===== Export some types of facts to Gramps =====
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.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
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.

There are two reasons to follow this workflow:
* 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.

* 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!

===== Match your source title and source abbreviation =====
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.

===== Complete publication information exported =====
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.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

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.

===== Evidentia-specific GEDCOM export =====
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).

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:

* 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.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* 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."

=== Family Tree Maker ===

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]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

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.

{{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.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [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.

====Experimental way====

[[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.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

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].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== Pro-Gen ===

PRO-GEN is a Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Importer plugin was created that reads the native PRO-GEN. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the Pro-Gen directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a ~/pg30 folder. If you are running Gramps on a Windows PC and have a copy Pro-Gen on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that ~/pg30 folder.

In the following steps, we will assume that the Pro-Gen files are at ~/pg30

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "Manage Family Trees..."
* use the "New" button to create a new family tree database
* Give the Tree a name (like "PRO-GEN imported Tree") and select that new database
* click the "Load Family Tree" button to open the blank tree database
* go to menu {{man menu|Family Trees -> Import}}
* in the file Selection dialog, go to the ~/pg30/nl/data directory
* select the .DEF of your Pro-Gen database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "Import"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers nice features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

You have two options.

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

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]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* 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.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

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?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

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.

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.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

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.

{{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.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"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.

*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.

*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.

===== Known issues =====

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:

# 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).
# 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.
# 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.
# 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.
# 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.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# 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.

===== Preparing to run tmg2gramps =====

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.

====== Copy your TMG projects folder ======
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:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
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:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
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:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

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:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

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:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

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:

<code>mysql> show databases;</code>

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:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...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:

<code>$ ls -l</code>

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:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

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

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:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

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

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

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.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

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:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{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://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== TMG-Working-Group ====

Information only at the moment.

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

https://github.com/girimonti/TMG-Working-Group

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

== See also ==
* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported for the first 6 to 18 months.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Addon:Graph View

2023-02-15T19:30:47Z

Ennoborg: /* Linux */ Added Fedora paragraph, removed outdated note for LMDE.

{{languages|Addon:Graph View}}
{{Third-party plugin}}
{{man warn|Feature is slow in larger Trees|The larger the number of people in the Family Tree, the longer the chart will take to appear. e.g.: a test with about 7000 people took 10 minutes.This can be adjusted by changing the number of generations to be shown.}}
[[File:Graph-View-addon-example-51.png|450px|thumb|right|Graph View - addon - In action showing both ancestors and descendant trees (Gramps 5.1.x version)]]
'''Graph View''' is an interactive {{icon|ance}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]]}} category view addon that presents a navigable ancestors and descendant tree using the current active person as a starting point. Clicking another person in the family tree will make that person the active person and will redraw the family tree based on them.

== Usage ==

From the {{icon|ance}} {{man label|Charts}} category view select the '''Graph View''' icon or select {{man menu|View > Graph View}} from the menu.

In general the Graph View is:
* Interactive, the view redraws in response to changes made to a person or family.
* The active person is highlighted.
* Clicking on another person will redraw the family tree based on that person.
* Clicking the active person will show the parent family of the active person, thereby allowing previous generations to be shown.
* A right mouse click on a person or family node shows the person or family editor as appropriate.
* Able to show both ancestors and descendant trees (adjustable from the Graph View toolbar).
* Graph view can be panned by using mouse click and drag. Select the background of the tree and drag the mouse to pan the view. Also you can use mouse scroll button to pan view in any place of view.

=== Graph View Toolbar ===
[[File:Graph-View-addon-toolbar-highlighted-51.png]]

Graph View has a smaller toolbar of its own with the following options (from left to right):

* {{man button|'''+'''(Zoom in)}} button - Zoom in the view.
* {{man button|'''-'''(Zoom out)}} button - Zoom out the view.
* {{man button|'''1'''(Zoom to original)}} button to reset the view to the default size.
* {{man button|'''☐'''(Zoom to best fit)}} button to fit the current family tree graph in the display
* {{man button|'''⏎''' (Go to active person)}}
* {{man button|Go to bookmark}} button - Center view on selected bookmark - also shows "Bookmarks for current graph:" (who are being display) and "Other Bookmarks:" (who are not being displayed) - along with two buttons to "Add active person" to bookmarks and "Edit" the bookmarks.
* {{man button|🔍 Search...}} - typing shows "Persons from current graph:" (who are being display) and "Other persons from the database:" (who are not being displayed) as well as any saved bookmarks. You can use {{man button|Ctrl + F}} to make search entry active.
* {{man button|Generations}} - setting to change the generations shown for Ancestor 3 generations by default and Descendants 10 generations by default.
* {{man button|Spacing}} - changes the vertical(5 default) and horizontal(2 default) spacing between the generations.
* {{man button|All connected}} - Show all connected persons limited by generation restrictions. Works slow, so don't set large generation values. ( Limited to 1000 persons, if your family tree has more than that you get the {{man label|Incomplete graph}} warning and only the first 1000 connected persons are drawn.)

==== On main Gramps Toolbar ====
On the main Gramps Toolbar you also have:
* {{man button|'''⎙'''(Print)}} button that does not print but instead allows you to save the currently displayed Graph into a dot format file for a later printing. This will save a .gv file and a svg file. You must select a .gv file. ([https://www.reddit.com/r/gramps/comments/jhnj9w/gramps_print_svg_does_not_show_photo/ Gramps Print -SVG does not show photo])
* {{man button|* (Configure Options)}} button with option shown in the next section.

=== Configure Options ===
Select {{man menu|View > Configure...}} from the menu to change the settings on the following four tabs:

*Layout
** {{checkbox|1}}{{man label|Show images}} (checkbox selected by default)
** {{checkbox|1}}{{man label|Show avatars}} (checkbox selected by default)
** {{checkbox|1}}{{man label|Highlight the home person}} (checkbox selected by default)
** {{checkbox|0}}{{man label|Show full dates}} (checkbox unselected by default)
** {{checkbox|0}}{{man label|Show places}} (checkbox unselected by default)
** {{man label|Placeformat:}}
*** '''Default'''
*** Full
** {{checkbox|0}}{{man label|Show tags}} (checkbox unselected by default)
** {{man label|Time Direction:}}
*** '''Vertical: Top to Bottom'''
*** Vertical: Bottom to Top
*** Horizontal: Left to Right
*** Horizontal: Right to Left

*Themes
** {{man label|Person theme:}}
***'''Default'''
*** Image on right side
*** Image on left side
** {{man label|Path color to home person:}} '''<code>#000000</code>'''(default)
** {{man label|Font:}} - shows the default that can be changed by selecting from the
*** {{man label|Pick a Font}} dialog
** {{man label|Avatars style:}}
*** Custom
*** Dark '''Default'''
*** Light
*** Cartoon
[[File:Graph-View Avatar set.png|471px|thumb|right|Graph View Avatars]]
Choose the Custom {{man label|Avatars style}} adds 2 more popup menus:
::* {{man label|Male avatar:}} ''File selector''
::* {{man label|Female avatar:}} ''File selector''
** {{man label|Active person border size:}} <code>3</code>(default)
** {{man label|Person border size:}} <code>1</code>(default)

*Animation
**{{checkbox|1}}{{man label|Show animation}} (checkbox selected by default)
***{{man label|Animation speed (1..5 and 5 is the slower):}} (default is 3)
***{{man label|Animation count (0..8 use 0 to turn off):}} (default is 4)

*Search
**{{checkbox|1}}{{man label|Search in all database}}(checkbox selected by default)
**{{checkbox|1}}{{man label|Show person image}}(checkbox selected by default)
**{{checkbox|1}}{{man label|Show bookmarked first}}(checkbox selected by default)

===Context menus===
Graph view has three [https://en.wikipedia.org/wiki/Context_menu context menus] that allow the following
{{-}}
====Empty section====
[[File:Graph View Empty context menu.png|thumb|450px|Right click menu shown when selecting an empty section of the chart.]]
Right-click an empty section of the Graph View to offer the following display options:
* {{checkbox|1}}{{man label|Show images}} - Display thumbnails or avatars
* {{checkbox|1}}{{man label|Highlight the home person}} - set the background of the Home Person to green
* {{checkbox|0}}{{man label|Show full dates}} - format the birth and death date as only the year or as the complete date
* {{checkbox|0}}{{man label|Show places}} - show or hide birth and death places
* {{checkbox|0}}{{man label|Show tags}} - show color markers on tagged Persons and Families
* {{checkbox|1}}{{man label|Show animation}} - after redraws, wiggle the Active Person to draw focus

* {{man label|Lines type}} - choose the style of lines connecting People and Families
** Direct
** Curves
** Ortho
* {{man label|About Graph View}} - this help wiki webpage
{{-}}

====Person node====
[[File:Graph View person context menu.png|thumb|450px|Right click menu shown when selecting a Person on the chart.]]
Right-click a person (node) to show a context menu offering the following options for the indicated person:

<hr>
* Edit
* Copy
* Delete
<hr>
* Tags
* Spouses
* Siblings
* Children
* Parents
* Related - shows people sharing an event
<hr>
* Set as home person
* Show path to home person - changes the view to show how these two people connect to their common ancestor
* Add to bookmarks
<hr>
* [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Quick_View|Quick View]]
* [[Addon:Web_Connect_Pack|Web Connection]]
<hr>
* About Graph View
{{-}}

====Family node====
[[File:Graph View family context menu.png|thumb|450px|Right click menu shown when selecting a Family (node) on the chart.]]
Right click a family (node) to add or delete a spouse or child.

* Edit
* Remove
<hr>
* Tags
* Spouse
* Children
<hr>
* About Graph View
<hr>
{{-}}

== Prerequisites ==
Before '''Graph View''' can be used you will need the following installed:
* Graphviz. If you can run the Gramps [[Gramps_{{Version manual}}_Wiki_Manual_-_Reports_-_part_5|Graph reports]] then you already have this installed.
* [http://live.gnome.org/PyGoocanvas PyGoocanvas] (Gramps3) or [https://wiki.gnome.org/Projects/GObjectIntrospection Goocanvas2 or gir1.2-goocanvas] (Gramps4)
* [http://live.gnome.org/GooCanvas Goocanvas]

=== Windows ===
These are already installed if you are using the Gramps All In One installer eg: GrampsAIOxxxxx.exe

=== Linux ===

All of these should be available in common Linux distributions.

For example,

;Debian
Packages Goocanvas/PyGoocanvas as libgoocanvas3 and python-pygoocanvas.

Note: As of May 2020 the required packages for Debian Testing are gir1.2-goocanvas-2.0 and libgoocanvas-2.0-9 from the official repositories.

Please make sure to download these for the proper architecture, like amd64 for 64-bit PCs (Intel included).

;Fedora
Try package goocanvas2-devel.

;Opensuse
You may need to install typelib-1_0-GooCanvas-2_0 as mentioned in issue {{bug|8076}}.

== Issues ==

You can see related issues at [https://gramps-project.org/bugs/search.php?tag_string=GraphView bug tracker].
* {{bug|8054#c44291}} - print options.
* {{bug|9806}} - Subprocess on [GraphView] can generate a memory issue
* {{bug|8054}} - Better label positioning in Graphview
* [https://gramps-project.org/bugs/view.php?id=8964 8964: Enable filter on GraphView] Feature Request
* [https://github.com/gramps-project/addons-source/pull/459 [GraphView] add custom avatars #459] [https://gramps.discourse.group/t/customizable-avatars-for-graphview/696 Themed avatar discussion]

==See also==
* [[Addon:AvatarGenerator]] - allows you to add and remove one or several images for a selected set of filtered people.

[[Category:Plugins]]
[[Category:Developers/General]]
[[Category:Views]]

Addon:PlaceUpdate Gramplet

2022-06-28T20:08:18Z

Ennoborg: minor language issue

{{Third-party plugin}}
[[File:PlaceUpdate-Gramplet-Addon-103.png|right|thumb|450px|PlaceUpdate Gramplet - Data entry - detached view]]
The {{man label|PlaceUpdate}} Gramplet allows you to manipulate and change properties of multiple places at the same time.

The properties that can be changed are:
* Place Type
* Tag
* Enclosing Place

Place names can be edited by substituting sub-strings with new values.

The gramplet can also generate a place hierarchy from place names or titles.

== Usage ==
The gramplet should be installed on the sidebar gramplet pane of the Places Category view.

The Place list is then used to select which places are affected.

=== Setting enclosing place ===

For the enclosing place first select the place that should enclose the other places and click the {{man button|Select enclosing place}} button. The {{man label|Select Place}} selector will be displayed and you can select your place. Then select any number of places that should be enclosed by the first one and click the {{man button|Apply to selected places}} button.

A place might already have an enclosing place. In that case the new place will be added and the place will end up being enclosed by multiple places. This is quite ok but you can also remove the previous enclosing places by checking the box {{man label|Clear original enclosing places}}. This can e.g. be used to "move" the places under another place.

Attempts to set a duplicate enclosing place or a loop (so that a place contains itself) are quietly bypassed.

=== Setting place type or tag ===

[[File:PlaceUpdateGramplet-Addon-example-51.png|right|Thumb|450px]]You can also set the type of the selected places or assign any tag if needed. The operations can be combined so that e.g. the place type and enclosing place can be set at the same time. Type and tag can be selected from pre-existing ones or you can type a new name if needed.

Any existing tags can also be first removed if the {{man label|Clear tags}} checkbox is marked. Otherwise the new tag is added to the set of the tags for the places.

If the enclosing place, type or tag is not specified, then the corresponding setting is not changed.

=== Generating a place hierarchy ===

If a place name contains comma separated names then the gramplet can change this to a place hierarchy. For example if the name is of the form "place1, place2, place3" then two new places, place2 and place3 (with type "Unknown") are created, the name of the original place is changed to place1 and the places are put in the hierarchy "place1 < place2 < place3".

Duplicate place names at the same level are automatically merged. The original names can also be separated by spaces instead of commas - but then you must be careful that the names do not contain spaces.

The hierarchy can also be generated in reverse, e.g. the result can also be "place3 < place2 < place1" if the corresponding checkbox is marked.

The place type and tag setting affects only the original place.

If the original place is under another place or a new enclosing place is specified then the new hierarchy is placed under the enclosing place.

=== Editing place names ===

The {{man label|Replace text}} function allows substituting a specified text string in the place names with another. Regular expressions can also be used.

Example

Select "United States" as the new enclosing places and select the three states. Set the {{man label|Place type:}} to "State":

Setting enclosing place

Click {{man button|Apply to selected places}}. The result is:

Setting enclosing place

== Notes ==

The {{man button|Clear selections}} button will clear the form.

All changes are done under a transaction and they can be undone from the Gramps menu {{man menu|Edit > Undo Setting place properties}}.

This gramplet does not have direct support for filters. The "Filter" gramplet can be used to search for the places that need changes.

This gramplet can only be added on the Places view and it requires Gramps 5.x.

Author: kari.kujansuu@gmail.com (19 Jan 2020)

==Issues==
* Help button goes to https://gramps-project.org/wiki/index.php?title=Gramps_5.1_Wiki_Manual_-_Gramplets#PlaceUpdate

[[Category:Plugins]]
[[Category:Developers/General]]
[[Category:Gramplets]]

Download

2020-09-06T11:51:17Z

Ennoborg: /* Debian-based */ Install language pack

{{languages|Download}}
[[File:Gramp-Small-background-wiki-2020.jpg|120px|left]]
'''Research, organize and share your family tree with Gramps.'''

Gramps is a free software project and community. We strive to produce a genealogy program that is both intuitive for hobbyists and feature-complete for professional genealogists. It is a community project, created, developed and governed by genealogists.

{{man note|{{Man menu|Gramps '''Current version: '''{{version}}''' Released: '''2020-08-13'''}}|''Different data format to the GRAMPS 3.4 series. Full Python 3 support only as [https://www.python.org/doc/sunset-python-2/ Python 2 support dropped]. Uses GTK+ 3 GUI. Default database is now SQlite. Lot of updates see: ''[[Gramps 5.1 Wiki Manual - What's new?|What's new?]]{{-}}
[[File:Linux_220x261.png|128px|link=Download#Linux]] [[File:windows_180x160.png|128px|link=Download#MS_Windows]] [[File:macos_200x200.png|128px|link=Download#macOS]] [[File:Bsd daemon.png|128px|link=Download#BSD]]}}

== Linux ==

[[File:Linux_220x261.png|128px|left|link=Download#Linux]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version ({{version}}) (advanced users only)]]</big>
{{-}}

== MS Windows ==

[[File:windows_180x160.png|128px|left|link=Download#MS_Windows]]

Before downloading the [[All_In_One_Gramps_Software_Bundle_for_Windows|All-In-One software installer bundle for Windows]]: Use your '''earlier version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees to the hardy and portable [[#1|XML format1]].

This installer supports Microsoft Windows in all versions [http://windows.microsoft.com/en-au/windows/lifecycle Vista/7] and later.

(''Please note: Gramps prefers the Python-3.5 and Gtk-3.18 libraries and newer. Those libraries have dropped support for Windows XP. But Gramps can still be run on Windows XP with earlier library versions, i.e., Python3.4.4 and Gtk-3.16'')

<big>
*[{{github_url}}/releases/download/v{{version_windows_AIO32}}/{{filename_windows_AIO32}}.exe Windows Installer (32-bit) {{version_windows_AIO32}}]
*[{{github_url}}/releases/download/v{{version_windows_AIO64}}/{{filename_windows_AIO64}}.exe Windows Installer (64-bit) {{version_windows_AIO64}}]</big>

After download: '''double-click to install Gramps'''. By default: new releases will be added in a new directory and earlier installations of Gramps will ''not'' be overwritten; the language will be a [[#Missing_other_languages|mix of British and US English]].

{{man tip|Shortcuts|During installation, one shortcut is placed on the desktop and two shortcuts are added the Start menu. ''Please only use the 'console' secondary shortcut when performing diagnostics requested by a developer.'' 1) ''GrampsAIO'''XX''' ''{{version}}'' {{man menu| ← for normal use of Gramps}} 2) ''GrampsAIO'''XX''' ''{{version}}''-console}}

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. Should this fail for any reason, '''Create''' a new Family Tree and [[How_to_restore_a_backup|'''Import''' the back-up]] into this new Tree.

Use the Windows AIO (All-In-One) version, please use the download links above. For more information about individual versions, console and debug modes, release notes, etc., look at [[GrampsAIO cx freeze-based|this page]] (English only).

If necessary, there is an alternative independent '''Legacy''' MS Windows [[#2|portable version2]].

You may also install using the alternative independent Gramps [[#3|Chocolatey NuGet Package3]].

{{-}}
=== Missing other languages ===
[[File:Microsoft Window Gramps AIO Installer Choose Components-Selection-51.png|right|thumb|450px|Microsoft Window Gramps AIO Installer Choose Components-Selection window.]]
The default Gramps AIO installer will embed the US dialect of English for the interface with the British spellcheck dictionary.

If you prefer a different language (or spell with the US or Australian dialects of English), please ensure that you pay special attention to the Choose Components phase of the installation.

To install a language other than English, select from both the '''Translations''' ''and'' '''Dictionaries''' during the Choose Components phase of the installation.

Even your primary language is installed by default, you might anticipate the need to spellcheck Notes in other than the British dialect of English. Be certain to select the appropriate languages from '''Dictionaries'''. Gramps will not access your Operating System's native dictionary.

There is no simple facility for adding interface or dictionary languages after installation.
{{-}}


== macOS ==

[[File:macos_200x200.png|128px|left|link=Download#Mac_OS_X]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]]. Read the [[Mac OS X:Application package|before installation]] instructions.

Supports Apple macOS/Mac OS X in all versions 10.5 ([https://wikipedia.org/wiki/Mac_OS_X_Leopard Leopard]) and later. (Help determining your Operating System version can be found in the [https://support.apple.com/en-us/HT201260 HT201260 Apple Support article.])

<big>[{{github_url}}/releases/download/v{{version_Mac}}/{{Filename_mac_intel}}.dmg Intel {{version_Mac}}]</big>
    

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next drag the Gramps application to your application folder and double-click to launch it [[#4|[4]]].

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

{{man tip|Spell Checking:|Gramps uses a different spell checker than the one provided by Mac OS X, with different spelling dictionary requirements. We can't easily provide dictionaries for all of the supported languages in the bundle, but they're easily downloaded from [https://extensions.openoffice.org/ OpenOffice.org's website]. Download the language you want and save it, then navigate to the download in Finder. Most browsers have a downloads window that offers "Show in Finder" in its context menu. Change the file extension from <tt>oxt</tt> to <tt>zip</tt>, then from the context menu select '''Open with... Archive Utility''' to decompress it. In the decompressed folder or perhaps in a subfolder you'll find the dictionary files in pairs, <tt>foo.aff</tt> and <tt>foo.dic</tt>. Some languages have more than one pair with a README file to explain why. Select a pair and copy it to /Library/Dictionaries (you'll have to authenticate with an administrator id and password), and if 'foo' isn't already a language or locale code, make it one. For example, the French package includes several pairs with names like <tt>fr-moderne.aff</tt> and <tt>fr-moderne.dic</tt>. The spell checker doesn't recognize those names, so when you copy them to /Library/Dictionaries you must rename them to <tt>fr.aff</tt> and <tt>fr.dic</tt> or <tt>fr_FR.aff</tt> and <tt>fr_FR.dic</tt>. You can have more than one dictionary pair installed if you use several languages, but one '''must''' match the language you use for Gramps or spell checking won't be enabled at all.}}

An alternative way to download and install Gramps on MacOS can be done using the MacPorts[[#5|[5]]] framework.
{{-}}

== Linux and BSD distributions ==
{{man note|These packages are built and supported by the [https://en.wikipedia.org/wiki/Linux_distribution distros].|If your distribution is not listed you may possibly find it listed on [https://repology.org/metapackage/gramps/versions ''Repology''] Please report any problems with them to the package maintainer.}}
Most Linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| {{prettytable}}
!style="width: 85pt;" | Distribution
!GUI Package manager
!Current versions
!Notes
|-
|[[File:Debianopenlogo-32.png|link=https://packages.debian.org/search?keywords=gramps]]''' [[Debian]] '''
|Add/Remove Software
|
* Debian 8 ("jessie")(old old stable): Gramps 4.1.1
* Debian 9 ("stretch") (old stable): Gramps 4.2.5
* Debian 9 ("stretch")([https://packages.debian.org/stretch-backports/gramps backports]): Gramps 5.0.1
* Debian 10 ("buster") (stable): Gramps 5.0.1
* Debian 10 ("buster")([https://packages.debian.org/buster-backports/gramps backports]) (stable): Gramps 5.1.2
* bullseye (testing): Gramps 5.1.3
* [http://packages.debian.org/sid/gramps sid (unstable)]: Gramps 5.1.3
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[File:Ubuntu_32x32.png]]''' Ubuntu '''
|Software Centre
|
* Xenial (16.04 LTS): Gramps: 4.2.2
* Xenial (16.04 LTS): Gramps: 4.2.6 ([https://launchpad.net/~rosco2/+archive/ubuntu/backports Backport])
* Bionic Beaver (18.04 LTS): Gramps: 5.0.0
* Eoan (19.10): Gramps: 5.0.1
* Focal (20.04 LTS): Gramps: 5.1.2
* Groovy Gorilla (Development: 20.10): Gramps: 5.1.3
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]/ (Also see: [https://launchpad.net/~rosco2/+archive/ubuntu/backports Backports])
|-
|[[File:Farm-Fresh linux mint.png]]''' [https://www.linuxmint.com/ Linux Mint]'''
|Software Manager
|
* 18.x(Gramps 4.2.2~dfsg-1)
* 19.x(Gramps 4.2.8)
* 20.x(Gramps 5.1.2)
|
* Use the "Software Manager" to install a recent version.
* Manually install the most current version of Gramps using the following [https://forums.linuxmint.com/viewtopic.php?t=220159 instructions] from the ''Linux Mint Forums''
* [http://community.linuxmint.com/software/view/gramps Old versions available from Linuxmint]
|-
|[[File:Fedora_32x32.png]]''' Fedora '''
|Add/Remove Software (Gnome) or Software Management (KDE)
|
* Rawhide (Gramps 5.1.2)
* Fedora 30 (Gramps 5.1.2)
* Fedora 31 (Gramps 5.1.2)
* Fedora 32 (Gramps 5.1.2)
|[https://apps.fedoraproject.org/packages/gramps available versions]
|-
|'''[https://www.mageia.org/en/ Mageia]'''
||[https://wiki.mageia.org/en/Installing_and_removing_software drakrpm (or rpmdrake)]
|
* Mageia [https://madb.mageia.org/package/show/name/gramps/release/cauldron/ Caulron]: Gramps 5.1.2
* Mageia 7.1: Gramps 5.0.1
|[http://mageia.madb.org/package/show/name/gramps Mageia App Db - gramps]
|-
|[[File:OpenSUSE-distribution-icon.png|32px]]''' openSUSE '''
|[https://en.opensuse.org/YaST_Software_Management YaST]
|
* openSUSE Tumbleweed: Gramps 5.1.2
* openSUSE Leap 15.2: Gramps 4.2.8
* openSUSE Leap 15.1: Gramps 4.2.8
* openSUSE Leap 15.0: Gramps 4.2.8
|[https://software.opensuse.org/package/gramps available versions] The most recent version can usually be installed from the 'openSUSE BuildService - GNOME:Apps' repository
|-
|[[File:Slackware-distribution-icon.jpg|32px]]'''Slackware'''
|
|
* 14.2: Gramps 4.2.6
* 14.2: Gramps 5.1.2 - [https://slackbuilds.org/repository/14.2/misc/gramps/?search=gramps slackbuilds.org]
* 14.1: Gramps 4.0.3
|[http://pkgs.org/search/?keyword=gramps available versions]
|-
|[[File:archlinux-icon-crystal-32.svg]]'''[https://www.archlinux.org/ Arch Linux]'''
|
|
* Gramps 5.1.2
|[https://www.archlinux.org/packages/community/any/gramps/ available versions]
|-
|[[File:Gentoo-distribution-icon.png|32px]]'''[https://gentoo.org Gentoo Linux]'''
|
|
* Gramps 5.1.2
|[https://packages.gentoo.org/packages/app-misc/gramps available versions]
|-
|'''[https://www.netbsd.org/ NetBSD]'''
|
|
* NetBSD: [http://pkgsrc.se/databases/gramps3 Gramps 3.4.9]
* NetBSD: [http://pkgsrc.se/databases/gramps5 Gramps 5.1.2]
|
|-
|'''[https://www.freebsd.org/ FreeBSD]'''
|
|
* FreeBSD: Gramps 4.2.8
* [https://www.freshports.org/science/gramps/ FreshPorts: Gramps 5.1.1]
|[http://portsmon.freebsd.org/portoverview.py?category=science&portname=gramps available versions]
|-
|'''[https://www.openbsd.org/ OpenBSD]'''
|
|
* OpenBSD: Gramps 5.1.1
|[http://openports.se/misc/gramps available versions]
|-
|
|
|
|
|}

{{-}}

== Linux: Install latest version ==

If your distribution doesn't ship with Gramps or you wish to install a different version than it ships with, you could try to install the latest version of Gramps manually.

{{man warn|1=Warning before attempting this use your existing installation to [[How to make a backup|make a Gramps XML backup]]|2=This should only be attempted by experienced users, and after you have backed up your Family Tree.

The version of Gramps that has been included in your distribution will have been tested to work with the components in that distribution. If you try to install a different version of Gramps there is a possibility that the components needed for the new version of Gramps are not available for your distribution, or they are available, but don't work properly. You might not discover that there is a problem till you have already done some work with the new version of Gramps.

If you already have Gramps installed, and you are only making a 'point' upgrade (i.e. from Gramps x.y.z to x.y.z+1, e.g. from 3.4.3 to 3.4.4), then it is likely but not certain that Gramps will continue to work. However, if the change is much greater, especially if it is a major version change (e.g. from 2.y.z to 3.y.z), then the danger that it does not work properly is much greater.}}

=== Debian-based ===
For [[File:Debianopenlogo-32.png|link=Download#Debian-based]]'''[[Debian|Debian-based linux distributions]]''' (Which includes [[File:Ubuntu_32x32.png|link=Download#Debian-based]]''' Ubuntu ''') [{{github_url}}/releases/v{{version}} Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved ({{man menu|change the filename to match the one you downloaded}}).

sudo dpkg -i gramps_{{version}}-1_all.deb

If you have an error about having unmet dependencies run:

sudo apt-get -f install

to install the dependencies.

If you see an error about language support when starting Gramps, run

sudo apt install language-pack-gnome-en

to install the proper language pack. You may need to replace 'en' with your own language code, like 'nl' for Dutch.

==== Useful command lines ====
Before upgrading you can[https://sourceforge.net/p/gramps/mailman/message/35460486/]:

* Find out what version you are running, by using this:

dpkg-query -s gramps

that queries the package and gives you info about it.

* If you are committed to an upgrade then make sure you have backed up you Family Trees to Gramps XML then run :

sudo dpkg -r gramps

this will remove the current gramps package (assuming its a python3 version older versions could be python-gramps )

* To stop Ubuntu updating gramps (to possibly an older version from Ubuntu!) you may need to run:

sudo apt-mark hold gramps

'''Upgrade is then complete.'''

=== For other distributions ===
For other distributions, [[File:Download_link.png|150px|link={{github_url}}/releases/v{{version}}]] the source and follow the instructions for [[Linux:Build from source]]

== BSD ==

[[File:Bsd daemon.png|128px|left|link=Download#BSD]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux and BSD distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version (advanced users only)]]</big>

See also:
* [[BSD platforms]]
{{-}}

== Live CD ==

{{man warn|Note that both Live CD demonstrations use an old version of Gramps and it is not recommended for general use}}

[[File:Download_link.png|150px|left|link=https://sourceforge.net/projects/gramps/files/gramps-cdrom/lgenealogy-6.1-desktop-i386.iso/download]]
'''Linux live CD Demonstration''' includes Gramps {{Version Linux Live CD}} pre-installed to trial, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn..). [[Linux_Genealogy_CD#Download_the_CD|Download the CD]] (727 MB). The [[Linux Genealogy CD|Linux Genealogy CD is based on Ubuntu 10.10 (Maverick Meerkat)]]. If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install latest [http://www.ubuntulinux.org/ Ubuntu] and Gramps from the CD anytime you like.
{{-}}

=== Online Demonstration ===
You can also try an online demonstration of Gramps on rollApp:
* https://www.rollapp.com/app/gramps
Select '''Launch Online''' then '''Test Drive(Opening/saving files will not be available)'''

{{man note|Note|This is a commercial limited trial and not endorsed by the Gramps-project. Beware of third parties having your genealogical data.}}
{{-}}

== Notes ==

[1]
Backup to Gramps XML. You will find backup in the Family Tree menu of recent Gramps versions, otherwise use export in the same menu but '''uncheck privacy options''' in the Exporter Assistant in order to export all data. See : [[How to make a backup]]

[2]
{{man menu|Note that PortableApps.com use an old version of Gramps and it is not recommended for general use}} An alternative independent '''Legacy''' version is [http://sourceforge.net/projects/portableapps/files/Gramps%20Portable/ GrampsPortable_{{version_windows_portable}}.paf.exe] (29.0 MB)
[http://portableapps.com/apps/education/gramps_portable Portable Gramps from PortableApps.com] includes all dependencies required for Windows. ''Note:You can install it on C: then to run Gramps type C:\PortableApps\GrampsPortable\GrampsPortable.exe (Or the path you installed it to) or make a shortcut to that file on your desktop or start-menu.'' By Bart.S - '''[http://portableapps.com/blog/84601 Please report packaging issues to the author.]''' (2012-09-07)

[3]
Chocolatey NuGet is a Machine Package Manager, somewhat like apt-get, but built with Windows in mind. [https://chocolatey.org/packages/gramps/ Gramps Chocolatey Package]

[4]
For Apple Mac OS X, alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.

[5]
The MacPorts Project is an open-source community initiative to design an easy-to-use system for compiling, installing, and upgrading open-source software on the Mac operating system. https://www.macports.org/ In order to do that run the following command: <code>port install gramps</code> see: [[Mac OS X:Build from source:MacPorts]]

== See also ==
* [[Previous releases of Gramps]]

[[Category:Documentation]]

Nl:Download

2016-12-31T18:21:31Z

Ennoborg: Let op dat je zelf voor Windows extra talen moet installeeren.

__NOTOC__
{{languages|Download|Nl:Download}}
== Linux ==

[[Image:Linux_220x261.png|128px|left]]

Voor u uw distro opwaardeert: gebruik uw '''oude Gramps-versie''' om een [[How_to_make_a_backup/nl#Gramps_versie_3.3_en_later|reservekopie]] van uw stambo(o)m(en) te maken [[#1|[1]]].

<big>
[[Download#Linux distributions|via distro's]]
    
[[Download#Linux:_Installeer_laatste_versie|Laatste versie ({{version}}) (enkel voor gevorderden)]]</big>
{{-}}

== MS Windows ==

[[Image:windows_180x160.png|128px|left]]

Voor u de versie downloadt: gebruik uw '''oude Gramps-versie''' om een [[How_to_make_a_backup/nl#Gramps_versie_3.3_en_later|reservekopie]] van uw stambo(o)m(en) te maken [[#1|[1]]].

<big>[{{github_url}}/releases/download/v{{version_windows_AIO32}}/{{filename_windows_AIO32}}.exe Windows Installer (32-bit) {{version_windows_AIO32}}]
    
[{{github_url}}/releases/download/v{{version_windows_AIO64}}/{{filename_windows_AIO64}}.exe Windows Installer (64-bit) {{version_windows_AIO64}}]</big>

Na het downloaden: dubbelklikken om Gramps te installeren. Houd er rekening mee dat de nieuwe installer standaard alleen Engels installeert. U moet daarom indien gewenst bij Dictionaries en Languages zelf nog Nederlands (en eventuele andere talen) selecteren.

Normaal gezien zal wanneer u uw oude stamboom tracht te laden, zal er een mogelijkheid geboden worden om indien nodig op te waarderen en de stamboom zal geopend worden. Maar indien dit om welke reden dan ook niet lukt, kunt u een nieuwe stamboom aanmaken en vervolgens de importfunctie gebruiken.

Alternatieve onafhankelijke MS Windows versie [[#3|[3]]].

== Mac OS X ==

[[Image:macos_200x200.png|128px|left]]

Voor u de versie downloadt: gebruik uw '''oude Gramps-versie''' om een [[How_to_make_a_backup/nl#Gramps_versie_3.3_en_later|reservekopie]] van uw stambo(o)m(en) te maken [[#1|[1]]]. Lees ook de [[Mac OS X:Application package|pre-installatie]] instructies.

Mac OS X 10.5, 10.6 and 10.7    <big>[{{github_url}}/releases/download/v{{version_Mac}}/{{filename_mac_intel}}.dmg Intel {{version_Mac}}]</big>
    
Mac OS X 10.5    <big>[{{github_url}}/releases/download/v{{version_Mac}}/{{filename_mac_ppc}}.dmg Power PC {{version_Mac}}]</big>

Na het downloaden: dubbelklik het ''.dmg'' bestand om de schijf te 'mounten' (opmerking: mogelijk doet uw browser dat al voor u). Versleep vervolgens de Gramps-applicatie naar uw applicatiefolder. Dubbelklikken zal de applicatie starten [[#2|[2]]].

Normaal gezien zal wanneer u uw oude stamboom tracht te laden, zal er een mogelijkheid geboden worden om indien nodig op te waarderen en de stamboom zal geopend worden. Maar indien dit om welke reden dan ook niet lukt, kunt u een nieuwe stamboom aanmaken en vervolgens de importfunctie gebruiken.

{{-}}

== BSD ==

Voor u uw distro opwaardeert: gebruik uw '''oude Gramps-versie''' om een [[How_to_make_a_backup/nl#Gramps_versie_3.3_en_later|reservekopie]] van uw stambo(o)m(en) te maken [[#1|[1]]].

<big>
[[Download#Linux en BSD distro's|via distro's]]
    
[[Download#Linux:_Installeer_laatste_versie|Laatste versie (enkel voor gevorderden)]]</big>
{{-}}

== Live CD ==

[[Image:Download_link.png|150px|left|link=http://sourceforge.net/projects/gramps/files/OldFiles/3.2.5/lgenealogy-6.1-desktop-i386.iso]]
'''Linux live cd demo''' [[Linux_Genealogy_CD/nl#Hoe_geraakt_u_aan_de_cd|hoe geraakt u aan de cd]] (727 MB) [[Linux_Genealogy_CD/nl|Linux Genealogy cd gebaseerd op Ubuntu 10.10 (Maverick Meerkat)]]. Deze methode laat u toe om een live cd uit te proberen zonder dat u iets hoeft te installeren op de harde schijf. U dient wel uw computer op te starten en te booten met de live cd in een cd/dvd-station. (U dient eerst dit beeld naar een cd-rom te branden). Indien u wel geïnteresseerd bent in Gramps, maar bang bent om ook effectief iets te moeten installeren of niet de mogelijkheid hebt dit te doen (geen eigen computer, windows, laptop van het werk of geen internetverbinding ...) kunt u dus deze [[Linux_Genealogy_CD/nl|live cd]] gebruiken. Het programma draait zonder iets te installeren op de harde schijf en bevat tevens een verzameling van genealogische openbron programma's. U kunt dan later wanneer het u past [http://www.ubuntulinux.org/ Ubuntu 10.10] en ook Gramps via de cd installeren.

== Linux en BSD distro's ==

De meeste linux distro's bevatten een Gramps-versie maar dit is niet altijd de meest recente versie. Bovendien wordt Gramps niet altijd standaard geïnstalleerd. Maar het is wel nog steeds aan te bevelen om de versie die geleverd wordt door uw distro te gebruiken.

Onderstaande tabel geeft voor de belangrijkste distro's de installatiemethode:

{| {{prettytable}}
|Distro
|GUI pakketbeheerder
|Huidige versies
|Opmerkingen
|-
|'''Linux Mint'''
|Software Manager
|Nadia: Gramps 3.4.0-1 Lisa: Gramps 3.3.1-1 Isadora: Gramps 3.2.0-1
|
|-
|''' Mageia '''
|
|
|
|-
|[[Image:Ubuntu_32x32.png]]''' Ubuntu '''
| Software Centre
|Quantal: Gramps 3.4.0-1
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]
|-
|[[Image:Fedora_32x32.png]]''' Fedora '''
|Software verwijderen/toevoegen (Gnome) of Software Management (KDE)
|Fedora Rawhide: Gramps 3.4.3 Fedora 18: Gramps 3.4.2.
|
|-
|[[Image:Debianopenlogo-32.png]]''' Debian '''
|Add/Remove Software
|squeeze (old stable): Gramps 3.2.3 wheezy (stable): Gramps 3.4.0 jessie (testing): Gramps 3.4.0 [http://packages.debian.org/sid/gramps sid (unstable)]: Gramps 3.4.0
|[http://packages.debian.org/search?keywords=gramps beschikbare versies]
|-
|[[Image:Mandriva_32x32.png]]''' Mandriva '''
|Software Management in the 
Mandriva Linux Control Center
|
|Mandriva 2010.1: Gramps 3.3.1 Mandriva 2011: Gramps 3.2.6 Zie ook [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Advanced_use:_Backports_and_candidate_updates backports] en contrib repository
|-
|[[Image:Redhat_32x32.png]]''' Redhat '''
|
|
|
|-
|''' openSUSE '''
|YaST ??
|openSUSE 12.3: Gramps 3.4.2
|[http://software.opensuse.org/package/gramps beschikbare versies]
|-
|'''Slackware'''
|
|Slackware 14.0: Gramps 3.4.2
|[http://pkgs.org/search/?keyword=gramps beschikbare versies]
|-
|'''NetBSD'''
|
|NetBSD: Gramps 3.4.3
|[http://pkgsrc.se/databases/gramps3 beschikbare versies]
|-
|'''FreeBSD'''
|
|FreeBSD: Gramps 3.3.0
|[http://portsmon.freebsd.org/portoverview.py?category=science&portname=gramps beschikbare versies]
|-
|'''PC-BSD'''
|
|PC-BSD: Gramps 3.3.0
|
|}

{{-}}

== Linux: Installeer laatste versie ==

Indien uw distro geen Gramps-versie bevat of u een andere versie wenst te installeren dan de versie die voorradig is, kunt u manueel de laatste Gramps-versie zelf installeren.

Instructies worden voor een aantal distro's hieronder vermeld.

{{man warn|1=Waarschuwing|2=Dit is enkel voor ervaren gebruikers. Maak ook steeds eerst een reservekopie van uw stamboom.

De Gramps-versie die uw distro bevat werd getest om met alle onderdelen van die distro te werken. Indien u een andere Gramps-versie installeert, bestaat de mogelijkheid dat bepaalde onderdelen niet juist meer werken. Bovendien kan het best zijn dat u dit eerst later merkt nadat u al een aantal aanpassingen hebt gedaan aan uw gegevens.

Hebt u Gramps al geïnstalleerd en u maakt enkel een 'punt' opwaardering (bijvoorbeeld van Gramps x.y.z naar x.y.z+1 dus van bijvoorbeeld 3.4.3 naar 3.4.4), dan is het waarschijnlijk maar niet zeker dat alles naar behoren blijft functioneren. Maar is de verandering van de opwaardering veel groter en zeker bij een belangrijke versieverandering (van bijvoorbeeld 2.y.z naar 3.y.z) dan is de kans zeer groot dat het niet werkt.}}

[[Image:Debianopenlogo-32.png]]'''Debian''' en [[Image:Ubuntu_32x32.png]]''' Ubuntu ''' [{{github_url}}/releases/v{{version}} Download het .deb bestand]. Dubbelklik op het gedownloade .deb bestand of (voor sommige distro's zoals Mint Debian) geeft het volgende commando in (in de map waar het bestand werd opgeslagen) (verander indien nodig de bestandsnaam om die te laten overeenstemmen).

sudo dpkg -i gramps_{{version}}-1_all.deb

Voor andere distro's: [[Image:Download_link.png|150px|link={{github_url}}/releases/v{{version}}]] de broncode en volg de instructies [[Linux:Build from source]].

== Opmerkingen ==

[1]
Backup naar Gramps-XML. In het menu -stambomen- vindt u een optie om een reservekopie te maken. Gebruik anders de exportoptie (terug te vinden in hetzelfde menu) maar stel zeker dat de optie om private gegevens weg te laten niet geactiveerd is!

[2]
U kunt ook het schijficoontje klikken en vasthouden en dan de versleepoptie naar de applicatiefolder gebruiken. Er wordt dan een nieuwe folder aangemaakt die alle bestanden, met inbegrip van het README en NEWS bestand, bevat.

[3]
Een alternatieve onafhankelijke versie is [http://sourceforge.net/projects/portableapps/files/Gramps%20Portable/ GrampsPortable_{{version_windows_portable}}.paf.exe] (20.3 MB)
[http://portableapps.com/apps/education/gramps_portable Portable Gramps from PortableApps.com] die alle afhankelijkheden nodig voor Windows bevatten. ''Opmerking: U kunt dit op C installeren: om programma te starten geeft u in: C:\PortableApps\GrampsPortable\GrampsPortable.exe (Of gebruik het installatiepad dat u zelf koos) of maak een snelkoppeling naar het bestand op uw bureaublad of startmenu.'' Door Bart.S - '''[http://portableapps.com/blog/84601 gelieve problemen aan de auteur te melden.]''' (7/9/2012)

{{languages|Download|Nl:Download}}

[[Category:Nl:Documentatie|Download]]

Indicate a divorce

2016-12-26T17:57:16Z

Ennoborg: Added marriage event

{{languages|Indicate_a_divorce}}
;How do I represent a divorce?

''I want to indicate that two people are divorced, yet Gramps does not have a Relationship type of Divorced. How do I represent this?''

Gramps does not consider ''Divorced'' to be a relationship type. Instead, it is an event that terminates the relationship. If two people are divorced, it does not change the fact that they had a relationship type of ''Married''. Divorce, like Death, is one way in which a marriage is terminated. Just as the death of a spouse does not change the fact that two people were married, a divorce does not change the fact that two people were married.

So to represent a marriage that ended in divorce:

# Create a family
# Add both spouses
# Set the relationship to ''Married''
# Add an Event of type ''Marriage''
# Add an Event of type ''Divorce''

[[Category:How do I...]]

Nl:Hoe een scheiding aangeven

2016-12-26T17:55:44Z

Ennoborg: Huwelijks-gebeurtenis toegevoegd.

{{languages|Indicate_a_divorce}}
;Hoe best een scheiding voorstellen?

''Ik wil aangeven dat twee mensen gescheiden zijn, maar Gramps heeft geen relatietype ''gescheiden''. Hoe kan dit dan best gedaan worden?''

Gramps beschouwt ''Gescheiden'' niet al een relatietype. Het is eerder een gebeurtenis die een relatie beëindigd. Wanneer twee mensen scheiden, veranderd dat niets aan het feit dat ze een relatie ''Getrouwd'' hadden. Scheiding, zoals overlijden, is een manier om het huwelijk te beëindigen. Juist zoals het overlijden van een partner niets veranderd aan het gegeven dat beiden gehuwd waren met elkaar, verandert een scheiding niets aan het feit dat twee mensen gehuwd waren.

Dus om een huwelijk dat in een scheiding eindigde, weer te geven:

# Familie aanmaken,
# Beide partners toevoegen,
# De relatie als ''Getrouwd'' vastleggen,
# Een gebeurtenis toevoegen van het type ''Huwelijk'', en
# Een gebeurtenis van het type ''Scheiding''.

[[Category:Nl:Hoe...|Scheiding aangeven]]

Download

2016-12-26T13:58:18Z

Ennoborg: /* MS Windows */ only two shortcuts, all additional languages are optional

{{languages}}

'''Research, organize and share your family tree with Gramps.'''

Gramps is a free software project and community. We strive to produce a genealogy program that is both intuitive for hobbyists and feature-complete for professional genealogists. It is a community project, created, developed and governed by genealogists.

{{man note|{{Man menu|'''Current version: {{version}} Released: 2016-12-15'''}}|''Different data format to the GRAMPS 3.4 series. Full Python 3 support only as Python 2 support dropped. Uses GTK+ 3 GUI. Lot of updates see:.''[[Gramps_4.2_Wiki_Manual_-_What's_new%3F|What's new?]]}}

{{man warn|''Legacy version: 3.4.9 Released: 2015-04-30|This is the final maintenance release designed for those of you still running gramps with gtk2. The database is common between version 4.0.x (not version 4.1.x and version 4.2.x) and 3.4.x branch, most differences are into interface...''[https://gramps-project.org/2015/04/gramps-3-4-9-released/]}}

== Linux ==

[[File:Linux_220x261.png|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version ({{version}}) (advanced users only)]]</big>
{{-}}

== MS Windows ==

[[File:windows_180x160.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

Supports Microsoft Windows in all versions [http://windows.microsoft.com/en-au/windows/lifecycle Vista/7] and later.(''Please note: Python-3.5 and Gtk-3.18 dropped support for Windows XP not Gramps itself. Gramps can still be run on Windows XP with older versions of those libraries eg:(Gtk-3.16 & Python3.4.4)'')

<big>[{{github_url}}/releases/download/v{{version_windows_AIO32}}/{{filename_windows_AIO32}}.exe Windows Installer (32-bit) {{version_windows_AIO32}}]
    
[{{github_url}}/releases/download/v{{version_windows_AIO64}}/{{filename_windows_AIO64}}.exe Windows Installer (64-bit) {{version_windows_AIO64}}]</big>

After download: double-click to install Gramps. '''Make sure that you select extra dictionary and language files before you actually start the install process. Standard setup is English only!'''

{{man tip|Shortcuts|Once installed one shortcut is placed on the desktop and in the Start menu two shortcuts are added, please only use the first shortcut, unless requested by a developer. 1) ''GrampsAIO'''XX''' ''{{version}}'' {{man menu|<--- Shortcut for everyday use of Gramps}} 2) ''GrampsAIO'''XX''' ''{{version}}''-console)}}

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

Use the Windows AIO version, please use the download links above. For more information about individual versions, console and debug modes, release notes, etc., look at [[GrampsAIO-4|this page]] (English only).

Alternative independent '''Legacy''' MS Windows version [[#3|[3]]].

You may also install using the alternative independent Gramps Chocolatey Package [[#4|[4]]].

== Mac OS X ==

[[File:macos_200x200.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]]. Read the [[Mac OS X:Application package|before installation]] instructions.

Supports Mac OS X in all versions 10.5 (Leopard) and later.

<big>[{{github_url}}/releases/download/v{{version_Mac}}/{{Filename_mac_intel}}.dmg Intel {{version_Mac}}]</big>
    
<big>[{{github_url}}/releases/download/v{{version_Mac}}/{{Filename_mac_ppc}}.dmg Power PC {{version_Mac}}]</big>

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next drag the Gramps application to your application folder and double-click to launch it [[#2|[2]]].

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

{{man tip|Spell Checking:|Gramps uses a different spell checker than the one provided by Mac OS X, with different spelling dictionary requirements. We can't easily provide dictionaries for all of the supported languages in the bundle, but they're easily downloaded from [http://extensions.openoffice.org/ OpenOffice.org's website]. Download the language you want and save it, then navigate to the download in Finder. Most browsers have a downloads window that offers "Show in Finder" in its context menu. Change the file extension from <tt>oxt</tt> to <tt>zip</tt>, then from the context menu select '''Open with... Archive Utility''' to decompress it. In the decompressed folder or perhaps in a subfolder you'll find the dictionary files in pairs, <tt>foo.aff</tt> and <tt>foo.dic</tt>. Some languages have more than one pair with a README file to explain why. Select a pair and copy it to /Library/Dictionaries (you'll have to authenticate with an administrator id and password), and if 'foo' isn't already a language or locale code, make it one. For example, the French package includes several pairs with names like <tt>fr-moderne.aff</tt> and <tt>fr-moderne.dic</tt>. The spell checker doesn't recognize those names, so when you copy them to /Library/Dictionaries you must rename them to <tt>fr.aff</tt> and <tt>fr.dic</tt> or <tt>fr_FR.aff</tt> and <tt>fr_FR.dic</tt>. You can have more than one dictionary pair installed if you use several languages, but one '''must''' match the language you use for Gramps or spell checking won't be enabled at all.}}

{{-}}

== BSD ==

[[File:Bsd daemon.jpg|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux and BSD distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version (advanced users only)]]</big>
{{-}}

== Live CD ==

[[File:Download_link.png|150px|left|link=http://sourceforge.net/projects/gramps/files/OldFiles/3.2.5/lgenealogy-6.1-desktop-i386.iso]]
'''Linux live CD Demonstration''' includes Gramps {{Version Linux Live CD}} pre-installed to trial, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn..). [[Linux_Genealogy_CD#Obtaining_the_CD|Obtaining the CD]] (727 MB) [[Linux Genealogy CD|Linux Genealogy CD based on Ubuntu 10.10 (Maverick Meerkat)]]. If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install latest [http://www.ubuntulinux.org/ Ubuntu 14.04.3] and Gramps from the CD anytime you like.
{{-}}
[[File:Download_link.png|150px|left|link=http://cdimage.ubuntu.com/edubuntu/releases/14.04/release/]]
'''Edubuntu 14.04.3''' includes Gramps 4.0.3-1 (For information about Edubuntu [http://www.edubuntu.org/news/14.04.2-release visit])
{{-}}

=== Online Demonstration ===
You can also try an online demonstration of Gramps on rollApp:
* https://www.rollapp.com/app/gramps
Select '''Launch Online''' then '''Test Drive(Opening/saving files will not be available)'''

{{man note|Note|This is a commercial limited trial and not endorsed by the Gramps-project. Beware of third parties having your genealogical data.}}
{{-}}

== Linux and BSD distributions ==
{{man note|These packages are built and supported by the distros.|Please report any problems with them to the package maintainer.}}
Most Linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

— current stable release
Debian 7 ("wheezy") — obsolete stable release
— obsolete stable release

{| {{prettytable}}
!Distribution
!GUI Package manager
!Current versions
!Notes
|-
|[[File:Debianopenlogo-32.png]]''' [[Debian]] '''
|Add/Remove Software
|Debian 7 ("wheezy") (old stable): Gramps 3.4.0 Debian 8 ("jessie")(stable): Gramps 4.1.1 Debian 8 ("jessie")(backports): Gramps 4.2.4 stretch (testing): Gramps 4.2.4 [http://packages.debian.org/sid/gramps sid (unstable)]: Gramps 4.2.4
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[File:Ubuntu_32x32.png]]''' Ubuntu '''
|Software Centre
|Precise (12.04 LTS): Gramps 3.3.1 Trusty (14.04 LTS): Gramps: 4.0.3 Trusty Backports (14.04 LTS): Gramps: 4.0.4 Xenial (16.04 LTS): Gramps: 4.2.2 Yakkety (16.10): Gramps: 4.2.3 Zesty (Development: 17.04): Gramps: 4.2.4
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]
|-
|'''Linux Mint'''
|Software Manager
|Isadora (Gramps 3.2.0-1) Lisa (Gramps 3.3.1-1) Olivia (Gramps 3.4.0-1) Qiana (Gramps 4.0.3+dfsg-2) Sarah (Gramps 4.2.2~dfsg-1)
|[http://community.linuxmint.com/software/view/gramps available versions]
|-
|[[File:Fedora_32x32.png]]''' Fedora '''
|Add/Remove Software (Gnome) or Software Management (KDE)
|Rawhide (Gramps 4.2.5) Fedora 25 (Gramps 4.2.4) Fedora 24 (Gramps 4.2.4) Fedora 23 (Gramps 4.2.4)
|[https://apps.fedoraproject.org/packages/gramps available versions] / Note:The Fedora and Red Hat Projects were merged on September 22, 2003.
|-
|'''[https://www.mageia.org/en/ Mageia]'''
||[https://wiki.mageia.org/en/Installing_and_removing_software drakrpm (or rpmdrake)]
|Mageia Caulron: Gramps 4.2.4 Mageia 5.0: Gramps 4.1.3
|[http://mageia.madb.org/package/show/name/gramps Mageia App Db - gramps]
|-
|''' openSUSE '''
|[https://en.opensuse.org/YaST_Software_Management YaST]
|openSUSE Tumbleweed: Gramps 4.2.4 openSUSE Leap 42.1: Gramps 4.2.0 openSUSE 13.2: Gramps 4.0.4
|[http://software.opensuse.org/package/gramps available versions] See note [http://gramps.1791082.n4.nabble.com/ahnenforschung-familie-ihle-de-td4672224.html#a4672266] : Gramps 4.2 can be installed on Opensuse 13.2 ( if you add the 'openSUSE BuildService - GNOME:Apps' )
|-
|'''Slackware'''
|
|Slackware 14.1: Gramps 4.0.3
|[http://pkgs.org/search/?keyword=gramps available versions]
|-
|'''[https://www.netbsd.org/ NetBSD]'''
|
|NetBSD: Gramps 3.4.4
|[http://pkgsrc.se/databases/gramps3 available versions]
|-
|'''[https://www.freebsd.org/ FreeBSD]'''
|
|FreeBSD: Gramps 4.2.3
|[http://portsmon.freebsd.org/portoverview.py?category=science&portname=gramps available versions]
|-
|'''TrueOS'''
|
|PC-BSD: Gramps 3.4.8
|[http://web.pcbsd.org/pc-bsd-is-now-trueos/ 2016/09/01 - PC-BSD in now TrueOS]
|-
|'''[https://www.openbsd.org/ OpenBSD]'''
|
|OpenBSD: Gramps 4.2.3
|[http://openports.se/misc/gramps available versions]
|-
|'''Arch Linux'''
|
| Gramps 4.2.5
|[https://www.archlinux.org/packages/community/any/gramps/ available versions]
|-
|'''Gentoo Linux'''
|
| Gramps 4.2.4
|[https://packages.gentoo.org/packages/app-misc/gramps available versions]
|-
|
|
|
|
|}

{{-}}

== Linux: Install latest version ==

If your distribution doesn't ship with Gramps or you wish to install a different version than it ships with, you could try to install the latest version of Gramps manually. Instructions are given below for a number of distributions.

{{man warn|1=Warning|2=This should only be attempted by experienced users, and after you have backed up your Family Tree.

The version of Gramps that has been included in your distribution will have been tested to work with the components in that distribution. If you try to install a different version of Gramps there is a possibility that the components needed for the new version of Gramps are not available for your distribution, or they are available, but don't work properly. You might not discover that there is a problem till you have already done some work with the new version of Gramps.

If you already have Gramps installed, and you are only making a 'point' upgrade (i.e. from Gramps x.y.z to x.y.z+1, e.g. from 3.4.3 to 3.4.4), then it is likely but not certain that Gramps will continue to work. However, if the change is much greater, especially if it is a major version change (e.g. from 2.y.z to 3.y.z), then the danger that it does not work properly is much greater.}}

[[Image:Debianopenlogo-32.png]]'''[[Debian]]''' and [[Image:Ubuntu_32x32.png]]''' Ubuntu ''' [{{github_url}}/releases/v{{version}} Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved (change the filename to match the one you downloaded).

sudo dpkg -i python-gramps_{{version}}-1_all.deb
or
sudo dpkg -i python3-gramps_{{version}}-1_all.deb

For other distributions, [[Image:Download_link.png|150px|link={{github_url}}/releases/v{{version}}]] the source and follow the instructions for [[Linux:Build from source]]

== Notes ==

[1]
Backup to Gramps XML. You will find backup in the Family Tree menu of recent Gramps versions, otherwise use export in the same menu but '''uncheck privacy options''' in the Exporter Assistant in order to export all data

[2]
Alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.

[3]
An alternative independent '''Legacy''' version is [http://sourceforge.net/projects/portableapps/files/Gramps%20Portable/ GrampsPortable_{{version_windows_portable}}.paf.exe] (29.0 MB)
[http://portableapps.com/apps/education/gramps_portable Portable Gramps from PortableApps.com] includes all dependencies required for Windows. ''Note:You can install it on C: then to run Gramps type C:\PortableApps\GrampsPortable\GrampsPortable.exe (Or the path you installed it to) or make a shortcut to that file on your desktop or start-menu.'' By Bart.S - '''[http://portableapps.com/blog/84601 Please report packaging issues to the author.]''' (2012-09-07)

[4]
Chocolatey NuGet is a Machine Package Manager, somewhat like apt-get, but built with Windows in mind. [https://chocolatey.org/packages/gramps/ Gramps Chocolatey Package]

== See also ==
* [[Previous releases of Gramps]]

[[Category:Documentation]]

Brief introduction to Git

2015-08-06T14:00:57Z

Ennoborg: /* Stable version */ changed to gramps42

The development source code of Gramps is stored in the Git repository at GitHub.

;https://github.com/gramps-project/gramps/.

This helps synchronizing changes from various developers, tracking changes, managing releases, etc. If you are reading this, you probably want to do one of two things with Git: either download the latest source or the development version, or else upload your changes (if you have write access to the repository) or [[Brief_introduction_to_Git#Send_your_contribution_without_rights_to_push|submit a pull request]] with the changes (if you don't have write access).

== Install Git on your system ==

* Debian/Ubuntu: <code>sudo apt-get install git</code>
* Fedora: <code>yum install git-core</code>
* Mac OS X (intel) Download git from here http://git-scm.com/download/mac.
* Mac OS X (PPC) Although the git download above is called 'git-1.8.4.2-intel-universal-snow-leopard.dmg', implying that this is a universal binary, in fact only the installer is universal, the binary to be installed in actually intel only. On a PPC you will need to build git manually. Follow the instructions here: http://jnorthr.wordpress.com/2013/03/29/building-a-git-client-1-8-2-on-apple-imac-ppc-osx-10-5-8/. I think you will also need some additional tools like 'msgfmt'. I don't think this is installed by the Apple development tool Xcode, but fortunately I have it either via fink which I installed some time ago, or via MacPorts which I installed more recently.

: Mac OS X (PPC) Eclipse. If you are using Eclipse on a PPC, then there may be missing components for installing the latest version of EGit, depending on your version of Eclipse. If you have the Helios version of Eclipse, then you will not be able to install the latest EGit because you will get ''requires 'org.eclipse.team.core 3.6.100' but it could not be found''. Installing EGit version 2.0 from http://download.eclipse.org/egit/updates-2.0 should work if you uncheck the EGit Import Support feature when selecting what to install. You will obviously lose the Import Support feature. See [http://stackoverflow.com/questions/15281273/dependency-fail-installing-egit-on-eclipse-indigo here]. You will probably need to do ''git config core.filemode false'' to get round [https://bugs.eclipse.org/bugs/show_bug.cgi?id=307560 this bug] as suggested [http://stackoverflow.com/questions/1257592/how-do-i-remove-files-saying-old-mode-100755-new-mode-100644-from-unstaged-cha here].

If you use Eclipse then will need to locally ignore the Eclipse files as suggested at 5.2.2 [http://www.vogella.com/tutorials/EclipseGit/article.html#d186251e250 here].

cd ~/
touch .gitignore
echo ".metadata" >> .gitignore
echo ".project" >> .gitignore
echo ".pydevproject" >> .gitignore
echo "windows" >> .gitignore

Git includes your name and email address in commits. To configure them, use the following commands:
git config --global user.name "John Smith"
git config --global user.email john@example.com

Git will automatically convert line endings for you. Use the following settings:
git config --global core.autocrlf true # Windows
git config --global core.autocrlf input # Linux/Mac

== Obtaining a copy of the Gramps repository ==

The description below is for a single working folder at ~/Gramps. An alternative approach for [[Brief_introduction_to_Git#Multiple_Working_Folders|Multiple Working Folders]] is described below.

To obtain a copy of the Gramps repository, type the following in the command line if you '''don't have a GitHub account''':
git clone <nowiki>https://github.com/gramps-project/gramps.git</nowiki> Gramps

You should see the downloading progress reported in your terminal.

If you have a GitHub account, use ssh instead:
git clone <nowiki>git@github.com:gramps-project/gramps.git</nowiki> Gramps

You will need a [https://help.github.com/articles/generating-ssh-keys/ SSH Key] in order to authenticate using this method. '''Before you accept any host keys, make sure you [https://help.github.com/articles/what-are-github-s-ssh-key-fingerprints/ verify the SSH fingerprint]''' of github.com.

You can check your connection by:
ssh -T git@github.com
which should return:
Hi <name>! You've successfully authenticated, but GitHub does not provide shell access.

== Basic Work Flow ==

The basic work flow after you've checked out the repository is update, develop, commit, update again, push.
To update the current branch, run

git pull --rebase

As a general rule ''always'' use <tt>git pull --rebase</tt> to avoid creating unnecessary merge commits. Note that one must have no uncommitted edits when running <tt>git pull</tt>.

The differences between "git pull" and git pull --rebase" is explained well [http://stackoverflow.com/a/3357174/2615612 here].

To review your changes before a commit, type:

git status

To commit your changes locally, use the following command:

git commit

Which will bring up the default $EDITOR to create a commit message. If you are fixing a bug, the first line of the commit message should be the bug number and title, otherwise a brief statement of purpose. Skip a line and describe what you did.

* All developers should read Gramps [[Committing policies]]

If the commit is a minor change that can be described entirely in the subject, you can instead use:

git commit -am "message describing the nature of the change"

Try to keep your commits digestible and understandable. A large changeset can be broken into several commits that "tell a story" about how the changeset moves the program from its old behavior to its new one.

To push your changes to the Gramps repository, you need to have cloned the Gramps source code with ssh, and have push access to the Gramps repository (the Gramps admins can give you this, [[Contact|Brian Matherly or Benny Malengier]]). First update again to make sure that you can fast-forward the repository, then push:

git pull --rebase
git push

Since uploading is a potentially dangerous operation, most people do not obtain write access to the git repository. In this case, create a new bug on the [http://bugs.gramps-project.org bug tracker] and attach a patch to it. See the [[Brief_introduction_to_Git#Making_a_patchfile|make a patchfile]] section for details.

If someone else has made changes that interfere with yours, you will get a conflict error when you pull. You will have to resolve that conflict and re-commit (you can use <tt>git commit --amend</tt> if it affects only the last ''unpushed'' commit) before git will push successfully.

:Also see: [[Getting started with Gramps Trunk]].

== Types of branches ==
When you clone the Gramps repository, a branch called ''master'' will be created for you. This contains the latest development version of Gramps. Gramps maintains different branches in several categories:

* ''master'' - There is only one ''master'' branch. All new feature and most bug-fix development happens in the ''master'' branch. New releases never come from the ''master'' branch.

* ''maintenance'' - There are many maintenance branches, though usually only one or two are active. A maintenance branch is created from the ''master'' branch when all the features for a release are complete. New features are not committed to maintenance branches. Releases only come from active maintenance branches; a branch is no longer active when no further releases are planned for it. Inactive branches should not have any changes committed to them. The purpose of maintenance branches is to allow the line of code to stabilize while new features are added in the ''master'' branch. In order to prevent regressions (fixed bugs reoccurring in later releases), it is a "best practice" to fix bugs on the master branch and then to backport them to the current maintenance branches.

* ''geps'' - These are meant for development of [[Portal:Enhancement_Proposals|Gramps Enhancement Proposals]]. Most of the time GEPS are developed in the ''master'' branch. Occassionally a GEP will require extensive reworking or long periods when the code base is ususable. In these cases a branch in ''geps'' can be used as a temporary development area. Once the hard work is done the change should be merged into the trunk and the ''geps'' branch should be removed. ''geps'' branches should follow the naming convention ''gep-<###>-<descriptive text>'' e.g. ''gep-013-server''. Please read the [[#Working with development branches]] section for help with managing these branches.

Tags are created for each Gramps release. The first two digits of the Gramps version number are reserved to indicate the maintenance branch the code came from. The last digit indicates the revision from that maintenance branch. For example, 3.0.4 would indicate the 5th release from the 3.0 branch (3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4).

Here is a hypothetical example:
Imagine that the current version of Gramps is 8.3.2. A new series of features has been added in the ''master'' branch and are ready for release. A new maintenance branch is created from the ''master'' branch named 8.4 (or possibly 9.0 depending on the nature of the new features). New features continue to be added in the ''master'' branch that will not be included in the 8.4 series of releases, but will be included in the 8.5 series. Bug fixes continue to occur in the 8.4 branch until the code is deemed worthy of release. At that time, a release is tagged from the 8.4 maintenance branch and named 8.4.0. Some time after the release of 8.4.0, some bugs are found and fixed in the 8.4 maintenance branch. Those bug fixes are released as 8.4.1.

== Stable version ==

There are several versions of the Gramps source code in Git. The development branch for small changes and bug fixes is
''maintenance/gramps42''

By default, the remote server you cloned the Gramps repository from is called ''origin''.

To see a list of branches on the server, type:

git remote show origin

To create a local branch which tracks a branch on the server, use:

git checkout -b gramps42 origin/maintenance/gramps42

{{man warn|1=Warning|2=This sets the name of the local branch to "gramps42" (not "maintenance/gramps42"). This may cause problems when you come to "push" your changes back to the server, depending on the "push.default" configuration settings (see below). You can change the name of the local branch by "git branch -m old new" i.e.
git branch -m gramps42 maintenance/gramps42}}

This is known as a "tracking" branch.

To list the available branches, type:

git branch

The current branch is marked by an asterisk.

To switch to another branch, type:

git checkout <branch>

To look at any stable release version, type:

git checkout <tag> -b <new_local_branch_name>

The following configuration option simplifies pushing a branch back to the server:

git config --global push.default upstream

You can then use:

git push

{{man warn|1=Warning|2=This will push commited changes from '''all''' local branches, not just the one that is currently checked-out. If you want to ensure that only one branch is pushed, then use:
git push origin gramps42:maintenance/gramps42}}

=== Where for bugs? ===

The [http://bugs.gramps-project.org bug tracker] has in the right top angle different projects. Choose project ''trunk'' and submit an issue.

=== Making a patchfile ===

A patchfile is a text file with your changes which can be sent by email to somebody, or posted/uploaded to the bug tracker (against a bug you are fixing or a feature request which you are solving for instance), etc...

These instructions tell how to make a patchfile against the ''master'' branch, so that your changes are added to the next major release of Gramps. (To make a patchfile against a branch the process is similar, with some slight changes.)

First create a new branch to work in:

git checkout -b fix

Then use your favorite editor to change whatever file(s) you want. Add the files you have changed to the staging area and commit them.

Obtain the latest changes from the server.

git checkout master
git pull --rebase

Next, rebase your fix again the ''master'' branch. This will ensure that your patch will apply cleanly.

git rebase master fix

This will leave you in the fix branch.

Finally, create a patchfile, using:

git format-patch master --stdout > fix.patch

You now have a patchfile that can be sent by email, or attached to a bug report. The patch can be applied using the 'git apply' command.

== Working with development branches ==

Creating branches with Git is quick and easy.

Here is a quick crib sheet:

=== Creating a branch ===

To create a branch from the ''master'' branch:

git checkout master
git branch gep-014-fab-feature

To make this branch available on the server use:

git push origin gep-014-fab-feature

=== Merging changes from the branch back into the ''master'' branch ===

When you are ready to merge your changes back into the ''master'' branch:

git checkout master
git merge gep-014-fab-feature
git push

=== Removing branches ===

It is important that branches are removed once they have been merged into the trunk or have been abandoned. To remove a branch:

git branch -d gep-014-fab-feature

To remove a branch from the server, use:

git push origin :gep-014-fab-feature

The developers reserve the right to remove branches that have been dormant for more than 1 year.

=== Applying a fix to another branch ===

If you write a fix for the master branch, you may need to also apply it to a maintenance branch.

To apply a commit from the branch to a maintenance branch:
git checkout gramps41
git cherry-pick fix

Then you may have to fix things that could not be applied due to conflicts. The patch program would mark the conflicts with the <<<<<<, ======, and >>>>>> signs. You will then need to push your changes.

If you apply a small fix that applies cleanly to another branch, it can be done like this (assuming you've just committed the fix to master in a single commit):
git checkout gramps41
git diff master^ master | git apply
If `git apply' fails, nothing will be changed in the working copy, and you can try to resolve the conflicts by cherry-picking, or manually saving the diff result, using the "patch" program, and resolving the conflicts.

=== Workflow ===

Before switching to another branch it is useful to remove untracked files created by the build process. You can do this with the following command:

git clean -dxf

== Useful Tips ==

=== Getting help ===

Git has excellent man pages. You can view the manual page for a Git command, by using one of the following:

git help <verb>
git <verb> --help
man git-<verb>

For example, to get help on the 'git log' command, type:

git help log

=== Configuration settings ===

You can set your default editor with:

git config --global core.editor <editor>

To enable colored command line output, use:

git config --global color.ui auto

=== Some procedural recommendations ===

# Always do ''git pull --rebase'' before pushing changes to the server. If necessary get advice about handling conflicts.
# Always do ''git status'' and look for staged files that are unexpected or unintended. This is a *very important* sanity check.

;And here are a couple of incidental suggestions

* Avoid grouping unrelated changes; better to divide into separate commits for the following reasons: a better log entry; easier troubleshooting/reverting. (and probably more).

* Similar to above, it may be better to make small incremental changes than one big one (if possible). Interim changes should not introduce breakage, of course. For instance, if you change code in gramps/ and do associated translation changes in po/, you might want to commit the changes in po/ in a commit following the commit(s) with the changes in gramps/.

* logs are important -- please give some thought to the log message. All developers should read the [[Committing policies]].

== Multiple Working Folders ==
{{out of date}}

Using a single working folder as described above entails context switching when developing across multiple branches. For example:
* develop and test changes on the gramps41 branch,
* commit or stash the changes,
* clean to remove untracked files created by the development process,
* checkout the master 'branch',
* build (python setup.py build),
* cherry pick the changes from the gramps41 branch into the master 'branch',
* test and if necessary develop the changes to master,
* commit or stash the changes.

If the changes are all OK, then they can pushed to the GitHub repository.

An alternative is to clone the GitHub repository for each branch, but although git saves local disk space by using hard links for locally cloned repositories, keeping the local repositories in sync is complex.

The problem is well explained [http://finik.net/2010/10/24/multiple-working-folders-with-single-git-repository/ here] as is the solution, which is to create copies of the working directories only. This is done by a script that is in the git 'contrib' directory [http://nuclearsquid.com/writings/git-new-workdir/ git-new-workdir].

Assuming that the directory structure would be:
~
+-Gramps
+-repository
+-.git
+- etc
+-gramps34
+-gramps40
+-gramps41
+-master

The approach would be:
* checkout from the GitHub repository (it doesn't much matter which branch you checkout as we are not going to use this branch directly):

git checkout -b Gramps/repository origin/master

* then create the various working copies:

git-new-workdir Gramps/repository ~/Gramps/gramps34 maintenance/gramps34
git-new-workdir Gramps/repository ~/Gramps/gramps40 maintenance/gramps40
git-new-workdir Gramps/repository ~/Gramps/gramps41 maintenance/gramps41
git-new-workdir Gramps/repository ~/Gramps/master master

You will then need to build the source, but this only needs to be done once, and the 'clean' step is not needed. See [[Getting_started_with_Gramps_development#Run_Gramps_from_the_source| Run from source]] and [[Running_a_development_version_of_Gramps| running]] which describes the process for 'gramps 3.4 and before' as well as after. For example:

cd ~/Gramps/gramps41
python setup.py build

== Browse Git ==

An alternative to the command line tools to view the Git repository is the [https://github.com/gramps-project/gramps online interface].

==Send your contribution without rights to push==

Check it into Git if you obtained the [[#Obtaining_a_copy_of_the_Gramps_repository|permission to do push]].
Otherwise you can [https://help.github.com/articles/fork-a-repo/ fork] the Gramps repository with and create a [https://help.github.com/articles/using-pull-requests/ pull request].

Since syncing a fork can create unwanted commits, you may need to [https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request rebase] your pull request first. Remember to replace edx and master with the actual names of the remote repository (upstream) and the branch you're working on.

== git2cl ==

The Gramps project does not keep a ChangeLog file under source control. All change history is captured by git automatically when it is committed. A ChangeLog file is generated from the git commit logs before each release using [[Brief_introduction_to_SVN#How_to_use_git2cl|git2cl]]. Developers should take care to make useful commit log messages when committing changes to git. Please read the [[Committing policies]] for details.

=== How to use git2cl ===

Starting with Gramps 3.0.0, we no longer have a <tt>ChangeLog</tt> file.

Instead, the list of changes is generated automatically using the standard <tt>git2cl</tt> script.

Note that <tt>git2cl</tt> is not included in the base installation of Git. With a Debian-based distro such as Ubuntu, you can get <tt>git2cl</tt> as follows:

sudo apt-get install git2cl

There typically are two <tt>ChangeLog</tt> files needed for releases; one in the main directory, and one in the <tt>po</tt> directory. You can generate these files with the following commands:

git log gramps-4.0.1.. --pretty --numstat --summary --no-merges | git2cl > ChangeLog
git log gramps-4.0.1.. --pretty --numstat --summary --no-merges -- po | git2cl > po/ChangeLog

== External links ==

*[http://git-scm.com/ Git]
*[http://git-scm.com/book Git Book]
*[https://help.github.com/articles/generating-ssh-keys/ GitHub SSH Keys]
*[https://help.github.com/articles/what-are-github-s-ssh-key-fingerprints/ GitHub SSH Key Fingerprints]

[[Category:Developers/General|B]]

Running a development version of Gramps

2015-07-07T17:47:42Z

Ennoborg: /* Preparation */ outdated clone command removed

== Preparation ==

* Install a recent version of Ubuntu, or Mint, which is Ubuntu based. ''The steps in this document have been tested with Ubuntu 7.04, 7.10, 8.04, 10.04, 10.10 and 12.10, and Mint 14''

* Install a text editor if you plan on modifying the Gramps source. You can use any text editor such as gedit, kate, or sourcenav (<tt>sudo apt-get install sourcenav</tt>), erik4, SPE, or [http://www.eclipse.org Eclipse] with the python plugin. Instructions on [[Development using Eclipse and Pydev|installing and configuring Eclipse for Gramps development]]. Note the [[Programming Guidelines|programming guidelines for Gramps]].

* [[Brief_introduction_to_Git#Obtaining_a_copy_of_the_Gramps_repository|Clone the Gramps repository]]

== Gramps 4.0 and the master branch ==

{{man warn|1=warning|2=Do not open your existing databases with the master branch, it might destroy your data, and will make it impossible to use the data in the stable version {{stable_branch}}. To try it out, export your database to a gramps xml file, eg <code>test_master.gramps</code>, create a new family tree in the master branch, and import this xml file.}}

For the internationalization code to work, you need to have the translation tools.

On Debian, just run (as root) - ('''Only if Debian installs Gramps 4.0+ as Gramps version!):
apt-get build-dep gramps

On Fedora 8 - 10 (Fedora is up to version 17 now so does this still apply?), you will need:
yum install intltool gnome-doc-utils gettext git-core rcs

=== Build ===
Now go into the top-level directory and type:

python setup.py build

{{man warn|1=Warning|2=Do not install the development version if you don't know how to version python modules. That is, do '''not''' type {{man label|sudo python setup.py install}}. }}

=== Run ===
==== Option 1: run from source repo ====
Here, we use the code in working directory to run Gramps. This means that compiled python files will be stored there. This is not ideal, but the easiest way to develop Gramps, as changes are immediately picked up by the code.

Copy the const.py file created in build to your source directory if you want to use your source directory to work with Gramps:
cp build/lib.linux-$(uname -m)-2.7/gramps/gen/const.py gramps/gen/const.py
python Gramps.py

''Note'': the <code>lib.linux-$(uname -m)-2.7</code> folder name vary depending on your system (i686 or x86_64).

That is it. If you installed some dependencies of Gramps in non-default positions, you need to indicate with PYTHONPATH where they can be found, and with LD_LIBRARY_PATH where link libraries can be found. Eg, if you install GTK and spell checking from source too, you will need something like:
PYTHONPATH=/usr/local/lib/python2.7/site-packages/ LD_LIBRARY_PATH=/usr/local/lib python Gramps.py

==== Option 2: use the build code ====
Here, we use the code build in <code>trunk/build</code> directory to run Gramps. For compiled programs this is the only way, but for Gramps nothing is compiled. It is not bad however to keep your code separated from your execution, as deleting the build directory is easy. After a code change in your source, you then need to run however <code>python setup.py</code> again to update the build direcotry. To run Gramps from build, do
cd trunk/build/lib.linux-$(uname -m)-2.7/
python -c 'from gramps.grampsapp import main; main()'

Again, it might be needed to set with PYTHONPATH where dependencies can be found, and with LD_LIBRARY_PATH link libraries, see option 1.

If you point your PYTHONPATH to the build directory, you can actually run Gramps from a random directory. Like this:

cd
PYTHONPATH=~/gramps-trunk/build/lib.linux-$(uname -m)-2.7/ python -c 'from gramps.grampsapp import main; main()'

So, more general:
cd
PYTHONPATH=~/gramps-trunk/build/lib.linux-$(uname -m)-2.7/:/usr/local/lib/python2.7/site-packages/ LD_LIBRARY_PATH=/usr/local/lib python -c 'from gramps.grampsapp import main; main()'

If the build directory is in your PYTHONPATH, you can also just execute the grampsapp.py module. So this will work too:
cd ~/gramps-trunk/build/lib.linux-$(uname -m)-2.7/gramps
PYTHONPATH=~/gramps-trunk/build/lib.linux-$(uname -m)-2.7/ python grampsapp.py

or again more generally
PYTHONPATH=~/gramps-trunk/build/lib.linux-$(uname -m)-2.7/:/usr/local/lib/python2.7/site-packages/ LD_LIBRARY_PATH=/usr/local/lib python grampsapp.py

'''Note''': At the time of writing, only the last, so using grampsapp.py works, as not all imports in Gramps have been converted to relative or absolute imports. This conversion will be finished by end of 2012 however.

{{man note|1=Known Problems|2=Some problems are due to the migration from GTK2 to GTK3: [[GEPS_029:_GTK3-GObject_introspection_Conversion#Problems|list of known problems]]}}

== Gramps 3.4 and before ==

* Install the tools we will need:
sudo apt-get install build-essential gnome-common libglib2.0-dev git-core gettext

=== Build ===
* Get ready to build Gramps:
The old versions of Gramps use autotools, so you need to run:
./autogen.sh

* Build GRAMPS:
make

=== Run ===
* Run Gramps:
python src/gramps.py

At this point, any time you want to update to the latest version of Gramps, simply run:
git pull --rebase
python src/gramps.py

If some of the Gramps constants have changed and you obtain an error in const.py, rerun the commands <tt>autogen.sh</tt> and <tt>make</tt>.

[[Category:Developers/General]]

Brief introduction to Git

2015-06-18T20:19:26Z

Ennoborg: /* Send your contribution without rights to push */ rebase information added

The development source code of Gramps is stored in the Git repository at GitHub.

;https://github.com/gramps-project/gramps/.

This helps synchronizing changes from various developers, tracking changes, managing releases, etc. If you are reading this, you probably want to do one of two things with Git: either download the latest source or the development version, or else upload your changes (if you have write access to the repository) or [[Brief_introduction_to_Git#Making_a_patchfile|make a patchfile]] (if you don't have write access).

== Install Git on your system ==

* Debian/Ubuntu: <code>sudo apt-get install git</code>
* Fedora: <code>yum install git-core</code>
* Mac OS X (intel) Download git from here http://git-scm.com/download/mac.
* Mac OS X (PPC) Although the git download above is called 'git-1.8.4.2-intel-universal-snow-leopard.dmg', implying that this is a universal binary, in fact only the installer is universal, the binary to be installed in actually intel only. On a PPC you will need to build git manually. Follow the instructions here: http://jnorthr.wordpress.com/2013/03/29/building-a-git-client-1-8-2-on-apple-imac-ppc-osx-10-5-8/. I think you will also need some additional tools like 'msgfmt'. I don't think this is installed by the Apple development tool Xcode, but fortunately I have it either via fink which I installed some time ago, or via MacPorts which I installed more recently.

: Mac OS X (PPC) Eclipse. If you are using Eclipse on a PPC, then there may be missing components for installing the latest version of EGit, depending on your version of Eclipse. If you have the Helios version of Eclipse, then you will not be able to install the latest EGit because you will get ''requires 'org.eclipse.team.core 3.6.100' but it could not be found''. Installing EGit version 2.0 from http://download.eclipse.org/egit/updates-2.0 should work if you uncheck the EGit Import Support feature when selecting what to install. You will obviously lose the Import Support feature. See [http://stackoverflow.com/questions/15281273/dependency-fail-installing-egit-on-eclipse-indigo here]. You will probably need to do ''git config core.filemode false'' to get round [https://bugs.eclipse.org/bugs/show_bug.cgi?id=307560 this bug] as suggested [http://stackoverflow.com/questions/1257592/how-do-i-remove-files-saying-old-mode-100755-new-mode-100644-from-unstaged-cha here].

If you use Eclipse then will need to locally ignore the Eclipse files as suggested at 5.2.2 [http://www.vogella.com/tutorials/EclipseGit/article.html#d186251e250 here].

cd ~/
touch .gitignore
echo ".metadata" >> .gitignore
echo ".project" >> .gitignore
echo ".pydevproject" >> .gitignore
echo "windows" >> .gitignore

Git includes your name and email address in commits. To configure them, use the following commands:
git config --global user.name "John Smith"
git config --global user.email john@example.com

Git will automatically convert line endings for you. Use the following settings:
git config --global core.autocrlf true # Windows
git config --global core.autocrlf input # Linux/Mac

== Obtaining a copy of the Gramps repository ==

The description below is for a single working folder at ~/Gramps. An alternative approach for [[Brief_introduction_to_Git#Multiple_Working_Folders|Multiple Working Folders]] is described below.

To obtain a copy of the Gramps repository, type the following in the command line if you '''don't have a GitHub account''':
git clone <nowiki>https://github.com/gramps-project/gramps.git</nowiki> Gramps

You should see the downloading progress reported in your terminal.

If you have a GitHub account, use ssh instead:
git clone <nowiki>git@github.com:gramps-project/gramps.git</nowiki> Gramps

You will need a [https://help.github.com/articles/generating-ssh-keys/ SSH Key] in order to authenticate using this method. '''Before you accept any host keys, make sure you [https://help.github.com/articles/what-are-github-s-ssh-key-fingerprints/ verify the SSH fingerprint]''' of github.com.

You can check your connection by:
ssh -T git@github.com
which should return:
Hi <name>! You've successfully authenticated, but GitHub does not provide shell access.

== Basic Work Flow ==

The basic work flow after you've checked out the repository is update, develop, commit, update again, push.
To update the current branch, run

git pull --rebase

As a general rule ''always'' use <tt>git pull --rebase</tt> to avoid creating unnecessary merge commits. Note that one must have no uncommitted edits when running <tt>git pull</tt>.

The differences between "git pull" and git pull --rebase" is explained well [http://stackoverflow.com/a/3357174/2615612 here].

To review your changes before a commit, type:

git status

To commit your changes locally, use the following command:

git commit

Which will bring up the default $EDITOR to create a commit message. If you are fixing a bug, the first line of the commit message should be the bug number and title, otherwise a brief statement of purpose. Skip a line and describe what you did.

* All developers should read Gramps [[Committing policies]]

If the commit is a minor change that can be described entirely in the subject, you can instead use:

git commit -am "message describing the nature of the change"

Try to keep your commits digestible and understandable. A large changeset can be broken into several commits that "tell a story" about how the changeset moves the program from its old behavior to its new one.

To push your changes to the Gramps repository, you need to have cloned the Gramps source code with ssh, and have push access to the Gramps repository (the Gramps admins can give you this, [[Contact|Brian Matherly or Benny Malengier]]). First update again to make sure that you can fast-forward the repository, then push:

git pull --rebase
git push

Since uploading is a potentially dangerous operation, most people do not obtain write access to the git repository. In this case, create a new bug on the [http://bugs.gramps-project.org bug tracker] and attach a patch to it. See the [[Brief_introduction_to_Git#Making_a_patchfile|make a patchfile]] section for details.

If someone else has made changes that interfere with yours, you will get a conflict error when you pull. You will have to resolve that conflict and re-commit (you can use <tt>git commit --amend</tt> if it affects only the last ''unpushed'' commit) before git will push successfully.

:Also see: [[Getting started with Gramps Trunk]].

== Types of branches ==
When you clone the Gramps repository, a branch called ''master'' will be created for you. This contains the latest development version of Gramps. Gramps maintains different branches in several categories:

* ''master'' - There is only one ''master'' branch. All new feature and most bug-fix development happens in the ''master'' branch. New releases never come from the ''master'' branch.

* ''maintenance'' - There are many maintenance branches, though usually only one or two are active. A maintenance branch is created from the ''master'' branch when all the features for a release are complete. New features are not committed to maintenance branches. Releases only come from active maintenance branches; a branch is no longer active when no further releases are planned for it. Inactive branches should not have any changes committed to them. The purpose of maintenance branches is to allow the line of code to stabilize while new features are added in the ''master'' branch. In order to prevent regressions (fixed bugs reoccurring in later releases), it is a "best practice" to fix bugs on the master branch and then to backport them to the current maintenance branches.

* ''geps'' - These are meant for development of [[Portal:Enhancement_Proposals|Gramps Enhancement Proposals]]. Most of the time GEPS are developed in the ''master'' branch. Occassionally a GEP will require extensive reworking or long periods when the code base is ususable. In these cases a branch in ''geps'' can be used as a temporary development area. Once the hard work is done the change should be merged into the trunk and the ''geps'' branch should be removed. ''geps'' branches should follow the naming convention ''gep-<###>-<descriptive text>'' e.g. ''gep-013-server''. Please read the [[#Working with development branches]] section for help with managing these branches.

Tags are created for each Gramps release. The first two digits of the Gramps version number are reserved to indicate the maintenance branch the code came from. The last digit indicates the revision from that maintenance branch. For example, 3.0.4 would indicate the 5th release from the 3.0 branch (3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4).

Here is a hypothetical example:
Imagine that the current version of Gramps is 8.3.2. A new series of features has been added in the ''master'' branch and are ready for release. A new maintenance branch is created from the ''master'' branch named 8.4 (or possibly 9.0 depending on the nature of the new features). New features continue to be added in the ''master'' branch that will not be included in the 8.4 series of releases, but will be included in the 8.5 series. Bug fixes continue to occur in the 8.4 branch until the code is deemed worthy of release. At that time, a release is tagged from the 8.4 maintenance branch and named 8.4.0. Some time after the release of 8.4.0, some bugs are found and fixed in the 8.4 maintenance branch. Those bug fixes are released as 8.4.1.

== Stable version ==

There are several versions of the Gramps source code in Git. The development branch for small changes and bug fixes is ''maintenance/gramps{{stable_branch}}''.

By default, the remote server you cloned the Gramps repository from is called ''origin''.

To see a list of branches on the server, type:

git remote show origin

To create a local branch which tracks a branch on the server, use:

git checkout -b gramps41 origin/maintenance/gramps41

{{man warn|1=Warning|2=This sets the name of the local branch to "gramps41" (not "maintenance/gramps41"). This may cause problems when you come to "push" your changes back to the server, depending on the "push.default" configuration settings (see below). You can change the name of the local branch by "git branch -m old new" i.e.
git branch -m gramps41 maintenance/gramps41}}

This is known as a "tracking" branch.

To list the available branches, type:

git branch

The current branch is marked by an asterisk.

To switch to another branch, type:

git checkout <branch>

To look at any stable release version, type:

git checkout <tag> -b <new_local_branch_name>

The following configuration option simplifies pushing a branch back to the server:

git config --global push.default upstream

You can then use:

git push

{{man warn|1=Warning|2=This will push commited changes from '''all''' local branches, not just the one that is currently checked-out. If you want to ensure that only one branch is pushed, then use:
git push origin gramps41:maintenance/gramps41}}

=== Where for bugs? ===

The [http://bugs.gramps-project.org bug tracker] has in the right top angle different projects. Choose project ''trunk'' and submit an issue.

=== Making a patchfile ===

If you do not have push access to the repository, you can make a patchfile with your changes. This is a text file which can then be sent by email to somebody, or posted/uploaded to the bug tracker (against a bug you are fixing or a feature request which you are solving for instance), etc...

These instructions tell how to make a patchfile against the ''master'' branch, so that your changes are added to the next major release of Gramps. (To make a patchfile against a branch the process is similar, with some slight changes.)

First create a new branch to work in:

git checkout -b fix

Then use your favorite editor to change whatever file(s) you want. Add the files you have changed to the staging area and commit them.

Obtain the latest changes from the server.

git checkout master
git pull --rebase

Next, rebase your fix again the ''master'' branch. This will ensure that your patch will apply cleanly.

git rebase master fix

This will leave you in the fix branch.

Finally, create a patchfile, using:

git format-patch master --stdout > fix.patch

You now have a patchfile that can be sent by email, or attached to a bug report. The patch can be applied using the 'git apply' command.

== Working with development branches ==

Creating branches with Git is quick and easy.

Here is a quick crib sheet:

=== Creating a branch ===

To create a branch from the ''master'' branch:

git checkout master
git branch gep-014-fab-feature

To make this branch available on the server use:

git push origin gep-014-fab-feature

=== Merging changes from the branch back into the ''master'' branch ===

When you are ready to merge your changes back into the ''master'' branch:

git checkout master
git merge gep-014-fab-feature
git push

=== Removing branches ===

It is important that branches are removed once they have been merged into the trunk or have been abandoned. To remove a branch:

git branch -d gep-014-fab-feature

To remove a branch from the server, use:

git push origin :gep-014-fab-feature

The developers reserve the right to remove branches that have been dormant for more than 1 year.

=== Applying a fix to another branch ===

If you write a fix for the master branch, you may need to also apply it to a maintenance branch.

To apply a commit from the a branch to a maintenance branch:
git checkout gramps41
git cherry-pick fix

Then you may have to fix things that could not be applied due to conflicts. The patch program would mark the conflicts with the <<<<<<, ======, and >>>>>> signs. You will then need to push your changes.

If you apply a small fix that applies cleanly to another branch, it can be done like this (assuming you've just committed the fix to master in a single commit):
git checkout gramps41
git diff master^ master | git apply
If `git apply' fails, nothing will be changed in the working copy, and you can try to resolve the conflicts by cherry-picking, or manually saving the diff result, using the "patch" program, and resolving the conflicts.

=== Workflow ===

Before switching to another branch it is useful to remove untracked files created by the build process. You can do this with the following command:

git clean -dxf

== Useful Tips ==

=== Getting help ===

Git has excellent man pages. You can view the manual page for a Git command, by using one of the following:

git help <verb>
git <verb> --help
man git-<verb>

For example, to get help on the 'git log' command, type:

git help log

=== Configuration settings ===

You can set your default editor with:

git config --global core.editor <editor>

To enable colored command line output, use:

git config --global color.ui auto

=== Some procedural recommendations ===

# Always do ''git pull --rebase'' before pushing changes to the server. If necessary get advice about handling conflicts.
# Always do ''git status'' and look for staged files that are unexpected or unintended. This is a *very important* sanity check.

;And here are a couple of incidental suggestions

* Avoid grouping unrelated changes; better to divide into separate commits for the following reasons: a better log entry; easier troubleshooting/reverting. (and probably more).

* Similar to above, it may be better to make small incremental changes than one big one (if possible). Interim changes should not introduce breakage, of course. For instance, if you change code in gramps/ and do associated translation changes in po/, you might want to commit the changes in po/ in a commit following the commit(s) with the changes in gramps/.

* logs are important -- please give some thought to the log message. All developers should read the [[Committing policies]].

== Multiple Working Folders ==

Using a single working folder as described above entails context switching when developing across multiple branches. For example:
* develop and test changes on the gramps41 branch,
* commit or stash the changes,
* clean to remove untracked files created by the development process,
* checkout the master 'branch',
* build (python setup.py build),
* cherry pick the changes from the gramps41 branch into the master 'branch',
* test and if necessary develop the changes to master,
* commit or stash the changes.

If the changes are all OK, then they can pushed to the GitHub repository.

An alternative is to clone the GitHub repository for each branch, but although git saves local disk space by using hard links for locally cloned repositories, keeping the local repositories in sync is complex.

The problem is well explained [http://finik.net/2010/10/24/multiple-working-folders-with-single-git-repository/ here] as is the solution, which is to create copies of the working directories only. This is done by a script that is in the git 'contrib' directory [http://nuclearsquid.com/writings/git-new-workdir/ git-new-workdir].

Assuming that the directory structure would be:
~
+-Gramps
+-repository
+-.git
+- etc
+-gramps34
+-gramps40
+-gramps41
+-master

The approach would be:
* checkout from the GitHub repository (it doesn't much matter which branch you checkout as we are not going to use this branch directly):

git checkout -b Gramps/repository origin/master

* then create the various working copies:

git-new-workdir Gramps/repository ~/Gramps/gramps34 maintenance/gramps34
git-new-workdir Gramps/repository ~/Gramps/gramps40 maintenance/gramps40
git-new-workdir Gramps/repository ~/Gramps/gramps41 maintenance/gramps41
git-new-workdir Gramps/repository ~/Gramps/master master

You will then need to build the source, but this only needs to be done once, and the 'clean' step is not needed. See [[Getting_started_with_Gramps_development#Run_Gramps_from_the_source| Run from source]] and [[Running_a_development_version_of_Gramps| running]] which describes the process for 'gramps 3.4 and before' as well as after. For example:

cd ~/Gramps/gramps41
python setup.py build

== Browse Git ==

An alternative to the command line tools to view the Git repository is the [https://github.com/gramps-project/gramps online interface].

==Send your contribution without rights to push==

Check it into Git if you obtained the [[#Obtaining_a_copy_of_the_Gramps_repository|permission to do push]].
Otherwise you can [https://help.github.com/articles/fork-a-repo/ fork] the Gramps repository with and create a [https://help.github.com/articles/using-pull-requests/ pull request].

Since syncing a fork can create unwanted commits, you may need to [https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request rebase] your pull request first. Remember to replace edx and master with the actual names of the remote repository (upstream) and the branch you're working on.

== git2cl ==

The Gramps project does not keep a ChangeLog file under source control. All change history is captured by git automatically when it is committed. A ChangeLog file is generated from the git commit logs before each release using [[Brief_introduction_to_SVN#How_to_use_git2cl|git2cl]]. Developers should take care to make useful commit log messages when committing changes to git. Please read the [[Committing policies]] for details.

=== How to use git2cl ===

Starting with Gramps 3.0.0, we no longer have a <tt>ChangeLog</tt> file.

Instead, the list of changes is generated automatically using the standard <tt>git2cl</tt> script.

Note that <tt>git2cl</tt> is not included in the base installation of Git. With a Debian-based distro such as Ubuntu, you can get <tt>git2cl</tt> as follows:

sudo apt-get install git2cl

There typically are two <tt>ChangeLog</tt> files needed for releases; one in the main directory, and one in the <tt>po</tt> directory. You can generate these files with the following commands:

git log gramps-4.0.1.. --pretty --numstat --summary --no-merges | git2cl > ChangeLog
git log gramps-4.0.1.. --pretty --numstat --summary --no-merges -- po | git2cl > po/ChangeLog

== External links ==

*[http://git-scm.com/ Git]
*[http://git-scm.com/book Git Book]
*[https://help.github.com/articles/generating-ssh-keys/ GitHub SSH Keys]
*[https://help.github.com/articles/what-are-github-s-ssh-key-fingerprints/ GitHub SSH Key Fingerprints]

[[Category:Developers/General|B]]

Gramps 4.1 Wiki Manual - User Directory

2015-05-28T18:01:45Z

Ennoborg: /* MS Windows */ gramps34 folder removed

{{grampsmanualcopyright}}

{{man index|Gramps_4.1_Wiki_Manual_-_Command_Line#Environment_variables|Gramps 4.1 Wiki Manual - About|4.1}}

{{languages|Gramps_4.1_Wiki_Manual_-_User_Directory}}

{{#vardefine:chapter|D}}
{{#vardefine:figure|0}}

This appendix provides the reference to the Gramps user directory available on various operating systems.

{{man note|Note|The location of your Gramps user directory depends on the operating system you are using and how you have set up your computer. In the table below <tt><~username></tt> should be replaced by the name you use to log in to your computer.}}

== POSIX - style systems ==
The default location for an installation of Gramps in a [http://en.wikipedia.org/wiki/Posix POSIX]-style [http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard environment] is:

/home/<~username>/.gramps

This is true for [http://en.wikipedia.org/wiki/Bsd BSD], [http://en.wikipedia.org/wiki/Linux Linux], [http://en.wikipedia.org/wiki/Solaris_(operating_system) Solaris], [http://en.wikipedia.org/wiki/Unix Unix] and [http://en.wikipedia.org/wiki/Mac_OS_X Mac OS-X] when using [[Build_from_source#Mac_OS_X|Mac OS X Build from source]].

=== Mac OS X ===
On Macs, filenames starting with "." do not show up in Finder. To make access to the Gramps user directory easy, open a terminal window with Finder-Applications-Utilities-Terminal and type there
ln -s .gramps gramps_user_directory
which will allow Finder to show the contents. Or simply click on Go -> 'Go to Folder...' in the Finder, and type
~/.gramps
in the Go to Folder dialog box.

The default location for the [[Mac OS X:Application package]] is
/Users/<username>/Library/Application Support/gramps

== MS Windows ==

The default location for an installation on a Windows 7 and higher system is
C:\Users\<~username>\AppData\Roaming\gramps

On Windows XP and earlier, it is
C:\Documents and Settings\<~username>\Application Data\gramps

{{man index|Gramps_4.1_Wiki_Manual_-_Command_Line#Environment_variables|Gramps 4.1 Wiki Manual - About|4.1}}

{{languages|Gramps_4.1_Wiki_Manual_-_User_Directory}}

[[Category:Documentation|U]]

Talk:Download

2015-05-06T14:14:40Z

Ennoborg:

I think that we can better stop distinguishing 32 and 64 bit Windows, since there are no new 64 bit builds. Agreed?
:: No ? They do exist at the moment. What do you mean exactly?
::: Well, a while ago, there was only a 32 bit version, and I thought it might confuse users, and I saw no speed advantage for the 64 bit version, which in fact still starts very slow on my PCs. But as long as Josip likes building both, we can continue.

Talk:Download

2015-05-06T14:14:14Z

Ennoborg:

Download

2015-05-01T12:17:23Z

Ennoborg: 3.4.9 blog link

__NOTOC__
{{languages}}

:{{Man menu|'''Current version: {{version}} Released: 2015/05/01'''}} - ''Different data format to the GRAMPS 3.4 series. Full Python 3 support. Conversion to GTK+ 3. New place hierarchies model.''[https://gramps-project.org/wiki/index.php?title=Gramps_4.1_Wiki_Manual_-_What%27s_new%3F#Place_hierarchies]

:''Legacy version: 3.4.9 Released: 2015/04/30 - This is a maintenance release designed for those of you still running gramps with gtk2. The database is common between version 4.0.x (not version 4.1.x) and 3.4.x branch, most differences are into interface...''[https://gramps-project.org/2015/04/gramps-3-4-9-released/]

== Linux ==

[[Image:Linux_220x261.png|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version ({{version}}) (advanced users only)]]</big>
{{-}}

== MS Windows ==

[[Image:windows_180x160.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO32}}/{{filename_windows_AIO32}}.exe Windows Installer (32-bit) {{version_windows_AIO32}}]
    
[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO64}}/{{filename_windows_AIO64}}.exe Windows Installer (64-bit) {{version_windows_AIO64}}]</big>

After download: double-click to install Gramps.

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

Use the Windows AIO version, please use the download links above. For more information about individual versions, console and debug modes, release notes, etc., look at [[GrampsAIO-4|this page]] (English only).

Alternative independent '''Legacy''' MS Windows version [[#3|[3]]].

== Mac OS X ==

[[Image:macos_200x200.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]]. Read the [[Mac OS X:Application package|before installation]] instructions.

Mac OS X 10.5, 10.6, 10.7, 10.8, and 10.9     <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{Filename_mac_intel}}.dmg Intel {{version_Mac}}]</big>
    
Mac OS X 10.5    <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{filename_mac_ppc}}.dmg Power PC {{version_Mac}}]</big>

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next drag the Gramps application to your application folder and double-click to launch it [[#2|[2]]].

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

{{-}}

== BSD ==

[[File:Bsd daemon.jpg|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux and BSD distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version (advanced users only)]]</big>
{{-}}

== Live CD ==

[[Image:Download_link.png|150px|left|link=http://sourceforge.net/projects/gramps/files/OldFiles/3.2.5/lgenealogy-6.1-desktop-i386.iso]]
'''Linux live CD Demonstration''' includes Gramps {{Version Linux Live CD}} pre-installed to trial, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn..). [[Linux_Genealogy_CD#Obtaining_the_CD|Obtaining the CD]] (727 MB) [[Linux Genealogy CD|Linux Genealogy CD based on Ubuntu 10.10 (Maverick Meerkat)]]. If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install latest [http://www.ubuntulinux.org/ Ubuntu 14.04.1] and Gramps from the CD anytime you like.
{{-}}
[[Image:Download_link.png|150px|left|link=http://cdimage.ubuntu.com/edubuntu/releases/14.04.2/release/]]
'''Edubuntu 14.04.2''' includes Gramps 4.0.3-1 (For information about Edubuntu [http://www.edubuntu.org/news/14.04.2-release visit])
{{-}}

== Linux and BSD distributions ==

Most linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| {{prettytable}}
!Distribution
!GUI Package manager
!Current versions
!Notes
|-
|[[Image:Debianopenlogo-32.png]]''' [[Debian]] '''
|Add/Remove Software
|wheezy (old stable): Gramps 3.4.0 jessie (stable): Gramps 4.1.1 stretch (testing): Gramps 4.1.1 [http://packages.debian.org/sid/gramps sid (unstable)]: Gramps 4.1.2
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[Image:Ubuntu_32x32.png]]''' Ubuntu '''
| Software Centre
|Precise (12.04 LTS): Gramps 3.3.1 Trusty (14.04 LTS): Gramps: 4.0.3 Utopic (14.10): Gramps: 4.0.4 Vivid (Development): Gramps: 4.1.1
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]
|-
|'''Linux Mint'''
|Software Manager
|Isadora (Gramps 3.2.0-1) Lisa (Gramps 3.3.1-1) Olivia (Gramps 3.4.0-1) Qiana (Gramps 4.0.3+dfsg-2)
|[http://community.linuxmint.com/software/view/gramps available versions]
|-
|[[Image:Fedora_32x32.png]]''' Fedora '''
|Add/Remove Software (Gnome) or Software Management (KDE)
|Rawhide (Gramps 4.1.2) Fedora 21 (Gramps 4.1.1) Fedora 20 (Gramps 4.0.3) Fedora 19 (Gramps 3.4.8) Fedora EPEL 6 (Gramps 3.4.8)
|[https://apps.fedoraproject.org/packages/gramps available versions]
|-
|[[Image:Redhat_32x32.png]]''' Redhat '''
|Package Management Tool([https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/ch-graphical-rpm.html pirut])
|
|
|-
|[[Image:Mandriva_32x32.png]]''' Mandriva '''
|Software Management in the 
Mandriva Linux Control Center
|Mandriva 2010.1: Gramps 3.3.1 Mandriva 2011: Gramps 3.2.6
|See also [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Advanced_use:_Backports_and_candidate_updates backports] and contrib repository
|-
|''' Mageia '''
|
|
|
|-
|''' openSUSE '''
|[https://en.opensuse.org/YaST_Software_Management YaST]
|openSUSE 13.2: Gramps 4.0.4
|[http://software.opensuse.org/package/gramps available versions]
|-
|'''Slackware'''
|
|Slackware 14.1: Gramps 4.0.3
|[http://pkgs.org/search/?keyword=gramps available versions]
|-
|'''NetBSD'''
|
|NetBSD: Gramps 3.4.4
|[http://pkgsrc.se/databases/gramps3 available versions]
|-
|'''FreeBSD'''
|
|FreeBSD: Gramps 3.4.8
|[http://portsmon.freebsd.org/portoverview.py?category=science&portname=gramps available versions]
|-
|'''PC-BSD'''
|
|PC-BSD: Gramps 3.4.8
|
|}

{{-}}

== Linux: Install latest version ==

If your distribution doesn't ship with Gramps or you wish to install a different version than it ships with, you could try to install the latest version of Gramps manually. Instructions are given below for a number of distributions.

{{man warn|1=Warning|2=This should only be attempted by experienced users, and after you have backed up your Family Tree.

The version of Gramps that has been included in your distribution will have been tested to work with the components in that distribution. If you try to install a different version of Gramps there is a possibility that the components needed for the new version of Gramps are not available for your distribution, or they are available, but don't work properly. You might not discover that there is a problem till you have already done some work with the new version of Gramps.

If you already have Gramps installed, and you are only making a 'point' upgrade (i.e. from Gramps x.y.z to x.y.z+1, e.g. from 3.4.3 to 3.4.4), then it is likely but not certain that Gramps will continue to work. However, if the change is much greater, especially if it is a major version change (e.g. from 2.y.z to 3.y.z), then the danger that it does not work properly is much greater.}}

[[Image:Debianopenlogo-32.png]]'''[[Debian]]''' and [[Image:Ubuntu_32x32.png]]''' Ubuntu ''' [http://sourceforge.net/projects/gramps/files/Stable/{{version}} Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved (change the filename to match the one you downloaded).

sudo dpkg -i python-gramps_{{version}}-1_all.deb
or
sudo dpkg -i python3-gramps_{{version}}-1_all.deb

For other distributions, [[Image:Download_link.png|150px|link=http://sourceforge.net/projects/gramps/files/Stable/{{version}}/gramps-{{version}}.tar.gz]] the source and follow the instructions for [[Linux:Build from source]]

== Notes ==

[1]
Backup to Gramps XML. You will find backup in the Family Tree menu of recent Gramps versions, otherwise use export in the same menu but '''uncheck privacy options''' in the Exporter Assistant in order to export all data

[2]
Alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.

[3]
An alternative independent '''Legacy''' version is [http://sourceforge.net/projects/portableapps/files/Gramps%20Portable/ GrampsPortable_{{version_windows_portable}}.paf.exe] (20.3 MB)
[http://portableapps.com/apps/education/gramps_portable Portable Gramps from PortableApps.com] includes all dependencies required for Windows. ''Note:You can install it on C: then to run Gramps type C:\PortableApps\GrampsPortable\GrampsPortable.exe (Or the path you installed it to) or make a shortcut to that file on your desktop or start-menu.'' By Bart.S - '''[http://portableapps.com/blog/84601 Please report issues to the author.]''' (2012-09-07)

[[Category:Documentation]]

OCR

2015-03-29T16:39:15Z

Ennoborg: /* Using OCR with Gramps */ clara OCR site not available

{{languages|OCR}}

While researching your family tree, you will use books or administrative documents. You may avoid long and annoying work or transcribing texts into Gramps by using optical character recognition ([http://en.wikipedia.org/wiki/Optical_character_recognition OCR]).

Here we show you how to work on your picture or scan of a document to change it into typed text.

==How does this work?==

* You picture needs to have a strong contrast (black text, white background), and a good resolution.
* The OCR program scans the picture and uses glyph libraries to detect the characters. Those that are recognised are transformed into the corresponding character.
* Dictionaries will be used to minimize errors. These compare the resulting words with existing words to determine the outcome and guess the words that were not fully recognized.
* Some programs recognize bold, italic or custom fonts size.

==Using OCR with Gramps==

There is not a lot of OCR open sources programs, and those that exist mostly use the same backend. For ''Intelligent Word Recognition (IWR)'' or ''[http://en.wikipedia.org/wiki/Intelligent_Character_Recognition Intelligent Character Recognition (ICR)]'', used for written certificates, they are even rarer.

You can use some of the programs alongside Gramps. For the backend tools, only command line tools are available (use ''-h'' for the options), but fortunately some GUI's have been made too:

* [http://conjecture.sourceforge.net/ Conjecture] is an OCR third party tool who incorporate both open sources programs code bases.

* The [http://gamera.informatik.hsnr.de/ Gamera Project] is a framework for the creation of custom OCR applications. It supports the training of custom character shapes.

* [http://jocr.sourceforge.net/ GOCR/JOCR] is used by [http://www.xsane.org/ xsane] and [http://kooka.kde.org/ kooka]. It can generate custom database characters from a picture with the command:
mkdir ./db
gocr -p ./db/ -m 130 -m 256 certificate.pnm
:This will ask you of each new letter it recognizes what the value is (a,b,...), and will generate a new index (db.list) + portable-bitmap (pbm) for your letters. Each key entry on db.list is one of the .pbm files and is connected to your custom value (a, b, c ...)
:This is however not very successfull on written text.
* With [http://www.gnu.org/software/ocrad/ocrad.html Ocrad], you need to use pgm file format.
* People using KDE will probably know [http://kooka.kde.org/ Kooka] the standard KDE scanning tool with builtin OCR (using [http://jocr.sourceforge.net/ GOCR], [http://www.gnu.org/software/ocrad/ocrad.html Ocrad], which are OSS, or the commercial KADMOS).

* [http://live.gnome.org/OCRFeeder OCRFeeder] is a document layout analysis and optical character recognition system.

* The [http://code.google.com/p/ocropus/ OCRopus] engine is based on two research projects: a high-performance handwriting recognizer developed in the mid-90's and deployed by the US Census bureau, and novel high-performance layout analysis methods. See, also [http://docs.google.com/Doc?id=dfxcv4vc_67g844kf hOCR format] and [http://code.google.com/p/hocr-tools/ hOCR tools].

* [http://code.google.com/p/tesseract-ocr/ Tesseract] may be a good solution. Version 2.00 and later support English, French, Italian, German, Spanish, Dutch.

==Example and related information==
I think the easiest would be to use kooka or xsane, scan an image and do OCR or importing an existing image into kooka and do OCR.

*There is a [http://en.wikipedia.org/wiki/CuneiForm_(software) CuneiForm] for ocr image to text.

*A [http://www.wired.com/gadgets/miscellaneous/news/2007/06/iliad_scan robot scans Ancient Manuscript in 3-D]. Also, This summer a group of graduate and undergraduate students of Greek will gather at the [http://chs.harvard.edu/ Center for Hellenic Studies] in Washington, D.C., to produce XML transcriptions of the text. Eventually, their work will be posted online for anyone to search under [http://creativecommons.org/about/licenses/ Creative Commons] licence.

*[http://www.geocities.jp/takascience/lego/fabs_en.html How to make a full Auto Book Scanner] with LEGO ...

*[http://spectrum.ieee.org/automaton/robotics/robotics-software/book-flipping-scanning Superfast scanner lets you digitize a book by rapidly flipping pages]

*[http://bookliberator.com bookliberator] is a set of free software and hardware to digitize books: it lets you photograph all the pages in a book without harming the book. The resulting images can be processed with free, open source software to make user-friendly files in a variety of formats.

*[http://sites.google.com/site/decapodproject/ decapodproject] is a project focused on building a low-cost digitization solution that will allow for rare materials, materials held in collections without large budgets, and other scholarly content to be digitized into a high-quality PDF format. This project will work to incorporate the hardware and software necessary to accomplish this goal.

*[http://www.diybookscanner.org/ Do It Yourself Book Scanner] and how to make a book scanner out of stuff we can find in dumpsters, or buy cheaply, including off-the-shelf, cheap digital camers. Se also the related [http://code.google.com/p/diy-ebook-creator/ ebook project].

*[http://www.bookscanner.fr/ Build your own Book scanner (in french)].

[[Category:Sources]]
[[Category:Genealogy]]

Addon:Graph View

2015-03-27T14:42:04Z

Ennoborg: /* Prerequisites */ binary download links for LMDE

{{Third-party plugin}}

[[File:Graph-View-plugin-addon-example-41.png|500px|thumb|right|Graph View - plugin addon - In action]]

== What is Graph View ==

'''Graph View''' is a view plugin that presents a navigable descendant tree using the current active person as a starting point. Clicking another person in the family tree will make that person the active person and will redraw the family tree based on them.

== Features ==

* Interactive.
* The active person is highlighted.
* Clicking a person will redraw the family tree based on that person.
* Clicking the active person will show the parent family of the active person, thereby allowing previous generations to be shown.
* The view can be panned by using mouse click and drag. Select the background of the tree and drag the mouse to pan the view.
* The view can be zoomed using the slider.
* A right mouse click on a person or family node shows the person or family editor as appropriate.
* Right click a family to add or delete a spouse or child.
* The view redraws in response to changes made to a person or family.

== Configure Options ==
You can change the following:

*Layout
** Show images : checkbox selected by default
** Highlight the home person : checkbox selected by default
** Show full dates
** Show places

*Colors
** Home person color: '''#bbe68a'''(default)

== Prerequisites ==
Before '''Graph View''' can be used you will need the following installed:
* Graphviz. If you can run the Gramps Graph reports then you already have this installed.
* [http://live.gnome.org/PyGoocanvas PyGoocanvas] (Gramps3) or [https://wiki.gnome.org/Projects/GObjectIntrospection Goocanvas2 or gir1.2-goocanvas] (Gramps4)
* [http://live.gnome.org/GooCanvas Goocanvas]

All of these should be available in common Linux distributions.

For example, Debian packages Goocanvas/PyGoocanvas as libgoocanvas3 and python-pygoocanvas.

=== Note ===

These packages are not available for Linux Mint Debian Edition (LMDE). You can download these as .deb files from [https://launchpad.net/ubuntu/+source/goocanvas-2.0/2.0.2-0ubuntu2 launchpad] and install them in the usual manner. You need the Binary packages shown at the bottom of that pages, except for the development libraries.

Please make sure to download these for the proper architecture, like amd64 for 64-bit PCs (Intel included).

[[Category:Plugins]]
[[Category:Developers/General]]
[[Category:Views]]

Download

2015-03-22T20:03:26Z

Ennoborg: /* MS Windows */ language

__NOTOC__
{{languages}}
== Linux ==

[[Image:Linux_220x261.png|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version ({{version}}) (advanced users only)]]</big>
{{-}}

== MS Windows ==

[[Image:windows_180x160.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO32}}/{{filename_windows_AIO32}}.exe Windows Installer (32-bit) {{version_windows_AIO32}}]
    
[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO64}}/{{filename_windows_AIO64}}.exe Windows Installer (64-bit) {{version_windows_AIO64}}]</big>

After download: double-click to install Gramps.

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

Alternative independent MS Windows version [[#3|[3]]].

If you feel comfortable with the Windows AIO version, please use the download links above. For more information about individual versions, console and debug modes, release notes, etc., look at [[GrampsAIO-4|this page]] (English only).

== Mac OS X ==

[[Image:macos_200x200.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]]. Read the [[Mac OS X:Application package|before installation]] instructions.

Mac OS X 10.5, 10.6, 10.7, 10.8, and 10.9     <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{Filename_mac_intel}}.dmg Intel {{version_Mac}}]</big>
    
Mac OS X 10.5    <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{filename_mac_ppc}}.dmg Power PC {{version_Mac}}]</big>

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next drag the Gramps application to your application folder and double-click to launch it [[#2|[2]]].

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

{{-}}

== BSD ==

[[File:Bsd daemon.jpg|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux and BSD distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version (advanced users only)]]</big>
{{-}}

== Live CD ==

[[Image:Download_link.png|150px|left|link=http://sourceforge.net/projects/gramps/files/OldFiles/3.2.5/lgenealogy-6.1-desktop-i386.iso]]
'''Linux live CD Demonstration''' includes Gramps {{Version Linux Live CD}} pre-installed to trial, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn..). [[Linux_Genealogy_CD#Obtaining_the_CD|Obtaining the CD]] (727 MB) [[Linux Genealogy CD|Linux Genealogy CD based on Ubuntu 10.10 (Maverick Meerkat)]]. If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install latest [http://www.ubuntulinux.org/ Ubuntu 14.04.1] and Gramps from the CD anytime you like.
{{-}}
[[Image:Download_link.png|150px|left|link=http://cdimage.ubuntu.com/edubuntu/releases/14.04.1/release/]]
'''Edubuntu 14.04.1''' includes Gramps 4.0.3-1 (For information about Edubuntu [http://www.edubuntu.org/news/14.04.1-release visit])
{{-}}

== Linux and BSD distributions ==

Most linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| {{prettytable}}
!Distribution
!GUI Package manager
!Current versions
!Notes
|-
|[[Image:Debianopenlogo-32.png]]''' [[Debian]] '''
|Add/Remove Software
|squeeze (old stable): Gramps 3.2.3 wheezy (stable): Gramps 3.4.0 jessie (testing): Gramps 4.1.1 [http://packages.debian.org/sid/gramps sid (unstable)]: Gramps 4.1.1
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[Image:Ubuntu_32x32.png]]''' Ubuntu '''
| Software Centre
|Precise (12.04 LTS): Gramps 3.3.1 Trusty (14.04 LTS): Gramps: 4.0.3 Utopic (14.10): Gramps: 4.0.4 Vivid (Development): Gramps: 4.1.1
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]
|-
|'''Linux Mint'''
|Software Manager
|Isadora (Gramps 3.2.0-1) Lisa (Gramps 3.3.1-1) Olivia (Gramps 3.4.0-1) Qiana (Gramps 4.0.3+dfsg-2)
|[http://community.linuxmint.com/software/view/gramps available versions]
|-
|[[Image:Fedora_32x32.png]]''' Fedora '''
|Add/Remove Software (Gnome) or Software Management (KDE)
|Rawhide (Gramps 4.1.1) Fedora 21 (Gramps 4.1.1) Fedora 20 (Gramps 4.0.3) Fedora 19 (Gramps 3.4.8) Fedora EPEL 6 (Gramps 3.4.8)
|[https://apps.fedoraproject.org/packages/gramps available versions]
|-
|[[Image:Redhat_32x32.png]]''' Redhat '''
|Package Management Tool([https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/ch-graphical-rpm.html pirut])
|
|
|-
|[[Image:Mandriva_32x32.png]]''' Mandriva '''
|Software Management in the 
Mandriva Linux Control Center
|Mandriva 2010.1: Gramps 3.3.1 Mandriva 2011: Gramps 3.2.6
|See also [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Advanced_use:_Backports_and_candidate_updates backports] and contrib repository
|-
|''' Mageia '''
|
|
|
|-
|''' openSUSE '''
|[https://en.opensuse.org/YaST_Software_Management YaST]
|openSUSE 13.2: Gramps 4.0.4
|[http://software.opensuse.org/package/gramps available versions]
|-
|'''Slackware'''
|
|Slackware 14.1: Gramps 4.0.3
|[http://pkgs.org/search/?keyword=gramps available versions]
|-
|'''NetBSD'''
|
|NetBSD: Gramps 3.4.4
|[http://pkgsrc.se/databases/gramps3 available versions]
|-
|'''FreeBSD'''
|
|FreeBSD: Gramps 3.4.8
|[http://portsmon.freebsd.org/portoverview.py?category=science&portname=gramps available versions]
|-
|'''PC-BSD'''
|
|PC-BSD: Gramps 3.4.8
|
|}

{{-}}

== Linux: Install latest version ==

If your distribution doesn't ship with Gramps or you wish to install a different version than it ships with, you could try to install the latest version of Gramps manually. Instructions are given below for a number of distributions.

{{man warn|1=Warning|2=This should only be attempted by experienced users, and after you have backed up your Family Tree.

The version of Gramps that has been included in your distribution will have been tested to work with the components in that distribution. If you try to install a different version of Gramps there is a possibility that the components needed for the new version of Gramps are not available for your distribution, or they are available, but don't work properly. You might not discover that there is a problem till you have already done some work with the new version of Gramps.

If you already have Gramps installed, and you are only making a 'point' upgrade (i.e. from Gramps x.y.z to x.y.z+1, e.g. from 3.4.3 to 3.4.4), then it is likely but not certain that Gramps will continue to work. However, if the change is much greater, especially if it is a major version change (e.g. from 2.y.z to 3.y.z), then the danger that it does not work properly is much greater.}}

[[Image:Debianopenlogo-32.png]]'''[[Debian]]''' and [[Image:Ubuntu_32x32.png]]''' Ubuntu ''' [http://sourceforge.net/projects/gramps/files/Stable/{{version}} Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved (change the filename to match the one you downloaded).

sudo dpkg -i gramps_{{version}}-1_all.deb

For other distributions, [[Image:Download_link.png|150px|link=http://sourceforge.net/projects/gramps/files/Stable/{{version}}/gramps-{{version}}.tar.gz]] the source and follow the instructions for [[Linux:Build from source]]

== Notes ==

[1]
Backup to Gramps XML. You will find backup in the Family Tree menu of recent Gramps versions, otherwise use export in the same menu but '''uncheck privacy options''' in the Exporter Assistant in order to export all data

[2]
Alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.

[3]
An alternative independent version is [http://sourceforge.net/projects/portableapps/files/Gramps%20Portable/ GrampsPortable_{{version_windows_portable}}.paf.exe] (20.3 MB)
[http://portableapps.com/apps/education/gramps_portable Portable Gramps from PortableApps.com] includes all dependencies required for Windows. ''Note:You can install it on C: then to run Gramps type C:\PortableApps\GrampsPortable\GrampsPortable.exe (Or the path you installed it to) or make a shortcut to that file on your desktop or start-menu.'' By Bart.S - '''[http://portableapps.com/blog/84601 Please report issues to the author.]''' (2012-09-07)

[[Category:Documentation]]

Download

2015-03-22T20:02:07Z

Ennoborg: /* MS Windows */ AIO-4 link

__NOTOC__
{{languages}}
== Linux ==

[[Image:Linux_220x261.png|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version ({{version}}) (advanced users only)]]</big>
{{-}}

== MS Windows ==

[[Image:windows_180x160.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO32}}/{{filename_windows_AIO32}}.exe Windows Installer (32-bit) {{version_windows_AIO32}}]
    
[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO64}}/{{filename_windows_AIO64}}.exe Windows Installer (64-bit) {{version_windows_AIO64}}]</big>

After download: double-click to install Gramps.

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

Alternative independent MS Windows version [[#3|[3]]].

If you feel comfortable with the Windows AIO version of Gramps, please use the download links above. For more information about individual versions, and release notes, visit [[GrampsAIO-4|this]] (English only).

== Mac OS X ==

[[Image:macos_200x200.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]]. Read the [[Mac OS X:Application package|before installation]] instructions.

Mac OS X 10.5, 10.6, 10.7, 10.8, and 10.9     <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{Filename_mac_intel}}.dmg Intel {{version_Mac}}]</big>
    
Mac OS X 10.5    <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{filename_mac_ppc}}.dmg Power PC {{version_Mac}}]</big>

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next drag the Gramps application to your application folder and double-click to launch it [[#2|[2]]].

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

{{-}}

== BSD ==

[[File:Bsd daemon.jpg|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux and BSD distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version (advanced users only)]]</big>
{{-}}

== Live CD ==

[[Image:Download_link.png|150px|left|link=http://sourceforge.net/projects/gramps/files/OldFiles/3.2.5/lgenealogy-6.1-desktop-i386.iso]]
'''Linux live CD Demonstration''' includes Gramps {{Version Linux Live CD}} pre-installed to trial, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn..). [[Linux_Genealogy_CD#Obtaining_the_CD|Obtaining the CD]] (727 MB) [[Linux Genealogy CD|Linux Genealogy CD based on Ubuntu 10.10 (Maverick Meerkat)]]. If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install latest [http://www.ubuntulinux.org/ Ubuntu 14.04.1] and Gramps from the CD anytime you like.
{{-}}
[[Image:Download_link.png|150px|left|link=http://cdimage.ubuntu.com/edubuntu/releases/14.04.1/release/]]
'''Edubuntu 14.04.1''' includes Gramps 4.0.3-1 (For information about Edubuntu [http://www.edubuntu.org/news/14.04.1-release visit])
{{-}}

== Linux and BSD distributions ==

Most linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| {{prettytable}}
!Distribution
!GUI Package manager
!Current versions
!Notes
|-
|[[Image:Debianopenlogo-32.png]]''' [[Debian]] '''
|Add/Remove Software
|squeeze (old stable): Gramps 3.2.3 wheezy (stable): Gramps 3.4.0 jessie (testing): Gramps 4.1.1 [http://packages.debian.org/sid/gramps sid (unstable)]: Gramps 4.1.1
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[Image:Ubuntu_32x32.png]]''' Ubuntu '''
| Software Centre
|Precise (12.04 LTS): Gramps 3.3.1 Trusty (14.04 LTS): Gramps: 4.0.3 Utopic (14.10): Gramps: 4.0.4 Vivid (Development): Gramps: 4.1.1
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]
|-
|'''Linux Mint'''
|Software Manager
|Isadora (Gramps 3.2.0-1) Lisa (Gramps 3.3.1-1) Olivia (Gramps 3.4.0-1) Qiana (Gramps 4.0.3+dfsg-2)
|[http://community.linuxmint.com/software/view/gramps available versions]
|-
|[[Image:Fedora_32x32.png]]''' Fedora '''
|Add/Remove Software (Gnome) or Software Management (KDE)
|Rawhide (Gramps 4.1.1) Fedora 21 (Gramps 4.1.1) Fedora 20 (Gramps 4.0.3) Fedora 19 (Gramps 3.4.8) Fedora EPEL 6 (Gramps 3.4.8)
|[https://apps.fedoraproject.org/packages/gramps available versions]
|-
|[[Image:Redhat_32x32.png]]''' Redhat '''
|Package Management Tool([https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/ch-graphical-rpm.html pirut])
|
|
|-
|[[Image:Mandriva_32x32.png]]''' Mandriva '''
|Software Management in the 
Mandriva Linux Control Center
|Mandriva 2010.1: Gramps 3.3.1 Mandriva 2011: Gramps 3.2.6
|See also [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Advanced_use:_Backports_and_candidate_updates backports] and contrib repository
|-
|''' Mageia '''
|
|
|
|-
|''' openSUSE '''
|[https://en.opensuse.org/YaST_Software_Management YaST]
|openSUSE 13.2: Gramps 4.0.4
|[http://software.opensuse.org/package/gramps available versions]
|-
|'''Slackware'''
|
|Slackware 14.1: Gramps 4.0.3
|[http://pkgs.org/search/?keyword=gramps available versions]
|-
|'''NetBSD'''
|
|NetBSD: Gramps 3.4.4
|[http://pkgsrc.se/databases/gramps3 available versions]
|-
|'''FreeBSD'''
|
|FreeBSD: Gramps 3.4.8
|[http://portsmon.freebsd.org/portoverview.py?category=science&portname=gramps available versions]
|-
|'''PC-BSD'''
|
|PC-BSD: Gramps 3.4.8
|
|}

{{-}}

== Linux: Install latest version ==

If your distribution doesn't ship with Gramps or you wish to install a different version than it ships with, you could try to install the latest version of Gramps manually. Instructions are given below for a number of distributions.

{{man warn|1=Warning|2=This should only be attempted by experienced users, and after you have backed up your Family Tree.

The version of Gramps that has been included in your distribution will have been tested to work with the components in that distribution. If you try to install a different version of Gramps there is a possibility that the components needed for the new version of Gramps are not available for your distribution, or they are available, but don't work properly. You might not discover that there is a problem till you have already done some work with the new version of Gramps.

If you already have Gramps installed, and you are only making a 'point' upgrade (i.e. from Gramps x.y.z to x.y.z+1, e.g. from 3.4.3 to 3.4.4), then it is likely but not certain that Gramps will continue to work. However, if the change is much greater, especially if it is a major version change (e.g. from 2.y.z to 3.y.z), then the danger that it does not work properly is much greater.}}

[[Image:Debianopenlogo-32.png]]'''[[Debian]]''' and [[Image:Ubuntu_32x32.png]]''' Ubuntu ''' [http://sourceforge.net/projects/gramps/files/Stable/{{version}} Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved (change the filename to match the one you downloaded).

sudo dpkg -i gramps_{{version}}-1_all.deb

For other distributions, [[Image:Download_link.png|150px|link=http://sourceforge.net/projects/gramps/files/Stable/{{version}}/gramps-{{version}}.tar.gz]] the source and follow the instructions for [[Linux:Build from source]]

== Notes ==

[1]
Backup to Gramps XML. You will find backup in the Family Tree menu of recent Gramps versions, otherwise use export in the same menu but '''uncheck privacy options''' in the Exporter Assistant in order to export all data

[2]
Alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.

[3]
An alternative independent version is [http://sourceforge.net/projects/portableapps/files/Gramps%20Portable/ GrampsPortable_{{version_windows_portable}}.paf.exe] (20.3 MB)
[http://portableapps.com/apps/education/gramps_portable Portable Gramps from PortableApps.com] includes all dependencies required for Windows. ''Note:You can install it on C: then to run Gramps type C:\PortableApps\GrampsPortable\GrampsPortable.exe (Or the path you installed it to) or make a shortcut to that file on your desktop or start-menu.'' By Bart.S - '''[http://portableapps.com/blog/84601 Please report issues to the author.]''' (2012-09-07)

[[Category:Documentation]]

Talk:Download

2015-03-22T18:47:50Z

Ennoborg: get rid of 64-bit windows downloads

I think that we can better stop distinguishing 32 and 64 bit Windows, since there are no new 64 bit builds. Agreed?

Download

2015-03-22T18:46:07Z

Ennoborg: /* MS Windows */ old link removed

__NOTOC__
{{languages}}
== Linux ==

[[Image:Linux_220x261.png|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version ({{version}}) (advanced users only)]]</big>
{{-}}

== MS Windows ==

[[Image:windows_180x160.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO32}}/{{filename_windows_AIO32}}.exe Windows Installer (32-bit) {{version_windows_AIO32}}]
    
[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO64}}/{{filename_windows_AIO64}}.exe Windows Installer (64-bit) {{version_windows_AIO64}}]</big>

After download: double-click to install Gramps.

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

Alternative independent MS Windows version [[#3|[3]]].

== Mac OS X ==

[[Image:macos_200x200.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]]. Read the [[Mac OS X:Application package|before installation]] instructions.

Mac OS X 10.5, 10.6, 10.7, 10.8, and 10.9     <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{Filename_mac_intel}}.dmg Intel {{version_Mac}}]</big>
    
Mac OS X 10.5    <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{filename_mac_ppc}}.dmg Power PC {{version_Mac}}]</big>

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next drag the Gramps application to your application folder and double-click to launch it [[#2|[2]]].

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

{{-}}

== BSD ==

[[File:Bsd daemon.jpg|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux and BSD distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version (advanced users only)]]</big>
{{-}}

== Live CD ==

[[Image:Download_link.png|150px|left|link=http://sourceforge.net/projects/gramps/files/OldFiles/3.2.5/lgenealogy-6.1-desktop-i386.iso]]
'''Linux live CD Demonstration''' includes Gramps {{Version Linux Live CD}} pre-installed to trial, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn..). [[Linux_Genealogy_CD#Obtaining_the_CD|Obtaining the CD]] (727 MB) [[Linux Genealogy CD|Linux Genealogy CD based on Ubuntu 10.10 (Maverick Meerkat)]]. If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install latest [http://www.ubuntulinux.org/ Ubuntu 14.04.1] and Gramps from the CD anytime you like.
{{-}}
[[Image:Download_link.png|150px|left|link=http://cdimage.ubuntu.com/edubuntu/releases/14.04.1/release/]]
'''Edubuntu 14.04.1''' includes Gramps 4.0.3-1 (For information about Edubuntu [http://www.edubuntu.org/news/14.04.1-release visit])
{{-}}

== Linux and BSD distributions ==

Most linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| {{prettytable}}
!Distribution
!GUI Package manager
!Current versions
!Notes
|-
|[[Image:Debianopenlogo-32.png]]''' [[Debian]] '''
|Add/Remove Software
|squeeze (old stable): Gramps 3.2.3 wheezy (stable): Gramps 3.4.0 jessie (testing): Gramps 4.1.1 [http://packages.debian.org/sid/gramps sid (unstable)]: Gramps 4.1.1
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[Image:Ubuntu_32x32.png]]''' Ubuntu '''
| Software Centre
|Precise (12.04 LTS): Gramps 3.3.1 Trusty (14.04 LTS): Gramps: 4.0.3 Utopic (14.10): Gramps: 4.0.4 Vivid (Development): Gramps: 4.1.1
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]
|-
|'''Linux Mint'''
|Software Manager
|Isadora (Gramps 3.2.0-1) Lisa (Gramps 3.3.1-1) Olivia (Gramps 3.4.0-1) Qiana (Gramps 4.0.3+dfsg-2)
|[http://community.linuxmint.com/software/view/gramps available versions]
|-
|[[Image:Fedora_32x32.png]]''' Fedora '''
|Add/Remove Software (Gnome) or Software Management (KDE)
|Rawhide (Gramps 4.1.1) Fedora 21 (Gramps 4.1.1) Fedora 20 (Gramps 4.0.3) Fedora 19 (Gramps 3.4.8) Fedora EPEL 6 (Gramps 3.4.8)
|[https://apps.fedoraproject.org/packages/gramps available versions]
|-
|[[Image:Redhat_32x32.png]]''' Redhat '''
|Package Management Tool([https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/ch-graphical-rpm.html pirut])
|
|
|-
|[[Image:Mandriva_32x32.png]]''' Mandriva '''
|Software Management in the 
Mandriva Linux Control Center
|Mandriva 2010.1: Gramps 3.3.1 Mandriva 2011: Gramps 3.2.6
|See also [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Advanced_use:_Backports_and_candidate_updates backports] and contrib repository
|-
|''' Mageia '''
|
|
|
|-
|''' openSUSE '''
|[https://en.opensuse.org/YaST_Software_Management YaST]
|openSUSE 13.2: Gramps 4.0.4
|[http://software.opensuse.org/package/gramps available versions]
|-
|'''Slackware'''
|
|Slackware 14.1: Gramps 4.0.3
|[http://pkgs.org/search/?keyword=gramps available versions]
|-
|'''NetBSD'''
|
|NetBSD: Gramps 3.4.4
|[http://pkgsrc.se/databases/gramps3 available versions]
|-
|'''FreeBSD'''
|
|FreeBSD: Gramps 3.4.8
|[http://portsmon.freebsd.org/portoverview.py?category=science&portname=gramps available versions]
|-
|'''PC-BSD'''
|
|PC-BSD: Gramps 3.4.8
|
|}

{{-}}

== Linux: Install latest version ==

If your distribution doesn't ship with Gramps or you wish to install a different version than it ships with, you could try to install the latest version of Gramps manually. Instructions are given below for a number of distributions.

{{man warn|1=Warning|2=This should only be attempted by experienced users, and after you have backed up your Family Tree.

The version of Gramps that has been included in your distribution will have been tested to work with the components in that distribution. If you try to install a different version of Gramps there is a possibility that the components needed for the new version of Gramps are not available for your distribution, or they are available, but don't work properly. You might not discover that there is a problem till you have already done some work with the new version of Gramps.

If you already have Gramps installed, and you are only making a 'point' upgrade (i.e. from Gramps x.y.z to x.y.z+1, e.g. from 3.4.3 to 3.4.4), then it is likely but not certain that Gramps will continue to work. However, if the change is much greater, especially if it is a major version change (e.g. from 2.y.z to 3.y.z), then the danger that it does not work properly is much greater.}}

[[Image:Debianopenlogo-32.png]]'''[[Debian]]''' and [[Image:Ubuntu_32x32.png]]''' Ubuntu ''' [http://sourceforge.net/projects/gramps/files/Stable/{{version}} Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved (change the filename to match the one you downloaded).

sudo dpkg -i gramps_{{version}}-1_all.deb

For other distributions, [[Image:Download_link.png|150px|link=http://sourceforge.net/projects/gramps/files/Stable/{{version}}/gramps-{{version}}.tar.gz]] the source and follow the instructions for [[Linux:Build from source]]

== Notes ==

[1]
Backup to Gramps XML. You will find backup in the Family Tree menu of recent Gramps versions, otherwise use export in the same menu but '''uncheck privacy options''' in the Exporter Assistant in order to export all data

[2]
Alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.

[3]
An alternative independent version is [http://sourceforge.net/projects/portableapps/files/Gramps%20Portable/ GrampsPortable_{{version_windows_portable}}.paf.exe] (20.3 MB)
[http://portableapps.com/apps/education/gramps_portable Portable Gramps from PortableApps.com] includes all dependencies required for Windows. ''Note:You can install it on C: then to run Gramps type C:\PortableApps\GrampsPortable\GrampsPortable.exe (Or the path you installed it to) or make a shortcut to that file on your desktop or start-menu.'' By Bart.S - '''[http://portableapps.com/blog/84601 Please report issues to the author.]''' (2012-09-07)

[[Category:Documentation]]

Nl:Gramps 3.4 Wiki Handleiding - Invoeren en aanpassen gegevens: details - deel 3

2015-03-17T21:26:58Z

Ennoborg: taaldingetje

{{grampsmanualcopyright/nl}}

{{man index/nl|Gramps 3.4 Wiki Manual - Entering and Editing Data:_Detailed_-_part_2/nl|Gramps_3.4_Wiki_Manual_-_Navigation/nl|3.4}}

{{languages|Gramps_3.4_Wiki_Manual_-_Entering_and_Editing_Data:_Detailed_-_part_3}}

Het vorige deel gaf een gedetailleerd overzicht hoe u de hoofdobjecten die u in Gramps ziet, invoerde en kon bewerken. Dit deel gaat verder met objecten die u zeker bij het gebruik van bronnen, personen, enz. tegenkomt.

== Naam bewerken==

[[Image:Name-Editor-33-nl.png|thumb|250px|right|Fig. 1. Namen aanpassen]]

Namen worden aangepast via de verbeterde {{man label|naameditor}} dialoog:

In het bovenste venstergedeelte kan een naamtype worden ingevuld. Dit is een identificatie van het naamtype. Dit kan bijvoorbeeld geboortenaam of getrouwde naam zijn. De types kunnen gekozen worden uit een uitvalslijst. Vervolgens komen de naamelementen van de persoonlijke naam aan bod. Het zijn die elementen die gewoonlijk samen onder de voornaam worden gegroepeerd. Vervolgens na de voornaamsectie, komt de familienaamsectie. Onderaan zijn er elementen die toelaten de naamelementen zelf aan te passen, datums opgeven voor namen, bronnen van de namen en opmerkingen over de namen.

{{man tip|Tip|De hoofdingen van de tabs geven weer of er verdere informatie beschikbaar is: indien een tab informatie bevat, wordt de hoofding '''vet''' weergegeven; omgekeerd als de hoofding in een normaal lettertype (niet vet) wordt weergegeven, is geen verdere informatie beschikbaar.}}

{{-}}

===Type===

De uitvalslijst laat u toe om een naamtype te kiezen.

=== Voornamensectie ===

De voornamensectie bevat alle mogelijke delen van de voornaam die u in Gramps kunt opslaan.

*{{man label|Voornaam:}}, alle voornamen van de persoon worden hier ingevuld.
*{{man label|Roep:}}, De normale wettelijke naam van de persoon wordt hier ingevuld. Bijvoorbeeld iemand die Jan Robert Janssens noemt en die normaal de naam Robert gebruikt, moet hier dus ''Robert'' invullen. Gebruikt deze persoon normaal ''Rob'' als zijn naam, dan wordt ''Rob'' onder de bijnaam ingevuld omdat dit niet de wettelijke voornaam is (zie onderstaande). In Duitsland en sommige andere plaatsen is het gebruikelijk om de roepnaam te onderlijnen om zo een verschil te maken met de andere delen van de voornaam. Zie ook [http://www.gramps-project.org/wiki/index.php?title=CallName hier]).
*{{man label|Titel:}}, de persoonlijke titel zoals Dokter (of Dr. of Eerw.) of andere titels kunnen hier opgegeven worden.
*{{man label|Suffix:}}, een optioneel naamachtervoegsel zoals Junior (Jr.) of III kunnen hier ingevuld worden.
*{{man label|Bij:}}, de persoonlijke bijnaam wordt hier ingevuld. Bijnamen zijn ook die namen die een afkorting bevatten van een deel van de wettelijk voornamen zoals Greg voor Gregory (zie Roepnaam hier boven).

===Familienamensectie===

Dit familienamendeel bevat die naamelementen die samen de familienaam uitmaken. Gramps laat u toe om samengestelde familienamen of meerdere familienamen in te voeren.

*Een {{man label|prefix:}} voor de familienaam dat niet gebruikt wordt bij het sorteren (zoals "de" of "van").
*{{man label|Familienaam}} dit is de ruimte bedoeld voor de eigenlijk familienaam.
*{{man label|Connectie}} vaak gebruikt in matroniem of patroniem naamvormen zoals ''dotter''.
*{{man label|Oorsprong}} geeft aan welk naamtype de familienaam heeft en de mogelijke afleiding.
*{{man label|Familiebijnaam:}} een meestal niet-officiële naam aan de familie gegeven om ze te kunnen onderscheiden van personen met dezelfde familienaam. Vaak wordt hier een naam van de familieboerderij gebruikt voorbeeld Peeters van de Haaghoek.

Zie ook: [http://www.gramps-project.org/wiki/index.php?title=Names Names wiki entry]

Klik het icoon in de rechterbovenhoek {{man label|gegeven is openbaar}} aan, om dit gegeven als privaat of openbaar te kenmerken. Dit laat u toe om deze naam weg te laten in verslagen indien u dit wenst.

===Tab algemeen===

De {{man label|opties}} laten u toe om specifieke groepering, sortering en naamweergave-eigenschappen aan te passen en ook de mogelijk een datum toe te kennen aan de naamgeving.

* Het veld {{man label|Groeperen als:}} geeft de mogelijkheid om een alternatief groeperingschema voor een persoon in het boomscherm. Dit vervangt dan het standaardschema gebaseerd op de familienamen. Dit kan nodig zijn om soortgelijke familienamen te groeperen -- voorbeeld van de Russische namen Ivanov en Ivanova worden als dezelfde namen beschouwd maar het verschil in geslacht wordt weergegeven in een verschillende spelling. Om in het veld gegevens te kunnen intypen moet u de controleknop {{man label|Overschrijven}} aanklikken.
:Personen worden weergegeven volgens een naamschema dat vastgelegd wordt in de voorkeuren (de standaard).
:Hier kunt u dit aanpassen en de persoon volgens een eigen naamschema tonen (bijkomende naamformaten kunnen vastgelegd worden onder voorkeuren).
*De velden {{man label|Sorteren als:}} en {{man label|Weergeven als:}} bepalen hoe de naam wordt getoond in het personenscherm en in de verslagen. Het veld sorteren als laat u toe het standaard naamschema zoals in de voorkeuren vastgelegd te vervangen door een ander schema. Dit kan bijvoorbeeld handig zijn indien u plots een aantal Zweedse namen in de familiestamboom moet invoeren. Deze bestaan meestal uit een voornaam en patroniem. Voor de rest van de familiestamboom kunnen de namen gesorteerd worden op Familienaam, Voornaam. Hier kunt u dan opgeven dat de sorteervolgorde steeds Patroniem, Voornaam dient te zijn.
:Hier maakt u zeker dat deze persoon gesorteerd wordt volgens een eigen naamschema (extra schema's kunnen ingegeven worden bij voorkeuren).
:Weergeven als laat u toe om vast te leggen hoe een naam getoond wordt. Het kan zijn dat u een naam op een welbepaalde manier wenst te sorteren maar de naam toch wenst te tonen volgens de voorkeuren.
:Het personenboomscherm groepeert personen onder de voorkeursnaam. U kunt deze instelling wijzigen door hier een groepswaarde in te stellen. U dient dan wel de vraag te beantwoorden of u enkel deze persoon of alle personen met deze welbepaalde voorkeursnaam wenst te groeperen.

*Het {{man label|Datum:}} veld kan informatie bevatten over de geldigheidsduur van deze naam -- u kunt tevens bereiken gebruiken indien gewenst. Het icoon bewerken opent een dialoog waar u dan de [[Gramps_3.4_Wiki_Manual_-_Entering_and_Editing_Data:_Detailed_-_part_1/nl#Datums_aanpassen|datums kunt aanpassen]]. Voorbeeld van een huwelijksnaam, de datum dat deze naam voor het eerst werd gebruikt of de huwelijksdatum.

===Tab Broncitaten===

De tab {{man label|Citaten}} toont informatie over de bronnen en de citaten die relevant zijn voor deze naam en laat toe om deze informatie te wijzigen en aan te passen. Het centrale gedeelte toont een lijst van bronverwijzingen en citaatverwijzingen die in het gegevensbestand opgeslagen zijn. De {{man button|+}} , {{man button|Bewerken}} en {{man button|-}} knoppen laten u toe om respectievelijk bronnenverwijzingen voor deze naam toe te voegen, aan te passen en te verwijderen. Merk op dat de {{man button|Bewerken}} en {{man button|-}} knoppen enkel dan beschikbaar zijn indien er een bronverwijzing uit de lijst werd geselecteerd.

Meer informatie: [[Gramps_3.4_Wiki_Manual_-_Entering_and_Editing_Data:_Detailed_-_part_2/nl#Broninformatie_aanpassen|broninformatie aanpassen]]

===Tab Opmerkingen===

De tab {{man label|Opmerkingen}} toont alle opmerkingen die verband houden met de naam. Om een opmerking toe te voegen of bestaande opmerkingen aan te passen kunt u eenvoudig de tekst wijzigen in het tekstingaveveld.

Meer informatie: [[Gramps_3.4_Wiki_Manual_-_Entering_and_Editing_Data:_Detailed_-_part_2/nl#Opmerkingeninformatie_aanpassen|opmerkingeninformatie aanpassen]]

== Tab Kenmerken ==

[[Image:Edit-at-31-nl.png|thumb|250px|Fig. 2. Kenmerken bewerken]]

[[Attributes_in_GRAMPS/nl|Kenmerken]] worden aangepast met een dialoog die verschijnt indien u op de tab klikt:

{{-}}

{{man tip|Tip|De hoofdingen van de tabs geven weer of er verdere informatie beschikbaar is: indien een tab informatie bevat, wordt de hoofding '''vet''' weergegeven; omgekeerd als de hoofding in een normaal lettertype (niet vet) wordt weergegeven, is geen verdere informatie beschikbaar.}}

Twee gegevens kunnen hier ingevuld worden:
# Het {{man label|Kenmerk}} dat u wenst te gebruiken Bijvoorbeeld: lengte (voor een persoon), weer van de dag (voor een gebeurtenis),... U kunt dit gebruiken om informatieknipsels die u verzamelde, op te slaan en die u aan bronnen wenst te koppelen. Kenmerken kunnen voor personen, families, gebeurtenissen en media-objecten gebruikt worden.
# De {{man label|Waarde}} van het kenmerk. Vb. ''1,8, zonnig of blauwe ogen''.

De informatie kan in de voorziene tekstingavevelden worden ingetypt. De kenmerknaam kan ook gekozen worden uit een aantal beschikbare mogelijkheden via een uitvalmenu.

{{man note|Opmerkingen|Verscheidene reeds beschikbare kenmerken verwijzen naar de 'GEDCOM'-standaard.}}

Klik het icoon in de rechterbovenhoek {{man label|gegeven is openbaar}} aan, om dit gegeven als privaat of openbaar te kenmerken. Dit laat u toe om deze naam weg te laten in verslagen indien u dit wenst.

*Broncitaten

De tab {{man label|Citaten}} toont informatie over de bronnen en de citaten die relevant zijn voor dit kenmerk en laat toe om deze informatie te wijzigen en aan te passen. Het centrale gedeelte toont een lijst van bronverwijzingen en citaatverwijzingen die in het gegevensbestand opgeslagen zijn. De {{man button|+}} , {{man button|Bewerken}} en {{man button|-}} knoppen laten u toe om respektievelijk bronnenverwijzingen voor deze naam toe te voegen, aan te passen en te verwijderen. Merk op dat de {{man button|Bewerken}} en {{man button|-}} knoppen enkel dan beschikbaar zijn indien er een bronverwijzing uit de lijst werd geselecteerd.

*Opmerkingen

De tab {{man label|Opmerkingen}} toont alle opmerkingen die verband houden met het kenmerk. Om een opmerking toe te voegen of bestaande opmerkingen aan te passen kunt u eenvoudig de tekst wijzigen in het tekstingaveveld.

De {{man label|Opmaak}} optie laat u toe om het uitzicht van de opmerking in een uitdruk (bijvoorbeeld in verslagen of webpagina's) aan te passen. Door {{man label|Opmaak}} niet aan te klikken worden alle meervoudige spaties, tabs en eindelijnkarakters vervangen door één enkele spatie in de uitdruk. Twee opeenvolgende nieuwe lijnen (ook lege lijn) geven een nieuwe paragraaf aan. In het andere geval worden de meervoudige spaties, tabs en nieuwe lijnen behouden, zodat de uitdruk er juist zo uitziet zoals u de tekst in het ingavescherm hebt ingevoerd.

== Tab Adressen ==

[[Image:Address-Editor-33-nl.png|thumb|250px|Fig. 3. Adres bewerken]]
Adressen worden aangepast met de {{man label|Adres bewerken}} dialoog:

Volgende informatie kan hier ingevoerd worden:

Het bovenste venstergedeelte laat u toe om de meeste algemene adresinformatie in te vullen:
#{{man label|Datum}}: datum waarop het adres geldig is/was.
#{{man label|Straat}}: de straat van het adres.
#{{man label|Plaats}}: de plaats waar het adres is.
#{{man label|Stad, dorp}}: de stad of het dorp waar het adres is.
#{{man label|Staat/Provincie}}: de staat of de provincie waar het adres is.
#{{man label|Land}}: land van het adres.
#{{man label|Postcode}}: postcode.
#{{man label|Tel.}}: telefoonnummer verbonden met het adres.

U kunt gelijk welke tab naar voren brengen door op de juiste hoofding te klikken. Het onderste deel heeft een {{man button|OK}} en een {{man button|Annuleren}} knop. Door op de {{man button|OK}} knop te klikken kunt u steeds alle veranderingen die u in alle tabs maakte opslaan en het dialoogscherm stuiten. Door op de {{man button|Annuleren}} knop te klikken kunt u steeds het dialoogscherm sluiten zonder de veranderingen op te slaan.

{{man tip|Tip|De hoofdingen van de tabs geven weer of er verdere informatie beschikbaar is: indien een tab informatie bevat, wordt de hoofding '''vet''' weergegeven; omgekeerd als de hoofding in een normaal lettertype (niet vet) wordt weergegeven, is geen verdere informatie beschikbaar.}}

{{man tip|Opmerking|Gebruik een residentie gebeurtenis om genealogische adresgegevens op te slaan.}}

De informatie kan ingevoerd worden in de juiste tekstingavevelden.
Klik het icoon met het slot {{man label|gegeven is openbaar}} aan, om dit gegeven als privaat of openbaar te kenmerken. Dit laat u toe om deze naam weg te laten in verslagen indien u dit wenst.

*Broncitaten

De tab {{man label|Broncitaten}} toont informatie over de bronnen en de citaten die relevant zijn voor dit adres en laat toe om deze informatie te wijzigen en aan te passen. Het centrale gedeelte toont een lijst van bronverwijzingen en citaatverwijzingen die in het gegevensbestand opgeslagen zijn. De {{man button|+}} , {{man button|Bewerken}} en {{man button|-}} knoppen laten u toe om respectievelijk bronnenverwijzingen voor deze naam toe te voegen, aan te passen en te verwijderen. Merk op dat de {{man button|Bewerken}} en {{man button|-}} knoppen enkel dan beschikbaar zijn indien er een bronverwijzing uit de lijst werd geselecteerd.

*Opmerkingen

De tab {{man label|Opmerkingen}} toont alle opmerkingen verbonden met dit adres. Om een opmerking toe te voegen of een bestaande opmerking aan te passen past u eenvoudig de tekst aan in het ingavescherm.

De {{man label|Opmaak}} optie laat u toe om het uitzicht van de opmerking in een uitdruk (bijvoorbeeld in verslagen of webpagina's) aan te passen. Door {{man label|Opmaak}} niet aan te klikken worden alle meervoudige spaties, tabs en eindelijnkarakters vervangen door één enkele spatie in de uitdruk. Twee opeenvolgende nieuwe lijnen (ook lege lijn) geven een nieuwe paragraaf aan. In het andere geval worden de meervoudige spaties, tabs en nieuwe lijnen behouden, zodat de uitdruk er juist zo uitziet zoals u de tekst in het ingavescherm hebt ingevoerd.

== Gegevens samenvoegen ==

Het kan gebeuren dat verschillende gegevens in het gegevensbestand hetzelfde onderwerp blijken te beschrijven: dezelfde persoon, dezelfde plaats of dezelfde bron. Misschien zijn de gegevens per vergissing tweemaal ingegeven of het kan zijn dat nieuwe informatie aantoont dat twee gegevens verwijzen naar eenzelfde persoon. Ook kan het zijn dat door het importeren van een GEDCOM-bestand van een familielid waarvan de gegevens gedeeltelijk uw eigen gegevens overlappen.

Telkens u duplicaten ontdekt, is samenvoegen van de gegevens een goede manier om de situatie te corrigeren.

{{man tip|1=Tip|2=Om een samenvoeging te kunnen doen moeten exact twee gegevens geselecteerd worden in het desbetreffende scherm (personen-, bronnen- of locatiescherm). Dit doet u door eerst een gegeven te selecteren om vervolgens een tweede gegeven te selecteren terwijl u de {{man key press|Ctrl}} toets ingedrukt houdt.}}

===Personen samenvoegen===

Personen samenvoegen gebeurd via het {{man menu|Bewerken}} menu.

{{man note|Opmerking|Het samenvoegen van personen zal geen informatie verwijderen. De beslissingen die u neemt tijdens het samenvoegen zullen enkel een effect hebben op welke informatie als primair en secundair zal beschouwd worden voor het samengevoegde gegeven.}}

*Samenvoegen

[[Image:Merge-dialog-regular-33-nl.png|left|thumb|350px|Fig. 4. Personen samenvoegen (normaal scherm view)]]
[[Image:Merge-dialog-expanded-33-nl.png|right|thumb|350px|Fig. 5. Personen samenvoegen (uitgebreid scherm)]]

Wanneer twee personen zijn geselecteerd, kiest u {{man menu|''' Bewerken ->Samenvoegen...}} om de aanpassingsdialoog te tonen.

Door te klikken op het driehoekje links naast {{man label|Gedetailleerde selectie}} wordt het uitgebreide scherm met meer informatie getoond over de personen die samengevoegd kunnen worden.

Om nog meer informatie over de personen te zien, klikt u op de driehoek links van {{man label|Contextinformatie}}. Dan wordt zeer veel informatie van beide personen getoond en kunt u vergelijken.

Wilt u toch doorgaan met het samenvoegen, kiest u met behulp van cirkels {{man label| Selecteren}} welk gegeven moet gebruikt worden als primaire gegevensbron. Klik vervolgens op {{man button|OK}}.

De andere gegevens zullen als alternatieve gegevensbron bewaard worden.

Meer bepaald zullen alle namen van het alternatieve gegeven beschouwd worden als alternatieve namen voor het samengevoegde gegeven. Zo ook zullen ouders, kinderen en echtgenoten dus alternatieve ouders, kinderen en echtgenoten worden van het samengevoegde gegeven.

{{-}}

===Families samenvoegen===

Wanneer twee families zijn geselecteerd, kiest u {{man menu|''' Bewerken ->Samenvoegen...}} om de aanpassingsdialoog te tonen.

Door te klikken op het driehoekje links naast {{man label|Gedetailleerde selectie}} wordt het uitgebreide scherm met meer informatie getoond over de families die samengevoegd kunnen worden.

Het venster laat u toe om een beslissing te nemen of de families al dan niet moeten samengevoegd worden.

Indien u beslist dat de gegevens niet samengevoegd dienen te worden, klikt u op {{man button|Annuleren}} om het venster te sluiten zonder aanpassingen. Wilt u toch doorgaan met het samenvoegen, kiest u met behulp van de cirkels die aan de linkerzijde van het venster, naast de familienamen staan om de titel van de samengevoegde familie te bepalen. Vervolgens klikt u op {{man button|OK}}.

{{-}}

===Gebeurtenissen samenvoegen===

Wanneer twee gebeurtenissen zijn geselecteerd, kiest u {{man menu|''' Bewerken ->Samenvoegen...}} om de aanpassingsdialoog te tonen.

Door te klikken op het driehoekje links naast {{man label|Gedetailleerde selectie}} wordt het uitgebreide scherm met meer informatie getoond over de gebeurtenissen die samengevoegd kunnen worden.

Het venster laat u toe om een beslissing te nemen of de gebeurtenissen al dan niet moeten samengevoegd worden.

Indien u beslist dat de gegevens niet samengevoegd dienen te worden, klikt u op {{man button|Annuleren}} om het venster te sluiten zonder aanpassingen. Wilt u toch doorgaan met het samenvoegen, kiest u met behulp van de cirkels die aan de linkerzijde van het venster, naast de gebeurtenisnamen staan om de titel van de samengevoegde gebeurtenis te bepalen. Vervolgens klikt u op {{man button|OK}}.

{{-}}

===Bronnen samenvoegen===

[[Image:Merge-sources-regular-33-nl.png|left|thumb|250px|Fig. 6. Merge sources (regular)]]
[[Image:Merge-sources-expanded-33-nl.png|right|thumb|250px|Fig. 7. Merge sources (expanded)]]
Wanneer twee bronnen zijn geselecteerd, kiest u {{man menu|''' Bewerken ->Samenvoegen...}} om de aanpassingsdialoog te tonen.

Door te klikken op het driehoekje links naast {{man label|Gedetailleerde selectie}} wordt het uitgebreide scherm met meer informatie getoond over de bronnen die samengevoegd kunnen worden.

Het venster laat u toe om een beslissing te nemen of de bronnen al dan niet moeten samengevoegd worden. Indien u beslist dat de gegevens niet samengevoegd dienen te worden, klikt u op {{man button|Annuleren}} om het venster te sluiten zonder aanpassingen.
Wilt u toch doorgaan met het samenvoegen, kiest u met behulp van de dubbele rijen cirkels die naast de bronnengegevens staan welke titel, auteur, afgekorte titel, publicatie-informatie en Gramps-id de samengevoegde bron moet hebben. Vervolgens klikt u op {{man button|OK}}.

{{-}}

===Locaties samenvoegen===

[[Image:Merge-places-regular-33-nl.png|thumb|left|250px|Fig. 8. Locaties samenvoegen (normaal)]]
[[Image:Merge-places-expanded-33-nl.png|thumb|right|250px|Fig. 9. Locaties samenvoegen (uitgebreid)]]

Door te klikken op het driehoekje links naast {{man label|Gedetailleerde selectie}} wordt het uitgebreide scherm met meer informatie getoond over de locaties die samengevoegd kunnen worden.

Wanneer twee locaties zijn geselecteerd, kiest u {{man menu|''' Bewerken ->Samenvoegen...}} om de aanpassingsdialoog te tonen.

Het venster laat u toe om een beslissing te nemen of de locaties al dan niet moeten samengevoegd worden.

Indien u beslist dat de gegevens niet samengevoegd dienen te worden, klikt u op {{man button|Annuleren}} om het venster te sluiten zonder aanpassingen.
Wilt u toch doorgaan met het samenvoegen, kiest u met behulp van de cirkels die aan de linkerzijde van het venster, naast de locatienamen staan om de titel, lengte, breedte, locatie en ID van de samengevoegde locatie te bepalen. Vervolgens klikt u op {{man button|OK}}.

{{-}}

===Media-objecten samenvoegen===

Wanneer twee media-objecten zijn geselecteerd, kiest u {{man menu|''' Bewerken ->Samenvoegen...}} om de aanpassingsdialoog te tonen.

Door te klikken op het driehoekje links naast {{man label|Gedetailleerde selectie}} wordt het uitgebreide scherm met meer informatie getoond over de objecten die samengevoegd kunnen worden.

De getoonde dialoog laat u toe om een beslissing te nemen of de twee media-objecten al dan niet moeten samengevoegd worden.

Indien u beslist dat de gegevens niet samengevoegd dienen te worden, klikt u op {{man button|Annuleren}} om het venster te sluiten zonder aanpassingen. Wilt u toch doorgaan met het samenvoegen, kiest u met behulp van de cirkels die aan de linkerzijde van het venster, naast de media-objecten staan om de titel van het samengevoegde media-object te bepalen. Vervolgens klikt u op {{man button|OK}}.

{{-}}

===Bibliotheken samenvoegen===

Wanneer twee bibliotheken zijn geselecteerd, kiest u {{man menu|''' Bewerken ->Samenvoegen...}} om de aanpassingsdialoog te tonen.

Door te klikken op het driehoekje links naast {{man label|Gedetailleerde selectie}} wordt het uitgebreide scherm met meer informatie getoond over de bibliotheken die samengevoegd kunnen worden.

De getoonde dialoog laat u toe om een beslissing te nemen of de twee bibliotheken al dan niet moeten samengevoegd worden.

Indien u beslist dat de gegevens niet samengevoegd dienen te worden, klikt u op {{man button|Annuleren}} om het venster te sluiten zonder aanpassingen. Wilt u toch doorgaan met het samenvoegen, kiest u met behulp van de cirkels die aan de linkerzijde van het venster, naast de bibliotheeknamen staan om de titel van de samengevoegde bibliotheek te bepalen. Vervolgens klikt u op {{man button|OK}}.

{{-}}

===Opmerkingen samenvoegen===

Wanneer twee opmerkingen zijn geselecteerd, kiest u {{man menu|''' Bewerken ->Samenvoegen...}} om de aanpassingsdialoog te tonen.

Door te klikken op het driehoekje links naast {{man label|Gedetailleerde selectie}} wordt het uitgebreide scherm met meer informatie getoond over de opmerkingen die samengevoegd kunnen worden.

De getoonde dialoog laat u toe om een beslissing te nemen of de twee opmerkingen al dan niet moeten samengevoegd worden.

Indien u beslist dat de gegevens niet samengevoegd dienen te worden, klikt u op {{man button|Annuleren}} om het venster te sluiten zonder aanpassingen. Wilt u toch doorgaan met het samenvoegen, kiest u met behulp van de cirkels die aan de linkerzijde van het venster, naast de opmerkingen staan om de titel van de samengevoegde opmerking. Vervolgens klikt u op {{man button|OK}}.

{{-}}

{{man index/nl|Gramps 3.4 Wiki Manual - Entering and Editing Data:_Detailed_-_part_2/nl|Gramps_3.4_Wiki_Manual_-_Navigation/nl|3.4}}

{{languages|Gramps_3.4_Wiki_Manual_-_Entering_and_Editing_Data:_Detailed_-_part_3}}

[[Category:Nl:Documentatie|Invoeren en aanpassen gegevens: details_-deel_3]]

Import from another genealogy program

2015-03-14T15:54:55Z

Ennoborg: /* tmg2gramps */ download for TMG 8

{{Languages}}
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.

== Gramps to Gramps==

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.

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.

== Standard GEDCOM as transfer tool==

Most programs for family history can export and import [[GEDCOM]] (.ged) files.

# Check the documentation for your program to learn how to create a GEDCOM file with all your data.
#* If you have a choice, GEDCOM 5.5 Standard is usually the safest type of GEDCOM.
# 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, give it a good name, and click on the {{man button|Load Family Tree}} button to open.
# Now that a Family tree is loaded, choose in the menu {{man menu|Family Trees -> Import}}
# Locate the GEDCOM file created by your program, and choose {{man button|Open}}.

{{man warn| Check The Results |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. Gramps aims to support the GEDCOM 5.5. standard.}}

Take special attention 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.

== Spreadsheet import ==

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. The CSV import option currently doesn't allow import of all Gramps data. 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. For more details on this format see [[Gramps 4.0 Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

[[GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

== Import instructions from different programs ==

=== Ancestrologie ===

Ancestrologie seems to produce non-standard gedcom for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

* [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.

* [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.

* [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:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:
* _ANCES_CLE_FIXE .. special internal reference : "Who they are ?"
* _ANCES_ORDRE .. considered non-critical, events classification
* _ANCES_XACTE .. non-critical (certificat found = 1)
* _ANCES_XINSEE .. INSEE geographical code (evidently ''simplified 5-digit'')
* EVEN F .. invalid EVENTS_RECORDED format in a SOUR record
* EVEN I .. (same)
* LIEU .. a subdivision of place, is not our place but a division
* XTYPE .. these seem to be OBJE subordinates
* XIDEN .. considered non-critical, media object used for primary media (photo)
* XMODE .. " (file is not present at the FILE address)

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.

1 FILA Enfant légitime
becomes
1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard gedcom or gedcom extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

=== Ancestry.com ===

{{Out_of_date}}

GEDCOM produced by Ancestry.com is not fully readable by Gramps 2.0.x and 2.2.x (Relationship lost).
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.

=== Evidentia ===
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.

====General Tips====
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.

====People====
=====IMPORT INTO Evidentia as Subjects=====
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.

=====What Evidentia IMPORTS and EXPORTS=====
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:
* @I0000@ INDI (person's ID number, called a "Reference number" in Evidentia)
* NAME Lakshmi /Wolowitz/ (full name)
* GIVN Lakshmi (given or first name)
* SURN Wolowitz (surname or last name)
* SEX F (gender)
* BIRT (birth year)

====Events and Facts====
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.

=====Manually add Facts INTO Evidentia=====
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.

=====EXPORT some types of Facts to Gramps=====
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.

====Sources & Citations====
=====Manually add to Evidentia FIRST=====
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.

There are two reasons to follow this workflow:
* 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.

* 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!

=====Match your Source Title and Source Abbreviation =====
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.

=====Complete Publication information Exported =====
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.

=====Citation Title only used in Evidentia=====
Citation Titles are only used within the Evidentia program, and don't effect gramps. So, choose whatever pattern you like for naming them.

====Claims & Proof====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:
* individual information: id, name, gender
* claim type: facts, events, or attributes
* source information: title, abbreviation, and full publication info (PUBL)
* full citation (PAGE)

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.

===== Evidentia-specific GEDCOM export =====
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).

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:
* 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.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* 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."

=== Family Tree Maker (FTM)===

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]].

====If you do not have access to Family Tree Maker:====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

====Specific instructions for FTM2005:====

Select File->Export File->Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

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.

{{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.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

====Programs for fixing some of the known problems====

* [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.

====Experimental way====

[[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.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

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].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

'''Modifications of gedcom from Heredis to import in Gramps'''

''With editor (like gedit ot note++) find and replace '''« > »''':''

'''1. Non standard tags of Heredis'''

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

'''2. Assign value Y to following to tags'''

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

''
'''3. Sources and Repositories'''

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

'''4. Change levels in Associations'''

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

'''5. Équivalents of disks drives when loaded Linux Gramps'''

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

'''6. For people's tags located in Events instead of Attributes'''

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, Gedcom generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to Gedcom generated by Heredis :

* Heredis format to Gedcom : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

=== Pro-Gen ===

Using GEDCOM to export data from Pro-Gen is less than ideal. Therefor a plugin was created.
The plugin is included in the Gramps distribution.

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

Import the data:
* start gramps
* create a new family database
* select that new database
* go to menu {{man menu|Family Trees-> Import}}
* in the file dialog go to the ~/pg30/nl/data directory
* select the .DEF of your Pro-Gen database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "Import"
* wait ...

=== The Master Genealogist (TMG) ===

You have two options.

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

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]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* 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.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

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?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

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.

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.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

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.

'''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]]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.

===== Data tmg2gramps successfully converts =====
Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"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.

*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.

*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.

===== Known issues =====
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:

#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).
#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.
#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.
#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.
#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.
#Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_4.0_Wiki_Manual_-_Tools#Media_Manager... |Gramps Media Manager]].
#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.

===== Preparing to Run tmg2gramps =====

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.

Before beginning, copy your entire TMG 'projects' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG 'projects' folder for posterity, just in case you may someday need it. On Windows XP, the TMG 'projects' folder is located here:

C:\Program Files\The Master Genealogist\projects

Once you've copied it, rename the copied 'projects' folder to 'tmgdata'

Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of 'tmgdata' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the 'tmgdata' directory. Once there, simply type this at the command prompt:

$ rename 'y/A-Z/a-z/' *

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:

$ sudo apt-get install mysql-server

That will either install MySQL, or if it is already installed, it won't cause any harm.

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:

$ sudo apt-get install libdbd-xbase-perl

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:

$ mysql -u root

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

$ mysql -u root -p

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:

mysql> show databases;

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 tmg_gramps) by typing this at the mysql prompt:

mysql> create database tmg_gramps;

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';

You can now exit MySQL:

mysql> exit

...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 'tmgdata' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

$ ls -l

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:

smith__.acc

smith__.pjc

smith_$.cdx

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

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:

$ chmod +x tmg2gramps.pl

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

*name of TMG project: smith
*home directory: /home/asmith

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

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

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.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

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:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

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.

==== TMG-Working-Group ====

Information only at the moment.

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

https://github.com/girimonti/TMG-Working-Group

==== tmgviewer ====

An attempt at reading a TMG file Directly from python and does not use Genbridge. [[user:sam888]]

See {{bug|7591}} for more details and tests.

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partials sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

== See also ==
* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]

[[Category:How do I...]]
[[Category:Developers/General]]

File:Tmg2gramps-v8.gz

2015-03-14T15:52:20Z

Ennoborg: Perl script for TMG version 8.

Perl script for TMG version 8.

Import from another genealogy program

2015-03-14T15:49:24Z

Ennoborg: /* tmg2gramps */

{{Languages}}
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.

== Gramps to Gramps==

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.

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.

== Standard GEDCOM as transfer tool==

Most programs for family history can export and import [[GEDCOM]] (.ged) files.

# Check the documentation for your program to learn how to create a GEDCOM file with all your data.
#* If you have a choice, GEDCOM 5.5 Standard is usually the safest type of GEDCOM.
# 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, give it a good name, and click on the {{man button|Load Family Tree}} button to open.
# Now that a Family tree is loaded, choose in the menu {{man menu|Family Trees -> Import}}
# Locate the GEDCOM file created by your program, and choose {{man button|Open}}.

{{man warn| Check The Results |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. Gramps aims to support the GEDCOM 5.5. standard.}}

Take special attention 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.

== Spreadsheet import ==

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. The CSV import option currently doesn't allow import of all Gramps data. 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. For more details on this format see [[Gramps 4.0 Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

[[GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

== Import instructions from different programs ==

=== Ancestrologie ===

Ancestrologie seems to produce non-standard gedcom for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

* [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.

* [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.

* [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:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:
* _ANCES_CLE_FIXE .. special internal reference : "Who they are ?"
* _ANCES_ORDRE .. considered non-critical, events classification
* _ANCES_XACTE .. non-critical (certificat found = 1)
* _ANCES_XINSEE .. INSEE geographical code (evidently ''simplified 5-digit'')
* EVEN F .. invalid EVENTS_RECORDED format in a SOUR record
* EVEN I .. (same)
* LIEU .. a subdivision of place, is not our place but a division
* XTYPE .. these seem to be OBJE subordinates
* XIDEN .. considered non-critical, media object used for primary media (photo)
* XMODE .. " (file is not present at the FILE address)

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.

1 FILA Enfant légitime
becomes
1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard gedcom or gedcom extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

=== Ancestry.com ===

{{Out_of_date}}

GEDCOM produced by Ancestry.com is not fully readable by Gramps 2.0.x and 2.2.x (Relationship lost).
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.

=== Evidentia ===
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.

====General Tips====
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.

====People====
=====IMPORT INTO Evidentia as Subjects=====
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.

=====What Evidentia IMPORTS and EXPORTS=====
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:
* @I0000@ INDI (person's ID number, called a "Reference number" in Evidentia)
* NAME Lakshmi /Wolowitz/ (full name)
* GIVN Lakshmi (given or first name)
* SURN Wolowitz (surname or last name)
* SEX F (gender)
* BIRT (birth year)

====Events and Facts====
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.

=====Manually add Facts INTO Evidentia=====
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.

=====EXPORT some types of Facts to Gramps=====
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.

====Sources & Citations====
=====Manually add to Evidentia FIRST=====
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.

There are two reasons to follow this workflow:
* 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.

* 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!

=====Match your Source Title and Source Abbreviation =====
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.

=====Complete Publication information Exported =====
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.

=====Citation Title only used in Evidentia=====
Citation Titles are only used within the Evidentia program, and don't effect gramps. So, choose whatever pattern you like for naming them.

====Claims & Proof====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:
* individual information: id, name, gender
* claim type: facts, events, or attributes
* source information: title, abbreviation, and full publication info (PUBL)
* full citation (PAGE)

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.

===== Evidentia-specific GEDCOM export =====
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).

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:
* 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.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* 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."

=== Family Tree Maker (FTM)===

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]].

====If you do not have access to Family Tree Maker:====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

====Specific instructions for FTM2005:====

Select File->Export File->Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

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.

{{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.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

====Programs for fixing some of the known problems====

* [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.

====Experimental way====

[[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.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

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].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

'''Modifications of gedcom from Heredis to import in Gramps'''

''With editor (like gedit ot note++) find and replace '''« > »''':''

'''1. Non standard tags of Heredis'''

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

'''2. Assign value Y to following to tags'''

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

''
'''3. Sources and Repositories'''

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

'''4. Change levels in Associations'''

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

'''5. Équivalents of disks drives when loaded Linux Gramps'''

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

'''6. For people's tags located in Events instead of Attributes'''

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, Gedcom generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to Gedcom generated by Heredis :

* Heredis format to Gedcom : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

=== Pro-Gen ===

Using GEDCOM to export data from Pro-Gen is less than ideal. Therefor a plugin was created.
The plugin is included in the Gramps distribution.

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

Import the data:
* start gramps
* create a new family database
* select that new database
* go to menu {{man menu|Family Trees-> Import}}
* in the file dialog go to the ~/pg30/nl/data directory
* select the .DEF of your Pro-Gen database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "Import"
* wait ...

=== The Master Genealogist (TMG) ===

You have two options.

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

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]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* 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.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

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?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

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.

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.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

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.

'''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 [[File:here]]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.

===== Data tmg2gramps successfully converts =====
Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"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.

*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.

*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.

===== Known issues =====
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:

#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).
#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.
#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.
#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.
#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.
#Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_4.0_Wiki_Manual_-_Tools#Media_Manager... |Gramps Media Manager]].
#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.

===== Preparing to Run tmg2gramps =====

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.

Before beginning, copy your entire TMG 'projects' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG 'projects' folder for posterity, just in case you may someday need it. On Windows XP, the TMG 'projects' folder is located here:

C:\Program Files\The Master Genealogist\projects

Once you've copied it, rename the copied 'projects' folder to 'tmgdata'

Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of 'tmgdata' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the 'tmgdata' directory. Once there, simply type this at the command prompt:

$ rename 'y/A-Z/a-z/' *

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:

$ sudo apt-get install mysql-server

That will either install MySQL, or if it is already installed, it won't cause any harm.

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:

$ sudo apt-get install libdbd-xbase-perl

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:

$ mysql -u root

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

$ mysql -u root -p

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:

mysql> show databases;

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 tmg_gramps) by typing this at the mysql prompt:

mysql> create database tmg_gramps;

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';

You can now exit MySQL:

mysql> exit

...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 'tmgdata' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

$ ls -l

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:

smith__.acc

smith__.pjc

smith_$.cdx

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

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:

$ chmod +x tmg2gramps.pl

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

*name of TMG project: smith
*home directory: /home/asmith

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the ''italicized'' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/''asmith''/tmgdata ''smith'' converted_''smith''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

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.

When tmg2gramps has finished running, converted_''smith''_tmgdata.xml should be in your home folder.

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:

$ mv converted_''smith''_tmgdata.xml converted_''smith''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

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.

==== TMG-Working-Group ====

Information only at the moment.

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

https://github.com/girimonti/TMG-Working-Group

==== tmgviewer ====

An attempt at reading a TMG file Directly from python and does not use Genbridge. [[user:sam888]]

See {{bug|7591}} for more details and tests.

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partials sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

== See also ==
* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]

[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2015-03-14T15:46:55Z

Ennoborg: /* tmg2gramps */

{{Languages}}
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.

== Gramps to Gramps==

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.

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.

== Standard GEDCOM as transfer tool==

Most programs for family history can export and import [[GEDCOM]] (.ged) files.

# Check the documentation for your program to learn how to create a GEDCOM file with all your data.
#* If you have a choice, GEDCOM 5.5 Standard is usually the safest type of GEDCOM.
# 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, give it a good name, and click on the {{man button|Load Family Tree}} button to open.
# Now that a Family tree is loaded, choose in the menu {{man menu|Family Trees -> Import}}
# Locate the GEDCOM file created by your program, and choose {{man button|Open}}.

{{man warn| Check The Results |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. Gramps aims to support the GEDCOM 5.5. standard.}}

Take special attention 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.

== Spreadsheet import ==

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. The CSV import option currently doesn't allow import of all Gramps data. 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. For more details on this format see [[Gramps 4.0 Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

[[GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

== Import instructions from different programs ==

=== Ancestrologie ===

Ancestrologie seems to produce non-standard gedcom for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

* [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.

* [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.

* [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:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:
* _ANCES_CLE_FIXE .. special internal reference : "Who they are ?"
* _ANCES_ORDRE .. considered non-critical, events classification
* _ANCES_XACTE .. non-critical (certificat found = 1)
* _ANCES_XINSEE .. INSEE geographical code (evidently ''simplified 5-digit'')
* EVEN F .. invalid EVENTS_RECORDED format in a SOUR record
* EVEN I .. (same)
* LIEU .. a subdivision of place, is not our place but a division
* XTYPE .. these seem to be OBJE subordinates
* XIDEN .. considered non-critical, media object used for primary media (photo)
* XMODE .. " (file is not present at the FILE address)

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.

1 FILA Enfant légitime
becomes
1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard gedcom or gedcom extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

=== Ancestry.com ===

{{Out_of_date}}

GEDCOM produced by Ancestry.com is not fully readable by Gramps 2.0.x and 2.2.x (Relationship lost).
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.

=== Evidentia ===
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.

====General Tips====
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.

====People====
=====IMPORT INTO Evidentia as Subjects=====
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.

=====What Evidentia IMPORTS and EXPORTS=====
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:
* @I0000@ INDI (person's ID number, called a "Reference number" in Evidentia)
* NAME Lakshmi /Wolowitz/ (full name)
* GIVN Lakshmi (given or first name)
* SURN Wolowitz (surname or last name)
* SEX F (gender)
* BIRT (birth year)

====Events and Facts====
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.

=====Manually add Facts INTO Evidentia=====
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.

=====EXPORT some types of Facts to Gramps=====
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.

====Sources & Citations====
=====Manually add to Evidentia FIRST=====
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.

There are two reasons to follow this workflow:
* 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.

* 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!

=====Match your Source Title and Source Abbreviation =====
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.

=====Complete Publication information Exported =====
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.

=====Citation Title only used in Evidentia=====
Citation Titles are only used within the Evidentia program, and don't effect gramps. So, choose whatever pattern you like for naming them.

====Claims & Proof====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:
* individual information: id, name, gender
* claim type: facts, events, or attributes
* source information: title, abbreviation, and full publication info (PUBL)
* full citation (PAGE)

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.

===== Evidentia-specific GEDCOM export =====
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).

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:
* 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.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* 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."

=== Family Tree Maker (FTM)===

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]].

====If you do not have access to Family Tree Maker:====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

====Specific instructions for FTM2005:====

Select File->Export File->Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

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.

{{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.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

====Programs for fixing some of the known problems====

* [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.

====Experimental way====

[[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.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

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].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

'''Modifications of gedcom from Heredis to import in Gramps'''

''With editor (like gedit ot note++) find and replace '''« > »''':''

'''1. Non standard tags of Heredis'''

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

'''2. Assign value Y to following to tags'''

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

''
'''3. Sources and Repositories'''

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

'''4. Change levels in Associations'''

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

'''5. Équivalents of disks drives when loaded Linux Gramps'''

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

'''6. For people's tags located in Events instead of Attributes'''

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, Gedcom generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to Gedcom generated by Heredis :

* Heredis format to Gedcom : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

=== Pro-Gen ===

Using GEDCOM to export data from Pro-Gen is less than ideal. Therefor a plugin was created.
The plugin is included in the Gramps distribution.

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

Import the data:
* start gramps
* create a new family database
* select that new database
* go to menu {{man menu|Family Trees-> Import}}
* in the file dialog go to the ~/pg30/nl/data directory
* select the .DEF of your Pro-Gen database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "Import"
* wait ...

=== The Master Genealogist (TMG) ===

You have two options.

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

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]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* 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.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

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?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

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.

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.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

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.

'''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:here]]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.

===== Data tmg2gramps successfully converts =====
Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"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.

*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.

*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.

===== Known issues =====
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:

#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).
#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.
#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.
#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.
#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.
#Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_4.0_Wiki_Manual_-_Tools#Media_Manager... |Gramps Media Manager]].
#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.

===== Preparing to Run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible.

Before beginning, copy your entire TMG 'projects' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG 'projects' folder for posterity, just in case you may someday need it. On Windows XP, the TMG 'projects' folder is located here:

C:\Program Files\The Master Genealogist\projects

Once you've copied it, rename the copied 'projects' folder to 'tmgdata'

Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of 'tmgdata' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the 'tmgdata' directory. Once there, simply type this at the command prompt:

$ rename 'y/A-Z/a-z/' *

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:

$ sudo apt-get install mysql-server

That will either install MySQL, or if it is already installed, it won't cause any harm.

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:

$ sudo apt-get install libdbd-xbase-perl

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:

$ mysql -u root

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

$ mysql -u root -p

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:

mysql> show databases;

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 tmg_gramps) by typing this at the mysql prompt:

mysql> create database tmg_gramps;

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';

You can now exit MySQL:

mysql> exit

...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 'tmgdata' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

$ ls -l

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:

smith__.acc

smith__.pjc

smith_$.cdx

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

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:

$ chmod +x tmg2gramps.pl

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

*name of TMG project: smith
*home directory: /home/asmith

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the ''italicized'' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/''asmith''/tmgdata ''smith'' converted_''smith''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

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.

When tmg2gramps has finished running, converted_''smith''_tmgdata.xml should be in your home folder.

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:

$ mv converted_''smith''_tmgdata.xml converted_''smith''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

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.

==== TMG-Working-Group ====

Information only at the moment.

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

https://github.com/girimonti/TMG-Working-Group

==== tmgviewer ====

An attempt at reading a TMG file Directly from python and does not use Genbridge. [[user:sam888]]

See {{bug|7591}} for more details and tests.

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partials sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

== See also ==
* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]

[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2015-03-14T15:43:55Z

Ennoborg: /* tmg2gramps */

{{Languages}}
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.

== Gramps to Gramps==

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.

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.

== Standard GEDCOM as transfer tool==

Most programs for family history can export and import [[GEDCOM]] (.ged) files.

# Check the documentation for your program to learn how to create a GEDCOM file with all your data.
#* If you have a choice, GEDCOM 5.5 Standard is usually the safest type of GEDCOM.
# 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, give it a good name, and click on the {{man button|Load Family Tree}} button to open.
# Now that a Family tree is loaded, choose in the menu {{man menu|Family Trees -> Import}}
# Locate the GEDCOM file created by your program, and choose {{man button|Open}}.

{{man warn| Check The Results |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. Gramps aims to support the GEDCOM 5.5. standard.}}

Take special attention 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.

== Spreadsheet import ==

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. The CSV import option currently doesn't allow import of all Gramps data. 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. For more details on this format see [[Gramps 4.0 Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

[[GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

== Import instructions from different programs ==

=== Ancestrologie ===

Ancestrologie seems to produce non-standard gedcom for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

* [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.

* [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.

* [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:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:
* _ANCES_CLE_FIXE .. special internal reference : "Who they are ?"
* _ANCES_ORDRE .. considered non-critical, events classification
* _ANCES_XACTE .. non-critical (certificat found = 1)
* _ANCES_XINSEE .. INSEE geographical code (evidently ''simplified 5-digit'')
* EVEN F .. invalid EVENTS_RECORDED format in a SOUR record
* EVEN I .. (same)
* LIEU .. a subdivision of place, is not our place but a division
* XTYPE .. these seem to be OBJE subordinates
* XIDEN .. considered non-critical, media object used for primary media (photo)
* XMODE .. " (file is not present at the FILE address)

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.

1 FILA Enfant légitime
becomes
1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard gedcom or gedcom extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

=== Ancestry.com ===

{{Out_of_date}}

GEDCOM produced by Ancestry.com is not fully readable by Gramps 2.0.x and 2.2.x (Relationship lost).
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.

=== Evidentia ===
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.

====General Tips====
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.

====People====
=====IMPORT INTO Evidentia as Subjects=====
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.

=====What Evidentia IMPORTS and EXPORTS=====
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:
* @I0000@ INDI (person's ID number, called a "Reference number" in Evidentia)
* NAME Lakshmi /Wolowitz/ (full name)
* GIVN Lakshmi (given or first name)
* SURN Wolowitz (surname or last name)
* SEX F (gender)
* BIRT (birth year)

====Events and Facts====
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.

=====Manually add Facts INTO Evidentia=====
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.

=====EXPORT some types of Facts to Gramps=====
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.

====Sources & Citations====
=====Manually add to Evidentia FIRST=====
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.

There are two reasons to follow this workflow:
* 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.

* 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!

=====Match your Source Title and Source Abbreviation =====
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.

=====Complete Publication information Exported =====
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.

=====Citation Title only used in Evidentia=====
Citation Titles are only used within the Evidentia program, and don't effect gramps. So, choose whatever pattern you like for naming them.

====Claims & Proof====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:
* individual information: id, name, gender
* claim type: facts, events, or attributes
* source information: title, abbreviation, and full publication info (PUBL)
* full citation (PAGE)

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.

===== Evidentia-specific GEDCOM export =====
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).

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:
* 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.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* 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."

=== Family Tree Maker (FTM)===

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]].

====If you do not have access to Family Tree Maker:====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

====Specific instructions for FTM2005:====

Select File->Export File->Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

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.

{{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.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

====Programs for fixing some of the known problems====

* [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.

====Experimental way====

[[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.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

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].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

'''Modifications of gedcom from Heredis to import in Gramps'''

''With editor (like gedit ot note++) find and replace '''« > »''':''

'''1. Non standard tags of Heredis'''

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

'''2. Assign value Y to following to tags'''

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

''
'''3. Sources and Repositories'''

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

'''4. Change levels in Associations'''

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

'''5. Équivalents of disks drives when loaded Linux Gramps'''

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

'''6. For people's tags located in Events instead of Attributes'''

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, Gedcom generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to Gedcom generated by Heredis :

* Heredis format to Gedcom : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

=== Pro-Gen ===

Using GEDCOM to export data from Pro-Gen is less than ideal. Therefor a plugin was created.
The plugin is included in the Gramps distribution.

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

Import the data:
* start gramps
* create a new family database
* select that new database
* go to menu {{man menu|Family Trees-> Import}}
* in the file dialog go to the ~/pg30/nl/data directory
* select the .DEF of your Pro-Gen database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "Import"
* wait ...

=== The Master Genealogist (TMG) ===

You have two options.

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

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]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* 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.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

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?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

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.

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.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

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.

'''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 [[File:here]]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.

===== Data tmg2gramps successfully converts =====
Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"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.

*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.

*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.

===== Known issues =====
Here are some known issues that have occurred when using tmg2gramps:

#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).
#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.
#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.
#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.
#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.
#Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_4.0_Wiki_Manual_-_Tools#Media_Manager... |Gramps Media Manager]].
#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.

===== Preparing to Run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible.

Before beginning, copy your entire TMG 'projects' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG 'projects' folder for posterity, just in case you may someday need it. On Windows XP, the TMG 'projects' folder is located here:

C:\Program Files\The Master Genealogist\projects

Once you've copied it, rename the copied 'projects' folder to 'tmgdata'

Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of 'tmgdata' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the 'tmgdata' directory. Once there, simply type this at the command prompt:

$ rename 'y/A-Z/a-z/' *

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:

$ sudo apt-get install mysql-server

That will either install MySQL, or if it is already installed, it won't cause any harm.

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:

$ sudo apt-get install libdbd-xbase-perl

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:

$ mysql -u root

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

$ mysql -u root -p

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:

mysql> show databases;

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 tmg_gramps) by typing this at the mysql prompt:

mysql> create database tmg_gramps;

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';

You can now exit MySQL:

mysql> exit

...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 'tmgdata' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

$ ls -l

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:

smith__.acc

smith__.pjc

smith_$.cdx

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

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:

$ chmod +x tmg2gramps.pl

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

*name of TMG project: smith
*home directory: /home/asmith

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the ''italicized'' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/''asmith''/tmgdata ''smith'' converted_''smith''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

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.

When tmg2gramps has finished running, converted_''smith''_tmgdata.xml should be in your home folder.

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:

$ mv converted_''smith''_tmgdata.xml converted_''smith''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

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.

==== TMG-Working-Group ====

Information only at the moment.

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

https://github.com/girimonti/TMG-Working-Group

==== tmgviewer ====

An attempt at reading a TMG file Directly from python and does not use Genbridge. [[user:sam888]]

See {{bug|7591}} for more details and tests.

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partials sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

== See also ==
* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]

[[Category:How do I...]]
[[Category:Developers/General]]

Download

2014-08-16T12:07:44Z

Ennoborg: /* MS Windows */ 4.1.0

__NOTOC__
{{languages}}
== Linux ==

[[Image:Linux_220x261.png|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version ({{version}}) (advanced users only)]]</big>
{{-}}

== MS Windows ==

[[Image:windows_180x160.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO32}}/{{filename_windows_AIO32}}.exe Windows Installer (32-bit) {{version_windows_AIO32}}]
    
[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO64}}/{{filename_windows_AIO64}}.exe Windows Installer (64-bit) {{version_windows_AIO64}}]</big>

After download: double-click to install Gramps.

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

Alternative independent MS Windows version [[#3|[3]]].

Latest 4.1.0 [http://sourceforge.net/projects/gramps/files/Stable/4.1.0/ here].

== Mac OS X ==

[[Image:macos_200x200.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]]. Read the [[Mac OS X:Application package|before installation]] instructions.

Mac OS X 10.5, 10.6, 10.7, 10.8, and 10.9     <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{filename_mac_intel}}.dmg Intel {{version_Mac}}]</big>
    
Mac OS X 10.5    <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{filename_mac_ppc}}.dmg Power PC {{version_Mac}}]</big>

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next drag the Gramps application to your application folder and double-click to launch it [[#2|[2]]].

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

{{-}}

== BSD ==

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux and BSD distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version (advanced users only)]]</big>
{{-}}

== Live CD ==

[[Image:Download_link.png|150px|left|link=http://sourceforge.net/projects/gramps/files/OldFiles/3.2.5/lgenealogy-6.1-desktop-i386.iso]]
'''Linux live CD Demonstration''' [[Linux_Genealogy_CD#Obtaining_the_CD|Obtaining the CD]] (727 MB) [[Linux Genealogy CD|Linux Genealogy CD based on Ubuntu 10.10 (Maverick Meerkat)]]. Allows you to trial a pre-installed Gramps {{Version Linux Live CD}}, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn..). If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install [http://www.ubuntulinux.org/ Ubuntu 10.10] and Gramps from the CD anytime you like.
{{-}}
[[Image:Download_link.png|150px|left|link=http://cdimage.ubuntu.com/edubuntu/releases/13.04/release/]]
'''Edubuntu 13.04''' includes Gramps 3.4.0
{{-}}

== Linux and BSD distributions ==

Most linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| border="1" cellspacing="0"
|Distribution
|GUI pkg manager
|Current versions
|Notes
|-
|'''Linux Mint'''
|Software Manager
|Nadia: Gramps 3.4.0-1 Lisa: Gramps 3.3.1-1 Isadora: Gramps 3.2.0-1
|
|-
|''' Mageia '''
|
|
|
|-
|[[Image:Ubuntu_32x32.png]]''' Ubuntu '''
| Software Centre
|Precise (12.04 LTS): Gramps 3.3.1 Saucy (13.10): Gramps 3.4.0 Trusty (14.04 LTS): Gramps: 4.0.3 Utopic (development): Gramps: 4.0.4
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]
|-
|[[Image:Fedora_32x32.png]]''' Fedora '''
|Add/Remove Software (Gnome) or Software Management (KDE)
|Fedora Rawhide: Gramps 3.4.3 Fedora 18: Gramps 3.4.2.
|
|-
|[[Image:Debianopenlogo-32.png]]''' [[Debian]] '''
|Add/Remove Software
|squeeze (old stable): Gramps 3.2.3 wheezy (stable): Gramps 3.4.0 jessie (testing): Gramps 4.0.4 [http://packages.debian.org/sid/gramps sid (unstable)]: Gramps 4.0.4
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[Image:Mandriva_32x32.png]]''' Mandriva '''
|Software Management in the 
Mandriva Linux Control Center
|
|Mandriva 2010.1: Gramps 3.3.1 Mandriva 2011: Gramps 3.2.6 See also [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Advanced_use:_Backports_and_candidate_updates backports] and contrib repository
|-
|[[Image:Redhat_32x32.png]]''' Redhat '''
|
|
|
|-
|''' openSUSE '''
|YaST ??
|openSUSE 12.3: Gramps 3.4.2
|[http://software.opensuse.org/package/gramps available versions]
|-
|'''Slackware'''
|
|Slackware 14.0: Gramps 3.4.2
|[http://pkgs.org/search/?keyword=gramps available versions]
|-
|'''NetBSD'''
|
|NetBSD: Gramps 3.4.3
|[http://pkgsrc.se/databases/gramps3 available versions]
|-
|'''FreeBSD'''
|
|FreeBSD: Gramps 3.3.0
|[http://portsmon.freebsd.org/portoverview.py?category=science&portname=gramps available versions]
|-
|'''PC-BSD'''
|
|PC-BSD: Gramps 3.3.0
|
|}

{{-}}

== Linux: Install latest version ==

If your distribution doesn't ship with Gramps or you wish to install a different version than it ships with, you could try to install the latest version of Gramps manually. Instructions are given below for a number of distributions.

{{man warn|1=Warning|2=This should only be attempted by experienced users, and after you have backed up your Family Tree.

The version of Gramps that has been included in your distribution will have been tested to work with the components in that distribution. If you try to install a different version of Gramps there is a possibility that the components needed for the new version of Gramps are not available for your distribution, or they are available, but don't work properly. You might not discover that there is a problem till you have already done some work with the new version of Gramps.

If you already have Gramps installed, and you are only making a 'point' upgrade (i.e. from Gramps x.y.z to x.y.z+1, e.g. from 3.4.3 to 3.4.4), then it is likely but not certain that Gramps will continue to work. However, if the change is much greater, especially if it is a major version change (e.g. from 2.y.z to 3.y.z), then the danger that it does not work properly is much greater.}}

[[Image:Debianopenlogo-32.png]]'''[[Debian]]''' and [[Image:Ubuntu_32x32.png]]''' Ubuntu ''' [http://sourceforge.net/projects/gramps/files/Stable/{{version}} Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved (change the filename to match the one you downloaded).

sudo dpkg -i gramps_{{version}}-1_all.deb

For other distributions, [[Image:Download_link.png|150px|link=http://sourceforge.net/projects/gramps/files/Stable/{{version}}/gramps-{{version}}.tar.gz]] the source and follow the instructions for [[Linux:Build from source]]

== Notes ==

[1]
Backup to Gramps XML. You will find backup in the Family Tree menu of recent Gramps versions, otherwise use export in the same menu but '''uncheck privacy options''' in the Exporter Assistant in order to export all data

[2]
Alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.

[3]
An alternative independent version is [http://sourceforge.net/projects/portableapps/files/Gramps%20Portable/ GrampsPortable_{{version_windows_portable}}.paf.exe] (20.3 MB)
[http://portableapps.com/apps/education/gramps_portable Portable Gramps from PortableApps.com] includes all dependencies required for Windows. ''Note:You can install it on C: then to run Gramps type C:\PortableApps\GrampsPortable\GrampsPortable.exe (Or the path you installed it to) or make a shortcut to that file on your desktop or start-menu.'' By Bart.S - '''[http://portableapps.com/blog/84601 Please report issues to the author.]''' (2012-09-07)

[[Category:Documentation]]

Template:Version windows portable

2014-05-31T15:39:50Z

Ennoborg: version update

3.4.8

Brief introduction to Git

2014-05-06T11:00:20Z

Ennoborg: /* Install Git on your system */ sudo added

The development source code of Gramps is stored in the Git repository at SourceForge.

;[http://sourceforge.net/p/gramps/source/ http://sourceforge.net/p/gramps/source/].

This helps synchronizing changes from various developers, tracking changes, managing releases, etc. If you are reading this, you probably want to do one of two things with Git: either download the latest source or the development version, or else upload your changes (if you have write access to the repository) or [[Brief_introduction_to_SVN#Making_a_patchfile|make a patchfile]] (if you don't have write access).

== Install Git on your system ==

* Debian/Ubuntu: <code>sudo apt-get install git</code>
* Fedora: <code>yum install git-core</code>
* Mac OS X (intel) Download git from here http://git-scm.com/download/mac.
* Mac OS X (PPC) Although the git download above is called 'git-1.8.4.2-intel-universal-snow-leopard.dmg', implying that this is a universal binary, in fact only the installer is universal, the binary to be installed in actually intel only. On a PPC you will need to build git manually. Follow the instructions here: http://jnorthr.wordpress.com/2013/03/29/building-a-git-client-1-8-2-on-apple-imac-ppc-osx-10-5-8/. I think you will also need some additional tools like 'msgfmt'. I don't think this is installed by the Apple development tool Xcode, but fortunately I have it either via fink which I installed some time ago, or via MacPorts which I installed more recently.

: Mac OS X (PPC) Eclipse. If you are using Eclipse on a PPC, then there may be missing components for installing the latest version of EGit, depending on your version of Eclipse. If you have the Helios version of Eclipse, then you will not be able to install the latest EGit because you will get ''requires 'org.eclipse.team.core 3.6.100' but it could not be found''. Installing EGit version 2.0 from http://download.eclipse.org/egit/updates-2.0 should work if you uncheck the EGit Import Support feature when selecting what to install. You will obviously lose the Import Support feature. See [http://stackoverflow.com/questions/15281273/dependency-fail-installing-egit-on-eclipse-indigo here]. You will probably need to do ''git config core.filemode false'' to get round [https://bugs.eclipse.org/bugs/show_bug.cgi?id=307560 this bug] as suggested [http://stackoverflow.com/questions/1257592/how-do-i-remove-files-saying-old-mode-100755-new-mode-100644-from-unstaged-cha here].

If you use Eclipse then will need to locally ignore the Eclipse files as suggested at 5.2.2 [http://www.vogella.com/tutorials/EclipseGit/article.html#d186251e250 here].

cd ~/
touch .gitignore
echo ".metadata" >> .gitignore
echo ".project" >> .gitignore
echo ".pydevproject" >> .gitignore
echo "windows" >> .gitignore

Git includes your name and email address in commits. To configure them, use the following commands:
git config --global user.name "John Smith"
git config --global user.email john@example.com

Git will automatically convert line endings for you. Use the following settings:
git config --global core.autocrlf true # Windows
git config --global core.autocrlf input # Linux/Mac

== Obtaining a copy of the Gramps repository ==

The description below is for a single working folder at ~/Gramps. An alternative approach for [[Brief_introduction_to_Git#Multiple_Working_Folders|Multiple Working Folders]] is described below.

To obtain a copy of the Gramps repository, type the following in the command line if you '''don't have a sourceforge account''': <code>
git clone <nowiki>git://git.code.sf.net/p/gramps/source</nowiki> Gramps</code>

You should see the downloading progress reported in your terminal.

If you have a SourceForge account, use ssh instead:<code>
git clone <nowiki>ssh://<username>@git.code.sf.net/p/gramps/source</nowiki> Gramps</code>

You will need a [http://sourceforge.net/p/forge/documentation/SSH%20Keys/ SSH Key] in order to authenticate using this method. '''Before you accept any host keys, make sure you [https://sourceforge.net/p/forge/documentation/Git/#how-to-clone-an-existing-repository verify the fingerprint]''' of git.code.sf.net.

== Basic Work Flow ==

The basic work flow after you've checked out the repository is update, develop, commit, update again, push.
To update the current branch, run

git pull --rebase

As a general rule ''always'' use <tt>git pull --rebase</tt> to avoid creating unnecessary merge commits. Note that one must have no uncommitted edits when running <tt>git pull</tt>.

The differences between "git pull" and git pull --rebase" is explained well [http://stackoverflow.com/a/3357174/2615612 here].

To review your changes before a commit, type:

git status

To commit your changes locally, use the following command:

git commit

Which will bring up the default $EDITOR to create a commit message. If you are fixing a bug, the first line of the commit message should be the bug number and title, otherwise a brief statement of purpose. Skip a line and describe what you did.

* All developers should read Gramps [[Committing policies]]

If the commit is a minor change that can be described entirely in the subject, you can instead use:

git commit -am "message describing the nature of the change"

Try to keep your commits digestible and understandable. A large changeset can be broken into several commits that "tell a story" about how the changeset moves the program from its old behavior to its new one.

To push your changes to the Gramps repository, you need to have cloned the Gramps source code with ssh, and have push access to the Gramps repository (the Gramps admins can give you this, [[Contact|Brian Matherly or Benny Malengier]]). First update again to make sure that you can fast-forward the repository, then push:

git pull --rebase
git push

Since uploading is a potentially dangerous operation, most people do not obtain write access to the git repository. In this case, create a new bug on the [http://bugs.gramps-project.org bug tracker] and attach a patch to it. See the [[Brief_introduction_to_Git#Making_a_patchfile|make a patchfile]] section for details.

If someone else has made changes that interfere with yours, you will get a conflict error when you pull. You will have to resolve that conflict and re-commit (you can use <tt>git commit --amend</tt> if it affects only the last ''unpushed'' commit) before git will push successfully.

:Also see: [[Getting started with Gramps Trunk]].

== Types of branches ==
When you clone the Gramps repository, a branch called ''master'' will be created for you. This contains the latest development version of Gramps. Gramps maintains different branches in several categories:

* ''master'' - There is only one ''master'' branch. All new feature and most bug-fix development happens in the ''master'' branch. New releases never come from the ''master'' branch.

* ''maintenance'' - There are many maintenance branches, though usually only one or two are active. A maintenance branch is created from the ''master'' branch when all the features for a release are complete. New features are not committed to maintenance branches. Releases only come from active maintenance branches; a branch is no longer active when no further releases are planned for it. Inactive branches should not have any changes committed to them. The purpose of maintenance branches is to allow the line of code to stabilize while new features are added in the ''master'' branch. In order to prevent regressions (fixed bugs reoccurring in later releases), it is a "best practice" to fix bugs on the master branch and then to backport them to the current maintenance branches.

* ''geps'' - These are meant for development of [[Portal:Enhancement_Proposals|Gramps Enhancement Proposals]]. Most of the time GEPS are developed in the ''master'' branch. Occassionally a GEP will require extensive reworking or long periods when the code base is ususable. In these cases a branch in ''geps'' can be used as a temporary development area. Once the hard work is done the change should be merged into the trunk and the ''geps'' branch should be removed. ''geps'' branches should follow the naming convention ''gep-<###>-<descriptive text>'' e.g. ''gep-013-server''. Please read the [[#Working with development branches]] section for help with managing these branches.

Tags are created for each Gramps release. The first two digits of the Gramps version number are reserved to indicate the maintenance branch the code came from. The last digit indicates the revision from that maintenance branch. For example, 3.0.4 would indicate the 5th release from the 3.0 branch (3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4).

Here is a hypothetical example:
Imagine that the current version of Gramps is 8.3.2. A new series of features has been added in the ''master'' branch and are ready for release. A new maintenance branch is created from the ''master'' branch named 8.4 (or possibly 9.0 depending on the nature of the new features). New features continue to be added in the ''master'' branch that will not be included in the 8.4 series of releases, but will be included in the 8.5 series. Bug fixes continue to occur in the 8.4 branch until the code is deemed worthy of release. At that time, a release is tagged from the 8.4 maintenance branch and named 8.4.0. Some time after the release of 8.4.0, some bugs are found and fixed in the 8.4 maintenance branch. Those bug fixes are released as 8.4.1.

== Stable version ==

There are several versions of the Gramps source code in Git. The development branch for small changes and bug fixes is ''maintenance/gramps{{stable_branch}}''.

By default, the remote server you cloned the Gramps repository from is called ''origin''.

To see a list of branches on the server, type:

git remote show origin

To create a local branch which tracks a branch on the server, use:

git checkout -b gramps40 origin/maintenance/gramps40

{{man warn|1=Warning|2=This sets the name of the local branch to "gramps40" (not "maintenance/gramps40"). This may cause problems when you come to "push" your changes back to the server, depending on the "push.default" configuration settings (see below). You can change the name of the local branch by "git branch -m old new" i.e.
git branch -m gramps40 maintenance/gramps40}}

This is known as a "tracking" branch.

To list the available branches, type:

git branch

The current branch is marked by an asterisk.

To switch to another branch, type:

git checkout <branch>

The following configuration option simplifies pushing a branch back to the server:

git config --global push.default upstream

You can then use:

git push

{{man warn|1=Warning|2=This will push commited changes from '''all''' local branches, not just the one that is currently checked-out. If you want to ensure that only one branch is pushed, then use:
git push origin gramps40:maintenance/gramps40}}

=== Where for bugs? ===

The [http://bugs.gramps-project.org bug tracker] has in the right top angle different projects. Choose project ''trunk'' and submit an issue.

=== Making a patchfile ===

If you do not have push access to the repository, you can make a patchfile with your changes. This is a text file which can then be sent by email to somebody, or posted/uploaded to the bug tracker (against a bug you are fixing or a feature request which you are solving for instance), etc...

These instructions tell how to make a patchfile against the ''master'' branch, so that your changes are added to the next major release of Gramps. (To make a patchfile against a branch the process is similar, with some slight changes.)

First create a new branch to work in:

git checkout -b fix

Then use your favorite editor to change whatever file(s) you want. Add the files you have changed to the staging area and commit them.

Obtain the latest changes from the server.

git checkout master
git pull --rebase

Next, rebase your fix again the ''master'' branch. This will ensure that your patch will apply cleanly.

git rebase master fix

This will leave you in the fix branch.

Finally, create a patchfile, using:

git format-patch master --stdout > fix.patch

You now have a patchfile that can be sent by email, or attached to a bug report. The patch can be applied using the 'git apply' command.

== Working with development branches ==

Creating branches with Git is quick and easy.

Here is a quick crib sheet:

=== Creating a branch ===

To create a branch from the ''master'' branch:

git checkout master
git branch gep-014-fab-feature

To make this branch available on the server use:

git push origin gep-014-fab-feature

=== Merging changes from the branch back into the ''master'' branch ===

When you are ready to merge your changes back into the ''master'' branch:

git checkout master
git merge gep-014-fab-feature
git push

=== Removing branches ===

It is important that branches are removed once they have been merged into the trunk or have been abandoned. To remove a branch:

git branch -d gep-014-fab-feature

To remove a branch from the server, use:

git push origin :gep-014-fab-feature

The developers reserve the right to remove branches that have been dormant for more than 1 year.

=== Applying a fix to another branch ===

If you write a fix for the master branch, you may need to also apply it to a maintenance branch.

To apply a commit from the a branch to a maintenance branch:
git checkout gramps40
git cherry-pick fix

Then you may have to fix things that could not be applied due to conflicts. The patch program would mark the conflicts with the <<<<<<, ======, and >>>>>> signs. You will then need to push your changes.

If you apply a small fix that applies cleanly to another branch, it can be done like this (assuming you've just committed the fix to master in a single commit):
git checkout gramps40
git diff master^ master | git apply
If `git apply' fails, nothing will be changed in the working copy, and you can try to resolve the conflicts by cherry-picking, or manually saving the diff result, using the "patch" program, and resolving the conflicts.

=== Workflow ===

Before switching to another branch it is useful to remove untracked files created by the build process. You can do this with the following command:

git clean -dxf

== Useful Tips ==

=== Getting help ===

Git has excellent man pages. You can view the manual page for a Git command, by using one of the following:

git help <verb>
git <verb> --help
man git-<verb>

For example, to get help on the 'git log' command, type:

git help log

=== Configuration settings ===

You can set your default editor with:

git config --global core.editor <editor>

To enable colored command line output, use:

git config --global color.ui auto

=== Some procedural recommendations ===

# Always do 'git pull --rebase' before pushing changes to the server. If necessary get advice about handling conflicts.
# Always do 'git status' and look for staged files that are unexpected or unintended. This is a *very important* sanity check.

;And here are a couple of incidental suggestions

* avoid grouping unrelated changes; better to divide into separate commits for the following reasons: a better log entry; easier troubleshooting/reverting. (and probably more).

* similar to above, it may be better to make small incremental changes than one big one (if possible). Interim changes should not introduce breakage, of course. For instance, if you change code in gramps/ and do associated translation changes in po/, you might want to commit the changes in po/ in a commit following the commit(s) with the changes in gramps/.

* logs are important -- please give some thought to the log message. All developers should read the [[Committing policies]].

== Multiple Working Folders ==

Using a single working folder as described above entails context switching when developing across multiple branches. For example:
* develop and test changes on the gramps40 branch,
* commit or stash the changes,
* clean to remove untracked files created by the development process,
* checkout the master 'branch',
* build (python setup.py build),
* cherry pick the changes from the gramps40 branch into the master 'branch',
* test and if necessary develop the changes to master,
* commit or stash the changes.

If the changes are all OK, then they can pushed to the SourceForge repository.

An alternative is to clone the SourceForge repository for each branch, but although git saves local disk space by using hard links for locally cloned repositories, keeping the local repositories in sync is complex.

The problem is well explained [http://finik.net/blog/2010/10/24/multiple-working-folders-with-single-git-repository here] as is the solution, which is to create copies of the working directories only. This is done by a script that is in the git 'contrib' directory [http://nuclearsquid.com/writings/git-new-workdir/ git-new-workdir].

Assuming that the directory structure would be:
~
+-Gramps
+-repository
+-.git
+- etc
+-gramps34
+-gramps40
+-master

The approach would be:
* checkout from the SourceForge repository (it doesn't much matter which branch you checkout as we are not going to use this branch directly):

git checkout -b Gramps/repository origin/master

* then create the various working copies:

git-new-workdir Gramps/repository ~/Gramps/gramps34 maintenance/gramps34
git-new-workdir Gramps/repository ~/Gramps/gramps40 maintenance/gramps40
git-new-workdir Gramps/repository ~/Gramps/master master

You will then need to build the source, but this only needs to be done once, and the 'clean' step is not needed. See [[Getting_started_with_Gramps_development#Run_Gramps_from_the_source| Run from source]] and [[Running_a_development_version_of_Gramps| running]] which describes the process for 'gramps 3.4 and before' as well as after. For example:

cd ~/Gramps/gramps40
python setup.py build

== Browse Git ==

An alternative to the command line tools to view the Git repository is the [{{Code Browser}} online interface].

==Send your contribution without rights to push==

Check it into Git if you obtained the [[#Obtaining_a_copy_of_the_Gramps_repository|permission to do push]].
Otherwise you can [http://sourceforge.net/p/gramps/source/fork fork] gramps repository with a SourceForge account and pull a [http://sourceforge.net/p/gramps/source/merge-requests/ merge request].

== git2cl ==

The Gramps project does not keep a ChangeLog file under source control. All change history is captured by git automatically when it is committed. A ChangeLog file is generated from the git commit logs before each release using [[Brief_introduction_to_SVN#How_to_use_git2cl|git2cl]]. Developers should take care to make useful commit log messages when committing changes to git. Please read the [[Committing policies]] for details.

=== How to use git2cl ===

Starting with Gramps 3.0.0, we no longer have a <tt>ChangeLog</tt> file.

Instead, the list of changes is generated automatically using the standard <tt>git2cl</tt> script.

Note that <tt>git2cl</tt> is not included in the base installation of Git. With a Debian-based distro such as Ubuntu, you can get <tt>git2cl</tt> as follows:

sudo apt-get install git2cl

There typically are two <tt>ChangeLog</tt> files needed for releases; one in the main directory, and one in the <tt>po</tt> directory. You can generate these files with the following commands:

git log gramps-4.0.1.. --pretty --numstat --summary --no-merges | git2cl > ChangeLog
git log gramps-4.0.1.. --pretty --numstat --summary --no-merges -- po | git2cl > po/ChangeLog

== External links ==

*[http://git-scm.com/ Git]
*[http://git-scm.com/book Git Book]
*[http://sourceforge.net/p/forge/documentation/SSH%20Keys/ SourceForge SSH Keys]
*[http://sourceforge.net/p/forge/documentation/SSH%20Key%20Fingerprints/ SourceForge SSH Key Fingerprints]

[[Category:Developers/General|B]]

Gramps 4.0 Wiki Manual - What's new?

2014-04-19T18:25:43Z

Ennoborg: /* New Look and Feel */ scroll bar

{{grampsmanualcopyright}}

{{man index|Gramps 4.0 Wiki Manual - Preface|Gramps 4.0 Wiki Manual - Getting started|4.0}}

{{languages|Gramps 4.0 Wiki Manual - What's new?}}

This section gives an overview of changes since Gramps version 3.4. These changes are also detailed later in this manual. Users of Gramps upgrading from version 3.4 are encouraged to review this section to be sure to take advantage of these new features when they start using version 4.0.

= Before you upgrade =

{{man warn| Warning |Creating an archive alone to safeguard your data might not be appropriate before upgrading. In the unlikely event that Gramps 4.0 corrupts your database, it could also corrupt the archive. An backup of your data as outlined in this section is recommended.}}

Before you upgrade, make sure your family tree data is secure. The best way to do this is:
# Start Gramps 3.4
# Open your family tree
# Back up the family tree to the ''gramps xml'' format or the ''gramps xml package'' format (the ''gramps xml package'' includes your photographs and other media files associated with your family tree data). Backup your tree via menu {{man menu|Family Trees->Make Backup...}}.
# Close this family tree and repeat the above steps for any other family trees you have
# Keep the resulting file(s) in a safe place

For more information, please review [[Gramps_4.0_Wiki_Manual_-_Manage_Family_Trees#Backing_up_a_Family_Tree|Backing up a Family Tree]].

After properly safeguarding your data, proceed to install Gramps 4.0. Using your operating system's regular installation process to do this will in most cases ensure that the new Gramps 4.0 installation will not clash with your older version of Gramps. However, it may be safer to uninstall Gramps 3.4 before installing Gramps 4.0, or make sure you install Gramps 4.0 in a different location. This is always necessary if you are installing from the source code. For more information on installing Gramps 4.0, please see [[Download|Downloading the latest Gramps]]

After you install Gramps 4.0, you can open your existing family trees and continue working. In case of problems (e.g., after a complete system upgrade), import the backup file(s) created above to recreate your family tree(s).

{{man warn| Warning |Once you open a family tree in a newer version of Gramps '''or''' using a newer operating system, you generally should not try to open that database using an older version again. As always, the ''gramps xml'' format is the format to use for the interchange of your data in such cases. There are tools to repair broken databases, but they are for expert users, so avoid needing them by following the steps above before you upgrade your OS or Gramps.}}

= Visible changes to the core =

The changes from Gramps 3.4 to Gramps 4.0 have been kept to a minimum as Gramps 4.0 is a technology upgrade release, not a user feature upgrade release. Family trees in 3.4 and 4.0 are the same, so (provided the same database software is used) a family tree can be opened in both versions without upgrade or downgrade needed.

Nevertheless, some changes are visible after the migration:

== The Dashboard ==
The Gramplet view has been renamed Dashboard. This to avoid an overload of the word Gramplet, and to make it more clear to new users what can be expected in this view

== New Look and Feel ==

Gramps now uses GTK 3 to create the interface, so you need to set a GTK theme with the GTK theme switcher that supports GTK 3. If Gramps looks ugly after installation, this is because you use an old GTK Theme. Try out some GTK 3 themes to see which one gives you a beautifull Gramps experience. See [http://gramps-project.org/2012/08/status-gtk-3-for-gramps-4-0/ status GTK 3 for Gramps 4.0].

=== Scroll bar behavior ===

You may notice that when you click above or below the scroll bar slider, the view does not page up or page down, like you were used to see in earlier Gramps versions, but jumps to where you clicked. If you don't like that, you can restore the old behavior by editing ~/.config/gtk-3.0/settings.ini

<pre>
[Settings]
gtk-primary-button-warps-slider = false
</pre>

You may have to create this file if it does not yet exist. Anything set here, will also affect other GTK 3 applications, like the file manager in Linux Mint.

== Data Model ==
There are no changes to the data model. A .gramps xml file generated by Gramps 3.4 is identical to one generated by Gramps 4.0

See [[Database_Formats#Detailed_Changes]] for more details on internal database.

==Navigator modes==

[[Image:Viewing_mode_selection.png|left|thumb|300px|Category navigator mode]]

[[Image:Drop-Down.png|right|thumb|300px|Drop-Down navigator mode]]

[[Image:Expander.png|left|thumb|300px|Expander navigator mode]]

If there is more than one navigator mode installed, you can choose the navigator mode with the drop down.
The navigator modes are "Category", "Drop-Down" and "Expander".

{{-}}

==New wizards, help and bug report dialogs==

[[Image:ExportAssistantStart-40.png|left|thumb|300px|Export Assistant: Start screen]]

[[Image:ExportAssistantChoose-40.png|right|thumb|300px|Export Assistant: Choose the output format screen]]

Exporter, Help and Bug report dialogs have been rewritten according to Gtk3 migration.

{{-}}

==Colors dialog==

[[File:EditPreferencesColors-40.png|right|thumb|350px|Color Preferences]]

A new section on Preferences dialog, which let you set the colors used for boxes in the graphical views.

{{-}}

== Plugins changes ==

The following are the changes made in the plugins: import/export, gramplets, views, reports, tools.

=== To Do Gramplets ===

[[Image:ToDoList-sidebar-gramplet-40.png|right|thumb|200px| To Do Gramplet]]

Objects and the Dashboard now have a To Do gramplet, listing all the notes which have been indicated as with Note Type To Do. New ''To Do'' notes can be created directly from the gramplet. See [[Gramps_4.0_Wiki_Manual_-_Gramplets#To_Do_Gramplet|ToDo Gramplet]] for more details.

{{-}}

== Views ==

* New columns on views (private records)

=== Fan Charts ===

[[Image:ChartsViewFanChart-40.png|left|thumb|300px| Fan Chart]]
[[Image:ChartsViewDescendantFanChart-40.png|right|thumb|300px| Fan Chart]]

In the Charts category (Previously called the Ancestry category), you will see two new core Charts: Fan Chart and Descendant Fan. These are two Charts that give you a good overview of a family tree. The Fan charts shows the principal parents of every individual. The Descendant Fan shows you all children, all their families, and then so on to see the ''entire'' descendant tree.

The Fan Charts are powerfull, use the {{man button|Configure}} button in the toolbar to investigate some posibilities:
* colored filtering via filter sidebar
* Gradient coloring to give extra information
* Print to output (pdf, printer) from the toolbar

{{-}}

== Tools ==

New tool for refreshing given name's statistics according to gender.

== Reports ==

* More languages switcher into reports (draw, graph and textual reports), enhancements and consistency on this feature, in relation with new [[#Locales handling|locales handling]].

===Book ===

* More friendly way for accessing to book report via command line.
* Improvements on OpenDocument and PDF file formats support

=== NarrativeWeb ===

A huge restructuring happened for narrative website (these changes might also happen in a point update on 3.4). It should overall be much more stable

= Under the hood changes =

Technical stuff

== Python 3 support ==

Gramps supports Python 2.7+ and Python 3.2+ starting from 4.0. We advise to use python 3.2 if possible. To support both versions, some code now runs slower on python 2.x.

== Code reogranization ==

Gramps now has completed the code reorganization, making the code structure of Gramps much more cleaner.

== Python based install ==

Gramps has deprecated the use of autotools for installation, and now uses a python based installation. As a user you are advised to use a package installer to install Gramps. Those installing from source code can do so now with the commands :

python setup.py build
python setup.py install

See the INSTALL and README file for details. This means that once you have installed gramps, you can use the code as a standard python module, eg:

from gramps.gen.lib.date import Date

to use the date computations as used by Gramps.

== Locales handling ==

See [[Internationalization]].

== Command Line Interface ==

See [[#Code reogranization|code reorganization]] and [[#Python based install|python based installation]].

* more translated typeout

= Further information =

More information.

== Roadmap ==

* [[Roadmap]]: [http://www.gramps-project.org/bugs/roadmap_page.php?version_id=34 4.0.0], [http://www.gramps-project.org/bugs/roadmap_page.php?version_id=25 trunk]

== Changelog ==

* [http://www.gramps-project.org/bugs/roadmap_page.php?version_id=34 roadmap 4.0.0], [http://www.gramps-project.org/bugs/changelog_page.php?version_id=34 changelog]

{{man index|Gramps 4.0 Wiki Manual - Preface|Gramps 4.0 Wiki Manual - Getting started|4.0}}

{{languages|Gramps 4.0 Wiki Manual - What's new?}}

[[Category:Documentation]]

Talk:Brief introduction to Git

2014-03-16T18:16:50Z

Ennoborg: stable version

To avoid confusion and another mess-up like we got earlier, I recommend that we change the checkout instruction for a maintenance branch from

:git checkout -b gramps40 origin/maintenance/gramps40

to

:git checkout maintenance/gramps40

which looks like having the same effect to me.
--[[User:Ennoborg|Ennoborg]] ([[User talk:Ennoborg|talk]]) 11:16, 16 March 2014 (MST)

Download

2014-02-12T22:36:10Z

Ennoborg: /* MS Windows */ exe

__NOTOC__
{{languages}}
== Linux ==

[[Image:Linux_220x261.png|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version ({{version}}) (advanced users only)]]</big>
{{-}}

== MS Windows ==

[[Image:windows_180x160.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO32}}/{{filename_windows_AIO32}}.exe Windows Installer (32-bit) {{version_windows_AIO32}}]
    
[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO64}}/{{filename_windows_AIO64}}.exe Windows Installer (64-bit) {{version_windows_AIO64}}]</big>

After download: double-click to install Gramps.

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

Alternative independent MS Windows version [[#3|[3]]].

Gramps 4.0.3, see [[Gramps_4.0_Wiki_Manual_-_What's_new%3F|what's new]], is also available. Download [http://sourceforge.net/projects/gramps/files/Stable/4.0.3/ here].

== Mac OS X ==

[[Image:macos_200x200.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]]. Read the [[Mac OS X:Application package|before installation]] instructions.

Mac OS X 10.5, 10.6, 10.7, 10.8, and 10.9     <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{filename_mac_intel}}.dmg Intel {{version_Mac}}]</big>
    
Mac OS X 10.5    <big>[http://sourceforge.net/projects/gramps/files/Stable/4.0.1/{{filename_mac_ppc}}.dmg Power PC 4.0.1]</big>

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next drag the Gramps application to your application folder and double-click to launch it [[#2|[2]]].

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

{{-}}

== BSD ==

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux and BSD distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version (advanced users only)]]</big>
{{-}}

== Live CD ==

[[Image:Download_link.png|150px|left|link=http://sourceforge.net/projects/gramps/files/OldFiles/3.2.5/lgenealogy-6.1-desktop-i386.iso]]
'''Linux live CD Demonstration''' [[Linux_Genealogy_CD#Obtaining_the_CD|Obtaining the CD]] (727 MB) [[Linux Genealogy CD|Linux Genealogy CD based on Ubuntu 10.10 (Maverick Meerkat)]]. Allows you to trial a pre-installed Gramps {{Version Linux Live CD}}, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn..). If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install [http://www.ubuntulinux.org/ Ubuntu 10.10] and Gramps from the CD anytime you like.
{{-}}
[[Image:Download_link.png|150px|left|link=http://cdimage.ubuntu.com/edubuntu/releases/13.04/release/]]
'''Edubuntu 13.04''' includes Gramps 3.4.0
{{-}}

== Linux and BSD distributions ==

Most linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| border="1" cellspacing="0"
|Distribution
|GUI pkg manager
|Current versions
|Notes
|-
|'''Linux Mint'''
|Software Manager
|Nadia: Gramps 3.4.0-1 Lisa: Gramps 3.3.1-1 Isadora: Gramps 3.2.0-1
|
|-
|''' Mageia '''
|
|
|
|-
|[[Image:Ubuntu_32x32.png]]''' Ubuntu '''
| Software Centre
|Quantal: Gramps 3.4.0-1
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]
|-
|[[Image:Fedora_32x32.png]]''' Fedora '''
|Add/Remove Software (Gnome) or Software Management (KDE)
|Fedora Rawhide: Gramps 3.4.3 Fedora 18: Gramps 3.4.2.
|
|-
|[[Image:Debianopenlogo-32.png]]''' [[Debian]] '''
|Add/Remove Software
|squeeze (old stable): Gramps 3.2.3 wheezy (stable): Gramps 3.4.0 jessie (testing): Gramps 3.4.0 [http://packages.debian.org/sid/gramps sid (unstable)]: Gramps 3.4.0
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[Image:Mandriva_32x32.png]]''' Mandriva '''
|Software Management in the 
Mandriva Linux Control Center
|
|Mandriva 2010.1: Gramps 3.3.1 Mandriva 2011: Gramps 3.2.6 See also [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Advanced_use:_Backports_and_candidate_updates backports] and contrib repository
|-
|[[Image:Redhat_32x32.png]]''' Redhat '''
|
|
|
|-
|''' openSUSE '''
|YaST ??
|openSUSE 12.3: Gramps 3.4.2
|[http://software.opensuse.org/package/gramps available versions]
|-
|'''Slackware'''
|
|Slackware 14.0: Gramps 3.4.2
|[http://pkgs.org/search/?keyword=gramps available versions]
|-
|'''NetBSD'''
|
|NetBSD: Gramps 3.4.3
|[http://pkgsrc.se/databases/gramps3 available versions]
|-
|'''FreeBSD'''
|
|FreeBSD: Gramps 3.3.0
|[http://portsmon.freebsd.org/portoverview.py?category=science&portname=gramps available versions]
|-
|'''PC-BSD'''
|
|PC-BSD: Gramps 3.3.0
|
|}

{{-}}

== Linux: Install latest version ==

If your distribution doesn't ship with Gramps or you wish to install a different version than it ships with, you could try to install the latest version of Gramps manually. Instructions are given below for a number of distributions.

{{man warn|1=Warning|2=This should only be attempted by experienced users, and after you have backed up your Family Tree.

The version of Gramps that has been included in your distribution will have been tested to work with the components in that distribution. If you try to install a different version of Gramps there is a possibility that the components needed for the new version of Gramps are not available for your distribution, or they are available, but don't work properly. You might not discover that there is a problem till you have already done some work with the new version of Gramps.

If you already have Gramps installed, and you are only making a 'point' upgrade (i.e. from Gramps x.y.z to x.y.z+1, e.g. from 3.4.3 to 3.4.4), then it is likely but not certain that Gramps will continue to work. However, if the change is much greater, especially if it is a major version change (e.g. from 2.y.z to 3.y.z), then the danger that it does not work properly is much greater.}}

[[Image:Debianopenlogo-32.png]]'''[[Debian]]''' and [[Image:Ubuntu_32x32.png]]''' Ubuntu ''' [http://sourceforge.net/projects/gramps/files/Stable/{{version}} Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved (change the filename to match the one you downloaded).

sudo dpkg -i gramps_{{version}}-1_all.deb

For other distributions, [[Image:Download_link.png|150px|link=http://sourceforge.net/projects/gramps/files/Stable/{{version}}/gramps-{{version}}.tar.gz]] the source and follow the instructions for [[Linux:Build from source]]

== Notes ==

[1]
Backup to Gramps XML. You will find backup in the Family Tree menu of recent Gramps versions, otherwise use export in the same menu but '''uncheck privacy options''' in the Exporter Assistant in order to export all data

[2]
Alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.

[3]
An alternative independent version is [http://sourceforge.net/projects/portableapps/files/Gramps%20Portable/ GrampsPortable_{{version_windows_portable}}.paf.exe] (20.3 MB)
[http://portableapps.com/apps/education/gramps_portable Portable Gramps from PortableApps.com] includes all dependencies required for Windows. ''Note:You can install it on C: then to run Gramps type C:\PortableApps\GrampsPortable\GrampsPortable.exe (Or the path you installed it to) or make a shortcut to that file on your desktop or start-menu.'' By Bart.S - '''[http://portableapps.com/blog/84601 Please report issues to the author.]''' (2012-09-07)

[[Category:Documentation]]

Download

2014-01-30T19:17:29Z

Ennoborg: 4.03 as ZIP

__NOTOC__
{{languages}}
== Linux ==

[[Image:Linux_220x261.png|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version ({{version}}) (advanced users only)]]</big>
{{-}}

== MS Windows ==

[[Image:windows_180x160.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO32}}/{{filename_windows_AIO32}}.exe Windows Installer (32-bit) {{version_windows_AIO32}}]
    
[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO64}}/{{filename_windows_AIO64}}.exe Windows Installer (64-bit) {{version_windows_AIO64}}]</big>

After download: double-click to install Gramps.

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

Alternative independent MS Windows version [[#3|[3]]].

Gramps 4.0.3, see [[Gramps_4.0_Wiki_Manual_-_What's_new%3F|what's new]], is available as a ZIP file, no installer yet. Download [http://sourceforge.net/projects/gramps/files/Stable/4.0.3/ here].

== Mac OS X ==

[[Image:macos_200x200.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]]. Read the [[Mac OS X:Application package|before installation]] instructions.

Mac OS X 10.5, 10.6, 10.7, 10.8, and 10.9     <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{filename_mac_intel}}.dmg Intel {{version_Mac}}]</big>
    
Mac OS X 10.5    <big>[http://sourceforge.net/projects/gramps/files/Stable/4.0.1/{{filename_mac_ppc}}.dmg Power PC 4.0.1]</big>

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next drag the Gramps application to your application folder and double-click to launch it [[#2|[2]]].

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

{{-}}

== BSD ==

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux and BSD distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version (advanced users only)]]</big>
{{-}}

== Live CD ==

[[Image:Download_link.png|150px|left|link=http://sourceforge.net/projects/gramps/files/OldFiles/3.2.5/lgenealogy-6.1-desktop-i386.iso]]
'''Linux live CD Demonstration''' [[Linux_Genealogy_CD#Obtaining_the_CD|Obtaining the CD]] (727 MB) [[Linux Genealogy CD|Linux Genealogy CD based on Ubuntu 10.10 (Maverick Meerkat)]]. Allows you to trial a pre-installed Gramps {{Version Linux Live CD}}, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn..). If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install [http://www.ubuntulinux.org/ Ubuntu 10.10] and Gramps from the CD anytime you like.
{{-}}
[[Image:Download_link.png|150px|left|link=http://cdimage.ubuntu.com/edubuntu/releases/13.04/release/]]
'''Edubuntu 13.04''' includes Gramps 3.4.0
{{-}}

== Linux and BSD distributions ==

Most linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| border="1" cellspacing="0"
|Distribution
|GUI pkg manager
|Current versions
|Notes
|-
|'''Linux Mint'''
|Software Manager
|Nadia: Gramps 3.4.0-1 Lisa: Gramps 3.3.1-1 Isadora: Gramps 3.2.0-1
|
|-
|''' Mageia '''
|
|
|
|-
|[[Image:Ubuntu_32x32.png]]''' Ubuntu '''
| Software Centre
|Quantal: Gramps 3.4.0-1
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]
|-
|[[Image:Fedora_32x32.png]]''' Fedora '''
|Add/Remove Software (Gnome) or Software Management (KDE)
|Fedora Rawhide: Gramps 3.4.3 Fedora 18: Gramps 3.4.2.
|
|-
|[[Image:Debianopenlogo-32.png]]''' [[Debian]] '''
|Add/Remove Software
|squeeze (old stable): Gramps 3.2.3 wheezy (stable): Gramps 3.4.0 jessie (testing): Gramps 3.4.0 [http://packages.debian.org/sid/gramps sid (unstable)]: Gramps 3.4.0
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[Image:Mandriva_32x32.png]]''' Mandriva '''
|Software Management in the 
Mandriva Linux Control Center
|
|Mandriva 2010.1: Gramps 3.3.1 Mandriva 2011: Gramps 3.2.6 See also [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Advanced_use:_Backports_and_candidate_updates backports] and contrib repository
|-
|[[Image:Redhat_32x32.png]]''' Redhat '''
|
|
|
|-
|''' openSUSE '''
|YaST ??
|openSUSE 12.3: Gramps 3.4.2
|[http://software.opensuse.org/package/gramps available versions]
|-
|'''Slackware'''
|
|Slackware 14.0: Gramps 3.4.2
|[http://pkgs.org/search/?keyword=gramps available versions]
|-
|'''NetBSD'''
|
|NetBSD: Gramps 3.4.3
|[http://pkgsrc.se/databases/gramps3 available versions]
|-
|'''FreeBSD'''
|
|FreeBSD: Gramps 3.3.0
|[http://portsmon.freebsd.org/portoverview.py?category=science&portname=gramps available versions]
|-
|'''PC-BSD'''
|
|PC-BSD: Gramps 3.3.0
|
|}

{{-}}

== Linux: Install latest version ==

If your distribution doesn't ship with Gramps or you wish to install a different version than it ships with, you could try to install the latest version of Gramps manually. Instructions are given below for a number of distributions.

{{man warn|1=Warning|2=This should only be attempted by experienced users, and after you have backed up your Family Tree.

The version of Gramps that has been included in your distribution will have been tested to work with the components in that distribution. If you try to install a different version of Gramps there is a possibility that the components needed for the new version of Gramps are not available for your distribution, or they are available, but don't work properly. You might not discover that there is a problem till you have already done some work with the new version of Gramps.

If you already have Gramps installed, and you are only making a 'point' upgrade (i.e. from Gramps x.y.z to x.y.z+1, e.g. from 3.4.3 to 3.4.4), then it is likely but not certain that Gramps will continue to work. However, if the change is much greater, especially if it is a major version change (e.g. from 2.y.z to 3.y.z), then the danger that it does not work properly is much greater.}}

[[Image:Debianopenlogo-32.png]]'''[[Debian]]''' and [[Image:Ubuntu_32x32.png]]''' Ubuntu ''' [http://sourceforge.net/projects/gramps/files/Stable/{{version}} Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved (change the filename to match the one you downloaded).

sudo dpkg -i gramps_{{version}}-1_all.deb

For other distributions, [[Image:Download_link.png|150px|link=http://sourceforge.net/projects/gramps/files/Stable/{{version}}/gramps-{{version}}.tar.gz]] the source and follow the instructions for [[Linux:Build from source]]

== Notes ==

[1]
Backup to Gramps XML. You will find backup in the Family Tree menu of recent Gramps versions, otherwise use export in the same menu but '''uncheck privacy options''' in the Exporter Assistant in order to export all data

[2]
Alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.

[3]
An alternative independent version is [http://sourceforge.net/projects/portableapps/files/Gramps%20Portable/ GrampsPortable_{{version_windows_portable}}.paf.exe] (20.3 MB)
[http://portableapps.com/apps/education/gramps_portable Portable Gramps from PortableApps.com] includes all dependencies required for Windows. ''Note:You can install it on C: then to run Gramps type C:\PortableApps\GrampsPortable\GrampsPortable.exe (Or the path you installed it to) or make a shortcut to that file on your desktop or start-menu.'' By Bart.S - '''[http://portableapps.com/blog/84601 Please report issues to the author.]''' (2012-09-07)

[[Category:Documentation]]

Template:Version windows AIO64

2014-01-30T19:01:42Z

Ennoborg: 3.4.7

3.4.7

Template:Version windows AIO32

2014-01-30T19:00:44Z

Ennoborg: 3.4.7

3.4.7

Download

2014-01-09T12:22:08Z

Ennoborg: /* MS Windows */ what's new link added

__NOTOC__
{{languages}}
== Linux ==

[[Image:Linux_220x261.png|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version ({{version}}) (advanced users only)]]</big>
{{-}}

== MS Windows ==

[[Image:windows_180x160.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO32}}/{{filename_windows_AIO32}}.exe Windows Installer (32-bit) {{version_windows_AIO32}}]
    
[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO64}}/{{filename_windows_AIO64}}.exe Windows Installer (64-bit) {{version_windows_AIO64}}]</big>

After download: double-click to install Gramps.

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

Alternative independent MS Windows version [[#3|[3]]].

We have Windows versions of Gramps 4.0.2 too, see [[Gramps_4.0_Wiki_Manual_-_What's_new%3F|what's new]]. They are not perfect yet, but they do offer some improvements over 3.4.6, which you can read about on the [http://sourceforge.net/projects/gramps/files/Stable/4.0.2/ sourceforge download page]. We welcome feedback about these version and their installation, so if you use any, and like them, or not, please let us know [[Contact|here]].

== Mac OS X ==

[[Image:macos_200x200.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]]. Read the [[Mac OS X:Application package|before installation]] instructions.

Mac OS X 10.5, 10.6, 10.7, 10.8, and 10.9     <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{filename_mac_intel}}.dmg Intel {{version_Mac}}]</big>
    
Mac OS X 10.5    <big>[http://sourceforge.net/projects/gramps/files/Stable/4.0.1/{{filename_mac_ppc}}.dmg Power PC 4.0.1]</big>

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next drag the Gramps application to your application folder and double-click to launch it [[#2|[2]]].

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

{{-}}

== BSD ==

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux and BSD distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version (advanced users only)]]</big>
{{-}}

== Live CD ==

[[Image:Download_link.png|150px|left|link=http://sourceforge.net/projects/gramps/files/OldFiles/3.2.5/lgenealogy-6.1-desktop-i386.iso]]
'''Linux live CD Demonstration''' [[Linux_Genealogy_CD#Obtaining_the_CD|Obtaining the CD]] (727 MB) [[Linux Genealogy CD|Linux Genealogy CD based on Ubuntu 10.10 (Maverick Meerkat)]]. Allows you to trial a pre-installed Gramps {{Version Linux Live CD}}, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn..). If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install [http://www.ubuntulinux.org/ Ubuntu 10.10] and Gramps from the CD anytime you like.
{{-}}
[[Image:Download_link.png|150px|left|link=http://cdimage.ubuntu.com/edubuntu/releases/13.04/release/]]
'''Edubuntu 13.04''' includes Gramps 3.4.0
{{-}}

== Linux and BSD distributions ==

Most linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| border="1" cellspacing="0"
|Distribution
|GUI pkg manager
|Current versions
|Notes
|-
|'''Linux Mint'''
|Software Manager
|Nadia: Gramps 3.4.0-1 Lisa: Gramps 3.3.1-1 Isadora: Gramps 3.2.0-1
|
|-
|''' Mageia '''
|
|
|
|-
|[[Image:Ubuntu_32x32.png]]''' Ubuntu '''
| Software Centre
|Quantal: Gramps 3.4.0-1
|[http://packages.ubuntu.com/quantal/gramps available versions]
|-
|[[Image:Fedora_32x32.png]]''' Fedora '''
|Add/Remove Software (Gnome) or Software Management (KDE)
|Fedora Rawhide: Gramps 3.4.3 Fedora 18: Gramps 3.4.2.
|
|-
|[[Image:Debianopenlogo-32.png]]''' [[Debian]] '''
|Add/Remove Software
|squeeze (old stable): Gramps 3.2.3 wheezy (stable): Gramps 3.4.0 jessie (testing): Gramps 3.4.0 [http://packages.debian.org/sid/gramps sid (unstable)]: Gramps 3.4.0
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[Image:Mandriva_32x32.png]]''' Mandriva '''
|Software Management in the 
Mandriva Linux Control Center
|
|Mandriva 2010.1: Gramps 3.3.1 Mandriva 2011: Gramps 3.2.6 See also [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Advanced_use:_Backports_and_candidate_updates backports] and contrib repository
|-
|[[Image:Redhat_32x32.png]]''' Redhat '''
|
|
|
|-
|''' openSUSE '''
|YaST ??
|openSUSE 12.3: Gramps 3.4.2
|[http://software.opensuse.org/package/gramps available versions]
|-
|'''Slackware'''
|
|Slackware 14.0: Gramps 3.4.2
|[http://pkgs.org/search/?keyword=gramps available versions]
|-
|'''NetBSD'''
|
|NetBSD: Gramps 3.4.3
|[http://pkgsrc.se/databases/gramps3 available versions]
|-
|'''FreeBSD'''
|
|FreeBSD: Gramps 3.3.0
|[http://portsmon.freebsd.org/portoverview.py?category=science&portname=gramps available versions]
|-
|'''PC-BSD'''
|
|PC-BSD: Gramps 3.3.0
|
|}

{{-}}

== Linux: Install latest version ==

If your distribution doesn't ship with Gramps or you wish to install a different version than it ships with, you could try to install the latest version of Gramps manually. Instructions are given below for a number of distributions.

{{man warn|1=Warning|2=This should only be attempted by experienced users, and after you have backed up your Family Tree.

The version of Gramps that has been included in your distribution will have been tested to work with the components in that distribution. If you try to install a different version of Gramps there is a possibility that the components needed for the new version of Gramps are not available for your distribution, or they are available, but don't work properly. You might not discover that there is a problem till you have already done some work with the new version of Gramps.

If you already have Gramps installed, and you are only making a 'point' upgrade (i.e. from Gramps x.y.z to x.y.z+1, e.g. from 3.4.3 to 3.4.4), then it is likely but not certain that Gramps will continue to work. However, if the change is much greater, especially if it is a major version change (e.g. from 2.y.z to 3.y.z), then the danger that it does not work properly is much greater.}}

[[Image:Debianopenlogo-32.png]]'''[[Debian]]''' and [[Image:Ubuntu_32x32.png]]''' Ubuntu ''' [http://sourceforge.net/projects/gramps/files/Stable/{{version}}/gramps_{{version}}_all.deb Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved (change the filename to match the one you downloaded).

sudo dpkg -i gramps_3.4.6-1_all.deb

For other distributions, [[Image:Download_link.png|150px|link=http://sourceforge.net/projects/gramps/files/Stable/{{version}}/gramps-{{version}}.tar.gz]] the source and follow the instructions for [[Linux:Build from source]]

== Notes ==

[1]
Backup to Gramps XML. You will find backup in the Family Tree menu of recent Gramps versions, otherwise use export in the same menu but '''uncheck privacy options''' in the Exporter Assistant in order to export all data

[2]
Alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.

[3]
An alternative independent version is [http://sourceforge.net/projects/portableapps/files/Gramps%20Portable/ GrampsPortable_{{version_windows_portable}}.paf.exe] (20.3 MB)
[http://portableapps.com/apps/education/gramps_portable Portable Gramps from PortableApps.com] includes all dependencies required for Windows. ''Note:You can install it on C: then to run Gramps type C:\PortableApps\GrampsPortable\GrampsPortable.exe (Or the path you installed it to) or make a shortcut to that file on your desktop or start-menu.'' By Bart.S - '''[http://portableapps.com/blog/84601 Please report issues to the author.]''' (2012-09-07)

[[Category:Documentation]]

Download

2014-01-08T13:22:16Z

Ennoborg: /* MS Windows */

__NOTOC__
{{languages}}
== Linux ==

[[Image:Linux_220x261.png|128px|left]]

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version ({{version}}) (advanced users only)]]</big>
{{-}}

== MS Windows ==

[[Image:windows_180x160.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO32}}/{{filename_windows_AIO32}}.exe Windows Installer (32-bit) {{version_windows_AIO32}}]
    
[http://sourceforge.net/projects/gramps/files/Stable/{{version_windows_AIO64}}/{{filename_windows_AIO64}}.exe Windows Installer (64-bit) {{version_windows_AIO64}}]</big>

After download: double-click to install Gramps.

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

Alternative independent MS Windows version [[#3|[3]]].

We have Windows versions of Gramps 4.0.2 too. They are not perfect yet, but they do offer some improvements over 3.4.6, which you can read about on the [http://sourceforge.net/projects/gramps/files/Stable/4.0.2/ sourceforge download page]. We welcome feedback about these version and their installation, so if you use any, and like them, or not, please let us know [[Contact|here]].

== Mac OS X ==

[[Image:macos_200x200.png|128px|left]]

Before download: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]]. Read the [[Mac OS X:Application package|before installation]] instructions.

Mac OS X 10.5, 10.6, 10.7, 10.8, and 10.9     <big>[http://sourceforge.net/projects/gramps/files/Stable/{{version_Mac}}/{{filename_mac_intel}}.dmg Intel {{version_Mac}}]</big>
    
Mac OS X 10.5    <big>[http://sourceforge.net/projects/gramps/files/Stable/4.0.1/{{filename_mac_ppc}}.dmg Power PC 4.0.1]</big>

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next drag the Gramps application to your application folder and double-click to launch it [[#2|[2]]].

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. However if this fails for any reason, '''Create''' a new Family Tree and '''Import''' the back-up into this new Tree.

{{-}}

== BSD ==

Before upgrading your distribution: Use your '''old version of Gramps''' to [[How_to_make_a_backup#GRAMPS_version_3.3_and_later|backup]] your Family Trees [[#1|[1]]].

<big>
[[Download#Linux and BSD distributions|via Distributions]]
    
[[Download#Linux:_Install_latest_version|Latest version (advanced users only)]]</big>
{{-}}

== Live CD ==

[[Image:Download_link.png|150px|left|link=http://sourceforge.net/projects/gramps/files/OldFiles/3.2.5/lgenealogy-6.1-desktop-i386.iso]]
'''Linux live CD Demonstration''' [[Linux_Genealogy_CD#Obtaining_the_CD|Obtaining the CD]] (727 MB) [[Linux Genealogy CD|Linux Genealogy CD based on Ubuntu 10.10 (Maverick Meerkat)]]. Allows you to trial a pre-installed Gramps {{Version Linux Live CD}}, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn..). If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install [http://www.ubuntulinux.org/ Ubuntu 10.10] and Gramps from the CD anytime you like.
{{-}}
[[Image:Download_link.png|150px|left|link=http://cdimage.ubuntu.com/edubuntu/releases/13.04/release/]]
'''Edubuntu 13.04''' includes Gramps 3.4.0
{{-}}

== Linux and BSD distributions ==

Most linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| border="1" cellspacing="0"
|Distribution
|GUI pkg manager
|Current versions
|Notes
|-
|'''Linux Mint'''
|Software Manager
|Nadia: Gramps 3.4.0-1 Lisa: Gramps 3.3.1-1 Isadora: Gramps 3.2.0-1
|
|-
|''' Mageia '''
|
|
|
|-
|[[Image:Ubuntu_32x32.png]]''' Ubuntu '''
| Software Centre
|Quantal: Gramps 3.4.0-1
|[http://packages.ubuntu.com/quantal/gramps available versions]
|-
|[[Image:Fedora_32x32.png]]''' Fedora '''
|Add/Remove Software (Gnome) or Software Management (KDE)
|Fedora Rawhide: Gramps 3.4.3 Fedora 18: Gramps 3.4.2.
|
|-
|[[Image:Debianopenlogo-32.png]]''' [[Debian]] '''
|Add/Remove Software
|squeeze (old stable): Gramps 3.2.3 wheezy (stable): Gramps 3.4.0 jessie (testing): Gramps 3.4.0 [http://packages.debian.org/sid/gramps sid (unstable)]: Gramps 3.4.0
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[Image:Mandriva_32x32.png]]''' Mandriva '''
|Software Management in the 
Mandriva Linux Control Center
|
|Mandriva 2010.1: Gramps 3.3.1 Mandriva 2011: Gramps 3.2.6 See also [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Advanced_use:_Backports_and_candidate_updates backports] and contrib repository
|-
|[[Image:Redhat_32x32.png]]''' Redhat '''
|
|
|
|-
|''' openSUSE '''
|YaST ??
|openSUSE 12.3: Gramps 3.4.2
|[http://software.opensuse.org/package/gramps available versions]
|-
|'''Slackware'''
|
|Slackware 14.0: Gramps 3.4.2
|[http://pkgs.org/search/?keyword=gramps available versions]
|-
|'''NetBSD'''
|
|NetBSD: Gramps 3.4.3
|[http://pkgsrc.se/databases/gramps3 available versions]
|-
|'''FreeBSD'''
|
|FreeBSD: Gramps 3.3.0
|[http://portsmon.freebsd.org/portoverview.py?category=science&portname=gramps available versions]
|-
|'''PC-BSD'''
|
|PC-BSD: Gramps 3.3.0
|
|}

{{-}}

== Linux: Install latest version ==

If your distribution doesn't ship with Gramps or you wish to install a different version than it ships with, you could try to install the latest version of Gramps manually. Instructions are given below for a number of distributions.

{{man warn|1=Warning|2=This should only be attempted by experienced users, and after you have backed up your Family Tree.

The version of Gramps that has been included in your distribution will have been tested to work with the components in that distribution. If you try to install a different version of Gramps there is a possibility that the components needed for the new version of Gramps are not available for your distribution, or they are available, but don't work properly. You might not discover that there is a problem till you have already done some work with the new version of Gramps.

If you already have Gramps installed, and you are only making a 'point' upgrade (i.e. from Gramps x.y.z to x.y.z+1, e.g. from 3.4.3 to 3.4.4), then it is likely but not certain that Gramps will continue to work. However, if the change is much greater, especially if it is a major version change (e.g. from 2.y.z to 3.y.z), then the danger that it does not work properly is much greater.}}

[[Image:Debianopenlogo-32.png]]'''[[Debian]]''' and [[Image:Ubuntu_32x32.png]]''' Ubuntu ''' [http://sourceforge.net/projects/gramps/files/Stable/{{version}}/gramps_{{version}}_all.deb Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved (change the filename to match the one you downloaded).

sudo dpkg -i gramps_3.4.6-1_all.deb

For other distributions, [[Image:Download_link.png|150px|link=http://sourceforge.net/projects/gramps/files/Stable/{{version}}/gramps-{{version}}.tar.gz]] the source and follow the instructions for [[Linux:Build from source]]

== Notes ==

[1]
Backup to Gramps XML. You will find backup in the Family Tree menu of recent Gramps versions, otherwise use export in the same menu but '''uncheck privacy options''' in the Exporter Assistant in order to export all data

[2]
Alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.

[3]
An alternative independent version is [http://sourceforge.net/projects/portableapps/files/Gramps%20Portable/ GrampsPortable_{{version_windows_portable}}.paf.exe] (20.3 MB)
[http://portableapps.com/apps/education/gramps_portable Portable Gramps from PortableApps.com] includes all dependencies required for Windows. ''Note:You can install it on C: then to run Gramps type C:\PortableApps\GrampsPortable\GrampsPortable.exe (Or the path you installed it to) or make a shortcut to that file on your desktop or start-menu.'' By Bart.S - '''[http://portableapps.com/blog/84601 Please report issues to the author.]''' (2012-09-07)

[[Category:Documentation]]