Es:Manual Wiki para Gramps 3.4 - Novedades

From Gramps
Revision as of 21:39, 28 August 2012 by Jsanchez (talk | contribs) (Before you upgrade: Initial translation)
Jump to: navigation, search
Gnome-important.png Special copyright notice: All edits to this page need to be under two different copyright licenses:

These licenses allow the Gramps project to maximally use this wiki manual as free content in future Gramps versions. If you do not agree with this dual license, then do not edit this page. You may only link to other pages within the wiki which fall only under the GFDL license via external links (using the syntax: []), not via internal links.
Also, only use the known conventions

Previous Index Next

Esta sección da una visión general de los cambios introducidos desde la versión 3.3 de Gramps. Estos cambios se detallan también más adelante en este manual. Se recomienda a los usuarios de Gramps 3.3 la lectura de esta sección para asegurar que puedan aprovechares de estas nuevas características.

Antes de actualizar


Crear una copia archivada solamente puede no ser suficiente para proteger los datos antes de la actualización. En el improbable caso de que Gramps 3.4 corrompiera su base de datos, pordría también corromper la copia archivada. Se recomienda una exportación como s describe en esta sección.

Antes de actualizar, asegúrese de que los datos de su árbol genealógico están a salvo. La mejor forma de hacerlo es:

  1. Arrancar Gramps 3.3
  2. Abrir su árbol genealógico
  3. Exportar el árbol genealógico al formato XML Gramps o al formato paquete XML Gramps (que incluye sus fotografías y otros objetos audiovisuales asociados a los datos de su árbol genealógico). Exporte su árbol mediante el menú Árboles genealógicos->Hacer copia de seguridad....
  4. Cerrar este árbol genealógico y repetir los pasos anteriores para cualquier otro árbol genealógico que tenga
  5. Guarde los archivos resultantes en un lugar seguro

Para más información, consulte Hacer una copia de seguridad de un árbol genealógico.

Tras salvaguardar apropiadamente sus datos, proceda a instalar Gramps 3.4. Utilice el proceso de instalación normal de su sistema operativo para hacerlo. También es preferibe desinstalar Gramps 3.3 antes de instalar Gramps 3.4 o asegurarse de instalar Gramps 3.4 en un lugar diferente.

Tras instalar Gramps 3.4, puede abrir sus árboles genealógicos existentes y continuar trabajando. En caso de problemas (p.ej., tras una actualización total del sistema), utilice los archivos de copia de seguridad creados antes para volver a volver a crear los árboles genealógicos..


Una vez abra un árbol genealógico en una versión más moderna de o usando un sistema operativo más nuevo, no debe en general intentar abrir ese archivo usando versiones más antiguas. Como siempre, el formato XML Gramps es el formato a utilizar para el intercambio de sus datos en tales casos. Existen herramientas para reparar bases de datos dañadas, pero sólo están orientadas a usuarios expertos, así que evite verse en la situación de necesitar utilizarlas siguiendo los pasos anteriores antes de actualizar su sistema operativo o Gramps.

Visible changes to the core

Changes visible after the migration: interface, data.

Citations (formerly Source References)

The principal changes are that:

  • Citations can be shared; and,
  • Citations can have media object attached to them.

It is possible to use Gramps version 3.4 in the same way as Gramps version 3.3, if you do not want or need to take advantage of the new features:

  • The Sources view looks almost the same as the old Sources view (but with the addition of a disclosure triangle for sources that have citations),
  • The buttons for adding sources to information like events are the same as before,
  • The selector for choosing an existing source looks the same (although with the addition of disclosure triangles to allow a citation to be chosen),
  • The new 'Citation' editor looks (and behaves) almost exactly the same as the old 'Source Reference Editor',

Only if a user particularly wants to share citations between objects do they need to be aware of the change. The change is also intended to be entirely compatible with GEDCOM.

See GEPS_023:_Storing_data_from_large_sources for an explanation of the rationale behind the new features.

If you have an existing Gramps database which you are upgrading to Gramps 3.4, after the upgrade process, Gramps will suggest that you might like to merge citations that are the same and refer to the same source. Unless you have specifically recorded different information (for example different notes) on old Source References that are the same, you should probably use the Tools->Family Tree Processing->Merge Citations... tool.

When you start using Gramps, if you want to share a citation, then you would click on the Add an existing citation or source and in the Select Source or Citation dialogue, you would select the appropriate source and then citation. Clicking OK would take you to the Citation editor, but you will probably just click OK, because the citation and source are both shared.


  • The citation editor has changed very little from the former Source Reference Editor:
Figure 1.1

As shown, the main change is that the Citation can have a Gallery of images, Data fields, and also has (back-)references because it is a separate primary object.

  • Improvements on image selection feature.
  • New 'Default family relationship' option value (Preferences)
  • Add some accelerator keys on toogle buttons without labels. See also #Accessibility.

GEDCOM import

GEDCOM import error/warnings report. bug tracker: 5599 - provide a report of GEDCOM errors and warnings after import to show the user what information has not been imported.

Fig 1.2 Import report

The report (shown above) details most of the lines that were either ignored or could not be understood. The contents of the line (or lines where there are continuation lines) are also shown. In some cases, the lines may not be exactly what is contained in the input GEDCOM file, because the line is reconstructed following some processing.

In addition to this report, some improvements have been made to GEDCOM import to process more of the input file. Some data has been imported into Gramps data elements even when they are not exactly the same as the GEDCOM data elements. Because the format of GEDCOM, and the format that Gramps uses are different, there are inevitably some pieces of data that cannot be imported.

More details of the mapping from GEDCOM to Gramps are now provided. See GEDCOM import.

Plugins changes

Everything about the plugins: import/export, gramplets, views, reports, tools.


  • Citations support on file formats
  • Improvements on Gedcom file format support


  • output file formats

Improvements : RTF, ODF, LaTeX, cairo (PDF, Print...)

  • support image sections on textual reports
  • Citation support and source review (NarrativeWeb report, etc ...)
  • Paper options

Consistency rules on paper values, orientation and file format (options set by user)


  • Improvements
  • Alphabetical Index and Table Of Contents (TOC) features on book report

Detailed reports

  • Improvements, bug fix, consistency on age calculation, etc ...


  • Media gallery, thumbnails
  • hyperlink menu for screen readers and braille writers


The sources view has been enhanced with a new tree view (Fig 1.3) that also shows citations below the source, in addition to the existing flat view (Fig 1.4)

Fig. 1.3 Sources (Citation Tree) view
Fig. 1.4 Sources view

There is also a new Citations view (Fig 1.5).

Fig. 1.5 Citation view

  • Size adjustments on Main, Navigation, Bottom and Side bars


  • A new tool for merging our citation records: MergeCitations.
  • Review on some Repair Family Tree tools

Under the hood changes

Technical stuff (gui/gen).


  • Better ATK support

Addons manager

  • Review, improvements

Command Line Interface

  • Arguments/flags

Improvements, consistency, optional translation

Gramps XML file format and database

  • Citations support
  • Gramps XML is now idempotent[1].
  • Exporter does not change records order any more, making it easier to look at differences between versions/revisions.

User classes

Reports and tools have user classes. These classes provide a means to interact with the user in an abstract way. These classes should be overridden by each respective user interface to provide the appropriate interaction (eg. dialogs for GTK, promts for CLI).

Further info

More informations.



Previous Index Next