Gramps - User contributions [en]

Gramps Glossary

2026-03-18T17:52:13Z

DomoViridi: /* C */ Custom Types re-write

{{languages|Gramps_Glossary}}
__NOTOC__
This glossary gives an overview of terms that appear in the [[features|Gramps]] genealogy software, with a short description, and a link to relevant articles. (Since knowing a feature's name is necessary for finding the corresponding glossary term, also refer to the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Main_Window|Visual Guide to the Gramps Interface]].)

For a glossary of genealogical terms, see [[Genealogy Glossary]] and [[Latin words and expressions]].

{| border="0" align="center" style="margin-top:0.4em;"
|
[[#A|A]] -
[[#B|B]] -
[[#C|C]] -
[[#D|D]] -
[[#E|E]] -
[[#F|F]] -
[[#G|G]] -
[[#H|H]] -
[[#I|I]] -
[[#J|J]] -
[[#K|K]] -
[[#L|L]] -
[[#M|M]] -
[[#N|N]] -
[[#O|O]] -
[[#P|P]] -
[[#Q|Q]] -
[[#R|R]] -
[[#S|S]] -
[[#T|T]] -
[[#U|U]] -
[[#V|V]] -
[[#W|W]] -
[[#X|X]] -
[[#Y|Y]] -
[[#Z|Z]]
|}


==A==

;Active Person: ''(core concept)'' - The person designated (or 'selected') as the momentary center of focus in the open Gramps database. The perspective of this person defines the context for actions and for displaying all the surrounding information. Changing this focus is done by [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Setting_the_Active_Person|navigating the Active Person]] selection to another person.
:The Active Person's relationship to the [[#home_person|Home Person]] defines the scope of the perspective.
:<abbr title="nota bene (singular), notate bene (plural) - Latin phrase meaning 'note well'">N.B.</abbr>: There is ''always'' an Active Person selection, even when the [[#primary_object|primary object]] (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> record) selected in the current view is not a 'Person' [[#object|object]].

;addon: (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Plug-in_(computing) add-on])
:An optional [[{{man version}}_Addons#Addon_List|'''third-party''' expansion]] to Gramps that leverages Gramps [[#plugin|plugin]] customization framework to add and [[Addons_development#Create_a_Gramps_Plugin_Registration_file|register]] a specific feature. The [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Using_the_Addon_Manager|Addon Manager]] allows installing and updating from curated collections of Addons. (These curated collections are called "Projects" in the Addon Manager.)
:Addons may not conform to the same design or code quality standards of builtin plugin modules. Use with caution!
:Optional parts bundled with the core project are called by the more generic name: builtin plugins. After installation and being registered, both the "builtin" and "addon" plugins may be disabled or re-enabled with the [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager#Registered_Plugins|Plugin Manager]].

;address: ''([[#secondary_object|sec. obj.]])'' - The Gramps concept of an Address is a particular location with an associated time frame. Think of it as a mailing address. It is intended to represent where a person lived and when the person lived there. The Address consists:
:* Date
:* Street Address
:* Locality
:* City
:* County
:* State/Province
:* Postal/Zip code
:* Country
:* Phone
:Not to be confused with a [[#place|Place]] which has a fixed position (its location). [[Why_residence_event_and_not_Address%3F|Use this with care.]] For genealogical research you can also use the residence event coupled with a [[#place|Place]]. For mailing (email, postal), add an address to a [[#person|Person]] or [[#repository|Repository]].

;administrative division: A unit of a layered system subdividing a geopolitical (geographic or political) region. Such divisions are recorded as [[#place|Place]] Types in Gramps. Meanwhile the structure of a Place Tree is built by layering via the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Enclosed_By|'Enclosed by' tab in the Place Editor.]] The subdivisions are sometimes categorized as an entity, locality, area, or region. The terms of subnational entity, constituent unit, or country subdivision tend to imply divisions that are more related to political representation than administrative.
: See wikipedia's [https://wikipedia.org/wiki/Administrative_division Administrative division] for a conceptional definition or [https://wikipedia.org/wiki/List_of_administrative_divisions_by_country List of administrative divisions by country] for specific countries.

;Aide: ''([[#event_role|event role]])'' - A term to refer to the role of an assistant.

;anglicisation:
: Process of making something English. If an immigrant (or their descendant) adopts a naturalized variation of their birth name, that [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Preferred_name_section|preferred alias]] can be added with an ''Also Known As'' [[Names_in_Gramps#Name_Types|name type]] in the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Names|Names]] tab. All aliases can be categorized by type and surname variants may be [[Grouping_Surnames|grouped]] with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Name_Editor|Name Editor]].

;Association: ''([[#secondary_object|sec. obj.]])'' - The [[#role|roles]] in [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_1#Associations|Associations]] are to explicitly define the how one person relates to another.
:Association roles are used when the relationship falls outside the implicit roles of a family relationship or the explicit roles in shared events. These custom roles convey relationships that might not readily apparent... such as a [https://wikipedia.org/wiki/Pen_pal penpal] or the [https://wikipedia.org/wiki/Eponym eponymous person] honored by a namesake. Association roles may also be used as placeholder when the actual genetic connection has not yet been discovered.
:Association roles are created and edited with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_1#Person_Reference_Editor|Person Reference Editor]], which includes no pre-defined roles. This feature starts with a blank list of [[#custom|custom types]]) and the default "Godfather" role is only shown as a hint.

;attribute: ''([[#secondary_object|sec. obj.]])'' - [[Attributes_in_Gramps|Attributes]] are for something permanent, or at least somewhat permanent: eye color, blood type, etc. Usually you would have not more than one of each attribute type for a [[#person|Person]]/[[#family|Family]]/etc. Attributes are managed from an Attributes tab in each [[#primary_object|primary Object]] Editor. There are a few pre-defined Attributes to support GEDCOM, but [[#custom|custom types]] will tend to be needed.

==B==
;Books Report:
A [[Gramps_{{man version}}_Wiki_Manual_-_Reports|Reports menu]] feature of Gramps that allows the [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_3|design or generation of a repeatable custom genealogy ''Book'']]. A Book consists of an ordered collation of Gramps textual and graphical reports in a single document. The individual report configuration options are also stored with the Book but the Book's document pagesize and print destination configuration options override.

;Bride: ''([[#event_role|event role]])'' A term to refer to the woman a marriage ceremony who will have the role of ''wife'' in the marriage. See also: ''mother''.

;BSDDB: ''([[Database_Backends|database backend]] engine)'' The [http://www.oracle.com/us/products/database/berkeley-db/overview/index.html Berkeley Software Distribution database] (also known as BSDDB) was the first ''default database engine'' used by the [[Database_Formats#Gramps_2.0|2.0]] through the [[Database_Formats#Gramps_5.0|5.0]] versions of Gramps. Originally, Gramps [[#xml|XML]] was used directly rather than as a Backup and data exchange format. The default db engine changed to [[#sqlite|SQLite]] in the 5.1 version via the [[DB-API_Database_Backend|DB-API Database Backend]]. ([[Install_latest_BSDDB|Manual updates to the BSDDB engine]] for the 5.1.3 version may be advisable.)

==C==
;Category: ''(core concept)'' Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of different descriptive schemas called Categories, each with their own [[#view|View]]. Each Category is a smaller, more digestible portion of the total information that comprises a Genealogical Tree. The View categories are: {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]], {{icon|peop}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People]], {{icon|rela}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships]], {{icon|fami}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Families_Category|Families]], {{icon|ance}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]], {{icon|even}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Events_Category|Events]], {{icon|plac}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places]], {{icon|geog}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography]], {{icon|sour34}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources]], {{icon|cite}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Citations_Category|Citations]], {{icon|repo}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Repositories_Category|Repositories]], {{icon|medi}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Media_Category|Media]], {{icon|note}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Notes]]

;Celebrant: ''([[#event_role|event role]])'' A term describing a role of the person who performs a rite, especially referring to a priest at the Eucharist.

;[[File:Gramps-citation.png|right]]Citation: ''({{icon|cite}} [[#primary_object|prim. obj.]])'' - Contains the information that enables you or others to locate your source document. An isolated [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_source_citations|Citation can be created]] without first creating separate [[#source|Source]] object. But, should the same source be referenced repeatedly in a Tree, a separate Source simplifies the Citation and eliminates redundant information that must be harmonized.

;Clergy: ''([[#event_role|event role]])'' A term applied to a religious person regardless of religion. For example, a monk or priest. See also: ''[[#celebrant|celebrant]]''.
: Religious terminology is often subject to dispute, see the [https://www.merriam-webster.com/dictionary/clergy Merriam-Webster] for an independent definition.

;[[File:Gramps_Clipboard48x48_win.png|right]]Clipboard: ''([[#gui|graphical user interface terminology]])'' - The [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Using_the_Clipboard|Gramps Clipboard]] is a shortcut system for [[#sharing|sharing]] a [[#secondary_object|secondary]] object, navigation, and custom [[#filter|filter]] creation.
: '''Usage:''' The Clipboard can be opened from a icon on the [[#toolbar|Toolbar]], from the Edit -> Clipboard menu choice or by using the Copy [[Gramps_{{man version}}_Wiki_Manual_-_Keybindings#7|keybinding]] for the Active Record in the Active main view of a View category. A floating clipboard dialog that has become buried can be brought to the top of the stack by selecting '''Clipboard...''' from the Windows menu.
: The Clipboard can greatly improve data entry efficiency, see the "[[How_to_use_the_Gramps_Clipboard|How to use the Gramps Clipboard]]" article for more information.

;Context menu: ''([[#gui|graphical user interface terminology]])'' - A [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Pop-up_menus|contextual pop-up menu]] (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Context_menu "context menu"]) is a menu that appears when right-clicking (or pressing the [https://wikipedia.org/wiki/Menu_key Menu keyboard key]) when the menu options directly relate to the item indicated by the mouse pointer. Thus, the indicated item provided the "context."

;Custom Types: This is a user-defined classification, as opposed to classifications that came pre-defined in Gramps (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>: 'Birth' and 'Marriage' are two of the pre-defined types of [[#event|Events]]).
:When none of the pre-defined Types are suitable, a new Custom Type can be added by typing directly into the [[#selector_combo_box|selector combo box]]. The new Custom Type will be created when the {{man button|OK}} button is clicked. If the typed value precisely matches any of the existing menu items, a new Custom Type will '''not''' be created.
: Any added Custom Type will become available in the menu for this Family Tree.
: Custom Types can be removed by using a [[Third-party_Addons|Third party addon]] utility like [[Addon:Types_Cleanup_Tool|Type Cleanup]]. Exporting and re-importing the Family Tree will also remove any Custom Types.
: '''Custom Types''' can be defined for: Event [[#attribute|Attributes]], Family [[#attribute|Attributes]], media [[#attribute|Attributes]], Person [[#attribute|Attributes]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#General|Event Roles]], [[Custom_Event_Types|Event types]], Family [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Relationship_Information|Relationship Information]] types, [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Child_Reference_Editor|Child Reference]] Types, [[Names_in_Gramps#Origin_Attributes|Name Origin Types]], [[Names_in_Gramps#Name_Types|Names Types]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_2#Note_editor_dialog|Note Types]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_2#Place_Editor_dialog|Place Types]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Repository_Reference_Editor|Repository]] Types, Source [[#attribute|Attributes]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Repository_Reference_Editor|Repository]] Media Types, [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Internet_Address_Editor|Internet Address (URL)]] Types.

==D==
;date: ''([[#secondary_object|sec. obj.]])'' - Dates in Gramps are much more complex than just a month, day, and year. Dates are always in a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Calendars|particular calendar]], can span a time frame with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_Type|Date Type]], the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_Quality|Date Quality]] can be exact (or an approximation variant), and have support for many other subtleties specific to genealogy data. The approximation can be fine-tuned with the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Limits|Limits]] preferences.
: The [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_formats_and_parsing_rules|date parsing rules]] are applied whenever data is entered into a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_dates|date text field]] or a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_selection_dialog|date selection dialog]].

;DNA:
# Acronym: '''d'''eoxyribo'''n'''ucleic '''a'''cid
# A [https://wikipedia.org/wiki/Nucleic_acid nucleic acid] that carries genetic information. Genetic testing compares for matching sequence lengths (measured in centimorgans, aka cMs) at various loci on specific chromosomes to determine common ancestry.

;Dock: ''([[#gui|graphical user interface terminology]])'' - A [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Pop-up_menus|dock]] is one of the multitude of containers offering controlled access and context to Gramplets. Gramplets can be added to, removed from, or undocked from a container to float free of the main window.
: The Dashboard was the original container and can be configured with multiple columns and stacks of Gramplets. The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|sidebar and bottombar splitbars]] are Category-specific containers. The splitbars only show a single gramplet at a time but with tabs to quickly switch between them. Each view mode has its own set of splitbars. So the basic configuration of Gramps has the Dashboard plus 24 Category view modes... or 49 separate gramplet containers.

;DTD:
:Acronym: '''D'''ocument '''T'''ype '''D'''efinition. A document that defines the tagging structure which identifies the individual components of an [https://wikipedia.org/wiki/Standard_Generalized_Markup_Language SGML] or [[#xml|XML]] document.
:See the [https://www.gramps-project.org/xml/ reference documentation for the versions] of Gramps [[Gramps_XML#RELAX_NG_generation|RELAX NG]] ('''RE'''gular '''LA'''nguage for '''X'''ML '''N'''ext '''G'''eneration)(<code>.rng</code>) schema [[#xml|XML]] and DTD

==E==
;[[File:Gramps-event.png|right]]Event: ''({{icon|even}} [[#primary_object|prim. obj.]])'' - Contains the information related to an happening. [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_events|Adding an Event record]] provides the context of an interaction of the roles of People/Families, dates & places in activities.
: An Event is a defining moment in a person's life. See [[events in Gramps|events]] for the use in genealogy, for predefined events in Gramps and suggested naming for [[Events_in_Gramps|common events]].

;event role: The [[#role|role]] a [[#person|Person]] plays in an [[#Event|Event]]. The focal Person(s) holds a [[#primary|'''''Primary role''''']] in personal Events and the Family holds a [[#family_role|'''''Family role''''']] in Family events. In Gramps, an Event can be linked to as many participants as desired. Each [[#person|Person]] may participate in different roles but more than one Person might play the same role. The Event Role captures this and can be changed in the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]]. Some common Roles are pre-defined but the user can add other [[#custom|custom]] Roles by just typing in the appropriate new label into the [[#selector_combo_box|selector combo box]].
:Pre-defined Types of Event Role: [[#aide|Aide]], [[#bride|Bride]], [[#celebrant|Celebrant]], [[#clergy|Clergy]], [[#family_role|'''''Family''''']], [[#godparent|Godparent]], [[#groom|Groom]], [[#informant|Informant]], [[#primary|'''''Primary''''']], [[#witness|Witness]], [[#unknown|'''''Unknown''''']], ''[[#custom|custom]]''

;event type: The general denominator to which an event belongs, <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, a christian, civil, tibetan, ... marriage, are all denoted by the event type ''marriage''. See [[events in Gramps]] for an overview.

==F==
;Fallback events:
:Certain [[#event|event]] types are definitive bookends marking the beginning or end of a life (Birth/Death) or relationship (Marriage/Divorce). Those bookend events are key factors in any kind of timeline analysis.
:If the definitive event types are missing, Gramps will look for similar event types to calculate a 'fallback' approximation. When dates are shown in italics, it indicates that the preferred bookend event was not found and one of the [[Events_in_Gramps#Fallback_Events|pre-defined Fallback events]] had to be used. Markers for some fallback events can be customized using the '''Genealogical Symbols''' tab of [[#preferences|Preferences]].

;Family:
#[[File:Gramps-family.png|right]]'''Family''' ''({{icon|fami}} [[#primary_object|prim. obj.]])'' - Contains the information specific to relationships between people. The information may be edited directly using the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_relationships|Edit Family]]}} dialog. This traditionally contains one or two parents and zero or more children. A family unit is created in Gramps by [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_brief#Specifying_a_relationship_using_the_Relationship_View|adding Parents to an individual]], by [[Add_a_spouse|adding a partner/spouse]] to an individual, or by adding a family first then adding the people. (A family can even consist of just the offspring.) The Family relationship is a core concept in Gramps. It depicts the basic relations between people. Commonly this will contain a father, a mother and some children, however, it can also contain only parts of this (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, two brothers, a mother and child). People can be part of several families (adoption, remarried, ...)
#'''Family''' ''([[#event_role|event role]])'' An event can be coupled to a family, denoting that the both partners were equally involved in the event. Typically, the Marriage event will be coupled to a family with event role ''family''. '''Family''' is the ''default'' role when adding a new Event in the [[#edit_family|Edit Family]] dialog.

;File Chooser:
:Picking external files or folders for import, export, reports and media is done using a File Chooser dialog from [https://wikipedia.org/wiki/GTK GTK] (formerly known as "GIMP ToolKit" and "GTK+") rather than those of the native Operating System. While generally familiar, the '''[[Gramps_{{man version}}_Wiki_Manual_-_Settings#File_Chooser|GTK File Chooser]]''' has customizable features, [[#context menu|context menus]], options and keybindings that are documented in the [[Gramps_{{man version}}_Wiki_Manual_-_Settings|Settings]] section of the manual.

;File formats:
: File formats repackage the Tree database information for archiving, data exchange with other software or display.
:* '''[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Import]] formats:''' GRAMPS v2.x database (obsolete) <code>.grdb</code>, Comma Separated Values <code>.csv</code> with [[Gramps_{{man version}}_Wiki_Manual_-_Settings#CSV_Dialect|configurable delimiter dialects]], GEDCOM (Genealogical Data Communication) <code>.ged</code>, GeneWeb <code>.gw</code>, Pro-Gen <code>.def</code>, vCard (virtual contact card) <code>.vcf</code>, JSON (JavaScript Object Notation) <code>.json</code>, SQLite <code>.sql</code>
:* '''[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|Export]] formats:''' Gramps native XML format (compressed & uncompressed variants) <code>.gramps</code>, Gramps Package (Gramps XML plus media) <code>.gpkg</code>, GEDCOM (Genealogical Data Communication) <code>.ged</code>, GeneWeb <code>.gw</code>, Web Family Tree (a GEDCOM variant) <code>.ged</code>, vCalendar <code>.ics</code>, vCard (virtual contact card) <code>.vcf</code>
:* [[Output_formats|'''Output formats''']] including: Comma Separated Values <code>.csv</code> with [[Gramps_{{man version}}_Wiki_Manual_-_Settings#CSV_Dialect|configurable delimiter dialects]], Data-Driven Documents (D3) <code><code>.d3</code></code>, Graphviz graph description language <code>.dot</code>, Hypertext Markup Language <code>.html .htm</code>, LaTeX <code>.tex</code>, Open Document Text <code>.odt</code>, Portable Document Format <code>.pdf</code>, Plain Text <code>.txt</code>, PostScript <code>.ps</code>, Print (hardcopy), Rich Text Format <code>.rtf</code>, Scalable Vector Graphics <code>.svg</code>, vCard (virtual contact card) <code>.vcf</code>, Extensible Markup Language <code>.xml</code>

;Filter:
: A [[Gramps_{{man version}}_Wiki_Manual_-_Filters|filter]] (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> query) in a database finds (or hides by 'filtering out') records, displaying only those records that match certain criteria. (The criteria are comparison or query [[#rule|rules]] describing some attribute of a record.) Layers of criteria can be applied but each layer requires additional processing and slows performance of the interface.
: The [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Filter_vs._Search|basic Search]] is a single criteria filter. The search value is compares only one attribute of a record that has been selected from a pop-up menu.
: The '''[[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Filter|Filter Gramplets]]''' will compare several predefined common attributes simultaneously with simplified access to changing the search value. The default is for exact matching but [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Regular_Expressions|Regular Expressions (RegEx)]] can be used for pattern matching. A Custom Filter may be also layered in.
: A [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Custom_Filters|Custom Filter]] adds richly complex [[#rule|Rules]]-based comparison with [[Example_filters|layers of intersection]] options for those rules. Custom Filters allow repeatable filters to be created with pre-defined rules and values to be matched. Beyond interactively hiding (or revealing) records in views, Custom Filters are used to set limits for exporting, setting scopes for reports, and targeting tool actions.
: In addition to the [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Which_filter_rules_in_which_Category.3F|builtin rules]] for filtering, [[Addon:Rule expansions]] are available for Custom Filters.

==G==
;GEDCOM:
# Acronym: '''Ge'''nealogy '''D'''ata '''Com'''munication
# A format for [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#GEDCOM_import|importing]] and [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|exporting]] genealogical data. The <abbr title="an open standard is a standard that is publicly available and has various rights to use associated with it, and may also have various properties of how it was designed such as 'open process.' There is no single definition and interpretations vary with usage.">open</abbr> specification for the [https://www.familysearch.org/developers/docs/guides/gedcom GEDCOM format] was developed by The Church of Jesus Christ of Latter-day Saints (LDS Church) as an aid to genealogical research. The long standing standard release was version 5.5 in 1996 with a 5.5.1 draft update presented for comment in 1999. (Belatedly, the 'draft' label was officially removed in the annotated 2019 release. After 20 years as the de facto standard format, it remained unimproved excepting for 2 tags and the copyright.)
::As an Open Standard, there are extensive and constantly changing incompatibilities between implementations and data loss when transferring GEDCOM formatted data between competing software tools is common. Gramps has implemented a variety of [[GEDCOM|GEDCOM support features]].
::GEDCOM [https://www.familysearch.org/developers/docs/guides/gedcom-x X proposed in 2012] and [https://blog.eogn.com/2019/10/04/the-proposed-gedcom-5-5-5-standard-is-a-better-gedcom/ 5.5.5 proposed in 2019] are improvements that have not gained the approval of the copyright holder. As of June 2021, these proposals have been superseded by the GEDCOM 7.0.1 version.

;Godparent: ''([[#event_role|event role]])'' - A term to refer to the person who presents a child at a christening or baptism and promises to take responsibility for guiding the child emotionally, practically, and spiritually. This person will be referred to as ''godfather'' or ''godmother'' after the christening or baptism. See also: ''[[Add_a_godfather-godmother|Add a godfather-godmother]]''.

;Gramplet: A [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#definition|Gramplet]] is a plug-in (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Software_widget widget] or [https://wikipedia.org/wiki/Applet applet]) that can be [[#dock|docked]] in the {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]] category view. Later [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|sidebar or bottombar]] were added to the remaining [[#view|views]] to extend [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Gramplet_Bar_Menu|adding]] and [[#undock|undocking]] a Gramplet functionality of those view.
: Gramplets dynamically update as the different records are selected in the main display area of a view. Gramplets typically create an alternate interface to your Family Tree data. Collections of [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Summary_of_Gramplets|builtin]] and [[{{man version}}_Addons#Addon_List|"3rd party addon"]] gramplets are available for [[{{man version}}_Addons#Installing_Addons_in_Gramps|installation]] and download with the [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager|Plug-in Manager]]. The Plug-in Manager also regulates a [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Aren.27t_all_Plugins_also_Gramplets.3F|wide variety of other builtin and addons]] which can expand functionality unrelated to the interface.
: ''See the [[Gramplets development]] for independent information.''

;Gramps for Desktops: [https://gramps-project.org/blog/features/ Gramps] is an open-source genealogy application, a free software project and community.
: '''Gramps''' is an affectionate nickname for a "Grandfather". Originally, the all capital letter [https://wikipedia.org/wiki/Backronym backronym] stood for "'''G'''enealogical '''R'''esearch and '''A'''nalysis '''M'''anagement '''P'''rogramming '''S'''ystem" and was coined by Larry Allingham. ([https://gramps-project.org/blog/2006/04/looking-back-over-5-years/ GRAMPS was created around 2001] by [[User:Don|Don Allingham]] for use by his father, Larry.) This backronym was phased out around March 2010 in favor of '''Gramps''' as the official name of the software. All upper-case acronym-based names have become unfashionable for software.''

;Gramps Web for Servers: [https://gramps-project.org/blog/web/ Gramps Web] is collaborative interface (frontend) and backend created by David M. Straub for running the Gramps genealogy database engine on servers. It is one of the [[Web_Solutions_for_Gramps|Web Solutions for Gramps]].
: It is a multi-user system genealogical web application with different levels of options for Visitors, Members, Contributors, Editors, and Owners. Trees in [[https://www.grampsweb.org Gramps Web on a server]] can be synchronized with the more mature and feature laden [[#gramps|Gramps for Desktops]]. Single Tree or multiple Tree sites can be self-managed on a hosted service from an ISP, leased from a managed hosting ISP, or leased from an application-specific fully managed CMS provider, or installed locally for access from a local area network.

;Graphical User Interface (GUI): A visual way of indicating interactive features of a computer operating system or application/program.
:The '''Gramps for Desktops''' GUI is introduced in [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|Visual Guide to Gramps Interface]]. It uses a "windows, icons, menus, pointer" ([https://wikipedia.org/wiki/WIMP_(computing) WIMP]) based approach with [https://wikipedia.org/wiki/Post-WIMP post-WIMP] elements like hyperlinked redirection and custom interface objects. The desktop interface is built with [https://wikipedia.org/wiki/GTK Gtk] (the Gimp Toolkit), a free and open-source cross-platform widget toolkit for creating graphical user interfaces.
:The appearance and interaction may vary by conventions dictated by the [[Download|Operating System (OS)]], installation option (such as [[Portal:Translators|language localization support]] or [[{{man version}}_Addons|addon/plug-in]]), [https://wikipedia.org/wiki/Theme_(computing) theme] (at the OS or [[Addon:ThemePreferences|internal]] levels), and/or [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Preferences|user preferences customization]].
:The specific interface elements are identified by customary name, general appearance & behavior in the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|Visual Guide to Gramps Interface]]. Expansion interface elements are described in the user documentation for [[{{man version}}_Addons|each specific addon]].
: The '''Gramps Web''' GUI (or frontend) is a platform-agnostic web browser interface built with the [https://lit.dev/ Lit] lightweight JavaScript library for building fast, interoperable web components. Although the hosting side requires a webmaster with significant skills, genealogical collaborators can use web browser on almost any device.

;Groom: ''([[#event_role|event role]])'' - A term to refer to the man at a marriage who will be referred to as ''husband'' after the marriage. See also: ''[[Add_a_spouse|Add a spouse]]''.


;GUI: An acronym. ''see [[#graphical user interface|Graphical User Interface]]''.

==H==
[[File:Gramps Go-Home48x48 win.png|right]]
;Home Person: ''(core concept)'' - The persistently designated '''Home Person''' is the foundational [[#person|Person]] (the [[Genealogy_Glossary#proband|Proband]], [[Genealogy_Glossary#progenitor|Progenitor]], or [[Genealogy_Glossary#progenitrix|Progenitrix]]) in the Tree (the currently open Gramps database). This Person is the central target of genealogical research and family references extend from this center. Ideally, every person, event and source in the Tree will (however directly or indirectly) relate back to the '''Home Person'''.
: By default, the database reports describe everything else in contextual relation to this person. The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Status_Bar_and_Progress_Bar|Status Bar]], the [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Quick_View|Quick View]] called "[[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Relation_to_Home_Person|Relation to Home Person]]", and the Third party addon [[#gramplet|Gramplet]] called "[[Addon:Deep_Connections_Gramplet|Deep Connections]]" all describe different aspects of the relationship of the [[#active_person|Active Person]] to the '''Home Person'''.
: You (or your client) are customarily designated ([[Gramps_{{man version}}_Wiki_Manual_-_Settings#Setting_Home_person|set]]) as the Home Person. And this ''Home'' designation serves as a persistent point of reference for the rest of the Tree in Reports generally and for the Active Person in detail. But a different '''Home Person''' might be temporarily [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Setting_Home_person|set]] when generating reports or when researching a complex biography or obituary.
: Fascinating tidbits often lure Gramps researchers into wandering off-course. When the [[#active_person|Active Person]] has become lost, the bearings can be instantly regained by navigating the [[#active_person|Active Person]] selection back to the '''Home Person'''.
: Navigate to '''Home Person''' - ''keyboard shortcut'' {{man key press|Alt|Home}} or press the toolbar [[File:Gramps_Go-Home48x48 win.png|text-bottom|20px]]{{man button|Home}} button.
: The custom filter rule for finding the '''Home Person''' is in a People category filter under the General filters and was named 'Default person' until the 5.1 version.

==I==
;Informant: ''([[#event_role|event role]])'' - A term to refer to the [[#role|Role]] of Person who reports an [[#event|Event]].

==J==
;JSON: Acronym: [https://wikipedia.org/wiki/JSON '''J'''ava'''S'''cript '''O'''bject '''N'''otation]. JSON is a lightweight, text-based data format designed to be easy for humans to read while still structured enough for machines to parse efficiently. It organizes data in key-value pairs, allowing information to be grouped together in a clear and straightforward way.

==K==
;Keybinding: Keyboard shortcuts (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> hotkeys) key (or combination of keys) that can be used to navigate a Graphical User Interface (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [[#gui|GUI]]) as an alternative to using the mouse. A single keystroke (or combination of keys on a keyboard) executes a command.
:''see [[Gramps_{{man version}}_Wiki_Manual_-_Keybindings#toc|Gramps GUI keybindings]]''

==L==
==M==
;Matronym:
:''([[#name_origin|Name origin]] attribute)'' - Personal name based on the name of one's mother

;[[File:Gramps-media.png|right]]Media: ''({{icon|medi}} [[#primary_object|prim. obj.]])'' - Contains the information related to a media object. Media objects include images, videos, audio recordings, documents, webpages or any other type of related files.
:When new Media objects are edited from the Gallery tabs of Object Editors or from the Media category view, the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_media_objects|New Media editor]] allows the metadata to be modified.

;[[File:Gramps_Merge48x48_win.png|right]]Merge
:To combine the objects in two selected rows in a [[#view_category|category view]] into a single object. This reduces duplicates while consolidating references and [[#secondary_object|secondary objects]]. The [[Merging_people|merge process]] involves selecting two rows (a target row to be kept and a row to be deleted) then choosing '''Merge''' from the Toolbar or Edit menu. Choices are offered about which secondary objects take precedence when there are conflicts, but no data (except one of the descriptions in an Event merge) is lost by default. All secondary objects from both selected rows are conveyed to the surviving merged row. Only two objects may be merged at a time unless using addon tools designed for multiple object merges or batches of merges.

;Mode:
:''See [[#viewmode|View mode]]''

==N==
;Name Origin:
:An optional attribute (characteristic) identifying how a name was derived for a [[#person|Person]]. Pre-defined items of the [[Names_in_Gramps#Origin_Attributes|origin selection menu]] include: inherited, patrilineal, matrilineal, given, taken, [[#patronymic|patronymic]], [[#matronymic|matronymic]], feudal, pseudonym, occupation. The Name Origin of [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Multiple_Surnames|Multiple surnames]] and [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Names|Alternative names]] can be added from the [[#edit_person|Edit Person]] dialog.
: ''Available as a standard attribute of [[Names_in_Gramps|Names in Gramps]].''

;Navigator:
: ''([[#gui|graphical user interface terminology]])'' - The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Navigator|Navigator]] is a Gramps-specific name for a left sidebar layout of [[#category|category]] view icons, allowing movement between (aka 'navigating') the different View categories. There are [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Switching_Navigator_modes|multiple layout modes]] and a [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Environment_Settings|text label preferences option]] for the sidebar. This sidebar may be hidden or revealed from the menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Navigation#View|View ->Navigator]]}} or by using the [[Gramps_{{man version}}_Wiki_Manual_-_Keybindings#7|keybinding]]. Navigator layout modes are 'Sidebar' type [[#plugin|plugins]] that can be added, removed, hidden or revealed using the Plugin Manager.
: Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of [[#category|Categories]], each with their own View. Each of the Category Views displays a smaller, more digestible portion of the total information that comprises a Genealogical Tree. The View categories are: {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]], {{icon|peop}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People]], {{icon|rela}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships]], {{icon|fami}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Families_Category|Families]], {{icon|ance}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]], {{icon|even}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Events_Category|Events]], {{icon|plac}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places]], {{icon|geog}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography]], {{icon|sour34}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources]], {{icon|cite}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Citations_Category|Citations]], {{icon|repo}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Repositories_Category|Repositories]], {{icon|medi}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Media_Category|Media]], {{icon|note}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Notes]]

;[[File:Gramps-notes.png|right]]Note: ''({{icon|note}} [[#primary_object|prim. obj.]])'' - Contains the information representing a textual brief record of facts and how it [[#reference|references]] other objects in the Tree. Notes can be added to any object at any any level of the Tree and are often used to detail the context of that record in the Tree.
:Records in the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Note Category]] contain free-form text with [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Note_markup_and_preformat_in_reports|basic formatting]] and [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Link_Editor|linking]] features. Notes can be categorized by [[#tag|Tag]] and [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#note_type|Type]] in addition to the object to which it is attached. That information is created and modified using the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_notes|Notes Editor]].

==O==

;Object: The most basic framework unit of genealogical data as structured in the Gramps [[Gramps_Data_Model|data model]].
:The most complex structures are the [[#primary_object|Primary Object]] of a [[#category|category]]. Each has an [[#object_editor|Object Editor]] that organizes entering data in that structure but also allows attaching or creating [[#secondary_object|secondary objects]].

;Object Editor ''(<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> Edit Object dialogs)'':
: ''(core concept)'' - The object editor dialogs show the basic info of the [[#primary_object|Primary Object]] in the structured form of the header area where it can be directly edited. And the bottom tabbed section allows the editing of interrelationships with [[#secondary_object|secondary objects]] and provides access to the Object Editors for those secondary objects.
:Click the following links for instructions of how to open and use each type of Edit Object dialog.
:The available categories of object editor dialogs are: {{icon|peop}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_people|Edit Person]]}}, {{icon|fami}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_relationships|Edit Family]]}}, {{icon|even}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_events|Edit Event]]}}, {{icon|plac}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_places|Edit Place]]}}, {{icon|sour34}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_sources|Edit Source]]}}, {{icon|cite}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_source_citations|Edit Citation]]}}, {{icon|repo}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_repositories|Edit Repository]]}}, {{icon|medi}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_media_objects|Edit Media]]}}, {{icon|note}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_notes|Edit Note]]}}
:The available categories of object reference editor dialogs for [[#sharing|shared objects]] are: {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Person_Reference_Editor|Person Reference Editor]]}} ''(see [[#association|Associations]])'', {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Child_Reference_Editor|Child Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Place_Reference_Editor|Place Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Repository_Reference_Editor|Repository Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Media_Reference_Editor_dialog|Media Reference Editor]]}}

;Officiator: ''([[#event_role|event role]])'' - A term to refer to the role of a person authorized to conduct an official duty or function. (Such as performing a marriage or funeral ceremony or conferring a vocational degree.) Jurisdiction may be derived from a from holding a position of civil or religious authority. Use 'OFFICIATOR' rather than 'Officiant' for [[#gedcom|GEDCOM7]] Roles compatibility.

==P==
;patronym:
:''([[#name_origin|Name origin]] attribute)'' - Personal name based on the name of one's father.

;[[File:Gramps-person.png|right]]Person: ''({{icon|peop}} [[#primary_object|prim. obj.]])'' - Contains the information specific to an individual person in the People category. The information may be edited directly using the [[#edit_person|Edit Person]] dialog.

;[[File:Gramps-place.png|right]]Place: ''({{icon|plac}} [[#primary_object|prim. obj.]])'' - The Gramps concept of a Place is a particular location independent of time. Over time, the same Place may have different hierarchical (or name) information due to changing borders and political situation. For example, Leningrad and St. Petersburg represent the same place, but with different names. Places in Gramps are stored in a hierarchy and are direct accessed via the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places category view]]. Places can be defined (or refined) through the Place Editor and shared with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Select_Place_selector|Select Place]] object selector. A Place consists of:
:* Descriptive Title
:* Name (with optional date span and language attributes)
:* A list of alternative names for the place
:* Type ([[#administrative_division|administrative divisions]] such as country, state, county ...)
:* Longitude/Latitude
:* Code (such as a country code or postal code)
:* A hierachical list of regions which enclose the place

;plugin: (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Plug-in_(computing) plug-in])
:* A type of [[Writing_a_plugin|expansion framework that allows Gramps customization]] by providing interface hooks to recognize and use external code.
:* A customized module of code built to provide a specific feature or functionality that is not part of the core program.
:The [[Addon_list_legend#Type|various types]] of Gramps plugin code modules can be enabled or disabled via a [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager|plugin manager]]. Plugin types include: Citation formatter, [[Database_Backends|Database]], Doc creator, Exporter, [[#gramplet|Gramplet]], Gramps View ([[#view|''Category'']] or [[#viewmode|''mode'']]), Importer, [[Map_Services|Map Service]], Plugin lib, [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Quick_Views|Quickreport'''/'''Quickview]], Relationships, [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_1|Report]], [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Add_Rule_dialog|Rule]], Sidebar, Thumbnailer [[Gramps_{{man version}}_Wiki_Manual_-_Tools|Tool]].
:Plugins can be builtin ''(included with the normal distribution of Gramps)'' or an [[{{man version}}_Addons#Addon_List|addon]] ''(installed via the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Third_party_addons_management|Third party addons management]] in Preferences)''.

;POSIX: [https://wikipedia.org/wiki/Posix Portable Operating System Interface]: a family of OS standards specified by the [https://wikipedia.org/wiki/IEEE_Computer_Society IEEE] Computer Society for maintaining compatibility with variants of Unix (such as Linux) and other operating systems. Although the MacOS is "POSIX-certified", the term is used in this manual to generically refer to just the "Mostly POSIX-compliant" Linux and BSD distributions [[Download#Linux_and_BSD_distributions|with verified Gramps downloads]] and which use the POSIX-style [https://wikipedia.org/wiki/Filesystem_Hierarchy_Standard environment].

;Preferences: The {{Man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Preferences|Preferences]]}} is an option in the {{Man menu|Edit}} main menu that allows '''''global''''' customization of the appearance, defaults and behavior of Gramps. The customizations are categorized into the following tabs: {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Data|Data]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#General|General]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Family_Tree|Family Tree]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Import|Import]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Limits|Limits]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Colors|Colors]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Genealogical Symbols|Genealogical Symbols]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#ID_Formats|ID Formats]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Text|Text]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Warnings|Warnings]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Researcher|Researcher]]}}.
:(A {{man label|[[Addon:ThemePreferences|Theme]]}} tab is available as an addon.)
:(see also ''{{Man menu|Configure...}}'' option in the {{Man menu|View}} main menu is an option. Those customization are limited to the currently active view and its Gramplets. The feature may also be accessed by the {{man button|Configure...}} toolbar icon.)
:The Gramps 5.1 and older preferences are categorized into the following tabs: {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#General|General]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Family_Tree|Family Tree]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Display|Display]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Text|Text]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#ID_Formats|ID Formats]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Dates|Dates]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Researcher|Researcher]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Warnings|Warnings]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Colors|Colors]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Genealogical Symbols|Genealogical Symbols]]}}.

;Prerequisites: Additional software required to make certain features of Gramps work and or some [[:Category:Prerequisites|addons]].

;Primary object: Primary objects are the [[Using_database_API|data structures]] at the top level of a [[Gramps_Data_Model|hierarchical collection of records]] in the Gramps [[Gramps_Data_Model|data model]]. Beside the main structure of data, they can contain a hierarchy of [[#secondary_object|secondary objects]], and can be referenced by other primary or secondary objects. In the Gramps database, primary objects and the secondary objects that they contain are stored as separate records. Each primary object type is stored in a separate table. See [[Using_database_API#Primary_Objects|Using database API, Primary Objects]] (see also ''[[#secondary_object|secondary object]]'')
: The types of [[Using_database_API#Primary_Objects|primary objects]] are:
: {{icon|cite}} [[#citation|Citation]], {{icon|even}} [[#event|Event]], {{icon|fami}} [[#family|Family]], {{icon|medi}} [[#media|Media]], {{icon|note}} [[#note|Note]], {{icon|peop}} [[#person|Person]], {{icon|plac}} [[#place|Place]], {{icon|repo}} [[#repository|Repository]], {{icon|sour34}} [[#source|Source]], [[File:16x16-gramps-tag.png]] [[#tag|Tag]].

;Primary role: ''([[#event_role|event role]])'' - A term to refer to the [[#role|role]] of the focal participant of an [[#event|Event]]. '''Primary''' is the ''default'' role when adding a new Event in the [[#edit_person|Edit Person]] dialog.

;[[File:gramps-lock.png|right]]Private flag or tag:
: The Private option identifies sensitive information that should be redacted when sharing data or printing reports. ''(This marker should not be confused with the generic user-definable [[#tag|Tags]] used for custom filters and color highlighting.)'' Records are shown with: a [[File:22x22-gramps-lock.png]]locked padlock when private; and, an [[File:22x22-gramps-unlock.png]]unlocked padlock when public. Clicking the padlock icon toggles between Private & Public flags. This manual override supplements the automated [[Gramps_{{man version}}_Wiki_Manual_-_Probably_Alive|Probably Alive]] and custom [[Filter|Filter]] features which help Gramps to respect Personal Privacy.
:Gramps is a single user database and omits the typical security features of a multi-user system. So even "Private" data will be accessible from within Gramps. However, generating reports and exporting data default to redacting information flagged as Private.

;[[File:gramps-unlock.png|right]]Public tag or flag:
: The Public option identifies information that should be included when sharing data or printing reports. Records are shown with: a [[File:22x22-gramps-unlock.png]]unlocked padlock when public; and, an [[File:22x22-gramps-lock.png]]locked padlock when private. Clicking the padlock icon toggles between Public & Private flags. By default, all records are created as Public.

==Q==
;Quick View: On-screen [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Quick_Views|reports]] about information surrounding the active object that do not print or save to file. Generally the report is selected from a [[#context_menu|context menu]] for the selected category of record and will have no configurable options.
: The [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Quick_View|Quick View '''gramplet''']] refreshes a builtin [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Quick_Views|builtin]] or [[{{man version}}_Addons#Addon_List|addon]] QuickView reports as the focus of the active record is changed. The specific QuickView report is selected in a view configuration dialog opened with the {{man menu|View -> Configure...}} menu.

==R==
;Reference: The basic system of linking relationships between objects in Gramps. When an object is added in the Editor for record, a [[References#definition|Reference]] (link) is created in the object that was added.

;[[File:Gramps-relation.png|right]]References tab: When objects of Gramps are linked, the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#References|References tab]] lists the objects to link toward it.

;Regular Expressions: [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Regular_Expressions|RegEx]] is a system to specify a text string pattern for comparing and matching. Optionally used to extend a power of the Filter Gramplets and Custom Filters rules.
:Filters in [https://gramps.discourse.group/t/which-regex-syntax-does-gramps-use/2278/8 Gramps use the RegEx format specified by the installed version of Python]

;Re-order
:[[File:Stock_reorder.png|right]]To change the sequence of items within a list of [[#secondary_object|secondary objects]]. [https://gramps.discourse.group/t/re-ordering-data-in-gramps-topic-expansion-outline-for-wiki/5568 The interface for (and consequences of) re-ordering that sequence varies based on the list type.]
:The natural order of a list follows when the data was created. The first item in an ordered list is often considered the primary or preferred item of that type. The primary/preferred may be the only object considered in some charts and analyses. So when data entry of related objects was out of sequence, a re-ordering option becomes necessary.
:Re-ordering affects display order in the Tree, charts, and most reports. Note that in some contexts, dates can override the manual order, particularly for Places and Names.

;[[File:Gramps-repository.png|right]]Repository: ''({{icon|repo}} [[#primary_object|prim. obj.]])'' - Contains the information related to a physical or virtual structure where genealogical and family history sources are stored. Once a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_repositories|Repository is added]] to a Gramps Tree, it can used to organize [[#source|Sources]].

;Role: Function performed or part played by a person (or other Gramps [[#object|object]]) in a particular situation. When objects of Gramps are linked, a Reference is created where the implicit Role disambiguates the relative nature of the reference. ''For explicitly defined roles, see [[#event_role|event role]] and [[#association|association role]]''

;Romanization:
: Linguistic representation of a word in the Roman (Latin) alphabet

;Rule: A pre-defined abstraction that simplifies the interface for a structured query about a particular facet of your family tree. Rules allows users to choose search criteria without needing to understand the intricate details of the actual database query language. Rules are layered via the [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Custom_Filters|Custom Filters]] interface to [[#filter|filter]] with complex criteria.

==S==
;Secondary object: Secondary objects are contained within other [[#object|objects]] of the structured Gramps [[Gramps_Data_Model|data model]], and cannot be referenced directly. They can contain other secondary objects. Examples include: Name, Date and Address. See [[Using_database_API#Secondary_Objects|Using database API, Secondary Objects]] (see also ''[[#primary_object|primary object]]'')

;Selector combo box: ''([[#gui|graphical user interface terminology]])'' - a [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Combo_Boxes|standard text entry box paired with a pull-down list button]] is a [https://docs.gtk.org/gtk3/visual_index.html Gtk toolbox widget] (based on the standard [https://wikipedia.org/wiki/Combo_box combo box]). The combination of a drop-down list and a single-line editable textbox allows the user to either select a value from the list or key in a value directly. Moreover, keying in a value that is not already in the list will add that [[#custom|custom type]] to the drop-down list.

;Shared objects: {{icon|share}} Sharing allows an Object to be linked at multiple places in the tree. Doing so establishes a relationship or maintains single set of attributes (or [[#secondary_object|secondary objects]]) that they hold in common. ([[#role|Roles]] for shared Events define the person or family participation level.)
:'''[[#object_reference_editors|Object Reference Editors]]''' allow updates to a shared object to be reflected in all instances mentioning (referencing) that shared object. Redundantly creating object with the same information should be avoided. (So, refining a Transcription Note shared by multiple Citations will show the updated transcription in all the Citations.)
:Object descriptions are grouped in two distinct sections:
:  • The '''Reference Information''' section contains information unique to one instance.
:  • The '''Shared Information''' of an object will be seen in all instances that are linked to it.

;Selector: Combo interface box that allows you to select an object. The [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Selector_dialogs|Select Family selector]] is one example.

;[[File:Gramps-source.png|right]]Source: ''({{icon|sour34}} [[#primary_object|prim. obj.]])'' - Sources can be a person ''(family, friend, another researcher)'', thing ''(book, magazine newspaper, census)'', or place ''(courthouse, church, library, genealogical/historical society... although places might be better handled as Repositories)'' from which information comes, arises, or is obtained. After [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_sources|adding a Source]] with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#New_Source_dialog|new source dialog]] to the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources category]] of a Gramps Tree, the Source can be referenced when adding a [[#citation|Citations]] and organized within [[#repository|Repositories]]. The same Source may exist in multiple Repositories and may have different Media Types (such as book, microfilm, or electronic) and Call numbers in each Repository.
:[[Sources#Definition|[more]]]

;SQLite: ''([[Database_Backends|database backend]] engine)'' - The [https://sqlite.org/about.html SQLite project's in-process library] (also known simply as SQLite) is the ''default database engine'' used since the [[Database_Formats#Gramps_5.1|5.1]] version of Gramps. The support was extended from [[#bsddb|BSDDB]] in the 5.0 version via the [[DB-API_Database_Backend|DB-API Database Backend]].

;Swatch: ''([[#gui|graphical user interface terminology]])'' - A [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Pick_a_Color_selector|color swatch]] is a sample square of a color or color pattern. Swatches may be dragged from the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Pick_a_Color_selector|Pick a Color selector]] to apply that specific color to preferences.
:The word originally referred to sample pieces of cloth or fabric used for choosing or testing colors, patterns, or textures for interior or exterior design. It now means any small sample or representation of a larger whole and is commonly usage in the context of color representation and selection in software applications.

==T==
;[[File:gramps-tag.png|right]]Tag: ''([[File:16x16-gramps-tag.png]] [[#primary_object|prim. obj.]])'' - A custom titled and color-coded label that [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Tagging|can be created with the Organize Tags dialog and attached]] to selected {{icon|cite}} [[#citation|Citation]], {{icon|even}} [[#event|Event]], {{icon|fami}} [[#family|Family]], {{icon|medi}} [[#media|Media]], {{icon|note}} [[#note|Note]], {{icon|peop}} [[#person|Person]], {{icon|plac}} [[#place|Place]], {{icon|repo}} [[#repository|Repository]] or {{icon|sour34}} [[#source|Source]] objects for the purpose of easy identification and filtering.
: A keyword or phrase used to group the collection to produce a report. Multiple tags may be used to label and categorize objects into multiple groups when filtering by other attributes is not viable.

;Toolbar: ''([[#gui|graphical user interface terminology]])'' - The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Toolbar|Toolbar]] is a ribbon (located below the application menubar) with button shortcuts for the most widely needed functions associated with the current view. The selection of buttons changes in response to the context of the current view. (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, toolbar buttons for switching mapping [[#view_mode|view modes]] will only appear for the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography view]].)

;Typographical conventions: The [[Gramps_{{man version}}_Wiki_Manual_-_Preface#Typographical_conventions|customary formatting]] having special (and possibly peculiar) meaning when used throughout the MediaWiki driven [[Gramps_{{man version}}_Wiki_Manual|Gramps manual]] and documentation. The different typeface accents, highlighting and enclosures indicate specific parts of the Gramps [[#graphical user interface|Graphical User Interface]] ([[#GUI|GUI]]) or prompt a User activity.

==U==
;Unknown: ''([[#event_role|event role]])'' - A placeholder for when the [[#role|role]] of a participant in an [[#event|Event]] has not yet been defined. Gramps sets an appropriate default Role as each new Event type is created. But when a new participant is associated with an existing Event via Share or drag'n'drop, the Role isn't as predictable. In such a case, an Unknown placeholder is inserted.
:Any Unknown [[#event_role|Event Role]] type causes a variety of reporting problems. [[Addon:Rule_expansions#People_with_events_with_a_selected_role|(Rule_expansions)Persons and Families with Unknown Roles]] should be found and the Roles manually replaced as soon as is practical.

;User Directory: ''(core concept)'' - An alias for the file folder (directory) location where customizations (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>: preferences files, [[#addon|addons]], [[#plugin|plugins]]) are stored for the Gramps family of genealogy tools. Since this folder location varies by which Operating System and which Gramps fork has been installed, the '''User Directory''' is an 'alias' (a.k.a. placeholder) used in instructions about re-configuring Gramps.
: This alias allows [[Gramps_{{man version}}_Wiki_Manual_-_User_Directory|instructions for locating your specific '''User Directory''' file location]] to be consolidated in the documentation.

==V==
;View category: ''([[#gui|graphical user interface terminology]])'' - a [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|'''View category''']] (often simply called a "'''[[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|View]]'''") is a Gramps-specific name for the collection of [[#view mode|View modes]] (display layouts) presenting information in a structured and predictable manner. Different Views are selected from the [[#navigator|Navigator]] (left sidebar).
: Layouts are in table, outline or graphical formats, depending on the preferred way to represent how the data elements relate to one another.
: Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of [[#category|Categories]], each with their own View. Each of the Category Views displays a smaller, more digestible portion of the total information that comprises a Genealogical Tree. The View categories are: {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]], {{icon|peop}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People]], {{icon|rela}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships]], {{icon|fami}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Families_Category|Families]], {{icon|ance}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]], {{icon|even}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Events_Category|Events]], {{icon|plac}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places]], {{icon|geog}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography]], {{icon|sour34}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources]], {{icon|cite}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Citations_Category|Citations]], {{icon|repo}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Repositories_Category|Repositories]], {{icon|medi}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Media_Category|Media]], {{icon|note}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Notes]]

;View mode: ''([[#gui|graphical user interface terminology]])'' - a '''[[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|View mode]]''' is a Gramps-specific name for the display layouts presenting [[#view_category|View category]] information in a structured and predictable manner. A [[#view_category|View category]] may have alternate '''view modes''' (subcategories) of display layout. (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, Views with Table layouts might have flat listed or hierarchically grouped modes.) Navigating between View modes is from the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Toolbar|toolbar]] and [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Switching_Navigator_modes|Navigator]].
: Each mode of a category can be independently [[File:Gramps-config.png|22px]] configured. Each mode may maintain a separate object selection, filtering, and organization for its Gramplet bars.
: View data may be further subdivided with tabbed pages of layouts.

==W==
;wiki: (Hawaiian [https://wikipedia.org/wiki/Loanword loanword]) meaning 'quick'; or 'wikiwiki' meaning 'very quick'. For Gramps users, '''''[[User manual|the Wiki]]''''' (a.k.a. '''''[[User manual|Wiki Manual]]''''') refers to the collaborative website of educational material which is organized using the [https://mediawiki.org/wiki/MediaWiki MediaWiki] [https://wikipedia.org/wiki/Content_management_system content management system]. The core pages of that website being the structured reference-style [[#gramps|Gramps]] software user's operating guide. ''(Note that specific [[:Category:Tutorials|tutorial]] documents are also part of the wiki.)''
:For most internet users, the word is most often an inadvertent allusion to the 1995 [http://wiki.c2.com/?WikiWikiWeb WikiWikiWeb], the first website that builtin tools encouraging users to quickly & easily collaborate to expand the content of the site. See the term: [https://wiktionary.org/wiki/wiki 'wiki'] in [https://wiktionary.org/wiki/Wiktionary Wiktionary]

;Witness:''([[#event_role|event role]])'' - The term that applies to the people asked to be present at an event so as to be able to testify to its having taken place.

==X==
;XML: acronym: [https://wikipedia.org/wiki/XML E'''x'''tensible '''M'''arkup '''L'''anguage]. A schema used to define the expected structure of data in a text format. The system annotates a document in a way that data elements are syntactically distinguishable from identifying tags. A markup language defines a set of rules for encoding documents in a fault tolerant format that is both (marginally) human-readable and machine-readable.
: Gramps will [[Generate_XML|generate XML]] format natively in compressed and uncompressed forms identified with a <code>.gramps</code> or <code>.gpkg</code> file extension. It is the format that definitively supports every piece of genealogical data stored by Gramps. Used as the working format until Gramps 2.0 started using a ''[[Database_Backends|database backend]]'' to improve performance, XML is now the standard Tree data backup format and recommended data exchange format.
: See the [https://www.gramps-project.org/xml/ reference documentation for the versions] of Gramps [[Gramps_XML#RELAX_NG_generation|RELAX NG]] ('''RE'''gular '''LA'''nguage for '''X'''ML '''N'''ext '''G'''eneration)(<code>.rng</code>) schema XML and [[#dtd|DTD]]

==Y==
==Z==

{{man tip|1=Wiki manual|2=Please enhance the {{man label|Wiki}} - create new glossary terms and add them to the wiki manual. Glossary term IDs are more memorable & predictable if kept to all lower-case. When translating the Glossary, please leave the English ID anchors but also add translated variants of the same anchor. This allows users to look up a term in either language.

Inserting a "Glossary Term" into the Glossary list: 
<code><nowiki>;Glossary Term: Definition of the term.</nowiki></code> 
Do not replace a space in the anchor ID with an underscore. An anchor defined with a space can match both the underscore and space form, but an anchor defined with an underscore can only be referenced by the underscore form.

In a translated Glossary, add the English ID by putting an extra span around the translated header: 
<code><nowiki>;Translated Term: Translated definition of the term.</nowiki></code>

Referencing the glossary term in the Gramps wiki manual: 
<code><nowiki>[[Gramps_Glossary#glossary_term|Glossary Term]]</nowiki></code> 
(Note the optional underscores for spaces here.)

For more information about WikiMedia sections, see: 
<code>https://meta.wikimedia.org/w/index.php?title=Help:Section#id_with_space</code>

}}

[[Category:Gramps terminology|*]]
[[Category:Translators/Categories]]
[[Category:Documentation]]

Gramps Glossary

2026-03-18T17:29:00Z

DomoViridi: /* S */ added "combo box" as alternative to "selector combo box"

{{languages|Gramps_Glossary}}
__NOTOC__
This glossary gives an overview of terms that appear in the [[features|Gramps]] genealogy software, with a short description, and a link to relevant articles. (Since knowing a feature's name is necessary for finding the corresponding glossary term, also refer to the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Main_Window|Visual Guide to the Gramps Interface]].)

For a glossary of genealogical terms, see [[Genealogy Glossary]] and [[Latin words and expressions]].

{| border="0" align="center" style="margin-top:0.4em;"
|
[[#A|A]] -
[[#B|B]] -
[[#C|C]] -
[[#D|D]] -
[[#E|E]] -
[[#F|F]] -
[[#G|G]] -
[[#H|H]] -
[[#I|I]] -
[[#J|J]] -
[[#K|K]] -
[[#L|L]] -
[[#M|M]] -
[[#N|N]] -
[[#O|O]] -
[[#P|P]] -
[[#Q|Q]] -
[[#R|R]] -
[[#S|S]] -
[[#T|T]] -
[[#U|U]] -
[[#V|V]] -
[[#W|W]] -
[[#X|X]] -
[[#Y|Y]] -
[[#Z|Z]]
|}


==A==

;Active Person: ''(core concept)'' - The person designated (or 'selected') as the momentary center of focus in the open Gramps database. The perspective of this person defines the context for actions and for displaying all the surrounding information. Changing this focus is done by [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Setting_the_Active_Person|navigating the Active Person]] selection to another person.
:The Active Person's relationship to the [[#home_person|Home Person]] defines the scope of the perspective.
:<abbr title="nota bene (singular), notate bene (plural) - Latin phrase meaning 'note well'">N.B.</abbr>: There is ''always'' an Active Person selection, even when the [[#primary_object|primary object]] (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> record) selected in the current view is not a 'Person' [[#object|object]].

;addon: (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Plug-in_(computing) add-on])
:An optional [[{{man version}}_Addons#Addon_List|'''third-party''' expansion]] to Gramps that leverages Gramps [[#plugin|plugin]] customization framework to add and [[Addons_development#Create_a_Gramps_Plugin_Registration_file|register]] a specific feature. The [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Using_the_Addon_Manager|Addon Manager]] allows installing and updating from curated collections of Addons. (These curated collections are called "Projects" in the Addon Manager.)
:Addons may not conform to the same design or code quality standards of builtin plugin modules. Use with caution!
:Optional parts bundled with the core project are called by the more generic name: builtin plugins. After installation and being registered, both the "builtin" and "addon" plugins may be disabled or re-enabled with the [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager#Registered_Plugins|Plugin Manager]].

;address: ''([[#secondary_object|sec. obj.]])'' - The Gramps concept of an Address is a particular location with an associated time frame. Think of it as a mailing address. It is intended to represent where a person lived and when the person lived there. The Address consists:
:* Date
:* Street Address
:* Locality
:* City
:* County
:* State/Province
:* Postal/Zip code
:* Country
:* Phone
:Not to be confused with a [[#place|Place]] which has a fixed position (its location). [[Why_residence_event_and_not_Address%3F|Use this with care.]] For genealogical research you can also use the residence event coupled with a [[#place|Place]]. For mailing (email, postal), add an address to a [[#person|Person]] or [[#repository|Repository]].

;administrative division: A unit of a layered system subdividing a geopolitical (geographic or political) region. Such divisions are recorded as [[#place|Place]] Types in Gramps. Meanwhile the structure of a Place Tree is built by layering via the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Enclosed_By|'Enclosed by' tab in the Place Editor.]] The subdivisions are sometimes categorized as an entity, locality, area, or region. The terms of subnational entity, constituent unit, or country subdivision tend to imply divisions that are more related to political representation than administrative.
: See wikipedia's [https://wikipedia.org/wiki/Administrative_division Administrative division] for a conceptional definition or [https://wikipedia.org/wiki/List_of_administrative_divisions_by_country List of administrative divisions by country] for specific countries.

;Aide: ''([[#event_role|event role]])'' - A term to refer to the role of an assistant.

;anglicisation:
: Process of making something English. If an immigrant (or their descendant) adopts a naturalized variation of their birth name, that [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Preferred_name_section|preferred alias]] can be added with an ''Also Known As'' [[Names_in_Gramps#Name_Types|name type]] in the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Names|Names]] tab. All aliases can be categorized by type and surname variants may be [[Grouping_Surnames|grouped]] with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Name_Editor|Name Editor]].

;Association: ''([[#secondary_object|sec. obj.]])'' - The [[#role|roles]] in [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_1#Associations|Associations]] are to explicitly define the how one person relates to another.
:Association roles are used when the relationship falls outside the implicit roles of a family relationship or the explicit roles in shared events. These custom roles convey relationships that might not readily apparent... such as a [https://wikipedia.org/wiki/Pen_pal penpal] or the [https://wikipedia.org/wiki/Eponym eponymous person] honored by a namesake. Association roles may also be used as placeholder when the actual genetic connection has not yet been discovered.
:Association roles are created and edited with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_1#Person_Reference_Editor|Person Reference Editor]], which includes no pre-defined roles. This feature starts with a blank list of [[#custom|custom types]]) and the default "Godfather" role is only shown as a hint.

;attribute: ''([[#secondary_object|sec. obj.]])'' - [[Attributes_in_Gramps|Attributes]] are for something permanent, or at least somewhat permanent: eye color, blood type, etc. Usually you would have not more than one of each attribute type for a [[#person|Person]]/[[#family|Family]]/etc. Attributes are managed from an Attributes tab in each [[#primary_object|primary Object]] Editor. There are a few pre-defined Attributes to support GEDCOM, but [[#custom|custom types]] will tend to be needed.

==B==
;Books Report:
A [[Gramps_{{man version}}_Wiki_Manual_-_Reports|Reports menu]] feature of Gramps that allows the [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_3|design or generation of a repeatable custom genealogy ''Book'']]. A Book consists of an ordered collation of Gramps textual and graphical reports in a single document. The individual report configuration options are also stored with the Book but the Book's document pagesize and print destination configuration options override.

;Bride: ''([[#event_role|event role]])'' A term to refer to the woman a marriage ceremony who will have the role of ''wife'' in the marriage. See also: ''mother''.

;BSDDB: ''([[Database_Backends|database backend]] engine)'' The [http://www.oracle.com/us/products/database/berkeley-db/overview/index.html Berkeley Software Distribution database] (also known as BSDDB) was the first ''default database engine'' used by the [[Database_Formats#Gramps_2.0|2.0]] through the [[Database_Formats#Gramps_5.0|5.0]] versions of Gramps. Originally, Gramps [[#xml|XML]] was used directly rather than as a Backup and data exchange format. The default db engine changed to [[#sqlite|SQLite]] in the 5.1 version via the [[DB-API_Database_Backend|DB-API Database Backend]]. ([[Install_latest_BSDDB|Manual updates to the BSDDB engine]] for the 5.1.3 version may be advisable.)

==C==
;Category: ''(core concept)'' Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of different descriptive schemas called Categories, each with their own [[#view|View]]. Each Category is a smaller, more digestible portion of the total information that comprises a Genealogical Tree. The View categories are: {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]], {{icon|peop}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People]], {{icon|rela}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships]], {{icon|fami}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Families_Category|Families]], {{icon|ance}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]], {{icon|even}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Events_Category|Events]], {{icon|plac}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places]], {{icon|geog}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography]], {{icon|sour34}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources]], {{icon|cite}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Citations_Category|Citations]], {{icon|repo}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Repositories_Category|Repositories]], {{icon|medi}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Media_Category|Media]], {{icon|note}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Notes]]

;Celebrant: ''([[#event_role|event role]])'' A term describing a role of the person who performs a rite, especially referring to a priest at the Eucharist.

;[[File:Gramps-citation.png|right]]Citation: ''({{icon|cite}} [[#primary_object|prim. obj.]])'' - Contains the information that enables you or others to locate your source document. An isolated [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_source_citations|Citation can be created]] without first creating separate [[#source|Source]] object. But, should the same source be referenced repeatedly in a Tree, a separate Source simplifies the Citation and eliminates redundant information that must be harmonized.

;Clergy: ''([[#event_role|event role]])'' A term applied to a religious person regardless of religion. For example, a monk or priest. See also: ''[[#celebrant|celebrant]]''.
: Religious terminology is often subject to dispute, see the [https://www.merriam-webster.com/dictionary/clergy Merriam-Webster] for an independent definition.

;[[File:Gramps_Clipboard48x48_win.png|right]]Clipboard: ''([[#gui|graphical user interface terminology]])'' - The [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Using_the_Clipboard|Gramps Clipboard]] is a shortcut system for [[#sharing|sharing]] a [[#secondary_object|secondary]] object, navigation, and custom [[#filter|filter]] creation.
: '''Usage:''' The Clipboard can be opened from a icon on the [[#toolbar|Toolbar]], from the Edit -> Clipboard menu choice or by using the Copy [[Gramps_{{man version}}_Wiki_Manual_-_Keybindings#7|keybinding]] for the Active Record in the Active main view of a View category. A floating clipboard dialog that has become buried can be brought to the top of the stack by selecting '''Clipboard...''' from the Windows menu.
: The Clipboard can greatly improve data entry efficiency, see the "[[How_to_use_the_Gramps_Clipboard|How to use the Gramps Clipboard]]" article for more information.

;Context menu: ''([[#gui|graphical user interface terminology]])'' - A [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Pop-up_menus|contextual pop-up menu]] (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Context_menu "context menu"]) is a menu that appears when right-clicking (or pressing the [https://wikipedia.org/wiki/Menu_key Menu keyboard key]) when the menu options directly relate to the item indicated by the mouse pointer. Thus, the indicated item provided the "context."

;''custom'' Types: This indicates a user-defined classification, as opposed to classifications that came pre-defined in Gramps. (i.e.: 'Birth' and 'Marriage' are 2 of the pre-defined 'types' of Events.)
:When none of the pre-defined Types are suitable, add a new ''[[#custom|custom]]'' Type by typewriting directly into the [[#selector_combo_box|selector combo box]]. If the value doesn't precisely match any of the existing menu items, a new ''custom'' Type will be created when the {{man button|OK}} button is clicked.
: Any added ''custom'' Type will remain available in that expanded menu... unless the Tree is exported and re-imported or removed via a [[Third-party_Addons|Third party addon]] Utility like [[Addon:Types_Cleanup_Tool|Type Cleanup]].
: '''''custom'' Types''' can be defined for: Event [[#attribute|Attributes]], Family [[#attribute|Attributes]], media [[#attribute|Attributes]], Person [[#attribute|Attributes]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#General|Event Roles]], [[Custom_Event_Types|Event types]], Family [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Relationship_Information|Relationship Information]] types, [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Child_Reference_Editor|Child Reference]] Types, [[Names_in_Gramps#Origin_Attributes|Name Origin Types]], [[Names_in_Gramps#Name_Types|Names Types]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_2#Note_editor_dialog|Note Types]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_2#Place_Editor_dialog|Place Types]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Repository_Reference_Editor|Repository]] Types, Source [[#attribute|Attributes]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Repository_Reference_Editor|Repository]] Media Types, [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Internet_Address_Editor|Internet Address (URL)]] Types.

==D==
;date: ''([[#secondary_object|sec. obj.]])'' - Dates in Gramps are much more complex than just a month, day, and year. Dates are always in a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Calendars|particular calendar]], can span a time frame with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_Type|Date Type]], the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_Quality|Date Quality]] can be exact (or an approximation variant), and have support for many other subtleties specific to genealogy data. The approximation can be fine-tuned with the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Limits|Limits]] preferences.
: The [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_formats_and_parsing_rules|date parsing rules]] are applied whenever data is entered into a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_dates|date text field]] or a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_selection_dialog|date selection dialog]].

;DNA:
# Acronym: '''d'''eoxyribo'''n'''ucleic '''a'''cid
# A [https://wikipedia.org/wiki/Nucleic_acid nucleic acid] that carries genetic information. Genetic testing compares for matching sequence lengths (measured in centimorgans, aka cMs) at various loci on specific chromosomes to determine common ancestry.

;Dock: ''([[#gui|graphical user interface terminology]])'' - A [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Pop-up_menus|dock]] is one of the multitude of containers offering controlled access and context to Gramplets. Gramplets can be added to, removed from, or undocked from a container to float free of the main window.
: The Dashboard was the original container and can be configured with multiple columns and stacks of Gramplets. The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|sidebar and bottombar splitbars]] are Category-specific containers. The splitbars only show a single gramplet at a time but with tabs to quickly switch between them. Each view mode has its own set of splitbars. So the basic configuration of Gramps has the Dashboard plus 24 Category view modes... or 49 separate gramplet containers.

;DTD:
:Acronym: '''D'''ocument '''T'''ype '''D'''efinition. A document that defines the tagging structure which identifies the individual components of an [https://wikipedia.org/wiki/Standard_Generalized_Markup_Language SGML] or [[#xml|XML]] document.
:See the [https://www.gramps-project.org/xml/ reference documentation for the versions] of Gramps [[Gramps_XML#RELAX_NG_generation|RELAX NG]] ('''RE'''gular '''LA'''nguage for '''X'''ML '''N'''ext '''G'''eneration)(<code>.rng</code>) schema [[#xml|XML]] and DTD

==E==
;[[File:Gramps-event.png|right]]Event: ''({{icon|even}} [[#primary_object|prim. obj.]])'' - Contains the information related to an happening. [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_events|Adding an Event record]] provides the context of an interaction of the roles of People/Families, dates & places in activities.
: An Event is a defining moment in a person's life. See [[events in Gramps|events]] for the use in genealogy, for predefined events in Gramps and suggested naming for [[Events_in_Gramps|common events]].

;event role: The [[#role|role]] a [[#person|Person]] plays in an [[#Event|Event]]. The focal Person(s) holds a [[#primary|'''''Primary role''''']] in personal Events and the Family holds a [[#family_role|'''''Family role''''']] in Family events. In Gramps, an Event can be linked to as many participants as desired. Each [[#person|Person]] may participate in different roles but more than one Person might play the same role. The Event Role captures this and can be changed in the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]]. Some common Roles are pre-defined but the user can add other [[#custom|custom]] Roles by just typing in the appropriate new label into the [[#selector_combo_box|selector combo box]].
:Pre-defined Types of Event Role: [[#aide|Aide]], [[#bride|Bride]], [[#celebrant|Celebrant]], [[#clergy|Clergy]], [[#family_role|'''''Family''''']], [[#godparent|Godparent]], [[#groom|Groom]], [[#informant|Informant]], [[#primary|'''''Primary''''']], [[#witness|Witness]], [[#unknown|'''''Unknown''''']], ''[[#custom|custom]]''

;event type: The general denominator to which an event belongs, <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, a christian, civil, tibetan, ... marriage, are all denoted by the event type ''marriage''. See [[events in Gramps]] for an overview.

==F==
;Fallback events:
:Certain [[#event|event]] types are definitive bookends marking the beginning or end of a life (Birth/Death) or relationship (Marriage/Divorce). Those bookend events are key factors in any kind of timeline analysis.
:If the definitive event types are missing, Gramps will look for similar event types to calculate a 'fallback' approximation. When dates are shown in italics, it indicates that the preferred bookend event was not found and one of the [[Events_in_Gramps#Fallback_Events|pre-defined Fallback events]] had to be used. Markers for some fallback events can be customized using the '''Genealogical Symbols''' tab of [[#preferences|Preferences]].

;Family:
#[[File:Gramps-family.png|right]]'''Family''' ''({{icon|fami}} [[#primary_object|prim. obj.]])'' - Contains the information specific to relationships between people. The information may be edited directly using the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_relationships|Edit Family]]}} dialog. This traditionally contains one or two parents and zero or more children. A family unit is created in Gramps by [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_brief#Specifying_a_relationship_using_the_Relationship_View|adding Parents to an individual]], by [[Add_a_spouse|adding a partner/spouse]] to an individual, or by adding a family first then adding the people. (A family can even consist of just the offspring.) The Family relationship is a core concept in Gramps. It depicts the basic relations between people. Commonly this will contain a father, a mother and some children, however, it can also contain only parts of this (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, two brothers, a mother and child). People can be part of several families (adoption, remarried, ...)
#'''Family''' ''([[#event_role|event role]])'' An event can be coupled to a family, denoting that the both partners were equally involved in the event. Typically, the Marriage event will be coupled to a family with event role ''family''. '''Family''' is the ''default'' role when adding a new Event in the [[#edit_family|Edit Family]] dialog.

;File Chooser:
:Picking external files or folders for import, export, reports and media is done using a File Chooser dialog from [https://wikipedia.org/wiki/GTK GTK] (formerly known as "GIMP ToolKit" and "GTK+") rather than those of the native Operating System. While generally familiar, the '''[[Gramps_{{man version}}_Wiki_Manual_-_Settings#File_Chooser|GTK File Chooser]]''' has customizable features, [[#context menu|context menus]], options and keybindings that are documented in the [[Gramps_{{man version}}_Wiki_Manual_-_Settings|Settings]] section of the manual.

;File formats:
: File formats repackage the Tree database information for archiving, data exchange with other software or display.
:* '''[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Import]] formats:''' GRAMPS v2.x database (obsolete) <code>.grdb</code>, Comma Separated Values <code>.csv</code> with [[Gramps_{{man version}}_Wiki_Manual_-_Settings#CSV_Dialect|configurable delimiter dialects]], GEDCOM (Genealogical Data Communication) <code>.ged</code>, GeneWeb <code>.gw</code>, Pro-Gen <code>.def</code>, vCard (virtual contact card) <code>.vcf</code>, JSON (JavaScript Object Notation) <code>.json</code>, SQLite <code>.sql</code>
:* '''[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|Export]] formats:''' Gramps native XML format (compressed & uncompressed variants) <code>.gramps</code>, Gramps Package (Gramps XML plus media) <code>.gpkg</code>, GEDCOM (Genealogical Data Communication) <code>.ged</code>, GeneWeb <code>.gw</code>, Web Family Tree (a GEDCOM variant) <code>.ged</code>, vCalendar <code>.ics</code>, vCard (virtual contact card) <code>.vcf</code>
:* [[Output_formats|'''Output formats''']] including: Comma Separated Values <code>.csv</code> with [[Gramps_{{man version}}_Wiki_Manual_-_Settings#CSV_Dialect|configurable delimiter dialects]], Data-Driven Documents (D3) <code><code>.d3</code></code>, Graphviz graph description language <code>.dot</code>, Hypertext Markup Language <code>.html .htm</code>, LaTeX <code>.tex</code>, Open Document Text <code>.odt</code>, Portable Document Format <code>.pdf</code>, Plain Text <code>.txt</code>, PostScript <code>.ps</code>, Print (hardcopy), Rich Text Format <code>.rtf</code>, Scalable Vector Graphics <code>.svg</code>, vCard (virtual contact card) <code>.vcf</code>, Extensible Markup Language <code>.xml</code>

;Filter:
: A [[Gramps_{{man version}}_Wiki_Manual_-_Filters|filter]] (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> query) in a database finds (or hides by 'filtering out') records, displaying only those records that match certain criteria. (The criteria are comparison or query [[#rule|rules]] describing some attribute of a record.) Layers of criteria can be applied but each layer requires additional processing and slows performance of the interface.
: The [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Filter_vs._Search|basic Search]] is a single criteria filter. The search value is compares only one attribute of a record that has been selected from a pop-up menu.
: The '''[[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Filter|Filter Gramplets]]''' will compare several predefined common attributes simultaneously with simplified access to changing the search value. The default is for exact matching but [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Regular_Expressions|Regular Expressions (RegEx)]] can be used for pattern matching. A Custom Filter may be also layered in.
: A [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Custom_Filters|Custom Filter]] adds richly complex [[#rule|Rules]]-based comparison with [[Example_filters|layers of intersection]] options for those rules. Custom Filters allow repeatable filters to be created with pre-defined rules and values to be matched. Beyond interactively hiding (or revealing) records in views, Custom Filters are used to set limits for exporting, setting scopes for reports, and targeting tool actions.
: In addition to the [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Which_filter_rules_in_which_Category.3F|builtin rules]] for filtering, [[Addon:Rule expansions]] are available for Custom Filters.

==G==
;GEDCOM:
# Acronym: '''Ge'''nealogy '''D'''ata '''Com'''munication
# A format for [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#GEDCOM_import|importing]] and [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|exporting]] genealogical data. The <abbr title="an open standard is a standard that is publicly available and has various rights to use associated with it, and may also have various properties of how it was designed such as 'open process.' There is no single definition and interpretations vary with usage.">open</abbr> specification for the [https://www.familysearch.org/developers/docs/guides/gedcom GEDCOM format] was developed by The Church of Jesus Christ of Latter-day Saints (LDS Church) as an aid to genealogical research. The long standing standard release was version 5.5 in 1996 with a 5.5.1 draft update presented for comment in 1999. (Belatedly, the 'draft' label was officially removed in the annotated 2019 release. After 20 years as the de facto standard format, it remained unimproved excepting for 2 tags and the copyright.)
::As an Open Standard, there are extensive and constantly changing incompatibilities between implementations and data loss when transferring GEDCOM formatted data between competing software tools is common. Gramps has implemented a variety of [[GEDCOM|GEDCOM support features]].
::GEDCOM [https://www.familysearch.org/developers/docs/guides/gedcom-x X proposed in 2012] and [https://blog.eogn.com/2019/10/04/the-proposed-gedcom-5-5-5-standard-is-a-better-gedcom/ 5.5.5 proposed in 2019] are improvements that have not gained the approval of the copyright holder. As of June 2021, these proposals have been superseded by the GEDCOM 7.0.1 version.

;Godparent: ''([[#event_role|event role]])'' - A term to refer to the person who presents a child at a christening or baptism and promises to take responsibility for guiding the child emotionally, practically, and spiritually. This person will be referred to as ''godfather'' or ''godmother'' after the christening or baptism. See also: ''[[Add_a_godfather-godmother|Add a godfather-godmother]]''.

;Gramplet: A [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#definition|Gramplet]] is a plug-in (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Software_widget widget] or [https://wikipedia.org/wiki/Applet applet]) that can be [[#dock|docked]] in the {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]] category view. Later [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|sidebar or bottombar]] were added to the remaining [[#view|views]] to extend [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Gramplet_Bar_Menu|adding]] and [[#undock|undocking]] a Gramplet functionality of those view.
: Gramplets dynamically update as the different records are selected in the main display area of a view. Gramplets typically create an alternate interface to your Family Tree data. Collections of [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Summary_of_Gramplets|builtin]] and [[{{man version}}_Addons#Addon_List|"3rd party addon"]] gramplets are available for [[{{man version}}_Addons#Installing_Addons_in_Gramps|installation]] and download with the [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager|Plug-in Manager]]. The Plug-in Manager also regulates a [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Aren.27t_all_Plugins_also_Gramplets.3F|wide variety of other builtin and addons]] which can expand functionality unrelated to the interface.
: ''See the [[Gramplets development]] for independent information.''

;Gramps for Desktops: [https://gramps-project.org/blog/features/ Gramps] is an open-source genealogy application, a free software project and community.
: '''Gramps''' is an affectionate nickname for a "Grandfather". Originally, the all capital letter [https://wikipedia.org/wiki/Backronym backronym] stood for "'''G'''enealogical '''R'''esearch and '''A'''nalysis '''M'''anagement '''P'''rogramming '''S'''ystem" and was coined by Larry Allingham. ([https://gramps-project.org/blog/2006/04/looking-back-over-5-years/ GRAMPS was created around 2001] by [[User:Don|Don Allingham]] for use by his father, Larry.) This backronym was phased out around March 2010 in favor of '''Gramps''' as the official name of the software. All upper-case acronym-based names have become unfashionable for software.''

;Gramps Web for Servers: [https://gramps-project.org/blog/web/ Gramps Web] is collaborative interface (frontend) and backend created by David M. Straub for running the Gramps genealogy database engine on servers. It is one of the [[Web_Solutions_for_Gramps|Web Solutions for Gramps]].
: It is a multi-user system genealogical web application with different levels of options for Visitors, Members, Contributors, Editors, and Owners. Trees in [[https://www.grampsweb.org Gramps Web on a server]] can be synchronized with the more mature and feature laden [[#gramps|Gramps for Desktops]]. Single Tree or multiple Tree sites can be self-managed on a hosted service from an ISP, leased from a managed hosting ISP, or leased from an application-specific fully managed CMS provider, or installed locally for access from a local area network.

;Graphical User Interface (GUI): A visual way of indicating interactive features of a computer operating system or application/program.
:The '''Gramps for Desktops''' GUI is introduced in [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|Visual Guide to Gramps Interface]]. It uses a "windows, icons, menus, pointer" ([https://wikipedia.org/wiki/WIMP_(computing) WIMP]) based approach with [https://wikipedia.org/wiki/Post-WIMP post-WIMP] elements like hyperlinked redirection and custom interface objects. The desktop interface is built with [https://wikipedia.org/wiki/GTK Gtk] (the Gimp Toolkit), a free and open-source cross-platform widget toolkit for creating graphical user interfaces.
:The appearance and interaction may vary by conventions dictated by the [[Download|Operating System (OS)]], installation option (such as [[Portal:Translators|language localization support]] or [[{{man version}}_Addons|addon/plug-in]]), [https://wikipedia.org/wiki/Theme_(computing) theme] (at the OS or [[Addon:ThemePreferences|internal]] levels), and/or [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Preferences|user preferences customization]].
:The specific interface elements are identified by customary name, general appearance & behavior in the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|Visual Guide to Gramps Interface]]. Expansion interface elements are described in the user documentation for [[{{man version}}_Addons|each specific addon]].
: The '''Gramps Web''' GUI (or frontend) is a platform-agnostic web browser interface built with the [https://lit.dev/ Lit] lightweight JavaScript library for building fast, interoperable web components. Although the hosting side requires a webmaster with significant skills, genealogical collaborators can use web browser on almost any device.

;Groom: ''([[#event_role|event role]])'' - A term to refer to the man at a marriage who will be referred to as ''husband'' after the marriage. See also: ''[[Add_a_spouse|Add a spouse]]''.


;GUI: An acronym. ''see [[#graphical user interface|Graphical User Interface]]''.

==H==
[[File:Gramps Go-Home48x48 win.png|right]]
;Home Person: ''(core concept)'' - The persistently designated '''Home Person''' is the foundational [[#person|Person]] (the [[Genealogy_Glossary#proband|Proband]], [[Genealogy_Glossary#progenitor|Progenitor]], or [[Genealogy_Glossary#progenitrix|Progenitrix]]) in the Tree (the currently open Gramps database). This Person is the central target of genealogical research and family references extend from this center. Ideally, every person, event and source in the Tree will (however directly or indirectly) relate back to the '''Home Person'''.
: By default, the database reports describe everything else in contextual relation to this person. The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Status_Bar_and_Progress_Bar|Status Bar]], the [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Quick_View|Quick View]] called "[[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Relation_to_Home_Person|Relation to Home Person]]", and the Third party addon [[#gramplet|Gramplet]] called "[[Addon:Deep_Connections_Gramplet|Deep Connections]]" all describe different aspects of the relationship of the [[#active_person|Active Person]] to the '''Home Person'''.
: You (or your client) are customarily designated ([[Gramps_{{man version}}_Wiki_Manual_-_Settings#Setting_Home_person|set]]) as the Home Person. And this ''Home'' designation serves as a persistent point of reference for the rest of the Tree in Reports generally and for the Active Person in detail. But a different '''Home Person''' might be temporarily [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Setting_Home_person|set]] when generating reports or when researching a complex biography or obituary.
: Fascinating tidbits often lure Gramps researchers into wandering off-course. When the [[#active_person|Active Person]] has become lost, the bearings can be instantly regained by navigating the [[#active_person|Active Person]] selection back to the '''Home Person'''.
: Navigate to '''Home Person''' - ''keyboard shortcut'' {{man key press|Alt|Home}} or press the toolbar [[File:Gramps_Go-Home48x48 win.png|text-bottom|20px]]{{man button|Home}} button.
: The custom filter rule for finding the '''Home Person''' is in a People category filter under the General filters and was named 'Default person' until the 5.1 version.

==I==
;Informant: ''([[#event_role|event role]])'' - A term to refer to the [[#role|Role]] of Person who reports an [[#event|Event]].

==J==
;JSON: Acronym: [https://wikipedia.org/wiki/JSON '''J'''ava'''S'''cript '''O'''bject '''N'''otation]. JSON is a lightweight, text-based data format designed to be easy for humans to read while still structured enough for machines to parse efficiently. It organizes data in key-value pairs, allowing information to be grouped together in a clear and straightforward way.

==K==
;Keybinding: Keyboard shortcuts (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> hotkeys) key (or combination of keys) that can be used to navigate a Graphical User Interface (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [[#gui|GUI]]) as an alternative to using the mouse. A single keystroke (or combination of keys on a keyboard) executes a command.
:''see [[Gramps_{{man version}}_Wiki_Manual_-_Keybindings#toc|Gramps GUI keybindings]]''

==L==
==M==
;Matronym:
:''([[#name_origin|Name origin]] attribute)'' - Personal name based on the name of one's mother

;[[File:Gramps-media.png|right]]Media: ''({{icon|medi}} [[#primary_object|prim. obj.]])'' - Contains the information related to a media object. Media objects include images, videos, audio recordings, documents, webpages or any other type of related files.
:When new Media objects are edited from the Gallery tabs of Object Editors or from the Media category view, the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_media_objects|New Media editor]] allows the metadata to be modified.

;[[File:Gramps_Merge48x48_win.png|right]]Merge
:To combine the objects in two selected rows in a [[#view_category|category view]] into a single object. This reduces duplicates while consolidating references and [[#secondary_object|secondary objects]]. The [[Merging_people|merge process]] involves selecting two rows (a target row to be kept and a row to be deleted) then choosing '''Merge''' from the Toolbar or Edit menu. Choices are offered about which secondary objects take precedence when there are conflicts, but no data (except one of the descriptions in an Event merge) is lost by default. All secondary objects from both selected rows are conveyed to the surviving merged row. Only two objects may be merged at a time unless using addon tools designed for multiple object merges or batches of merges.

;Mode:
:''See [[#viewmode|View mode]]''

==N==
;Name Origin:
:An optional attribute (characteristic) identifying how a name was derived for a [[#person|Person]]. Pre-defined items of the [[Names_in_Gramps#Origin_Attributes|origin selection menu]] include: inherited, patrilineal, matrilineal, given, taken, [[#patronymic|patronymic]], [[#matronymic|matronymic]], feudal, pseudonym, occupation. The Name Origin of [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Multiple_Surnames|Multiple surnames]] and [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Names|Alternative names]] can be added from the [[#edit_person|Edit Person]] dialog.
: ''Available as a standard attribute of [[Names_in_Gramps|Names in Gramps]].''

;Navigator:
: ''([[#gui|graphical user interface terminology]])'' - The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Navigator|Navigator]] is a Gramps-specific name for a left sidebar layout of [[#category|category]] view icons, allowing movement between (aka 'navigating') the different View categories. There are [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Switching_Navigator_modes|multiple layout modes]] and a [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Environment_Settings|text label preferences option]] for the sidebar. This sidebar may be hidden or revealed from the menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Navigation#View|View ->Navigator]]}} or by using the [[Gramps_{{man version}}_Wiki_Manual_-_Keybindings#7|keybinding]]. Navigator layout modes are 'Sidebar' type [[#plugin|plugins]] that can be added, removed, hidden or revealed using the Plugin Manager.
: Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of [[#category|Categories]], each with their own View. Each of the Category Views displays a smaller, more digestible portion of the total information that comprises a Genealogical Tree. The View categories are: {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]], {{icon|peop}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People]], {{icon|rela}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships]], {{icon|fami}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Families_Category|Families]], {{icon|ance}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]], {{icon|even}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Events_Category|Events]], {{icon|plac}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places]], {{icon|geog}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography]], {{icon|sour34}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources]], {{icon|cite}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Citations_Category|Citations]], {{icon|repo}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Repositories_Category|Repositories]], {{icon|medi}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Media_Category|Media]], {{icon|note}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Notes]]

;[[File:Gramps-notes.png|right]]Note: ''({{icon|note}} [[#primary_object|prim. obj.]])'' - Contains the information representing a textual brief record of facts and how it [[#reference|references]] other objects in the Tree. Notes can be added to any object at any any level of the Tree and are often used to detail the context of that record in the Tree.
:Records in the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Note Category]] contain free-form text with [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Note_markup_and_preformat_in_reports|basic formatting]] and [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Link_Editor|linking]] features. Notes can be categorized by [[#tag|Tag]] and [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#note_type|Type]] in addition to the object to which it is attached. That information is created and modified using the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_notes|Notes Editor]].

==O==

;Object: The most basic framework unit of genealogical data as structured in the Gramps [[Gramps_Data_Model|data model]].
:The most complex structures are the [[#primary_object|Primary Object]] of a [[#category|category]]. Each has an [[#object_editor|Object Editor]] that organizes entering data in that structure but also allows attaching or creating [[#secondary_object|secondary objects]].

;Object Editor ''(<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> Edit Object dialogs)'':
: ''(core concept)'' - The object editor dialogs show the basic info of the [[#primary_object|Primary Object]] in the structured form of the header area where it can be directly edited. And the bottom tabbed section allows the editing of interrelationships with [[#secondary_object|secondary objects]] and provides access to the Object Editors for those secondary objects.
:Click the following links for instructions of how to open and use each type of Edit Object dialog.
:The available categories of object editor dialogs are: {{icon|peop}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_people|Edit Person]]}}, {{icon|fami}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_relationships|Edit Family]]}}, {{icon|even}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_events|Edit Event]]}}, {{icon|plac}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_places|Edit Place]]}}, {{icon|sour34}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_sources|Edit Source]]}}, {{icon|cite}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_source_citations|Edit Citation]]}}, {{icon|repo}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_repositories|Edit Repository]]}}, {{icon|medi}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_media_objects|Edit Media]]}}, {{icon|note}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_notes|Edit Note]]}}
:The available categories of object reference editor dialogs for [[#sharing|shared objects]] are: {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Person_Reference_Editor|Person Reference Editor]]}} ''(see [[#association|Associations]])'', {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Child_Reference_Editor|Child Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Place_Reference_Editor|Place Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Repository_Reference_Editor|Repository Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Media_Reference_Editor_dialog|Media Reference Editor]]}}

;Officiator: ''([[#event_role|event role]])'' - A term to refer to the role of a person authorized to conduct an official duty or function. (Such as performing a marriage or funeral ceremony or conferring a vocational degree.) Jurisdiction may be derived from a from holding a position of civil or religious authority. Use 'OFFICIATOR' rather than 'Officiant' for [[#gedcom|GEDCOM7]] Roles compatibility.

==P==
;patronym:
:''([[#name_origin|Name origin]] attribute)'' - Personal name based on the name of one's father.

;[[File:Gramps-person.png|right]]Person: ''({{icon|peop}} [[#primary_object|prim. obj.]])'' - Contains the information specific to an individual person in the People category. The information may be edited directly using the [[#edit_person|Edit Person]] dialog.

;[[File:Gramps-place.png|right]]Place: ''({{icon|plac}} [[#primary_object|prim. obj.]])'' - The Gramps concept of a Place is a particular location independent of time. Over time, the same Place may have different hierarchical (or name) information due to changing borders and political situation. For example, Leningrad and St. Petersburg represent the same place, but with different names. Places in Gramps are stored in a hierarchy and are direct accessed via the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places category view]]. Places can be defined (or refined) through the Place Editor and shared with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Select_Place_selector|Select Place]] object selector. A Place consists of:
:* Descriptive Title
:* Name (with optional date span and language attributes)
:* A list of alternative names for the place
:* Type ([[#administrative_division|administrative divisions]] such as country, state, county ...)
:* Longitude/Latitude
:* Code (such as a country code or postal code)
:* A hierachical list of regions which enclose the place

;plugin: (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Plug-in_(computing) plug-in])
:* A type of [[Writing_a_plugin|expansion framework that allows Gramps customization]] by providing interface hooks to recognize and use external code.
:* A customized module of code built to provide a specific feature or functionality that is not part of the core program.
:The [[Addon_list_legend#Type|various types]] of Gramps plugin code modules can be enabled or disabled via a [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager|plugin manager]]. Plugin types include: Citation formatter, [[Database_Backends|Database]], Doc creator, Exporter, [[#gramplet|Gramplet]], Gramps View ([[#view|''Category'']] or [[#viewmode|''mode'']]), Importer, [[Map_Services|Map Service]], Plugin lib, [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Quick_Views|Quickreport'''/'''Quickview]], Relationships, [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_1|Report]], [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Add_Rule_dialog|Rule]], Sidebar, Thumbnailer [[Gramps_{{man version}}_Wiki_Manual_-_Tools|Tool]].
:Plugins can be builtin ''(included with the normal distribution of Gramps)'' or an [[{{man version}}_Addons#Addon_List|addon]] ''(installed via the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Third_party_addons_management|Third party addons management]] in Preferences)''.

;POSIX: [https://wikipedia.org/wiki/Posix Portable Operating System Interface]: a family of OS standards specified by the [https://wikipedia.org/wiki/IEEE_Computer_Society IEEE] Computer Society for maintaining compatibility with variants of Unix (such as Linux) and other operating systems. Although the MacOS is "POSIX-certified", the term is used in this manual to generically refer to just the "Mostly POSIX-compliant" Linux and BSD distributions [[Download#Linux_and_BSD_distributions|with verified Gramps downloads]] and which use the POSIX-style [https://wikipedia.org/wiki/Filesystem_Hierarchy_Standard environment].

;Preferences: The {{Man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Preferences|Preferences]]}} is an option in the {{Man menu|Edit}} main menu that allows '''''global''''' customization of the appearance, defaults and behavior of Gramps. The customizations are categorized into the following tabs: {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Data|Data]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#General|General]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Family_Tree|Family Tree]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Import|Import]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Limits|Limits]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Colors|Colors]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Genealogical Symbols|Genealogical Symbols]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#ID_Formats|ID Formats]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Text|Text]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Warnings|Warnings]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Researcher|Researcher]]}}.
:(A {{man label|[[Addon:ThemePreferences|Theme]]}} tab is available as an addon.)
:(see also ''{{Man menu|Configure...}}'' option in the {{Man menu|View}} main menu is an option. Those customization are limited to the currently active view and its Gramplets. The feature may also be accessed by the {{man button|Configure...}} toolbar icon.)
:The Gramps 5.1 and older preferences are categorized into the following tabs: {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#General|General]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Family_Tree|Family Tree]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Display|Display]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Text|Text]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#ID_Formats|ID Formats]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Dates|Dates]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Researcher|Researcher]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Warnings|Warnings]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Colors|Colors]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Genealogical Symbols|Genealogical Symbols]]}}.

;Prerequisites: Additional software required to make certain features of Gramps work and or some [[:Category:Prerequisites|addons]].

;Primary object: Primary objects are the [[Using_database_API|data structures]] at the top level of a [[Gramps_Data_Model|hierarchical collection of records]] in the Gramps [[Gramps_Data_Model|data model]]. Beside the main structure of data, they can contain a hierarchy of [[#secondary_object|secondary objects]], and can be referenced by other primary or secondary objects. In the Gramps database, primary objects and the secondary objects that they contain are stored as separate records. Each primary object type is stored in a separate table. See [[Using_database_API#Primary_Objects|Using database API, Primary Objects]] (see also ''[[#secondary_object|secondary object]]'')
: The types of [[Using_database_API#Primary_Objects|primary objects]] are:
: {{icon|cite}} [[#citation|Citation]], {{icon|even}} [[#event|Event]], {{icon|fami}} [[#family|Family]], {{icon|medi}} [[#media|Media]], {{icon|note}} [[#note|Note]], {{icon|peop}} [[#person|Person]], {{icon|plac}} [[#place|Place]], {{icon|repo}} [[#repository|Repository]], {{icon|sour34}} [[#source|Source]], [[File:16x16-gramps-tag.png]] [[#tag|Tag]].

;Primary role: ''([[#event_role|event role]])'' - A term to refer to the [[#role|role]] of the focal participant of an [[#event|Event]]. '''Primary''' is the ''default'' role when adding a new Event in the [[#edit_person|Edit Person]] dialog.

;[[File:gramps-lock.png|right]]Private flag or tag:
: The Private option identifies sensitive information that should be redacted when sharing data or printing reports. ''(This marker should not be confused with the generic user-definable [[#tag|Tags]] used for custom filters and color highlighting.)'' Records are shown with: a [[File:22x22-gramps-lock.png]]locked padlock when private; and, an [[File:22x22-gramps-unlock.png]]unlocked padlock when public. Clicking the padlock icon toggles between Private & Public flags. This manual override supplements the automated [[Gramps_{{man version}}_Wiki_Manual_-_Probably_Alive|Probably Alive]] and custom [[Filter|Filter]] features which help Gramps to respect Personal Privacy.
:Gramps is a single user database and omits the typical security features of a multi-user system. So even "Private" data will be accessible from within Gramps. However, generating reports and exporting data default to redacting information flagged as Private.

;[[File:gramps-unlock.png|right]]Public tag or flag:
: The Public option identifies information that should be included when sharing data or printing reports. Records are shown with: a [[File:22x22-gramps-unlock.png]]unlocked padlock when public; and, an [[File:22x22-gramps-lock.png]]locked padlock when private. Clicking the padlock icon toggles between Public & Private flags. By default, all records are created as Public.

==Q==
;Quick View: On-screen [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Quick_Views|reports]] about information surrounding the active object that do not print or save to file. Generally the report is selected from a [[#context_menu|context menu]] for the selected category of record and will have no configurable options.
: The [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Quick_View|Quick View '''gramplet''']] refreshes a builtin [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Quick_Views|builtin]] or [[{{man version}}_Addons#Addon_List|addon]] QuickView reports as the focus of the active record is changed. The specific QuickView report is selected in a view configuration dialog opened with the {{man menu|View -> Configure...}} menu.

==R==
;Reference: The basic system of linking relationships between objects in Gramps. When an object is added in the Editor for record, a [[References#definition|Reference]] (link) is created in the object that was added.

;[[File:Gramps-relation.png|right]]References tab: When objects of Gramps are linked, the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#References|References tab]] lists the objects to link toward it.

;Regular Expressions: [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Regular_Expressions|RegEx]] is a system to specify a text string pattern for comparing and matching. Optionally used to extend a power of the Filter Gramplets and Custom Filters rules.
:Filters in [https://gramps.discourse.group/t/which-regex-syntax-does-gramps-use/2278/8 Gramps use the RegEx format specified by the installed version of Python]

;Re-order
:[[File:Stock_reorder.png|right]]To change the sequence of items within a list of [[#secondary_object|secondary objects]]. [https://gramps.discourse.group/t/re-ordering-data-in-gramps-topic-expansion-outline-for-wiki/5568 The interface for (and consequences of) re-ordering that sequence varies based on the list type.]
:The natural order of a list follows when the data was created. The first item in an ordered list is often considered the primary or preferred item of that type. The primary/preferred may be the only object considered in some charts and analyses. So when data entry of related objects was out of sequence, a re-ordering option becomes necessary.
:Re-ordering affects display order in the Tree, charts, and most reports. Note that in some contexts, dates can override the manual order, particularly for Places and Names.

;[[File:Gramps-repository.png|right]]Repository: ''({{icon|repo}} [[#primary_object|prim. obj.]])'' - Contains the information related to a physical or virtual structure where genealogical and family history sources are stored. Once a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_repositories|Repository is added]] to a Gramps Tree, it can used to organize [[#source|Sources]].

;Role: Function performed or part played by a person (or other Gramps [[#object|object]]) in a particular situation. When objects of Gramps are linked, a Reference is created where the implicit Role disambiguates the relative nature of the reference. ''For explicitly defined roles, see [[#event_role|event role]] and [[#association|association role]]''

;Romanization:
: Linguistic representation of a word in the Roman (Latin) alphabet

;Rule: A pre-defined abstraction that simplifies the interface for a structured query about a particular facet of your family tree. Rules allows users to choose search criteria without needing to understand the intricate details of the actual database query language. Rules are layered via the [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Custom_Filters|Custom Filters]] interface to [[#filter|filter]] with complex criteria.

==S==
;Secondary object: Secondary objects are contained within other [[#object|objects]] of the structured Gramps [[Gramps_Data_Model|data model]], and cannot be referenced directly. They can contain other secondary objects. Examples include: Name, Date and Address. See [[Using_database_API#Secondary_Objects|Using database API, Secondary Objects]] (see also ''[[#primary_object|primary object]]'')

;Selector combo box: ''([[#gui|graphical user interface terminology]])'' - a [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Combo_Boxes|standard text entry box paired with a pull-down list button]] is a [https://docs.gtk.org/gtk3/visual_index.html Gtk toolbox widget] (based on the standard [https://wikipedia.org/wiki/Combo_box combo box]). The combination of a drop-down list and a single-line editable textbox allows the user to either select a value from the list or key in a value directly. Moreover, keying in a value that is not already in the list will add that [[#custom|custom type]] to the drop-down list.

;Shared objects: {{icon|share}} Sharing allows an Object to be linked at multiple places in the tree. Doing so establishes a relationship or maintains single set of attributes (or [[#secondary_object|secondary objects]]) that they hold in common. ([[#role|Roles]] for shared Events define the person or family participation level.)
:'''[[#object_reference_editors|Object Reference Editors]]''' allow updates to a shared object to be reflected in all instances mentioning (referencing) that shared object. Redundantly creating object with the same information should be avoided. (So, refining a Transcription Note shared by multiple Citations will show the updated transcription in all the Citations.)
:Object descriptions are grouped in two distinct sections:
:  • The '''Reference Information''' section contains information unique to one instance.
:  • The '''Shared Information''' of an object will be seen in all instances that are linked to it.

;Selector: Combo interface box that allows you to select an object. The [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Selector_dialogs|Select Family selector]] is one example.

;[[File:Gramps-source.png|right]]Source: ''({{icon|sour34}} [[#primary_object|prim. obj.]])'' - Sources can be a person ''(family, friend, another researcher)'', thing ''(book, magazine newspaper, census)'', or place ''(courthouse, church, library, genealogical/historical society... although places might be better handled as Repositories)'' from which information comes, arises, or is obtained. After [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_sources|adding a Source]] with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#New_Source_dialog|new source dialog]] to the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources category]] of a Gramps Tree, the Source can be referenced when adding a [[#citation|Citations]] and organized within [[#repository|Repositories]]. The same Source may exist in multiple Repositories and may have different Media Types (such as book, microfilm, or electronic) and Call numbers in each Repository.
:[[Sources#Definition|[more]]]

;SQLite: ''([[Database_Backends|database backend]] engine)'' - The [https://sqlite.org/about.html SQLite project's in-process library] (also known simply as SQLite) is the ''default database engine'' used since the [[Database_Formats#Gramps_5.1|5.1]] version of Gramps. The support was extended from [[#bsddb|BSDDB]] in the 5.0 version via the [[DB-API_Database_Backend|DB-API Database Backend]].

;Swatch: ''([[#gui|graphical user interface terminology]])'' - A [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Pick_a_Color_selector|color swatch]] is a sample square of a color or color pattern. Swatches may be dragged from the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Pick_a_Color_selector|Pick a Color selector]] to apply that specific color to preferences.
:The word originally referred to sample pieces of cloth or fabric used for choosing or testing colors, patterns, or textures for interior or exterior design. It now means any small sample or representation of a larger whole and is commonly usage in the context of color representation and selection in software applications.

==T==
;[[File:gramps-tag.png|right]]Tag: ''([[File:16x16-gramps-tag.png]] [[#primary_object|prim. obj.]])'' - A custom titled and color-coded label that [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Tagging|can be created with the Organize Tags dialog and attached]] to selected {{icon|cite}} [[#citation|Citation]], {{icon|even}} [[#event|Event]], {{icon|fami}} [[#family|Family]], {{icon|medi}} [[#media|Media]], {{icon|note}} [[#note|Note]], {{icon|peop}} [[#person|Person]], {{icon|plac}} [[#place|Place]], {{icon|repo}} [[#repository|Repository]] or {{icon|sour34}} [[#source|Source]] objects for the purpose of easy identification and filtering.
: A keyword or phrase used to group the collection to produce a report. Multiple tags may be used to label and categorize objects into multiple groups when filtering by other attributes is not viable.

;Toolbar: ''([[#gui|graphical user interface terminology]])'' - The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Toolbar|Toolbar]] is a ribbon (located below the application menubar) with button shortcuts for the most widely needed functions associated with the current view. The selection of buttons changes in response to the context of the current view. (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, toolbar buttons for switching mapping [[#view_mode|view modes]] will only appear for the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography view]].)

;Typographical conventions: The [[Gramps_{{man version}}_Wiki_Manual_-_Preface#Typographical_conventions|customary formatting]] having special (and possibly peculiar) meaning when used throughout the MediaWiki driven [[Gramps_{{man version}}_Wiki_Manual|Gramps manual]] and documentation. The different typeface accents, highlighting and enclosures indicate specific parts of the Gramps [[#graphical user interface|Graphical User Interface]] ([[#GUI|GUI]]) or prompt a User activity.

==U==
;Unknown: ''([[#event_role|event role]])'' - A placeholder for when the [[#role|role]] of a participant in an [[#event|Event]] has not yet been defined. Gramps sets an appropriate default Role as each new Event type is created. But when a new participant is associated with an existing Event via Share or drag'n'drop, the Role isn't as predictable. In such a case, an Unknown placeholder is inserted.
:Any Unknown [[#event_role|Event Role]] type causes a variety of reporting problems. [[Addon:Rule_expansions#People_with_events_with_a_selected_role|(Rule_expansions)Persons and Families with Unknown Roles]] should be found and the Roles manually replaced as soon as is practical.

;User Directory: ''(core concept)'' - An alias for the file folder (directory) location where customizations (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>: preferences files, [[#addon|addons]], [[#plugin|plugins]]) are stored for the Gramps family of genealogy tools. Since this folder location varies by which Operating System and which Gramps fork has been installed, the '''User Directory''' is an 'alias' (a.k.a. placeholder) used in instructions about re-configuring Gramps.
: This alias allows [[Gramps_{{man version}}_Wiki_Manual_-_User_Directory|instructions for locating your specific '''User Directory''' file location]] to be consolidated in the documentation.

==V==
;View category: ''([[#gui|graphical user interface terminology]])'' - a [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|'''View category''']] (often simply called a "'''[[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|View]]'''") is a Gramps-specific name for the collection of [[#view mode|View modes]] (display layouts) presenting information in a structured and predictable manner. Different Views are selected from the [[#navigator|Navigator]] (left sidebar).
: Layouts are in table, outline or graphical formats, depending on the preferred way to represent how the data elements relate to one another.
: Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of [[#category|Categories]], each with their own View. Each of the Category Views displays a smaller, more digestible portion of the total information that comprises a Genealogical Tree. The View categories are: {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]], {{icon|peop}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People]], {{icon|rela}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships]], {{icon|fami}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Families_Category|Families]], {{icon|ance}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]], {{icon|even}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Events_Category|Events]], {{icon|plac}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places]], {{icon|geog}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography]], {{icon|sour34}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources]], {{icon|cite}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Citations_Category|Citations]], {{icon|repo}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Repositories_Category|Repositories]], {{icon|medi}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Media_Category|Media]], {{icon|note}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Notes]]

;View mode: ''([[#gui|graphical user interface terminology]])'' - a '''[[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|View mode]]''' is a Gramps-specific name for the display layouts presenting [[#view_category|View category]] information in a structured and predictable manner. A [[#view_category|View category]] may have alternate '''view modes''' (subcategories) of display layout. (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, Views with Table layouts might have flat listed or hierarchically grouped modes.) Navigating between View modes is from the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Toolbar|toolbar]] and [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Switching_Navigator_modes|Navigator]].
: Each mode of a category can be independently [[File:Gramps-config.png|22px]] configured. Each mode may maintain a separate object selection, filtering, and organization for its Gramplet bars.
: View data may be further subdivided with tabbed pages of layouts.

==W==
;wiki: (Hawaiian [https://wikipedia.org/wiki/Loanword loanword]) meaning 'quick'; or 'wikiwiki' meaning 'very quick'. For Gramps users, '''''[[User manual|the Wiki]]''''' (a.k.a. '''''[[User manual|Wiki Manual]]''''') refers to the collaborative website of educational material which is organized using the [https://mediawiki.org/wiki/MediaWiki MediaWiki] [https://wikipedia.org/wiki/Content_management_system content management system]. The core pages of that website being the structured reference-style [[#gramps|Gramps]] software user's operating guide. ''(Note that specific [[:Category:Tutorials|tutorial]] documents are also part of the wiki.)''
:For most internet users, the word is most often an inadvertent allusion to the 1995 [http://wiki.c2.com/?WikiWikiWeb WikiWikiWeb], the first website that builtin tools encouraging users to quickly & easily collaborate to expand the content of the site. See the term: [https://wiktionary.org/wiki/wiki 'wiki'] in [https://wiktionary.org/wiki/Wiktionary Wiktionary]

;Witness:''([[#event_role|event role]])'' - The term that applies to the people asked to be present at an event so as to be able to testify to its having taken place.

==X==
;XML: acronym: [https://wikipedia.org/wiki/XML E'''x'''tensible '''M'''arkup '''L'''anguage]. A schema used to define the expected structure of data in a text format. The system annotates a document in a way that data elements are syntactically distinguishable from identifying tags. A markup language defines a set of rules for encoding documents in a fault tolerant format that is both (marginally) human-readable and machine-readable.
: Gramps will [[Generate_XML|generate XML]] format natively in compressed and uncompressed forms identified with a <code>.gramps</code> or <code>.gpkg</code> file extension. It is the format that definitively supports every piece of genealogical data stored by Gramps. Used as the working format until Gramps 2.0 started using a ''[[Database_Backends|database backend]]'' to improve performance, XML is now the standard Tree data backup format and recommended data exchange format.
: See the [https://www.gramps-project.org/xml/ reference documentation for the versions] of Gramps [[Gramps_XML#RELAX_NG_generation|RELAX NG]] ('''RE'''gular '''LA'''nguage for '''X'''ML '''N'''ext '''G'''eneration)(<code>.rng</code>) schema XML and [[#dtd|DTD]]

==Y==
==Z==

{{man tip|1=Wiki manual|2=Please enhance the {{man label|Wiki}} - create new glossary terms and add them to the wiki manual. Glossary term IDs are more memorable & predictable if kept to all lower-case. When translating the Glossary, please leave the English ID anchors but also add translated variants of the same anchor. This allows users to look up a term in either language.

Inserting a "Glossary Term" into the Glossary list: 
<code><nowiki>;Glossary Term: Definition of the term.</nowiki></code> 
Do not replace a space in the anchor ID with an underscore. An anchor defined with a space can match both the underscore and space form, but an anchor defined with an underscore can only be referenced by the underscore form.

In a translated Glossary, add the English ID by putting an extra span around the translated header: 
<code><nowiki>;Translated Term: Translated definition of the term.</nowiki></code>

Referencing the glossary term in the Gramps wiki manual: 
<code><nowiki>[[Gramps_Glossary#glossary_term|Glossary Term]]</nowiki></code> 
(Note the optional underscores for spaces here.)

For more information about WikiMedia sections, see: 
<code>https://meta.wikimedia.org/w/index.php?title=Help:Section#id_with_space</code>

}}

[[Category:Gramps terminology|*]]
[[Category:Translators/Categories]]
[[Category:Documentation]]

Addon:Types Cleanup Tool

2026-03-18T17:00:45Z

DomoViridi: Everywhere: Type Cleanup Tool -> Types Cleanup Tool

{{languages|Addon:Types Cleanup Tool}}
{{Third-party addon}}
The '''{{man label|Types Cleanup Tool}}''' - removes custom types.

''Note: This tool is named '''Types Cleanup Tool''' when used, but '''Type Cleanup''' in the Addon Manager and the Tools menu.''
[[File:TypesCleanup-Tool-Options-dialog-addon-example-51.png|thumb|right|450px|Types Cleanup Tool - example window]]
==What is it For?==

The '''{{man label|Types Cleanup Tool}}''' searches your database for records that contain "custom" Types, provides a filtered list allowing those records to be edited, and an option to delete or rename the custom type. Custom Types are recognized by Gramps but the various reports that Gramps can generate and other applications may not recognize or handle them.

==What causes the extra (Custom) Types?==
[[Gramps_Glossary#custom|Custom types]] are created automatically by some importers, or other addons ([[Addon:Forms_Gramplet|Forms Gramplet]], for example) to supplement the standard Gramps types.

They are also created manually by the user. Typing directly into the Type [[Gramps_Glossary#selector_combo_box|selector combo box]] allows the pattern matching to select from the builtin list. But entering a value not already present in that list will create a Custom Type and insert it into the Custom submenu.

==Usage==
* Select Menu {{man menu|Tools -> Utilities -> Type Cleanup...}}

{{man warn|Warning|Proceeding with this tool may make unexpected changes to your data. While it is possible to '''Undo''' the changes made by this tool, it may be easier to recover from a backup.}}

[[File:TypesCleanup-Tool-Options-ReadingDatabase-51.png|thumb|right|450px|Types Cleanup Tool - progress window]]

This tool will display a progress window while examining the database for custom types and then display the result in the {{man label|[[Addon:Types_Cleanup_Tool#Types_Cleanup_Tool_window_results|Types Cleanup Tool]]}} window.
{{-}}
=== Types Cleanup Tool window results ===
[[File:TypesCleanup-Tool-Options-dialog-addon-example-51.png|thumb|right|450px|Types Cleanup Tool - example window]]

The {{man label|Types Cleanup Tool}} window result.

==== Left pane ====
The left pane has the list of various groupings of Types. Any grouping which has custom values will also have the [[File:RightwardsTriangleArrowhead20x20.png]] expansion button at the left. Clicking the button will [[File:DownwardsTriangleArrowhead20x20.png]] expand the submenu to list any existing Custom types.
Select one of those custom types and the [[#Right_pane|right pane]] will show the list of references that utilize the custom type. If the list is empty, the Custom Type can be removed without affecting any records.

==== Right pane ====
You can edit any of the references in the right pane by selecting one then either double-clicking or using the enter key, et cetera. Use this feature to correct the Type of any record with an accidental Custom Type. The reference will continue to be listed even if the Type has been changed. It is a best practice to re-run the Tool to verify all the Custom Types have been resolved before Removing that Custom Type.
{{-}}
[[File:Types-cleanup-tool-remove-warning-dialog-51.png|thumb|right|450px|"Remove" buttons Warning dialog]]
When a custom type is selected in the left pane, the {{man button|Remove}} button is enabled. If you want to remove this custom type from your drop-down lists in the type selectors when editing, you can use this button. However, if there are references using the type, you will get a warning that the references will not be changed. If you elect to remove the custom type anyway, it will disappear from your drop-down lists in the type selectors when editing. But if you ever edit and save an object that still uses the custom type, it will re-added to your drop-down lists of the type selectors.
{{-}}
You can also rename a custom type by changing its value in the combo entry at the bottom of the tool. You can select a standard name, or just modify the name by typing. When a different name has been selected, the {{man button|Rename}} button will become enabled. Activating this button will actually make changes to your database, modifying all of the referenced objects at once to the new name. This also causes the tool to re-scan the database, to allow the changes to be properly reflected in the panes.

It is possible to undo changes to the database objects via the usual usual Edit/Undo menu item. But note that undoing a rename which caused a custom type to be modified, will not cause that custom type to reappear in the drop-down lists in the type selectors when editing. This is a limitation of the undo function.

The {{man button|Help}} button shows this web page and selecting the {{man button|Close}} button exits the tool.

==Issues==
==See also==
* [[Gramps_{{man version}}_Wiki_Manual_-_Tools#Rename_Event_Types|Renaming Event Types]]

[[Category:Addons]]
[[Category:Plugins]]
[[Category:Developers/General]]
[[Category:Tools]]

Addon:Types Cleanup Tool

2026-03-18T16:54:09Z

DomoViridi: Note different names: Types Cleanup Tool / Type Cleanup

{{languages|Addon:Types Cleanup Tool}}
{{Third-party addon}}
The '''{{man label|Type Cleanup Tool}}''' - removes custom types.

''Note: This tool is named '''Types Cleanup Tool''' when used, but '''Type Cleanup''' in the Addon Manager and the Tools menu.''
[[File:TypesCleanup-Tool-Options-dialog-addon-example-51.png|thumb|right|450px|Type Cleanup Tool - example window]]
==What is it For?==

The '''{{man label|Type Cleanup Tool}}''' searches your database for records that contain "custom" Types, provides a filtered list allowing those records to be edited, and an option to delete or rename the custom type. Custom Types are recognized by Gramps but the various reports that Gramps can generate and other applications may not recognize or handle them.

==What causes the extra (Custom) Types?==
[[Gramps_Glossary#custom|Custom types]] are created automatically by some importers, or other addons ([[Addon:Forms_Gramplet|Forms Gramplet]], for example) to supplement the standard Gramps types.

They are also created manually by the user. Typing directly into the Type [[Gramps_Glossary#selector_combo_box|selector combo box]] allows the pattern matching to select from the builtin list. But entering a value not already present in that list will create a Custom Type and insert it into the Custom submenu.

==Usage==
* Select Menu {{man menu|Tools -> Utilities -> Type Cleanup...}}

{{man warn|Warning|Proceeding with this tool may make unexpected changes to your data. While it is possible to '''Undo''' the changes made by this tool, it may be easier to recover from a backup.}}

[[File:TypesCleanup-Tool-Options-ReadingDatabase-51.png|thumb|right|450px|Type Cleanup Tool - progress window]]

This tool will display a progress window while examining the database for custom types and then display the result in the {{man label|[[Addon:Types_Cleanup_Tool#Type_Cleanup_Tool_window_results|Type Cleanup Tool]]}} window.
{{-}}
===Type Cleanup Tool window results===
[[File:TypesCleanup-Tool-Options-dialog-addon-example-51.png|thumb|right|450px|Type Cleanup Tool - example window]]

The {{man label|Type Cleanup Tool}} window result.

==== Left pane ====
The left pane has the list of various groupings of Types. Any grouping which has custom values will also have the [[File:RightwardsTriangleArrowhead20x20.png]] expansion button at the left. Clicking the button will [[File:DownwardsTriangleArrowhead20x20.png]] expand the submenu to list any existing Custom types.
Select one of those custom types and the [[#Right_pane|right pane]] will show the list of references that utilize the custom type. If the list is empty, the Custom Type can be removed without affecting any records.

==== Right pane ====
You can edit any of the references in the right pane by selecting one then either double-clicking or using the enter key, et cetera. Use this feature to correct the Type of any record with an accidental Custom Type. The reference will continue to be listed even if the Type has been changed. It is a best practice to re-run the Tool to verify all the Custom Types have been resolved before Removing that Custom Type.
{{-}}
[[File:Types-cleanup-tool-remove-warning-dialog-51.png|thumb|right|450px|"Remove" buttons Warning dialog]]
When a custom type is selected in the left pane, the {{man button|Remove}} button is enabled. If you want to remove this custom type from your drop-down lists in the type selectors when editing, you can use this button. However, if there are references using the type, you will get a warning that the references will not be changed. If you elect to remove the custom type anyway, it will disappear from your drop-down lists in the type selectors when editing. But if you ever edit and save an object that still uses the custom type, it will re-added to your drop-down lists of the type selectors.
{{-}}
You can also rename a custom type by changing its value in the combo entry at the bottom of the tool. You can select a standard name, or just modify the name by typing. When a different name has been selected, the {{man button|Rename}} button will become enabled. Activating this button will actually make changes to your database, modifying all of the referenced objects at once to the new name. This also causes the tool to re-scan the database, to allow the changes to be properly reflected in the panes.

It is possible to undo changes to the database objects via the usual usual Edit/Undo menu item. But note that undoing a rename which caused a custom type to be modified, will not cause that custom type to reappear in the drop-down lists in the type selectors when editing. This is a limitation of the undo function.

The {{man button|Help}} button shows this web page and selecting the {{man button|Close}} button exits the tool.

==Issues==
==See also==
* [[Gramps_{{man version}}_Wiki_Manual_-_Tools#Rename_Event_Types|Renaming Event Types]]

[[Category:Addons]]
[[Category:Plugins]]
[[Category:Developers/General]]
[[Category:Tools]]

Gramps 6.0 Wiki Manual - Main Window

2026-03-18T16:15:01Z

DomoViridi: /* Combo Boxes */ Grammar

{{man index|Gramps 6.0 Wiki Manual - Getting started|Gramps 6.0 Wiki Manual - Categories|6.0}}
{{languages|Gramps 6.0 Wiki Manual - Main Window}}
{{#vardefine:chapter|3}}{{#vardefine:figure|0}}
[[File:MainWindow-example-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Example of a Gramps Main Windows]]
'''Elements of Gramps main window''' ''or'' '''A Visual Guide to the Gramps Interface'''.

Graphical User Interfaces (GUIs) are a way of arranging information on a computer screen that is easy to understand and use because it uses icons, menus, and a mouse rather than only text.

While a GUI is much more intuitive than memorizing keyboard commands, it is hard to learn from the feature documentation without knowing the feature’s name to lookup. Many elements are not labeled in Gramps to reduce clutter and maximize space for displaying Genealogical information. There are even [[Gramps_6.0_Wiki_Manual_-_Settings#Environment_Settings|preference options]] to not show text labels for the buttons (icons) in the Category Navigator panel.

So this section of the Wiki Manual gives the standardized names of Gramps screen elements. Armed with the standard names, you can more efficiently use a search engine (like Google) to find pages in the online manual that discuss that element. As an example, to search for Gramps Wiki Manual pages on the [https://www.google.com/search?q=navigator%20mode+site%3Agramps-project.org%2Fwiki "Navigator Mode" phrase], use following the Google search terms:

<code> "Navigator Mode" site:gramps-project.org/wiki +"Gramps {{man version}} Wiki Manual"</code>

This particular search even finds descriptively named illustrations of selecting the modes for the Navigator sidebar. Selecting one of those images shows a webpage about the illustration and where it is used in the documentation. Those illustrated pages tend to have greater introductory material.

If a particular screen element does not appear among the images below, look through the [[screenshots| Gramps Screenshot Gallery]]. This page shows the Gramps thumbnail screenshots that are used throughout the documentation. Click the thumbnail image to show the full sized image and variants of that image, then scroll down to the "File usage" section to find Wiki pages that illustrate the features within that [[screenshots|screenshot]]. Likewise, the [[Gramps_icon_set| Gramps Icon Gallery]] identifies the proper names of icons used throughout Gramps.

Once you are familiar with the screen elements, explore the [[Gramps_6.0_Wiki_Manual_-_Keybindings| keybindings or hotkeys]] to learn the shortcuts for features used so frequently that keyboard shortcuts have been created.

== Main Window ==

When opening a (new or existing) Family Tree database, the introductory Gramps [[Gramps_6.0_Wiki_Manual_-_Categories#Dashboard_Category|{{man label|Dashboard}} window]] will be shown in the "Display Area" with no Sidebar or Bottombar available. Upon selecting the [[Gramps_6.0_Wiki_Manual_-_Categories#People_Category|{{man label|People}} Category]] from the [[Gramps_6.0_Wiki_Manual_-_Categories#Categories_of_the_Navigator|Navigator]], the Main Window layout will be updated to show the [[Gramps_6.0_Wiki_Manual_-_Categories#Tree_View_-_Grouped_People|{{man label|"Grouped People" (List) View}}]] in the "Display Area".

The main Gramps window contains the following elements see Fig. {{#var:chapter}}.{{#expr:{{#var:figure}}+1}}:
{{-}}





{| class="wikitable" style="width: 100%;" 
| style="background-color:#E1DEDB;"| 

{| class="wikitable" style="width: 100%;" 
|-
|style="text-align:left; width: 100%; background-color:white;" | [[Gramps_6.0_Wiki_Manual_-_Main_Window#Window_Title_Bar|Window Title Bar]]
|-
|style="text-align:left; width: 100%; background-color:#F6F5F4;" | [[Gramps_6.0_Wiki_Manual_-_Main_Window#Menubar|Menubar]]
|-
|style="text-align:left; width: 100%; background-color:white;" | [[Gramps_6.0_Wiki_Manual_-_Main_Window#Toolbar|Toolbar]]
|} 

{| class="wikitable" style="width: 100%;" 
|style="text-align:center; width: 100%; padding:10px" | [[Gramps_6.0_Wiki_Manual_-_Main_Window#Search_Bar|Search Bar]] (Present only if Sidebar is not displayed.)(Not shown on Dashboard)
|}

{| class="wikitable" style="width: 100%;" 
|style="width: 20%; background-color:#F6F5F4;" | [[Gramps_6.0_Wiki_Manual_-_Main_Window#Navigator|Navigator]]
|style="width: 60%; background-color:white; padding:40px" | [[Gramps_6.0_Wiki_Manual_-_Main_Window#Display_area|Display Area]]
|style="width: 20%; background-color:#F6F5F4;" | [[Gramps_6.0_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Sidebar]] (Not shown on Dashboard)
|-
|} 

{| class="wikitable" style="width: 100%;" 
|style="text-align:center; width: 100%; padding:20px" | [[Gramps_6.0_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Bottombar]] (Not shown on Dashboard)
|-
|style="text-align:left; width: 100%; background-color:#F6F5F4;" | [[Gramps_6.0_Wiki_Manual_-_Main_Window#Status_Bar_and_Progress_Bar|Status Bar and Progress Bar]]
|} 

|+ style="caption-side:bottom; color:blue;"| Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Textual representation of Gramps interface

|} 


{{-}}
{{-}}
===Window Title Bar===
[[File:WindowTitleBar-MainWindow-example-60.png|left|thumb|650px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Example Windows Title Bar]]
{{-}}
*The Window Title Bar shows the name of selected Family Tree, the name of the Category view, Gramps application name and buttons to minimize, maximize and close Gramps. The window can also be dragged by the Title Bar.
{{-}}


=== Menubar ===
[[File:Menubar-MainWindow-example-60.png|left|thumb|650px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Example Menubar]]
{{-}}
*Menubar: The menubar ([[Gramps_6.0_Wiki_Manual_-_Navigation#Main_Menus|Main Menu]]) is located at the very top of the window (right below the window title bar) and provides access to all the features of Gramps.
*Menus are contextual - the options shown depend on which category is active.
*Clicking a menu's header label opens that particular submenu. Submenu items may be dimmed (unavailable) if they are not usable with the active item.

[[Gramps_6.0_Wiki_Manual_-_Preface#Typographical_conventions_in_the_Gramps_Wiki_Manual|Typographically]], Menu selections will look like this in the wiki manual: {{Man menu|Menu -> Submenu -> Menu Item}}.

{{man tip| Visibility of elements |Using the {{man label|[[Gramps_6.0_Wiki_Manual_-_Navigation#View|View]]}} menu, you can hide or unhide several elements of Main Window. In addition, there are Preference option to hide or reveal aspects of the elements -- such as text labels, scrollbars and Close gadgets.}}
{{-}}
==== Pull-down menus ====
[[File:Bottombar-sidebar-drop-down-menu-60.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} {{man tooltip|Gramplet Bar Menu}} the unlabeled ''Down Arrowhead'' {{man button|&or;}} pull-down menu button]]
Outside the menubar, the occurrence of the {{man button|[[Gramps_6.0_Wiki_Manual_-_Main_Window#Gramplet_Bar_Menu|Gramplet Bar Menu]]}} an unlabeled ''Down Arrowhead'' {{man button|&or;}} '''pull-down menu''' button indicates additional options are available for the interface item to its left.

What is the difference between a [[#Pull-down_menus|Pull-down]] menu and a [[#Pop-up_menus|Pop-up]] menu? Both show a mouse menu. But Pull-down menus are revealed by right-clicking on a button or marker. A pop-up menu is a context-aware menu that is revealed by right-clicking on an element on the screen.
{{-}}

==== Pop-up menus ====
Also know as the:
=====Context menu=====
[[File:Clipboard-dialog-example-context-menu-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Clipboard - with example contextual pop-up menu from right-clicking a Family]]
The most invisible interface option might be the '''contextual pop-up menu''' (aka "[[Gramps_6.0_Wiki_Manual_-_Settings#Context_menu|context menu]]").

Right-clicking an interface item (or on a selected record row in a table) will reveal a pop-up menu of shortcuts to some frequently useful features for that item (or record).

Note that the right-clicking on row in a table ''other'' than the selected (high-lighted or 'active') row still reveals the pop-up menu related to the ''selected'' row. So, left-click the row first to select then right-click for the menu.
{{-}}
[[File:QuickViewReport-EditPerson-context-menu-popup-default-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Person Editor - with example contextual pop-up menu from right-clicking the empty header space]]Right-clicking on objects is a familiar theme in GUIs. But right-clicking in the ''empty header space'' of any Object Editor is less obvious. However, this right-click will reveal another contextual pop-up menu with other shortcuts to useful reporting and navigation options.

What is the difference between a [[#Pull-down_menus|Pull-down]] menu and a [[#Pop-up_menus|Pop-up]] menu? Both show a mouse menu. But Pull-down menus are revealed by right-clicking on a button or marker. A pop-up menu is a context-aware menu that is revealed by right-clicking on an element on the screen.
{{-}}

==== Combo Boxes ====
[[File:ComboBox-example-with-pull-down-menu-button-places-editor-60.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} A custom type combo box]]
A [https://en.wikipedia.org/wiki/Combo_box combo box] is a standard text entry box paired with a pull-down list button. The button shows pull-down list for quickly selecting from a list of pre-defined types of data as well as any additional custom types.

Adding a new [[Gramps_Glossary#custom|custom type]] to the pull-down list is simple. Just enter a new term into the text box that doesn't match those of the known types. (Note that the list is case-sensitive.)

Be conservative when creating new types. Categorization becomes more confusing and sorting becomes less meaningful when there are Types that are too similar to other Types.

Some of [[Gramps_Glossary#custom|'''''Custom'' Types''']] that can be defined include: Event Attributes, Family Attributes, media Attributes, Person Attributes, [[Gramps_6.0_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#General|Event Roles]], [[Custom_Event_Types|Event types]], Family Relation types, Child Reference Types, Name Origin Types, Names Types, Note Types, Place Types, Repository Types, Source Attributes, source Media Types, URL Types and Types for [[Gramps_Glossary#filter|custom filters]].

Consolidating or removing custom types is a bit more complex. The [[Addon:Types_Cleanup_Tool|Types Cleanup]] addon tool cleanly updates records that use an outdated custom type.
{{-}}

=== Toolbar ===
[[File:Toolbar-MainWindow-example-60.png|left|thumb|650px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Example Toolbar]]
{{-}}
* The [[Gramps_6.0_Wiki_Manual_-_Navigation#Toolbar|Toolbar]] is located right below the menubar. Its buttons (icons) with text labels provide fast access to the most frequently used functions for the active screen of Gramps.
* The assortment of toolbar buttons (icons) is [https://wikipedia.org/wiki/Context-sensitive_user_interface context sensitive]. Which Tools are shown depends on which category is active. And only the buttons (icons) for submodes of the currently selected view category are included in the toolbar.
* ⚙ Configurable Options: most Category views have a [[File:Gramps-config.png]]{{man button|Configure...}} button as an alternative to choosing the {{Man menu|View > Configure...}} from the View menu, or pressing the ''Configure active view'' [[Gramps_6.0_Wiki_Manual_-_Keybindings#Common_keybindings|keyboard keybinding]]. This option opens a dialog with choices for customizing the display records in the View. Basic customizations might include choice of sorting order and choice of whether to display specific details.
* ''Configuration customizations are persistent''. They are carried over to future sessions using Gramps.
* Hovering over a toolbar button (icon) shows a tip of its function
[[File:ToolbarIcon-OpenTheToolsDialog-60.png|center|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Tip for the Tools button of the Dashboard category toolbar]]
The Toolbar can be hidden or revealed by the option in menu {{man menu|[[Gramps_6.0_Wiki_Manual_-_Navigation#View|View ->Toolbar]]}}.
{{-}}

=== Navigator ===
[[File:Navigator-MainWindow-example-60.png|left|thumb|200px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Example Navigator]]
*Navigator: The navigator is an optional sidebar located at the left of the window and allows selection of the different categories. See [[Gramps_6.0_Wiki_Manual_-_Categories#Categories_of_the_Navigator|Categories of the Navigator]]
:The Navigator is shown by default but this sidebar can be optionally hidden or revealed from the menu {{man menu|[[Gramps_6.0_Wiki_Manual_-_Navigation#View|View ->Navigator]]}} or the [[Gramps_6.0_Wiki_Manual_-_Keybindings#7|keybinding]] {{Man key press|CTRL|M}}. ({{Man key press|CMD|M}} on macOS.)

Also see:
* [[Gramps_6.0_Wiki_Manual_-_Main_Window#Switching_Navigator_modes|Switching Navigator modes]]
* You can hide the text labels by deselecting the ☑{{man label|Show text label beside Navigator buttons}} option in the {{man menu|Edit -> Preferences}} [[Gramps_6.0_Wiki_Manual_-_Settings#Environment_Settings|General]] tab.
* Navigator sidebar features (View categories, View Modes, and Navigator interface styles) can be added, removed, hidden or revealed using the Plugin Manager.

{{-}}

=== Display area ===
[[File:DisplayArea-MainWindow-example-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Example Display area]]
*Display area: The area in the center of the Gramps window is the display area. What it displays depends on the currently selected View category. [[Gramps_6.0_Wiki_Manual_-_Main_Window#Switching_Views|We will discuss Views in detail below]].
{{-}}

=== Status Bar and Progress Bar ===
[[File:StatusBar-and-ProgressBar-MainWindow-example-60.png|left|thumb|650px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Example Status Bar and Progress Bar]]
{{-}}
*Status Bar and Progress Bar: These two bars are combined and located at the very bottom of the Gramps window.
** The Progress Bar is located in the lower left corner of the Gramps window. It displays the progress of time consuming operations, such as opening and saving large Family Tree databases, importing and exporting to other formats, generating web sites, etc. When you are not doing these types of operations, the Progress Bar is not shown.
** The Status Bar is located to the right of the Progress Bar. It displays information about current Gramps activity and contextual information about the selected items. (You can also edit the [[Gramps_6.0_Wiki_Manual_-_Settings#Display_Options|Display Options Preferences]] to show the [[Gramps_Glossary#active_person|Active Person]]'s '''Relationship to the [[Gramps_Glossary#home_person|home person]]'''.)
** The Status Bar may occasionally show a passing alert, [[Gramps_6.0_Wiki_Manual_-_Error_and_Warning_Reference#Warnings|warning]] of unusual conditions. An informative {{man button|[[Gramps_6.0_Wiki_Manual_-_Error_and_Warning_Reference#Warnings|💡 Warning]]}} button with a superficial summary (like the one below) will be displayed for three minutes at the left of the Status Bar. Clicking this lightbulb icon will show details of these minor alerts.
[[File:Status-bar-warning-button-60.png|750px|thumb|left|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Gramps Main Window showing Warning button on the Status Bar]]

{{-}}

=== Bottombar and Sidebar ===

The {{man label|Gramplet Bar}} is also known as the Bottombar and Sidebar.

==== Gramplet Bar ====

The Bottombar and Sidebar can be individually hidden or revealed by options in menu {{man menu|[[Gramps_6.0_Wiki_Manual_-_Navigation#View|View]]}} or the relevant [[Gramps_6.0_Wiki_Manual_-_Keybindings#17|keybinding]]. If the Sidebar is hidden the {{man label|[[Gramps_6.0_Wiki_Manual_-_Main_Window#Search_Bar|Search bar]]}} will be displayed.
{{-}}

The Bottombar and the Sidebar allow [[Gramps_6.0_Wiki_Manual_-_Gramplets|Gramplets]] and [[Gramps_6.0_Wiki_Manual_-_Main_Window#Filters|filters]] to be displayed alongside a view.
{{-}}
===== Bottombar =====
[[File:Bottombar-MainWindow-example-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Example BottomBar]]
*Bottombar: The bottombar is located below the display area.
{{-}}

===== Sidebar =====
[[File:Sidebar-MainWindow-example-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Example SideBar]]
*Sidebar: The sidebar is located to the right of the display area.

{{-}}

====Gramplet Bar Menu====
[[File:Bottombar-sidebar-drop-down-menu-60.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Location of '''Gramplet Bar Menu''' unlabeled ''Down Arrowhead'' (&or;) Add/Remove/Restore Gramplets Menu ]]

You can also add / remove and restore the default Gramplets by clicking the {{man button|&or;}} (''Down Arrowhead'' button) also known as the '''Gramplet Bar Menu''' at the far top right of the bars titles, and then using one of the options from the drop-down menu eg:
*'''Gramplet Bar Menu'''
** {{man menu|Add a gramplet}} - Displays a list of Gramplets available for use on that '''Gramplet Bar'''
** {{man menu|Remove a gramplet}} - Displays a list of Gramplets currently shown on the '''Gramplet Bar''' available for removal.
** {{man menu|Restore default gramplets}} - Displays the {{man label|[[Gramps_6.0_Wiki_Manual_-_Main_Window#Restore_to_defaults.3F_dialog|Restore to defaults?]]}} confirmation dialog, that allows you to restore the Gramplet Bar to its default Gramplets.
** {{man menu|[[Gramps_6.0_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|Gramplet Bar Help]]}}
** {{man menu|[[Gramps_6.0_Wiki_Manual_-_Gramplets#What_is_a_Gramplet.3F|About Gramplets]]}}

A similar {{man menu|[[Gramps_6.0_Wiki_Manual_-_Categories#Add_a_gramplet|Add a gramplet]]}} menu is also available on the {{man label|[[Gramps_6.0_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard View]]}}; but only shows the {{man menu|[[Gramps_6.0_Wiki_Manual_-_Categories#Add_a_gramplet|Add a gramplet]]}} and {{man menu|[[Gramps_6.0_Wiki_Manual_-_Categories#Restore_a_gramplet|Restore a gramplet]]}} options.
{{-}}
=====Restore to defaults? dialog=====
[[File:GrampletBar-Restore-to-defaults-dialog-60.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Restore to defaults? dialog ]]

The {{man label|Restore to defaults?}} dialog, allows you to restore the Gramplet Bar to its default Gramplets. This action cannot be undone. Select {{man button|OK}} to confirm or select {{man button|Cancel}}.
{{-}}



====Search Bar====

[[File:SearchBar-MainWindow-example-60.png|left|thumb|650px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Example Search Bar]]
{{-}}
If the Sidebar is not displayed in a Category view with a list, then the {{man label|Search Bar}} is displayed instead. Available search options vary depending on Category View you are in. But a visible sidebar makes the Search Bar Invisible.
{{-}}
[[File:MainWindow-SearchBar-sidebar-hidden-example-60.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} People Category View - showing Search Bar after Sidebar has been hidden]]
[[File:PeopleCategory-sidebar-filter-enabled-60.png|450px|thumb|center|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} People Category View - showing the sidebar superseding the Search Bar]]
{{-}}
A {{man label|Search Bar}} is available for the following Views and the Select windows for the following Categories: People, Relationships, Families, Events, Places, Sources, Citations, Repositories, Media, Notes. ''Not Available in the following Category Views: Dashboard, Relationships, Charts, Geography.''

Typing the characters into the {{man label|Search Bar}} and clicking the {{man button|Find}} button will display only lines that match the text.
{{-}}
{{-}}
[[File:SelectFamily-SelectorDialog-example-60.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Example [[Gramps_6.0_Wiki_Manual_-_Categories#Select_Family_selector|Select Family selector]] - showing Search Bar]]
Note that various {{man label|Selectors}} also have search bars:
* [[Gramps_6.0_Wiki_Manual_-_Settings#Selector_dialogs|Selector dialogs]]
{{-}}

== Switching Navigator modes ==

[[File:Navigator-mode-selection-dropdownlist-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Navigator mode selection drop down list -"Category" selected ]]

You can choose the [[Gramps_6.0_Wiki_Manual_-_Main_Window#Navigator|navigator]] mode from the sidebar {{man label|Category}} drop down list:
* [[Gramps_6.0_Wiki_Manual_-_Main_Window#Category_navigator_mode_.28default.29|'''Category''']] (Default)
* [[Gramps_6.0_Wiki_Manual_-_Main_Window#Drop-Down_navigator_mode|Drop-Down]]
* [[Gramps_6.0_Wiki_Manual_-_Main_Window#Expander_navigator_mode|Expander]]

{{man tip|You may also add the {{man label|[https://github.com/kkujansuu/gramps/tree/master/addons/SimpleSidebar Simple Side bar]}} Navigator mode addon with the|Third-party Addon manager by adding the [[Gramps_6.0_Wiki_Manual_-_Navigation#Other_Projects|other project]]. It displays all views without using the category layer (although the list is displayed in category order.[https://gramps.discourse.group/t/keyboard-shortcuts-not-valid/7898/14])}}
{{man tip|To hide the {{man label|Category}} drop down list|When labels have been disabled for the Navigator in Preferences, this Category drop-down list control becomes the widest object. Its width limits how narrow the sidebar may be resized. The control can be made to disappear by using the {{man label|[[Gramps_6.0_Wiki_Manual_-_Plugin_Manager|Plugin Manager]]}} to hide (or remove) all but your single preferred Navigator ''sidebar'' mode. (When only one mode remains unhidden, there is no need for a menu and it will also become hidden.)}}
{{-}}
==='''Category''' navigator mode (default)===
[[File:Navigator-mode-selection-category-default-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Category (default) Navigator mode]]

Category Sidebar - A sidebar to allow the selection of view categories.
{{-}}

==='''Drop-Down''' navigator mode===
[[File:Navigator-mode-selection-drop-down-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Drop-Down navigator mode]]

Drop-down Sidebar - Selection of categories and views from drop-down lists.
{{-}}

==='''Expander''' navigator mode===
[[File:Navigator-mode-selection-expander-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Expander navigator mode]]

Expander Sidebar - Selection of views from lists with expanders {{man button|▶}} arrows.
{{-}}

== Switching Categories ==

Gramps comes with number of different standard [[Gramps_Glossary#viewcategory|View categories]] built in, each of which has one or more standard [[Gramps_Glossary#viewmode|View modes]]. The built-in categories are described in the introduction to the [[Gramps_6.0_Wiki_Manual_-_Categories#Categories_of_the_Navigator|Categories of the Navigator]].

{{man note|Expanding the Views|You can [[6.0_Addons|download addon]] a '[[Gramps_Glossary#view|Gramps View]]' in the General tab Preferences menu (or activate or remove previously downloaded Addon Views) via the Plugin Manager.
*If the view is a ''new mode'' (subcategory), the toolbar, menus and Navigator mode lists are modified to give access to the new layout.
*If it is a View of a ''existing category'', then the view layout is replaced for that category.
*If it is a ''new category'' of view, then an entire new visualization will be added with an additional icon appended to the navigator selections.}}

The way you change the currently displayed category depends on the navigator mode. Normally (for most navigator modes) you can select the category you want by clicking one of the navigator icons.

Alternatively you can use the [[Gramps_6.0_Wiki_Manual_-_Keybindings#4|keyboard shortcuts]] {{man key press|CTRL|N}} and {{man key press|CTRL|P}} ({{man key press|CMD|N}} and {{man key press|CMD|P}} on macOS) go to the next or previous category respectively or use [[Gramps_6.0_Wiki_Manual_-_Keybindings#45|keyboard shortcuts]] {{man key press|CTRL|Alt|<number>}} ({{man key press|CMD|OPT|<number>}} on macOS) Shortcut are only available for the first 10 categories (e.g. Repositories/Media/Notes categories miss out on shortcuts.) If you have hidden the [[Gramps_6.0_Wiki_Manual_-_Main_Window#Navigator|Navigator]] then shortcuts will be the only way to change categories until you [[Gramps_6.0_Wiki_Manual_-_Navigation#View|turn the Navigator on]] again.
{{-}}

== Switching Views ==
A [[Gramps_Glossary#viewcategory|View category]] can contain different ways of presenting the data, called a [[Gramps_Glossary#view mode|View mode]]. If there are several viewing modes, you can switch between modes interactively. The way you change between the modes depends on the Category View. The Configuration options for each mode are independently controlled.

In Views styled in tables of data with rows and columns, the modes are typically between a hierarchically grouped outline or a simple single-level sortable list. Table style view modes are configured with the [[Gramps_6.0_Wiki_Manual_-_Settings#Column_Editor|Column Editor]] and have have [[Gramps_6.0_Wiki_Manual_-_Settings#Sorting_columns|sorting]] options.

In some graphical Category Views (like [[Gramps_6.0_Wiki_Manual_-_Categories#Charts_Category|Charts]] and [[Gramps_6.0_Wiki_Manual_-_Categories#Geography_Category|Geography]]) there may be a wide variety of viewing modes.

[[File:Navigator-mode-selection-expander-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Navigator sidebar in Expander mode]]
When there are multiple viewing modes, additional icon buttons will be shown on the toolbar to switch between those different viewing modes.

You can also switch via the {{man menu|View}} menu, or the View menu [[Gramps_6.0_Wiki_Manual_-_Keybindings#6|keybindings]] by pressing {{Man key press|Ctrl|Alt|''<number>''}} (for Linux & Windows) or {{Man key press|Cmd|Alt|''<number>''}} (for macOS), where ''<number>'' corresponds to the order of viewing modes listed in the category's View menu.

Modes are also selectable from the Navigator sidebar when using the '''Drop-Down''' or '''Expander''' arrangements. The Navigator sidebar defaults to the [[Gramps_6.0_Wiki_Manual_-_Main_Window#Switching_Navigator_modes|'''Category''' arrangement]] which has no mode selector. Using the '''Drop-Down''' or '''Expander''' mode makes the additional viewing modes available as Navigator icons.
{{-}}

== Filters ==

[[File:PeopleCategory-sidebar-filter-enabled-60.png|right|thumb|400px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Filter Controls Displayed]]

Genealogical databases can contain information on '''''many''''' people, families, places, and objects. That means it is possible for a View to contain a list of data so long that is difficult to navigate. Beyond the basic ''seek-as-you-type'' [[Gramps_6.0_Wiki_Manual_-_Navigation#Finding_records|Find box]] for precision navigation of the list, Gramps gives you two different means for filtering a list to a more manageable size.

These methods are '''Search''' and '''Filtering'''.

A search will search the text displayed in list, whereas filters display people whose data match the criteria of the filter.

Search is a simple but fast method of searching the columns displayed on the screen. When the [[Gramps_6.0_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|sidebar]] is '''not''' displayed, the {{man label|[[Gramps_6.0_Wiki_Manual_-_Main_Window#Search_Bar|Search bar]]}} is displayed. Typing the characters into the {{man label|[[Gramps_6.0_Wiki_Manual_-_Main_Window#Search_Bar|Search bar]]}} and clicking the {{man button|Find}} button will display only lines that match the text.

Alternatively, you can enable a filter in either the [[Gramps_6.0_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|bottombar or the sidebar]]. When the filter sidebar is displayed, the {{man label|Search bar}} is not displayed. The Filter allows you to interactively build a set of filter rules that can be applied to the display. The filter is applied based on the rules and the data, not on the screen display. Filters of the displayed category can also be constructed by clicking on the corresponding 'editor' button in the {{man menu|Edit}} menu.

Further details of how filters work is given in the [[Gramps_6.0_Wiki_Manual_-_Filters|Filters Chapter]]

{{-}}

{{man tip| Searching vs. Filtering |Searching only searches for exact text matches. If the date displayed is "Jan 1, 2000", a search of "1/1/2000" will fail, but a filter of "1/1/2000" will match because it matches the date value rather than the formatted date.}}

When Gramps opens a Family Tree, no filtering is in effect. In People View, for example, all people in the Family Tree are listed by default.

== Troubleshooting a misbehaving interface ==
If your Gramps GUI ( Graphical User Interface ) is behaving contrary to the manner described in this guide, you may have an installation or minor compatibility issue.

It is likely that the behavior has been seen before and a solution has been identified.

Please review the [[:Category:Troubleshooting|Troubleshooting pages]]. If you are unable to discover the solution there, post a description of the problem to the general Gramps community on our [[Contact#Official|user forum]]. We help each other constantly there.
{{-}}
{{man index|Gramps 6.0 Wiki Manual - Getting started|Gramps 6.0 Wiki Manual - Categories|6.0}}
{{languages|Gramps 6.0 Wiki Manual - Main Window}}
{{grampsmanualcopyright}}

[[Category:Documentation]]
[[Category:Gramps terminology|Visual Guide to the Gramps Interface]]

Gramps Glossary

2026-03-17T23:20:34Z

DomoViridi: /* S */ Selector combo box: updated link to Manual; grammar; didactic ordering of possible actions.

{{languages|Gramps_Glossary}}
__NOTOC__
This glossary gives an overview of terms that appear in the [[features|Gramps]] genealogy software, with a short description, and a link to relevant articles. (Since knowing a feature's name is necessary for finding the corresponding glossary term, also refer to the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Main_Window|Visual Guide to the Gramps Interface]].)

For a glossary of genealogical terms, see [[Genealogy Glossary]] and [[Latin words and expressions]].

{| border="0" align="center" style="margin-top:0.4em;"
|
[[#A|A]] -
[[#B|B]] -
[[#C|C]] -
[[#D|D]] -
[[#E|E]] -
[[#F|F]] -
[[#G|G]] -
[[#H|H]] -
[[#I|I]] -
[[#J|J]] -
[[#K|K]] -
[[#L|L]] -
[[#M|M]] -
[[#N|N]] -
[[#O|O]] -
[[#P|P]] -
[[#Q|Q]] -
[[#R|R]] -
[[#S|S]] -
[[#T|T]] -
[[#U|U]] -
[[#V|V]] -
[[#W|W]] -
[[#X|X]] -
[[#Y|Y]] -
[[#Z|Z]]
|}


==A==

;Active Person: ''(core concept)'' - The person designated (or 'selected') as the momentary center of focus in the open Gramps database. The perspective of this person defines the context for actions and for displaying all the surrounding information. Changing this focus is done by [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Setting_the_Active_Person|navigating the Active Person]] selection to another person.
:The Active Person's relationship to the [[#home_person|Home Person]] defines the scope of the perspective.
:<abbr title="nota bene (singular), notate bene (plural) - Latin phrase meaning 'note well'">N.B.</abbr>: There is ''always'' an Active Person selection, even when the [[#primary_object|primary object]] (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> record) selected in the current view is not a 'Person' [[#object|object]].

;addon: (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Plug-in_(computing) add-on])
:An optional [[{{man version}}_Addons#Addon_List|'''third-party''' expansion]] to Gramps that leverages Gramps [[#plugin|plugin]] customization framework to add and [[Addons_development#Create_a_Gramps_Plugin_Registration_file|register]] a specific feature. The [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Using_the_Addon_Manager|Addon Manager]] allows installing and updating from curated collections of Addons. (These curated collections are called "Projects" in the Addon Manager.)
:Addons may not conform to the same design or code quality standards of builtin plugin modules. Use with caution!
:Optional parts bundled with the core project are called by the more generic name: builtin plugins. After installation and being registered, both the "builtin" and "addon" plugins may be disabled or re-enabled with the [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager#Registered_Plugins|Plugin Manager]].

;address: ''([[#secondary_object|sec. obj.]])'' - The Gramps concept of an Address is a particular location with an associated time frame. Think of it as a mailing address. It is intended to represent where a person lived and when the person lived there. The Address consists:
:* Date
:* Street Address
:* Locality
:* City
:* County
:* State/Province
:* Postal/Zip code
:* Country
:* Phone
:Not to be confused with a [[#place|Place]] which has a fixed position (its location). [[Why_residence_event_and_not_Address%3F|Use this with care.]] For genealogical research you can also use the residence event coupled with a [[#place|Place]]. For mailing (email, postal), add an address to a [[#person|Person]] or [[#repository|Repository]].

;administrative division: A unit of a layered system subdividing a geopolitical (geographic or political) region. Such divisions are recorded as [[#place|Place]] Types in Gramps. Meanwhile the structure of a Place Tree is built by layering via the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Enclosed_By|'Enclosed by' tab in the Place Editor.]] The subdivisions are sometimes categorized as an entity, locality, area, or region. The terms of subnational entity, constituent unit, or country subdivision tend to imply divisions that are more related to political representation than administrative.
: See wikipedia's [https://wikipedia.org/wiki/Administrative_division Administrative division] for a conceptional definition or [https://wikipedia.org/wiki/List_of_administrative_divisions_by_country List of administrative divisions by country] for specific countries.

;Aide: ''([[#event_role|event role]])'' - A term to refer to the role of an assistant.

;anglicisation:
: Process of making something English. If an immigrant (or their descendant) adopts a naturalized variation of their birth name, that [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Preferred_name_section|preferred alias]] can be added with an ''Also Known As'' [[Names_in_Gramps#Name_Types|name type]] in the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Names|Names]] tab. All aliases can be categorized by type and surname variants may be [[Grouping_Surnames|grouped]] with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Name_Editor|Name Editor]].

;Association: ''([[#secondary_object|sec. obj.]])'' - The [[#role|roles]] in [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_1#Associations|Associations]] are to explicitly define the how one person relates to another.
:Association roles are used when the relationship falls outside the implicit roles of a family relationship or the explicit roles in shared events. These custom roles convey relationships that might not readily apparent... such as a [https://wikipedia.org/wiki/Pen_pal penpal] or the [https://wikipedia.org/wiki/Eponym eponymous person] honored by a namesake. Association roles may also be used as placeholder when the actual genetic connection has not yet been discovered.
:Association roles are created and edited with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_1#Person_Reference_Editor|Person Reference Editor]], which includes no pre-defined roles. This feature starts with a blank list of [[#custom|custom types]]) and the default "Godfather" role is only shown as a hint.

;attribute: ''([[#secondary_object|sec. obj.]])'' - [[Attributes_in_Gramps|Attributes]] are for something permanent, or at least somewhat permanent: eye color, blood type, etc. Usually you would have not more than one of each attribute type for a [[#person|Person]]/[[#family|Family]]/etc. Attributes are managed from an Attributes tab in each [[#primary_object|primary Object]] Editor. There are a few pre-defined Attributes to support GEDCOM, but [[#custom|custom types]] will tend to be needed.

==B==
;Books Report:
A [[Gramps_{{man version}}_Wiki_Manual_-_Reports|Reports menu]] feature of Gramps that allows the [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_3|design or generation of a repeatable custom genealogy ''Book'']]. A Book consists of an ordered collation of Gramps textual and graphical reports in a single document. The individual report configuration options are also stored with the Book but the Book's document pagesize and print destination configuration options override.

;Bride: ''([[#event_role|event role]])'' A term to refer to the woman a marriage ceremony who will have the role of ''wife'' in the marriage. See also: ''mother''.

;BSDDB: ''([[Database_Backends|database backend]] engine)'' The [http://www.oracle.com/us/products/database/berkeley-db/overview/index.html Berkeley Software Distribution database] (also known as BSDDB) was the first ''default database engine'' used by the [[Database_Formats#Gramps_2.0|2.0]] through the [[Database_Formats#Gramps_5.0|5.0]] versions of Gramps. Originally, Gramps [[#xml|XML]] was used directly rather than as a Backup and data exchange format. The default db engine changed to [[#sqlite|SQLite]] in the 5.1 version via the [[DB-API_Database_Backend|DB-API Database Backend]]. ([[Install_latest_BSDDB|Manual updates to the BSDDB engine]] for the 5.1.3 version may be advisable.)

==C==
;Category: ''(core concept)'' Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of different descriptive schemas called Categories, each with their own [[#view|View]]. Each Category is a smaller, more digestible portion of the total information that comprises a Genealogical Tree. The View categories are: {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]], {{icon|peop}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People]], {{icon|rela}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships]], {{icon|fami}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Families_Category|Families]], {{icon|ance}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]], {{icon|even}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Events_Category|Events]], {{icon|plac}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places]], {{icon|geog}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography]], {{icon|sour34}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources]], {{icon|cite}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Citations_Category|Citations]], {{icon|repo}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Repositories_Category|Repositories]], {{icon|medi}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Media_Category|Media]], {{icon|note}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Notes]]

;Celebrant: ''([[#event_role|event role]])'' A term describing a role of the person who performs a rite, especially referring to a priest at the Eucharist.

;[[File:Gramps-citation.png|right]]Citation: ''({{icon|cite}} [[#primary_object|prim. obj.]])'' - Contains the information that enables you or others to locate your source document. An isolated [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_source_citations|Citation can be created]] without first creating separate [[#source|Source]] object. But, should the same source be referenced repeatedly in a Tree, a separate Source simplifies the Citation and eliminates redundant information that must be harmonized.

;Clergy: ''([[#event_role|event role]])'' A term applied to a religious person regardless of religion. For example, a monk or priest. See also: ''[[#celebrant|celebrant]]''.
: Religious terminology is often subject to dispute, see the [https://www.merriam-webster.com/dictionary/clergy Merriam-Webster] for an independent definition.

;[[File:Gramps_Clipboard48x48_win.png|right]]Clipboard: ''([[#gui|graphical user interface terminology]])'' - The [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Using_the_Clipboard|Gramps Clipboard]] is a shortcut system for [[#sharing|sharing]] a [[#secondary_object|secondary]] object, navigation, and custom [[#filter|filter]] creation.
: '''Usage:''' The Clipboard can be opened from a icon on the [[#toolbar|Toolbar]], from the Edit -> Clipboard menu choice or by using the Copy [[Gramps_{{man version}}_Wiki_Manual_-_Keybindings#7|keybinding]] for the Active Record in the Active main view of a View category. A floating clipboard dialog that has become buried can be brought to the top of the stack by selecting '''Clipboard...''' from the Windows menu.
: The Clipboard can greatly improve data entry efficiency, see the "[[How_to_use_the_Gramps_Clipboard|How to use the Gramps Clipboard]]" article for more information.

;Context menu: ''([[#gui|graphical user interface terminology]])'' - A [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Pop-up_menus|contextual pop-up menu]] (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Context_menu "context menu"]) is a menu that appears when right-clicking (or pressing the [https://wikipedia.org/wiki/Menu_key Menu keyboard key]) when the menu options directly relate to the item indicated by the mouse pointer. Thus, the indicated item provided the "context."

;''custom'' Types: This indicates a user-defined classification, as opposed to classifications that came pre-defined in Gramps. (i.e.: 'Birth' and 'Marriage' are 2 of the pre-defined 'types' of Events.)
:When none of the pre-defined Types are suitable, add a new ''[[#custom|custom]]'' Type by typewriting directly into the [[#selector_combo_box|selector combo box]]. If the value doesn't precisely match any of the existing menu items, a new ''custom'' Type will be created when the {{man button|OK}} button is clicked.
: Any added ''custom'' Type will remain available in that expanded menu... unless the Tree is exported and re-imported or removed via a [[Third-party_Addons|Third party addon]] Utility like [[Addon:Types_Cleanup_Tool|Type Cleanup]].
: '''''custom'' Types''' can be defined for: Event [[#attribute|Attributes]], Family [[#attribute|Attributes]], media [[#attribute|Attributes]], Person [[#attribute|Attributes]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#General|Event Roles]], [[Custom_Event_Types|Event types]], Family [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Relationship_Information|Relationship Information]] types, [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Child_Reference_Editor|Child Reference]] Types, [[Names_in_Gramps#Origin_Attributes|Name Origin Types]], [[Names_in_Gramps#Name_Types|Names Types]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_2#Note_editor_dialog|Note Types]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_2#Place_Editor_dialog|Place Types]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Repository_Reference_Editor|Repository]] Types, Source [[#attribute|Attributes]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Repository_Reference_Editor|Repository]] Media Types, [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Internet_Address_Editor|Internet Address (URL)]] Types.

==D==
;date: ''([[#secondary_object|sec. obj.]])'' - Dates in Gramps are much more complex than just a month, day, and year. Dates are always in a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Calendars|particular calendar]], can span a time frame with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_Type|Date Type]], the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_Quality|Date Quality]] can be exact (or an approximation variant), and have support for many other subtleties specific to genealogy data. The approximation can be fine-tuned with the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Limits|Limits]] preferences.
: The [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_formats_and_parsing_rules|date parsing rules]] are applied whenever data is entered into a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_dates|date text field]] or a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_selection_dialog|date selection dialog]].

;DNA:
# Acronym: '''d'''eoxyribo'''n'''ucleic '''a'''cid
# A [https://wikipedia.org/wiki/Nucleic_acid nucleic acid] that carries genetic information. Genetic testing compares for matching sequence lengths (measured in centimorgans, aka cMs) at various loci on specific chromosomes to determine common ancestry.

;Dock: ''([[#gui|graphical user interface terminology]])'' - A [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Pop-up_menus|dock]] is one of the multitude of containers offering controlled access and context to Gramplets. Gramplets can be added to, removed from, or undocked from a container to float free of the main window.
: The Dashboard was the original container and can be configured with multiple columns and stacks of Gramplets. The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|sidebar and bottombar splitbars]] are Category-specific containers. The splitbars only show a single gramplet at a time but with tabs to quickly switch between them. Each view mode has its own set of splitbars. So the basic configuration of Gramps has the Dashboard plus 24 Category view modes... or 49 separate gramplet containers.

;DTD:
:Acronym: '''D'''ocument '''T'''ype '''D'''efinition. A document that defines the tagging structure which identifies the individual components of an [https://wikipedia.org/wiki/Standard_Generalized_Markup_Language SGML] or [[#xml|XML]] document.
:See the [https://www.gramps-project.org/xml/ reference documentation for the versions] of Gramps [[Gramps_XML#RELAX_NG_generation|RELAX NG]] ('''RE'''gular '''LA'''nguage for '''X'''ML '''N'''ext '''G'''eneration)(<code>.rng</code>) schema [[#xml|XML]] and DTD

==E==
;[[File:Gramps-event.png|right]]Event: ''({{icon|even}} [[#primary_object|prim. obj.]])'' - Contains the information related to an happening. [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_events|Adding an Event record]] provides the context of an interaction of the roles of People/Families, dates & places in activities.
: An Event is a defining moment in a person's life. See [[events in Gramps|events]] for the use in genealogy, for predefined events in Gramps and suggested naming for [[Events_in_Gramps|common events]].

;event role: The [[#role|role]] a [[#person|Person]] plays in an [[#Event|Event]]. The focal Person(s) holds a [[#primary|'''''Primary role''''']] in personal Events and the Family holds a [[#family_role|'''''Family role''''']] in Family events. In Gramps, an Event can be linked to as many participants as desired. Each [[#person|Person]] may participate in different roles but more than one Person might play the same role. The Event Role captures this and can be changed in the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]]. Some common Roles are pre-defined but the user can add other [[#custom|custom]] Roles by just typing in the appropriate new label into the [[#selector_combo_box|selector combo box]].
:Pre-defined Types of Event Role: [[#aide|Aide]], [[#bride|Bride]], [[#celebrant|Celebrant]], [[#clergy|Clergy]], [[#family_role|'''''Family''''']], [[#godparent|Godparent]], [[#groom|Groom]], [[#informant|Informant]], [[#primary|'''''Primary''''']], [[#witness|Witness]], [[#unknown|'''''Unknown''''']], ''[[#custom|custom]]''

;event type: The general denominator to which an event belongs, <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, a christian, civil, tibetan, ... marriage, are all denoted by the event type ''marriage''. See [[events in Gramps]] for an overview.

==F==
;Fallback events:
:Certain [[#event|event]] types are definitive bookends marking the beginning or end of a life (Birth/Death) or relationship (Marriage/Divorce). Those bookend events are key factors in any kind of timeline analysis.
:If the definitive event types are missing, Gramps will look for similar event types to calculate a 'fallback' approximation. When dates are shown in italics, it indicates that the preferred bookend event was not found and one of the [[Events_in_Gramps#Fallback_Events|pre-defined Fallback events]] had to be used. Markers for some fallback events can be customized using the '''Genealogical Symbols''' tab of [[#preferences|Preferences]].

;Family:
#[[File:Gramps-family.png|right]]'''Family''' ''({{icon|fami}} [[#primary_object|prim. obj.]])'' - Contains the information specific to relationships between people. The information may be edited directly using the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_relationships|Edit Family]]}} dialog. This traditionally contains one or two parents and zero or more children. A family unit is created in Gramps by [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_brief#Specifying_a_relationship_using_the_Relationship_View|adding Parents to an individual]], by [[Add_a_spouse|adding a partner/spouse]] to an individual, or by adding a family first then adding the people. (A family can even consist of just the offspring.) The Family relationship is a core concept in Gramps. It depicts the basic relations between people. Commonly this will contain a father, a mother and some children, however, it can also contain only parts of this (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, two brothers, a mother and child). People can be part of several families (adoption, remarried, ...)
#'''Family''' ''([[#event_role|event role]])'' An event can be coupled to a family, denoting that the both partners were equally involved in the event. Typically, the Marriage event will be coupled to a family with event role ''family''. '''Family''' is the ''default'' role when adding a new Event in the [[#edit_family|Edit Family]] dialog.

;File Chooser:
:Picking external files or folders for import, export, reports and media is done using a File Chooser dialog from [https://wikipedia.org/wiki/GTK GTK] (formerly known as "GIMP ToolKit" and "GTK+") rather than those of the native Operating System. While generally familiar, the '''[[Gramps_{{man version}}_Wiki_Manual_-_Settings#File_Chooser|GTK File Chooser]]''' has customizable features, [[#context menu|context menus]], options and keybindings that are documented in the [[Gramps_{{man version}}_Wiki_Manual_-_Settings|Settings]] section of the manual.

;File formats:
: File formats repackage the Tree database information for archiving, data exchange with other software or display.
:* '''[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Import]] formats:''' GRAMPS v2.x database (obsolete) <code>.grdb</code>, Comma Separated Values <code>.csv</code> with [[Gramps_{{man version}}_Wiki_Manual_-_Settings#CSV_Dialect|configurable delimiter dialects]], GEDCOM (Genealogical Data Communication) <code>.ged</code>, GeneWeb <code>.gw</code>, Pro-Gen <code>.def</code>, vCard (virtual contact card) <code>.vcf</code>, JSON (JavaScript Object Notation) <code>.json</code>, SQLite <code>.sql</code>
:* '''[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|Export]] formats:''' Gramps native XML format (compressed & uncompressed variants) <code>.gramps</code>, Gramps Package (Gramps XML plus media) <code>.gpkg</code>, GEDCOM (Genealogical Data Communication) <code>.ged</code>, GeneWeb <code>.gw</code>, Web Family Tree (a GEDCOM variant) <code>.ged</code>, vCalendar <code>.ics</code>, vCard (virtual contact card) <code>.vcf</code>
:* [[Output_formats|'''Output formats''']] including: Comma Separated Values <code>.csv</code> with [[Gramps_{{man version}}_Wiki_Manual_-_Settings#CSV_Dialect|configurable delimiter dialects]], Data-Driven Documents (D3) <code><code>.d3</code></code>, Graphviz graph description language <code>.dot</code>, Hypertext Markup Language <code>.html .htm</code>, LaTeX <code>.tex</code>, Open Document Text <code>.odt</code>, Portable Document Format <code>.pdf</code>, Plain Text <code>.txt</code>, PostScript <code>.ps</code>, Print (hardcopy), Rich Text Format <code>.rtf</code>, Scalable Vector Graphics <code>.svg</code>, vCard (virtual contact card) <code>.vcf</code>, Extensible Markup Language <code>.xml</code>

;Filter:
: A [[Gramps_{{man version}}_Wiki_Manual_-_Filters|filter]] (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> query) in a database finds (or hides by 'filtering out') records, displaying only those records that match certain criteria. (The criteria are comparison or query [[#rule|rules]] describing some attribute of a record.) Layers of criteria can be applied but each layer requires additional processing and slows performance of the interface.
: The [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Filter_vs._Search|basic Search]] is a single criteria filter. The search value is compares only one attribute of a record that has been selected from a pop-up menu.
: The '''[[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Filter|Filter Gramplets]]''' will compare several predefined common attributes simultaneously with simplified access to changing the search value. The default is for exact matching but [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Regular_Expressions|Regular Expressions (RegEx)]] can be used for pattern matching. A Custom Filter may be also layered in.
: A [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Custom_Filters|Custom Filter]] adds richly complex [[#rule|Rules]]-based comparison with [[Example_filters|layers of intersection]] options for those rules. Custom Filters allow repeatable filters to be created with pre-defined rules and values to be matched. Beyond interactively hiding (or revealing) records in views, Custom Filters are used to set limits for exporting, setting scopes for reports, and targeting tool actions.
: In addition to the [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Which_filter_rules_in_which_Category.3F|builtin rules]] for filtering, [[Addon:Rule expansions]] are available for Custom Filters.

==G==
;GEDCOM:
# Acronym: '''Ge'''nealogy '''D'''ata '''Com'''munication
# A format for [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#GEDCOM_import|importing]] and [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|exporting]] genealogical data. The <abbr title="an open standard is a standard that is publicly available and has various rights to use associated with it, and may also have various properties of how it was designed such as 'open process.' There is no single definition and interpretations vary with usage.">open</abbr> specification for the [https://www.familysearch.org/developers/docs/guides/gedcom GEDCOM format] was developed by The Church of Jesus Christ of Latter-day Saints (LDS Church) as an aid to genealogical research. The long standing standard release was version 5.5 in 1996 with a 5.5.1 draft update presented for comment in 1999. (Belatedly, the 'draft' label was officially removed in the annotated 2019 release. After 20 years as the de facto standard format, it remained unimproved excepting for 2 tags and the copyright.)
::As an Open Standard, there are extensive and constantly changing incompatibilities between implementations and data loss when transferring GEDCOM formatted data between competing software tools is common. Gramps has implemented a variety of [[GEDCOM|GEDCOM support features]].
::GEDCOM [https://www.familysearch.org/developers/docs/guides/gedcom-x X proposed in 2012] and [https://blog.eogn.com/2019/10/04/the-proposed-gedcom-5-5-5-standard-is-a-better-gedcom/ 5.5.5 proposed in 2019] are improvements that have not gained the approval of the copyright holder. As of June 2021, these proposals have been superseded by the GEDCOM 7.0.1 version.

;Godparent: ''([[#event_role|event role]])'' - A term to refer to the person who presents a child at a christening or baptism and promises to take responsibility for guiding the child emotionally, practically, and spiritually. This person will be referred to as ''godfather'' or ''godmother'' after the christening or baptism. See also: ''[[Add_a_godfather-godmother|Add a godfather-godmother]]''.

;Gramplet: A [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#definition|Gramplet]] is a plug-in (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Software_widget widget] or [https://wikipedia.org/wiki/Applet applet]) that can be [[#dock|docked]] in the {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]] category view. Later [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|sidebar or bottombar]] were added to the remaining [[#view|views]] to extend [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Gramplet_Bar_Menu|adding]] and [[#undock|undocking]] a Gramplet functionality of those view.
: Gramplets dynamically update as the different records are selected in the main display area of a view. Gramplets typically create an alternate interface to your Family Tree data. Collections of [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Summary_of_Gramplets|builtin]] and [[{{man version}}_Addons#Addon_List|"3rd party addon"]] gramplets are available for [[{{man version}}_Addons#Installing_Addons_in_Gramps|installation]] and download with the [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager|Plug-in Manager]]. The Plug-in Manager also regulates a [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Aren.27t_all_Plugins_also_Gramplets.3F|wide variety of other builtin and addons]] which can expand functionality unrelated to the interface.
: ''See the [[Gramplets development]] for independent information.''

;Gramps for Desktops: [https://gramps-project.org/blog/features/ Gramps] is an open-source genealogy application, a free software project and community.
: '''Gramps''' is an affectionate nickname for a "Grandfather". Originally, the all capital letter [https://wikipedia.org/wiki/Backronym backronym] stood for "'''G'''enealogical '''R'''esearch and '''A'''nalysis '''M'''anagement '''P'''rogramming '''S'''ystem" and was coined by Larry Allingham. ([https://gramps-project.org/blog/2006/04/looking-back-over-5-years/ GRAMPS was created around 2001] by [[User:Don|Don Allingham]] for use by his father, Larry.) This backronym was phased out around March 2010 in favor of '''Gramps''' as the official name of the software. All upper-case acronym-based names have become unfashionable for software.''

;Gramps Web for Servers: [https://gramps-project.org/blog/web/ Gramps Web] is collaborative interface (frontend) and backend created by David M. Straub for running the Gramps genealogy database engine on servers. It is one of the [[Web_Solutions_for_Gramps|Web Solutions for Gramps]].
: It is a multi-user system genealogical web application with different levels of options for Visitors, Members, Contributors, Editors, and Owners. Trees in [[https://www.grampsweb.org Gramps Web on a server]] can be synchronized with the more mature and feature laden [[#gramps|Gramps for Desktops]]. Single Tree or multiple Tree sites can be self-managed on a hosted service from an ISP, leased from a managed hosting ISP, or leased from an application-specific fully managed CMS provider, or installed locally for access from a local area network.

;Graphical User Interface (GUI): A visual way of indicating interactive features of a computer operating system or application/program.
:The '''Gramps for Desktops''' GUI is introduced in [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|Visual Guide to Gramps Interface]]. It uses a "windows, icons, menus, pointer" ([https://wikipedia.org/wiki/WIMP_(computing) WIMP]) based approach with [https://wikipedia.org/wiki/Post-WIMP post-WIMP] elements like hyperlinked redirection and custom interface objects. The desktop interface is built with [https://wikipedia.org/wiki/GTK Gtk] (the Gimp Toolkit), a free and open-source cross-platform widget toolkit for creating graphical user interfaces.
:The appearance and interaction may vary by conventions dictated by the [[Download|Operating System (OS)]], installation option (such as [[Portal:Translators|language localization support]] or [[{{man version}}_Addons|addon/plug-in]]), [https://wikipedia.org/wiki/Theme_(computing) theme] (at the OS or [[Addon:ThemePreferences|internal]] levels), and/or [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Preferences|user preferences customization]].
:The specific interface elements are identified by customary name, general appearance & behavior in the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|Visual Guide to Gramps Interface]]. Expansion interface elements are described in the user documentation for [[{{man version}}_Addons|each specific addon]].
: The '''Gramps Web''' GUI (or frontend) is a platform-agnostic web browser interface built with the [https://lit.dev/ Lit] lightweight JavaScript library for building fast, interoperable web components. Although the hosting side requires a webmaster with significant skills, genealogical collaborators can use web browser on almost any device.

;Groom: ''([[#event_role|event role]])'' - A term to refer to the man at a marriage who will be referred to as ''husband'' after the marriage. See also: ''[[Add_a_spouse|Add a spouse]]''.


;GUI: An acronym. ''see [[#graphical user interface|Graphical User Interface]]''.

==H==
[[File:Gramps Go-Home48x48 win.png|right]]
;Home Person: ''(core concept)'' - The persistently designated '''Home Person''' is the foundational [[#person|Person]] (the [[Genealogy_Glossary#proband|Proband]], [[Genealogy_Glossary#progenitor|Progenitor]], or [[Genealogy_Glossary#progenitrix|Progenitrix]]) in the Tree (the currently open Gramps database). This Person is the central target of genealogical research and family references extend from this center. Ideally, every person, event and source in the Tree will (however directly or indirectly) relate back to the '''Home Person'''.
: By default, the database reports describe everything else in contextual relation to this person. The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Status_Bar_and_Progress_Bar|Status Bar]], the [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Quick_View|Quick View]] called "[[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Relation_to_Home_Person|Relation to Home Person]]", and the Third party addon [[#gramplet|Gramplet]] called "[[Addon:Deep_Connections_Gramplet|Deep Connections]]" all describe different aspects of the relationship of the [[#active_person|Active Person]] to the '''Home Person'''.
: You (or your client) are customarily designated ([[Gramps_{{man version}}_Wiki_Manual_-_Settings#Setting_Home_person|set]]) as the Home Person. And this ''Home'' designation serves as a persistent point of reference for the rest of the Tree in Reports generally and for the Active Person in detail. But a different '''Home Person''' might be temporarily [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Setting_Home_person|set]] when generating reports or when researching a complex biography or obituary.
: Fascinating tidbits often lure Gramps researchers into wandering off-course. When the [[#active_person|Active Person]] has become lost, the bearings can be instantly regained by navigating the [[#active_person|Active Person]] selection back to the '''Home Person'''.
: Navigate to '''Home Person''' - ''keyboard shortcut'' {{man key press|Alt|Home}} or press the toolbar [[File:Gramps_Go-Home48x48 win.png|text-bottom|20px]]{{man button|Home}} button.
: The custom filter rule for finding the '''Home Person''' is in a People category filter under the General filters and was named 'Default person' until the 5.1 version.

==I==
;Informant: ''([[#event_role|event role]])'' - A term to refer to the [[#role|Role]] of Person who reports an [[#event|Event]].

==J==
;JSON: Acronym: [https://wikipedia.org/wiki/JSON '''J'''ava'''S'''cript '''O'''bject '''N'''otation]. JSON is a lightweight, text-based data format designed to be easy for humans to read while still structured enough for machines to parse efficiently. It organizes data in key-value pairs, allowing information to be grouped together in a clear and straightforward way.

==K==
;Keybinding: Keyboard shortcuts (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> hotkeys) key (or combination of keys) that can be used to navigate a Graphical User Interface (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [[#gui|GUI]]) as an alternative to using the mouse. A single keystroke (or combination of keys on a keyboard) executes a command.
:''see [[Gramps_{{man version}}_Wiki_Manual_-_Keybindings#toc|Gramps GUI keybindings]]''

==L==
==M==
;Matronym:
:''([[#name_origin|Name origin]] attribute)'' - Personal name based on the name of one's mother

;[[File:Gramps-media.png|right]]Media: ''({{icon|medi}} [[#primary_object|prim. obj.]])'' - Contains the information related to a media object. Media objects include images, videos, audio recordings, documents, webpages or any other type of related files.
:When new Media objects are edited from the Gallery tabs of Object Editors or from the Media category view, the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_media_objects|New Media editor]] allows the metadata to be modified.

;[[File:Gramps_Merge48x48_win.png|right]]Merge
:To combine the objects in two selected rows in a [[#view_category|category view]] into a single object. This reduces duplicates while consolidating references and [[#secondary_object|secondary objects]]. The [[Merging_people|merge process]] involves selecting two rows (a target row to be kept and a row to be deleted) then choosing '''Merge''' from the Toolbar or Edit menu. Choices are offered about which secondary objects take precedence when there are conflicts, but no data (except one of the descriptions in an Event merge) is lost by default. All secondary objects from both selected rows are conveyed to the surviving merged row. Only two objects may be merged at a time unless using addon tools designed for multiple object merges or batches of merges.

;Mode:
:''See [[#viewmode|View mode]]''

==N==
;Name Origin:
:An optional attribute (characteristic) identifying how a name was derived for a [[#person|Person]]. Pre-defined items of the [[Names_in_Gramps#Origin_Attributes|origin selection menu]] include: inherited, patrilineal, matrilineal, given, taken, [[#patronymic|patronymic]], [[#matronymic|matronymic]], feudal, pseudonym, occupation. The Name Origin of [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Multiple_Surnames|Multiple surnames]] and [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Names|Alternative names]] can be added from the [[#edit_person|Edit Person]] dialog.
: ''Available as a standard attribute of [[Names_in_Gramps|Names in Gramps]].''

;Navigator:
: ''([[#gui|graphical user interface terminology]])'' - The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Navigator|Navigator]] is a Gramps-specific name for a left sidebar layout of [[#category|category]] view icons, allowing movement between (aka 'navigating') the different View categories. There are [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Switching_Navigator_modes|multiple layout modes]] and a [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Environment_Settings|text label preferences option]] for the sidebar. This sidebar may be hidden or revealed from the menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Navigation#View|View ->Navigator]]}} or by using the [[Gramps_{{man version}}_Wiki_Manual_-_Keybindings#7|keybinding]]. Navigator layout modes are 'Sidebar' type [[#plugin|plugins]] that can be added, removed, hidden or revealed using the Plugin Manager.
: Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of [[#category|Categories]], each with their own View. Each of the Category Views displays a smaller, more digestible portion of the total information that comprises a Genealogical Tree. The View categories are: {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]], {{icon|peop}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People]], {{icon|rela}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships]], {{icon|fami}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Families_Category|Families]], {{icon|ance}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]], {{icon|even}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Events_Category|Events]], {{icon|plac}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places]], {{icon|geog}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography]], {{icon|sour34}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources]], {{icon|cite}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Citations_Category|Citations]], {{icon|repo}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Repositories_Category|Repositories]], {{icon|medi}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Media_Category|Media]], {{icon|note}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Notes]]

;[[File:Gramps-notes.png|right]]Note: ''({{icon|note}} [[#primary_object|prim. obj.]])'' - Contains the information representing a textual brief record of facts and how it [[#reference|references]] other objects in the Tree. Notes can be added to any object at any any level of the Tree and are often used to detail the context of that record in the Tree.
:Records in the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Note Category]] contain free-form text with [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Note_markup_and_preformat_in_reports|basic formatting]] and [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Link_Editor|linking]] features. Notes can be categorized by [[#tag|Tag]] and [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#note_type|Type]] in addition to the object to which it is attached. That information is created and modified using the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_notes|Notes Editor]].

==O==

;Object: The most basic framework unit of genealogical data as structured in the Gramps [[Gramps_Data_Model|data model]].
:The most complex structures are the [[#primary_object|Primary Object]] of a [[#category|category]]. Each has an [[#object_editor|Object Editor]] that organizes entering data in that structure but also allows attaching or creating [[#secondary_object|secondary objects]].

;Object Editor ''(<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> Edit Object dialogs)'':
: ''(core concept)'' - The object editor dialogs show the basic info of the [[#primary_object|Primary Object]] in the structured form of the header area where it can be directly edited. And the bottom tabbed section allows the editing of interrelationships with [[#secondary_object|secondary objects]] and provides access to the Object Editors for those secondary objects.
:Click the following links for instructions of how to open and use each type of Edit Object dialog.
:The available categories of object editor dialogs are: {{icon|peop}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_people|Edit Person]]}}, {{icon|fami}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_relationships|Edit Family]]}}, {{icon|even}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_events|Edit Event]]}}, {{icon|plac}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_places|Edit Place]]}}, {{icon|sour34}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_sources|Edit Source]]}}, {{icon|cite}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_source_citations|Edit Citation]]}}, {{icon|repo}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_repositories|Edit Repository]]}}, {{icon|medi}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_media_objects|Edit Media]]}}, {{icon|note}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_notes|Edit Note]]}}
:The available categories of object reference editor dialogs for [[#sharing|shared objects]] are: {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Person_Reference_Editor|Person Reference Editor]]}} ''(see [[#association|Associations]])'', {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Child_Reference_Editor|Child Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Place_Reference_Editor|Place Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Repository_Reference_Editor|Repository Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Media_Reference_Editor_dialog|Media Reference Editor]]}}

;Officiator: ''([[#event_role|event role]])'' - A term to refer to the role of a person authorized to conduct an official duty or function. (Such as performing a marriage or funeral ceremony or conferring a vocational degree.) Jurisdiction may be derived from a from holding a position of civil or religious authority. Use 'OFFICIATOR' rather than 'Officiant' for [[#gedcom|GEDCOM7]] Roles compatibility.

==P==
;patronym:
:''([[#name_origin|Name origin]] attribute)'' - Personal name based on the name of one's father.

;[[File:Gramps-person.png|right]]Person: ''({{icon|peop}} [[#primary_object|prim. obj.]])'' - Contains the information specific to an individual person in the People category. The information may be edited directly using the [[#edit_person|Edit Person]] dialog.

;[[File:Gramps-place.png|right]]Place: ''({{icon|plac}} [[#primary_object|prim. obj.]])'' - The Gramps concept of a Place is a particular location independent of time. Over time, the same Place may have different hierarchical (or name) information due to changing borders and political situation. For example, Leningrad and St. Petersburg represent the same place, but with different names. Places in Gramps are stored in a hierarchy and are direct accessed via the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places category view]]. Places can be defined (or refined) through the Place Editor and shared with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Select_Place_selector|Select Place]] object selector. A Place consists of:
:* Descriptive Title
:* Name (with optional date span and language attributes)
:* A list of alternative names for the place
:* Type ([[#administrative_division|administrative divisions]] such as country, state, county ...)
:* Longitude/Latitude
:* Code (such as a country code or postal code)
:* A hierachical list of regions which enclose the place

;plugin: (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Plug-in_(computing) plug-in])
:* A type of [[Writing_a_plugin|expansion framework that allows Gramps customization]] by providing interface hooks to recognize and use external code.
:* A customized module of code built to provide a specific feature or functionality that is not part of the core program.
:The [[Addon_list_legend#Type|various types]] of Gramps plugin code modules can be enabled or disabled via a [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager|plugin manager]]. Plugin types include: Citation formatter, [[Database_Backends|Database]], Doc creator, Exporter, [[#gramplet|Gramplet]], Gramps View ([[#view|''Category'']] or [[#viewmode|''mode'']]), Importer, [[Map_Services|Map Service]], Plugin lib, [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Quick_Views|Quickreport'''/'''Quickview]], Relationships, [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_1|Report]], [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Add_Rule_dialog|Rule]], Sidebar, Thumbnailer [[Gramps_{{man version}}_Wiki_Manual_-_Tools|Tool]].
:Plugins can be builtin ''(included with the normal distribution of Gramps)'' or an [[{{man version}}_Addons#Addon_List|addon]] ''(installed via the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Third_party_addons_management|Third party addons management]] in Preferences)''.

;POSIX: [https://wikipedia.org/wiki/Posix Portable Operating System Interface]: a family of OS standards specified by the [https://wikipedia.org/wiki/IEEE_Computer_Society IEEE] Computer Society for maintaining compatibility with variants of Unix (such as Linux) and other operating systems. Although the MacOS is "POSIX-certified", the term is used in this manual to generically refer to just the "Mostly POSIX-compliant" Linux and BSD distributions [[Download#Linux_and_BSD_distributions|with verified Gramps downloads]] and which use the POSIX-style [https://wikipedia.org/wiki/Filesystem_Hierarchy_Standard environment].

;Preferences: The {{Man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Preferences|Preferences]]}} is an option in the {{Man menu|Edit}} main menu that allows '''''global''''' customization of the appearance, defaults and behavior of Gramps. The customizations are categorized into the following tabs: {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Data|Data]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#General|General]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Family_Tree|Family Tree]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Import|Import]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Limits|Limits]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Colors|Colors]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Genealogical Symbols|Genealogical Symbols]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#ID_Formats|ID Formats]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Text|Text]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Warnings|Warnings]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Researcher|Researcher]]}}.
:(A {{man label|[[Addon:ThemePreferences|Theme]]}} tab is available as an addon.)
:(see also ''{{Man menu|Configure...}}'' option in the {{Man menu|View}} main menu is an option. Those customization are limited to the currently active view and its Gramplets. The feature may also be accessed by the {{man button|Configure...}} toolbar icon.)
:The Gramps 5.1 and older preferences are categorized into the following tabs: {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#General|General]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Family_Tree|Family Tree]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Display|Display]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Text|Text]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#ID_Formats|ID Formats]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Dates|Dates]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Researcher|Researcher]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Warnings|Warnings]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Colors|Colors]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Genealogical Symbols|Genealogical Symbols]]}}.

;Prerequisites: Additional software required to make certain features of Gramps work and or some [[:Category:Prerequisites|addons]].

;Primary object: Primary objects are the [[Using_database_API|data structures]] at the top level of a [[Gramps_Data_Model|hierarchical collection of records]] in the Gramps [[Gramps_Data_Model|data model]]. Beside the main structure of data, they can contain a hierarchy of [[#secondary_object|secondary objects]], and can be referenced by other primary or secondary objects. In the Gramps database, primary objects and the secondary objects that they contain are stored as separate records. Each primary object type is stored in a separate table. See [[Using_database_API#Primary_Objects|Using database API, Primary Objects]] (see also ''[[#secondary_object|secondary object]]'')
: The types of [[Using_database_API#Primary_Objects|primary objects]] are:
: {{icon|cite}} [[#citation|Citation]], {{icon|even}} [[#event|Event]], {{icon|fami}} [[#family|Family]], {{icon|medi}} [[#media|Media]], {{icon|note}} [[#note|Note]], {{icon|peop}} [[#person|Person]], {{icon|plac}} [[#place|Place]], {{icon|repo}} [[#repository|Repository]], {{icon|sour34}} [[#source|Source]], [[File:16x16-gramps-tag.png]] [[#tag|Tag]].

;Primary role: ''([[#event_role|event role]])'' - A term to refer to the [[#role|role]] of the focal participant of an [[#event|Event]]. '''Primary''' is the ''default'' role when adding a new Event in the [[#edit_person|Edit Person]] dialog.

;[[File:gramps-lock.png|right]]Private flag or tag:
: The Private option identifies sensitive information that should be redacted when sharing data or printing reports. ''(This marker should not be confused with the generic user-definable [[#tag|Tags]] used for custom filters and color highlighting.)'' Records are shown with: a [[File:22x22-gramps-lock.png]]locked padlock when private; and, an [[File:22x22-gramps-unlock.png]]unlocked padlock when public. Clicking the padlock icon toggles between Private & Public flags. This manual override supplements the automated [[Gramps_{{man version}}_Wiki_Manual_-_Probably_Alive|Probably Alive]] and custom [[Filter|Filter]] features which help Gramps to respect Personal Privacy.
:Gramps is a single user database and omits the typical security features of a multi-user system. So even "Private" data will be accessible from within Gramps. However, generating reports and exporting data default to redacting information flagged as Private.

;[[File:gramps-unlock.png|right]]Public tag or flag:
: The Public option identifies information that should be included when sharing data or printing reports. Records are shown with: a [[File:22x22-gramps-unlock.png]]unlocked padlock when public; and, an [[File:22x22-gramps-lock.png]]locked padlock when private. Clicking the padlock icon toggles between Public & Private flags. By default, all records are created as Public.

==Q==
;Quick View: On-screen [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Quick_Views|reports]] about information surrounding the active object that do not print or save to file. Generally the report is selected from a [[#context_menu|context menu]] for the selected category of record and will have no configurable options.
: The [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Quick_View|Quick View '''gramplet''']] refreshes a builtin [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Quick_Views|builtin]] or [[{{man version}}_Addons#Addon_List|addon]] QuickView reports as the focus of the active record is changed. The specific QuickView report is selected in a view configuration dialog opened with the {{man menu|View -> Configure...}} menu.

==R==
;Reference: The basic system of linking relationships between objects in Gramps. When an object is added in the Editor for record, a [[References#definition|Reference]] (link) is created in the object that was added.

;[[File:Gramps-relation.png|right]]References tab: When objects of Gramps are linked, the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#References|References tab]] lists the objects to link toward it.

;Regular Expressions: [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Regular_Expressions|RegEx]] is a system to specify a text string pattern for comparing and matching. Optionally used to extend a power of the Filter Gramplets and Custom Filters rules.
:Filters in [https://gramps.discourse.group/t/which-regex-syntax-does-gramps-use/2278/8 Gramps use the RegEx format specified by the installed version of Python]

;Re-order
:[[File:Stock_reorder.png|right]]To change the sequence of items within a list of [[#secondary_object|secondary objects]]. [https://gramps.discourse.group/t/re-ordering-data-in-gramps-topic-expansion-outline-for-wiki/5568 The interface for (and consequences of) re-ordering that sequence varies based on the list type.]
:The natural order of a list follows when the data was created. The first item in an ordered list is often considered the primary or preferred item of that type. The primary/preferred may be the only object considered in some charts and analyses. So when data entry of related objects was out of sequence, a re-ordering option becomes necessary.
:Re-ordering affects display order in the Tree, charts, and most reports. Note that in some contexts, dates can override the manual order, particularly for Places and Names.

;[[File:Gramps-repository.png|right]]Repository: ''({{icon|repo}} [[#primary_object|prim. obj.]])'' - Contains the information related to a physical or virtual structure where genealogical and family history sources are stored. Once a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_repositories|Repository is added]] to a Gramps Tree, it can used to organize [[#source|Sources]].

;Role: Function performed or part played by a person (or other Gramps [[#object|object]]) in a particular situation. When objects of Gramps are linked, a Reference is created where the implicit Role disambiguates the relative nature of the reference. ''For explicitly defined roles, see [[#event_role|event role]] and [[#association|association role]]''

;Romanization:
: Linguistic representation of a word in the Roman (Latin) alphabet

;Rule: A pre-defined abstraction that simplifies the interface for a structured query about a particular facet of your family tree. Rules allows users to choose search criteria without needing to understand the intricate details of the actual database query language. Rules are layered via the [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Custom_Filters|Custom Filters]] interface to [[#filter|filter]] with complex criteria.

==S==
;Secondary object: Secondary objects are contained within other [[#object|objects]] of the structured Gramps [[Gramps_Data_Model|data model]], and cannot be referenced directly. They can contain other secondary objects. Examples include: Name, Date and Address. See [[Using_database_API#Secondary_Objects|Using database API, Secondary Objects]] (see also ''[[#primary_object|primary object]]'')

;Selector combo box: ''([[#gui|graphical user interface terminology]])'' - a [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Combo_Boxes|standard text entry box paired with a pull-down list button]] is a [https://docs.gtk.org/gtk3/visual_index.html Gtk toolbox widget] (based on the standard [https://wikipedia.org/wiki/Combo_box combo box]). The combination of a drop-down list and a single-line editable textbox allows the user to either select a value from the list or key in a value directly. Moreover, keying in a value that is not already in the list will add that [[#custom|custom type]] to the drop-down list.

;Shared objects: {{icon|share}} Sharing allows an Object to be linked at multiple places in the tree. Doing so establishes a relationship or maintains single set of attributes (or [[#secondary_object|secondary objects]]) that they hold in common. ([[#role|Roles]] for shared Events define the person or family participation level.)
:'''[[#object_reference_editors|Object Reference Editors]]''' allow updates to a shared object to be reflected in all instances mentioning (referencing) that shared object. Redundantly creating object with the same information should be avoided. (So, refining a Transcription Note shared by multiple Citations will show the updated transcription in all the Citations.)
:Object descriptions are grouped in two distinct sections:
:  • The '''Reference Information''' section contains information unique to one instance.
:  • The '''Shared Information''' of an object will be seen in all instances that are linked to it.

;Selector: Combo interface box that allows you to select an object. The [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Selector_dialogs|Select Family selector]] is one example.

;[[File:Gramps-source.png|right]]Source: ''({{icon|sour34}} [[#primary_object|prim. obj.]])'' - Sources can be a person ''(family, friend, another researcher)'', thing ''(book, magazine newspaper, census)'', or place ''(courthouse, church, library, genealogical/historical society... although places might be better handled as Repositories)'' from which information comes, arises, or is obtained. After [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_sources|adding a Source]] with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#New_Source_dialog|new source dialog]] to the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources category]] of a Gramps Tree, the Source can be referenced when adding a [[#citation|Citations]] and organized within [[#repository|Repositories]]. The same Source may exist in multiple Repositories and may have different Media Types (such as book, microfilm, or electronic) and Call numbers in each Repository.
:[[Sources#Definition|[more]]]

;SQLite: ''([[Database_Backends|database backend]] engine)'' - The [https://sqlite.org/about.html SQLite project's in-process library] (also known simply as SQLite) is the ''default database engine'' used since the [[Database_Formats#Gramps_5.1|5.1]] version of Gramps. The support was extended from [[#bsddb|BSDDB]] in the 5.0 version via the [[DB-API_Database_Backend|DB-API Database Backend]].

;Swatch: ''([[#gui|graphical user interface terminology]])'' - A [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Pick_a_Color_selector|color swatch]] is a sample square of a color or color pattern. Swatches may be dragged from the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Pick_a_Color_selector|Pick a Color selector]] to apply that specific color to preferences.
:The word originally referred to sample pieces of cloth or fabric used for choosing or testing colors, patterns, or textures for interior or exterior design. It now means any small sample or representation of a larger whole and is commonly usage in the context of color representation and selection in software applications.

==T==
;[[File:gramps-tag.png|right]]Tag: ''([[File:16x16-gramps-tag.png]] [[#primary_object|prim. obj.]])'' - A custom titled and color-coded label that [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Tagging|can be created with the Organize Tags dialog and attached]] to selected {{icon|cite}} [[#citation|Citation]], {{icon|even}} [[#event|Event]], {{icon|fami}} [[#family|Family]], {{icon|medi}} [[#media|Media]], {{icon|note}} [[#note|Note]], {{icon|peop}} [[#person|Person]], {{icon|plac}} [[#place|Place]], {{icon|repo}} [[#repository|Repository]] or {{icon|sour34}} [[#source|Source]] objects for the purpose of easy identification and filtering.
: A keyword or phrase used to group the collection to produce a report. Multiple tags may be used to label and categorize objects into multiple groups when filtering by other attributes is not viable.

;Toolbar: ''([[#gui|graphical user interface terminology]])'' - The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Toolbar|Toolbar]] is a ribbon (located below the application menubar) with button shortcuts for the most widely needed functions associated with the current view. The selection of buttons changes in response to the context of the current view. (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, toolbar buttons for switching mapping [[#view_mode|view modes]] will only appear for the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography view]].)

;Typographical conventions: The [[Gramps_{{man version}}_Wiki_Manual_-_Preface#Typographical_conventions|customary formatting]] having special (and possibly peculiar) meaning when used throughout the MediaWiki driven [[Gramps_{{man version}}_Wiki_Manual|Gramps manual]] and documentation. The different typeface accents, highlighting and enclosures indicate specific parts of the Gramps [[#graphical user interface|Graphical User Interface]] ([[#GUI|GUI]]) or prompt a User activity.

==U==
;Unknown: ''([[#event_role|event role]])'' - A placeholder for when the [[#role|role]] of a participant in an [[#event|Event]] has not yet been defined. Gramps sets an appropriate default Role as each new Event type is created. But when a new participant is associated with an existing Event via Share or drag'n'drop, the Role isn't as predictable. In such a case, an Unknown placeholder is inserted.
:Any Unknown [[#event_role|Event Role]] type causes a variety of reporting problems. [[Addon:Rule_expansions#People_with_events_with_a_selected_role|(Rule_expansions)Persons and Families with Unknown Roles]] should be found and the Roles manually replaced as soon as is practical.

;User Directory: ''(core concept)'' - An alias for the file folder (directory) location where customizations (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>: preferences files, [[#addon|addons]], [[#plugin|plugins]]) are stored for the Gramps family of genealogy tools. Since this folder location varies by which Operating System and which Gramps fork has been installed, the '''User Directory''' is an 'alias' (a.k.a. placeholder) used in instructions about re-configuring Gramps.
: This alias allows [[Gramps_{{man version}}_Wiki_Manual_-_User_Directory|instructions for locating your specific '''User Directory''' file location]] to be consolidated in the documentation.

==V==
;View category: ''([[#gui|graphical user interface terminology]])'' - a [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|'''View category''']] (often simply called a "'''[[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|View]]'''") is a Gramps-specific name for the collection of [[#view mode|View modes]] (display layouts) presenting information in a structured and predictable manner. Different Views are selected from the [[#navigator|Navigator]] (left sidebar).
: Layouts are in table, outline or graphical formats, depending on the preferred way to represent how the data elements relate to one another.
: Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of [[#category|Categories]], each with their own View. Each of the Category Views displays a smaller, more digestible portion of the total information that comprises a Genealogical Tree. The View categories are: {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]], {{icon|peop}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People]], {{icon|rela}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships]], {{icon|fami}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Families_Category|Families]], {{icon|ance}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]], {{icon|even}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Events_Category|Events]], {{icon|plac}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places]], {{icon|geog}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography]], {{icon|sour34}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources]], {{icon|cite}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Citations_Category|Citations]], {{icon|repo}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Repositories_Category|Repositories]], {{icon|medi}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Media_Category|Media]], {{icon|note}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Notes]]

;View mode: ''([[#gui|graphical user interface terminology]])'' - a '''[[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|View mode]]''' is a Gramps-specific name for the display layouts presenting [[#view_category|View category]] information in a structured and predictable manner. A [[#view_category|View category]] may have alternate '''view modes''' (subcategories) of display layout. (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, Views with Table layouts might have flat listed or hierarchically grouped modes.) Navigating between View modes is from the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Toolbar|toolbar]] and [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Switching_Navigator_modes|Navigator]].
: Each mode of a category can be independently [[File:Gramps-config.png|22px]] configured. Each mode may maintain a separate object selection, filtering, and organization for its Gramplet bars.
: View data may be further subdivided with tabbed pages of layouts.

==W==
;wiki: (Hawaiian [https://wikipedia.org/wiki/Loanword loanword]) meaning 'quick'; or 'wikiwiki' meaning 'very quick'. For Gramps users, '''''[[User manual|the Wiki]]''''' (a.k.a. '''''[[User manual|Wiki Manual]]''''') refers to the collaborative website of educational material which is organized using the [https://mediawiki.org/wiki/MediaWiki MediaWiki] [https://wikipedia.org/wiki/Content_management_system content management system]. The core pages of that website being the structured reference-style [[#gramps|Gramps]] software user's operating guide. ''(Note that specific [[:Category:Tutorials|tutorial]] documents are also part of the wiki.)''
:For most internet users, the word is most often an inadvertent allusion to the 1995 [http://wiki.c2.com/?WikiWikiWeb WikiWikiWeb], the first website that builtin tools encouraging users to quickly & easily collaborate to expand the content of the site. See the term: [https://wiktionary.org/wiki/wiki 'wiki'] in [https://wiktionary.org/wiki/Wiktionary Wiktionary]

;Witness:''([[#event_role|event role]])'' - The term that applies to the people asked to be present at an event so as to be able to testify to its having taken place.

==X==
;XML: acronym: [https://wikipedia.org/wiki/XML E'''x'''tensible '''M'''arkup '''L'''anguage]. A schema used to define the expected structure of data in a text format. The system annotates a document in a way that data elements are syntactically distinguishable from identifying tags. A markup language defines a set of rules for encoding documents in a fault tolerant format that is both (marginally) human-readable and machine-readable.
: Gramps will [[Generate_XML|generate XML]] format natively in compressed and uncompressed forms identified with a <code>.gramps</code> or <code>.gpkg</code> file extension. It is the format that definitively supports every piece of genealogical data stored by Gramps. Used as the working format until Gramps 2.0 started using a ''[[Database_Backends|database backend]]'' to improve performance, XML is now the standard Tree data backup format and recommended data exchange format.
: See the [https://www.gramps-project.org/xml/ reference documentation for the versions] of Gramps [[Gramps_XML#RELAX_NG_generation|RELAX NG]] ('''RE'''gular '''LA'''nguage for '''X'''ML '''N'''ext '''G'''eneration)(<code>.rng</code>) schema XML and [[#dtd|DTD]]

==Y==
==Z==

{{man tip|1=Wiki manual|2=Please enhance the {{man label|Wiki}} - create new glossary terms and add them to the wiki manual. Glossary term IDs are more memorable & predictable if kept to all lower-case. When translating the Glossary, please leave the English ID anchors but also add translated variants of the same anchor. This allows users to look up a term in either language.

Inserting a "Glossary Term" into the Glossary list: 
<code><nowiki>;Glossary Term: Definition of the term.</nowiki></code> 
Do not replace a space in the anchor ID with an underscore. An anchor defined with a space can match both the underscore and space form, but an anchor defined with an underscore can only be referenced by the underscore form.

In a translated Glossary, add the English ID by putting an extra span around the translated header: 
<code><nowiki>;Translated Term: Translated definition of the term.</nowiki></code>

Referencing the glossary term in the Gramps wiki manual: 
<code><nowiki>[[Gramps_Glossary#glossary_term|Glossary Term]]</nowiki></code> 
(Note the optional underscores for spaces here.)

For more information about WikiMedia sections, see: 
<code>https://meta.wikimedia.org/w/index.php?title=Help:Section#id_with_space</code>

}}

[[Category:Gramps terminology|*]]
[[Category:Translators/Categories]]
[[Category:Documentation]]

Gramps 6.0 Wiki Manual - Preface

2026-03-15T17:53:14Z

DomoViridi: span id goes tight around the section header text.

{{man index|Gramps 6.0 Wiki Manual|Gramps 6.0 Wiki Manual - What's new?|6.0}}
{{languages|Gramps_6.0_Wiki_Manual_-_Preface}}
{{#vardefine:chapter|0}}
{{#vardefine:figure|0}}
[[File:Dashboard-category-view-first-open-no-family-tree-loaded-60.png|right|thumb|450px|Fig {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Gramps (with no family tree loaded)]]
'''Gramps''' is software designed for genealogical research (and packaged for several [https://wikipedia.org/wiki/Operating_system operating system] computer environments and [[Portal:Translators#status|languages]]). Although similar to other genealogical programs, Gramps offers some unique and features which we'll discuss below.

Gramps is [https://wikipedia.org/wiki/Free_and_open-source_software Free and Open-Source Software (FOSS)], which means you are free to make copies, to customize the code, and to distribute it to anyone you like. It is developed and maintained by a worldwide team of volunteers whose goal is to make Gramps powerful, yet easy to use.
__FORCETOC__

== Why use Gramps? ==

Most genealogy programs allow you to enter information about your ancestors and descendants. Typically, they can display family relationships through charts, graphs, or reports. Some allow you to include pictures or other media. Most let you include information about people even if those people are not related to the primary family you happen to be researching. And they may include features that let you exchange data with other programs and print different types of reports.

Gramps has all these capabilities and more. Notably, it allows you to integrate bits and pieces of data as they arise from your research and to put them in one place -- your computer. You can then use your computer to manipulate, correlate, and analyze your data, rather than messing with reams of paper.

== Typographical conventions in the Gramps Wiki Manual ==

<onlyinclude>In this book, some words are marked with special typography:
* [[Write_a_%22How_Do_I...%22_Article#Create_a_page|Internal links]] (aka: hotlinks, hyperlinks) mark terminology or procedures that are explained more completely elsewhere (on the same webpage or on another webpage) internally within the Gramps-Project wiki.

* [https://wikipedia.org/wiki/Wikipedia:External_links External links] mark terminology that is not specific to Gramps where well-defined explanations can be found on a website external to the Gramps-Project wiki.

*Applications

*<pre>Commands you type at the command line</pre>

*''Filenames'' or <code>Filenames</code>

*<tt>''Replaceable text''</tt>

*{{man label|Labels}} for buttons and other portions of the graphical interface. A trailing ▴ and ▾ in a column header indicates the sort order for table column. ◂ more headers or tabs ▸

*{{man tooltip|Hint text}} for hover or roll-over hints (aka Tooltips) that identify elements of the graphical interface

*Menu selections look like this: {{Man menu|Menu -> Submenu -> Menu Item}} (Spaces should enclose the <code>-></code> to make webpage auto-translation recognize menu words.) Gramplet pop-up menus are marked with a {{man button|&or;}} (''Down Arrowhead'' button).

*{{man button|Buttons}} you can click

*[https://en.wikipedia.org/wiki/Disclosure_widget Disclosure triangle] node {{man button|▶}}expand or {{man button|▼}}collapse disclosure triangular widget. All the nodes of the tree view mode can be simultaneously collapsed or expanded from the pop-up menu shown by right-clicking.

*{{Man key press|CTRL|D}} [[Gramps_6.0_Wiki_Manual_-_Keybindings|Key combinations]] you can press on your Keyboard.

*<tt>Anything you type in</tt>

*{{checkbox|1|Checked}} - Checkbox that is ☑ selected
*{{checkbox|0|Unchecked}} - Checkbox that is ❏ unselected
*[[File:RadioButton_Selected.png|21px]] - Radio button that is ◉ selected
*[[File:RadioButton_Deselected.png|21px]] - Radio button that is 🔘 deselected

* Abbreviated [[Genealogy_Glossary#latin|Latin notations]]: <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, <abbr title="et cetera - Latin phrase meaning 'and so on'">etc.</abbr>, <abbr title="id est - Latin phrase meaning 'that is'">i.e.</abbr>, <abbr title="nota bene (singular), notate bene (plural) - Latin phrase meaning 'note well'">N.B.</abbr>, <abbr title="post scriptum - Latin phrase meaning 'postscript - after what has been written'">P.S.</abbr>, <abbr title="videlicet - Latin phrase meaning 'namely'; 'to wit'; 'precisely'; 'that is to say'">viz.</abbr>, <abbr title="versus - Latin phrase meaning 'against'">vs,</abbr>

The manual also provides assorted bits of additional information in tips and notes as follows:

{{man tip| 1=Example Tip |2=Tips and bits of extra information will look like this.}}

{{man note| Example Note |Notes will look like this.}}

Finally, there are [[Gramps_6.0_Wiki_Manual_-_Error_and_Warning_Reference|warnings]], notifying you where you should be careful:

{{man warn| Example Warning |This is what a warning looks like. If there's a chance you'll run into trouble, you will be warned beforehand.}}</onlyinclude>
{{-}}
{{man index|Gramps 6.0 Wiki Manual|Gramps 6.0 Wiki Manual - What's new?|6.0}}
{{languages|Gramps_6.0_Wiki_Manual_-_Preface}}
{{grampsmanualcopyright}}

[[Category:Documentation]]

Gramps Glossary

2026-03-15T14:48:04Z

DomoViridi: /* W */ (Witness): added final period.

{{languages|Gramps_Glossary}}
__NOTOC__
This glossary gives an overview of terms that appear in the [[features|Gramps]] genealogy software, with a short description, and a link to relevant articles. (Since knowing a feature's name is necessary for finding the corresponding glossary term, also refer to the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Main_Window|Visual Guide to the Gramps Interface]].)

For a glossary of genealogical terms, see [[Genealogy Glossary]] and [[Latin words and expressions]].

{| border="0" align="center" style="margin-top:0.4em;"
|
[[#A|A]] -
[[#B|B]] -
[[#C|C]] -
[[#D|D]] -
[[#E|E]] -
[[#F|F]] -
[[#G|G]] -
[[#H|H]] -
[[#I|I]] -
[[#J|J]] -
[[#K|K]] -
[[#L|L]] -
[[#M|M]] -
[[#N|N]] -
[[#O|O]] -
[[#P|P]] -
[[#Q|Q]] -
[[#R|R]] -
[[#S|S]] -
[[#T|T]] -
[[#U|U]] -
[[#V|V]] -
[[#W|W]] -
[[#X|X]] -
[[#Y|Y]] -
[[#Z|Z]]
|}


==A==

;Active Person: ''(core concept)'' - The person designated (or 'selected') as the momentary center of focus in the open Gramps database. The perspective of this person defines the context for actions and for displaying all the surrounding information. Changing this focus is done by [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Setting_the_Active_Person|navigating the Active Person]] selection to another person.
:The Active Person's relationship to the [[#home_person|Home Person]] defines the scope of the perspective.
:<abbr title="nota bene (singular), notate bene (plural) - Latin phrase meaning 'note well'">N.B.</abbr>: There is ''always'' an Active Person selection, even when the [[#primary_object|primary object]] (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> record) selected in the current view is not a 'Person' [[#object|object]].

;addon: (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Plug-in_(computing) add-on])
:An optional [[{{man version}}_Addons#Addon_List|'''third-party''' expansion]] to Gramps that leverages Gramps [[#plugin|plugin]] customization framework to add and [[Addons_development#Create_a_Gramps_Plugin_Registration_file|register]] a specific feature. The [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Using_the_Addon_Manager|Addon Manager]] allows installing and updating from curated collections of Addons. (These curated collections are called "Projects" in the Addon Manager.)
:Addons may not conform to the same design or code quality standards of builtin plugin modules. Use with caution!
:Optional parts bundled with the core project are called by the more generic name: builtin plugins. After installation and being registered, both the "builtin" and "addon" plugins may be disabled or re-enabled with the [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager#Registered_Plugins|Plugin Manager]].

;address: ''([[#secondary_object|sec. obj.]])'' - The Gramps concept of an Address is a particular location with an associated time frame. Think of it as a mailing address. It is intended to represent where a person lived and when the person lived there. The Address consists:
:* Date
:* Street Address
:* Locality
:* City
:* County
:* State/Province
:* Postal/Zip code
:* Country
:* Phone
:Not to be confused with a [[#place|Place]] which has a fixed position (its location). [[Why_residence_event_and_not_Address%3F|Use this with care.]] For genealogical research you can also use the residence event coupled with a [[#place|Place]]. For mailing (email, postal), add an address to a [[#person|Person]] or [[#repository|Repository]].

;administrative division: A unit of a layered system subdividing a geopolitical (geographic or political) region. Such divisions are recorded as [[#place|Place]] Types in Gramps. Meanwhile the structure of a Place Tree is built by layering via the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Enclosed_By|'Enclosed by' tab in the Place Editor.]] The subdivisions are sometimes categorized as an entity, locality, area, or region. The terms of subnational entity, constituent unit, or country subdivision tend to imply divisions that are more related to political representation than administrative.
: See wikipedia's [https://wikipedia.org/wiki/Administrative_division Administrative division] for a conceptional definition or [https://wikipedia.org/wiki/List_of_administrative_divisions_by_country List of administrative divisions by country] for specific countries.

;Aide: ''([[#event_role|event role]])'' - A term to refer to the role of an assistant.

;anglicisation:
: Process of making something English. If an immigrant (or their descendant) adopts a naturalized variation of their birth name, that [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Preferred_name_section|preferred alias]] can be added with an ''Also Known As'' [[Names_in_Gramps#Name_Types|name type]] in the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Names|Names]] tab. All aliases can be categorized by type and surname variants may be [[Grouping_Surnames|grouped]] with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Name_Editor|Name Editor]].

;Association: ''([[#secondary_object|sec. obj.]])'' - The [[#role|roles]] in [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_1#Associations|Associations]] are to explicitly define the how one person relates to another.
:Association roles are used when the relationship falls outside the implicit roles of a family relationship or the explicit roles in shared events. These custom roles convey relationships that might not readily apparent... such as a [https://wikipedia.org/wiki/Pen_pal penpal] or the [https://wikipedia.org/wiki/Eponym eponymous person] honored by a namesake. Association roles may also be used as placeholder when the actual genetic connection has not yet been discovered.
:Association roles are created and edited with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_1#Person_Reference_Editor|Person Reference Editor]], which includes no pre-defined roles. This feature starts with a blank list of [[#custom|custom types]]) and the default "Godfather" role is only shown as a hint.

;attribute: ''([[#secondary_object|sec. obj.]])'' - [[Attributes_in_Gramps|Attributes]] are for something permanent, or at least somewhat permanent: eye color, blood type, etc. Usually you would have not more than one of each attribute type for a [[#person|Person]]/[[#family|Family]]/etc. Attributes are managed from an Attributes tab in each [[#primary_object|primary Object]] Editor. There are a few pre-defined Attributes to support GEDCOM, but [[#custom|custom types]] will tend to be needed.

==B==
;Books Report:
A [[Gramps_{{man version}}_Wiki_Manual_-_Reports|Reports menu]] feature of Gramps that allows the [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_3|design or generation of a repeatable custom genealogy ''Book'']]. A Book consists of an ordered collation of Gramps textual and graphical reports in a single document. The individual report configuration options are also stored with the Book but the Book's document pagesize and print destination configuration options override.

;Bride: ''([[#event_role|event role]])'' A term to refer to the woman a marriage ceremony who will have the role of ''wife'' in the marriage. See also: ''mother''.

;BSDDB: ''([[Database_Backends|database backend]] engine)'' The [http://www.oracle.com/us/products/database/berkeley-db/overview/index.html Berkeley Software Distribution database] (also known as BSDDB) was the first ''default database engine'' used by the [[Database_Formats#Gramps_2.0|2.0]] through the [[Database_Formats#Gramps_5.0|5.0]] versions of Gramps. Originally, Gramps [[#xml|XML]] was used directly rather than as a Backup and data exchange format. The default db engine changed to [[#sqlite|SQLite]] in the 5.1 version via the [[DB-API_Database_Backend|DB-API Database Backend]]. ([[Install_latest_BSDDB|Manual updates to the BSDDB engine]] for the 5.1.3 version may be advisable.)

==C==
;Category: ''(core concept)'' Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of different descriptive schemas called Categories, each with their own [[#view|View]]. Each Category is a smaller, more digestible portion of the total information that comprises a Genealogical Tree. The View categories are: {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]], {{icon|peop}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People]], {{icon|rela}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships]], {{icon|fami}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Families_Category|Families]], {{icon|ance}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]], {{icon|even}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Events_Category|Events]], {{icon|plac}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places]], {{icon|geog}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography]], {{icon|sour34}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources]], {{icon|cite}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Citations_Category|Citations]], {{icon|repo}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Repositories_Category|Repositories]], {{icon|medi}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Media_Category|Media]], {{icon|note}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Notes]]

;Celebrant: ''([[#event_role|event role]])'' A term describing a role of the person who performs a rite, especially referring to a priest at the Eucharist.

;[[File:Gramps-citation.png|right]]Citation: ''({{icon|cite}} [[#primary_object|prim. obj.]])'' - Contains the information that enables you or others to locate your source document. An isolated [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_source_citations|Citation can be created]] without first creating separate [[#source|Source]] object. But, should the same source be referenced repeatedly in a Tree, a separate Source simplifies the Citation and eliminates redundant information that must be harmonized.

;Clergy: ''([[#event_role|event role]])'' A term applied to a religious person regardless of religion. For example, a monk or priest. See also: ''[[#celebrant|celebrant]]''.
: Religious terminology is often subject to dispute, see the [https://www.merriam-webster.com/dictionary/clergy Merriam-Webster] for an independent definition.

;[[File:Gramps_Clipboard48x48_win.png|right]]Clipboard: ''([[#gui|graphical user interface terminology]])'' - The [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Using_the_Clipboard|Gramps Clipboard]] is a shortcut system for [[#sharing|sharing]] a [[#secondary_object|secondary]] object, navigation, and custom [[#filter|filter]] creation.
: '''Usage:''' The Clipboard can be opened from a icon on the [[#toolbar|Toolbar]], from the Edit -> Clipboard menu choice or by using the Copy [[Gramps_{{man version}}_Wiki_Manual_-_Keybindings#7|keybinding]] for the Active Record in the Active main view of a View category. A floating clipboard dialog that has become buried can be brought to the top of the stack by selecting '''Clipboard...''' from the Windows menu.
: The Clipboard can greatly improve data entry efficiency, see the "[[How_to_use_the_Gramps_Clipboard|How to use the Gramps Clipboard]]" article for more information.

;Context menu: ''([[#gui|graphical user interface terminology]])'' - A [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Pop-up_menus|contextual pop-up menu]] (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Context_menu "context menu"]) is a menu that appears when right-clicking (or pressing the [https://wikipedia.org/wiki/Menu_key Menu keyboard key]) when the menu options directly relate to the item indicated by the mouse pointer. Thus, the indicated item provided the "context."

;''custom'' Types: This indicates a user-defined classification, as opposed to classifications that came pre-defined in Gramps. (i.e.: 'Birth' and 'Marriage' are 2 of the pre-defined 'types' of Events.)
:When none of the pre-defined Types are suitable, add a new ''[[#custom|custom]]'' Type by typewriting directly into the [[#selector_combo_box|selector combo box]]. If the value doesn't precisely match any of the existing menu items, a new ''custom'' Type will be created when the {{man button|OK}} button is clicked.
: Any added ''custom'' Type will remain available in that expanded menu... unless the Tree is exported and re-imported or removed via a [[Third-party_Addons|Third party addon]] Utility like [[Addon:Types_Cleanup_Tool|Type Cleanup]].
: '''''custom'' Types''' can be defined for: Event [[#attribute|Attributes]], Family [[#attribute|Attributes]], media [[#attribute|Attributes]], Person [[#attribute|Attributes]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#General|Event Roles]], [[Custom_Event_Types|Event types]], Family [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Relationship_Information|Relationship Information]] types, [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Child_Reference_Editor|Child Reference]] Types, [[Names_in_Gramps#Origin_Attributes|Name Origin Types]], [[Names_in_Gramps#Name_Types|Names Types]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_2#Note_editor_dialog|Note Types]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data%3A_detailed_-_part_2#Place_Editor_dialog|Place Types]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Repository_Reference_Editor|Repository]] Types, Source [[#attribute|Attributes]], [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Repository_Reference_Editor|Repository]] Media Types, [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Internet_Address_Editor|Internet Address (URL)]] Types.

==D==
;date: ''([[#secondary_object|sec. obj.]])'' - Dates in Gramps are much more complex than just a month, day, and year. Dates are always in a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Calendars|particular calendar]], can span a time frame with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_Type|Date Type]], the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_Quality|Date Quality]] can be exact (or an approximation variant), and have support for many other subtleties specific to genealogy data. The approximation can be fine-tuned with the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Limits|Limits]] preferences.
: The [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_formats_and_parsing_rules|date parsing rules]] are applied whenever data is entered into a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_dates|date text field]] or a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Date_selection_dialog|date selection dialog]].

;DNA:
# Acronym: '''d'''eoxyribo'''n'''ucleic '''a'''cid
# A [https://wikipedia.org/wiki/Nucleic_acid nucleic acid] that carries genetic information. Genetic testing compares for matching sequence lengths (measured in centimorgans, aka cMs) at various loci on specific chromosomes to determine common ancestry.

;Dock: ''([[#gui|graphical user interface terminology]])'' - A [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Pop-up_menus|dock]] is one of the multitude of containers offering controlled access and context to Gramplets. Gramplets can be added to, removed from, or undocked from a container to float free of the main window.
: The Dashboard was the original container and can be configured with multiple columns and stacks of Gramplets. The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|sidebar and bottombar splitbars]] are Category-specific containers. The splitbars only show a single gramplet at a time but with tabs to quickly switch between them. Each view mode has its own set of splitbars. So the basic configuration of Gramps has the Dashboard plus 24 Category view modes... or 49 separate gramplet containers.

;DTD:
:Acronym: '''D'''ocument '''T'''ype '''D'''efinition. A document that defines the tagging structure which identifies the individual components of an [https://wikipedia.org/wiki/Standard_Generalized_Markup_Language SGML] or [[#xml|XML]] document.
:See the [https://www.gramps-project.org/xml/ reference documentation for the versions] of Gramps [[Gramps_XML#RELAX_NG_generation|RELAX NG]] ('''RE'''gular '''LA'''nguage for '''X'''ML '''N'''ext '''G'''eneration)(<code>.rng</code>) schema [[#xml|XML]] and DTD

==E==
;[[File:Gramps-event.png|right]]Event: ''({{icon|even}} [[#primary_object|prim. obj.]])'' - Contains the information related to an happening. [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_events|Adding an Event record]] provides the context of an interaction of the roles of People/Families, dates & places in activities.
: An Event is a defining moment in a person's life. See [[events in Gramps|events]] for the use in genealogy, for predefined events in Gramps and suggested naming for [[Events_in_Gramps|common events]].

;event role: The [[#role|role]] a [[#person|Person]] plays in an [[#Event|Event]]. The focal Person(s) holds a [[#primary|'''''Primary role''''']] in personal Events and the Family holds a [[#family_role|'''''Family role''''']] in Family events. In Gramps, an Event can be linked to as many participants as desired. Each [[#person|Person]] may participate in different roles but more than one Person might play the same role. The Event Role captures this and can be changed in the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]]. Some common Roles are pre-defined but the user can add other [[#custom|custom]] Roles by just typing in the appropriate new label into the [[#selector_combo_box|selector combo box]].
:Pre-defined Types of Event Role: [[#aide|Aide]], [[#bride|Bride]], [[#celebrant|Celebrant]], [[#clergy|Clergy]], [[#family_role|'''''Family''''']], [[#godparent|Godparent]], [[#groom|Groom]], [[#informant|Informant]], [[#primary|'''''Primary''''']], [[#witness|Witness]], [[#unknown|'''''Unknown''''']], ''[[#custom|custom]]''

;event type: The general denominator to which an event belongs, <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, a christian, civil, tibetan, ... marriage, are all denoted by the event type ''marriage''. See [[events in Gramps]] for an overview.

==F==
;Fallback events:
:Certain [[#event|event]] types are definitive bookends marking the beginning or end of a life (Birth/Death) or relationship (Marriage/Divorce). Those bookend events are key factors in any kind of timeline analysis.
:If the definitive event types are missing, Gramps will look for similar event types to calculate a 'fallback' approximation. When dates are shown in italics, it indicates that the preferred bookend event was not found and one of the [[Events_in_Gramps#Fallback_Events|pre-defined Fallback events]] had to be used. Markers for some fallback events can be customized using the '''Genealogical Symbols''' tab of [[#preferences|Preferences]].

;Family:
#[[File:Gramps-family.png|right]]'''Family''' ''({{icon|fami}} [[#primary_object|prim. obj.]])'' - Contains the information specific to relationships between people. The information may be edited directly using the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_relationships|Edit Family]]}} dialog. This traditionally contains one or two parents and zero or more children. A family unit is created in Gramps by [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_brief#Specifying_a_relationship_using_the_Relationship_View|adding Parents to an individual]], by [[Add_a_spouse|adding a partner/spouse]] to an individual, or by adding a family first then adding the people. (A family can even consist of just the offspring.) The Family relationship is a core concept in Gramps. It depicts the basic relations between people. Commonly this will contain a father, a mother and some children, however, it can also contain only parts of this (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, two brothers, a mother and child). People can be part of several families (adoption, remarried, ...)
#'''Family''' ''([[#event_role|event role]])'' An event can be coupled to a family, denoting that the both partners were equally involved in the event. Typically, the Marriage event will be coupled to a family with event role ''family''. '''Family''' is the ''default'' role when adding a new Event in the [[#edit_family|Edit Family]] dialog.

;File Chooser:
:Picking external files or folders for import, export, reports and media is done using a File Chooser dialog from [https://wikipedia.org/wiki/GTK GTK] (formerly known as "GIMP ToolKit" and "GTK+") rather than those of the native Operating System. While generally familiar, the '''[[Gramps_{{man version}}_Wiki_Manual_-_Settings#File_Chooser|GTK File Chooser]]''' has customizable features, [[#context menu|context menus]], options and keybindings that are documented in the [[Gramps_{{man version}}_Wiki_Manual_-_Settings|Settings]] section of the manual.

;File formats:
: File formats repackage the Tree database information for archiving, data exchange with other software or display.
:* '''[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Import]] formats:''' GRAMPS v2.x database (obsolete) <code>.grdb</code>, Comma Separated Values <code>.csv</code> with [[Gramps_{{man version}}_Wiki_Manual_-_Settings#CSV_Dialect|configurable delimiter dialects]], GEDCOM (Genealogical Data Communication) <code>.ged</code>, GeneWeb <code>.gw</code>, Pro-Gen <code>.def</code>, vCard (virtual contact card) <code>.vcf</code>, JSON (JavaScript Object Notation) <code>.json</code>, SQLite <code>.sql</code>
:* '''[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|Export]] formats:''' Gramps native XML format (compressed & uncompressed variants) <code>.gramps</code>, Gramps Package (Gramps XML plus media) <code>.gpkg</code>, GEDCOM (Genealogical Data Communication) <code>.ged</code>, GeneWeb <code>.gw</code>, Web Family Tree (a GEDCOM variant) <code>.ged</code>, vCalendar <code>.ics</code>, vCard (virtual contact card) <code>.vcf</code>
:* [[Output_formats|'''Output formats''']] including: Comma Separated Values <code>.csv</code> with [[Gramps_{{man version}}_Wiki_Manual_-_Settings#CSV_Dialect|configurable delimiter dialects]], Data-Driven Documents (D3) <code><code>.d3</code></code>, Graphviz graph description language <code>.dot</code>, Hypertext Markup Language <code>.html .htm</code>, LaTeX <code>.tex</code>, Open Document Text <code>.odt</code>, Portable Document Format <code>.pdf</code>, Plain Text <code>.txt</code>, PostScript <code>.ps</code>, Print (hardcopy), Rich Text Format <code>.rtf</code>, Scalable Vector Graphics <code>.svg</code>, vCard (virtual contact card) <code>.vcf</code>, Extensible Markup Language <code>.xml</code>

;Filter:
: A [[Gramps_{{man version}}_Wiki_Manual_-_Filters|filter]] (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> query) in a database finds (or hides by 'filtering out') records, displaying only those records that match certain criteria. (The criteria are comparison or query [[#rule|rules]] describing some attribute of a record.) Layers of criteria can be applied but each layer requires additional processing and slows performance of the interface.
: The [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Filter_vs._Search|basic Search]] is a single criteria filter. The search value is compares only one attribute of a record that has been selected from a pop-up menu.
: The '''[[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Filter|Filter Gramplets]]''' will compare several predefined common attributes simultaneously with simplified access to changing the search value. The default is for exact matching but [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Regular_Expressions|Regular Expressions (RegEx)]] can be used for pattern matching. A Custom Filter may be also layered in.
: A [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Custom_Filters|Custom Filter]] adds richly complex [[#rule|Rules]]-based comparison with [[Example_filters|layers of intersection]] options for those rules. Custom Filters allow repeatable filters to be created with pre-defined rules and values to be matched. Beyond interactively hiding (or revealing) records in views, Custom Filters are used to set limits for exporting, setting scopes for reports, and targeting tool actions.
: In addition to the [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Which_filter_rules_in_which_Category.3F|builtin rules]] for filtering, [[Addon:Rule expansions]] are available for Custom Filters.

==G==
;GEDCOM:
# Acronym: '''Ge'''nealogy '''D'''ata '''Com'''munication
# A format for [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#GEDCOM_import|importing]] and [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|exporting]] genealogical data. The <abbr title="an open standard is a standard that is publicly available and has various rights to use associated with it, and may also have various properties of how it was designed such as 'open process.' There is no single definition and interpretations vary with usage.">open</abbr> specification for the [https://www.familysearch.org/developers/docs/guides/gedcom GEDCOM format] was developed by The Church of Jesus Christ of Latter-day Saints (LDS Church) as an aid to genealogical research. The long standing standard release was version 5.5 in 1996 with a 5.5.1 draft update presented for comment in 1999. (Belatedly, the 'draft' label was officially removed in the annotated 2019 release. After 20 years as the de facto standard format, it remained unimproved excepting for 2 tags and the copyright.)
::As an Open Standard, there are extensive and constantly changing incompatibilities between implementations and data loss when transferring GEDCOM formatted data between competing software tools is common. Gramps has implemented a variety of [[GEDCOM|GEDCOM support features]].
::GEDCOM [https://www.familysearch.org/developers/docs/guides/gedcom-x X proposed in 2012] and [https://blog.eogn.com/2019/10/04/the-proposed-gedcom-5-5-5-standard-is-a-better-gedcom/ 5.5.5 proposed in 2019] are improvements that have not gained the approval of the copyright holder. As of June 2021, these proposals have been superseded by the GEDCOM 7.0.1 version.

;Godparent: ''([[#event_role|event role]])'' - A term to refer to the person who presents a child at a christening or baptism and promises to take responsibility for guiding the child emotionally, practically, and spiritually. This person will be referred to as ''godfather'' or ''godmother'' after the christening or baptism. See also: ''[[Add_a_godfather-godmother|Add a godfather-godmother]]''.

;Gramplet: A [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#definition|Gramplet]] is a plug-in (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Software_widget widget] or [https://wikipedia.org/wiki/Applet applet]) that can be [[#dock|docked]] in the {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]] category view. Later [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Bottombar_and_Sidebar|sidebar or bottombar]] were added to the remaining [[#view|views]] to extend [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Gramplet_Bar_Menu|adding]] and [[#undock|undocking]] a Gramplet functionality of those view.
: Gramplets dynamically update as the different records are selected in the main display area of a view. Gramplets typically create an alternate interface to your Family Tree data. Collections of [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Summary_of_Gramplets|builtin]] and [[{{man version}}_Addons#Addon_List|"3rd party addon"]] gramplets are available for [[{{man version}}_Addons#Installing_Addons_in_Gramps|installation]] and download with the [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager|Plug-in Manager]]. The Plug-in Manager also regulates a [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Aren.27t_all_Plugins_also_Gramplets.3F|wide variety of other builtin and addons]] which can expand functionality unrelated to the interface.
: ''See the [[Gramplets development]] for independent information.''

;Gramps for Desktops: [https://gramps-project.org/blog/features/ Gramps] is an open-source genealogy application, a free software project and community.
: '''Gramps''' is an affectionate nickname for a "Grandfather". Originally, the all capital letter [https://wikipedia.org/wiki/Backronym backronym] stood for "'''G'''enealogical '''R'''esearch and '''A'''nalysis '''M'''anagement '''P'''rogramming '''S'''ystem" and was coined by Larry Allingham. ([https://gramps-project.org/blog/2006/04/looking-back-over-5-years/ GRAMPS was created around 2001] by [[User:Don|Don Allingham]] for use by his father, Larry.) This backronym was phased out around March 2010 in favor of '''Gramps''' as the official name of the software. All upper-case acronym-based names have become unfashionable for software.''

;Gramps Web for Servers: [https://gramps-project.org/blog/web/ Gramps Web] is collaborative interface (frontend) and backend created by David M. Straub for running the Gramps genealogy database engine on servers. It is one of the [[Web_Solutions_for_Gramps|Web Solutions for Gramps]].
: It is a multi-user system genealogical web application with different levels of options for Visitors, Members, Contributors, Editors, and Owners. Trees in [[https://www.grampsweb.org Gramps Web on a server]] can be synchronized with the more mature and feature laden [[#gramps|Gramps for Desktops]]. Single Tree or multiple Tree sites can be self-managed on a hosted service from an ISP, leased from a managed hosting ISP, or leased from an application-specific fully managed CMS provider, or installed locally for access from a local area network.

;Graphical User Interface (GUI): A visual way of indicating interactive features of a computer operating system or application/program.
:The '''Gramps for Desktops''' GUI is introduced in [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|Visual Guide to Gramps Interface]]. It uses a "windows, icons, menus, pointer" ([https://wikipedia.org/wiki/WIMP_(computing) WIMP]) based approach with [https://wikipedia.org/wiki/Post-WIMP post-WIMP] elements like hyperlinked redirection and custom interface objects. The desktop interface is built with [https://wikipedia.org/wiki/GTK Gtk] (the Gimp Toolkit), a free and open-source cross-platform widget toolkit for creating graphical user interfaces.
:The appearance and interaction may vary by conventions dictated by the [[Download|Operating System (OS)]], installation option (such as [[Portal:Translators|language localization support]] or [[{{man version}}_Addons|addon/plug-in]]), [https://wikipedia.org/wiki/Theme_(computing) theme] (at the OS or [[Addon:ThemePreferences|internal]] levels), and/or [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Preferences|user preferences customization]].
:The specific interface elements are identified by customary name, general appearance & behavior in the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|Visual Guide to Gramps Interface]]. Expansion interface elements are described in the user documentation for [[{{man version}}_Addons|each specific addon]].
: The '''Gramps Web''' GUI (or frontend) is a platform-agnostic web browser interface built with the [https://lit.dev/ Lit] lightweight JavaScript library for building fast, interoperable web components. Although the hosting side requires a webmaster with significant skills, genealogical collaborators can use web browser on almost any device.

;Groom: ''([[#event_role|event role]])'' - A term to refer to the man at a marriage who will be referred to as ''husband'' after the marriage. See also: ''[[Add_a_spouse|Add a spouse]]''.


;GUI: An acronym. ''see [[#graphical user interface|Graphical User Interface]]''.

==H==
[[File:Gramps Go-Home48x48 win.png|right]]
;Home Person: ''(core concept)'' - The persistently designated '''Home Person''' is the foundational [[#person|Person]] (the [[Genealogy_Glossary#proband|Proband]], [[Genealogy_Glossary#progenitor|Progenitor]], or [[Genealogy_Glossary#progenitrix|Progenitrix]]) in the Tree (the currently open Gramps database). This Person is the central target of genealogical research and family references extend from this center. Ideally, every person, event and source in the Tree will (however directly or indirectly) relate back to the '''Home Person'''.
: By default, the database reports describe everything else in contextual relation to this person. The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Status_Bar_and_Progress_Bar|Status Bar]], the [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Quick_View|Quick View]] called "[[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Relation_to_Home_Person|Relation to Home Person]]", and the Third party addon [[#gramplet|Gramplet]] called "[[Addon:Deep_Connections_Gramplet|Deep Connections]]" all describe different aspects of the relationship of the [[#active_person|Active Person]] to the '''Home Person'''.
: You (or your client) are customarily designated ([[Gramps_{{man version}}_Wiki_Manual_-_Settings#Setting_Home_person|set]]) as the Home Person. And this ''Home'' designation serves as a persistent point of reference for the rest of the Tree in Reports generally and for the Active Person in detail. But a different '''Home Person''' might be temporarily [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Setting_Home_person|set]] when generating reports or when researching a complex biography or obituary.
: Fascinating tidbits often lure Gramps researchers into wandering off-course. When the [[#active_person|Active Person]] has become lost, the bearings can be instantly regained by navigating the [[#active_person|Active Person]] selection back to the '''Home Person'''.
: Navigate to '''Home Person''' - ''keyboard shortcut'' {{man key press|Alt|Home}} or press the toolbar [[File:Gramps_Go-Home48x48 win.png|text-bottom|20px]]{{man button|Home}} button.
: The custom filter rule for finding the '''Home Person''' is in a People category filter under the General filters and was named 'Default person' until the 5.1 version.

==I==
;Informant: ''([[#event_role|event role]])'' - A term to refer to the [[#role|Role]] of Person who reports an [[#event|Event]].

==J==
;JSON: Acronym: [https://wikipedia.org/wiki/JSON '''J'''ava'''S'''cript '''O'''bject '''N'''otation]. JSON is a lightweight, text-based data format designed to be easy for humans to read while still structured enough for machines to parse efficiently. It organizes data in key-value pairs, allowing information to be grouped together in a clear and straightforward way.

==K==
;Keybinding: Keyboard shortcuts (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> hotkeys) key (or combination of keys) that can be used to navigate a Graphical User Interface (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [[#gui|GUI]]) as an alternative to using the mouse. A single keystroke (or combination of keys on a keyboard) executes a command.
:''see [[Gramps_{{man version}}_Wiki_Manual_-_Keybindings#toc|Gramps GUI keybindings]]''

==L==
==M==
;Matronym:
:''([[#name_origin|Name origin]] attribute)'' - Personal name based on the name of one's mother

;[[File:Gramps-media.png|right]]Media: ''({{icon|medi}} [[#primary_object|prim. obj.]])'' - Contains the information related to a media object. Media objects include images, videos, audio recordings, documents, webpages or any other type of related files.
:When new Media objects are edited from the Gallery tabs of Object Editors or from the Media category view, the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_media_objects|New Media editor]] allows the metadata to be modified.

;[[File:Gramps_Merge48x48_win.png|right]]Merge
:To combine the objects in two selected rows in a [[#view_category|category view]] into a single object. This reduces duplicates while consolidating references and [[#secondary_object|secondary objects]]. The [[Merging_people|merge process]] involves selecting two rows (a target row to be kept and a row to be deleted) then choosing '''Merge''' from the Toolbar or Edit menu. Choices are offered about which secondary objects take precedence when there are conflicts, but no data (except one of the descriptions in an Event merge) is lost by default. All secondary objects from both selected rows are conveyed to the surviving merged row. Only two objects may be merged at a time unless using addon tools designed for multiple object merges or batches of merges.

;Mode:
:''See [[#viewmode|View mode]]''

==N==
;Name Origin:
:An optional attribute (characteristic) identifying how a name was derived for a [[#person|Person]]. Pre-defined items of the [[Names_in_Gramps#Origin_Attributes|origin selection menu]] include: inherited, patrilineal, matrilineal, given, taken, [[#patronymic|patronymic]], [[#matronymic|matronymic]], feudal, pseudonym, occupation. The Name Origin of [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Multiple_Surnames|Multiple surnames]] and [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Names|Alternative names]] can be added from the [[#edit_person|Edit Person]] dialog.
: ''Available as a standard attribute of [[Names_in_Gramps|Names in Gramps]].''

;Navigator:
: ''([[#gui|graphical user interface terminology]])'' - The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Navigator|Navigator]] is a Gramps-specific name for a left sidebar layout of [[#category|category]] view icons, allowing movement between (aka 'navigating') the different View categories. There are [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Switching_Navigator_modes|multiple layout modes]] and a [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Environment_Settings|text label preferences option]] for the sidebar. This sidebar may be hidden or revealed from the menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Navigation#View|View ->Navigator]]}} or by using the [[Gramps_{{man version}}_Wiki_Manual_-_Keybindings#7|keybinding]]. Navigator layout modes are 'Sidebar' type [[#plugin|plugins]] that can be added, removed, hidden or revealed using the Plugin Manager.
: Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of [[#category|Categories]], each with their own View. Each of the Category Views displays a smaller, more digestible portion of the total information that comprises a Genealogical Tree. The View categories are: {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]], {{icon|peop}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People]], {{icon|rela}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships]], {{icon|fami}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Families_Category|Families]], {{icon|ance}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]], {{icon|even}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Events_Category|Events]], {{icon|plac}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places]], {{icon|geog}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography]], {{icon|sour34}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources]], {{icon|cite}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Citations_Category|Citations]], {{icon|repo}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Repositories_Category|Repositories]], {{icon|medi}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Media_Category|Media]], {{icon|note}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Notes]]

;[[File:Gramps-notes.png|right]]Note: ''({{icon|note}} [[#primary_object|prim. obj.]])'' - Contains the information representing a textual brief record of facts and how it [[#reference|references]] other objects in the Tree. Notes can be added to any object at any any level of the Tree and are often used to detail the context of that record in the Tree.
:Records in the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Note Category]] contain free-form text with [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Note_markup_and_preformat_in_reports|basic formatting]] and [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Link_Editor|linking]] features. Notes can be categorized by [[#tag|Tag]] and [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#note_type|Type]] in addition to the object to which it is attached. That information is created and modified using the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_notes|Notes Editor]].

==O==

;Object: The most basic framework unit of genealogical data as structured in the Gramps [[Gramps_Data_Model|data model]].
:The most complex structures are the [[#primary_object|Primary Object]] of a [[#category|category]]. Each has an [[#object_editor|Object Editor]] that organizes entering data in that structure but also allows attaching or creating [[#secondary_object|secondary objects]].

;Object Editor ''(<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> Edit Object dialogs)'':
: ''(core concept)'' - The object editor dialogs show the basic info of the [[#primary_object|Primary Object]] in the structured form of the header area where it can be directly edited. And the bottom tabbed section allows the editing of interrelationships with [[#secondary_object|secondary objects]] and provides access to the Object Editors for those secondary objects.
:Click the following links for instructions of how to open and use each type of Edit Object dialog.
:The available categories of object editor dialogs are: {{icon|peop}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_people|Edit Person]]}}, {{icon|fami}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Editing_information_about_relationships|Edit Family]]}}, {{icon|even}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_events|Edit Event]]}}, {{icon|plac}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_places|Edit Place]]}}, {{icon|sour34}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_sources|Edit Source]]}}, {{icon|cite}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_source_citations|Edit Citation]]}}, {{icon|repo}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_repositories|Edit Repository]]}}, {{icon|medi}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_media_objects|Edit Media]]}}, {{icon|note}} {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_notes|Edit Note]]}}
:The available categories of object reference editor dialogs for [[#sharing|shared objects]] are: {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Person_Reference_Editor|Person Reference Editor]]}} ''(see [[#association|Associations]])'', {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Child_Reference_Editor|Child Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Place_Reference_Editor|Place Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Repository_Reference_Editor|Repository Reference Editor]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Media_Reference_Editor_dialog|Media Reference Editor]]}}

;Officiator: ''([[#event_role|event role]])'' - A term to refer to the role of a person authorized to conduct an official duty or function. (Such as performing a marriage or funeral ceremony or conferring a vocational degree.) Jurisdiction may be derived from a from holding a position of civil or religious authority. Use 'OFFICIATOR' rather than 'Officiant' for [[#gedcom|GEDCOM7]] Roles compatibility.

==P==
;patronym:
:''([[#name_origin|Name origin]] attribute)'' - Personal name based on the name of one's father.

;[[File:Gramps-person.png|right]]Person: ''({{icon|peop}} [[#primary_object|prim. obj.]])'' - Contains the information specific to an individual person in the People category. The information may be edited directly using the [[#edit_person|Edit Person]] dialog.

;[[File:Gramps-place.png|right]]Place: ''({{icon|plac}} [[#primary_object|prim. obj.]])'' - The Gramps concept of a Place is a particular location independent of time. Over time, the same Place may have different hierarchical (or name) information due to changing borders and political situation. For example, Leningrad and St. Petersburg represent the same place, but with different names. Places in Gramps are stored in a hierarchy and are direct accessed via the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places category view]]. Places can be defined (or refined) through the Place Editor and shared with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Select_Place_selector|Select Place]] object selector. A Place consists of:
:* Descriptive Title
:* Name (with optional date span and language attributes)
:* A list of alternative names for the place
:* Type ([[#administrative_division|administrative divisions]] such as country, state, county ...)
:* Longitude/Latitude
:* Code (such as a country code or postal code)
:* A hierachical list of regions which enclose the place

;plugin: (<abbr title="also known as — abbreviation used to indicate another name that a person/thing has/uses">''aka''</abbr> [https://wikipedia.org/wiki/Plug-in_(computing) plug-in])
:* A type of [[Writing_a_plugin|expansion framework that allows Gramps customization]] by providing interface hooks to recognize and use external code.
:* A customized module of code built to provide a specific feature or functionality that is not part of the core program.
:The [[Addon_list_legend#Type|various types]] of Gramps plugin code modules can be enabled or disabled via a [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager|plugin manager]]. Plugin types include: Citation formatter, [[Database_Backends|Database]], Doc creator, Exporter, [[#gramplet|Gramplet]], Gramps View ([[#view|''Category'']] or [[#viewmode|''mode'']]), Importer, [[Map_Services|Map Service]], Plugin lib, [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Quick_Views|Quickreport'''/'''Quickview]], Relationships, [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_1|Report]], [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Add_Rule_dialog|Rule]], Sidebar, Thumbnailer [[Gramps_{{man version}}_Wiki_Manual_-_Tools|Tool]].
:Plugins can be builtin ''(included with the normal distribution of Gramps)'' or an [[{{man version}}_Addons#Addon_List|addon]] ''(installed via the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Third_party_addons_management|Third party addons management]] in Preferences)''.

;POSIX: [https://wikipedia.org/wiki/Posix Portable Operating System Interface]: a family of OS standards specified by the [https://wikipedia.org/wiki/IEEE_Computer_Society IEEE] Computer Society for maintaining compatibility with variants of Unix (such as Linux) and other operating systems. Although the MacOS is "POSIX-certified", the term is used in this manual to generically refer to just the "Mostly POSIX-compliant" Linux and BSD distributions [[Download#Linux_and_BSD_distributions|with verified Gramps downloads]] and which use the POSIX-style [https://wikipedia.org/wiki/Filesystem_Hierarchy_Standard environment].

;Preferences: The {{Man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Preferences|Preferences]]}} is an option in the {{Man menu|Edit}} main menu that allows '''''global''''' customization of the appearance, defaults and behavior of Gramps. The customizations are categorized into the following tabs: {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Data|Data]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#General|General]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Family_Tree|Family Tree]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Import|Import]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Limits|Limits]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Colors|Colors]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Genealogical Symbols|Genealogical Symbols]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#ID_Formats|ID Formats]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Text|Text]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Warnings|Warnings]]}}, {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Researcher|Researcher]]}}.
:(A {{man label|[[Addon:ThemePreferences|Theme]]}} tab is available as an addon.)
:(see also ''{{Man menu|Configure...}}'' option in the {{Man menu|View}} main menu is an option. Those customization are limited to the currently active view and its Gramplets. The feature may also be accessed by the {{man button|Configure...}} toolbar icon.)
:The Gramps 5.1 and older preferences are categorized into the following tabs: {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#General|General]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Family_Tree|Family Tree]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Display|Display]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Text|Text]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#ID_Formats|ID Formats]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Dates|Dates]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Researcher|Researcher]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Warnings|Warnings]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Colors|Colors]]}}, {{man label|[[Gramps_5.1_Wiki_Manual_-_Settings#Genealogical Symbols|Genealogical Symbols]]}}.

;Prerequisites: Additional software required to make certain features of Gramps work and or some [[:Category:Prerequisites|addons]].

;Primary object: Primary objects are the [[Using_database_API|data structures]] at the top level of a [[Gramps_Data_Model|hierarchical collection of records]] in the Gramps [[Gramps_Data_Model|data model]]. Beside the main structure of data, they can contain a hierarchy of [[#secondary_object|secondary objects]], and can be referenced by other primary or secondary objects. In the Gramps database, primary objects and the secondary objects that they contain are stored as separate records. Each primary object type is stored in a separate table. See [[Using_database_API#Primary_Objects|Using database API, Primary Objects]] (see also ''[[#secondary_object|secondary object]]'')
: The types of [[Using_database_API#Primary_Objects|primary objects]] are:
: {{icon|cite}} [[#citation|Citation]], {{icon|even}} [[#event|Event]], {{icon|fami}} [[#family|Family]], {{icon|medi}} [[#media|Media]], {{icon|note}} [[#note|Note]], {{icon|peop}} [[#person|Person]], {{icon|plac}} [[#place|Place]], {{icon|repo}} [[#repository|Repository]], {{icon|sour34}} [[#source|Source]], [[File:16x16-gramps-tag.png]] [[#tag|Tag]].

;Primary role: ''([[#event_role|event role]])'' - A term to refer to the [[#role|role]] of the focal participant of an [[#event|Event]]. '''Primary''' is the ''default'' role when adding a new Event in the [[#edit_person|Edit Person]] dialog.

;[[File:gramps-lock.png|right]]Private flag or tag:
: The Private option identifies sensitive information that should be redacted when sharing data or printing reports. ''(This marker should not be confused with the generic user-definable [[#tag|Tags]] used for custom filters and color highlighting.)'' Records are shown with: a [[File:22x22-gramps-lock.png]]locked padlock when private; and, an [[File:22x22-gramps-unlock.png]]unlocked padlock when public. Clicking the padlock icon toggles between Private & Public flags. This manual override supplements the automated [[Gramps_{{man version}}_Wiki_Manual_-_Probably_Alive|Probably Alive]] and custom [[Filter|Filter]] features which help Gramps to respect Personal Privacy.
:Gramps is a single user database and omits the typical security features of a multi-user system. So even "Private" data will be accessible from within Gramps. However, generating reports and exporting data default to redacting information flagged as Private.

;[[File:gramps-unlock.png|right]]Public tag or flag:
: The Public option identifies information that should be included when sharing data or printing reports. Records are shown with: a [[File:22x22-gramps-unlock.png]]unlocked padlock when public; and, an [[File:22x22-gramps-lock.png]]locked padlock when private. Clicking the padlock icon toggles between Public & Private flags. By default, all records are created as Public.

==Q==
;Quick View: On-screen [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Quick_Views|reports]] about information surrounding the active object that do not print or save to file. Generally the report is selected from a [[#context_menu|context menu]] for the selected category of record and will have no configurable options.
: The [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Quick_View|Quick View '''gramplet''']] refreshes a builtin [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_8#Quick_Views|builtin]] or [[{{man version}}_Addons#Addon_List|addon]] QuickView reports as the focus of the active record is changed. The specific QuickView report is selected in a view configuration dialog opened with the {{man menu|View -> Configure...}} menu.

==R==
;Reference: The basic system of linking relationships between objects in Gramps. When an object is added in the Editor for record, a [[References#definition|Reference]] (link) is created in the object that was added.

;[[File:Gramps-relation.png|right]]References tab: When objects of Gramps are linked, the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#References|References tab]] lists the objects to link toward it.

;Regular Expressions: [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Regular_Expressions|RegEx]] is a system to specify a text string pattern for comparing and matching. Optionally used to extend a power of the Filter Gramplets and Custom Filters rules.
:Filters in [https://gramps.discourse.group/t/which-regex-syntax-does-gramps-use/2278/8 Gramps use the RegEx format specified by the installed version of Python]

;Re-order
:[[File:Stock_reorder.png|right]]To change the sequence of items within a list of [[#secondary_object|secondary objects]]. [https://gramps.discourse.group/t/re-ordering-data-in-gramps-topic-expansion-outline-for-wiki/5568 The interface for (and consequences of) re-ordering that sequence varies based on the list type.]
:The natural order of a list follows when the data was created. The first item in an ordered list is often considered the primary or preferred item of that type. The primary/preferred may be the only object considered in some charts and analyses. So when data entry of related objects was out of sequence, a re-ordering option becomes necessary.
:Re-ordering affects display order in the Tree, charts, and most reports. Note that in some contexts, dates can override the manual order, particularly for Places and Names.

;[[File:Gramps-repository.png|right]]Repository: ''({{icon|repo}} [[#primary_object|prim. obj.]])'' - Contains the information related to a physical or virtual structure where genealogical and family history sources are stored. Once a [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_repositories|Repository is added]] to a Gramps Tree, it can used to organize [[#source|Sources]].

;Role: Function performed or part played by a person (or other Gramps [[#object|object]]) in a particular situation. When objects of Gramps are linked, a Reference is created where the implicit Role disambiguates the relative nature of the reference. ''For explicitly defined roles, see [[#event_role|event role]] and [[#association|association role]]''

;Romanization:
: Linguistic representation of a word in the Roman (Latin) alphabet

;Rule: A pre-defined abstraction that simplifies the interface for a structured query about a particular facet of your family tree. Rules allows users to choose search criteria without needing to understand the intricate details of the actual database query language. Rules are layered via the [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Custom_Filters|Custom Filters]] interface to [[#filter|filter]] with complex criteria.

==S==
;Secondary object: Secondary objects are contained within other [[#object|objects]] of the structured Gramps [[Gramps_Data_Model|data model]], and cannot be referenced directly. They can contain other secondary objects. Examples include: Name, Date and Address. See [[Using_database_API#Secondary_Objects|Using database API, Secondary Objects]] (see also ''[[#primary_object|primary object]]'')

;Selector combo box: ''([[#gui|graphical user interface terminology]])'' - a [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Selector_Combo_Boxes|standard text entry box paired with pull-down list button]] is a [https://docs.gtk.org/gtk3/visual_index.html Gtk toolbox widget] (based on the standard [https://wikipedia.org/wiki/Combo_box combo box]). The combination of a drop-down list and a single-line editable textbox allows the user to: either key in a value directly; or, select a value from the list. Moreover, keying in a value that is not already in the list will add that [[#custom|custom type]] to the drop-down list.

;Shared objects: {{icon|share}} Sharing allows an Object to be linked at multiple places in the tree. Doing so establishes a relationship or maintains single set of attributes (or [[#secondary_object|secondary objects]]) that they hold in common. ([[#role|Roles]] for shared Events define the person or family participation level.)
:'''[[#object_reference_editors|Object Reference Editors]]''' allow updates to a shared object to be reflected in all instances mentioning (referencing) that shared object. Redundantly creating object with the same information should be avoided. (So, refining a Transcription Note shared by multiple Citations will show the updated transcription in all the Citations.)
:Object descriptions are grouped in two distinct sections:
:  • The '''Reference Information''' section contains information unique to one instance.
:  • The '''Shared Information''' of an object will be seen in all instances that are linked to it.

;Selector: Combo interface box that allows you to select an object. The [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Selector_dialogs|Select Family selector]] is one example.

;[[File:Gramps-source.png|right]]Source: ''({{icon|sour34}} [[#primary_object|prim. obj.]])'' - Sources can be a person ''(family, friend, another researcher)'', thing ''(book, magazine newspaper, census)'', or place ''(courthouse, church, library, genealogical/historical society... although places might be better handled as Repositories)'' from which information comes, arises, or is obtained. After [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_sources|adding a Source]] with the [[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#New_Source_dialog|new source dialog]] to the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources category]] of a Gramps Tree, the Source can be referenced when adding a [[#citation|Citations]] and organized within [[#repository|Repositories]]. The same Source may exist in multiple Repositories and may have different Media Types (such as book, microfilm, or electronic) and Call numbers in each Repository.
:[[Sources#Definition|[more]]]

;SQLite: ''([[Database_Backends|database backend]] engine)'' - The [https://sqlite.org/about.html SQLite project's in-process library] (also known simply as SQLite) is the ''default database engine'' used since the [[Database_Formats#Gramps_5.1|5.1]] version of Gramps. The support was extended from [[#bsddb|BSDDB]] in the 5.0 version via the [[DB-API_Database_Backend|DB-API Database Backend]].

;Swatch: ''([[#gui|graphical user interface terminology]])'' - A [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Pick_a_Color_selector|color swatch]] is a sample square of a color or color pattern. Swatches may be dragged from the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Pick_a_Color_selector|Pick a Color selector]] to apply that specific color to preferences.
:The word originally referred to sample pieces of cloth or fabric used for choosing or testing colors, patterns, or textures for interior or exterior design. It now means any small sample or representation of a larger whole and is commonly usage in the context of color representation and selection in software applications.

==T==
;[[File:gramps-tag.png|right]]Tag: ''([[File:16x16-gramps-tag.png]] [[#primary_object|prim. obj.]])'' - A custom titled and color-coded label that [[Gramps_{{man version}}_Wiki_Manual_-_Filters#Tagging|can be created with the Organize Tags dialog and attached]] to selected {{icon|cite}} [[#citation|Citation]], {{icon|even}} [[#event|Event]], {{icon|fami}} [[#family|Family]], {{icon|medi}} [[#media|Media]], {{icon|note}} [[#note|Note]], {{icon|peop}} [[#person|Person]], {{icon|plac}} [[#place|Place]], {{icon|repo}} [[#repository|Repository]] or {{icon|sour34}} [[#source|Source]] objects for the purpose of easy identification and filtering.
: A keyword or phrase used to group the collection to produce a report. Multiple tags may be used to label and categorize objects into multiple groups when filtering by other attributes is not viable.

;Toolbar: ''([[#gui|graphical user interface terminology]])'' - The [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Toolbar|Toolbar]] is a ribbon (located below the application menubar) with button shortcuts for the most widely needed functions associated with the current view. The selection of buttons changes in response to the context of the current view. (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, toolbar buttons for switching mapping [[#view_mode|view modes]] will only appear for the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography view]].)

;Typographical conventions: The [[Gramps_{{man version}}_Wiki_Manual_-_Preface#Typographical_conventions|customary formatting]] having special (and possibly peculiar) meaning when used throughout the MediaWiki driven [[Gramps_{{man version}}_Wiki_Manual|Gramps manual]] and documentation. The different typeface accents, highlighting and enclosures indicate specific parts of the Gramps [[#graphical user interface|Graphical User Interface]] ([[#GUI|GUI]]) or prompt a User activity.

==U==
;Unknown: ''([[#event_role|event role]])'' - A placeholder for when the [[#role|role]] of a participant in an [[#event|Event]] has not yet been defined. Gramps sets an appropriate default Role as each new Event type is created. But when a new participant is associated with an existing Event via Share or drag'n'drop, the Role isn't as predictable. In such a case, an Unknown placeholder is inserted.
:Any Unknown [[#event_role|Event Role]] type causes a variety of reporting problems. [[Addon:Rule_expansions#People_with_events_with_a_selected_role|(Rule_expansions)Persons and Families with Unknown Roles]] should be found and the Roles manually replaced as soon as is practical.

;User Directory: ''(core concept)'' - An alias for the file folder (directory) location where customizations (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>: preferences files, [[#addon|addons]], [[#plugin|plugins]]) are stored for the Gramps family of genealogy tools. Since this folder location varies by which Operating System and which Gramps fork has been installed, the '''User Directory''' is an 'alias' (a.k.a. placeholder) used in instructions about re-configuring Gramps.
: This alias allows [[Gramps_{{man version}}_Wiki_Manual_-_User_Directory|instructions for locating your specific '''User Directory''' file location]] to be consolidated in the documentation.

==V==
;View category: ''([[#gui|graphical user interface terminology]])'' - a [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|'''View category''']] (often simply called a "'''[[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|View]]'''") is a Gramps-specific name for the collection of [[#view mode|View modes]] (display layouts) presenting information in a structured and predictable manner. Different Views are selected from the [[#navigator|Navigator]] (left sidebar).
: Layouts are in table, outline or graphical formats, depending on the preferred way to represent how the data elements relate to one another.
: Gramps divides and organizes the information about each [[#primary_object|Primary Object]] into a series of [[#category|Categories]], each with their own View. Each of the Category Views displays a smaller, more digestible portion of the total information that comprises a Genealogical Tree. The View categories are: {{icon|gram}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard]], {{icon|peop}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People]], {{icon|rela}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships]], {{icon|fami}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Families_Category|Families]], {{icon|ance}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Charts_Category|Charts]], {{icon|even}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Events_Category|Events]], {{icon|plac}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Places_Category|Places]], {{icon|geog}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Geography_Category|Geography]], {{icon|sour34}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Sources_Category|Sources]], {{icon|cite}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Citations_Category|Citations]], {{icon|repo}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Repositories_Category|Repositories]], {{icon|medi}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Media_Category|Media]], {{icon|note}} [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Notes_Category|Notes]]

;View mode: ''([[#gui|graphical user interface terminology]])'' - a '''[[Gramps_{{man version}}_Wiki_Manual_-_Main_Window|View mode]]''' is a Gramps-specific name for the display layouts presenting [[#view_category|View category]] information in a structured and predictable manner. A [[#view_category|View category]] may have alternate '''view modes''' (subcategories) of display layout. (<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, Views with Table layouts might have flat listed or hierarchically grouped modes.) Navigating between View modes is from the [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Toolbar|toolbar]] and [[Gramps_{{man version}}_Wiki_Manual_-_Main_Window#Switching_Navigator_modes|Navigator]].
: Each mode of a category can be independently [[File:Gramps-config.png|22px]] configured. Each mode may maintain a separate object selection, filtering, and organization for its Gramplet bars.
: View data may be further subdivided with tabbed pages of layouts.

==W==
;wiki: (Hawaiian [https://wikipedia.org/wiki/Loanword loanword]) meaning 'quick'; or 'wikiwiki' meaning 'very quick'. For Gramps users, '''''[[User manual|the Wiki]]''''' (a.k.a. '''''[[User manual|Wiki Manual]]''''') refers to the collaborative website of educational material which is organized using the [https://mediawiki.org/wiki/MediaWiki MediaWiki] [https://wikipedia.org/wiki/Content_management_system content management system]. The core pages of that website being the structured reference-style [[#gramps|Gramps]] software user's operating guide. ''(Note that specific [[:Category:Tutorials|tutorial]] documents are also part of the wiki.)''
:For most internet users, the word is most often an inadvertent allusion to the 1995 [http://wiki.c2.com/?WikiWikiWeb WikiWikiWeb], the first website that builtin tools encouraging users to quickly & easily collaborate to expand the content of the site. See the term: [https://wiktionary.org/wiki/wiki 'wiki'] in [https://wiktionary.org/wiki/Wiktionary Wiktionary]

;Witness:''([[#event_role|event role]])'' - The term that applies to the people asked to be present at an event so as to be able to testify to its having taken place.

==X==
;XML: acronym: [https://wikipedia.org/wiki/XML E'''x'''tensible '''M'''arkup '''L'''anguage]. A schema used to define the expected structure of data in a text format. The system annotates a document in a way that data elements are syntactically distinguishable from identifying tags. A markup language defines a set of rules for encoding documents in a fault tolerant format that is both (marginally) human-readable and machine-readable.
: Gramps will [[Generate_XML|generate XML]] format natively in compressed and uncompressed forms identified with a <code>.gramps</code> or <code>.gpkg</code> file extension. It is the format that definitively supports every piece of genealogical data stored by Gramps. Used as the working format until Gramps 2.0 started using a ''[[Database_Backends|database backend]]'' to improve performance, XML is now the standard Tree data backup format and recommended data exchange format.
: See the [https://www.gramps-project.org/xml/ reference documentation for the versions] of Gramps [[Gramps_XML#RELAX_NG_generation|RELAX NG]] ('''RE'''gular '''LA'''nguage for '''X'''ML '''N'''ext '''G'''eneration)(<code>.rng</code>) schema XML and [[#dtd|DTD]]

==Y==
==Z==

{{man tip|1=Wiki manual|2=Please enhance the {{man label|Wiki}} - create new glossary terms and add them to the wiki manual. Glossary term IDs are more memorable & predictable if kept to all lower-case. When translating the Glossary, please leave the English ID anchors but also add translated variants of the same anchor. This allows users to look up a term in either language.

Inserting a "Glossary Term" into the Glossary list: 
<code><nowiki>;Glossary Term: Definition of the term.</nowiki></code> 
Do not replace a space in the anchor ID with an underscore. An anchor defined with a space can match both the underscore and space form, but an anchor defined with an underscore can only be referenced by the underscore form.

In a translated Glossary, add the English ID by putting an extra span around the translated header: 
<code><nowiki>;Translated Term: Translated definition of the term.</nowiki></code>

Referencing the glossary term in the Gramps wiki manual: 
<code><nowiki>[[Gramps_Glossary#glossary_term|Glossary Term]]</nowiki></code> 
(Note the optional underscores for spaces here.)

For more information about WikiMedia sections, see: 
<code>https://meta.wikimedia.org/w/index.php?title=Help:Section#id_with_space</code>

}}

[[Category:Gramps terminology|*]]
[[Category:Translators/Categories]]
[[Category:Documentation]]

Template:Latindict/N

2026-03-13T20:43:32Z

DomoViridi: Abbreviations: Changed "default" parameter to "full"

{{dict|lang ={{{1}}} |word=n., nat.|full=natus|}}
{{dict|lang ={{{1}}} |word=naalis|full=naturalis|}}
{{dict|lang ={{{1}}} |word=N.B.|full=notabene|}}
{{dict|lang ={{{1}}} |word=N.D.|full=nobilis domine, - domina|}}
{{dict|lang ={{{1}}} |word=N.N.|full=nomen nescio|}}
{{dict|lang ={{{1}}} |word=noe., noie|full=nomine|}}
{{dict|lang ={{{1}}} |word=not., nots|full=notarius|}}

{{dict|lang ={{{1}}} |word=naevus|default=moedervlek|}}
{{dict|lang ={{{1}}} |word=nam|default=want|}}
{{dict|lang ={{{1}}} |word=nata|default=geboren|}}
{{dict|lang ={{{1}}} |word=nativatas, nativatis|default=geboorte|}}
{{dict|lang ={{{1}}} |word=nativus|default=geboortig|}}
{{dict|lang ={{{1}}} |word=natum, natus|default=geboren|}}
{{dict|lang ={{{1}}} |word=natum mediam nocte|default=geboren te middernacht|}}
{{dict|lang ={{{1}}} |word=naturalis|default=natuurlijk -, onwettig kind|}}
{{dict|lang ={{{1}}} |word=natus anno|default=geboren in het jaar|}}
{{dict|lang ={{{1}}} |word=nauta|default=schipper|}}
{{dict|lang ={{{1}}} |word=navector|default=veerman|}}
{{dict|lang ={{{1}}} |word=navigator|default=schipper|}}
{{dict|lang ={{{1}}} |word=navis|default=boot|}}
{{dict|lang ={{{1}}} |word=navium gubernator|default=(scheeps)stuurman|}}
{{dict|lang ={{{1}}} |word=necessariis moribundorum sacramentis|default=met de nodige sacramenten der stervenden|}}
{{dict|lang ={{{1}}} |word=necessitatis baptismum|default=nooddoop|}}
{{dict|lang ={{{1}}} |word=nec non|default=en eveneens|}}
{{dict|lang ={{{1}}} |word=neonatus|default=pasgeboren|}}
{{dict|lang ={{{1}}} |word=neosponsi|default=de jonggehuwden|}}
{{dict|lang ={{{1}}} |word=nepos|default=kleinzoon, neef, kinderen van oom of tante|}}
{{dict|lang ={{{1}}} |word=nepta, neptis|default=kleindochter, nicht (dochter van iemends broer of zuster, dochter van oom of tante)|}}
{{dict|lang ={{{1}}} |word=nesciens scribere|default=niet kunnende schrijven|}}
{{dict|lang ={{{1}}} |word=nescius|default=onkundig|}}
{{dict|lang ={{{1}}} |word=nobilis|default=adel, edel|}}
{{dict|lang ={{{1}}} |word=nobilis domina|default=weledele dame|}}
{{dict|lang ={{{1}}} |word=nobilis dominus|default=weledele heer|}}
{{dict|lang ={{{1}}} |word=noctis|default=nacht (van de)|}}
{{dict|lang ={{{1}}} |word=nocturnus|default=nachtelij|}}
{{dict|lang ={{{1}}} |word=nomen (mv) nomina|default=naam|}}
{{dict|lang ={{{1}}} |word=nomen nescio|default=onbekende naam|}}
{{dict|lang ={{{1}}} |word=nomina defunctorum|default=naamlijst overledenen|}}
{{dict|lang ={{{1}}} |word=nominavit|default=heeft genoemd|}}
{{dict|lang ={{{1}}} |word=nomine|default=in naam van, met als naam|}}
{{dict|lang ={{{1}}} |word=nonagenarius|default=negentigjarige, negentiger|}}
{{dict|lang ={{{1}}} |word=nonaginta|default=negentig|}}
{{dict|lang ={{{1}}} |word=nonam|default=negende (uur)|}}
{{dict|lang ={{{1}}} |word=nondum|default=nog niet|}}
{{dict|lang ={{{1}}} |word=nono|default=negen|}}
{{dict|lang ={{{1}}} |word=noster|default=onze|}}
{{dict|lang ={{{1}}} |word=notabene|default=let wel|}}
{{dict|lang ={{{1}}} |word=notabilis|default=de aanzienlijkste, voornaamste burgers van de gemeente|}}
{{dict|lang ={{{1}}} |word=notandum quod ....|default=noteer dat|}}
{{dict|lang ={{{1}}} |word=notarius|default=notaris|}}
{{dict|lang ={{{1}}} |word=notarius publicus|default=openbaar notaris|}}
{{dict|lang ={{{1}}} |word=notarius regius|default=koninklijk notaris|}}
{{dict|lang ={{{1}}} |word=nothus|default=onwettig, bastaard, onecht|}}
{{dict|lang ={{{1}}} |word=novalis, novaal|default=nieuw|}}
{{dict|lang ={{{1}}} |word=novem|default=negen|}}
{{dict|lang ={{{1}}} |word=novemdecima|default=negentien|}}
{{dict|lang ={{{1}}} |word=novembris|default=november|}}
{{dict|lang ={{{1}}} |word=novennis|default=negen jaar oud|}}
{{dict|lang ={{{1}}} |word=noverca|default=stiefmoeder|}}
{{dict|lang ={{{1}}} |word=novercalis|default=(bn) stiefmoederlijk|}}
{{dict|lang ={{{1}}} |word=novercari|default=stiefmoederlijk bejegenen|}}
{{dict|lang ={{{1}}} |word=novercus|default=stiefvader|}}
{{dict|lang ={{{1}}} |word=nubilis|default=huwbaar|}}
{{dict|lang ={{{1}}} |word=nuda proprietas|default=naakte eigendom, de blooteigenaar is hij wiens eigendom belast is met vruchtgebruik|}}
{{dict|lang ={{{1}}} |word=nudius tertius|default=eergisteren|}}
{{dict|lang ={{{1}}} |word=nullo allato impedimento|default=(en) geen huwelijksbeletsel ontdekt zijnde|}}
{{dict|lang ={{{1}}} |word=nullo(que) detecto impedimento|default=(en) geen huwelijksbeletsel ontdekt zijnde|}}
{{dict|lang ={{{1}}} |word=nummophylacis, -lax|default=muntmeester|}}
{{dict|lang ={{{1}}} |word=nummularius|default=muntsnijder, wisselaar|}}
{{dict|lang ={{{1}}} |word=nunc|default=nu|}}
{{dict|lang ={{{1}}} |word=nuncupatio|default=mondelinge aanwijzing van een erfgenaam|}}
{{dict|lang ={{{1}}} |word=nuntius|default=gerechtsbode|}}
{{dict|lang ={{{1}}} |word=nuper|default=onlangs|}}
{{dict|lang ={{{1}}} |word=nupta, nuptae|default=(bn) gehuwd, getrouwd, bruid|}}
{{dict|lang ={{{1}}} |word=nuptus|default=gehuwd|}}
{{dict|lang ={{{1}}} |word=nuptiae, nuptiarum|default=huwelijksfeest, bruiloft|}}
{{dict|lang ={{{1}}} |word=nuptialis|default=(bn) bruilofts_, van of betreffende de bruiloft|}}
{{dict|lang ={{{1}}} |word=nuptiare|default=(ww) huwen, met iemend trouwen|}}
{{dict|lang ={{{1}}} |word=nuptura|default=bruid|}}
{{dict|lang ={{{1}}} |word=nupturus|default=bruidegom|}}
{{dict|lang ={{{1}}} |word=nuptus|default=huwelijk, echt|}}
{{dict|lang ={{{1}}} |word=nurus|default=schoondochter|}}
{{dict|lang ={{{1}}} |word=nutritor|default=verpleger, pleegvader, verzorger|}}
{{dict|lang ={{{1}}} |word=nutrix, nutricis|default=min, baker, pleegmoeder, opvoedster|}}

User:DomoViridi/TempTest/Testcases

2026-03-13T20:06:04Z

DomoViridi: Putting PAGELANGUAGE inside a span with lang=nl

Test cases for the sandbox Dict template.

FULLPAGENAME for this page is {{FULLPAGENAME}}.

PAGELANGUAGE for this page is {{PAGELANGUAGE}}, for {{#language:{{PAGELANGUAGE}}}}.

Note: In this format, the case of the template name '''does''' matter. "Dict" works, but "dict" does not.

== Classic, with lang and default= for Dutch ==

=== Straight-up classic entry, calling English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
| default=sukkel
}}

=== Straight-up classic entry, calling Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
| default=sukkel
}}

=== Straight-up classic entry, calling French ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=fr| word=sillius soddus
| en=silly sod
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=fr| word=sillius soddus
| en=silly sod
| default=sukkel
}}

=== Straight-up classic entry, calling Spanish ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
| default=sukkel
}}

=== Only English, calling English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
}}

=== Only English, calling Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
}}

=== Only English, calling Spanish ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
}}

=== Only Dutch, calling English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| default=sukkel
}}

=== Only Dutch, calling Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| default=sukkel
}}

=== Only Dutch, calling Spanish ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| default=sukkel
}}

== With lang parameter ==

=== Straight-up classic entry, calling English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
| nl=sukkel
}}

=== Straight-up classic entry, calling Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
| nl=sukkel
}}

=== Straight-up classic entry, calling French ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=fr| word=sillius soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=fr| word=sillius soddus
| en=silly sod
| nl=sukkel
}}

=== Straight-up classic entry, calling Spanish ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
| nl=sukkel
}}

=== Only English, calling English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
}}

=== Only English, calling Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
}}

=== Only English, calling Spanish ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
}}

=== Only Dutch, calling English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| nl=sukkel
}}

=== Only Dutch, calling Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| nl=sukkel
}}

=== Only Dutch, calling Spanish ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| nl=sukkel
}}

== No lang parameter ==

=== Full ===
<nowiki>{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| en=silly sod
| nl=sukkel
}}

=== No parameters ===
<nowiki>{{User:DomoViridi/TempTest/Dict}}</nowiki>
{{User:DomoViridi/TempTest/Dict}}

=== Only English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| en=silly sod
}}

=== Only Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| nl=sukkel
}}

== Adding a language span ==
Adding
<nowiki>...</nowiki>
might set the PAGELANGUAGE magic word in the template.

Test on PAGELANGUAGE directly:
<nowiki>PAGELANGUAGE for this page is {{PAGELANGUAGE}}, for {{#language:{{PAGELANGUAGE}}}}.</nowiki>
PAGELANGUAGE for this page is {{PAGELANGUAGE}}, for {{#language:{{PAGELANGUAGE}}}}.

Or with a div:

Test on PAGELANGUAGE directly:
<nowiki><div lang="nl" dir="ltr" class="mw-content-ltr">PAGELANGUAGE for this page is {{PAGELANGUAGE}}, for {{#language:{{PAGELANGUAGE}}}}.</div></nowiki>
<div lang="nl" dir="ltr" class="mw-content-ltr">PAGELANGUAGE for this page is {{PAGELANGUAGE}}, for {{#language:{{PAGELANGUAGE}}}}.</div>

Test on a lemma:
<nowiki>{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| en=silly sod
| nl=sukkel
}}

== With 'full' parameter ==
Planned for future support for abbreviations.

Classical, with only the '''default''' parameter, containing the expansion (en).
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=S.S. | default=Sillius Soddus}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=S.S. | default=Sillius Soddus}}

Classical, with only the '''default''' parameter, containing the expansion (nl).
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | default=Sillius Soddus}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | default=Sillius Soddus}}

Modernised, with '''full''' parameter and '''en''' and '''nl''' translations (en).
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}

Modernised, with '''full''' parameter and '''en''' and '''nl''' translations (nl).
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}

== Spacing check ==
Does the template introduce extra newlines or spaces?

=== Calls close together ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}
{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}
{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}</nowiki>

{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}
{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}
{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}
These should generate only one HTML <dl> block.

=== Calls with blank line in between ===

<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}

{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}

{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}</nowiki>

{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}

{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}

{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}
These will generate separate HTML <dl> blocks.
The vertical space between entries should be slightly larger than with a single block.

=== Silly: two calls on one line ===
<nowiki>{{User:DomoViridi/TempTest/Dict|lang=nl|abamita|nl=overgrootmoeder}}{{User:DomoViridi/TempTest/Dict|lang=nl|abamita|nl=overgrootmoeder}}</nowiki>

{{User:DomoViridi/TempTest/Dict|lang=nl|abamita|nl=overgrootmoeder}}{{User:DomoViridi/TempTest/Dict|lang=nl|abamita|nl=overgrootmoeder}}

These should also generate only one HTML <dl> block.
Although: really tight template coding should produce malformed wiki code:
<nowiki>;abamita:overgrootmoeder;abimata:overgrootmoeder</nowiki>
resulting in
;abamita:overgrootmoeder;abimata:overgrootmoeder

== The real template ==

Word as first parameter (nl)
<nowiki>{{Dict|lang=nl|abamita|nl=overgrootmoeder}}</nowiki>

{{Dict|lang=nl|abamita|nl=overgrootmoeder}}

== Problem with unnamed word parameter ==

Gives problem in [[Template:Latindict/K]]

The unnamed '''word''' parameter should not be followed by a newline.
That newline becomes part of the value.
That breaks up the description-list-entry format.
<nowiki>{{dict|lang ={{{1}}} |k
|nl= zie c
|en= see c
}}</nowiki>

{{dict|lang ={{{1}}} |k
|nl= zie c
|en= see c
}}

Our local template:
<nowiki>{{User:DomoViridi/TempTest/Dict|lang ={{{1}}} |k
|nl= zie c
|en= see c
}}</nowiki>

{{User:DomoViridi/TempTest/Dict|lang ={{{1}}} |k
|nl= zie c
|en= see c
}}

Better:
<nowiki>{{User:DomoViridi/TempTest/Dict|lang ={{{1}}} |k|
nl= zie c|
en= see c|
}}</nowiki>

{{User:DomoViridi/TempTest/Dict|lang ={{{1}}} |k|
nl= zie c|
en= see c|
}}

User:DomoViridi/TempTest

2026-03-13T15:35:43Z

DomoViridi: /* Check the Hebrew pages */ No translated lemmas

The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

== Sandbox to test templates ==

For [[Template:Latindict]], [[Template:Latindict/A]] (and all the other letter-subpages), [[Template:Dict/Glossary]], [[Template:Dict]], as used in [[Latin words and expressions]], and the translations [[Latin words and expressions/nl]], [[Latin words and expressions/fr]] and [[Latin words and expressions/he]].

== Improvements to Dict template ==

* The '''default''' parameter does not make sense, and should be eliminated. If there is no descriptive text for a given language, then the wiki page should show a blank line (or nothing).
: Before removing it, in all uses of this template '''default=''' should be replaced with '''nl='''. This is also the solution to the problem of showing lots of Dutch language descriptions on the English pages.
:* Better yet: first make '''default''' an alternative to '''nl'''. That way, the existing calls to this template can remain unchanged, while also only showing the Dutch description (given in '''default''') if '''lang''' is "nl".

* The '''lang''' parameter is exclusively used as <code><nowiki>{{dict|lang ={{{1}}} |word=...</nowiki></code>, i.e. the value is read from the first unnamed parameter that was passed to <kbd>Template:Latindict/A</kbd>. This value cascades down from the main page.
: This cascade might be unnecessary, because the template should be able to use the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word. Entries can then be simplified to <code><nowiki>{{dict|word=...</nowiki></code>. For the use in special cases '''lang=''' could be left available to override the wiki language setting for a particular lemma.
:* Unfortunately <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> always returns "en" on this wiki, even on .../nl and Nl:... pages.

* The '''word''' named parameter should be optional, and the word should be allowed to be passed as the first anonymous parameter, so we can write <code><nowiki>{{dict| abiit| en=he/she has left | nl=hij/zij is vertrokken }}</nowiki></code>.
: Disadvantage: That would make the lemma an unnamed parameter. Unnamed parameters are not stripped of leading and trailing spaces. This can lead to lemmas with extra spaces around them.
: Although: because it is the term in a definition list, leading spaces are ignored, and trailing spaces do not affect the layout (the displayed wiki text goes to a new line after the term), or are maybe also ignored.
:* Beware: Though spaces have little effect, a value for an unnamed parameter should never be the last thing on a line, because then the newline following the parameter will become part of the parameter value. In this template that messes up the description-list-item format.
:* This might also be true for a newline ''before'' an unnamed parameter.
: Can be implemented with <code><nowiki>{{{word|{{{1}}} }}}</nowiki></code> in the template. This accepts the first anonymous parameter, except when a '''word''' parameter was given when calling the template. This gives backward compatibility, where it is ''allowed'' to use the '''word''' parameter, but not ''mandatory''.

* Make it so that <kbd>Template:Dict</kbd> does not need an explicit list of language codes. The current list blocks additional translations from being added.
: The value of the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word can be used to create the name of the desired parameter, e.g. "en". See [https://www.mediawiki.org/wiki/Manual:Advanced_templates#Variable_parameter_name Mediawiki Advanced Templates Help: Variable parameter name].
:Code: <code><nowiki>;{{{word|{{{1}}} }}}:{{{ {{PAGELANGUAGE}} }}}</nowiki></code>
: The use of <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> also makes '''en''' the default language.
:* Unfortunately <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> always returns "en", making it useless. We still need the '''lang''' parameter. The trick with double evaluation of the parameter still works, so we can write:
:: <code><nowiki>;{{{word|{{{1}}} }}}:{{{ {{{lang}}} }}}</nowiki></code>

* The current version outputs <code><nowiki>{{{en}}}</nowiki></code> if no '''default''' or language code parameter was given. Also produces <code><nowiki>'''{{{word}}}'''</nowiki></code> if no '''word''' parameter was given.
:This is probably actually a good thing, because it shows when there is an error and the template call should be edited to resolve this.
: '''documentation''': add to the docs what parameters should be given and what happens if one is missing.

* There should be a parameter to give the expansion of an abbreviation, separate from the translations. For example <code><nowiki>{{dict|A.D.|full=Anno Domini"|en=in the year of our lord|nl=in het jaar van de Heer}}</nowiki></code>. The wiki format to be produced needs to be invented. Possibly as extra text in parentheses added to the lemma, e.g.
:;A.D. (Anno Domini):in the year of our lord
:Or on the description line:
:;A.D.:'''Anno Domini''': in the year of our lord
: By putting the formatting in the template we can ensure that it is universal accross all pages.
:* This addition is very useful, and helps to show lemmas which only had an expansion (as the '''default''' value), but no language-specific descriptions.

=== Behaviour for missing description text ===
If there is no descriptive text parameter for the language of the page, then by default the template will show the lemma, but with an empty description.

This might be annoying for translations with relatively few translated descriptions (e.g. for brand new translated pages). The reader will be looking at a long list of lemmas with only a few descriptions.

A possible solution is the introduction of a '''show''' parameter, which will determine what will happen if the lemma has is no descriptive text for the current language. Possible values:
;quiet:Show nothing. Pages will only show the lemmas which have a description in the page's language.
;blank:The default. Show the lemma with a blank description.
;a language code:Substitute the description with the given language. (Complicated implementation; maybe wait if there is demand for it.)
If the parameter is not set then do the '''blank''' behaviour.

For this parameter to work, we need to set up a new cascade of parameter passing.
Then this parameter can be set on the main page for a language, e.g. initially '''quiet''' or '''nl''', later to be removed as the descriptions start to become more common.

== Restructuring the template cascade ==

The subdivision into templates for each letter of the alphabet is a pain in the <donkey>, and actually unnecessary.
We describe how it is structured currently (Feb 2006), and draw up a plan for a simpler structure.

=== The two paths to this template: why? ===
Find out why there are two paths to this template:
# Through [[Template:Latindict]] and [[Template:Latindict/A]] (and the other letters).
# Via non-template "Latin words and expressions/''letter''" pages.
This also happens for the Dutch translated pages, so we get
Latin words and expressions/nl/A
Latin words and expressions/nl/B
etc.
and also
Nl:Latijnse woorden en uitdrukkingen/A
Nl:Latijnse woorden en uitdrukkingen/A
etc.

At first the suspect in this was the French translation, which uses a translated French page for each letter page.

Looking at the page history of the pages involved to see what happened, it turns out these pages were created around the same time and by the same author as the templates. They might be a remnant of an earlier setup. Examination of the exact creation dates and time may shed more light.

While this is going on, the use of <kbd>Template:languages</kbd> and <kbd>Template:Dict/Glossary</kbd> on all these pages creates a tangled web of pages being linked to by other pages. For example
Nl:Latijnse woorden en uitdukkingen/A
is linked to by:
* The main Dutch page
* Itself
* The non-redirected version of itself
* The main French page
* Every other <kbd>Nl:Latijnse woorden en uitdukkingen/''letter''</kbd> page

=== The Reason ===
All these subpages were created in a desperate bid by the original author to split the list into separate pages, allowing an editor to edit the list only a letter-section at the time, rather than having to edit the entire list of thousands of lemmas.

Because the actual content of the article is transcluded, the normal "edit by section" mechanism does not work.

This problem is not trivial to solve. Idealy [https://www.mediawiki.org/ mediawiki] should have a built-in mechanism to redirect an action to edit a section to edit the section in the transcluded page.
: '''Find out''' if such a mechanism exists

The documentation on this subject is shockingly poor. We must find out through experimentation.

[[User:DomoViridi/Temsects|It turns out]] that the '''current Wiki''' implements this '''exactly as expected'''.
* Put the sections in a transcluded file
* Transclude that file in the main file
* Put a ToC in either the main file or the transcluded file (both work), with simple <code><nowiki>[[#A|A]]</nowiki></code> links
* The ToC links will show you the section on the main page
* The auto-generated edit links will open the transcluded file on that section
* It also works with [[User:DomoViridi/Temsects/nl|translated pages]]

=== Current structure ===

==== The main page [[Latin_words_and_expressions]] ====
This contains
* A warning box about the mixing of English and Dutch descriptions.
* A code to suppress the Table of Contents.
* A call to <kbd>Template:Languages</kbd>, to make automatic links to the translated pages.
* An introductory text.
* A call to <kbd>Template:Dict/Glossary</kbd>, passing the name of the page as a parameter. This generates a substitute Table of Contents, linking to all the letter sections which will be generated on this page. '''Note:''' instead of passing a literal copy of the name of the page, the code <code><nowiki>{{BASEPAGENAME}}</nowiki></code> should have been used by the template.
* A call to <kbd>Template:Latindict, with the language code as a parameter (<nowiki>{{latindict|en}}</nowiki>). The language code is not needed, as <kbd>Template:Dict</kbd> should have used the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word.
* A comment with instructions on where to edit lemmas.
* A Category link <code><nowiki>[[Category:Genealogy|L]]</nowiki></code>.

Translated pages such as [[Latin_words_and_expressions/nl]] (or the page they redirect to) contain the same, with adaptations.
* The introductory text is translated.
* The parameter passed to <kbd>Template:Dict/Glossary</kbd> changed to the translated page name. (Using <code><nowiki>{{BASEPAGENAME}}</nowiki></code> would have prevented this, but that issue is moot in the new structure.)
* The parameter passed to <kbd>Template:Latindict</kbd> is changed to the code for the translated language. (Again, this could have been automated using <code><nowiki>{{PAGELANGUAGE}}</nowiki></code>. Again, issue is moot in the new structure.)
* The instructions in the comment are translated.
* The Category link is translated: <code><nowiki>[[Category:Nl:Genealogie|Latijnse woorden]]</nowiki></code>.

==== Template:Latindict ====
This contains
* A list of sections, one for each letter of the alphabet, and one for the 'at' symbol (<kbd>@</kbd>), with a Level 2 header with that letter.
* In each letter section, a call to a sub-template for that letter (<code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> etc.). The language code (passed into <kbd>Template:Latindict</kbd> as the first parameter), is passed on as the first parameter to the sub-template.
* Nothing else.

==== Template:Latindict/A etc. ====
These contain
* the actual lemmas, in the form of a <kbd>Template:Dict</kbd> entry for each lemma:
<nowiki>{{dict|lang ={{{1}}} |word=abavia|default=betovergrootmoeder |en=second great grandmother}}</nowiki>
* A link (now dead) to the Dutch/Flemish source material, as a <kbd>noinclude</kbd> so it won't show up on the page, but ''is'' visible in the source. This could have been done with an HTML comment.
''(Note: the English description in the example should be 'great-great-grandmother'.)''

The parameters to <kbd>Template:Dict</kbd> are filled in as follows:
;lang:The language code was passed in as the first parameter, and is now copied into this parameter: <kbd><nowiki>lang={{{1}}}</nowiki></kbd>.
;word:Set to the Latin lemma.
;default:Set to the Dutch description (which is wrong, this should be changed to the '''nl''' parameter everywhere; this is the main cause of the English/Dutch mixing of the descriptions).
;en, nl, fr, etc:Descriptions in other languages are given as a parameter named after their language code. Texts for other languages can be added here, e.g. <kbd>fr=Arrière-arrière-grand-mère</kbd>.

==== Template:Dict ====
This finally generates a display list entry based on the parameters.

The template turns the parameters into a display list entry, with the format
<nowiki>;'''word''':description</nowiki>
(The lemma word does not need to be explicitly made bold, the description list format already does that.)
This results in
;word:description

=== New structure ===

==== The main page (and the translations) ====
* The warning box about the error will probably be gone by this time.
* The code to suppress the Table of Contents remains.
* The call to <kbd>Template:Languages</kbd> can remain unchanged.
* The introductory text can probably remain unchanged.
* The call to <kbd>Template:Dict/Glossary</kbd> must be removed.
* The call <kbd><nowiki>{{Latindict}}</nowiki></kbd> must remain unchanged, with the language of the page as the first parameter (because the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word does not work on this wiki).
* The comment with instructions must be updated to reflect the new situation, i.e. find the lemma in <kbd>Template:Latindict</kbd> and edit it there.

The translated page pages must do the same changes:
* Remove the call to <kbd>Template:Dict/Glossary</kbd>.
* Update the translation of the instructions.

The result will be that:
* The homebrew ToC entries will jump to that letter on the main page.
* The "Edit" link on each section will open an edit on the section '''in the template''', allowing direct editing of lemmas.

==== Template:Latindict ====
Change to contain:
* A Table-of-Contents header with in-page links to all the letters. This replaces the <kbd>Template:Dict/Glossary</kbd> call from the main page. If the user clicks on one of these links, the view should jump to that letter header on the same page. This helps the user find a lemma more quickly.
: There will only be one call for this, so there is no need for a template. A simple set of <code><nowiki>[[#A|A]] - [[#B|B]] -[[#C|C]] - [[#D|D]] - ...</nowiki></code> with a table around it should do the trick. Copy from the template contents and search/replace <code><nowiki>{{{1}}</nowiki>}/</code> with <code>#</code>. Note that this moves this fuctionality from the main page (and the translated pages) to this template (with only one occurence), useful in all translations of the main page.
* Sections for each letter (unchanged). Simple <code>== A ==</code> headers are enough.
* In each section replace the <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> with all the <code><nowiki>{{dict|...}}</nowiki></code> entries for that letter. These can be substituted in by changing <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> to <code><nowiki>{{subst:Latindict/A|{{{1}}}}}</nowiki></code> and saving the page. Repeat for all the letters.

If all goes as expected, the ToC links will bring you to the section on the main page, and the auto-generated edit links will open this template for editing on the chosen section.

By allowing editing-by-section, users will not be overburdened by edit pages which are too big. As a major advantage, it will be much easier for editors to find the lemma they want to edit, without the need to search for the correct lettered subpage.

==== Template:Latindict/A etc. ====
These can all be eliminated.

==== Template:Dict ====
This must be overhauled.
* Eliminate the '''lang''' parameter. Take the language from the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word. On this wiki this will always have a valid value.
** Unfortunately, <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> always produces "en" on this wiki. So we still need the '''lang''' parameter
* Eliminate the '''default''' parameter.
** Or better: Allow '''default''' as an alternative for '''nl'''. This gives backward compatiblilty with the existing calls to this template.
* Other improvements are described in the [[#Improvements to Dict template]] section

=== Pages no longer needed ===
With this new structure the following pages can be eliminated:
* All the lettered sub-templates (<kbd>Template:Latindict/A</kbd> etc.).
* All the <kbd>Main:</kbd> space lettered sub-pages (<kbd>Latin words and expressions/A</kbd> etc.).
* All the Dutch translated main space lettered sub-pages (<kbd>Latin words and expressions/A/nl</kbd> etc.), and the pages they redirect to (<kbd>Nl:Latijnse woorden en expressies/A</kbd> etc.).
* Same for the French translated pages. Although we will have to copy the descriptions from the French pages into the <kbd>Template:Dict</kbd> calls as <kbd>fr=</kbd> parameters first.
* Status of the Hebrew translated pages needs to be examined.

== Actions to take for modification ==

=== Set up a test environment ===
Set up a test environment to create and test a better version of the template without disturbing the existing one.
* (done) Create a Sandbox subspace to my user page: <kbd>User:DomoViridi/TempTest</kbd>; Think about the use or no-use of capital letters in the names of the pages first (doesn't realy matter). Put my own version of the pages there, but in the <kbd>User:DomoViridi/TempTest</kbd> space. Test templates can be called with the syntax <code><nowiki>{{User:DomoViridi/TempTest/mytemplate}}</nowiki></code> (the braces ensure transclusion, the <kbd>User:</kbd> namespace replaces the default <kbd>Template:</kbd> namespace.
* (done) Create a template page with the test template, [[User:DomoViridi/TempTest/Dict]]. Fill it initially with a copy of the original <kbd>Template:Dict</kbd>.
* (done) Create a page with test cases, [[User:DomoViridi/TempTest/Testcases]]. Put some calls to our Dict template in it, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus| en=silly sod| nl=sukkel}}</nowiki></code>. Add many testcases and put their source code in nowiki text above each.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict/A]] with calls to the Dict template, using <code><nowiki>{{User:DomoViridi/TempTest/Dict}}</nowiki></code>. Copy the existing "A" page and shorten it, leaving some useful examples, with different languages, some abbreviations, and some missing languages. Add French translations to some of the lemmas. Also copy a different letter page (a short one), which has some translations.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict]] which calls our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space.
* (done) Create a main page [[User:DomoViridi/TempTest/Latin words and expressions]], which calls <code><nowiki>{{User:DomoViridi/TempTest/Latindict}}</nowiki></code>.
: '''Oh hey!''', it turns out <kbd>Template:Dict/Glossary</kbd> creates links to [[Latin words and expressions/A]] and all the other letters.
* (done) Create lettered pages [[User:DomoViridi/TempTest/Latin words and expressions/A]] for each of the pages for wich we have a template, and fill them with a copy of the originals. which call our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space. Note that this is all duplicate work.
* (done) Create a translated page [[User:DomoViridi/TempTest/Latin words and expressions/nl]], fill it with the contents of [[Nl:Latijnse woorden en expressies]]. Change the calls to point to the sandbox, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Latindict | nl}}</nowiki></code> (passing the language to the template).
: '''Oh hey!''', once again we see how the clumsy <kbd>Template:Dict/Glossary</kbd> requires subpages of the translated page, one for each letter of the alphabet.
* (done) Create the translated subpages before moving the translated main page.
: Although: this does not help, because the letter pages are not subpages of the <kbd>.../nl</kbd> page, but are formed with <kbd>.../A/nl</kbd>.
* (done) Move the translated page to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies]]. This will automatically create a redirect from the <kbd>/nl</kbd> page to this page.
* (done) Move all the frakking translated subpages to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies/A]], again auto-generating a redirect.

Creating 27 (one for each letter of the alphabet, plus '@') lettered subpages each time for:
* The Templates
* The main page (English)
* The Dutch (nl) translation
* The redirect for the Dutch (nl) translation
* The French (fr) translation
* The redirect for the French (fr) translation
* The Hebrew (he) translation
* The redirect Hebrew (he) translation
* The same again for every new translation
is an unbelievable pile of unnecessary busywork. All so that we can have separate pages for every letter, and links to them.
Good thing I only did letters A and B for this sandbox.

''Note: the Gramps wiki does not support the [https://www.mediawiki.org/wiki/Extension:TemplateSandbox TemplateSandbox extension], which would have allowed to attach a sandbox subpage directly to the template. This means the <code><nowiki>{{testcases notice}}</nowiki></code> template is also not available.''

=== Create an improved Dict template ===
(done) Do this in the sandbox. See the [[#Improvements to Dict template]] section.

(done) Don't forget to adjust the documentation.

(done) When it works with no detected problems, overwrite the actual template with our code.

=== Change "default" to "nl" ===
Because <kbd>Template:Dict</kbd> defaults to <nowiki>{{{en}}}</nowiki> if there is no description in a valid language, changing '''default''' to '''nl''' will result in a lot of bad output for all entries where '''en''' is missing.
: (done) Solution: make '''default''' an alternative for '''nl''', so if '''lang=en''' then a blank description is shown, and if '''lang=nl''' then the Dutch '''default''' description is shown.

(done) This means we need to modify <kbd>Template:Dict</kbd> before we make this change.

(deferred) Edit all the <kbd>Template:Latindict/<letter></kbd> pages to change '''default=''' to '''nl='''.
The effect should be that Dutch descriptions only show on the Dutch pages.
* Start with a small page and see how it goes.
* Then do a few more with export-to-editor, bulk search/replace, import from editor. Check for anomalies.
* Do the other pages

(deferred) This should all have effect without the need to change the templates yet. It also makes room for a modification of <kbd>Template:Dict</kbd> which drops the '''default''' parameter.

Note: This operation has been deferred, pending a decision to about the future of this dictionary.

=== Restructure the template cascade ===
Do this in the sandbox. See [[#Restructuring the template cascade]].
Make sure it works perfectly.

Before modifying the real pages, put notices in the talk pages and banners in any and all of the pages involved.

Then modify the real pages.

Try to get the useless pages deleted. At the least put a warning box in them. Something like "Do not use this page. Use page xxx instead. This page will be deleted in the near future".

=== Move the translated French pages ===
Copy all the existing French translations to the <kbd>Template:Latindict/<letter></kbd> pages.
Note: This leaves the translated French pages unchanged for now.
* Could be a big job.
* Have these pages changed much in the last few years?
* Put a notice on the Talk page for the French translation to tell them what is going on.
* Maybe put a banner on the pages too.
* Make sure they work nicely.

Switch the translated French page to use Template:Latindict
* One edit to [[Fr:Mots et expressions en latin]] should be enough.
* Add a notice to the French page about the change

=== Check the Hebrew pages ===
(done) Check what the Hebrew pages look like now that we made '''default=''' an alternative to '''nl='''.
: The Hebrew pages do not have a single translated lemma. Only the main page header has been translated, and the body of the page is set to RTL mode.

=== Remove unneeded pages ===
Remove all the unneeded letter pages and letter templates, for each language that uses them.

=== Possible 'silent' mode ===
We may want to add a "silent" mode, where lemmas are not shown if there is no description for that language. This will avoid long pages of untranslated Latin words and expressions, and emphasise the lemmas that have been translated.

This will require an extra parameter, which must be passed down through all the templates. This named parameter should be given with a value, so that it evaluates to "take the then case" for the parser function:
<nowiki>{{#if:{{{silent|}}} | do silent version | do not-silent version}}</nowiki>
That means the parameter should be set as <kbd>"silent=<something>"</kbd>, with an arbitrary, non-empty value. See [https://www.mediawiki.org/wiki/Help:Parser_functions_in_templates Parser functions in templates]
* On page [[Latin words and expressions/fr]]: call template <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd> for silent and <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd> for not-silent.
* [[Template:Latindict]]: call <kbd><nowiki>{{Latindict/A|{{{1}}}|silent={{{silent|}}}}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* [[Template:Latindict/A]]: call <kbd><nowiki>{{Dict|lang={{{1}}}|silent={{{silent|}}}|word=...}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* Inside [[Template:Dict]] use <kbd><nowiki>{{#if: {{{silent|}}} | do silent stuff | do non-silent stuff}}</nowiki></kbd> (again with a bar after the parameter).

The following table shows how the parameter values trickle down to the <kbd>#if</kbd> parser, with or without the extra bar (<kbd>|</kbd>). The conclusion is that the extra bar should be used thoughout, and the parameter should be omitted for non-silent mode and passed with a value (e.g. <kbd>silent=yes</kbd>) for silent mode. The string used for the value (in this example "yes") does not matter. Note that passing the parameter with an empty string as a value ("<kbd>silent=</kbd>") will set the result to non-silent.

''Note: the use of the variables <kbd>s1</kbd>, <kbd>s2</kbd> and <kbd>s3</kbd> is arbitrary, and is used here for clarity. They could all be called <kbd>silent</kbd>.''

{| class="wikitable" style="margin:auto" width="90%"
|+ Passing on the silent parameter
! Main page
! <kbd>Latindict</kbd>
! <kbd>Latindict/A</kbd>
! <kbd>Dict</kbd>
! <kbd>#if</kbd>
|-
! style="text-align:right" | without bar
! <kbd><nowiki>s1={{{silent}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| then
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
! style="text-align:right" | with bar
! <kbd><nowiki>s1={{{silent|}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
|}

In the end, all the entries in [[Template:Latindict]] need to be modified, as must all calls to [[Template:Dict]] in all the letter templates ([[Template:Latindict/A]] etc.). And finally [[Template:Dict]] needs to implement the silent mode.

== Copyright ==
The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

User:DomoViridi/TempTest

2026-03-13T15:15:47Z

DomoViridi: /* Change "default" to "nl" */ Added "(done)" where appropriate. Main action is deferred.

The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

== Sandbox to test templates ==

For [[Template:Latindict]], [[Template:Latindict/A]] (and all the other letter-subpages), [[Template:Dict/Glossary]], [[Template:Dict]], as used in [[Latin words and expressions]], and the translations [[Latin words and expressions/nl]], [[Latin words and expressions/fr]] and [[Latin words and expressions/he]].

== Improvements to Dict template ==

* The '''default''' parameter does not make sense, and should be eliminated. If there is no descriptive text for a given language, then the wiki page should show a blank line (or nothing).
: Before removing it, in all uses of this template '''default=''' should be replaced with '''nl='''. This is also the solution to the problem of showing lots of Dutch language descriptions on the English pages.
:* Better yet: first make '''default''' an alternative to '''nl'''. That way, the existing calls to this template can remain unchanged, while also only showing the Dutch description (given in '''default''') if '''lang''' is "nl".

* The '''lang''' parameter is exclusively used as <code><nowiki>{{dict|lang ={{{1}}} |word=...</nowiki></code>, i.e. the value is read from the first unnamed parameter that was passed to <kbd>Template:Latindict/A</kbd>. This value cascades down from the main page.
: This cascade might be unnecessary, because the template should be able to use the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word. Entries can then be simplified to <code><nowiki>{{dict|word=...</nowiki></code>. For the use in special cases '''lang=''' could be left available to override the wiki language setting for a particular lemma.
:* Unfortunately <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> always returns "en" on this wiki, even on .../nl and Nl:... pages.

* The '''word''' named parameter should be optional, and the word should be allowed to be passed as the first anonymous parameter, so we can write <code><nowiki>{{dict| abiit| en=he/she has left | nl=hij/zij is vertrokken }}</nowiki></code>.
: Disadvantage: That would make the lemma an unnamed parameter. Unnamed parameters are not stripped of leading and trailing spaces. This can lead to lemmas with extra spaces around them.
: Although: because it is the term in a definition list, leading spaces are ignored, and trailing spaces do not affect the layout (the displayed wiki text goes to a new line after the term), or are maybe also ignored.
:* Beware: Though spaces have little effect, a value for an unnamed parameter should never be the last thing on a line, because then the newline following the parameter will become part of the parameter value. In this template that messes up the description-list-item format.
:* This might also be true for a newline ''before'' an unnamed parameter.
: Can be implemented with <code><nowiki>{{{word|{{{1}}} }}}</nowiki></code> in the template. This accepts the first anonymous parameter, except when a '''word''' parameter was given when calling the template. This gives backward compatibility, where it is ''allowed'' to use the '''word''' parameter, but not ''mandatory''.

* Make it so that <kbd>Template:Dict</kbd> does not need an explicit list of language codes. The current list blocks additional translations from being added.
: The value of the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word can be used to create the name of the desired parameter, e.g. "en". See [https://www.mediawiki.org/wiki/Manual:Advanced_templates#Variable_parameter_name Mediawiki Advanced Templates Help: Variable parameter name].
:Code: <code><nowiki>;{{{word|{{{1}}} }}}:{{{ {{PAGELANGUAGE}} }}}</nowiki></code>
: The use of <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> also makes '''en''' the default language.
:* Unfortunately <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> always returns "en", making it useless. We still need the '''lang''' parameter. The trick with double evaluation of the parameter still works, so we can write:
:: <code><nowiki>;{{{word|{{{1}}} }}}:{{{ {{{lang}}} }}}</nowiki></code>

* The current version outputs <code><nowiki>{{{en}}}</nowiki></code> if no '''default''' or language code parameter was given. Also produces <code><nowiki>'''{{{word}}}'''</nowiki></code> if no '''word''' parameter was given.
:This is probably actually a good thing, because it shows when there is an error and the template call should be edited to resolve this.
: '''documentation''': add to the docs what parameters should be given and what happens if one is missing.

* There should be a parameter to give the expansion of an abbreviation, separate from the translations. For example <code><nowiki>{{dict|A.D.|full=Anno Domini"|en=in the year of our lord|nl=in het jaar van de Heer}}</nowiki></code>. The wiki format to be produced needs to be invented. Possibly as extra text in parentheses added to the lemma, e.g.
:;A.D. (Anno Domini):in the year of our lord
:Or on the description line:
:;A.D.:'''Anno Domini''': in the year of our lord
: By putting the formatting in the template we can ensure that it is universal accross all pages.
:* This addition is very useful, and helps to show lemmas which only had an expansion (as the '''default''' value), but no language-specific descriptions.

=== Behaviour for missing description text ===
If there is no descriptive text parameter for the language of the page, then by default the template will show the lemma, but with an empty description.

This might be annoying for translations with relatively few translated descriptions (e.g. for brand new translated pages). The reader will be looking at a long list of lemmas with only a few descriptions.

A possible solution is the introduction of a '''show''' parameter, which will determine what will happen if the lemma has is no descriptive text for the current language. Possible values:
;quiet:Show nothing. Pages will only show the lemmas which have a description in the page's language.
;blank:The default. Show the lemma with a blank description.
;a language code:Substitute the description with the given language. (Complicated implementation; maybe wait if there is demand for it.)
If the parameter is not set then do the '''blank''' behaviour.

For this parameter to work, we need to set up a new cascade of parameter passing.
Then this parameter can be set on the main page for a language, e.g. initially '''quiet''' or '''nl''', later to be removed as the descriptions start to become more common.

== Restructuring the template cascade ==

The subdivision into templates for each letter of the alphabet is a pain in the <donkey>, and actually unnecessary.
We describe how it is structured currently (Feb 2006), and draw up a plan for a simpler structure.

=== The two paths to this template: why? ===
Find out why there are two paths to this template:
# Through [[Template:Latindict]] and [[Template:Latindict/A]] (and the other letters).
# Via non-template "Latin words and expressions/''letter''" pages.
This also happens for the Dutch translated pages, so we get
Latin words and expressions/nl/A
Latin words and expressions/nl/B
etc.
and also
Nl:Latijnse woorden en uitdrukkingen/A
Nl:Latijnse woorden en uitdrukkingen/A
etc.

At first the suspect in this was the French translation, which uses a translated French page for each letter page.

Looking at the page history of the pages involved to see what happened, it turns out these pages were created around the same time and by the same author as the templates. They might be a remnant of an earlier setup. Examination of the exact creation dates and time may shed more light.

While this is going on, the use of <kbd>Template:languages</kbd> and <kbd>Template:Dict/Glossary</kbd> on all these pages creates a tangled web of pages being linked to by other pages. For example
Nl:Latijnse woorden en uitdukkingen/A
is linked to by:
* The main Dutch page
* Itself
* The non-redirected version of itself
* The main French page
* Every other <kbd>Nl:Latijnse woorden en uitdukkingen/''letter''</kbd> page

=== The Reason ===
All these subpages were created in a desperate bid by the original author to split the list into separate pages, allowing an editor to edit the list only a letter-section at the time, rather than having to edit the entire list of thousands of lemmas.

Because the actual content of the article is transcluded, the normal "edit by section" mechanism does not work.

This problem is not trivial to solve. Idealy [https://www.mediawiki.org/ mediawiki] should have a built-in mechanism to redirect an action to edit a section to edit the section in the transcluded page.
: '''Find out''' if such a mechanism exists

The documentation on this subject is shockingly poor. We must find out through experimentation.

[[User:DomoViridi/Temsects|It turns out]] that the '''current Wiki''' implements this '''exactly as expected'''.
* Put the sections in a transcluded file
* Transclude that file in the main file
* Put a ToC in either the main file or the transcluded file (both work), with simple <code><nowiki>[[#A|A]]</nowiki></code> links
* The ToC links will show you the section on the main page
* The auto-generated edit links will open the transcluded file on that section
* It also works with [[User:DomoViridi/Temsects/nl|translated pages]]

=== Current structure ===

==== The main page [[Latin_words_and_expressions]] ====
This contains
* A warning box about the mixing of English and Dutch descriptions.
* A code to suppress the Table of Contents.
* A call to <kbd>Template:Languages</kbd>, to make automatic links to the translated pages.
* An introductory text.
* A call to <kbd>Template:Dict/Glossary</kbd>, passing the name of the page as a parameter. This generates a substitute Table of Contents, linking to all the letter sections which will be generated on this page. '''Note:''' instead of passing a literal copy of the name of the page, the code <code><nowiki>{{BASEPAGENAME}}</nowiki></code> should have been used by the template.
* A call to <kbd>Template:Latindict, with the language code as a parameter (<nowiki>{{latindict|en}}</nowiki>). The language code is not needed, as <kbd>Template:Dict</kbd> should have used the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word.
* A comment with instructions on where to edit lemmas.
* A Category link <code><nowiki>[[Category:Genealogy|L]]</nowiki></code>.

Translated pages such as [[Latin_words_and_expressions/nl]] (or the page they redirect to) contain the same, with adaptations.
* The introductory text is translated.
* The parameter passed to <kbd>Template:Dict/Glossary</kbd> changed to the translated page name. (Using <code><nowiki>{{BASEPAGENAME}}</nowiki></code> would have prevented this, but that issue is moot in the new structure.)
* The parameter passed to <kbd>Template:Latindict</kbd> is changed to the code for the translated language. (Again, this could have been automated using <code><nowiki>{{PAGELANGUAGE}}</nowiki></code>. Again, issue is moot in the new structure.)
* The instructions in the comment are translated.
* The Category link is translated: <code><nowiki>[[Category:Nl:Genealogie|Latijnse woorden]]</nowiki></code>.

==== Template:Latindict ====
This contains
* A list of sections, one for each letter of the alphabet, and one for the 'at' symbol (<kbd>@</kbd>), with a Level 2 header with that letter.
* In each letter section, a call to a sub-template for that letter (<code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> etc.). The language code (passed into <kbd>Template:Latindict</kbd> as the first parameter), is passed on as the first parameter to the sub-template.
* Nothing else.

==== Template:Latindict/A etc. ====
These contain
* the actual lemmas, in the form of a <kbd>Template:Dict</kbd> entry for each lemma:
<nowiki>{{dict|lang ={{{1}}} |word=abavia|default=betovergrootmoeder |en=second great grandmother}}</nowiki>
* A link (now dead) to the Dutch/Flemish source material, as a <kbd>noinclude</kbd> so it won't show up on the page, but ''is'' visible in the source. This could have been done with an HTML comment.
''(Note: the English description in the example should be 'great-great-grandmother'.)''

The parameters to <kbd>Template:Dict</kbd> are filled in as follows:
;lang:The language code was passed in as the first parameter, and is now copied into this parameter: <kbd><nowiki>lang={{{1}}}</nowiki></kbd>.
;word:Set to the Latin lemma.
;default:Set to the Dutch description (which is wrong, this should be changed to the '''nl''' parameter everywhere; this is the main cause of the English/Dutch mixing of the descriptions).
;en, nl, fr, etc:Descriptions in other languages are given as a parameter named after their language code. Texts for other languages can be added here, e.g. <kbd>fr=Arrière-arrière-grand-mère</kbd>.

==== Template:Dict ====
This finally generates a display list entry based on the parameters.

The template turns the parameters into a display list entry, with the format
<nowiki>;'''word''':description</nowiki>
(The lemma word does not need to be explicitly made bold, the description list format already does that.)
This results in
;word:description

=== New structure ===

==== The main page (and the translations) ====
* The warning box about the error will probably be gone by this time.
* The code to suppress the Table of Contents remains.
* The call to <kbd>Template:Languages</kbd> can remain unchanged.
* The introductory text can probably remain unchanged.
* The call to <kbd>Template:Dict/Glossary</kbd> must be removed.
* The call <kbd><nowiki>{{Latindict}}</nowiki></kbd> must remain unchanged, with the language of the page as the first parameter (because the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word does not work on this wiki).
* The comment with instructions must be updated to reflect the new situation, i.e. find the lemma in <kbd>Template:Latindict</kbd> and edit it there.

The translated page pages must do the same changes:
* Remove the call to <kbd>Template:Dict/Glossary</kbd>.
* Update the translation of the instructions.

The result will be that:
* The homebrew ToC entries will jump to that letter on the main page.
* The "Edit" link on each section will open an edit on the section '''in the template''', allowing direct editing of lemmas.

==== Template:Latindict ====
Change to contain:
* A Table-of-Contents header with in-page links to all the letters. This replaces the <kbd>Template:Dict/Glossary</kbd> call from the main page. If the user clicks on one of these links, the view should jump to that letter header on the same page. This helps the user find a lemma more quickly.
: There will only be one call for this, so there is no need for a template. A simple set of <code><nowiki>[[#A|A]] - [[#B|B]] -[[#C|C]] - [[#D|D]] - ...</nowiki></code> with a table around it should do the trick. Copy from the template contents and search/replace <code><nowiki>{{{1}}</nowiki>}/</code> with <code>#</code>. Note that this moves this fuctionality from the main page (and the translated pages) to this template (with only one occurence), useful in all translations of the main page.
* Sections for each letter (unchanged). Simple <code>== A ==</code> headers are enough.
* In each section replace the <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> with all the <code><nowiki>{{dict|...}}</nowiki></code> entries for that letter. These can be substituted in by changing <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> to <code><nowiki>{{subst:Latindict/A|{{{1}}}}}</nowiki></code> and saving the page. Repeat for all the letters.

If all goes as expected, the ToC links will bring you to the section on the main page, and the auto-generated edit links will open this template for editing on the chosen section.

By allowing editing-by-section, users will not be overburdened by edit pages which are too big. As a major advantage, it will be much easier for editors to find the lemma they want to edit, without the need to search for the correct lettered subpage.

==== Template:Latindict/A etc. ====
These can all be eliminated.

==== Template:Dict ====
This must be overhauled.
* Eliminate the '''lang''' parameter. Take the language from the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word. On this wiki this will always have a valid value.
** Unfortunately, <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> always produces "en" on this wiki. So we still need the '''lang''' parameter
* Eliminate the '''default''' parameter.
** Or better: Allow '''default''' as an alternative for '''nl'''. This gives backward compatiblilty with the existing calls to this template.
* Other improvements are described in the [[#Improvements to Dict template]] section

=== Pages no longer needed ===
With this new structure the following pages can be eliminated:
* All the lettered sub-templates (<kbd>Template:Latindict/A</kbd> etc.).
* All the <kbd>Main:</kbd> space lettered sub-pages (<kbd>Latin words and expressions/A</kbd> etc.).
* All the Dutch translated main space lettered sub-pages (<kbd>Latin words and expressions/A/nl</kbd> etc.), and the pages they redirect to (<kbd>Nl:Latijnse woorden en expressies/A</kbd> etc.).
* Same for the French translated pages. Although we will have to copy the descriptions from the French pages into the <kbd>Template:Dict</kbd> calls as <kbd>fr=</kbd> parameters first.
* Status of the Hebrew translated pages needs to be examined.

== Actions to take for modification ==

=== Set up a test environment ===
Set up a test environment to create and test a better version of the template without disturbing the existing one.
* (done) Create a Sandbox subspace to my user page: <kbd>User:DomoViridi/TempTest</kbd>; Think about the use or no-use of capital letters in the names of the pages first (doesn't realy matter). Put my own version of the pages there, but in the <kbd>User:DomoViridi/TempTest</kbd> space. Test templates can be called with the syntax <code><nowiki>{{User:DomoViridi/TempTest/mytemplate}}</nowiki></code> (the braces ensure transclusion, the <kbd>User:</kbd> namespace replaces the default <kbd>Template:</kbd> namespace.
* (done) Create a template page with the test template, [[User:DomoViridi/TempTest/Dict]]. Fill it initially with a copy of the original <kbd>Template:Dict</kbd>.
* (done) Create a page with test cases, [[User:DomoViridi/TempTest/Testcases]]. Put some calls to our Dict template in it, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus| en=silly sod| nl=sukkel}}</nowiki></code>. Add many testcases and put their source code in nowiki text above each.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict/A]] with calls to the Dict template, using <code><nowiki>{{User:DomoViridi/TempTest/Dict}}</nowiki></code>. Copy the existing "A" page and shorten it, leaving some useful examples, with different languages, some abbreviations, and some missing languages. Add French translations to some of the lemmas. Also copy a different letter page (a short one), which has some translations.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict]] which calls our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space.
* (done) Create a main page [[User:DomoViridi/TempTest/Latin words and expressions]], which calls <code><nowiki>{{User:DomoViridi/TempTest/Latindict}}</nowiki></code>.
: '''Oh hey!''', it turns out <kbd>Template:Dict/Glossary</kbd> creates links to [[Latin words and expressions/A]] and all the other letters.
* (done) Create lettered pages [[User:DomoViridi/TempTest/Latin words and expressions/A]] for each of the pages for wich we have a template, and fill them with a copy of the originals. which call our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space. Note that this is all duplicate work.
* (done) Create a translated page [[User:DomoViridi/TempTest/Latin words and expressions/nl]], fill it with the contents of [[Nl:Latijnse woorden en expressies]]. Change the calls to point to the sandbox, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Latindict | nl}}</nowiki></code> (passing the language to the template).
: '''Oh hey!''', once again we see how the clumsy <kbd>Template:Dict/Glossary</kbd> requires subpages of the translated page, one for each letter of the alphabet.
* (done) Create the translated subpages before moving the translated main page.
: Although: this does not help, because the letter pages are not subpages of the <kbd>.../nl</kbd> page, but are formed with <kbd>.../A/nl</kbd>.
* (done) Move the translated page to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies]]. This will automatically create a redirect from the <kbd>/nl</kbd> page to this page.
* (done) Move all the frakking translated subpages to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies/A]], again auto-generating a redirect.

Creating 27 (one for each letter of the alphabet, plus '@') lettered subpages each time for:
* The Templates
* The main page (English)
* The Dutch (nl) translation
* The redirect for the Dutch (nl) translation
* The French (fr) translation
* The redirect for the French (fr) translation
* The Hebrew (he) translation
* The redirect Hebrew (he) translation
* The same again for every new translation
is an unbelievable pile of unnecessary busywork. All so that we can have separate pages for every letter, and links to them.
Good thing I only did letters A and B for this sandbox.

''Note: the Gramps wiki does not support the [https://www.mediawiki.org/wiki/Extension:TemplateSandbox TemplateSandbox extension], which would have allowed to attach a sandbox subpage directly to the template. This means the <code><nowiki>{{testcases notice}}</nowiki></code> template is also not available.''

=== Create an improved Dict template ===
(done) Do this in the sandbox. See the [[#Improvements to Dict template]] section.

(done) Don't forget to adjust the documentation.

(done) When it works with no detected problems, overwrite the actual template with our code.

=== Change "default" to "nl" ===
Because <kbd>Template:Dict</kbd> defaults to <nowiki>{{{en}}}</nowiki> if there is no description in a valid language, changing '''default''' to '''nl''' will result in a lot of bad output for all entries where '''en''' is missing.
: (done) Solution: make '''default''' an alternative for '''nl''', so if '''lang=en''' then a blank description is shown, and if '''lang=nl''' then the Dutch '''default''' description is shown.

(done) This means we need to modify <kbd>Template:Dict</kbd> before we make this change.

(deferred) Edit all the <kbd>Template:Latindict/<letter></kbd> pages to change '''default=''' to '''nl='''.
The effect should be that Dutch descriptions only show on the Dutch pages.
* Start with a small page and see how it goes.
* Then do a few more with export-to-editor, bulk search/replace, import from editor. Check for anomalies.
* Do the other pages

(deferred) This should all have effect without the need to change the templates yet. It also makes room for a modification of <kbd>Template:Dict</kbd> which drops the '''default''' parameter.

Note: This operation has been deferred, pending a decision to about the future of this dictionary.

=== Restructure the template cascade ===
Do this in the sandbox. See [[#Restructuring the template cascade]].
Make sure it works perfectly.

Before modifying the real pages, put notices in the talk pages and banners in any and all of the pages involved.

Then modify the real pages.

Try to get the useless pages deleted. At the least put a warning box in them. Something like "Do not use this page. Use page xxx instead. This page will be deleted in the near future".

=== Move the translated French pages ===
Copy all the existing French translations to the <kbd>Template:Latindict/<letter></kbd> pages.
Note: This leaves the translated French pages unchanged for now.
* Could be a big job.
* Have these pages changed much in the last few years?
* Put a notice on the Talk page for the French translation to tell them what is going on.
* Maybe put a banner on the pages too.
* Make sure they work nicely.

Switch the translated French page to use Template:Latindict
* One edit to [[Fr:Mots et expressions en latin]] should be enough.
* Add a notice to the French page about the change

=== Check the Hebrew pages ===
Check what the Hebrew pages look like now that we changed '''default=''' to '''nl='''.

=== Remove unneeded pages ===
Remove all the unneeded letter pages and letter templates, for each language that uses them.

=== Possible 'silent' mode ===
We may want to add a "silent" mode, where lemmas are not shown if there is no description for that language. This will avoid long pages of untranslated Latin words and expressions, and emphasise the lemmas that have been translated.

This will require an extra parameter, which must be passed down through all the templates. This named parameter should be given with a value, so that it evaluates to "take the then case" for the parser function:
<nowiki>{{#if:{{{silent|}}} | do silent version | do not-silent version}}</nowiki>
That means the parameter should be set as <kbd>"silent=<something>"</kbd>, with an arbitrary, non-empty value. See [https://www.mediawiki.org/wiki/Help:Parser_functions_in_templates Parser functions in templates]
* On page [[Latin words and expressions/fr]]: call template <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd> for silent and <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd> for not-silent.
* [[Template:Latindict]]: call <kbd><nowiki>{{Latindict/A|{{{1}}}|silent={{{silent|}}}}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* [[Template:Latindict/A]]: call <kbd><nowiki>{{Dict|lang={{{1}}}|silent={{{silent|}}}|word=...}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* Inside [[Template:Dict]] use <kbd><nowiki>{{#if: {{{silent|}}} | do silent stuff | do non-silent stuff}}</nowiki></kbd> (again with a bar after the parameter).

The following table shows how the parameter values trickle down to the <kbd>#if</kbd> parser, with or without the extra bar (<kbd>|</kbd>). The conclusion is that the extra bar should be used thoughout, and the parameter should be omitted for non-silent mode and passed with a value (e.g. <kbd>silent=yes</kbd>) for silent mode. The string used for the value (in this example "yes") does not matter. Note that passing the parameter with an empty string as a value ("<kbd>silent=</kbd>") will set the result to non-silent.

''Note: the use of the variables <kbd>s1</kbd>, <kbd>s2</kbd> and <kbd>s3</kbd> is arbitrary, and is used here for clarity. They could all be called <kbd>silent</kbd>.''

{| class="wikitable" style="margin:auto" width="90%"
|+ Passing on the silent parameter
! Main page
! <kbd>Latindict</kbd>
! <kbd>Latindict/A</kbd>
! <kbd>Dict</kbd>
! <kbd>#if</kbd>
|-
! style="text-align:right" | without bar
! <kbd><nowiki>s1={{{silent}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| then
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
! style="text-align:right" | with bar
! <kbd><nowiki>s1={{{silent|}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
|}

In the end, all the entries in [[Template:Latindict]] need to be modified, as must all calls to [[Template:Dict]] in all the letter templates ([[Template:Latindict/A]] etc.). And finally [[Template:Dict]] needs to implement the silent mode.

== Copyright ==
The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

User:DomoViridi/TempTest

2026-03-13T15:02:11Z

DomoViridi: /* Create an improved Dict template */ All done

The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

== Sandbox to test templates ==

For [[Template:Latindict]], [[Template:Latindict/A]] (and all the other letter-subpages), [[Template:Dict/Glossary]], [[Template:Dict]], as used in [[Latin words and expressions]], and the translations [[Latin words and expressions/nl]], [[Latin words and expressions/fr]] and [[Latin words and expressions/he]].

== Improvements to Dict template ==

* The '''default''' parameter does not make sense, and should be eliminated. If there is no descriptive text for a given language, then the wiki page should show a blank line (or nothing).
: Before removing it, in all uses of this template '''default=''' should be replaced with '''nl='''. This is also the solution to the problem of showing lots of Dutch language descriptions on the English pages.
:* Better yet: first make '''default''' an alternative to '''nl'''. That way, the existing calls to this template can remain unchanged, while also only showing the Dutch description (given in '''default''') if '''lang''' is "nl".

* The '''lang''' parameter is exclusively used as <code><nowiki>{{dict|lang ={{{1}}} |word=...</nowiki></code>, i.e. the value is read from the first unnamed parameter that was passed to <kbd>Template:Latindict/A</kbd>. This value cascades down from the main page.
: This cascade might be unnecessary, because the template should be able to use the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word. Entries can then be simplified to <code><nowiki>{{dict|word=...</nowiki></code>. For the use in special cases '''lang=''' could be left available to override the wiki language setting for a particular lemma.
:* Unfortunately <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> always returns "en" on this wiki, even on .../nl and Nl:... pages.

* The '''word''' named parameter should be optional, and the word should be allowed to be passed as the first anonymous parameter, so we can write <code><nowiki>{{dict| abiit| en=he/she has left | nl=hij/zij is vertrokken }}</nowiki></code>.
: Disadvantage: That would make the lemma an unnamed parameter. Unnamed parameters are not stripped of leading and trailing spaces. This can lead to lemmas with extra spaces around them.
: Although: because it is the term in a definition list, leading spaces are ignored, and trailing spaces do not affect the layout (the displayed wiki text goes to a new line after the term), or are maybe also ignored.
:* Beware: Though spaces have little effect, a value for an unnamed parameter should never be the last thing on a line, because then the newline following the parameter will become part of the parameter value. In this template that messes up the description-list-item format.
:* This might also be true for a newline ''before'' an unnamed parameter.
: Can be implemented with <code><nowiki>{{{word|{{{1}}} }}}</nowiki></code> in the template. This accepts the first anonymous parameter, except when a '''word''' parameter was given when calling the template. This gives backward compatibility, where it is ''allowed'' to use the '''word''' parameter, but not ''mandatory''.

* Make it so that <kbd>Template:Dict</kbd> does not need an explicit list of language codes. The current list blocks additional translations from being added.
: The value of the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word can be used to create the name of the desired parameter, e.g. "en". See [https://www.mediawiki.org/wiki/Manual:Advanced_templates#Variable_parameter_name Mediawiki Advanced Templates Help: Variable parameter name].
:Code: <code><nowiki>;{{{word|{{{1}}} }}}:{{{ {{PAGELANGUAGE}} }}}</nowiki></code>
: The use of <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> also makes '''en''' the default language.
:* Unfortunately <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> always returns "en", making it useless. We still need the '''lang''' parameter. The trick with double evaluation of the parameter still works, so we can write:
:: <code><nowiki>;{{{word|{{{1}}} }}}:{{{ {{{lang}}} }}}</nowiki></code>

* The current version outputs <code><nowiki>{{{en}}}</nowiki></code> if no '''default''' or language code parameter was given. Also produces <code><nowiki>'''{{{word}}}'''</nowiki></code> if no '''word''' parameter was given.
:This is probably actually a good thing, because it shows when there is an error and the template call should be edited to resolve this.
: '''documentation''': add to the docs what parameters should be given and what happens if one is missing.

* There should be a parameter to give the expansion of an abbreviation, separate from the translations. For example <code><nowiki>{{dict|A.D.|full=Anno Domini"|en=in the year of our lord|nl=in het jaar van de Heer}}</nowiki></code>. The wiki format to be produced needs to be invented. Possibly as extra text in parentheses added to the lemma, e.g.
:;A.D. (Anno Domini):in the year of our lord
:Or on the description line:
:;A.D.:'''Anno Domini''': in the year of our lord
: By putting the formatting in the template we can ensure that it is universal accross all pages.
:* This addition is very useful, and helps to show lemmas which only had an expansion (as the '''default''' value), but no language-specific descriptions.

=== Behaviour for missing description text ===
If there is no descriptive text parameter for the language of the page, then by default the template will show the lemma, but with an empty description.

This might be annoying for translations with relatively few translated descriptions (e.g. for brand new translated pages). The reader will be looking at a long list of lemmas with only a few descriptions.

A possible solution is the introduction of a '''show''' parameter, which will determine what will happen if the lemma has is no descriptive text for the current language. Possible values:
;quiet:Show nothing. Pages will only show the lemmas which have a description in the page's language.
;blank:The default. Show the lemma with a blank description.
;a language code:Substitute the description with the given language. (Complicated implementation; maybe wait if there is demand for it.)
If the parameter is not set then do the '''blank''' behaviour.

For this parameter to work, we need to set up a new cascade of parameter passing.
Then this parameter can be set on the main page for a language, e.g. initially '''quiet''' or '''nl''', later to be removed as the descriptions start to become more common.

== Restructuring the template cascade ==

The subdivision into templates for each letter of the alphabet is a pain in the <donkey>, and actually unnecessary.
We describe how it is structured currently (Feb 2006), and draw up a plan for a simpler structure.

=== The two paths to this template: why? ===
Find out why there are two paths to this template:
# Through [[Template:Latindict]] and [[Template:Latindict/A]] (and the other letters).
# Via non-template "Latin words and expressions/''letter''" pages.
This also happens for the Dutch translated pages, so we get
Latin words and expressions/nl/A
Latin words and expressions/nl/B
etc.
and also
Nl:Latijnse woorden en uitdrukkingen/A
Nl:Latijnse woorden en uitdrukkingen/A
etc.

At first the suspect in this was the French translation, which uses a translated French page for each letter page.

Looking at the page history of the pages involved to see what happened, it turns out these pages were created around the same time and by the same author as the templates. They might be a remnant of an earlier setup. Examination of the exact creation dates and time may shed more light.

While this is going on, the use of <kbd>Template:languages</kbd> and <kbd>Template:Dict/Glossary</kbd> on all these pages creates a tangled web of pages being linked to by other pages. For example
Nl:Latijnse woorden en uitdukkingen/A
is linked to by:
* The main Dutch page
* Itself
* The non-redirected version of itself
* The main French page
* Every other <kbd>Nl:Latijnse woorden en uitdukkingen/''letter''</kbd> page

=== The Reason ===
All these subpages were created in a desperate bid by the original author to split the list into separate pages, allowing an editor to edit the list only a letter-section at the time, rather than having to edit the entire list of thousands of lemmas.

Because the actual content of the article is transcluded, the normal "edit by section" mechanism does not work.

This problem is not trivial to solve. Idealy [https://www.mediawiki.org/ mediawiki] should have a built-in mechanism to redirect an action to edit a section to edit the section in the transcluded page.
: '''Find out''' if such a mechanism exists

The documentation on this subject is shockingly poor. We must find out through experimentation.

[[User:DomoViridi/Temsects|It turns out]] that the '''current Wiki''' implements this '''exactly as expected'''.
* Put the sections in a transcluded file
* Transclude that file in the main file
* Put a ToC in either the main file or the transcluded file (both work), with simple <code><nowiki>[[#A|A]]</nowiki></code> links
* The ToC links will show you the section on the main page
* The auto-generated edit links will open the transcluded file on that section
* It also works with [[User:DomoViridi/Temsects/nl|translated pages]]

=== Current structure ===

==== The main page [[Latin_words_and_expressions]] ====
This contains
* A warning box about the mixing of English and Dutch descriptions.
* A code to suppress the Table of Contents.
* A call to <kbd>Template:Languages</kbd>, to make automatic links to the translated pages.
* An introductory text.
* A call to <kbd>Template:Dict/Glossary</kbd>, passing the name of the page as a parameter. This generates a substitute Table of Contents, linking to all the letter sections which will be generated on this page. '''Note:''' instead of passing a literal copy of the name of the page, the code <code><nowiki>{{BASEPAGENAME}}</nowiki></code> should have been used by the template.
* A call to <kbd>Template:Latindict, with the language code as a parameter (<nowiki>{{latindict|en}}</nowiki>). The language code is not needed, as <kbd>Template:Dict</kbd> should have used the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word.
* A comment with instructions on where to edit lemmas.
* A Category link <code><nowiki>[[Category:Genealogy|L]]</nowiki></code>.

Translated pages such as [[Latin_words_and_expressions/nl]] (or the page they redirect to) contain the same, with adaptations.
* The introductory text is translated.
* The parameter passed to <kbd>Template:Dict/Glossary</kbd> changed to the translated page name. (Using <code><nowiki>{{BASEPAGENAME}}</nowiki></code> would have prevented this, but that issue is moot in the new structure.)
* The parameter passed to <kbd>Template:Latindict</kbd> is changed to the code for the translated language. (Again, this could have been automated using <code><nowiki>{{PAGELANGUAGE}}</nowiki></code>. Again, issue is moot in the new structure.)
* The instructions in the comment are translated.
* The Category link is translated: <code><nowiki>[[Category:Nl:Genealogie|Latijnse woorden]]</nowiki></code>.

==== Template:Latindict ====
This contains
* A list of sections, one for each letter of the alphabet, and one for the 'at' symbol (<kbd>@</kbd>), with a Level 2 header with that letter.
* In each letter section, a call to a sub-template for that letter (<code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> etc.). The language code (passed into <kbd>Template:Latindict</kbd> as the first parameter), is passed on as the first parameter to the sub-template.
* Nothing else.

==== Template:Latindict/A etc. ====
These contain
* the actual lemmas, in the form of a <kbd>Template:Dict</kbd> entry for each lemma:
<nowiki>{{dict|lang ={{{1}}} |word=abavia|default=betovergrootmoeder |en=second great grandmother}}</nowiki>
* A link (now dead) to the Dutch/Flemish source material, as a <kbd>noinclude</kbd> so it won't show up on the page, but ''is'' visible in the source. This could have been done with an HTML comment.
''(Note: the English description in the example should be 'great-great-grandmother'.)''

The parameters to <kbd>Template:Dict</kbd> are filled in as follows:
;lang:The language code was passed in as the first parameter, and is now copied into this parameter: <kbd><nowiki>lang={{{1}}}</nowiki></kbd>.
;word:Set to the Latin lemma.
;default:Set to the Dutch description (which is wrong, this should be changed to the '''nl''' parameter everywhere; this is the main cause of the English/Dutch mixing of the descriptions).
;en, nl, fr, etc:Descriptions in other languages are given as a parameter named after their language code. Texts for other languages can be added here, e.g. <kbd>fr=Arrière-arrière-grand-mère</kbd>.

==== Template:Dict ====
This finally generates a display list entry based on the parameters.

The template turns the parameters into a display list entry, with the format
<nowiki>;'''word''':description</nowiki>
(The lemma word does not need to be explicitly made bold, the description list format already does that.)
This results in
;word:description

=== New structure ===

==== The main page (and the translations) ====
* The warning box about the error will probably be gone by this time.
* The code to suppress the Table of Contents remains.
* The call to <kbd>Template:Languages</kbd> can remain unchanged.
* The introductory text can probably remain unchanged.
* The call to <kbd>Template:Dict/Glossary</kbd> must be removed.
* The call <kbd><nowiki>{{Latindict}}</nowiki></kbd> must remain unchanged, with the language of the page as the first parameter (because the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word does not work on this wiki).
* The comment with instructions must be updated to reflect the new situation, i.e. find the lemma in <kbd>Template:Latindict</kbd> and edit it there.

The translated page pages must do the same changes:
* Remove the call to <kbd>Template:Dict/Glossary</kbd>.
* Update the translation of the instructions.

The result will be that:
* The homebrew ToC entries will jump to that letter on the main page.
* The "Edit" link on each section will open an edit on the section '''in the template''', allowing direct editing of lemmas.

==== Template:Latindict ====
Change to contain:
* A Table-of-Contents header with in-page links to all the letters. This replaces the <kbd>Template:Dict/Glossary</kbd> call from the main page. If the user clicks on one of these links, the view should jump to that letter header on the same page. This helps the user find a lemma more quickly.
: There will only be one call for this, so there is no need for a template. A simple set of <code><nowiki>[[#A|A]] - [[#B|B]] -[[#C|C]] - [[#D|D]] - ...</nowiki></code> with a table around it should do the trick. Copy from the template contents and search/replace <code><nowiki>{{{1}}</nowiki>}/</code> with <code>#</code>. Note that this moves this fuctionality from the main page (and the translated pages) to this template (with only one occurence), useful in all translations of the main page.
* Sections for each letter (unchanged). Simple <code>== A ==</code> headers are enough.
* In each section replace the <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> with all the <code><nowiki>{{dict|...}}</nowiki></code> entries for that letter. These can be substituted in by changing <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> to <code><nowiki>{{subst:Latindict/A|{{{1}}}}}</nowiki></code> and saving the page. Repeat for all the letters.

If all goes as expected, the ToC links will bring you to the section on the main page, and the auto-generated edit links will open this template for editing on the chosen section.

By allowing editing-by-section, users will not be overburdened by edit pages which are too big. As a major advantage, it will be much easier for editors to find the lemma they want to edit, without the need to search for the correct lettered subpage.

==== Template:Latindict/A etc. ====
These can all be eliminated.

==== Template:Dict ====
This must be overhauled.
* Eliminate the '''lang''' parameter. Take the language from the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word. On this wiki this will always have a valid value.
** Unfortunately, <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> always produces "en" on this wiki. So we still need the '''lang''' parameter
* Eliminate the '''default''' parameter.
** Or better: Allow '''default''' as an alternative for '''nl'''. This gives backward compatiblilty with the existing calls to this template.
* Other improvements are described in the [[#Improvements to Dict template]] section

=== Pages no longer needed ===
With this new structure the following pages can be eliminated:
* All the lettered sub-templates (<kbd>Template:Latindict/A</kbd> etc.).
* All the <kbd>Main:</kbd> space lettered sub-pages (<kbd>Latin words and expressions/A</kbd> etc.).
* All the Dutch translated main space lettered sub-pages (<kbd>Latin words and expressions/A/nl</kbd> etc.), and the pages they redirect to (<kbd>Nl:Latijnse woorden en expressies/A</kbd> etc.).
* Same for the French translated pages. Although we will have to copy the descriptions from the French pages into the <kbd>Template:Dict</kbd> calls as <kbd>fr=</kbd> parameters first.
* Status of the Hebrew translated pages needs to be examined.

== Actions to take for modification ==

=== Set up a test environment ===
Set up a test environment to create and test a better version of the template without disturbing the existing one.
* (done) Create a Sandbox subspace to my user page: <kbd>User:DomoViridi/TempTest</kbd>; Think about the use or no-use of capital letters in the names of the pages first (doesn't realy matter). Put my own version of the pages there, but in the <kbd>User:DomoViridi/TempTest</kbd> space. Test templates can be called with the syntax <code><nowiki>{{User:DomoViridi/TempTest/mytemplate}}</nowiki></code> (the braces ensure transclusion, the <kbd>User:</kbd> namespace replaces the default <kbd>Template:</kbd> namespace.
* (done) Create a template page with the test template, [[User:DomoViridi/TempTest/Dict]]. Fill it initially with a copy of the original <kbd>Template:Dict</kbd>.
* (done) Create a page with test cases, [[User:DomoViridi/TempTest/Testcases]]. Put some calls to our Dict template in it, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus| en=silly sod| nl=sukkel}}</nowiki></code>. Add many testcases and put their source code in nowiki text above each.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict/A]] with calls to the Dict template, using <code><nowiki>{{User:DomoViridi/TempTest/Dict}}</nowiki></code>. Copy the existing "A" page and shorten it, leaving some useful examples, with different languages, some abbreviations, and some missing languages. Add French translations to some of the lemmas. Also copy a different letter page (a short one), which has some translations.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict]] which calls our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space.
* (done) Create a main page [[User:DomoViridi/TempTest/Latin words and expressions]], which calls <code><nowiki>{{User:DomoViridi/TempTest/Latindict}}</nowiki></code>.
: '''Oh hey!''', it turns out <kbd>Template:Dict/Glossary</kbd> creates links to [[Latin words and expressions/A]] and all the other letters.
* (done) Create lettered pages [[User:DomoViridi/TempTest/Latin words and expressions/A]] for each of the pages for wich we have a template, and fill them with a copy of the originals. which call our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space. Note that this is all duplicate work.
* (done) Create a translated page [[User:DomoViridi/TempTest/Latin words and expressions/nl]], fill it with the contents of [[Nl:Latijnse woorden en expressies]]. Change the calls to point to the sandbox, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Latindict | nl}}</nowiki></code> (passing the language to the template).
: '''Oh hey!''', once again we see how the clumsy <kbd>Template:Dict/Glossary</kbd> requires subpages of the translated page, one for each letter of the alphabet.
* (done) Create the translated subpages before moving the translated main page.
: Although: this does not help, because the letter pages are not subpages of the <kbd>.../nl</kbd> page, but are formed with <kbd>.../A/nl</kbd>.
* (done) Move the translated page to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies]]. This will automatically create a redirect from the <kbd>/nl</kbd> page to this page.
* (done) Move all the frakking translated subpages to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies/A]], again auto-generating a redirect.

Creating 27 (one for each letter of the alphabet, plus '@') lettered subpages each time for:
* The Templates
* The main page (English)
* The Dutch (nl) translation
* The redirect for the Dutch (nl) translation
* The French (fr) translation
* The redirect for the French (fr) translation
* The Hebrew (he) translation
* The redirect Hebrew (he) translation
* The same again for every new translation
is an unbelievable pile of unnecessary busywork. All so that we can have separate pages for every letter, and links to them.
Good thing I only did letters A and B for this sandbox.

''Note: the Gramps wiki does not support the [https://www.mediawiki.org/wiki/Extension:TemplateSandbox TemplateSandbox extension], which would have allowed to attach a sandbox subpage directly to the template. This means the <code><nowiki>{{testcases notice}}</nowiki></code> template is also not available.''

=== Create an improved Dict template ===
(done) Do this in the sandbox. See the [[#Improvements to Dict template]] section.

(done) Don't forget to adjust the documentation.

(done) When it works with no detected problems, overwrite the actual template with our code.

=== Change "default" to "nl" ===
Because <kbd>Template:Dict</kbd> defaults to <nowiki>{{{en}}}</nowiki> if there is no description in a valid language, changing '''default''' to '''nl''' will result in a lot of bad output for all entries where '''en''' is missing.

This means we need to modify <kbd>Template:Dict</kbd> before we make this change.

Edit all the <kbd>Template:Latindict/<letter></kbd> pages to change '''default=''' to '''nl='''.
The effect should be that Dutch descriptions only show on the Dutch pages.
* Start with a small page and see how it goes.
* Then do a few more with export-to-editor, bulk search/replace, import from editor. Check for anomalies.
* Do the other pages

This should all have effect without the need to change the templates yet. It also makes room for a modification of <kbd>Template:Dict</kbd> which drops the '''default''' parameter.

=== Restructure the template cascade ===
Do this in the sandbox. See [[#Restructuring the template cascade]].
Make sure it works perfectly.

Before modifying the real pages, put notices in the talk pages and banners in any and all of the pages involved.

Then modify the real pages.

Try to get the useless pages deleted. At the least put a warning box in them. Something like "Do not use this page. Use page xxx instead. This page will be deleted in the near future".

=== Move the translated French pages ===
Copy all the existing French translations to the <kbd>Template:Latindict/<letter></kbd> pages.
Note: This leaves the translated French pages unchanged for now.
* Could be a big job.
* Have these pages changed much in the last few years?
* Put a notice on the Talk page for the French translation to tell them what is going on.
* Maybe put a banner on the pages too.
* Make sure they work nicely.

Switch the translated French page to use Template:Latindict
* One edit to [[Fr:Mots et expressions en latin]] should be enough.
* Add a notice to the French page about the change

=== Check the Hebrew pages ===
Check what the Hebrew pages look like now that we changed '''default=''' to '''nl='''.

=== Remove unneeded pages ===
Remove all the unneeded letter pages and letter templates, for each language that uses them.

=== Possible 'silent' mode ===
We may want to add a "silent" mode, where lemmas are not shown if there is no description for that language. This will avoid long pages of untranslated Latin words and expressions, and emphasise the lemmas that have been translated.

This will require an extra parameter, which must be passed down through all the templates. This named parameter should be given with a value, so that it evaluates to "take the then case" for the parser function:
<nowiki>{{#if:{{{silent|}}} | do silent version | do not-silent version}}</nowiki>
That means the parameter should be set as <kbd>"silent=<something>"</kbd>, with an arbitrary, non-empty value. See [https://www.mediawiki.org/wiki/Help:Parser_functions_in_templates Parser functions in templates]
* On page [[Latin words and expressions/fr]]: call template <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd> for silent and <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd> for not-silent.
* [[Template:Latindict]]: call <kbd><nowiki>{{Latindict/A|{{{1}}}|silent={{{silent|}}}}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* [[Template:Latindict/A]]: call <kbd><nowiki>{{Dict|lang={{{1}}}|silent={{{silent|}}}|word=...}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* Inside [[Template:Dict]] use <kbd><nowiki>{{#if: {{{silent|}}} | do silent stuff | do non-silent stuff}}</nowiki></kbd> (again with a bar after the parameter).

The following table shows how the parameter values trickle down to the <kbd>#if</kbd> parser, with or without the extra bar (<kbd>|</kbd>). The conclusion is that the extra bar should be used thoughout, and the parameter should be omitted for non-silent mode and passed with a value (e.g. <kbd>silent=yes</kbd>) for silent mode. The string used for the value (in this example "yes") does not matter. Note that passing the parameter with an empty string as a value ("<kbd>silent=</kbd>") will set the result to non-silent.

''Note: the use of the variables <kbd>s1</kbd>, <kbd>s2</kbd> and <kbd>s3</kbd> is arbitrary, and is used here for clarity. They could all be called <kbd>silent</kbd>.''

{| class="wikitable" style="margin:auto" width="90%"
|+ Passing on the silent parameter
! Main page
! <kbd>Latindict</kbd>
! <kbd>Latindict/A</kbd>
! <kbd>Dict</kbd>
! <kbd>#if</kbd>
|-
! style="text-align:right" | without bar
! <kbd><nowiki>s1={{{silent}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| then
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
! style="text-align:right" | with bar
! <kbd><nowiki>s1={{{silent|}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
|}

In the end, all the entries in [[Template:Latindict]] need to be modified, as must all calls to [[Template:Dict]] in all the letter templates ([[Template:Latindict/A]] etc.). And finally [[Template:Dict]] needs to implement the silent mode.

== Copyright ==
The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

User:DomoViridi/TempTest/Testcases/nl

2026-03-13T14:35:56Z

DomoViridi: Added non-transcluded call to magic words.

(NL subpage)

Before the transclusion:

FULLPAGENAME for this page is {{FULLPAGENAME}}.

PAGELANGUAGE for this page is {{PAGELANGUAGE}}, for {{#language:{{PAGELANGUAGE}}}}.

In the transcluded page:

{{../../Testcases}}

User:DomoViridi/TempTest/Testcases

2026-03-13T10:43:58Z

DomoViridi: /* Spacing check */ Good code makes only one HTML <dl> block

Test cases for the sandbox Dict template.

FULLPAGENAME for this page is {{FULLPAGENAME}}.

PAGELANGUAGE for this page is {{PAGELANGUAGE}}, for {{#language:{{PAGELANGUAGE}}}}.

Note: In this format, the case of the template name '''does''' matter. "Dict" works, but "dict" does not.

== Classic, with lang and default= for Dutch ==

=== Straight-up classic entry, calling English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
| default=sukkel
}}

=== Straight-up classic entry, calling Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
| default=sukkel
}}

=== Straight-up classic entry, calling French ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=fr| word=sillius soddus
| en=silly sod
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=fr| word=sillius soddus
| en=silly sod
| default=sukkel
}}

=== Straight-up classic entry, calling Spanish ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
| default=sukkel
}}

=== Only English, calling English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
}}

=== Only English, calling Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
}}

=== Only English, calling Spanish ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
}}

=== Only Dutch, calling English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| default=sukkel
}}

=== Only Dutch, calling Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| default=sukkel
}}

=== Only Dutch, calling Spanish ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| default=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| default=sukkel
}}

== With lang parameter ==

=== Straight-up classic entry, calling English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
| nl=sukkel
}}

=== Straight-up classic entry, calling Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
| nl=sukkel
}}

=== Straight-up classic entry, calling French ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=fr| word=sillius soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=fr| word=sillius soddus
| en=silly sod
| nl=sukkel
}}

=== Straight-up classic entry, calling Spanish ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
| nl=sukkel
}}

=== Only English, calling English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| en=silly sod
}}

=== Only English, calling Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| en=silly sod
}}

=== Only English, calling Spanish ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| en=silly sod
}}

=== Only Dutch, calling English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus
| nl=sukkel
}}

=== Only Dutch, calling Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=sillius soddus
| nl=sukkel
}}

=== Only Dutch, calling Spanish ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=sp| word=sillius soddus
| nl=sukkel
}}

== No lang parameter ==

=== Full ===
<nowiki>{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| en=silly sod
| nl=sukkel
}}

=== No parameters ===
<nowiki>{{User:DomoViridi/TempTest/Dict}}</nowiki>
{{User:DomoViridi/TempTest/Dict}}

=== Only English ===
<nowiki>{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| en=silly sod
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| en=silly sod
}}

=== Only Dutch ===
<nowiki>{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| nl=sukkel
}}

== Adding a language span ==
Adding
<nowiki>...</nowiki>
might set the PAGELANGUAGE magic word in the template.

<nowiki>{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | word=sillius soddus
| en=silly sod
| nl=sukkel
}}

== With 'full' parameter ==
Planned for future support for abbreviations.

Classical, with only the '''default''' parameter, containing the expansion (en).
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=S.S. | default=Sillius Soddus}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=S.S. | default=Sillius Soddus}}

Classical, with only the '''default''' parameter, containing the expansion (nl).
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | default=Sillius Soddus}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | default=Sillius Soddus}}

Modernised, with '''full''' parameter and '''en''' and '''nl''' translations (en).
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=en| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}

Modernised, with '''full''' parameter and '''en''' and '''nl''' translations (nl).
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}</nowiki>
{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}

== Spacing check ==
Does the template introduce extra newlines or spaces?

=== Calls close together ===
<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}
{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}
{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}</nowiki>

{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}
{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}
{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}
These should generate only one HTML <dl> block.

=== Calls with blank line in between ===

<nowiki>{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}

{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}

{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}</nowiki>

{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}

{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}

{{User:DomoViridi/TempTest/Dict | lang=nl| word=S.S. | full=Sillius Soddus
| en=silly sod
| nl=sukkel
}}
These will generate separate HTML <dl> blocks.
The vertical space between entries should be slightly larger than with a single block.

=== Silly: two calls on one line ===
<nowiki>{{User:DomoViridi/TempTest/Dict|lang=nl|abamita|nl=overgrootmoeder}}{{User:DomoViridi/TempTest/Dict|lang=nl|abamita|nl=overgrootmoeder}}</nowiki>

{{User:DomoViridi/TempTest/Dict|lang=nl|abamita|nl=overgrootmoeder}}{{User:DomoViridi/TempTest/Dict|lang=nl|abamita|nl=overgrootmoeder}}

These should also generate only one HTML <dl> block.
Although: really tight template coding should produce malformed wiki code:
<nowiki>;abamita:overgrootmoeder;abimata:overgrootmoeder</nowiki>
resulting in
;abamita:overgrootmoeder;abimata:overgrootmoeder

== The real template ==

Word as first parameter (nl)
<nowiki>{{Dict|lang=nl|abamita|nl=overgrootmoeder}}</nowiki>

{{Dict|lang=nl|abamita|nl=overgrootmoeder}}

== Problem with unnamed word parameter ==

Gives problem in [[Template:Latindict/K]]

The unnamed '''word''' parameter should not be followed by a newline.
That newline becomes part of the value.
That breaks up the description-list-entry format.
<nowiki>{{dict|lang ={{{1}}} |k
|nl= zie c
|en= see c
}}</nowiki>

{{dict|lang ={{{1}}} |k
|nl= zie c
|en= see c
}}

Our local template:
<nowiki>{{User:DomoViridi/TempTest/Dict|lang ={{{1}}} |k
|nl= zie c
|en= see c
}}</nowiki>

{{User:DomoViridi/TempTest/Dict|lang ={{{1}}} |k
|nl= zie c
|en= see c
}}

Better:
<nowiki>{{User:DomoViridi/TempTest/Dict|lang ={{{1}}} |k|
nl= zie c|
en= see c|
}}</nowiki>

{{User:DomoViridi/TempTest/Dict|lang ={{{1}}} |k|
nl= zie c|
en= see c|
}}

User:DomoViridi/TempTest

2026-03-12T08:46:53Z

DomoViridi: /* Improvements to Dict template */ "full" parameter is useful

The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

== Sandbox to test templates ==

For [[Template:Latindict]], [[Template:Latindict/A]] (and all the other letter-subpages), [[Template:Dict/Glossary]], [[Template:Dict]], as used in [[Latin words and expressions]], and the translations [[Latin words and expressions/nl]], [[Latin words and expressions/fr]] and [[Latin words and expressions/he]].

== Improvements to Dict template ==

* The '''default''' parameter does not make sense, and should be eliminated. If there is no descriptive text for a given language, then the wiki page should show a blank line (or nothing).
: Before removing it, in all uses of this template '''default=''' should be replaced with '''nl='''. This is also the solution to the problem of showing lots of Dutch language descriptions on the English pages.
:* Better yet: first make '''default''' an alternative to '''nl'''. That way, the existing calls to this template can remain unchanged, while also only showing the Dutch description (given in '''default''') if '''lang''' is "nl".

* The '''lang''' parameter is exclusively used as <code><nowiki>{{dict|lang ={{{1}}} |word=...</nowiki></code>, i.e. the value is read from the first unnamed parameter that was passed to <kbd>Template:Latindict/A</kbd>. This value cascades down from the main page.
: This cascade might be unnecessary, because the template should be able to use the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word. Entries can then be simplified to <code><nowiki>{{dict|word=...</nowiki></code>. For the use in special cases '''lang=''' could be left available to override the wiki language setting for a particular lemma.
:* Unfortunately <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> always returns "en" on this wiki, even on .../nl and Nl:... pages.

* The '''word''' named parameter should be optional, and the word should be allowed to be passed as the first anonymous parameter, so we can write <code><nowiki>{{dict| abiit| en=he/she has left | nl=hij/zij is vertrokken }}</nowiki></code>.
: Disadvantage: That would make the lemma an unnamed parameter. Unnamed parameters are not stripped of leading and trailing spaces. This can lead to lemmas with extra spaces around them.
: Although: because it is the term in a definition list, leading spaces are ignored, and trailing spaces do not affect the layout (the displayed wiki text goes to a new line after the term), or are maybe also ignored.
:* Beware: Though spaces have little effect, a value for an unnamed parameter should never be the last thing on a line, because then the newline following the parameter will become part of the parameter value. In this template that messes up the description-list-item format.
:* This might also be true for a newline ''before'' an unnamed parameter.
: Can be implemented with <code><nowiki>{{{word|{{{1}}} }}}</nowiki></code> in the template. This accepts the first anonymous parameter, except when a '''word''' parameter was given when calling the template. This gives backward compatibility, where it is ''allowed'' to use the '''word''' parameter, but not ''mandatory''.

* Make it so that <kbd>Template:Dict</kbd> does not need an explicit list of language codes. The current list blocks additional translations from being added.
: The value of the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word can be used to create the name of the desired parameter, e.g. "en". See [https://www.mediawiki.org/wiki/Manual:Advanced_templates#Variable_parameter_name Mediawiki Advanced Templates Help: Variable parameter name].
:Code: <code><nowiki>;{{{word|{{{1}}} }}}:{{{ {{PAGELANGUAGE}} }}}</nowiki></code>
: The use of <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> also makes '''en''' the default language.
:* Unfortunately <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> always returns "en", making it useless. We still need the '''lang''' parameter. The trick with double evaluation of the parameter still works, so we can write:
:: <code><nowiki>;{{{word|{{{1}}} }}}:{{{ {{{lang}}} }}}</nowiki></code>

* The current version outputs <code><nowiki>{{{en}}}</nowiki></code> if no '''default''' or language code parameter was given. Also produces <code><nowiki>'''{{{word}}}'''</nowiki></code> if no '''word''' parameter was given.
:This is probably actually a good thing, because it shows when there is an error and the template call should be edited to resolve this.
: '''documentation''': add to the docs what parameters should be given and what happens if one is missing.

* There should be a parameter to give the expansion of an abbreviation, separate from the translations. For example <code><nowiki>{{dict|A.D.|full=Anno Domini"|en=in the year of our lord|nl=in het jaar van de Heer}}</nowiki></code>. The wiki format to be produced needs to be invented. Possibly as extra text in parentheses added to the lemma, e.g.
:;A.D. (Anno Domini):in the year of our lord
:Or on the description line:
:;A.D.:'''Anno Domini''': in the year of our lord
: By putting the formatting in the template we can ensure that it is universal accross all pages.
:* This addition is very useful, and helps to show lemmas which only had an expansion (as the '''default''' value), but no language-specific descriptions.

=== Behaviour for missing description text ===
If there is no descriptive text parameter for the language of the page, then by default the template will show the lemma, but with an empty description.

This might be annoying for translations with relatively few translated descriptions (e.g. for brand new translated pages). The reader will be looking at a long list of lemmas with only a few descriptions.

A possible solution is the introduction of a '''show''' parameter, which will determine what will happen if the lemma has is no descriptive text for the current language. Possible values:
;quiet:Show nothing. Pages will only show the lemmas which have a description in the page's language.
;blank:The default. Show the lemma with a blank description.
;a language code:Substitute the description with the given language. (Complicated implementation; maybe wait if there is demand for it.)
If the parameter is not set then do the '''blank''' behaviour.

For this parameter to work, we need to set up a new cascade of parameter passing.
Then this parameter can be set on the main page for a language, e.g. initially '''quiet''' or '''nl''', later to be removed as the descriptions start to become more common.

== Restructuring the template cascade ==

The subdivision into templates for each letter of the alphabet is a pain in the <donkey>, and actually unnecessary.
We describe how it is structured currently (Feb 2006), and draw up a plan for a simpler structure.

=== The two paths to this template: why? ===
Find out why there are two paths to this template:
# Through [[Template:Latindict]] and [[Template:Latindict/A]] (and the other letters).
# Via non-template "Latin words and expressions/''letter''" pages.
This also happens for the Dutch translated pages, so we get
Latin words and expressions/nl/A
Latin words and expressions/nl/B
etc.
and also
Nl:Latijnse woorden en uitdrukkingen/A
Nl:Latijnse woorden en uitdrukkingen/A
etc.

At first the suspect in this was the French translation, which uses a translated French page for each letter page.

Looking at the page history of the pages involved to see what happened, it turns out these pages were created around the same time and by the same author as the templates. They might be a remnant of an earlier setup. Examination of the exact creation dates and time may shed more light.

While this is going on, the use of <kbd>Template:languages</kbd> and <kbd>Template:Dict/Glossary</kbd> on all these pages creates a tangled web of pages being linked to by other pages. For example
Nl:Latijnse woorden en uitdukkingen/A
is linked to by:
* The main Dutch page
* Itself
* The non-redirected version of itself
* The main French page
* Every other <kbd>Nl:Latijnse woorden en uitdukkingen/''letter''</kbd> page

=== The Reason ===
All these subpages were created in a desperate bid by the original author to split the list into separate pages, allowing an editor to edit the list only a letter-section at the time, rather than having to edit the entire list of thousands of lemmas.

Because the actual content of the article is transcluded, the normal "edit by section" mechanism does not work.

This problem is not trivial to solve. Idealy [https://www.mediawiki.org/ mediawiki] should have a built-in mechanism to redirect an action to edit a section to edit the section in the transcluded page.
: '''Find out''' if such a mechanism exists

The documentation on this subject is shockingly poor. We must find out through experimentation.

[[User:DomoViridi/Temsects|It turns out]] that the '''current Wiki''' implements this '''exactly as expected'''.
* Put the sections in a transcluded file
* Transclude that file in the main file
* Put a ToC in either the main file or the transcluded file (both work), with simple <code><nowiki>[[#A|A]]</nowiki></code> links
* The ToC links will show you the section on the main page
* The auto-generated edit links will open the transcluded file on that section
* It also works with [[User:DomoViridi/Temsects/nl|translated pages]]

=== Current structure ===

==== The main page [[Latin_words_and_expressions]] ====
This contains
* A warning box about the mixing of English and Dutch descriptions.
* A code to suppress the Table of Contents.
* A call to <kbd>Template:Languages</kbd>, to make automatic links to the translated pages.
* An introductory text.
* A call to <kbd>Template:Dict/Glossary</kbd>, passing the name of the page as a parameter. This generates a substitute Table of Contents, linking to all the letter sections which will be generated on this page. '''Note:''' instead of passing a literal copy of the name of the page, the code <code><nowiki>{{BASEPAGENAME}}</nowiki></code> should have been used by the template.
* A call to <kbd>Template:Latindict, with the language code as a parameter (<nowiki>{{latindict|en}}</nowiki>). The language code is not needed, as <kbd>Template:Dict</kbd> should have used the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word.
* A comment with instructions on where to edit lemmas.
* A Category link <code><nowiki>[[Category:Genealogy|L]]</nowiki></code>.

Translated pages such as [[Latin_words_and_expressions/nl]] (or the page they redirect to) contain the same, with adaptations.
* The introductory text is translated.
* The parameter passed to <kbd>Template:Dict/Glossary</kbd> changed to the translated page name. (Using <code><nowiki>{{BASEPAGENAME}}</nowiki></code> would have prevented this, but that issue is moot in the new structure.)
* The parameter passed to <kbd>Template:Latindict</kbd> is changed to the code for the translated language. (Again, this could have been automated using <code><nowiki>{{PAGELANGUAGE}}</nowiki></code>. Again, issue is moot in the new structure.)
* The instructions in the comment are translated.
* The Category link is translated: <code><nowiki>[[Category:Nl:Genealogie|Latijnse woorden]]</nowiki></code>.

==== Template:Latindict ====
This contains
* A list of sections, one for each letter of the alphabet, and one for the 'at' symbol (<kbd>@</kbd>), with a Level 2 header with that letter.
* In each letter section, a call to a sub-template for that letter (<code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> etc.). The language code (passed into <kbd>Template:Latindict</kbd> as the first parameter), is passed on as the first parameter to the sub-template.
* Nothing else.

==== Template:Latindict/A etc. ====
These contain
* the actual lemmas, in the form of a <kbd>Template:Dict</kbd> entry for each lemma:
<nowiki>{{dict|lang ={{{1}}} |word=abavia|default=betovergrootmoeder |en=second great grandmother}}</nowiki>
* A link (now dead) to the Dutch/Flemish source material, as a <kbd>noinclude</kbd> so it won't show up on the page, but ''is'' visible in the source. This could have been done with an HTML comment.
''(Note: the English description in the example should be 'great-great-grandmother'.)''

The parameters to <kbd>Template:Dict</kbd> are filled in as follows:
;lang:The language code was passed in as the first parameter, and is now copied into this parameter: <kbd><nowiki>lang={{{1}}}</nowiki></kbd>.
;word:Set to the Latin lemma.
;default:Set to the Dutch description (which is wrong, this should be changed to the '''nl''' parameter everywhere; this is the main cause of the English/Dutch mixing of the descriptions).
;en, nl, fr, etc:Descriptions in other languages are given as a parameter named after their language code. Texts for other languages can be added here, e.g. <kbd>fr=Arrière-arrière-grand-mère</kbd>.

==== Template:Dict ====
This finally generates a display list entry based on the parameters.

The template turns the parameters into a display list entry, with the format
<nowiki>;'''word''':description</nowiki>
(The lemma word does not need to be explicitly made bold, the description list format already does that.)
This results in
;word:description

=== New structure ===

==== The main page (and the translations) ====
* The warning box about the error will probably be gone by this time.
* The code to suppress the Table of Contents remains.
* The call to <kbd>Template:Languages</kbd> can remain unchanged.
* The introductory text can probably remain unchanged.
* The call to <kbd>Template:Dict/Glossary</kbd> must be removed.
* The call <kbd><nowiki>{{Latindict}}</nowiki></kbd> must remain unchanged, with the language of the page as the first parameter (because the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word does not work on this wiki).
* The comment with instructions must be updated to reflect the new situation, i.e. find the lemma in <kbd>Template:Latindict</kbd> and edit it there.

The translated page pages must do the same changes:
* Remove the call to <kbd>Template:Dict/Glossary</kbd>.
* Update the translation of the instructions.

The result will be that:
* The homebrew ToC entries will jump to that letter on the main page.
* The "Edit" link on each section will open an edit on the section '''in the template''', allowing direct editing of lemmas.

==== Template:Latindict ====
Change to contain:
* A Table-of-Contents header with in-page links to all the letters. This replaces the <kbd>Template:Dict/Glossary</kbd> call from the main page. If the user clicks on one of these links, the view should jump to that letter header on the same page. This helps the user find a lemma more quickly.
: There will only be one call for this, so there is no need for a template. A simple set of <code><nowiki>[[#A|A]] - [[#B|B]] -[[#C|C]] - [[#D|D]] - ...</nowiki></code> with a table around it should do the trick. Copy from the template contents and search/replace <code><nowiki>{{{1}}</nowiki>}/</code> with <code>#</code>. Note that this moves this fuctionality from the main page (and the translated pages) to this template (with only one occurence), useful in all translations of the main page.
* Sections for each letter (unchanged). Simple <code>== A ==</code> headers are enough.
* In each section replace the <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> with all the <code><nowiki>{{dict|...}}</nowiki></code> entries for that letter. These can be substituted in by changing <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> to <code><nowiki>{{subst:Latindict/A|{{{1}}}}}</nowiki></code> and saving the page. Repeat for all the letters.

If all goes as expected, the ToC links will bring you to the section on the main page, and the auto-generated edit links will open this template for editing on the chosen section.

By allowing editing-by-section, users will not be overburdened by edit pages which are too big. As a major advantage, it will be much easier for editors to find the lemma they want to edit, without the need to search for the correct lettered subpage.

==== Template:Latindict/A etc. ====
These can all be eliminated.

==== Template:Dict ====
This must be overhauled.
* Eliminate the '''lang''' parameter. Take the language from the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word. On this wiki this will always have a valid value.
** Unfortunately, <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> always produces "en" on this wiki. So we still need the '''lang''' parameter
* Eliminate the '''default''' parameter.
** Or better: Allow '''default''' as an alternative for '''nl'''. This gives backward compatiblilty with the existing calls to this template.
* Other improvements are described in the [[#Improvements to Dict template]] section

=== Pages no longer needed ===
With this new structure the following pages can be eliminated:
* All the lettered sub-templates (<kbd>Template:Latindict/A</kbd> etc.).
* All the <kbd>Main:</kbd> space lettered sub-pages (<kbd>Latin words and expressions/A</kbd> etc.).
* All the Dutch translated main space lettered sub-pages (<kbd>Latin words and expressions/A/nl</kbd> etc.), and the pages they redirect to (<kbd>Nl:Latijnse woorden en expressies/A</kbd> etc.).
* Same for the French translated pages. Although we will have to copy the descriptions from the French pages into the <kbd>Template:Dict</kbd> calls as <kbd>fr=</kbd> parameters first.
* Status of the Hebrew translated pages needs to be examined.

== Actions to take for modification ==

=== Set up a test environment ===
Set up a test environment to create and test a better version of the template without disturbing the existing one.
* (done) Create a Sandbox subspace to my user page: <kbd>User:DomoViridi/TempTest</kbd>; Think about the use or no-use of capital letters in the names of the pages first (doesn't realy matter). Put my own version of the pages there, but in the <kbd>User:DomoViridi/TempTest</kbd> space. Test templates can be called with the syntax <code><nowiki>{{User:DomoViridi/TempTest/mytemplate}}</nowiki></code> (the braces ensure transclusion, the <kbd>User:</kbd> namespace replaces the default <kbd>Template:</kbd> namespace.
* (done) Create a template page with the test template, [[User:DomoViridi/TempTest/Dict]]. Fill it initially with a copy of the original <kbd>Template:Dict</kbd>.
* (done) Create a page with test cases, [[User:DomoViridi/TempTest/Testcases]]. Put some calls to our Dict template in it, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus| en=silly sod| nl=sukkel}}</nowiki></code>. Add many testcases and put their source code in nowiki text above each.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict/A]] with calls to the Dict template, using <code><nowiki>{{User:DomoViridi/TempTest/Dict}}</nowiki></code>. Copy the existing "A" page and shorten it, leaving some useful examples, with different languages, some abbreviations, and some missing languages. Add French translations to some of the lemmas. Also copy a different letter page (a short one), which has some translations.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict]] which calls our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space.
* (done) Create a main page [[User:DomoViridi/TempTest/Latin words and expressions]], which calls <code><nowiki>{{User:DomoViridi/TempTest/Latindict}}</nowiki></code>.
: '''Oh hey!''', it turns out <kbd>Template:Dict/Glossary</kbd> creates links to [[Latin words and expressions/A]] and all the other letters.
* (done) Create lettered pages [[User:DomoViridi/TempTest/Latin words and expressions/A]] for each of the pages for wich we have a template, and fill them with a copy of the originals. which call our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space. Note that this is all duplicate work.
* (done) Create a translated page [[User:DomoViridi/TempTest/Latin words and expressions/nl]], fill it with the contents of [[Nl:Latijnse woorden en expressies]]. Change the calls to point to the sandbox, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Latindict | nl}}</nowiki></code> (passing the language to the template).
: '''Oh hey!''', once again we see how the clumsy <kbd>Template:Dict/Glossary</kbd> requires subpages of the translated page, one for each letter of the alphabet.
* (done) Create the translated subpages before moving the translated main page.
: Although: this does not help, because the letter pages are not subpages of the <kbd>.../nl</kbd> page, but are formed with <kbd>.../A/nl</kbd>.
* (done) Move the translated page to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies]]. This will automatically create a redirect from the <kbd>/nl</kbd> page to this page.
* (done) Move all the frakking translated subpages to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies/A]], again auto-generating a redirect.

Creating 27 (one for each letter of the alphabet, plus '@') lettered subpages each time for:
* The Templates
* The main page (English)
* The Dutch (nl) translation
* The redirect for the Dutch (nl) translation
* The French (fr) translation
* The redirect for the French (fr) translation
* The Hebrew (he) translation
* The redirect Hebrew (he) translation
* The same again for every new translation
is an unbelievable pile of unnecessary busywork. All so that we can have separate pages for every letter, and links to them.
Good thing I only did letters A and B for this sandbox.

''Note: the Gramps wiki does not support the [https://www.mediawiki.org/wiki/Extension:TemplateSandbox TemplateSandbox extension], which would have allowed to attach a sandbox subpage directly to the template. This means the <code><nowiki>{{testcases notice}}</nowiki></code> template is also not available.''

=== Create an improved Dict template ===
Do this in the sandbox. See the [[#Improvements to Dict template]] section.

Don't forget to adjust the documentation.

When it works with no detected problems, overwrite the actual template with our code.

=== Change "default" to "nl" ===
Because <kbd>Template:Dict</kbd> defaults to <nowiki>{{{en}}}</nowiki> if there is no description in a valid language, changing '''default''' to '''nl''' will result in a lot of bad output for all entries where '''en''' is missing.

This means we need to modify <kbd>Template:Dict</kbd> before we make this change.

Edit all the <kbd>Template:Latindict/<letter></kbd> pages to change '''default=''' to '''nl='''.
The effect should be that Dutch descriptions only show on the Dutch pages.
* Start with a small page and see how it goes.
* Then do a few more with export-to-editor, bulk search/replace, import from editor. Check for anomalies.
* Do the other pages

This should all have effect without the need to change the templates yet. It also makes room for a modification of <kbd>Template:Dict</kbd> which drops the '''default''' parameter.

=== Restructure the template cascade ===
Do this in the sandbox. See [[#Restructuring the template cascade]].
Make sure it works perfectly.

Before modifying the real pages, put notices in the talk pages and banners in any and all of the pages involved.

Then modify the real pages.

Try to get the useless pages deleted. At the least put a warning box in them. Something like "Do not use this page. Use page xxx instead. This page will be deleted in the near future".

=== Move the translated French pages ===
Copy all the existing French translations to the <kbd>Template:Latindict/<letter></kbd> pages.
Note: This leaves the translated French pages unchanged for now.
* Could be a big job.
* Have these pages changed much in the last few years?
* Put a notice on the Talk page for the French translation to tell them what is going on.
* Maybe put a banner on the pages too.
* Make sure they work nicely.

Switch the translated French page to use Template:Latindict
* One edit to [[Fr:Mots et expressions en latin]] should be enough.
* Add a notice to the French page about the change

=== Check the Hebrew pages ===
Check what the Hebrew pages look like now that we changed '''default=''' to '''nl='''.

=== Remove unneeded pages ===
Remove all the unneeded letter pages and letter templates, for each language that uses them.

=== Possible 'silent' mode ===
We may want to add a "silent" mode, where lemmas are not shown if there is no description for that language. This will avoid long pages of untranslated Latin words and expressions, and emphasise the lemmas that have been translated.

This will require an extra parameter, which must be passed down through all the templates. This named parameter should be given with a value, so that it evaluates to "take the then case" for the parser function:
<nowiki>{{#if:{{{silent|}}} | do silent version | do not-silent version}}</nowiki>
That means the parameter should be set as <kbd>"silent=<something>"</kbd>, with an arbitrary, non-empty value. See [https://www.mediawiki.org/wiki/Help:Parser_functions_in_templates Parser functions in templates]
* On page [[Latin words and expressions/fr]]: call template <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd> for silent and <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd> for not-silent.
* [[Template:Latindict]]: call <kbd><nowiki>{{Latindict/A|{{{1}}}|silent={{{silent|}}}}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* [[Template:Latindict/A]]: call <kbd><nowiki>{{Dict|lang={{{1}}}|silent={{{silent|}}}|word=...}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* Inside [[Template:Dict]] use <kbd><nowiki>{{#if: {{{silent|}}} | do silent stuff | do non-silent stuff}}</nowiki></kbd> (again with a bar after the parameter).

The following table shows how the parameter values trickle down to the <kbd>#if</kbd> parser, with or without the extra bar (<kbd>|</kbd>). The conclusion is that the extra bar should be used thoughout, and the parameter should be omitted for non-silent mode and passed with a value (e.g. <kbd>silent=yes</kbd>) for silent mode. The string used for the value (in this example "yes") does not matter. Note that passing the parameter with an empty string as a value ("<kbd>silent=</kbd>") will set the result to non-silent.

''Note: the use of the variables <kbd>s1</kbd>, <kbd>s2</kbd> and <kbd>s3</kbd> is arbitrary, and is used here for clarity. They could all be called <kbd>silent</kbd>.''

{| class="wikitable" style="margin:auto" width="90%"
|+ Passing on the silent parameter
! Main page
! <kbd>Latindict</kbd>
! <kbd>Latindict/A</kbd>
! <kbd>Dict</kbd>
! <kbd>#if</kbd>
|-
! style="text-align:right" | without bar
! <kbd><nowiki>s1={{{silent}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| then
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
! style="text-align:right" | with bar
! <kbd><nowiki>s1={{{silent|}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
|}

In the end, all the entries in [[Template:Latindict]] need to be modified, as must all calls to [[Template:Dict]] in all the letter templates ([[Template:Latindict/A]] etc.). And finally [[Template:Dict]] needs to implement the silent mode.

== Copyright ==
The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

User:DomoViridi/TempTest

2026-03-12T08:37:13Z

DomoViridi: /* Improvements to Dict template */ With "lang" we can still use double expansion

The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

== Sandbox to test templates ==

For [[Template:Latindict]], [[Template:Latindict/A]] (and all the other letter-subpages), [[Template:Dict/Glossary]], [[Template:Dict]], as used in [[Latin words and expressions]], and the translations [[Latin words and expressions/nl]], [[Latin words and expressions/fr]] and [[Latin words and expressions/he]].

== Improvements to Dict template ==

* The '''default''' parameter does not make sense, and should be eliminated. If there is no descriptive text for a given language, then the wiki page should show a blank line (or nothing).
: Before removing it, in all uses of this template '''default=''' should be replaced with '''nl='''. This is also the solution to the problem of showing lots of Dutch language descriptions on the English pages.
:* Better yet: first make '''default''' an alternative to '''nl'''. That way, the existing calls to this template can remain unchanged, while also only showing the Dutch description (given in '''default''') if '''lang''' is "nl".

* The '''lang''' parameter is exclusively used as <code><nowiki>{{dict|lang ={{{1}}} |word=...</nowiki></code>, i.e. the value is read from the first unnamed parameter that was passed to <kbd>Template:Latindict/A</kbd>. This value cascades down from the main page.
: This cascade might be unnecessary, because the template should be able to use the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word. Entries can then be simplified to <code><nowiki>{{dict|word=...</nowiki></code>. For the use in special cases '''lang=''' could be left available to override the wiki language setting for a particular lemma.
:* Unfortunately <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> always returns "en" on this wiki, even on .../nl and Nl:... pages.

* The '''word''' named parameter should be optional, and the word should be allowed to be passed as the first anonymous parameter, so we can write <code><nowiki>{{dict| abiit| en=he/she has left | nl=hij/zij is vertrokken }}</nowiki></code>.
: Disadvantage: That would make the lemma an unnamed parameter. Unnamed parameters are not stripped of leading and trailing spaces. This can lead to lemmas with extra spaces around them.
: Although: because it is the term in a definition list, leading spaces are ignored, and trailing spaces do not affect the layout (the displayed wiki text goes to a new line after the term), or are maybe also ignored.
:* Beware: Though spaces have little effect, a value for an unnamed parameter should never be the last thing on a line, because then the newline following the parameter will become part of the parameter value. In this template that messes up the description-list-item format.
:* This might also be true for a newline ''before'' an unnamed parameter.
: Can be implemented with <code><nowiki>{{{word|{{{1}}} }}}</nowiki></code> in the template. This accepts the first anonymous parameter, except when a '''word''' parameter was given when calling the template. This gives backward compatibility, where it is ''allowed'' to use the '''word''' parameter, but not ''mandatory''.

* Make it so that <kbd>Template:Dict</kbd> does not need an explicit list of language codes. The current list blocks additional translations from being added.
: The value of the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word can be used to create the name of the desired parameter, e.g. "en". See [https://www.mediawiki.org/wiki/Manual:Advanced_templates#Variable_parameter_name Mediawiki Advanced Templates Help: Variable parameter name].
:Code: <code><nowiki>;{{{word|{{{1}}} }}}:{{{ {{PAGELANGUAGE}} }}}</nowiki></code>
: The use of <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> also makes '''en''' the default language.
:* Unfortunately <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> always returns "en", making it useless. We still need the '''lang''' parameter. The trick with double evaluation of the parameter still works, so we can write:
:: <code><nowiki>;{{{word|{{{1}}} }}}:{{{ {{{lang}}} }}}</nowiki></code>

* The current version outputs <code><nowiki>{{{en}}}</nowiki></code> if no '''default''' or language code parameter was given. Also produces <code><nowiki>'''{{{word}}}'''</nowiki></code> if no '''word''' parameter was given.
:This is probably actually a good thing, because it shows when there is an error and the template call should be edited to resolve this.
: '''documentation''': add to the docs what parameters should be given and what happens if one is missing.

* There should be a parameter to give the expansion of an abbreviation, separate from the translations. For example <code><nowiki>{{dict|A.D.|full=Anno Domini"|en=in the year of our lord|nl=in het jaar van de Heer}}</nowiki></code>. The wiki format to be produced needs to be invented. Possibly as extra text in parentheses added to the lemma, e.g.
:;A.D. (Anno Domini):in the year of our lord
:Or on the description line:
:;A.D.:'''Anno Domini''': in the year of our lord
: By putting the formatting in the template we can ensure that it is universal accross all pages.

=== Behaviour for missing description text ===
If there is no descriptive text parameter for the language of the page, then by default the template will show the lemma, but with an empty description.

This might be annoying for translations with relatively few translated descriptions (e.g. for brand new translated pages). The reader will be looking at a long list of lemmas with only a few descriptions.

A possible solution is the introduction of a '''show''' parameter, which will determine what will happen if the lemma has is no descriptive text for the current language. Possible values:
;quiet:Show nothing. Pages will only show the lemmas which have a description in the page's language.
;blank:The default. Show the lemma with a blank description.
;a language code:Substitute the description with the given language. (Complicated implementation; maybe wait if there is demand for it.)
If the parameter is not set then do the '''blank''' behaviour.

For this parameter to work, we need to set up a new cascade of parameter passing.
Then this parameter can be set on the main page for a language, e.g. initially '''quiet''' or '''nl''', later to be removed as the descriptions start to become more common.

== Restructuring the template cascade ==

The subdivision into templates for each letter of the alphabet is a pain in the <donkey>, and actually unnecessary.
We describe how it is structured currently (Feb 2006), and draw up a plan for a simpler structure.

=== The two paths to this template: why? ===
Find out why there are two paths to this template:
# Through [[Template:Latindict]] and [[Template:Latindict/A]] (and the other letters).
# Via non-template "Latin words and expressions/''letter''" pages.
This also happens for the Dutch translated pages, so we get
Latin words and expressions/nl/A
Latin words and expressions/nl/B
etc.
and also
Nl:Latijnse woorden en uitdrukkingen/A
Nl:Latijnse woorden en uitdrukkingen/A
etc.

At first the suspect in this was the French translation, which uses a translated French page for each letter page.

Looking at the page history of the pages involved to see what happened, it turns out these pages were created around the same time and by the same author as the templates. They might be a remnant of an earlier setup. Examination of the exact creation dates and time may shed more light.

While this is going on, the use of <kbd>Template:languages</kbd> and <kbd>Template:Dict/Glossary</kbd> on all these pages creates a tangled web of pages being linked to by other pages. For example
Nl:Latijnse woorden en uitdukkingen/A
is linked to by:
* The main Dutch page
* Itself
* The non-redirected version of itself
* The main French page
* Every other <kbd>Nl:Latijnse woorden en uitdukkingen/''letter''</kbd> page

=== The Reason ===
All these subpages were created in a desperate bid by the original author to split the list into separate pages, allowing an editor to edit the list only a letter-section at the time, rather than having to edit the entire list of thousands of lemmas.

Because the actual content of the article is transcluded, the normal "edit by section" mechanism does not work.

This problem is not trivial to solve. Idealy [https://www.mediawiki.org/ mediawiki] should have a built-in mechanism to redirect an action to edit a section to edit the section in the transcluded page.
: '''Find out''' if such a mechanism exists

The documentation on this subject is shockingly poor. We must find out through experimentation.

[[User:DomoViridi/Temsects|It turns out]] that the '''current Wiki''' implements this '''exactly as expected'''.
* Put the sections in a transcluded file
* Transclude that file in the main file
* Put a ToC in either the main file or the transcluded file (both work), with simple <code><nowiki>[[#A|A]]</nowiki></code> links
* The ToC links will show you the section on the main page
* The auto-generated edit links will open the transcluded file on that section
* It also works with [[User:DomoViridi/Temsects/nl|translated pages]]

=== Current structure ===

==== The main page [[Latin_words_and_expressions]] ====
This contains
* A warning box about the mixing of English and Dutch descriptions.
* A code to suppress the Table of Contents.
* A call to <kbd>Template:Languages</kbd>, to make automatic links to the translated pages.
* An introductory text.
* A call to <kbd>Template:Dict/Glossary</kbd>, passing the name of the page as a parameter. This generates a substitute Table of Contents, linking to all the letter sections which will be generated on this page. '''Note:''' instead of passing a literal copy of the name of the page, the code <code><nowiki>{{BASEPAGENAME}}</nowiki></code> should have been used by the template.
* A call to <kbd>Template:Latindict, with the language code as a parameter (<nowiki>{{latindict|en}}</nowiki>). The language code is not needed, as <kbd>Template:Dict</kbd> should have used the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word.
* A comment with instructions on where to edit lemmas.
* A Category link <code><nowiki>[[Category:Genealogy|L]]</nowiki></code>.

Translated pages such as [[Latin_words_and_expressions/nl]] (or the page they redirect to) contain the same, with adaptations.
* The introductory text is translated.
* The parameter passed to <kbd>Template:Dict/Glossary</kbd> changed to the translated page name. (Using <code><nowiki>{{BASEPAGENAME}}</nowiki></code> would have prevented this, but that issue is moot in the new structure.)
* The parameter passed to <kbd>Template:Latindict</kbd> is changed to the code for the translated language. (Again, this could have been automated using <code><nowiki>{{PAGELANGUAGE}}</nowiki></code>. Again, issue is moot in the new structure.)
* The instructions in the comment are translated.
* The Category link is translated: <code><nowiki>[[Category:Nl:Genealogie|Latijnse woorden]]</nowiki></code>.

==== Template:Latindict ====
This contains
* A list of sections, one for each letter of the alphabet, and one for the 'at' symbol (<kbd>@</kbd>), with a Level 2 header with that letter.
* In each letter section, a call to a sub-template for that letter (<code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> etc.). The language code (passed into <kbd>Template:Latindict</kbd> as the first parameter), is passed on as the first parameter to the sub-template.
* Nothing else.

==== Template:Latindict/A etc. ====
These contain
* the actual lemmas, in the form of a <kbd>Template:Dict</kbd> entry for each lemma:
<nowiki>{{dict|lang ={{{1}}} |word=abavia|default=betovergrootmoeder |en=second great grandmother}}</nowiki>
* A link (now dead) to the Dutch/Flemish source material, as a <kbd>noinclude</kbd> so it won't show up on the page, but ''is'' visible in the source. This could have been done with an HTML comment.
''(Note: the English description in the example should be 'great-great-grandmother'.)''

The parameters to <kbd>Template:Dict</kbd> are filled in as follows:
;lang:The language code was passed in as the first parameter, and is now copied into this parameter: <kbd><nowiki>lang={{{1}}}</nowiki></kbd>.
;word:Set to the Latin lemma.
;default:Set to the Dutch description (which is wrong, this should be changed to the '''nl''' parameter everywhere; this is the main cause of the English/Dutch mixing of the descriptions).
;en, nl, fr, etc:Descriptions in other languages are given as a parameter named after their language code. Texts for other languages can be added here, e.g. <kbd>fr=Arrière-arrière-grand-mère</kbd>.

==== Template:Dict ====
This finally generates a display list entry based on the parameters.

The template turns the parameters into a display list entry, with the format
<nowiki>;'''word''':description</nowiki>
(The lemma word does not need to be explicitly made bold, the description list format already does that.)
This results in
;word:description

=== New structure ===

==== The main page (and the translations) ====
* The warning box about the error will probably be gone by this time.
* The code to suppress the Table of Contents remains.
* The call to <kbd>Template:Languages</kbd> can remain unchanged.
* The introductory text can probably remain unchanged.
* The call to <kbd>Template:Dict/Glossary</kbd> must be removed.
* The call <kbd><nowiki>{{Latindict}}</nowiki></kbd> must remain unchanged, with the language of the page as the first parameter (because the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word does not work on this wiki).
* The comment with instructions must be updated to reflect the new situation, i.e. find the lemma in <kbd>Template:Latindict</kbd> and edit it there.

The translated page pages must do the same changes:
* Remove the call to <kbd>Template:Dict/Glossary</kbd>.
* Update the translation of the instructions.

The result will be that:
* The homebrew ToC entries will jump to that letter on the main page.
* The "Edit" link on each section will open an edit on the section '''in the template''', allowing direct editing of lemmas.

==== Template:Latindict ====
Change to contain:
* A Table-of-Contents header with in-page links to all the letters. This replaces the <kbd>Template:Dict/Glossary</kbd> call from the main page. If the user clicks on one of these links, the view should jump to that letter header on the same page. This helps the user find a lemma more quickly.
: There will only be one call for this, so there is no need for a template. A simple set of <code><nowiki>[[#A|A]] - [[#B|B]] -[[#C|C]] - [[#D|D]] - ...</nowiki></code> with a table around it should do the trick. Copy from the template contents and search/replace <code><nowiki>{{{1}}</nowiki>}/</code> with <code>#</code>. Note that this moves this fuctionality from the main page (and the translated pages) to this template (with only one occurence), useful in all translations of the main page.
* Sections for each letter (unchanged). Simple <code>== A ==</code> headers are enough.
* In each section replace the <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> with all the <code><nowiki>{{dict|...}}</nowiki></code> entries for that letter. These can be substituted in by changing <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> to <code><nowiki>{{subst:Latindict/A|{{{1}}}}}</nowiki></code> and saving the page. Repeat for all the letters.

If all goes as expected, the ToC links will bring you to the section on the main page, and the auto-generated edit links will open this template for editing on the chosen section.

By allowing editing-by-section, users will not be overburdened by edit pages which are too big. As a major advantage, it will be much easier for editors to find the lemma they want to edit, without the need to search for the correct lettered subpage.

==== Template:Latindict/A etc. ====
These can all be eliminated.

==== Template:Dict ====
This must be overhauled.
* Eliminate the '''lang''' parameter. Take the language from the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word. On this wiki this will always have a valid value.
** Unfortunately, <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> always produces "en" on this wiki. So we still need the '''lang''' parameter
* Eliminate the '''default''' parameter.
** Or better: Allow '''default''' as an alternative for '''nl'''. This gives backward compatiblilty with the existing calls to this template.
* Other improvements are described in the [[#Improvements to Dict template]] section

=== Pages no longer needed ===
With this new structure the following pages can be eliminated:
* All the lettered sub-templates (<kbd>Template:Latindict/A</kbd> etc.).
* All the <kbd>Main:</kbd> space lettered sub-pages (<kbd>Latin words and expressions/A</kbd> etc.).
* All the Dutch translated main space lettered sub-pages (<kbd>Latin words and expressions/A/nl</kbd> etc.), and the pages they redirect to (<kbd>Nl:Latijnse woorden en expressies/A</kbd> etc.).
* Same for the French translated pages. Although we will have to copy the descriptions from the French pages into the <kbd>Template:Dict</kbd> calls as <kbd>fr=</kbd> parameters first.
* Status of the Hebrew translated pages needs to be examined.

== Actions to take for modification ==

=== Set up a test environment ===
Set up a test environment to create and test a better version of the template without disturbing the existing one.
* (done) Create a Sandbox subspace to my user page: <kbd>User:DomoViridi/TempTest</kbd>; Think about the use or no-use of capital letters in the names of the pages first (doesn't realy matter). Put my own version of the pages there, but in the <kbd>User:DomoViridi/TempTest</kbd> space. Test templates can be called with the syntax <code><nowiki>{{User:DomoViridi/TempTest/mytemplate}}</nowiki></code> (the braces ensure transclusion, the <kbd>User:</kbd> namespace replaces the default <kbd>Template:</kbd> namespace.
* (done) Create a template page with the test template, [[User:DomoViridi/TempTest/Dict]]. Fill it initially with a copy of the original <kbd>Template:Dict</kbd>.
* (done) Create a page with test cases, [[User:DomoViridi/TempTest/Testcases]]. Put some calls to our Dict template in it, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus| en=silly sod| nl=sukkel}}</nowiki></code>. Add many testcases and put their source code in nowiki text above each.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict/A]] with calls to the Dict template, using <code><nowiki>{{User:DomoViridi/TempTest/Dict}}</nowiki></code>. Copy the existing "A" page and shorten it, leaving some useful examples, with different languages, some abbreviations, and some missing languages. Add French translations to some of the lemmas. Also copy a different letter page (a short one), which has some translations.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict]] which calls our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space.
* (done) Create a main page [[User:DomoViridi/TempTest/Latin words and expressions]], which calls <code><nowiki>{{User:DomoViridi/TempTest/Latindict}}</nowiki></code>.
: '''Oh hey!''', it turns out <kbd>Template:Dict/Glossary</kbd> creates links to [[Latin words and expressions/A]] and all the other letters.
* (done) Create lettered pages [[User:DomoViridi/TempTest/Latin words and expressions/A]] for each of the pages for wich we have a template, and fill them with a copy of the originals. which call our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space. Note that this is all duplicate work.
* (done) Create a translated page [[User:DomoViridi/TempTest/Latin words and expressions/nl]], fill it with the contents of [[Nl:Latijnse woorden en expressies]]. Change the calls to point to the sandbox, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Latindict | nl}}</nowiki></code> (passing the language to the template).
: '''Oh hey!''', once again we see how the clumsy <kbd>Template:Dict/Glossary</kbd> requires subpages of the translated page, one for each letter of the alphabet.
* (done) Create the translated subpages before moving the translated main page.
: Although: this does not help, because the letter pages are not subpages of the <kbd>.../nl</kbd> page, but are formed with <kbd>.../A/nl</kbd>.
* (done) Move the translated page to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies]]. This will automatically create a redirect from the <kbd>/nl</kbd> page to this page.
* (done) Move all the frakking translated subpages to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies/A]], again auto-generating a redirect.

Creating 27 (one for each letter of the alphabet, plus '@') lettered subpages each time for:
* The Templates
* The main page (English)
* The Dutch (nl) translation
* The redirect for the Dutch (nl) translation
* The French (fr) translation
* The redirect for the French (fr) translation
* The Hebrew (he) translation
* The redirect Hebrew (he) translation
* The same again for every new translation
is an unbelievable pile of unnecessary busywork. All so that we can have separate pages for every letter, and links to them.
Good thing I only did letters A and B for this sandbox.

''Note: the Gramps wiki does not support the [https://www.mediawiki.org/wiki/Extension:TemplateSandbox TemplateSandbox extension], which would have allowed to attach a sandbox subpage directly to the template. This means the <code><nowiki>{{testcases notice}}</nowiki></code> template is also not available.''

=== Create an improved Dict template ===
Do this in the sandbox. See the [[#Improvements to Dict template]] section.

Don't forget to adjust the documentation.

When it works with no detected problems, overwrite the actual template with our code.

=== Change "default" to "nl" ===
Because <kbd>Template:Dict</kbd> defaults to <nowiki>{{{en}}}</nowiki> if there is no description in a valid language, changing '''default''' to '''nl''' will result in a lot of bad output for all entries where '''en''' is missing.

This means we need to modify <kbd>Template:Dict</kbd> before we make this change.

Edit all the <kbd>Template:Latindict/<letter></kbd> pages to change '''default=''' to '''nl='''.
The effect should be that Dutch descriptions only show on the Dutch pages.
* Start with a small page and see how it goes.
* Then do a few more with export-to-editor, bulk search/replace, import from editor. Check for anomalies.
* Do the other pages

This should all have effect without the need to change the templates yet. It also makes room for a modification of <kbd>Template:Dict</kbd> which drops the '''default''' parameter.

=== Restructure the template cascade ===
Do this in the sandbox. See [[#Restructuring the template cascade]].
Make sure it works perfectly.

Before modifying the real pages, put notices in the talk pages and banners in any and all of the pages involved.

Then modify the real pages.

Try to get the useless pages deleted. At the least put a warning box in them. Something like "Do not use this page. Use page xxx instead. This page will be deleted in the near future".

=== Move the translated French pages ===
Copy all the existing French translations to the <kbd>Template:Latindict/<letter></kbd> pages.
Note: This leaves the translated French pages unchanged for now.
* Could be a big job.
* Have these pages changed much in the last few years?
* Put a notice on the Talk page for the French translation to tell them what is going on.
* Maybe put a banner on the pages too.
* Make sure they work nicely.

Switch the translated French page to use Template:Latindict
* One edit to [[Fr:Mots et expressions en latin]] should be enough.
* Add a notice to the French page about the change

=== Check the Hebrew pages ===
Check what the Hebrew pages look like now that we changed '''default=''' to '''nl='''.

=== Remove unneeded pages ===
Remove all the unneeded letter pages and letter templates, for each language that uses them.

=== Possible 'silent' mode ===
We may want to add a "silent" mode, where lemmas are not shown if there is no description for that language. This will avoid long pages of untranslated Latin words and expressions, and emphasise the lemmas that have been translated.

This will require an extra parameter, which must be passed down through all the templates. This named parameter should be given with a value, so that it evaluates to "take the then case" for the parser function:
<nowiki>{{#if:{{{silent|}}} | do silent version | do not-silent version}}</nowiki>
That means the parameter should be set as <kbd>"silent=<something>"</kbd>, with an arbitrary, non-empty value. See [https://www.mediawiki.org/wiki/Help:Parser_functions_in_templates Parser functions in templates]
* On page [[Latin words and expressions/fr]]: call template <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd> for silent and <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd> for not-silent.
* [[Template:Latindict]]: call <kbd><nowiki>{{Latindict/A|{{{1}}}|silent={{{silent|}}}}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* [[Template:Latindict/A]]: call <kbd><nowiki>{{Dict|lang={{{1}}}|silent={{{silent|}}}|word=...}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* Inside [[Template:Dict]] use <kbd><nowiki>{{#if: {{{silent|}}} | do silent stuff | do non-silent stuff}}</nowiki></kbd> (again with a bar after the parameter).

The following table shows how the parameter values trickle down to the <kbd>#if</kbd> parser, with or without the extra bar (<kbd>|</kbd>). The conclusion is that the extra bar should be used thoughout, and the parameter should be omitted for non-silent mode and passed with a value (e.g. <kbd>silent=yes</kbd>) for silent mode. The string used for the value (in this example "yes") does not matter. Note that passing the parameter with an empty string as a value ("<kbd>silent=</kbd>") will set the result to non-silent.

''Note: the use of the variables <kbd>s1</kbd>, <kbd>s2</kbd> and <kbd>s3</kbd> is arbitrary, and is used here for clarity. They could all be called <kbd>silent</kbd>.''

{| class="wikitable" style="margin:auto" width="90%"
|+ Passing on the silent parameter
! Main page
! <kbd>Latindict</kbd>
! <kbd>Latindict/A</kbd>
! <kbd>Dict</kbd>
! <kbd>#if</kbd>
|-
! style="text-align:right" | without bar
! <kbd><nowiki>s1={{{silent}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| then
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
! style="text-align:right" | with bar
! <kbd><nowiki>s1={{{silent|}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
|}

In the end, all the entries in [[Template:Latindict]] need to be modified, as must all calls to [[Template:Dict]] in all the letter templates ([[Template:Latindict/A]] etc.). And finally [[Template:Dict]] needs to implement the silent mode.

== Copyright ==
The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

User:DomoViridi/TempTest

2026-03-11T21:09:03Z

DomoViridi: /* Improvements to Dict template */ Beware: no newline after unnamed parameter value

The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

== Sandbox to test templates ==

For [[Template:Latindict]], [[Template:Latindict/A]] (and all the other letter-subpages), [[Template:Dict/Glossary]], [[Template:Dict]], as used in [[Latin words and expressions]], and the translations [[Latin words and expressions/nl]], [[Latin words and expressions/fr]] and [[Latin words and expressions/he]].

== Improvements to Dict template ==

* The '''default''' parameter does not make sense, and should be eliminated. If there is no descriptive text for a given language, then the wiki page should show a blank line (or nothing).
: Before removing it, in all uses of this template '''default=''' should be replaced with '''nl='''. This is also the solution to the problem of showing lots of Dutch language descriptions on the English pages.
:* Better yet: first make '''default''' an alternative to '''nl'''. That way, the existing calls to this template can remain unchanged, while also only showing the Dutch description (given in '''default''') if '''lang''' is "nl".

* The '''lang''' parameter is exclusively used as <code><nowiki>{{dict|lang ={{{1}}} |word=...</nowiki></code>, i.e. the value is read from the first unnamed parameter that was passed to <kbd>Template:Latindict/A</kbd>. This value cascades down from the main page.
: This cascade might be unnecessary, because the template should be able to use the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word. Entries can then be simplified to <code><nowiki>{{dict|word=...</nowiki></code>. For the use in special cases '''lang=''' could be left available to override the wiki language setting for a particular lemma.
:* Unfortunately <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> always returns "en" on this wiki, even on .../nl and Nl:... pages.

* The '''word''' named parameter should be optional, and the word should be allowed to be passed as the first anonymous parameter, so we can write <code><nowiki>{{dict| abiit| en=he/she has left | nl=hij/zij is vertrokken }}</nowiki></code>.
: Disadvantage: That would make the lemma an unnamed parameter. Unnamed parameters are not stripped of leading and trailing spaces. This can lead to lemmas with extra spaces around them.
: Although: because it is the term in a definition list, leading spaces are ignored, and trailing spaces do not affect the layout (the displayed wiki text goes to a new line after the term), or are maybe also ignored.
:* Beware: Though spaces have little effect, a value for an unnamed parameter should never be the last thing on a line, because then the newline following the parameter will become part of the parameter value. In this template that messes up the description-list-item format.
:* This might also be true for a newline ''before'' an unnamed parameter.
: Can be implemented with <code><nowiki>{{{word|{{{1}}} }}}</nowiki></code> in the template. This accepts the first anonymous parameter, except when a '''word''' parameter was given when calling the template. This gives backward compatibility, where it is ''allowed'' to use the '''word''' parameter, but not ''mandatory''.

* Make it so that <kbd>Template:Dict</kbd> does not need an explicit list of language codes. The current list blocks additional translations from being added.
: The value of the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word can be used to create the name of the desired parameter, e.g. "en". See [https://www.mediawiki.org/wiki/Manual:Advanced_templates#Variable_parameter_name Mediawiki Advanced Templates Help: Variable parameter name].
:Code: <code><nowiki>;{{{word|{{{1}}} }}}:{{{{{PAGELANGUAGE}}}}}</nowiki></code>
: The use of <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> also makes '''en''' the default language.

* The current version outputs <code><nowiki>{{{en}}}</nowiki></code> if no '''default''' or language code parameter was given. Also produces <code><nowiki>'''{{{word}}}'''</nowiki></code> if no '''word''' parameter was given.
:This is probably actually a good thing, because it shows when there is an error and the template call should be edited to resolve this.
: '''documentation''': add to the docs what parameters should be given and what happens if one is missing.

* There should be a parameter to give the expansion of an abbreviation, separate from the translations. For example <code><nowiki>{{dict|A.D.|full=Anno Domini"|en=in the year of our lord|nl=in het jaar van de Heer}}</nowiki></code>. The wiki format to be produced needs to be invented. Possibly as extra text in parentheses added to the lemma, e.g.
:;A.D. (Anno Domini):in the year of our lord
:Or on the description line:
:;A.D.:'''Anno Domini''': in the year of our lord
: By putting the formatting in the template we can ensure that it is universal accross all pages.

=== Behaviour for missing description text ===
If there is no descriptive text parameter for the language of the page, then by default the template will show the lemma, but with an empty description.

This might be annoying for translations with relatively few translated descriptions (e.g. for brand new translated pages). The reader will be looking at a long list of lemmas with only a few descriptions.

A possible solution is the introduction of a '''show''' parameter, which will determine what will happen if the lemma has is no descriptive text for the current language. Possible values:
;quiet:Show nothing. Pages will only show the lemmas which have a description in the page's language.
;blank:The default. Show the lemma with a blank description.
;a language code:Substitute the description with the given language. (Complicated implementation; maybe wait if there is demand for it.)
If the parameter is not set then do the '''blank''' behaviour.

For this parameter to work, we need to set up a new cascade of parameter passing.
Then this parameter can be set on the main page for a language, e.g. initially '''quiet''' or '''nl''', later to be removed as the descriptions start to become more common.

== Restructuring the template cascade ==

The subdivision into templates for each letter of the alphabet is a pain in the <donkey>, and actually unnecessary.
We describe how it is structured currently (Feb 2006), and draw up a plan for a simpler structure.

=== The two paths to this template: why? ===
Find out why there are two paths to this template:
# Through [[Template:Latindict]] and [[Template:Latindict/A]] (and the other letters).
# Via non-template "Latin words and expressions/''letter''" pages.
This also happens for the Dutch translated pages, so we get
Latin words and expressions/nl/A
Latin words and expressions/nl/B
etc.
and also
Nl:Latijnse woorden en uitdrukkingen/A
Nl:Latijnse woorden en uitdrukkingen/A
etc.

At first the suspect in this was the French translation, which uses a translated French page for each letter page.

Looking at the page history of the pages involved to see what happened, it turns out these pages were created around the same time and by the same author as the templates. They might be a remnant of an earlier setup. Examination of the exact creation dates and time may shed more light.

While this is going on, the use of <kbd>Template:languages</kbd> and <kbd>Template:Dict/Glossary</kbd> on all these pages creates a tangled web of pages being linked to by other pages. For example
Nl:Latijnse woorden en uitdukkingen/A
is linked to by:
* The main Dutch page
* Itself
* The non-redirected version of itself
* The main French page
* Every other <kbd>Nl:Latijnse woorden en uitdukkingen/''letter''</kbd> page

=== The Reason ===
All these subpages were created in a desperate bid by the original author to split the list into separate pages, allowing an editor to edit the list only a letter-section at the time, rather than having to edit the entire list of thousands of lemmas.

Because the actual content of the article is transcluded, the normal "edit by section" mechanism does not work.

This problem is not trivial to solve. Idealy [https://www.mediawiki.org/ mediawiki] should have a built-in mechanism to redirect an action to edit a section to edit the section in the transcluded page.
: '''Find out''' if such a mechanism exists

The documentation on this subject is shockingly poor. We must find out through experimentation.

[[User:DomoViridi/Temsects|It turns out]] that the '''current Wiki''' implements this '''exactly as expected'''.
* Put the sections in a transcluded file
* Transclude that file in the main file
* Put a ToC in either the main file or the transcluded file (both work), with simple <code><nowiki>[[#A|A]]</nowiki></code> links
* The ToC links will show you the section on the main page
* The auto-generated edit links will open the transcluded file on that section
* It also works with [[User:DomoViridi/Temsects/nl|translated pages]]

=== Current structure ===

==== The main page [[Latin_words_and_expressions]] ====
This contains
* A warning box about the mixing of English and Dutch descriptions.
* A code to suppress the Table of Contents.
* A call to <kbd>Template:Languages</kbd>, to make automatic links to the translated pages.
* An introductory text.
* A call to <kbd>Template:Dict/Glossary</kbd>, passing the name of the page as a parameter. This generates a substitute Table of Contents, linking to all the letter sections which will be generated on this page. '''Note:''' instead of passing a literal copy of the name of the page, the code <code><nowiki>{{BASEPAGENAME}}</nowiki></code> should have been used by the template.
* A call to <kbd>Template:Latindict, with the language code as a parameter (<nowiki>{{latindict|en}}</nowiki>). The language code is not needed, as <kbd>Template:Dict</kbd> should have used the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word.
* A comment with instructions on where to edit lemmas.
* A Category link <code><nowiki>[[Category:Genealogy|L]]</nowiki></code>.

Translated pages such as [[Latin_words_and_expressions/nl]] (or the page they redirect to) contain the same, with adaptations.
* The introductory text is translated.
* The parameter passed to <kbd>Template:Dict/Glossary</kbd> changed to the translated page name. (Using <code><nowiki>{{BASEPAGENAME}}</nowiki></code> would have prevented this, but that issue is moot in the new structure.)
* The parameter passed to <kbd>Template:Latindict</kbd> is changed to the code for the translated language. (Again, this could have been automated using <code><nowiki>{{PAGELANGUAGE}}</nowiki></code>. Again, issue is moot in the new structure.)
* The instructions in the comment are translated.
* The Category link is translated: <code><nowiki>[[Category:Nl:Genealogie|Latijnse woorden]]</nowiki></code>.

==== Template:Latindict ====
This contains
* A list of sections, one for each letter of the alphabet, and one for the 'at' symbol (<kbd>@</kbd>), with a Level 2 header with that letter.
* In each letter section, a call to a sub-template for that letter (<code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> etc.). The language code (passed into <kbd>Template:Latindict</kbd> as the first parameter), is passed on as the first parameter to the sub-template.
* Nothing else.

==== Template:Latindict/A etc. ====
These contain
* the actual lemmas, in the form of a <kbd>Template:Dict</kbd> entry for each lemma:
<nowiki>{{dict|lang ={{{1}}} |word=abavia|default=betovergrootmoeder |en=second great grandmother}}</nowiki>
* A link (now dead) to the Dutch/Flemish source material, as a <kbd>noinclude</kbd> so it won't show up on the page, but ''is'' visible in the source. This could have been done with an HTML comment.
''(Note: the English description in the example should be 'great-great-grandmother'.)''

The parameters to <kbd>Template:Dict</kbd> are filled in as follows:
;lang:The language code was passed in as the first parameter, and is now copied into this parameter: <kbd><nowiki>lang={{{1}}}</nowiki></kbd>.
;word:Set to the Latin lemma.
;default:Set to the Dutch description (which is wrong, this should be changed to the '''nl''' parameter everywhere; this is the main cause of the English/Dutch mixing of the descriptions).
;en, nl, fr, etc:Descriptions in other languages are given as a parameter named after their language code. Texts for other languages can be added here, e.g. <kbd>fr=Arrière-arrière-grand-mère</kbd>.

==== Template:Dict ====
This finally generates a display list entry based on the parameters.

The template turns the parameters into a display list entry, with the format
<nowiki>;'''word''':description</nowiki>
(The lemma word does not need to be explicitly made bold, the description list format already does that.)
This results in
;word:description

=== New structure ===

==== The main page (and the translations) ====
* The warning box about the error will probably be gone by this time.
* The code to suppress the Table of Contents remains.
* The call to <kbd>Template:Languages</kbd> can remain unchanged.
* The introductory text can probably remain unchanged.
* The call to <kbd>Template:Dict/Glossary</kbd> must be removed.
* The call <kbd><nowiki>{{Latindict}}</nowiki></kbd> must remain unchanged, with the language of the page as the first parameter (because the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word does not work on this wiki).
* The comment with instructions must be updated to reflect the new situation, i.e. find the lemma in <kbd>Template:Latindict</kbd> and edit it there.

The translated page pages must do the same changes:
* Remove the call to <kbd>Template:Dict/Glossary</kbd>.
* Update the translation of the instructions.

The result will be that:
* The homebrew ToC entries will jump to that letter on the main page.
* The "Edit" link on each section will open an edit on the section '''in the template''', allowing direct editing of lemmas.

==== Template:Latindict ====
Change to contain:
* A Table-of-Contents header with in-page links to all the letters. This replaces the <kbd>Template:Dict/Glossary</kbd> call from the main page. If the user clicks on one of these links, the view should jump to that letter header on the same page. This helps the user find a lemma more quickly.
: There will only be one call for this, so there is no need for a template. A simple set of <code><nowiki>[[#A|A]] - [[#B|B]] -[[#C|C]] - [[#D|D]] - ...</nowiki></code> with a table around it should do the trick. Copy from the template contents and search/replace <code><nowiki>{{{1}}</nowiki>}/</code> with <code>#</code>. Note that this moves this fuctionality from the main page (and the translated pages) to this template (with only one occurence), useful in all translations of the main page.
* Sections for each letter (unchanged). Simple <code>== A ==</code> headers are enough.
* In each section replace the <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> with all the <code><nowiki>{{dict|...}}</nowiki></code> entries for that letter. These can be substituted in by changing <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> to <code><nowiki>{{subst:Latindict/A|{{{1}}}}}</nowiki></code> and saving the page. Repeat for all the letters.

If all goes as expected, the ToC links will bring you to the section on the main page, and the auto-generated edit links will open this template for editing on the chosen section.

By allowing editing-by-section, users will not be overburdened by edit pages which are too big. As a major advantage, it will be much easier for editors to find the lemma they want to edit, without the need to search for the correct lettered subpage.

==== Template:Latindict/A etc. ====
These can all be eliminated.

==== Template:Dict ====
This must be overhauled.
* Eliminate the '''lang''' parameter. Take the language from the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word. On this wiki this will always have a valid value.
** Unfortunately, <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> always produces "en" on this wiki. So we still need the '''lang''' parameter
* Eliminate the '''default''' parameter.
** Or better: Allow '''default''' as an alternative for '''nl'''. This gives backward compatiblilty with the existing calls to this template.
* Other improvements are described in the [[#Improvements to Dict template]] section

=== Pages no longer needed ===
With this new structure the following pages can be eliminated:
* All the lettered sub-templates (<kbd>Template:Latindict/A</kbd> etc.).
* All the <kbd>Main:</kbd> space lettered sub-pages (<kbd>Latin words and expressions/A</kbd> etc.).
* All the Dutch translated main space lettered sub-pages (<kbd>Latin words and expressions/A/nl</kbd> etc.), and the pages they redirect to (<kbd>Nl:Latijnse woorden en expressies/A</kbd> etc.).
* Same for the French translated pages. Although we will have to copy the descriptions from the French pages into the <kbd>Template:Dict</kbd> calls as <kbd>fr=</kbd> parameters first.
* Status of the Hebrew translated pages needs to be examined.

== Actions to take for modification ==

=== Set up a test environment ===
Set up a test environment to create and test a better version of the template without disturbing the existing one.
* (done) Create a Sandbox subspace to my user page: <kbd>User:DomoViridi/TempTest</kbd>; Think about the use or no-use of capital letters in the names of the pages first (doesn't realy matter). Put my own version of the pages there, but in the <kbd>User:DomoViridi/TempTest</kbd> space. Test templates can be called with the syntax <code><nowiki>{{User:DomoViridi/TempTest/mytemplate}}</nowiki></code> (the braces ensure transclusion, the <kbd>User:</kbd> namespace replaces the default <kbd>Template:</kbd> namespace.
* (done) Create a template page with the test template, [[User:DomoViridi/TempTest/Dict]]. Fill it initially with a copy of the original <kbd>Template:Dict</kbd>.
* (done) Create a page with test cases, [[User:DomoViridi/TempTest/Testcases]]. Put some calls to our Dict template in it, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus| en=silly sod| nl=sukkel}}</nowiki></code>. Add many testcases and put their source code in nowiki text above each.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict/A]] with calls to the Dict template, using <code><nowiki>{{User:DomoViridi/TempTest/Dict}}</nowiki></code>. Copy the existing "A" page and shorten it, leaving some useful examples, with different languages, some abbreviations, and some missing languages. Add French translations to some of the lemmas. Also copy a different letter page (a short one), which has some translations.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict]] which calls our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space.
* (done) Create a main page [[User:DomoViridi/TempTest/Latin words and expressions]], which calls <code><nowiki>{{User:DomoViridi/TempTest/Latindict}}</nowiki></code>.
: '''Oh hey!''', it turns out <kbd>Template:Dict/Glossary</kbd> creates links to [[Latin words and expressions/A]] and all the other letters.
* (done) Create lettered pages [[User:DomoViridi/TempTest/Latin words and expressions/A]] for each of the pages for wich we have a template, and fill them with a copy of the originals. which call our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space. Note that this is all duplicate work.
* (done) Create a translated page [[User:DomoViridi/TempTest/Latin words and expressions/nl]], fill it with the contents of [[Nl:Latijnse woorden en expressies]]. Change the calls to point to the sandbox, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Latindict | nl}}</nowiki></code> (passing the language to the template).
: '''Oh hey!''', once again we see how the clumsy <kbd>Template:Dict/Glossary</kbd> requires subpages of the translated page, one for each letter of the alphabet.
* (done) Create the translated subpages before moving the translated main page.
: Although: this does not help, because the letter pages are not subpages of the <kbd>.../nl</kbd> page, but are formed with <kbd>.../A/nl</kbd>.
* (done) Move the translated page to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies]]. This will automatically create a redirect from the <kbd>/nl</kbd> page to this page.
* (done) Move all the frakking translated subpages to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies/A]], again auto-generating a redirect.

Creating 27 (one for each letter of the alphabet, plus '@') lettered subpages each time for:
* The Templates
* The main page (English)
* The Dutch (nl) translation
* The redirect for the Dutch (nl) translation
* The French (fr) translation
* The redirect for the French (fr) translation
* The Hebrew (he) translation
* The redirect Hebrew (he) translation
* The same again for every new translation
is an unbelievable pile of unnecessary busywork. All so that we can have separate pages for every letter, and links to them.
Good thing I only did letters A and B for this sandbox.

''Note: the Gramps wiki does not support the [https://www.mediawiki.org/wiki/Extension:TemplateSandbox TemplateSandbox extension], which would have allowed to attach a sandbox subpage directly to the template. This means the <code><nowiki>{{testcases notice}}</nowiki></code> template is also not available.''

=== Create an improved Dict template ===
Do this in the sandbox. See the [[#Improvements to Dict template]] section.

Don't forget to adjust the documentation.

When it works with no detected problems, overwrite the actual template with our code.

=== Change "default" to "nl" ===
Because <kbd>Template:Dict</kbd> defaults to <nowiki>{{{en}}}</nowiki> if there is no description in a valid language, changing '''default''' to '''nl''' will result in a lot of bad output for all entries where '''en''' is missing.

This means we need to modify <kbd>Template:Dict</kbd> before we make this change.

Edit all the <kbd>Template:Latindict/<letter></kbd> pages to change '''default=''' to '''nl='''.
The effect should be that Dutch descriptions only show on the Dutch pages.
* Start with a small page and see how it goes.
* Then do a few more with export-to-editor, bulk search/replace, import from editor. Check for anomalies.
* Do the other pages

This should all have effect without the need to change the templates yet. It also makes room for a modification of <kbd>Template:Dict</kbd> which drops the '''default''' parameter.

=== Restructure the template cascade ===
Do this in the sandbox. See [[#Restructuring the template cascade]].
Make sure it works perfectly.

Before modifying the real pages, put notices in the talk pages and banners in any and all of the pages involved.

Then modify the real pages.

Try to get the useless pages deleted. At the least put a warning box in them. Something like "Do not use this page. Use page xxx instead. This page will be deleted in the near future".

=== Move the translated French pages ===
Copy all the existing French translations to the <kbd>Template:Latindict/<letter></kbd> pages.
Note: This leaves the translated French pages unchanged for now.
* Could be a big job.
* Have these pages changed much in the last few years?
* Put a notice on the Talk page for the French translation to tell them what is going on.
* Maybe put a banner on the pages too.
* Make sure they work nicely.

Switch the translated French page to use Template:Latindict
* One edit to [[Fr:Mots et expressions en latin]] should be enough.
* Add a notice to the French page about the change

=== Check the Hebrew pages ===
Check what the Hebrew pages look like now that we changed '''default=''' to '''nl='''.

=== Remove unneeded pages ===
Remove all the unneeded letter pages and letter templates, for each language that uses them.

=== Possible 'silent' mode ===
We may want to add a "silent" mode, where lemmas are not shown if there is no description for that language. This will avoid long pages of untranslated Latin words and expressions, and emphasise the lemmas that have been translated.

This will require an extra parameter, which must be passed down through all the templates. This named parameter should be given with a value, so that it evaluates to "take the then case" for the parser function:
<nowiki>{{#if:{{{silent|}}} | do silent version | do not-silent version}}</nowiki>
That means the parameter should be set as <kbd>"silent=<something>"</kbd>, with an arbitrary, non-empty value. See [https://www.mediawiki.org/wiki/Help:Parser_functions_in_templates Parser functions in templates]
* On page [[Latin words and expressions/fr]]: call template <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd> for silent and <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd> for not-silent.
* [[Template:Latindict]]: call <kbd><nowiki>{{Latindict/A|{{{1}}}|silent={{{silent|}}}}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* [[Template:Latindict/A]]: call <kbd><nowiki>{{Dict|lang={{{1}}}|silent={{{silent|}}}|word=...}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* Inside [[Template:Dict]] use <kbd><nowiki>{{#if: {{{silent|}}} | do silent stuff | do non-silent stuff}}</nowiki></kbd> (again with a bar after the parameter).

The following table shows how the parameter values trickle down to the <kbd>#if</kbd> parser, with or without the extra bar (<kbd>|</kbd>). The conclusion is that the extra bar should be used thoughout, and the parameter should be omitted for non-silent mode and passed with a value (e.g. <kbd>silent=yes</kbd>) for silent mode. The string used for the value (in this example "yes") does not matter. Note that passing the parameter with an empty string as a value ("<kbd>silent=</kbd>") will set the result to non-silent.

''Note: the use of the variables <kbd>s1</kbd>, <kbd>s2</kbd> and <kbd>s3</kbd> is arbitrary, and is used here for clarity. They could all be called <kbd>silent</kbd>.''

{| class="wikitable" style="margin:auto" width="90%"
|+ Passing on the silent parameter
! Main page
! <kbd>Latindict</kbd>
! <kbd>Latindict/A</kbd>
! <kbd>Dict</kbd>
! <kbd>#if</kbd>
|-
! style="text-align:right" | without bar
! <kbd><nowiki>s1={{{silent}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| then
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
! style="text-align:right" | with bar
! <kbd><nowiki>s1={{{silent|}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
|}

In the end, all the entries in [[Template:Latindict]] need to be modified, as must all calls to [[Template:Dict]] in all the letter templates ([[Template:Latindict/A]] etc.). And finally [[Template:Dict]] needs to implement the silent mode.

== Copyright ==
The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

User:DomoViridi/TempTest

2026-03-11T20:27:55Z

DomoViridi: /* Improvements to Dict template */ "lang" parameter is still needed.

The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

== Sandbox to test templates ==

For [[Template:Latindict]], [[Template:Latindict/A]] (and all the other letter-subpages), [[Template:Dict/Glossary]], [[Template:Dict]], as used in [[Latin words and expressions]], and the translations [[Latin words and expressions/nl]], [[Latin words and expressions/fr]] and [[Latin words and expressions/he]].

== Improvements to Dict template ==

* The '''default''' parameter does not make sense, and should be eliminated. If there is no descriptive text for a given language, then the wiki page should show a blank line (or nothing).
: Before removing it, in all uses of this template '''default=''' should be replaced with '''nl='''. This is also the solution to the problem of showing lots of Dutch language descriptions on the English pages.
:* Better yet: first make '''default''' an alternative to '''nl'''. That way, the existing calls to this template can remain unchanged, while also only showing the Dutch description (given in '''default''') if '''lang''' is "nl".

* The '''lang''' parameter is exclusively used as <code><nowiki>{{dict|lang ={{{1}}} |word=...</nowiki></code>, i.e. the value is read from the first unnamed parameter that was passed to <kbd>Template:Latindict/A</kbd>. This value cascades down from the main page.
: This cascade might be unnecessary, because the template should be able to use the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word. Entries can then be simplified to <code><nowiki>{{dict|word=...</nowiki></code>. For the use in special cases '''lang=''' could be left available to override the wiki language setting for a particular lemma.
:* Unfortunately <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> always returns "en" on this wiki, even on .../nl and Nl:... pages.

* The '''word''' named parameter should be optional, and the word should be allowed to be passed as the first anonymous parameter, so we can write <code><nowiki>{{dict| abiit| en=he/she has left | nl=hij/zij is vertrokken }}</nowiki></code>.
: Disadvantage: That would make the lemma an unnamed parameter. Unnamed parameters are not stripped of leading and trailing spaces. This can lead to lemmas with extra spaces around them.
: Although: because it is the term in a definition list, leading spaces are ignored, and trailing spaces do not affect the layout (the displayed wiki text goes to a new line after the term), or are maybe also ignored.
: Can be implemented with <code><nowiki>{{{word|{{{1}}} }}}</nowiki></code> in the template. This accepts the first anonymous parameter, except when a '''word''' parameter was given when calling the template. This gives backward compatibility, where it is ''allowed'' to use the '''word''' parameter, but not ''mandatory''.

* Make it so that <kbd>Template:Dict</kbd> does not need an explicit list of language codes. The current list blocks additional translations from being added.
: The value of the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word can be used to create the name of the desired parameter, e.g. "en". See [https://www.mediawiki.org/wiki/Manual:Advanced_templates#Variable_parameter_name Mediawiki Advanced Templates Help: Variable parameter name].
:Code: <code><nowiki>;{{{word|{{{1}}} }}}:{{{{{PAGELANGUAGE}}}}}</nowiki></code>
: The use of <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> also makes '''en''' the default language.

* The current version outputs <code><nowiki>{{{en}}}</nowiki></code> if no '''default''' or language code parameter was given. Also produces <code><nowiki>'''{{{word}}}'''</nowiki></code> if no '''word''' parameter was given.
:This is probably actually a good thing, because it shows when there is an error and the template call should be edited to resolve this.
: '''documentation''': add to the docs what parameters should be given and what happens if one is missing.

* There should be a parameter to give the expansion of an abbreviation, separate from the translations. For example <code><nowiki>{{dict|A.D.|full=Anno Domini"|en=in the year of our lord|nl=in het jaar van de Heer}}</nowiki></code>. The wiki format to be produced needs to be invented. Possibly as extra text in parentheses added to the lemma, e.g.
:;A.D. (Anno Domini):in the year of our lord
:Or on the description line:
:;A.D.:'''Anno Domini''': in the year of our lord
: By putting the formatting in the template we can ensure that it is universal accross all pages.

=== Behaviour for missing description text ===
If there is no descriptive text parameter for the language of the page, then by default the template will show the lemma, but with an empty description.

This might be annoying for translations with relatively few translated descriptions (e.g. for brand new translated pages). The reader will be looking at a long list of lemmas with only a few descriptions.

A possible solution is the introduction of a '''show''' parameter, which will determine what will happen if the lemma has is no descriptive text for the current language. Possible values:
;quiet:Show nothing. Pages will only show the lemmas which have a description in the page's language.
;blank:The default. Show the lemma with a blank description.
;a language code:Substitute the description with the given language. (Complicated implementation; maybe wait if there is demand for it.)
If the parameter is not set then do the '''blank''' behaviour.

For this parameter to work, we need to set up a new cascade of parameter passing.
Then this parameter can be set on the main page for a language, e.g. initially '''quiet''' or '''nl''', later to be removed as the descriptions start to become more common.

== Restructuring the template cascade ==

The subdivision into templates for each letter of the alphabet is a pain in the <donkey>, and actually unnecessary.
We describe how it is structured currently (Feb 2006), and draw up a plan for a simpler structure.

=== The two paths to this template: why? ===
Find out why there are two paths to this template:
# Through [[Template:Latindict]] and [[Template:Latindict/A]] (and the other letters).
# Via non-template "Latin words and expressions/''letter''" pages.
This also happens for the Dutch translated pages, so we get
Latin words and expressions/nl/A
Latin words and expressions/nl/B
etc.
and also
Nl:Latijnse woorden en uitdrukkingen/A
Nl:Latijnse woorden en uitdrukkingen/A
etc.

At first the suspect in this was the French translation, which uses a translated French page for each letter page.

Looking at the page history of the pages involved to see what happened, it turns out these pages were created around the same time and by the same author as the templates. They might be a remnant of an earlier setup. Examination of the exact creation dates and time may shed more light.

While this is going on, the use of <kbd>Template:languages</kbd> and <kbd>Template:Dict/Glossary</kbd> on all these pages creates a tangled web of pages being linked to by other pages. For example
Nl:Latijnse woorden en uitdukkingen/A
is linked to by:
* The main Dutch page
* Itself
* The non-redirected version of itself
* The main French page
* Every other <kbd>Nl:Latijnse woorden en uitdukkingen/''letter''</kbd> page

=== The Reason ===
All these subpages were created in a desperate bid by the original author to split the list into separate pages, allowing an editor to edit the list only a letter-section at the time, rather than having to edit the entire list of thousands of lemmas.

Because the actual content of the article is transcluded, the normal "edit by section" mechanism does not work.

This problem is not trivial to solve. Idealy [https://www.mediawiki.org/ mediawiki] should have a built-in mechanism to redirect an action to edit a section to edit the section in the transcluded page.
: '''Find out''' if such a mechanism exists

The documentation on this subject is shockingly poor. We must find out through experimentation.

[[User:DomoViridi/Temsects|It turns out]] that the '''current Wiki''' implements this '''exactly as expected'''.
* Put the sections in a transcluded file
* Transclude that file in the main file
* Put a ToC in either the main file or the transcluded file (both work), with simple <code><nowiki>[[#A|A]]</nowiki></code> links
* The ToC links will show you the section on the main page
* The auto-generated edit links will open the transcluded file on that section
* It also works with [[User:DomoViridi/Temsects/nl|translated pages]]

=== Current structure ===

==== The main page [[Latin_words_and_expressions]] ====
This contains
* A warning box about the mixing of English and Dutch descriptions.
* A code to suppress the Table of Contents.
* A call to <kbd>Template:Languages</kbd>, to make automatic links to the translated pages.
* An introductory text.
* A call to <kbd>Template:Dict/Glossary</kbd>, passing the name of the page as a parameter. This generates a substitute Table of Contents, linking to all the letter sections which will be generated on this page. '''Note:''' instead of passing a literal copy of the name of the page, the code <code><nowiki>{{BASEPAGENAME}}</nowiki></code> should have been used by the template.
* A call to <kbd>Template:Latindict, with the language code as a parameter (<nowiki>{{latindict|en}}</nowiki>). The language code is not needed, as <kbd>Template:Dict</kbd> should have used the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word.
* A comment with instructions on where to edit lemmas.
* A Category link <code><nowiki>[[Category:Genealogy|L]]</nowiki></code>.

Translated pages such as [[Latin_words_and_expressions/nl]] (or the page they redirect to) contain the same, with adaptations.
* The introductory text is translated.
* The parameter passed to <kbd>Template:Dict/Glossary</kbd> changed to the translated page name. (Using <code><nowiki>{{BASEPAGENAME}}</nowiki></code> would have prevented this, but that issue is moot in the new structure.)
* The parameter passed to <kbd>Template:Latindict</kbd> is changed to the code for the translated language. (Again, this could have been automated using <code><nowiki>{{PAGELANGUAGE}}</nowiki></code>. Again, issue is moot in the new structure.)
* The instructions in the comment are translated.
* The Category link is translated: <code><nowiki>[[Category:Nl:Genealogie|Latijnse woorden]]</nowiki></code>.

==== Template:Latindict ====
This contains
* A list of sections, one for each letter of the alphabet, and one for the 'at' symbol (<kbd>@</kbd>), with a Level 2 header with that letter.
* In each letter section, a call to a sub-template for that letter (<code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> etc.). The language code (passed into <kbd>Template:Latindict</kbd> as the first parameter), is passed on as the first parameter to the sub-template.
* Nothing else.

==== Template:Latindict/A etc. ====
These contain
* the actual lemmas, in the form of a <kbd>Template:Dict</kbd> entry for each lemma:
<nowiki>{{dict|lang ={{{1}}} |word=abavia|default=betovergrootmoeder |en=second great grandmother}}</nowiki>
* A link (now dead) to the Dutch/Flemish source material, as a <kbd>noinclude</kbd> so it won't show up on the page, but ''is'' visible in the source. This could have been done with an HTML comment.
''(Note: the English description in the example should be 'great-great-grandmother'.)''

The parameters to <kbd>Template:Dict</kbd> are filled in as follows:
;lang:The language code was passed in as the first parameter, and is now copied into this parameter: <kbd><nowiki>lang={{{1}}}</nowiki></kbd>.
;word:Set to the Latin lemma.
;default:Set to the Dutch description (which is wrong, this should be changed to the '''nl''' parameter everywhere; this is the main cause of the English/Dutch mixing of the descriptions).
;en, nl, fr, etc:Descriptions in other languages are given as a parameter named after their language code. Texts for other languages can be added here, e.g. <kbd>fr=Arrière-arrière-grand-mère</kbd>.

==== Template:Dict ====
This finally generates a display list entry based on the parameters.

The template turns the parameters into a display list entry, with the format
<nowiki>;'''word''':description</nowiki>
(The lemma word does not need to be explicitly made bold, the description list format already does that.)
This results in
;word:description

=== New structure ===

==== The main page (and the translations) ====
* The warning box about the error will probably be gone by this time.
* The code to suppress the Table of Contents remains.
* The call to <kbd>Template:Languages</kbd> can remain unchanged.
* The introductory text can probably remain unchanged.
* The call to <kbd>Template:Dict/Glossary</kbd> must be removed.
* The call <kbd><nowiki>{{Latindict}}</nowiki></kbd> must remain unchanged, with the language of the page as the first parameter (because the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word does not work on this wiki).
* The comment with instructions must be updated to reflect the new situation, i.e. find the lemma in <kbd>Template:Latindict</kbd> and edit it there.

The translated page pages must do the same changes:
* Remove the call to <kbd>Template:Dict/Glossary</kbd>.
* Update the translation of the instructions.

The result will be that:
* The homebrew ToC entries will jump to that letter on the main page.
* The "Edit" link on each section will open an edit on the section '''in the template''', allowing direct editing of lemmas.

==== Template:Latindict ====
Change to contain:
* A Table-of-Contents header with in-page links to all the letters. This replaces the <kbd>Template:Dict/Glossary</kbd> call from the main page. If the user clicks on one of these links, the view should jump to that letter header on the same page. This helps the user find a lemma more quickly.
: There will only be one call for this, so there is no need for a template. A simple set of <code><nowiki>[[#A|A]] - [[#B|B]] -[[#C|C]] - [[#D|D]] - ...</nowiki></code> with a table around it should do the trick. Copy from the template contents and search/replace <code><nowiki>{{{1}}</nowiki>}/</code> with <code>#</code>. Note that this moves this fuctionality from the main page (and the translated pages) to this template (with only one occurence), useful in all translations of the main page.
* Sections for each letter (unchanged). Simple <code>== A ==</code> headers are enough.
* In each section replace the <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> with all the <code><nowiki>{{dict|...}}</nowiki></code> entries for that letter. These can be substituted in by changing <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> to <code><nowiki>{{subst:Latindict/A|{{{1}}}}}</nowiki></code> and saving the page. Repeat for all the letters.

If all goes as expected, the ToC links will bring you to the section on the main page, and the auto-generated edit links will open this template for editing on the chosen section.

By allowing editing-by-section, users will not be overburdened by edit pages which are too big. As a major advantage, it will be much easier for editors to find the lemma they want to edit, without the need to search for the correct lettered subpage.

==== Template:Latindict/A etc. ====
These can all be eliminated.

==== Template:Dict ====
This must be overhauled.
* Eliminate the '''lang''' parameter. Take the language from the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word. On this wiki this will always have a valid value.
** Unfortunately, <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> always produces "en" on this wiki. So we still need the '''lang''' parameter
* Eliminate the '''default''' parameter.
** Or better: Allow '''default''' as an alternative for '''nl'''. This gives backward compatiblilty with the existing calls to this template.
* Other improvements are described in the [[#Improvements to Dict template]] section

=== Pages no longer needed ===
With this new structure the following pages can be eliminated:
* All the lettered sub-templates (<kbd>Template:Latindict/A</kbd> etc.).
* All the <kbd>Main:</kbd> space lettered sub-pages (<kbd>Latin words and expressions/A</kbd> etc.).
* All the Dutch translated main space lettered sub-pages (<kbd>Latin words and expressions/A/nl</kbd> etc.), and the pages they redirect to (<kbd>Nl:Latijnse woorden en expressies/A</kbd> etc.).
* Same for the French translated pages. Although we will have to copy the descriptions from the French pages into the <kbd>Template:Dict</kbd> calls as <kbd>fr=</kbd> parameters first.
* Status of the Hebrew translated pages needs to be examined.

== Actions to take for modification ==

=== Set up a test environment ===
Set up a test environment to create and test a better version of the template without disturbing the existing one.
* (done) Create a Sandbox subspace to my user page: <kbd>User:DomoViridi/TempTest</kbd>; Think about the use or no-use of capital letters in the names of the pages first (doesn't realy matter). Put my own version of the pages there, but in the <kbd>User:DomoViridi/TempTest</kbd> space. Test templates can be called with the syntax <code><nowiki>{{User:DomoViridi/TempTest/mytemplate}}</nowiki></code> (the braces ensure transclusion, the <kbd>User:</kbd> namespace replaces the default <kbd>Template:</kbd> namespace.
* (done) Create a template page with the test template, [[User:DomoViridi/TempTest/Dict]]. Fill it initially with a copy of the original <kbd>Template:Dict</kbd>.
* (done) Create a page with test cases, [[User:DomoViridi/TempTest/Testcases]]. Put some calls to our Dict template in it, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus| en=silly sod| nl=sukkel}}</nowiki></code>. Add many testcases and put their source code in nowiki text above each.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict/A]] with calls to the Dict template, using <code><nowiki>{{User:DomoViridi/TempTest/Dict}}</nowiki></code>. Copy the existing "A" page and shorten it, leaving some useful examples, with different languages, some abbreviations, and some missing languages. Add French translations to some of the lemmas. Also copy a different letter page (a short one), which has some translations.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict]] which calls our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space.
* (done) Create a main page [[User:DomoViridi/TempTest/Latin words and expressions]], which calls <code><nowiki>{{User:DomoViridi/TempTest/Latindict}}</nowiki></code>.
: '''Oh hey!''', it turns out <kbd>Template:Dict/Glossary</kbd> creates links to [[Latin words and expressions/A]] and all the other letters.
* (done) Create lettered pages [[User:DomoViridi/TempTest/Latin words and expressions/A]] for each of the pages for wich we have a template, and fill them with a copy of the originals. which call our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space. Note that this is all duplicate work.
* (done) Create a translated page [[User:DomoViridi/TempTest/Latin words and expressions/nl]], fill it with the contents of [[Nl:Latijnse woorden en expressies]]. Change the calls to point to the sandbox, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Latindict | nl}}</nowiki></code> (passing the language to the template).
: '''Oh hey!''', once again we see how the clumsy <kbd>Template:Dict/Glossary</kbd> requires subpages of the translated page, one for each letter of the alphabet.
* (done) Create the translated subpages before moving the translated main page.
: Although: this does not help, because the letter pages are not subpages of the <kbd>.../nl</kbd> page, but are formed with <kbd>.../A/nl</kbd>.
* (done) Move the translated page to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies]]. This will automatically create a redirect from the <kbd>/nl</kbd> page to this page.
* (done) Move all the frakking translated subpages to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies/A]], again auto-generating a redirect.

Creating 27 (one for each letter of the alphabet, plus '@') lettered subpages each time for:
* The Templates
* The main page (English)
* The Dutch (nl) translation
* The redirect for the Dutch (nl) translation
* The French (fr) translation
* The redirect for the French (fr) translation
* The Hebrew (he) translation
* The redirect Hebrew (he) translation
* The same again for every new translation
is an unbelievable pile of unnecessary busywork. All so that we can have separate pages for every letter, and links to them.
Good thing I only did letters A and B for this sandbox.

''Note: the Gramps wiki does not support the [https://www.mediawiki.org/wiki/Extension:TemplateSandbox TemplateSandbox extension], which would have allowed to attach a sandbox subpage directly to the template. This means the <code><nowiki>{{testcases notice}}</nowiki></code> template is also not available.''

=== Create an improved Dict template ===
Do this in the sandbox. See the [[#Improvements to Dict template]] section.

Don't forget to adjust the documentation.

When it works with no detected problems, overwrite the actual template with our code.

=== Change "default" to "nl" ===
Because <kbd>Template:Dict</kbd> defaults to <nowiki>{{{en}}}</nowiki> if there is no description in a valid language, changing '''default''' to '''nl''' will result in a lot of bad output for all entries where '''en''' is missing.

This means we need to modify <kbd>Template:Dict</kbd> before we make this change.

Edit all the <kbd>Template:Latindict/<letter></kbd> pages to change '''default=''' to '''nl='''.
The effect should be that Dutch descriptions only show on the Dutch pages.
* Start with a small page and see how it goes.
* Then do a few more with export-to-editor, bulk search/replace, import from editor. Check for anomalies.
* Do the other pages

This should all have effect without the need to change the templates yet. It also makes room for a modification of <kbd>Template:Dict</kbd> which drops the '''default''' parameter.

=== Restructure the template cascade ===
Do this in the sandbox. See [[#Restructuring the template cascade]].
Make sure it works perfectly.

Before modifying the real pages, put notices in the talk pages and banners in any and all of the pages involved.

Then modify the real pages.

Try to get the useless pages deleted. At the least put a warning box in them. Something like "Do not use this page. Use page xxx instead. This page will be deleted in the near future".

=== Move the translated French pages ===
Copy all the existing French translations to the <kbd>Template:Latindict/<letter></kbd> pages.
Note: This leaves the translated French pages unchanged for now.
* Could be a big job.
* Have these pages changed much in the last few years?
* Put a notice on the Talk page for the French translation to tell them what is going on.
* Maybe put a banner on the pages too.
* Make sure they work nicely.

Switch the translated French page to use Template:Latindict
* One edit to [[Fr:Mots et expressions en latin]] should be enough.
* Add a notice to the French page about the change

=== Check the Hebrew pages ===
Check what the Hebrew pages look like now that we changed '''default=''' to '''nl='''.

=== Remove unneeded pages ===
Remove all the unneeded letter pages and letter templates, for each language that uses them.

=== Possible 'silent' mode ===
We may want to add a "silent" mode, where lemmas are not shown if there is no description for that language. This will avoid long pages of untranslated Latin words and expressions, and emphasise the lemmas that have been translated.

This will require an extra parameter, which must be passed down through all the templates. This named parameter should be given with a value, so that it evaluates to "take the then case" for the parser function:
<nowiki>{{#if:{{{silent|}}} | do silent version | do not-silent version}}</nowiki>
That means the parameter should be set as <kbd>"silent=<something>"</kbd>, with an arbitrary, non-empty value. See [https://www.mediawiki.org/wiki/Help:Parser_functions_in_templates Parser functions in templates]
* On page [[Latin words and expressions/fr]]: call template <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd> for silent and <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd> for not-silent.
* [[Template:Latindict]]: call <kbd><nowiki>{{Latindict/A|{{{1}}}|silent={{{silent|}}}}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* [[Template:Latindict/A]]: call <kbd><nowiki>{{Dict|lang={{{1}}}|silent={{{silent|}}}|word=...}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* Inside [[Template:Dict]] use <kbd><nowiki>{{#if: {{{silent|}}} | do silent stuff | do non-silent stuff}}</nowiki></kbd> (again with a bar after the parameter).

The following table shows how the parameter values trickle down to the <kbd>#if</kbd> parser, with or without the extra bar (<kbd>|</kbd>). The conclusion is that the extra bar should be used thoughout, and the parameter should be omitted for non-silent mode and passed with a value (e.g. <kbd>silent=yes</kbd>) for silent mode. The string used for the value (in this example "yes") does not matter. Note that passing the parameter with an empty string as a value ("<kbd>silent=</kbd>") will set the result to non-silent.

''Note: the use of the variables <kbd>s1</kbd>, <kbd>s2</kbd> and <kbd>s3</kbd> is arbitrary, and is used here for clarity. They could all be called <kbd>silent</kbd>.''

{| class="wikitable" style="margin:auto" width="90%"
|+ Passing on the silent parameter
! Main page
! <kbd>Latindict</kbd>
! <kbd>Latindict/A</kbd>
! <kbd>Dict</kbd>
! <kbd>#if</kbd>
|-
! style="text-align:right" | without bar
! <kbd><nowiki>s1={{{silent}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| then
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
! style="text-align:right" | with bar
! <kbd><nowiki>s1={{{silent|}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
|}

In the end, all the entries in [[Template:Latindict]] need to be modified, as must all calls to [[Template:Dict]] in all the letter templates ([[Template:Latindict/A]] etc.). And finally [[Template:Dict]] needs to implement the silent mode.

== Copyright ==
The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

User:DomoViridi/TempTest

2026-03-11T20:19:29Z

DomoViridi: /* Improvements to Dict template */ "default" parameter should first be made an alternative for "nl".

The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

== Sandbox to test templates ==

For [[Template:Latindict]], [[Template:Latindict/A]] (and all the other letter-subpages), [[Template:Dict/Glossary]], [[Template:Dict]], as used in [[Latin words and expressions]], and the translations [[Latin words and expressions/nl]], [[Latin words and expressions/fr]] and [[Latin words and expressions/he]].

== Improvements to Dict template ==

* The '''default''' parameter does not make sense, and should be eliminated. If there is no descriptive text for a given language, then the wiki page should show a blank line (or nothing).
: Before removing it, in all uses of this template '''default=''' should be replaced with '''nl='''. This is also the solution to the problem of showing lots of Dutch language descriptions on the English pages.
:* Better yet: first make '''default''' an alternative to '''nl'''. That way, the existing calls to this template can remain unchanged, while also only showing the Dutch description (given in '''default''') if '''lang''' is "nl".

* The '''lang''' parameter is exclusively used as <code><nowiki>{{dict|lang ={{{1}}} |word=...</nowiki></code>, i.e. the value is read from the first unnamed parameter that was passed to <kbd>Template:Latindict/A</kbd>. This value cascades down from the main page.
: This cascade is unnecessary, because the template can use the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word. Entries can then be simplified to <code><nowiki>{{dict|word=...</nowiki></code>. For the use in special cases '''lang=''' could be left available to override the wiki language setting for a particular lemma.

* The '''word''' named parameter should be optional, and the word should be allowed to be passed as the first anonymous parameter, so we can write <code><nowiki>{{dict| abiit| en=he/she has left | nl=hij/zij is vertrokken }}</nowiki></code>.
: Disadvantage: That would make the lemma an unnamed parameter. Unnamed parameters are not stripped of leading and trailing spaces. This can lead to lemmas with extra spaces around them.
: Although: because it is the term in a definition list, leading spaces are ignored, and trailing spaces do not affect the layout (the displayed wiki text goes to a new line after the term), or are maybe also ignored.
: Can be implemented with <code><nowiki>{{{word|{{{1}}} }}}</nowiki></code> in the template. This accepts the first anonymous parameter, except when a '''word''' parameter was given when calling the template. This gives backward compatibility, where it is ''allowed'' to use the '''word''' parameter, but not ''mandatory''.

* Make it so that <kbd>Template:Dict</kbd> does not need an explicit list of language codes. The current list blocks additional translations from being added.
: The value of the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word can be used to create the name of the desired parameter, e.g. "en". See [https://www.mediawiki.org/wiki/Manual:Advanced_templates#Variable_parameter_name Mediawiki Advanced Templates Help: Variable parameter name].
:Code: <code><nowiki>;{{{word|{{{1}}} }}}:{{{{{PAGELANGUAGE}}}}}</nowiki></code>
: The use of <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> also makes '''en''' the default language.

* The current version outputs <code><nowiki>{{{en}}}</nowiki></code> if no '''default''' or language code parameter was given. Also produces <code><nowiki>'''{{{word}}}'''</nowiki></code> if no '''word''' parameter was given.
:This is probably actually a good thing, because it shows when there is an error and the template call should be edited to resolve this.
: '''documentation''': add to the docs what parameters should be given and what happens if one is missing.

* There should be a parameter to give the expansion of an abbreviation, separate from the translations. For example <code><nowiki>{{dict|A.D.|full=Anno Domini"|en=in the year of our lord|nl=in het jaar van de Heer}}</nowiki></code>. The wiki format to be produced needs to be invented. Possibly as extra text in parentheses added to the lemma, e.g.
:;A.D. (Anno Domini):in the year of our lord
:Or on the description line:
:;A.D.:'''Anno Domini''': in the year of our lord
: By putting the formatting in the template we can ensure that it is universal accross all pages.

=== Behaviour for missing description text ===
If there is no descriptive text parameter for the language of the page, then by default the template will show the lemma, but with an empty description.

This might be annoying for translations with relatively few translated descriptions (e.g. for brand new translated pages). The reader will be looking at a long list of lemmas with only a few descriptions.

A possible solution is the introduction of a '''show''' parameter, which will determine what will happen if the lemma has is no descriptive text for the current language. Possible values:
;quiet:Show nothing. Pages will only show the lemmas which have a description in the page's language.
;blank:The default. Show the lemma with a blank description.
;a language code:Substitute the description with the given language. (Complicated implementation; maybe wait if there is demand for it.)
If the parameter is not set then do the '''blank''' behaviour.

For this parameter to work, we need to set up a new cascade of parameter passing.
Then this parameter can be set on the main page for a language, e.g. initially '''quiet''' or '''nl''', later to be removed as the descriptions start to become more common.

== Restructuring the template cascade ==

The subdivision into templates for each letter of the alphabet is a pain in the <donkey>, and actually unnecessary.
We describe how it is structured currently (Feb 2006), and draw up a plan for a simpler structure.

=== The two paths to this template: why? ===
Find out why there are two paths to this template:
# Through [[Template:Latindict]] and [[Template:Latindict/A]] (and the other letters).
# Via non-template "Latin words and expressions/''letter''" pages.
This also happens for the Dutch translated pages, so we get
Latin words and expressions/nl/A
Latin words and expressions/nl/B
etc.
and also
Nl:Latijnse woorden en uitdrukkingen/A
Nl:Latijnse woorden en uitdrukkingen/A
etc.

At first the suspect in this was the French translation, which uses a translated French page for each letter page.

Looking at the page history of the pages involved to see what happened, it turns out these pages were created around the same time and by the same author as the templates. They might be a remnant of an earlier setup. Examination of the exact creation dates and time may shed more light.

While this is going on, the use of <kbd>Template:languages</kbd> and <kbd>Template:Dict/Glossary</kbd> on all these pages creates a tangled web of pages being linked to by other pages. For example
Nl:Latijnse woorden en uitdukkingen/A
is linked to by:
* The main Dutch page
* Itself
* The non-redirected version of itself
* The main French page
* Every other <kbd>Nl:Latijnse woorden en uitdukkingen/''letter''</kbd> page

=== The Reason ===
All these subpages were created in a desperate bid by the original author to split the list into separate pages, allowing an editor to edit the list only a letter-section at the time, rather than having to edit the entire list of thousands of lemmas.

Because the actual content of the article is transcluded, the normal "edit by section" mechanism does not work.

This problem is not trivial to solve. Idealy [https://www.mediawiki.org/ mediawiki] should have a built-in mechanism to redirect an action to edit a section to edit the section in the transcluded page.
: '''Find out''' if such a mechanism exists

The documentation on this subject is shockingly poor. We must find out through experimentation.

[[User:DomoViridi/Temsects|It turns out]] that the '''current Wiki''' implements this '''exactly as expected'''.
* Put the sections in a transcluded file
* Transclude that file in the main file
* Put a ToC in either the main file or the transcluded file (both work), with simple <code><nowiki>[[#A|A]]</nowiki></code> links
* The ToC links will show you the section on the main page
* The auto-generated edit links will open the transcluded file on that section
* It also works with [[User:DomoViridi/Temsects/nl|translated pages]]

=== Current structure ===

==== The main page [[Latin_words_and_expressions]] ====
This contains
* A warning box about the mixing of English and Dutch descriptions.
* A code to suppress the Table of Contents.
* A call to <kbd>Template:Languages</kbd>, to make automatic links to the translated pages.
* An introductory text.
* A call to <kbd>Template:Dict/Glossary</kbd>, passing the name of the page as a parameter. This generates a substitute Table of Contents, linking to all the letter sections which will be generated on this page. '''Note:''' instead of passing a literal copy of the name of the page, the code <code><nowiki>{{BASEPAGENAME}}</nowiki></code> should have been used by the template.
* A call to <kbd>Template:Latindict, with the language code as a parameter (<nowiki>{{latindict|en}}</nowiki>). The language code is not needed, as <kbd>Template:Dict</kbd> should have used the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word.
* A comment with instructions on where to edit lemmas.
* A Category link <code><nowiki>[[Category:Genealogy|L]]</nowiki></code>.

Translated pages such as [[Latin_words_and_expressions/nl]] (or the page they redirect to) contain the same, with adaptations.
* The introductory text is translated.
* The parameter passed to <kbd>Template:Dict/Glossary</kbd> changed to the translated page name. (Using <code><nowiki>{{BASEPAGENAME}}</nowiki></code> would have prevented this, but that issue is moot in the new structure.)
* The parameter passed to <kbd>Template:Latindict</kbd> is changed to the code for the translated language. (Again, this could have been automated using <code><nowiki>{{PAGELANGUAGE}}</nowiki></code>. Again, issue is moot in the new structure.)
* The instructions in the comment are translated.
* The Category link is translated: <code><nowiki>[[Category:Nl:Genealogie|Latijnse woorden]]</nowiki></code>.

==== Template:Latindict ====
This contains
* A list of sections, one for each letter of the alphabet, and one for the 'at' symbol (<kbd>@</kbd>), with a Level 2 header with that letter.
* In each letter section, a call to a sub-template for that letter (<code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> etc.). The language code (passed into <kbd>Template:Latindict</kbd> as the first parameter), is passed on as the first parameter to the sub-template.
* Nothing else.

==== Template:Latindict/A etc. ====
These contain
* the actual lemmas, in the form of a <kbd>Template:Dict</kbd> entry for each lemma:
<nowiki>{{dict|lang ={{{1}}} |word=abavia|default=betovergrootmoeder |en=second great grandmother}}</nowiki>
* A link (now dead) to the Dutch/Flemish source material, as a <kbd>noinclude</kbd> so it won't show up on the page, but ''is'' visible in the source. This could have been done with an HTML comment.
''(Note: the English description in the example should be 'great-great-grandmother'.)''

The parameters to <kbd>Template:Dict</kbd> are filled in as follows:
;lang:The language code was passed in as the first parameter, and is now copied into this parameter: <kbd><nowiki>lang={{{1}}}</nowiki></kbd>.
;word:Set to the Latin lemma.
;default:Set to the Dutch description (which is wrong, this should be changed to the '''nl''' parameter everywhere; this is the main cause of the English/Dutch mixing of the descriptions).
;en, nl, fr, etc:Descriptions in other languages are given as a parameter named after their language code. Texts for other languages can be added here, e.g. <kbd>fr=Arrière-arrière-grand-mère</kbd>.

==== Template:Dict ====
This finally generates a display list entry based on the parameters.

The template turns the parameters into a display list entry, with the format
<nowiki>;'''word''':description</nowiki>
(The lemma word does not need to be explicitly made bold, the description list format already does that.)
This results in
;word:description

=== New structure ===

==== The main page (and the translations) ====
* The warning box about the error will probably be gone by this time.
* The code to suppress the Table of Contents remains.
* The call to <kbd>Template:Languages</kbd> can remain unchanged.
* The introductory text can probably remain unchanged.
* The call to <kbd>Template:Dict/Glossary</kbd> must be removed.
* The call <kbd><nowiki>{{Latindict}}</nowiki></kbd> must remain unchanged, with the language of the page as the first parameter (because the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word does not work on this wiki).
* The comment with instructions must be updated to reflect the new situation, i.e. find the lemma in <kbd>Template:Latindict</kbd> and edit it there.

The translated page pages must do the same changes:
* Remove the call to <kbd>Template:Dict/Glossary</kbd>.
* Update the translation of the instructions.

The result will be that:
* The homebrew ToC entries will jump to that letter on the main page.
* The "Edit" link on each section will open an edit on the section '''in the template''', allowing direct editing of lemmas.

==== Template:Latindict ====
Change to contain:
* A Table-of-Contents header with in-page links to all the letters. This replaces the <kbd>Template:Dict/Glossary</kbd> call from the main page. If the user clicks on one of these links, the view should jump to that letter header on the same page. This helps the user find a lemma more quickly.
: There will only be one call for this, so there is no need for a template. A simple set of <code><nowiki>[[#A|A]] - [[#B|B]] -[[#C|C]] - [[#D|D]] - ...</nowiki></code> with a table around it should do the trick. Copy from the template contents and search/replace <code><nowiki>{{{1}}</nowiki>}/</code> with <code>#</code>. Note that this moves this fuctionality from the main page (and the translated pages) to this template (with only one occurence), useful in all translations of the main page.
* Sections for each letter (unchanged). Simple <code>== A ==</code> headers are enough.
* In each section replace the <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> with all the <code><nowiki>{{dict|...}}</nowiki></code> entries for that letter. These can be substituted in by changing <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> to <code><nowiki>{{subst:Latindict/A|{{{1}}}}}</nowiki></code> and saving the page. Repeat for all the letters.

If all goes as expected, the ToC links will bring you to the section on the main page, and the auto-generated edit links will open this template for editing on the chosen section.

By allowing editing-by-section, users will not be overburdened by edit pages which are too big. As a major advantage, it will be much easier for editors to find the lemma they want to edit, without the need to search for the correct lettered subpage.

==== Template:Latindict/A etc. ====
These can all be eliminated.

==== Template:Dict ====
This must be overhauled.
* Eliminate the '''lang''' parameter. Take the language from the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word. On this wiki this will always have a valid value.
** Unfortunately, <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> always produces "en" on this wiki. So we still need the '''lang''' parameter
* Eliminate the '''default''' parameter.
** Or better: Allow '''default''' as an alternative for '''nl'''. This gives backward compatiblilty with the existing calls to this template.
* Other improvements are described in the [[#Improvements to Dict template]] section

=== Pages no longer needed ===
With this new structure the following pages can be eliminated:
* All the lettered sub-templates (<kbd>Template:Latindict/A</kbd> etc.).
* All the <kbd>Main:</kbd> space lettered sub-pages (<kbd>Latin words and expressions/A</kbd> etc.).
* All the Dutch translated main space lettered sub-pages (<kbd>Latin words and expressions/A/nl</kbd> etc.), and the pages they redirect to (<kbd>Nl:Latijnse woorden en expressies/A</kbd> etc.).
* Same for the French translated pages. Although we will have to copy the descriptions from the French pages into the <kbd>Template:Dict</kbd> calls as <kbd>fr=</kbd> parameters first.
* Status of the Hebrew translated pages needs to be examined.

== Actions to take for modification ==

=== Set up a test environment ===
Set up a test environment to create and test a better version of the template without disturbing the existing one.
* (done) Create a Sandbox subspace to my user page: <kbd>User:DomoViridi/TempTest</kbd>; Think about the use or no-use of capital letters in the names of the pages first (doesn't realy matter). Put my own version of the pages there, but in the <kbd>User:DomoViridi/TempTest</kbd> space. Test templates can be called with the syntax <code><nowiki>{{User:DomoViridi/TempTest/mytemplate}}</nowiki></code> (the braces ensure transclusion, the <kbd>User:</kbd> namespace replaces the default <kbd>Template:</kbd> namespace.
* (done) Create a template page with the test template, [[User:DomoViridi/TempTest/Dict]]. Fill it initially with a copy of the original <kbd>Template:Dict</kbd>.
* (done) Create a page with test cases, [[User:DomoViridi/TempTest/Testcases]]. Put some calls to our Dict template in it, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus| en=silly sod| nl=sukkel}}</nowiki></code>. Add many testcases and put their source code in nowiki text above each.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict/A]] with calls to the Dict template, using <code><nowiki>{{User:DomoViridi/TempTest/Dict}}</nowiki></code>. Copy the existing "A" page and shorten it, leaving some useful examples, with different languages, some abbreviations, and some missing languages. Add French translations to some of the lemmas. Also copy a different letter page (a short one), which has some translations.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict]] which calls our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space.
* (done) Create a main page [[User:DomoViridi/TempTest/Latin words and expressions]], which calls <code><nowiki>{{User:DomoViridi/TempTest/Latindict}}</nowiki></code>.
: '''Oh hey!''', it turns out <kbd>Template:Dict/Glossary</kbd> creates links to [[Latin words and expressions/A]] and all the other letters.
* (done) Create lettered pages [[User:DomoViridi/TempTest/Latin words and expressions/A]] for each of the pages for wich we have a template, and fill them with a copy of the originals. which call our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space. Note that this is all duplicate work.
* (done) Create a translated page [[User:DomoViridi/TempTest/Latin words and expressions/nl]], fill it with the contents of [[Nl:Latijnse woorden en expressies]]. Change the calls to point to the sandbox, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Latindict | nl}}</nowiki></code> (passing the language to the template).
: '''Oh hey!''', once again we see how the clumsy <kbd>Template:Dict/Glossary</kbd> requires subpages of the translated page, one for each letter of the alphabet.
* (done) Create the translated subpages before moving the translated main page.
: Although: this does not help, because the letter pages are not subpages of the <kbd>.../nl</kbd> page, but are formed with <kbd>.../A/nl</kbd>.
* (done) Move the translated page to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies]]. This will automatically create a redirect from the <kbd>/nl</kbd> page to this page.
* (done) Move all the frakking translated subpages to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies/A]], again auto-generating a redirect.

Creating 27 (one for each letter of the alphabet, plus '@') lettered subpages each time for:
* The Templates
* The main page (English)
* The Dutch (nl) translation
* The redirect for the Dutch (nl) translation
* The French (fr) translation
* The redirect for the French (fr) translation
* The Hebrew (he) translation
* The redirect Hebrew (he) translation
* The same again for every new translation
is an unbelievable pile of unnecessary busywork. All so that we can have separate pages for every letter, and links to them.
Good thing I only did letters A and B for this sandbox.

''Note: the Gramps wiki does not support the [https://www.mediawiki.org/wiki/Extension:TemplateSandbox TemplateSandbox extension], which would have allowed to attach a sandbox subpage directly to the template. This means the <code><nowiki>{{testcases notice}}</nowiki></code> template is also not available.''

=== Create an improved Dict template ===
Do this in the sandbox. See the [[#Improvements to Dict template]] section.

Don't forget to adjust the documentation.

When it works with no detected problems, overwrite the actual template with our code.

=== Change "default" to "nl" ===
Because <kbd>Template:Dict</kbd> defaults to <nowiki>{{{en}}}</nowiki> if there is no description in a valid language, changing '''default''' to '''nl''' will result in a lot of bad output for all entries where '''en''' is missing.

This means we need to modify <kbd>Template:Dict</kbd> before we make this change.

Edit all the <kbd>Template:Latindict/<letter></kbd> pages to change '''default=''' to '''nl='''.
The effect should be that Dutch descriptions only show on the Dutch pages.
* Start with a small page and see how it goes.
* Then do a few more with export-to-editor, bulk search/replace, import from editor. Check for anomalies.
* Do the other pages

This should all have effect without the need to change the templates yet. It also makes room for a modification of <kbd>Template:Dict</kbd> which drops the '''default''' parameter.

=== Restructure the template cascade ===
Do this in the sandbox. See [[#Restructuring the template cascade]].
Make sure it works perfectly.

Before modifying the real pages, put notices in the talk pages and banners in any and all of the pages involved.

Then modify the real pages.

Try to get the useless pages deleted. At the least put a warning box in them. Something like "Do not use this page. Use page xxx instead. This page will be deleted in the near future".

=== Move the translated French pages ===
Copy all the existing French translations to the <kbd>Template:Latindict/<letter></kbd> pages.
Note: This leaves the translated French pages unchanged for now.
* Could be a big job.
* Have these pages changed much in the last few years?
* Put a notice on the Talk page for the French translation to tell them what is going on.
* Maybe put a banner on the pages too.
* Make sure they work nicely.

Switch the translated French page to use Template:Latindict
* One edit to [[Fr:Mots et expressions en latin]] should be enough.
* Add a notice to the French page about the change

=== Check the Hebrew pages ===
Check what the Hebrew pages look like now that we changed '''default=''' to '''nl='''.

=== Remove unneeded pages ===
Remove all the unneeded letter pages and letter templates, for each language that uses them.

=== Possible 'silent' mode ===
We may want to add a "silent" mode, where lemmas are not shown if there is no description for that language. This will avoid long pages of untranslated Latin words and expressions, and emphasise the lemmas that have been translated.

This will require an extra parameter, which must be passed down through all the templates. This named parameter should be given with a value, so that it evaluates to "take the then case" for the parser function:
<nowiki>{{#if:{{{silent|}}} | do silent version | do not-silent version}}</nowiki>
That means the parameter should be set as <kbd>"silent=<something>"</kbd>, with an arbitrary, non-empty value. See [https://www.mediawiki.org/wiki/Help:Parser_functions_in_templates Parser functions in templates]
* On page [[Latin words and expressions/fr]]: call template <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd> for silent and <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd> for not-silent.
* [[Template:Latindict]]: call <kbd><nowiki>{{Latindict/A|{{{1}}}|silent={{{silent|}}}}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* [[Template:Latindict/A]]: call <kbd><nowiki>{{Dict|lang={{{1}}}|silent={{{silent|}}}|word=...}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* Inside [[Template:Dict]] use <kbd><nowiki>{{#if: {{{silent|}}} | do silent stuff | do non-silent stuff}}</nowiki></kbd> (again with a bar after the parameter).

The following table shows how the parameter values trickle down to the <kbd>#if</kbd> parser, with or without the extra bar (<kbd>|</kbd>). The conclusion is that the extra bar should be used thoughout, and the parameter should be omitted for non-silent mode and passed with a value (e.g. <kbd>silent=yes</kbd>) for silent mode. The string used for the value (in this example "yes") does not matter. Note that passing the parameter with an empty string as a value ("<kbd>silent=</kbd>") will set the result to non-silent.

''Note: the use of the variables <kbd>s1</kbd>, <kbd>s2</kbd> and <kbd>s3</kbd> is arbitrary, and is used here for clarity. They could all be called <kbd>silent</kbd>.''

{| class="wikitable" style="margin:auto" width="90%"
|+ Passing on the silent parameter
! Main page
! <kbd>Latindict</kbd>
! <kbd>Latindict/A</kbd>
! <kbd>Dict</kbd>
! <kbd>#if</kbd>
|-
! style="text-align:right" | without bar
! <kbd><nowiki>s1={{{silent}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| then
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
! style="text-align:right" | with bar
! <kbd><nowiki>s1={{{silent|}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
|}

In the end, all the entries in [[Template:Latindict]] need to be modified, as must all calls to [[Template:Dict]] in all the letter templates ([[Template:Latindict/A]] etc.). And finally [[Template:Dict]] needs to implement the silent mode.

== Copyright ==
The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

User:DomoViridi/TempTest

2026-03-11T18:49:39Z

DomoViridi: /* The main page (and the translations) */ Do not add code to prevent editing by section, and other updates.

The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

== Sandbox to test templates ==

For [[Template:Latindict]], [[Template:Latindict/A]] (and all the other letter-subpages), [[Template:Dict/Glossary]], [[Template:Dict]], as used in [[Latin words and expressions]], and the translations [[Latin words and expressions/nl]], [[Latin words and expressions/fr]] and [[Latin words and expressions/he]].

== Improvements to Dict template ==

* The '''default''' parameter does not make sense, and should be eliminated. If there is no descriptive text for a given language, then the wiki page should show a blank line (or nothing).
: Before removing it, in all uses of this template '''default=''' should be replaced with '''nl='''. This is also the solution to the problem of showing lots of Dutch language descriptions on the English pages.

* The '''lang''' parameter is exclusively used as <code><nowiki>{{dict|lang ={{{1}}} |word=...</nowiki></code>, i.e. the value is read from the first unnamed parameter that was passed to <kbd>Template:Latindict/A</kbd>. This value cascades down from the main page.
: This cascade is unnecessary, because the template can use the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word. Entries can then be simplified to <code><nowiki>{{dict|word=...</nowiki></code>. For the use in special cases '''lang=''' could be left available to override the wiki language setting for a particular lemma.

* The '''word''' named parameter should be optional, and the word should be allowed to be passed as the first anonymous parameter, so we can write <code><nowiki>{{dict| abiit| en=he/she has left | nl=hij/zij is vertrokken }}</nowiki></code>.
: Disadvantage: That would make the lemma an unnamed parameter. Unnamed parameters are not stripped of leading and trailing spaces. This can lead to lemmas with extra spaces around them.
: Although: because it is the term in a definition list, leading spaces are ignored, and trailing spaces do not affect the layout (the displayed wiki text goes to a new line after the term), or are maybe also ignored.
: Can be implemented with <code><nowiki>{{{word|{{{1}}} }}}</nowiki></code> in the template. This accepts the first anonymous parameter, except when a '''word''' parameter was given when calling the template. This gives backward compatibility, where it is ''allowed'' to use the '''word''' parameter, but not ''mandatory''.

* Make it so that <kbd>Template:Dict</kbd> does not need an explicit list of language codes. The current list blocks additional translations from being added.
: The value of the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word can be used to create the name of the desired parameter, e.g. "en". See [https://www.mediawiki.org/wiki/Manual:Advanced_templates#Variable_parameter_name Mediawiki Advanced Templates Help: Variable parameter name].
:Code: <code><nowiki>;{{{word|{{{1}}} }}}:{{{{{PAGELANGUAGE}}}}}</nowiki></code>
: The use of <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> also makes '''en''' the default language.

* The current version outputs <code><nowiki>{{{en}}}</nowiki></code> if no '''default''' or language code parameter was given. Also produces <code><nowiki>'''{{{word}}}'''</nowiki></code> if no '''word''' parameter was given.
:This is probably actually a good thing, because it shows when there is an error and the template call should be edited to resolve this.
: '''documentation''': add to the docs what parameters should be given and what happens if one is missing.

* There should be a parameter to give the expansion of an abbreviation, separate from the translations. For example <code><nowiki>{{dict|A.D.|full=Anno Domini"|en=in the year of our lord|nl=in het jaar van de Heer}}</nowiki></code>. The wiki format to be produced needs to be invented. Possibly as extra text in parentheses added to the lemma, e.g.
:;A.D. (Anno Domini):in the year of our lord
:Or on the description line:
:;A.D.:'''Anno Domini''': in the year of our lord
: By putting the formatting in the template we can ensure that it is universal accross all pages.

=== Behaviour for missing description text ===
If there is no descriptive text parameter for the language of the page, then by default the template will show the lemma, but with an empty description.

This might be annoying for translations with relatively few translated descriptions (e.g. for brand new translated pages). The reader will be looking at a long list of lemmas with only a few descriptions.

A possible solution is the introduction of a '''show''' parameter, which will determine what will happen if the lemma has is no descriptive text for the current language. Possible values:
;quiet:Show nothing. Pages will only show the lemmas which have a description in the page's language.
;blank:The default. Show the lemma with a blank description.
;a language code:Substitute the description with the given language. (Complicated implementation; maybe wait if there is demand for it.)
If the parameter is not set then do the '''blank''' behaviour.

For this parameter to work, we need to set up a new cascade of parameter passing.
Then this parameter can be set on the main page for a language, e.g. initially '''quiet''' or '''nl''', later to be removed as the descriptions start to become more common.

== Restructuring the template cascade ==

The subdivision into templates for each letter of the alphabet is a pain in the <donkey>, and actually unnecessary.
We describe how it is structured currently (Feb 2006), and draw up a plan for a simpler structure.

=== The two paths to this template: why? ===
Find out why there are two paths to this template:
# Through [[Template:Latindict]] and [[Template:Latindict/A]] (and the other letters).
# Via non-template "Latin words and expressions/''letter''" pages.
This also happens for the Dutch translated pages, so we get
Latin words and expressions/nl/A
Latin words and expressions/nl/B
etc.
and also
Nl:Latijnse woorden en uitdrukkingen/A
Nl:Latijnse woorden en uitdrukkingen/A
etc.

At first the suspect in this was the French translation, which uses a translated French page for each letter page.

Looking at the page history of the pages involved to see what happened, it turns out these pages were created around the same time and by the same author as the templates. They might be a remnant of an earlier setup. Examination of the exact creation dates and time may shed more light.

While this is going on, the use of <kbd>Template:languages</kbd> and <kbd>Template:Dict/Glossary</kbd> on all these pages creates a tangled web of pages being linked to by other pages. For example
Nl:Latijnse woorden en uitdukkingen/A
is linked to by:
* The main Dutch page
* Itself
* The non-redirected version of itself
* The main French page
* Every other <kbd>Nl:Latijnse woorden en uitdukkingen/''letter''</kbd> page

=== The Reason ===
All these subpages were created in a desperate bid by the original author to split the list into separate pages, allowing an editor to edit the list only a letter-section at the time, rather than having to edit the entire list of thousands of lemmas.

Because the actual content of the article is transcluded, the normal "edit by section" mechanism does not work.

This problem is not trivial to solve. Idealy [https://www.mediawiki.org/ mediawiki] should have a built-in mechanism to redirect an action to edit a section to edit the section in the transcluded page.
: '''Find out''' if such a mechanism exists

The documentation on this subject is shockingly poor. We must find out through experimentation.

[[User:DomoViridi/Temsects|It turns out]] that the '''current Wiki''' implements this '''exactly as expected'''.
* Put the sections in a transcluded file
* Transclude that file in the main file
* Put a ToC in either the main file or the transcluded file (both work), with simple <code><nowiki>[[#A|A]]</nowiki></code> links
* The ToC links will show you the section on the main page
* The auto-generated edit links will open the transcluded file on that section
* It also works with [[User:DomoViridi/Temsects/nl|translated pages]]

=== Current structure ===

==== The main page [[Latin_words_and_expressions]] ====
This contains
* A warning box about the mixing of English and Dutch descriptions.
* A code to suppress the Table of Contents.
* A call to <kbd>Template:Languages</kbd>, to make automatic links to the translated pages.
* An introductory text.
* A call to <kbd>Template:Dict/Glossary</kbd>, passing the name of the page as a parameter. This generates a substitute Table of Contents, linking to all the letter sections which will be generated on this page. '''Note:''' instead of passing a literal copy of the name of the page, the code <code><nowiki>{{BASEPAGENAME}}</nowiki></code> should have been used by the template.
* A call to <kbd>Template:Latindict, with the language code as a parameter (<nowiki>{{latindict|en}}</nowiki>). The language code is not needed, as <kbd>Template:Dict</kbd> should have used the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word.
* A comment with instructions on where to edit lemmas.
* A Category link <code><nowiki>[[Category:Genealogy|L]]</nowiki></code>.

Translated pages such as [[Latin_words_and_expressions/nl]] (or the page they redirect to) contain the same, with adaptations.
* The introductory text is translated.
* The parameter passed to <kbd>Template:Dict/Glossary</kbd> changed to the translated page name. (Using <code><nowiki>{{BASEPAGENAME}}</nowiki></code> would have prevented this, but that issue is moot in the new structure.)
* The parameter passed to <kbd>Template:Latindict</kbd> is changed to the code for the translated language. (Again, this could have been automated using <code><nowiki>{{PAGELANGUAGE}}</nowiki></code>. Again, issue is moot in the new structure.)
* The instructions in the comment are translated.
* The Category link is translated: <code><nowiki>[[Category:Nl:Genealogie|Latijnse woorden]]</nowiki></code>.

==== Template:Latindict ====
This contains
* A list of sections, one for each letter of the alphabet, and one for the 'at' symbol (<kbd>@</kbd>), with a Level 2 header with that letter.
* In each letter section, a call to a sub-template for that letter (<code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> etc.). The language code (passed into <kbd>Template:Latindict</kbd> as the first parameter), is passed on as the first parameter to the sub-template.
* Nothing else.

==== Template:Latindict/A etc. ====
These contain
* the actual lemmas, in the form of a <kbd>Template:Dict</kbd> entry for each lemma:
<nowiki>{{dict|lang ={{{1}}} |word=abavia|default=betovergrootmoeder |en=second great grandmother}}</nowiki>
* A link (now dead) to the Dutch/Flemish source material, as a <kbd>noinclude</kbd> so it won't show up on the page, but ''is'' visible in the source. This could have been done with an HTML comment.
''(Note: the English description in the example should be 'great-great-grandmother'.)''

The parameters to <kbd>Template:Dict</kbd> are filled in as follows:
;lang:The language code was passed in as the first parameter, and is now copied into this parameter: <kbd><nowiki>lang={{{1}}}</nowiki></kbd>.
;word:Set to the Latin lemma.
;default:Set to the Dutch description (which is wrong, this should be changed to the '''nl''' parameter everywhere; this is the main cause of the English/Dutch mixing of the descriptions).
;en, nl, fr, etc:Descriptions in other languages are given as a parameter named after their language code. Texts for other languages can be added here, e.g. <kbd>fr=Arrière-arrière-grand-mère</kbd>.

==== Template:Dict ====
This finally generates a display list entry based on the parameters.

The template turns the parameters into a display list entry, with the format
<nowiki>;'''word''':description</nowiki>
(The lemma word does not need to be explicitly made bold, the description list format already does that.)
This results in
;word:description

=== New structure ===

==== The main page (and the translations) ====
* The warning box about the error will probably be gone by this time.
* The code to suppress the Table of Contents remains.
* The call to <kbd>Template:Languages</kbd> can remain unchanged.
* The introductory text can probably remain unchanged.
* The call to <kbd>Template:Dict/Glossary</kbd> must be removed.
* The call <kbd><nowiki>{{Latindict}}</nowiki></kbd> must remain unchanged, with the language of the page as the first parameter (because the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word does not work on this wiki).
* The comment with instructions must be updated to reflect the new situation, i.e. find the lemma in <kbd>Template:Latindict</kbd> and edit it there.

The translated page pages must do the same changes:
* Remove the call to <kbd>Template:Dict/Glossary</kbd>.
* Update the translation of the instructions.

The result will be that:
* The homebrew ToC entries will jump to that letter on the main page.
* The "Edit" link on each section will open an edit on the section '''in the template''', allowing direct editing of lemmas.

==== Template:Latindict ====
Change to contain:
* A Table-of-Contents header with in-page links to all the letters. This replaces the <kbd>Template:Dict/Glossary</kbd> call from the main page. If the user clicks on one of these links, the view should jump to that letter header on the same page. This helps the user find a lemma more quickly.
: There will only be one call for this, so there is no need for a template. A simple set of <code><nowiki>[[#A|A]] - [[#B|B]] -[[#C|C]] - [[#D|D]] - ...</nowiki></code> with a table around it should do the trick. Copy from the template contents and search/replace <code><nowiki>{{{1}}</nowiki>}/</code> with <code>#</code>. Note that this moves this fuctionality from the main page (and the translated pages) to this template (with only one occurence), useful in all translations of the main page.
* Sections for each letter (unchanged). Simple <code>== A ==</code> headers are enough.
* In each section replace the <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> with all the <code><nowiki>{{dict|...}}</nowiki></code> entries for that letter. These can be substituted in by changing <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> to <code><nowiki>{{subst:Latindict/A|{{{1}}}}}</nowiki></code> and saving the page. Repeat for all the letters.

If all goes as expected, the ToC links will bring you to the section on the main page, and the auto-generated edit links will open this template for editing on the chosen section.

By allowing editing-by-section, users will not be overburdened by edit pages which are too big. As a major advantage, it will be much easier for editors to find the lemma they want to edit, without the need to search for the correct lettered subpage.

==== Template:Latindict/A etc. ====
These can all be eliminated.

==== Template:Dict ====
This must be overhauled.
* Eliminate the '''lang''' parameter. Take the language from the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word. On this wiki this will always have a valid value.
** Unfortunately, <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> always produces "en" on this wiki. So we still need the '''lang''' parameter
* Eliminate the '''default''' parameter.
** Or better: Allow '''default''' as an alternative for '''nl'''. This gives backward compatiblilty with the existing calls to this template.
* Other improvements are described in the [[#Improvements to Dict template]] section

=== Pages no longer needed ===
With this new structure the following pages can be eliminated:
* All the lettered sub-templates (<kbd>Template:Latindict/A</kbd> etc.).
* All the <kbd>Main:</kbd> space lettered sub-pages (<kbd>Latin words and expressions/A</kbd> etc.).
* All the Dutch translated main space lettered sub-pages (<kbd>Latin words and expressions/A/nl</kbd> etc.), and the pages they redirect to (<kbd>Nl:Latijnse woorden en expressies/A</kbd> etc.).
* Same for the French translated pages. Although we will have to copy the descriptions from the French pages into the <kbd>Template:Dict</kbd> calls as <kbd>fr=</kbd> parameters first.
* Status of the Hebrew translated pages needs to be examined.

== Actions to take for modification ==

=== Set up a test environment ===
Set up a test environment to create and test a better version of the template without disturbing the existing one.
* (done) Create a Sandbox subspace to my user page: <kbd>User:DomoViridi/TempTest</kbd>; Think about the use or no-use of capital letters in the names of the pages first (doesn't realy matter). Put my own version of the pages there, but in the <kbd>User:DomoViridi/TempTest</kbd> space. Test templates can be called with the syntax <code><nowiki>{{User:DomoViridi/TempTest/mytemplate}}</nowiki></code> (the braces ensure transclusion, the <kbd>User:</kbd> namespace replaces the default <kbd>Template:</kbd> namespace.
* (done) Create a template page with the test template, [[User:DomoViridi/TempTest/Dict]]. Fill it initially with a copy of the original <kbd>Template:Dict</kbd>.
* (done) Create a page with test cases, [[User:DomoViridi/TempTest/Testcases]]. Put some calls to our Dict template in it, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus| en=silly sod| nl=sukkel}}</nowiki></code>. Add many testcases and put their source code in nowiki text above each.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict/A]] with calls to the Dict template, using <code><nowiki>{{User:DomoViridi/TempTest/Dict}}</nowiki></code>. Copy the existing "A" page and shorten it, leaving some useful examples, with different languages, some abbreviations, and some missing languages. Add French translations to some of the lemmas. Also copy a different letter page (a short one), which has some translations.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict]] which calls our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space.
* (done) Create a main page [[User:DomoViridi/TempTest/Latin words and expressions]], which calls <code><nowiki>{{User:DomoViridi/TempTest/Latindict}}</nowiki></code>.
: '''Oh hey!''', it turns out <kbd>Template:Dict/Glossary</kbd> creates links to [[Latin words and expressions/A]] and all the other letters.
* (done) Create lettered pages [[User:DomoViridi/TempTest/Latin words and expressions/A]] for each of the pages for wich we have a template, and fill them with a copy of the originals. which call our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space. Note that this is all duplicate work.
* (done) Create a translated page [[User:DomoViridi/TempTest/Latin words and expressions/nl]], fill it with the contents of [[Nl:Latijnse woorden en expressies]]. Change the calls to point to the sandbox, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Latindict | nl}}</nowiki></code> (passing the language to the template).
: '''Oh hey!''', once again we see how the clumsy <kbd>Template:Dict/Glossary</kbd> requires subpages of the translated page, one for each letter of the alphabet.
* (done) Create the translated subpages before moving the translated main page.
: Although: this does not help, because the letter pages are not subpages of the <kbd>.../nl</kbd> page, but are formed with <kbd>.../A/nl</kbd>.
* (done) Move the translated page to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies]]. This will automatically create a redirect from the <kbd>/nl</kbd> page to this page.
* (done) Move all the frakking translated subpages to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies/A]], again auto-generating a redirect.

Creating 27 (one for each letter of the alphabet, plus '@') lettered subpages each time for:
* The Templates
* The main page (English)
* The Dutch (nl) translation
* The redirect for the Dutch (nl) translation
* The French (fr) translation
* The redirect for the French (fr) translation
* The Hebrew (he) translation
* The redirect Hebrew (he) translation
* The same again for every new translation
is an unbelievable pile of unnecessary busywork. All so that we can have separate pages for every letter, and links to them.
Good thing I only did letters A and B for this sandbox.

''Note: the Gramps wiki does not support the [https://www.mediawiki.org/wiki/Extension:TemplateSandbox TemplateSandbox extension], which would have allowed to attach a sandbox subpage directly to the template. This means the <code><nowiki>{{testcases notice}}</nowiki></code> template is also not available.''

=== Create an improved Dict template ===
Do this in the sandbox. See the [[#Improvements to Dict template]] section.

Don't forget to adjust the documentation.

When it works with no detected problems, overwrite the actual template with our code.

=== Change "default" to "nl" ===
Because <kbd>Template:Dict</kbd> defaults to <nowiki>{{{en}}}</nowiki> if there is no description in a valid language, changing '''default''' to '''nl''' will result in a lot of bad output for all entries where '''en''' is missing.

This means we need to modify <kbd>Template:Dict</kbd> before we make this change.

Edit all the <kbd>Template:Latindict/<letter></kbd> pages to change '''default=''' to '''nl='''.
The effect should be that Dutch descriptions only show on the Dutch pages.
* Start with a small page and see how it goes.
* Then do a few more with export-to-editor, bulk search/replace, import from editor. Check for anomalies.
* Do the other pages

This should all have effect without the need to change the templates yet. It also makes room for a modification of <kbd>Template:Dict</kbd> which drops the '''default''' parameter.

=== Restructure the template cascade ===
Do this in the sandbox. See [[#Restructuring the template cascade]].
Make sure it works perfectly.

Before modifying the real pages, put notices in the talk pages and banners in any and all of the pages involved.

Then modify the real pages.

Try to get the useless pages deleted. At the least put a warning box in them. Something like "Do not use this page. Use page xxx instead. This page will be deleted in the near future".

=== Move the translated French pages ===
Copy all the existing French translations to the <kbd>Template:Latindict/<letter></kbd> pages.
Note: This leaves the translated French pages unchanged for now.
* Could be a big job.
* Have these pages changed much in the last few years?
* Put a notice on the Talk page for the French translation to tell them what is going on.
* Maybe put a banner on the pages too.
* Make sure they work nicely.

Switch the translated French page to use Template:Latindict
* One edit to [[Fr:Mots et expressions en latin]] should be enough.
* Add a notice to the French page about the change

=== Check the Hebrew pages ===
Check what the Hebrew pages look like now that we changed '''default=''' to '''nl='''.

=== Remove unneeded pages ===
Remove all the unneeded letter pages and letter templates, for each language that uses them.

=== Possible 'silent' mode ===
We may want to add a "silent" mode, where lemmas are not shown if there is no description for that language. This will avoid long pages of untranslated Latin words and expressions, and emphasise the lemmas that have been translated.

This will require an extra parameter, which must be passed down through all the templates. This named parameter should be given with a value, so that it evaluates to "take the then case" for the parser function:
<nowiki>{{#if:{{{silent|}}} | do silent version | do not-silent version}}</nowiki>
That means the parameter should be set as <kbd>"silent=<something>"</kbd>, with an arbitrary, non-empty value. See [https://www.mediawiki.org/wiki/Help:Parser_functions_in_templates Parser functions in templates]
* On page [[Latin words and expressions/fr]]: call template <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd> for silent and <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd> for not-silent.
* [[Template:Latindict]]: call <kbd><nowiki>{{Latindict/A|{{{1}}}|silent={{{silent|}}}}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* [[Template:Latindict/A]]: call <kbd><nowiki>{{Dict|lang={{{1}}}|silent={{{silent|}}}|word=...}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* Inside [[Template:Dict]] use <kbd><nowiki>{{#if: {{{silent|}}} | do silent stuff | do non-silent stuff}}</nowiki></kbd> (again with a bar after the parameter).

The following table shows how the parameter values trickle down to the <kbd>#if</kbd> parser, with or without the extra bar (<kbd>|</kbd>). The conclusion is that the extra bar should be used thoughout, and the parameter should be omitted for non-silent mode and passed with a value (e.g. <kbd>silent=yes</kbd>) for silent mode. The string used for the value (in this example "yes") does not matter. Note that passing the parameter with an empty string as a value ("<kbd>silent=</kbd>") will set the result to non-silent.

''Note: the use of the variables <kbd>s1</kbd>, <kbd>s2</kbd> and <kbd>s3</kbd> is arbitrary, and is used here for clarity. They could all be called <kbd>silent</kbd>.''

{| class="wikitable" style="margin:auto" width="90%"
|+ Passing on the silent parameter
! Main page
! <kbd>Latindict</kbd>
! <kbd>Latindict/A</kbd>
! <kbd>Dict</kbd>
! <kbd>#if</kbd>
|-
! style="text-align:right" | without bar
! <kbd><nowiki>s1={{{silent}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| then
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
! style="text-align:right" | with bar
! <kbd><nowiki>s1={{{silent|}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
|}

In the end, all the entries in [[Template:Latindict]] need to be modified, as must all calls to [[Template:Dict]] in all the letter templates ([[Template:Latindict/A]] etc.). And finally [[Template:Dict]] needs to implement the silent mode.

== Copyright ==
The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

User:DomoViridi/Temsects/Mydictionary

2026-03-11T18:32:15Z

DomoViridi: /* A */ Replace fixed text with calls to Dict

And here is a ToC from inside the template:

[[#A|A]] - [[#B|B]] - [[#C|C]]

== A ==
Words beginning with A.
{{User:DomoViridi/TempTest/Dict|lang=en|Apple|en=jummy}}
{{User:DomoViridi/TempTest/Dict|lang=en|Apricot|en=also jummy}}

== B ==
Words beginning with B.
;Beehive:humming
;B-hive:secondary hive

User:DomoViridi/TempTest

2026-03-11T18:27:43Z

DomoViridi: /* Template:Dict */ PAGELANGUAGE does not work; Keep "default" for backward compatibility

The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

== Sandbox to test templates ==

For [[Template:Latindict]], [[Template:Latindict/A]] (and all the other letter-subpages), [[Template:Dict/Glossary]], [[Template:Dict]], as used in [[Latin words and expressions]], and the translations [[Latin words and expressions/nl]], [[Latin words and expressions/fr]] and [[Latin words and expressions/he]].

== Improvements to Dict template ==

* The '''default''' parameter does not make sense, and should be eliminated. If there is no descriptive text for a given language, then the wiki page should show a blank line (or nothing).
: Before removing it, in all uses of this template '''default=''' should be replaced with '''nl='''. This is also the solution to the problem of showing lots of Dutch language descriptions on the English pages.

* The '''lang''' parameter is exclusively used as <code><nowiki>{{dict|lang ={{{1}}} |word=...</nowiki></code>, i.e. the value is read from the first unnamed parameter that was passed to <kbd>Template:Latindict/A</kbd>. This value cascades down from the main page.
: This cascade is unnecessary, because the template can use the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word. Entries can then be simplified to <code><nowiki>{{dict|word=...</nowiki></code>. For the use in special cases '''lang=''' could be left available to override the wiki language setting for a particular lemma.

* The '''word''' named parameter should be optional, and the word should be allowed to be passed as the first anonymous parameter, so we can write <code><nowiki>{{dict| abiit| en=he/she has left | nl=hij/zij is vertrokken }}</nowiki></code>.
: Disadvantage: That would make the lemma an unnamed parameter. Unnamed parameters are not stripped of leading and trailing spaces. This can lead to lemmas with extra spaces around them.
: Although: because it is the term in a definition list, leading spaces are ignored, and trailing spaces do not affect the layout (the displayed wiki text goes to a new line after the term), or are maybe also ignored.
: Can be implemented with <code><nowiki>{{{word|{{{1}}} }}}</nowiki></code> in the template. This accepts the first anonymous parameter, except when a '''word''' parameter was given when calling the template. This gives backward compatibility, where it is ''allowed'' to use the '''word''' parameter, but not ''mandatory''.

* Make it so that <kbd>Template:Dict</kbd> does not need an explicit list of language codes. The current list blocks additional translations from being added.
: The value of the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word can be used to create the name of the desired parameter, e.g. "en". See [https://www.mediawiki.org/wiki/Manual:Advanced_templates#Variable_parameter_name Mediawiki Advanced Templates Help: Variable parameter name].
:Code: <code><nowiki>;{{{word|{{{1}}} }}}:{{{{{PAGELANGUAGE}}}}}</nowiki></code>
: The use of <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> also makes '''en''' the default language.

* The current version outputs <code><nowiki>{{{en}}}</nowiki></code> if no '''default''' or language code parameter was given. Also produces <code><nowiki>'''{{{word}}}'''</nowiki></code> if no '''word''' parameter was given.
:This is probably actually a good thing, because it shows when there is an error and the template call should be edited to resolve this.
: '''documentation''': add to the docs what parameters should be given and what happens if one is missing.

* There should be a parameter to give the expansion of an abbreviation, separate from the translations. For example <code><nowiki>{{dict|A.D.|full=Anno Domini"|en=in the year of our lord|nl=in het jaar van de Heer}}</nowiki></code>. The wiki format to be produced needs to be invented. Possibly as extra text in parentheses added to the lemma, e.g.
:;A.D. (Anno Domini):in the year of our lord
:Or on the description line:
:;A.D.:'''Anno Domini''': in the year of our lord
: By putting the formatting in the template we can ensure that it is universal accross all pages.

=== Behaviour for missing description text ===
If there is no descriptive text parameter for the language of the page, then by default the template will show the lemma, but with an empty description.

This might be annoying for translations with relatively few translated descriptions (e.g. for brand new translated pages). The reader will be looking at a long list of lemmas with only a few descriptions.

A possible solution is the introduction of a '''show''' parameter, which will determine what will happen if the lemma has is no descriptive text for the current language. Possible values:
;quiet:Show nothing. Pages will only show the lemmas which have a description in the page's language.
;blank:The default. Show the lemma with a blank description.
;a language code:Substitute the description with the given language. (Complicated implementation; maybe wait if there is demand for it.)
If the parameter is not set then do the '''blank''' behaviour.

For this parameter to work, we need to set up a new cascade of parameter passing.
Then this parameter can be set on the main page for a language, e.g. initially '''quiet''' or '''nl''', later to be removed as the descriptions start to become more common.

== Restructuring the template cascade ==

The subdivision into templates for each letter of the alphabet is a pain in the <donkey>, and actually unnecessary.
We describe how it is structured currently (Feb 2006), and draw up a plan for a simpler structure.

=== The two paths to this template: why? ===
Find out why there are two paths to this template:
# Through [[Template:Latindict]] and [[Template:Latindict/A]] (and the other letters).
# Via non-template "Latin words and expressions/''letter''" pages.
This also happens for the Dutch translated pages, so we get
Latin words and expressions/nl/A
Latin words and expressions/nl/B
etc.
and also
Nl:Latijnse woorden en uitdrukkingen/A
Nl:Latijnse woorden en uitdrukkingen/A
etc.

At first the suspect in this was the French translation, which uses a translated French page for each letter page.

Looking at the page history of the pages involved to see what happened, it turns out these pages were created around the same time and by the same author as the templates. They might be a remnant of an earlier setup. Examination of the exact creation dates and time may shed more light.

While this is going on, the use of <kbd>Template:languages</kbd> and <kbd>Template:Dict/Glossary</kbd> on all these pages creates a tangled web of pages being linked to by other pages. For example
Nl:Latijnse woorden en uitdukkingen/A
is linked to by:
* The main Dutch page
* Itself
* The non-redirected version of itself
* The main French page
* Every other <kbd>Nl:Latijnse woorden en uitdukkingen/''letter''</kbd> page

=== The Reason ===
All these subpages were created in a desperate bid by the original author to split the list into separate pages, allowing an editor to edit the list only a letter-section at the time, rather than having to edit the entire list of thousands of lemmas.

Because the actual content of the article is transcluded, the normal "edit by section" mechanism does not work.

This problem is not trivial to solve. Idealy [https://www.mediawiki.org/ mediawiki] should have a built-in mechanism to redirect an action to edit a section to edit the section in the transcluded page.
: '''Find out''' if such a mechanism exists

The documentation on this subject is shockingly poor. We must find out through experimentation.

[[User:DomoViridi/Temsects|It turns out]] that the '''current Wiki''' implements this '''exactly as expected'''.
* Put the sections in a transcluded file
* Transclude that file in the main file
* Put a ToC in either the main file or the transcluded file (both work), with simple <code><nowiki>[[#A|A]]</nowiki></code> links
* The ToC links will show you the section on the main page
* The auto-generated edit links will open the transcluded file on that section
* It also works with [[User:DomoViridi/Temsects/nl|translated pages]]

=== Current structure ===

==== The main page [[Latin_words_and_expressions]] ====
This contains
* A warning box about the mixing of English and Dutch descriptions.
* A code to suppress the Table of Contents.
* A call to <kbd>Template:Languages</kbd>, to make automatic links to the translated pages.
* An introductory text.
* A call to <kbd>Template:Dict/Glossary</kbd>, passing the name of the page as a parameter. This generates a substitute Table of Contents, linking to all the letter sections which will be generated on this page. '''Note:''' instead of passing a literal copy of the name of the page, the code <code><nowiki>{{BASEPAGENAME}}</nowiki></code> should have been used by the template.
* A call to <kbd>Template:Latindict, with the language code as a parameter (<nowiki>{{latindict|en}}</nowiki>). The language code is not needed, as <kbd>Template:Dict</kbd> should have used the <code><nowiki>{{PAGELANGUAGE}}</nowiki></code> magic word.
* A comment with instructions on where to edit lemmas.
* A Category link <code><nowiki>[[Category:Genealogy|L]]</nowiki></code>.

Translated pages such as [[Latin_words_and_expressions/nl]] (or the page they redirect to) contain the same, with adaptations.
* The introductory text is translated.
* The parameter passed to <kbd>Template:Dict/Glossary</kbd> changed to the translated page name. (Using <code><nowiki>{{BASEPAGENAME}}</nowiki></code> would have prevented this, but that issue is moot in the new structure.)
* The parameter passed to <kbd>Template:Latindict</kbd> is changed to the code for the translated language. (Again, this could have been automated using <code><nowiki>{{PAGELANGUAGE}}</nowiki></code>. Again, issue is moot in the new structure.)
* The instructions in the comment are translated.
* The Category link is translated: <code><nowiki>[[Category:Nl:Genealogie|Latijnse woorden]]</nowiki></code>.

==== Template:Latindict ====
This contains
* A list of sections, one for each letter of the alphabet, and one for the 'at' symbol (<kbd>@</kbd>), with a Level 2 header with that letter.
* In each letter section, a call to a sub-template for that letter (<code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> etc.). The language code (passed into <kbd>Template:Latindict</kbd> as the first parameter), is passed on as the first parameter to the sub-template.
* Nothing else.

==== Template:Latindict/A etc. ====
These contain
* the actual lemmas, in the form of a <kbd>Template:Dict</kbd> entry for each lemma:
<nowiki>{{dict|lang ={{{1}}} |word=abavia|default=betovergrootmoeder |en=second great grandmother}}</nowiki>
* A link (now dead) to the Dutch/Flemish source material, as a <kbd>noinclude</kbd> so it won't show up on the page, but ''is'' visible in the source. This could have been done with an HTML comment.
''(Note: the English description in the example should be 'great-great-grandmother'.)''

The parameters to <kbd>Template:Dict</kbd> are filled in as follows:
;lang:The language code was passed in as the first parameter, and is now copied into this parameter: <kbd><nowiki>lang={{{1}}}</nowiki></kbd>.
;word:Set to the Latin lemma.
;default:Set to the Dutch description (which is wrong, this should be changed to the '''nl''' parameter everywhere; this is the main cause of the English/Dutch mixing of the descriptions).
;en, nl, fr, etc:Descriptions in other languages are given as a parameter named after their language code. Texts for other languages can be added here, e.g. <kbd>fr=Arrière-arrière-grand-mère</kbd>.

==== Template:Dict ====
This finally generates a display list entry based on the parameters.

The template turns the parameters into a display list entry, with the format
<nowiki>;'''word''':description</nowiki>
(The lemma word does not need to be explicitly made bold, the description list format already does that.)
This results in
;word:description

=== New structure ===

==== The main page (and the translations) ====
* The warning box about the error will probably be gone by this time.
* The code to suppress the Table of Contents remains.
* Add the code to prevent editing by section (user should edit template instead).
* Add an informative box to tell the user to edit the template rather than this page.
* The call to <kbd>Template:Languages</kbd> can remain unchanged.
* The introductory test can probably remain unchanged.
* The call to <kbd>Template:Dict/Glossary</kbd> must be removed.
* The call <kbd><nowiki>{{Latindict}}</nowiki></kbd> can be done without the language code passed as a parameter. The language of the descriptions shown will be handled in <kbd>Template:Dict</kbd> using <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd>.
* The comment with instructions must be updated to reflect the new situation, i.e. find the lemma in <kbd>Template:Latindict</kbd> and edit it there.

The translated page pages must do the same changes:
* Add the code to prevent editing by section.
* Add the informative box pointing to the template.
* Remove the call to <kbd>Template:Dict/Glossary</kbd>.
* Remove the language parameter from the <kbd>Template:Latindict</kbd> call.
* Update the translation of the instructions.

==== Template:Latindict ====
Change to contain:
* A Table-of-Contents header with in-page links to all the letters. This replaces the <kbd>Template:Dict/Glossary</kbd> call from the main page. If the user clicks on one of these links, the view should jump to that letter header on the same page. This helps the user find a lemma more quickly.
: There will only be one call for this, so there is no need for a template. A simple set of <code><nowiki>[[#A|A]] - [[#B|B]] -[[#C|C]] - [[#D|D]] - ...</nowiki></code> with a table around it should do the trick. Copy from the template contents and search/replace <code><nowiki>{{{1}}</nowiki>}/</code> with <code>#</code>. Note that this moves this fuctionality from the main page (and the translated pages) to this template (with only one occurence), useful in all translations of the main page.
* Sections for each letter (unchanged). Simple <code>== A ==</code> headers are enough.
* In each section replace the <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> with all the <code><nowiki>{{dict|...}}</nowiki></code> entries for that letter. These can be substituted in by changing <code><nowiki>{{Latindict/A|{{{1}}}}}</nowiki></code> to <code><nowiki>{{subst:Latindict/A|{{{1}}}}}</nowiki></code> and saving the page. Repeat for all the letters.

If all goes as expected, the ToC links will bring you to the section on the main page, and the auto-generated edit links will open this template for editing on the chosen section.

By allowing editing-by-section, users will not be overburdened by edit pages which are too big. As a major advantage, it will be much easier for editors to find the lemma they want to edit, without the need to search for the correct lettered subpage.

==== Template:Latindict/A etc. ====
These can all be eliminated.

==== Template:Dict ====
This must be overhauled.
* Eliminate the '''lang''' parameter. Take the language from the <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> magic word. On this wiki this will always have a valid value.
** Unfortunately, <kbd><nowiki>{{PAGELANGUAGE}}</nowiki></kbd> always produces "en" on this wiki. So we still need the '''lang''' parameter
* Eliminate the '''default''' parameter.
** Or better: Allow '''default''' as an alternative for '''nl'''. This gives backward compatiblilty with the existing calls to this template.
* Other improvements are described in the [[#Improvements to Dict template]] section

=== Pages no longer needed ===
With this new structure the following pages can be eliminated:
* All the lettered sub-templates (<kbd>Template:Latindict/A</kbd> etc.).
* All the <kbd>Main:</kbd> space lettered sub-pages (<kbd>Latin words and expressions/A</kbd> etc.).
* All the Dutch translated main space lettered sub-pages (<kbd>Latin words and expressions/A/nl</kbd> etc.), and the pages they redirect to (<kbd>Nl:Latijnse woorden en expressies/A</kbd> etc.).
* Same for the French translated pages. Although we will have to copy the descriptions from the French pages into the <kbd>Template:Dict</kbd> calls as <kbd>fr=</kbd> parameters first.
* Status of the Hebrew translated pages needs to be examined.

== Actions to take for modification ==

=== Set up a test environment ===
Set up a test environment to create and test a better version of the template without disturbing the existing one.
* (done) Create a Sandbox subspace to my user page: <kbd>User:DomoViridi/TempTest</kbd>; Think about the use or no-use of capital letters in the names of the pages first (doesn't realy matter). Put my own version of the pages there, but in the <kbd>User:DomoViridi/TempTest</kbd> space. Test templates can be called with the syntax <code><nowiki>{{User:DomoViridi/TempTest/mytemplate}}</nowiki></code> (the braces ensure transclusion, the <kbd>User:</kbd> namespace replaces the default <kbd>Template:</kbd> namespace.
* (done) Create a template page with the test template, [[User:DomoViridi/TempTest/Dict]]. Fill it initially with a copy of the original <kbd>Template:Dict</kbd>.
* (done) Create a page with test cases, [[User:DomoViridi/TempTest/Testcases]]. Put some calls to our Dict template in it, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Dict | lang=en| word=sillius soddus| en=silly sod| nl=sukkel}}</nowiki></code>. Add many testcases and put their source code in nowiki text above each.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict/A]] with calls to the Dict template, using <code><nowiki>{{User:DomoViridi/TempTest/Dict}}</nowiki></code>. Copy the existing "A" page and shorten it, leaving some useful examples, with different languages, some abbreviations, and some missing languages. Add French translations to some of the lemmas. Also copy a different letter page (a short one), which has some translations.
* (done) Create a sample template page [[User:DomoViridi/TempTest/Latindict]] which calls our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space.
* (done) Create a main page [[User:DomoViridi/TempTest/Latin words and expressions]], which calls <code><nowiki>{{User:DomoViridi/TempTest/Latindict}}</nowiki></code>.
: '''Oh hey!''', it turns out <kbd>Template:Dict/Glossary</kbd> creates links to [[Latin words and expressions/A]] and all the other letters.
* (done) Create lettered pages [[User:DomoViridi/TempTest/Latin words and expressions/A]] for each of the pages for wich we have a template, and fill them with a copy of the originals. which call our <kbd>Latindict/A</kbd> template using <code><nowiki>{{User:DomoViridi/TempTest/Latindict/A}}</nowiki></code>, and any other letter pages from the test space. Note that this is all duplicate work.
* (done) Create a translated page [[User:DomoViridi/TempTest/Latin words and expressions/nl]], fill it with the contents of [[Nl:Latijnse woorden en expressies]]. Change the calls to point to the sandbox, e.g. <code><nowiki>{{User:DomoViridi/TempTest/Latindict | nl}}</nowiki></code> (passing the language to the template).
: '''Oh hey!''', once again we see how the clumsy <kbd>Template:Dict/Glossary</kbd> requires subpages of the translated page, one for each letter of the alphabet.
* (done) Create the translated subpages before moving the translated main page.
: Although: this does not help, because the letter pages are not subpages of the <kbd>.../nl</kbd> page, but are formed with <kbd>.../A/nl</kbd>.
* (done) Move the translated page to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies]]. This will automatically create a redirect from the <kbd>/nl</kbd> page to this page.
* (done) Move all the frakking translated subpages to a page with the translated title e.g. [[User:DomoViridi/TempTest/Nl:Latijnse woorden en expressies/A]], again auto-generating a redirect.

Creating 27 (one for each letter of the alphabet, plus '@') lettered subpages each time for:
* The Templates
* The main page (English)
* The Dutch (nl) translation
* The redirect for the Dutch (nl) translation
* The French (fr) translation
* The redirect for the French (fr) translation
* The Hebrew (he) translation
* The redirect Hebrew (he) translation
* The same again for every new translation
is an unbelievable pile of unnecessary busywork. All so that we can have separate pages for every letter, and links to them.
Good thing I only did letters A and B for this sandbox.

''Note: the Gramps wiki does not support the [https://www.mediawiki.org/wiki/Extension:TemplateSandbox TemplateSandbox extension], which would have allowed to attach a sandbox subpage directly to the template. This means the <code><nowiki>{{testcases notice}}</nowiki></code> template is also not available.''

=== Create an improved Dict template ===
Do this in the sandbox. See the [[#Improvements to Dict template]] section.

Don't forget to adjust the documentation.

When it works with no detected problems, overwrite the actual template with our code.

=== Change "default" to "nl" ===
Because <kbd>Template:Dict</kbd> defaults to <nowiki>{{{en}}}</nowiki> if there is no description in a valid language, changing '''default''' to '''nl''' will result in a lot of bad output for all entries where '''en''' is missing.

This means we need to modify <kbd>Template:Dict</kbd> before we make this change.

Edit all the <kbd>Template:Latindict/<letter></kbd> pages to change '''default=''' to '''nl='''.
The effect should be that Dutch descriptions only show on the Dutch pages.
* Start with a small page and see how it goes.
* Then do a few more with export-to-editor, bulk search/replace, import from editor. Check for anomalies.
* Do the other pages

This should all have effect without the need to change the templates yet. It also makes room for a modification of <kbd>Template:Dict</kbd> which drops the '''default''' parameter.

=== Restructure the template cascade ===
Do this in the sandbox. See [[#Restructuring the template cascade]].
Make sure it works perfectly.

Before modifying the real pages, put notices in the talk pages and banners in any and all of the pages involved.

Then modify the real pages.

Try to get the useless pages deleted. At the least put a warning box in them. Something like "Do not use this page. Use page xxx instead. This page will be deleted in the near future".

=== Move the translated French pages ===
Copy all the existing French translations to the <kbd>Template:Latindict/<letter></kbd> pages.
Note: This leaves the translated French pages unchanged for now.
* Could be a big job.
* Have these pages changed much in the last few years?
* Put a notice on the Talk page for the French translation to tell them what is going on.
* Maybe put a banner on the pages too.
* Make sure they work nicely.

Switch the translated French page to use Template:Latindict
* One edit to [[Fr:Mots et expressions en latin]] should be enough.
* Add a notice to the French page about the change

=== Check the Hebrew pages ===
Check what the Hebrew pages look like now that we changed '''default=''' to '''nl='''.

=== Remove unneeded pages ===
Remove all the unneeded letter pages and letter templates, for each language that uses them.

=== Possible 'silent' mode ===
We may want to add a "silent" mode, where lemmas are not shown if there is no description for that language. This will avoid long pages of untranslated Latin words and expressions, and emphasise the lemmas that have been translated.

This will require an extra parameter, which must be passed down through all the templates. This named parameter should be given with a value, so that it evaluates to "take the then case" for the parser function:
<nowiki>{{#if:{{{silent|}}} | do silent version | do not-silent version}}</nowiki>
That means the parameter should be set as <kbd>"silent=<something>"</kbd>, with an arbitrary, non-empty value. See [https://www.mediawiki.org/wiki/Help:Parser_functions_in_templates Parser functions in templates]
* On page [[Latin words and expressions/fr]]: call template <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd> for silent and <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd> for not-silent.
* [[Template:Latindict]]: call <kbd><nowiki>{{Latindict/A|{{{1}}}|silent={{{silent|}}}}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* [[Template:Latindict/A]]: call <kbd><nowiki>{{Dict|lang={{{1}}}|silent={{{silent|}}}|word=...}}</nowiki></kbd> (with a bar after the parameter). The same for all the other letter-subtemplates.
* Inside [[Template:Dict]] use <kbd><nowiki>{{#if: {{{silent|}}} | do silent stuff | do non-silent stuff}}</nowiki></kbd> (again with a bar after the parameter).

The following table shows how the parameter values trickle down to the <kbd>#if</kbd> parser, with or without the extra bar (<kbd>|</kbd>). The conclusion is that the extra bar should be used thoughout, and the parameter should be omitted for non-silent mode and passed with a value (e.g. <kbd>silent=yes</kbd>) for silent mode. The string used for the value (in this example "yes") does not matter. Note that passing the parameter with an empty string as a value ("<kbd>silent=</kbd>") will set the result to non-silent.

''Note: the use of the variables <kbd>s1</kbd>, <kbd>s2</kbd> and <kbd>s3</kbd> is arbitrary, and is used here for clarity. They could all be called <kbd>silent</kbd>.''

{| class="wikitable" style="margin:auto" width="90%"
|+ Passing on the silent parameter
! Main page
! <kbd>Latindict</kbd>
! <kbd>Latindict/A</kbd>
! <kbd>Dict</kbd>
! <kbd>#if</kbd>
|-
! style="text-align:right" | without bar
! <kbd><nowiki>s1={{{silent}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| <kbd><nowiki>{{{silent}}}</nowiki></kbd>
| then
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
! style="text-align:right" | with bar
! <kbd><nowiki>s1={{{silent|}}}</nowiki></kbd>
! <kbd><nowiki>s2={{{s1|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}</nowiki></kbd>
! <kbd><nowiki>{{{s2|}}}|then|else</nowiki></kbd>
|-
| <kbd><nowiki>{{Latindict|fr}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=}}</nowiki></kbd>
| empty string
| empty string
| empty string
| else
|-
| <kbd><nowiki>{{Latindict|fr|silent=yes}}</nowiki></kbd>
| yes
| yes
| yes
| then
|-
|}

In the end, all the entries in [[Template:Latindict]] need to be modified, as must all calls to [[Template:Dict]] in all the letter templates ([[Template:Latindict/A]] etc.). And finally [[Template:Dict]] needs to implement the silent mode.

== Copyright ==
The contents of this page is © Copyright 2026 by DomoViridi. All rights reserved.

Template:Dict/doc

2026-03-11T17:59:29Z

DomoViridi: /* Usage */ Unnamed parameter: do not end in newline

This template produces one lemma plus a description in a selected language.

It is intended for the [[Latin words and expressions]] article and its translated pages, where in every translation the lemmas are in Latin, but the description should only show the selected translation.

== Code ==
(Prettified for clarity. The actual code avoids extra newlines and spaces.)
<nowiki>;{{{word|{{{1}}} }}}{{#if:{{{full|}}}| - {{{full}}} }}:
{{#ifeq: {{{lang|}}} | nl
| {{{nl|{{{default|}}} }}}
| {{{ {{{lang}}}| }}}
}}</nowiki>

Explanation:
* Start the display list entry <code>;lemma:...</code>:
** Use either '''word''' or the '''first parameter''' for the lemma.
** If '''full''' was given, attach it to the lemma.
** Separate the expansion of the abbreviation from the main lemma with a dash.
* Continue with the description text:
** If '''lang''' is nl then
*** Use the '''nl''' parameter. It it's missing, use the '''default''' parameter
** For any other language:
*** Expand the '''lang''' parameter, giving us a country code
*** Use that country code as the name of a parameter, and fill in the value of that parameter.

== Usage ==

Recommended standard use:
<nowiki>{{Dict|lang=en|sillius soddus|
en=silly sod|
nl=sukkel|
... (descriptions in more languages)
}}</nowiki>
''Note: unnamed parameters should not end in a newline''

The lemma can also be passed in the '''word''' parameter:
<nowiki>{{Dict|lang=nl
|word=sillius soddus
|en=silly sod
|nl=sukkel
}}</nowiki>

Legacy usage with '''default''' parameter for Dutch description:
<nowiki>{{Dict|lang=en
|word=sillius soddus
|default=sukkel
|en=silly sod
}}</nowiki>

Usage for an abbreviation, with '''full''' parameter:
<nowiki>{{Dict|lang=en|A.D.|full=Anno Domini
|en=in the year of our Lord
|nl=in het jaar onzes Heren
}}</nowiki>

Example where the requested translated text is not yet available (yields only lemma):
<nowiki>{{Dict|lang=en|sillius soddus|default=sukkel}}</nowiki>

== Parameters ==

* The '''lang''' parameter is mandatory, and must be the country code for the language to be shown. Its value will be used to select which country code parameter will be used for the description text. In normal use the editor does not need to fill in this parameter. It will be passed into the template where this template is used. Usual calls to this template will look like:
<nowiki>{{Dict|lang={{}}|word=...|en=...|...}}</nowiki>

* The first unnamed parameter will be printed as the lemma. It can also be passed as the '''word''' parameter.

* The '''full''' parameter is optional, and useful for abbreviations, to add the full (i.e. expanded) version of the lemma. It will be added (with some formatting) to the lemma text.

* The other parameters give the description text for various languages. The name of the parameter must be the country code for the language in which the description is written.

* For historic reasons, '''default''' is allowed as an alternative for '''nl'''. Do not use the '''default''' parameter for new entries, use '''nl''' instead. This parameter is obsolete, and its support will be withdrawn in the future.

It is advisable to have at least an '''en''' parameter, so descriptions will show up on the default English page.

== The output ==

This template will construct a description list entry (a bold lemma, with on the next line an indented description).
The description will be chosen from the list of descriptions in different languages the one given in the '''lang''' parameter.

On an English page (default)
;sillius soddus:silly sod
On a Dutch page
;sillius soddus:sukkel
With an expanded abbreviation
;A.D. - Anno Domini: the year of our Lord
;S.S. - Sillius Soddus: silly sod
If the requested language is not available
;sillius soddus:

If the chosen language (corresponding to the language of the page) is not present in the list given in the template call, only the lemma will be printed.
[[Category:Templates]]

Latin words and expressions/B

2026-03-11T17:29:13Z